Hi Damir, A proxy can fork an initial INVITE based on whatever logic, to whatever destination - the forking mechanism is not necessary related to registration (multiple devices registered with the same account).
Forking is used only for initial request (when establishing the dialog) in order to try multiple locations for finding a callee to pick up the call (callee discovery)). After the call is setup (200 OK), for the sequential requests there will be no forking as the dialog path and parties are known and there is no need for any discovery. Regards, Bogdan Damir Reic wrote: > Hi all, > > I have a question regarding forking mechanism. > Is it possible that a proxy forks a request to an AOR? I believe it would > imply that a proxy forks a request to two different proxies which would end > up with loop detection on UAS side. So forking is done only in proxies that > have user contacts stored in it's location service? So non-INVITE requests, > which are sent within a dialog (early or confirmed) will never fork? > Now, if I got it all right, from UAC perspective, when it sends an initial > INVITE to a user that has n contacts stored in it's proxies LS it is > possible that most n early dialogs will be created, probably with the same > route-set, but sure different remote target? > Thanks for any clarification. > > regards, > Damir > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
