Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Well, I don't have your script, cannot help further. If you are proxying, you should proxy every message. Maybe you are mixing stateful and stateless forwarding and are not handling all scenarios? It could be an Opensips problem, but again, don't know what you are doing internally. On Wed, May 4, 2022 at 2:19 PM Yannick LE COENT wrote: > Hi Daniel, > > I do not think the ACK is sent by my script. It is sent by the TM module > since it is a negative response. > Am I wrong ? > > Thanks, > Yannick > > Le 04/05/2022 à 18:48, Daniel Zanutti a écrit : > > Hi Yannick > > I think you should not reply with ACK to the 407 from destination. Just > forward 407 to origin and wait for ACK. As soon you receive ACK from > origin, you forward to destination. > > It's more like a stateless but I believe it's the only way. > > Regards > > On Tue, May 3, 2022 at 12:16 PM Yannick LE COENT < > yannick.leco...@nexcom.fr> wrote: > >> Hello Daniel, >> >> This is not what I looking for. >> My OpenSIPS instance is working as a relay between the softphone and >> another proxy (proxy#2 in the call). >> So it does not handle authentication. >> >> Alice OpenSIPS Proxy#2 >>| INVITE || >>|--->| INVITE | >>| 100 Tring |--->| >>|<---|407 | >>||<---| >>|| ACK| >>||--->| >>|407 || >>| X<-|| >>| (no retrans.) || >> >> When the 407 is lost between OpenSIPS and Alice, it is not retransmitted >> by OpenSIPS. >> >> I would like to force retransmission. >> >> Thanks, >> Yannick >> >> Le 03/05/2022 à 15:16, Daniel Zanutti a écrit : >> >> Generate in Stateful -> www_challenge or proxy_challenge? >> https://opensips.org/html/docs/modules/3.2.x/auth.html >> >> Is this what you are looking for? >> >> >> On Tue, May 3, 2022 at 3:50 AM Yannick LE COENT < >> yannick.leco...@nexcom.fr> wrote: >> >>> Hello all, >>> >>> Could you tell if there is a way to enable 407 in stateful mode ? >>> >>> Thanks, >>> Yannick >>> >>> Le 30/04/2022 à 18:14, Yannick LE COENT a écrit : >>> >>> Hello Ben, >>> >>> Thanks for your answer. >>> >>> This problem occurs when OpenSIPS is not in charge of authenticating the >>> INVITE request, but this is done downstream. >>> I've sent this question to know if somebody has already solved this kind >>> of problem. >>> >>> Best regards, >>> Yannick >>> >>> Le 30/04/2022 à 16:15, Ben Newlin a écrit : >>> >>> I see. Apologies, I misunderstood the problem scenario. >>> >>> >>> >>> Ben Newlin >>> >>> >>> >>> *From: *Users >>> on behalf of Yannick LE COENT >>> >>> *Date: *Saturday, April 30, 2022 at 5:46 AM >>> *To: *OpenSIPS users mailling list >>> >>> *Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission >>> >>> *EXTERNAL EMAIL - Please use caution with links and attachments * >>> >>> >>> -- >>> >>> Hello Ben, >>> >>> The 407 is sent upstream, but when it is lost, it is not retransmitted >>> by OpenSIPS. >>> I do not have this problem with other negative status codes (e.g. 486). >>> >>> This is clearly explained in >>> https://opensips.org/pub/opensips/1.8.6/src/ChangeLog >>> >>> 2012-03-21 18:36:58 Bogdan-Andrei Iancu, >>> * [8811] : >>> >>> TM will no longer do retransmission for the 407/401 replies (if no >>> ACK is received) for both local or proxied replies. >>> >>> According to RFC 3261, retransmitting 407s/401s is probably a bad >>> idea: >>> >>> 26.3.2.4 DoS Protection >>> >>> At the moment, my only solution is to use forward() instead of t_relay() >>> in order to use the stateless mode. >>> >>> Yannick >>> >>> >>> Yannick, >>> >>> >>> >>> The default behavior of OpenSIPS is to relay any received responses back >>> upstream
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Hi Daniel,
I do not think the ACK is sent by my script. It is sent by the TM module
since it is a negative response.
Am I wrong ?
Thanks,
Yannick
Le 04/05/2022 à 18:48, Daniel Zanutti a écrit :
Hi Yannick
I think you should not reply with ACK to the 407 from destination.
Just forward 407 to origin and wait for ACK. As soon you receive ACK
from origin, you forward to destination.
It's more like a stateless but I believe it's the only way.
Regards
On Tue, May 3, 2022 at 12:16 PM Yannick LE COENT
wrote:
Hello Daniel,
This is not what I looking for.
My OpenSIPS instance is working as a relay between the softphone
and another proxy (proxy#2 in the call).
So it does not handle authentication.
Alice OpenSIPS Proxy#2
| INVITE | |
|--->| INVITE |
| 100 Tring |--->|
|<---| 407 |
| |<---|
| | ACK |
| |--->|
| 407 | |
| X<-| |
| (no retrans.) | |
When the 407 is lost between OpenSIPS and Alice, it is not
retransmitted by OpenSIPS.
I would like to force retransmission.
Thanks,
Yannick
Le 03/05/2022 à 15:16, Daniel Zanutti a écrit :
Generate in Stateful -> www_challenge or proxy_challenge?
https://opensips.org/html/docs/modules/3.2.x/auth.html
Is this what you are looking for?
On Tue, May 3, 2022 at 3:50 AM Yannick LE COENT
wrote:
Hello all,
Could you tell if there is a way to enable 407 in stateful mode ?
Thanks,
Yannick
Le 30/04/2022 à 18:14, Yannick LE COENT a écrit :
Hello Ben,
Thanks for your answer.
This problem occurs when OpenSIPS is not in charge of
authenticating the INVITE request, but this is done downstream.
I've sent this question to know if somebody has already
solved this kind of problem.
Best regards,
Yannick
Le 30/04/2022 à 16:15, Ben Newlin a écrit :
I see. Apologies, I misunderstood the problem scenario.
Ben Newlin
*From: *Users
<mailto:users-boun...@lists.opensips.org> on behalf of
Yannick LE COENT
<mailto:yannick.leco...@nexcom.fr>
*Date: *Saturday, April 30, 2022 at 5:46 AM
*To: *OpenSIPS users mailling list
<mailto:users@lists.opensips.org>
*Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407
retransmission
*EXTERNAL EMAIL - Please use caution with links and
attachments *
Hello Ben,
The 407 is sent upstream, but when it is lost, it is not
retransmitted by OpenSIPS.
I do not have this problem with other negative status codes
(e.g. 486).
This is clearly explained in
https://opensips.org/pub/opensips/1.8.6/src/ChangeLog
2012-03-21 18:36:58 Bogdan-Andrei Iancu,
* [8811] :
TM will no longer do retransmission for the 407/401
replies (if no ACK is received) for both local or
proxied replies.
According to RFC 3261, retransmitting 407s/401s is
probably a bad idea:
26.3.2.4 DoS Protection
At the moment, my only solution is to use forward() instead
of t_relay() in order to use the stateless mode.
Yannick
Yannick,
The default behavior of OpenSIPS is to relay any received responses
back upstream. If it is not doing that it would have to be because you are
stopping it in the script. Take a look at the documentation for failure_route
[1] which explains this. Check your own failure_route in your script; you must
be doing something there that is telling OpenSIPS not to relay the 401/407 back
upstream.
[1]https://www.opensips.org/Documentation/Script-Routes-2-4#toc3
Ben Newlin
From: Users
<mailto:users-boun...@lists.opensips.org> on behalf of Yannick LE
COENT <mailto:yannick.leco...@nexcom.fr>
Date: Friday, April 29, 2022 at 6:44 PM
To:users@lists.opensips.org
<mailto:users@lists.opensips.org>
Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
EXTERNAL EMAIL - Please use caution with links and attachments
Hello,
I'm using OpenSIPS as a proxy in front of another proxy. The 2nd
proxy
is in charge of authenticating the request.
This is the callflow:
Alice
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Hi Yannick I think you should not reply with ACK to the 407 from destination. Just forward 407 to origin and wait for ACK. As soon you receive ACK from origin, you forward to destination. It's more like a stateless but I believe it's the only way. Regards On Tue, May 3, 2022 at 12:16 PM Yannick LE COENT wrote: > Hello Daniel, > > This is not what I looking for. > My OpenSIPS instance is working as a relay between the softphone and > another proxy (proxy#2 in the call). > So it does not handle authentication. > > Alice OpenSIPS Proxy#2 >| INVITE || >|--->| INVITE | >| 100 Tring |--->| >|<---|407 | >||<---| >|| ACK| >||--->| >|407 || >| X<-|| >| (no retrans.) || > > When the 407 is lost between OpenSIPS and Alice, it is not retransmitted > by OpenSIPS. > > I would like to force retransmission. > > Thanks, > Yannick > > Le 03/05/2022 à 15:16, Daniel Zanutti a écrit : > > Generate in Stateful -> www_challenge or proxy_challenge? > https://opensips.org/html/docs/modules/3.2.x/auth.html > > Is this what you are looking for? > > > On Tue, May 3, 2022 at 3:50 AM Yannick LE COENT > wrote: > >> Hello all, >> >> Could you tell if there is a way to enable 407 in stateful mode ? >> >> Thanks, >> Yannick >> >> Le 30/04/2022 à 18:14, Yannick LE COENT a écrit : >> >> Hello Ben, >> >> Thanks for your answer. >> >> This problem occurs when OpenSIPS is not in charge of authenticating the >> INVITE request, but this is done downstream. >> I've sent this question to know if somebody has already solved this kind >> of problem. >> >> Best regards, >> Yannick >> >> Le 30/04/2022 à 16:15, Ben Newlin a écrit : >> >> I see. Apologies, I misunderstood the problem scenario. >> >> >> >> Ben Newlin >> >> >> >> *From: *Users >> on behalf of Yannick LE COENT >> >> *Date: *Saturday, April 30, 2022 at 5:46 AM >> *To: *OpenSIPS users mailling list >> >> *Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission >> >> *EXTERNAL EMAIL - Please use caution with links and attachments * >> >> >> -- >> >> Hello Ben, >> >> The 407 is sent upstream, but when it is lost, it is not retransmitted by >> OpenSIPS. >> I do not have this problem with other negative status codes (e.g. 486). >> >> This is clearly explained in >> https://opensips.org/pub/opensips/1.8.6/src/ChangeLog >> >> 2012-03-21 18:36:58 Bogdan-Andrei Iancu, >> * [8811] : >> >> TM will no longer do retransmission for the 407/401 replies (if no >> ACK is received) for both local or proxied replies. >> >> According to RFC 3261, retransmitting 407s/401s is probably a bad >> idea: >> >> 26.3.2.4 DoS Protection >> >> At the moment, my only solution is to use forward() instead of t_relay() >> in order to use the stateless mode. >> >> Yannick >> >> >> Yannick, >> >> >> >> The default behavior of OpenSIPS is to relay any received responses back >> upstream. If it is not doing that it would have to be because you are >> stopping it in the script. Take a look at the documentation for >> failure_route [1] which explains this. Check your own failure_route in your >> script; you must be doing something there that is telling OpenSIPS not to >> relay the 401/407 back upstream. >> >> >> >> [1] https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 >> >> >> >> Ben Newlin >> >> >> >> From: Users >> on behalf of Yannick LE COENT >> >> >> Date: Friday, April 29, 2022 at 6:44 PM >> >> To: users@lists.opensips.org >> >> >> Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission >> >> EXTERNAL EMAIL - Please use caution with links and attachments >> >> >> >> Hello, >> >> >> >> I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy >> >> is in charge of authenticating the request. >> >> >> >> This is the callflow: >> >> >> >> Alice OpenSIPS Proxy#2
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Hello Daniel, This is not what I looking for. My OpenSIPS instance is working as a relay between the softphone and another proxy (proxy#2 in the call). So it does not handle authentication. Alice OpenSIPS Proxy#2 | INVITE | | |--->| INVITE | | 100 Tring |--->| |<---| 407 | | |<---| | | ACK | | |--->| | 407 | | | X<-| | | (no retrans.) | | When the 407 is lost between OpenSIPS and Alice, it is not retransmitted by OpenSIPS. I would like to force retransmission. Thanks, Yannick Le 03/05/2022 à 15:16, Daniel Zanutti a écrit : Generate in Stateful -> www_challenge or proxy_challenge? https://opensips.org/html/docs/modules/3.2.x/auth.html Is this what you are looking for? On Tue, May 3, 2022 at 3:50 AM Yannick LE COENT wrote: Hello all, Could you tell if there is a way to enable 407 in stateful mode ? Thanks, Yannick Le 30/04/2022 à 18:14, Yannick LE COENT a écrit : Hello Ben, Thanks for your answer. This problem occurs when OpenSIPS is not in charge of authenticating the INVITE request, but this is done downstream. I've sent this question to know if somebody has already solved this kind of problem. Best regards, Yannick Le 30/04/2022 à 16:15, Ben Newlin a écrit : I see. Apologies, I misunderstood the problem scenario. Ben Newlin *From: *Users <mailto:users-boun...@lists.opensips.org> on behalf of Yannick LE COENT <mailto:yannick.leco...@nexcom.fr> *Date: *Saturday, April 30, 2022 at 5:46 AM *To: *OpenSIPS users mailling list <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission *EXTERNAL EMAIL - Please use caution with links and attachments * Hello Ben, The 407 is sent upstream, but when it is lost, it is not retransmitted by OpenSIPS. I do not have this problem with other negative status codes (e.g. 486). This is clearly explained in https://opensips.org/pub/opensips/1.8.6/src/ChangeLog 2012-03-21 18:36:58 Bogdan-Andrei Iancu, * [8811] : TM will no longer do retransmission for the 407/401 replies (if no ACK is received) for both local or proxied replies. According to RFC 3261, retransmitting 407s/401s is probably a bad idea: 26.3.2.4 DoS Protection At the moment, my only solution is to use forward() instead of t_relay() in order to use the stateless mode. Yannick Yannick, The default behavior of OpenSIPS is to relay any received responses back upstream. If it is not doing that it would have to be because you are stopping it in the script. Take a look at the documentation for failure_route [1] which explains this. Check your own failure_route in your script; you must be doing something there that is telling OpenSIPS not to relay the 401/407 back upstream. [1]https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 Ben Newlin From: Users <mailto:users-boun...@lists.opensips.org> on behalf of Yannick LE COENT <mailto:yannick.leco...@nexcom.fr> Date: Friday, April 29, 2022 at 6:44 PM To:users@lists.opensips.org <mailto:users@lists.opensips.org> Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello, I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy is in charge of authenticating the request. This is the callflow: Alice OpenSIPS Proxy#2 | INVITE | | |--->| INVITE | | 100 Tring |--->| |<---| 407 | | |<---| | | ACK | | |--->| | 407 | | | X<-| | | | | Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. What can I do ? If I set auto_100trying=1, that works, but this increases the number of INVITE retransmissions since 180Ringing are not received instantly.
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Generate in Stateful -> www_challenge or proxy_challenge? https://opensips.org/html/docs/modules/3.2.x/auth.html Is this what you are looking for? On Tue, May 3, 2022 at 3:50 AM Yannick LE COENT wrote: > Hello all, > > Could you tell if there is a way to enable 407 in stateful mode ? > > Thanks, > Yannick > > Le 30/04/2022 à 18:14, Yannick LE COENT a écrit : > > Hello Ben, > > Thanks for your answer. > > This problem occurs when OpenSIPS is not in charge of authenticating the > INVITE request, but this is done downstream. > I've sent this question to know if somebody has already solved this kind > of problem. > > Best regards, > Yannick > > Le 30/04/2022 à 16:15, Ben Newlin a écrit : > > I see. Apologies, I misunderstood the problem scenario. > > > > Ben Newlin > > > > *From: *Users > on behalf of Yannick LE COENT > > *Date: *Saturday, April 30, 2022 at 5:46 AM > *To: *OpenSIPS users mailling list > > *Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission > > *EXTERNAL EMAIL - Please use caution with links and attachments * > > > -- > > Hello Ben, > > The 407 is sent upstream, but when it is lost, it is not retransmitted by > OpenSIPS. > I do not have this problem with other negative status codes (e.g. 486). > > This is clearly explained in > https://opensips.org/pub/opensips/1.8.6/src/ChangeLog > > 2012-03-21 18:36:58 Bogdan-Andrei Iancu, > * [8811] : > > TM will no longer do retransmission for the 407/401 replies (if no ACK > is received) for both local or proxied replies. > > According to RFC 3261, retransmitting 407s/401s is probably a bad idea: > > 26.3.2.4 DoS Protection > > At the moment, my only solution is to use forward() instead of t_relay() > in order to use the stateless mode. > > Yannick > > > Yannick, > > > > The default behavior of OpenSIPS is to relay any received responses back > upstream. If it is not doing that it would have to be because you are > stopping it in the script. Take a look at the documentation for failure_route > [1] which explains this. Check your own failure_route in your script; you > must be doing something there that is telling OpenSIPS not to relay the > 401/407 back upstream. > > > > [1] https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 > > > > Ben Newlin > > > > From: Users > on behalf of Yannick LE COENT > > > Date: Friday, April 29, 2022 at 6:44 PM > > To: users@lists.opensips.org > > > Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission > > EXTERNAL EMAIL - Please use caution with links and attachments > > > > Hello, > > > > I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy > > is in charge of authenticating the request. > > > > This is the callflow: > > > > Alice OpenSIPS Proxy#2 > >| INVITE || > >|--->| INVITE | > >| 100 Tring |--->| > >|<---|407 | > >||<---| > >|| ACK| > >||--->| > >|407 || > >| X<-|| > >||| > > > > Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. > > > > What can I do ? > > If I set auto_100trying=1, that works, but this increases the number of > > INVITE retransmissions since 180Ringing are not received instantly. > > > > Do you have any suggestion ? > > > > Thanks, > > Yannick > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Hello all, Could you tell if there is a way to enable 407 in stateful mode ? Thanks, Yannick Le 30/04/2022 à 18:14, Yannick LE COENT a écrit : Hello Ben, Thanks for your answer. This problem occurs when OpenSIPS is not in charge of authenticating the INVITE request, but this is done downstream. I've sent this question to know if somebody has already solved this kind of problem. Best regards, Yannick Le 30/04/2022 à 16:15, Ben Newlin a écrit : I see. Apologies, I misunderstood the problem scenario. Ben Newlin *From: *Users on behalf of Yannick LE COENT *Date: *Saturday, April 30, 2022 at 5:46 AM *To: *OpenSIPS users mailling list *Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission *EXTERNAL EMAIL - Please use caution with links and attachments * Hello Ben, The 407 is sent upstream, but when it is lost, it is not retransmitted by OpenSIPS. I do not have this problem with other negative status codes (e.g. 486). This is clearly explained in https://opensips.org/pub/opensips/1.8.6/src/ChangeLog 2012-03-21 18:36:58 Bogdan-Andrei Iancu, * [8811] : TM will no longer do retransmission for the 407/401 replies (if no ACK is received) for both local or proxied replies. According to RFC 3261, retransmitting 407s/401s is probably a bad idea: 26.3.2.4 DoS Protection At the moment, my only solution is to use forward() instead of t_relay() in order to use the stateless mode. Yannick Yannick, The default behavior of OpenSIPS is to relay any received responses back upstream. If it is not doing that it would have to be because you are stopping it in the script. Take a look at the documentation for failure_route [1] which explains this. Check your own failure_route in your script; you must be doing something there that is telling OpenSIPS not to relay the 401/407 back upstream. [1]https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 Ben Newlin From: Users <mailto:users-boun...@lists.opensips.org> on behalf of Yannick LE COENT <mailto:yannick.leco...@nexcom.fr> Date: Friday, April 29, 2022 at 6:44 PM To:users@lists.opensips.org <mailto:users@lists.opensips.org> Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello, I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy is in charge of authenticating the request. This is the callflow: Alice OpenSIPS Proxy#2 | INVITE | | |--->| INVITE | | 100 Tring |--->| |<---| 407 | | |<---| | | ACK | | |--->| | 407 | | | X<-| | | | | Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. What can I do ? If I set auto_100trying=1, that works, but this increases the number of INVITE retransmissions since 180Ringing are not received instantly. Do you have any suggestion ? Thanks, Yannick ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Hello Ben, Thanks for your answer. This problem occurs when OpenSIPS is not in charge of authenticating the INVITE request, but this is done downstream. I've sent this question to know if somebody has already solved this kind of problem. Best regards, Yannick Le 30/04/2022 à 16:15, Ben Newlin a écrit : I see. Apologies, I misunderstood the problem scenario. Ben Newlin *From: *Users on behalf of Yannick LE COENT *Date: *Saturday, April 30, 2022 at 5:46 AM *To: *OpenSIPS users mailling list *Subject: *Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission *EXTERNAL EMAIL - Please use caution with links and attachments * Hello Ben, The 407 is sent upstream, but when it is lost, it is not retransmitted by OpenSIPS. I do not have this problem with other negative status codes (e.g. 486). This is clearly explained in https://opensips.org/pub/opensips/1.8.6/src/ChangeLog 2012-03-21 18:36:58 Bogdan-Andrei Iancu, * [8811] : TM will no longer do retransmission for the 407/401 replies (if no ACK is received) for both local or proxied replies. According to RFC 3261, retransmitting 407s/401s is probably a bad idea: 26.3.2.4 DoS Protection At the moment, my only solution is to use forward() instead of t_relay() in order to use the stateless mode. Yannick Yannick, The default behavior of OpenSIPS is to relay any received responses back upstream. If it is not doing that it would have to be because you are stopping it in the script. Take a look at the documentation for failure_route [1] which explains this. Check your own failure_route in your script; you must be doing something there that is telling OpenSIPS not to relay the 401/407 back upstream. [1]https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 Ben Newlin From: Users <mailto:users-boun...@lists.opensips.org> on behalf of Yannick LE COENT <mailto:yannick.leco...@nexcom.fr> Date: Friday, April 29, 2022 at 6:44 PM To:users@lists.opensips.org <mailto:users@lists.opensips.org> Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello, I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy is in charge of authenticating the request. This is the callflow: Alice OpenSIPS Proxy#2 | INVITE | | |--->| INVITE | | 100 Tring |--->| |<---| 407 | | |<---| | | ACK | | |--->| | 407 | | | X<-| | | | | Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. What can I do ? If I set auto_100trying=1, that works, but this increases the number of INVITE retransmissions since 180Ringing are not received instantly. Do you have any suggestion ? Thanks, Yannick ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
I see. Apologies, I misunderstood the problem scenario. Ben Newlin From: Users on behalf of Yannick LE COENT Date: Saturday, April 30, 2022 at 5:46 AM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello Ben, The 407 is sent upstream, but when it is lost, it is not retransmitted by OpenSIPS. I do not have this problem with other negative status codes (e.g. 486). This is clearly explained in https://opensips.org/pub/opensips/1.8.6/src/ChangeLog<https://opensips.org/pub/opensips/1.8.6/src/ChangeLog> 2012-03-21 18:36:58 Bogdan-Andrei Iancu, * [8811] : TM will no longer do retransmission for the 407/401 replies (if no ACK is received) for both local or proxied replies. According to RFC 3261, retransmitting 407s/401s is probably a bad idea: 26.3.2.4 DoS Protection At the moment, my only solution is to use forward() instead of t_relay() in order to use the stateless mode. Yannick Yannick, The default behavior of OpenSIPS is to relay any received responses back upstream. If it is not doing that it would have to be because you are stopping it in the script. Take a look at the documentation for failure_route [1] which explains this. Check your own failure_route in your script; you must be doing something there that is telling OpenSIPS not to relay the 401/407 back upstream. [1] https://www.opensips.org/Documentation/Script-Routes-2-4#toc3<https://www.opensips.org/Documentation/Script-Routes-2-4#toc3> Ben Newlin From: Users <mailto:users-boun...@lists.opensips.org> on behalf of Yannick LE COENT <mailto:yannick.leco...@nexcom.fr> Date: Friday, April 29, 2022 at 6:44 PM To: users@lists.opensips.org<mailto:users@lists.opensips.org> <mailto:users@lists.opensips.org> Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello, I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy is in charge of authenticating the request. This is the callflow: Alice OpenSIPS Proxy#2 | INVITE || |--->| INVITE | | 100 Tring |--->| |<---|407 | ||<---| || ACK| ||--->| |407 || | X<-|| ||| Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. What can I do ? If I set auto_100trying=1, that works, but this increases the number of INVITE retransmissions since 180Ringing are not received instantly. Do you have any suggestion ? Thanks, Yannick ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Hello Ben, The 407 is sent upstream, but when it is lost, it is not retransmitted by OpenSIPS. I do not have this problem with other negative status codes (e.g. 486). This is clearly explained in https://opensips.org/pub/opensips/1.8.6/src/ChangeLog 2012-03-21 18:36:58 Bogdan-Andrei Iancu, * [8811] : TM will no longer do retransmission for the 407/401 replies (if no ACK is received) for both local or proxied replies. According to RFC 3261, retransmitting 407s/401s is probably a bad idea: 26.3.2.4 DoS Protection At the moment, my only solution is to use forward() instead of t_relay() in order to use the stateless mode. Yannick Yannick, The default behavior of OpenSIPS is to relay any received responses back upstream. If it is not doing that it would have to be because you are stopping it in the script. Take a look at the documentation for failure_route [1] which explains this. Check your own failure_route in your script; you must be doing something there that is telling OpenSIPS not to relay the 401/407 back upstream. [1]https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 Ben Newlin From: Users on behalf of Yannick LE COENT Date: Friday, April 29, 2022 at 6:44 PM To:users@lists.opensips.org Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello, I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy is in charge of authenticating the request. This is the callflow: Alice OpenSIPS Proxy#2 | INVITE || |--->| INVITE | | 100 Tring |--->| |<---|407 | ||<---| || ACK| ||--->| |407 || | X<-|| ||| Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. What can I do ? If I set auto_100trying=1, that works, but this increases the number of INVITE retransmissions since 180Ringing are not received instantly. Do you have any suggestion ? Thanks, Yannick___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS : no 407 retransmission
Yannick, The default behavior of OpenSIPS is to relay any received responses back upstream. If it is not doing that it would have to be because you are stopping it in the script. Take a look at the documentation for failure_route [1] which explains this. Check your own failure_route in your script; you must be doing something there that is telling OpenSIPS not to relay the 401/407 back upstream. [1] https://www.opensips.org/Documentation/Script-Routes-2-4#toc3 Ben Newlin From: Users on behalf of Yannick LE COENT Date: Friday, April 29, 2022 at 6:44 PM To: users@lists.opensips.org Subject: [OpenSIPS-Users] OpenSIPS : no 407 retransmission EXTERNAL EMAIL - Please use caution with links and attachments Hello, I'm using OpenSIPS as a proxy in front of another proxy. The 2nd proxy is in charge of authenticating the request. This is the callflow: Alice OpenSIPS Proxy#2 | INVITE || |--->| INVITE | | 100 Tring |--->| |<---|407 | ||<---| || ACK| ||--->| |407 || | X<-|| ||| Since OpenSIPS does not retransmit 401/407, the call setup gets stuck. What can I do ? If I set auto_100trying=1, that works, but this increases the number of INVITE retransmissions since 180Ringing are not received instantly. Do you have any suggestion ? Thanks, Yannick ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
