AVAYA 4621SW SIP logs off from Asterisk 1.4.36

Asterisk Asterisk Support
1

Dear Community,

I have Asterisk 1.4.36 setup for some time and its working without problems until I installed one AVAYA 4621SW phone.
For a while it seemed that everything was working well, phone registered with asterisk, until the next day in the office when I realized that the phone lost the registration. The screen was showing same info as if it was logged on - no difference, just you couldn’t make or receive calls. After a reset everything was OK again.

Here is some additional info:
I successfully updated firmware to s20d01b2_2_2.bin application file and b20d01b2_9_1.bin boot file and uploaded 46xxsettings.txt to the phone through TFTP.

I’m forwarding to you part of the asterisk log file relevant to 4621sw phone I am having problems with.
It goes unreachable once per day in average except for Nov 11 since on that day I played with OUTBOUND_SUBSCRIPTION_REQUEST_DURATION values of AVAYA cfg file.

root@sip:/var/log/asterisk# grep -i REACHABLE messages | grep 2077165
[Nov 8 13:02:46] NOTICE[4176] chan_sip.c: Peer ‘2077165’ is now Reachable. (126ms / 2000ms)
[Nov 8 20:55:51] NOTICE[4176] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 83
[Nov 9 09:51:49] NOTICE[4176] chan_sip.c: Peer ‘2077165’ is now Reachable. (78ms / 2000ms)
[Nov 9 10:35:01] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (49ms / 2000ms)
[Nov 9 15:44:55] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 87
[Nov 10 08:57:16] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (79ms / 2000ms)
[Nov 10 09:15:21] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 49
[Nov 10 09:17:03] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (80ms / 2000ms)
[Nov 10 17:10:08] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 83
[Nov 11 09:35:02] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (123ms / 2000ms)
[Nov 11 10:56:07] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 48
[Nov 11 10:57:23] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (82ms / 2000ms)
[Nov 11 14:26:26] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 47
[Nov 11 14:53:23] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (80ms / 2000ms)
[Nov 11 14:53:51] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 80
[Nov 11 15:18:09] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (125ms / 2000ms)
[Nov 11 23:11:13] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now UNREACHABLE! Last qualify: 91
[Nov 12 09:19:27] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (125ms / 2000ms)
[Nov 12 09:22:05] NOTICE[1937] chan_sip.c: Peer ‘2077165’ is now Reachable. (132ms / 2000ms)

If I can provide You with more details about the problem, just ask, I will be more than glad to help You help me :wink:

Thank You for your time
Regards,
Gnev

2

Do you have qualify or qualifyfreq set for that peer in sip.conf?

3

Thank you for response malcolmd.

My coning regarding those fields for the peer is as follows:
qualify=yes
qualifyfreq=60

I also tried without these values defined, but without success. Should I try something else?

Regards

4

Howdy,

You did:

And that made the phone’s registration not timeout?

5

On Nov 11 I reset the phone several times for testing diferent values of OUTBOUND_SUBSCRIPTION_REQUEST_DURATION which could be the reason for multiple reachable/UNREACHABLE! messages for that day.

Subscription Request Duration Specifies the duration of initial SUBSCRIBE messages sent from the phone. May be lowered by the server. Maximum is one year , default is one day.

I set this value to one year, but It seems that asterisk is ignoring this.

6

when you upgraded the firmware, was that to set the phone to sip? I always thought the 4621’s were H323 phones? Thats what we set the users to when we create them in the IP Office… Also what steps did you use to get asterisk and the phone talking? Just setup a tftp server, then drop the bin files and the 46xxsettings onto it? Did you have to make any changes to the 46xxsettings file? What do you need in sip.conf/h323.conf to get it working? Thanks

7

4621SW can work with both SIP and H323 protocols
I updated firmware over TFTP like you described (46xxupgrade.scr tells which files to be loaded)
both R2.2.2 SIP release for the 4602/4602SW/4610SW/4620SW/4621SW
and
R2.9 SP1 H.323 GA release for the 4610SW, 4620SW, 4621SW and 4622SW
were updated in the process

I didn’t have to change nothing in 46xxsettings file, it was working right away, I did however change few settings concerning VLAN setup and some other non crucial setting like date/time format etc…

I added new peer in sip.conf, and that is about all I did to make it work, but still can’t figure out why it suddenly loses registration after a while.

[2077165] context=from-jugotrade-national-gsm username=2077165 secret=**** type=friend callerid="Miroljub Labus" <2077165> host=dynamic nat=yes canreinvite=no disallow=all allow=g729 allow=alaw qualify=yes qualifyfreq=60 mailbox=2077165@jugotrade notifyringing=yes accountcode=jugotrade qualify=yes dtmfmode = rfc2833 pickupgroup=24,15 callgroup=24

If someone still has an idea what could be a cause for this, your input is appreciated.
Regards