[Freeswitch-users] Parallel Outbound Dialing Failure Causes

[Colin Morelli]

Any thoughts here?

I think I can probably solve this with an additional forked dial to a
loopback leg that sleeps for the call_timeout and then completes, but I
want to see if anyone else has a suggestion because I'm not a fan of that
one.

Best,
Colin

On Thu, Jul 7, 2016 at 1:18 PM Colin Morelli <colin.morelli at gmail.com>
wrote:

> Hey all,
>
> I'm trying to initiate a parallel outbound bridge to a SIP user and pickup
> group combination. I have devices on mobile networks that don't register
> (my experience has been that doing SIP registrations on mobile devices
> makes little sense - better off to just send a push notification and allow
> them to call into FS with a pickup group)
>
> Anyway, it seems like the call is immediately terminated when FS receives
> a final response from my SIP endpoint, whether the call_timeout value has
> been reached or not. I've tried setting
> fail_on_single_reject=CALL_REJECTED, FS immediately closes the pickup group
> channel and terminates the bridge, even when the response from the SIP
> endpoint is UNALLOCATED_NUMBER (404).
>
> Am I missing something else here - is this a bug or is this how pickup
> groups are supposed to work? If the latter, is there something else I can
> do to ensure the channel bridge attempt stays active and ringing until the
> timeout is reached, unless one of the legs responds with an explicit
> decline?
>
> Best,
> Colin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160708/204a0e21/attachment.html