Mahudeswaran A <mahudeswara...@acqueon.com> writes: > 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.
You don't actually state what the problem is. BTW: Your use of UAC and UAS is incorrect. Those terms are only defined for a single transaction (request/response pair), the UAC is the endpoint that sends the request, the UAS is the endpoint that sends the response. So in 5, 6, and 7, the left endpoint is the UAC and the right endpoint is the UAS. (Yes, in SIP, connections are symmetric between the endpoints.) > 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. The appropriate address and port MUST arrive in the SDP that the endpoint receives. If it does not, the endpoint that is generating the SDP is doing so incorrectly. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
