On 10/5/15 8:43 AM, Mahudeswaran A wrote:
Hello All,
We are facing a situation and looking for insights on how to handle the scenario
1.uac--------------(invite/sdp)-------------------->uas
2.uac<------------(100 trying)---------------uas
3.uac<------------(200ok/sdp)--------------------uas
4.uac--------------(Ack)---------------------->uas
-----
5.uac<------------(re-invite/sdp)-----------------uas
6.uac--------------(200ok/sdp)------------------>uas
7.uac<------------(Ack)-----------------------------uas
In the above sequence, at step-5, re-invite comes with remote-party-id sip
header. The step-3, step-5 connection details in SDP are same. The RTP
connection ip and port are same.
How to handle this scenario?
The remote-party-id sip header comes with unique sip endpoint uri.
I don't understand what you are asking. The remote-party-id is a
declaration of fact. The recipient doesn't need to do anything with it.
Are you wondering if the receiving UA should make some change in its UI
as a result of this? (Such things are not standardized as part of sip.
Maybe they are standardized by 3gpp.)
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
