Hi
I've been trying to experiment with leg_delay_start when bridging to two
mobiles via a gateway, however regardless of settings both legs are bridged
immediately. I noticed a previous post on problems with leg_delay_start
which seemed to go unanswered, just wondered if there is a known issue
Those vars were not even available in 1.0.3. I can't recall if they
were in 1.0.4 or if you will need to use the latest 1.0.5 pre-release.
Mike
On Nov 7, 2009, at 9:26 AM, Steven Brown wrote:
Hi
I've been trying to experiment with leg_delay_start when bridging to
two mobiles via a
Thanks Mike,
I should have checked that, I've just done a make current on my other FS
box and tested on it and can confirm that leg_delay_start works a treat,
exactly as I need.
Steve
___
FreeSWITCH-users mailing list
turn on the debug option in mod_cdr_csv and you will get something similar
to the info app only at the end of the call
On Thu, Apr 16, 2009 at 3:19 AM, Mikael Aleksander Bjerkeland
mik...@bjerkeland.com wrote:
El mié, 15-04-2009 a las 17:43 +0200, Mikael Bjerkeland escribió:
Hi,
I have
Thanks. I just tested and got some more data but it didn't contain any
variable containing MEDIA_TIMEOUT. Perhaps it's not really set anywhere?
variable_hangup_cause and variable_originate_disposition contain
NORMAL_CLEARING and SUCCESS respectively. I need a var which contains
the real reason for
I think I know a bit more about the problem now. The MEDIA_TIMEOUT
hangup cause is probably coming from the B leg of the call and thus not
visible when I do info or debug on mod_cdr_csv.
I then tried the following after bridge to get it:
action application=set data=other_leg_hangup_cause=
