Hi Paul
Yes, understand the remote-party-id is not part of sip standard. But in our
environment the scenario as follows
Call-leg-1: sip-dialer---------cisco-cm----phone
Call-leg-2: sip-dialer---------cisco-cm-----uccx trigger DN then call
transferred to agent DN then transfer to agent phone.
Finally the RTP path should get established between sip-dialer & agent phone.
The re-invite case happens for call-leg-2.
We are expecting the agent phone's media ip:port in the sdp connection details.
But only the sip signalling ip:port available in remote - party - id.
In this case how to establish media path between sip-dialer with agent phone.
Sorry if I'm not making it clear..will explain further if required.
Thank you...
Regards
Mahu
-------- Original message --------
From: Paul Kyzivat
Date:05/10/2015 22:25 (GMT+05:30)
To: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Remote-party-id in reinvite
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
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
