Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#363 closed defect (fixed)

Incorrect RTP marker and timestamp in DTMF event/RFC 2833 packet (thanks Pedro Sanchez)

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

Description (last modified by bennylp)

Several bugs with DTMF event/RFC 2833 packet generation:

  1. PJSIP fails to set the SDP Marker flag to TRUE on the very first packet of each sequence as requested by RFC 2833 section 3.4.
  2. RTP time stamp in the RTP EVENT packets should remain the same for a single event, according to RFC 2833 section 3.6:

"If an event continues for more than one period, the source generating the events should send a new event packet with the RTP timestamp value corresponding to the beginning of the event and the duration of the event increased correspondingly."

Change History (4)

comment:1 Changed 12 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 12 years ago by bennylp

  • Description modified (diff)

comment:3 Changed 12 years ago by bennylp

  • Resolution set to fixed
  • Status changed from new to closed
  • Summary changed from Several bugs with DTMF event/RFC 2833 packet generation (thanks Pedro Sanchez) to Incorrect RTP marker and timestamp in DTMF event/RFC 2833 packet (thanks Pedro Sanchez)

Fixed in r1416

comment:4 Changed 12 years ago by bennylp

Note:

One issue that hasn't been fixed:

RFC 2833 Section 3.6:

If there has been no new event in the last interval, the event SHOULD be retransmitted three times or until the next event is recognized. This ensures that the duration of the event can be recognized correctly even if the last packet for an event is lost

Note: See TracTickets for help on using tickets.