> > In this case you should not advertise that you can. Use separate "m" > lines, each with one codec. This will remove the ambiguity you're > having, and be compliant with the relative RFCs. >
Hi Bert, This sounds like a good idea, and it would mean that the answerer wouldn't dynamically change codecs used on each RTP port - but I think it give the impression that the offerer can support multiple _simultaneous_ different codec streams, all on seperate RTP ports. What I actually want is the offerer to advertise all the codecs it supports in such a way that the answerer responds with just one. Alex _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
