- sr-users - kamailio.org

Kamailio v5.3.7 Released
by Daniel-Constantin Mierla 02 Nov '20

02 Nov '20

Hello, Kamailio SIP Server v5.3.7 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.6. 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.7. Note that 5.3 is the second last stable branch, still officially maintained by Kamailio development … [View More]

1 0

Releasing Kamailio v5.3.7
by Daniel-Constantin Mierla 02 Nov '20

02 Nov '20

Hello, I am planning to release Kamailio v5.3.7 sometime next week, likely on Monday or Tuesday, this being the usual prior notice for heads up to identify issues not reported yet on bug tracker as well as the commits you are aware of that were not backported yet. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 1

Missing refresher parameter in the Session-Expires header and Min-SE header
by Jose Figueroa 01 Nov '20

01 Nov '20

Hello everybody, I am trying an INVITE with a SBCs but fails, finding out it seems the Session-Expires doesn't include the param refresher= and according to this closed issue is already included https://github.com/kamailio/kamailio/issues/288 but I cannot achive this, I read the sst module documentation but I don't see anything related this parameter. So, in summary the SBC expects the following: Session-Expires: 1800; refresher=uac; Min-SE: 600 I set only: modparam("sst", "enable_stats", 1);… [View More]

1 0

Confusion about TCP worker ports
by Noah Mehl 30 Oct '20

30 Oct '20

Hey all, I’m a little stuck on an implementation of a set of dispatchers via TCP. There are some oddities about the behavior of the TCP source port of the Kamailio tcp worker/s, and maybe this is expected, but it doesn’t seem valid. For instance, I have a dispatcher: "RECORDS": [{ "SET": { "ID": 1, "TARGETS": [{ "DEST": { "URI": “sip:2.2.2.2:5060;transport=tcp", "FLAGS": "AP", "PRIORITY": 5 } }] } }] But when Kamailio sends … [View More]an OPTIONS keep alive, the source port for the worker is 33940, and not 5060 (which is the TCP listen port), as received by Freeswitch: recv 447 bytes from tcp/[1.1.1.1]:33940 at 18:58:24.958720: ------------------------------------------------------------------------ OPTIONS sip:2.2.2.2:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bK1525.80a9e442000000000000000000000000.0 To: <sip:2.2.2.2:5060;transport=tcp> From: <sip:inbound-kamailio-01>;tag=3c52ba62ee4c4621b9660728159919d3-cda8066f CSeq: 10 OPTIONS Call-ID: 3aa18693487268dc-2790(a)1.1.1.1 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.4.2 (x86_64/linux)) ------------------------------------------------------------------------ Also, I get weird debug messages when this tcp worker is spun up (specifically about Resource temporarily unavailable): 11(2790) DEBUG: dispatcher [dispatch.c:3340]: ds_ping_result_helper(): probe all, mode DS_PROBE_ALL 11(2790) DEBUG: dispatcher [dispatch.c:3383]: ds_ping_set(): probing set #1, URI sip:2.2.2.2:5060;transport=tcp 11(2790) DEBUG: dispatcher [dispatch.c:3414]: ds_ping_set(): Default ping_from: sip:inbound-kamailio-01 11(2790) DEBUG: dispatcher [dispatch.c:3424]: ds_ping_set(): Default outbound proxy: 11(2790) DEBUG: tm [uac.c:450]: t_uac_prepare(): next_hop=<sip:2.2.2.2:5060;transport=tcp> 11(2790) DEBUG: tm [uac.c:158]: dlg2hash(): hashid 21073 11(2790) DEBUG: <core> [core/tcp_main.c:1993]: tcp_send(): no open tcp connection found, opening new one 11(2790) DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 2.2.2.2 11(2790) DEBUG: <core> [core/tcp_main.c:1175]: tcpconn_new(): on port 5060, type 2, socket -1 11(2790) DEBUG: <core> [core/tcp_main.c:1494]: tcpconn_add(): hashes: 2712:0:0, 1 11(2790) DEBUG: <core> [core/tcp_main.c:2886]: tcpconn_1st_send(): pending write on new connection 0x7f24e64c1e18 sock 8 (-1/447 bytes written) (err: 11 - Resource temporarily unavailable) 11(2790) DEBUG: tm [uac.c:678]: send_prepared_request_impl(): uac: 0x7f24e65285a8 branch: 0 to 2.2.2.2:5060 11(2790) DEBUG: <core> [core/onsend.c:50]: run_onsend(): required parameters are not available - ignoring 27(2806) DEBUG: <core> [core/tcp_main.c:3792]: handle_ser_child(): read response= 7f24e64c1e18, 5, fd 46 from 11 (2790) 27(2806) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): DBG: io_watch_add(0x56490f0f8060, 46, 2, 0x7f24e64c1e18), fd_no=37 27(2806) DEBUG: <core> [core/io_wait.h:782]: io_watch_chg(): DBG: io_watch_chg (0x56490f0f8060, 46, 0x1, 0xffffffff) fd_no=38 called 27(2806) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0x56490f0f8060, 46, -1, 0x0) fd_no=38 called 27(2806) DEBUG: <core> [core/tcp_main.c:4457]: handle_tcpconn_ev(): sending to child, events 1 27(2806) DEBUG: <core> [core/tcp_main.c:4127]: send2child(): selected tcp worker idx:0 proc:19 pid:2798 for activity on [tcp:1.1.1.1:5060], 0x7f24e64c1e18 19(2798) DEBUG: <core> [core/tcp_read.c:1749]: handle_io(): received n=8 con=0x7f24e64c1e18, fd=8 19(2798) DEBUG: <core> [core/tcp_read.c:1548]: tcp_read_req(): content-length=0 19(2798) DEBUG: <core> [core/parser/msg_parser.c:620]: parse_msg(): SIP Reply (status): 19(2798) DEBUG: <core> [core/parser/msg_parser.c:622]: parse_msg(): version: <SIP/2.0> 19(2798) DEBUG: <core> [core/parser/msg_parser.c:624]: parse_msg(): status: <200> 19(2798) DEBUG: <core> [core/parser/msg_parser.c:626]: parse_msg(): reason: <OK> 19(2798) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1525.80a9e442000000000000000000000000.0>; state=6 19(2798) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <33940>; state=16 19(2798) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 19(2798) DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 19(2798) DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via 19(2798) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1mB9HryQ8ZBFc 19(2798) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 19(2798) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [59]; uri=[sip:2.2.2.2:5060;transport=tcp] 19(2798) DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body (39)[<sip:2.2.2.2:5060;transport=tcp>], to tag (13)[1mB9HryQ8ZBFc] 19(2798) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <10> <OPTIONS> 19(2798) DEBUG: <core> [core/receive.c:319]: receive_msg(): --- received sip message - reply - call-id: [3aa18693487268dc-2790(a)1.1.1.1] - cseq: [10 OPTIONS] 19(2798) DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 19(2798) DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Are these SIP messages expected to come from other ports than the listen port (5060 in this case)? Also, if the worker source port is not 5060, shouldn’t the SIP message get updated with the correct port? In the case of OPTIONS, Freeswitch is replying correctly to the source port: 33940. However, in the case of an in dialog BYE, Freeswitch is NOT replying to the source port of the Kamailio messages, but only to port 5060. Here is an example (relayed from web sockets to freeswitch over TCP) INVITE (as received from Freeswitch): recv 1481 bytes from tcp/[1.1.1.1]:33940 at 16:56:47.920698: ------------------------------------------------------------------------ INVITE sip:991012@sip.domain <sip:991012@sip.domain>.com SIP/2.0 Record-Route: <sip:1.1.1.1;transport=tcp;r2=on;lr;nat=yes> Record-Route: <sip:1.1.1.1:5061;transport=tls;r2=on;lr;nat=yes> Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bKd408.3f53e940ccb20c1033df4b3a8ebd8a34.0;i=1 Via: SIP/2.0/TLS 172.22.199.110:55304;received=5.5.5.5;rport=39518;branch=z9hG4bKPj5Css6JomCt9Cli2cCINbXi4FbPM5wewG;alias Max-Forwards: 69 From: "Noah Mehl" <sip:5135555555@inbound-jail>;tag=s3i3y2tiOCgnUId5TD4Vp0UChf9GyEy9 To: <sip:991012@inbound-jail> Contact: <sip:74895612@172.22.199.110:54887;transport=tls;alias=5.5.5.5~39518~3> Call-ID: 5aoRBMBHahxqSLzrIpFnlfRz.UcGsmfq CSeq: 27271 INVITE Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER Supported: replaces, norefersub, gruu User-Agent: Blink Pro 4.6.0 (MacOSX) Content-Type: application/sdp Content-Length: 528 v=0 o=- 3812979407 3812979407 IN IP4 5.5.5.5 s=Blink Pro 4.6.0 (MacOSX) t=0 0 m=audio 50016 RTP/SAVP 113 0 101 c=IN IP4 5.5.5.5 a=rtcp:50017 a=rtpmap:113 opus/48000/2 a=fmtp:113 useinbandfec=1 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:UhHq6hth9HqALmiJ3AEeoGkixObBzkLURG60wJKT a=crypto:2 AES_CM_128_HMAC_SHA1_32 inline:VKYaSCVwgvXCPaRvudTrgLORhWmOA7wyDJVeGjcu a=sendrecv a=oldmediaip:172.22.199.110 a=oldmediaip:172.22.199.110 ------------------------------------------------------------------------ This doesn’t seem valid, as the top Via doesn’t have a port specified? For reference, just rebuilt form the 5.4 branch today: commit 62dff5b8b157236cae7defe64291a6e4a8ae27b5 (upstream/5.4) Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: Wed Oct 28 20:16:28 2020 +0100 modules: readme files regenerated - modules ... [skip ci] Thanks! ~Noah [View Less]

6 19

Double port in TO header
by David Villasmil 30 Oct '20

30 Oct '20

Hello guys, This happened to me a long time ago but i totally forgot the reason. I using a simple dispatcher, and when relaying out to the destination, kamailio is adding an additional :5060 port to the To header: To: <sip:910609738@172.31.6.1:5080:5060> The Destination is actually 172.16.6.1:5080, i don't know why Kamailio is adding that :5060 The dispatcher is if (!ds_select_dst($var(dispatcher_outbound), "4")) { xlog("[DISPATCH]: ds_select_dst FAILED!\n"); … [View More]

2 8

Re: [SR-Users] Building db_postgres with PostgreSQL headers and libs in non-standard location
by Chaigneau, Nicolas 30 Oct '20

30 Oct '20

Perfect, that's what I was looking for. :) Thanks! > This is what I have always done: > > # export PATH=$PATH:/usr/pgsql-${MAJOR_VER}/bin > # cd src/modules/db_postgres > # make install > > The `pg_config` utility in /usr/pgsql-${MAJOR_VER}/bin ensures that the proper header include path is supplied. > > -- Alex This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person … [View More]

1 0

Building db_postgres with PostgreSQL headers and libs in non-standard location
by Chaigneau, Nicolas 29 Oct '20

29 Oct '20

Hello, I'd like to build Kamailio module db_postgres, with the PostgreSQL headers and libs in a non-standard location. I'm trying to figure out how to do that, if it's possible, without having to edit db_postgres/Makefile. I see in the Makefile that it's trying to find the files relative to $(LOCALBASE): # use standard know paths # libpq-fe.h locations DEFS +=-I$(LOCALBASE)/include -I$(LOCALBASE)/pgsql/include \ -I$(SYSBASE)/include/pgsql -I$(SYSBASE)/… [View More]

2 2

www.kamailio.org maintenance on 29th October 2020, 10:00 CET
by Henning Westerholt 29 Oct '20

29 Oct '20

Hello, there will be a short planned maintenance on www.kamailio.org<http://www.kamailio.org> on 29th October 2020 at 10:00 CET. Relevant services including main homepage and documentation wiki will be unavailable for about 10-15 minutes. Best regards, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

Kamailio unresponsive with Dialog+DMQ
by Patrick Wakano 28 Oct '20

28 Oct '20

Hello list, Hope all are doing well! We are running load tests in our Kamailio server, that is just making inbound and outbound calls and eventually (there is no identified pattern) Kamailio freezes and of course all calls start to fail. It does not crash, it just stops responding and it has to be killed -9. When this happens, SIP messages are not processed, dmq keepalive fails (so the other node reports as down), dialog KA are not sent, but Registrations from UAC seem to still go out (logs … [View More]from local_route are seen). We don't have a high amount of cps, it is max 3 or 4 per sec, and it gets around 1900 active calls. We are now using Kamailio 5.2.8 installed from the repo on a CentOS7 server. Dialog has KA active and DMQ (with 2 workers) is being used on an active-active instance. >From investigation using GDB as pasted below, I can see UDP workers are stuck on a lock either on a callback from t_relay... #0 0x00007ffb74e9bbf9 in syscall () from /lib64/libc.so.6 #1 0x00007ffb2b1bce08 in futex_get (lock=0x7ffb35217b90) at ../../core/futexlock.h:108 #2 0x00007ffb2b1bec44 in bcast_dmq_message1 (peer=0x7ffb35e8bf38, body=0x7fff2e95ffb0, except=0x0, resp_cback=0x7ffb2a8a0ab0 <dlg_dmq_resp_callback>, max_forwards=1, content_type=0x7ffb2a8a0a70 <dlg_dmq_content_type>, incl_inactive=0) at dmq_funcs.c:156 #3 0x00007ffb2b1bf46b in bcast_dmq_message (peer=0x7ffb35e8bf38, body=0x7fff2e95ffb0, except=0x0, resp_cback=0x7ffb2a8a0ab0 <dlg_dmq_resp_callback>, max_forwards=1, content_type=0x7ffb2a8a0a70 <dlg_dmq_content_type>) at dmq_funcs.c:188 #4 0x00007ffb2a6448fa in dlg_dmq_send (body=0x7fff2e95ffb0, node=0x0) at dlg_dmq.c:88 #5 0x00007ffb2a64da5d in dlg_dmq_replicate_action (action=DLG_DMQ_UPDATE, dlg=0x7ffb362ea3c8, needlock=1, node=0x0) at dlg_dmq.c:628 #6 0x00007ffb2a61f28e in dlg_on_send (t=0x7ffb36c98120, type=16, param=0x7fff2e9601e0) at dlg_handlers.c:739 #7 0x00007ffb2ef285b6 in run_trans_callbacks_internal (cb_lst=0x7ffb36c98198, type=16, trans=0x7ffb36c98120, params=0x7fff2e9601e0) at t_hooks.c:260 #8 0x00007ffb2ef286d0 in run_trans_callbacks (type=16, trans=0x7ffb36c98120, req=0x7ffb742f27e0, rpl=0x0, code=-1) at t_hooks.c:287 #9 0x00007ffb2ef38ac1 in prepare_new_uac (t=0x7ffb36c98120, i_req=0x7ffb742f27e0, branch=0, uri=0x7fff2e9603e0, path=0x7fff2e9603c0, next_hop=0x7ffb742f2a58, fsocket=0x7ffb73e3e968, snd_flags=..., fproto=0, flags=2, instance=0x7fff2e9603b0, ruid=0x7fff2e9603a0, location_ua=0x7fff2e960390) at t_fwd.c:381 #10 0x00007ffb2ef3d02d in add_uac (t=0x7ffb36c98120, request=0x7ffb742f27e0, uri=0x7ffb742f2a58, next_hop=0x7ffb742f2a58, path=0x7ffb742f2e20, proxy=0x0, fsocket=0x7ffb73e3e968, snd_flags=..., proto=0, flags=2, instance=0x7ffb742f2e30, ruid=0x7ffb742f2e48, location_ua=0x7ffb742f2e58) at t_fwd.c:811 #11 0x00007ffb2ef4535a in t_forward_nonack (t=0x7ffb36c98120, p_msg=0x7ffb742f27e0, proxy=0x0, proto=0) at t_fwd.c:1699 #12 0x00007ffb2ef20505 in t_relay_to (p_msg=0x7ffb742f27e0, proxy=0x0, proto=0, replicate=0) at t_funcs.c:334 or loose_route... #0 0x00007ffb74e9bbf9 in syscall () from /lib64/libc.so.6 #1 0x00007ffb2b1bce08 in futex_get (lock=0x7ffb35217b90) at ../../core/futexlock.h:108 #2 0x00007ffb2b1bec44 in bcast_dmq_message1 (peer=0x7ffb35e8bf38, body=0x7fff2e9629d0, except=0x0, resp_cback=0x7ffb2a8a0ab0 <dlg_dmq_resp_callback>, max_forwards=1, content_type=0x7ffb2a8a0a70 <dlg_dmq_content_type>, incl_inactive=0) at dmq_funcs.c:156 #3 0x00007ffb2b1bf46b in bcast_dmq_message (peer=0x7ffb35e8bf38, body=0x7fff2e9629d0, except=0x0, resp_cback=0x7ffb2a8a0ab0 <dlg_dmq_resp_callback>, max_forwards=1, content_type=0x7ffb2a8a0a70 <dlg_dmq_content_type>) at dmq_funcs.c:188 #4 0x00007ffb2a6448fa in dlg_dmq_send (body=0x7fff2e9629d0, node=0x0) at dlg_dmq.c:88 #5 0x00007ffb2a64da5d in dlg_dmq_replicate_action (action=DLG_DMQ_STATE, dlg=0x7ffb363e0c10, needlock=0, node=0x0) at dlg_dmq.c:628 #6 0x00007ffb2a62b3bf in dlg_onroute (req=0x7ffb742f11d0, route_params=0x7fff2e962ce0, param=0x0) at dlg_handlers.c:1538 #7 0x00007ffb2e7db203 in run_rr_callbacks (req=0x7ffb742f11d0, rr_param=0x7fff2e962d80) at rr_cb.c:96 #8 0x00007ffb2e7eb2f9 in after_loose (_m=0x7ffb742f11d0, preloaded=0) at loose.c:945 #9 0x00007ffb2e7eb990 in loose_route (_m=0x7ffb742f11d0) at loose.c:979 or t_check_trans: #0 0x00007ffb74e9bbf9 in syscall () from /lib64/libc.so.6 #1 0x00007ffb2a5ea9c6 in futex_get (lock=0x7ffb35e78804) at ../../core/futexlock.h:108 #2 0x00007ffb2a5f1c46 in dlg_lookup_mode (h_entry=1609, h_id=59882, lmode=0) at dlg_hash.c:709 #3 0x00007ffb2a5f27aa in dlg_get_by_iuid (diuid=0x7ffb36326bd0) at dlg_hash.c:777 #4 0x00007ffb2a61ba1d in dlg_onreply (t=0x7ffb36952988, type=2, param=0x7fff2e963bf0) at dlg_handlers.c:437 #5 0x00007ffb2ef285b6 in run_trans_callbacks_internal (cb_lst=0x7ffb36952a00, type=2, trans=0x7ffb36952988, params=0x7fff2e963bf0) at t_hooks .c:260 #6 0x00007ffb2ef286d0 in run_trans_callbacks (type=2, trans=0x7ffb36952988, req=0x7ffb3675c360, rpl=0x7ffb742f1930, code=200) at t_hooks.c:28 7 #7 0x00007ffb2ee7037f in t_reply_matching (p_msg=0x7ffb742f1930, p_branch=0x7fff2e963ebc) at t_lookup.c:997 #8 0x00007ffb2ee725e4 in t_check_msg (p_msg=0x7ffb742f1930, param_branch=0x7fff2e963ebc) at t_lookup.c:1101 #9 0x00007ffb2eee44c7 in t_check_trans (msg=0x7ffb742f1930) at tm.c:2351 And the DMQ workers are here: #0 0x00007ffb74e9bbf9 in syscall () from /lib64/libc.so.6 #1 0x00007ffb2b1d6c81 in futex_get (lock=0x7ffb35217c34) at ../../core/futexlock.h:108 #2 0x00007ffb2b1d7c3a in worker_loop (id=1) at worker.c:86 #3 0x00007ffb2b1d5d35 in child_init (rank=0) at dmq.c:300 Currently I will not be able to upgrade to latest 5.4 version to try to reproduce the error and since 5.2.8 has already reached end-of-life, maybe is there anything I can do on the configuration to avoid such condition? Any ideas are welcome! Kind regards, Patrick Wakano [View Less]

3 6

Kamailio v5.4.2 Released
by Daniel-Constantin Mierla 27 Oct '20

27 Oct '20

Hello, Kamailio SIP Server v5.4.2 stable release is out. This is a maintenance release of the latest stable branch, 5.4, that includes fixes since the release of v5.4.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.4.x. Deployments running previous v5.4.x versions are strongly recommended to be upgraded to v5.4.1. For more details about version 5.4.2 (including links and guidelines to download the tarball or … [View More]

1 0

Releasing Kamailio v5.4.2
by Daniel-Constantin Mierla 27 Oct '20

27 Oct '20

Hello, I am considering to release Kamailio v5.4.2 sometime next week, likely on Tuesday, October 27, 2020. This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

1 1

KEMI and Native mixing
by Marcin Kowalczyk 26 Oct '20

26 Oct '20

Hi, Is it possible to mix both KEMI (lua) and Native configs in one kamailio instance? So some blocks are called from native script and some others from KEMI (lua)? Marcin

6 5

Kamailio-5.x and Asterisk16.X Integration Walkthrough Videos or Wikis
by Lorem Ipsum 26 Oct '20

26 Oct '20

Hi there, After reading about Kamailio, i like this project but i am having trouble finding the wikis or step by step guide to successfully integrate asterisk with kamailio for simple use case where phones register to the asterisk pbx via kamailio and make/receive calls to ITSP, there is no proper documentation on 2 products integration, really appreciated your guidance and if somebody could provide me the step by step guide. Looking forward to the guides.

2 1

I want to write function in group module but i could not
by ahmed moghazy 25 Oct '20

25 Oct '20

I have 2 function first If(is_user_in(“Request-URI”, ”ld”)){ ..... } So i dont know what to do , second If(get_user_group(“Request-URI”, ”$avp(i:10)”){ ... } I put users in 2 groups but they could call each others but i dont want that . Any help please , Thank you.

1 0

Re: [SR-Users] Load balance on HA scenario
by Yufei Tao 22 Oct '20

22 Oct '20

Hi Duarte, I'm not sure if your situation is more complicated than mine. I have two dispatcher nodes in the HA setup, with real IPs say IPa, IPb. They share a floating/virtual IP, let's call it VIP. Both nodes listen to the VIP (not its real IP), and use the VIP as the dispatcher's socket. In this case the master node which has the VIP can always send OPTIONS pings fine. My problem was with the backup node, which doesn't have the VIP so fails to send OPTIONS pings. Joel Serrano gave a good … [View More]

1 0

Incoming DID calls routing to subscriber
by Jose N Figueroa 22 Oct '20

22 Oct '20

Hello everybody, I'm trying to route incoming calls to kamailio with specific subscriber but I can't make it working. The complete scenario is: SoftSwith -> kamailio 5.3 -> zoiper What i'm trying to do is to receive a call into the zoiper when I dial specific DID which is already coming into the kamailio. It goes until the routing from kamilio to the subscriber account but it keeps in INVITE command, no response from the subscriber. Any help would be great! This is what I've been … [View More]

3 3

Load balance on HA scenario
by Duarte Rocha 21 Oct '20

21 Oct '20

Greetings, I have two machines with Kamailio in a HA setup with replicated DB. For simplicity let's say each machine has one HA IP and that IP can jump to the other machine in case something happens (kamailio stopping, etc). I'm using Dispatcher with load balance configuration. I have Dispatcher configured so that each peer has one instance for socket with HA IP 1 and HA IP 2. In order for this to work correctly on the load balance scenario I must disable via RPC command the peer which has … [View More]

3 8

kamailio RTP Engine in kubernetes pods
by Pavithra Mohanraja 21 Oct '20

21 Oct '20

Hi, I have installed rtp engine inside pcscf pod and tried to make a call. caller was unable to reach the pod environment with 2223 port exposed for rtp. Kindly anyone help, if you have already done with pod based deployment of ims. Thanks, Pavithra

4 7

Kamailio + rtpengine
by Amit Pal 21 Oct '20

21 Oct '20

Hi, I have using kamailio with rtpengine, I have started rtpengine session (rtpengine_offer() /rtpengine_answer() )only when call getting hold and then play media file and on un hold detach rtpengine session(rtpengine_delete()). during this activity I have received the log "No supported output codec found in SDP" from rtpengine. And getting silence on other leg. Above activity log are attach in mail. if we do same step again (i.e. hold/unhold) in same call then second leg listening the … [View More]

2 1

How to read "duid" from dispatcher.list in kamamilio.cfg
by Jani Biju Babjan 21 Oct '20

21 Oct '20

Hi, I have a dispatcher.list file like the following: 1 sip:127.0.0.1:5060 0 0 duid=abcd;maxload=5 1 sip:127.0.0.2:5060 0 0 duid=efgh;maxload=5 After calling the ds_select_dst("1", "4") function(ie, round-robin selection), I want to read the value of the "duid" attribute of the selected destination and then pass it to a database. How can I read this value in the configuration file? Jani Biju Babjan

2 2

Re: [SR-Users] Load balance on HA scenario
by Yufei Tao 21 Oct '20

21 Oct '20

Hi Joel, Thanks for the tip! Having the pings disabled and enable it on HA status being master sounds like a good idea :) Cheers, Yufei

1 0

ERROR: <core> [core/socket_info.c:2225]: parse_protohostport():
by Andy Kama 20 Oct '20

20 Oct '20

I am seeing this error in the logs i am using kamailio 5.4.1 any idea what the cause is? ERROR: <core> [core/socket_info.c:2225]: parse_protohostport(): bad protocol in sip:myp:5060

2 4

Re: [SR-Users] Load balance on HA scenario
by Yufei Tao 20 Oct '20

20 Oct '20

Hi Duarte, Not sure if I understand it correctly but are you trying to set up an HA pair of dispatchers? If so I am doing it differently in that, I use the Virtual/floating IP (VIP) as socket. This way the master node (which has got the VIP) can send OPTIONs pings out fine but the backup node won't be able to send. Functionally it is fine, but the backup node keeps logging errors because it doesn't have the VIP: ERROR: <core> [core/udp_server.c:599]: udp_send(): sendto(sock, buf: … [View More]

2 1

No retry on INVITE
by Allan Kristensen 20 Oct '20

20 Oct '20

Hello, I'm trying to get Kamailio to retry INVITE. We have a Freeswitch which is sending INVITE to a sip user via Kamailio proxy using static ip/location. All is well, calls are flowing, but sometimes INVITE from kamailio to user is lost and no attempt to retry is occurring and so after 30 sec kamailio just returns 408 Request timeout. Call flow is like this: FS Kamailio User --- INVITE --> <-- 100 Trying --- INVITE ---> (Waiting 30 secs) <-- 408 … [View More]

3 4

Re: [SR-Users] SRTP
by Yufei Tao 20 Oct '20

20 Oct '20

Hi, Like Olle said RTPEngine is perfectly capable of handling one leg in RTP the other in SRTP. When looking up RTPEngine's documentation, may be worth checking these out: SRTP SDES-unencrypted_srtp SDES-unencrypted_srtcp SDES-unauthenticated_srtp e.g. try apply these flags to rtpengin_offer() on the incoming RTP leg, to get RTPEngine to add encryption to the outgoing leg etc. Cheers, Yufei

1 0

Re: [SR-Users] Kamailio 5.2.5 - Need help with rtpengine error
by Yufei Tao 20 Oct '20

20 Oct '20

Hi Andrew, Like Alex said, have a look at the commands RTPEngine received and the responses it sent in the history of the call, and see if RTPEngine has ever received any commands regarding this call, or, if the call has been deleted from RTPEngine. You can raise the RTPEngine logging level to 6 for example so you can see the command/responses of RTPEngine. Cheers, Yufei

1 0

about registrar save()/lookup()
by Juha Heinanen 20 Oct '20

20 Oct '20

I didn't find any mention in registrar module README that save() function saves also branch flags and that lookup() retrieves them. Is that documented somewhere? -- Juha

3 5

dialog_active_dialogs erroneous value
by Sergiu Pojoga 20 Oct '20

20 Oct '20

Hi there, Every now and then, the value of active dialogs metric spikes to an erroneous huge number, messing up my otherwise beautiful grafana gauges :( Example: kamailio_dialog_active_dialogs 18446744073709551614 1602812239115 kamailio_dialog_early_dialogs 0 1602812239115 kamailio_dialog_expired_dialogs 2 1602812239115 kamailio_dialog_failed_dialogs 7361 1602812239115 Anybody faced the same symptoms, any clues what might be causing this? Thanks, --Sergiu

3 6

TOPOS module and fix_nated_contact
by Minh Phan 19 Oct '20

19 Oct '20

Hi List, I am using Topos module to hide network topology. I am having a problem of routing the ACK request for REINVITE. Here is the schema: A KAMAILIO B 1. --------- INVITE --------> 2. <---- 180 RINGING --- 3. <---- 200 OK --- 4. ---- ACK ---> 5. <--------- (RE) INVITE -- 6. --------- OK ---> 7. <---- ACK ----- (THIS … [View More]

2 1

hold_on_music over P2P call [Kamailio]
by Amit Pal 19 Oct '20

19 Oct '20

Hi Team, Pls guide me on following point. :- By using kamailio (P2P call), want to play hold on music during hold call. Shall it be possible without any external media server like (RTPProxy/media proxy). Regards Amit Pal

2 1

Kamailio IMS RTP Engine
by Pavithra Mohanraja 19 Oct '20

19 Oct '20

Hi, I have followed below link to setup rtp engine. https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ RTP engine is started without any errors and it is enabled in pcscf also. I am using the config files of pcscf as per the above link .. still rtp packets are not reaching pcscf from UE . What could be the problem? The only difference is that i have deployed ims in kubernetes environment as pods. Kindly help. Thanks, Pavithra

2 2

Libphonenumber - Updating metadata
by Zach Nielsen 18 Oct '20

18 Oct '20

Hey all, I've been using the PHONENUM module, which uses Google's libphonenumber library, to perform number validation among other handy things within the route script. One problem I've run into however is the metadata in the latest stable (5.4) repo is pretty stale. I'm curious if anyone is running this module, and if so how they've gone about updating the metadata used by the underlying library. If I have to ditch the repo and compile everything manually, that's not a huge deal. Just hoping … [View More]

3 3

No trusted table found
by Jon Bonilla (Manwe) 17 Oct '20

17 Oct '20

Hi all Just installed a kamailio 5.4.1 for a simple proxy scenario. I created the version,address and trusted tables, and added some ips to the trusted via kamctl. If I execute "kamctl trusted show" I see the list of servers. But with "kamctl trusted dump" I receive { "jsonrpc": "2.0", "error": { "code": 500, "message": "No trusted table" }, "id": 13063 } when I start kamailio with debug I see these messages: b_do_submit_query(): submitted query: select `… [View More]

2 5

TLS connection from Chrome to Kamailio fails
by Juha Heinanen 17 Oct '20

17 Oct '20

White testing WebRTC, I noticed that TLS connection from Chrome browser 85.0.4183.121 to Kamailio's (master version) TLS listening port fails. Chrome sends Client Hello and K responds with Server Hello. After that Chrome terminates the handshake by sending TCP FIN. Connection setup from Firefox works fine. After receiving Server Hello, is sends Change Cipher Spec, etc. My K is using Let's Encrypt server certificate and is server tls_method is TLSv1.2+. Any ideas what goes wrong? Has … [View More]

3 6

How to increase private & shared memory in kamailio Container?
by Hamid Hashmi 16 Oct '20

16 Oct '20

Dear Users How can I increase private memory in the Kamailio container? the service was started with the following command docker run -d --restart unless-stopped --network host -v /root/volumes/scscf/:/etc/kamailio --name scscf -e IP=10.161.224.90 -e INT_IP=10.161.224.90 10.161.224.196:5000/kamailio-ngvoice PS: I don't have a docker file to build the image again. Regards Hamid R. Hashmi

2 1

usrloc_dmq - Suddenly stopped usrloc replication
by José Seabra 16 Oct '20

16 Oct '20

Hello there, Suddenly the usrloc replication through DMQ stopped, but the interesting thing is that DMQ cluster status is OK, htable replication still working only usrloc_dmq stopped working. I increased the kamailio loglevel to 3 in order to see if there was some log related and then registered a peer, but the only DMQ logs that I see are related with notification_peer and htable replication, nothing related with usrloc_dmq. What I can do more here to try to understand what went wrong? I … [View More]

3 8

Kamailio 5.2.5 - Need help with rtpengine error
by Andrew Chen 15 Oct '20

15 Oct '20

Hi all, Today I saw the following errors reported by rtpengine module: Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 30(8086) DEBUG: rtpengine [rtpengine.c:2453]: rtpp_function_call(): proxy reply: d6:result5:error12:error-reason15:Unknown call-ide Oct 15 15:02:10 ashprodkama52 kamailio[8028]: 30(8086) ERROR: rtpengine [rtpengine.c:2474]: rtpp_function_call(): proxy replied with error: Unknown call-id This was on the 200 OK response back from our Freeswitch. Any idea what would cause this? … [View More]

2 2

Regd : SIP Configuration in Kamailio
by Santanu B 15 Oct '20

15 Oct '20

Hi, We are using Jitsi Meet for Video Conference Service. We want our SIP endpoint to join in the conference room in Jitsi. For that i am trying to configure Kamailio SIP Server in our environment. I have installed the Server and my endpoints are registered in my SIP server. Both endpoints are able to connect to each other. But I am unable to configure the SIP endpoints to join in the Meet Conference Room. Please guide me to configure. Thanks and regards, Santanu

5 5

sdpops - modifying sdp codecs' presedence list - order
by Melek Oktay 15 Oct '20

15 Oct '20

Hello, Kamailio *sdpops *module consist of several useful functions for manipulating SDP on Proxy side such as *sdp_keep_codecs_by_name*() . This function *sdp_keep_codecs_by_name*("PCMU,PCMA,GSM") finds codecs id [0,8,3] and if incoming packet consist of other than these codecs, they are removed ! For example, assume incoming packet SDP --> [8 0 3 9 101] after applying this function 9 and 101 are removed and outgoing packet SDP consist only PCMU,PCMA,GSM [0,8,3]. This function does … [View More]

1 0

Kamailio Relay Replies Issue
by me.projects＠yahoo.com 15 Oct '20

15 Oct '20

I have DID provider which is sending INVITES to Kamailio and kamailio has UAC module with asterisk to forward Calls to Asterisk with uac_auth() 1-DID Provider ----> (TLS)2-Kamailio (UDP) -----> (UDP) 3-Asterisk Call from Kamailio to Asterisk is forwarded and answered but NON of the reply received in "MANAGE_REPLY" route is not relayed back to DID provider call get disconnected. =================SIP DUMP INVITE FROM DID INVITE sip:+1700@KAMAILIOSERER.com:5061;user=phone;… [View More]transport=tls SIP/2.0FROM: Alga Tech<sip:+17900000002@DIDPROVIDER.com:5061;user=phone>;tag=28989e96e28d47d891b4d8d21d85fa92TO: <sip:+1700@KAMAILIOSERER.com:5061;user=phone>CSEQ: 1 INVITECALL-ID: 936ba28f302f5a5d9b09f32e2e7c41f2MAX-FORWARDS: 70VIA: SIP/2.0/TLS DID-IP:5061;TH=div;branch=z9hG4bK77976715RECORD-ROUTE: <sip:DIDPROVIDER-ROUTE.com:5061;transport=tls;lr>CONTACT: <sip:DIDPROVIDER-CONTACT.com:443;x-i=b9483d0b-e3aa-4487-8dec-68de62d93a35;x-c=936ba28f302f5a5d9b09f32e2e7c41f2/d/8/26d69f6b729942a799552629a315d5d1>CONTENT-LENGTH: 1103MIN-SE: 300SUPPORTED: timerUSER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.10.12.5 i.USEA.0CONTENT-TYPE: application/sdpALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFYSESSION-EXPIRES: 3600TH: dih -----------------------Invite to Asterisk with AUTH INVITE sip:+1700@KAMAILIOSERER.com:5061;user=phone;transport=tls SIP/2.0FROM: Alga Tech<sip:+17900000002@DIDPROVIDER.com:5061;user=phone>;tag=28989e96e28d47d891b4d8d21d85fa92TO: <sip:+1700@KAMAILIOSERER.com:5061;user=phone>CSEQ: 1 INVITECALL-ID: 936ba28f302f5a5d9b09f32e2e7c41f2MAX-FORWARDS: 69VIA: SIP/2.0/TLS DID-IP:5061;TH=div;branch=z9hG4bK77976715RECORD-ROUTE: <sip:DIDPROVIDER-ROUTE.com:5061;transport=tls;lr>CONTACT: <sip:DIDPROVIDER-CONTACT.com:443;x-i=b9483d0b-e3aa-4487-8dec-68de62d93a35;x-c=936ba28f302f5a5d9b09f32e2e7c41f2/d/8/26d69f6b729942a799552629a315d5d1>CONTENT-LENGTH: 1103MIN-SE: 300SUPPORTED: timerUSER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.10.12.5 i.USEA.0CONTENT-TYPE: application/sdpALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFYSESSION-EXPIRES: 3600TH: dih ------------------ >From Asterisk to Kamailio SIP/2.0 100 TryingVia: SIP/2.0/UDP KAMAILIO-IP:7790;TH=ucv;rport=7790;received=KAMAILIO-IP;branch=z9hG4bK7317.fe3491996f35f580f2efa1c50081a62c.1;i=7Via: SIP/2.0/TLS DID-IP:5061;rport=8256;TH=div;branch=z9hG4bK77976715Record-Route: <sip:KAMAILIO-IP:7790;lr;r2=on;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:KAMAILIO-IP:5061;transport=tls;r2=on;lr;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:DIDPROVIDER-ROUTE.com:5061;transport=tls;lr>Call-ID: 936ba28f302f5a5d9b09f32e2e7c41f2From: "Alga Tech" <sip:1508@qs.callsprout.com>;tag=28989e96e28d47d891b4d8d21d85fa92To: <sip:+1700@KAMAILIOSERER.com;user=phone>CSeq: 1 INVITEServer: AsteriskContent-Length: 0TH: uch ---------------------- >From Asterisk to Kamailio SIP/2.0 180 RingingVia: SIP/2.0/UDP KAMAILIO-IP:7790;TH=ucv;rport=7790;received=KAMAILIO-IP;branch=z9hG4bK7317.fe3491996f35f580f2efa1c50081a62c.1;i=7Via: SIP/2.0/TLS DID-IP:5061;rport=8256;TH=div;branch=z9hG4bK77976715Record-Route: <sip:KAMAILIO-IP:7790;lr;r2=on;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:KAMAILIO-IP:5061;transport=tls;r2=on;lr;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:DIDPROVIDER-ROUTE.com:5061;transport=tls;lr>Call-ID: 936ba28f302f5a5d9b09f32e2e7c41f2From: "Alga Tech" <sip:1508@qs.callsprout.com>;tag=28989e96e28d47d891b4d8d21d85fa92To: <sip:+1700@KAMAILIOSERER.com;user=phone>;tag=17f0e0ba-c1c0-457a-b0dd-9a9729d312e7CSeq: 1 INVITEServer: AsteriskContact: <sip:66.232.107.106:7790>Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFERContent-Length: 0 ---------------------- >From Asterisk to Kamailio SIP/2.0 180 RingingVia: SIP/2.0/UDP KAMAILIO-IP:7790;TH=ucv;rport=7790;received=KAMAILIO-IP;branch=z9hG4bK7317.fe3491996f35f580f2efa1c50081a62c.1;i=7Via: SIP/2.0/TLS DID-IP:5061;rport=8256;TH=div;branch=z9hG4bK77976715Record-Route: <sip:KAMAILIO-IP:7790;lr;r2=on;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:KAMAILIO-IP:5061;transport=tls;r2=on;lr;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:DIDPROVIDER-ROUTE.com:5061;transport=tls;lr>Call-ID: 936ba28f302f5a5d9b09f32e2e7c41f2From: "Alga Tech" <sip:1508@qs.callsprout.com>;tag=28989e96e28d47d891b4d8d21d85fa92To: <sip:+1700@KAMAILIOSERER.com;user=phone>;tag=17f0e0ba-c1c0-457a-b0dd-9a9729d312e7CSeq: 1 INVITEServer: AsteriskAllow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFERContact: <sip:66.232.107.106:7790>Content-Length: 0TH: uch ---------------------- >From Asterisk to Kamailio SIP/2.0 200 OKVia: SIP/2.0/UDP KAMAILIO-IP:7790;TH=ucv;rport=7790;received=KAMAILIO-IP;branch=z9hG4bK7317.fe3491996f35f580f2efa1c50081a62c.1;i=7Via: SIP/2.0/TLS DID-IP:5061;rport=8256;TH=div;branch=z9hG4bK77976715Record-Route: <sip:KAMAILIO-IP:7790;lr;r2=on;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:KAMAILIO-IP:5061;transport=tls;r2=on;lr;ftag=28989e96e28d47d891b4d8d21d85fa92;vsf=AAAAABoEBwFwQUMeU1FcXjMDGx9bBF0XAQV1Yi5taWNyb3NvZnQuY29tOjUwNjE7dXNlcj1waG9uZQ--;nat=yes>Record-Route: <sip:DIDPROVIDER-ROUTE.com:5061;transport=tls;lr>Call-ID: 936ba28f302f5a5d9b09f32e2e7c41f2From: "Alga Tech" <sip:1508@qs.callsprout.com>;tag=28989e96e28d47d891b4d8d21d85fa92To: <sip:+1700@KAMAILIOSERER.com;user=phone>;tag=17f0e0ba-c1c0-457a-b0dd-9a9729d312e7CSeq: 1 INVITEServer: AsteriskAllow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFERContact: <sip:66.232.107.106:7790>Supported: 100rel, timer, replaces, norefersubSession-Expires: 3600;refresher=uacRequire: timerContent-Type: application/sdpContent-Length: 299TH: uch [View Less]

1 0

To Header Manipulation
by Sam Ware 15 Oct '20

15 Oct '20

Wondering if this is intended behavior. We have a customer doing some craziness with the TO header. They are including their tech prefix in the TO header as well as the RURI. It doesn't cause any issue in our systems but apparently it does with one of our vendors. In an effect to prevent the issue, we thought we would check if the tech prefix was added on the TO header and remove it. Initially, I tried this by changing the $tU variable. $avp(tp_len) = $(avp(techprefix){s.len}) + 1; # Get … [View More]

2 1

Error in RTP engine setup
by Pavithra Mohanraja 15 Oct '20

15 Oct '20

Hi, I tried to setup rtpengine to make my sip clients communicate through proxy following https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ I started sip communication since the service was running and saw that the RTP packets go to exposed rtp interface instead of other sip client. But i don't receive packets from the other end. When analyzed I noticed the rtp-engine daemon gives a few errors. *modprobe: FATAL: Module xt_RTPENGINE not found in directory /lib/modules/4.15.0-118-… [View More]

2 2

Re: [SR-Users] Regd : SIP Configuration in Kamailio
by Henning Westerholt 14 Oct '20

14 Oct '20

Hello, please keep the list in CC. I can see Kamailio in your log: Oct 14 11:21:59 nickar /usr/sbin/kamailio[24567]: INFO: <core> [main.c:842]: sig_usr(): signal 15 received Oct 14 11:21:59 nickar systemd[1]: Stopping Kamailio (OpenSER) - the Open Source SIP Server... Oct 14 11:21:59 nickar /usr/sbin/kamailio[24568]: INFO: <core> [main.c:842]: sig_usr(): signal 15 received About tracing/debugging, one good option is sngrep. Cheers, Henning -- Henning Westerholt – https://… [View More]skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Santanu B <santanu.br(a)gmail.com> Sent: Wednesday, October 14, 2020 1:41 PM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] Regd : SIP Configuration in Kamailio Hi, My syslog file is enclosed for your reference. Thanks, Santanu On Wed, Oct 14, 2020 at 1:07 PM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello, have a look to /var/log/messages or /var/log/syslog, depending on the distribution. Kamailio might be logged there. 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 Santanu B Sent: Wednesday, October 14, 2020 7:09 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: Re: [SR-Users] Regd : SIP Configuration in Kamailio Dear David, In /var/log folder I am unable to see any kamailio log. Only syslog file is available. Please help me to find the Kamailio log. Also please guide me to find out the trace also as I am very new to SIP Server. Thanks a lot. Regards, Santanu On Tue, Oct 13, 2020 at 4:05 PM David Villasmil <david.villasmil.work(a)gmail.com<mailto:david.villasmil.work@gmail.com>> wrote: Hello, You will need to provide more information. What happens? What errors do you see in kamailio’s log? A trace would also be nice. On Tue, 13 Oct 2020 at 06:24, Santanu B <santanu.br(a)gmail.com<mailto:santanu.br@gmail.com>> wrote: Hi, We are using Jitsi Meet for Video Conference Service. We want our SIP endpoint to join in the conference room in Jitsi. For that i am trying to configure Kamailio SIP Server in our environment. I have installed the Server and my endpoints are registered in my SIP server. Both endpoints are able to connect to each other. But I am unable to configure the SIP endpoints to join in the Meet Conference Room. Please guide me to configure. Thanks and regards, Santanu _______________________________________________ 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 -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com<mailto:david.villasmil.work@gmail.com> phone: +34669448337 _______________________________________________ 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 [View Less]

1 0

SRTP
by Andy Kama 14 Oct '20

14 Oct '20

Hi All, I have setup a tls connection to a sip provider and it works perfectly But they are requesting i send srtp i can find any documentation how i do it with rtpengine etc? any guidance would be appreciated

3 3

pstn_route add_route(): route name <IP> not defined error
by sai Sudheer 14 Oct '20

14 Oct '20

Hii,I am trying to use pstn_route module for the first time, and i want to route the invite to specific pstn server based on its prefix.I have loaded the module & setup the DB, and it's giving error saying route name (from DB) is not defined after adding the a prefix into DB table., and there were no errors when DB table is empty.Not sure how to defined it, or i dont know what did i miss. Please help. #### CONFIG ##########loadmodule "prefix_route.so"modparam("prefix_route", "db_url", "… [View More]

2 2

how to get a value from SIP INVITE Header
by sai sudheer 14 Oct '20

14 Oct '20

Hii Please help me to get the a value from SIP INVITE header reached to kamailio like INVITE sip:+341930203454@sub.domain.com;myid=+34@sub.domain.com SIP/2.0 and i want to save the myid value +34 into a variable, without the domain name. $var(uri) = $sel(ruri); xavp_params_explode("$(var(uri){s.unbracket})", "uri"); xlog("L_INFO", "$var(uri) Received converted to $xavp(uri=>myid[0])\n"); I tried above and it prints +34(a)sub.… [View More]

3 7

'302 Moved temporarily' contact parsing error
by David VILLAUME 14 Oct '20

14 Oct '20

Hello, I see parsing errors on 302 contact header that seems compliant to RFC : Contact:<sip:172.16.0.21:5060>;q=0.5,<sip:172.16.0.22:5060>;q=0.25 <core> [core/parser/parse_addr_spec.c:479]: parse_to_param(): invalid character ',' in status 27: [;q=0.5] Is there an error in my contact or is it truly a parsing error ? Regards, David

3 6

Wants to know kamailio supports IMS with SRVCC Handover or not
by Anwesh Babu 14 Oct '20

14 Oct '20

Hello Team, I am working for a telecom company and want to use Kamailio for my VoLTE testing. I had earlier used these tools for my VoLTE testing using a Polaris CNE. But i have a requirement to perform SRVCC Handover for CS/CS+PS. will Kamailio support the SRVCC Handover? If supported, can it be possible to share the details ? -- Best Regards, Anwesh Babu T

1 0

routing calls based on prefix
by Andy Kama 13 Oct '20

13 Oct '20

Hi All, What is the best way to approach this? example if a call comes into kamailio with a specific number it example to:123456789 it must go to the dispatcher module but if a call comes with any other number it must route to a uac or can you use uac with dispatcher? basically i want to route inbound calls to a dispatcher and calls from that dispatcher out a uac

2 2

Caseless regex
by Marat Gareev 13 Oct '20

13 Oct '20

Hello, Is it possible write more readable regular expression if ($tU =~ "(?i)^test$") { ... } instead of "^[tT][eE][sS][tT]$"? On the first option, I get the error: 0(47250) ERROR: <core> [core/rvalue.c:3038]: fix_match_rve(): Bad regular expression Regards, Marat

3 5

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