Hi 

INFO method is defined in RFC 2976. But yes "dtmf" and "dtmf-relay" are
not standard defined mime types. No there is no registered MIME type for
DTMF.  


Regards
Ranjit

-----Original Message-----
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Shefali Dutta
Sent: Tuesday, September 15, 2009 4:28 PM
To: Rohit Aggarwal
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] [Sip-Implementors] DTMF using SIP INFO

Hi,
  Thanks for your reply.

The link below gives two MIME types application/dtmf and
application/dtmf-relay but additionally gives the Note ->

"Note: dtmf-relay or dtmf are not yet IANA registered application mime
types"

Is there some other registered MIME type for DTMF?

Rgds,
Shefali

-----Original Message-----
From: Rohit Aggarwal
Sent: Tuesday, September 15, 2009 3:29 PM
To: Shefali Dutta
Subject: RE: [Sip-Implementors] DTMF using SIP INFO

Hi Shefali

Checkout
http://www.voip-info.org/wiki/view/SIP+Info+DTMF

Regards
Rohit Aggarwal

-----Original Message-----
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Shefali Dutta
Sent: Tuesday, September 15, 2009 3:25 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] [Sip-Implementors] DTMF using SIP INFO

Hi All,
  How DTMF is carried using SIP INFO method? I found some examples using
Content type application/dtmf and application/dtmf-relay. Which is the
reference RFC for these content types?

Rgds,
Shefali


________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error,please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility for loss or damage arising from the use of the
information transmitted by this email including damage from virus."
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

"DISCLAIMER: This message is proprietary to Aricent and is intended
solely for the use of the individual to whom it is addressed. It may
contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.
If you have received this message in error,please notify the originator
immediately. If you are not the intended recipient, you are notified
that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. Aricent accepts no
responsibility for loss or damage arising from the use of the
information transmitted by this email including damage from virus."

_______________________________________________
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

Reply via email to