I guess the details in Section 3 of rfc4855, overrides rfc4566, which suggests
that telephone-event is case-insensitive:
An example mapping is as follows:
audio/L16; rate=48000; channels=2; ptime=5; emphasis=50-15
m=audio 49170 RTP/AVP 97
a=rtpmap:97 L16/48000/2
a=fmtp:97 emphasis=50-15
a=ptime:5
Note that the payload format (encoding) names defined in the RTP
Profile [4] are commonly shown in upper case. Media subtype names
are commonly shown in lower case. These names are case-insensitive
in both places. Similarly, parameter names are case-insensitive both
in media type strings and in the default mapping to the SDP a=fmtp
attribute.
Thanks,
Pranab
________________________________________
From: [email protected]
[[email protected]] On Behalf Of Pranab Bohra
[[email protected]]
Sent: Tuesday, July 24, 2012 6:12 PM
To: Aleksey Entsov; sip-implementors
Subject: Re: [Sip-implementors] Is value of SDP "a" field case-sensitive?
Hi Aleksey,
>From rfc 4566 -
"In general, <value> is either a number of fields delimited by a single
space character or a free format string, and is case-significant
unless a specific field defines otherwise."
I would infer that <value> is case-significant as well.
Thanks,
Pranab
________________________________________
From: [email protected]
[[email protected]] On Behalf Of Aleksey Entsov
[[email protected]]
Sent: Tuesday, July 24, 2012 5:44 PM
To: sip-implementors
Subject: [Sip-implementors] Is value of SDP "a" field case-sensitive?
Hi Everyone!
In some call scenario I have incoming 180/SDP.
And SDP contains this line:
.....
a=rtpmap:101 TELEPHONE-EVENT/8000
.....
My gateway cannot parse this string "TELEPHONE-EVENT/8000" because upper-case
letters are used. If "telephone-event/8000" string comes in lower-case letters
only,
then it's fine. Value of "a=" field can be parsed.
So the question is:
Is it allowed to use upper-case letters for "TELEPHONE-EVENT"?
I was searching through RFC, but could not find the explicit approval.
RFC4566 says "An SDP session description consists of a number of lines of text
of
the form:
<type>=<value>
where <type> MUST be exactly one case-significant character and
<value> is structured text whose format depends on
<type>. In
general, <value> is either a number of fields delimited
by a single
space character or a free format string, and is
case-significant
unless a specific field defines otherwise. Whitespace
MUST NOT be
used on either side of the "=" sign."
I found that <type> fied should becase sensitive. Bot how about <value>?
Best regards,
Aleksey Entsov
mailto:[email protected]
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
________________________________
SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary
or legally privileged information. In case you are not the original intended
Recipient of the message, you must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message and you are requested to
delete it and inform the sender. Any views expressed in this message are those
of the individual sender unless otherwise stated. Nothing contained in this
message shall be construed as an offer or acceptance of any offer by Sasken
Communication Technologies Limited ("Sasken") unless sent with that express
intent and with due authority of Sasken. Sasken has taken enough precautions to
prevent the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
