Changes between Initial Version and Version 2 of Ticket #1539


Ignore:
Timestamp:
Jun 19, 2012 2:17:31 PM (12 years ago)
Author:
nanang
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1539

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed

  • Ticket #1539 – Description

    initial v2  
    11Reported that PJSIP sends UPDATE to lock to one codec, but remote does not like the UPDATE that finally causing the call to be hung up by PJSIP. From the SIP messages log, the 180 response has UPDATE method in Allow header, but the 200 response has not. 
     2 
     3For reference, the spec does specify about SIP header fields contexts: 
     4 - headers in a provisional response, [http://tools.ietf.org/html/rfc3261#section-13.2.2.1 rfc3261 section-13.2.2.1]: 
     5   {{{ 
     6   Header fields present in a provisional 
     7   response are applicable as long as the dialog is in the early state 
     8   (for example, an Allow header field in a provisional response 
     9   contains the methods that can be used in the dialog while this is in 
     10   the early state). 
     11   }}} 
     12 - capability info headers in 2xx response, [http://tools.ietf.org/html/rfc3261#section-13.3.1.4 rfc3261 section-13.3.1.4] 
     13   {{{ 
     14   A 2xx response to an INVITE SHOULD contain the Allow header field and 
     15   the Supported header field, and MAY contain the Accept header field. 
     16   Including these header fields allows the UAC to determine the 
     17   features and extensions supported by the UAS for the duration of the 
     18   call, without probing. 
     19   }}}