Yes.

freeswitch@internal> version
FreeSWITCH Version 1.0.trunk (17097M)

Spencer

On Mar 24, 2010, at 9:34 PM, Brian West wrote:

are you on SVN trunk?

/b

On Mar 24, 2010, at 11:28 PM, Spencer Thomason wrote:

Hello all,
I use Bandtel as one of my trunking providers and Freeswitch will work flawlessly for 24-36 hours and then stop responding to SIP requests.  I have monit setup to send an options ping once a minute and restart the process if it doesn't get a reply.  This has been working ok but the Freeswitch process has to get restarted about once a day on average.  Has anybody else had any issues like this?  They are using fairly standard issue stuff, Freeswitch registers to SER 0.9.6 and they are using Sippy as a B2BUA on their end.  The log shows a call ending, a period of no activity, and Freeswitch attempting to register repeatedly, the process then stops responding to requests and monit restarts Freeswitch.

2010-03-24 17:31:03.897756 [DEBUG] switch_core_state_machine.c:439 (sofia/default/13105106983@208.70.78.37) State DESTROY going to sleep
2010-03-24 17:33:16.353544 [NOTICE] sofia_reg.c:336 Registering bandtel
2010-03-24 17:37:58.452249 [NOTICE] sofia_reg.c:336 Registering bandtel
2010-03-24 17:42:40.588167 [NOTICE] sofia_reg.c:336 Registering bandtel
2010-03-24 17:47:22.529220 [NOTICE] sofia_reg.c:336 Registering bandtel
2010-03-24 17:53:15.899570 [INFO] switch_core.c:1734 Shutting down

Here is a typical register request.
 ------------------------------------------------------------------------
2010-03-24 21:12:59.955693 [NOTICE] sofia_reg.c:336 Registering bandtel
send 772 bytes to udp/[66.237.65.67]:5060 at 04:12:59.956245:
   ------------------------------------------------------------------------
   REGISTER sip:66.237.65.67 SIP/2.0
   Via: SIP/2.0/UDP 208.70.78.36;rport;branch=z9hG4bKZcD7H9aN1D50j
   Max-Forwards: 70
   From: <sip:201009000001@66.237.65.67;transport=udp>;tag=3yZ6ZSZUFj3gQ
   Call-ID: b1eae39a-37ae-11df-9bcf-f1944b4d3175
   CSeq: 128622152 REGISTER
   Expires: 390
   User-Agent: FreeSWITCH
   Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, NOTIFY
   Supported: timer, precondition, path, replaces
   Authorization: Digest username="201009000001", realm="10.1.2.1", nonce="4baabf0e1e68a1fdfbde46913ca850da0cbecc8a", algorithm=MD5, uri="sip:66.237.65.67", response="3974689c5cb3eeb4f09e634716d2239e"
   Content-Length: 0
   
   ------------------------------------------------------------------------
recv 505 bytes from udp/[66.237.65.67]:5060 at 04:12:59.980247:
   ------------------------------------------------------------------------
   SIP/2.0 200 OK
   From: <sip:201009000001@66.237.65.67;transport=UDP>;tag=3yZ6ZSZUFj3gQ
   To: <sip:201009000001@66.237.65.67;transport=UDP>;tag=2e41cc73d384c8f458f34dd410d7744b-b5e6
   Call-ID: b1eae39a-37ae-11df-9bcf-f1944b4d3175
   CSeq: 128622152 REGISTER
   Via: SIP/2.0/UDP 208.70.78.36;rport=5060;branch=z9hG4bKZcD7H9aN1D50j
   PortaBilling: currency:USD
   Server: Sip EXpress router (0.9.6 (i386/freebsd))
   Expires: 385
   Content-Length: 0
   
   ------------------------------------------------------------------------
2010-03-24 21:12:59.979821 [DEBUG] sofia_reg.c:1478 Changing expire time to 385 by request of proxy sip:66.237.65.67

What is the best way to debug this?  It seems strange that everything works for a while and then stops.

Thanks,
Spencer

--
Spencer Thomason
5Nine Solutions LLC
e. sales@5ninesolutions.com
p. +1.888.271.7959
f. +1.310.510.6980


_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org