search

gulelat / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 0 forks source link

Unnecessary Accept-contact header in 200 OK response #127

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
2.3.1.1 SIP OPTIONS message extension to support capability discovery
The RCS (Release 1 and 2) specifications only provide a mechanism to exchange 
the
capability status (based on a SIP OPTIONS exchange) related to the image and 
video
share services during a call. This mechanism is based on the use of tags 
transported in the
Accept-contact and Contact headers for the SIP OPTIONS and its responses:
• The tags corresponding to the set of functionalities supported by the 
requesting terminal
at the time this request is made are carried in both the Contact and 
Accept-contact
headers of the SIP OPTIONS message.
• The tags corresponding to the subset of the functionalities that are 
supported by the
receiver are included in the Contact header of the 200 OK response.

Original issue reported on code.google.com by jmauffret@gmail.com on 30 Jul 2013 at 9:29