The info method is unofficial and non-standard.
One of its limitations is that it *isn't* negotiated.
The "official" ways are:
- in the rtp media itself
- rfc2833 in the media stream
- kpml event package
(draft-ietf-sipping-kpml-08, which is done except for
dependency, on gruu I think.)
In addition, there is work on an *enhanced* info mechanism with
negotiation. That might eventually provide a way to negotiate dtmf over
info.
Thanks,
Paul
Peter Nijhuis wrote:
> Sending dtmf tones over sip can be done in 2 ways, SIP INFO or RFC2833. Using
> RFC2833 is negotiated in the SDP message as Media Attribute (a): rtpmap:101
> telephone-event/8000. In SDP is negotiated if this media attribute is used or
> not, but when sending dtmf as SIP INFO there is no negotiation, but only a
> 415 message telling the remote party that this media type is unsupported.
>
> Is there a way to switch back to RFC2833 if SIP INFO is not supported, or
> should SIP INFO be negotiated in SDP too?
>
> Met vriendelijke groet, with kind regards, mit freundlichen Gruß
>
> Peter Nijhuis
> peter.nijh...@televersal.com
>
>
> _______________________________________________
> 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
