> -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of Maxim Sobolev > Sent: Friday, January 09, 2009 12:19 PM > To: Dale Worley > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] Weird SDP > > Dale Worley wrote: > > On Thu, 2009-01-08 at 10:21 -0800, Maxim Sobolev wrote: > >> We have come over to a device that generates "strange" SDP. Basically, > >> it splits the same media description into two separate media section. > As > >> a result our software considers it as two separate streams, not as one > >> which it apparently is. > >> > >> To me, it seems like the format is invalid, however I cannot find any > >> direct prohibition in the RFC 2327. What do people think: is it > allowed? > > > > I is *allowed*, but as you think, it means that there are two separate > > media streams (both of which are to be sent to port 5010. If the UA > > that is generating the SDP does not intend to specify two separate media > > streams, the UA is behaving incorrectly. > > Of course it does not. What's the point in having two separate audio > media streams in two different codecs sent to the same port?
Perhaps there is only one port open for media in the NAT pinhole and by sending two streams with different codecs, it is letting the terminating endpoint decide the location of the sink to play the media at, iLBC on the speaker and the other on Bluetooth headset. Serhad > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: sa...@sippysoft.com > Skype: SippySoft > _______________________________________________ > 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
