Helo,
Can anyone help me know why opensips crashing? The last core dump backtrace
is as follows...
#0 0x7f6cc4be5786 in shm_str_dup (src=0x7f6d78ed64d8, dst=) at ../../ut.h:736
No locals.
#1 dlg_clone_callee_leg (dlg=dlg@entry=0x7f6d72b45050,
cloned_leg_idx=cloned_leg_idx@entry=6) at dlg_h
I think the problem is with the statistics module:
DBG:statistics:pv_parse_name: name 0x7f2a934d5fc0 with name
DBG:statistics:pv_parse_name: name 0x7f2a934d5fc0, name cloned
(in=0x7fff6f8b1876, out=0x7f2a934d8fa0)
DBG:statistics:get_stat_name: stat with name 0x7f2a934d5fc0 still not found
DBG
Thanks Liviu. I will try it
On Wed, 16 Sep 2020, 7:31 pm Liviu Chircu, wrote:
> On 15.09.2020 16:31, sagar malam wrote:
> > I want to use UAC REGISTRANT module to register with remote registrar.
> > Does it support it ?
> > https://opensips.org/html/docs/modules/2.3.x/uac_registrant.html
>
> Hey
And now that I know where to look .. t_check_status("403") in the
failure_route is an option too.
Thanks again.
On Wed, 2020-09-16 at 13:57 +, Ben Newlin wrote:
> John,
>
> The status of the response is exposed in several places, depending on
> your configuration. It can be accessed vis $rs [
Hi Ben,
Thank you. I can see the 401 and 403 responses in the failure route
with $T_reply_code
I really appreciate you taking the time to respond, it's helped me out.
Cheers,John
On Wed, 2020-09-16 at 13:57 +, Ben Newlin wrote:
> John,
>
> The status of the response is exposed in several plac
On 15.09.2020 16:31, sagar malam wrote:
I want to use UAC REGISTRANT module to register with remote registrar.
Does it support it ?
https://opensips.org/html/docs/modules/2.3.x/uac_registrant.html
Hey, Sagar!
I don't see why not! The transport layer is decoupled from all modules,
so even if
John,
The status of the response is exposed in several places, depending on your
configuration. It can be accessed vis $rs [1], but since failure_route is
processing the request you will need to specify the reply context [2], so
$(rs). But if you are using the TM module then you can just use
$
I have tried using t_on_failure + failure_route but every registration
ends up in the failure_route branch regardless of whether the
authentication was successful or not.
Does anyone know how I can capture the response returned from the main
registrar please to know in script whether the register
On 20.08.2020 19:04, HS wrote:
First time poster here, so apologies if something is incorrect.
Welcome! <3
http://www.powerpbx.org/content/opensips-v30-debian-v10-mariadb-apache-v1
Awesome guide, thanks for sharing! And kudos to the PowerPBX developers
for taking the time to write and maint
On 16.09.2020 10:15, John Matich - Siptalk wrote:
But there isn't anywhere that I can find to read a failed
authentication.
Hi, John!
That is a SIP transaction handling, problem. To solve it, make sure to
read about t_on_failure() [1] and failure_route [2]. Once you hit the
failure_route,
Hi , yes I got that latter and that works for me .
Now I am wandring how I will ignore port for some perticular gateway but
not all gateway .
is_from_gw(3, "n") {
-- do look up ---
}
This says it will ignore ports of all the gateway . I want to allow only
one gtaeway ignoring the port by le
How do I capture the response of a failed registration that has been
passed through to the main registrar and failed to authenticate?
My code is:
if (is_method("REGISTER")) {
mid_registrar_save("location");
switch ($retcode) {
case 1:
xlog("L_INFO", "forwar
Hi Sasmita,
isn’t the ‘n’ option of the function what you need?
https://opensips.org/docs/modules/2.4.x/drouting.html#func_is_from_gw
---
BR, Alexey
http://alexeyka.zantsev.com/
___
Users mailing list
Us
13 matches
Mail list logo
