Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#1539 closed defect (fixed)

Remote capability info update for UAC (thanks Bogdan Krakowski for the report)

Reported by: nanang Owned by: bennylp
Priority: normal Milestone: release-2.0.1
Component: pjsip Version: trunk
Keywords: Cc:
Backport to 1.x milestone: release-1.16 Backported: yes

Description (last modified by nanang)

Reported 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.

For reference, the spec does specify about SIP header fields contexts:

  • headers in a provisional response, rfc3261 section-13.2.2.1:
    Header fields present in a provisional
    response are applicable as long as the dialog is in the early state
    (for example, an Allow header field in a provisional response
    contains the methods that can be used in the dialog while this is in
    the early state).
    
  • capability info headers in 2xx response, rfc3261 section-13.3.1.4
    A 2xx response to an INVITE SHOULD contain the Allow header field and
    the Supported header field, and MAY contain the Accept header field.
    Including these header fields allows the UAC to determine the
    features and extensions supported by the UAS for the duration of the
    call, without probing.
    

Change History (4)

comment:1 Changed 7 years ago by nanang

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

In 4171:

Fix #1539: Applied non-strict update of remote capability info after receiving the first 2xx response.

comment:2 Changed 7 years ago by nanang

  • Description modified (diff)

comment:3 Changed 6 years ago by nanang

In 4380:

Re #1539: backported to 1.x

comment:4 Changed 6 years ago by nanang

  • Backported set
Note: See TracTickets for help on using tickets.