MSD-1001 S-Series Panels deregistering from SIP server after 10 minutes

Can anyone make heads or tails of this? we have nine MSD-1001 panels that all
seem to de-register from an Asterisk SiP server after 10 or so minutes.

I am setting the SiP parameters in the actual panel and they work great for a while
but seem stop after 10 or so minutes. The log indicates the panel losing connection
to the master but the panels keep on doing their control functions. They still show as
registered in the panel settings but do not ring even after disabling, saving and re-enabling
sip. I have reboot the panels for them to start working again for 10 minutes..
Any ideas? AMX tech are looking into it but want where shark traces...

Log files from one of the panels below.....


01/09 17:15:22.12 [849462368] Diag :CommandParser::Command ^TXT-101,0,006
01/09 17:15:22.13 [849462368] Diag :CommandParser::Command ^TXT-102,0,00:41:40
01/09 17:15:23.01 [849462368] Diag :CommandParser::Command ^TXT-100,0,
01/09 17:15:23.02 [849462368] Diag :CommandParser::Command ^TXT-101,0,
01/09 17:15:23.03 [849462368] Diag :CommandParser::Command ^TXT-102,0,Loading
01/09 17:15:39.01 [857850976] Diag :SIP stats: memory 18, dialog 1 tact 1
01/09 17:15:39.06 [857850976] Diag :$$$$$$$$ SipStackCallback CALLED rq_method=0 status_code=401
01/09 17:15:39.07 [857850976] Diag :CPAPP RECEIVE msg: method=RESPONSE
01/09 17:15:39.07 [857850976] Diag : status_code=401
01/09 17:15:39.07 [857850976] Diag :SIP stats: memory 22, dialog 1 tact 2
01/09 17:15:39.12 [857850976] Diag :$$$$$$$$ SipStackCallback CALLED rq_method=5 status_code=0
01/09 17:15:39.12 [857850976] Diag :CPAPP RECEIVE msg: method=OPTIONS
01/09 17:15:39.12 [857850976] Diag : CONNID=3
01/09 17:15:39.12 [857850976] Diag :SIP stats: memory 42, dialog 2 tact 3
01/09 17:15:39.17 [857850976] Diag :$$$$$$$$ SipStackCallback CALLED rq_method=0 status_code=200
01/09 17:15:39.17 [857850976] Diag :CPAPP RECEIVE msg: method=RESPONSE
01/09 17:15:39.17 [857850976] Diag : status_code=200
01/09 17:15:39.17 [857850976] Diag :SIP stats: memory 41, dialog 2 tact 3
01/09 17:15:39.22 [857850976] Diag :$$$$$$$$ SipStackCallback CALLED rq_method=10 status_code=0
01/09 17:15:39.22 [857850976] Diag :CPAPP RECEIVE msg: method=NOTIFY
01/09 17:15:39.22 [857850976] Diag : CONNID=3
01/09 17:15:39.22 [857850976] Diag :CPSIP_METHOD_NOTIFY: Got NOTIFY for event message-summary length 86
01/09 17:15:39.22 [857850976] Diag :SipUserAgentManager::MessageWaiting Messages waiting: no 0/0 0/0

01/09 17:15:39.22 [857850976] Diag :SIP stats: memory 58, dialog 3 tact 4
01/09 17:15:44.02 [857850976] Diag :SIP stats: memory 52, dialog 3 tact 2
01/09 17:16:11.03 [857850976] Diag :SIP stats: memory 15, dialog 1 tact 0
01/09 17:16:25.76 [1041056864] Diag :ICSPRouter::onOnlineEvent state:0
01/09 17:16:26.02 [1041056864] Info :CommunicationDispatcher::masterOffline
01/09 17:16:26.02 [1041056864] Info :Master DISCONNECTED
01/09 17:16:26.02 [1041056864] Diag :updateMasterConnection for channel 142
01/09 17:16:26.02 [1041056864] WARN :End stream request for callID Intercom::Call but current call is [email protected]:5060
01/09 17:16:26.02 [1041056864] Diag :SendMessage: CPSIP_METHOD_UNREGISTER ********************
01/09 17:16:26.02 [1041056864] Diag :SipUserAgentManager::RegistrationState Setting SIP registration state to 2
01/09 17:16:26.02 [1041056864] Diag :CPAPP SEND msg: connid=0 method=UNREGISTER arg1=(null) arg2=(null)
01/09 17:16:26.02 [1041056864] Diag :CPAPP_SEND: connId=0 dialog_context=888a98
01/09 17:16:26.02 [1041056864] Diag :SEND msg: connId=0 method=UNREGISTER
01/09 17:16:26.06 [857850976] Diag :$$$$$$$$ SipStackCallback CALLED rq_method=0 status_code=401
01/09 17:16:26.06 [857850976] Diag :CPAPP RECEIVE msg: method=RESPONSE
01/09 17:16:26.06 [857850976] Diag : status_code=401
01/09 17:16:26.06 [857850976] Diag :SIP stats: memory 25, dialog 1 tact 2
01/09 17:16:26.11 [857850976] Diag :$$$$$$$$ SipStackCallback CALLED rq_method=0 status_code=200
01/09 17:16:26.12 [857850976] Diag :CPAPP RECEIVE msg: method=RESPONSE
01/09 17:16:26.12 [857850976] Diag : status_code=200
01/09 17:16:26.12 [857850976] Diag :SipUserAgentManager::RegistrationState Setting SIP registration state to 0
01/09 17:16:26.12 [857850976] Diag :SIP stats: memory 9, dialog 0 tact 0
01/09 17:16:28.75 [734669488] Diag :-- Block=0 Size= 1CH Count=10780 Total= 294K
01/09 17:16:28.75 [734669488] Diag :-- Block=1 Size= 2CH Count=35346 Total= 1518K
01/09 17:16:28.75 [734669488] Diag :-- Block=2 Size= 4CH Count= 8130 Total= 603K
01/09 17:16:28.75 [734669488] Diag :-- Block=3 Size= 8CH Count= 1610 Total= 220K
01/09 17:16:28.75 [734669488] Diag :-- Block=4 Size= 11CH Count= 466 Total= 129K
01/09 17:16:28.75 [734669488] Diag :-- Block=5 Size= 21CH Count= 67 Total= 35K
01/09 17:16:28.75 [734669488] Diag :-- Block=6 Size= 81CH Count= 10 Total= 20K
01/09 17:16:28.75 [734669488] Diag :-- Block=7 Size= 410CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=8 Size= 800CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=9 Size= C00CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=10 Size=1000CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=11 Size=1800CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=12 Size=2000CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=13 Size=3000CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=14 Size=4000CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=15 Size=6000CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=16 Size=8000CH Count= 0 Total= 0K
01/09 17:16:28.75 [734669488] Diag :-- Block=17 Size=C000CH Count= 0 Total= 0K
01/09 17:16:28.76 [734669488] Diag :-- Block=18 Size=10000CH Count= 0 Total= 0K

Comments

  • mkleynhansmkleynhans Junior Member Posts: 76
    Just incase anyone else runs into this problem, It ended up being the region and time zone settings on the phone system. The integrators hadn't set this correctly and somehow the SIP re-registration timers were janky.. Very simple but boy did it cause issues for us...
Sign In or Register to comment.