Phone Disconnects After 6 Seconds

jeffrappvmi · ‎05-31-2013

So here's my problem. I have a new SPA504G that I added to our network, and is having some issues that seem to be netowork related. Our Asterisk phone server is located at 192.168.1.40, and DHCP assiged the phone to 192.168.2.200. Both have the netmask set to 255.255.240.0, and I can ping, access the web interface, and pretty much everything from my computer at 192.168.1.147.

The problem is with calling. The phone is registered to the server, and I can dial out, but I'm disconnected after 6 seconds every time. I also think that maybe my outgoing audio isn't working, either, but haven't been able to confirm that.

If I manually assign the phone to something in the 192.168.1.x range, it works perfectly.

Any ideas what could be causing this?

I was able to attach the phone to a syslogger:

5/30/2013 3:31:32 PM [20] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_DOWN) par=(10) par2=(0x0)

5/30/2013 3:31:32 PM [21] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_GETCURLINE) par=(0) par2=(0x0)

5/30/2013 3:31:32 PM [22] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_UP) par=(10) par2=(0x0)

5/30/2013 3:31:33 PM [23] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_UP) par=(3) par2=(0x0)

5/30/2013 3:31:33 PM [24] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_UP) par=(4) par2=(0x0)

5/30/2013 3:31:41 PM [25] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_DOWN) par=(10) par2=(0x0)

5/30/2013 3:31:41 PM [29] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_UP) par=(3) par2=(0x0)

5/30/2013 3:31:41 PM [28] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_UP) par=(4) par2=(0x0)

5/30/2013 3:31:41 PM [26] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_GETCURLINE) par=(0) par2=(0x0)

5/30/2013 3:31:41 PM [27] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_KEY_UP) par=(10) par2=(0x0)

5/30/2013 3:31:42 PM [35] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_NEWCALLSTATE) par=(0) par2=(0x8)

5/30/2013 3:31:42 PM [34] From: (192.168.4.201) Fac:16 Sev:6 Msg >>>

5/30/2013 3:31:42 PM [38] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_NEWCALLSTATE) par=(0) par2=(0xd)

5/30/2013 3:31:42 PM [37] From: (192.168.4.201) Fac:16 Sev:6 Msg >>>

5/30/2013 3:31:42 PM [33] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [0]CC:NewCallState 8/6

5/30/2013 3:31:42 PM [30] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [CMXHTTP] force stop wav

5/30/2013 3:31:42 PM [32] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [CMXHTTP] force stop wav

5/30/2013 3:31:42 PM [31] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_GETCURLINE) par=(0) par2=(0x0)

5/30/2013 3:31:42 PM [36] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [0]CC:NewCallState 13/8

5/30/2013 3:31:48 PM [41] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [PHONEAPP]: PHN_eventProc msg=(WM_SYS_NEWCALLSTATE) par=(0) par2=(0x0)

5/30/2013 3:31:48 PM [39] From: (192.168.4.201) Fac:16 Sev:6 Msg >>> [0]CC:NewCallState 0/13

5/30/2013 3:31:48 PM [40] From: (192.168.4.201) Fac:16 Sev:6 Msg >>>

edit: Firmware is up-to-date with version 7.5.4.

Steven Howes · ‎05-31-2013

192.168.1.40 and 192.168.2.200 are not in the same subnet if the mask is 255.255.255.240 (that mask only has 16 hosts per subnet) - I bet your PC can access both as it has an invalid mask on it.

jeffrappvmi · ‎05-31-2013

Looks like I got generous with the 255s on that. It actually is set to 255.255.240.0. I edited my post above to reflect that.

jeffrappvmi · ‎05-31-2013

Ok, figured it out. It was actually an Asterisk issue. Haven't had DHCP assign any phones into the 192.168.2.x range yet, so this was a new experience.

Just needed to add the localnet value in the sip_nat.conf file, and it started working.

Thanks!