[SR-Users] DMQ - Failed to get domain

[Daniel W. Graham]

Receiving the following message on the node receiving usr_loc via DMQ, for each 
location received:

DEBUG: dmq [worker.c:87]: worker_loop(): dmq_worker [0 54958] lock acquired
DEBUG: dmq_usrloc [usrloc_sync.c:460]: usrloc_dmq_handle_msg(): dmq message 
received from sip:usrloc@x.x.x.x
DEBUG: dmq_usrloc [usrloc_sync.c:405]: usrloc_dmq_execute_action(): Received 
DMQ_UPDATE. Update contact info...
ERROR: dmq_usrloc [usrloc_sync.c:70]: add_contact(): Failed to get domain

Any input is appreciated.

Thanks,
-dan
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] null $au

[Alex Balashov]

Just grab it right before the consume_credentials() block, after all the 
challenge stuff. 

--
Sent from mobile. Apologies for brevity and errors. 

-Original Message-
From: David Villasmil 
To: "Kamailio (SER) - Users Mailing List" 
Sent: Wed, 05 Sep 2018 6:27 PM
Subject: [SR-Users] null $au

Hello,

in the block:

if (is_method("REGISTER") || from_uri==myself) {
# authenticate requests
if (!auth_check("$fd", "subscriber", "1")) {
auth_challenge("$fd", "0");
exit;
}
# user authenticated - remove auth header
if(!is_method("REGISTER|PUBLISH"))
consume_credentials();
}

I'm trying to print out $au, but it's coming up NULL many times, i don't
get why this is. If i remember correctly, the script goes through this
block twice, once when we get the REGISTER with no credentials, and once
when the REGISTER comes with credentials after the challenge... is this
correct?

i need to know how to catch $au when the authentication is successful...

help?

Thanks!


David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
ᐧ

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] null $au

[David Villasmil]

Hello,

in the block:

if (is_method("REGISTER") || from_uri==myself) {
# authenticate requests
if (!auth_check("$fd", "subscriber", "1")) {
auth_challenge("$fd", "0");
exit;
}
# user authenticated - remove auth header
if(!is_method("REGISTER|PUBLISH"))
consume_credentials();
}

I'm trying to print out $au, but it's coming up NULL many times, i don't
get why this is. If i remember correctly, the script goes through this
block twice, once when we get the REGISTER with no credentials, and once
when the REGISTER comes with credentials after the challenge... is this
correct?

i need to know how to catch $au when the authentication is successful...

help?

Thanks!


David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
ᐧ
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Via header line missing

[Henning Westerholt]

Am Mittwoch, 5. September 2018, 17:43:34 CEST schrieb Karlheinz Knapp:
> we want to use kamailio as a IPv6 to IPv4 proxy.
> IPv4 to IPv4 bridging with NAT works.
> 
> If we come from an IPv6 address, the registration packet is send via IPv4
> to the provider.
> He answers with 401 Unauthorized and one Via line in the header.
> On the IPv6 side was no Via line in the packet.

Hello Karlheinz,

so I think you are using the 3.x tutorial from:

https://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6

This is indeed a bit old, but should mostly apply to today versions.

Have you added the IPv6 address to the listen statement in your cfg?
 
> So I tried to add one line by hand using an onreply_route and append_hf(),
> msg_apply_changes()
> To my suprise, this line does never appear, but the original Via line is
> now in the packet !!!
> If I add now additional Via header lines, they appear in the packet too.

You should not need to manually add a Via header to a message, Kamailio should 
take care of this if its properly setup.

Can you post a bit more details about the SIP message that you see on the net?

> This looks realy like a bug to me.
> 
> A solution is needed, because the phone does not respond to the 401 with
> user and password.
> It starts a new registration instead.
> 
> Maybe I can fix it with my additional Via linem but I need the original
> branch ID (I think)
> How can I get this?
> 
> Btw. we have this behaviour with 4.4.2 and 5.1.5
> 
> If I get no answer during the next 12 hours I'll try 3.3.7

My suggestion is to not use 3.x anymore especially in a new setup, even 4.x is 
out of maintenance and contain know security issues. It will also not get you 
a faster answer an a free support list. ;-)

Best regards,

Henning

-- 
Henning Westerholt
https://skalatan.de/blog/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] TOPOH module im REGISTER method.

[Henning Westerholt]

Am Dienstag, 4. September 2018, 11:37:43 CEST schrieb Mojtaba:
> I am used topoh module in kamailio, Why this module does not work (No
> change ) in Register request Method?
> I need to change UA' ip address in Via header in Register request
> before forwarded to my network? Does the topoh module used in this
> situation?
> I have not this issue in INVITE request, I just have this issue in
> Register request.

Hello Mojtaba,

an use case for the topoh module is the topology hiding of forwarded messages 
(in most cases from INVITE transactions) to your downstream customers or 
provider.

Therefore this module will skip REGISTER (and also PUBLISH) messages.

Why you need to hide the topology in REGISTER messages?

Best regards,

Henning

-- 
Henning Westerholt
https://skalatan.de/blog/

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] dispatcher local socket

[Евгений Голей]

Hello!

Kamilio version 5.1.0

Please tell me why the module dispatcher does not correctly determine the 
availability of destination gateways.

The scheme is as follows:

Kamailio (udp:XX.XX.XX.XX:5060) - Provider_1 -> (sip:aa.bb.cc.dd:5060) 
Dest GW
Kamailio (udp:YY.YY.YY.YY:5060) --- Provider_2 -/

In table dispatcher:

setid  |    destination    | flags |  priority |       attrs
   17   |  sip:aa.bb.cc.dd:5060  |   8 |   50   |   
socket=udp:XX.XX.XX.XX:5060
   17   |  sip:aa.bb.cc.dd:5060  |   8 |   40   |   
socket=udp:YY.YY.YY.YY:5060

That is, our server controls the availability of the remote gateway through two 
local sockets, in order to switch to the backup if it is not available through 
the primary Internet provider.

But as I understand at the moment when determining the availability of a remote 
gateway, the outgoing socket does not play any role, that is, if the remote 
gateway is not accessible through the secondary operator (priority is less than 
the primary one), only the one that has priority above is always inactive.

Are there any solutions to this problem?

BR. Evgeniy
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio with evapi crashing on high volume

[Jayesh Nambiar]

Hi Daniel,
Have got these core dumps. Let me know if I should be doing a bt full. I'll
pastebin and send. Thanks,

Core was generated by `/usr/local/kamailio/sbin/kamailio -P
/var/run/siptrunk.pid -f /usr/local/carrie'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00505d30 in sip_msg_shm_clone (org_msg=0x7f6ab0d9f618,
sip_msg_len=0x7ffdddb2e8bc, clone_lumps=1) at core/sip_msg_clone.c:491
491 LUMP_LIST_LEN(len, org_msg->add_rm);
(gdb) bt
#0  0x00505d30 in sip_msg_shm_clone (org_msg=0x7f6ab0d9f618,
sip_msg_len=0x7ffdddb2e8bc, clone_lumps=1) at core/sip_msg_clone.c:491
#1  0x7f6af0bdf68d in fake_req (shmem_msg=0x7f6ab0d9f618,
extra_flags=0, uac=0x7f6ab1738980, len=0x7ffdddb2e8bc) at t_reply.c:854
#2  0x7f6af0c3aa27 in t_continue_helper (hash_index=58039,
label=413633661, rtact=0x7f6af10500f0, cbname=0x0, cbparam=0x0) at
t_suspend.c:293
#3  0x7f6af0c3eed4 in t_continue (hash_index=58039, label=413633661,
route=0x7f6af10500f0) at t_suspend.c:583
#4  0x7f6aae4dd010 in w_t_continue (msg=0x7ffdddb2fa60,
idx=0x7f6af1098e90 "8\306\t\361j\177", lbl=0x7f6af1098ff0
"\240\264\t\361j\177", rtn=0x7f6af1099150 "0\275\t\361j\177") at
tmx_mod.c:760
#5  0x0045b477 in do_action (h=0x7ffdddb2f850, a=0x7f6af109ab38,
msg=0x7ffdddb2fa60) at core/action.c:1085
#6  0x00467fd5 in run_actions (h=0x7ffdddb2f850, a=0x7f6af1096630,
msg=0x7ffdddb2fa60) at core/action.c:1565
#7  0x0045b234 in do_action (h=0x7ffdddb2f850, a=0x7f6af10a0f80,
msg=0x7ffdddb2fa60) at core/action.c:1058
#8  0x00467fd5 in run_actions (h=0x7ffdddb2f850, a=0x7f6af10a0f80,
msg=0x7ffdddb2fa60) at core/action.c:1565
#9  0x00468797 in run_top_route (a=0x7f6af10a0f80,
msg=0x7ffdddb2fa60, c=0x0) at core/action.c:1654
#10 0x7f6aabe79370 in evapi_run_cfg_route (evenv=0x7ffdddb30250, rt=3,
rtname=0x7f6aac08cb18 <_evapi_rts+56>) at evapi_dispatch.c:161
#11 0x7f6aabe7f271 in evapi_recv_client (loop=0x7f6aabe698e0,
watcher=0x27af5e0, revents=1) at evapi_dispatch.c:467
#12 0x7f6aabc5fd73 in ev_invoke_pending () from
/usr/lib/x86_64-linux-gnu/libev.so.4
#13 0x7f6aabc633de in ev_run () from
/usr/lib/x86_64-linux-gnu/libev.so.4
#14 0x7f6aabe7867c in ev_loop (loop=0x7f6aabe698e0, flags=0) at
/usr/include/ev.h:835
#15 0x7f6aabe83fc6 in evapi_run_dispatcher (laddr=0x7f6af0f72300
"127.0.0.1", lport=8060) at evapi_dispatch.c:705
#16 0x7f6aabe6e262 in child_init (rank=0) at evapi_mod.c:213
#17 0x00542cad in init_mod_child (m=0x7f6af0f71b70, rank=0) at
core/sr_module.c:943
#18 0x00542971 in init_mod_child (m=0x7f6af0f72968, rank=0) at
core/sr_module.c:939
#19 0x00542971 in init_mod_child (m=0x7f6af0f73d38, rank=0) at
core/sr_module.c:939
#20 0x00542971 in init_mod_child (m=0x7f6af0f74670, rank=0) at
core/sr_module.c:939
#21 0x00542971 in init_mod_child (m=0x7f6af0f76708, rank=0) at
core/sr_module.c:939
#22 0x00542971 in init_mod_child (m=0x7f6af0f76c08, rank=0) at
core/sr_module.c:939
#23 0x00542971 in init_mod_child (m=0x7f6af0f770d0, rank=0) at
core/sr_module.c:939
#24 0x00542971 in init_mod_child (m=0x7f6af0f77cf0, rank=0) at
core/sr_module.c:939
#25 0x00542971 in init_mod_child (m=0x7f6af0f78808, rank=0) at
core/sr_module.c:939
#26 0x00542971 in init_mod_child (m=0x7f6af0f78bd8, rank=0) at
core/sr_module.c:939
#27 0x00542971 in init_mod_child (m=0x7f6af0f794c8, rank=0) at
core/sr_module.c:939
#28 0x00542971 in init_mod_child (m=0x7f6af0f79920, rank=0) at
core/sr_module.c:939
#29 0x00542971 in init_mod_child (m=0x7f6af0f7a330, rank=0) at
core/sr_module.c:939
#30 0x00542971 in init_mod_child (m=0x7f6af0f7afd0, rank=0) at
core/sr_module.c:939
#31 0x00542971 in init_mod_child (m=0x7f6af0f7bc80, rank=0) at
core/sr_module.c:939
#32 0x0054303d in init_child (rank=0) at core/sr_module.c:970
#33 0x00425399 in main_loop () at main.c:1701
#34 0x0042bd5c in main (argc=13, argv=0x7ffdddb31088) at main.c:2638

And this:
[New LWP 15804]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/kamailio/sbin/kamailio -P
/var/run/siptrunk.pid -f /usr/local/carrie'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f6af0b90b70 in free_cell_helper (dead_cell=0x7f6ab0a6baa8,
silent=0, fname=0x7f6af0c8f630 "timer.c", fline=654) at h_table.c:230
230 foo = tt->next;
(gdb) bt
#0  0x7f6af0b90b70 in free_cell_helper (dead_cell=0x7f6ab0a6baa8,
silent=0, fname=0x7f6af0c8f630 "timer.c", fline=654) at h_table.c:230
#1  0x7f6af0c24409 in wait_handler (ti=932640643,
wait_tl=0x7f6ab0a6bb28, data=0x7f6ab0a6baa8) at timer.c:654
#2  0x004bb445 in timer_list_expire (t=932640643, h=0x7f6ab03ad158,
slow_l=0x7f6ab03ae480, slow_mark=271) at core/timer.c:874
#3  0x004bb8ab in timer_handler () at core/timer.c:939
#4  

[SR-Users] Via header line missing

[Karlheinz Knapp]

Hi,

we want to use kamailio as a IPv6 to IPv4 proxy.
IPv4 to IPv4 bridging with NAT works.

If we come from an IPv6 address, the registration packet is send via IPv4
to the provider.
He answers with 401 Unauthorized and one Via line in the header.
On the IPv6 side was no Via line in the packet.

So I tried to add one line by hand using an onreply_route and append_hf(),
msg_apply_changes()
To my suprise, this line does never appear, but the original Via line is
now in the packet !!!
If I add now additional Via header lines, they appear in the packet too.

This looks realy like a bug to me.

A solution is needed, because the phone does not respond to the 401 with
user and password.
It starts a new registration instead.

Maybe I can fix it with my additional Via linem but I need the original
branch ID (I think)
How can I get this?

Btw. we have this behaviour with 4.4.2 and 5.1.5

If I get no answer during the next 12 hours I'll try 3.3.7

Best regards
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Simultaneous usage of t_on_reply() and t_on_failure()

[Володимир Іванець]

There is only one branch_route - MANAGE_BRANCH. Same as in default Kamailio
configuration file.

Thank you.

2018-09-05 17:31 GMT+03:00 Vitalii Aleksandrov :

> How many branches do you have? Failure route is called for the whole
> transaction failure and not for every individual failed branch.
>
> On 05.09.18 15:03, Володимир Іванець wrote:
>
> Hello everyone,
>
> I wanted to ask those who know if Kamailio's behavior I'm facing is
> expected or I should make some improvements to the configuration. Kamailio
> version is 5.1.0.
>
> I have a route where RTPEngine parameters are being collected and
> *rtpengine_offer()* is called. After that
> *t_on_reply("REPLY_SIP_TO_SIP");* followed by the
> *t_on_failure("FAILURE_SIP_TO_SIP");* are used. The idea is to process
> all responces except 415 or 488 from UAC as usual in
> *onreply_route[REPLY_SIP_TO_SIP]* and use
> *failure_route[FAILURE_SIP_TO_SIP]* to update SDP with *rtpengine_offer()* if
> necessary.
>
> *onreply_route[REPLY_SIP_TO_SIP]* just goes to *exit;* if *$rs* equals  415
> or 488. This works fine with Htek phone which sends 100, 180 and then 488.
> But I can not see  *failure_route[FAILURE_SIP_TO_SIP]* execution for
> calls to Zoiper which replies with 100 and immediately 415.
>
> t_on_failure(failure_route) documentation says: "Sets failure routing
> block, to which control is passed after a transaction completed with a
> negative result but before sending a final reply." and to be honest I don't
> really understand how lacking of responce prevents  failure_route from
> executing.
>
> Thanks a lot!
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Simultaneous usage of t_on_reply() and t_on_failure()

[Vitalii Aleksandrov]

How many branches do you have? Failure route is called for the whole 
transaction failure and not for every individual failed branch.



On 05.09.18 15:03, Володимир Іванець wrote:

Hello everyone,

I wanted to ask those who know if Kamailio's behavior I'm facing is 
expected or I should make some improvements to the configuration. 
Kamailio version is 5.1.0.


I have a route where RTPEngine parameters are being collected and 
/rtpengine_offer()/ is called. After that 
/t_on_reply("REPLY_SIP_TO_SIP");/ followed by the 
/t_on_failure("FAILURE_SIP_TO_SIP");/ are used. The idea is to process 
all responces except 415 or 488 from UAC as usual in 
/onreply_route[REPLY_SIP_TO_SIP]/ and use 
/failure_route[FAILURE_SIP_TO_SIP]/ to update SDP with 
/rtpengine_offer()/ if necessary.


/onreply_route[REPLY_SIP_TO_SIP]/ just goes to /exit;/ if /$rs/ equals 
415 or 488. This works fine with Htek phone which sends 100, 180 and 
then 488. But I can not see 
/failure_route[FAILURE_SIP_TO_SIP]/ execution for calls to Zoiper 
which replies with 100 and immediately 415.


t_on_failure(failure_route) documentation says: "Sets failure routing 
block, to which control is passed after a transaction completed with a 
negative result but before sending a final reply." and to be honest I 
don't really understand how lacking of responce prevents failure_route 
from executing.


Thanks a lot!


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] From URI attribute for dispatcher target

[Giacomo Vacca]

Hi all,
I was looking for a solution to set a dedicated From URI in OPTIONS
requests to a specific dispatcher target.

ds_ping_from (
https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_ping_from)
applies globally, why I needed the granularity of a single target.

With these changes to the dispatcher module I get what I need:
https://github.com/kamailio/kamailio/commit/3f9c38be11416f7abe5c4448088ba66d2d3e6aad

I can just add an attribute to the others, e.g. instead of

*1 sip:127.0.0.1:7070  0 1*

something like:

*1 sip:127.0.0.1:7070  0 1 ping_from=sip.custom.com
*

When the ping_from attribute is not specified, the general ds_ping_from
applies and is used.

This would save me from a solution like intercepting the outgoing OPTIONS
and manipulating the From header.

Does this approach make sense? Are there other ways already available to
achieve this?

Thanks,
Giacomo
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] SCA: sca_call_info_bye_handler: no in-use callee appearance for BYE

[Asgaroth]

Hi All,

I've just started playing with the SCA module and am encountering an 
issue whereby SCA cannot seem to find an in-use appearance for the BYE 
message.


From my limited understanding of SCA, the module, in this case, appears 
to be trying to track the state of the call using callid as there are no 
call-info headers in the signalling for it to extract and use.


I call sca_call_info_update() for initial invite, 100 response, 180 
response, 200 response and again for the terminating bye.


When I answer the call, at the 200 ok for the initial invite, I can see 
sca sending a notify to the subscribed devices indicating appearance 
state being active. I can verify this with kamcmd sca.all_appearances.


However, when I hang up the call, when sca_call_info_update() is fired 
for the bye message it fails with the following error message:


sca [sca_call_info.c:1587]: sca_call_info_bye_handler(): 
sca_call_info_bye_handler: no in-use callee appearance for BYE  
from , call-ID 7989c223-2ba4-1237-1888-20474786734e


I cannot seem to track down where this is failing for me, or where I may 
be missing something in my configuration. sca.all_appearances does 
appear to have the entry mentioned in the failure message, there must be 
something I'm missing somewhere.


Is there anyone out there who is using the sca module and may have a 
moment to assist with this issue.


I have a pcap trace that I can send privately.

Any assistance would be greatly appreciated.

Thanks

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Simultaneous usage of t_on_reply() and t_on_failure()

[Володимир Іванець]

Hello everyone,

I wanted to ask those who know if Kamailio's behavior I'm facing is
expected or I should make some improvements to the configuration. Kamailio
version is 5.1.0.

I have a route where RTPEngine parameters are being collected and
*rtpengine_offer()* is called. After that *t_on_reply("REPLY_SIP_TO_SIP");*
followed by the *t_on_failure("FAILURE_SIP_TO_SIP");* are used. The idea is
to process all responces except 415 or 488 from UAC as usual in
*onreply_route[REPLY_SIP_TO_SIP]* and use
*failure_route[FAILURE_SIP_TO_SIP]* to update SDP with *rtpengine_offer()* if
necessary.

*onreply_route[REPLY_SIP_TO_SIP]* just goes to *exit;* if *$rs* equals  415
or 488. This works fine with Htek phone which sends 100, 180 and then 488.
But I can not see  *failure_route[FAILURE_SIP_TO_SIP]* execution for calls
to Zoiper which replies with 100 and immediately 415.

t_on_failure(failure_route) documentation says: "Sets failure routing
block, to which control is passed after a transaction completed with a
negative result but before sending a final reply." and to be honest I don't
really understand how lacking of responce prevents  failure_route from
executing.

Thanks a lot!
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] kamailio with evapi crashing on high volume

[Daniel-Constantin Mierla]

Hello,

the backtrace doesn't show any hint about kamailio, only from closelog() up.

It may be the core generated by shutdown procedure, have you enabled one
core file per pid/process? If not, do it and reproduce the issue again,
you may get two core files, one being the runtime issue and the other
one from shutdown procedure, which likely is an effect of the other one.
The one from the runtime is more relevant.

Cheers,
Daniel


On 05.09.18 10:09, Jayesh Nambiar wrote:
> Hello,
> I'm using kamailio 5.1.5 with evapi. I have a node.js connecting with
> kamailio evapi to which I send events and also consume events based on
> which I do the routing. I have 8 evapi workers defined in the config. 
> The problem is that kamailio randomly crashes on high load. I'm
> assuming that it is related to the evapi module as rest of the config
> is pretty straight forward. I could get a core file and here's the
> core dump:
> [New LWP 14042]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
> Core was generated by `/usr/local/kamailio/sbin/kamailio -P
> /var/run/siptrunk.pid -f /usr/local/carrie’.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x7f9995283428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> 54    ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> (gdb) bt
> #0  0x7f9995283428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> #1  0x7f999528502a in __GI_abort () at abort.c:89
> #2  0x0041a029 in sig_alarm_abort (signo=14) at main.c:646
> #3  
> #4  0x7f999534f497 in __libc_cleanup_routine (f=)
> at ../sysdeps/nptl/libc-lockP.h:291
> #5  closelog () at ../misc/syslog.c:415
> #6  0x in ?? ()
>
> Any help in this regards is would allow me to identify the reason of
> the crash. Thanks for the support.
>
> - Jayesh
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

[Daniel-Constantin Mierla]

There is the dlg.terminate_dlg rpc command that requires callid,
from-tag and to-tag as parameters:

  *
https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate_dlg

So it expects something like:



dlg.terminate_dlg

_CALLID_VALUE__
_FROM_TAG_VALUE__
_TO_TAG_VALUE__



I planned to make the from-tag and to-tag optional for quite some time,
but didn't get the time for it yet.

Cheers,
Daniel

On 05.09.18 08:52, Richard Fuchs wrote:
> Yup that's exactly right.
>
> It would be fairly simple to implement an additional XMLRPC format if
> there's a particular one that's more friendly towards Kamailio.
>
> Cheers
>
> On 2018-09-05 02:42, Daniel-Constantin Mierla wrote:
>>
>> Looking quickly at the readme of rtpengine application and digging a
>> bit with google, it is something like rtpengine has to be started with
>>
>> -b http(s)://myrpcserver.ip/path -x 1
>>
>> and then the xmlrpc request is going to be sent to that url, having a
>> format like:
>>
>> 
>> 
>> teardown
>> 
>> _CALLID_VALUE__
>> 
>> 
>>
>> Is it right? If yes, then I can try to make a sample config that
>> could handle it using xmlops, xhttp and jsonrpcs modules.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 05.09.18 08:24, Richard Fuchs wrote:
>>> It does an XMLRPC callback. Currently there's two formats for it,
>>> one is a sems sbc teardown request (using the from-tag), the other
>>> is a generic "teardown" command using the call ID.
>>>
>>> Cheers
>>>
>>> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:

 Hello,

 what do you get from rtpengine on rtp timeout? An RPC call back or
 an http request?

 Cheers,
 Daniel


 On 04.09.18 12:48, Igor Olhovskiy wrote:
> Hi all!
>
> Is there any way to end dialog in Kamailio on RTP Timeout event on
> RTPEngine?
>
> Or only look at logs/redis database with external tool?
>
> Regards, Igor
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

 -- 
 Daniel-Constantin Mierla -- www.asipto.com
 www.twitter.com/miconda -- www.linkedin.com/in/miconda
 Kamailio World Conference -- www.kamailioworld.com
 Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com


 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> -- 
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio World Conference -- www.kamailioworld.com
>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] kamailio with evapi crashing on high volume

[Jayesh Nambiar]

Hello,
I'm using kamailio 5.1.5 with evapi. I have a node.js connecting with
kamailio evapi to which I send events and also consume events based on
which I do the routing. I have 8 evapi workers defined in the config.
The problem is that kamailio randomly crashes on high load. I'm assuming
that it is related to the evapi module as rest of the config is pretty
straight forward. I could get a core file and here's the core dump:
[New LWP 14042]
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
Core was generated by `/usr/local/kamailio/sbin/kamailio -P
/var/run/siptrunk.pid -f /usr/local/carrie’.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f9995283428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x7f9995283428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7f999528502a in __GI_abort () at abort.c:89
#2  0x0041a029 in sig_alarm_abort (signo=14) at main.c:646
#3  
#4  0x7f999534f497 in __libc_cleanup_routine (f=) at
../sysdeps/nptl/libc-lockP.h:291
#5  closelog () at ../misc/syslog.c:415
#6  0x in ?? ()

Any help in this regards is would allow me to identify the reason of the
crash. Thanks for the support.

- Jayesh
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] TOPOH module im REGISTER method.

[Mojtaba]

Hi all,
I try to used SEMS in this regards, But i have this issue.
https://lists.kamailio.org/pipermail/sr-users/2018-August/102753.html
Any updates?
Thanks
On Tue, Sep 4, 2018 at 2:07 PM Mojtaba  wrote:
>
> Hello,
> I am used topoh module in kamailio, Why this module does not work (No
> change ) in Register request Method?
> I need to change UA' ip address in Via header in Register request
> before forwarded to my network? Does the topoh module used in this
> situation?
> I have not this issue in INVITE request, I just have this issue in
> Register request.
> Thanks.
> With Regards.Mojtaba
>
> --
> --Mojtaba Esfandiari.S



--
--Mojtaba Esfandiari.S

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

[Richard Fuchs]

Yup that's exactly right.

It would be fairly simple to implement an additional XMLRPC format if 
there's a particular one that's more friendly towards Kamailio.


Cheers

On 2018-09-05 02:42, Daniel-Constantin Mierla wrote:


Looking quickly at the readme of rtpengine application and digging a 
bit with google, it is something like rtpengine has to be started with


-b http(s)://myrpcserver.ip/path -x 1

and then the xmlrpc request is going to be sent to that url, having a 
format like:




teardown

_CALLID_VALUE__



Is it right? If yes, then I can try to make a sample config that could 
handle it using xmlops, xhttp and jsonrpcs modules.


Cheers,
Daniel


On 05.09.18 08:24, Richard Fuchs wrote:
It does an XMLRPC callback. Currently there's two formats for it, one 
is a sems sbc teardown request (using the from-tag), the other is a 
generic "teardown" command using the call ID.


Cheers

On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:


Hello,

what do you get from rtpengine on rtp timeout? An RPC call back or 
an http request?


Cheers,
Daniel


On 04.09.18 12:48, Igor Olhovskiy wrote:

Hi all!

Is there any way to end dialog in Kamailio on RTP Timeout event on 
RTPEngine?


Or only look at logs/redis database with external tool?

Regards, Igor


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda  --www.linkedin.com/in/miconda
Kamailio World Conference --www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda  --www.linkedin.com/in/miconda
Kamailio World Conference --www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

[Daniel-Constantin Mierla]

Looking quickly at the readme of rtpengine application and digging a bit
with google, it is something like rtpengine has to be started with

-b http(s)://myrpcserver.ip/path -x 1

and then the xmlrpc request is going to be sent to that url, having a
format like:



teardown

_CALLID_VALUE__



Is it right? If yes, then I can try to make a sample config that could
handle it using xmlops, xhttp and jsonrpcs modules.

Cheers,
Daniel


On 05.09.18 08:24, Richard Fuchs wrote:
> It does an XMLRPC callback. Currently there's two formats for it, one
> is a sems sbc teardown request (using the from-tag), the other is a
> generic "teardown" command using the call ID.
>
> Cheers
>
> On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:
>>
>> Hello,
>>
>> what do you get from rtpengine on rtp timeout? An RPC call back or an
>> http request?
>>
>> Cheers,
>> Daniel
>>
>>
>> On 04.09.18 12:48, Igor Olhovskiy wrote:
>>> Hi all!
>>>
>>> Is there any way to end dialog in Kamailio on RTP Timeout event on
>>> RTPEngine?
>>>
>>> Or only look at logs/redis database with external tool?
>>>
>>> Regards, Igor
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> -- 
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio World Conference -- www.kamailioworld.com
>> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] dlg.end_dlg on RTP timeout

[Richard Fuchs]

It does an XMLRPC callback. Currently there's two formats for it, one is 
a sems sbc teardown request (using the from-tag), the other is a generic 
"teardown" command using the call ID.


Cheers

On 2018-09-04 07:52, Daniel-Constantin Mierla wrote:


Hello,

what do you get from rtpengine on rtp timeout? An RPC call back or an 
http request?


Cheers,
Daniel


On 04.09.18 12:48, Igor Olhovskiy wrote:

Hi all!

Is there any way to end dialog in Kamailio on RTP Timeout event on 
RTPEngine?


Or only look at logs/redis database with external tool?

Regards, Igor


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda  --www.linkedin.com/in/miconda
Kamailio World Conference --www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --www.asipto.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users