Stephan Steiner wrote: > Dale > > Is there any guidance in an RFC with regards to that? I dug out an older > thread > (http://www.opensubscriber.com/message/sip-implement...@cs.columbia.edu/6832126.html) > > where Bala said those attributes are global, not codec specific. Is there > any reference for that (in that case we can open a case with the > manufacturer of the PBX)? For now we're attempting to remove the codec that > causes the inconsistency in the hopes that this will permit interoperability > but of course the end goal is to have it fixed in case G.723 ever becomes > needed.
The RFC4566 (http://tools.ietf.org/html/rfc4566) has no provisions for the a=rtpmap creating its own sub-section within the media description. It says that attribute can be connection-scope or session-scope, there is nothing about rtpmap-scope in there. IMHO if any codec-specific parameters are necessary they should use the a=fmtp attribute for that. 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
