Dale Is there any guidance in an RFC with regards to that? I dug out an older thread (http://www.opensubscriber.com/message/[email protected]/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.
Regards Stephan -------------------------------------------------- From: "Dale Worley" <[email protected]> Sent: Wednesday, February 11, 2009 11:09 PM To: "Stephan Steiner" <[email protected]> Cc: <[email protected]> Subject: Re: [Sip-implementors] 488 Invalid incoming Gateway SDP: Invalidmedia > On Wed, 2009-02-11 at 22:52 +0100, Stephan Steiner wrote: >> v=0 >> o=OXE 1233842864 1233842864 IN IP4 10.145.27.72 >> s=abs >> c=IN IP4 10.145.26.27 >> t=0 0 >> m=audio 32514 RTP/AVP 8 0 4 97 >> a=sendrecv >> a=rtpmap:8 PCMA/8000 >> a=ptime:20 >> a=maxptime:30 >> a=rtpmap:0 PCMU/8000 >> a=ptime:20 >> a=maxptime:30 >> a=rtpmap:4 G723/8000 >> a=ptime:30 >> a=maxptime:30 >> a=rtpmap:97 telephone-event/8000 > > I see that the first m-group has 3 instances of a=ptime and 3 of > a=maxptime, and the ptime values are not consistent. As far as I know > (and I may be wrong), the a=rtpmap attributes do not create subgroups of > the a-lines within the m-group, so the various a=ptime values contradict > each other, rather than describing separate ptimes for each codec. > > Dale > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
