March 2016 - sr-users - kamailio.org

rare impossibility to send requests to TLS connected peer
by Vasiliy Ganchev 09 Mar '16

09 Mar '16

Hi folk! Have a rare issue with tls connections. Have a server with 100+ active tls connections, that are connected to separate TCP proxy, that listen on port 443. TCP proxy send sip traffic to Kamailio via localhost:5061. In this way all connections in Kamailio are considered from Localhost. Issue scheme: - UA-A (sip-phone, UDP/TCP/TLS) -> call -> sip server (Kamailio+Asterisk based) -> UA-B (sip phone, transport=TLS) - The troubles happened in part of flow to UA-B: --- kamailio script make lookup(location), find AOR for UA-B (here is OK) --- after t_relay, kamailio make branch_route logic and try to send INVITE to tcp socket --- HERE IS the trouble: connection seems to be opened, but Kamailio cannot send INVITE there (say: no open tcp connection found) --- Kamailio try to open tcp connection from itself, TCP proxy refuse it --- as a result - Kamailio answer 477 to Asterisk, and finish processing debug level 3 logs (from the point where Kamailio try to send INVITE in opened connection) Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1463]: _tcpconn_find(): tcpconn_find: 0 port 60286 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_find: ip 127.0.0.1 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1820]: tcp_send(): tcp_send: no open tcp connection found, opening new one Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 127.0.0.1 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 60286, type 3 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1626]: _tcpconn_add_alias_unsafe(): _tcpconn_add_alias_unsafe: alias port 60286 for hash 2646, id 404319 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1626]: _tcpconn_add_alias_unsafe(): _tcpconn_add_alias_unsafe: alias port 60286 for hash 2728, id 404319 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1624]: _tcpconn_add_alias_unsafe(): _tcpconn_add_alias_unsafe: alias already present Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 2646:2728:0, 863 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tls [tls_server.c:184]: tls_complete_init(): Using TLS domain TLSc<default> Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tls [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started Jan 25 14:32:43 /usr/sbin/kamailio[4722]: ERROR: <core> [tcp_main.c:2742]: tcpconn_1st_send(): connect 127.0.0.1:60286 failed (RST) Connection refused Jan 25 14:32:43 /usr/sbin/kamailio[4722]: ERROR: <core> [tcp_main.c:2752]: tcpconn_1st_send(): 127.0.0.1:60286: connect & send for 0xb1d3b7e8 failed: Connection refused (111) Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [tcp_main.c:2947]: tcpconn_chld_put(): tcpconn_chld_put: destroying connection 0xb1d3b7e8 (404319, -1) flags 0060 Jan 25 14:32:43 /usr/sbin/kamailio[4722]: ERROR: tm [../../forward.h:247]: msg_send(): tcp_send failed Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_fwd.c:1591]: t_send_branch(): t_send_branch: send to 127.0.0.1:60286 (3) failed Jan 25 14:32:43 /usr/sbin/kamailio[4722]: WARNING: tm [t_fwd.c:1610]: t_send_branch(): ERROR: t_send_branch: sending request on branch 0 failed Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_funcs.c:358]: t_relay_to(): ERROR:tm:t_relay_to: t_forward_nonack returned error Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_funcs.c:375]: t_relay_to(): -477 error reply generation delayed Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_lookup.c:1526]: t_unref(): t_unref: delayed error reply generation(-477) Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: <core> [parser/msg_parser.c:339]: parse_headers(): parse_headers: flags=ffffffffffffffff Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_reply.c:1670]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_reply.c:728]: _reply_light(): DEBUG: reply sent out. buf=0xb67c000c: SIP/2.0 477 Unfortun..., shmem=0xb1b676cc: SIP/2.0 477 Unfortun Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_funcs.c:156]: put_on_wait(): DEBUG: put on WAIT Jan 25 14:32:43 /usr/sbin/kamailio[4722]: DEBUG: tm [t_reply.c:738]: _reply_light(): DEBUG: _reply_light: finished Additionally want to say, that suddenly we don't have clear reproduce, it happened only on 2 production servers, what are common conditions for issue: - transport=TLS - when issued call is done, I checked with netstat, the connection is alive - the issued device is re-REGISTERed as usual, in kamctl ul show I see registration before/during/after issued call - issue appear only when connection through our custom TCP proxy :443 (to Kamailio it is from 127.0.0.1:5061) - if connection switched to Kamailio 5061 directly - issue never (till now) reproduced - in one of the issued server - I noticed big number of tcp id. Doing kamcmd core.tcp_list, I saw e.g. id: 567852 (usually id numbers are not more than 1000). - if kamailio/device reboot - problem disappear Because of not completely understanding how tcp core is working in kamailio, ask any suggestion, why such could happen. Any idea/hints would be greatly appreciated! kamailio -v version: kamailio 4.2.5 (i386/linux) flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 16:03:38 Jan 12 2016 with gcc 4.3.2 sorry for the long description cheers! -- View this message in context: http://sip-router.1086192.n5.nabble.com/rare-impossibility-to-send-requests… Sent from the Users mailing list archive at Nabble.com.

2 5

Branching v4.4
by Daniel-Constantin Mierla 09 Mar '16

09 Mar '16

Hello, I am considering to branch v4.4 latest on March 10, after that the master branch can be used again for adding new features and fixes will be backported to branch 4.4. If it proves to worth branching earlier, it can be done. As an estimate date for the release of v4.4.0, a good candidate would be one of the days between March 22, 23 or 24. Any other suggestions or comments? Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, March 7-9, 2016 - http://www.asipto.com

1 1

Kamailio 5.0 - Scripted DB Migrations
by Tim Chubb 08 Mar '16

08 Mar '16

As a suggestion for 5.0 having a scripted DB migration system would make upgrading much easier. Something like what Asterisk now uses (Alembic https://pypi.python.org/pypi/alembic) would be ideal, as it works in a DB agnostic manner and you would just have to ensure that there is a driver for the DB you wish to use. That way you would just update the definition script and select the target when you run the updater, and would allow kamailio a greater choice in backing DB's as once the script is written assuming a driver is available for you RDBMS the schema would be successfully ported. This would do away with maintaining separate MySQL, Postgres, Oracle, MSSQL scripts as well. The only issue I can think with a system like this is in the situation where hardcoded SQL strings are in the source and use a RDBMS specific function as that could cause some "fun" in debugging...

3 2

question about dlg_var
by 张顺通 08 Mar '16

08 Mar '16

I want to distingguish 200 OK is for INVITE or reINVITE。 so I do this: request_route { if (is_method("INVITE") && !has_totag()) { $dlg_var(is_init_invite) = "1"; } } onreply_route { xlog("L_INFO","[$rs-$rr][is_init_invite:$dlg_var(is_init_invite)]"); if (is_method("INVITE") && t_check_status("200") && $dlg_var(is_init_invite) == "1") { # do somting $dlg_var(is_init_invite) = "0"; } xlog("L_INFO","[$rs-$rr][is_init_invite:$dlg_var(is_init_invite)]"); } What I confuse is： When I recive 100 Trying LOG is [100 - Trying][is_init_invite:0] [100 - Trying][is_init_invite:1] why is_init_invite is 0?

4 5

Kamailio design that needs one b2bua
by anthony gonzalez 08 Mar '16

08 Mar '16

Hello there, I'm designing and implementing a kamailio solution for sip routing between several softswitch based on prefixes. IIn this setup i will need an b2bua in order to do topology hiding and also to make transparent the call transfer between phones registered in kamailio and softswitches(that doesn't support very well REFER messages). I was searching what solution should I use and I found 3 opensource solutions that for me seems to be acceptable: Sems. Freeswitch. Opensips with module b2bua. Based on your experience and contemplating the stability, performance and support, what is the solution that you advice me ? Thank you for you time. Anthony

2 1

is 't_reply_with_body' currently available in kamailio
by jaflong jaflong 07 Mar '16

07 Mar '16

Hi Is the function 't_reply_with_body' currently available in Kamailio. I am using 4.3.5 I get the error0(7176) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_reply_with_body (params 3) thanks

3 5

Kamailio 5.0 - pseudo variable name cleanup
by Sven Neuhaus 07 Mar '16

07 Mar '16

Hi, a suggestion for Kamailio 5.0 is to get rid of the cryptic, case sensitive pseudo-variable names. Instead we replace them with descriptive names like the ones already provided by the TLS module. The current pseudo variables are a constant nuisance unless you deal with Kamailio every day and know them all by heart. They are an unnecessary barrier for new users learning Kamailio and force you to refer to the documentation more often than necessary. Ideally there would be a script to replace old variable names in configuration files with the new ones to make the transition less painful. -Sven

3 3

How to get Authorization Attributes
by Matthew Harrold 07 Mar '16

07 Mar '16

Hi All, I am trying to get attributes from the Proxy-Authenticate WWW-Authenticate and Authorization headers, namely username, realm, uri, nonce, and response, I can see some of these are already presented as psuedo-variables, however nonce and response are not. What's the most efficient way to obtain these headers? I'm currently using a regex, but there must be a more efficient method. Thanks for your help, Matthew

3 2

How to comunicate two different server voip
by Raihan Satya 06 Mar '16

06 Mar '16

Halo, my name dadang setiawan sample case VOIP Server A IP Address : 192.168.10.57 voip number Jon 100 Voip server B IP Address : 192.168.15.30 voip number Brian 200 i am using linphone video for comunication jon & brian the question is How to solution comunication jon with brian withhout 200(a)192.168.15.30 but direct 200 without using @

2 1

Re: [SR-Users] KAMAILIO Installation Problem
by Ed Todd 05 Mar '16

05 Mar '16

KAMAILIO Installation Problem Fred: re confusion. A few more details. Site 1 is a development site. The project in question is VoIP, using ANTISIP. A Windows server application is monitoring activities and carrying out local functions via IPhones. It has a LAN with static IPs for: · Windows 10 PC used for development · Windows 10 laptop, used for testing · MACBOOK, used for IPhone development · ‘Other PC’, recently converted to Linux + KAMailIO, using the binaries installation route rather than the source code route. It has a Comcast Modem/Router, Cisco DPC3941B Site 2 is a business site, which demonstrates the application using its own Windows PC and IPhones. It does not have any static IPs. Each site uses IPhones as the user interface of this application, via cell or WIFI. Both sites can communicate via SIP.ANTISIP.COM Site 1 can communicate with site 1 KAMAILIO but site 2 cannot: timeouts occur. I just installed what seems like a standard package: · Debian 32 or 64 bit graphical · Apt-get install git gcc make flex bison mysql-server kamailio-mysql-modules kamailio-tls-modules kamailio Should be OK so far apart from the .COM name of the Linux box. I then updated files as described earlier and the problems start. Apart from changing a few constants, I have not altered any script, I am just using the standard one shipped in the package above. I’ve had to guess how to tell KAMailIO about the static IP.

1 0