Opened 9 years ago

Closed 9 years ago

#1148 closed defect (fixed)

Assertion when offering SDP media with port zero but answered with port non-zero

Reported by: nanang Owned by: nanang
Priority: normal Milestone:
Component: pjmedia Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported:

Description (last modified by nanang)

When SDP media in the offer uses port zero, it means that the media is not wanted and must be answered with port zero as well (RFC 3264 Section 5.1 and 8.2). However, some implementations may disobey it (we found one!), and unfortunately it may lead to assertion in the SDP negotiation process (when there is dynamic payload type involved).

Sample SDP offer/answer that trigger assertion:

  • Offer (may be after some offer/answer cycles):
    ...
    m=audio 4000 RTP/AVP 0
    m=video 0 RTP/AVP 100
    ...
    
  • Answer:
    ...
    m=audio 6000 RTP/AVP 0
    m=video 7000 RTP/AVP 100
    a=rtpmap:100 H261/90000
    ...
    

Change History (2)

comment:1 Changed 9 years ago by nanang

  • Description modified (diff)

comment:2 Changed 9 years ago by nanang

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

(In [3347]) Fixed #1148:

  • Added check in processing answer, if media offer port is zero, just skip negotiation process.
  • Added SIPp test scenario.
Note: See TracTickets for help on using tickets.