[Freeswitch-users] bridge and originate - difference between opening a channel and ring ready

[Steven Ayre]

> But when at the same time user/C gets called from someone else while
leg_delay_start is not over yet, can user/C still answer the second call?

Maybe. They can get sent calls concurrently. How they handle that would
depend on their client.

On Mon, 29 Oct 2018 at 14:37, Paul Muaddib <paul.muaddib83 at gmail.com> wrote:

> Hi,
>
> I am trying to understand the difference between opening a channel and
> ring ready
>
> Following example:
> <action application="bridge"
> data="<originate_timeout=90,ignore_early_media=true>user/A, user/B,
> [leg_delay_start]user/C"/>
>
> When I call multiple endpoints with bridge in parallel and delay one of
> them with leg_delay_start, then I can see in the log files that freeswitch
> opens up three channels and delays the ring ready for C. But when at the
> same time user/C gets called from someone else while leg_delay_start is not
> over yet, can user/C still answer the second call? And which call reaches
> the user first if the user lets pass by leg_delay_start from the first call?
>
> When I do the whole thing with enterprise originate, it looks much more
> efficient since freeswitch is creating the channels only after the time for
> originate_delay_start has passed by. What should be used when?
>
> Best regards,
> Paul
>
> _________________________________________________________________________
> Professional FreeSWITCH Services
> sales at freeswitch.com
> https://freeswitch.com
>
> Official FreeSWITCH Sites
> https://freeswitch.com/oss
> https://freeswitch.org/confluence
> https://cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> https://freeswitch.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20181030/388c7ae2/attachment-0001.html>