sr-users January 2019

sr-users@lists.kamailio.org

84 participants
104 discussions

MWI notification through pua.publish
by willy 23 Jan '19

23 Jan '19

Hello. Have anyone tried to use pua.publish to send MWI notification? Can it work at all? I'm sending request through jsonrpc server, but it is not dispatched by handle_publish. Thank you, Kirill

6 9

Maximum Number of Probed Gateways
by Duarte Rocha 23 Jan '19

23 Jan '19

Greetings, Is there a limitation to the number of Gateways probed by Dispatcher? I have several gateways configured to be probed, but the OPTIONS is only sent to the first 16? Is there a configuration regarding this? Thanks in advance, Duarte Rocha

2 2

Kamailio v5.1.6 crashes with rtpengine restarts
by Yufei Tao 23 Jan '19

23 Jan '19

Hi, I have been testing one Kamailio v5.1.6 instance with one rtpengine instance, using sipp playing media files at 40 cps (-r 40) with up to 1600 concurrent calls. During the load tests if rtpengine is pkill'ed/restarted a few times Kamailio would crash. It is quite repeatable and every time the backtrace from gdb points to the same place as shown below. However the same tests on Kamailio v5.0.7 with the same cfg files and the same rtpengine instance did not cause any crash. Here’s what I got from gdb backtrace for v5.1.6 using a dbg build: 2 core dump files: 1. UDP receiver processes 14483 {{{ [New LWP 14483] Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fadfa824d8e in t_should_relay_response (Trans=0x7fadf4207730, new_code=200, branch=0, should_store=0x7ffd5038fce4, should_relay=0x7ffd5038fce0, cancel_data=0x7ffd5038fed0, reply=0x7fadfb545210) at t_reply.c:1282 1282 t_reply.c: No such file or directory. (gdb) bt #0 0x00007fadfa824d8e in t_should_relay_response (Trans=0x7fadf4207730, new_code=200, branch=0, should_store=0x7ffd5038fce4, should_relay=0x7ffd5038fce0, cancel_data=0x7ffd5038fed0, reply=0x7fadfb545210) at t_reply.c:1282 #1 0x00007fadfa829577 in relay_reply (t=0x7fadf4207730, p_msg=0x7fadfb545210, branch=0, msg_status=200, cancel_data=0x7ffd5038fed0, do_put_on_wait=1) at t_reply.c:1786 #2 0x00007fadfa82f54c in reply_received (p_msg=0x7fadfb545210) at t_reply.c:2537 #3 0x000000000054624b in do_forward_reply (msg=0x7fadfb545210, mode=0) at core/forward.c:747 #4 0x0000000000547e4c in forward_reply (msg=0x7fadfb545210) at core/forward.c:852 #5 0x000000000058e186 in receive_msg ( buf=0xa595a0 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 192.168.70.102;branch=z9hG4bKa042.afac8eb973f1dfad7a549af0ab1a8ccc.0, SIP/2.0/UDP 192.168.60.80:5060;branch=z9hG4bK-3750-978-0\r\nFrom: sipp < sip:Customer68@192.168.60.8"..., len=888, rcv_info=0x7ffd50390480) at core/receive.c:364 #6 0x00000000004af6b1 in udp_rcv_loop () at core/udp_server.c:554 #7 0x00000000004246ac in main_loop () at main.c:1619 #8 0x000000000042bd5c in main (argc=13, argv=0x7ffd50390b38) at main.c:2638 }}} 2. Main process 14468 {{{ [New LWP 14468] Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fadfbc77428 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 0x00007fadfbc77428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007fadfbc7902a in __GI_abort () at abort.c:89 #2 0x000000000041a029 in sig_alarm_abort (signo=14) at main.c:646 #3 <signal handler called> #4 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:37 #5 0x00007fadf354e67d in futex_get (lock=0x7fadf3e94e50) at ../../core/parser/../mem/../futexlock.h:121 #6 0x00007fadf3561113 in mod_destroy () at rtpengine.c:1810 #7 0x000000000055132b in destroy_modules () at core/sr_module.c:832 #8 0x0000000000418c9f in cleanup (show_status=1) at main.c:521 #9 0x000000000041a313 in shutdown_children (sig=15, show_status=1) at main.c:663 #10 0x000000000041cfa5 in handle_sigs () at main.c:768 #11 0x0000000000425fb5 in main_loop () at main.c:1752 #12 0x000000000042bd5c in main (argc=13, argv=0x7ffd50390b38) at main.c:2638 }}} The parameters for rtpengine: {{{ loadmodule "rtpengine.so" modparam("rtpengine", "db_url", "text:///usr/share/kamailio/dbtext/kamailio") modparam("rtpengine", "hash_table_size", 4) modparam("rtpengine", "setid_default", 1) modparam("rtpengine", "rtpengine_disable_tout", 20) modparam("rtpengine", "rtpengine_retr", 1) modparam("rtpengine", "setid_avp", "$avp(setid)") modparam("rtpengine", "rtp_inst_pvar", "$avp(rtpInstance)") modparam("rtpengine", "rtpengine_tout_ms", 1000) modparam("rtpengine", "read_sdp_pv", "$var(sdpToRtpengine)") modparam("rtpengine", "write_sdp_pv", "$var(sdpFromRtpengine)") }}} I'm using a simplified kamailio.cfg from installation, and here are calls to rtpengine: {{{ ... route[INVITE] { $var(sdpToRtpengine) = $rb; $var(ret) = rtpengine_manage("direction=dirty direction=clean ICE=remove"); xlog("L_INFO", "$ci INVITE: rtpengine chosen: $avp(rtpInstance)"); remove_body(); replace_body(".*", $var(sdpFromRtpengine)); t_on_reply("RESPONSE"); route(RELAY); } onreply_route[RESPONSE] { $var(sdpToRtpengine) = $rb; $var(ret) = rtpengine_manage("direction=clean direction=dirty ICE=remove"); remove_body(); replace_body(".*", $var(sdpFromRtpengine)); xlog("L_INFO", "$ci RESPONSE: $rm - $rs $rr, cseq=$cs, by [$hdr(Server)], from $si:$sp"); } ... }}} When rtpengine is down for a couple of seconds, there were a lot of SIP retransmissions and timeouts. Doing a netstat and I can see Kamailio’s receive buffer is quite filled up. Please let me know if more information is needed. Thank you! Cheers, Yufei

2 3

Additional Param Check in ConsumeCredential Auth
by Prabhat Kumar 22 Jan '19

22 Jan '19

Hi, I want to check additional param in Auth module. For. ex., other than username and secret , i want to validate user by its email address. How can i do that? Regards, Prabhat Kumar

4 8

How to send NOTIFY to UA
by CuiGang 22 Jan '19

22 Jan '19

Hello, Does any one know, how to send a NOTIFY message to a special UA? Why I need to do this? I’m using kamailio integration with Yealink IP Phone. Yealink IP Phone can perform some specified action immediately by accepting a SIP NOTIFY message with the “Event: ACTION-URI” header. I want to use RPC or HTTP or NSQ or some other interface trigger kamailio ROUTE make a NOTIFY message and send it to a special Yealink IP Phone. Thanks! Regards, CuiGang cuigang0120(a)aliyun.com

2 2

Empty presence event NOTIFY
by EDUARDO PASCUAL GALLEGO 22 Jan '19

22 Jan '19

Hello: I am testing the Kamailio Presence Server. I can see when the presence of an user agent expires then the server sends an empty NOTIFY without XML document. Also, when the server receives a SUBSCRIBE it sends a NOTIFY with XML if the UA is present but it sends an empty NOTIFY when the UA is not present. However, if the presence server receive a PUBLISH with Expires header equals cero then it sends a NOTIFY with XML document. I do not understant why it sends empty NOTIFY messages. Especially if the user agent is not present. I tested 4.4.7 version and I can see that it is the best version, because I tested 5.1.6 and 5.2.0 versions and I could see that they sends empty NOTIFY messages even the user agent is present. Then I am using 4.4.7 version, an I am considering as no present when a NOTIFY message is empty. But I think it is not RFC3856 compliant. Kamailio presence server es configured like that: #!ifdef WITH_PRESENCE # ----- presence params ----- modparam("presence", "db_url", DBURL) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) #!endif Can anyone help me? Thank you very much in advance. *Eduardo Pascual Gallego* *Ingeniero de Desarrollo / Development Engineer.* T. +34 91 807 39 99 · eduardo.pascual(a)nucleocc.com <https://www.nucleocc.com/> *Núcleo HQ* C/Vía de los Poblados, 7 28033 Madrid (Spain) <https://www.google.es/maps/place/DF+N%C3%BAcleo/@40.4747861,-3.6352894,17z/…> *Núcleo USA* 100 Crescent Dr, STE.700 75201 Dallas, Texas (USA) <https://www.google.es/maps/place/100+Crescent+Ct,+Dallas,+TX+75201,+EE.+UU.…> *www.nucleocc.com* <https://www.nucleocc.com/> Este correo electrónico y cualquier fichero adjunto al mismo contienen información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. En el caso de haber recibido este correo electrónico por error, le indicamos que no le está permitido por ley la lectura, copia y uso del mismo . En tal caso, le rogamos notifique lo antes posible esta circunstancia mediante reenvío a la dirección electrónica del remitente y destruya el mensaje. Antes de imprimir este correo, piense en su responsabilidad y compromiso con el medio ambiente. -- Advertencia | Este mensaje está destinado únicamente a su destinatario y puede contener información CONFIDENCIAL y/o protegida por secreto profesional cuya revelación está prohibida por la ley. Si usted no es el destinatario a quien va dirigido le informamos que la lectura, la distribución, el copiado o la revelación de este mensaje están prohibidos por la ley. Si ha recibido este mensaje por error le solicitamos que nos notifique por e-mail su recepción equivocada y que borre este mensaje sin conservar copia, al tiempo que le pedimos disculpas por las molestias que le haya ocasionado. El servicio de e-mail por internet no garantiza ni la confidencialidad ni la integridad o la recepción de los mensajes por lo que nuestra Firma no asume ninguna responsabilidad portales circunstancias. De conformidad con lo previsto en el REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO de 27 de abril de 2016, a continuación facilitamos la información básica en relación con la protección de los datos personales que nos sean suministrados: Responsable: NUCLEO DE COMUNICACIONES Y CONTROL, SLU Finalidad: Cumplimiento de las relaciones jurídicas y obligaciones legales asociadas. Legitimación: Ejecución contractual y cumplimiento de nuestras obligaciones. No se cederán o transferirán los datos personales a terceros, salvo siguiendo sus instrucciones o por obligación legal. Ejercicio de derechos de acceso, rectificación y supresión de los datos, así como el ejercicio de otros derechos, tal y como se explica en la información adicional. Puede consultar la información adicional y detallada en el siguiente enlace a nuestra política de privacidad y *Tratamiento de Datos Personales* <http://www.nucleocc.com/paginas_informativas/proteccin_de_datos_de_carcter_…>*.*

1 1

uri_param function
by Andrew Chen 21 Jan '19

21 Jan '19

Hi all, Question. I'm executing uri_param() function to look for our customized Request-URI parameters generated by our client. However, it keeps saying the param is not there even though my client logs shows the param was generated. Below is an example Request-URI from a test call I made: sips:<some long string>@sjomainkamavip50.fuzemeeting.com:443;FN= sjomainfn92.a.fuzemeeting.com;BR=sjomainfn91.a.fuzemeeting.com;AK=<some key>;transport=wss" And here is my line of code to check it: if(uri_param("AK") ||uri_param("ak")) { xlog("L_INFO", "[CSeq $cs] AK value detected"); } else { xlog("L_INFO", "[CSeq $cs] AK value not detected. Aborting call"); drop(); } Am I misusing this function somehow? I'm running 5.1.2. Thanks Regards, -- Andy Chen -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 4

Radius Accounting with Kamailio 5.1 (On-line Charging)
by Yazar Lwin 21 Jan '19

21 Jan '19

Hi All, I've Kamailio 5.1 running with Mysql as local DB. I've configured Siremis as well. I completed accounting configuration as per the instruction. Now I can see the accounting list, CDR list and as well as missed calls in Siremis But I can't integrate with free radius server to trigger the accounting, just like Diameter transaction in IMS. Kindly advise which doc I should check. I would like to enable Radius server as an online charging. Best regards Yazar

2 3

Dynamic UAC Registration
by Mack Hendricks 20 Jan '19

20 Jan '19

Hey All, So, I want to use the UAC module to handle Digest Auth to upstream carriers. But, I don’t know which carrier will be selected until another module (dRouting in this case) tells the logic which carrier to use. I can see in the logs that the uac_auth function can capture the Auth Realm. But, I need to access it from the Kamailio script so that I can lookup the credentials for that realm and then call uac_auth. I’ve tried getting the info from $ar, but that gives me the realm of the inbound request versus the realm of the upstream carrier. Also, I’ve tried using $T_rpl($ar), but that returns 0. Here’s my logic from the Kamailio file: if(t_check_status("401|407")) { $var(reply_realm) = $T_rpl($ar); $var(query)="select auth_username,auth_password from uacreg where realm='" + $var(reply_realm) + "'"; sql_xquery("cb","$var(query)","rb"); xlog("L_DEBUG","[MANAGE_FAILURE: Proxy Auth]: The query is $var(query) auth realm is $var(reply_realm) and the user name is $xavp(rb=>auth_username)"); $avp(auser) = $xavp(rb=>auth_username); $avp(apass) = $xavp(rb=>auth_password); uac_auth(); t_relay(); exit;` } A snippet of the log file is below: Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1616 a=63 n=assign Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1617 a=63 n=assign Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1618 a=24 n=uac_auth Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:409]: uac_auth(): picked reply is 0x7f900cb7eaf0, code 407 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:225]: get_autenticate_hdr(): looking for header "Proxy-Authenticate" Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:429]: uac_auth(): header found; body=<Digest realm="sip.flowroute.com", nonce="XERJMlxESAbDNCK3INmBfoET1GGxpcyr", qop="auth"> Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <realm>="sip.flowroute.com" state=2 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <nonce>="XERJMlxESAbDNCK3INmBfoET1GGxpcyr" state=3 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <qop>="auth" state=1 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:449]: uac_auth(): no credential for realm "sip.flowroute.com" Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1619 a=24 n=t_relay Thanks in advance for any help Mack Hendricks dSIPRouter

4 4

Kamailio Docker 5.2.1
by Grant Bagdasarian 20 Jan '19

20 Jan '19

Hello, I was wondering when the Kamailio Docker image will be updated to use 5.2.1 and be available through the Docker public repository ( https://hub.docker.com/r/kamailio/kamailio)? Thanks and regards, Grant

4 10

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2019