[Freeswitch-users] Behavior of call_timeout during sequential bridge

[Michael Collins]

Try putting the call_timeout=10 in the dialstring instead:

<application app_name="bridge"
app_data="{call_timeout=10}[leg_timeout=5]sofia/internal/user1 at 192.168.2.2|[leg_timeout=5]sofia/internal/user2 at 192.168.2.2|[leg_timeout=5]sofia/internal/user3 at 192.168.2.2"/>

Alternatively you might try using export instead of set since you need
the call_timeout to be on the other call leg.

-MC

On 11/2/10, mayamatakeshi <mayamatakeshi at gmail.com> wrote:
> Hello,
> I have a dialplan app (mod_xml_curl) that fetches a number of users from my
> DB and composes a brigde command that will try to contact each user in
> sequence.
> Each user should be attempted for at most 5 seconds and the total bridge
> attempt should not surpass 10 seconds. So my app generates something like
> this:
>
> <application app_name="set" app_data="call_timeout=10"/>
> <application app_name="bridge" app_data="[leg_timeout=5]sofia/internal/
> user1 at 192.168.2.2|[leg_timeout=5]sofia/internal/user2 at 192.168.2.2
> |[leg_timeout=5]sofia/internal/user3 at 192.168.2.2"/>
>
> However, in this case, call_timeout is ignored and the whole sequence of
> users will be attempted.
> Is there any way to enforce at timeout for the whole bridge operation when
> bridging sequentially?
>
> br,
> takeshi
>