Stops accepting calls when idle for four minutes
[Just learning Freeswitch, but I really did search this list looking for my answer for awhile] I compiled the latest trunk release from svn two days ago. I have a DID from flowroute.com pointing to it. Added the flowroute IP to acl.conf.domains and added flowroute.xml to conf/sip_profiles/ internal/ with: <include> <gateway name="flowroute"> <param name="username" value="USERNAME"/> <param name="from-domain" value="sip.flowroute.com"/> <param name="password" value="PASSWORD"/> <param name="extension" value="USERNAME"/> <param name="realm" value="sip.flowroute.com"/> <param name="proxy" value="sip.flowroute.com"/> <param name="expire-seconds" value="3600"/> <param name="register" value="true"/> <param name="retry-seconds" value="3600"/> </gateway> </include> Start up freeswitch and it works! Dialing into the flowroute number connects, everything works exactly as expected. But if I don't call in for four minutes, it stops taking accepting the call. Freeswitch has not crashed, it seems up and running; but nothing is even logged when I try to call. It's as if it never reaches freeswitch. Shutdown and restart Freeswitch, and again it works. It will continue to work as long as I call in every minute or so. If I wait four minutes and then call in again, the call never makes it to Freeswitch again. Oddly, I have another test machine running Freeswitch 1.03 release and a nearly identical setup with the flowroute number, and it works fine all the time. Anyone think they can point me in the right direction? -- Greg
Hello Greg, It's a NAT box issue. Nat bindings expire if no activity. Try adding a: <param name="ping" value="30" /> to your gateway params. But to be honest it's flowroute duty to keep a connection alive by sending keepalives. -- Mike Tkachuk
That solved it! Is there any downside to this method of keeping the nat binding alive? -- Greg On May 8, 2009, at 12:49 PM, Mike Tkachuk wrote:
Hello Greg,
It's a NAT box issue. Nat bindings expire if no activity. Try adding a:
<param name="ping" value="30" />
to your gateway params. But to be honest it's flowroute duty to keep a connection alive by sending keepalives.
-- Mike Tkachuk
_______________________________________________ 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
Hello Greg, Should be no problem - only few more bytes of bandwidth used. Friday, May 8, 2009 9:23:49 PM, you wrote: GT> That solved it! Is there any downside to this method of keeping the nat binding alive? GT> -- GT> Greg GT> On May 8, 2009, at 12:49 PM, Mike Tkachuk wrote: GT> Hello Greg, GT> It's a NAT box issue. Nat bindings expire if no activity. GT> Try adding a: GT> <param name="ping" value="30" /> GT> to your gateway params. GT> But to be honest it's flowroute duty to keep a connection alive by GT> sending keepalives. GT> -- GT> Mike Tkachuk -- Mike Tkachuk
participants (2)
-
Greg Thoen
-
Mike Tkachuk