Ugh, callcentric... "Callcentric's SIP config specifically states its Register Expiry should be 1800 secs. In addition, Callcentric uses its own Keep Alive scheme to keep a device connected. I've found that it works well. "
Not my quote, but they evidently provide this information somewhere and other forums refer to that. Somehow they don't like 600 (10 minutes), so try 1800 (30 minutes, and see what the re-registration intervals look like (or ask them what the setting should be). On Sun, Oct 10, 2010 at 2:34 PM, Roman Gelfand <[email protected]> wrote: > I found the following messages identify the registration cycle. It > appears that ITSP is the one that expires the registrations after > roughly a minute. > > "2010-10-10T15:24:08.818000Z":258:OUTGOING:INFO:sipx.comms.com: > Timer-0:00000000:sipXbridge:"Sent > SIP Message :\n----Remote Host:204.11.192.36---- Port: > 5080----\nREGISTER sip:callcentric.com SIP/2.0\r\nCall-ID: > [email protected]\r\ncseq: 23 > REGISTER\r\nFrom: > <sip:[email protected] <sip%[email protected]> > >;tag=3569972568635762579\r\nTo: > <sip:[email protected] <sip%[email protected]>>\r\nVia: > SIP/2.0/UDP > 96.57.168.254:5080 > ;branch=z9hG4bK9c9cff643bf681d6da100a32753124fe323335\r\nMax-Forwards: > 70\r\nUser-Agent: sipXecs/4.2.1 sipXecs/sipxbridge (Linux)\r\nAllow: > INVITE,BYE,ACK,CANCEL,OPTIONS\r\nSupported: timer\r\nRoute: > <sip:204.11.192.36:5080;transport=udp;lr>\r\nContact: > <sip:[email protected]:5080;transport=udp>\r\nExpires: > 600\r\nContent-Length: > 0\r\n\r\n--------------------END--------------------\n" > "2010-10-10T15:24:08.844000Z":260:INCOMING:INFO:sipx.comms.com: > Thread-37:00000000:sipXbridge:"Read > SIP Message:\n----Remote Host:204.11.192.36---- Port: > 5080----\nSIP/2.0 200 Ok\r\nVia: SIP/2.0/UDP > 96.57.168.254:5080 > ;branch=z9hG4bK9c9cff643bf681d6da100a32753124fe323335\r\nFrom: > <sip:[email protected] <sip%[email protected]> > >;tag=3569972568635762579\r\nTo: > <sip:[email protected] <sip%[email protected]> > >\r\nCall-ID: > [email protected]\r\ncseq: 23 > REGISTER\r\nContact: > <sip:[email protected]:5080 > ;transport=udp>;expires=65\r\nContent-Length: > 0\r\n\r\n====================END====================\n" > "2010-10-10T15:25:08.853000Z":269:OUTGOING:INFO:sipx.comms.com: > Timer-0:00000000:sipXbridge:"Sent > SIP Message :\n----Remote Host:204.11.192.36---- Port: > 5080----\nREGISTER sip:callcentric.com SIP/2.0\r\nCall-ID: > [email protected]\r\ncseq: 24 > REGISTER\r\nFrom: > <sip:[email protected] <sip%[email protected]> > >;tag=7841565365425075670\r\nTo: > <sip:[email protected] <sip%[email protected]>>\r\nVia: > SIP/2.0/UDP > 96.57.168.254:5080 > ;branch=z9hG4bKcc56dc985c15a2c9658a8e35713a36b1323335\r\nMax-Forwards: > 70\r\nUser-Agent: sipXecs/4.2.1 sipXecs/sipxbridge (Linux)\r\nAllow: > INVITE,BYE,ACK,CANCEL,OPTIONS\r\nSupported: timer\r\nRoute: > <sip:204.11.192.36:5080;transport=udp;lr>\r\nContact: > <sip:[email protected]:5080;transport=udp>\r\nExpires: > 600\r\nContent-Length: > 0\r\n\r\n--------------------END--------------------\n" > "2010-10-10T15:25:08.882000Z":271:INCOMING:INFO:sipx.comms.com: > Thread-38:00000000:sipXbridge:"Read > SIP Message:\n----Remote Host:204.11.192.36---- Port: > 5080----\nSIP/2.0 200 Ok\r\nVia: SIP/2.0/UDP > 96.57.168.254:5080 > ;branch=z9hG4bKcc56dc985c15a2c9658a8e35713a36b1323335\r\nFrom: > <sip:[email protected] <sip%[email protected]> > >;tag=7841565365425075670\r\nTo: > <sip:[email protected] <sip%[email protected]> > >\r\nCall-ID: > [email protected]\r\ncseq: 24 > REGISTER\r\nContact: > <sip:[email protected]:5080 > ;transport=udp>;expires=65\r\nContent-Length: > 0\r\n\r\n====================END====================\n" > > > On Sun, Oct 10, 2010 at 12:52 PM, M. Ranganathan <[email protected]> wrote: > > Take a look at the Expires header or expires parameter on the contact > > header that is returned from the 200 OK of the REGISTER. > > > > On Sun, Oct 10, 2010 at 12:14 PM, Tony Graziano > > <[email protected]> wrote: > >> The initial part of the log, where it starts up up and registers is the > >> piece that needs to be inspected. > >> ============================ > >> Tony Graziano, Manager > >> Telephone: 434.984.8430 > >> Fax: 434.984.8431 > >> > >> Email: [email protected] > >> > >> LAN/Telephony/Security and Control Systems Helpdesk: > >> Telephone: 434.984.8426 > >> Fax: 434.984.8427 > >> > >> Helpdesk Contract Customers: > >> http://www.myitdepartment.net/gethelp/ > >> > >> ----- Original Message ----- > >> From: [email protected] > >> <[email protected]> > >> To: Discussion list for users of sipXecs software > >> <[email protected]> > >> Sent: Sun Oct 10 11:18:35 2010 > >> Subject: Re: [sipx-users] SIP Trunk Registration > >> > >> Unless I misunderstood you, I deleted sipxbridge log and restarted > >> sipx trunk service and still I am seeing registration every minute. > >> > >> On Sun, Oct 10, 2010 at 10:42 AM, Tony Graziano > >> <[email protected]> wrote: > >>> I think I pointed that out to you on your other post. > >>> > >>> I would get a fresh log or pcap from your firewall for a restart of > >>> sipxbridge. > >>> ============================ > >>> Tony Graziano, Manager > >>> Telephone: 434.984.8430 > >>> Fax: 434.984.8431 > >>> > >>> Email: [email protected] > >>> > >>> LAN/Telephony/Security and Control Systems Helpdesk: > >>> Telephone: 434.984.8426 > >>> Fax: 434.984.8427 > >>> > >>> Helpdesk Contract Customers: > >>> http://www.myitdepartment.net/gethelp/ > >>> > >>> ----- Original Message ----- > >>> From: [email protected] > >>> <[email protected]> > >>> To: [email protected] <[email protected]> > >>> Sent: Sun Oct 10 10:07:52 2010 > >>> Subject: [sipx-users] SIP Trunk Registration > >>> > >>> On the ITSP gateway, I specified registration interval of 600 ( I > >>> assume seconds as it states so on the page). However, the sipx is > >>> attempting to register with ITSP every minute. Why? > >>> > >>> Thanks in advance > >>> _______________________________________________ > >>> sipx-users mailing list > >>> [email protected] > >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> _______________________________________________ > >>> sipx-users mailing list > >>> [email protected] > >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >>> > >> _______________________________________________ > >> sipx-users mailing list > >> [email protected] > >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >> _______________________________________________ > >> sipx-users mailing list > >> [email protected] > >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >> > > > > > > > > -- > > M. Ranganathan > > _______________________________________________ > > sipx-users mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
