Mybe this is a matter of "interpretation" only. Are you logging the packets with Wireshark? Wireshark only displays the DTMF events as "DTMF events" if the original INVITE request (defining the RFC2833 payload type, here: 96) was logged in the beginning. If you start Wireshark after INVITE/OK was passed between both sides, the tool does not know how to interpret the RTP packets and uses a "transparent" mode for displaying the packets.
Mit freundlichen Grüßen Henning Christiansen -----Ursprüngliche Nachricht----- Von: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] Im Auftrag von Sylvester, Prasanth (NSN - IN/Bangalore) Gesendet: Montag, 11. August 2014 10:31 An: sip-implementors@lists.cs.columbia.edu Betreff: [Sip-implementors] SIP - DTMF transfer using RFC2833 Hi Team, Good day, In our deployment, MSS - SBC (Session border Controller) - IVR System MSS/MGW (.242) ---------> (.10) SBC (.9) ----------> IVR (10.58.2.20) RFC2833 is configured on all ends, I see MSS is sending the DTMF as RTP Events to SBC 402 3.845469000 10.33.64.242 10.33.1.10 RTP EVENT 58 Payload type=RTP Event, DTMF One 1 SBC is sending DTMF as RTP Events to IVR system 403 3.845471000 10.33.13.9 10.58.2.20 RTP EVENT 58 Payload type=RTP Event, DTMF One 1 However, when IVR system receives it, they get it as 551 88.724062 10.33.13.9 10.58.2.20 RTP 60 PT=DynamicRTP-Type-96, SSRC=0x81346A0C, Seq=169, Time=30560, Mark Please help me understand what PT=DynamicRTP-Type-96 in passing DTMF? Sylvester, Prasanth _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
