Hi,
The per-branch data is :
* R-URI
* DST-URI (outbound proxy)
* PATH header
* q value (priority)
* send_socket
* branch flags
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 28.11.2016 14:11, Schoolhouse Filing wrote:
Hi Razvan,
What I found was then if I appended branches then called
force_send_socket() only the current branch went out on that
interface, the other branches went out on a different interface. It's
not a problem I will re-structure my script, I was simply appending
branches to create a ring group.
Kind Regards,
Adrian.
On 28/11/16 09:35, Răzvan Crainea wrote:
Hi, Adrian!
I don't think you will find such a list.
Usually the idea is to do the changes that affect all branches in the
main route, and if you want to do per-branch changes, do them in the
branch_route.
Are you sure that force_send_socket() only applies to the main
branch? If you call force_send_socket() in the main route, and then
add a second branch, the messages leave on different interfaces?
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 11/26/2016 12:19 PM, Adrian Fretwell wrote:
Hello,
I understand from the documentation that after calling
append_branch() any further URI manipulations only apply to the main
branch, but I am trying to understand what actions will still apply
over all the branches. For example I discovered that
rtpproxy_offer() appears to affect all branches, but
force_send_socket() only apples to the main branch.
Is there a list or rule that will help me work out what I need to
apply before branching and what I can leave until later, perhaps
until just before t_relay() is called?
I hope my question makes sense.
Kind regards,
Adrian Fretwell
The Old School house
Top Green
Sibthorpe
Nottinghamshire
NG23 5PN.
T: 01636 525360
M: 07850 756603
This electronic message contains information from A-Squared
Engineering Services which may be privileged or confidential. The
information is intended to be for the use of the individual(s) or
entity(s) named above. If you are not the intended recipient be
aware that any disclosure, copying, distribution or use of the
contents of this information is prohibited. If you have received
this electronic message in error, please notify us by telephone or
email to [email protected] immediately.
_______________________________________________
Users mailing list
[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
_______________________________________________
Users mailing list
[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
