Re: [OpenSIPS-Users] question about rtpengine_manage() in failure_route

2020-06-08 Thread William Jin
Below is a short config example. route { ... setflag(CallFWD); rtpengine_manage(); #say the first call attempt need rtpengine t_on_failure("handle_failure"); r_relay(); ... } failure_route[handle_failure] { ... if (isflagset(CallFWD)){route(handle_callfwd);} ... } route[handle_callfwd]{ ... xl

[OpenSIPS-Users] question about rtpengine_manage() in failure_route

2020-06-08 Thread William Jin
Hi All May I know how can I rewrite the SDP (rtpengine) in the failure route? The scenario is we use rtpengine_manage() in the first call attempt, if it fails, it uses failure_route, however, we want to change the SDP info. For example, the call's first attempt is to an ipv6 UAC, when failed, w

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

2020-06-08 Thread Ben Newlin
Solarmon, Yes, that code is your issue. While it makes sense to mark the remote destination unreachable on some error responses possibly, or certainly on lack of response, this code is marking the destination unreachable on receipt of any 5xx or 6xx response (or timeout), without regard to whet

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

2020-06-08 Thread Diptesh Patel
Hello Solarmon, I think, The * ds_mark_dst("p");* put your destinations on Probing and after a few seconds you will get the reply for OPTIONS and now your destinations are Active. Are you making a second call immediately? If yes then it is clear. Please remove the ds_mark_dst("p"), OpenSIPS automa

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

2020-06-08 Thread solarmon
Hi Diptesh , Thanks for your reply. Apologies, I'm using the term 'blacklist' to generally mean that the endpoints are not available. Also, the 502 Bad Gateway is response to an INVITE, not SIP OPTIONS, returned by the far end and the ITSP is just passing that back to us, because the call has fa

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

2020-06-08 Thread Diptesh Patel
Hello Solarmon, 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 scrip

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

2020-06-08 Thread solarmon
Hi, 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