sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

Error while installing kamailio
by Prabhat Kumar 25 Jan '19

25 Jan '19

I am getting this error while installing kamailio LD (gcc) [U kamcmd] kamcmd /usr/bin/ld: cannot find -lncurses collect2: error: ld returned 1 exit status ../../src//Makefile.rules:191: recipe for target 'kamcmd' failed make[3]: *** [kamcmd] Error 1 ERROR: make --no-print-directory -C ../../../utils/kamcmd install-if-newer failed ../../Makefile.modules:145: recipe for target 'install-utils' failed make[2]: *** [install-utils] Error 1 Makefile:511: recipe for target 'install-modules' failed make[1]: *** [install-modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.1/kamailio/src' Makefile:36: recipe for target 'install' failed make: *** [install] Error 2

2 1

Kamailio Ignore Re-INVITE
by Alvaro Araos 25 Jan '19

25 Jan '19

Hi, When receive a Re-INVITE with new Media IP and PORT, kamailio keeps sending RTP to the old IP PORT. Seems kamailio not update info to the rtpproxy. Saludos, ALVARO ARAOS MÉNDEZ Director de Tecnología en FONOIP +56 2 2947 9000 alvaro(a)fonoip.com | www.fonoip.com [1] Moisés Chacón 46, El Monte, RM Links: ------ [1] http://www.fonoip.com

2 1

presence_mwi body check problem
by Володимир Іванець 24 Jan '19

24 Jan '19

Hello! I'm trying to process PUBLISH on Kamailio (v. 5.2.1) but constantly getting "500 Server Internal Error" responce. For packet body: *Messages-Waiting: yes* *Message-Account: sip:100-test@172.16.30.151 <sip%3A100-test(a)172.16.30.151>* *Voice-Message: 1/2* ... debug output is: *kamailio: 2(27127) DEBUG: presence [event_list.c:348]: search_event(): start event= [message-summary/6]* *kamailio: 2(27127) DEBUG: presence [publish.c:351]: ki_handle_publish_uri(): SIP-If-Match header not found* *kamailio: 2(27127) DEBUG: presence [presentity.c:88]: generate_ETag(): etag= a.1548164100.27127.7.0 / 22* *kamailio: 2(27127) DEBUG: presence [publish.c:360]: ki_handle_publish_uri(): new etag = a.1548164100.27127.7.0* *kamailio: 2(27127) DEBUG: presence [publish.c:385]: ki_handle_publish_uri(): Expires header found, value= 16* *kamailio: 2(27127) ERROR: presence_mwi [add_events.c:110]: mwi_publ_handl(): check of body <Messages-Waiting: yes* *kamailio: Message-Account: sip:100-test@172.16.30.151 <sip%3A100-test(a)172.16.30.151>* *kamailio: Voice-Message: 1/2* *kamailio: > failed at character number 22* *kamailio: 2(27127) ERROR: presence [publish.c:480]: ki_handle_publish_uri(): in event specific publish handling* I'm not sure, but it appears to me that check in line 95 from https://github.com/kamailio/kamailio/blob/5.2/src/modules/presence_mwi/add_… is not passing. I was trying to add "\n" and "\r" to the end of each string but I always had failure on character number 22. Does anyone know how exactly PUBLISH packet body should look like? Thanks a lot!

2 4

Problem at Rx Interface - kamailio P-CSCF 5.1.6
by Valentin Christoph 23 Jan '19

23 Jan '19

Hi all, We are using kamailio 5.1.6, configured as P-CSCF, facing following problem. Please refer to the attached tshark trace, too. If during call setup (by simulated UAs) at the terminating P-CSCF the simulated PCRF rejects the Diameter AAR message (frame 46/47 at the attached trace), then the kamailio P-CSCF runs into a questionable behaviour. By calling the Rx_AAR() function in configuration, the processing of the 200 OK (frame 45) is suspended (by the ims_qos module) and then resumed with the receipt of the AAA message (frame 47). Now the ims_dialog module is called with the dlg_terminate("all", "reason") function, but the 200 OK has not yet been sent. The ims_dialog sends CANCEL downstream and 488 upstream. However, the 200 OK is sent additionally. We would rather have expected the ims_dialog module should send BYE in both directions. When we respond the CANCEL with 481 Call/Transaction does not exist (which we MUST according to RFC 3261), then we would expect the ims_dialog module at least now to react with BYE in both directions. Could you help? What's our misunderstanding? How could we proceed to get this issue fixed? Kind regards Christoph ____ Christoph VALENTIN Software Developer | R&D Core / SIP Core P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 1

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

Jump to page:

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