SIP sets disconnect

[asterisk18]

Greetings everyone,

I am supporting a CS1000E Rls. 7.5 (with CPMG128 Linux) and for the last month I have been receiving complaints that the SIP sets (12 extensions - remote site) disconnect during conversation. This happens 3-4 times a day on most of the extensions.

I did some troubleshooting using the "slgTrace" commands and I captured these messages for extension 2112 (the user complained of dropped line at this time):

cs1ke vtrk: (ERROR) tSSG: ITG2107 Proxy Server / Redirect Server <10.59.229.53:5060> unreachable (7)
Jun 17 11:24:50 cs1ke vtrk: (WARNING) tSSG: sipNpmKeepAliveResTimerEv: Primary proxy <10.59.229.53:5060> (transport=TCP) lost for 3 times...
cs1ke vtrk: (WARNING) tSSG: sipNpmProxyAddrSwap: The current Active Proxy(Primary NRS) is down
cs1ke vtrk: (WARNING) tSSG: sipNpmProxyAddrSwap: Secondary Proxy has invalid IP address, try third-level NRS
cs1ke vtrk: (WARNING) tSSG: sipNpmProxyAddrSwap:: All proxies are down, set flag sessionStatusNotify
cs1ke vtrk: (WARNING) tSSG: sipNpmProxyAddrSwap: failsafe or tertiary proxy not configured
cs1ke vtrk: (INFO) tSLG: User "sp2112" TN 248-00-00-01 slgUsmMsgHandler: USM received for TN 0xf801 keyNum=0
cs1ke vtrk: (INFO) tSLG: User "sp2112" TN 248-00-00-01 slgUsmPdnUnringHandler: PDN Un-Ring on key 0 -- callID 0x24d97, from 1994-41
cs1ke vtrk: (ERROR) tSLG: User "sp2112" TN 248-00-00-01 slgUsmPdnUnringHandler: USM-Unring ignored -- failed to find uadn call for (2112->1994-41), id 0x24d97
cs1ke vtrk: (WARNING) tSLG: User "sp2112" TN 248-00-00-01 slgUsmPdnUnringHandler: No more call legs from call 1994-41->2112, clean up data structure
cs1ke vtrk: (INFO) tSLG: INCOMING: 03 3b 00 00 f8 01 16 1a 00 00 00 00 37 02 f8 01 36 02 21 12 3b 01 08 38 01 03 3a 02 70 84 39 04 19 94 f4 10 3c 01 09 96 04 00 02 4d 97 5f 07 11 06 14 0d 0b 18 34 e2 04 00 2b 00 29

The system was patched at installation time; "DepList 1: core Issue: 01 (created: 2011-05-24 10:13:35)".
I also asked the Network admin of the site to check the switches and routers for any problems. He didn't find any errors.

Any idea what the logs indicate and/or what else I should check?

Thanks.

*

 

[gwebster]

If I am reading your information correctly, this system has not been patched since it was installed two years ago. I would start by getting it patched to current.

 

[monkey101]

I would definitely get your sig servers patched. I had that issue about a year and a half ago and patching resolved it.