This is in regards to this thread I had started before - http://forum.sipfoundry.org/index.php?t=msg&th=13427&goto=47362&S=173b77 b3f1eb007e6c353c47189b19db#msg_47362
(I did not know how to reply back to the list from that thread since I no longer had that email from the list, and posting a reply in the forum would probably not be looked at.) Anyhow, this problem still persists and has crept back up this weekend. All the phones, local and remote showed up as Expired on the Registration page. Rebooting the phone does not re-register, but restarting the Registrar services cleared it up. Took a snapshot, and looked at the sipxregistrar.log Once the phones started to expire, this is what the log is saying for a particular phone: "2010-07-25T02:00:35.481624Z":790069:OUTGOING:INFO:sipx.synaptyk.com:Sip SubscribeServer-30:B5FCEB90:SipRegistrar:"SipUserAgent::sendTcp TCP SIP User Agent sent message:\n----Remote Host:192.168.2.2---- Port: 5060----\nNOTIFY sip:192.168.2.2:49452;transport=udp;x-sipX-nonat SIP/2.0\r\nFrom: <sip:9...@synaptyk.com;sipx-noroute=VoiceMail;sipx-userforward=false>;ta g=eryIlz\r\nTo: <sip:sipx...@192.168.2.2:49452>;tag=T3YA09\r\nCseq: 373 NOTIFY\r\nRoute: <sip:192.168.2.2:5060;lr>\r\nCall-Id: Q7aPPNVFeU8199\r\nEvent: reg\r\nSubscription-State: terminated;reason=timeout\r\nContent-Type: application/reginfo+xml\r\nContact: sip:9...@192.168.2.2:5075\r\nDate: Sun, 25 Jul 2010 02:00:35 GMT\r\nMax-Forwards: 20\r\nUser-Agent: sipXecs/4.2.0 sipXecs/reg-event (Linux)\r\nAccept-Language: en\r\nVia: SIP/2.0/TCP 192.168.2.2:5075;branch=z9hG4bK-XX-6c08uhrQ195mLSvdUAyVlah5Sg\r\nContent -Length: 850\r\n\r\n<?xml version=\"1.0\"?>\r\n<reginfo xmlns=\"urn:ietf:params:xml:ns:reginfo\" xmlns:gr=\"urn:ietf:params:xml:ns:gruuinfo\" xmlns:in=\"http://www.sipfoundry.org/sipX/schema/xml/reg-instrument-00-0 0\" version=\"372\" state=\"full\">\r\n <registration aor=\"sip:9...@synaptyk.com\" id=\"sip:9...@synaptyk.com\" state=\"init\">\r\n <contact id=\"sip:9...@synaptyk.com@@<sip:9...@192.168.2.249:5060;x-sipX-nonat >\" state=\"terminated\" event=\"expired\" q=\"1\" callid=\"3936323300-aabb-105d-0405a182d30-0-7...@192.168.2.249\" cseq=\"285\">\r\n <uri>sip:9...@192.168.2.249:5060;x-sipX-nonat</uri>\r\n <unknown-param name=\"+sip.instance\"><urn:uuid:39363233-AABB-0000-0000-00405A182D30 ></unknown-param>\r\n <gr:pub-gruu uri=\"sip:~~gr~d44008f185b60...@synaptyk.com;gr\"/>\r\n <in:instrument>00405a182d30</in:instrument>\r\n </contact>\r\n </registration>\r\n</reginfo>\r\n--------------------END---------------- ----" It says subscription state is terminated and the reason is timeout. The question is why? During the normal course of the work week, it doesn't happen but seems to only be during the weekend when no phone calls are being made for an extended period of time. Can someone make heads or tail and help me troubleshoot this? Ly Tran
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
