after starting freeswitch I am able to receive incoming calls but if I let freeswitch run in the background it stops picking up incoming calls. The only way I am able to get freeswitch to recognize incoming calls again is by making an outbound call and it then afterwards receives inbound calls. Not sure what if any log information would be beneficial to post here. I am new to freeswitch.
How are you running it in the background? Freeswitch -nc starts it in the background and it should run fine there
From: Adam Falcone <adam.falcone@gmail.com> Reply-To: <freeswitch-users@lists.freeswitch.org> Date: Sun, 10 May 2009 10:20:32 -0700 To: <freeswitch-users@lists.freeswitch.org> Subject: [Freeswitch-users] Running FreeSwitch in the background
after starting freeswitch I am able to receive incoming calls but if I let freeswitch run in the background it stops picking up incoming calls. The only way I am able to get freeswitch to recognize incoming calls again is by making an outbound call and it then afterwards receives inbound calls. Not sure what if any log information would be beneficial to post here. I am new to freeswitch.
_______________________________________________ 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
Yes I am passing -nc when starting freeswitch and I can receive calls without issue initially. If I wait 10-15 then try to place another incoming call freeswitch will not pick it up. I haaven't found where anyone else has reported this issue so I am at a loss. Ken Rice-2 wrote:
How are you running it in the background?
Freeswitch -nc starts it in the background and it should run fine there
From: Adam Falcone <adam.falcone@gmail.com> Reply-To: <freeswitch-users@lists.freeswitch.org> Date: Sun, 10 May 2009 10:20:32 -0700 To: <freeswitch-users@lists.freeswitch.org> Subject: [Freeswitch-users] Running FreeSwitch in the background
after starting freeswitch I am able to receive incoming calls but if I let freeswitch run in the background it stops picking up incoming calls. The only way I am able to get freeswitch to recognize incoming calls again is by making an outbound call and it then afterwards receives inbound calls. Not sure what if any log information would be beneficial to post here. I am new to freeswitch.
_______________________________________________ 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
-- View this message in context: http://www.nabble.com/Running-FreeSwitch-in-the-background-tp23472194p235795... Sent from the Freeswitch-users mailing list archive at Nabble.com.
adamF <adam.falcone@gmail.com> wrote:
Yes I am passing -nc when starting freeswitch and I can receive calls without issue initially. If I wait 10-15 then try to place another incoming call freeswitch will not pick it up. I haaven't found where anyone else has reported this issue so I am at a loss.
Is there a NAT device between your FreeSWITCH system and the SIP endpoints that are making the calls? I'm assuming these are SIP calls; if not, I would suggest that you explain the scenario in greater detail. If there is a NAT device involved, it could well be your problem, and you could try setting a ping parameter in the relevant FreeSWITCH profile to keep the NAT port mapping alive. This might well be a problem that you'll have to solve by reconfiguring the NAT device (a router, for example), if there is one that is responsible for your issues.
I was able to fix this by assigning my public IP to the following in vars.xml <X-PRE-PROCESS cmd="set" data="external_rtp_ip=XX.XX.XX.XX"/> <X-PRE-PROCESS cmd="set" data="external_sip_ip=XX.XX.XX.XX"/> XX's obviously being my public IP and now Freeswitch is receiving calls while running in the background. Thanks for your help Jason White-14 wrote:
adamF <adam.falcone@gmail.com> wrote:
Yes I am passing -nc when starting freeswitch and I can receive calls without issue initially. If I wait 10-15 then try to place another incoming call freeswitch will not pick it up. I haaven't found where anyone else has reported this issue so I am at a loss.
Is there a NAT device between your FreeSWITCH system and the SIP endpoints that are making the calls? I'm assuming these are SIP calls; if not, I would suggest that you explain the scenario in greater detail.
If there is a NAT device involved, it could well be your problem, and you could try setting a ping parameter in the relevant FreeSWITCH profile to keep the NAT port mapping alive.
This might well be a problem that you'll have to solve by reconfiguring the NAT device (a router, for example), if there is one that is responsible for your issues.
_______________________________________________ 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
-- View this message in context: http://www.nabble.com/Running-FreeSwitch-in-the-background-tp23472194p235856... Sent from the Freeswitch-users mailing list archive at Nabble.com.
participants (4)
-
Adam Falcone
-
adamF
-
Jason White
-
Ken Rice