Bogdan, thank you that is very helpful.
Kind regards,
Adrian Fretwell
On 29/11/16 12:14, Bogdan-Andrei Iancu wrote:
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
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
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
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
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
