I changed the script to set hangup_after_bridge to false, but still the same
thing happens, I get this on the console:
2009-08-07 12:27:44.229091 [NOTICE] sofia.c:322 Hangup
sofia/external/00569xxx [CS_SOFT_EXECUTE] [NORMAL_CLEARING]
2009-08-07 12:27:44.229091 [DEBUG] switch_channel.c:1683
What does
bridge_hangup_cause
give you?
On Fri, Aug 7, 2009 at 12:43 PM, Nicolas Brenner nico...@medularis.com wrote:
I changed the script to set hangup_after_bridge to false, but still the same
thing happens, I get this on the console:
2009-08-07 12:27:44.229091 [NOTICE] sofia.c:322
That variable is not available, it is not included with the
CHANNEL_HANGUP_COMPLETE event info. However I discovered that when the
bridge does not work, there are two CHANNEL_HANGUP_COMPLETE events, one for
each leg, nevertheless for some reason the daemon I have watching the events
misses the
I'm bridging 2 calls in a javascript file, I originate the first call and
then execute a bridge with an origination string for the second call. If I
hangup the first call while trying to make the second call, I get this on
the console:
2009-08-05 16:44:05.69122 [NOTICE]
Hi Nicolas,
do you have a copy of the .js code you can paste. I would guess tho, that
ORIGINATOR_CANCLE might be related to not setting hangup_after_bridge to
false. Just a guess tho.
Hangup causes can be found here:
http://wiki.freeswitch.org/wiki/Hangup_causes
Hi Matt,
Actually I'm explicitly setting hangup_after_bridge to true, think setting
it to false would help? I'm going to try that.
Here's the JS code:
(Note: session.getVariable() doesn't work, FS complains saying it is not a
function, also tried self.session.getVariable() - that's what the wiki
