- sr-users - kamailio.org

pcscf logs - error in kamailio
by Pavithra M 09 Apr '20

09 Apr '20

Hi , The error i am facing in kamailio pcscf Apr 9 13:44:31 tel-VirtualBox kamailio[2847]: INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present. Apr 9 13:44:31 tel-VirtualBox kamailio[2811]: ERROR: <core> [core/lvalue.c:353]: lval_pvar_assign(): setting pvar failed Apr 9 13:44:31 tel-VirtualBox kamailio[2811]: ERROR: <core> [core/lvalue.c:404]: lval_assign(): assignment failed at pos: (106,30-106,48) Apr 9 13:44:31 tel-VirtualBox kamailio[2811]: ERROR: <core> [core/lvalue.c:353]: lval_pvar_assign(): setting pvar failed Apr 9 13:44:31 tel-VirtualBox kamailio[2811]: ERROR: <core> [core/lvalue.c:404]: lval_assign(): assignment failed at pos: (114,31-114,52) kindly help me in this issue .. because of this , it is throwing 403 domain not server error in scscf

1 0

Error in kamailio 5.3.3
by Pavithra M 08 Apr '20

08 Apr '20

Hi, I have configured kamailio as Ims server with pcscf,icscf,scsf and hss in 4 different vms . After that I use zoiper client for testing the call flow . Registration is successful .It goes via UE -> Pcscf -> icscf -> scscf and returns back with 200 OK . Registration is happening with authentication from hss . When I make an INVITE , it goes from UE -> PCSCF -> SCSCF -> ICSCF -> SCSF and s-cscf gives *403 - Domain not served *to icscf and i-cscf returns to p-cscf with the same error . I am not seeing any errors in scscf and i-cscf . In pcscf , I am seeing an error like *Error : <core> [core/lvalue.c] :lval_pvar_assign() : setting pvar failed * *Error : <core> [core/lvalue.c] :* *lval_assign():assignment failed at pos* What should I do? Kindly advise. I am struggling with this issue for a week.kindly do the needful. Version - kamailio - 5.3.3 I need a normal call flow to be established between two clients.kindly help .

3 10

Re: [SR-Users] Kamailio propagates 180 and 200 OK OUT OF ORDER
by Alex Balashov 08 Apr '20

08 Apr '20

On Wed, Apr 08, 2020 at 10:51:25PM +0200, Daniel-Constantin Mierla wrote: > - corex module offers functions to set source address and received > socket for more flexibility why processing on 127.0.0.1 Interesting. Thanks for the tip! -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

1 0

Re: [SR-Users] Kamailio propagates 180 and 200 OK OUT OF ORDER
by Alex Balashov 08 Apr '20

08 Apr '20

On Wed, Apr 08, 2020 at 04:54:48PM +0100, David Villasmil wrote: > I have a question on this, since 180 arrived before the 200, shouldn’t it > go out before? I.e.: FIFO? Or is this not happening because there are > multiple processes and one may take the 180 and the other the 200 and they > are processes independently? > > I guess setting the childs to only 1 should prove this theory. In theory, it should all be FIFO, of course. In practice, there are stochastic aspects to OS process scheduling and I/O scheduling which make the ingress and egress of messages arriving at Kamailio simultaneously or substantially simultaneously somewhat indeterminate. And, of course, it depends on how complicated the processing of the messages respectively is, either in computational terms, or external I/O wait, or both. To Steve Davies' point, that's just the nature of the multiprocess architecture, together with the lack of a distributor thread. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 5

Re: [SR-Users] Kamailio propagates 180 and 200 OK OUT OF ORDER
by Alex Balashov 08 Apr '20

08 Apr '20

On Wed, Apr 08, 2020 at 01:30:21PM +0000, Henning Westerholt wrote: > There is also the option to do an asynchronous sleep (with the async) > module on the message that you want to delay but still processing > other messages during it. We have a buggy endpoint that consistently sends reinvites immediately following the e2e ACK, and substantially simultaneously with the ACK. It quite often happens that the re-invite goes out the door before the ACK, which is of course rejected by the target due to inconsistent state. We solved this a somewhat nasty hack using just the very technique you mentioned -- we use the async features of Kamailio to 'delay' all re-invites about 50 ms. It does solve this problem, if a bit suboptimally and at the cost of eccentricity and complexity. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

1 0

KEMI - "record_route_advertised_address" - function export or alternative
by Jacob Greene 08 Apr '20

08 Apr '20

Hello all! I'm wondering if there are any plans to add record_route_advertised_address() function to KEMI? I'm unable to completely finish my migration to KEMI without this function due to server side NAT in our VPC and the record_route header getting automatically set to the advertised address. Is there a workaround I could use to change the record route header? Is anyone aware of any resources we could utilize to help get this fixed? Thanks for reading! Jake, Voice Engineer

2 1

Kamailio - pcscf error
by Pavithra M 07 Apr '20

07 Apr '20

Hi, I have configured kamailio as Ims server with pcscf,icscf,scsf and hss in 4 different vms . After that I use zoiper client for testing the call flow . Registration is successful .It goes via UE -> Pcscf -> icscf -> scscf and returns back with 200 OK . Registration is happening with authentication from hss . When I make an INVITE , it goes from UE -> PCSCF -> SCSCF -> ICSCF -> SCSF and s-cscf gives *403 - Domain not served *to icscf and i-cscf returns to p-cscf with the same error . I am not seeing any errors in scscf and i-cscf . In pcscf , I am seeing an error like *Error : <core> [core/lvalue.c] :lval_pvar_assign() : setting pvar failed * *Error : <core> [core/lvalue.c] :* *lval_assign():assignment failed at pos* What should I do? Kindly advise. I am struggling with this issue for a week.kindly do the needful. Version - kamailio - 5.3.3 I need a normal call flow to be established between two clients.kindly help .

1 0

[kamailio][webrtc issue]
by Bilal Abbasi 07 Apr '20

07 Apr '20

Hi Users, I am new to kamailio, and trying to implement webrtc on kamailio, i am getting following error when i try to login from tryjssip page. Mar 29 21:11:15 kamailio kamailio[20570]: ERROR: <core> [core/tcp_read.c:1535]: tcp_read_req(): bad request, state=7, error=4 buf:#012GET / HTTP/1.1#015#012Host: kamailio..com:7443#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://tryit.jssip.net#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9,ur;q=0.8#015#012Sec-WebSocket-Key: 88fVCzdsvQPCrwV7gMrWaA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012#012parsed:#012GET / HTTP/1.1#015#012Host: kamailio..com:7443#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://tryit.jssip.net#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9,ur;q=0.8#015#012Sec-WebSocket-Key: 88fVCzdsvQPCrwV7gMrWaA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip I can see following error on chrome console. WebSocket connection to 'wss://kamailio..com:7443/' failed: Connection closed before receiving a handshake response I tried to set tcp_accept_no_cl to value 'no' and this did not helped me either. Can someone please help me with the issue Regards Bilal Abbasi

3 7

Reloading Contacts/Attributes at runtime
by Sergiu Pojoga 07 Apr '20

07 Apr '20

Hi there, Is there some mechanism to reload Contacts *and *their attributes at runtime, without a full Kamailio restart? Known to me tools: *rpc ul.add* will add a new Contact, but not its attributes *rpc ul.flush* will flush from memory to DB, not the other way around Having a combination of registered/permanent Contacts, I can add permanent ones with *ul.add*, however I couldn't find a way to set its attributes other than in DB location, which implies the need for a reload. Thanks in advance. --Sergiu

1 0

Substitution of Contact Header
by Mack Hendricks 07 Apr '20

07 Apr '20

Hey All, I always have issues with substituting out header values. I’ve tried subst and subst_hf. Here is the value that I want to change out: Contact: <sip:52.41.52.34:5060;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC <sip:52.41.52.34:5060;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC>> And this is what I want it to be Contact: <sip:1313717555@jump.dsiprouter.net <sip:1313717555@jump.dsiprouter.net>;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC> I’m using this subst('/^Contact: <sip:(.*);(.*)>$/Contact: <sip:1313717555@jump.dsiprouter.net;\2 <sip:1313717555@jump.dsiprouter.net;\2>>\r/ig’); And it doesn’t work, but putting into a online regular expression tester it looks good as shown below. Any ideas?

3 4

kamailio-pcscf-error
by Pavithra M 07 Apr '20

07 Apr '20

Hi I am facing the error in pcscf and i have attached the error log and tcp dump of pcscf. kindly do the needful.

1 0

Substitution of Contact Header
by Mack Hendricks 07 Apr '20

07 Apr '20

Hey All, I always have issues with substituting out header values. I’ve tried subst and subst_hf. Here is the value that I want to change out: Contact: <sip:52.41.52.34:5060;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC <sip:52.41.52.34:5060;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC>> And this is what I want it to be Contact: <sip:1313717555@jump.dsiprouter.net <sip:1313717555@jump.dsiprouter.net>;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC> I’m using this subst('/^Contact: <sip:(.*);(.*)>$/Contact: <sip:1313717555@jump.dsiprouter.net;\2 <sip:1313717555@jump.dsiprouter.net;\2>>\r/ig’); And it doesn’t work, but putting into a online regular expression tester it looks good as shown below. Any ideas?

2 1

Scscf error
by Pavithra M 06 Apr '20

06 Apr '20

Hi, I have configured p-cscf ,icscf, scscf , hss in different vms and I am able to get the registration successful. I am using zoiper client and kamailio version 5.3.3. After the registration , when I try to make a call, it is showing 403 , Domain not served In my scscf TCP dump . What is this error and how to solve this . Kindly help me asap since I am facing this issue for a week and struggling to resolve it . Thanks.

1 0

Pcscf error
by Pavithra M 06 Apr '20

06 Apr '20

Hi, I have configured p-cscf ,I cscf, scscf ,hss in four different vms. I am getting below errors in my pcscf log . Kindly provide me the solution asap . Kamailio version - 5.3.3 Apr 6 18:02:29 tel-VirtualBox kamailio: INFO: <core> [core/tcp_main.c:5042]: init_tcp(): using epoll_lt as the io watch method (auto detected) Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: auth [auth_mod.c:345]: mod_init(): qop set, but nonce-count (nc_enabled) support disabled Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: path [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: path [path_mod.c:151]: mod_init(): outbound module not available Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:264]: mod_init(): Successfully bound to PCSCF Usrloc module Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:271]: mod_init(): Successfully bound to TM module Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:114]: ipsec_print_all_socket_lists(): Listening on: Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): udp: 10.45.6.179 [10.45.6.179]:4060 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): udp: 0.0.0.0 [0.0.0.0]:5062 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): udp: 0.0.0.0 [0.0.0.0]:5063 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): udp: 0.0.0.0 [0.0.0.0]:5064 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): tcp: 10.45.6.179 [10.45.6.179]:4060 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): tcp: 0.0.0.0 [0.0.0.0]:5062 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): tcp: 0.0.0.0 [0.0.0.0]:5063 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:164]: ipsec_print_all_socket_lists(): tcp: 0.0.0.0 [0.0.0.0]:5064 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: ims_registrar_pcscf [ims_registrar_pcscf_mod.c:275]: mod_init(): Successfully bound to PCSCF IPSEC module Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: ERROR: rtpengine [rtpengine.c:2901]: select_rtpp_set(): no rtpp_set_list->rset_first Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: NOTICE: rtpengine [rtpengine.c:1722]: mod_init(): Default rtpp set 0 NOT found Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [main.c:2779]: main(): processes (at least): 82 - shm size: 67108864 - pkg size: 8388608 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: WARNING: tm [tm.c:507]: fixup_routes(): t_on_failure("NATMANAGE"): empty/non existing route Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Apr 6 18:02:29 tel-VirtualBox kamailio[9603]: ERROR: <script>: event_route[htable:mod-init] { Apr 6 18:02:29 tel-VirtualBox kamailio[9722]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Apr 6 18:02:29 tel-VirtualBox kamailio[9730]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9737]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9736]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9738]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9739]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9740]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9735]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/9735 Apr 6 18:02:29 tel-VirtualBox kamailio[9741]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9752]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:02:29 tel-VirtualBox kamailio[9751]: WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=843 a=5 n=route Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=902 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=902 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=904 a=27 n=sql_query Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=905 a=25 n=xlog Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <script>: Preloading NAT-PING. Rows: 10 Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=921 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=907 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=919 a=23 n=while Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=911 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=915 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=917 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=918 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=921 a=25 n=sql_result_free Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=845 a=26 n=sht_iterator_start Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=855 a=23 n=while Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=846 a=25 n=sht_iterator_next Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=847 a=25 n=xlog Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <script>: OPTIONS to sip:bob@10.45.6.75:60060;rinstance=a59e664cda799366;transport=tcp via sip:10.45.6.75:38891;transport=tcp... Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=848 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=849 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=850 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=851 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=852 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=853 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=854 a=24 n=uac_req_send Apr 6 18:03:29 tel-VirtualBox kamailio[9753]: ERROR: <core> [core/tcp_main.c:4456]: handle_tcpconn_ev(): connect 10.45.6.75:38891 failed Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=846 a=25 n=sht_iterator_next Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=847 a=25 n=xlog Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <script>: OPTIONS to sip:alice@10.45.6.174:43244;rinstance=72779c915b29d0c2;transport=UDP via sip:10.45.6.174:43244... Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=848 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=849 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=850 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=851 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=852 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=853 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=854 a=24 n=uac_req_send Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=846 a=25 n=sht_iterator_next Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=847 a=25 n=xlog Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <script>: OPTIONS to sip:bob@10.45.6.75:46205;transport=TCP;rinstance=f2285c01dd4acb41 via sip:10.45.6.75:46205;transport=tcp... Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=848 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=849 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=850 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=851 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=852 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=853 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=854 a=24 n=uac_req_send Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=846 a=25 n=sht_iterator_next Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=847 a=25 n=xlog Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <script>: OPTIONS to sip:bob@10.45.6.75:37861;transport=TCP;rinstance=e965f9424c56508e via sip:10.45.6.75:37861;transport=tcp... Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=848 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=849 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=850 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=851 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=852 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=853 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=854 a=24 n=uac_req_send Apr 6 18:03:29 tel-VirtualBox kamailio[9605]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=861 a=25 n=xlog Apr 6 18:03:29 tel-VirtualBox kamailio[9605]: ERROR: <script>: request sent to sip:alice@10.45.6.174:43244;rinstance=72779c915b29d0c2;transport=UDP completed with code: 200, Type 1 Apr 6 18:03:29 tel-VirtualBox kamailio[9605]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=888 a=16 n=if Apr 6 18:03:29 tel-VirtualBox kamailio[9605]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=887 a=63 n=assign Apr 6 18:03:29 tel-VirtualBox kamailio[9753]: ERROR: <core> [core/tcp_main.c:4456]: handle_tcpconn_ev(): connect 10.45.6.75:46205 failed Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <core> [core/tcp_main.c:2997]: tcpconn_1st_send(): connect 10.45.6.75:37861 failed (RST) Connection refused Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: <core> [core/tcp_main.c:3005]: tcpconn_1st_send(): 10.45.6.75:37861: connect & send for 0x7fea3e2a3660 failed: Connection refused (111) Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: tm [../../core/forward.h:261]: msg_send_buffer(): tcp_send failed Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: tm [uac.c:644]: send_prepared_request_impl(): Attempt to send to precreated request failed Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=846 a=25 n=sht_iterator_next Apr 6 18:03:29 tel-VirtualBox kamailio[9730]: ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=856 a=25 n=sht_iterator_end Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=861 a=25 n=xlog Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: <script>: request sent to sip:bob@10.45.6.75:60060;rinstance=a59e664cda799366;transport=tcp completed with code: 408, Type 2 Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=888 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=868 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=865 a=63 n=assign Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=886 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=861 a=25 n=xlog Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: <script>: request sent to sip:bob@10.45.6.75:46205;transport=TCP;rinstance=f2285c01dd4acb41 completed with code: 408, Type 2 Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=888 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=868 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=865 a=63 n=assign Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=886 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=861 a=25 n=xlog Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: <script>: request sent to sip:bob@10.45.6.75:37861;transport=TCP;rinstance=e965f9424c56508e completed with code: 408, Type 2 Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=888 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=868 a=16 n=if Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=865 a=63 n=assign Apr 6 18:03:32 tel-VirtualBox kamailio[9719]: ERROR: *** cfgtrace:request_route=[uac:reply] c=[/etc/kamailio/pcscf/kamailio.cfg] l=886 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=444 a=25 n=xlog Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: <script>: REGISTER ( sip:alice@sip.example.com;transport=UDP (10.45.6.174:43244) to sip:alice@sip.example.com;transport=UDP, xJ8PR1SPmFBplNjHGYC1LA..) Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=455 a=5 n=route Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=668 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=663 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=668 a=63 n=assign Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=669 a=26 n=xlog Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=709 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=714 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=709 a=25 n=mf_process_maxfwd_header Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=720 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=714 a=26 n=sanity_check Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=725 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=720 a=24 n=has_totag Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=730 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=725 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=734 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=730 a=24 n=t_lookup_request Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=737 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=734 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=735 a=26 n=send_reply Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=466 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=458 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=472 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=466 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=472 a=5 n=route Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/pcscf/kamailio.cfg] l=788 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/pcscf/kamailio.cfg] l=748 a=24 n=has_totag Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=481 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=477 a=24 n=t_precheck_trans Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=481 a=24 n=t_check_trans Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=484 a=24 n=t_check_trans Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=490 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=486 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=495 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=490 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=495 a=24 n=loose_route Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=640 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present. Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=585 a=55 n=force_rport Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=589 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=586 a=25 n=is_method Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=587 a=24 n=add_contact_alias Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=589 a=39 n=setflag Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=597 a=16 n=if Apr 6 18:04:19 tel-VirtualBox kamailio[9606]: ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=591 a=25 n=is_method Kindly do the needful Thanks.

1 0

Problem Storing USRLOC Attributes, Part 2
by Sergiu Pojoga 06 Apr '20

06 Apr '20

Hi there, I'm observing a similar behavior as reported a while ago in this case: https://github.com/kamailio/kamailio/issues/243 It appears that only the *last *attribute before save() is stored in DB and later restored on lookup() kamcmd version kamailio 5.2.5 (x86_64/linux) e10d4f Script: $xavp(ulattrs=>PubNetIP) = $si; $xavp(ulattrs=>PubNetPort) = $sp; $xavp(ulattrs=>Transport) = $proto; pv_xavp_print(); save("location", ""); Mysql log: insert into `location_attrs` (`username`,`ruid`,`last_modified`,`aname`,`atype`,`avalue`,`domain` ) values ('firstuser','uloc-5e855601-2529-1','2020-04-01 23:03:48','Transport',0,'udp','sip.mydomain.net') MariaDB [(none)]> select * from kamailio.location_attrs; *************************** 1. row *************************** id: 26 ruid: uloc-5e855601-2529-1 username: firstuser domain: sip.mydomain.net aname: Transport atype: 0 avalue: udp last_modified: 2020-04-01 23:12:48 Kamailio xavp pring in logs: +++++ start XAVP list: 0x7f28ff1e9590 ((nil)) (level=0) *** (l:0 - 0x7f28ff1e9590) XAVP name: ulattrs XAVP id: 2085639187 XAVP value type: 6 XAVP value: <xavp:0x7f28ff1e94e0> +++++ start XAVP list: 0x7f28ff1e94e0 (0x7f28ff1e95b0) (level=1) *** (l:1 - 0x7f28ff1e94e0) XAVP name: Transport XAVP id: 3694982711 XAVP value type: 2 XAVP value (str): udp *** (l:1 - 0x7f28ff1e94e0) end ----- end XAVP list: 0x7f28ff1e94e0 (level=1) *** (l:0 - 0x7f28ff1e9590) end *** (l:0 - 0x7f28ff1e9438) XAVP name: ulattrs XAVP id: 2085639187 XAVP value type: 6 XAVP value: <xavp:0x7f28ff1e9388> +++++ start XAVP list: 0x7f28ff1e9388 (0x7f28ff1e9458) (level=1) *** (l:1 - 0x7f28ff1e9388) XAVP name: PubNetPort XAVP id: 3296056264 XAVP value type: 1 XAVP value (int): 58535 *** (l:1 - 0x7f28ff1e9388) end ----- end XAVP list: 0x7f28ff1e9388 (level=1) *** (l:0 - 0x7f28ff1e9438) end *** (l:0 - 0x7f28ff1e92e0) XAVP name: ulattrs XAVP id: 2085639187 XAVP value type: 6 XAVP value: <xavp:0x7f28ff1e9228> +++++ start XAVP list: 0x7f28ff1e9228 (0x7f28ff1e9300) (level=1) *** (l:1 - 0x7f28ff1e9228) XAVP name: PubNetIP XAVP id: 3296017806 XAVP value type: 2 XAVP value (str): 173.246.28.83 *** (l:1 - 0x7f28ff1e9228) end ----- end XAVP list: 0x7f28ff1e9228 (level=1) *** (l:0 - 0x7f28ff1e92e0) end ----- end XAVP list: 0x7f28ff1e9590 (level=0)

2 4

Substitution of Contact Header
by Mack Hendricks 06 Apr '20

06 Apr '20

Hey All, I always have issues with substituting out header values. I’ve tried subst and subst_hf. Here is the value that I want to change out: Contact: <sip:52.41.52.34:5060;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC> And this is what I want it to be Contact: <sip:1313717555@jump.dsiprouter.net <sip:1313717555@jump.dsiprouter.net>;line=sr-h06Cy7RYRFkYacM0a7epa7sVa7sVRcNCW7IbaGZ9RGlC> I’m using this subst('/^Contact: <sip:(.*);(.*)>$/Contact: <sip:1313717555@jump.dsiprouter.net;\2>\r/ig’); And it doesn’t work, but putting into a online regular expression tester it looks good as shown below. Any ideas?

1 0

Confused with forwarding REGISTER
by fuxfwgc4a2i1gr 06 Apr '20

06 Apr '20

Hi. Well issue already described there : https://github.com/kamailio/kamailio/issues/2271 I will be really happy if somebody point me what exactly i have to do to route 404 answer from Registar to UA. If i understand right, in moment when registrar generate 404 i have to see in log message which generated inside onreply_route[REPLYROUTE] but in current moment i not see it and 404 not transmitted to UA. And it just silently ignored by Kamailio. In case if i am right and this is a bug in Kamailio please point me what words i have to use to prove that this is really bug. In current moment routing config looks like : request_route { # per request initial checks route(REQINIT); route(CATCH_CANCEL); route(RR_PARSE); route(REGISTRATION); xlog("L_INFO", "Initial relay packet\n"); $du = "sip:10.34.64.2:5060"; route(FORWARD); # update $du to set the destination address for proxying exit; } route[CATCH_CANCEL] { if (is_method("CANCEL") == true) { if (t_check_trans() == true) { route(FORWARD); } sl_reply("500", "Internal Server Error"); drop; } } route[RR_PARSE] { if(loose_route() == true ) { xlog("L_INFO", "RR-enforced\n"); append_hf("P-hint: rr-enforced\r\n"); route(FORWARD); } else { xlog("L_INFO", "RR simple\n"); record_route(); } } route[REGISTRATION] { if(is_method("REGISTER") == true) { add_path_received(); append_hf("Supported: path\r\n"); xlog("L_INFO", "GOT REGISTER\n"); } } # Per SIP request initial checks route[REQINIT] { if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { # silent drop for scanners - uncomment next line if want to reply # sl_send_reply("200", "OK"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } route[FORWARD] { t_on_failure("FAILROUTE"); t_on_reply("REPLYROUTE"); if(t_relay() <= 0) { sl_reply_error(); } drop; } onreply_route[REPLYROUTE] { xlog("Reply SIP message from $si:$sp\n"); if (t_check_trans() == false) { drop; } } failure_route[FAILROUTE] { xlog("Reply Fail SIP message from $si:$sp\n"); }

4 6

Problem with max tcp connections
by Jose Fco. Irles Durá 06 Apr '20

06 Apr '20

Hi I have a kamailio 5.1.2 as load balancer and registration offloading, but I have a problem with the max tcp connections that it can handle. I suspect that is a linux limit, but I don't find the reason or config. When that limit arrives, I can't connect to kamailio and I receive "Connection reset by peer", but I can't view any error message in the logs. If I check the connections in kamailio, I view that it have "free" connections: # kamctl kamcmd core.tcp_info { readers: 8 max_connections: 4096 max_tls_connections: 2048 opened_connections: 2655 opened_tls_connections: 0 write_queued_bytes: 0 } I have this configs in kamailio.conf (related to tcp) disable_tcp=no tcp_connection_lifetime=3610 tcp_connect_timeout=5 tcp_crlf_ping=yes tcp_accept_aliases=no tcp_keepalive=yes tcp_keepidle=5 tcp_rd_buf_size=65536 tcp_conn_wq_max=131072 mlock_pages=yes shm_force_alloc=yes tcp_max_connections=4096 The shm memory to 256 and the pkg memory to 32. And, following this doc: https://github.com/kamailio/kamailio/blob/master/doc/tutorials/tcp_tunning.… I have setted this values: net.ipv4.ip_local_port_range = 1024 65535 net.core.somaxconn = 65535 net.core.netdev_max_backlog = 182757 Also, I had checked the limits for the main process pid: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes unlimited unlimited processes Max open files 1048576 1048576 files Max locked memory 16777216 16777216 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 386297 386297 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us The service is running inside a lxc container, without any resource limit, connected to the outside word throught macvlan interface. Where can I find problem source? Best regards

4 13

need help with RTPProxy in bridged mode
by Grant Bagdasarian 04 Apr '20

04 Apr '20

Hello, I'm using RTPproxy for the first time in bridged mode and I can't get kamailio/rtpproxy to rewrite the c parameter to the correct public ip address of kamailio. The setup is as following: Carrier ------[fiber]------ Kamailio ---------[lan]--------- Freeswitch Kamailio is listening on two interfaces: 1) Private: 172.0.0.1 2) Public: 192.168.0.1 (since we have a dedicated fiber with our carrier, this is its public address) Freeswitch is listening on: 1) 172.0.0.2 Carrier is on: 1) 10.0.0.1 I've started an rtpproxy instance on the Kamailio box using: rtpproxy -s udp:127.0.0.1:7721 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -l 192.168.0.1 172.0.0.1 I've played around with rtpproxy_manage() and the various flags (ie, ei), but I can't get kamailio to set the correct public IP when the 200 OK has to be sent back to the carrier. It always sets it to its private address, instead of its public address. I'm using Kamailio 4.2 with sippy/rtpproxy 2.0. Could someone please point me into the right direction? Thanks! Grant

4 8

need help with RTPProxy in bridged mode
by Artur Hovsepyan 04 Apr '20

04 Apr '20

hi, i'm also having the same issue, same setup, but instead of private IP i have real IP on my WAN interface. and regardless that i've used rtpproxy_manage("coeir")and rtpproxy_manage("coier")kamailio is still replying with my internal (sip+rtp) ip in the outgoing to WAN SDP. Can you please help to understand how do i need to manager rtp proxy to send WAN IP in SDP? when my WAN IP is private IP and my carrier is also having private IP from same network, the issue is not seen. Thanks in advance,

1 1

rtpproxy bridge external(real ip)/internal
by Artur Hovsepyan 03 Apr '20

03 Apr '20

Hey, This is my first post here, so I wanted a bit of help. Appreciating that in advance. i have following setup: carrier(asterisk with sip ip=rtp ip=real IP) <==> kamailio+rtpproxy(ext real ip, internal ip) <==> internal asterisk(sip ip != rtp ip, both internal ips). rtprpoxy setup/usr/local/bin/rtpproxy -p /var/run/rtpproxy.pid -u rtpproxy -F -s udp:127.0.0.1 7722 -l kam_int_ip kam_ext_ip -m 10000 -M 20000 -L 30000 -d DBUG LOG kamailio listens on both external and internal ipsdispatcher list: 0 towards carrier SOCKET: udp:external_ip2 towards internal asterisk SOCKET: udp:internal_ip calls being routed with if(src_ip==carrier's real ip) sent to route "from_carrier" and if(src_ip==int_ast_sip_ip) sent to route "to_carrier" in the routes calls are dispatched with if(!ds_select_dst("0", "4")) and if(!ds_select_dst("2", "4")) rtpproxy_manage is done in "NATMANAGE" route: #checking if call is from carrier or to carrier:if(src_ip!=carrier_ext_ip) { if(nat_uac_test("8")) { rtpproxy_manage("coier"); } else { rtpproxy_manage("cor"); }}else { rtpproxy_manage("coeir");} so, this setup works, when i setup private IP addresses(from same network) on both carrier side(10.0.1.1) and external interface of kamailio(10.0.1.2) (accordingly changing the dispatcher file, rtpproxy and the kamailio.cfg). as per below: carrier(asterisk with sip ip=rtp ip=10.0.1.1) <==> kamailio+rtpproxy(ext ip=10.0.1.2, internal ip=10.0.2.1) <==> internal asterisk(sip ip != rtp ip, both internal ips). rtprpoxy setup/usr/local/bin/rtpproxy -p /var/run/rtpproxy.pid -u rtpproxy -F -s udp:127.0.0.1 7722 -l 10.0.2.1 10.0.1.2 -m 10000 -M 20000 -L 30000 -d DBUG LOG kamailio listens on both external and internal ipsdispatcher list: 0 towards carrier SOCKET: udp:10.0.1.22 towards internal asterisk SOCKET: udp:10.0.2.1 calls being routed with if(src_ip==10.0.1.1) sent to route "from_carrier" and if(src_ip==172.16.21.21) sent to route "to_carrier" in the routes calls are dispatched with if(!ds_select_dst("0", "4")) and if(!ds_select_dst("2", "4")) rtpproxy_manage is done in "NATMANAGE" route: #checking if call is from carrier or to carrier:if(src_ip!=10.0.1.1) { if(nat_uac_test("8")) { rtpproxy_manage("coier"); } else { rtpproxy_manage("cor"); }}else { rtpproxy_manage("coeir");} once i replace the IP addresses of carrier and kamailio with real IPs, kamailio is starting to forward internal asterisk's sip and rtp IP addresses to carrier and carrier's sip/rtp IPs in the SDP and breaking the SIP flow. that is is not the case while private IPs are setup for both external and internal interfaces. in the later case it normally does the bridging and sends correct info in SDP messages. can someone help me please to understand why/how it is working correctly for private IPs and "misbehaving" in case of real IPs. thanks,Art

1 1

Query on force_send_socket
by Amarnath K 03 Apr '20

03 Apr '20

Hi All, I'm using Kamailio version 5.1.9. In cfg file have routing to send out SIP messages from Kamailio stack. In this routing logic added force_send_socket("tcp:192.168.40.10:5060"); forward() I'm expecting the send port should be from 5060, but it always pick random port to send out message. my requirement is to send SIP messages from 5060 port instead of picking random port. Regards, Amarnath

5 6

Kamailio release
by Virgílio Cunha 03 Apr '20

03 Apr '20

Hi, When is the scheduled release date of kamailio-5.3.4? Best Regards, Virgílio Cunha

1 0

[ot] lightweight sip app for auto-answering with play file and echo mode
by Daniel-Constantin Mierla 01 Apr '20

01 Apr '20

Hello, wondering if anyone here is aware of a lightweight sip app that can answer a call, play some file and/or do echo mode, mainly targeted at using it for basic sip routing and call testing. Of course I know that Asterisk and FreeSwitch (or even SEMS) can do that, but they have many dependencies, requiring quite some resources to run them, so I thought maybe someone here figured out different solutions, eventually cli based apps like pjsua or baresip. GUI apps for Linux are also fine if they can be configured for such behaviour. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

7 18

Invite transaction lifetime
by Duarte Rocha 01 Apr '20

01 Apr '20

Greetings, I have a strange call with a client in which he sends me an INVITE and i do the usual "100", "183" and "200 - OK" but the client never gets my provisional or final responses and, as such keeps retransmitting the first INVITE. For the first retransmissions Kamailio doesn't relay the INVITE which i think is the correct behaviour. However, after around 30s, a retransmission is processed and is relayed to a different destination, using "ds_select_dst()" from the DISPATCH module. For this to happen it had to fail the "t_check_trans()" function from TM module which tells me that the transaction from the first INVITE was gone. I went to search timers and lifetime definitions on TM module and found one "max_inv_lifetime" which tells me that "An INVITE transaction will be kept in memory for maximum: max_inv_lifetime+fr_timer(from the ACK to the final reply wait)+wt_timer". In this case : max_inv_lifetime is 180 seconds, fr_timer is 30 seconds and wt_timer is 5 seconds. It's sum is 215seconds and from what i can see, my transaction only had a lifetime of 30s. fr_timer is configured with 30s but it's definition is "Timer which hits if no final reply for a request or ACK for a negative INVITE reply arrives (in milliseconds)." and it mentions ACK, but in my case it's an ACK for a final reply that is missing and not an ACK for a negative reply. What other reasons might have caused this transaction to be terminated ? Best Regards

1 0

Re: [SR-Users] Use topos module to hide contact in OPTIONS request
by Enzo 01 Apr '20

01 Apr '20

2 1

Dialog: dlg_var and multi-branch call
by SamyGo 31 Mar '20

31 Mar '20

Hi All, Just curious to ask as how to save $dlg_var for a multi-leg/branched call. When I call a subscriber with multiple Contacts, and one branch answer while rest are CANCEL'd from that point onward I've seen that the dialog and its variables disappear from Kamailio memory and DB.Is this how its intended to be ? Here are the relevant debug line: DEBUG: dialog [dlg_hash.c:1266]: next_state_dlg(): dialog 0x7f7c1461e2e8 changed from state 2 to state 5, due event 4 (ref 2) DEBUG: dialog [dlg_handlers.c:574]: dlg_onreply(): dialog 0x7f7c1461e2e8 failed (negative reply) DEBUG: dialog [dlg_cb.c:271]: run_dlg_callbacks(): dialog=0x7f7c1461e2e8, type=4 DEBUG: dialog [dlg_handlers.c:1050]: dlg_set_tm_waitack(): registering TMCB to wait for negative ACK Best Regard, Sammy

1 0

Can MSRP module relay to multiple destinations?
by Sefa Cebe 31 Mar '20

31 Mar '20

Hello, I'm using Kamailio MSRP module as a MSRP relay, It works successfully when I send one-to-one MSRP messages. I am having trouble while sending msrp messages to multiple receivers. My question is that can I use this module to forward msrp messages not just one receiver, but multiple receivers? Can this module be used like MSRP switch? Thanks in advance.

2 3

Kamailio breaks RFC's 'Contact Header'
by Edward Romanenco 31 Mar '20

31 Mar '20

Description I'm running Kamailio 5.2.0, whenever I relay an invite via Kamailio, my original contact header is changed from the original: sip:+XXXXXXXXX@YYY.YYY.YYY.YYYY:5060;transport=udp;gw=netvision To sip:YYY.YYY.YYY.YYY;line=sr-.n274i0TMfsHMcCAlVyAMV5IlgCXvV8n4edQlgIUlgKQ4Vk74gI1LmZ69NM79FZAR3JC.cDNLfHUj3Wnp3MP9nd*. Even when I set it correctly on my route, using: remove_hf("Contact"); append_hf("Contact: sip:$tU@YYY.YYY.YYY.YYY:5060;transport=udp;gw=netvision\r\n", "Contact"); It still ends up being modified. What can I do to keep the contact header as it is? SIP Traffic U YYY.YYY.YYY.YYY:5060 -> 81.24.193.248:5060 INVITE sip:+442033202609@81.24.193.248:5060 SIP/2.0. Record-Route: <sip:YYY.YYY.YYY.YYY;r2=on;lr=on;ftag=mp0S9yH11vryH;vsf=AAAAAAAAAAAAAAAAAAAAAAADCAEACRgPGB8AAy4xNjM->. Record-Route: <sip:2YYY.YYY.YYY.YYY;line=sr-.n274V8TlidQMVyUlg87vV8nlfDXlVHB9VD0.VHB9VDoLGtNRbH7ltlTEkyQl3jXEky1LNMoRkt5ukt5ukt5ukt5ukt5ukt5ukt5ukt5W8M5WktckoLuWAsduktTMm64pCAD>. Via: SIP/2.0/UDP YYY.YYY.YYY.YYY;branch=z9hG4bK53e9.308596b23ed683368534c9d609dce0f6.0. Via: SIP/2.0/UDP YYY.YYY.YYY.YYY;branch=z9hG4bKsr-kA2uvfsUlerJWtIylgCXvV8n4edQlgIUlgKQ4Vk74gI1.oJVjb2njburlgCXvV8n4edQlgIUlgKQ4HWsRbWPLVDX.GrXLcAHlcC74nZXKbTVpcHh4b6mMGZvJgLsLcJTkgtGu2PGgy**. Max-Forwards: 67. From: +18702935016 <sip:+18702935016@YYY.YYY.YYY.YYY>;tag=mp0S9yH11vryH. To: <sip:+442033202609@81.24.193.248>. Call-ID: !!:jbkfMgyHjbsDjblfjqAQlVldvgyHKolDlcIHlcknKVIdjcIT. CSeq: 18182498 INVITE. Contact: <sip:YYY.YYY.YYY.YYY;line=sr-.n274i0TMfsHMcCAlVyAMV5IlgCXvV8n4edQlgIUlgKQ4Vk74gI1LmZ69NM79FZAR3JC.cDNLfHUj3Wnp3MP9nd*>. User-Agent: FreeSWITCH-mod_sofia/1.9.0+git~20180706T160334Z~de3df8dc0e~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY. Supported: timer, path, replaces. Allow-Events: talk, hold, conference, refer. Content-Type: application/sdp. Content-Disposition: session. Content-Length: 224. Remote-Party-ID: "+18702935016" <sip:+18702935016@YYY.YYY.YYY.YYY>;party=calling;screen=yes;privacy=off. . v=0. o=FreeSWITCH 1585439298 1585439299 IN IP4 ZZZ.ZZZ.ZZZ.ZZZ. s=FreeSWITCH. c=IN IP4 ZZZ.ZZZ

2 3

Re: [SR-Users] How to correctly answer a PnP-SUBSCRIBE message
by Jan-Hendrik Dörner 31 Mar '20

31 Mar '20

Hello Daniel, thank you for your reply. I changed the line mentioned to t_uac_send("NOTIFY", "$(ct{s.substr,1,0}{s.striptail,1})", "$su", "192.168.1.156","Call-ID: $hdr(Call-ID)\r\nSubscription-State: terminated;reason=timeout\r\nEvent: $hdr(Event)\r\nContent-Type: application/url\r\nFrom: $fU\r\nTo: $hdr(From)", "http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D>"); the result is: 3) Call-ID is fine now ; Problem solved :-) 1) The Via IP is now changed to the IP and port of the server, but not to the IP of the phone. 2) The sending interface / IP is not correct: It now sends _only_ from the wrong IP !! As a result, it repeats sending the NOTIFY-message over and over again since the message does not get to the phone ... Please see the starting of the SIP-traffic below U 192.168.1.152:57283 -> 224.0.1.75:5060 #53 SUBSCRIBE sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:57283;rport. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:57283 <sip:192.168.1.152:57283>>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:57283 #54 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:57283;rport=57283;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=fb721cde02dffb6bb099728401306798.1182. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 172.23.56.1:5060 -> 192.168.1.152:57283 #55 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKee8f.0ea476a1000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-9700. CSeq: 10 NOTIFY. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 172.23.56.1:5060 -> 192.168.1.152:57283 #56 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKee8f.0ea476a1000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-9700. CSeq: 10 NOTIFY. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 172.23.56.1:5060 -> 192.168.1.152:57283 #57 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKee8f.0ea476a1000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=176419003. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-9700. CSeq: 10 NOTIFY. Call-ID: 277773303(a)192.168.1.152 <mailto:277773303@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 192.168.1.152:57283 -> 224.0.1.75:5060 #58 SUBSCRIBE sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:57283;rport. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:57283 <sip:192.168.1.152:57283>>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:57283 #59 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:57283;rport=57283;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=fb721cde02dffb6bb099728401306798.1182. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 172.23.56.1:5060 -> 192.168.1.152:57283 #60 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKa0df.967a0433000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-d106. CSeq: 10 NOTIFY. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # U 172.23.56.1:5060 -> 192.168.1.152:57283 #61 NOTIFY sip:192.168.1.152:57283 <sip:192.168.1.152:57283> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.156:5060;branch=z9hG4bKa0df.967a0433000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1472545741. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-d106. CSeq: 10 NOTIFY. Call-ID: 1886698335(a)192.168.1.152 <mailto:1886698335@192.168.1.152>. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> # (If I change the IP-parameter to "172.23.56.1" the resulting sending IP is unchanged!) > Am 30.03.2020 um 16:17 schrieb Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>>: > > Hello, > > On 30.03.20 12:07, Jan-Hendrik Dörner wrote: >> Hallo, >> >> several telephones send a SIP-multicast SUBSCRIBE message to address 224.0.1.75 if they have no settings-URL configured and receive none over DHCP. >> >> So I configure my kamailio server, to respond to that multicast-request. >> But: Although mine is working, I do feel it could be improved, since the NOTIFY packet send out is not quite as it should be … >> >> Here is what I did (the 172.23.56.1 is my voip-vlan-address) >> >> listen=udp:172.23.56.1:5060 advertise 192.168.1.156:5060 >> listen=udp:192.168.1.156:5060 advertise 192.168.1.156:5060 >> listen=tcp:127.0.0.1:5060 >> >> mcast="eth0" >> listen=udp:224.0.1.75:5060 >> >> …. >> >> if ($Ri == "224.0.1.75"){ >> if(is_method("SUBSCRIBE")){ >> xlog("L_INFO", "Received pnp-event from IP $si from User-Agent $hdr(User-Agent) und User $fU\r\n" ); >> sl_send_reply("200", "OK"); >> t_uac_send("NOTIFY", "$(ct{s.substr,1,0}{s.striptail,1})", "", "","Subscription-State: terminated;reason=timeout\r\nEvent: $hdr(Event)\r\nContent-Type: application/url\r\nFrom: $fU\r\nTo: $hdr(From)", "http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D>"); >> }else { >> xlog("L_INFO", "Drop message $rm from pnp-Interface \r\n" ); >> } >> exit; >> } >> >> >> And here are the SIP-packets I see on my server (192.168.1.156) coming from my snom-phone (192.168.1.152). >> My problems with the NOTIFY -packets are: >> 1) How do I set the Via parameters to be the same as in the OK-reply? > > Try to set the next hop address to "$su" and combined with 2) maybe it > results in what you want to get. > > >> 2) How do I send out the NOTIFY only via the 192.168.1.156 network interface? > > Set the local socket parameter from where to send the NOTIFY. > > >> 3) May I send out the NOTIFY with the Call-ID from the SUBSCRIBE message? How? > > > Provide the Call-Id haeder as part of the headers parameter: > > - > https://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_uac_send <https://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.f.t_uac_send> > > Cheers, > Daniel > > >> >> Any help is highly appreciated >> Jan-Hendrik >> >> # >> U 192.168.1.152:58714 -> 224.0.1.75:5060 #258 >> SUBSCRIBE sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan> SIP/2.0. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport. >> From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1750588964. >> To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>. >> Call-ID: 1395386659(a)192.168.1.152 <mailto:1395386659@192.168.1.152>. >> CSeq: 1 SUBSCRIBE. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Expires: 0. >> Accept: application/url. >> Contact: <sip:192.168.1.152:58714 <sip:192.168.1.152:58714>>. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #259 >> SIP/2.0 200 OK. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. >> From: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1750588964. >> To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=fb721cde02dffb6bb099728401306798.2f00. >> Call-ID: 1395386659(a)192.168.1.152 <mailto:1395386659@192.168.1.152>. >> CSeq: 1 SUBSCRIBE. >> Server: kamailio (5.2.5 (x86_64/linux)). >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #260 >> NOTIFY sip:192.168.1.152:58714 <sip:192.168.1.152:58714> SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan <sip:MAC%3a0004137120D8@lan>>;tag=1750588964. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1 <mailto:24eaa8de01be1768-70960@172.23.56.1>. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} <http://server.conf/settings-%7Bmac%7D> >> # >> U 172.23.56.1:5060 -> 192.168.1.152:58714 #261 >> NOTIFY sip:192.168.1.152:58714 SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} >> # >> U 172.23.56.1:5060 -> 192.168.1.152:58714 #262 >> NOTIFY sip:192.168.1.152:58714 SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} >> # >> U 192.168.1.152:58714 -> 224.0.1.75:5060 #263 >> SUBSCRIBE sip:MAC%3a0004137120D8@lan SIP/2.0. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport. >> From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. >> To: <sip:MAC%3a0004137120D8@lan>. >> Call-ID: 1846532696(a)192.168.1.152. >> CSeq: 1 SUBSCRIBE. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Expires: 0. >> Accept: application/url. >> Contact: <sip:192.168.1.152:58714>. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #264 >> SIP/2.0 200 OK. >> Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. >> From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. >> To: <sip:MAC%3a0004137120D8@lan>;tag=fb721cde02dffb6bb099728401306798.2f00. >> Call-ID: 1846532696(a)192.168.1.152. >> CSeq: 1 SUBSCRIBE. >> Server: kamailio (5.2.5 (x86_64/linux)). >> Content-Length: 0. >> . >> >> # >> U 192.168.1.156:5060 -> 192.168.1.152:58714 #265 >> NOTIFY sip:192.168.1.152:58714 SIP/2.0. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0. >> To: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. >> From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. >> CSeq: 10 NOTIFY. >> Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. >> Max-Forwards: 70. >> Content-Length: 33. >> User-Agent: kamailio (5.2.5 (x86_64/linux)). >> Subscription-State: terminated;reason=timeout. >> Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". >> Content-Type: application/url. >> . >> http://server.conf/settings-{mac} >> # >> U 192.168.1.152:58714 -> 192.168.1.156:5060 #266 >> SIP/2.0 200 Ok. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. >> From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> CSeq: 10 NOTIFY. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.152:58714 -> 192.168.1.156:5060 #267 >> SIP/2.0 200 Ok. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. >> From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. >> To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. >> Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. >> CSeq: 10 NOTIFY. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> # >> U 192.168.1.152:58714 -> 192.168.1.156:5060 #268 >> SIP/2.0 200 Ok. >> Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0;received=192.168.1.156. >> From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. >> To: <sip:MAC%3A0004137120D8@lan>;tag=1971605806. >> Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. >> CSeq: 10 NOTIFY. >> User-Agent: snom760/8.9.3.80. >> Content-Length: 0. >> . >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> > > -- > Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com/> > www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>

2 4

P-CSCF Error - help required asap
by Pavithra N M 30 Mar '20

30 Mar '20

Hi, I am facing the below error in my P-CSCF module as i am running P-CSCF, I-CSCF, S-CSCF, HSS in separate VMs. 0(3512) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(3512) ERROR: <script>: event_route[htable:mod-init] { 1(3513) ERROR: rtpengine [rtpengine.c:2839]: send_rtpp_command(): can't send command "ping" to RTP proxy <udp:localhost:9910> 1(3513) ERROR: rtpengine [rtpengine.c:2740]: rtpp_test(): proxy did not respond to ping 1(3513) ERROR: rtpengine [rtpengine.c:2839]: send_rtpp_command(): can't send command "ping" to RTP proxy <udp:localhost:9911> 1(3513) ERROR: rtpengine [rtpengine.c:2740]: rtpp_test(): proxy did not respond to ping 68(3637) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 72(3644) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 73(3645) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 69(3641) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 75(3653) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 71(3643) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/3643 77(3655) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 76(3654) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 74(3652) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 79(3657) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing root@tel-VirtualBox:/etc/kamailio/pcscf# 78(3656) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB connection already open... continuing 69(3641) ERROR: *** cfgtrace:request_route=[NATPING] c=[/etc/kamailio/pcscf/kamailio.cfg] l=836 a=5 n=route 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=895 a=16 n=if 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=895 a=63 n=assign 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=897 a=27 n=sql_query 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] l=898 a=25 n=xlog 69(3641) ERROR: <script>: Preloading NAT-PING. Rows: 0 69(3641) ERROR: *** cfgtrace:request_route=[preload_pcscf] c=[/etc/kamailio/pcscf/kamailio.cfg] kindly help me in this issue of how to configure the rtp proxy or even if it is not required for basic configuration,let me know the procedure to comment this part or the procedure to take it forward to run P-CSCF without any errors. Kindly help me in this regard. Thanks Best Regards Pavithra M Tata Elxsi [cid:7ca5c450-5bb2-4d74-85ab-1c3e16346e2e] ________________________________ Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version. ________________________________

1 0

How to correctly answer a PnP-SUBSCRIBE message
by Jan-Hendrik Dörner 30 Mar '20

30 Mar '20

Hallo, several telephones send a SIP-multicast SUBSCRIBE message to address 224.0.1.75 if they have no settings-URL configured and receive none over DHCP. So I configure my kamailio server, to respond to that multicast-request. But: Although mine is working, I do feel it could be improved, since the NOTIFY packet send out is not quite as it should be … Here is what I did (the 172.23.56.1 is my voip-vlan-address) listen=udp:172.23.56.1:5060 advertise 192.168.1.156:5060 listen=udp:192.168.1.156:5060 advertise 192.168.1.156:5060 listen=tcp:127.0.0.1:5060 mcast="eth0" listen=udp:224.0.1.75:5060 …. if ($Ri == "224.0.1.75"){ if(is_method("SUBSCRIBE")){ xlog("L_INFO", "Received pnp-event from IP $si from User-Agent $hdr(User-Agent) und User $fU\r\n" ); sl_send_reply("200", "OK"); t_uac_send("NOTIFY", "$(ct{s.substr,1,0}{s.striptail,1})", "", "","Subscription-State: terminated;reason=timeout\r\nEvent: $hdr(Event)\r\nContent-Type: application/url\r\nFrom: $fU\r\nTo: $hdr(From)", "http://server.conf/settings-{mac}"); }else { xlog("L_INFO", "Drop message $rm from pnp-Interface \r\n" ); } exit; } And here are the SIP-packets I see on my server (192.168.1.156) coming from my snom-phone (192.168.1.152). My problems with the NOTIFY -packets are: 1) How do I set the Via parameters to be the same as in the OK-reply? 2) How do I send out the NOTIFY only via the 192.168.1.156 network interface? 3) May I send out the NOTIFY with the Call-ID from the SUBSCRIBE message? How? Any help is highly appreciated Jan-Hendrik # U 192.168.1.152:58714 -> 224.0.1.75:5060 #258 SUBSCRIBE sip:MAC%3a0004137120D8@lan SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:58714;rport. From: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. To: <sip:MAC%3a0004137120D8@lan>. Call-ID: 1395386659(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:58714>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #259 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. To: <sip:MAC%3a0004137120D8@lan>;tag=fb721cde02dffb6bb099728401306798.2f00. Call-ID: 1395386659(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #260 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 172.23.56.1:5060 -> 192.168.1.152:58714 #261 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 172.23.56.1:5060 -> 192.168.1.152:58714 #262 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1750588964. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 192.168.1.152:58714 -> 224.0.1.75:5060 #263 SUBSCRIBE sip:MAC%3a0004137120D8@lan SIP/2.0. Via: SIP/2.0/UDP 192.168.1.152:58714;rport. From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. To: <sip:MAC%3a0004137120D8@lan>. Call-ID: 1846532696(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Expires: 0. Accept: application/url. Contact: <sip:192.168.1.152:58714>. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #264 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.152:58714;rport=58714;received=192.168.1.152. From: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. To: <sip:MAC%3a0004137120D8@lan>;tag=fb721cde02dffb6bb099728401306798.2f00. Call-ID: 1846532696(a)192.168.1.152. CSeq: 1 SUBSCRIBE. Server: kamailio (5.2.5 (x86_64/linux)). Content-Length: 0. . # U 192.168.1.156:5060 -> 192.168.1.152:58714 #265 NOTIFY sip:192.168.1.152:58714 SIP/2.0. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0. To: <sip:MAC%3a0004137120D8@lan>;tag=1971605806. From: <MAC%3a0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. CSeq: 10 NOTIFY. Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. Max-Forwards: 70. Content-Length: 33. User-Agent: kamailio (5.2.5 (x86_64/linux)). Subscription-State: terminated;reason=timeout. Event: ua-profile;profile-type="device";vendor="snom";model="snom760";version="8.9.3.80". Content-Type: application/url. . http://server.conf/settings-{mac} # U 192.168.1.152:58714 -> 192.168.1.156:5060 #266 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. CSeq: 10 NOTIFY. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.152:58714 -> 192.168.1.156:5060 #267 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bKf21c.917eaf36000000000000000000000000.0;received=192.168.1.156. From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-8cfb. To: <sip:MAC%3A0004137120D8@lan>;tag=1750588964. Call-ID: 24eaa8de01be1768-70960(a)172.23.56.1. CSeq: 10 NOTIFY. User-Agent: snom760/8.9.3.80. Content-Length: 0. . # U 192.168.1.152:58714 -> 192.168.1.156:5060 #268 SIP/2.0 200 Ok. Via: SIP/2.0/UDP 224.0.1.75;branch=z9hG4bK201a.063839a4000000000000000000000000.0;received=192.168.1.156. From: <MAC:0004137120D8>;tag=da567df9df3ac234e43969a051db4641-f31b. To: <sip:MAC%3A0004137120D8@lan>;tag=1971605806. Call-ID: 24eaa8de01be1768-70963(a)172.23.56.1. CSeq: 10 NOTIFY. User-Agent: snom760/8.9.3.80. Content-Length: 0. .

2 1

setting $du in branch route has no effect in 5.3
by Juha Heinanen 30 Mar '20

30 Mar '20

I noticed that in 5.3 and master setting $du in branch route has no effect. It works fine in 5.2 using exactly the same config. -- Juha

2 12

Problem faced when Using Kamaiio as Session Refresher
by harneet singh 30 Mar '20

30 Mar '20

Hi, I am fairly new to Kamailio and had a question regarding how to use Kamailio to enable Session refresh functionality when Kamailio is acting as Sip Stateful Proxy. Kamailio Version used: *5.3.2* with *Call Load based routing* using the *dispatcher *module. * From what i understand from the documentation, Kamailio will probably not be acting as a session refresher, but Kamailio can tear down the call in case session refresh is negotiated, between the caller and the callee(via Kamailio Sip Proxy), and no message exchange happens in the duration set in Session-Expires header. *Is my understanding correct?* ** *I believe the above functionality is possible by using the *sst* and *dialog* module. I have set the same according to the documentation but I keep getting the following error: "dialog [dlg_handlers.c:681]: *get_dlg_timeout(): invalid AVP value, using default timeout*" Can someone share a working example? * When i tried hardcoding the timeout value by setting the timeout_avp to a specific value, Kamailio did sense a timeout and hence sent a BYE towards the caller and the Callee side both(which is what the requirement is), however, i do see the *dialog is still not cleared* in the "kamcmd dispatcher.list". Output excerpt below for reference: [root@CPaaSVM ~]# kamcmd dispatcher.list { NRSETS: 1 RECORDS: { SET: { ID: 1 TARGETS: { DEST: { URI: sip:172.27.44.121:5080 ;transport=tcp FLAGS: AP PRIORITY: 0 ATTRS: { BODY: duid=sample-cas;maxload=1000 DUID: sample-cas MAXLOAD: 1000 WEIGHT: 0 RWEIGHT: 0 SOCKET: } LATENCY: { AVG: 111.304000 STD: 1042.193000 EST: 2.385000 MAX: 9999 TIMEOUT: 1 } RUNTIME: { DLGLOAD: *1* } } } } } } It is noteworthy that in case the BYE is initiated by either the caller or the callee, the dialog is cleared properly and the DLGLOAD is set to 0 on call termination. Any pointers for the above questions would be highly appreciated. Regards, Harneet -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

3 17

Transaction Matching Failed - ACK BYE
by egemen ulus 29 Mar '20

29 Mar '20

Hi All, I'm trying to establish a topology with Kamailio which is located between Asterisk and Outside. My issue is "transaction matching failed" (t_check_trans failed). That means Kamailio does not recognise ACK & BYE message to forwards. I had a check on email list and google but found nothing. I'm using it with record_route. SIP signalling and part of kamailio.cfg is below. Is there any suggestion? route[WITHINDLG] { if (!has_totag()) return; if (loose_route()) { route(DLGURI); if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if ( is_method("ACK") ) { xlog("ack is came: $si:$sp\n"); route(NATMANAGE); } else if ( is_method("NOTIFY") ) { record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { route(RELAY); exit; } else { exit; } } sl_send_reply("404","Not here"); exit; } route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } route(RTPPROXY); if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) set_contact_alias(); } } #!endif return; } Asterisk > Kamailio INVITE sip:user@outside_ip SIP/2.0 Via: SIP/2.0/UDP asterisk_ip:5060;branch=z9hG4bK1b56cce0 Max-Forwards: 70 From: "KUYRUK" <sip:0553847<tel:+10553847>aaaa@asterisk_ip>;tag=as3dde7cdb To: <sip:user@outside_ip> Contact: <sip:0553847<tel:+10553847>aaaa@asterisk_ip:5060> Call-ID: 62a480bf71d2a1aa0ec94b454cd98945@asterisk_ip:5060 CSeq: 102 INVITE User-Agent: Asterisk PBX 1.8.32.3 Kamailio > Outside INVITE sip:user@outside_ip SIP/2.0 Record-Route: <sip:kamailio_ip;lr;nat=yes> Via: SIP/2.0/UDP kamailio_ip;branch=z9hG4bK7b3f.8e4716eeea4b0dc45cc51d21b5aded57.0 Via: SIP/2.0/UDP asterisk_ip:5060;rport=5060;branch=z9hG4bK1b56cce0 From: "KUYRUK" <sip:0553847<tel:+10553847>aaaa@asterisk_ip>;tag=as3dde7cdb To: <sip:user@outside_ip> Contact: <sip:0553847<tel:+10553847>aaaa@asterisk_ip:5060;alias=asterisk_ip~5060~1> Call-ID: 62a480bf71d2a1aa0ec94b454cd98945@asterisk_ip:5060 CSeq: 102 INVITE User-Agent: Asterisk PBX 1.8.32.3 Outside > Kamailio SIP/2.0 200 OK Via: SIP/2.0/UDP kamailio_ip;branch=z9hG4bK7b3f.8e4716eeea4b0dc45cc51d21b5aded57.0 Via: SIP/2.0/UDP asterisk_ip:5060;rport=5060;branch=z9hG4bK1b56cce0 From: "KUYRUK" <sip:0553847<tel:+10553847>aaaa@asterisk_ip>;tag=as3dde7cdb To: <sip:user@outside_ip>;tag=kv8iml6ur9 Call-ID: 62a480bf71d2a1aa0ec94b454cd98945@asterisk_ip:5060 CSeq: 102 INVITE Record-Route: <sip:kamailio_ip;lr;nat=yes> Contact: <sip:user@outside_ip:5060;alias=x.x.x.x~18005~6;transport=udp> Kamailio > Asterisk SIP/2.0 200 OK Via: SIP/2.0/UDP asterisk_ip:5060;rport=5060;branch=z9hG4bK1b56cce0 From: "KUYRUK" <sip:0553847<tel:+10553847>aaaa@asterisk_ip>;tag=as3dde7cdb To: <sip:user@outside_ip>;tag=kv8iml6ur9 Call-ID: 62a480bf71d2a1aa0ec94b454cd98945@asterisk_ip:5060 CSeq: 102 INVITE Record-Route: <sip:kamailio_ip;lr;nat=yes> Contact: <sip:user@outside_ip:5060;alias=x.x.x.x~18005~6;transport=udp> Asterisk > Kamailio THIS ACK IS NOT ROUTED TO OUTSIDE BY KAMAILIO!! ACK sip:user@outside_ip:5060;alias=x.x.x.x~18005~6;transport=udp SIP/2.0 Via: SIP/2.0/UDP asterisk_ip:5060;branch=z9hG4bK73366924 Route: <sip:kamailio_ip;lr;nat=yes> From: "KUYRUK" <sip:0553847<tel:+10553847>aaaa@asterisk_ip>;tag=as3dde7cdb To: <sip:user@outside_ip>;tag=kv8iml6ur9 Contact: <sip:0553847<tel:+10553847>aaaa@asterisk_ip:5060> Call-ID: 62a480bf71d2a1aa0ec94b454cd98945@asterisk_ip:5060 CSeq: 102 ACK User-Agent: Asterisk PBX 1.8.32.3 Get Outlook for Android<https://aka.ms/ghei36>

2 6

Kamailiio TLS and Let'sEncrypt certs
by Igor Olhovskiy 29 Mar '20

29 Mar '20

Hi! Actually I’m trying to get Kamailio to work as MS Teams SBC following by perfect article https://skalatan.de/en/blog/kamailio-sbc-teams <https://skalatan.de/en/blog/kamailio-sbc-teams> It works well, but one thing is bothering me. I’m using Let’sEncrypt certs (actually, works well), but with setting in tls.conf verify_certificate = yes require_certificate = yes It’s giving an errors like /usr/sbin/kamailio[4551]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed /usr/sbin/kamailio[4551]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f03e6d23d88 r: 0x7f03e6d23e08 (-1) They are resolved with setting these settings (verify/require) to off (actually, as mentioned here - https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/ <https://www.fredposner.com/1836/kamailio-tls-and-letsencrypt/>), but I’m really curious - why? As I got, it’s using openssl verify on a background, but this check locally passed with openssl verify -CAfile issuer.crt myserver.crt myserver.crt: OK So, is there any tricks to lets encrypt or just some misconfig in tls.cfg? Now it looks like one from article [server:default] method = TLSv1.2+ verify_certificate = yes require_certificate = yes private_key = /etc/kamailio/tls/myserver.key certificate = /etc/kamailio/tls/myserver.crt ca_list = /etc/kamailio/tls/issuer.crt [client:default] method = TLSv1.2+ verify_certificate = yes require_certificate = yes private_key = /etc/kamailio/tls/myserver.key certificate = /etc/kamailio/tls/myserver.crt ca_list = /etc/kamailio/tls/issuer.crt — Regards, Igor

3 3

Kamailio OPTIONS Round-Trip
by Soltanici Ilie 27 Mar '20

27 Mar '20

Hi, With Asterisk, we are able to get some peer round-trip connection statistic by setting qualify=yes for the specified peer. It sends periodic OPTIONS to the peer and calculates the time round trip time. It's something like - "Status: OK (30 ms)". Is there any way to achieve this in Kamailio by using nathelper module, or any other? Thank you.

9 13

Segmentation fault in DMQ module
by Virgílio Cunha 27 Mar '20

27 Mar '20

Hello, I have in production environment with 4 proxies using DMQ to sync terminal registers and the DMQ configuration parameters is following: loadmodule "dmq.so" #modparam("dmq", "server_address", "sip:MY_IP_ADDRESS:MY_PORT_ADDRESS") modparam("dmq", "notification_address", "DMQ_HOSTS") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) In the lab environment with the same configuration that in prod, I can simulate this problem with 12000 terminal REGISTERS and, when doing several restarts on a proxy, one of them is generated a coredump. Analyzing the core, I can see that the problem is concurrency in the dmq synchronization. Job_queue_size (...) is called with a valid *queue *and, but inside this function, the *queue *is null. (gdb) up #1 0x00007fefe58ee246 in job_queue_size (queue=0x0) at worker.c:254 254 return atomic_get(&queue->count); (gdb) print queue $1 = (job_queue_t *) 0x0 (gdb) up #2 0x00007fefe58ed920 in add_dmq_job (msg=0x7ff028b453f8, peer=0x7fefebcc4df8) at worker.c:184 184 if(job_queue_size(workers[i].queue) == 0) { (gdb) print i $2 = 1 (gdb) print workers[i].queue $3 = (job_queue_t *) 0x7fefebce49b0 If I configure DMQ with num_workers=1 I can't reproduce this problem. I'm using the kamailio 5.0.8 release. Is this problem known to you? What is the right way to solve it? Best Regards, Virgílio Cunha

3 7

Multiple advertise addresses per socket
by Sergiu Pojoga 25 Mar '20

25 Mar '20

Hi there, Question: how can I advertise and later match multiple FQDNs per socket? Example: auto_aliases=no alias="mydomain.net":5060 alias="mydomain.net":5061 alias="client1.mydomain.net":5060 alias="client1.mydomain.net":5061 # looks like I can advertise only one address per socket? listen=udp:65.65.65.65:5060 advertise "mydomain.net":5060 listen=tls:65.65.65.65:5061 advertise "mydomain.net":5061 Adding RR before relaying downstream like so: record_route_preset("client1.mydomain.net:5061;transport=tls;r2=on", "client1.mydomain.net:5060;r2=on"); This is the warning (just warning, works fine otherwise) after receiving for example the ACK from upstream following the 200 OK: *WARNING*: {1 19082 ACK } rr [loose.c:768]: rr_do_force_send_socket(): no socket found to match second RR (sip:client1.mydomain.net:5061 ;transport=tls;lr;r2=on) Figured warning itself can be turned off with modparam "enable_socket_mismatch_warning" of RR, still I'd like to know if I'm doing something wrong or there's a better way. Much obliged, --Sergiu

2 3

Kamailio 5.3.2 - Signal 11 on startup
by José Seabra 25 Mar '20

25 Mar '20

Hello there, I'm facing an issue with kamailio 5.3.2 when it is starting up, it breaks with signal 11 and generates a coredump file: - https://pastebin.com/FSqyGFp8 This seems to be something related to dmq module, kamailio exits with signal 11 when it receives a DMQ notification_peer message. I did a few more tests and I noticed that problem disappears if I configure DMQ with one worker only, which takes me to think that it's something related to concurrency. Best regards -- Cumprimentos José Seabra

2 7

about kamailio.cfg NAT test
by Juha Heinanen 24 Mar '20

24 Mar '20

In kamailio/etc/kamailio.cfg NAT test is based on nat_uac_test("19"). 19 includes test 16: 16 - Test if the source port is different from the port in the “Via” header. If the “Via” header contains no port, it uses the default SIP port 5060 Based on a couple of tests using baresip, looks like that results in false positive when UA connects to SIP proxy via TCP. An example: T 2020/03/24 13:57:12.685441 192.26.134.10:38940 -> 192.26.134.1:5060 [AP] #127 REGISTER sip:test.tutpro.com SIP/2.0. Via: SIP/2.0/TCP 192.26.134.10:44717;branch=z9hG4bK5b6aa423104ef942;rport. Does someone know why test 16 is included? -- Juha

3 5

Transformations - urlencode
by João Vitor Arruda 24 Mar '20

24 Mar '20

Hello, I was looking in the transformation documentation ( https://www.kamailio.org/wiki/cookbooks/devel/transformations) something to URL encode a pv or var for use in a HTTP query but was not able to find it. Digging a bit in the source code I found that "s.urlencode.param" actually exists and from my initial tests it works just fine. I'm wondering if there is any reason why this is not mentioned in the documentation of if it should not be used at all. Thanks, Joao Arruda

3 3

Manipulating contacts header results in a malformed SIP packet
by Andrew White 23 Mar '20

23 Mar '20

Hi all, Hope everyone is well, and looking forward to seeing you all whenever Kamailio World ends up being! I’m currently dealing with an issue which I’m unsure if it’s due to my own implementation, or a bug. When attempting to manipulate the Contact header via app_ruby, the SIP message I send ends up being malformed. Here’s the code I’m using: def replace_contact_header(uri) #KSR::HDR.remove("Contact") if KSR::HDR.is_present('Contact') > 0 #KSR::HDR.append("Contact: #{uri}\r\n") KSR::HDR.rmappend("Contact", "Contact: #{uri}\r\n") end Note that I have tried both rmappend and the commented out functions too. I call this with a custom built URI, such as <61400123123(a)kamailio.test.uconnected.com.au <mailto:61400123123@kamailio.test.uconnected.com.au>>. This function is called just before a KSR::TM.t_relay(). Here’s the result I get watching from tshark (some info scrubbed for privacy): Record-Route: <sip:1.2.3.4;lr;ftag=e3p42efd3635HH;vst=AAAAAAAAAAAAAAAAAAAAAAoUXVFHDQAAs83AEGwAAFgwCQA8QY3RlZC5jb20uYXU-;did=927.f0f2> … Call-ID: 3de29646-e423-1238-e712-023563fb337c CSeq: 17736747 INVITE sip:4.5.6.7:5060;alias=10.100.1.1~5060~1Content-Type: application/sdp Content-Length: 483 Contact: <sip:61400123123@kamailio.test.uconnected.com.au> In this case, 4.5.6.7 is the PBX I made the call from (and the value of the original Contact header), and 1.2.3.4 is what kamailio.test.uconnected.com.au <http://kamailio.test.uconnected.com.au/> resolves to, and is this Kamailio instance. Here’s a copy of the same thing when I don’t call my replace_contact_header function and t_relay: Record-Route: <sip:1.2.3.4;lr;ftag=j6jebCSa5Qap6c;vst=AAAAAAAAAAAAAAAAAAAAAAoUXVND38dTgwEGEAEGwAAFgwCQA8Fdn83lZC5jb20uYXU-;did=827.40b> ... Call-ID: 249571c5-e91a-ae91-6d8e-023563fb337c CSeq: 17735867 INVITE Contact: <sip:4.5.6.7:5060;alias=10.100.1.1~5060~1> Content-Type: application/sdp Content-Length: 483 Given the relative simplicity of the function, I have to assume this is an error with how the function is manipulating the existing Contact header? It seems that the “Contact: <“ part of the header is being removed as well as the “>\r\n", but the rest being left. I’m currently using commit 283e468401d809ca9b71368c32badf3a70d48b8b <https://github.com/kamailio/kamailio/commit/283e46> on Amazon Linux 2, which is CentOS/RHEL based. Thanks! Andrew

5 7

Pike Module Clarification
by JR Richardson 23 Mar '20

23 Mar '20

Hi All, Please clarify the pike settings for SIP message count, the module Doc reports: ---- modparam("pike", "sampling_time_unit", 10) modparam("pike", "reqs_density_per_unit", 30) How many requests should be allowed per sampling_time_unit before blocking all the incoming request from that IP. Practically, the blocking limit is between ( let's have x=reqs_density_per_unit) x and 3*x for IPv4 addresses and between x and 8*x for IPv6 addresses. ----- So the example above the SIP message rate is 30 messages within 10 seconds triggers an pike alert? The description I'm confused on is "Practically, the blocking 'limit is between' (let's have x=reqs_density_per_unit) x and 3*x for IPv4" The way this reads to me is the Pike alert could be triggered anywhere between 30 and 90 (3*30) messages within 10 second period. Am I reading this correctly? What determines when the pike trigger actually happens, could the trigger happen at say 56 messages within 10 seconds? Thanks. JR Richardson Engineering for the Masses Chasing the Azeotrope JRx DistillCo 1'st Place Brisket 1'st Place Chili

4 7

set_advertised_address not accepting vars
by Sergiu Pojoga 22 Mar '20

22 Mar '20

Hi there, The function doesn't appear to accept vars. For example, set_advertised_address("$var(someaddress)") results in a VIA of string $var(someaddress), instead of var's value. https://www.kamailio.org/wiki/cookbooks/5.3.x/core#set_advertised_address kamailio 5.3.2 (x86_64/linux) 0bed10 Cheers. --Sergiu

3 3

pipelimit: inexistent pipe error logs
by Nuno Ferreira 20 Mar '20

20 Mar '20

Hi all, I'm using pipelimit with the "clean_unused" option to get rid of pipes that are not used for quite some time. At the same time we are monitoring pipelimit with a jsonrpc call similar to: # curl --header 'Content-Type: application/json' --data-binary '{"id": 1, "jsonrpc": "2.0", "method": "pl.list", "params": ["pipe_INVITE"]' http://127.0.0.1:8000/RPC Reply: { "jsonrpc": "2.0", "error": { "code": 400, "message": "Unknown pipe id pipe_INVITE" }, "id": 1 } The above reply is valid because the pipe_INVITE was not loaded yet, but the request makes kamailio to log the following log messages: Jan 20 11:21:48 proxy1 kamailio[24474]: ERROR: pipelimit [pl_ht.c:519]: rpc_pl_list(): no pipe: pipe_INVITE Jan 20 11:21:48 proxy1 kamailio[24474]: ERROR: <core> [core/parser/parse_fline.c:262]: parse_first_line(): parse_first_line: bad message (offset: 20) Jan 20 11:21:48 proxy1 kamailio[24474]: [466B blob data] Since the monitoring system does periodic requests, those log lines get a bit annoying and fill the log with ERROR messages that aren't really errors. IMHO the first log line should be converted to DEBUG instead of ERROR, but I have some doubts about the one from parse_fline.c:262. parse_first_line() is used to process both SIP and HTTP. It makes sense to log ERROR if SIP but not in the case of HTTP... Regarding the "[466B blob data]" I really don't know from where it's coming from. I can submit a PR, but I would like to have first some feedback from you. Thank you, Nuno -- *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.*

3 10

is_gflag Always Returns FALSE
by Yufei Tao 20 Mar '20

20 Mar '20

Hi, I got some problems with is_gflags: 1. Set the gflag: # kamcmd cfgutils.set_gflag 1024 2. Check the gflags - fine: # kamcmd cfgutils.get_gflags 0x400 (1024) 3. Check using is_gflag - problem: # kamcmd cfgutils.is_gflag 1024 FALSE Seems is_gflag always returns FALSE somehow. Calling function is_gflag() from the cfg file seems to always return FALSE too. I tried this on Kamailio 5.3.2 and 5.3.3 and the behaviour is the same. Best regards, Yufei

2 5

OPTIONS sent from the wrong IP
by David Villasmil 19 Mar '20

19 Mar '20

Hello, It seems kamailio is selecting the local ip wrongly when selecting the socket with which to send out OPTIONS. This is 5.2.3, and i have multiple IPs Listen=ip1 (private) Listen=ip2 (public) And when the options goes out, it goes via the first ip instead of the one through which it can reach the OPTIONS destination (public IP). I have mhomed=1 set This is using dispatcher. Has anyone seen this behaviour? Thanks all David -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 4

unknown error messages
by Juha Heinanen 19 Mar '20

19 Mar '20

It turned out that the unknown error messages were produced by process 32058 that was not in ctl ps list at all. So it must have survived alive from a previous restart of K. Question: how it is possible that a tcp worker that does not belong to the current running K instance gets to service a json rpc request? -- Juha

2 2

raise of inuse_transactions after enabled dispatcher probing
by Michal Popovic 18 Mar '20

18 Mar '20

Hi, after I have enabled dispatcher probing with OPTIONS, tmx statistic inuse_transactions reports constantly multiple existing transactions per checked server. Is this normal behaviour or could it be any sign of potential issue? Thanks. Michal

2 4

Re: [SR-Users] Kamailio release policy
by Henning Westerholt 18 Mar '20

18 Mar '20

Hi Virgilio, there is a page in the old wiki: https://www.kamailio.org/dokuwiki/doku.php/development:release-policy about it. Basically, the last two stable version are supported. We release roughly every 10-12 month a new major release, the next one probably this summer (e.g. 5.4.0). I estimate the 5.3 branch will be maintained until roughly second/third quarter of 2021, so there is still plenty of time. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Virgílio Cunha Sent: Wednesday, March 18, 2020 7:23 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] Segmentation fault in DMQ module Hi, Sorry for using this topic for this question, but where can I find Kamailio's release policy? I needed to know how long the kamailio 5.3.x branch will maintain its support. Best Regards, Virgílio Cunha Em ter., 17 de mar. de 2020 às 11:03, Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> escreveu: Hello, if it is a runtime issue, then it is better to upgrade to a supported release series and try to reproduce it. Looking at startup/shutdown code is easier than the rest used during runtime by a module, but it is not the case here. So we may waste a lot of time to dig into it and discover it was fixed or the code in an older release was refactored not matching any longer what is now in stable releases. Cheers, Daniel On 17.03.20 11:35, Virgílio Cunha wrote: Hi, The problem does not just occur when kamailio is restarted. The restart was the way I found to reproduce the problem, because when a proxy is restarted, there is more traffic from DMQ messages, so the problem is more likely to occur. The full backtrace is following: GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /opt/ptin/kamailio-ksipadp/bin/ksipadp-proxy...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New Thread 506] Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /usr/lib64/kamailio/modules/db_postgres.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/db_postgres.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/db_postgres.so Reading symbols from /usr/lib64/libpq.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libpq.so.5 Reading symbols from /usr/lib64/kamailio/libsrdb2.so.1...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/libsrdb2.so.1.0.debug...done. done. Loaded symbols for /usr/lib64/kamailio/libsrdb2.so.1 Reading symbols from /usr/lib64/kamailio/libsrdb1.so.1...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/libsrdb1.so.1.0.debug...done. done. Loaded symbols for /usr/lib64/kamailio/libsrdb1.so.1 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libldap_r-2.4.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libldap_r-2.4.so.2 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/liblber-2.4.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/liblber-2.4.so.2 Reading symbols from /usr/lib64/libsasl2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libsasl2.so.2 Reading symbols from /usr/lib64/libssl3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl3.so Reading symbols from /usr/lib64/libsmime3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libsmime3.so Reading symbols from /usr/lib64/libnss3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libnss3.so Reading symbols from /usr/lib64/libnssutil3.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libnssutil3.so Reading symbols from /lib64/libplds4.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libplds4.so Reading symbols from /lib64/libplc4.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libplc4.so Reading symbols from /lib64/libnspr4.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libnspr4.so Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libcrypt.so.1 Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/librt.so.1 Reading symbols from /lib64/libfreebl3.so...(no debugging symbols found)...done. Loaded symbols for /lib64/libfreebl3.so Reading symbols from /usr/lib64/kamailio/modules/ctl.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/ctl.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/ctl.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Reading symbols from /usr/lib64/kamailio/modules/kex.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/kex.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/kex.so Reading symbols from /usr/lib64/kamailio/libsrutils.so.1...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/libsrutils.so.1.0.debug...done. done. Loaded symbols for /usr/lib64/kamailio/libsrutils.so.1 Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /usr/lib64/kamailio/modules/tm.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/tm.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/tm.so Reading symbols from /usr/lib64/kamailio/modules/tmx.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/tmx.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/tmx.so Reading symbols from /usr/lib64/kamailio/modules/corex.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/corex.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/corex.so Reading symbols from /usr/lib64/kamailio/modules/cfg_rpc.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/cfg_rpc.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/cfg_rpc.so Reading symbols from /usr/lib64/kamailio/modules/sl.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/sl.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/sl.so Reading symbols from /usr/lib64/kamailio/modules/rr.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/rr.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/rr.so Reading symbols from /usr/lib64/kamailio/modules/maxfwd.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/maxfwd.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/maxfwd.so Reading symbols from /usr/lib64/kamailio/modules/siputils.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/siputils.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/siputils.so Reading symbols from /usr/lib64/kamailio/modules/sanity.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/sanity.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/sanity.so Reading symbols from /usr/lib64/kamailio/modules/textops.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/textops.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/textops.so Reading symbols from /usr/lib64/kamailio/modules/textopsx.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/textopsx.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/textopsx.so Reading symbols from /usr/lib64/kamailio/modules/dmq.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dmq.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dmq.so Reading symbols from /usr/lib64/kamailio/modules/htable.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/htable.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/htable.so Reading symbols from /usr/lib64/kamailio/modules/pv.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/pv.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/pv.so Reading symbols from /usr/lib64/kamailio/modules/xlog.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/xlog.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/xlog.so Reading symbols from /usr/lib64/kamailio/modules/jsonrpcs.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/jsonrpcs.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/jsonrpcs.so Reading symbols from /usr/lib64/kamailio/modules/uac.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/uac.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/uac.so Reading symbols from /usr/lib64/kamailio/modules/uac_redirect.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/uac_redirect.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/uac_redirect.so Reading symbols from /usr/lib64/kamailio/modules/db_text.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/db_text.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/db_text.so Reading symbols from /usr/lib64/kamailio/modules/dispatcher.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dispatcher.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dispatcher.so Reading symbols from /usr/lib64/kamailio/modules/sqlops.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/sqlops.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/sqlops.so Reading symbols from /usr/lib64/kamailio/modules/regex.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/regex.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/regex.so Reading symbols from /lib64/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libpcre.so.0 Reading symbols from /usr/lib64/kamailio/modules/permissions.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/permissions.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/permissions.so Reading symbols from /usr/lib64/kamailio/modules/dialplan.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dialplan.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dialplan.so Reading symbols from /usr/lib64/kamailio/modules/mtree.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/mtree.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/mtree.so Reading symbols from /usr/lib64/kamailio/modules/cfgutils.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/cfgutils.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/cfgutils.so Reading symbols from /usr/lib64/kamailio/modules/statsd.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/statsd.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/statsd.so Reading symbols from /usr/lib64/kamailio/modules/app_lua.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/app_lua.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/app_lua.so Reading symbols from /usr/lib64/liblua-5.1.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/liblua-5.1.so<http://liblua-5.1.so> Reading symbols from /usr/lib64/kamailio/modules/rtimer.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/rtimer.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/rtimer.so Reading symbols from /usr/lib64/kamailio/modules/mqueue.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/mqueue.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/mqueue.so Reading symbols from /usr/lib64/kamailio/modules/auth.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/auth.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/auth.so Reading symbols from /usr/lib64/kamailio/modules/usrloc.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/usrloc.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/usrloc.so Reading symbols from /usr/lib64/kamailio/modules/registrar.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/registrar.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/registrar.so Reading symbols from /usr/lib64/kamailio/modules/dmq_usrloc.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/dmq_usrloc.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/dmq_usrloc.so Reading symbols from /usr/lib64/kamailio/modules/xhttp.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/xhttp.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/xhttp.so Reading symbols from /usr/lib64/kamailio/modules/exec.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/exec.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/exec.so Reading symbols from /usr/lib64/kamailio/modules/http_client.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/http_client.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/http_client.so Reading symbols from /usr/lib64/libxml2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libxml2.so.2 Reading symbols from /usr/lib64/libcurl.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcurl.so.4 Reading symbols from /lib64/libidn.so.11...(no debugging symbols found)...done. Loaded symbols for /lib64/libidn.so.11 Reading symbols from /lib64/libldap-2.4.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libldap-2.4.so.2 Reading symbols from /usr/lib64/libssh2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssh2.so.1 Reading symbols from /usr/lib64/kamailio/modules/json.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/json.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/json.so Reading symbols from /lib64/libjson-c.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libjson-c.so.2 Reading symbols from /usr/lib64/kamailio/modules/ipops.so...Reading symbols from /usr/lib/debug/usr/lib64/kamailio/modules/ipops.so.debug...done. done. Loaded symbols for /usr/lib64/kamailio/modules/ipops.so Reading symbols from /lib64/libnss_dns.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_dns.so.2 Core was generated by `/opt/ptin/kamailio-ksipadp/bin/ksipadp-proxy -f /opt/ptin/kamailio-ksipadp/prox'. Program terminated with signal 11, Segmentation fault. #0 0x00007fefe58ea7c4 in atomic_get (v=0x0) at ../../core/atomic/atomic_common.h:66 66 return atomic_get_int(&(v->val)); Missing separate debuginfos, use: debuginfo-install kamailio-ksipadp-2.8.0-1.ptin.el6.x86_64 (gdb) bt full #0 0x00007fefe58ea7c4 in atomic_get (v=0x0) at ../../core/atomic/atomic_common.h:66 No locals. #1 0x00007fefe58ee246 in job_queue_size (queue=0x0) at worker.c:254 No locals. #2 0x00007fefe58ed920 in add_dmq_job (msg=0x7ff028b453f8, peer=0x7fefebcc4df8) at worker.c:184 i = 1 found_available = 0 new_job = {f = 0x7fefe2613797 <usrloc_dmq_handle_msg>, msg = 0x7fefebce67c8, orig_peer = 0x7fefebcc4df8, next = 0x0, prev = 0x0} worker = 0x7fefe7a1d890 cloned_msg = 0x7fefebce67c8 cloned_msg_len = 3888 __FUNCTION__ = "add_dmq_job" #3 0x00007fefe58dfec1 in dmq_handle_message (msg=0x7ff028b453f8, str1=0x0, str2=0x0) at message.c:66 peer = 0x7fefebcc4df8 __FUNCTION__ = "dmq_handle_message" #4 0x0000000000433729 in do_action (h=0x7ffc89e35670, a=0x7ff0285a9340, msg=0x7ff028b453f8) at core/action.c:1054 ret = -5 v = 1 dst = {send_sock = 0x7ff0285a8810, to = {s = {sa_family = 21376, sa_data = "\343\211\374\177\000\000\370S\264(\360\177\000"}, sin = { sin_family = 21376, sin_port = 35299, sin_addr = {s_addr = 32764}, sin_zero = "\370S\264(\360\177\000"}, sin6 = {sin6_family = 21376, sin6_port = 35299, sin6_flowinfo = 32764, sin6_addr = {__in6_u = {__u6_addr8 = "\370S\264(\360\177\000\000pV\343\211\374\177\000", __u6_addr16 = {21496, 10420, 32752, 0, 22128, 35299, 32764, 0}, __u6_addr32 = {682906616, 32752, 2313377392, 32764}}}, sin6_scope_id = 1}}, id = 32764, proto = 0 '\000', send_flags = {f = 0, blst_imask = 0}} tmp = 0x389c422190 "" new_uri = 0x7c00000000 <Address 0x7c00000000 out of bounds> end = 0x6e00000077 <Address 0x6e00000077 out of bounds> crt = 0x389c98e120 "" cmd = 0x7ff0283219b0 len = 0 user = 0 uri = {user = {s = 0x7ffc89e34a10 "@K\343\211\374\177", len = 4459394}, passwd = {s = 0x7ffc89e34e80 "\356Q\343\211\374\177", len = 682906616}, host = {s = 0x7ff0285a9020 "\177\001", len = -1981589904}, port = {s = 0x0, len = 1}, params = { s = 0x7ff028b453f8 "\017", len = 295169284}, sip_params = {s = 0x32 <Address 0x32 out of bounds>, len = 1073741824}, headers = { s = 0x2000000 <Address 0x2000000 out of bounds>, len = 4289104}, port_no = 60676, proto = 5047, type = 2312043322, flags = 2168712452, transport = {s = 0x0, len = -1675583518}, ttl = {s = 0x89e34e90 <Address 0x89e34e90 out of bounds>, len = 35715777}, user_param = { s = 0xffffffff0000003c <Address 0xffffffff0000003c out of bounds>, len = -1671419584}, maddr = {s = 0x0, len = -1981592704}, method = { s = 0x389c603c48 "", len = -1671391960}, lr = {s = 0x0, len = -1981592544}, r2 = {s = 0x1dde9a0 " 9\336\001", len = 0}, gr = { s = 0x4 <Address 0x4 out of bounds>, len = 2479}, transport_val = {s = 0x389c422190 "", len = 1}, ttl_val = { s = 0x7ffc89e34b40 "pM\343\211\374\177", len = 5683491}, user_param_val = {s = 0x40e7e8 "\370\377\377\377\377\377\377\377@ݘ\234\070", len = -1671362728}, maddr_val = {s = 0x404130 "", len = 0}, method_val = {s = 0x1000003b4 <Address 0x1000003b4 out of bounds>, len = 0}, lr_val = {s = 0x7fefe7374b9a "%x%c%x%c", len = -1673386776}, r2_val = {s = 0x7ffc89e34bd0 "", len = -1981592584}, gr_val = { ---Type <return> to continue, or q <return> to quit--- s = 0x389c422190 "", len = 0}} next_hop = {user = {s = 0x1 <Address 0x1 out of bounds>, len = 40}, passwd = {s = 0x0, len = -1407107317}, host = { s = 0x2000000 <Address 0x2000000 out of bounds>, len = 31398688}, port = {s = 0x1dde9a0 " 9\336\001", len = 31320480}, params = { s = 0x7ffc89e34c20 "", len = -1981593152}, sip_params = {s = 0x7ffc89e34910 "\200N\343\211\374\177", len = 682906616}, headers = { s = 0x32 <Address 0x32 out of bounds>, len = 1073741824}, port_no = 0, proto = 512, type = ERROR_URI_T, flags = 4289104, transport = { s = 0x7ffc89e34900 "\020J\343\211\374\177", len = 4457737}, ttl = {s = 0x7ffc89e348f0 "", len = -1981593520}, user_param = { s = 0x7ffc89e34858 "\r", len = -1981593264}, maddr = {s = 0x7ffc89e34870 "", len = -1981593456}, method = {s = 0x7ffc89e348b0 "\r", len = -1981593392}, lr = {s = 0x8cd2d0 <Address 0x8cd2d0 out of bounds>, len = 13}, r2 = { s = 0x10100000002 <Address 0x10100000002 out of bounds>, len = -1}, gr = {s = 0x0, len = 0}, transport_val = {s = 0x0, len = 682906616}, ttl_val = {s = 0x7ff0285a9020 "\177\001", len = -1981593296}, user_param_val = {s = 0x7ffc89e34fa0 "\001\200\255\373\374\177", len = 0}, maddr_val = {s = 0x10000000d <Address 0x10000000d out of bounds>, len = -1981591296}, method_val = { s = 0x7fef00000000 <Address 0x7fef00000000 out of bounds>, len = -1671151657}, lr_val = {s = 0x7fefe7374ba2 "", len = 682906616}, r2_val = {s = 0x32 <Address 0x32 out of bounds>, len = 1073741824}, gr_val = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 4289104}} u = 0x389c4224e8 port = 0 dst_host = 0x89e34bd0 i = 32764 flags = 52 avp = 0x189e35040 st = {flags = 2313374752, id = 32764, name = {n = -1981593512, s = {s = 0x7ffc89e34858 "\r", len = -1981593152}, re = 0x7ffc89e34858}, avp = 0x7ffc89e347a0} sct = 0x0 sjt = 0x7ff028b453f8 rve = 0x32 mct = 0x40000000 rv = 0x7ffc89e34c20 rv1 = 0x2000000 c1 = {cache_type = 2313374144, val_type = 32764, c = {avp_val = {n = 1, s = {s = 0x1 <Address 0x1 out of bounds>, len = 1}, re = 0x1}, pval = { rs = {s = 0x1 <Address 0x1 out of bounds>, len = 1}, ri = -1407115050, flags = 52}}, i2s = "\000\000\000\000\000\000\000\000\274\224 \254\064\000\000\000\240G\343\211\374\177"} s = {s = 0x1 <Address 0x1 out of bounds>, len = -1981593512} srevp = {0x7ffc89e34960, 0x34ac208a97} mod_f_params = {{type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, { type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}} ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "do_action" #5 0x00000000004404b8 in run_actions (h=0x7ffc89e35670, a=0x7ff0285a9340, msg=0x7ff028b453f8) at core/action.c:1552 t = 0x7ff0285a9340 ret = -1 mod = 0x1dde9a0 ms = 176570657 __FUNCTION__ = "run_actions" #6 0x0000000000433692 in do_action (h=0x7ffc89e35670, a=0x7ff0285a9668, msg=0x7ff028b453f8) at core/action.c:1045 ret = 1 v = 1 dst = {send_sock = 0x7ffc89e35380, to = {s = {sa_family = 61042, sa_data = "I", '\000' <repeats 12 times>}, sin = {sin_family = 61042, sin_port = 73, sin_addr = {s_addr = 0}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 61042, sin6_port = 73, sin6_flowinfo = 0, sin6_addr = {__in6_u = {__u6_addr8 = "\000\000\000\000\000\000\000\000\020\000\000\000\005\000\000", __u6_addr16 = { 0, 0, 0, 0, 16, 0, 5, 0}, __u6_addr32 = {0, 0, 16, 5}}}, sin6_scope_id = 673678288}}, id = 32752, proto = 0 '\000', send_flags = { f = 0, blst_imask = 32752}} tmp = 0x66307b "H\213E\270H\203\300\070\351O\003" new_uri = 0x7ff028a93048 "" end = 0x7ff028a93038 "\303l\256" crt = 0x2000000 <Address 0x2000000 out of bounds> cmd = 0x1773508 len = 6791248 user = 0 uri = {user = {s = 0xae6ecd "", len = 11430897}, passwd = {s = 0x7c95f8 "core: core/parser/msg_parser.c", len = 682507016}, host = { s = 0xae6c43 "To: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128:5060<http://sip:usrloc@10.112.101.128:5060>>;tag=8a3534eb92149bbe647f599d354f2511-090e\r\nCSeq: 10 KDMQ\r\nCall-ID: 409f4ac5788a8cc4-24333(a)10.112.101.128<mailto:409f4ac5788a8cc4-24333@10.112.101.128>\r\nContent-Length: 39"..., len = 11430924}, port = {s = 0x0, len = 682507072}, params = { s = 0x7ff028ae3c90 <incomplete sequence \350>, len = 0}, sip_params = {s = 0x7ffc89e35330 "\246", len = 6697083}, headers = { s = 0x7c9170 "core", len = -1981590832}, port_no = 8, proto = 0, type = ERROR_URI_T, flags = 30415600, transport = { s = 0xa8428197 <Address 0xa8428197 out of bounds>, len = -1675583518}, ttl = {s = 0x3000000030 <Address 0x3000000030 out of bounds>, len = 44108294}, user_param = {s = 0x400000017 <Address 0x400000017 out of bounds>, len = 8176032}, maddr = {s = 0x0, len = -1981590448}, method = {s = 0x389c603c48 "", len = 11431629}, lr = {s = 0x7ffc89e35450 "\220T\343\211\374\177", len = 6869803}, r2 = { s = 0x7cc190 "get_hdr_field", len = 6730416}, gr = {s = 0x7ffc89e35300 "", len = 673677328}, transport_val = {s = 0x389c422190 "", len = 673677328}, ttl_val = {s = 0x7ffc89e35350 "\200S\343\211\374\177", len = -413652166}, user_param_val = {s = 0x40e7f9 "", len = 0}, maddr_val = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 24588552}, method_val = { s = 0x67a450 "\030A\211\321A)\301D\211ȉ\302H\213\205(\377\377\377\211P \276\004", len = 8965880}, lr_val = { s = 0x8cd2d0 <Address 0x8cd2d0 out of bounds>, len = 8}, r2_val = {s = 0xa6 <Address 0xa6 out of bounds>, len = 8136007}, gr_val = { s = 0x7c95f8 "core: core/parser/msg_parser.c", len = 682176488}} next_hop = {user = {s = 0x1e7374b9a <Address 0x1e7374b9a out of bounds>, len = 674472240}, passwd = { s = 0xffffffff <Address 0xffffffff out of bounds>, len = 4289104}, host = {s = 0x4e2cb1825 <Address 0x4e2cb1825 out of bounds>, len = -1667705792}, port = {s = 0x0, len = 1073741824}, params = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 4289104}, sip_params = {s = 0x7ffc89e35180 "\360Q\343\211\374\177", len = 6031673}, headers = {s = 0x7fefe2cb183f "", len = -1981591296}, port_no = 23013, proto = 58022, type = 32751, flags = 2313376240, transport = {s = 0x7fefe7374b9a "%x%c%x%c", len = -1981590944}, ttl = { ---Type <return> to continue, or q <return> to quit--- s = 0x1a <Address 0x1a out of bounds>, len = 4289104}, user_param = {s = 0x7fefe2a659e5 "5e6a5a14-1fa-", len = -1670974014}, maddr = { s = 0x30fbad8001 <Address 0x30fbad8001 out of bounds>, len = -492414491}, method = {s = 0x7fefe2a659e5 "5e6a5a14-1fa-", len = -492414491}, lr = {s = 0x7fefe2a659e5 "5e6a5a14-1fa-", len = -492414478}, r2 = {s = 0x7fefe2a659ff "", len = -492414491}, gr = {s = 0x7fefe2a659ff "", len = 0}, transport_val = {s = 0x0, len = 6730416}, ttl_val = {s = 0x7ffc89e351a0 "", len = 673677328}, user_param_val = { s = 0x2000000 <Address 0x2000000 out of bounds>, len = 673677328}, maddr_val = {s = 0x7ffc89e351f0 "Cl\256", len = -413652166}, method_val = {s = 0x7ff028278010 "\001", len = 0}, lr_val = {s = 0x2000000 <Address 0x2000000 out of bounds>, len = 24589344}, r2_val = { s = 0x67a138 "", len = 8965088}, gr_val = {s = 0x8cd2d0 <Address 0x8cd2d0 out of bounds>, len = 682507072}} u = 0x66273d port = 0 dst_host = 0x40000000 i = 28 flags = 0 avp = 0xae6cc7 st = {flags = 31129600, id = 0, name = {n = 0, s = {s = 0x0, len = 93}, re = 0x0}, avp = 0x7ffc89e35080} sct = 0x7ffc89e35490 sjt = 0x6943d3 rve = 0x7ff0285a8808 mct = 0x6a283b rv = 0x0 rv1 = 0x7c9170 c1 = {cache_type = 24, val_type = 48, c = {avp_val = {n = -1981590720, s = {s = 0x7ffc89e35340 "\370\225|", len = -1981590912}, re = 0x7ffc89e35340}, pval = {rs = {s = 0x7ffc89e35340 "\370\225|", len = -1981590912}, ri = 0, flags = 0}}, i2s = '\000' <repeats 21 times>} s = {s = 0x7fefe2cb183f "", len = -490006491} srevp = {0x7fefe2cb1825, 0x7fefe2cb1832} mod_f_params = {{type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, { type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}} __FUNCTION__ = "do_action" #7 0x00000000004404b8 in run_actions (h=0x7ffc89e35670, a=0x7ff0285a85d0, msg=0x7ff028b453f8) at core/action.c:1552 t = 0x7ff0285a9668 ret = 1 mod = 0x417250 ms = 176570657 __FUNCTION__ = "run_actions" #8 0x0000000000440c4a in run_top_route (a=0x7ff0285a85d0, msg=0x7ff028b453f8, c=0x0) at core/action.c:1641 ---Type <return> to continue, or q <return> to quit--- ctx = {rec_lev = 2, run_flags = 0, last_retcode = 1, jmp_env = {{__jmpbuf = {140669451785720, -8516593617994257148, 50, 1073741824, 33554432, 4289104, -8516593618092823292, 8518532807277145348}, __mask_was_saved = 0, __saved_mask = {__val = {140668355198191, 4302791168, 48, 48, 18446744073709551615, 140722621863712, 140668355198919, 50, 0, 4611686022755909632, 140669451785208, 140722621863776, 5814046, 6608344928, 140669451785208, 0}}}}} p = 0x7ffc89e35670 ret = 682907128 sfbk = 0 #9 0x000000000052e6b9 in receive_msg ( buf=0xae6bc0 "KDMQ sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080> SIP/2.0\r\nVia: SIP/2.0/UDP 10.112.101.128;branch=z9hG4bK8791.0c350dd3", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128<mailto:sip%3Ausrloc@10.112.101.128>"..., len=781, rcv_info=0x7ffc89e35a70) at core/receive.c:264 msg = 0x7ff028b453f8 ctx = {rec_lev = -1981589208, run_flags = 32764, last_retcode = 8, jmp_env = {{__jmpbuf = {163, 4253893, 8100093, 140669451683568, 140722621864176, 4845170, 0, 21474836480}, __mask_was_saved = 673677840, __saved_mask = {__val = {140668768878592, 140722621864448, 6697083, 8094080, 5501958, 243141751568, 140669476122624, 140722621864896, 4294967295, 88212724672, 1, 140668357584160, 0, 33554432, 1024, 6608345520}}}}} bctx = 0x7ffc89e359b0 ret = 0 stats_on = 0 tvb = {tv_sec = 140722621864208, tv_usec = 8961768} tve = {tv_sec = 0, tv_usec = 243139749096} tz = {tz_minuteswest = 50, tz_dsttime = 0} diff = 0 inb = { s = 0xae6bc0 "KDMQ sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080> SIP/2.0\r\nVia: SIP/2.0/UDP 10.112.101.128;branch=z9hG4bK8791.0c350dd3", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128<mailto:sip%3Ausrloc@10.112.101.128>"..., len = 781} netinfo = {data = {s = 0x7ffc00000001 <Address 0x7ffc00000001 out of bounds>, len = 0}, dst = 0x1, rcv = 0x389c422190} keng = 0x0 __FUNCTION__ = "receive_msg" #10 0x00000000006456a3 in udp_rcv_loop () at core/udp_server.c:515 len = 781 buf = "KDMQ sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080> SIP/2.0\r\nVia: SIP/2.0/UDP 10.112.101.128;branch=z9hG4bK8791.0c350dd3", '0' <repeats 24 times>, ".0\r\nTo: <sip:usrloc@10.112.103.64:5080<http://sip:usrloc@10.112.103.64:5080>>\r\nFrom: <sip:usrloc@10.112.101.128:5060<http://sip:usrloc@10.112.101.128:5060>>;tag=8a3"... tmp = 0x100000000 <Address 0x100000000 out of bounds> from = 0x7ff028b2c728 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {140722462617610, 140722621864592}, addr32 = {2154131466, 32764, 2313378448, 32764}, addr16 = { 28682, 32869, 32764, 0, 23184, 35299, 32764, 0}, addr = "\npe\200\374\177\000\000\220Z\343\211\374\177\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {1080520714, 0}, addr32 = {1080520714, 0, 0, 0}, addr16 = {28682, 16487, 0, 0, 0, 0, 0, 0}, addr = "\npg@", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5080, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = { sa_family = 2, sa_data = "\023\304\npe\200\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = { s_addr = 2154131466}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, ---Type <return> to continue, or q <return> to quit--- sin6_flowinfo = 2154131466, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7ff02830fff0, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #11 0x0000000000423c7d in main_loop () at main.c:1623 i = 0 pid = 0 si = 0x7ff02830fff0 si_desc = "udp receiver child=0 sock=10.112.103.64:5080<http://10.112.103.64:5080>\000\000\000\000 _\343\211\374\177\000\000\062\000\000\000\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\002\000\000\000\000PrA\000\000\000\000\000PSn\234\070\000\000\000\060\000\000\000\060\000\000\000\020]\343\211\374\177\000\000@\\\343\211\374\177\000\000\000px\347\357\177\000" nrprocs = 4 woneinit = 0 __FUNCTION__ = "main_loop" #12 0x000000000042b0ce in main (argc=13, argv=0x7ffc89e36008) at main.c:2646 cfg_stream = 0x1bb5010 c = -1 r = 0 tmp = 0x7ffc89e36ef7 "" tmp_len = 32764 port = -1981587768 proto = 56 options = 0x7434f8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 4012862799 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffc89e35f08 p = 0x100000000 <Address 0x100000000 out of bounds> st = {st_dev = 64769, st_ino = 148592, st_nlink = 2, st_mode = 16877, st_uid = 498, st_gid = 498, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1576522467, tv_nsec = 972000117}, st_mtim = {tv_sec = 1519927576, tv_nsec = 668342155}, st_ctim = {tv_sec = 1584026268, tv_nsec = 165523404}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) Em ter., 17 de mar. de 2020 às 09:52, Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> escreveu: Hello, does it happen only when doing restart of kamailio? Can you send the full backtrace from gdb? Also, 5.0.x is no longer a supported release for quite some time, try to upgrade to 5.2.x or even better to the latest one 5.3.x and see if you can reproduce it with one of the supported releases, maybe it is something that was already fixed. Cheers, Daniel On 17.03.20 10:32, Virgílio Cunha wrote: Hello, I have in production environment with 4 proxies using DMQ to sync terminal registers and the DMQ configuration parameters is following: loadmodule "dmq.so" #modparam("dmq", "server_address", "sip:MY_IP_ADDRESS:MY_PORT_ADDRESS") modparam("dmq", "notification_address", "DMQ_HOSTS") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) In the lab environment with the same configuration that in prod, I can simulate this problem with 12000 terminal REGISTERS and, when doing several restarts on a proxy, one of them is generated a coredump. Analyzing the core, I can see that the problem is concurrency in the dmq synchronization. Job_queue_size (...) is called with a valid queue and, but inside this function, the queue is null. (gdb) up #1 0x00007fefe58ee246 in job_queue_size (queue=0x0) at worker.c:254 254 return atomic_get(&queue->count); (gdb) print queue $1 = (job_queue_t *) 0x0 (gdb) up #2 0x00007fefe58ed920 in add_dmq_job (msg=0x7ff028b453f8, peer=0x7fefebcc4df8) at worker.c:184 184 if(job_queue_size(workers[i].queue) == 0) { (gdb) print i $2 = 1 (gdb) print workers[i].queue $3 = (job_queue_t *) 0x7fefebce49b0 If I configure DMQ with num_workers=1 I can't reproduce this problem. I'm using the kamailio 5.0.8 release. Is this problem known to you? What is the right way to solve it? Best Regards, Virgílio Cunha _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>

1 0

tls: ssl bug #1491 workaround
by Javier Valencia 18 Mar '20

18 Mar '20

Hi there I have a Kamailio with TLS/Websocket solution. I'm getting some errors on log and some users can't connect. My log: Mar 18 09:49:15 webrtc /usr/sbin/kamailio[11915]: ERROR: tls [tls_server.c:192]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=8212904 threshold1=8388608 Mar 18 09:49:15 webrtc /usr/sbin/kamailio[11915]: ERROR: <core> [core/tcp_read.c:1485]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f6297bd62c0 r: 0x7f6297bd6340 Kamailio is running like: /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 128 -M 16 -u kamailio -g kamailio Kind regards, Javier Valencia. -- Logo <http://www.voiper.es/> Javier Valencia | CTO Centro de Negocios Martín Buendía Camino de las Cañadas, nº 1C, Portal 1, 2ºG 29649 Mijas (Málaga) # 951562080 (T) <tel:951562080> | 687486759 (M) <tel:687486759> # www.voiper.es <http://www.voiper.es/> ------------------------------------------------------------------------ AVISO LEGAL ----------- Este mensaje contiene información confidencial destinada para ser leída exclusivamente por el destinatario. Queda prohibida la reproducción, publicación, divulgación, total o parcial del mensaje así como el uso no autorizados por el emisor. En caso de recibir el mensaje por error, se ruega su comunicación al remitente lo antes posible. Por favor, indique inmediatamente si usted o su empresa no aceptan comunicaciones de este tipo por Internet. Las opiniones, conclusiones y demás información incluida en este mensaje que no esté relacionada con asuntos profesionales de SMART RECARGAS, S.L, se entenderá que nunca se ha dado, ni está respaldado por el mismo. Responsable del Tratamiento de Datos ------------------------------------ SMART RECARGAS , SL Camino de las Cañadas, 1C PORTAL 1 2º G 29651 MIJAS COSTA (MALAGA)

4 14

Re: [SR-Users] I need to configure apns push notification in kamailio
by master1024 17 Mar '20

17 Mar '20

Hello Team, I need to configure apns sip push in kamailio, I have read it many sites but I don't get proper understanding I read it is done with the help of tsilo module kindly support in it. Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, February 27, 2020 11:10 AM, master1024 <master1024(a)protonmail.com> wrote: > Hello, > > I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this. > > Think Out of the Box > > Sent with [ProtonMail](https://protonmail.com) Secure Email.

5 12

systemd - properly starting up rtpengine with kernel forwarding
by Daniel-Constantin Mierla 17 Mar '20

17 Mar '20

Hello, do people here have (implemented) special ways to properly start rtpengine with kernel forwarding after system reboot? >From rtpengine readme: """ A typical start-up sequence including in-kernel forwarding might look like this: # this only needs to be one once after system (re-) boot modprobe xt_RTPENGINE iptables -I INPUT -p udp -j RTPENGINE --id 0 ip6tables -I INPUT -p udp -j RTPENGINE --id 0 # ensure that the table we want to use doesn't exist - usually needed after a daemon # restart, otherwise will error echo 'del 0' > /proc/rtpengine/control # start daemon /usr/sbin/rtpengine --table=0 --interface=10.64.73.31 --interface=2001:db8::4f3:3d \ --listen-ng=127.0.0.1:2223 --tos=184 --pidfile=/run/rtpengine.pid --no-fallback """ I was relying on shell scripts executed on boot time, but now that systemd is more common, I am looking to see what are "standard"/"recommended" ways for running additional scripts besides the start/stop daemon, which makes it also easier to build packages not worrying about the type of OS and how it can run scripts at startup. Systemd seems to have the "ExecStartPre" option, is it what people use to ensure the rtpengine kernel module is loaded and iptables rule exists? Any systemd-specific wayt to run a script only once after system boot? I have seen workarounds on the net for creating like a rc.local service, but they didn't look to be systemd-native, ... Not strictly related, but if someone is aware or had some experiences with, I am curious if "echo 'del 0' > /proc/rtpengine/control" is really needed because on a system where I forgot to have it in the scripts (well, was commented), I haven't noticed any issues after rtpengine restarts. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

3 8

I need to configure apns push notification in kamailio
by master1024 17 Mar '20

17 Mar '20

Hello Team, I want to configure ios push notification in kamailio, if it is possible kindly support me in deep, because I am new in kamailio. Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, March 16, 2020 1:24 PM, master1024 <master1024(a)protonmail.com> wrote: > Hello Team, > > I want to implement apns push notification on messages and calling in kamailio kindly support me. I am Beginner in kamailio. > > Sent with [ProtonMail](https://protonmail.com) Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Thursday, March 5, 2020 10:18 AM, master1024 <master1024(a)protonmail.com> wrote: > >> Hello Team, >> Kindly support in the same. >> >> Sent with [ProtonMail](https://protonmail.com) Secure Email. >> >> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >> On Wednesday, March 4, 2020 11:18 AM, master1024 <master1024(a)protonmail.com> wrote: >> >>> Hello Team, >>> >>> I need to configure apns Push Notification in kamailio kindly support in it. I read from the site https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eec… but I don't understand properly because here is missing push.php, I have another push.php and it is able to push notification on ios device but I need to understand how to integrate that push.php with kamailio, I need that when user is offline during call or message then push notification will fire from php script and application will wake up via push notification. >>> >>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>> >>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>> On Tuesday, March 3, 2020 12:06 PM, master1024 <master1024(a)protonmail.com> wrote: >>> >>>> Hello Team, >>>> I already read this and attempt to implement that but $sht is creating problem for me. and it is not working for me. >>>> >>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>> >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>> On Monday, March 2, 2020 11:14 PM, M S <shaheryarkh(a)gmail.com> wrote: >>>> >>>>> Here is a good starting point for you. Adapt and extend as needed in your setup. >>>>> >>>>> https://medium.com/@denys.pozniak/apple-push-notification-with-kamailio-eec… >>>>> >>>>> Hope this helps. >>>>> >>>>> On Mon, 2 Mar 2020, 12:39 master1024, <master1024(a)protonmail.com> wrote: >>>>> >>>>>> Hello Team, >>>>>> Kindly explain your 1st step, The IOS app must what what kind of parameters and how many parameters we needed ??? >>>>>> >>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>> >>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>>>> On Thursday, February 27, 2020 6:38 PM, M S <shaheryarkh(a)gmail.com> wrote: >>>>>> >>>>>>> Push notification setup is long and complex but generally has following process. Don't forget to read documentation of relevant kamailio modules for proper use. >>>>>>> >>>>>>> 1. The iOS app must send push notification parameters in SIP request e.g. SIP Register. In kamailio, when this request is received, you must extract them and save them in some db backend, e.g. MySQL, Redis etc. >>>>>>> >>>>>>> 2. For each income call, check if destination is offline and push parameters stored in db. If so, then you suspend the INVITE transaction using ASYNC or TSILO module and store transaction information in db. >>>>>>> >>>>>>> 3. Then using the push parameters stored in db, you send the push notification to device using CURL or HTTP client modules etc. >>>>>>> >>>>>>> 4. When device receives push notification, it must come online and send SIP register with push parameters. Kamailio again stores push parameters and checks if an INVITE transaction is waiting for the device. Retrieve the transaction, restore it and forward call to the device. >>>>>>> >>>>>>> 5. If device does not comes online upon receiving push notification and call times out or caller hangs up the call then you need to clean up transaction data stored in db. Similarly, you need to setup mechanism to purge push notification data after some time e.g. 7 or 10 days to ensure device push parameters remain up to date etc. >>>>>>> >>>>>>> The iOS apps now need to implement CallKit for push notification capable calls, that adds some serious difficultly in processing such calls since they show fake call screen before the actual call is received by app and if callee is too quick to respond to call (answer or reject) then kamailio will never know and still send the real call (step 4 above) later on, so you will need to manage that too. >>>>>>> >>>>>>> Hope this helps. >>>>>>> >>>>>>> On Thu, 27 Feb 2020, 13:25 master1024, <master1024(a)protonmail.com> wrote: >>>>>>> >>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>>>> >>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>>>>>> On Thursday, February 27, 2020 5:52 PM, master1024 <master1024(a)protonmail.com> wrote: >>>>>>>> >>>>>>>>> Hello Team, >>>>>>>>> >>>>>>>>> I need to configure apns sip push notification in kamailio, I have read it many sites but I don't get proper understanding I read it is done with the help of tsilo module kindly support in it. >>>>>>>>> >>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>>>>> >>>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ >>>>>>>>> On Thursday, February 27, 2020 11:10 AM, master1024 <master1024(a)protonmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I need to configure apns push notification in kamailio kindly help. I have a file push.php It is capable to push notification on ios device know i want to implement in kamailio when the user is offline then push notification fire kindly help in this. >>>>>>>>>> >>>>>>>>>> Think Out of the Box >>>>>>>>>> >>>>>>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

tls.options RPC reporting default settings
by Sergiu Pojoga 16 Mar '20

16 Mar '20

Hi there, Having custom TLS config in tls.cfg, RPC `tls.options` seems to report default settings. Bug or intended? root@kam:/# kamcmd version kamailio 5.3.2 (x86_64/linux) 0bed10 root@kam:/# kamcmd tls.options { force_run: 0 method: TLSv1 verify_certificate: 0 verify_depth: 9 require_certificate: 0 private_key: /usr/local/etc/kamailio/cert.pem ca_list: certificate: /usr/local/etc/kamailio/cert.pem cipher_list: session_cache: 0 session_id: kamailio-tls-5.x.y config: /usr/local/etc/kamailio/tls.cfg ... } modparam("tls", "config", "/usr/local/etc/kamailio/tls.cfg") root@kam:/usr/local/etc/kamailio# cat tls.cfg [server:default] method = TLSv1.2+ verify_certificate = yes require_certificate = yes private_key = /tmp/privkey.pem certificate = /tmp/fullchain.pem ca_list = /etc/ssl/certs/ca-certificates.crt [client:default] method = TLSv1.2+ verify_certificate = yes require_certificate = yes private_key = /tmp/privkey.pem certificate = /tmp/fullchain.pem ca_list = /etc/ssl/certs/ca-certificates.crt Cheers.

2 2

Kamailio v5.3.3 Released
by Daniel-Constantin Mierla 16 Mar '20

16 Mar '20

Hello, Kamailio SIP Server v5.3.3 stable release is out. This is a maintenance release of the latest stable branch, 5.3, that includes fixes since the release of v5.3.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.3.x. Deployments running previous v5.3.x versions are strongly recommended to be upgraded to v5.3.3. For more details about version 5.3.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2020/03/kamailio-v5-3-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Special circumstances are now everywhere word wide, impacting all of us, therefore we wish a smooth time during this crisis and to stay healthy to all our developers, supporters and community members along with their beloved ones! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Info: Kamailio World 2020 – Event Cancelled For April 27-29, 2020
by Daniel-Constantin Mierla 16 Mar '20

16 Mar '20

Source: https://www.kamailioworld.com/k08/2020/03/kamailio-world-2020-event-cancell… It is probably no much of a surprise that the next Kamailio World Conference and the NG-Emergency track cannot be organized any more during April 27-29, 2020. We are trying to find out the best alternatives for later in the year, when we hope the situation will be back to normal and people will be again in mood for social interaction. Being one of proposed alternatives, because we discussed a lot during the last several days with the people involved in organizing the event as well as its active community, we want to make it clear right now that we do not plan to switch to an online version (i.e., video conferencing) at the same dates. With the current situation out there, it is very likely that the level of stress everywhere will be high during the next 6 weeks till the initial planned dates, so putting together the infrastructure for video conferencing, synchronizing with the speakers and participants will just add to it, therefore it is better that everyone is focusing on taking care of the beloved ones and how to deal the best with the daily constraints during this interval. All the payments received for participating at or supporting Kamailio World 2020 will be refunded. If you are among them, thank you once more! We will contact you very soon with the relevant details. Keep also an eye on the event website for updates related to what is going to be next related to the conference! We hope the evolution will turn into a positive perspective very soon and the crisis is going to end rapidly, so everyone can return to the usual activities! Moreover, we wish you and the beloved ones a smooth time during this exceptional situation and to stay healthy! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Releasing Kamailio v5.3.3
by Daniel-Constantin Mierla 16 Mar '20

16 Mar '20

Hello, I am considering to release Kamailio v5.3.3 next week, either on Monday (March 16) or Tuesday (March 17). As usual, if any of you are aware of issues not reported on the tracker yet or knows fixes not backported to branch 5.3, reported them as soon as possible to take care of them. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

1 1

out of shm without any visible reason
by Juha Heinanen 12 Mar '20

12 Mar '20

K reported during about 90 sec period that it is out of shared memory: Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_hooks.c:136]: insert_tmcb(): out of shm. mem Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc [acc_logic.c:394]: acc_onreq(): cannot register additional callbacks Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate shared memory from shm pool Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_lookup.c:1293]: new_t(): out of mem: Feb 28 09:47:28 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_lookup.c:1439]: t_newtran(): new_t failed ... Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f1f2a506000, 1232); Free fragment not found! Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/mem/q_malloc.c:434]: qm_malloc(): qm_malloc(0x7f1f2a506000, 1232); Free fragment not found! Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: tm [t_reply.c:1957]: relay_reply(): cannot alloc reply shmem Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: <core> [core/sip_msg_clone.c:499]: sip_msg_shm_clone(): could not allocate shared memory from shm pool Feb 28 09:47:29 rox1 /usr/bin/sip-proxy[19725]: ERROR: acc [acc_logic.c:562]: acc_onreply(): failed to clone the request - acc aborted ... Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: <core> [core/mem/q_malloc.c:297]: qm_find_free(): qm_find_free(0x7f1f2a506000, 5728); Free fragment not found! Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: <core> [core/mem/q_malloc.c:434]: qm_malloc(): qm_malloc(0x7f1f2a506000, 5728); Free fragment not found! Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: tm [t_lookup.c:1293]: new_t(): out of mem: Feb 28 09:48:51 rox1 /usr/bin/sip-proxy[19724]: ERROR: tm [t_lookup.c:1439]: t_newtran(): new_t failed And after that period it started working normally again and core.shmmem showed: { total: 134217728 free: 124173808 used: 9530960 real_used: 10043920 max_used: 134217728 fragments: 349 } As can be seen, shm had been full, but normally only about 10% of it is in use. Syslog does not show any traffic spikes or other unusual activity before the memory got full. Any ideas what could cause such a high memory usage or could there be a bug in shm management? -- Juha

5 35

unknown error messages
by Juha Heinanen 12 Mar '20

12 Mar '20

Any idea where this kind of error message could come from: Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 61 Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core> [core/io_wait.h:607]: io_watch_del(): trying to delete already erased entry 61 in the hash(-1, 0, 0x7f689c16a868) flags 0) Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core> [core/io_wait.h:607]: io_watch_del(): trying to delete already erased entry 64 in the hash(-1, 0, 0x7f68c063b0f0) flags 0) Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: CRITICAL: <core> [core/pass_fd.c:191]: send_fd(): sendmsg failed sending 79 on 64: Broken pipe (32) Mar 12 07:16:17 rox2 /usr/bin/sip-proxy[32058]: ERROR: <core> [core/tcp_main.c:4225]: send2child(): send_fd failed for 0x7f689c18a0b0 (flags 0x4018), fd 79 Debug does not give any hints. -- Juha

2 2

Topoh and dialog track_cseq_updates
by Aidar Kamalov 12 Mar '20

12 Mar '20

Hello, I am trying to increase cseq in invite with credentials to 401 Unauthorized, but with topoh.so module and mask_callid enabled it does not work. Are there any way to fix it? -- Aydar A. Kamalov

2 1

xhttp_prom - Adding new metrics for dispatcher list to monitor SIP trunk availability
by Jonathan Hunter 12 Mar '20

12 Mar '20

Hi Guys, We are running kamailio 5.3 in our dev environment with a view to using the xhttp_prom module, so that we can monitor using prometheous. It works fine in terms of getting all the internal stats and groups, however is it possible to grab the dispatcher.list output/stats using the module? I know there is a collector that does this and provides the dispatcher gateway trunk status, but wondered if it could be implemented using xhttp_prom, or if external code would be required to grab the states using rpc etc? Many thanks Jon

2 2

Re: [SR-Users] (no subject)
by Henning Westerholt 12 Mar '20

12 Mar '20

Hello, you need to provide some details about the errors (like output from log messages etc..) that we can help you here on this list. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: ahmed moghazy <ahmed.m.moghazi(a)gmail.com> Sent: Thursday, March 12, 2020 8:56 AM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] (no subject) I want to know steps for that cause when i try this it give me error i dont know why ?! On Mar 11, 2020, at 10:21 AM, Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello, this could be done with a database query (e.g. with sqlops module). If you are looking for a dedicated interface, there is for example the group module: https://kamailio.org/docs/modules/devel/modules/group.html Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of ahmed moghazy Sent: Tuesday, March 10, 2020 8:53 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: Re: [SR-Users] (no subject) If i want to make users in groups for example two Groups group A and group B and each group has 4 users but users in group A couldn't Call users in group B? On Mar 3, 2020, at 10:36 PM, ahmed moghazy <ahmed.m.moghazi(a)gmail.com<mailto:ahmed.m.moghazi@gmail.com>> wrote: I generate those certificates and i put then in linphone source code i want to enable require_certficate=1 could you help me how and where to put the certificates and linphone peer return it ? , thank you On Mar 3, 2020, at 10:52 AM, M S <shaheryarkh(a)gmail.com<mailto:shaheryarkh@gmail.com>> wrote: Any sip client will work with kamailio (as sip server) as long as it supports TLS and configured correctly. I mostly use Linphone, Xlite and some of my own sip clients that i have built over the years. You simply need to follow the quick howto in tls module documentation (as i mentioned earlier) to generate client and server certificates. Then copy client cert along with CA to sip client, provide connection and authentication info and it should work fine. For over simplified setup where you don't have client certificate or not sure how to configure one for any given sip client, you can disable "verify_certificate" option in tls module. Hope this helps. On Tue, 3 Mar 2020, 08:53 ahmed moghazy, <ahmed.m.moghazi(a)gmail.com<mailto:ahmed.m.moghazi@gmail.com>> wrote: I know that but i want voip program to be used with kamailio using tls i you could suggest one , thank you Sent from my iPhone On Mar 3, 2020, at 5:54 AM, M S <shaheryarkh(a)gmail.com<mailto:shaheryarkh@gmail.com>> wrote: Dude again, RTFM! The TLS module has a quick how-to generate client and server certificates. Both must be issued by same CA and server must have all issued certificates along with CA, CRL and private key. The whole directory structure and what to put where is listed, along with how to configure kamailio. On Mon, 2 Mar 2020, 20:27 ahmed moghazy, <ahmed.m.moghazi(a)gmail.com<mailto:ahmed.m.moghazi@gmail.com>> wrote: I put my own certficate in /res/raw/rootca.pem in linphone Sent from my iPhone On Mar 2, 2020, at 7:40 PM, M S <shaheryarkh(a)gmail.com<mailto:shaheryarkh@gmail.com>> wrote: Please read the tls module documentation, https://kamailio.org/docs/modules/devel/modules/tls.html#tls.p.require_cert… when enabled it requires client to present certificate, but client does not have one, which is the likely cause of the problem. Hope this helps. On Mon, 2 Mar 2020, 14:34 ahmed moghazy, <ahmed.m.moghazi(a)gmail.com<mailto:ahmed.m.moghazi@gmail.com>> wrote: Hello sir , when i enabled tls module in kamailio and i made the configurations in tls.cfg, kamailio always sent me that peer dont return certificate when i make requre_certficate=1 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

Use topos module to hide contact in OPTIONS request
by Enzo 12 Mar '20

12 Mar '20

2 1

(no subject)
by ahmed moghazy 11 Mar '20

11 Mar '20

Hello sir , when i enabled tls module in kamailio and i made the configurations in tls.cfg, kamailio always sent me that peer dont return certificate when i make requre_certficate=1

3 8

secfilter not working for me
by Joli Martinez 10 Mar '20

10 Mar '20

I have a fresh install of Kamailio 5.2.5 on CentOS7. I am trying to install the secfilter module as per the link below https://www.kamailio.org/wiki/tutorials/security/kamailio-security When I restarted the service it is not finding the geoid or secfilter module. From what I was reading there are no dependencies or anything to install. What am I missing? ------------------------------------------------- Mar 10 16:30:47 kamailio01 systemd: Started Kamailio (OpenSER) - the Open Source SIP Server. Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/sr_module.c:487]: load_module(): could not find module <geoip2> in </usr/lib64/kamailio/modules> Mar 10 16:30:47 kamailio01 kamailio: CRITICAL: <core> [core/cfg.y:3508]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 300, column 15-25: failed to load module Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/sr_module.c:487]: load_module(): could not find module <secfilter> in </usr/lib64/kamailio/modules> Mar 10 16:30:47 kamailio01 kamailio: CRITICAL: <core> [core/cfg.y:3508]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 301, column 15-28: failed to load module Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <secfilter> found Mar 10 16:30:47 kamailio01 kamailio: CRITICAL: <core> [core/cfg.y:3511]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 322, column 81: Can't set module parameter Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/modparam.c:152]: set_mod_param_regex(): No module matching <secfilter> found Mar 10 16:30:47 kamailio01 kamailio: CRITICAL: <core> [core/cfg.y:3511]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 323, column 43: Can't set module parameter Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/cfg.y:3371]: yyparse(): cfg. parser: failed to find command geoip2_match (params 2) Mar 10 16:30:47 kamailio01 kamailio: CRITICAL: <core> [core/cfg.y:3511]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 614, column 38: unknown command, missing loadmodule? Mar 10 16:30:47 kamailio01 kamailio: ERROR: bad config file (6 errors) Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/pvapi.c:915]: pv_parse_spec2(): error searching pvar "gip2" Mar 10 16:30:47 kamailio01 kamailio: ERROR: <core> [core/pvapi.c:1119]: pv_parse_spec2(): wrong char [s/115] in [$gip2(src=>cc)] at [6 (5)] Mar 10 16:30:47 kamailio01 kamailio: CRITICAL: <core> [core/cfg.y:3508]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 615, column 36-49: Can't get from cache: $gip2(src=>cc)

2 1

Kamailio TLS
by Mike Nasr 10 Mar '20

10 Mar '20

Dear Hope all is well. Can i trouble you with pointing me to the right tutorial for properly adding tls on any version of Kamailio. i have been trying for days, all versions and method i can find on the internet, even build from source and changed openssl version as suggested by one of the threads in the mailing list still without any luck. apologies for not providing any references as i am sending this email from my colleague machine. Thanking you in advance Mike Nasr ICT Consultant mikenasr.com

2 1

Re: [SR-Users] Thank you --- Compilation success
by Henning Westerholt 09 Mar '20

09 Mar '20

Hello, (moving discussion to users list) have a look to the Kamailio log files to see the actual errors, maybe there is a path not correct. You can also execute Kamailio with logging to stdout (have a look to the parameter visible with kamailio -h). Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: subhra giri <subhraprakash79(a)gmail.com> Sent: Monday, March 9, 2020 12:20 PM To: Henning Westerholt <hw(a)skalatan.de> Cc: sr-dev(a)lists.kamailio.org Subject: Re: Thank you --- Compilation success Dear Henning Sure, will do that. But after running kamailio on the mips board i am getting below error. /bin/kamailio-5.3.2/src # ./kamailio loading modules under config path: /usr/lib/kamailio-5.3.2/src/modules/ ERROR: bad config file (45 errors) I have attached config file. Please help me what is wrong in this config file. Thanks and regards Subhra Prakash On Mon, Mar 9, 2020 at 3:27 PM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello Subhra, Great! Could you share the here steps that lead to the success that others might be able to learn from it as well? Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: subhra giri <subhraprakash79(a)gmail.com<mailto:subhraprakash79@gmail.com>> Sent: Saturday, March 7, 2020 11:18 AM To: Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> Subject: Thank you --- Compilation success Dear Henning Compilation is successful for MIPS. Thank you very much Subhra Prakash Giri On Sat, Mar 7, 2020 at 1:26 PM subhra giri <subhraprakash79(a)gmail.com<mailto:subhraprakash79@gmail.com>> wrote: Dear Henning I tried to compile directly on MIPS board, but there is no make file in my board. so it is not compiling. I am not getting Make for MIPS board. Is there any other way to compile on x86 for mips board. Thanks and Regards Subhra Prakash Giri On Fri, Mar 6, 2020 at 6:43 PM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hi Subhra, I meant with native platform – to test compilation directly on the MIPS board, not sure if you understood it the same way. Cheers, Henning From: subhra giri <subhraprakash79(a)gmail.com<mailto:subhraprakash79@gmail.com>> Sent: Friday, March 6, 2020 1:11 PM To: Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> Cc: sr-dev(a)lists.kamailio.org<mailto:sr-dev@lists.kamailio.org> Subject: Re: [sr-dev] Regarding MIPS Compilation Dear Henning Executing "make cfg " gives below output [root@www kamailio-5.3.2]# make cfg make -C src/ cfg target architecture <mips64>, host architecture <x86_64> ---------------------------------------------------------------------------------------------------------------------------------------------------------- In native platform it is compiling successfully. But giving problem for target platform i.e mips64-octeon-linux. Please help me with steps for mips compilation Thanks and Regards Subhra Prakash Giri

1 0

Kamailio 5.0.1 Crashes
by Virgílio Cunha 09 Mar '20

09 Mar '20

Hello everyone, I have a problem in production environment where I have two SIP Proxies and both had the same problem but I don't have a ideia about root cause that triggered it. Unfortunately I don't have a core dump file because it was truncated for don't have space enough in file system. So I only have loggings filesin DEBUG level. The proxy_1 apparently was processing a SUBSCRIBE request and the proxy_2 was processing a DMQ messages. Both of proxies crashed after appear this line in logging file " CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 10" What could trigger this error? The loggin of proxy_1 is following: 2020-01-28 05:17:37.058 INFO: <script>: New request - M=SUBSCRIBE R=sip: 172.29.213.10:5070 F=sip:9147323151@businesshostedvoice.com:5061 T=sip:9147323156@busine sshostedvoice.com:5061 IP=udp:10.159.0.25:5060 ID= 0gQAAC8WAAACBAAALxYAAJmTUrVeFdEMSouFoeDnzdKbnqZHYs2tiFs+Okphqx4p(a)10.159.0.25 CSeq=20830 2020-01-28 05:17:37.058 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f3f97a41000, 74) called from core: core/usr_avp.c: create_avp(175) 2020-01-28 05:17:37.058 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f3f97a41000, 80) returns address 0x7f3fb4365df8 frag. 0x7f3fb4365dc0 (size=80) on 1 -th hit 2020-01-28 05:17:37.058 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f3f97a41000, 52) called from core: core/usr_avp.c: create_avp(175) 2020-01-28 05:17:37.058 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f3f97a41000, 56) returns address 0x7f3fb7c8ef08 frag. 0x7f3fb7c8eed0 (size=56) on 1 -th hit 2020-01-28 05:17:37.058 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f3f97a41000, 67) called from core: core/usr_avp.c: create_avp(175) 2020-01-28 05:17:37.058 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f3f97a41000, 72) returns address 0x7f3fd2bc8928 frag. 0x7f3fd2bc88f0 (size=72) on 1 -th hit 2020-01-28 05:17:37.059 INFO: <script>: Applying rewrite rules on '9147323156' using dialplan 'DB_MANIPS' - R=sip:172.29.213.10:5070 ID=0gQAAC8WAAACBAAALxYAAJmT UrVeFdEMSouFoeDnzdKbnqZHYs2tiFs+Okphqx4p(a)10.159.0.25 UA='Grandstream GXP2140 1.0.9.135' 2020-01-28 05:17:37.059 DEBUG: dialplan [dialplan.c:208]: dp_get_ivalue(): searching 4 2020-01-28 05:17:37.059 DEBUG: dialplan [dialplan.c:216]: dp_get_ivalue(): dpid is 1 from pv argument 2020-01-28 05:17:37.059 DEBUG: dialplan [dialplan.c:225]: dp_get_svalue(): searching 4 2020-01-28 05:17:37.059 DEBUG: dialplan [dialplan.c:313]: dp_translate_f(): input is 9147323156 2020-01-28 05:17:37.059 DEBUG: dialplan [dp_repl.c:606]: translate(): regex operator testing over [9147323156] 2020-01-28 05:17:37.059 DEBUG: dialplan [dp_repl.c:606]: translate(): regex operator testing over [9147323156] 2020-01-28 05:17:37.059 DEBUG: dialplan [dp_repl.c:606]: translate(): regex operator testing over [9147323156] 2020-01-28 05:17:37.059 DEBUG: dialplan [dp_repl.c:676]: translate(): no matching rule 2020-01-28 05:17:37.059 DEBUG: dialplan [dialplan.c:318]: dp_translate_f(): could not translate 9147323156 with dpid 1 2020-01-28 05:17:37.059 INFO: <script>: No matching rewrite rules for '9147323156' found - R=sip:172.29.213.10:5070 ID=0gQAAC8WAAACBAAALxYAAJmTUrVeFdEMSouFoeDnz dKbnqZHYs2tiFs+Okphqx4p(a)10.159.0.25 UA='Grandstream GXP2140 1.0.9.135' 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f3f97a41000, 70) called from core: core/usr_avp.c: create_avp(175) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f3f97a41000, 72) returns address 0x7f3fa7f6f028 frag. 0x7f3fa7f6eff0 (size=72) on 1 -th hit 2020-01-28 05:17:37.059 INFO: <script>: Clean AVPs that contains rewrite rule from method ROUTE_APPLY_REWRITE_RULE ID=0gQAAC8WAAACBAAALxYAAJmTUrVeFdEMSouFoeDnzd KbnqZHYs2tiFs+Okphqx4p(a)10.159.0.25 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f3f97a41000, 0x7f3fb4365df8), called from core: core/usr_avp.c: destroy_a vp(592) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f3fb4365dc0 alloc'ed from core: core/usr_avp.c: create_avp (175) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f3f97a41000, 0x7f3fb7c8ef08), called from core: core/usr_avp.c: destroy_avp(592) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f3fb7c8eed0 alloc'ed from core: core/usr_avp.c: create_avp(175) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f3f97a41000, 0x7f3fd2bc8928), called from core: core/usr_avp.c: destroy_avp(592) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f3fd2bc88f0 alloc'ed from core: core/usr_avp.c: create_avp(175) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f40d8531010, 247) called from db_postgres: km_dbase.c: db_postgres_submit_query(171) 2020-01-28 05:17:37.059 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f40d8531010, 248) returns address 0x7f40d8aac7d8 frag. 0x7f40d8aac7a0 (size=376) on 1 -th hit 2020-01-28 05:17:37.059 CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 10 2020-01-28 05:17:37.059 DEBUG: <core> [core/tcp_main.c:3456]: handle_ser_child(): dead child 2, pid 28150 (shutting down?) 2020-01-28 05:17:37.059 DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa52ba0, 10, -1, 0x0) fd_no=61 called 2020-01-28 05:17:37.059 ALERT: <core> [main.c:744]: handle_sigs(): child process 28150 exited by a signal 11 2020-01-28 05:17:37.059 ALERT: <core> [main.c:747]: handle_sigs(): core was generated 2020-01-28 05:17:37.059 INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD 2020-01-28 05:17:37.059 DEBUG: <core> [main.c:761]: handle_sigs(): terminating due to SIGCHLD 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5260600, used+overhead=7067400, free=11806968 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5260600, used+overhead=7067400, free=11806968 2020-01-28 05:17:37.060 DEBUG: qm_status: max used (+overhead)= 7144424 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5111688, used+overhead=6932632, free=11941736 2020-01-28 05:17:37.060 DEBUG: qm_status: max used (+overhead)= 7144424 2020-01-28 05:17:37.060 DEBUG: qm_status: dumping all alloc'ed. fragments: 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: qm_status: 0. N address=0x7f40d856a6d8 frag=0x7f40d856a6a0 size=1024 used=1 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: alloc'd from core: core/str_hash.h: str_hash_alloc(59) 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5260600, used+overhead=7067400, free=11806968 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: max used (+overhead)= 7144424 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5260600, used+overhead=7067400, free=11806968 2020-01-28 05:17:37.060 DEBUG: qm_status: max used (+overhead)= 7144424 2020-01-28 05:17:37.060 DEBUG: qm_status: dumping all alloc'ed. fragments: 2020-01-28 05:17:37.060 DEBUG: qm_status: 0. N address=0x7f40d856a6d8 frag=0x7f40d856a6a0 size=1024 used=1 2020-01-28 05:17:37.060 DEBUG: qm_status: alloc'd from core: core/str_hash.h: str_hash_alloc(59) 2020-01-28 05:17:37.060 DEBUG: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: 1. N address=0x7f40d856ab40 frag=0x7f40d856ab08 size=256 used=1 2020-01-28 05:17:37.060 DEBUG: qm_status: alloc'd from core: core/str_hash.h: str_hash_alloc(59) 2020-01-28 05:17:37.060 DEBUG: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed 2020-01-28 05:17:37.060 DEBUG: qm_status: 2. N address=0x7f40d856aca8 frag=0x7f40d856ac70 size=176 used=1 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: alloc'd from core: core/counters.c: cnt_hash_add(332) 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: (0x7f40d8531010): 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5103784, used+overhead=6908920, free=11965448 2020-01-28 05:17:37.060 DEBUG: qm_status: heap size= 18874368 2020-01-28 05:17:37.060 DEBUG: qm_status: used= 5103784, used+overhead=6908920, free=11965448 2020-01-28 05:17:37.060 DEBUG: qm_status: max used (+overhead)= 7144424 2020-01-28 05:17:37.060 DEBUG: qm_status: dumping all alloc'ed. fragments: The loggin of proxy_2 is following: 2020-01-28 05:57:21.077 DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [74]; uri=[sip:usrloc@172.29.217.7:5060] 2020-01-28 05:57:21.077 DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): to body [<sip:usrloc@172.29.217.7:5060>] 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f5ae4367010, 64) called from core: core/parser/msg_parser.c: parse_he aders(319) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f5ae4367010, 64) returns address 0x7f5ae499f980 frag. 0x7f5ae499f948 (size=64) on 1 -th hit 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f5ae4367010, 64) called from core: core/parser/msg_parser.c: parse_he aders(319) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f5ae4367010, 64) returns address 0x7f5ae499bcf8 frag. 0x7f5ae499bcc0 (size=64) on 1 -th hit 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f5ae4367010, 48) called from core: core/parser/msg_parser.c: get_hdr_ field(135) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f5ae4367010, 48) returns address 0x7f5ae4916f90 frag. 0x7f5ae4916f58 (size=48) on 1 -th hit 2020-01-28 05:57:21.077 DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <10> <KDMQ> 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f5ae4367010, 64) called from core: core/parser/msg_parser.c: parse_headers(319) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f5ae4367010, 64) returns address 0x7f5ae499e520 frag. 0x7f5ae499e4e8 (size=64) on 1 -th hit 2020-01-28 05:57:21.077 DEBUG: <core> [core/receive.c:191]: receive_msg(): --- received sip message - reply - call-id: [ 3d48b3aa4ec7e11f-8255(a)172.29.213.8] - cseq: [10 KDMQ] 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:368]: qm_malloc(): qm_malloc(0x7f5ae4367010, 936) called from core: core/rvalue.c: rval_new_empty(224) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:413]: qm_malloc(): qm_malloc(0x7f5ae4367010, 936) returns address 0x7f5ae48e1340 frag. 0x7f5ae48e1308 (size=1736) on 1 -th hit 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae48e1340), called from core: core/rvalue.c: rval_destroy(129) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae48e1308 alloc'ed from core: core/rvalue.c: rval_new_empty(224) 2020-01-28 05:57:21.077 DEBUG: tm [t_lookup.c:1001]: t_check_msg(): msg id=190277 global id=190276 T start=0xffffffffffffffff 2020-01-28 05:57:21.077 DEBUG: tm [t_lookup.c:879]: t_reply_matching(): t_reply_matching: hash 26335 label 0 branch 0 2020-01-28 05:57:21.077 DEBUG: tm [t_lookup.c:933]: t_reply_matching(): reply matched (T=0x7f59eef5b310)! 2020-01-28 05:57:21.077 DEBUG: tm [t_lookup.c:1070]: t_check_msg(): msg id=190277 global id=190277 T end=0x7f59eef5b310 2020-01-28 05:57:21.077 DEBUG: tm [t_lookup.c:1001]: t_check_msg(): msg id=190277 global id=190277 T start=0x7f59eef5b310 2020-01-28 05:57:21.077 DEBUG: tm [t_lookup.c:1073]: t_check_msg(): T already found! 2020-01-28 05:57:21.077 DEBUG: tm [t_reply.c:2147]: reply_received(): org. status uas=0, uac[0]=0 local=2 is_invite=0) 2020-01-28 05:57:21.077 DEBUG: tm [t_reply.c:1220]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=200 2020-01-28 05:57:21.077 DEBUG: tm [t_reply.c:2021]: local_reply(): branch=0, save=0, winner=0 2020-01-28 05:57:21.077 DEBUG: tm [t_reply.c:2060]: local_reply(): local transaction completed 200/0 (totag retr: 0/1024) 2020-01-28 05:57:21.077 DEBUG: tm [t_hooks.c:258]: run_trans_callbacks_internal(): DBG: trans=0x7f59eef5b310, callback type 1024, id 0 entered 2020-01-28 05:57:21.077 DEBUG: dmq [dmq_funcs.c:61]: dmq_tm_callback(): dmq_tm_callback start 2020-01-28 05:57:21.077 DEBUG: dmq_usrloc [usrloc_sync.c:583]: usrloc_dmq_resp_callback_f(): dmq response callback triggered [0x7f5ae4a373c8 200 (nil)] 2020-01-28 05:57:21.077 DEBUG: dmq [dmq_funcs.c:67]: dmq_tm_callback(): dmq_tm_callback done 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f59a3877000, 0x7f59f9b93080), called from dmq: dmqnode.c: shm_free_node(306) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f59f9b93048 alloc'ed from dmq: ../../core/ut.h: shm_str_dup(723) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f59a3877000, 0x7f59c6055a40), called from dmq: dmqnode.c: shm_free_node(307) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f59c6055a08 alloc'ed from dmq: dmqnode.c: shm_dup_node(279) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f59a3877000, 0x7f59c4a46a48), called from dmq: dmq_funcs.c: dmq_tm_callback(69) 2020-01-28 05:57:21.077 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f59c4a46a10 alloc'ed from dmq: dmq_funcs.c: dmq_send_message(212) 2020-01-28 05:57:21.077 DEBUG: tm [t_reply.c:1578]: cleanup_uac_timers(): RETR/FR timers reset 2020-01-28 05:57:21.077 DEBUG: <core> [core/receive.c:348]: receive_msg(): reply-route executed in: 143 usec 2020-01-28 05:57:21.077 DEBUG: <core> [core/usr_avp.c:631]: destroy_avp_list(): destroying list (nil) 2020-01-28 05:57:21.077 DEBUG: <core> [core/usr_avp.c:631]: destroy_avp_list(): destroying list (nil) 2020-01-28 05:57:21.077 DEBUG: <core> [core/usr_avp.c:631]: destroy_avp_list(): destroying list (nil) 2020-01-28 05:57:21.077 DEBUG: <core> [core/usr_avp.c:631]: destroy_avp_list(): destroying list (nil) 2020-01-28 05:57:21.077 DEBUG: <core> [core/usr_avp.c:631]: destroy_avp_list(): destroying list (nil) 2020-01-28 05:57:21.077 DEBUG: <core> [core/usr_avp.c:631]: destroy_avp_list(): destroying list (nil) 2020-01-28 05:57:21.077 DEBUG: <core> [core/xavp.c:446]: xavp_destroy_list(): destroying xavp list (nil) 2020-01-28 05:57:21.078 DEBUG: <core> [core/receive.c:368]: receive_msg(): cleaning up 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae499e670), called from core: core/parser/parse_via.c: free_via_param_list(2725) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae499e638 alloc'ed from core: core/parser/parse_via.c: parse_via(2511) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae499f830), called from core: core/parser/parse_via.c: free_via_list(2738) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae499f7f8 alloc'ed from core: core/parser/msg_parser.c: get_hdr_field(116) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae4921478), called from core: core/parser/hf.c: free_hdr_field_lst(217) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae4921440 alloc'ed from core: core/parser/msg_parser.c: parse_headers(319) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae4924f60), called from core: core/parser/parse_addr_spec.c: free_to_params(895) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae4924f28 alloc'ed from core: core/parser/parse_addr_spec.c: parse_to_param(285) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae4998e48), called from core: core/parser/parse_addr_spec.c: free_to(905) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae4998e10 alloc'ed from core: core/parser/msg_parser.c: get_hdr_field(155) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae48ecd18), called from core: core/parser/hf.c: free_hdr_field_lst(217) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae48ecce0 alloc'ed from core: core/parser/msg_parser.c: parse_headers(319) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae499f980), called from core: core/parser/hf.c: free_hdr_field_lst(217) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae499f948 alloc'ed from core: core/parser/msg_parser.c: parse_headers(319) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae4916f90), called from core: core/parser/parse_cseq.c: free_cseq(99) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae4916f58 alloc'ed from core: core/parser/msg_parser.c: get_hdr_field(135) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae499bcf8), called from core: core/parser/hf.c: free_hdr_field_lst(217) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae499bcc0 alloc'ed from core: core/parser/msg_parser.c: parse_headers(319) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae499e520), called from core: core/parser/hf.c: free_hdr_field_lst(217) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae499e4e8 alloc'ed from core: core/parser/msg_parser.c: parse_headers(319) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:454]: qm_free(): qm_free(0x7f5ae4367010, 0x7f5ae4a373c8), called from core: core/receive.c: receive_msg(370) 2020-01-28 05:57:21.078 DEBUG: <core> [core/mem/q_malloc.c:489]: qm_free(): qm_free: freeing frag. 0x7f5ae4a37390 alloc'ed from core: core/receive.c: receive_msg(150) 2020-01-28 05:57:21.117 CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 10 2020-01-28 05:57:21.117 DEBUG: <core> [core/tcp_main.c:3456]: handle_ser_child(): dead child 2, pid 8253 (shutting down?) 2020-01-28 05:57:21.117 DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa52ba0, 10, -1, 0x0) fd_no=61 called 2020-01-28 05:57:21.118 ALERT: <core> [main.c:744]: handle_sigs(): child process 8253 exited by a signal 11 2020-01-28 05:57:21.118 ALERT: <core> [main.c:747]: handle_sigs(): core was generated 2020-01-28 05:57:21.118 INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD 2020-01-28 05:57:21.118 DEBUG: <core> [main.c:761]: handle_sigs(): terminating due to SIGCHLD 2020-01-28 05:57:21.118 INFO: <core> [main.c:814]: sig_usr(): signal 15 received 2020-01-28 05:57:21.118 DEBUG: <core> [main.c:825]: sig_usr(): Memory status (pkg): Best regards Virgílio Cunha

3 3

Kamailio connection issue
by Tomas Zanet 09 Mar '20

09 Mar '20

Hi All, In these days I'm facing an issue or a misconfiguration, I don't know, with our remote apps (SIP clients) and our cloud server in which there's a Kamailio version 4.4.4. Sometimes our app takes some seconds (about 10-12sec) to connect to the Kamailio socket (sips on 5061) and our app is stuck on connect sytem call. To debug this behaviour I put a rule in the iptable like this: sudo iptables -I INPUT -p tcp -m tcp --dport 5061 -m state --state NEW -j LOG --log-level 1 --log-prefix "New Connection " when everything goes well, there is one row which describes the new incoming connection Mar 4 07:08:40 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=15819 DPT=5061 WINDOW=65535 RES=0x00 CWR ECE SYN URGP=0 when our app gets stuck in the connect, there are many attempts and seems that Kamailio is not ready to accept this connection: Mar 4 07:11:54 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 CWR ECE SYN URGP=0 Mar 4 07:11:54 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:55 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:55 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:55 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:56 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:56 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:56 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:11:58 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:12:00 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=64 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 Mar 4 07:12:05 server-xip-01 kernel: New Connection IN=eth0 OUT= MAC=bc:76:4e:20:1f:fb:e8:ed:f3:3a:52:41:08:00 SRC=X.X.X.X DST=Y.Y.Y.Y LEN=48 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=52900 DPT=5061 WINDOW=65535 RES=0x00 SYN URGP=0 When it happens our app takes more than 10 sec to connect to the Kamailio socket. I tried to increase the children configuration parameter in the cfg file because I thought there were not enough tcp receiver but with no luck. Here are some configuration parameters: children = 16 // was 8 before found this issue # life time of TCP connection when there is no traffic # - a bit higher than registration expires to cope with UA behind NAT tcp_connection_lifetime=3605 open_files_limit=8192 tcp_max_connections=8192 tls_max_connections=8192 Here is the output of the ulimit command: ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31393 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 65535 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 31393 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited In the kamailio log file I don't see anything wrong, I don't see messages like "[tcp_main.c:3913]: handle_new_connect(): maximum number of tls connections exceeded". Here is the output of kamctl ps command Process:: ID=0 PID=11725 Type=main process - attendant Process:: ID=1 PID=11727 Type=udp receiver child=0 sock=10.208.194.26:5061 Process:: ID=2 PID=11728 Type=udp receiver child=1 sock=10.208.194.26:5061 Process:: ID=3 PID=11729 Type=udp receiver child=2 sock=10.208.194.26:5061 Process:: ID=4 PID=11730 Type=udp receiver child=3 sock=10.208.194.26:5061 Process:: ID=5 PID=11731 Type=udp receiver child=4 sock=10.208.194.26:5061 Process:: ID=6 PID=11732 Type=udp receiver child=5 sock=10.208.194.26:5061 Process:: ID=7 PID=11733 Type=udp receiver child=6 sock=10.208.194.26:5061 Process:: ID=8 PID=11734 Type=udp receiver child=7 sock=10.208.194.26:5061 Process:: ID=9 PID=11735 Type=udp receiver child=8 sock=10.208.194.26:5061 Process:: ID=10 PID=11736 Type=udp receiver child=9 sock=10.208.194.26:5061 Process:: ID=11 PID=11737 Type=udp receiver child=10 sock=10.208.194.26:5061 Process:: ID=12 PID=11738 Type=udp receiver child=11 sock=10.208.194.26:5061 Process:: ID=13 PID=11739 Type=udp receiver child=12 sock=10.208.194.26:5061 Process:: ID=14 PID=11740 Type=udp receiver child=13 sock=10.208.194.26:5061 Process:: ID=15 PID=11741 Type=udp receiver child=14 sock=10.208.194.26:5061 Process:: ID=16 PID=11742 Type=udp receiver child=15 sock=10.208.194.26:5061 Process:: ID=17 PID=11743 Type=slow timer Process:: ID=18 PID=11744 Type=timer Process:: ID=19 PID=11745 Type=secondary timer Process:: ID=20 PID=11746 Type=MI FIFO Process:: ID=21 PID=11747 Type=USRLOC Timer Process:: ID=22 PID=11748 Type=USRLOC Timer Process:: ID=23 PID=11749 Type=USRLOC Timer Process:: ID=24 PID=11750 Type=USRLOC Timer Process:: ID=25 PID=11751 Type=ctl handler Process:: ID=26 PID=11752 Type=RTIMER SEC EXEC Process:: ID=27 PID=11753 Type=TIMER NH Process:: ID=28 PID=11754 Type=tcp receiver (generic) child=0 Process:: ID=29 PID=11755 Type=tcp receiver (generic) child=1 Process:: ID=30 PID=11756 Type=tcp receiver (generic) child=2 Process:: ID=31 PID=11757 Type=tcp receiver (generic) child=3 Process:: ID=32 PID=11758 Type=tcp receiver (generic) child=4 Process:: ID=33 PID=11759 Type=tcp receiver (generic) child=5 Process:: ID=34 PID=11760 Type=tcp receiver (generic) child=6 Process:: ID=35 PID=11761 Type=tcp receiver (generic) child=7 Process:: ID=36 PID=11762 Type=tcp receiver (generic) child=8 Process:: ID=37 PID=11763 Type=tcp receiver (generic) child=9 Process:: ID=38 PID=11764 Type=tcp receiver (generic) child=10 Process:: ID=39 PID=11765 Type=tcp receiver (generic) child=11 Process:: ID=40 PID=11766 Type=tcp receiver (generic) child=12 Process:: ID=41 PID=11767 Type=tcp receiver (generic) child=13 Process:: ID=42 PID=11768 Type=tcp receiver (generic) child=14 Process:: ID=43 PID=11769 Type=tcp receiver (generic) child=15 Process:: ID=44 PID=11770 Type=tcp main process Can anyone address me to find out this happens, please? Please let me know if you need further information... Thanks in advance, Best Regards Tomas Tomas Zanet R&D Software Designer tzanet(a)came.com CAME S.p.A.

4 5

Using DNS hostname with the Dispatcher module to determine online routes
by Thomas Cavill 09 Mar '20

09 Mar '20

Hi all, I am wondering if it is possible for the dispatcher module to monitor multiple endpoints that resolve from a single hostname using DNS. Can I configure a single DNS name in the dispatcher table which resolves to 3 IP addresses and have them monitored by OPTIONS pings, and then select the first one that is marked as active to route requests to? I haven't found much help online to know if this is possible/supported. i.e. Does the dispatcher module support monitoring of multiple results returned from DNS NAPTR records? Thanks, Tom

2 1

usrloc db_mode 2 and dropped contacts
by Alex Balashov 09 Mar '20

09 Mar '20

Hi, On 4.4.7, since switching to db_mode 2 for usrloc with the following settings: modparam("usrloc", "db_mode", 2) modparam("usrloc", "timer_procs", 2) modparam("usrloc", "skip_remote_socket", 1) modparam("usrloc", "timer_interval", 30) modparam("usrloc", "matching_mode", 0) I seem to run into a situation where, despite starting from zero local registrations and an empty DB `location` table, out of ~1700 registrations visible in the runtime usrloc table, about 60-80 never make it into the database. This is because they're being continuously UPDATE'd rather than INSERT'd, so there is some presumption that they should already be in the Postgres database. But they're not. This gap seems to very slowly grow over time. I understand that this option is intended to deal with a scenario like that: https://kamailio.org/docs/modules/5.3.x/modules/usrloc.html#usrloc.p.db_che… but the documentation doesn't say it needs to be on for db_mode 2 to work correctly, and it's off by default. I'm wondering what causes certain registrants to get into this state in the first place, where the registrar presumes that they've already been synced to the DB and only need to be update'd on renewal, where in fact they have not been synced. Causes I've ruled out: 1) The contacts being ignored due to non-local socket or other invalidation; 2) Contacts being explicitly deleted by an outside process. Any ideas appreciated! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

4 8

problem in sending out calls
by Mohammad Reza Keshavarzianpoor 06 Mar '20

06 Mar '20

Hi, I installed kamailio and siremis. I receive incoming calls from gateway and all is ok. but about sending out calls using dynamic routes I have problem, always I get "not found" error on calling out phone numbers. 1.I need to send my did number with call to approved by gateway 2.do drouting module needs to enabled by config file? 3. if any better solution than drouting, write please, all I need is every subscriber have its did number and route on outgoing calls too. Thanks

1 0

problem in sending out calls to gateway
by Mohammad Reza Keshavarzianpoor 06 Mar '20

06 Mar '20

Hi, I installed kamailio and siremis. I receive incoming calls from gateway and all is ok. but about sending out calls using dynamic routes I have problem, always I get "not found" error on calling out phone numbers. 1.I need to send my did number with call to approved by gateway 2.do drouting module needs to enabled by config file? 3. if any better solution than drouting, write please, all I need is every subscriber have its did number and route on outgoing calls too. Thanks

1 0

rtpengine failover in same SIP dialog with response Unknown call-ide
by Michal Popovic 06 Mar '20

06 Mar '20

Hi, we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms. configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 udp:10.0.0.2:2222") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 udp:10.0.0.4:2222") INVITE request from kamailio to 10.0.0.1:2222 3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere RESPONSE 6:result2:oke ANSWER request is than send to 10.0.0.2:2222 with error 3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere RESPONSE d6:result5:error12:error-reason15:Unknown call-ide Only possible fix is to have only one setid with only one server. First RTPengine is not marked as failed in list of rtpengine servers after the first response.

2 5

uac_replace_from in 200 OK of BYE
by Grant Bagdasarian 06 Mar '20

06 Mar '20

Hello, We've been using the uac_replace_from function to anonymize the From header to anonymous(a)anonymous.invalid<mailto:anonymous@anonymous.invalid>. The uac module makes use of the dialog module for restoring the original URI. Everything works fine, except when the callee sends the BYE request (replaced uri is present in To header): the 200 OK received by the callee of the BYE suddenly contains the original URI in the To header. We're running Kamailio 5.1. Is this a known bug or limitation of the uac module? Any way to have this replaced correctly (preferably automatically by uac module)? Regards, Grant

3 4

Kamailio Websocket Module call hangup issue with freeswitch
by Murugan Pandian 06 Mar '20

06 Mar '20

Hello, We are using Kamailio as a register freeswitch as a Media server for SIP its working fine with out any issue. But when we use Websocket module (WebRTC) i can able to register and make call , Even call also connected from browser to PSTN but call will disconnect after 30 seconds look like ICE gathering issue can i know its NAT issue Proxy issue. Regard's Murugan Panidan

2 2

sip domain
by Joli Martinez 05 Mar '20

05 Mar '20

Hello, We have several SIP domains coming into our SBC. I need to build a Kamailio box that will 302 the call to the appropriate server based on the domain. If the call does not come in with a recognized domain I would like for it to 404 the call. Not sure how to do this. Can someone point me in the right direction?

5 5

Unexpected behavior on tmrec with monthly recurrence
by David Gonçalves 04 Mar '20

04 Mar '20

Hi, During some tests with the module tmrec, we stumble upon an unexpected behavior of the monthly recurrence with days of the week. The last week does not match our expected date. For example, the last Monday of March 2020 is day 30 (fifth Monday of the month) however, neither the 5MO or -1MO configuration on the bday parameter match with a timestamp configured to day 30. The same situation is verified on months with only 4 weeks. To easily explain the behavior we create this configuration: $var(ts)="1584355625"; # Monday, March 16, 2020 10:47:05 if(tmrec_match("20200101T090000|PT8H|monthly||1|3MO||||","$(var(ts){s.int})")) { xlog("L_INFO","Epoch $var(ts) matches with 3MO\n"); }else{ xlog("L_INFO","Epoch $var(ts) doesn't match with 3MO\n"); } $var(ts)="1584960425"; # Monday, March 23, 2020 10:47:05 if(tmrec_match("20200101T090000|PT8H|monthly||1|4MO||||","$(var(ts){s.int})")) { xlog("L_INFO","Epoch $var(ts) matches with 4MO\n"); }else{ xlog("L_INFO","Epoch $var(ts) doesn't match with 4MO\n"); } $var(ts)="1585565225"; # Monday, March 30, 2020 10:47:05 if(tmrec_match("20200101T090000|PT8H|monthly||1|5MO||||","$(var(ts){s.int })")){ xlog("L_INFO","Epoch $var(ts) matches with 5MO\n"); }else{ xlog("L_INFO","Epoch $var(ts) doesn't match with 5MO\n"); } $var(ts)="1584960425"; # Monday, March 23, 2020 10:47:05 if(tmrec_match("20200101T090000|PT8H|monthly||1|-1MO||||","$(var(ts){s.int })")){ xlog("L_INFO","Epoch $var(ts) matches with -1MO\n"); }else{ xlog("L_INFO","Epoch $var(ts) doesn't match with -1MO\n"); } The results were: Epoch 1584355625 matches with 3MO Epoch 1584960425 matches with 4MO Epoch 1585565225 doesn't match with 5MO Epoch 1584960425 matches with -1MO Are we configuring the tmrec_match wrongly? -- Cumprimentos / Best regards, *David Gonçalves* Research and Development Technician Phone: +351 256 370 980 Email: david.goncalves(a)itcenter.com.pt

2 5

Outbound calling with user based carrier
by Gaurav Bmotra 04 Mar '20

04 Mar '20

Hi Is it possible to configure user based carrier on kamailio for outbound calling ? Thank you Regards

2 1

Help me open ports for my kamailio
by Stefan Troplev 04 Mar '20

04 Mar '20

Hi, I've been struggling around with my kamailio configuration. I've managed to install kamailio on Ubuntu Server and configured 2 clients, I've registered them in Zoiper to my server. They can call each other, but are unable to talk. There is no audio heard. Ports opened on the router are 20000-30000 UDP and both TCP and UDP for 5060 and 5062. Are these ports correctly opened? Thank you. kamailio.cfg > #!KAMAILIO > #!define WITH_MYSQL > #!define WITH_AUTH > #!define WITH_USRLOCDB > #!define WITH_ACCDB > # > # Kamailio (OpenSER) SIP Server v5.2 - default configuration script > # - web: https://www.kamailio.org > # - git: https://github.com/kamailio/kamailio > # > # Direct your questions about this file to: <sr-users(a)lists.kamailio.org> > # > # Refer to the Core CookBook at https://www.kamailio.org/wiki/ > # for an explanation of possible statements, functions and parameters. > # > # Note: the comments can be: > # - lines starting with #, but not the pre-processor directives, > # which start with #!, like #!define, #!ifdef, #!endif, #!else, > #!trydef, > # #!subst, #!substdef, ... > # - lines starting with // > # - blocks enclosed in between /* */ > # > # Several features can be enabled using '#!define WITH_FEATURE' directives: > # > # *** To run in debug mode: > # - define WITH_DEBUG > # > # *** To enable mysql: > # - define WITH_MYSQL > # > # *** To enable authentication execute: > # - enable mysql > # - define WITH_AUTH > # - add users using 'kamctl' > # > # *** To enable IP authentication execute: > # - enable mysql > # - enable authentication > # - define WITH_IPAUTH > # - add IP addresses with group id '1' to 'address' table > # > # *** To enable persistent user location execute: > # - enable mysql > # - define WITH_USRLOCDB > # > # *** To enable presence server execute: > # - enable mysql > # - define WITH_PRESENCE > # > # *** To enable nat traversal execute: > # - define WITH_NAT > # - install RTPProxy: http://www.rtpproxy.org > # - start RTPProxy: > # rtpproxy -l _your_public_ip_ -s udp:localhost:7722 > # - option for NAT SIP OPTIONS keepalives: WITH_NATSIPPING > # > # *** To enable PSTN gateway routing execute: > # - define WITH_PSTN > # - set the value of pstn.gw_ip > # - check route[PSTN] for regexp routing condition > # > # *** To enable database aliases lookup execute: > # - enable mysql > # - define WITH_ALIASDB > # > # *** To enable speed dial lookup execute: > # - enable mysql > # - define WITH_SPEEDDIAL > # > # *** To enable multi-domain support execute: > # - enable mysql > # - define WITH_MULTIDOMAIN > # > # *** To enable TLS support execute: > # - adjust CFGDIR/tls.cfg as needed > # - define WITH_TLS > # > # *** To enable XMLRPC support execute: > # - define WITH_XMLRPC > # - adjust route[XMLRPC] for access policy > # > # *** To enable anti-flood detection execute: > # - adjust pike and htable=>ipban settings as needed (default is > # block if more than 16 requests in 2 seconds and ban for 300 > seconds) > # - define WITH_ANTIFLOOD > # > # *** To block 3XX redirect replies execute: > # - define WITH_BLOCK3XX > # > # *** To block 401 and 407 authentication replies execute: > # - define WITH_BLOCK401407 > # > # *** To enable VoiceMail routing execute: > # - define WITH_VOICEMAIL > # - set the value of voicemail.srv_ip > # - adjust the value of voicemail.srv_port > # > # *** To enhance accounting execute: > # - enable mysql > # - define WITH_ACCDB > # - add following columns to database > #!ifdef ACCDB_COMMENT > ALTER TABLE acc ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; > ALTER TABLE acc ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; > ALTER TABLE acc ADD COLUMN src_ip varchar(64) NOT NULL default ''; > ALTER TABLE acc ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; > ALTER TABLE acc ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; > ALTER TABLE acc ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; > ALTER TABLE missed_calls ADD COLUMN src_user VARCHAR(64) NOT NULL > DEFAULT ''; > ALTER TABLE missed_calls ADD COLUMN src_domain VARCHAR(128) NOT NULL > DEFAULT ''; > ALTER TABLE missed_calls ADD COLUMN src_ip varchar(64) NOT NULL default > ''; > ALTER TABLE missed_calls ADD COLUMN dst_ouser VARCHAR(64) NOT NULL > DEFAULT ''; > ALTER TABLE missed_calls ADD COLUMN dst_user VARCHAR(64) NOT NULL > DEFAULT ''; > ALTER TABLE missed_calls ADD COLUMN dst_domain VARCHAR(128) NOT NULL > DEFAULT ''; > #!endif > > ####### Include Local Config If Exists ######### > import_file "kamailio-local.cfg" > > ####### Defined Values ######### > > # *** Value defines - IDs used later in config > #!ifdef WITH_MYSQL > # - database URL - used to connect to database server by modules such > # as: auth_db, acc, usrloc, a.s.o. > #!ifndef DBURL > #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" > #!endif > #!endif > #!ifdef WITH_MULTIDOMAIN > # - the value for 'use_domain' parameters > #!define MULTIDOMAIN 1 > #!else > #!define MULTIDOMAIN 0 > #!endif > > # - flags > # FLT_ - per transaction (message) flags > # FLB_ - per branch flags > #!define FLT_ACC 1 > #!define FLT_ACCMISSED 2 > #!define FLT_ACCFAILED 3 > #!define FLT_NATS 5 > > #!define FLB_NATB 6 > #!define FLB_NATSIPPING 7 > > ####### Global Parameters ######### > > ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR > #!ifdef WITH_DEBUG > debug=4 > log_stderror=yes > #!else > debug=2 > log_stderror=no > #!endif > > memdbg=5 > memlog=5 > > log_facility=LOG_LOCAL0 > log_prefix="{$mt $hdr(CSeq) $ci} " > > /* number of SIP routing processes for each UDP socket > * - value inherited by tcp_children and sctp_children when not set > explicitely */ > children=8 > > /* uncomment the next line to disable TCP (default on) */ > # disable_tcp=yes > > /* number of SIP routing processes for all TCP/TLS sockets */ > # tcp_children=8 > > /* uncomment the next line to disable the auto discovery of local aliases > * based on reverse DNS on IPs (default on) */ > # auto_aliases=no > > /* add local domain aliases */ > # alias="sip.mydomain.com" > > /* uncomment and configure the following line if you want Kamailio to > * bind on a specific interface/port/proto (default bind on all available) > */ > # listen=udp:10.0.0.10:5060 > listen=udp:192.168.1.127:5060 advertise PublicIP:5060 > /* life time of TCP connection when there is no traffic > * - a bit higher than registration expires to cope with UA behind NAT */ > tcp_connection_lifetime=3605 > > /* upper limit for TCP connections (it includes the TLS connections) */ > tcp_max_connections=2048 > > #!ifdef WITH_TLS > enable_tls=yes > > /* upper limit for TLS connections */ > tls_max_connections=2048 > #!endif > > ####### Custom Parameters ######### > > /* These parameters can be modified runtime via RPC interface > * - see the documentation of 'cfg_rpc' module. > * > * Format: group.id = value 'desc' description > * Access: $sel(cfg_get.group.id) or @cfg_get.group.id */ > > #!ifdef WITH_PSTN > /* PSTN GW Routing > * > * - pstn.gw_ip: valid IP or hostname as string value, example: > * pstn.gw_ip = "10.0.0.101" desc "My PSTN GW Address" > * > * - by default is empty to avoid misrouting */ > pstn.gw_ip = "" desc "PSTN GW Address" > pstn.gw_port = "" desc "PSTN GW Port" > #!endif > > #!ifdef WITH_VOICEMAIL > /* VoiceMail Routing on offline, busy or no answer > * > * - by default Voicemail server IP is empty to avoid misrouting */ > voicemail.srv_ip = "" desc "VoiceMail IP Address" > voicemail.srv_port = "5060" desc "VoiceMail Port" > #!endif > > ####### Modules Section ######## > > /* set paths to location of modules */ > # mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" > > #!ifdef WITH_MYSQL > loadmodule "db_mysql.so" > #!endif > > loadmodule "jsonrpcs.so" > loadmodule "kex.so" > loadmodule "corex.so" > loadmodule "tm.so" > loadmodule "tmx.so" > loadmodule "sl.so" > loadmodule "rr.so" > loadmodule "pv.so" > loadmodule "maxfwd.so" > loadmodule "usrloc.so" > loadmodule "registrar.so" > loadmodule "textops.so" > loadmodule "siputils.so" > loadmodule "xlog.so" > loadmodule "sanity.so" > loadmodule "ctl.so" > loadmodule "cfg_rpc.so" > loadmodule "acc.so" > loadmodule "counters.so" > > #!ifdef WITH_AUTH > loadmodule "auth.so" > loadmodule "auth_db.so" > #!ifdef WITH_IPAUTH > loadmodule "permissions.so" > #!endif > #!endif > > #!ifdef WITH_ALIASDB > loadmodule "alias_db.so" > #!endif > > #!ifdef WITH_SPEEDDIAL > loadmodule "speeddial.so" > #!endif > > #!ifdef WITH_MULTIDOMAIN > loadmodule "domain.so" > #!endif > > #!ifdef WITH_PRESENCE > loadmodule "presence.so" > loadmodule "presence_xml.so" > #!endif > > #!ifdef WITH_NAT > loadmodule "nathelper.so" > loadmodule "rtpproxy.so" > #!endif > > #!ifdef WITH_TLS > loadmodule "tls.so" > #!endif > > #!ifdef WITH_ANTIFLOOD > loadmodule "htable.so" > loadmodule "pike.so" > #!endif > > #!ifdef WITH_XMLRPC > loadmodule "xmlrpc.so" > #!endif > > #!ifdef WITH_DEBUG > loadmodule "debugger.so" > #!endif > > # ----------------- setting module-specific parameters --------------- > > > # ----- jsonrpcs params ----- > modparam("jsonrpcs", "pretty_format", 1) > /* set the path to RPC fifo control file */ > # modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo") > /* set the path to RPC unix socket control file */ > # modparam("jsonrpcs", "dgram_socket", > "/var/run/kamailio/kamailio_rpc.sock") > > # ----- ctl params ----- > /* set the path to RPC unix socket control file */ > # modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") > > # ----- tm params ----- > # auto-discard branches from previous serial forking leg > modparam("tm", "failure_reply_mode", 3) > # default retransmission timeout: 30sec > modparam("tm", "fr_timer", 30000) > # default invite retransmission timeout after 1xx: 120sec > modparam("tm", "fr_inv_timer", 120000) > > # ----- rr params ----- > # set next param to 1 to add value to ;lr param (helps with some UAs) > modparam("rr", "enable_full_lr", 0) > # do not append from tag to the RR (no need for this script) > modparam("rr", "append_fromtag", 0) > > # ----- registrar params ----- > modparam("registrar", "method_filtering", 1) > /* uncomment the next line to disable parallel forking via location */ > # modparam("registrar", "append_branches", 0) > /* uncomment the next line not to allow more than 10 contacts per AOR */ > # modparam("registrar", "max_contacts", 10) > /* max value for expires of registrations */ > modparam("registrar", "max_expires", 3600) > /* set it to 1 to enable GRUU */ > modparam("registrar", "gruu_enabled", 0) > > # ----- acc params ----- > /* what special events should be accounted ? */ > modparam("acc", "early_media", 0) > modparam("acc", "report_ack", 0) > modparam("acc", "report_cancels", 0) > /* by default ww do not adjust the direct of the sequential requests. > * if you enable this parameter, be sure the enable "append_fromtag" > * in "rr" module */ > modparam("acc", "detect_direction", 0) > /* account triggers (flags) */ > modparam("acc", "log_flag", FLT_ACC) > modparam("acc", "log_missed_flag", FLT_ACCMISSED) > modparam("acc", "log_extra", > "src_user=$fU;src_domain=$fd;src_ip=$si;" > "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") > modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) > /* enhanced DB accounting */ > #!ifdef WITH_ACCDB > modparam("acc", "db_flag", FLT_ACC) > modparam("acc", "db_missed_flag", FLT_ACCMISSED) > modparam("acc", "db_url", DBURL) > modparam("acc", "db_extra", > "src_user=$fU;src_domain=$fd;src_ip=$si;" > "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") > #!endif > > # ----- usrloc params ----- > /* enable DB persistency for location entries */ > #!ifdef WITH_USRLOCDB > modparam("usrloc", "db_url", DBURL) > modparam("usrloc", "db_mode", 2) > modparam("usrloc", "use_domain", MULTIDOMAIN) > #!endif > > # ----- auth_db params ----- > #!ifdef WITH_AUTH > modparam("auth_db", "db_url", DBURL) > modparam("auth_db", "calculate_ha1", yes) > modparam("auth_db", "password_column", "password") > modparam("auth_db", "load_credentials", "") > modparam("auth_db", "use_domain", MULTIDOMAIN) > > # ----- permissions params ----- > #!ifdef WITH_IPAUTH > modparam("permissions", "db_url", DBURL) > modparam("permissions", "db_mode", 1) > #!endif > > #!endif > > # ----- alias_db params ----- > #!ifdef WITH_ALIASDB > modparam("alias_db", "db_url", DBURL) > modparam("alias_db", "use_domain", MULTIDOMAIN) > #!endif > > # ----- speeddial params ----- > #!ifdef WITH_SPEEDDIAL > modparam("speeddial", "db_url", DBURL) > modparam("speeddial", "use_domain", MULTIDOMAIN) > #!endif > > # ----- domain params ----- > #!ifdef WITH_MULTIDOMAIN > modparam("domain", "db_url", DBURL) > /* register callback to match myself condition with domains list */ > modparam("domain", "register_myself", 1) > #!endif > > #!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 > > #!ifdef WITH_NAT > # ----- rtpproxy params ----- > modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") > > # ----- nathelper params ----- > modparam("nathelper", "natping_interval", 30) > modparam("nathelper", "ping_nated_only", 1) > modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) > modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") > > # params needed for NAT traversal in other modules > modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") > modparam("usrloc", "nat_bflag", FLB_NATB) > #!endif > > #!ifdef WITH_TLS > # ----- tls params ----- > modparam("tls", "config", "/etc/kamailio/tls.cfg") > #!endif > > #!ifdef WITH_ANTIFLOOD > # ----- pike params ----- > modparam("pike", "sampling_time_unit", 2) > modparam("pike", "reqs_density_per_unit", 16) > modparam("pike", "remove_latency", 4) > > # ----- htable params ----- > /* ip ban htable with autoexpire after 5 minutes */ > modparam("htable", "htable", "ipban=>size=8;autoexpire=300;") > #!endif > > #!ifdef WITH_XMLRPC > # ----- xmlrpc params ----- > modparam("xmlrpc", "route", "XMLRPC"); > modparam("xmlrpc", "url_match", "^/RPC") > #!endif > > #!ifdef WITH_DEBUG > # ----- debugger params ----- > modparam("debugger", "cfgtrace", 1) > modparam("debugger", "log_level_name", "exec") > #!endif > > ####### Routing Logic ######## > > > /* Main SIP request routing logic > * - processing of any incoming SIP request starts with this route > * - note: this is the same as route { ... } */ > request_route { > > # per request initial checks > route(REQINIT); > > # NAT detection > route(NATDETECT); > > # CANCEL processing > if (is_method("CANCEL")) { > if (t_check_trans()) { > route(RELAY); > } > exit; > } > > # handle retransmissions > if (!is_method("ACK")) { > if(t_precheck_trans()) { > t_check_trans(); > exit; > } > t_check_trans(); > } > > # handle requests within SIP dialogs > route(WITHINDLG); > > ### only initial requests (no To tag) > > # authentication > route(AUTH); > > # record routing for dialog forming requests (in case they are routed) > # - remove preloaded route headers > remove_hf("Route"); > if (is_method("INVITE|SUBSCRIBE")) { > record_route(); > } > > # account only INVITEs > if (is_method("INVITE")) { > setflag(FLT_ACC); # do accounting > } > > # dispatch requests to foreign domains > route(SIPOUT); > > ### requests for my local domains > > # handle presence related requests > route(PRESENCE); > > # handle registrations > route(REGISTRAR); > > if ($rU==$null) { > # request with no Username in RURI > sl_send_reply("484","Address Incomplete"); > exit; > } > > # dispatch destinations to PSTN > route(PSTN); > > # user location service > route(LOCATION); > } > > # Wrapper for relaying requests > route[RELAY] { > > # enable additional event routes for forwarded requests > # - serial forking, RTP relaying handling, a.s.o. > if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { > if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); > } > if (is_method("INVITE|SUBSCRIBE|UPDATE")) { > if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); > } > if (is_method("INVITE")) { > if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); > } > > if (!t_relay()) { > sl_reply_error(); > } > exit; > } > > # Per SIP request initial checks > route[REQINIT] { > #!ifdef WITH_ANTIFLOOD > # flood detection from same IP and traffic ban for a while > # be sure you exclude checking trusted peers, such as pstn gateways > # - local host excluded (e.g., loop to self) > if(src_ip!=myself) { > if($sht(ipban=>$si)!=$null) { > # ip is already blocked > xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); > exit; > } > if (!pike_check_req()) { > xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); > $sht(ipban=>$si) = 1; > exit; > } > } > #!endif > if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { > # silent drop for scanners - uncomment next line if want to reply > # sl_send_reply("200", "OK"); > exit; > } > > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > exit; > } > > if(is_method("OPTIONS") && uri==myself && $rU==$null) { > sl_send_reply("200","Keepalive"); > exit; > } > > if(!sanity_check("17895", "7")) { > xlog("Malformed SIP message from $si:$sp\n"); > exit; > } > } > > # Handle requests within SIP dialogs > route[WITHINDLG] { > if (!has_totag()) return; > > # sequential request withing a dialog should > # take the path determined by record-routing > if (loose_route()) { > route(DLGURI); > if (is_method("BYE")) { > setflag(FLT_ACC); # do accounting ... > setflag(FLT_ACCFAILED); # ... even if the transaction fails > } else if ( is_method("ACK") ) { > # ACK is forwarded statelessly > route(NATMANAGE); > } else if ( is_method("NOTIFY") ) { > # Add Record-Route for in-dialog NOTIFY as per RFC 6665. > record_route(); > } > route(RELAY); > exit; > } > > if (is_method("SUBSCRIBE") && uri == myself) { > # in-dialog subscribe requests > route(PRESENCE); > exit; > } > if ( is_method("ACK") ) { > if ( t_check_trans() ) { > # no loose-route, but stateful ACK; > # must be an ACK after a 487 > # or e.g. 404 from upstream server > route(RELAY); > exit; > } else { > # ACK without matching transaction ... ignore and discard > exit; > } > } > sl_send_reply("404","Not here"); > exit; > } > > # Handle SIP registrations > route[REGISTRAR] { > if (!is_method("REGISTER")) return; > > if(isflagset(FLT_NATS)) { > setbflag(FLB_NATB); > #!ifdef WITH_NATSIPPING > # do SIP NAT pinging > setbflag(FLB_NATSIPPING); > #!endif > } > if (!save("location")) { > sl_reply_error(); > } > exit; > } > > # User location service > route[LOCATION] { > > #!ifdef WITH_SPEEDDIAL > # search for short dialing - 2-digit extension > if($rU=~"^[0-9][0-9]$") { > if(sd_lookup("speed_dial")) { > route(SIPOUT); > } > } > #!endif > > #!ifdef WITH_ALIASDB > # search in DB-based aliases > if(alias_db_lookup("dbaliases")) { > route(SIPOUT); > } > #!endif > > $avp(oexten) = $rU; > if (!lookup("location")) { > $var(rc) = $rc; > route(TOVOICEMAIL); > t_newtran(); > switch ($var(rc)) { > case -1: > case -3: > send_reply("404", "Not Found"); > exit; > case -2: > send_reply("405", "Method Not Allowed"); > exit; > } > } > > # when routing via usrloc, log the missed calls also > if (is_method("INVITE")) { > setflag(FLT_ACCMISSED); > } > > route(RELAY); > exit; > } > > # Presence server processing > route[PRESENCE] { > if(!is_method("PUBLISH|SUBSCRIBE")) return; > > if(is_method("SUBSCRIBE") && $hdr(Event)=="message-summary") { > route(TOVOICEMAIL); > # returns here if no voicemail server is configured > sl_send_reply("404", "No voicemail service"); > exit; > } > > #!ifdef WITH_PRESENCE > if (!t_newtran()) { > sl_reply_error(); > exit; > } > > if(is_method("PUBLISH")) { > handle_publish(); > t_release(); > } else if(is_method("SUBSCRIBE")) { > handle_subscribe(); > t_release(); > } > exit; > #!endif > > # if presence enabled, this part will not be executed > if (is_method("PUBLISH") || $rU==$null) { > sl_send_reply("404", "Not here"); > exit; > } > return; > } > > # IP authorization and user authentication > route[AUTH] { > #!ifdef WITH_AUTH > > #!ifdef WITH_IPAUTH > if((!is_method("REGISTER")) && allow_source_address()) { > # source IP allowed > return; > } > #!endif > > 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(); > } > # if caller is not local subscriber, then check if it calls > # a local destination, otherwise deny, not an open relay here > if (from_uri!=myself && uri!=myself) { > sl_send_reply("403","Not relaying"); > exit; > } > > #!else > > # authentication not enabled - do not relay at all to foreign networks > if(uri!=myself) { > sl_send_reply("403","Not relaying"); > exit; > } > > #!endif > return; > } > > # Caller NAT detection > route[NATDETECT] { > #!ifdef WITH_NAT > force_rport(); > if (nat_uac_test("19")) { > if (is_method("REGISTER")) { > fix_nated_register(); > } else { > if(is_first_hop()) { > set_contact_alias(); > } > } > setflag(FLT_NATS); > } > #!endif > return; > } > > # RTPProxy control and signaling updates for NAT traversal > route[NATMANAGE] { > #!ifdef WITH_NAT > if (is_request()) { > if(has_totag()) { > if(check_route_param("nat=yes")) { > setbflag(FLB_NATB); > } > } > } > if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; > > if(nat_uac_test("8")) { > rtpproxy_manage("co"); > } else { > rtpproxy_manage("cor"); > } > > if (is_request()) { > if (!has_totag()) { > if(t_is_branch_route()) { > add_rr_param(";nat=yes"); > } > } > } > if (is_reply()) { > if(isbflagset(FLB_NATB)) { > if(is_first_hop()) > set_contact_alias(); > } > } > #!endif > return; > } > > # URI update for dialog requests > route[DLGURI] { > #!ifdef WITH_NAT > if(!isdsturiset()) { > handle_ruri_alias(); > } > #!endif > return; > } > > # Routing to foreign domains > route[SIPOUT] { > if (uri==myself) return; > > append_hf("P-hint: outbound\r\n"); > route(RELAY); > exit; > } > > # PSTN GW routing > route[PSTN] { > #!ifdef WITH_PSTN > # check if PSTN GW IP is defined > if (strempty($sel(cfg_get.pstn.gw_ip))) { > xlog("SCRIPT: PSTN routing enabled but pstn.gw_ip not defined\n"); > return; > } > > # route to PSTN dialed numbers starting with '+' or '00' > # (international format) > # - update the condition to match your dialing rules for PSTN routing > if(!($rU=~"^(\+|00)[1-9][0-9]{3,20}$")) return; > > # only local users allowed to call > if(from_uri!=myself) { > sl_send_reply("403", "Not Allowed"); > exit; > } > > # normalize target number for pstn gateway > # - convert leading 00 to + > if (starts_with("$rU", "00")) { > strip(2); > prefix("+"); > } > > if (strempty($sel(cfg_get.pstn.gw_port))) { > $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip); > } else { > $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ":" > + $sel(cfg_get.pstn.gw_port); > } > > route(RELAY); > exit; > #!endif > > return; > } > > # XMLRPC routing > #!ifdef WITH_XMLRPC > route[XMLRPC] { > # allow XMLRPC from localhost > if ((method=="POST" || method=="GET") > && (src_ip==127.0.0.1)) { > # close connection only for xmlrpclib user agents (there is a bug in > # xmlrpclib: it waits for EOF before interpreting the response). > if ($hdr(User-Agent) =~ "xmlrpclib") > set_reply_close(); > set_reply_no_connect(); > dispatch_rpc(); > exit; > } > send_reply("403", "Forbidden"); > exit; > } > #!endif > > # Routing to voicemail server > route[TOVOICEMAIL] { > #!ifdef WITH_VOICEMAIL > if(!is_method("INVITE|SUBSCRIBE")) return; > > # check if VoiceMail server IP is defined > if (strempty($sel(cfg_get.voicemail.srv_ip))) { > xlog("SCRIPT: VoiceMail routing enabled but IP not defined\n"); > return; > } > if(is_method("INVITE")) { > if($avp(oexten)==$null) return; > > $ru = "sip:" + $avp(oexten) + "@" + $sel(cfg_get.voicemail.srv_ip) > + ":" + $sel(cfg_get.voicemail.srv_port); > } else { > if($rU==$null) return; > > $ru = "sip:" + $rU + "@" + $sel(cfg_get.voicemail.srv_ip) > + ":" + $sel(cfg_get.voicemail.srv_port); > } > route(RELAY); > exit; > #!endif > > return; > } > > # Manage outgoing branches > branch_route[MANAGE_BRANCH] { > xdbg("new branch [$T_branch_idx] to $ru\n"); > route(NATMANAGE); > } > > # Manage incoming replies > onreply_route[MANAGE_REPLY] { > xdbg("incoming reply\n"); > if(status=~"[12][0-9][0-9]") { > route(NATMANAGE); > } > } > > # Manage failure routing cases > failure_route[MANAGE_FAILURE] { > route(NATMANAGE); > > if (t_is_canceled()) exit; > > #!ifdef WITH_BLOCK3XX > # block call redirect based on 3xx replies. > if (t_check_status("3[0-9][0-9]")) { > t_reply("404","Not found"); > exit; > } > #!endif > > #!ifdef WITH_BLOCK401407 > # block call redirect based on 401, 407 replies. > if (t_check_status("401|407")) { > t_reply("404","Not found"); > exit; > } > #!endif > > #!ifdef WITH_VOICEMAIL > # serial forking > # - route to voicemail on busy or no answer (timeout) > if (t_check_status("486|408")) { > $du = $null; > route(TOVOICEMAIL); > exit; > } > #!endif > } > # The Kamailio configuration file for the control tools. # # Here you can set variables used in the kamctl and kamdbctl setup # scripts. Per default all variables here are commented out, the control tools # will use their internal default values. ## your SIP domain SIP_DOMAIN=192.168.1.127 ## chrooted directory # $CHROOT_DIR="/path/to/chrooted/directory" ## database type: MYSQL, PGSQL, ORACLE, DB_BERKELEY, DBTEXT, or SQLITE # by default none is loaded # # If you want to setup a database with kamdbctl, you must at least specify # this parameter. DBENGINE=MYSQL ## database host DBHOST=localhost ## database port DBPORT=3306 ## database name (for ORACLE this is TNS name) DBNAME=kamailio # database path used by dbtext, db_berkeley or sqlite # DB_PATH="/usr/local/etc/kamailio/dbtext" ## database read/write user DBRWUSER="kamailio" ## password for database read/write user DBRWPW="kamailiorw" ## database read only user DBROUSER="kamailioro" ## password for database read only user DBROPW="kamailioro" ## database access host (from where is kamctl used) # DBACCESSHOST=192.168.0.1 ## database super user (for ORACLE this is 'scheme-creator' user) # DBROOTUSER="root" ## password for database super user ## - important: this is insecure, targeting the use only for automatic testing ## - known to work for: mysql # DBROOTPW="dbrootpw" ## database character set (used by MySQL when creating database) #CHARSET="latin1" ## user name column # USERCOL="username" # SQL definitions # If you change this definitions here, then you must change them # in db/schema/entities.xml too. # FIXME # FOREVER="2030-05-28 21:32:15" # DEFAULT_Q="1.0" # Program to calculate a message-digest fingerprint # MD5="md5sum" # awk tool # AWK="awk" # gdb tool # GDB="gdb" # If you use a system with a grep and egrep that is not 100% gnu grep compatible, # e.g. solaris, install the gnu grep (ggrep) and specify this below. # # grep tool # GREP="grep" # egrep tool # EGREP="egrep" # sed tool # SED="sed" # tail tool # LAST_LINE="tail -n 1" # expr tool # EXPR="expr" # Describe what additional tables to install. Valid values for the variables # below are yes/no/ask. With ask (default) it will interactively ask the user # for an answer, while yes/no allow for automated, unassisted installs. # # If to install tables for the modules in the EXTRA_MODULES variable. # INSTALL_EXTRA_TABLES=ask # If to install presence related tables. # INSTALL_PRESENCE_TABLES=ask # If to install uid modules related tables. # INSTALL_DBUID_TABLES=ask # Define what module tables should be installed. # If you use the postgres database and want to change the installed tables, then you # must also adjust the STANDARD_TABLES or EXTRA_TABLES variable accordingly in the # kamdbctl.base script. # Kamailio standard modules # STANDARD_MODULES="standard acc lcr domain group permissions registrar usrloc msilo # alias_db uri_db speeddial avpops auth_db pdt dialog dispatcher # dialplan" # Kamailio extra modules # EXTRA_MODULES="imc cpl siptrace domainpolicy carrierroute userblacklist htable purple sca" ## type of aliases used: DB - database aliases; UL - usrloc aliases ## - default: none ALIASES_TYPE="DB" ## control engine: RPCFIFO ## - default RPCFIFO CTLENGINE="RPCFIFO" ## path to FIFO file for engine RPCFIFO RPCFIFOPATH="/var/run/kamailio/kamailio_rpc.fifo" ## check ACL names; default on (1); off (0) # VERIFY_ACL=1 ## ACL names - if VERIFY_ACL is set, only the ACL names from below list ## are accepted # ACL_GROUPS="local ld int voicemail free-pstn" ## check if user exists (used by some commands such as acl); ## - default on (1); off (0) # VERIFY_USER=1 ## verbose - debug purposes - default '0' VERBOSE=1 ## do (1) or don't (0) store plaintext passwords ## in the subscriber table - default '1' # STORE_PLAINTEXT_PW=0 ## Kamailio START Options ## PID file path - default is: /var/run/kamailio/kamailio.pid PID_FILE=/var/run/kamailio/kamailio.pid ## Extra start options - default is: not set # example: start Kamailio with 64MB share memory: STARTOPTIONS="-m 64" # STARTOPTIONS= >

2 3

kamailio 5.2.5 core WARNING
by Andrew Chen 03 Mar '20

03 Mar '20

Hi all, Can someone help shed some light as to what this core WARNING means? root@ashmaintpsg51:/etc/kamailio # kamailio -c kamailio.cfg 0(2192) WARNING: <core> [core/ppcfg.c:220]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 2 Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *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 2

Dynamically change the transport protocol from UDP to TCP to avoid fragmentation
by supreeth herle 03 Mar '20

03 Mar '20

Hello Everyone, I have an IMS setup using Kamailo and is working as expected when the 4G Core Network and IMS is running in a single VM. However, when running in two different VMs registration is successful but calling fails. As per the scripts in kamailio ims example folder for P-CSCF, uac module is used to generate OPTIONS message to achieve a kind of NATPINGING to UEs. The ping achieved in this way times out with 408 when IMS and Core Network is run in different VMs. I suspect that the increasing packets size could be the issue for UE not responding to OPTIONS from P-CSCF (I have verified that OPTIONS message from P-CSCF is reaching the eNB). In this aspect, I would like to switch the transport protocol to TCP when MTU is greater than 1300 (please guide me if my thinking of switching to TCP to tackle NAT issue is wrong). I have explored the following options: tcp_reuse_port=yes udp_mtu=1300 udp_mtu_try_proto=TCP But, when I use these options, any request message which hit 1300 MTU mark are not sent out at all (in my case it is the NOTIFY request from SCSCF) and Kamailio has a warning saying that binding to address failed as the address is already in use. Following is the small part of the log: Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19712]: DEBUG: ims_registrar_scscf [registrar_notify.c:2275]: notification_event_process(): About to free notification Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: PCSCF MO_reply: Destination URI: <null> Request URI: <null> Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present. Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Source IP and Port: (10.4.128.21:6060) Route-URI: Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Received IP and Port: (10.4.128.21:5060) Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Contact header: <sip:scscf.ims.mnc001.mcc001.3gppnetwork.org:6060> Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: ERROR: <script>: NOTIFY (tel:0198765432100 (172.24.15.30:6060) to tel:0198765432100, 4125089758_4268630712(a)192.168.101.2) Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Within DLG Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Within loose route Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: PCSCF MO_indialog: Destination URI: sip:172.24.15.10:5060 Request URI: sip: 192.168.101.2:5060 Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Source IP and Port: (172.24.15.30:6060) Route-URI: sip:mo@172.24.15.30;lr=on;ftag=4125089761 Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Received IP and Port: (10.4.128.21:5060) Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: NOTICE: <script>: Contact header: <sip:scscf.ims.mnc001.mcc001.3gppnetwork.org:6060> Feb 27 14:31:15 epc-ims /usr/local/sbin/kamailio[19730]: WARNING: <core> [core/tcp_main.c:1298]: tcp_do_connect(): binding to source address 10.4.128.21:5060 failed: Address already in use [98] I could be assuming things here about huge packet sizes causing the issue, if anyone has experienced similar issue in NATed scenario please let me know some hints or pointer to solve this. Thanks in advance. Best Regards, Supreeth

1 1

push notification via lua script on tsilo module
by max 03 Mar '20

03 Mar '20

I am expert in voip solution such as Asterisk and familiar with Kamailio .in one of our project we use the linphone app as a client mobile and we have to solved registering issue when extension has been unregistered in background mode. so i try to implement this scenario according federico document and enable extra module like this: loadmodule "tsilo.so" loadmodule "htable.so" #loadmodule "app_lua.so" loadmodule "cfgutils.so" I must disable app_lua.so because i haven't suitable lua script .i think most parts is OK and i can see ts_store parameters: ts.dump { Size: 1024 R-URIs: { R-URI: sip:1003@192.168.1.169:25378;rinstance=6cb3b1cc5efabdfb Hash: -238368019 Transactions: { Transaction: { Tindex: 9977 Tlabel: 1825563922 } } } Stats: { RURIs: 1 Max-Slots: 1 Transactions: 1 } } by the way push notification feature is enable in linphone app . Now i need a script (lua) for handling this issue (push notification for app) when we fetch SEND PUSH route. Could you please advice me ? do you have any example of this script? -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

2 2

Kamailio - Force UAC to re register
by Sharad Kumar 03 Mar '20

03 Mar '20

Hey guys, I am implementing one scenario where I want the help of very smart people. So let’s say one UAC 999 registers to Asterisk 1 server via kamailio and asterisk 1 server goes down. Is there any way I can move that registration to another asterisk server or is there any way I can force UAC to re register so that I can route the new Register to the available asterisk ? Any help will be really appreciated. Thank you

2 1

Siremis web interface issue -- siptrace module active
by Bugaian A. Vitalie 02 Mar '20

02 Mar '20

Hi list, there is an issue in latest git version of Siremis with showing sip method content. If I select it from mysql I see it all good: select * from sip_trace where method = 'INVITE'; If I click it from web interface and select needed method I get only first register from sip_trace table. You can reproduce by /siremis/sipadmin/sip_trace_list <http://sbc.pride.md/siremis/sipadmin/sip_trace_list> then click on the method to see details. I tested on opera and chrome. Same result, something wrong with javascript, its not passing correctly parameter for selecting. Please have a look let me know if I can help. Thanks. Regards Vitalie A. Bugaian

2 9

Strange behaviour on $tu
by Duarte Rocha 02 Mar '20

02 Mar '20

Greetings, I have a cenario with the following header To = "sip:111234567890;npdi@111.222.333.444" If i print $tu I got "sip:111234567890". If i print $hdr(To) I get "sip:111234567890;npdi@111.222.333.444". If i don't include the "npdi" or any other user parameters, it works fine Is this the intended behaviour? Am i doing something wrong here? Best Regards,

2 3

How to detect NAT during authenticated registration of clients which adjust the headers
by Awal Junanto 02 Mar '20

02 Mar '20

Hi, We are building a service where we need to detect NAT when the clients register to our server. We are struggling in analyzing NAT status of some clients which modify their IP addresses/ports in the headers according to the value of "received" parameter sent during "401 Unauthorized" response. Here's the flow: Client->Server REGISTER sip:... Via: SIP/2.0/TLS 192.168.0.1:41157 ;rport;branch=z9hG4bKPj30093e5d-550d-4d4c-a9a2-22c3bd1cda7e;alias Contact: <sip:user@192.168.0.1:42251;transport=TLS;ob> ... Server->Client SIP/2.0 401 Unauthorized Via: SIP/2.0/TLS 192.168.0.1:41157 ;rport;branch=z9hG4bKPj30093e5d-550d-4d4c-a9a2-22c3bd1cda7e;alias;received=1.2.3.4 WWW-Authenticate: ... ... Client->Server REGISTER sip:... Via: SIP/2.0/TLS 1.2.3.4:6201 ;rport;branch=z9hG4bKPj30093e5d-550d-4d4c-a9a2-22c3bd1cda7e;alias Contact: <sip:user@ 1.2.3.4:6201;transport=TLS;ob> Authorization: ... ... By the time the client is authenticated, there is no way to detect whether the request was coming from a natted device or not by just analysing the Via or Contact headers. Thanks in advance.

3 6

using kamailio as sip server
by Mohammad Reza Keshavarzianpoor 02 Mar '20

02 Mar '20

Hi, I'm new to Kamailio I need to have a kamalio as sip server which do a trunk to NGN Center(like a friend peer trunk in freepbx). I need to outgoing calls go through kamailio and forwarded to ngn(multi did values, a range of numbers ...) extensions will register on kamailio I need incoming calls forwarded to an extension or a pbx server, doesn't matter and both are good ... that server will have heavy traffic about 1000 concurrent calls... I tried a successful kamailio installation but I don't know how to config that for my purpose. even I tried installation of dsiprouter over a fresh debian 9 but stopped on pyspark installation. please give me your helps, advises, hints or ideas! best regards

2 1

Re: [SR-Users] dlg.end_dlg on RTP timeout
by Miteshkumar Thakkar 28 Feb '20

28 Feb '20

This is really helpful development. I am facing one issue, when I use this. RTPEngine is sending two "dlg.terminate_dlg" events for single call to kamailio with same call-id but reversed to-tag and from-tag in second event. I believe this is due to two separate RTP streams. Problem here is that - in first event kamailio terminates the call, hence when second event comes, kamailio says - call-id not found and send response back to RTPEngine. But still RTPEngine keeps sending that event message for three more times. Kamailio has to respond to it with call-id not found. Which is overhead. Not recommended for production environment. How can I avoid this? Any help is appreciated. Thank you Mitesh That's great, thank you! Cheers, Daniel On 06.09.18 11:15, Richard Fuchs wrote: >* This is now supported as per * >* https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701… <https://github.com/sipwise/rtpengine/commit/89084da8d820919b44a0244e16e6701…> * > >* Cheers * > >* On 2018-09-05 05:39, Daniel-Constantin Mierla wrote: * >> >>* 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… <https://kamailio.org/docs/modules/5.1.x/modules/dialog.html#dlg.r.terminate…> * >> >>* So it expects something like: * >> >>* <?xml version="1.0" encoding="UTF-8"?> * >>* <methodCall> * >>* <methodName>dlg.terminate_dlg</methodName> * >>* <params> * >>* <param><value><string>_CALLID_VALUE__</string></value></param> * >>* <param><value><string>_FROM_TAG_VALUE__</string></value></param> * >>* <param><value><string>_TO_TAG_VALUE__</string></value></param> * >>* </params> * >>* </methodCall> * >> >>* 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: * >>>> >>>>* <?xml version="1.0" encoding="UTF-8"?> * >>>>* <methodCall> * >>>>* <methodName>teardown</methodName> * >>>>* <params> * >>>>* <param><value><string>_CALLID_VALUE__</string></value></param> * >>>>* </params> * >>>>* </methodCall> * >>>> >>>>* 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 at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>>>>>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>>>> >>>>>>* -- * >>>>>>* Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> * >>>>>>* www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> * >>>>>>* Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> * >>>>>>* Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com> * >>>>>> >>>>>> >>>>>>* _______________________________________________ * >>>>>>* Kamailio (SER) - Users Mailing List * >>>>>>* sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>>>>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>>> >>>>> >>>>>* _______________________________________________ * >>>>>* Kamailio (SER) - Users Mailing List * >>>>>* sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>>>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>> >>>>* -- * >>>>* Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> * >>>>* www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> * >>>>* Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> * >>>>* Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com> * >>> >>> >>>* _______________________________________________ * >>>* Kamailio (SER) - Users Mailing List * >>>* sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >>>* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >> >>* -- * >>* Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com> * >>* www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> * >>* Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com> * >>* Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com <http://www.asipto.com> * > > >* _______________________________________________ * >* Kamailio (SER) - Users Mailing List * >* sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> * >* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <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

2 11

Teams integration
by Bugaian A. Vitalie 28 Feb '20

28 Feb '20

Hello list, its been about one month for me playing with kamailio and I need some help to sort out a real life situation. I followed this guide https://skalatan.de/en/blog/kamailio-sbc-teams; great article, also got some inspiration from here https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/..articles look very similar. I manged to get my calls out to kamailio from TEAMS it works perfectly call gets connected and codec negotiation is fine, but I am facing issue geting the call inbound to TEAMS. My invite looks like this: ======================== U 217.26.163.205:5060 -> 52.114.75.24:5061 #22 INVITE sip:+37360844269@sip.pstnhub.microsoft.com:5061 SIP/2.0. Record-Route: <sip:sbc.pride.md:5061;transport=tls;lr>. Record-Route: <sip:217.26.163.205:5061;nat=yes;lr>. Via: SIP/2.0/UDP 217.26.163.205;branch=z9hG4bK7838.7417f50ed201fcada9609f5b7c4e520f.0. Via: SIP/2.0/UDP 192.168.169.102:5060 ;received=46.214.187.67;branch=z9hG4bK80e3f7e5cc50ea11806b6eeeb899592c;rport=5060. From: "+37379844267" <sip:+37379844267@sbc.pride.md>;tag=1604785394. To: "+37360844269" <sip:+37360844269@sip.pstnhub.microsoft.com:5061 ;user=phone>. Call-ID: 80E3F7E5-CC50-EA11-8069-6EEEB899592C(a)192.168.169.102. CSeq: 227 INVITE. sip:+37379844267@192.168.169.102:5060;gr=008A94E3-CA50-EA11-805B-6EEEB899592C;alias=46.214.187.67~5060~1Content-Type: application/sdp. Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK. Max-Forwards: 69. User-Agent: SIPPER for PhonerLite. Session-Expires: 1800. Supported: 100rel, replaces, from-change, gruu, timer. P-Preferred-Identity: <sip:+37379844267@sbc.pride.md>. Content-Length: 362. Contact: <sip:+37379844267@sbc.pride.md:5061;user=phone;transport=tls>. . v=0. o=- 2307737351 1 IN IP4 217.26.163.205. s=SIPPER for PhonerLite. c=IN IP4 217.26.163.205. t=0 0. m=audio 36864 RTP/SAVP 8 101. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:owGy5+mMZNyO5+9lFmUUOK3WqpEsxJH0+jtWz =============================================== Anybody has a good invite exaple for Teams? Or do you see any issue with my invite? I do use : record_route_preset("sbc.pride.md:5061;transport=tls","217.26.163.205:5060 ;nat=yes"); add_rr_param(";r2=on"); before sending this out. Please let me know if you can help. Thanks. Vitalie.

3 7

Trouble with 302 Redirect
by Jim Leahy 27 Feb '20

27 Feb '20

Hi All, I'm having some issues trying to properly send a '302 Moved Temporarily' reply to the calling UAC (UAC1) when the remote UAC (UAC2) returns a 486 status (Do Not Disturb). The goal is to redirect UAC1 to a voicemail server when UAC2 is in DND. Here are the pertinent parts of my config: route { # drop some things right away route(DROP); # perform sanity check route(SANITYCHECK); # handle registrations if(is_method("REGISTER")) { route(REGISTRATION); exit; } # handle invites if(is_method("INVITE")) { route("INVITE"); exit; } route(RELAY); } route[INVITE] { # add this proxy to the record-route so it stays in the loop record_route(); # if we can find this user in the location DB... if(lookup("location")) { # relay the invite to the new dURI t_on_failure("FOURDIGITFAIL"); t_on_reply("FOURDIGITREPLY"); route(RELAY); # go back to the main route return; } onreply_route[FOURDIGITREPLY] { if(t_check_status("4[0-9]{2}")) { t_reply("302", "Moved Temporarily"); } } I'm having issues with the t_reply in the onreply_route. It successfully sends the reply, but I can't seem to set the Contact header properly. I'm trying to set it to the location of the user's mailbox on the voicemail sever (ie sip:1000@vmpbx.domain.com), but nothing I try works. I've tried: remove_hf("Contact"); insert_hf("Contact: sip:1000@vmpbx.domain.com"); t_reply("302", "Moved Temporarily"); But as I understand it, that just changes the header in the reply from UAC2, not the reply I'm sending to UAC1 Then I tried: append_to_reply("Contact: sip:1000@vmpbx.domain.com" ); t_reply("302", "Moved Temporarily"); But I can't use append_to_reply in an onreply block. How can I change the Contact header in the reply that's sent? Am I just going about this the wrong way? Any help would be appreciated. Thanks

5 4

Rtpproxy not work in 2 kamailio + rtpproxy setup
by Voip support 27 Feb '20

27 Feb '20

Dear Community, I have a problem with rtpproxy not changing the SDP IP in connection information in following scenario: SIP1 -> kamailio1 + rtpproxy1 -> kamailio2 + rtpproxy2 -> SIP2 The first kamailio put SDP IP correctly (from rtpproxy) then the second kamailio does not change SDP connection information. I think its related to SDP body which has: a=nortpproxy:yes line added by kamailio1. So i tried to remove the a=nortpproxy:yes line from SDP before calling rtpproxy_manage. But it looks like no difference in working - i think the SDP sent to rtpproxy is still having the line even when i removed it. The issue is not happening when i remove kamailio1 + rtpproxy1. In that case my IP is put correctly in SDP in INVITE and in 200 OK. In case of two kamailio with rtpproxy (kamailio1 and kamailio2) in signalling path i am getting: rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy for replies (SIP2 IP address in 200OK SDP is present instead of kamailio2 IP address). For request INVITE i am not getting the error but the IP in SDP doesn't change. kamailio2 config is now like below (but the attempt to remove a=nortpproxy:yes, did not work for me) # RTPProxy control and signaling updates for NAT traversal route[NATMANAGE] { #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } # if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; -- commented this out because sometimes rtpproxy was not used and i wanted to use it always # added below code to remove a=nortpproxy:yes from SDP before rtpproxy_manage but its still not working if( has_body("application/sdp") && (1 == sdp_get_line_startswith("$avp(nortpproxy)", "a=nortpproxy" )) ){ sdp_remove_line_by_prefix("a=nortpproxy:yes"); xlog("removed nortpproxy:yes from SDP"); } if(nat_uac_test("8")) { xlog("rtpproxy CO"); rtpproxy_manage("co","MY_PUBLIC_IP_HERE"); } else { xlog("rtpproxy COR"); rtpproxy_manage("cor"," MY_PUBLIC_IP_HERE "); } if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) set_contact_alias(); } } if(isbflagset(FLB_NATB)) { # no connect message in a dialog involving NAT traversal if (is_request()) { if(has_totag()) { set_forward_no_connect(); } } } #!endif return; } Best regards, Tom PS. thanks for any hints to resolve the issue.

2 1

record_route_advertised_address causes null send socket error
by Daniel Greenwald 26 Feb '20

26 Feb '20

I am using record_route_advertised_address to insert a record route header with an SRV record. The header is added correctly and everything appears to be working fine however I get a CRITICAL log error when calling record_route_advertised_address('INTERNAL_SRV'); 2020-02-25T20:14:57.078235+00:00,ip-10-0-16-53: CRITICAL: cbbcfe06-d181-467c-bbf4-78772aa0562f 2 16777053 INVITE:<core> [core/msg_translator.c:514]: lump_check_opt(): null send socket 2020-02-25T20:14:57.078352+00:00,ip-10-0-16-53: CRITICAL: cbbcfe06-d181-467c-bbf4-78772aa0562f 2 16777053 INVITE:<core> [core/msg_translator.c:514]: lump_check_opt(): null send socket Any ideas? I'm considering using insert_hf() to manually add it and bypass whatever check is failing. Thoughts? Thanks

3 7

Access to CANCEL messages sent during parallel forking
by Marco Capetta 26 Feb '20

26 Feb '20

Hi All, I have a question regarding call forking and how to access failed branches: the ones for which kamailio sends out the CANCEL because on another one a 200OK was received. This is the scenario: - A calls B - 3 devices are registered on B, so a parallel forking is done to B1, B2 and B3 - B1, B2, and B3 all reply with 180 Ringing - B1 replies with 200OK - Kamailio CANCELs the branches with B2 and B3 What I need is access to each single CANCEL that Kamailio sends out to B2 and B3. In particular I need to know the branch-id and Via branch of all the cancelled branches. Additionally it would be perfect to have them inside the TM module, in order to have access also to internal AVPs. I tried with dedicated failure routes and also with per-branch failure routes, but I was never able to access to those values. I also didn't found a specific event-route that can help me solve this problem. Does anyone have an idea? Kamailio version 5.2.5 Thanks Regards Marco

3 5

Siremis v5.3.0 Released
by Daniel-Constantin Mierla 26 Feb '20

26 Feb '20

Siremis v5.3.0 is out – the open source web management interface for Kamailio SIP Server. This version comes with major changes and many new features, among them the removal of legacy flash charts (now uses pure JS), make the code compatible with PHP 7.x and web views to manage many new modules added up to Kamailio v5.3.x, including the replacement of MI control interface with JSONRPC. This is the first full release in the 5.x series of Siremis. Step by step installation tutorial, screenshots and changelog are available on the web at: * https://kb.asipto.com/siremis:install53x:main * https://kb.asipto.com/siremis:install32x:screenshots * https://github.com/asipto/siremis/blob/v5.3.0/ChangeLog The deployment of Siremis can be also done using Docker, see the guidelines at: * https://github.com/asipto/siremis/tree/master/misc/docker Siremis project is hosted on Github at: * https://github.com/asipto/siremis/ The web site for the project is at: * https://www.siremis.org Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

1 0

Understanding set_rtp_engine with two sets
by Anthony Alba 25 Feb '20

25 Feb '20

There is a use case mentioned "This is useful if you have a set of RTP proxies that the caller must use, and another distinct set of RTP proxies that the callee must use. This is supported by all rtpengine commands except rtpengine_manage(). " How do you actually implement this - is it something like this? Say caller supposed to target Set 1and callee supposed to target Set 2: # offer/request route set_rtpengine_set(1, 2) rtpengine_offer() # cannot use rtpengine_manage() # callee sees set 2 in SDP, right? # reply_route set_rtpengine_set(2, 1) # reverse the order? Is this correct?? # OR set_rtpengine_set(1, 2) # keep order, module does autoreversal magic # caller sees Set 1 in SDP My question: in the reply route do you keep the same order (module is clever enough to autoreverse so caller sees Set 1) OR do you explicitly reverse the order and THAT means caller sees Set 1. Cheer Anthony

3 2

kamcli postgres support
by Daniel-Constantin Mierla 25 Feb '20

25 Feb '20

Hello, anyone in the community with Python knowledge using Postgres that can spend a bit of time to add support in kamcli? * https://github.com/kamailio/kamcli It should be mainly about the content of the code corresponding to db subcommand: * https://github.com/kamailio/kamcli/blob/master/kamcli/commands/cmd_db.py The target for it is to replace kamdbctl and has some command line variants for couple of its functions, now being implemented for MySQL. The rest of the code relies on sqlalchemy, which should have transparent support for both mysql and postgress (even more). Testing the other commands connecting to database with postgres would be good, though. With more and more diversity in the default shell by main Linux/Unix distros, we hope to be able to replace in the near future the kamctl and kamdbctl tools, which are more like bash scripting (a few issue being reported and fixed lately). Besides that, using python allows better input/parameter checking/validation as well as more options for formatted output. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

2 3

Database errors with usrloc db_mode=1 and dmq_usrloc
by Joel Serrano 25 Feb '20

25 Feb '20

Hello, I have a setup with 2 kamailio in active/idle, locations are shared via dmq_usrloc, but database is also used as a cache where other systems can access and query "real-time" data. The config we have is: # ----- usrloc params ----- modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 1) modparam("usrloc", "db_load", 0) modparam("usrloc", "db_insert_update", 1) modparam("usrloc", "db_timer_clean", 1) modparam("usrloc", "server_id_filter", 1) modparam("usrloc", "timer_procs", 2) modparam("usrloc", "timer_interval", 60) # ----- dmq_usrloc params ----- modparam("dmq_usrloc", "enable", 1) modparam("dmq_usrloc", "sync", 1) modparam("dmq_usrloc", "batch_msg_contacts", 50) # 50 contacts / message modparam("dmq_usrloc", "batch_size", 10000) # 10000 contacts / batch modparam("dmq_usrloc", "batch_usleep", 500000) # one batch every 500ms With this setup, we assume: 1- almost real-time updated location info in the database. 2- as long as one of the two Kam is up, location information will not be lost (as they will sync with each other via DMQ) 3- if both servers go down, locations are lost (as they will not reload from database on startup). Our tests work well with the above config, with one exception, on the idle node, we see a lot of (only happens on the node receiving location via dmq): Feb 21 00:11:25 csbc02 csbc[13916]: ERROR: <core> [db.c:481]: db_use_table(): invalid parameter value Feb 21 00:11:25 csbc02 csbc[13916]: ERROR: usrloc [ucontact.c:1136]: db_update_ucontact_ruid(): sql use_table failed Feb 21 00:11:25 csbc02 csbc[13916]: ERROR: usrloc [ucontact.c:1657]: update_contact_db(): failed to update database I added debug logs to see if I could understand the reason: Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:478]: usrloc_dmq_handle_msg(): dmq message received from sip:usrloc@10.2.1.181:5050 Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:423]: usrloc_dmq_execute_action(): Received DMQ_UPDATE. Update contact info... Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:75]: add_contact(): aor: 1063362 Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:76]: add_contact(): ci->ruid: uloc-1-5e502cd3-5629-1 Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:77]: add_contact(): aorhash: 928261667 Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:115]: add_contact(): '1063362' Not found in usrloc Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:117]: add_contact(): Insert record Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: usrloc [ul_callback.h:83]: run_ul_callbacks(): contact=0x7fe41ff41f40, callback type 1/15, id 0 entered Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:800]: dmq_ul_cb_contact(): Callback from usrloc with type=1 Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:826]: dmq_ul_cb_contact(): Contact received from DMQ... skip Feb 21 14:38:34 csbc02 csbc[30796]: ERROR: <core> [db.c:481]: db_use_table(): invalid parameter value Feb 21 14:38:34 csbc02 csbc[30796]: ERROR: usrloc [ucontact.c:669]: db_insert_ucontact(): sql use_table failed Feb 21 14:38:34 csbc02 csbc[30796]: ERROR: usrloc [urecord.c:598]: insert_ucontact(): failed to insert in database Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:121]: add_contact(): Insert ucontact Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:124]: add_contact(): Release record Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: dmq_usrloc [usrloc_sync.c:126]: add_contact(): Unlock udomain Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: sl [sl.c:305]: send_reply(): reply in stateless mode (sl) Feb 21 14:38:34 csbc02 csbc[30796]: DEBUG: <core> [core/msg_translator.c:161]: check_via_address(): (10.2.1.181, 10.2.1.181, 0) Can anyone help me understand what's the problem? I have the server_id setting, and the modparam server_id_filter, so shouldn't the receiving node just ignore any database tasks? Thanks, Joel.

3 12

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