search

JNec / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

Problem with 407 proxy authentication in b2bua appliation #205

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
The flow I intend to implement is the following:

Client B2BUA SIP Trunk

     |      INVITE (SDP)         |                           |
     |-------------------------->|                           |
     |      100 TRYING           |                           |
     |<--------------------------|                           |
     |                           | INVITE (mod SDP)          |
     |                           |-------------------------->|
     |                           | 401 Unauthorized          |
     |                           |<--------------------------|
     |                           |      ACK                  | 
     |                           |-------------------------->|
     |    401 Unauthorized       |                           | 
     |<--------------------------|                           |
     |      ACK                  |                           | 
     |-------------------------->|                           |
     |      INVITE (SDP) W/AUTH  |                           |
     |-------------------------->|                           |
     |                           |  INVITE (mod SDP) W/AUTH  |
     |                           |-------------------------->|
     |                           | 200 OK (SDP)              |
     |                           |<--------------------------|
     | 200 OK (SDP)              |                           |
     |<--------------------------|                           |
     |      ACK                  |                           | 
     |-------------------------->|                           |
     |                           |      ACK                  | 
     |                           |-------------------------->|

In the B2BUA I don't have (and I don't want) to store the user credentials, so 
I just copy the authentication headers from one side to the other.

The problem I am getting is that the second INVITE with the authentication 
header does not belong to the same sip app session/sip session than the 
original so I am not able to find the session from the previous INVITE, so I am 
not able to create the new INVITE with the same call-id/from tag as the 
previous one.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
latest mss snapshot

Please provide any additional information below.
Discussed in the mobicents-public
https://groups.google.com/forum/?fromgroups=#!topic/mobicents-public/EhNobqO2F_w

Original issue reported on code.google.com by sergio.g...@gmail.com on 11 Apr 2013 at 9:51

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 5 Jul 2013 at 7:44

GoogleCodeExporter commented 8 years ago 
Won't be fixed for now as the spec mentioned it. See public thread on that

Original comment by jean.deruelle on 2 May 2014 at 4:21

GoogleCodeExporter commented 8 years ago

Original comment by jean.der...@telestax.com on 25 Aug 2014 at 10:53