Thanks for the explanation! That matches what I was expecting to see so I think
there is an issue worth examining here.
*** Server Details ***
opensips -V
version: opensips 2.3.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
Hi Bogdan,
Thanks for the reply!
Yes correct the $avp(originURI) I set to;
$avp(originURI) = "sip:" + $si + ":" + $sp;
Then use it a few times;
if(dr_is_gw("$avp(originURI)","1")) {
Do some stuff
}
if(dr_is_gw("$avp(originURI)", "2")) {
# Do some other stuff
}
However
Let me rephrase. The UA receives a 401 message from opensip. The nonce is
reported as stale. The UA attempts again to register using the same nonce as
previously. On and on. I calculated the digest myself and it is correct for
the stale nonce. My thinking is that if opensips ignored the fact
Hi Jon,
So, the $avp(originURI) holds a SIP URI pointing to a FS box. But the
check against group 2 fails and against group 1 succeeds ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
HI Sean,
If I understand correctly your setup, you should use into PATH support
on opensips (RFC 3327). Also take a look at the path module in OpenSIPS:
http://www.opensips.org/html/docs/modules/2.3.x/path.html
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
Hi Rob,
A "reused" and a "stale" nonce are different things. A reused one means
that same nonce is to be used for multiple auth attempts. A stale nonce
means the nonce (used or not) is rejected as it is too old (relative to
the time when the nonce was generated by the server).
Of course,
Hi,
Are you sure the OpenSIPS LB is able to reach via SIP the destinations
you configured in the LB table ? Run a single call (with sipp) and make
a network capture to understand how the call is routed.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
Hi Guys,
Is there any reason why after moving from version 2.2.5 to 2.3.2 that I would
then get issues with drouting module, in particular dr_is_gw ?
As if I test between the two versions the same statement doesnt match correctly.
Essentially I have 2 main gateways types in dr_gateways, type=1
Hi, Steve!
The transport layer was heavily refactored roughly three years ago, see
[1], [2] and [3] for the relevant commits which, indeed, bumped the
default connect timeout down a lot, to a much lower value (10s ->
100ms). Although 100ms might seem unnecessary (it's async! let it sleep
as
Hi, Tito!
Can you try to compile with memory debugging (compiling with QM_MALLOC
and DBG_MALOC macros)? You can do that either manually[1] or by using
the menuconfig tool, where you should go to Compile Flags and enable the
two macros, then recompile your sources.
[1]
10 matches
Mail list logo