Thanks Federico, that did the trick!
On Tue, May 15, 2018 at 3:51 AM, Alex Balashov
wrote:
> On Tue, May 15, 2018 at 09:48:11AM +0200, Federico Cabiddu wrote:
>
> > Hi,
> > rfc 3261 (the one and only) states at section16.7
> >
> > "
> > A proxy which receives
On Tue, May 15, 2018 at 09:48:11AM +0200, Federico Cabiddu wrote:
> Hi,
> rfc 3261 (the one and only) states at section16.7
>
> "
> A proxy which receives a 503 (Service Unavailable) response
> SHOULD NOT forward it upstream unless it can determine that any
>
Hi,
rfc 3261 (the one and only) states at section16.7
"
A proxy which receives a 503 (Service Unavailable) response
SHOULD NOT forward it upstream unless it can determine that any
subsequent requests it might proxy will also generate a 503.
In other words,
Hi,
1. Do you have a failure_route for this transaction? If so, can you provide it?
2. Make sure the `failure_reply_mode` modparam for TM is set to 3, which
is default anyway:
https://kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.p.failure_reply_mode
-- Alex
On Mon, May 14, 2018 at
Not sure if it's a default Kamailio behavior or something I'm doing wrong...
When receiving a negative reply for an INVITE (more like in the 5xx range),
proxy doesn't relay the message to the originator but instead issues it's
own "500 Service Unavailable".
That doesn't happen, from observations