- sr-users - kamailio.org

disparcher making loop with call
by Gaurav Bmotra 22 Nov '19

22 Nov '19

hi i m using kamailio 5.3 as register server and using dispatcher i m dendign the calls to freeswitch .. but the issue is then freeswitch send back call to kamailio after processing media ... it should go back to client but it again send call to freeswitch ,, which create the loop and hangup the call with (Temporarily Unavailable (code: 480)) *what i want *client1------>Kamailio------>FS-----Kamailio----->Client2 *but I am getting this * client1------>Kamailio------>FS-----Kamailio----->FS----->kamailio----->FS *Routing Logic*------------------------------- if(!ds_is_from_list()) { route(DISPATCH); } -------- # Dispatch requests route[DISPATCH] { # round robin dispatching on gateways group '1' if(!ds_select_dst("1", "4")) { send_reply("404", "No destination"); exit; } xdbg("--- SCRIPT: going to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } # Try next destionations in failure route failure_route[RTF_DISPATCH] { xnotice("RTF_DISPATCH: $rm $rU [$ci]"); if (t_is_canceled()) { exit; } # next DST - only for 500 or local timeout if (t_check_status("(^5)") or (t_branch_timeout() and !t_branch_replied())) { xnotice("RTF_DISPATCH: WARNING $du is broken and marked as inactive"); # ds_mark_dst("ip"); if(ds_next_dst()) { #xdbg("--- SCRIPT: retrying to <$ru> via <$du> (attrs: $xavp(_dsdst_=>attrs))\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } } } -- thank you *Regards:* Gaurav Kumar

3 2

How to retrieve local socket that will be used to send a message from the branch route
by Patrick Wakano 22 Nov '19

22 Nov '19

Hello list, Hope you are all doing well! I am trying to figure out a way to retrieve the local socket the t_relay() has decided to use in a mhomed=1 env. Is there a way to do that? I couldn't find any variable other than the $snd ones that maybe have this info, but I am not using onsend_route anyway..... I am after this value because this is what I can use to figure out if I need to engage RTPEngine with parameters "external, internal", "external, external", "internal, external" or "internal, internal". In my case, my server is in between two networks, and calls can traverse or can be routed back to the same interface depending on what was decide by the LCR module. Signalling is fine, but engaging the RTPEngine must be done with the correct parameters to get the correct IPs in the SDP, other else I get one way audio in the call..... Any help is much appreciated! Thank you! Kind regards, Patrick Wakano

4 7

Adding SIP Gateway Endpoint in Kamailio
by Sujit Roy 21 Nov '19

21 Nov '19

Hello Here is my call flow scenario. SIP Gateway (A) Kamailio (K) Asterisk (AST) SIP Gateway (B) Now i want to send calls from A -> B by using Asterisk as media server. Kamailio shall be used to authenticate A and allow A to send calls to B. What are the configurations i need to make in Kamailio and Asterisk ? Thanks in advance. -- Regards =================== Sujit Roy

3 6

How to access different uris in a header
by Duarte Rocha 21 Nov '19

21 Nov '19

Greetings, In order to identify Redirecting Number and Original Called Number on a given request i look for the top( Redirecting Number) and bottom (Original Called) Diversion headers using hdr(Diversion)[0] and hdr(Diversion)[-1]. However, i have a client that sends me all the Diversions URIS in the same header. Does kamailio has a similar tool for accessing the different URIS in the header? Best Regards,

2 1

CentOS Repo for Kamailio 5.3 - Strange Python23 Dependency?
by Zach Nielsen 21 Nov '19

21 Nov '19

Hi all, Working with some of our Centos-based Kamailio boxes lately has produced a strange result when using the provided yum repos (download.opensuse.org). When trying to yum update the system or install some additional modules, we're getting feedback from yum indicating that it's expecting /usr/bin/python23 --> Finished Dependency Resolution Error: Package: kamailio-5.3.1-3.1.x86_64 (home_kamailio_v5.3.x-rpms) Requires: /usr/bin/python23 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Tried my best to do my due diligence here to make sure there was nothing up with our local env that was causing this, but this issue persists across multiple systems, including a new (no frills) one that we just build out. Can I get some confirmation if this is a "me" issue, or if maybe there's an issue with what made it into the repo? Also, just a general question... what's the typical way of you folks deploying Kamailio from a sysadmin perspective? Do you generally compile from source, or do any of you use the provided repositories to manage it? Thanks! Zach

5 6

kamailio Dispatcher error
by Gaurav Bmotra 20 Nov '19

20 Nov '19

hi i want to use dispatcher Module and following is the config.. --------------------------------------- loadmodule "dispatcher.so" -------------- modparam("dispatcher", "db_url", "mysql://kamailio:kamailiorw@localhost /kamailio") modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") modparam("dispatcher", "ds_hash_size", 2) -------------------------------------------------------------- but when i hit $ kamailio out put: ERROR: bad config file (4 errors) ------------------------------------------------------ logs : kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/lib/systemd/system/kamailio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-11-20 15:16:34 IST; 16s ago Process: 25747 ExecStart=/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -u $USER -g $GROUP (code=exited, status=255/EXCEPTION) Nov 20 15:16:34 gaurav-Latitude-E7240 systemd[1]: kamailio.service: Service RestartSec=100ms expired, scheduling restart. Nov 20 15:16:34 gaurav-Latitude-E7240 systemd[1]: kamailio.service: Scheduled restart job, restart counter is at 5. Nov 20 15:16:34 gaurav-Latitude-E7240 systemd[1]: Stopped Kamailio (OpenSER) - the Open Source SIP Server. Nov 20 15:16:34 gaurav-Latitude-E7240 systemd[1]: kamailio.service: Start request repeated too quickly. Nov 20 15:16:34 gaurav-Latitude-E7240 systemd[1]: kamailio.service: Failed with result 'exit-code'. Nov 20 15:16:34 gaurav-Latitude-E7240 systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. ------------------------------------------------------------- plz help me -- Thank you *Regards:* Gaurav Kumar

4 6

Dynamic routing and REGISTER
by Igor Olhovskiy 20 Nov '19

20 Nov '19

Hi! I’m trying to get `drouting` module working for REGISTER. But seems it’s not passing one of internal checks, cause in REGISTER R-URI does not contains username and I’m getting errors drouting [drouting.c:567]: build_ruri(): stripping 0 makes username <> null drouting [drouting.c:970]: do_routing(): failed to build ruri So, as I got, this module is mainly for calls (means INVITE) routing, rather than to use it like one more dispatcher, or it’s also a way to handle this part here? Thanks, Igor

3 5

Query regarding Kamailio Sip Server for IMS supporting VOLTE
by Shubhendu Das 20 Nov '19

20 Nov '19

Hi , I have a query regarding Kamailio open source SIP server. Does it have any release, where its supports the feature of IMS supporting VOLTE with real commercial mobile phones(IMSI based) ? If so, what is the release number ? Please also let me know about the supported mobile phones list. BR, Shubhendu -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

1 0

How to intercept an INVITE after (ts_append)
by Oleg Podguyko 20 Nov '19

20 Nov '19

Hello everybody! Kamailio works as a Registrar. Additionally, rtpengine is deployed next to it. Using rtpgngine module I proxy media stream via rtpengine(rtpengine_manage()). I change SDP. SiP2SIP calls work fine. Now I would like to have possibility to "wake up" sip-clients(at the android and ios phones) which are usually not on-line via push notification. Trying to use TSILO module. # User location service route[LOCATION] { lookup("location"); $var(rc) = $rc; if (is_method("INVITE")) { if (t_newtran()) { ts_store(); # if it a new transuction ,it will be store for some time. } } switch ($var(rc)) { case 1: route(RELAY); break; case -1: break; case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } # Handle SIP registrations route[REGISTRAR] { if (!is_method("REGISTER")) return; if (!save("location")) { sl_reply_error(); } ts_append("location", "$tu"); # if transuction for this sip-client is exist. The invite will be send. exit; } If the client is not registered at the kamailio during the call. Then such calls are stored through the "ts_store" function for some time. And if during this time the client send register, kamailio will be sent INVITE to it. But I have the problem. Such calls after "wake up"go through a special branch route that I don't know how to intercept. As a result, I can't change SDP(using rtpengite_manage commands) and rtp stream do not proxy via rtpengine… and call failed. /usr/sbin/kamailio[9957]: exec: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} *** cfgtrace:request_route=[REGISTRAR] c=[/etc/kamailio/kamailio.cfg] l=428 a=26 n=ts_append /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tsilo [ts_append.c:72]: ts_append(): transaction 36343:92182831 found for 777777777, going to append branches /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tm [t_lookup.c:1629]: t_lookup_ident_filter(): transaction found /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} registrar [lookup.c:255]: lookup_helper(): contact for [777777777] found by address /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} registrar [lookup.c:456]: lookup_helper(): instance is /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tm [t_append_branches.c:77]: t_append_branches(): transaction 36343:92182831 in status 0 /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tm [t_append_branches.c:99]: t_append_branches(): Call uvAzTGsEV9N2ReDjmWoo8A..: 0 (1) outgoing branches /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tm [t_append_branches.c:126]: t_append_branches(): Current uri sip:77777777@95.165.146.181:63618;transport=TCP;rinstance=8b1865b95767b7ba /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} <core> [core/msg_translator.c:2933]: create_via_hf(): id added: <;i=1>, rcv proto=2 /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tm [t_append_branches.c:149]: t_append_branches(): added branch [sip:777777777@95.165.146.181:63618;transport=TCP;rinstance=8b1865b95767b7ba] with ruid [uloc-5dd2faa0-26e5-1] /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} tm [t_append_branches.c:163]: t_append_branches(): Call uvAzTGsEV9N2ReDjmWoo8A..: 0 (0) outgoing branches after clear_branches() /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} <core> [core/tcp_main.c:2238]: tcpconn_send_put(): send from reader (9957 (22)), reusing fd /usr/sbin/kamailio[9957]: DEBUG: {1 2 REGISTER JxPcA9D1hIJ8PmkcnOvI7g..} <core> [core/tcp_main.c:2473]: tcpconn_do_send(): sending... -- Oleg Podguyko

2 2

TLS v 1.3 failed call
by Andrew Chen 19 Nov '19

19 Nov '19

Hi guys, I was wondering if someone can help decipher what these few lines mean? Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:431]: tls_accept(): tls_accept: new connection from 10.94.98.18:51698 using TLSv1.3 TLS_AES_256_GCM_SHA384 256 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:434]: tls_accept(): tls_accept: local socket: 206.81.191.45:443 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:445]: tls_accept(): tls_accept: client did not present a certificate Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: tls [tls_server.c:1189]: tls_read_f(): Reading on a renegotiation of connection (n:1652) (0) Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: <core> [core/tcp_read.c:1527]: tcp_read_req(): EOF Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0x56367f8b8f80, 12, -1, 0x10) fd_no=2 called Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: <core> [core/tcp_read.c:1680]: release_tcpconn(): releasing con 0x7fcfc20c57b0, state -1, fd=12, id=23 ([10.94.98.18]:51698 -> [10.94.98.18]:443) Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21501]: DEBUG: <core> [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7fcfc2089f88 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21517]: DEBUG: <core> [core/tcp_main.c:3320]: handle_tcp_child(): reader response= 7fcfc20c57b0, -1 from 16 Nov 19 20:12:50 sjomainkama51 /usr/sbin/kamailio[21517]: DEBUG: tls [tls_server.c:683]: tls_h_close(): Closing SSL connection 0x7fcfc2089f88 Bottom line is kamailio closed the connection and I have method setting to this: root@sjomainkama51:/etc/kamailio # grep method tls.cfg method = TLSv1.1+ Supposedly this should work? -- 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

Fwd: Websocket immediately disconnecting
by Tom D 19 Nov '19

19 Nov '19

Gentlemen, Thanks for your feedback. Yes, I've doubled the RAM last night (between my posts) and I am monitoring the behavior. It *feels* that it is definitely working better. I haven't enabled memjoin yet - are there any repercussions that should be expected for enabling memjoin=yes? Thanks for your guidance. Tom

3 2

Websocket immediately disconnecting
by Tom D 19 Nov '19

19 Nov '19

Hi David, Thanks for your reply. After increasing the verbosity of the debugging, I found the following entries. So am I understanding the log correctly: the websocket module is trying to get some free memory (from Kamilio's general pool?). It doesn't receive any yet proceeds with parsing the response (I get this same parsing error even when it's working) and ultimately, it doesn't register the websocket? I appreciate your (or anyone's) thoughts. Regards, Tom Nov 19 02:44:44 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: tls [tls_domain.c:737]: sr_ssl_ctx_info_callback(): SSL handshake started Nov 19 02:44:44 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: tls [tls_domain.c:749]: sr_ssl_ctx_info_callback(): SSL handshake done Nov 19 02:44:44 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: tls [tls_domain.c:753]: sr_ssl_ctx_info_callback(): SSL disable renegotiation Nov 19 02:44:44 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: tls [tls_server.c:431]: tls_accept(): tls_accept: new connection from HI.DD.E.N:63356 using TLSv1/SSLv3 AES256-GCM-SHA384 256 Nov 19 02:44:44 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: tls [tls_server.c:434]: tls_accept(): tls_accept: local socket: HI.DD.E.N:8089 Nov 19 02:44:44 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: tls [tls_server.c:445]: tls_accept(): tls_accept: client did not present a certificate Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: CRITICAL: <script>: 857:HTTP Request Received Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: ERROR: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7f8b8cdcd000, 65728); Free fragment not found! Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: ERROR: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7f8b8cdcd000, 65728) called from websocket: ws_conn.c: wsconn_add(197), module: websocket; Free fragment not found! Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: ERROR: websocket [ws_conn.c:199]: wsconn_add(): allocating shared memory Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: ERROR: <core> [core/parser/parse_fline.c:262]: parse_first_line(): parse_first_line: bad message (offset: 22) Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TLS HI.DD.E.N:63356#015#012Access-Control-Allow-Origin: https://www.doubango.org#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: taS0s3Z7t4tOhklSbJDLGmSSYsY=#015#012Server: kamailio (5.2.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012> Nov 19 02:44:45 MY-HOSTNAME /usr/sbin/kamailio[14928]: ERROR: websocket [ws_frame.c:583]: ws_frame_receive(): WebSocket connection not found

3 3

Asterisk text messages not delivered to SIP client
by Adesh Pandey 19 Nov '19

19 Nov '19

Hi Guys, I have been using Kamailio as dispatcher but I have been facing a weird situation that when asterisk SendText command says that message was delivered successfully but webrtc sip client did not receive the message. My deployment has Kamailio as registrar where sip users are registered and when they make any outgoing call, the call is proxied by RTPEngine and then dispatched to Asterisk boxes. Asterisk boxes send some text to the client using SendText but the message is not received by the SIP client. My config as follows: https://gist.github.com/adeshpandey/2c338db7f5d992267f7415de0325e0b4

1 0

Kamailio meeting Istanbul and Cairo
by Henning Westerholt 19 Nov '19

19 Nov '19

Hello, I will be in about 2 weeks in Istanbul and in Cairo a few days later. I am thinking of organizing a Kamailio/SIP/VoIP social networking event (perhaps a dinner or a pub meeting). Possible dates are the 19th- 20th November in Istanbul and the 23th - 24th November in Cairo. Are people from the community interested in joining such event? If yes, write me your preferred date -- based on feedback in the next days, it will be decided whether it is going to happen and when. Best regards, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services

2 2

Re: [SR-Users] call disconnected in 45 min
by Liu, Charles 18 Nov '19

18 Nov '19

Hi All, I have install kamailio IMS using the example config files for P/S/I-cscf with version 5.2... call randomly disconnected between 15 to 45 minutes. Wireshark log show scscf sent BYE to the caller and callee. Any idea what maybe the problem? Scscf debug output ......... ............ 20(25) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp 20(25) INFO: ims_registrar_scscf [cxdx_sar.c:84]: create_return_code(): created AVP successfully : [saa_return_code] - [1] 13(18) DEBUG: ims_dialog [dlg_handlers.c:1923]: print_all_dlgs(): ********************13(18) DEBUG: ims_dialog [dlg_handlers.c:1924]: print_all_dlgs(): printing 4096 dialogs 13(18) DEBUG: ims_dialog [dlg_handlers.c:1862]: internal_print_all_dlg(): Trying to get lock for printing 13(18) DEBUG: ims_dialog [dlg_handlers.c:1868]: internal_print_all_dlg(): ----------------------------13(18) DEBUG: ims_dialog [dlg_handlers.c:1869]: internal_print_all_dlg(): Dialog h_entry:h_id = [3396 : 2798] 13(18) DEBUG: ims_dialog [dlg_handlers.c:1870]: internal_print_all_dlg(): Dialog age: 2749 13(18) DEBUG: ims_dialog [dlg_handlers.c:1871]: internal_print_all_dlg(): Dialog call-id: ATokIPEjouNpuwSo6MpHUw.. 13(18) DEBUG: ims_dialog [dlg_handlers.c:1872]: internal_print_all_dlg(): Dialog state: 4 13(18) DEBUG: ims_dialog [dlg_handlers.c:1873]: internal_print_all_dlg(): Dialog ref counter: 2 13(18) DEBUG: ims_dialog [dlg_handlers.c:1874]: internal_print_all_dlg(): Dialog did: 13(18) DEBUG: ims_dialog [dlg_handlers.c:1875]: internal_print_all_dlg(): Dialog from_tag: 8975d611 13(18) DEBUG: ims_dialog [dlg_handlers.c:1876]: internal_print_all_dlg(): Dialog from_uri: sip:bob@ims.mnc001.mcc001.3gppnetwork.org;transport=UDP 13(18) DEBUG: ims_dialog [dlg_handlers.c:1877]: internal_print_all_dlg(): Dialog caller contact: sip:bob@192.168.164.23:39180;transport=UDP 13(18) DEBUG: ims_dialog [dlg_handlers.c:1878]: internal_print_all_dlg(): Dialog first request cseq: 1 13(18) DEBUG: ims_dialog [dlg_handlers.c:1879]: internal_print_all_dlg(): Dialog caller route set: <sip:mo@10.1.1.1;lr=on;ftag=8975d611;rm=8> 13(18) DEBUG: ims_dialog [dlg_handlers.c:1880]: internal_print_all_dlg(): Dialog lifetime: 43200 13(18) DEBUG: ims_dialog [dlg_handlers.c:1881]: internal_print_all_dlg(): Dialog bind_address: udp:172.26.1.60:6060 13(18) DEBUG: ims_dialog [dlg_handlers.c:1882]: internal_print_all_dlg(): Dialog-creating transaction pointer [0x7f8bb2a51858] 13(18) DEBUG: ims_dialog [dlg_handlers.c:1888]: internal_print_all_dlg(): ----------13(18) DEBUG: ims_dialog [dlg_handlers.c:1889]: internal_print_all_dlg(): Dialog out h_entry:h_id = [3296 : 0] 13(18) DEBUG: ims_dialog [dlg_handlers.c:1890]: internal_print_all_dlg(): Dialog out did: 13(18) DEBUG: ims_dialog [dlg_handlers.c:1891]: internal_print_all_dlg(): Dialog out to_tag: c9eb5e55 13(18) DEBUG: ims_dialog [dlg_handlers.c:1892]: internal_print_all_dlg(): Dialog out caller cseq: 1 13(18) DEBUG: ims_dialog [dlg_handlers.c:1893]: internal_print_all_dlg(): Dialog out callee cseq: 1 13(18) DEBUG: ims_dialog [dlg_handlers.c:1894]: internal_print_all_dlg(): Dialog out callee contact: sip:alice@192.168.164.84:49153;alias=192.168.164.84~49153~1 13(18) DEBUG: ims_dialog [dlg_handlers.c:1895]: internal_print_all_dlg(): Dialog out callee route set: <sip:mt@172.26.1.60:6060;lr;ftag=8975d611;did=44d.eea>,<sip:mt@10.1.1.1;lr;ftag=8975d611;rm=7> 13(18) DEBUG: ims_dialog [dlg_handlers.c:1896]: internal_print_all_dlg(): Dialog out branch: z9hG4bKb7d5.6f11b9b34a8a493a3a1b7949831e2f47.0 13(18) DEBUG: ims_dialog [dlg_handlers.c:1897]: internal_print_all_dlg(): Dialog out state (deleted): 0 13(18) DEBUG: ims_dialog [dlg_handlers.c:1899]: internal_print_all_dlg(): ----------13(18) DEBUG: ims_dialog [dlg_handlers.c:1903]: internal_print_all_dlg(): Releasing lock for dlgout 13(18) DEBUG: ims_dialog [dlg_handlers.c:1906]: internal_print_all_dlg(): ----------------------------13(18) DEBUG: ims_dialog [dlg_handlers.c:1934]: print_all_dlgs(): ********************13(18) DEBUG: ims_auth [authorize.c:187]: reg_await_timer(): Looking for expired/useless at 44469727 13(18) DEBUG: ims_auth [authorize.c:192]: reg_await_timer(): Slot 121 <alice(a)ims.mnc001.mcc001.3gppnetwork.org<mailto:alice@ims.mnc001.mcc001.3gppnetwork.org>> 13(18) DEBUG: ims_auth [authorize.c:197]: reg_await_timer(): .. AV 1 - 3 Exp 44469993 0x7f8bb2a5c988 13(18) DEBUG: ims_auth [authorize.c:192]: reg_await_timer(): Slot 914 <bob(a)ims.mnc001.mcc001.3gppnetwork.org<mailto:bob@ims.mnc001.mcc001.3gppnetwork.org>> 13(18) DEBUG: ims_auth [authorize.c:197]: reg_await_timer(): .. AV 1 - 3 Exp 44470022 0x7f8bb2a54e88 13(18) DEBUG: ims_auth [authorize.c:197]: reg_await_timer(): .. AV 1 - 2 Exp 44469974 0x7f8bb2a506a8 13(18) DEBUG: ims_auth [authorize.c:203]: reg_await_timer(): ... dropping av 1 - 2 13(18) DEBUG: ims_auth [authorize.c:232]: reg_await_timer(): [DONE] Looking for expired/useless at 44469727 13(18) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f8bb2a551f8 with 1 -> 3 13(18) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=2798 found on entry 3396 13(18) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f8bb2a551f8 with 1 -> 2 13(18) DEBUG: ims_dialog [dlg_req_within.c:379]: dlg_terminate(): terminating confirmed dialog 13(18) DEBUG: ims_dialog [dlg_req_within.c:272]: send_bye(): sending BYE to caller 13(18) DEBUG: ims_dialog [dlg_hash.c:1047]: ref_dlg(): ref dlg 0x7f8bb2a551f8 with 1 -> 3 13(18) DEBUG: ims_dialog [dlg_req_within.c:289]: send_bye(): BYE sent to caller 13(18) DEBUG: ims_dialog [dlg_req_within.c:272]: send_bye(): sending BYE to callee 13(18) DEBUG: ims_dialog [dlg_hash.c:1047]: ref_dlg(): ref dlg 0x7f8bb2a551f8 with 1 -> 4 13(18) DEBUG: ims_dialog [dlg_req_within.c:289]: send_bye(): BYE sent to callee 1(6) ERROR: <script>: BYE (sip:bob@ims.mnc001.mcc001.3gppnetwork.org;transport=UDP (172.26.1.60:6060) to sip:alice@ims.mnc001.mcc001.3gppnetwork.org, ATokIPEjouNpuwSo6MpHUw..) 1(6) DEBUG: ims_dialog [dlg_handlers.c:844]: dlg_onroute(): route param is '44d.eea' (len=7) 1(6) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f8bb2a551f8 with 1 -> 5 1(6) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=2798 found on entry 3396 1(6) DEBUG: ims_dialog [dlg_hash.h:459]: match_dialog(): searching dlg_outs 1(6) DEBUG: ims_dialog [dlg_hash.h:496]: match_dialog(): p: 0x7f8bb2a68c48 ft[8975d611] tt [c9eb5e55] 1(6) DEBUG: ims_dialog [dlg_hash.h:520]: match_dialog(): dout: tt[c9eb5e55] 1(6) DEBUG: ims_dialog [dlg_profile.c:419]: set_current_dialog(): setting current dialog [3396:2798] 1(6) DEBUG: ims_dialog [dlg_hash.c:1293]: next_state_dlg(): dialog 0x7f8bb2a551f8 changed from state 4 to state 6, due event 7 CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving.

1 0

Re: [SR-Users] Saving REGISTER status in kamailio database while REGSITER packets are forwarded.
by Voip support 18 Nov '19

18 Nov '19

I figured this finally out and all works for me very well. In usrloc dbmode i set value of 3 (its saving immediately changes into DB). In request route for REGISTER method i set t_on_reply("MANAGE_REPLY_REGISTER" and for REGISTER with expires set to 0 i set t_on_reply("MANAGE_REPLY_UNREGISTER") (used pseudovariable $expires(max)). I stored Contact header in $avp(contact) for unREGISTER request for further use when calling unregister(). Then in onreply_route for MANAGE_REPLY_REGISTER i call save lcoation and in MANAGE_REPLY_UNREGISTER for reply code 200 i call unregister function with the stored contact (i had to remove < > and display name using re.subst). So far it looks to work perfect. pon., 18 lis 2019 o 13:38 Voip support <voipexpert0(a)gmail.com> napisał(a): > > Thanks again for all replies... I need to try it out - did not have time > for it yet. > > I think i will go for the onreply_route answer and try to save location in > this place. > > pon., 18 lis 2019 o 06:23 Joel Serrano <joel(a)textplus.com> napisał(a): > >> Yes sir! Works perfectly! >> >> To give you a quick example: >> >> 1) Add in the appropriate place for the REGISTER request: >> t_on_reply("MANAGE_REG_REPLY"); >> 2) Create a new onreply route: >> >> # Manage registration incoming replies >> onreply_route[MANAGE_REG_REPLY] { >> if(status=~"2[0-9][0-9]") { >> if (save("location", "0x04")) { >> xlog("L_NOTICE", "[usrloc] saved user location\n"); >> } >> } >> } >> >> >> Note1: In my setup, I needed to strictly simulate asterisk (chan_sip) >> registrations, so only one AoR was allowed, thus the flags 0x04, if you are >> using PJSIP you might not need it. >> Note2: With this example code, a "unregister" (REGISTER with expires=0) >> will not remove the AoR from Kamailio, to achieve that I check >> independently if the header Expires exists and is 0, or if the contact >> param Expires exists and is 0, and in that case I use the unregister() >> function instead of the save(). >> >> Hope it helps! >> Joel. >> >> >> >> On Sun, Nov 17, 2019 at 5:42 PM Ovidiu Sas <osas(a)voipembedded.com> wrote: >> >>> Did it work calling save() on the reply route? >>> >>> -ovidiu >>> >>> On Thu, Nov 14, 2019 at 6:20 PM Voip support <voipexpert0(a)gmail.com> >>> wrote: >>> > >>> > I am using kamailio 5.3. >>> > >>> > Ovidiu Sas, i will try this tomorrow today is bit late. Maybe it could >>> work. >>> > >>> > David Villasmil , i know i can use SQLOPS but i was thinking of easier >>> method of doing this. >>> > By successful REGISTER i mean save only REGISTER attempt that >>> authenticated correctly at SIP server and in 200 OK a binding was returned. >>> > Same if the binding is later removed i would like remove it from >>> database. I need this because when i run REGISTER over kamailio to >>> destination SIP server i see all register from same IP. >>> > I need to be able to check what was the real source IP of client >>> REGISTER. >>> > >>> > Regards, >>> > Tomasz >>> > >>> > >>> > >>> > pt., 15 lis 2019 o 00:16 Mike from ApoloCore <mike(a)apolocore.com> >>> napisał(a): >>> >> >>> >> I am using kamailio 5.3. >>> >> >>> >> Ovidiu Sas, i will try this tomorrow today is bit late. Maybe it >>> could work. >>> >> >>> >> David Villasmil , i know i can use SQLOPS but i was thinking of >>> easier method of doing this. >>> >> By successful REGISTER i mean save only REGISTER attempt that >>> authenticated correctly at SIP server and in 200 OK a binding was returned. >>> >> Same if the binding is later removed i would like remove it from >>> database. I need this because when i run REGISTER over kamailio to >>> destination SIP server i see all register from same IP. >>> >> I need to be able to check what was the real source IP of client >>> REGISTER. >>> >> >>> >> Regards, >>> >> Tomasz >>> >> >>> >> >>> >> >>> >> >>> >> czw., 14 lis 2019 o 23:33 Ovidiu Sas <osas(a)voipembedded.com> >>> napisał(a): >>> >>> >>> >>> Try to use save() when you process the 200 ok reply for REGISTER in >>> >>> the reply route. >>> >>> >>> >>> Regards, >>> >>> Ovidiu Sas >>> >>> >>> >>> On Thu, Nov 14, 2019 at 3:40 PM Voip support <voipexpert0(a)gmail.com> >>> wrote: >>> >>> > >>> >>> > I setup kamailio to forward REGISTER packets using dispatcher to >>> two servers main and backup. >>> >>> > >>> >>> > The routing logic is quite simple i use the dispatcher probing >>> mechanism to detect if my main dispatcher set id (one server) is active or >>> inactive once it detect a failure all packets are sent to secondary SIP >>> server to achieve High Availability. >>> >>> > >>> >>> > I am looking for module or a way to save into kamailio database >>> client information such as IP address, register username (from FROM >>> header), digest username (authorization username), call-id for successful >>> registration. >>> >>> > >>> >>> > I tried to use registrar module but once i used function >>> save("location") the client was registered on kamailio and packets was not >>> forwarded to main/secondary SIP server (like dispatcher stopped working, >>> the destination did not override). >>> >>> > >>> >>> > REGISTER is sent to SIP URI of kamailio. >>> >>> > >>> >>> > Please let me know if you have any idea how to make this data >>> update in database (insert an entry on fresh successfull REGISTER, delete >>> on expired or removed binding). >>> >>> > >>> >>> > Best regards, >>> >>> > Tomasz >>> >>> > >>> >>> > _______________________________________________ >>> >>> > Kamailio (SER) - Users Mailing List >>> >>> > sr-users(a)lists.kamailio.org >>> >>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> VoIP Embedded, Inc. >>> >>> http://www.voipembedded.com >>> >>> >>> >>> _______________________________________________ >>> >>> Kamailio (SER) - Users Mailing List >>> >>> sr-users(a)lists.kamailio.org >>> >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> > >>> > _______________________________________________ >>> > Kamailio (SER) - Users Mailing List >>> > sr-users(a)lists.kamailio.org >>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >>> >>> -- >>> VoIP Embedded, Inc. >>> http://www.voipembedded.com >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >>

1 0

Websocket immediately disconnecting
by Tom D 18 Nov '19

18 Nov '19

Hi Everyone, We're running Kamailio 5.2.5 with XHTTP, Websocket and TLS extensions - for the purpose of being able to provide WebRTC capability. The settings for the HTTP request are quite default as set out below. The SIP client we're using is SIP5ML in different web browsers. After a successful start of Kamailio, it is possible to use SIP5ML and its features - i.e. it REGISTER's properly, calls can be made, etc. After about a few hours of running, Kamailio refuses to interact and abruptly closes the TCP connection. The only solution (discovered so far) is to restart Kamailio, which is not feasible on a server that is serving production needs. (On our development server, where the load is only a fraction - this problem does not occur). When the problems does start to occur, in Wireshark I see: 1) Normal TLS negotiation and certificate exchange; followed by 2) SIP5ML initiating the initial HTTP GET 3) Kamailio responds to the upgrade with a 101/Switch Protocols. (4- SIP5ML outputs a SIP REGISTER on a defunct socket as its was closed) Immediately after the 101/Switching Protocol message is received, Kamailio closes down the TCP connection with a FIN message. Nothing in the message or Kamailio log files help to identify what module is responsible for this. Would anyone have any advise where to look further? BTW, I don't see the TCP connection being Reset in the exchanges - so any advise will be appreciated. Tom event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); if ($Rp != 8089) { xlogl("L_CRIT", "HTTP request received on $Rp\n"); xhttp_reply("403", "Forbidden - 0x24", "", ""); exit; } xlogl("L_CRIT", "HTTP Request Received\n"); if ($hdr(Upgrade)=~"websocket" && $hdr(Connection)=~"Upgrade" && $rm=~"GET") { # Validate Host - make sure the client is using the correct # alias for WebSockets if ($hdr(Host) == $null || !is_myself("sip:" + $hdr(Host))) { xlogl("L_CRIT", "Bad host $hdr(Host)\n"); xhttp_reply("403", "Forbidden - 0x25", "", ""); exit; } # ws_handle_handshake() exits (no further configuration file # processing of the request) when complete. if (ws_handle_handshake()) { # Optional... cache some information about the # successful connection exit; } } xhttp_reply("404", "Resource Not Found - 0x27", "", ""); } event_route[websocket:closed] { xlogl("L_CRIT", "WebSocket connection from $si:$sp has closed\n"); }

2 1

Kamailio stop responding to AWS R53 health check
by Andrew Chen 18 Nov '19

18 Nov '19

Hi all, R53 reported healthcheck failure on tcp port 5060. Looking at the system, all the ports that kamailio listens on can't be monitored remotely. To test this theory, I can telnet successfully to consul port. I ran tcpdump and see no responses returned back to R53 monitoring hosts: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens5, link-type EN10MB (Ethernet), capture size 262144 bytes 19:11:49.368378 IP ec2-54-241-32-75.us-west-1.compute.amazonaws.com.10072 > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 1252984048, win 29200, options [mss 1460,sackOK,TS val 3770272726 ecr 0,nop,wscale 7], length 0 19:11:49.558877 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, options [mss 1460,sackOK,TS val 1780607162 ecr 0,nop,wscale 7], length 0 19:11:50.572870 IP ec2-107-23-255-43.compute-1.amazonaws.com.60794 > sjoprodkama51.fuzemeeting.com.sip: Flags [S], seq 3484910496, win 29200, options [mss 1460,sackOK,TS val 1780608175 ecr 0,nop,wscale 7], length 0 Fixed the issue after restarting kamailio process. Given this system is support production traffic, we have minimized the logging on it. The events that we thought may lead to this is as follows: Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdd829e8 r: 0x7f33fdd82a68 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb70738 r: 0x7f33fdb707b8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20310]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdd829e8 r: 0x7f33fdd82a68 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaec8f0 r: 0x7f33fdaec970 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd93e6c0 r: 0x7f33fd93e740 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaec8f0 r: 0x7f33fdaec970 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaec8f0 r: 0x7f33fdaec970 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdd829e8 r: 0x7f33fdd82a68 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda69958 r: 0x7f33fda699d8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdd829e8 r: 0x7f33fdd82a68 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda69958 r: 0x7f33fda699d8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20309]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdd829e8 r: 0x7f33fdd82a68 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20311]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20312]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20312]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20312]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20312]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20312]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20312]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdbd5d78 r: 0x7f33fdbd5df8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb822d0 r: 0x7f33fdb82350 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb822d0 r: 0x7f33fdb82350 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda47c98 r: 0x7f33fda47d18 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaec8f0 r: 0x7f33fdaec970 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdacac30 r: 0x7f33fdacacb0 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaec8f0 r: 0x7f33fdaec970 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20317]: BUG: tls [tls_server.c:1303]: tls_read_f(): IO error (0) Success Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20317]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdacac30 r: 0x7f33fdacacb0 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdbb40b8 r: 0x7f33fdbb4138 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaa8f70 r: 0x7f33fdaa8ff0 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb70738 r: 0x7f33fdb707b8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdc7f490 r: 0x7f33fdc7f510 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20317]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20317]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb70738 r: 0x7f33fdb707b8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20314]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdbb40b8 r: 0x7f33fdbb4138 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20313]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdacac30 r: 0x7f33fdacacb0 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda01dc0 r: 0x7f33fda01e40 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd960380 r: 0x7f33fd960400 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdacac30 r: 0x7f33fdacacb0 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20308]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdaa8f70 r: 0x7f33fdaa8ff0 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20307]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd93e6c0 r: 0x7f33fd93e740 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20305]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb70738 r: 0x7f33fdb707b8 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20315]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20315]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdb822d0 r: 0x7f33fdb82350 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20316]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20316]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fda25fd8 r: 0x7f33fda26058 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20306]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fdc196f8 r: 0x7f33fdc19778 (-1) Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac Nov 13 18:28:05 sjoprodkama51 /usr/sbin/kamailio[20304]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f33fd9c27a8 r: 0x7f33fd9c2828 (-1) Any thoughts on what would cause this issue? 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.*

4 14

Re: [SR-Users] Parsing Contact Port Field
by Michael Iedema 18 Nov '19

18 Nov '19

> Oops. No, it’s not a bug, it’s just that the URI isn’t the only value present in $ct. > > Try $(ct{nameaddr.uri}{uri.host}) Yup, that fixed it. Thanks again! I have another question about how I’m applying these to some routing logic but I’ll start a new thread for that in a bit.

1 0

http_async_client and HTTP2
by Igor Olhovskiy 18 Nov '19

18 Nov '19

HI! Seems to be, http_async client is not compatible with http2 servers. I'm having like kamailio_1 | 15(20) INFO: http_async_client [http_multi.c:238]: debug_cb(): [cURL] Connection #0 to host relay-api.pbxservice.com left intact kamailio_1 | 15(20) ERROR: <core> [core/parser/parse_fline.c:264]: parse_first_line(): parse_first_line: bad message (offset: 11) kamailio_1 | 15(20) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: parse_msg: message=<HTTP/2 404 kamailio_1 | date: Thu, 14 Nov 2019 18:31:34 GMT .... kamailio_1 | 15(20) ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [(null)] kamailio_1 | 15(20) ERROR: <core> [core/parser/msg_parser.c:1274]: get_body(): failed to parse to end of headers But plain http_client worked good (not async for sure) kamailio 5.3.0 -- Best regards, Igor

3 3

Problem with URI transformations
by Duarte Rocha 18 Nov '19

18 Nov '19

Greetings, I'm trying to parse some URI info on Kamailio but i'm having some troubles the URI transformations. Here i have two examples of URIS from which i'm trying to extract username(with user parameters included) and URI Parameters : - sip:123456789;test=param@1.1.1.1 - sip:123456789;test=param@1.1.1.1;user=phone In order to test this i made the following code : $var(URI) = "sip:123456789;test=param@1.1.1.1"; xerr("DEBUG 1 : URI $var(URI)"); $var(User) = $(var(URI){uri.user}); $var(Parameters) = $(var(URI){uri.params}); xerr("DEBUG 1 : User = $var(User)"); xerr("DEBUG 1 : Parameters = $var(Parameters)"); $var(URI) = "sip:123456789;test=param@1.1.1.1;user=phone"; xerr("DEBUG 2 : URI $var(URI)"); ; $var(User) = $(var(URI){uri.user}); $var(Parameters) = $(var(URI){uri.params}); xerr("DEBUG 2 : User = $var(User)"); xerr("DEBUG 2 : Parameters = $var(Parameters)"); The result is the following : DEBUG 1 : URI sip:123456789;test=param@1.1.1.1 DEBUG 1 : User = 123456789;test=param DEBUG 1 : Parameters = DEBUG 2 : URI sip:123456789;test=param@1.1.1.1;user=phone DEBUG 2 : User = 123456789 DEBUG 2 : Parameters = user=phone If the URI has parameters, the User parameters won't be included in the User part. Is this a bug or is it working as intended? I'm running Kamailio 5.2.0 . Thank you for your time. Best Regards, Duarte Rocha

3 6

Parsing Contact Port Field
by Michael Iedema 18 Nov '19

18 Nov '19

Hello everyone, I have a potentially silly beginners question: how can I parse the contact port field and act on it in my routing logic? I know that the $ct variable contains the entire contact header and I can print it in an xlog() call. However, I’d like to do something like the following in my routing logic: . . . SIP CONTENT Contact: <sip:someaccount@192.168.86.104:5062>;expires=1800 . . . CONFIG LOGIC #!define PORT_SERVICE1 5061 #!define PORT_SERVICE2 5062 route { if ( src_port == PORT_SERVICE1 ) { xlog(“L_INFO”, “Received $rm from SERVICE1\n”); } else if ( src_port == PORT_SERVICE2 ) { xlog(“L_INFO”, “Received $rm from SERVICE2\n”); } } I realize that src_port is not the correct value to compare against. I want to compare against the originating contact’s port value. How can I extract the port field from $ct? Many thanks in advance and apologies for the beginners question. I’ve googled for what I think I’m trying to do without any real results on functions or tokenizers, etc. I’m using Kamailio 5.3.0. Regards, -Michael

3 3

Re: [SR-Users] Saving REGISTER status in kamailio database while REGSITER packets are forwarded.
by Voip support 18 Nov '19

18 Nov '19

I am using kamailio 5.3. Ovidiu Sas, i will try this tomorrow today is bit late. Maybe it could work. David Villasmil , i know i can use SQLOPS but i was thinking of easier method of doing this. By successful REGISTER i mean save only REGISTER attempt that authenticated correctly at SIP server and in 200 OK a binding was returned. Same if the binding is later removed i would like remove it from database. I need this because when i run REGISTER over kamailio to destination SIP server i see all register from same IP. I need to be able to check what was the real source IP of client REGISTER. Regards, Tomasz pt., 15 lis 2019 o 00:16 Mike from ApoloCore <mike(a)apolocore.com> napisał(a): > I am using kamailio 5.3. > > Ovidiu Sas, i will try this tomorrow today is bit late. Maybe it could > work. > > David Villasmil , i know i can use SQLOPS but i was thinking of easier > method of doing this. > By successful REGISTER i mean save only REGISTER attempt that > authenticated correctly at SIP server and in 200 OK a binding was returned. > Same if the binding is later removed i would like remove it from database. > I need this because when i run REGISTER over kamailio to destination SIP > server i see all register from same IP. > I need to be able to check what was the real source IP of client REGISTER. > > Regards, > Tomasz > > > czw., 14 lis 2019 o 23:33 Ovidiu Sas <osas(a)voipembedded.com> napisał(a): > >> Try to use save() when you process the 200 ok reply for REGISTER in >> the reply route. >> >> Regards, >> Ovidiu Sas >> >> On Thu, Nov 14, 2019 at 3:40 PM Voip support <voipexpert0(a)gmail.com> >> wrote: >> > >> > I setup kamailio to forward REGISTER packets using dispatcher to two >> servers main and backup. >> > >> > The routing logic is quite simple i use the dispatcher probing >> mechanism to detect if my main dispatcher set id (one server) is active or >> inactive once it detect a failure all packets are sent to secondary SIP >> server to achieve High Availability. >> > >> > I am looking for module or a way to save into kamailio database client >> information such as IP address, register username (from FROM header), >> digest username (authorization username), call-id for successful >> registration. >> > >> > I tried to use registrar module but once i used function >> save("location") the client was registered on kamailio and packets was not >> forwarded to main/secondary SIP server (like dispatcher stopped working, >> the destination did not override). >> > >> > REGISTER is sent to SIP URI of kamailio. >> > >> > Please let me know if you have any idea how to make this data update in >> database (insert an entry on fresh successfull REGISTER, delete on expired >> or removed binding). >> > >> > Best regards, >> > Tomasz >> > >> > _______________________________________________ >> > Kamailio (SER) - Users Mailing List >> > sr-users(a)lists.kamailio.org >> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> >> >> -- >> VoIP Embedded, Inc. >> http://www.voipembedded.com >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >

3 2

Saving REGISTER status in kamailio database while REGSITER packets are forwarded.
by Voip support 15 Nov '19

15 Nov '19

I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup. The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability. I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration. I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override). REGISTER is sent to SIP URI of kamailio. Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding). Best regards, Tomasz

5 5

dispatcher, pvar_hash and multiple kamailio instances
by Barry Flanagan 15 Nov '19

15 Nov '19

Hi, I have multiple Kamailio instances using dispatcher using alg “7” - hash over the content of PVs string, both using the same dispatcher list. Is it reasonable to expect both Kamailio, given the same hash_pvar, to select the same host from the same set? Looking at the source I do not see any reason why not, but I am getting different results from the two Kamailio servers. The only difference between them is different minor version numbers - 4.3.4 and 4.3.7 I want to ensure that calls with the same hash_pvar value go to the same backend no matter which Kamailio processes the request. Thanks! -Barry Flanagan

3 2

Re: [SR-Users] Question on Database Version Table
by JR Richardson 15 Nov '19

15 Nov '19

Yep version_table Set the name of the table holding the table version. Useful if the proxy is sharing a database within a project and during upgrades. Default value is “version”. Example of usage: version_table="version44" That's what I was looking for, perfect! Yes, I added accountcode and notes to my table for internal use, was just making notes on columns I need on the new version upgrade. Thanks. JR On Tue, Jun 18, 2019 at 2:17 PM Daniel-Constantin Mierla <miconda(a)gmail.com> wrote: > > Hello, > > like Alex said, you can have two version tables, one for each versions > of kamailio you play with and use in config the core parameter to set > the name of that table. > > I am actually writing to say that address table never had accountcode > and notes columns. Likely they were added in your deployment for other > purposes or either the default column names were changed. The default > column names are listed at: > > - > https://kamailio.org/docs/db-tables/kamailio-db-5.2.x.html#gen-db-address > > These were the same for rather long time, iirc the recent version number > changed mainly due to with modifications done to the size, not due to > new columns. > > Cheers, > Daniel > > On 18.06.19 20:50, JR Richardson wrote: > > Hey All, > > > > I'm doing some upgrades and noticed database table version numbers > > have increased. > > > > database table adjustments: > > | address | production ver 3 | upgrade 5.2 ver 6 | need to add > > accountcode and notes column > > | dispatcher | production ver 3 | upgrade 5.2 ver 4 | need to add attr column > > | trusted | production ver 5 | upgrade 5.2 ver 6 | need to add > > ruri_pattern and priority column > > > > I run mysql master/slave so I'm concerned about the master database > > not having the correct version numbers or can I just update the > > version number in the table when I do the upgrade of the kamailio > > versions? > > > > Thanks. > > > > JR

4 6

Processes blocking - troubleshooting slow actions
by Julien Chavanton 15 Nov '19

15 Nov '19

I am troubleshooting intermittent latency on a server, several processes will report slow action at the same time every now and then, something odd it that some of the actions are most likely not using any mutexes, I can not imagine how they can end up blocking unless the process is actually suspended by the OS, however the CPU usage and load average is quite low on this server. Is there any reason why assigning to a PKG var could be delayed 3 seconds. 2019-11-13T21:58:04.018631614Z 23(42) WARNING: <core> [core/action.c:1586]: run_actions(): alert - action [corefunc (16)] cfg [/etc/kamailio/kamailio.cfg:115] took too long [2579486 us] $var(reply) = 0; // I wonder how this can endup blocking ? 2019-11-13T21:58:04.018748710Z 42(61) WARNING: <core> [core/action.c:1586]: run_actions(): alert - action [corefunc (16)] cfg [/etc/kamailio/kamailio.cfg:221] took too long [2222010 us] } // Samething here, simply exiting a scope 2019-11-13T21:58:04.015675095Z 11(30) WARNING: <core> [core/action.c:1586]: run_actions(): alert - action [t_relay_cancel (24)] cfg [/etc/kamailio/kamailio.cfg:86] took too long [2588818 us] } if (!t_relay_cancel()) { // Indeed a t_relay_cancel 2019-11-13T21:58:04.018647988Z 26(45) WARNING: <core> [core/action.c:1586]: run_actions(): alert - action [t_relay (24)] cfg [/etc/kamailio/kamailio.cfg:289] took too long [2739366 us] t_relay(); // Indeed a t_relay 2019-11-13T21:58:04.018651243Z 15(34) WARNING: <core> [core/action.c:1586]: run_actions(): alert - action [sl_send_reply (26)] cfg [/etc/kamailio/kamailio.cfg:112] took too long [2587812 us] sl_send_reply("100", "Trying"); // Indeed a sl_send_reply Not sure which mailing list is best for this question Regards Julien

2 4

kamailio 5.2.4 unable to load db_mysql.so
by Rupesh Kumar 15 Nov '19

15 Nov '19

I am trying to compile and load kamailio 5.2.4 on centos 7.5. I am getting below errors whenever I start kamailio . I have the latest openssl and openssl-devel packages installed on my centos . Not sure what other dependencies . Not starting Kamailio SIP Server: invalid configuration fil[FAILED] [FAILED]0(23235) ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/local/lib64/kamailio/modules/db_mysql.so>: /usr/local/lib64/kamailio/modules/db_mysql.so: undefined symbol: SSL_get_error 0(23235) CRITICAL: <core> [core/cfg.y:3508]: yyerror_at(): parse error in config file //usr/local/etc/kamailio/kamailio.cfg, line 229, column 12-24: failed to load module ERROR: bad config file (1 errors) 0(23235) INFO: <core[FAILED]sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized [FAILED]

1 1

Next online devel meeting - irc/video conference - Thursday, Nov 14, 15:00UTC
by Daniel-Constantin Mierla 14 Nov '19

14 Nov '19

Hello, on Thursday and Friday this week over a dozen of Kamailio developers will be in Dusseldorf for the annual coding meeting, so we thought of doing an online meeting via some video conferencing bridge, with IRC as a backup chatting channel, to allow also other community members to join remotely and discuss the development plans for short/medium term. It is more or less what we used to do during the past IRC devel meetings, but to make the discussions go faster and shorter the meeting, so people in Dusseldorf spend more time coding, this time we will try video conferencing. Very likely we will use Jitsi Meet, so anyone that wants to join should be prepared with a WebRTC capable web browser (all major ones support it) -- link and details how to join will be provided short before the meeting starts, right now the plan is to do it on Thursday, Nov 14, at 15:00UTC/London (16:00Berlin-Paris, 10:00New York). If someone wants to address questions but doesn't have the possibility to join the video conf bridge, then join the IRC #kamailio channel on freenode.net and post your question there during the meeting. The IRC channel will be monitored and used for text chatting whenever needed. 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

2 3

Kamailio v5.3.1 Released
by Daniel-Constantin Mierla 14 Nov '19

14 Nov '19

Hello, Kamailio SIP Server v5.3.1 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.1. 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.1. For more details about version 5.3.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/11/kamailio-v5-3-1-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! 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 0

Releasing Kamailio v5.3.1
by Daniel-Constantin Mierla 14 Nov '19

14 Nov '19

Hello, the plan right now is to release v5.3.1 during the next Kamailio Developers Meeting, if we succeed to coordinate on site, therefore expect it to happen next week during Nov 14-15. Besides just doing this specific release, to goal is to try to build a more automatic process for releases, document how is done, etc... updates about the results will follow after the event. Anyhow, for now the usual the pre-release notice: if anyone is aware of some issue that is not yet reported, do it asap in order to give it a chance to be analyzed and fixed. 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

event_route[core:msg-received] native vs kemi/lua
by GG GG 14 Nov '19

14 Nov '19

Hi! I just made a simple test performance between native script and kemi/lua with the event_route[core:msg-received] callback. # lua script children=1 cpu.process=100% function ksr_core_received() exit; end # native script children=1 cpu.process=70% event_route[core:msg-received] { exit; } # tested with udp 5060, 1000 Mbits/sec iperf -c 127.0.0.1 -p 5060 -u -b1000m I don't know if it's normal and what we should expect from kemi, but I would like to share this with you. Maybe someone could confirm the performance difference. Have a good day !

2 8

kemi framework design
by GG GG 12 Nov '19

12 Nov '19

Hi, looking at the documentation and the code, I couldn't answer myself. - does kamailio use one lua interpreter per fork ? - about the safety, I just made a bad lua module in c, to force a segmentation fault in the module. I would expect kamailio to protect itself from the crash, but kamailio restarted.

2 1

Change SDP Session Name
by Alvaro Araos 11 Nov '19

11 Nov '19

Hi everyone, Exists some way to change the SDP Session Name value (s=)??? Saludos, Alvaro Araos

3 2

Change SDP Session Name
by Alvaro Araos 11 Nov '19

11 Nov '19

Hi everyone, Exists some way to change the SDP Session Name value (s=)??? Saludos, Alvaro Araos

1 0

Change SDP Session Name
by Alvaro Araos 11 Nov '19

11 Nov '19

Hi everyone, Exists some way to change the SDP Session Name value (s=)??? Saludos, Alvaro Araos

1 0

Kamailio in cloud environments
by Alejandro Recarey 11 Nov '19

11 Nov '19

Hi, I am trying to get kamailio working cloud provider, autoscaling them behind a TCP load balancer. Is there a way for kamailio to discover its Public IP at startup? Or do people generally program their own startup scripts that modify the kamailio config file before starting it? Is there any gotchas you have hit while configuring this setup? Thank you! Alex

8 13

uac_replace_from(uri) alters display name
by Sergiu Pojoga 10 Nov '19

10 Nov '19

Hi ppl, Need to replace origination carrier's domain with my own, so I do: branch_route[MANAGE_PSTN_IN_BRANCH] { uac_replace_from("sip:$fU@mydomain.net"); } The dialog-forming INVITE is relayed properly with ONLY the domain part being replaced. However, subsequent messages such as ACK and BYE have the From DISPLAY NAME (_uac_fdp) stripped off. Not that it affects real functionality in any known way (CLID is still good for callee), but curious if this is intentional or not, as *uac_replace_from(uri)* clearly states that: "*Replace in FROM header the URI part without altering the display name*" # kamcmd dlg.list variables: { { _uac_fdpnew: } { _uac_fdp: "JOHN DOE" } { _uac_funew: sip:18661112222@mydomain.net } { _uac_fu: sip:18661112222@carrierdomain.net } Thanks!

2 4

OPTIONS request not authenticating
by Gustavo A. M. 10 Nov '19

10 Nov '19

Greetings, I'm trying to configure kamailio to get OPTIONS response, but it does not working properly. After a successful REGISTER, I send OPTIONS first time, get Proxy- Authenticate header to calculate Proxy-Authorization, and resend OPTIONS with Proxy-Authenticate header, but server follows answering with a 407 response, apparently ignoring Proxy-Authenticate. Note that same password is used in REGISTER request, and first time REGISTER response with a 401, not a 407 response. I think messages sent from client are right, and problem is on the server configuration. Follow messages and kamailio.cfg. Thanks in advance, Gustavo Adolfo Moennich OPTIONS sip:6000@kamailio.memorea.com SIP/2.0 Call-ID: A6DB9DCAA18049E784034FB6F5F95680 Contact: <sip:6000@kamailio.memorea.com> Content-Length: 0 CSeq: 0 OPTIONS Expires: 20 From: "Bob" <sip:6000@kamailio.memorea.com>;tag=0B3D2156FF9E46DAAD7FC43 B62C9E2FC Max-Forwards: 70 To: "Bob" <sip:6000@kamailio.memorea.com> User-Agent: Memorea 1.0 (SIP 2.0) Build 1.1.1.0, Windows x64 Build 6.1.7601 Via: SIP/2.0/UDP 192.168.122.21:5060;rport=58905 SIP/2.0 407 Proxy Authentication Required Call-ID: A6DB9DCAA18049E784034FB6F5F95680 CSeq: 0 OPTIONS From: "Bob" <sip:6000@kamailio.memorea.com>;tag=0B3D2156FF9E46DAAD7FC43 B62C9E2FC To: "Bob" <sip:6000@kamailio.memorea.com>;tag=9dd61ff61e802d8e2bef5f146 21ef3c2.467d Via: SIP/2.0/UDP 192.168.122.21:5060;rport=58905;received=192.168.122.12 Proxy-Authenticate: Digest realm="kamailio.memorea.com", nonce="Xcc1wV3HNJXdfUDchNlEUkT6kHCtqBAn" Server: kamailio (5.2.1 (x86_64/linux)) Content-Length: 0 OPTIONS sip:6000@kamailio.memorea.com SIP/2.0 Call-ID: A6DB9DCAA18049E784034FB6F5F95680 Contact: <sip:6000@kamailio.memorea.com> Content-Length: 0 CSeq: 1 OPTIONS Expires: 20 From: "Bob" <sip:6000@kamailio.memorea.com>;tag=0B3D2156FF9E46DAAD7FC43 B62C9E2FC Max-Forwards: 70 Proxy-Authorization: Digest uri=sip:6000@kamailio.memorea.com,nonce="Xc c1wV3HNJXdfUDchNlEUkT6kHCtqBAn",realm="kamailio.memorea.com",response=" 5bcd184eea53284f3ec548c2412ce36a",username=6000 To: "Bob" <sip:6000@kamailio.memorea.com> User-Agent: Memorea 1.0 (SIP 2.0) Build 1.1.1.0, Windows x64 Build 6.1.7601 Via: SIP/2.0/UDP 192.168.122.21:5060;rport=58905 SIP/2.0 407 Proxy Authentication Required Call-ID: A6DB9DCAA18049E784034FB6F5F95680 CSeq: 1 OPTIONS From: "Bob" <sip:6000@kamailio.memorea.com>;tag=0B3D2156FF9E46DAAD7FC43 B62C9E2FC To: "Bob" <sip:6000@kamailio.memorea.com>;tag=9dd61ff61e802d8e2bef5f146 21ef3c2.32de Via: SIP/2.0/UDP 192.168.122.21:5060;received=192.168.122.12;rport=58905 Proxy-Authenticate: Digest realm="kamailio.memorea.com", nonce="Xcc1xl3HNJqRobJFuZggPSGvNdtp+GnP" Server: kamailio (5.2.1 (x86_64/linux)) Content-Length: 0 kamailio.cfg content's: #!KAMAILIO #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB # # 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.or g> # # 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:temp@database.memorea.com/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 */ children=8 /* uncomment the next line to disable TCP (default on) */ # disable_tcp=yes /* 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 #!ifdef WITH_TLS enable_tls=yes #!endif /* 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 ####### 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!=$si) { 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 (uri==$ru) { if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { options_reply(); } } 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 == $ru) { # 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==$fu) { # 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 (is_method("OPTIONS") || from_uri==$fu) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("OPTIONS|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!=$fu && uri!=$ru) { sl_send_reply("403","Not relaying"); exit; } #!else # authentication not enabled - do not relay at all to foreign networks if(uri!=$ru) { 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==$ru) 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!=$fu) { 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 }

2 1

dispatch REGISTER over TLS
by sthustfo 10 Nov '19

10 Nov '19

I have a basic setup where kamailio receives SIP over websocket (no WSS) and forwards to SIP server over TLS. I have enabled TLS in kamailio.cfg and added dispatcher node as sips:SIP_SERVER:5061 and transport=tls. +----+-------+------------------------+-------+----------+---------------+----------------+ | id | setid | destination | flags | priority | attrs | description | +----+-------+------------------------+-------+----------+---------------+----------------+ | 4 | 1 | sips:10.0.0.100:5061 | 0 | 0 | transport=tls | SIP SERVER | +----+-------+------------------------+-------+----------+---------------+----------------+ Now when REGISTER is received over websocket, kamailio is responding with error code 500 and phrase "500 I'm terribly sorry, server error occurred (7/SL)". And on the console I see the following error messages. 12(33858) DEBUG: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: f1ecf7bcb659b07fe81e332e100044e5 12(33858) ERROR: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} tm [ut.h:315]: uri2dst2(): no corresponding socket found for "10.0.0.100" af 2 (tls: 10.0.0.100:5061) 12(33858) ERROR: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} tm [t_fwd.c:467]: prepare_new_uac(): can't fwd to af 2, proto 3 (no corresponding listening socket) 12(33858) ERROR: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} tm [t_fwd.c:1735]: t_forward_nonack(): failure to add branches 12(33858) DEBUG: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} tm [t_funcs.c:334]: t_relay_to(): t_forward_nonack returned error -7 (-7) 12(33858) DEBUG: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} tm [t_funcs.c:352]: t_relay_to(): -7 error reply generation delayed 12(33858) exec: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio.cfg] l=587 a=24 n=sl_reply_error 12(33858) DEBUG: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} <core> [core/msg_translator.c:162]: check_via_address(): (10.0.0.14, hsvmphm3ps12.invalid, 0) 12(33858) DEBUG: {1 2521 REGISTER o9q7ujqgin33qgp00abijv} websocket [ws_conn.c:452]: wsconn_get(): wsconn_get for id [3] *tls.cfg contents* [client:default] method = TLSv1 verify_certificate = yes require_certificate = yes private_key = /home/test/kamailio/internal.key certificate = /home/test/kamailio/internal.crt ca_list = /home/test/kamailio/ca_list.pem Any reason why this error is seen? Any inputs appreciated. Thanks.

4 20

Re: [SR-Users] _w_t_relay_to(): t_forward_noack failed when forwarding call
by Konstantinos Merentitis 08 Nov '19

08 Nov '19

I added $du=$null; before route(RELAY) as you suggested but I get the same results: Nov 8 12:40:22 spock /usr/sbin/kamailio[21826]: ERROR: <script>: transaction canceled Nov 8 12:40:22 spock /usr/sbin/kamailio[21826]: ERROR: <script>: #012 RDNIS = sip:297@192.168.1.134 Nov 8 12:40:22 spock /usr/sbin/kamailio[21826]: ERROR: <script>: =============forwarding to voicemail1, RDNIS: sip:297@192.168.1.134 =========== Nov 8 12:40:22 spock /usr/sbin/kamailio[21826]: ERROR: tm [tm.c:1679]: _w_t_relay_to(): t_forward_noack failed Nov 8 12:40:22 spock /usr/sbin/kamailio[21826]: ERROR: sl [sl_funcs.c:392]: sl_reply_error(): stateless error reply used: transaction canceled (487/SL) Regards, Konstantinos > On Fri Nov 8 10:24:06 CET 2019 Daniel Tryba wrote: > >> On Thu, Nov 07, 2019 at 04:53:43PM +0200, Konstantinos Merentitis wrote: >> >> I tried to modify the failure route in order to also forward not answered (failed?) calls to asterisk mailbox but i get the following error and the call is never forwarded: >> > You appear to do the same thing I do, except setting $du to null. If the user is REGISTERed $du will be set to their endpoint, changing $ru will have no effect on routing. So add $du=$null; in the TOVOICEMAIL route before route(RELAY) and see what happens. >

3 4

_w_t_relay_to(): t_forward_noack failed when forwarding call
by Konstantinos Merentitis 08 Nov '19

08 Nov '19

I would like to forward all incoming calls that are not answered from kamailio, to my asterisk voicemail server. - I have not setup any Realtime Integration. I am using the "Redirected Dialed Number Information Service" header and calling "554(a)192.168.1.134" which is my voicemail server. Forwarding succeeds when the subscriber is not registered to kamailio: Nov 7 16:19:45 spock /usr/sbin/kamailio[17606]: ERROR: <script>: =============User sip:6297@192.168.1.131 not found here, going to voicemail============= Nov 7 16:19:45 spock /usr/sbin/kamailio[17606]: ERROR: <script>: #012 RDNIS = sip:297@192.168.1.134 Nov 7 16:19:45 spock /usr/sbin/kamailio[17606]: ERROR: <script>: =============forwarding to voicemail1, RDNIS: sip:297@192.168.1.134 =========== I tried to modify the failure route in order to also forward not answered (failed?) calls to asterisk mailbox but i get the following error and the call is never forwarded: Nov 7 16:19:25 spock /usr/sbin/kamailio[17609]: ERROR: <script>: transaction canceled Nov 7 16:19:25 spock /usr/sbin/kamailio[17609]: ERROR: <script>: #012 RDNIS = sip:297@192.168.1.134 Nov 7 16:19:25 spock /usr/sbin/kamailio[17609]: ERROR: <script>: =============forwarding to voicemail1, RDNIS: sip:297@192.168.1.134 =========== Nov 7 16:19:25 spock /usr/sbin/kamailio[17609]: ERROR: tm [tm.c:1679]: _w_t_relay_to(): t_forward_noack failed Nov 7 16:19:25 spock /usr/sbin/kamailio[17609]: ERROR: sl [sl_funcs.c:392]: sl_reply_error(): stateless error reply used: transaction canceled (487/SL) failure and voicemail routes are slightly modified from the default config: 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")) { xlog("=============User $ru not found here, going to voicemail=============\n"); $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; } 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")) { $var(RDNIS)=$di; xlog("\n RDNIS = $var(RDNIS) \n"); if($avp(oexten)==$null) return; # $ru = "sip:" + $avp(oexten) + "@" + $sel(cfg_get.voicemail.srv_ip + ";transport=udp") # + ":" + $sel(cfg_get.voicemail.srv_port); xlog("=============forwarding to voicemail1, RDNIS: $di =========== "); $ru = "sip:554@192.168.1.134:5060"; } else { if($rU==$null) return; # $ru = "sip:" + $rU + "@" + $sel(cfg_get.voicemail.srv_ip + ";transport=udp") # + ":" + $sel(cfg_get.voicemail.srv_port); xlog("=============forwarding to voicemail2, RDNIS: $di =========== "); $ru = "sip:554@192.168.1.134:5060"; } route(RELAY); exit; #!endif return; } # Manage failure routing cases failure_route[MANAGE_FAILURE] { route(NATMANAGE); if (t_is_canceled()) { #modified here xlog("transaction canceled\n"); route(TOVOICEMAIL); #exit; #/modified } #!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; xlog("============= Route failure, forwarding to voicemail ============="); route(TOVOICEMAIL); exit; } #!endif }

2 1

How to read some data inside the INVITE ..
by Laura 07 Nov '19

07 Nov '19

Dears.. how is possibile to read that data 9052562462354464 inside the first INVITE message === Example === U 2019/11/07 14:46:59.320936 192.168.1.1:5060 -> 192.168.1.242:5060 INVITE sip:9052562462354464@192.168.1.242 SIP/2.0. Record-Route: <sip:192.168.1.1;lr;ftag=105854496;did=24e.e751;vst=AAAAAAAAAwQAAAAAAAAAAAAAAAAADQIAAwEDAAAHDwAGBAg1MDYw;nat=yes>. Max-Forwards: 66. Via: SIP/2.0/UDP 51.254.158.40:5060;branch=z9hG4bK501c.87a8e402c8f1cf93192ddd8e6744da57.1. From: "38617774738" <sip:38617774738@10.1.1.1>;tag=105854496. To: <sip:562462354464@192.168.1.242>. Call-ID: 1573138018-1602381967(a)10.1.1.182. CSeq: 20215490 INVITE ..... ETC ETC... Thanks to all

4 4

Re-invite after RTPengine pacemaker switching?
by Жан Базаров 07 Nov '19

07 Nov '19

I need to send re-invite after pacemaker fails over on new rtpengine server. Because new rtpengine dont participate in DTLS handshake and i hear nothing, but silence. I think, may me its would be work. Do you have any idea on this issue?

3 5

multihomed kamailio and sip-reinvites SRTP to RTP
by Karsten Horsmann 07 Nov '19

07 Nov '19

Hello Mailinglist, i try to figure out, how to solve RE-INVITES and SRTP: i have an kamailio route names route[MEDIAPROXY] that i used to controll rtpengine in an private and public ip setup. This works fine for me now. It use the permission module and the adress table to figure out $var(mediagroup) = allow_address_group($Ri, 0); received from internal or external ip. The idea is from SBC-OS chamless stolen, so thanks for that. So fare so good. I adapted SRTP also to this. But on RE-INVITES it stops handling SRTP correctly to the encryption upstream. And i am sure, its my fault. But i have no clue how to detect that correctly. Any hints where i can read more about an correct handling on this? Here my main-config file / kamailio 5.3.x and rtpengine. https://gist.github.com/khorsmann/02bd98a628a190caee68fc3d876a3448 -- Mit freundlichen Grüßen *Karsten Horsmann*

2 2

Re: [SR-Users] Group module
by Daniel Tryba 07 Nov '19

07 Nov '19

On Wed, Nov 06, 2019 at 07:15:42PM +0100, Igor Olhovskiy wrote: > > Hm... Maybe there is other module to achieve such functions? > Best if it would be with cache :) > But if no - regex also fine. But if it works it works! I don't think there is a specific module to do this but it is easy to implement yourself. What I don't like personally about your solution is the use of the permission tables, you need atleast 1 per user (unless users have the same ip). Personally I do this by direct database queries in usr_preferences on INVITEs and REGISTERs. You could use any database (depending on how you store the ACL) and cache it in a htable. My solution is mysql specific (inet_aton) and forces users to have atleast 1 CIDR notated subnet: if(!avp_db_query("select value from usr_preferences where username='$au' and attribute='acl' and inet_aton(substring_index(value,'/',1))&(1 << 32) - 1 & ~((1 << (32 - substring_index(value,'/',-1))) - 1)=inet_aton('$si')&(1 << 32) - 1 & ~((1 << (32 - substring_index(value,'/',-1))) - 1)")) { t_reply("404","Go away"); exit; }

3 2

MongoDB findone(). Is projection supported?
by Lars Olsson 06 Nov '19

06 Nov '19

Hi, I am using NDB_MONGODB to ask some questions to a database. My database structure is pretty heavy, so I like to return as little data as required to Kamailio. I have tried the following MongoDB syntax for projection to include only given (my_field) column in the response. mongodb_find_one("srv_name", "database", "collection", "{ \"user_id\" : \"$var(user_id)\" }, { \"my_field\" : 1}", "mgr1") I always get full DB entry back. Is this supported? The same string works OK in the vanilla mongo client. How can I limit the result? Thanks Lars

2 3

Group module
by Igor Olhovskiy 06 Nov '19

06 Nov '19

Hi! I'm trying to solve quite simple task and want to solve it as simple as possible. Idea is to have restriction to allow register certain username/domain only from certain subnets. So, I decided to use group and permissions modules. But stuck on group one. Code is fairly simple modparam("group", "db_url", DBURL) modparam("group", "use_domain", 1) ... if (get_user_group("From", "$avp(user_groups)")) { xlog("$fu from $si:$sp is matched group $avp(user_groups)\n"); if (allow_source_address("$avp(user_groups)")) { ...allow furter } } else { xlog("$fu from $si:$sp is not matched any groups\n"); } grp table is looks like kamctl db exec 'select * from grp' +----+-------------+-------------------+-----+---------------------+ | id | username | domain | grp | last_modified | +----+-------------+-------------------+-----+---------------------+ | 1 | 61388140395 | sip.localhost.net | 5 | 2000-01-01 00:00:01 | +----+-------------+-------------------+-----+---------------------+ But actual line of debug in logs saying this kamailio_1 | 10(18) exec: {1 1 REGISTER 4oQTNaaVlEWQC2VMK6YAKg..} *** cfgtrace:request_route=[PERMISSIONS] c=[/etc/kamailio/kamailio.cfg] l=720 a=26 n=get_user_group kamailio_1 | 10(18) DEBUG: {1 1 REGISTER 4oQTNaaVlEWQC2VMK6YAKg..} group [re_group.c:188]: get_user_group(): getting groups for <sip:61388140395@sip.localhost.net> kamailio_1 | 10(18) exec: {1 1 REGISTER 4oQTNaaVlEWQC2VMK6YAKg..} *** cfgtrace:request_route=[PERMISSIONS] c=[/etc/kamailio/kamailio.cfg] l=727 a=25 n=xlog kamailio_1 | 10(18) ERROR: {1 1 REGISTER 4oQTNaaVlEWQC2VMK6YAKg..} <script>: sip:61388140395@sip.localhost.net;transport=UDP from 172.21.0.1:56787 is not matched any groups What am I missing here? Or module is too old? Thanks!

1 0

RFC: default config with jsonrpc over http instead of xmlrpc
by Daniel-Constantin Mierla 06 Nov '19

06 Nov '19

Hello, I think it was discussed during past IRC meetings or at some events across the world, with jsonrpc being these days more popular than xmlrpc, specially due to easier integration with web based apps, I am considering to replace the example of using xmlrpc over http(s) with jsonrpc in the default configuration file. It is not enabled by default for xmlrpc (requiring to define WITH_XMLRPC), so it will stay also as a define option for jsonrpc. The jsonrpcs module is already loaded for kamctl, it will require the xhttp module to be added. As for those looking for xmlrpc in the future, there is another example kamailio cfg which has the option with it: misc/examples/pkg/kamailio-oob.cfg Any other opinions? 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

4 3

$jsonrpl(body) empty or malfunctioned during higher traffic
by Michal Škuta 05 Nov '19

05 Nov '19

Hello, Kamailio community, we are implementing evapi communication to our Kamailio server. We have implemented and tested it on our testing server. Everything was working OK. Now we are testing it on our production servers with a lot more calls and we have some problems here. Every n seconds we are requesting from Kamailio list of all dialogs. And this list of dialogs (from jsonrpc *dlg.list*) is sent to evapi connection. Here is a snippet of our *Kamailio code*: route[CGR_DLG_LIST] { xlog("L_INFO", "XLOG: $ci [CGR_DLG_LIST] Requested dialog list"); # CGRateS connection is still alive, set check to true $sht(cgrconn=>check) = 1; if $sht(cgrconn=>cgr) == $null { sl_send_reply("503","Charging controller unreachable"); exit; } jsonrpc_exec('{"jsonrpc":"2.0","id":1, "method":"dlg.list","params":[]}'); xlog("L_INFO", "XLOG: $ci [CGR_DLG_LIST] Test1: $jsonrpl(body)"); evapi_relay("{\"event\":\"CGR_DLG_LIST_REPLY\", \"jsonrpl_body\":$jsonrpl(body)}"); } During a higher number of calls Kamailio is generating ERROR messages from evapi module. Here is the syslog: Oct 30 12:02:15 kam-prod /opt/ipgate/kamailio/sbin/kamailio[19512]: INFO: <script>: XLOG: 123 [CGR_DLG_LIST] Requested dialog list Oct 30 12:02:15 kam-prod /opt/ipgate/kamailio/sbin/kamailio[19512]: INFO: <script>: Oct 30 12:02:15 kam-prod /opt/ipgate/kamailio/sbin/kamailio[19512]: DEBUG: evapi [evapi_dispatch.c:740]: _evapi_relay(): relaying event data [ Oct 30 12:02:15 kam-prod /opt/ipgate/kamailio/sbin/kamailio[19512]: ERROR: evapi [evapi_dispatch.c:764]: _evapi_relay(): cannot serialize event Oct 30 12:02:15 kam-prod /opt/ipgate/kamailio/sbin/kamailio[19512]: ERROR: evapi [evapi_mod.c:265]: w_evapi_relay(): failed to relay event: *We are expecting something like this when nobody is calling* Oct 30 14:12:22 kam-test /opt/ipgate/kamailio/sbin/kamailio[32090]: INFO: <script>: XLOG: 123 [CGR_DLG_LIST] Requested dialog list Oct 30 14:12:22 kam-test /opt/ipgate/kamailio/sbin/kamailio[32090]: INFO: <script>: XLOG: 123 [CGR_DLG_LIST] Test1: { #011"jsonrpc":#011"2.0", #011"result":#011[], #011"id":#0111 } Oct 30 14:12:22 kam-test /opt/ipgate/kamailio/sbin/kamailio[32090]: DEBUG: evapi [evapi_dispatch.c:740]: _evapi_relay(): relaying event data [{"event":"CGR_DLG_LIST_REPLY", #011#011#011"jsonrpl_body":{ #011"jsonrpc":#011"2.0", #011"result":#011[], #011"id":#0111 }}] (96) Oct 30 14:12:22 kam-test /opt/ipgate/kamailio/sbin/kamailio[32090]: DEBUG: evapi [evapi_dispatch.c:778]: _evapi_relay(): sending [0x169ff674] [96:{"event":"CGR_DLG_LIST_REPLY", #011#011#011"jsonrpl_body":{ #011"jsonrpc":#011"2.0", #011"result":#011[], #011"id":#0111 }},] (100) Oct 30 14:12:22 kam-test /opt/ipgate/kamailio/sbin/kamailio[32090]: DEBUG: evapi [evapi_dispatch.c:789]: _evapi_relay(): dispatching [0x169ff674] [96:{"event":"CGR_DLG_LIST_REPLY", #011#011#011"jsonrpl_body":{ #011"jsonrpc":#011"2.0", #011"result":#011[], #011"id":#0111 }},] (100) We enabled debug messages for module evapi and are trying to understand where is the problem. To make this work to this state we needed to increase the *pv_buffer* to really big size (2097152). It looks like $jsonrpl(body) is not ready and everything concated with it is not working. Any help or suggestion is welcomed. Sincerely Michal

3 6

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