If you go by the RTP/SDP guidelines the UAs should be capable and ready to receive rtp for any of the negotiated codecs. It is just not limited to the first one in the List.
If that is the case changing the order of the codecs does not matter. Also if the SDP version is not changed in the SDP it can be ignored. If the sdp version is changed it shld result in a new call-leg (To tag in 200 OK shld be different from the To:Tag in 18x Response) as if forking has happened Downstream. Kasturi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barman, Sibon B (Sibon) Sent: Friday, April 13, 2007 2:21 PM To: [EMAIL PROTECTED] Subject: [Sip-implementors] early media response codec sequence is differentfrom final answer codec sequence An INVITE is sent out with the following codec sequence in the offer: G729, G711a, G711u, A 183 response comes back up with the following codec sequence in its SDP: G729, G711a, G711u A 200 OK response come back with the following codec sequence in its SDP: G711u, G711a, G729 Is changing codec sequence in the 200 OK from 183 legal? I am guessing it is --- just need to verify if that's the case. Sibon Barman <http://fifaworldcup.avaya.com/default.asp> _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
