Jagan Mohan wrote:
> Hi,
>
> If the codec change requested in a Re-INVITE needs to be rejected by UAS,
> is it mandatory to send a 488 response to the Re-INVITE and continue
> operating with the codec negotiated in the INVITE?
Would be helpful if you showed the specifics of the SDP in the initial
and subsequent o/a.
If the new offer has multiple codecs, and you object to one of them,
then of course you may answer omitting that one. If there is only one
codec offered in the reinvite, and you don't like it, then you could:
- reject the reinvite with a 488, continuing with your old codec
- successfully answer, accepting the codec, but in an inoperable way,
such as by specifying a=inactive or c=0.0.0.0
- answer successfully, but reject the media line, by setting the port
to zero
Of those, I would think that the 488 would normally be the most useful
alternative.
> From section 14 of RFC 3261, looks like it's not mandatory to send a 488
> response and more a implementation specific problem. In that case, is it ok
> to send a 2xx response to the Re-INVITE with the codec negotiated in the
> initial INVITE?
If your answer accepts the stream, then it must mention at least one of
the codecs from the offer.
You should look at RFC 3264 if you haven't already.
Thanks,
Paul
> Or is this case addressed in any other standard?
>
> Thanks,
> Jagan
> _______________________________________________
> 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
