- sr-users - kamailio.org

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 28 Jan '19

28 Jan '19

Hello, Can someone help me to understand this error given by TM Module? I have a Kamailio SIP Proxy running in front of a few Asterisk boxes. On average, he is processing 70-80 requests per second. The problem is that sometimes (90-100 times/day) - I see such errors in the logs: 500 I'm terribly sorry, server error occurred (1/SL) 477 Unfortunately error on sending to next hop occurred (477/TM) Trying to investigate this error - I found that this is happening randomly and for INVITES coming from the Asterisk Box. For ex, the INVITE below: 192.168.180.10 - Kamailio Server 192.168.180.36 - Asterisk Server INVITE sip:1001@192.168.180.10:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.180.36:5060;branch=z9hG4bK4624ab4e;rport Max-Forwards: 70 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Contact: <sip:anonymous@192.168.180.36:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE User-Agent: MYCOMPANY Date: Mon, 28 Jan 2019 16:01:56 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Type: application/sdp Content-Length: 251 v=0 o=SIP 2139556641 2139556641 IN IP4 192.168.180.36 s=MYCOMPANY PBX c=IN IP4 192.168.180.36 t=0 0 m=audio 14674 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv Kamailio is replying back with 100 Trying and then with 500/477 errors: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 And I cannot actually get what is wrong with this INVITE - and why Kamailio cannot process it? Other calls for the same extension are working fine, this is happening randomly and with different extensions. Load on the server is very low: [root@kamailio root]# nproc 8 [root@kamailio root]# uptime 17:49:15 up 8 days, 21:17, 6 users, load average: 0.66, 0.56, 0.52 [root@kamailio root]# free -m total used free shared buff/cache available Mem: 7981 4283 142 818 3556 2581 Swap: 6141 137 6004 [root@kamailio root]# ss -4 -n -l | grep 5060 udp UNCONN 0 0 192.168.180.10 :5060 *:* udp UNCONN 0 0 127.0.0.1:5060 *:* tcp LISTEN 0 128 192.168.180.10 :5060 *:* tcp LISTEN 0 128 127.0.0.1:5060 *:* In the kamailio logs I found that kamailio was able to get the contact address: kamailio[18168]: INFO: {INVITE (1) Contacts loaded for 1001} kamailio[18168]: INFO: {INVITE (1) t_next_contacts - Only one contact found for 1001, calling} kamailio[18168]: INFO: {INVITE (1) Next Hop: <192.168.180.211:3126>} I don't know how to reproduce this - I tried to disconnect the phone from the power source - and made a call to that extension, and it is giving timeouts - like it is supposed to be. What could be the problem and how I can fix it? Thank You.

1 0

Playing with Diameter - Error opening connection to :3868
by Steve Bucklin 28 Jan '19

28 Jan '19

Hello all, I am brand new to this list and I am also on a steep learning curve with Kamailio and Diameter.... so please be gentle as I am just starting! I am trying to look at the Diameter signaling and have a glimpse into the information passed. I have set up a compiled 5.2 on CentOS 7. I suspect that I am missing something obvious, but not sure what. I am seeing this error: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known It looks like the FQDN in the diameter.xml under 'peer' is not being resolved, as it is seeing port 3868? Any pointers would be greatly taken :-) Here is my diameter: <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="mra1.testservers.xxx" Realm="testservers.xxx" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="16" QueueLength="32" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <peer FGDN="mra2.testservers.xxx" Realm="testservers.xxx" proto="sctp" port="3868"/> <Acceptor port="3868" bind="192.168.1.20"/> <Auth id="16777251" vendor="10415"/>  <SupportedVendor vendor="10415" /> </DiameterPeer> And here is what I am getting on the startup: Jan 28 14:19:35 telco-lon1-02 kamailio: INFO: <core> [core/tcp_main.c:4722]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: <core> [main.c:2649]: main(): processes (at least): 29 - shm size: 67108864 - pkg size: 8388608 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:240]: cdp_child_init(): CDiameterPeer child starting ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22783]: INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:242]: cdp_child_init(): ... CDiameterPeer child started Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22790]: INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22784]: INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22786]: INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22793]: INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22794]: INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22796]: INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22788]: INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [] Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22791]: INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22792]: INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22785]: INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22787]: INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22795]: INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22782]: INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22789]: INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22797]: INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22802]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: WARNING: cdp [receiver.c:866]: peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known Thanks, Steve

2 2

database reconnection db_unixodbc
by Karthik Srinivasan 27 Jan '19

27 Jan '19

Hello, I am testing how kamailio reacts to various database conditions. One such condition is if the database engine is simply shut down (that is, database server process no longer running, tcp listening socket closed, etc...) I am utilizing the db_unixodbc module to connect to an Informix database engine. I am currently running on Kamailio version 5.0. I have a test query that executes against the database engine every 10 seconds. Here is what i have noticed if i shut down the database engine at some point after i run Kamailio. the first test query that attempts to run against the db engine fails; it tries to reconnect and fails. The second test query (10 seconds after the 1st) results in a SIG_CHILD and shuts down the entire Kamailio process. Has anyone experienced this? Is there a solution to this? Ideally the second query should also fail and return gracefully; and ideally queries continue to fail until the database engine is back up. See logs below: Jan 17 20:07:25 [29297]: INFO: (s) SQL query: FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:135]: db_unixodbc_submit_query(): rv=-1. Query= FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=08S01:1:-11020:[Informix][Informix ODBC Driver]Communication link failure. Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:59]: reconnect(): Attempting DB reconnect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:74]: reconnect(): failed to connect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=08002:1:0:[unixODBC][Driver Manager]Connection name in use Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=HY010:2:-11067:[Informix][Informix ODBC Driver]Function sequence error. Jan 17 20:07:25 [29297]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jan 17 20:07:25 [29297]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query FIRST TEST QUERY Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL ret: fail (-1) Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL res: no rows Jan 17 20:07:35 [29297]: INFO: (s) [123] SQL query: 10 seconds later the SECOND TEST QUERY (it's the same query as the first one) Jan 17 20:07:35 [29301]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 28 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:744]: handle_sigs(): child process 29297 exited by a signal 11 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:747]: handle_sigs(): core was not generated Jan 17 20:07:35 [29283]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jan 17 20:07:35 [29301]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29295]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29291]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29288]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29300]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29284]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29286]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29293]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29289]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29287]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29292]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29296]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29298]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29299]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29285]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29294]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29290]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29283]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Thank you, Karthik

2 5

Why kamailio can not be a consumer of RabbitMQ?
by CuiGang 26 Jan '19

26 Jan '19

Hello every one. I noticed that module RABBITMQ just implements the publish functions. It means kamailio can only as a producer of RabbitMQ. My question is Why RABBITMQ module not implement consumer functions? As NSQ, let kamailio can be a consumer receive messages from RabbitMQ. Regards. CuiGang cuigang0120(a)aliyun.com

2 1

DMQ errors
by Aleksandar Sosic 25 Jan '19

25 Jan '19

Hi, when I have only one node and dmq enabled I've got this errors: ``` 17(45) ERROR: dmq [notification_peer.c:337]: add_server_and_notify(): error adding notification node 17(45) ERROR: dmq [dmq_funcs.c:516]: ping_servers(): cannot retrieve initial nodelist from sip:dmq-router-service.alex.svc.cluster.local:5062 ``` On the second node booting after this one I don't get any of these errors. Is there any flag/option to turn off this error on the `cannot retrieve initial nodelist` in case I have only one node for a period of time? Thanks, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 2

Re: [SR-Users] kamailio-lb fails after topos enabled.
by Daniel Tryba 25 Jan '19

25 Jan '19

On Fri, Jan 25, 2019 at 10:19:45AM -0300, Marcos Pytel wrote: > Could you help me to catch the coredump file? Please keep the mailinglist in the loop. > When I execute bt full the systems shows "no symbols". What package i need to perform it? I don't know what the sipwise config is, but it if is (anything like) debian the normal kamailio package is strippped of debugging symbols. You'll need to install the debug package (kamailio-dbg in debian).

1 0

kamailio-lb fails after topos enabled.
by Marcos Pytel 25 Jan '19

25 Jan '19

Hi team! I'm using Kamailio version: kamailio 5.1.6 (x86_64/linux). When I enabled topos, after a few minutes i get this erros in the log file and the LB Service goes down.: Jan 24 13:20:21 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:21:36 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:29:06 sipwise lb[30135]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:31:36 sipwise lb[30133]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:34:41 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:43:06 sipwise lb[30134]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:45:21 sipwise lb[30136]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:06 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:21 sipwise lb[30136]: ERROR: topos [tps_storage.c:340]: tps_storage_link_msg(): bad sip message or missing Contact hdr Jan 24 13:47:35 sipwise lb[30163]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:738]: handle_sigs(): child process 30120 exited by a signal 6 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:741]: handle_sigs(): core was generated I attached the coredump file. I tried to get bt full but i think that i need something else to catch it. Thank you! Marcos.

2 2

ERROR while using KEMI - Python
by Prabhat Kumar 25 Jan '19

25 Jan '19

Hi, I am getting this error message while starting kamailio. Enviroment: OS- Ubuntu 16.04.5 LTS (Xenial Xerus) python 2.7 ERROR: app_python [app_python_mod.c:164]: mod_init(): failed to load python script ERROR: <core> [core/sr_module.c:990]: init_mod(): Error while initializing module app_python (/usr/local/lib64/kamailio/modules/app_python.so)

2 2

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

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

Mysql
by Nicolas Breuer 20 Jan '19

20 Jan '19

Hello, Working on sip_trace table produce this error WARNING: db_mysql [km_res.c:142]: db_mysql_get_columns(): unhandled data type column (Msg_text) type id (250), use DB1_STRING as default

5 16

segfault error - process stopped
by AL RSM 20 Jan '19

20 Jan '19

Hi We are running Kamailio 3.7 on our production servers. The Kamailio process stopped running on one of the 4 servers. Log shows "segfault error". No core file generated. Any suggestion on how to verify the issue would be appreciated. kernel: [63574875.776269] kamailio[1558]: segfault at 0 ip 000000000055933a sp 00007fffd4ca6700 error 4 in kamailio[400000+211000] /usr/sbin/kamailio[1545]: ALERT: <core> [main.c:785]: child process 1558 exited by a signal 11 /usr/sbin/kamailio[1545]: ALERT: <core> [main.c:788]: core was not generated CRON[21436]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Thanks, AL

3 2

Mid-Registrar
by Mark Thomas 20 Jan '19

20 Jan '19

I’m currently and OpenSIPS user and I really want to be able to use their software on OpenWRT, but I have found it really hard to cross-compile. Is there a possibility to run Kamailio as a mid-registrar? For my application this is required, and I haven’t been able to find any information on this.

3 3

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