Hi Eduardo, Generally dialog is an end to end relation, not a SIP Proxy one. Proxy layer is built above transaction layer and there is no dialog forking there is only a request forking. When SIP Proxy receives a response, possibly related to forked requests, it finds the appropriate response context associated with server transaction created by downstream SIP request. Until the final response is sent on the server transaction any provisional response, other that 100, is immediately forwarded to UAC. UAC has to be prepared to handle many early dialogs (multiple provisional responses from different UAS) and further possible dialogs termination. In such case responses tag are used to identify any such early dialog.
Kind regards, - Tomasz Zieleniewski ------------------------------ ICT Backyard - http://ictbackyard.com On 2 September 2010 18:31, Eduardo Martins <emmart...@gmail.com> wrote: > Hello, trying to clarify thoughts with early dialog forking, generally > is there such concept? > > For instance when receiving two 180s with different tags, should: > > a) 2 early dialogs be "constructed" (why? is there any need to a > REQUEST to be sent before receiving 2xx response which needs the > tags?) > > or > > b) the remote tag should be ignored till final response arrives, > (cancel and pracks will not set a remote tag at all) > > Thanks in advance, > > -- Eduardo > > -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- > http://emmartins.blogspot.com > http://www.redhat.com/solutions/telco > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
