Nitin Kapoor wrote:
Thanks for your reply.
I checked the RFC and noticed that it does not limit the codec #s in mline,
but nor does it comment on infinite number of codecs support being
mandatory.
So could you please let me know whether it is mandatory to support them or
not. Because if my SBC is not supporting this then i cannot go and ask them
to support this.
Well, the number is far from infinite. There are only 128 possible
payload types, so you shouldn't see more than that many values.
Since there is a reasonable upper bound, it shouldn't be so hard to support.
The device that sent you this clearly thought it was something they were
prepared to deal with. You can refuse the ones you don't like, so what
is the problem?
Thanks,
Paul
Thanks,
Nitin Kapoor
On 1 September 2010 13:00, Sameer Sawhney <ssawh...@cisco.com> wrote:
As per spec 2327 this is valid ! check fmt.
media-field = "m=" media space port ["/" integer]
space proto 1*(space fmt) CRLF
media = 1*(alpha-numeric)
;typically "audio", "video", "application"
;or "data"
fmt = 1*(alpha-numeric)
;typically an RTP payload type for audio
;and video media
proto = 1*(alpha-numeric)
;typically "RTP/AVP" or "udp" for IP4
port = 1*(DIGIT)
;should in the range "1024" to "65535" inclusive
;for UDP based media
-----Original Message-----
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Nitin
Kapoor
Sent: Wednesday, September 01, 2010 7:21 PM
To: sip-implement...@lists.cs.columbia.edu; sip@ietf.org
Subject: [Sip-implementors] Infinite Number of RTP payload in "mline"
Dear All,
I am facing the problem where one of source is sending bunch of RTP payload
in "mline", and because of that my MSX is stripping 2 codec from that line,
when its forwarding that OFFER to termination end.
This is the "mline" which i am getting from source:
*m=audio 6300 RTP/AVP 18 0 8 35 36 2 38 39 40 41 42 43 44 45 46 47 4 80 3
56
118 101 13 120*
This is what my MSX is sending to termination after stripping the payload
from "mline"
*m=audio 6300 RTP/AVP 18 0 8 35 36 2 38 39 40 41 42 43 44 45 46 47 4 80 3
56
118 101 *
Now i checked some documents but unable to find anything which says its
correct or not.
Could any one please give some direction on this whether such amount of
payload type is correct in "mline" or it not acceptable .
Thanks,
Nitin Kapoor
_______________________________________________
Sip-implementors mailing list
sip-implement...@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
sip-implement...@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use sip-implement...@cs.columbia.edu for questions on how to develop a SIP
implementation.
Use dispa...@ietf.org for new developments on the application of sip.
Use sipc...@ietf.org for issues related to maintenance of the core SIP
specifications.
