One of my users (the one who uses the phone the most) has reported several times since switching to VoIP that sometimes calls are getting disconnected unexpectedly. Since this is intermittent, the only way I can debug it is looking through the log. Here are the entries when today's call got disconnected (I changed his number to 4085551212 in this log): 2013-03-21 09:53:47.420473 [DEBUG] switch_core_session.c:975 Send signal sofia/phone/sip:4085551212@192.168.4.244 [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_channel.c:3011 (sofia/phone/ sip:4085551212@192.168.4.244) Callstate Change ACTIVE -> HANGUP 2013-03-21 09:53:47.440473 [NOTICE] sofia.c:711 Hangup sofia/phone/ sip:4085551212@192.168.4.244 [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING] 2013-03-21 09:53:47.440473 [DEBUG] switch_channel.c:3034 Send signal sofia/phone/sip:4085551212@192.168.4.244 [KILL] 2013-03-21 09:53:47.440473 [DEBUG] switch_core_session.c:1310 Send signal sofia/phone/sip:4085551212@192.168.4.244 [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_ivr_bridge.c:597 BRIDGE THREAD DONE [sofia/phone/sip:4085551212@192.168.4.244] 2013-03-21 09:53:47.440473 [DEBUG] switch_ivr_bridge.c:622 Send signal sofia/external/+19259639530@flowroute.com [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:480 (sofia/phone/sip:4085551212@192.168.4.244) State EXCHANGE_MEDIA going to sleep 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:415 (sofia/phone/sip:4085551212@192.168.4.244) Running State Change CS_HANGUP 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:676 (sofia/phone/sip:4085551212@192.168.4.244) State HANGUP 2013-03-21 09:53:47.440473 [DEBUG] mod_sofia.c:503 Channel sofia/phone/ sip:4085551212@192.168.4.244 hanging up, cause: NORMAL_CLEARING I'm assuming this mean that the internal user (who's phone is 192.168.4.244) hung up, but he tells me he didn't. He was just talking and then there was no answer. I'm not sure where to look next. Any idea? -- Steve
The usual reason is re-INVITES being ignored by the other end. Freeswitch periodically sends a reinvite to check the channel is still live, if it does not recieve a response it hangs up the call. This can be cause either bad NAT or bad proxy configuration. On 21 March 2013 22:38, Steven Schoch <schoch+freeswitch.org@xwin32.com>wrote:
One of my users (the one who uses the phone the most) has reported several times since switching to VoIP that sometimes calls are getting disconnected unexpectedly. Since this is intermittent, the only way I can debug it is looking through the log. Here are the entries when today's call got disconnected (I changed his number to 4085551212 in this log):
2013-03-21 09:53:47.420473 [DEBUG] switch_core_session.c:975 Send signal sofia/phone/sip:4085551212@192.168.4.244 [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_channel.c:3011 (sofia/phone/ sip:4085551212@192.168.4.244) Callstate Change ACTIVE -> HANGUP 2013-03-21 09:53:47.440473 [NOTICE] sofia.c:711 Hangup sofia/phone/ sip:4085551212@192.168.4.244 [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING] 2013-03-21 09:53:47.440473 [DEBUG] switch_channel.c:3034 Send signal sofia/phone/sip:4085551212@192.168.4.244 [KILL] 2013-03-21 09:53:47.440473 [DEBUG] switch_core_session.c:1310 Send signal sofia/phone/sip:4085551212@192.168.4.244 [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_ivr_bridge.c:597 BRIDGE THREAD DONE [sofia/phone/sip:4085551212@192.168.4.244] 2013-03-21 09:53:47.440473 [DEBUG] switch_ivr_bridge.c:622 Send signal sofia/external/+19259639530@flowroute.com [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:480 (sofia/phone/sip:4085551212@192.168.4.244) State EXCHANGE_MEDIA going to sleep 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:415 (sofia/phone/sip:4085551212@192.168.4.244) Running State Change CS_HANGUP 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:676 (sofia/phone/sip:4085551212@192.168.4.244) State HANGUP 2013-03-21 09:53:47.440473 [DEBUG] mod_sofia.c:503 Channel sofia/phone/ sip:4085551212@192.168.4.244 hanging up, cause: NORMAL_CLEARING
I'm assuming this mean that the internal user (who's phone is 192.168.4.244) hung up, but he tells me he didn't. He was just talking and then there was no answer. I'm not sure where to look next. Any idea?
-- Steve
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director *T <info@cassidywebservices.co.uk> *03300 100 960 *F<info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk
On Thu, Mar 21, 2013 at 4:34 PM, Andrew Cassidy < andrew@cassidywebservices.co.uk> wrote:
The usual reason is re-INVITES being ignored by the other end. Freeswitch periodically sends a reinvite to check the channel is still live, if it does not recieve a response it hangs up the call. This can be cause either bad NAT or bad proxy configuration.
Does Freeswitch log when this happens? I don't see anything in these log entries about a reinvite failing to respond. There is no NAT or proxy involved. This Freeswitch box connects directly to the Internet, via a Comcast static IP address. Could it have something to do with the SLA I have on this phone? -- Steve On 21 March 2013 22:38, Steven Schoch <schoch+freeswitch.org@xwin32.com>wrote:
One of my users (the one who uses the phone the most) has reported several times since switching to VoIP that sometimes calls are getting disconnected unexpectedly. Since this is intermittent, the only way I can debug it is looking through the log. Here are the entries when today's call got disconnected (I changed his number to 4085551212 in this log):
2013-03-21 09:53:47.420473 [DEBUG] switch_core_session.c:975 Send signal sofia/phone/sip:4085551212@192.168.4.244 [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_channel.c:3011 (sofia/phone/ sip:4085551212@192.168.4.244) Callstate Change ACTIVE -> HANGUP 2013-03-21 09:53:47.440473 [NOTICE] sofia.c:711 Hangup sofia/phone/ sip:4085551212@192.168.4.244 [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING] 2013-03-21 09:53:47.440473 [DEBUG] switch_channel.c:3034 Send signal sofia/phone/sip:4085551212@192.168.4.244 [KILL] 2013-03-21 09:53:47.440473 [DEBUG] switch_core_session.c:1310 Send signal sofia/phone/sip:4085551212@192.168.4.244 [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_ivr_bridge.c:597 BRIDGE THREAD DONE [sofia/phone/sip:4085551212@192.168.4.244] 2013-03-21 09:53:47.440473 [DEBUG] switch_ivr_bridge.c:622 Send signal sofia/external/+19259639530@flowroute.com [BREAK] 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:480 (sofia/phone/sip:4085551212@192.168.4.244) State EXCHANGE_MEDIA going to sleep 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:415 (sofia/phone/sip:4085551212@192.168.4.244) Running State Change CS_HANGUP 2013-03-21 09:53:47.440473 [DEBUG] switch_core_state_machine.c:676 (sofia/phone/sip:4085551212@192.168.4.244) State HANGUP 2013-03-21 09:53:47.440473 [DEBUG] mod_sofia.c:503 Channel sofia/phone/ sip:4085551212@192.168.4.244 hanging up, cause: NORMAL_CLEARING
I'm assuming this mean that the internal user (who's phone is 192.168.4.244) hung up, but he tells me he didn't. He was just talking and then there was no answer. I'm not sure where to look next. Any idea?
participants (2)
-
Andrew Cassidy
-
Steven Schoch