Matthew Boehm
2004-Sep-23 13:33 UTC
[Asterisk-Users] Cisco 7960G, SIP, NAT, Qualify and Unreachable
Hey, I just started trying to use the qualify=yes option on my Cisco 7960 SIP phones. Of the 13 I have, 2 of them seem to loose their registration with asterisk on a regular basis. I see lots of these lines: -- Registered SIP '3030' at 62.74.107.1 port 58825 expires 60 in my console. But I only see them for 2 extensions. Never see them for the other 11. All 13 phones have the exact same configuration with the exception of the extension number in sip.conf and on the phone itself. I have no idea why these 2 phones refuse to stay constantly connected like the others. So I am trying to use 'qualify' to get * to "ping" them to keep them registered/connected. I tested it on my phone which is not one of the 2. As soon as I reloaded sip.conf, I got this: NOTICE[1087584960]: Peer '3044' is now UNREACHABLE! And 'sip show peers' shows: 3044/matthew304 62.74.107.1 D N 255.255.255.255 44854 UNREACHABLE and calls to that phone get pushed to the 'unreachable' category in my dialplan. Its been like that for the past 20 min. Why isn't anything happening? Should't I be getting some notice every 2 seconds (the qualify default) that something is happening? Thanks, Matthew
Rich Adamson
2004-Sep-23 14:54 UTC
[Asterisk-Users] Cisco 7960G, SIP, NAT, Qualify and Unreachable
> I just started trying to use the qualify=yes option on my Cisco 7960 SIP > phones. Of the 13 I have, 2 of them seem to loose their registration with > asterisk on a regular basis. I see lots of these lines: > > -- Registered SIP '3030' at 62.74.107.1 port 58825 expires 60 > > in my console. But I only see them for 2 extensions. Never see them for the > other 11. All 13 phones have the exact same configuration with the exception > of the extension number in sip.conf and on the phone itself. > > I have no idea why these 2 phones refuse to stay constantly connected like > the others. > > So I am trying to use 'qualify' to get * to "ping" them to keep them > registered/connected. > > I tested it on my phone which is not one of the 2. As soon as I reloaded > sip.conf, I got this: > > NOTICE[1087584960]: Peer '3044' is now UNREACHABLE! > > And 'sip show peers' shows: > > 3044/matthew304 62.74.107.1 D N 255.255.255.255 44854 > UNREACHABLE > > and calls to that phone get pushed to the 'unreachable' category in my > dialplan. > > Its been like that for the past 20 min. Why isn't anything happening? > Should't I be getting some notice every 2 seconds (the qualify default) that > something is happening?Without a trace, its hard to guess at what might be happening. First guess is... - the 7960 defaults to registering every 600 sec (SIPDefault.cnf) - your firewall next to the 7960 has a short udp timeout value and drops the table entry - * can't ping it (regardless of the qualify setting) as the firewall is blocking the path My 'sip show peers' is like: Name/username Host Dyn Nat ACL Mask Port Status 3021/3021 216.223.173.111 D 255.255.255.255 5060 Unmonitored 3020/3020 216.223.173.111 D 255.255.255.255 5060 Unmonitored 3015/3015 217.15.121.42 D N 255.255.255.255 5060 OK (193 ms) 3014/3014 217.15.121.42 D N 255.255.255.255 5060 OK (193 ms) where the 3015 & 3014 exten's are qualify=yes. They are behind a Linksys FW. Not sure why your display is not showing port 5060 though. You might change the SIPDefault.cnt to something like 120 to see if that impacts it at all. Rich