[OpenSIPS-Users] 502 Bad Gateway events leads to calls being rejected with 480 Temporarily Unavailable

solarmon solarmon at one-n.co.uk
Mon Jun 8 08:52:29 EST 2020


I'm trying to understand whether this is the correct or expected behaviour.

We have two destinations configured in Dispatcher.

What I am noticing is that when we receive 502 Bad Gateway messages (logged
as ("call failed to established with 502 code") from both endpoints. After
both endpoints have returned 502 Bad Gateway, opensips pass back 503
Service Unavailable back to the originating endpoint of the call. However,
subsequent calls are being immediately rejected with 480 Temporarily
Unavailable (logged as "failed to find an available destination,
rejecting") for a period of time.

It seems that opensips is blacklisting the Dispatcher endpoints because of
receiving the 502 Bad Gateway messages. Is this the correct/expected
behaviour? I would have thought the blacklisting should be based on the SIP
OPTIONS sent to the Dispatcher endpoints.

I do not currently see any issues with SIP OPTIONS to these endpoints so
I'm confused as to why they are seemingly blacklisted.

If this is the correct/expected behaviour, can it be changed to only
blacklist based on the SIP OPTIONs pings?

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200608/850084d4/attachment.html>

More information about the Users mailing list