Hi Jagan Yes, B2bua can insert the sip methods in the ALLOW header. For the response for the unsupported codec, I think the B2bua will respond back with 488, as per the extract from RFC 3311 below
*If the new session description is* * not acceptable, the UAS can reject it by returning a 488 (Not* * Acceptable Here) response for the UPDATE. This response SHOULD* * include a Warning header field.* ** Hope this helps Rgds Retesh _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
