- sr-users - kamailio.org

Kamailio
by Tomasz Gass 19 Feb '15

19 Feb '15

Good morning, I'm looking for someone who, according to my guidelines set kamailio and connect the asterisk. Kamailio to act as a proxy server to accept registrations sip and locate. Pay for the correct configuration. Please contact me with people interested. Regards Tom

2 1

kamailio asterisk
by Slava Bendersky 19 Feb '15

19 Feb '15

Hello Everyone, I have standard case where kamailio play role of proxy for asterisk servers. Kamailio configured use TLS transport on public side and on private side UDP 5060. When client (SIP soft phone) connect to TLS socket everything goes well until kamailio trying forward request. Kamailio tries DNS resolve tls transport srv records instead of udp then it just crashed when no tls configured on private side of kamailio. Do I need manually fix sips in URI ? Or some different miss configuration ? [root@canlvprx01 kamailio]# rpm -qa | grep kamail kamailio-carrierroute-4.2.1-4.2.fc21.x86_64 kamailio-mysql-4.2.1-4.2.fc21.x86_64 kamailio-outbound-4.2.1-4.2.fc21.x86_64 kamailio-4.2.1-4.2.fc21.x86_64 kamailio-tls-4.2.1-4.2.fc21.x86_64 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <REGISTER> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sips:domain.org> ---> Client come with TLS transport Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==12 && [domain.org] == [ 10.18.130.46 ] Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==11 && [domain.org] == [67.34.12.56] Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5081 (advertise 0) matches port 5060 Feb 17 11:13:49 canlvprx 01 kernel: [4130713.518667] kamailio[22484]: segfault at 88 ip 0000000 0004bd30c sp 00007fffa2f73a20 error 4 in kamailio[400000+3b8000] Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[SIPOUT] c=[/etc/kamailio/kamailio-asterisk.cfg] l=850 a=25 n=append_hf Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[SIPOUT] c=[/etc/kamailio/kamailio-asterisk.cfg] l=851 a=5 n=route Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio-asterisk.cfg] l=567 a=16 n=if Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio-asterisk.cfg] l=563 a=25 n=is_method Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio-asterisk.cfg] l=571 a=16 n=if Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio-asterisk.cfg] l=567 a=25 n=is_method Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio-asterisk.cfg] l=574 a=16 n=if Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** cfgtrace:request_route=[RELAY] c=[/etc/kamailio/kamailio-asterisk.cfg] l=571 a=24 n=t_relay Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_lookup.c:1373]: t_newtran(): DEBUG: t_newtran: msg id=1 , global msg id=1 , T on entrance=(nil) Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=48550, isACK=0 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: trans=0x7f598a9ced40, callback type 1, id 0 entered Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: trans=0x7f598a9ced40, callback type 1, id 0 entered Feb 17 11:13:49 canlvprx 01 kernel: kamailio[22484]: segfault at 88 ip 00000000004bd30c sp 00007 fffa2f73a20 error 4 in kamailio[400000+3b8000] Feb 17 11:13: 49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [md5utils.c:67]: MD5St ringArray(): DEBUG: MD5 calculated: 0475e0d0dd9778e889618cb724403b4d Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [dns_cache.c:566]: _dns_hash_find(): dns_hash_find(_sips._tcp.networklab.ca(24), 33), h=646 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [resolve.c:967]: get_record(): get_record: skipping 1 NS (p=0xa1f556, end=0xa1f588) Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [resolve.c:983]: get_record(): get_record: parsing 2 ARs (p=0xa1f568, end=0xa1f588) Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [dns_cache.c:1772]: dns_get_related(): dns_get_related(0x7f598a9e89b0 (_sips._tcp.domain.org, 33), 33, *0x7f5995bd55e0) (0) Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [dns_cache.c:869]: dns_cache_add_unsafe(): dns_cache_add: adding _sips._tcp.domain.org(24) 33 (flags=0) at 646 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [dns_cache.c:869]: dns_cache_add_unsafe(): dns_cache_add: adding camsgsrv02.domain.org(24) 1 (flags=0) at 967 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [dns_cache.c:566]: _dns_hash_find(): dns_hash_find(camsgsrv02.domain.org(24), 1), h=967 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [msg_translator.c:2871]: create_via_hf(): create_via_hf: id added: <;i=1>, rcv proto=3 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [tcp_main.c:1818]: tcp_send(): tcp_send: no open tcp connection found, opening new one Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 10.18.130.50 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 5061, type 3 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 3263:0:0, 2 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 10.18.130.50 :5061: could not find corresponding listening socket for 10.18.130.46 , using default... Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tls [tls_server.c:184]: tls_complete_init(): Using TLS domain TLSc<default> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tls [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake started Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> [tcp_main.c:2697]: tcpconn_1st_send(): pending write on new connection 0x7f598a9d4678 (-1/129 bytes written) Feb 17 11:13:49 canlvprx01 kamailio: 15(22484) DEBUG: <core> [tcp_main.c:3565]: handle_ser_child(): handle_ser_child: read response= 7f598a9d4678, 5, fd 31 from 11 (22480) Feb 17 11:13:49 canlvprx01 kamailio: 15(22484) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9daf00, 31, 2, 0x7f598a9d4678), fd_no=19 Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed Thank you Slava.

3 2

acc db_extra problem
by Uri Shacked 19 Feb '15

19 Feb '15

Hi, It is my second time upgrading kamailio to 4.2.X. Everything is working except the acc db_extra inserts. I keep on getting that error: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Incorrect integer value: '' for column XXXXXXX I must confess, I managed to solve the problem once. But I do not remember how :-(. The XXXXXX column is set as an integer with NULL enabled and no default value (which works on the kamailio server where i fixed it...) Any ideas of where it comes from? BR, Uri

2 2

Kamailio Debug
by keita Adoulaye 19 Feb '15

19 Feb '15

Hi friends, Having problems with this command: tail -f /var/log/kamailio.log That it’s what i got: ERROR: ctl [ctl.c:382]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) Any ideas will appreciated Thanks

3 2

ims_charging module - AVP's
by Shane Harrison 18 Feb '15

18 Feb '15

Hi IMS'ers I am generating CCR's happily from the ims_charging module (adapted to work standalone with standard userloc module) but have a couple of questions around AVP's supported. a) I note that in the 3GPP TS 32.299 V12.7.0 specification that table 7.1.0.1, that it indicates Vendor-Id and Vendor-Specific-Application-Id aren't used. But later in section 7.1.16 it indicates that the Vendor-Id should be 10415 and set inside the Vendor-Specific-Application-Id AVP. Should I assume that the table is wrong ? b) The ims_charging_module doesn't seem to put an Auth-Application-Id into the CCR. This is mandatory according to 3GPP and RFC4006. I note that it does appear under the Vendor-Specific-Application-Id - but this doesn't seem right to me? At this stage I am thinking to add the Auth-Application-Id AVP and also the 3GPP Called-Party-Address AVP. To I submit patches to the development list? Kind regards Shane Shane Harrison Senior Software Engineer Imagination Technologies NZ Limited Level 2 1 Market Grove Lower Hutt, 5010 New Zealand PO Box 30-449 Lower Hutt, 5040 New Zealand Phone: +64 4 890-3681 ext 3361

3 2

Credit Control modules
by Shane Harrison 18 Feb '15

18 Feb '15

Hi all, As you will have seen from my posts, I have adapted the ims_charging module to work with usrloc module i.e. outside ims environment. I am interested in whether others see a use in having a Diameter Credit Control module that is standalone. There are already a number of Credit Control modules other than the ims one e.g. cncxx and I am not sure if the community sees a need for YACC. If there is interest then need to consider further how best to approach accommodating both ims dependence and standalone operation. Cheers Shane Shane Harrison Senior Software Engineer Imagination Technologies NZ Limited Level 2 1 Market Grove Lower Hutt, 5010 New Zealand PO Box 30-449 Lower Hutt, 5040 New Zealand Phone: +64 4 890-3681 ext 3361

2 1

rtpproxy bridge "ie" "ei" behind NAT (like in aws EC2)
by Giovanni Maruzzelli 17 Feb '15

17 Feb '15

dear Kamailians, I have Kamailio+rtpproxy in front of FreeSWITCH. Kamailio and FreeSWITCH are on the same private network. Public Internet IP address ports are redirected to Kamailio and rtpproxy (same situation as in Amazon EC2). Clients comes from Internet, and make calls to Internet, SIP signaling passing through FreeSWITCH (eg: A leg incoming INVITE, FreeSWITCH originate an outbound B leg INVITE, and then bridge the legs). Using rtpproxy with -A "advertise" patch from Daniel, this topology works fine in a "traditional" telco way: rtp goes from caller to rtpproxy to callee, and viceversa. Now I want to maintain FreeSWITCH in the middle of rtp flow all the time, in a pure b2bua way, so it can control and analyze the media streams. So, I need rtpproxy to act paying attention to direction, as in caller->rtpproxy->freeswitch->rtpproxy->callee (and viceversa). Normally I would use Kamailio multihomed and rtpproxy in bridging mode. But I cannot have a NIC on the public address. How I can use the "ie" "ei" feature of rtpproxy in an Amazon-EC2 like environment? (eg: no public address attached to machine, but ports redirection from public address). I read this trick from Hugh Waite: "I have used rtpproxy (with the advertised address patch) in Amazon to bridge media between internet facing and private subnets in a VPC. I found that I couldn’t use different advertised addresses depending on which direction the signalling was going on a single private IP address. I worked around this by allocating a second private ip address to the instance and used that in the ‘bridge’. -A 54.86.X.X/10.0.1.15 –l 10.0.1.10/10.0.1.15" Can you explain how to use this trick, or another way (without additional addresses is gladly accepted!) to reach the same result (rtp always passing through FreeSWITCH) ? Thank you all in advance, -giovanni -- Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618

8 11

Session timers
by Eric Koome 17 Feb '15

17 Feb '15

How do I process session timers in Kamailio coming from particular upstream provider every 15mins during a call? At the moment the the call fails after 15 mins. Related to this, another provider sends re-invites during a dialog to check that my kamailio is alive. However Kamailio responds with "488 not here". How do I process these as well? Asterisk sits behind Kamailio. Thanks Eric

2 3

CAMARILLO : (9898) ERROR: ctl [ctl.c:382]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)
by BY - Boujraf Youssef 17 Feb '15

17 Feb '15

Dear all, We get this error message : Using Kamailio V4.2 debian wheezy (9898) ERROR: ctl [ctl.c:382]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) We are not able to fix it. If anybody could help us it will be great. Best Regards, Youssef

1 0

load balancing + rtpengine
by Virmantas Variakojis 17 Feb '15

17 Feb '15

Hi, I want to use load balancing (dispatcher or carrierroute) but i have two upstream interfaces (separate vlan's to provider sides) and third interface to SIP clients side. Also i need to rewrite sdp fields with correct information with rtpengine, but it's impossible as i don't know whitch direction (provider) will be chosen by algorithm. Is it possible to use load dispatcher or carrierroute in conjunction with rtpengine or load balancing must be done manualy? — Regards, Virmantas -- __________________________________________________________________________ CONFIDENTIALITY NOTICE: The information contained in the present message (including any information contained in attachments herein) may be confidential and privileged. It may be read, copied and used only by the intended recipient. If you have received it in error please contact the sender (by return e-mail) immediately and delete this message. Any unauthorized use or dissemination of this message in whole or in parts is strictly prohibited. Print this message only if sharp necessary. УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ: Информация, содержащаяся в настоящем сообщении (включая любое вложение) может быть конфиденциальной и охраняться действующим законодательством. Сообщение может быть прочитано, скопировано и использовано исключительно лицом, которому сообщение предназначается. Если Вы получили настоящее сообщение по ошибке, пожалуйста, незамедлительно сообщите об этом отправителю (ответным письмом по электронной почте). Любое несанкционированное использование или распространение информации, содержащейся в настоящем сообщении в целом или в части, строго запрещены. Не распечатывайте настоящее сообщение, если в этом нет крайней необходимости.

1 0

TLS certificates per domain
by Muhammad Shahzad 17 Feb '15

17 Feb '15

Hi, I want to deploy a kamailio v4.2.x setup with multiple domains, all resolve to same IPv4 address kamailio is listening on. I am bit confused about how to configure TLS certificates using tls config file as mentioned here, http://kamailio.org/docs/modules/4.2.x/modules/tls.html#tls.p.config The documentation states that, -- If set the TLS module will load a special config file or config files from config directory, in which different TLS parameters can be specified on a per role (server or client) and domain basis (*for now only IPs*). The corresponding module parameters will be ignored. -- since all domains resolve single IP, so i assume i can specify only one section in tls config file with pair of key/pem file path. How can i specify more server certificates for same ip but with different domains? Thank you.

2 2

Syntax issue?
by Igor Potjevlesch 17 Feb '15

17 Feb '15

Hello, I'm looking for a way to track a call by using basic AVP like this: Into a route that treats INVITE: $avp(s:state)="call_start"; Then, if I test this AVP into WITHINDLG route: if($avp(s:state)!="call_start") ; the test fails. Did I miss something? The goal is to update this AVP during the life of the transaction. Regards, Igor.

4 15

selective logging with debugger module
by Sharath Kumar 16 Feb '15

16 Feb '15

Hello, I followed the documentation from http://kamailio.org/docs/modules/4.2.x/modules/debugger.html#idp84752. I have the global debug flag at 9. modparam("debugger", "cfgtrace", 1) modparam("debugger", "mod_level_mode", 1) modparam("debugger", "mod_level", "core=3") My Kamailio complains with a parsing error of some sort and fails to start. - "dbg_mod_level_param(): cannot store parameter: core=3" My intention is to turn off/reduce the "core" module tracing while keeping the "script" module at debug. Any suggestions ? I am running version 4.1.4. thanks Sharath

1 0

Amazon VPS, long UDP packets are seen by sniffer, but don't reach application
by Andrey Utkin 16 Feb '15

16 Feb '15

We experience strange networking issue, not exactly specific to kamailio, but still related to it. Rtpengine's "ng" interface uses UDP. Protocol messages contains SDP, and for encrypted video call those messages exceed 1500 bytes. Everything works fine within localhost, but when rtpengine and Kamailio are on different hosts, and when hosts are Amazon-hosted, we have trouble. This is experienced with l3.large, t2.micro with Ubuntu 14. I believe we don't have any special settings over system defaults. We send a large datagram from remote host, e.g. with such trivial app in python: import socket UDP_IP = "123.123.123.123" # remote host IP UDP_PORT = 33333 MESSAGE = """ .....0010......0020......0030......0040......0050......0060......0070......0080......0090......0100 .....0110......0120......0130......0140......0150......0160......0170......0180......0190......0200 .....0210......0220......0230......0240......0250......0260......0270......0280......0290......0300 .....0310......0320......0330......0340......0350......0360......0370......0380......0390......0400 .....0410......0420......0430......0440......0450......0460......0470......0480......0490......0500 .....0510......0520......0530......0540......0550......0560......0570......0580......0590......0600 .....0610......0620......0630......0640......0650......0660......0670......0680......0690......0700 .....0710......0720......0730......0740......0750......0760......0770......0780......0790......0800 .....0810......0820......0830......0840......0850......0860......0870......0880......0890......0900 .....0910......0920......0930......0940......0950......0960......0970......0980......0990......1000 .....1010......1020......1030......1040......1050......1060......1070......1080......1090......1100 .....1110......1120......1130......1140......1150......1160......1170......1180......1190......1200 .....1210......1220......1230......1240......1250......1260......1270......1280......1290......1300 .....1310......1320......1330......1340......1350......1360......1370......1380......1390......1400 .....1410......1420......1430......1440......1450......1460......1470......1480......1490......1500 .....1510......1520......1530......1540......1550......1560......1570......1580......1590......1600 .....1610......1620......1630......1640......1650......1660......1670......1680......1690......1700 .....1710......1720......1730......1740......1750......1760......1770......1780......1790......1800 .....1810......1820......1830......1840......1850......1860......1870......1880......1890......1900 .....1910......1920......1930......1940......1950......1960......1970......1980......1990......2000""" print "UDP target IP:", UDP_IP print "UDP target port:", UDP_PORT print "message:", MESSAGE sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.sendto(MESSAGE, (UDP_IP, UDP_PORT)) Then we listen on that port with such trivial python app: import socket UDP_IP = "172.31.4.102" # local ip UDP_PORT = 33333 sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.bind((UDP_IP, UDP_PORT)) while True: data, addr = sock.recvfrom(0x10000) print "received message:", data Meanwhile, we monitor the traffic with e.g. ngrep: ngrep -t -e -d any -W byline -O large_udp.pcap port 33333 or '(ip[6:2]' '&' '0x1fff)' '!=' '0' (the part after "or" catches segments of segmented packets) About the host: # uname -a Linux hostname 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Also linux-image-3.13.0-36-generic and linux-image-3.13.0-45-generic behave in same way. What we see: - ngrep shows the packets with correct contents. All segments are delivered. - application doesn't get any data at all Rarely dmesg shows such messages: [ 102.161679] UDP: bad checksum. From 123.123.123.124:56439 to 172.31.4.102:33333 ulen 2008 but it is logged really rarely, so this is surely not what happens on every packet transmission. This test works fine on e.g. cheapest DigitalOcean VPS. I am concerned with this issue because rtpengine software has UDP interface. So on Amazon hosts this interface works only within localhost, and I cannot distribute software to different nodes. Any thoughts? What's wrong, how to fix? -- Andrey Utkin

2 4

Log Media IP
by Ryan Brindley 16 Feb '15

16 Feb '15

Hey community, What's the best way to pull out the media ip from the SIP INVITE body (for logging)? Ryan Brindley

2 1

Event reg - questions
by Stefan Ljung 16 Feb '15

16 Feb '15

I made a test configuration for trying the pua_regEvent module. There were two things I want to ask about. First - when the SUBSCRIBE to event 'reg' following a UEs registration to the Kamailio is responded with a NOTIFY - there was no body in the NOTIFY. I expected a XML body with registration status. Second - When the UE re-registers to Kamailio - I expected a NOTIFY to be send on the existing 'reg' subscription, but nothing happened. Or am I missing some configuration ? Here's some of the conf script: ####### Modules Section ######## loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "kex.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 "mi_rpc.so" loadmodule "xcap_client.so" loadmodule "pua.so" loadmodule "pua_reginfo.so" loadmodule "presence.so" loadmodule "presence_reginfo.so" loadmodule "presence_xml.so" # ----------------- setting module-specific parameters --------------- #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" # ----- xlog params ----- modparam("xlog", "prefix", "-xlog: ") # ----- mi_fifo params ----- modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo") # ----- 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 ----- # add value to ;lr param to cope with most of the UAs modparam("rr", "enable_full_lr", 1) # 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) modparam("registrar", "max_expires", 86400) # ----- pua_reginfo params ----- modparam("pua_reginfo", "default_domain", "system.test") modparam("pua_reginfo", "server_address", "sip:reginfo@10.171.0.4") modparam("pua_reginfo", "publish_reginfo", 0) modparam("pua_reginfo", "default_domain", "system.test") # ----- presence_xml params ----- modparam("presence_xml", "integrated_xcap_server", 1) # ----- presence params ----- modparam("presence", "db_url", DBURL)

2 1

dialog module 4.2 REFER
by Uri Shacked 16 Feb '15

16 Feb '15

Hi, I am trying to use dlg_refer. I set the side to refer and the final destination. But, the contact header of the refer stays "controler(a)kamailio.org". So, the refer fails. Is it a bug or should i change the contact header by myself before doing the dlg_refer? same with the dlg_bridge..... Cheers, Uri

3 2

Using dialog_ng
by Shane Harrison 15 Feb '15

15 Feb '15

Hi all, I think the lack of response to my previous thread is probably because it was too complicated. I have now narrowed my problem down after further archive readings . I am trying to use the dialog_ng module along with the ims_charging_module. Upon reception of an INVITE, a call to the Ro_CCR() from the request_route script is made. That function does a check that the dialog record exists (binds to dialog module and does a "get_dlg(msg)" call) - this fails i.e. dialog is not found. Running kamailio 4.2.2 and relevant sections of kamailio.cfg are: modparam("dialog_ng", "dlg_flag", FLT_DIALOG) modparam("dialog_ng", "timeout_avp", "$avp(DLG_TIMEOUT_AVP)") modparam("dialog_ng", "detect_spirals", 1) modparam("dialog_ng", "profiles_no_value", "orig ; term") request_route { # NAT detection route(NATDETECT); # Set DLG flag to track dialogs using dialog2 if (!is_method("REGISTER|SUBSCRIBE")) setflag(FLT_DIALOG); # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); if (is_method("INVITE")) { set_dlg_profile("orig"); Ro_CCR("CHARGING_CCR_REPLY", "orig", "SCUR", "", "30","CCR_location"); } So my question is, "should the above logic create a dialog record on the initial INVITE?" and if yes then "what possible reasons might there be for the Ro_CCR() function not be able to detect it exists?" Cheers Shane Harrison

3 7

rtpengine - Error when sending message. Error: Invalid argument
by Amit Patkar 14 Feb '15

14 Feb '15

Hi I am getting error with rtpengine. Running Kamailio 4.2.3 I am trying to call from conventional SIP client to WebRTC client Google Chrome v38.0.2125.104 Firefox v33.0 Using sipML5 as WebRTC client root@rtcpbx:/home/avhan# /usr/sbin/rtpengine --interface=127.0.0.1\!192.168.2.161 --listen-ng=7722 --pidfile=/var/run/ngcp-rtpengine-daemon.pid --tos=184 --table=42 --foreground --log-level=7 --log-stderr INFO: Generating new DTLS certificate DEBUG: Dump of DTLS certificate: DEBUG: --- -----BEGIN CERTIFICATE----- DEBUG: --- MIIBpDCCAQ2gAwIBAAIJAIH/X+7BeV8gMA0GCSqGSIb3DQEBBQUAMBQxEjAQBgNV DEBUG: --- BAMTCXJ0cGVuZ2luZTAeFw0xNTAyMTMxMjM5MjJaFw0xNTAzMTYxMjM5MjJaMBQx DEBUG: --- EjAQBgNVBAMTCXJ0cGVuZ2luZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA DEBUG: --- tfOduffYlJeuTeA6GRRKpeuUougYgu33QKjPZ9RuQNl6AIsmJQrqPJ9bTv93BlNd DEBUG: --- I/COq89SRxxjhAHEw6v3F283/lZAitySVa+TazbpZrwKsWbfPTXtLMC5oJvEPUr/ DEBUG: --- 8xcX+rnImLHZPrECMZj4pjSI6htclKok+YFf3incSmECAwEAATANBgkqhkiG9w0B DEBUG: --- AQUFAAOBgQBA2zHxUAv4J/dRLMboF9y3h6hQNnoEQNDwlmE+M4bBbOAxNYNxpmy3 DEBUG: --- mmZ54GBZFbvIWO4MVYrGiEMXBsQ3LSHo+MeExtY7Jq1RbXHU+DT/hHg5DGHHeFyr DEBUG: --- d46TUaHIFG/XhKSAaaCX1EbqtezMaUWrJw+mtOfzfZMEVzMP72CmiA== DEBUG: --- -----END CERTIFICATE----- DEBUG: Dump of DTLS private key: DEBUG: --- -----BEGIN PRIVATE KEY----- DEBUG: --- MIICdgIBADANBgkqhkiG9w0BAQEFAASCAmAwggJcAgEAAoGBALXznbn32JSXrk3g DEBUG: --- OhkUSqXrlKLoGILt90Coz2fUbkDZegCLJiUK6jyfW07/dwZTXSPwjqvPUkccY4QB DEBUG: --- xMOr9xdvN/5WQIrcklWvk2s26Wa8CrFm3z017SzAuaCbxD1K//MXF/q5yJix2T6x DEBUG: --- AjGY+KY0iOobXJSqJPmBX94p3EphAgMBAAECgYBJG9sLZz/Z7Nx3pBoUC6g25OKz DEBUG: --- VmjK6w0HKQ01XhDy869m2oJ4LduSgkFxC4rqusJY94aMGGCp/AkseH10VfuQ/Dn4 DEBUG: --- 6Zv9l8xGlprRmW0do6w0AR7F5JpcuoMT7ae8Jf7hAJpa//LbAg2s0lJBMofIUtd/ DEBUG: --- 0xs0y9uX/stV9hRAAQJBAOUocKdTbN1J9W6EB+r64/QBPxB7jhbs8J76RRfCjhE2 DEBUG: --- CS8JRBajMJJ3XgjOWQuh44xmydGCJeSSisDKsONVpgECQQDLQ6QCHYJxeXJ0R4w9 DEBUG: --- 5XqUEQhb03GlwoTIas3YQfJJyk/zKnQAkBKwjwatrNEldCGBOCOgeQhTERPwSxcx DEBUG: --- kGRhAkBxjmSkxjaAQhIZPdwemU00sRlrNY7n1Wo3nZV3fLWh2cEbSeAvx5ZePkCe DEBUG: --- 5IJDvWlhPd5sr63PYr7XYpndTagBAkEAj27Nvwhf0f8nOtJ6LftPAkj6owGUAqo+ DEBUG: --- 1MY5N09hz5xJyoe8j+EaryheSBPZChrmwa6BxW1i6Gr2rOvwE/OWQQJACxjVriL8 DEBUG: --- mKFqDLN1rQuDqyA6f0jSaxuPsA3TGCcEbgw4e8hQD9pFJ6NK7/X/UeqqWsW0sAZS DEBUG: --- mNrnLY9VvZPSpw== DEBUG: --- -----END PRIVATE KEY----- INFO: Startup complete, version 3.3.0.0+0~mr3.8.0.0 DEBUG: Adding a proxy for control ng stats:127.0.0.1 INFO: Got valid command from 127.0.0.1:60075: offer - { "sdp": "v=0 o=- 28314700 28314700 IN IP4 192.168.2.18 s=http://www.portsip.com c=IN IP4 192.168.2.18 t=0 0 m=audio 20670 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ", "ICE": "force", "flags": [ "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "FjDYirMD4b8ldLCQFrUMaw..", "received-from": [ "IP4", "192.168.2.18" ], "from-tag": "7a3b9012", "command": "offer" } NOTICE: [FjDYirMD4b8ldLCQFrUMaw..] Creating new call DEBUG: [FjDYirMD4b8ldLCQFrUMaw..] Opened ports 30000..30001 for media relay DEBUG: [FjDYirMD4b8ldLCQFrUMaw..] Opened ports 30010..30011 for media relay INFO: [FjDYirMD4b8ldLCQFrUMaw..] Returning to SIP proxy: d3:sdp669:v=0 o=- 28314700 28314700 IN IP4 192.168.2.161 s=http://www.portsip.com c=IN IP4 192.168.2.161 t=0 0 a=ice-lite m=audio 30000 RTP/SAVPF 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:30001 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:JBeKZmgOzhC3A5Ays2nm4Jx3GqSbsoVStGSjSFL/ a=setup:actpass a=fingerprint:sha-1 CE:47:48:60:04:D0:A5:D7:FD:00:89:6E:8F:D9:25:48:9D:2F:B9:89 a=ice-ufrag:bMtYwXGC a=ice-pwd:q053zJtRE8bxgCEu3eebdaqoWSmr a=candidate:EqkUFjVat8drCK70 1 UDP 2130706431 192.168.2.161 30000 typ host a=candidate:EqkUFjVat8drCK70 2 UDP 2130706430 192.168.2.161 30001 typ host 6:result2:oke INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] Successful STUN binding request from 192.168.2.18:7427 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30000] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] Successful STUN binding request from 192.168.2.18:7428 INFO: [FjDYirMD4b8ldLCQFrUMaw.. port 30001] STUN: using this candidate INFO: Got valid command from 127.0.0.1:42832: ping - { "command": "ping" } INFO: Returning to SIP proxy: d6:result4:ponge INFO: Got valid command from 127.0.0.1:35595: offer - { "sdp": "v=0 o=- 28373892 28373892 IN IP4 192.168.2.18 s=http://www.portsip.com c=IN IP4 192.168.2.18 t=0 0 m=audio 20674 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ", "ICE": "force", "flags": [ "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/SAVPF", "call-id": "fJTfptxXKrVoGdalt_2MMA..", "received-from": [ "IP4", "192.168.2.18" ], "from-tag": "bd78da3f", "command": "offer" } NOTICE: [fJTfptxXKrVoGdalt_2MMA..] Creating new call DEBUG: [fJTfptxXKrVoGdalt_2MMA..] Opened ports 30022..30023 for media relay DEBUG: [fJTfptxXKrVoGdalt_2MMA..] Opened ports 30044..30045 for media relay INFO: [fJTfptxXKrVoGdalt_2MMA..] Returning to SIP proxy: d3:sdp669:v=0 o=- 28373892 28373892 IN IP4 192.168.2.161 s=http://www.portsip.com c=IN IP4 192.168.2.161 t=0 0 a=ice-lite m=audio 30022 RTP/SAVPF 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:30023 a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:YUVDWqqE+RNOPLu4d1J81/gee3OY8tnfGSjc2zjB a=setup:actpass a=fingerprint:sha-1 CE:47:48:60:04:D0:A5:D7:FD:00:89:6E:8F:D9:25:48:9D:2F:B9:89 a=ice-ufrag:1d16gzNH a=ice-pwd:qpNBX4eBwfNKq0TPpNHLeuMdHOjX a=candidate:EqkUFjVat8drCK70 1 UDP 2130706431 192.168.2.161 30022 typ host a=candidate:EqkUFjVat8drCK70 2 UDP 2130706430 192.168.2.161 30023 typ host 6:result2:oke INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [FjDYirMD4b8ldLCQFrUMaw..] Closing call due to timeout INFO: [FjDYirMD4b8ldLCQFrUMaw..] Final packet stats: INFO: [FjDYirMD4b8ldLCQFrUMaw..] --- Tag '', created 1:06 ago, in dialogue with '(none)' INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30000 <> [::]:0 , 6 p, 600 b, 0 e, 1423917572 last_packet INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30001 <> [::]:0 (RTCP), 6 p, 600 b, 0 e, 1423917572 last_packet INFO: [FjDYirMD4b8ldLCQFrUMaw..] --- Tag '7a3b9012', created 1:06 ago, in dialogue with '' INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30010 <> 192.168.2.18:20670, 0 p, 0 b, 0 e, 1423917566 last_packet INFO: [FjDYirMD4b8ldLCQFrUMaw..] ------ Media #1, port 30011 <> 192.168.2.18:20671 (RTCP), 0 p, 0 b, 0 e, 1423917566 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] Successful STUN binding request from 192.168.2.18:7449 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30022] STUN: using this candidate INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] Successful STUN binding request from 192.168.2.18:7450 INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30023] STUN: using this candidate INFO: Got valid command from 127.0.0.1:36029: answer - { "sdp": "v=0 o=Mozilla-SIPUA-33.0 15128 1 IN IP4 0.0.0.0 s=Doubango Telecom - firefox t=0 0 a=ice-ufrag:524a14d8 a=ice-pwd:f23ceb82b6f9a86a2c1f180a013a9ff3 a=fingerprint:sha-256 6A:5D:49:F6:7B:FE:5B:5E:23:43:EE:31:43:20:46:C0:E8:12:B7:AD:AB:A2:09:66:94:55:42:E2:6B:D3:D9:63 m=audio 7449 UDP/TLS/RTP/SAVPF 0 101 c=IN IP4 192.168.2.18 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=setup:active a=candidate:0 1 UDP 2128609535 192.168.2.18 7449 typ host a=candidate:0 2 UDP 2128609534 192.168.2.18 7450 typ host ", "ICE": "remove", "flags": [ "trust-address" ], "replace": [ "origin", "session-connection" ], "transport-protocol": "RTP/AVP", "call-id": "fJTfptxXKrVoGdalt_2MMA..", "received-from": [ "IP4", "192.168.2.18" ], "from-tag": "bd78da3f", "to-tag": "mUTC7w3qs5ka6fJWKCiM", "command": "answer" } INFO: [fJTfptxXKrVoGdalt_2MMA..] Returning to SIP proxy: d3:sdp240:v=0 o=Mozilla-SIPUA-33.0 15128 1 IN IP4 0.0.0.0 s=Doubango Telecom - firefox t=0 0 m=audio 30044 RTP/AVP 0 101 c=IN IP4 192.168.2.161 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=rtcp:30045 6:result2:oke *DEBUG: [fJTfptxXKrVoGdalt_2MMA.. port 30044] Error when sending message. Error: Invalid argument WARNING: [fJTfptxXKrVoGdalt_2MMA.. port 30044] Write error on RTP socket: Invalid argument* INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] Final packet stats: INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] --- Tag 'mUTC7w3qs5ka6fJWKCiM', created 0:13 ago, in dialogue with 'bd78da3f' INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30022 <> 192.168.2.18:7449 , 7 p, 700 b, 0 e, 1423917638 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30023 <> 192.168.2.18:7450 (RTCP), 7 p, 700 b, 0 e, 1423917638 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] --- Tag 'bd78da3f', created 0:13 ago, in dialogue with 'mUTC7w3qs5ka6fJWKCiM' INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30044 <> 192.168.2.18:20674, 0 p, 0 b, 1 e, 1423917626 last_packet INFO: [fJTfptxXKrVoGdalt_2MMA.. port 30044] ------ Media #1, port 30045 <> 192.168.2.18:20675 (RTCP), 0 p, 0 b, 0 e, 1423917626 last_packet Regards Amit

2 2

Kamailio and rtpengine
by Marc Soda 14 Feb '15

14 Feb '15

How does Kamailio load balance traffic to rtpengine? Is it load based, round robin, etc? The module makes mention of this but I don't see how it works. Also, it talks about weighting the proxies. How is that accomplished? Thanks, Marc

3 2

WebRTC to PSTN call, proxied through Kamailio
by Rahul MathuR 14 Feb '15

14 Feb '15

Hello gents, I was trying my hands on getting a successful RTCweb call (JSsip, since Peter Dunkley mentioned that he's been using JSsip for most of the testing scenarios..) to PSTN, making my kamailio as proxy + protocol converter (sip over web-sockets to sip over udp). And yes, I've referred Carlos' config; the main problem is I get 'Bad Media Description' error in Google Chromium (Version 40.0.2214.111 m) & my SIP server even sends 200 OK, but my phone doesn't ring. To make it worse, I can see rtpengine throwing this error - "SRTCP output wanted, but no crypto suite was negotiated" BTW, I have - [root@localhost log]# openssl version OpenSSL 1.0.1j 15 Oct 2014 I even tried building kamailio & rtpengine using this openssl but in-vain. One thing that baffles me is that, apparently kamailio has started receiving RTP packets (perhaps early media) but the mobile phone hasn't ringed :-( I am attaching all possible logs & seek some guidance from the array of experts in this list. Files attached: a) tcpdump on ext. interface b) tcpdump on loopback c) syslogs d) Chromium JS logs UAC (14.98.55.38), Kamailio (125.99.186.126), SIP Server (157.238.178.153), Media Server (199.27.244.6) -- Warm Regds. MathuRahul

3 6

Issues after Ubuntu Server Update and WebRTC
by Manuel Camargo Lominchar 13 Feb '15

13 Feb '15

>* Is the SIP signaling still going fine via websocket? Do you get callee *>* ringing? *>>* Cheers, *>* Daniel* Hello Daniel Actually SIP signalling goes perfect, and i can see in RTP asterisk log that RTP packets are being sent, so I suppose there is something stuck somewhere in RTP maybe related with RTP Engine >Hi, > >If you are using rtpengine for the rtp you might have to upgrade to a >newer version. > >On my system crypto negotiation in rtpengine started failing after a >openssl update in January. Recompiling a newer version from git fixed that. > >regards > >M I updated to latest version through git but still stuck there. Now I can see that the config file (ngcp-rtpengine in etc default) has changed so I'm not sure how should this impact (not ADDRESS neither ADV ADDRESS now I see an Interfaces parameter) I also find for some reason very possible that somehow rtp traffic is not getting through. ICE candidates are being negotiated, so I feel that the route is clear, so maybe there might be some crypto issues as you point out, but update has not been enough :( Any other ideas? *Manuel Camargo* Teléfono: 638000836 eMail: sir.louen(a)gmail.com <https://twitter.com/SirLouen> [image: Ver el perfil de Manuel Camargo Lominchar en LinkedIn] <http://es.linkedin.com/in/louen>

1 1

change_reply_status() 415 -> 200 change
by Juha Heinanen 13 Feb '15

13 Feb '15

i tried to use change_reply_status() to change 415 to 200, but got: ERROR: textopsx [textopsx.c:283]: change_reply_status_f(): ERROR: textops: the class of provisional or positive final replies cannot be changed textopsx/README does not mention anything about what can or cannot be changed. why is it that the above change cannot be made? -- juha

2 1

Issues after Ubuntu Server Update and WebRTC
by Manuel Camargo Lominchar 13 Feb '15

13 Feb '15

This might be a weird question I've been operating for some months with my kam + asterisk + webrtc sipml5 based system inside an Ubuntu Server Today I had the idea to apt-get upgrade my system and... now the whole system webrtc communication service is dead Here is the VAST list of packages updated... But I cannot figure out who is the "destroyer" package. No prompts appeared during the update so I believe no config files have been updated I'm trying to debug but I cant find a solution The handshake is done, and in Wireshark the only thing I find is that no UDP (RTP) packages are being processed, but in the SIP log I can see ICE candidates and all process is done I tried to do a direct SIP connection without WebRTC, and it worked pretty fine, so this have something to do with maybe crypt libs, or something to do with kamailio and imcompatibilities with one of this packages. Kamailio Version: # kamailio -v version: kamailio 4.1.5 (x86_64/linux) 2b3d4b flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_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 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 2b3d4b compiled on 14:39:42 Aug 28 2014 with gcc 4.8.2 Any ideas of where to start digging? Start-Date: 2015-02-12 14:40:19 Install: linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-headers-3.13.0-45:amd64 (3.13.0-45.74, automatic) Upgrade: bind9-host:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), python3-problem-report:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), mime-support:amd64 (3.54ubuntu1, 3.54ubuntu1.1), liblwres90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), apt:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), libevent-2.0-5:amd64 (2.0.21-stable-1ubuntu1, 2.0.21-stable-1ubuntu1.14.04.1), libsystemd-login0:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), linux-headers-generic:amd64 (3.13.0.37.44, 3.13.0.45.52), mysql-server-core-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), ppp:amd64 (2.4.5-5.1ubuntu2, 2.4.5-5.1ubuntu2.1), mysql-server-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), multiarch-support:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libdns100:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), krb5-multidev:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), mysql-client-core-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), libisccfg90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), systemd-services:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), apt-transport-https:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), procps:amd64 (3.3.9-1ubuntu2, 3.3.9-1ubuntu2.2), libbind9-90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), tcpdump:amd64 (4.5.1-2ubuntu1, 4.5.1-2ubuntu1.1), dbus:amd64 (1.6.18-0ubuntu4.2, 1.6.18-0ubuntu4.3), libgssapi-krb5-2:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), php5-mysql:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), python-urllib3:amd64 (1.7.1-1build1, 1.7.1-1ubuntu0.1), dkms:amd64 (2.2.0.3-1.1ubuntu5, 2.2.0.3-1.1ubuntu5.14.04), php5-common:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), coreutils:amd64 (8.21-1ubuntu5, 8.21-1ubuntu5.1), libkrb5-3:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), apt-utils:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), cpio:amd64 (2.11+dfsg-1ubuntu1, 2.11+dfsg-1ubuntu1.1), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), python3-software-properties:amd64 (0.92.37.1, 0.92.37.3), libkadm5clnt-mit9:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), mount:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libsystemd-daemon0:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), python-apt:amd64 (0.9.3.5, 0.9.3.5ubuntu1), libc-dev-bin:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libcgmanager0:amd64 (0.24-0ubuntu7, 0.24-0ubuntu7.2), file:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), libapparmor1:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), libkrb5-dev:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libmagic1:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), libpam-systemd:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), libc-bin:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libc6:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libglib2.0-0:amd64 (2.40.0-2, 2.40.2-0ubuntu1), php5-readline:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libprocps3:amd64 (3.3.9-1ubuntu2, 3.3.9-1ubuntu2.2), libsepol1:amd64 (2.2-1, 2.2-1ubuntu0.1), libglib2.0-dev:amd64 (2.40.0-2, 2.40.2-0ubuntu1), libapt-inst1.5:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), libuuid1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libmount1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), dnsutils:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), libdbus-1-3:amd64 (1.6.18-0ubuntu4.2, 1.6.18-0ubuntu4.3), udev:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), curl:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), update-notifier-common:amd64 (0.154.1, 0.154.1ubuntu1), plymouth:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), libglib2.0-data:amd64 (2.40.0-2, 2.40.2-0ubuntu1), mysql-client-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), krb5-locales:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.3, 2.9.1+dfsg1-3ubuntu4.4), ntp:amd64 (4.2.6.p5+dfsg-3ubuntu2, 4.2.6.p5+dfsg-3ubuntu2.14.04.2), libudev1:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), binutils:amd64 (2.24-5ubuntu3, 2.24-5ubuntu3.1), bsdutils:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libxml2-dev:amd64 (2.9.1+dfsg1-3ubuntu4.3, 2.9.1+dfsg1-3ubuntu4.4), libapparmor-perl:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), lshw:amd64 (02.16-2ubuntu1, 02.16-2ubuntu1.2), libssl-dev:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), wget:amd64 (1.15-1ubuntu1, 1.15-1ubuntu1.14.04.1), libapt-pkg4.12:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), uuid-runtime:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python3-apt:amd64 (0.9.3.5, 0.9.3.5ubuntu1), mysql-common:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), php5-cli:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libmysqlclient18:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), git-man:amd64 (1.9.1-1, 1.9.1-1ubuntu0.1), libplymouth2:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), libmysqlclient-dev:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), git:amd64 (1.9.1-1, 1.9.1-1ubuntu0.1), python3-distupgrade:amd64 (0.220.5, 0.220.7), libcurl3:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), apport:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), linux-firmware:amd64 (1.127.7, 1.127.11), libssl-doc:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), libcurl4-gnutls-dev:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), landscape-common:amd64 (14.01-0ubuntu3, 14.12-0ubuntu0.14.04), libblkid1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python3-apport:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), apparmor:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), tzdata:amd64 (2014e-0ubuntu0.14.04, 2015a-0ubuntu0.14.04), mysql-server:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), software-properties-common:amd64 (0.92.37.1, 0.92.37.3), openssl:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), libelf1:amd64 (0.158-0ubuntu5.1, 0.158-0ubuntu5.2), libglib2.0-bin:amd64 (2.40.0-2, 2.40.2-0ubuntu1), libkdb5-7:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), ubuntu-release-upgrader-core:amd64 (0.220.5, 0.220.7), linux-libc-dev:amd64 (3.13.0-37.64, 3.13.0-45.74), util-linux:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python-apt-common:amd64 (0.9.3.5, 0.9.3.5ubuntu1), php5-gd:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libgssrpc4:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libdrm2:amd64 (2.4.52-1, 2.4.56-1~ubuntu1), language-pack-en:amd64 (14.04+20140707, 14.04+20141110), libmysqld-dev:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), linux-image-generic:amd64 (3.13.0.37.44, 3.13.0.45.52), libkadm5srv-mit9:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libkrb5support0:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libk5crypto3:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libisccc90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), dh-apparmor:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), libc6-dev:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libisc95:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), libcurl3-gnutls:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), rsyslog:amd64 (7.4.4-1ubuntu2.3, 7.4.4-1ubuntu2.5), ntpdate:amd64 (4.2.6.p5+dfsg-3ubuntu2, 4.2.6.p5+dfsg-3ubuntu2.14.04.2), linux-generic:amd64 (3.13.0.37.44, 3.13.0.45.52) End-Date: 2015-02-12 14:43:37 Kind regards, *Manuel Camargo* Teléfono: 638000836 eMail: sir.louen(a)gmail.com <https://twitter.com/SirLouen> [image: Ver el perfil de Manuel Camargo Lominchar en LinkedIn] <http://es.linkedin.com/in/louen>

4 3

Unable to route outbound with multiple VRRP IP's
by mark＠brightvoip.co.uk 13 Feb '15

13 Feb '15

Hi, I am trying to install a Kamailio server in a HA configuration, with IP's for 3 attached networks. I am using Keepalived/VRRP to manage the VIP's. I have tested v 4.1.6 and latest 4.2.2 I have 3 x listen entries, one for each network and mhomed=1. Also, for info, we have net.ipv4.ip_nonlocal_bind = 1 in sysctl.conf listen=udp:my.public.net.46:5060 listen=udp:192.168.106.46:5060 listen=udp:192.168.116.46:5060 mhomed=1 I have dispatcher set up to load balance over two seperate groups of Asterisk servers, one on each private network. Dispatcher does probing to know which Asterisks are 'alive'. When I ran the system, Kamailio/Dispatcher was not able to send any probing OPTIONS to any Asterisk (normal PINGS work fine in all networks in/out of Asterisk/Kamailio) Looking at the log, I see these entries for all 3 networks: Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: <core> [forward.c:218]: get_out_socket(): no socket found Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: <core> [forward.c:220]: get_out_socket(): no corresponding socket found for(u dp:192.168.116.38:5060) Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: tm [ut.h:345]: uri2dst2(): no corresponding socket found for "192.168.116.38" af 2 (udp:192.168.116.38:5060) Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: tm [uac.c:307]: t_uac_prepare(): t_uac: no socket found Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: dispatcher [dispatch.c:2564]: ds_check_timer(): unable to ping [sip:192.168.1 16.38:5060] I notice from other logging that Kamailio is receiving and processing incoming OPTIONS messages, and sending appropriate replies. Now, this might not be a Kamailio issue, as when I run the same config with 3 IP's, but NOT using VRRP/Keepalived/Aliased IP's, everything works normally. However, I do need to run this setup in HA, so would welcome any suggestions as to how I might resolve this issue. Kind regards, Mark Hall --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com

2 2

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