Thank you Bogdan. Got it. Regards, Agalya
From: Bogdan-Andrei Iancu [mailto:[email protected]] Sent: Wednesday, September 14, 2016 10:33 AM To: OpenSIPS users mailling list <[email protected]>; Ramachandran, Agalya (Contractor) <[email protected]> Subject: Re: [OpenSIPS-Users] Question regarding append_branch Hi Agalya, The append_branch() itself is not doing any SIP signaling. It is only creating (internally, as data structure) a new branch for the request (to a new destination). The signalling (to all created branches) is done by TM module when you relay the request out. The forking is a transaction level mechanism and it is handled by the TM module. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 07.09.2016 16:56, Ramachandran, Agalya (Contractor) wrote: Hi team, When append_branch() is called, it takes care of the forking process. When we say it is used to fork the call, append_branch() takes care of sending the request out to that branch and as well maintaining the dialog and transaction information for that call leg or it is used only to send SIP INVITE out? Sounds like a basic question. But I want to make sure how it works. Am assuming it takes care of dialog and transaction for that call leg and it maps the response to that call leg as well. Correct me if am wrong. Regards, Agalya _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
