elzaksspro / sipservlets

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

Via Header used instead of Contact Header for ReINVITE (from callee to caller) proxying #276

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
After establishing a session, the callee performs a Re-INVITE. 
The Request-URI of this outgoing Re-INVITE (from mobicents side) is not 
correct. 
Mobicents use the Record-Route header (or the last Via Header if none 
Record-Route is present) to proxy the Re-INVITE but it should use the Contact 
header of the initial INVITE.

Original issue reported on code.google.com by jean.der...@telestax.com on 23 Jul 2014 at 2:28

GoogleCodeExporter commented 8 years ago
https://telestax.atlassian.net/browse/MSS-112

Original comment by jean.der...@telestax.com on 23 Jul 2014 at 2:44

GoogleCodeExporter commented 8 years ago
This issue was updated by revision ae6c2c3ba8ee.

Backport to master : Fix + non regression tests
(cherry picked from commit 3b6ac5c0040c2140442dc3da988e41782f821434)

Conflicts:

    sip-servlets-impl/src/main/java/org/mobicents/servlet/sip/proxy/ProxyImpl.java
(cherry picked from commit 820735639c885348064bf60b161c781c4e4bcb9c)

Original comment by jean.der...@telestax.com on 24 Jul 2014 at 11:26

GoogleCodeExporter commented 8 years ago

Original comment by jean.der...@telestax.com on 24 Jul 2014 at 12:53

GoogleCodeExporter commented 8 years ago
This issue was updated by revision c409bb8281ce.

fix for TCK failing tests
(cherry picked from commit 52a4c8d34921a707f3ddadd4fd37d1be9d3908ab)

Original comment by jean.der...@telestax.com on 24 Jul 2014 at 9:25

GoogleCodeExporter commented 8 years ago

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