Strange MANAGER_REQUEST hangups
Hi there, The wiki states that the above hangup cause is used when a call is hung up from the API. However, I've recently been getting some calls being hung up (often, oddly, multiple calls simultaneously - this is all on a system without automated calls) with this reason, eg: freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076084900@10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076087470@10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/2076087440@10.10.0.2 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076087440@10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441768351327@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441502563921@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441325460860@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+447870616904@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441325385210@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] Is there any other reason that could produce this Cause code? I am *definitely* not executing any api commands to hang up channels. Thanks Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).
It's the default hangup cause for the 'hupall' command, but looking at the code there are other places it'll also happen... - When unloading a endpoint/codec/application module or stopping a Sofia profile... calls using it are hungup - mod_fifo under some condition.. not familiar enough with that module to say way specifically, but related to a (not) ready flag -Steve On 17 April 2013 16:06, Alex Crow <acrow@integrafin.co.uk> wrote:
Hi there,
The wiki states that the above hangup cause is used when a call is hung up from the API.
However, I've recently been getting some calls being hung up (often, oddly, multiple calls simultaneously - this is all on a system without automated calls) with this reason, eg:
freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076084900@10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076087470@10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/2076087440@10.10.0.2 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076087440@10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST]
freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441768351327@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441502563921@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441325460860@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+447870616904@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441325385210@88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST]
Is there any other reason that could produce this Cause code? I am *definitely* not executing any api commands to hang up channels.
Thanks
Alex
-- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).
_________________________________________________________________________ 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
On 17/04/13 17:48, Steven Ayre wrote:
It's the default hangup cause for the 'hupall' command, but looking at the code there are other places it'll also happen...
- When unloading a endpoint/codec/application module or stopping a Sofia profile... calls using it are hungup - mod_fifo under some condition.. not familiar enough with that module to say way specifically, but related to a (not) ready flag
-Steve
Thanks Steve, Neither of those would have happened, as I've not done/used either. However the point may well be moot as I got mixed up about the versions on my boxes and this one was: FreeSWITCH Version 1.3.17+git~20130319T183203Z~20110f4569 (git 20110f4 2013-03-19 18:32:03Z) Which is an oldish trunk build. As our main (very dumb) sbc, just doing address rewriting/topology hiding running with a <100 line dialplan I can afford to be on stable (which I thought I was) so I will revert to that and see how it goes. In fact, scrub that as well. They all occurred slightly after "EVENT_TRAP: IP change detected", since I seem to have acquired 2 default routes. So, entirely my fault I think. Apologies, Alex (Hoping to get employer to pay for me to come to Chicago this year!).
In fact, scrub that as well. They all occurred slightly after "EVENT_TRAP: IP change detected", since I seem to have acquired 2 default routes.
That sounds the most likely cause. Possibly that's restarting the sofia profiles to pick up the IP address changes, which could trigger it. -Steve On 17 April 2013 18:41, Alex Crow <acrow@integrafin.co.uk> wrote:
On 17/04/13 17:48, Steven Ayre wrote:
It's the default hangup cause for the 'hupall' command, but looking at the code there are other places it'll also happen...
- When unloading a endpoint/codec/application module or stopping a Sofia profile... calls using it are hungup - mod_fifo under some condition.. not familiar enough with that module to say way specifically, but related to a (not) ready flag
-Steve
Thanks Steve,
Neither of those would have happened, as I've not done/used either. However the point may well be moot as I got mixed up about the versions on my boxes and this one was:
FreeSWITCH Version 1.3.17+git~20130319T183203Z~20110f4569 (git 20110f4 2013-03-19 18:32:03Z)
Which is an oldish trunk build. As our main (very dumb) sbc, just doing address rewriting/topology hiding running with a <100 line dialplan I can afford to be on stable (which I thought I was) so I will revert to that and see how it goes.
In fact, scrub that as well. They all occurred slightly after "EVENT_TRAP: IP change detected", since I seem to have acquired 2 default routes.
So, entirely my fault I think.
Apologies,
Alex
(Hoping to get employer to pay for me to come to Chicago this year!).
_________________________________________________________________________ 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
participants (2)
-
Alex Crow
-
Steven Ayre