[OpenSIPS-Users] Delayed Bye?

[Jeff Pyle]

Eek.  This sounds like a recipe for future problems with this carrier.  If
you really want to try, you could do a sleep() or usleep() on BYE requests
in the section of your script that processes sequential requests....the
has_totag() and loose_route() part (assuming no topology_hiding).  That's
going to occupy the process, though, so you might want to look at doing it
async-style if scale is a concern.  If you want to do it only on BYE
requests to the carrier rather than on BYE requests in both directions,
then you'll have to detect the direction, which is possible but gets more
involved.

I know I'm going to regret asking this, but why does your carrier want you
to delay your BYE messages?


- Jeff


On Sun, Jun 27, 2021 at 5:07 PM Alexander Perkins <
alexanderhenryperkins at gmail.com> wrote:

> Hi All.  Our carrier has asked us if we can do a 'delayed bye'.  I have no
> idea what this means.  The way it was explained to me is -  the b-let is
> held for x numbers of seconds after the a leg hangs up.
>
> Does that make sense?  If so, can someone point me in the right direction?
>
> Thank you,
> Alex
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210628/bf25f61a/attachment.html>