search

ed33 / rcsjta

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

Implementation for SIP response 403 (forbidden) missing #80

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
If SIP response 403 (forbidden), invitation fails but the session state or 
message status is unchanged.

Original issue reported on code.google.com by lemordan...@gmail.com on 26 Nov 2014 at 3:52

GoogleCodeExporter commented 8 years ago 
Would the changed implementation include handling of 127 warning header, too?

Original comment by andreas-...@telekom.de on 9 Dec 2014 at 11:03

GoogleCodeExporter commented 8 years ago 
Fixed by revision 586c23c044d3.
With the correction of this issue, response to invite request with 403 
forbidden is handled correctly by the session. If it is a GC restart and if the 
warning header is set to "127 Service not authorised" then the restart fails 
and a new GC session is created with the same Contribution-ID as per 
specification.

Original comment by lemordan...@gmail.com on 8 Jan 2015 at 8:30