We are facing an issue where the UAC send a Re-Invite with modified SDP as an offer(a=sendonly), the UAS replies it with a answer containing the previous SDP o line version number but with a modified attribute line(a=recvonly).
Please find the detailed Scenario: 1. UAC<->UAS (call is established) 2. UAC-------->UAS(Re-Invite with a=sendonly) 3. UAC<--------UAS(200 Ok with same SDP o line version number as present in 1 but with a=recvonly) As per RFC 3264 section 6 "If the answer is different from the offer in any way (different IP addresses, ports, etc.), the origin line MUST be different in the answer, since the answer is generated by a different entity. In that case, the version number in the "o=" line of the answer is unrelated to the version number in the o line of the offer." So is it mandatory for the UAS to increment the o line version number in the response of the Re-Invite? "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
