I think i got it, default limit is 12 branches in config.h. Which corresponds
to my limit of 12 gateways, I will try and report back. :)
#define MAX_BRANCHES12 /*!< maximum number of branches
per transaction */
Max Mühlbronner
--
42com Telecommunication GmbH
Bogdan,
I have been able to reproduce this locally now. The piece that was missing is
that the Request URI must already have URI parameters on it. If it has both URI
and user parameters, the call to route_to_carrier (and possibly do_routing)
replaces all of the URI parameters with the user
Hi Alex,
As suspected, the ACK is not properly routed - see the retransmissions
of the 200OK + ACK. SImply based on the logs I cannot see what the
problem is - probably some missing fix_nated_contact() for the replies
coming from the WS party.
Please make a pcap capture + opensips log
Hi Max,
Yes, a transaction cannot have more than 12 branches used. But this does
not limit how many GWs you can put in Dynamic Routing - you can put as
many as you want on DR, but of course only 12 will be tried. But this
depends a lot on the GW selection algorithm (with wights, with
Hi,
I've never noticed this until i came across it recently. I got a weird issue
with drouting, it turned out that even though the gatewaylist ("carrier")
contains a total of 20 gateways, only 12 are being used. (all gateways got the
same weight)
E.g. if all gws are rejecting the calls, it
Hi,
Put an extra fields in subscriber table in order to assign to each user
an routing group - and after auth (see load_credentialas in auth_db
module for loading extra columns from subscriber table), use the routing
group value in order to trigger the corresponding routing logic.
Regards,
Thanks, i will try raising max_branches to allow the use of more gateways.
Yeah i know it seems to be unusual to "try" so many gateways, but the setup
works with a lot of smaller instances which are immediately rejecting calls
when full to allow a failover to the next instances. Load balancing
Max,
After moving to 30, just check the usage of the shm memory, as TM will
start using more (the branches are statically part of the transactions,
so the transactions will become larger with 30 branches).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
Thanks for the hint. I will keep an eye on it.
BR
Max M.
Von: Bogdan-Andrei Iancu
Gesendet: Montag, 3. Juli 2017 12:49:21
An: Max Mühlbronner; OpenSIPS users mailling list
Betreff: Re: AW: [OpenSIPS-Users] drouting (opensips 1.11.x) -
Hi Ben,
Thank you for your digging and reporting. Following your leads I found
some old strange behavior of the parse_uri() function - the function
responsible for parsing the URIs in OpenSISP.
For some ancient and unknown reasons, a SIP URI with user=phone was
automatically converted to a
This year we will be part of ClueCon once again !
https://blog.opensips.org/2017/07/03/opensips-cluecon-2017-training-and-more/
See you in Chicago,
--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2017, Houston, US
11 matches
Mail list logo