Hi, I am struggling to find out this from long time, however have seen some implementation as follows;
1. First of all, you can't know whether remote end has a capability to detect DTMF in Inband. 2. For SIP INFO, your device can consider that remote end supports SIP INFO if received in Allow header. If received, it's upto your device whether to generate DTMF in Inband or SIP INFO. 3. You can't always fallback to SIP INFO if RFC 2833 negotiation fails. Remote end must be capable of detecting DTMF in SIP INFO and this would be known only if INFO is received in Allow header. If RFC 2833 negotiation fails and remote end hasn't capability of detecting DTMF in SIP INFO, you haven't any other choice than sending DTMF in Inband :) Different people may have different views but that is what implemented in most of the live products. Best Regards, Vivek Batra Quoting "Manoj Priyankara" <manoj0...@gmail.com>: > Folks, > > I wonder how the offerer recognizes whether a particular SIP end point > supports in-band DTMF or SIP INFO by negotiating SDP? SIP INFO is assumed > when RFC2833 negotiation fails but how exactly we know whether the endpoint > supports SIP INFO not In Band? > > Cheers! > Manoj > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
