[OpenSIPS-Users] 502 Bad Gateway events leads to calls being rejected with 480 Temporarily Unavailable
diptesh.patel at ecosmob.com
Mon Jun 8 09:44:00 EST 2020
Need some clarification on term blacklisting, Are you using the blacklist
for Probing Mode of destination? or Are you using the *'ds_define_blacklist
(str)' *parameter. If you are not using the blacklist parameter then below
information help you. It is great if you share your script snippet and
output of *'opensipsctl dispatcher dump'* which shows you the current
status of your destinations.
If you are getting success(200 OK) response on OPTIONS then it is not
possible that you got a negative response from a destination and it will
not be blacklisted(probing mode) in dispatcher until you blacklist(probing
mode) from the script using 'ds_mark_dst()' exported function. I doubt that
you are also getting '502 Bad Gateway' on OPTIONS which is sending to the
destination to check the availability. If It is right and you want to add
the 502 response as a good response for OPTIONS. you can add the 502
Thanks & Regards
Ecosmob Technologies Ltd,
On Mon, Jun 8, 2020 at 2:24 PM solarmon <solarmon at one-n.co.uk> wrote:
> 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.
> Users mailing list
> Users at lists.opensips.org
In addition to generic Disclaimer which you have agreed on our
website, any views or opinions presented in this email are solely those of
the originator and do not necessarily represent those of the Company or its
sister concerns. Any liability (in negligence, contract or otherwise)
arising from any third party taking any action, or refraining from taking
any action on the basis of any of the information contained in this email
is hereby excluded.
This communication (including any
attachment/s) is intended only for the use of the addressee(s) and contains
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading,
dissemination, distribution, or copying of this communication is
prohibited. Please inform originator if you have received it in error.
*Caution for viruses, malware etc.*
This communication, including any
attachments, may not be free of viruses, trojans, similar or new
contaminants/malware, interceptions or interference, and may not be
compatible with your systems. You shall carry out virus/malware scanning on
your own before opening any attachment to this e-mail. The sender of this
e-mail and Company including its sister concerns shall not be liable for
any damage that may incur to you as a result of viruses, incompleteness of
this message, a delay in receipt of this message or any other computer
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users