- sr-users - kamailio.org

Legacy Cisco 7945 and 7960 Handset Integration with Kamailio
by Jonathan Hunter 19 Mar '14

19 Mar '14

Hi Guys, Hope your all well? Apologies for the post, however I wondered if anyone had successfully integrated Cisco 7945/7960 handsets running SIP firmware with Kamailio? I appreciate these handsets have some issues, whereby they expect responses on port 5060, even though they initiate transactions from a dynamic port, I just wondered if anyone had a working model or some pointers they could share? As we are pondering a VPN connection to remove NAT, however Id like to consider other alternatives before then. Many thanks Jon

2 3

Module not up to date in apt-get repository
by Oliver Roth 19 Mar '14

19 Mar '14

Hi all We updated from kamailio 3.1 to kamailio 3.3. As shown in module description the function rtpproxy_manage() should be available starting version 3.2 But if the update is done to 3.3 - we get the following error when trying to start kamailio * Not starting Kamailio SIP server: invalid configuration file! * * 0(24558) ERROR: <core> [cfg.y:3455]: cfg. parser: failed to find command rtpproxy_manage 0(24558) : <core> [cfg.y:3594]: parse error in config file /etc/kamailio/kamailio.cfg, line 905, column 17: unknown command, missing loadmodule? In request_route we have the command : Rtpproxy_manage() ; Any idea ? Kind regards, Oli

2 1

Installing Kamailio on Ubuntu
by Swetha Raj 19 Mar '14

19 Mar '14

Hi, I am trying to install Kamailio on Ubuntu 12.04,but hitting the below issue. root@test:/usr/local# apt-get install kamailio kamailio-mysql-modules kamailio-tls-modules Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package kamailio E: Unable to locate package kamailio-mysql-modules E: Unable to locate package kamailio-tls-modules Can anybody point me the right steps to do the same Thanks

3 3

Debian Kamailio Shell Script Installer
by Joel White 19 Mar '14

19 Mar '14

*https://gist.github.com/zhacker98/9643861 <https://gist.github.com/zhacker98/9643861>*

1 0

Does tls/wss actually work or What is required for tls/wss
by jaflong jaflong 19 Mar '14

19 Mar '14

Hi, What are the requirements for connecting with tls/wss. I have not come across any information or example for this. My config is working when the client uses ws. However if I change this to use wss, (this is it only paramter I change) it does not work. I understand Kamailio does not support DTLS, I set the jssip client DtlsSrtpKeyAgreement to false to disable this, I also set the tls option to not require or verify certicficates and it still does not work. What if other considaerstion do I need to check? thanks

6 8

db logging for unsuccessful calls
by betul.cerit＠netgsm.com.tr 19 Mar '14

19 Mar '14

Hi to all, I could hardly make kamailio log cdr to db but it just logs successful calls.I need cdr of unsuccessful calls also.I used to use asterisk so in cdr I need duration and billsec separately.As far as I understand kamailio can give only one of them.Is there a way to get them? Here is my acc configuration: #!ifdef WITH_ACCDB modparam("acc", "cdr_enable", 1) modparam("acc", "early_media", 0) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) modparam("acc", "detect_direction", 0) modparam("acc", "db_url", "mysql://root: secret@localhost/mydb") modparam("acc", "log_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_table_missed_calls", "missed_calls") modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 3) modparam("acc", "db_extra","src_user=$fU;src_domain=$fd;src_ip=$si;dst_user=$rU;dst_domain=$rd") #!endif What should I exactly do?Can someone help? Thanks in Advance. BETÜL CERİT

2 2

Kamailio vs Asterisk - Not found in usrloc
by Alexandr Usov 19 Mar '14

19 Mar '14

Kamailio (192.168.182.1) and Asterisk (192.168.182.24) realtime integration by http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb. Kamailio have a public interface also. Grep from debug on kamailio 4.2.1 on call from asterisk extensions/peers: Mar 19 14:51:50 netbox /usr/sbin/kamailio[547784]: DEBUG: usrloc [udomain.c:602]: db_load_urecord(): aor 101(a)192.168.182.1 not found in table location Mar 19 14:51:50 netbox /usr/sbin/kamailio[547784]: DEBUG: registrar [lookup.c:158]: lookup(): '101(a)192.168.182.1' Not found in usrloc Mar 19 14:51:50 netbox /usr/sbin/kamailio[547785]: DEBUG: usrloc [udomain.c:602]: db_load_urecord(): aor 102(a)192.168.182.1 not found in table location Mar 19 14:51:50 netbox /usr/sbin/kamailio[547785]: DEBUG: registrar [lookup.c:158]: lookup(): '102(a)192.168.182.1' Not found in usrloc Kamailio forwards registration to Asterisk and store location of peer with domain name sip.domain.tld. But Asterisk dials peer to peer in local dialplan - to IP of kamailio. asterisk1*CLI> sip show peers Name/username Host Dyn Forcerport Comedia ACL Port Status Description Realtime 101/101 192.168.182.1 D No No A 5060 Unmonitored Cached RT 102/102 192.168.182.1 D No No A 5060 Unmonitored Cached RT asterisk1*CLI> sip show peer 102 * Name : 102 Description : Realtime peer: Yes, cached Secret : <Not set> MD5Secret : <Not set> Remote Secret: <Not set> Context : ext-local Record On feature : automon Record Off feature : automon Subscr.Cont. : <Not set> Language : Tonezone : <Not set> AMA flags : Unknown Transfer mode: open CallingPres : Presentation Allowed, Not Screened FromUser : 102 FromDomain : sip.domain.com Port 5060 Callgroup : Pickupgroup : Named Callgr : Nam. Pickupgr: MOH Suggest : Mailbox : VM Extension : asterisk LastMsgsSent : 6/0 Call limit : 0 Max forwards : 0 Dynamic : Yes Callerid : "" <> MaxCallBR : 384 kbps Expire : 252 Insecure : no Force rport : No Symmetric RTP: No ACL : Yes DirectMedACL : No T.38 support : No T.38 EC mode : Unknown T.38 MaxDtgrm: -1 DirectMedia : Yes PromiscRedir : No User=Phone : No Video Support: No Text Support : No Ign SDP ver : No Trust RPID : No Send RPID : No Path support : No Path : N/A Subscriptions: Yes Overlap dial : No DTMFmode : rfc2833 Timer T1 : 500 Timer B : 32000 ToHost : Addr->IP : 192.168.182.1:5060 Defaddr->IP : (null) Prim.Transp. : UDP Allowed.Trsp : UDP Def. Username: 102 SIP Options : (none) Codecs : (gsm|ulaw|alaw|h263|testlaw) Codec Order : (none) Auto-Framing : No Status : Unmonitored Useragent : kamailio (4.1.2 (x86_64/linux)) Reg. Contact : sip:102@192.168.182.1:5060 Qualify Freq : 60000 ms Keepalive : 0 ms Sess-Timers : Accept Sess-Refresh : uas Sess-Expires : 1800 secs Min-Sess : 90 secs RTP Engine : asterisk Parkinglot : Use Reason : No Encryption : No /etc/asterisk/extensions.conf: ... [ext-local] ; our phones use 3 digit extensions, starting with 1 exten => _1XX,1,DumpChan(verbose) exten => _1XX,n,Dial(SIP/${EXTEN}) exten => _1XX,n,Voicemail(${EXTEN},u) exten => _1XX,n,Hangup exten => _1XX,101,Voicemail(${EXTEN},b) exten => _1XX,102,Hangup Also strabge why I see user.pub.lic in Variables on channel during call: ... SIPCALLID=GOB1.VSLU0SOTjG-u8jjarzXv.lJTjin SIPDOMAIN=netbox.teleservice.com.ua SIPURI=sip:101@user.pub.lic.ip:35835 Do I need rewrite To header with change IP to domain name? Maybe in this section: #!ifdef WITH_ASTERISK # Test if coming from Asterisk route[FROMASTERISK] { if($si==$sel(cfg_get.asterisk.bindip) && $sp==$sel(cfg_get.asterisk.bindport)) return 1; return -1; }

1 0

Ugrade Kamailio 4.0.2 to 4.1.2
by Helena Garcia-Nieto 19 Mar '14

19 Mar '14

Hi! I am not used to manage the software upgrade and I would like to have a more detailed explanation… I've searched in the web and in the mailing list but I need a more step-by-step explanation for newbie that what I found. I downloaded the kamailio version 4.0.1 some time ago (http://www.kamailio.org/pub/kamailio/latest/src/) when it was latest release. I untar it on /opt/kamailio-4.0.2 and did make FLAVOUR=kamailio include_modules="db_mysql " cfg, Make all and make install. Now I would like to upgrade to the 4.1.2 version but I am not sure how. When you say: " just replace the binaries." What do you mean? Should I delete the /opt/kamailio-4.0.2 folder and untar the (http://www.kamailio.org/pub/kamailio/latest/src/) on a new /opt/kamailio-4.1.2 and make again? Should I remove anything else? I have modified the config file, and the kamctlrc to use mysql as dbengine. Then after making it should I execute the sql script for adapting the db? And then connecting it by modifying the config file? I am sorry if that seems a really silly question but I'd appreciate a really step by step guide help! Thanks in advanced Helena -----Original Message----- From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Moritz Graf Sent: jueves, 05 de diciembre de 2013 13:48 To: mohammed alyaseen; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Ugrade Kamailio 4.0.4 to 4.1.0 Hi Medo, just replace the binaries. see http://www.kamailio.org/w/kamailio-v4-1-0-release-notes/ http://www.kamailio.org/wiki/install/4.1.x/git greetz ps i assume u mean [...]to the new version 4.1.0 or Do I [...] Am 05.12.2013 10:29, schrieb mohammed alyaseen: > Hello > > I am using kamailio 4.0.4. I want to change to kamailio 4.1.0. Can the > version 4.0.4 be upgraded to the new version 4.0.4 or Do I have to > uninstall it and install the 4.1.0? > > Thanks in advance > > Medo -- Moritz Graf, B.Sc. Betrieb NGN-Plattform G-FIT GmbH & Co. KG Greflingerstr. 26, 93055 Regensburg Telefon +49 (9 41) 69 85 - 1 86 Telefax +49 (9 41) 69 85 - 2 86 mailto:moritz.graf@g-fit.de http://www.g-fit.de G-FIT Gesellschaft für innovative Telekommunikationsdienste mbH & Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 7626; Geschäftsführer: Dipl.Inf. (FH) Alfred Rauscher

1 0

TLS websocket problem
by jaflong jaflong 19 Mar '14

19 Mar '14

Hi List, Any suggestions on why I am getting the following issues. I can get a successful tls connection when I connect with http Tested by having this in kamailio.cfg event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); xhttp_reply("200", "OK", "text/html","<html><body>Received HTTP request to $hu from [$si:$sp] with protocol $proto</body></html>"); xlog("L_INFO", "HTTP Request Received\n"); ...... Going to https://10.1.2.3:6443 gives this Received HTTP request to / from [10.1.1.1:58179] with protocol tls This seems ok so far. However problems are encounter when trying to connect by WSS. It appears to not accept wss connections. Any ideas please JSSIP settings var configuration = { 'ws_servers': 'wss://10.1.2.3:6443/ws', 'uri': 'sip:webrtc@10.1.2.3', 'stun_servers': '10.1.2.3', 'turn_servers': null, 'register': true, 'password': 'webrtc' ...... Browser Console log JsSIP | UA | configuration parameters after validation: jssip-0.3.0.min.js:11 · via_host: "m3lmqpohnnin.invalid" jssip-0.3.0.min.js:11 · password: "webrtc" jssip-0.3.0.min.js:11 · register_expires: 600 jssip-0.3.0.min.js:11 · register_min_expires: 120 jssip-0.3.0.min.js:11 · register: true jssip-0.3.0.min.js:11 · registrar_server: sip:10.1.2.3 jssip-0.3.0.min.js:11 · ws_server_max_reconnection: 3 jssip-0.3.0.min.js:11 · ws_server_reconnection_timeout: 4 jssip-0.3.0.min.js:11 · connection_recovery_min_interval: 2 jssip-0.3.0.min.js:11 · connection_recovery_max_interval: 30 jssip-0.3.0.min.js:11 · use_preloaded_route: false jssip-0.3.0.min.js:11 · no_answer_timeout: 60000 jssip-0.3.0.min.js:11 · stun_servers: ["stun:10.1.2.3"] jssip-0.3.0.min.js:11 · turn_servers: [] jssip-0.3.0.min.js:11 · trace_sip: false jssip-0.3.0.min.js:11 · hack_via_tcp: false jssip-0.3.0.min.js:11 · hack_ip_in_contact: false jssip-0.3.0.min.js:11 · uri: sip:webrtc@10.1.2.3 jssip-0.3.0.min.js:11 · ws_servers: [{"ws_uri":"wss://10.1.2.3:6443/ws","sip_uri":"<sip:10.1.2.3:6443;transport=ws;lr>","weight":0,"status":0,"scheme":"WSS"}] jssip-0.3.0.min.js:11 · instance_id: "5d2898f4-af42-41cf-865b-848d2ba9a3f2" jssip-0.3.0.min.js:11 · jssip_id: "fagpa" jssip-0.3.0.min.js:11 · hostport_params: "10.1.2.3" jssip-0.3.0.min.js:11 · authorization_user: "webrtc" jssip-0.3.0.min.js:11 JsSIP | EVENT EMITTER | adding event newMessage jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | adding event newRTCSession jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | adding event registrationFailed jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | adding event unregistered jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | adding event registered jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | adding event disconnected jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | adding event connected jssip-0.3.0.min.js:9 JsSIP | UA | user requested startup... jssip-0.3.0.min.js:10 JsSIP | TRANSPORT | connecting to WebSocket wss:/10.1.2.3:6443/ws jssip-0.3.0.min.js:9 s {cache: Object, configuration: Object, dialogs: Object, registrator: null, applicants: Object…} call.html:62 JsSIP | EVENT EMITTER | new listener added to event registered jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | new listener added to event registrationFailed jssip-0.3.0.min.js:9 JsSIP | EVENT EMITTER | new listener added to event newRTCSession jssip-0.3.0.min.js:9 JsSIP | TRANSPORT | WebSocket connection error: [object Event] jssip-0.3.0.min.js:9 JsSIP | TRANSPORT | WebSocket disconnected (code: 1006) jssip-0.3.0.min.js:9 JsSIP | TRANSPORT | WebSocket abrupt disconnection jssip-0.3.0.min.js:9 JsSIP | UA | transport wss://10.1.2.3:6443/ws failed | connection state set to 2 jssip-0.3.0.min.js:11 JsSIP | EVENT EMITTER | emitting event disconnected jssip-0.3.0.min.js:9 JsSIP | UA | next connection attempt in 2 seconds Kamailio [server:default] method = TLSv1 verify_certificate = no require_certificate = no private_key = /usr/local/etc/kamailio/kamailio-selfsigned.key certificate = /usr/local/etc/kamailio/kamailio-selfsigned.pem DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 10.1.1.1 14(17989) DEBUG: <core> [tcp_main.c:1096]: tcpconn_new(): tcpconn_new: on port 50261, type 3 14(17989) DEBUG: <core> [tcp_main.c:1408]: tcpconn_add(): tcpconn_add: hashes: 1825:534:2831, 39 14(17989) DEBUG: <core> [io_wait.h:390]: io_watch_add(): DBG: io_watch_add(0x89af40, 25, 2, 0x7f42527a75b8), fd_no=19 14(17989) DEBUG: <core> [io_wait.h:617]: io_watch_del(): DBG: io_watch_del (0x89af40, 25, -1, 0x0) fd_no=20 called 14(17989) DEBUG: <core> [tcp_main.c:4302]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 1 14(17989) DEBUG: <core> [tcp_main.c:3973]: send2child(): selected tcp worker 2 12(17987) for activity on [tls:10.1.2.3:6443], 0x7f42527a75b8 12(17987) DEBUG: <core> [tcp_read.c:1510]: handle_io(): received n=8 con=0x7f42527a75b8, fd=5 12(17987) DEBUG: tls [tls_server.c:178]: tls_complete_init(): Using TLS domain TLSs<default> 12(17987) DEBUG: tls [tls_domain.c:609]: sr_ssl_ctx_info_callback(): SSL handshake started 12(17987) DEBUG: <core> [tcp_main.c:2556]: tcpconn_do_send(): tcp_send: sending... 12(17987) DEBUG: <core> [tcp_main.c:2590]: tcpconn_do_send(): tcp_send: after real write: c= 0x7f42527a75b8 n=1099 fd=5 12(17987) DEBUG: <core> [tcp_main.c:2591]: tcpconn_do_send(): tcp_send: buf= 12(17987) DEBUG: <core> [io_wait.h:390]: io_watch_add(): DBG: io_watch_add(0x8df1e0, 5, 2, 0x7f42527a75b8), fd_no=1 12(17987) DEBUG: tls [tls_domain.c:621]: sr_ssl_ctx_info_callback(): SSL handshake done 12(17987) DEBUG: tls [tls_domain.c:624]: sr_ssl_ctx_info_callback(): SSL disable renegotiation 12(17987) DEBUG: tls [tls_server.c:348]: tls_accept(): TLS accept successful 12(17987) DEBUG: tls [tls_server.c:355]: tls_accept(): tls_accept: new connection from 10.1.1.1:50261 using TLSv1/SSLv3 AES256-SHA 256 12(17987) DEBUG: tls [tls_server.c:358]: tls_accept(): tls_accept: local socket: 10.1.2.3:6443 12(17987) DEBUG: tls [tls_server.c:369]: tls_accept(): tls_accept: client did not present a certificate 12(17987) DEBUG: <core> [tcp_main.c:2556]: tcpconn_do_send(): tcp_send: sending... 12(17987) DEBUG: <core> [tcp_main.c:2590]: tcpconn_do_send(): tcp_send: after real write: c= 0x7f42527a75b8 n=250 fd=5 12(17987) DEBUG: <core> [tcp_main.c:2591]: tcpconn_do_send(): tcp_send: buf= 12(17987) DEBUG: <core> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7f42527a75b8, FD 5 12(17987) DEBUG: <core> [tcp_read.c:1293]: tcp_read_req(): tcp_read_req: EOF 12(17987) DEBUG: <core> [io_wait.h:617]: io_watch_del(): DBG: io_watch_del (0x8df1e0, 5, -1, 0x10) fd_no=2 called 12(17987) DEBUG: <core> [tcp_read.c:1437]: release_tcpconn(): releasing con 0x7f42527a75b8, state -1, fd=5, id=39 12(17987) DEBUG: <core> [tcp_read.c:1438]: release_tcpconn(): extra_data 0x7f4252793e90 14(17989) DEBUG: <core> [tcp_main.c:3385]: handle_tcp_child(): handle_tcp_child: reader response= 7f42527a75b8, -1 from 2 14(17989) DEBUG: tls [tls_server.c:597]: tls_h_close(): Closing SSL connection 0x7f4252793e90

1 0

Re: [SR-Users] [Kamailio-Users] [Kamalito-Users] Sip MESSAGE
by Peter Reid 19 Mar '14

19 Mar '14

Hi Alex, Please let me make a comment here in support of Abdul Hakeem's comment in respect of Kamailio supporting a SIP to SMPP translation module and in furtherance of this thread (conversation). I believe Kamailio, as an open source community would glean the benefit of supporting a feature that could see better funded players use Kamailio, with SIP to SMPP, as an alternative strategy to supporting proprietary solutions. As networks look towards 4G technology the support of such a feature could see Kamailio used as a gateway between the origination technology and the legacy SMSC gateway. This is a solution, I believe, many will need to consider looking forward. Best Regards, Peter Reid Morodo Operations Director Manager - Mobile Software Development - ET Mob: +34603002300 E-mail: peter.reid(a)morodo.co.uk 04-04-2013 9-12-55Morodo Limited <mailto:support@morodo.co.uk> support(a)morodo.co.uk / <http://www.mo-call.com> www.mo-call.com Place of Registration: Companies House, England & Wales / Registered Office: 7 Breasy Place, 9 Burroughs Gardens Hendon, London NW4 4AU --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

1 0

Query About IMS request fetching
by Muhammad Nadeem 19 Mar '14

19 Mar '14

Hi, I am working on an educational research project, regarding IMS. I want to capture IMS request from IMS client and compare it with my defined rules. If the request satisfy my rules then it will be forwarded to IMS core. Could you please tell me, where i can do changing in IMS server and accomplish my goal. I am currently looking in files on following link. http://svn.berlios.de/svnroot/repos/openimscore/ Thanks in advance -- Best Regards Muhammad Nadeem International Islamic University Islamabad

1 0

Problem with TLS config
by Rene Montilva 19 Mar '14

19 Mar '14

Hi List i'm trying config sip with tls module, my config for module in kamailio.cfg is this: #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #!endif in tls.cfg is this: [server:192.168.1.1:5061] method = SSLv23 verify_certificate = no require_certificate = no private_key = /etc/kamailio/key.pem certificate = /etc/kamailio/cert.pem [client:default] verify_certificate = no require_certificate = no But when a reload kamailio i get the follow error: Mar 18 16:36:50 softswitch /usr/sbin/kamailio[23330]: ERROR: tls [tls_domain.c:906]: load_private_key(): TLSs<default>: Unable to load private key file '/etc/kamailio/cert.pem' Why try to find '/etc/kamailio/cert.pem' for a private key??

2 1

login to siremis failed 'siremis.user' doesn't exist
by malik sherif 18 Mar '14

18 Mar '14

2 3

Redirect, maddr, and domain
by Marc Soda 18 Mar '14

18 Mar '14

I'm trying to handle a redirect with get_redirects(). It seems that Kamailio is ignoring the maddr param on the contact header. Is there a way to force maddr to be used? The Contact header on the 302 looks like this: <sip:2404441112@domain.com:5060 ;maddr=1.1.1.1>;q=0.5,<sip:2404441112@comain.com:5060;maddr=2.2.2.2>;q=0.25 The message is then being sent to domain.com, rather than 1.1.1.1.

3 4

Query About Request Fetching
by Muhammad Nadeem 18 Mar '14

18 Mar '14

Hi, I am working on an educational research project, regarding IMS. I want to capture IMS request from IMS client and compare it with my defined rules. If the request satisfy my rules then it will be forwarded to IMS core. Could you please tell me, where i can do changing in IMS server and accomplish my goal. I am currently looking in files on following link. http://svn.berlios.de/svnroot/repos/openimscore/ Thanks in advance -- Best Regards Muhammad Nadeem Muhammad Ali Jinnah University

1 0

error messages from pv functions
by Juha Heinanen 18 Mar '14

18 Mar '14

in order to avoid scripting errors, it would be nice if pv functions would return an error message when applied to non-applicable pvs. for example, pv_isset() and pv_unset() applied on a script variable. -- juha

1 0

login to siremis failed 'siremis.user' doesn't
by Hugo Servellon 17 Mar '14

17 Mar '14

Hi There, A fast solution would be to re-run the installation procedure. To do so , follow the steps below : a)Remove siremis-4.0.0/siremis/install.lock b)While reinstalling and setting up the database properties , check all of the options available at the bottom of the form . That worked for me , Cheers

2 1

Transfer Problem
by Noriyuki Hayashi 17 Mar '14

17 Mar '14

Hi, Now I am going to use Asterisk-11.7.0 and Kamailio-4.1.1 on CentOS-5.10 x86-64. Backend is PostgreSQL-9.2.6 as Realtime. Conditons, Sip register is working. Extention to Extention is working. Echo test and meetme is fine. Only has the problem is When I Tranfer to other extention number as same context. In this case, Kamilio is using default context transfer is aborted. If anyone has any idea with much appriciated. Thank you. Noriyuki Hayashi Japan

2 1

where does iceserver configuration get set
by jaflong jaflong 17 Mar '14

17 Mar '14

Hi List Is ice settings initiaised on the browser side or Kamailio websocket side? Where are the setting parameters created for a=candidate In the debug I get such logs as a=candidate:3164634682 1 tcp 1509957375 xxx.xxx.xxx.xxx 0 typ host generation 0 a=candidate:3164634682 2 tcp 1509957375 xxx.xxx.xxx.xxx 0 typ host generation 0 a=ice-options:google-ice I am connecting with with jssip like the snippet below. There is nothing set for stun/turn. So how then does it use a=ice-options:google-ice. Does it set google as default var configuration = { .... .... stun_servers: '', turn_servers: null, .... .... }; // User Agent instance var coolPhone = new JsSIP.UA(configuration); Does anyone know are these the only options is relation to ice onfig, stun_servers: turn_servers: null,

1 0

evapi module question
by Alex Balashov 17 Mar '14

17 Mar '14

Hi, Does evapi_relay() have to emit JSON blobs? Or can it be used to emit generic strings? Thanks! -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/

2 1

Endpoint registration tracking and reporting
by Nick Raper 17 Mar '14

17 Mar '14

Hi all, What is the best way to monitor endpoint registrations? When one of our clients has a link failure or for some reason they lose their SIP registration with Kamailio, we'd like to be able to see this so that we can respond and get the trunk re-registered. We do monitor the physical links but endpoints, (usually Asterisk based), often don't re-register after connectivity is restored. I was thinking of a script that dumps the 'location' table every 10 minutes and compares it to the previous 'location' table dump and reports on the changes. Is there a better way of doing this? Regards, [Description: cid:image001.jpg@01C8D7A0.651BD080] Nick Raper 4th Dimension Technology | South Africa Office: +27 21 506 6260 | 24 hour helpline: +27 21 506 6260 | Fax: +27 86 610 5792 Email: nick(a)4dt.co.za<mailto:nick@4dt.co.za> | Web: www.4dt.co.za<http://www.4dt.co.za/> P Please consider the environment before printing this email.

3 4

Softphone cant connect
by aawaise 17 Mar '14

17 Mar '14

Hello, I have deployed a kamailio server. Now I am trying to set up a voip call between two soft phones (EyeBeam) located on local network. I am using "Outbound proxy option" on softphone. It shows "peer to peer mode enabled". Settings are shown in figure attached <http://sip-router.1086192.n5.nabble.com/file/n125931/1.jpg> But when I make a call. It doesnot connect. Using wireshark on kamailio server, I found that in response to "SIP : Request" packet, it sends ICMP packet "Destination Unreachable: Port Unreachable". Firewall is disabled on all concerned systems. What can be the possible reason. Any one will help please. Regards, Awais -- View this message in context: http://sip-router.1086192.n5.nabble.com/Softphone-cant-connect-tp125931.html Sent from the Users mailing list archive at Nabble.com.

1 0

alias behaving differently than droute
by Pete Ashdown 15 Mar '14

15 Mar '14

I presumed that aliases could be used for quickie destination routing, but for some reason my RTP isn't connecting up after. If I put the same alias into droute, it works. Am I understanding aliases wrong?

3 3

sip code and sip reason read only
by Kelvin Chua 14 Mar '14

14 Mar '14

How can i alter at least the sip reason in transit? $rr is read only for example: what i wanted to do is when an egress switch returned, 404 i am ugly i wanted to return this to ingress 404 he is ugly Kelvin Chua

1 1

bug in textops module
by Juha Heinanen 14 Mar '14

14 Mar '14

according to textops readme: 2.1. Kamailio Modules The following modules must be loaded before this module: * sl -- Stateless replies. however, i get these errors if pv module is not loaded before textops module: Mar 14 10:14:52 wheezy1 sip-proxy[4707]: ERROR: <core> [pvapi.c:790]: pv_parse_spec2(): error searching pvar "avp" Mar 14 10:14:52 wheezy1 sip-proxy[4707]: ERROR: <core> [pvapi.c:994]: pv_parse_spec2(): wrong char [s/115] in [$avp(s:rpid)] at [5 (5)] Mar 14 10:14:52 wheezy1 sip-proxy[4707]: ERROR: siputils [rpid.c:73]: init_rpid_avp(): malformed or non AVP $avp(s:rpid) AVP definition Mar 14 10:14:52 wheezy1 sip-proxy[4707]: ERROR: siputils [siputils.c:235]: mod_init(): failed to init rpid AVP name Mar 14 10:14:52 wheezy1 sip-proxy[4707]: ERROR: <core> [sr_module.c:970]: init_mod(): init_mod(): Error while initializing module siputils (/usr/lib/sip-proxy/modules/siputils.so) please fix textops module so that it does not depend on pv module if rpid_avp is not set. -- juha

2 7

SIREMIS redirecting to login prompt issue
by malik sherif 14 Mar '14

14 Mar '14

I configured apache web server and also installed siremis 4.1.1 successfully but i couldn't login and my problem is after " welcome to Siremis installation wizard" I went through steps 1to 4 without issue. On the last step I even receive installation complete congratulation also display username and login password but after 10 seconds it goes back to step 1. I was expecting to see a login window but I am stack. Did anybody experience this issue? Any help greatly appreciated. Thanks Abdulmalik

5 11

Kamailio World 2014 - Interactive sessions
by Daniel-Constantin Mierla 14 Mar '14

14 Mar '14

This year we scheduled more interactive sessions, to reveal better how Kamailio and open source RTC applications can be used out there. During the afternoon of April 2, a group of technical tutorials target to teach how to use various platforms for typical use cases: sip:provider CE, Kamailio for IMS and prepaid systems, SEMS. At the end of April 3, we have the open debate moderated by Randy, the host of weekly VoIP Users Conference. Before noon on April 4, James Body challenges everyone around to do a dangerous demo, impress the audience and win some goodies -- prepare yours in time! More details are presented in the schedule: - http://conference.kamailio.com/k02/schedule/ About two weeks and a half till the start of the event, there is no other meeting alternative in Europe for networking with professionals in large real time communications deployments and open source telephony, be sure you don't miss it. Registration details are available at: - http://conference.kamailio.com/k02/registration/ Credits to event sponsors that ensured a good location and excellent content by participation of world wide speakers - Asipto, FhG Fokus, Sipwise, IT Center, Sipgate, Simwood, Digium, NG Voice, Core Network Dynamics: - http://conference.kamailio.com/k02/sponsors/ See you very soon in Berlin! Meanwhile work on your idea for a dangerous demo! -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference - April 2-4, 2014, Berlin, Germany http://www.kamailioworld.com

1 0

401 after a 302
by Marc Soda 14 Mar '14

14 Mar '14

Can someone tell me how to handle a 401 from a 302 redirect? I am attempting to register with the uac module. Normally, I set a failure route for the 401 and call auc_auth(). In this case, I am receiving a 302, sending the register with get_redirects(), then getting a 401. However, Kamailio seems to be ignoring the 401. I see it in an onrely_route, but not a failure route. failure_route[REG_AUTH] { xlog("L_NOTICE","route[REG_AUTH]\n"); # Handle redirects if ($T_reply_code == 302) { get_redirects("*", "Redirected"); t_on_failure("REG_AUTH"); route(RELAY); } else if ($T_reply_code == 401) { uac_auth(); t_on_reply("REG_REPLY"); route(RELAY); } } route[RELAY] { xlog("L_NOTICE","route[RELAY] ($rm)\n"); 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"); } xlog("L_NOTICE","t_relay()'ing ($rm)\n"); if (!t_relay()) { sl_reply_error(); } exit; } Thanks! Marc

1 1

siremis doesn't works with postgresql
by Rene Montilva 14 Mar '14

14 Mar '14

Hi List i want to config siremis with postgresql and really to much things fail for the install, at the end y left the siremis db with mysql and kamailio with postgresql but the problems continue, when i want to show subscriber list from siremis interface, i get an error and check the postgresql log and found this LOG: sentencia: SET NAMES 'utf8' ERROR: error de sintaxis en o cerca de «`» en carácter 101 SENTENCIA: SELECT T0.id, T0.username, T0.domain, T0.password, T0.email_address, T0.ha1, T0.ha1b, T0.rpid FROM `subscriber` T0 LIMIT 10 what could be the right config?

2 1

Inter domain routing
by Owais ul Haq 14 Mar '14

14 Mar '14

Hello, I have two kamailio servers running independently with different domain names. I want to route calls between those two servers. Can it be done ? If yes then How ? Thanks.

5 6

Soft phone Issue
by Owais ul Haq 14 Mar '14

14 Mar '14

Hello, I have configured a kamailio server on my local network, gave it a dummy domain like "abcd.tk". I have a number of computers on my local network. I want to run eyebeam on them and connect to my kamailio server. Server is running fine. When I try to connect Eyebeam to Server, it goes to DNS to find IP for "abcd.tk". I have entered the value "192.168.1.10 = abcd.tk" in "hosts" file of all machines. File is located at "C:\WINDOWS\system32\drivers\etc\hosts". On other hand, when I ping abcd.tk from client computers. They ping 192.168.1.10. So Operating systems verify the entry "192.168.1.10 = abcd.tk", but problem lies with soft phones. I have tried X-Lite and Eyebeam. How can I make softphone understand that abcd.tk = 192.168.1.10 and please go to this adress, not DNS ?? Help please :( Regards, Awais.

4 3

Softphone not connecting
by Owais ul Haq 14 Mar '14

14 Mar '14

Hello, I have deployed a server. It is starting fine. Connection with MySQL database is also okay. Siremis is also working fine. But softphone "Eyebeam" can't login as a user to the server. Client functionality is ok. As same client with same setting is working good with other kamailio server. How can I trace down the error ?? Please guide. Regards, Owais

2 1

Two kamailio servers sharing database
by Owais ul Haq 14 Mar '14

14 Mar '14

Hello, I have deployed two kamailio servers. Both are sharing a common database deployed on Windows 2008 Server using MySQL. Now domain of one kamailio server is lets say "abc.com" and other's is "xyz.com". I want to know that if a user is created by user id "user1(a)abc.com" with password "qazwsx@123" in the database. And a user try to login from 2nd server "xyz.com" using user id "user1(a)xyz.com" with password "qazwsx@123". Will he able to login using this shared database ? Also please tell which modules controls this ? As I have few more questions also concerning this.

2 1

help with SIP Notify message, to make a endpoint (SPA504G and similar) to reboot.
by Pedro Niño 13 Mar '14

13 Mar '14

Sorry for intruding, but this is puzzling me a lot. I followed the guide to make Kamailio work with asterisk and realtime, Kamailio version 4 and asterisk 11. (http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb ) up until now its working, and now want to get the phones (CISCO SPA504G, former linksys) to get the SIP notify command and reload to get their new config, from the asterisk cli the cli command is "sip notify spa-reboot <username>" The problem is that, using the setup in the guide, the phones registers with kamailio, kamalio then strip the password and register with no password to the asterisk, as supposed to be. by that, when asterisk sends the SIP Notify with the reboot commands, it arrives to the kamailio, and is forwarded to phone, and the phone answers with a '401' and a digest. In the flow, the kamailio (in the middle) receives the 401 and sends again the sip message to asterisk, and asterisk uses the digest to cipher the password and reply, but as asterisk is configured with no password, the reply contains as 'wrong' password (the empty/blank one) is there any way to make kamailio intercepts again that '401' and reply with a crafted message, with the right digest, password, (the one in the ul table) and user, so the phone can accept the order and reboots? The other (ugly) option, is to remove the auth from the phone, for the Sip Provisioning, but that would leave and open door to a reboot attack without auth needed from any IP. And I dont like that option. As we talk, I managed to create a routing logic, but is that the right approach? : =================== request_route { if (is_method("NOTIFY")) { #xlog("NOTIFY received: $rs"); t_on_failure("MANAGE_FAILURE_401"); #try to intercep a 401 } ..... } failure_route[MANAGE_FAILURE_401] { if (t_check_status("401")) { #401 detectado dentro de un Notify, #probablemente ha sido por una orden de reboot. #hay que construir un paquete e intentar enviar, con el digest adecuado.... $uac_req(method)="NOTIFY"; $uac_req(ruri)="sip:"; $uac_req(furi)="sip:"; $uac_req(turi)="sip:"; $uac_req(hdrs)="Contact: <sip:"+ ">\r\n"; #Paquete construido, debe ser enviado uac_req_send(); xlog("401 detectado"); # exit; } =================== Thanks in advance.....

2 2

Problem install siremis and kamailio with postgresql
by Rene Montilva 13 Mar '14

13 Mar '14

Hi list i tried install siremis with postgresql db, but when i was in step 2 and select postgresql driver and fill all the required fields, but i saw siremis installer try to connect to postgresql with www-data user, why this happend

1 0

Bizarre dialog profile tracking behaviour
by Alex Balashov 13 Mar '14

13 Mar '14

Hello, We've got an issue we've been trying to track for days with 'dialog', where the dialogs go through the following life cycle: 1. INVITE --> 2. <-- 407 challenge 3. ACK --> 4. INVITE --> 5. <-- 100 Trying 6. <-- 180 Ringing 7. <-- 183 Session Progress 8. <-- 200 OK 9. ACK --> 10. BYE --> 11. <-- 200 OK Somewhere around steps #6-7 (18x messages), the dialogs no longer appear to be counted in the dialog profile they're attached to, as gleaned from 'kamctl fifo profile_get_size <profile> <key>'. The dialog count in the profile falls to 0. Naturally, I suspected a SIP issue that was preventing the dialog state from being tracked correctly. However, subsequent investigation revealed that these very same dialogs are tracked just fine throughout their entire lifetime. The 'kamctl fifo dlg_list' command shows them to have the right states at the right times. So, the dialog itself isn't going away from tracking. Its attachment to the given profile seems to be the issue. I can't find any logical explanation for this in the code, nor any technical reasoning to support this hypothesis. However, that's what seems to be happening. I'm not sure that this is the issue; it might be another issue masquerading as having this effect. I'm just trying to rule possibilities out. Are there any situations that can cause a dialog that is otherwise being normally tracked to be dumped from a profile of which it was previously part? Thanks! -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/

3 8

Problemas with kamctl ul show - Kamailio 4.1
by Raphael Borges 13 Mar '14

13 Mar '14

Hello, I'm having a problem with the command kamctl ul show, and I do not understand what is happening. On my server when I run just "kamctl ul show" command works fine but when I run "kamctl ul show [<username>]" an error happens. Before when I was using Kamailio 3.1, its work ok. I looked for some documentation and found nothing about this. For example: *$ /home2/local/kamailio/sbin/kamctl ul show* Domain:: location table=512 records=1 max_slot=1 AOR:: 2501 Contact:: sip:2501@192.168.XXX.XXX:5060;transport=udp Q= Expires:: 3594 ... Domain:: aliases table=512 records=0 max_slot=0 *$ /home2/local/kamailio/sbin/kamctl ul show 2501* 404 AOR not found Thanks for Help. Best regards. Raphael

2 6

Reminder: about private emails
by Daniel-Constantin Mierla 12 Mar '14

12 Mar '14

A message sent almost one year ago, but based on volume of private emails related to free support on SIP, Kamailio or other applications, perhaps it is time to refresh, with couple of extra bits for clarification: - http://lists.sip-router.org/pipermail/sr-users/2013-April/077700.html >>> I would like to remind that, at least in my case, writing emails directly without cc-ing the mailing list is not recommended. The rule is also suggested in the mailing lists presentation page: - http://www.kamailio.org/w/mailing-lists/ Unless I asked explicitly for a private email with some specific details, the message will not be noticed and therefore not replied. I use this email address for many public mailing lists and it is intended only for that usage, I am reacting based on the filters I created, unmatched messages getting the lowest priority. There are several common sense as well as technical reasons. Here are some along with other suggestions to improve the likeliness of getting an answer: - we are not answering questions on mailing lists to help only one person, but also other people that may have similar issues in the future -- they can find the answers in the archive with a search engine. Also, other people subscribed to the list can learn from conversation or contribute to the discussion, resulting in better outcome - the amount of unexpected messages is very high -- it is practically a zero chance to get to the folder with messages that didn't match any filter (thus your message is not going to be replied) - whenever I find time, the first emails I answer are those coming on mailing lists. They are many there as well, people are traveling or having other personal or business projects, so sometime is good to send a reminder if a question does not get an answer - starting with negative approach or no technical content, like you are going to use something else if you don't get this instantly, or this application is missing what so ever tutorial giving exactly the solution you need, or simply asking for full config of complex requirements, is not helping at all, but actually making people to ignore your messages. Start with what you tried and where you got stuck. Everything you get is for free, nobody here owe you anything. Therefore, if anyone sent me a private message asking about kamailio or continuing a discussion started on mailing lists, then the messages have to be resent on mailing list if one wants an answer. A quick look in my unfiltered folder revealed hundreds of messages during the past year, soon many will be deleted anyhow. Note that you can always mask sensitive data (e.g., replace passwords, IP addresses) before sending logs or config file. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference - April 2-4, 2014, Berlin, Germany http://www.kamailioworld.com

3 3

trixbox or asterisk as a media server for kamailio
by malik sherif 12 Mar '14

12 Mar '14

I am looking documentation as to how to integrate kamailio and Asterisk, I am not sure if I use the correct term "media server" but I would like to configure 3-way call, call waiting, call transfer , and call forwarding. Your help is greatly appreciated. Thanks Abdul

2 2

Kamailio LCR unable to relay new calls, memory issue
by Camila Troncoso 12 Mar '14

12 Mar '14

Hi, Last Friday I presented a increase of load in kamailio by a client. The load was almost twice as usual. By that time I encountered with many issues in kamailio. The calls were not relay to gateways, and a lot of messages about memory were appearing in log file. Kamailio didn't crash. When I remove the extra traffic all went back to normal. Is there a issue about memory leak or about to few memory resources to manage this amount of traffic? ERROR: tm [t_reply.c:1799]: ERROR: relay_reply: cannot alloc reply shmem ERROR: <core> [msg_translator.c:1782]: ERROR: build_req_buf_from_sip_req: out of memory ERROR: tm [t_fwd.c:431]: ERROR: print_uac_request: no shm mem ERROR: tm [t_fwd.c:1534]: ERROR: t_forward_nonack: failure to add branches ERROR: tm [tm.c:1369]: ERROR: w_t_relay_to: t_relay_to failed ERROR: tm [t_reply.c:598]: ERROR: _reply_light: cannot allocate shmem buffer ERROR: tm [t_msgbuilder.c:371]: ERROR: cannot allocate shared memory ERROR: tm [t_msgbuilder.c:521]: ERROR: build_local_reparse: cannot build ACK request MERROR: tm [t_msgbuilder.c:371]: ERROR: cannot allocate shared memory ERROR: tm [t_msgbuilder.c:521]: ERROR: build_local_reparse: cannot build ACK request ERROR: sl [sl_funcs.c:282]: ERROR: sl_reply_error used: No error (2/SL) ERROR: <core> [msg_translator.c:1782]: ERROR: build_req_buf_from_sip_req: out of memory ERROR: tm [t_fwd.c:431]: ERROR: print_uac_request: no shm mem ERROR: tm [t_fwd.c:1534]: ERROR: t_forward_nonack: failure to add branches ERROR: tm [tm.c:1369]: ERROR: w_t_relay_to: t_relay_to failed ERROR: sl [sl_funcs.c:282]: ERROR: sl_reply_error used: No error (2/SL) ERROR: <core> [sip_msg_clone.c:506]: ERROR: sip_msg_cloner: cannot allocate memory ERROR: tm [t_lookup.c:1338]: ERROR: new_t: out of mem: ERROR: tm [t_lookup.c:1478]: ERROR: t_newtran: new_t failed ERROR: sl [sl_funcs.c:282]: ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL) Regards, Camila *Camila Troncoso Solar **|* Ingeniero de Desarollo +56 2 22408535 *·* +56 9 97327220 | ctroncoso(a)redvoiss.net Badajoz 130, piso 16, Las Condes | Santiago - CHILE | *www.redvoiss.com <http://www.redvoiss.com>*

2 12

Re: [SR-Users] Routing based on destination and source
by Keith 12 Mar '14

12 Mar '14

Hi Yeah I do already use the lcr module for routing to external carriers but is probably a little overkill for what I need to route that traffic internally. Is that my only real option? Cheers Keith

1 0

Kamailio Proxy for Freeswitch
by jay binks 12 Mar '14

12 Mar '14

So im using Kamailio as a load balancer and proxy in-front of a few Freeswitch boxes. Im not going to use RTP Proxy, as my FS boxes will be public on the internet ( Direct RTP connection is fine ). I want ALL SIP to go via Kamailio, but the issue im running into is that the SIP Contact header has the FS IP address in it in some cases. ( 180's etc ) Every bit of documentation I can find about re-writing the Contact header is geared around NAT, and thats not what im trying to do here.. Can anyone give some pointers on how to basically topology hide the FS boxes on the SIP front but leave their IP in the SDP. im going to have the firewalls setup so the SIP Can ONLY come from kamailio, so its quite important I get this all right. Any pointers would be appreciated. Thanks Jay

2 3

(no subject)
by malik sherif 12 Mar '14

12 Mar '14

I send couple of email to Asipto.com about Siremis login issue but I didn't get any response. I configured apache web server and also installed siremis 4.1.1 successfully but i couldn't login and my problem is after " welcome to Siremis installation wizard" I went through step 1to 4 without issue on the last step I even receive installation complete congratulation also display username and login password but after 10 seconds it goes back to step 1. I was expecting to see a login window but I stack. Did anybody experience this issue? or if there is a mailing list, can someone point to the right group. Any help greatly appreciated. Thanks Abdulmalik

2 1

Re: [SR-Users] Routing based on destination and source
by Keith 12 Mar '14

12 Mar '14

Hi all, I am looking for the best module to route calls based on the authenticated user that call came from and the destination number. Is there any current module to do this? Many thanks Keith

2 1

Fail Safe Environment for kamailio
by Owais ul Haq 12 Mar '14

12 Mar '14

Hello, Guys, I need some help. I am tasked to deploy "Fail Safe Architecture" for already running Kamailio Server in our organization. Presently one Kamailio Server is serving the cause with one internet connection and database on MySQL running on Windows 2008 Server R2(which is attached to kamailio server on other LAN card). Now the requirement is to deploy redundancy for internet connection and kamailio server. Like they want two kamailio servers running parallel, so if one fails, other will automatically take over and service will be available to users without any obstruction. At any cost, my organization want to absolutely minimize any possible blackout. To further elaborate my point. Here is the network we want. 2 incoming internet connections to 2 kamailio servers. Both attached to a single database placed at the backend. Now is it possible ?? If not what are constraints ?? What workaround is possible ?? I seriously need help as it is matter of job. Thanking in advance for help. P.S : kamailio server is running of Fedora machine in our environment. Cheers.

3 2

Web interface for kamailio
by malik sherif 11 Mar '14

11 Mar '14

Any recommendation web interface for gathering statistics other than SIREMIS? I installed SIREMIS but unable to resolve login problem and my request for help on ASIPTO didn't get any response also unable to find siremis mailing list. Your help is greatly appreciated. Thanks Abdulmailk

3 4

kamailio 4.1.X and ast 11.8
by lore 11 Mar '14

11 Mar '14

hello folks, i'm really new with kamailio (a couple fo days) and I need some suggestion/samples/idea/HELP to realize my environment. I've been starting to read the docs on website but there are a lot and i don't know where start and which kind of modules need to use I''d like to realize a trunk from kamailio and asterisk. Each one has their own sip users. kamailio sip users are some inside network and some outside network (behind nat) Could someone be son kind to show me the right way to configure kamailio for incoming/ougoing calls from/to asterisk and for using sip peers (behind nat and not)?. Also same samples are really preciated. Thanks a lot in advance Kind regards Lorenzo -- "Chi vive sperando muore cagando ... Lo Russo isoletta dell'Egeo che non conta un cazzo, 1941 ... sono anche un autore"

1 0

milliseconds on $Ts
by Kelvin Chua 11 Mar '14

11 Mar '14

Hi guys, Is there a code somewhere in the project i can reuse to implement milliseconds on $Ts? for example introduce a "$Tms" or a "$TmS" to refer to a pv that stores milliseconds instead of seconds? Kelvin Chua

2 2

how to get value of route param?
by Juha Heinanen 10 Mar '14

10 Mar '14

rr module has check_route_param(re) function that can be used to check if local route header has a param that matches re. however, there does not exist a function to find out what is the value of a given rr param. for example, if route header has param ;param=foo, how to extract value foo of param? there is @rr.uri.params select that together with {param.value,name} transformation might be able to do the job? -- juha

3 3

How to encode domain in username for Asterisk REGISTER forwarding (was: How to configure Kamailio + Asterisk (on same server) to route between several disjoint networks?)
by Alex Villacís Lasso 10 Mar '14

10 Mar '14

On the previous issue (disjoint networks), I eventually settled for binding Asterisk on localhost:5080, and using rtpproxy to route media to the networks as required. The only snag is that I had to write a script to rewrite the Kamailio configuration in order to take current IPs into account. Now, for the same project. What I want now is to be able to express multiple domains with an Asterisk backend. That is: given pbx.company1.com and pbx.company2.com, two DNS addresses that point to the same server, I want to have separate accounts bob(a)pbx.company1.com and bob(a)pbx.company2.com, with separate registration and accounting, without collisions. I know about the Kamailio "domain" module, and I have enabled WITH_MULTIDOMAIN and filled the kamailio.domain table for it to work. Now the authentication is taking domains into account. Next, I want to express two non-colliding registrations for Asterisk. What comes to mind is username rewrite - Kamailio sees bob(a)company1.com, and forwards a REGISTER to Asterisk using bob_company1_com as the SIP username. I am looking right now at the WITH_ASTERISK block that uses the uac module: # Forward REGISTER to Asterisk route[REGFWD] { if(!is_method("REGISTER")) { return; } $var(rip) = $sel(cfg_get.asterisk.bindip); $uac_req(method)="REGISTER"; $uac_req(ruri)="sip:" + $var(rip) + ":" + $sel(cfg_get.asterisk.bindport); $uac_req(furi)="sip:" + $au + "@" + $var(rip) + ":5060"; $uac_req(turi)="sip:" + $au + "@" + $var(rip) + ":5060"; $uac_req(hdrs)="Contact: <sip:" + $au + "@" + $sel(cfg_get.kamailio.bindip) + ":" + $sel(cfg_get.kamailio.bindport) + ">\r\n"; if($sel(contact.expires) != $null) $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $sel(contact.expires) + "\r\n"; else $uac_req(hdrs)= $uac_req(hdrs) + "Expires: " + $hdr(Expires) + "\r\n"; uac_req_send(); } #!endif The above is the non-encoding version. What is the best way to modify it to do a domain encoding in the username? Or, if a better solution exists, what is it?

2 1

Debian init script "log_faiulre_msg"
by Corey Edwards 08 Mar '14

08 Mar '14

There's a typo in the Debian init script. Is this the correct place to report packaging bugs? --- /etc/init.d/kamailio 2014-03-06 13:42:23.000000000 -0700 +++ /tmp/kamailio 2014-03-07 08:41:05.000000000 -0700 @@ -52,7 +52,7 @@ log_failure_msg "Not starting $DESC: invalid configuration file!" log_failure_msg log_failure_msg "$out" - log_faiulre_msg + log_failure_msg exit 1 fi } Corey

3 3

Billing solutions for Kamailio?
by Sergey Kharlamov 07 Mar '14

07 Mar '14

Hi, Can someone recommend me good billing solution for kamailio? Ideally it should contain admin panel, user cabinet etc... -- Sergey Kharlamov

2 1

p-cscf - out of mem
by Daniel Ciprus 07 Mar '14

07 Mar '14

Hi, Has anybody seen this : Mar 2 17:25:16 kamailio kam-pcscf[20741]: ERROR: <core> [msg_translator.c:2011]: generate_res_buf_from_sip_res(): out of mem Mar 2 17:25:16 kamailio kam-pcscf[20741]: ERROR: tm [t_reply.c:1943]: relay_reply(): ERROR: relay_reply: no mem for outbound reply buffer followed by: Mar 2 17:27:03 kamailio kam-pcscf[20741]: ERROR: <core> [msg_translator.c:2011]: generate_res_buf_from_sip_res(): out of mem Mar 2 17:27:03 kamailio kam-pcscf[20741]: ERROR: tm [t_reply.c:1943]: relay_reply(): ERROR: relay_reply: no mem for outbound reply buffer Mar 2 17:27:03 kamailio kam-pcscf[20741]: ERROR: <core> [msg_translator.c:2168]: build_res_buf_from_sip_req(): ERROR: build_res_buf_from_sip_req: out of memory ; needs 386 Mar 2 17:27:53 kamailio kam-pcscf[20741]: ERROR: <core> [parser/contact/contact.c:194]: parse_contacts(): parse_contacts(): No memory left Mar 2 17:27:53 kamailio kam-pcscf[20741]: ERROR: <core> [parser/contact/parse_contact.c:59]: contact_parser(): contact_parser(): Error while parsing contacts Mar 2 17:27:53 kamailio kam-pcscf[20741]: ERROR: <core> [parser/contact/parse_contact.c:88]: parse_contact(): parse_contact(): Error while parsing However, seems like we still had enough mem: [root@kamailio kamailio]# vmstat 1 procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 3 0 0 9526348 230308 13282472 0 0 0 4 0 1 6 0 94 0 0 1 0 0 9526216 230308 13282524 0 0 0 0 1313 84424 17 8 75 0 0 1 0 0 9526092 230308 13282616 0 0 0 0 1482 86882 16 9 75 0 0 [root@kamailio monit.d]# kamailio -v version: kamailio 4.2.0-dev0 (x86_64/linux) 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: unknown compiled on 17:42:42 Dec 18 2013 with gcc 4.4.7 Unfortunately I had to reload p-cscf to get service working again. -- Daniel Ciprus Integration engineer http://www.acision.com 9954 Mayland Dr Suite 3100 Richmond, VA 23233 USA T: +1 804 762 5601 E: daniel.ciprus(a)acision.com<mailto:daniel.ciprus@acision.com> ________________________________ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.

2 6

(no subject)
by malik sherif 07 Mar '14

07 Mar '14

Hello, I am using kamailio 4.1.1, I am wondering if kamailio supports call forwarding , three-way call, and call transfer natively? Does it expect the endpoints to do the RTP mixing? Thanks Absul

3 3

500 Forking capacity exceeded (12/SL)
by Camila Troncoso 07 Mar '14

07 Mar '14

Hi, I´m having problems with kamailio as LCR . I have a route with 14 different gateways, each one with priority 1 and all with the same weight. If one gateway is full, busy, down or answers with any failed response to LCR , I jump to the next gateway in the list. I´m presenting the problem that its stops jumping after 12 gateways and returns the message 500 Forking capacity exceeded (12/SL). I need to increase this limit , so all the gateways in the list give the call a try. Regards, Camila *Camila Troncoso Solar **|* Ingeniero de Desarollo +56 2 22408535 *·* +56 9 97327220 | ctroncoso(a)redvoiss.net Badajoz 130, piso 16, Las Condes | Santiago - CHILE | *www.redvoiss.com <http://www.redvoiss.com>*

3 5

RV: 500 I'm terribly sorry, server error occurred (1/SL)
by Camila Troncoso 07 Mar '14

07 Mar '14

*De:* Camila Troncoso [mailto:ctroncoso@redvoiss.net] *Enviado el:* jueves, 06 de marzo de 2014 16:03 *Para:* sr-users(a)lists.sip-router.org *Asunto:* 500 I'm terribly sorry, server error occurred (1/SL) Hi, I have kamailio 3.2 as LCR with many gateways, weights and priorities. Out of no ware It presented this error today: 500 I'm terribly sorry, server error occurred (1/SL). This wasn't happening for all the calls , and was arbitrary. I read on google ,that this error comes form t_relay, so the server was unable to relay the call to the gateway. But all the gateways are reachable and active. The server was on load , almost 30 cps. The same configuration have been running for more than 2 years with any problem. Could these happened for heavy load? I have children=32 in config file. Has anyone an idea of what may happened? Regards, Camila Troncoso *Camila Troncoso Solar **|* Ingeniero de Desarollo +56 2 22408535 *·* +56 9 97327220 | ctroncoso(a)redvoiss.net Badajoz 130, piso 16, Las Condes | Santiago - CHILE | *www.redvoiss.com <http://www.redvoiss.com>*

1 0

KAMAILIO 4.1.1 Forward SIP REGISTER
by Francesco Maria Magnini 07 Mar '14

07 Mar '14

Hi, I would like to have a Kamailio Registrar/Location server on my private network and another one facing the public side: KAM1 (Private Registrar) <—> KAM2 (Public Proxy) I would like also to configure the proxy in this way: - REGISTRATION TO Public Proxy KAM2 going to Private Registrar KAM1 In the reference guides I’ve seen almost always application specific configuration (WITH_ASTERISK, WITH_FREESWITCH). Basically, how it is possible to forwards REGISTER messages to a generic upstream Registrar? Which modules are involved? I’m using Kamailio 4.1.1 Regards, Francesco

3 4

RPM packages for v4.1.2, v4.0.6 and v3.3.7
by Daniel-Constantin Mierla 07 Mar '14

07 Mar '14

Hello, based on the releases made yesterday, the rpm packages for various Linux distributions are available via opensuse build services - the list of distributions and links to the repositories are published at: - http://www.kamailio.org/wiki/packages/rpms Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference - April 2-4, 2014, Berlin, Germany http://www.kamailioworld.com

1 0

Newbie looking for resources
by richard.seguin＠marisec.ca 07 Mar '14

07 Mar '14

Hi folks, I'm new to Kamailio, and I am looking for some documentation on how to write config files, what should be included... etc.. I'm pretty much looking for product documentation and tutorials, not info on SIP (already went through the sip school). - How do I write a basic config file - Basic auth and forward examples I'm familiar with the cookbooks, however they don't really provide context as to what the recommendations do. Any resources that people could provide would be greatly appreciated. Thanks, Richard Seguin

3 2

500 I'm terribly sorry, server error occurred (1/SL)
by Camila Troncoso 06 Mar '14

06 Mar '14

Hi, I have kamailio 3.2 as LCR with many gateways, weights and priorities. Out of no ware It presented this error today: 500 I'm terribly sorry, server error occurred (1/SL). This wasn't happening for all the calls , and was arbitrary. I read on google ,that this error comes form t_relay, so the server was unable to relay the call to the gateway. But all the gateways are reachable and active. The server was on load , almost 30 cps. The same configuration have been running for more than 2 years with any problem. Could these happened for heavy load? I have children=32 in config file. Has anyone an idea of what may happened? Regards, Camila Troncoso *Camila Troncoso Solar **|* Ingeniero de Desarollo +56 2 22408535 *·* +56 9 97327220 | ctroncoso(a)redvoiss.net Badajoz 130, piso 16, Las Condes | Santiago - CHILE | *www.redvoiss.com <http://www.redvoiss.com>*

1 0

Kamailio v4.1.2 Released
by Daniel-Constantin Mierla 06 Mar '14

06 Mar '14

Hello, Kamailio SIP Server v4.1.2 stable release is out. This is a maintenance release of the latest stable branch, 4.1, that includes fixes since release of v4.1.1. There is no change to database schema or configuration language structure that you have to do on installations of v4.1.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.1.2. For more details about version 4.1.2 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2014/03/kamailio-v4-1-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Kamailio v4.0.6 Released
by Daniel-Constantin Mierla 06 Mar '14

06 Mar '14

Hello, Kamailio SIP Server v4.0.6 stable release is out. This is a maintenance release of the stable branch 4.0, that includes fixes since release of v4.0.5. There is no change to database schema or configuration language structure that you have to do on installations of v4.0.x. Deployments running previous v4.0.x versions are strongly recommended to be upgraded to v4.0.6. For more details about version 4.0.6 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2014/03/kamailio-v4-0-6-released/ Note that 4.0.x is previous stable release series, the latest one is now 4.1.x, with v4.1.2 released today as well. In addition, 3.3.7 was packaged in order to have it included in the new APT repository and make transition to newer versions easier for those still on branch 3.3. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Incorrect IP address in path header
by Rob Moore 06 Mar '14

06 Mar '14

Hi All, So an interesting one here. I'm doing pass through registrations using the dispatcher module in Kamailio and I'm using the Path Module to set the Path header In Register request so that Freeswitch knows to follow the route via Kamailio to find the sipPhone in future. In summary: [SIP Phone]------[NAT]------[(externalip)Kamailio(internalip)]-------[FS-Registrar] The problem I'm having is that the Path header is being added with the external ip address of the Kamailio instance not the internal ip e.g. "Path: sip:(externalip);transport=tcp" which mean FS doesn't root new calls out to the SIPPhone correctly via kamailios internal ip. I have noticed that if I remove the ;transport=tcp from the FS-Register address in my dispatcher group so that the last hop (from kamailio to FS-Register) is done over UDP then the problem corrects itself. (although this does present new issues whilst calling out back along the path from FS, and we also have a prerequisite to use TCP so this doesn't help). Has anyone had any experience of this issue? I can't see what I've done wrong here. Many Thanks Rob

2 2

sqlops crash after out of memory
by Juha Heinanen 06 Mar '14

06 Mar '14

pkg memory run out here: Mar 4 09:00:20 localhost /usr/sbin/sip-proxy[31923]: ERROR: sqlops [sql_api.c:318]: sql_do_query(): no more memory then sip proxy crashed here: (gdb) where #0 0xb5fce89b in sql_reset_result (res=0xb6ce3438) at sql_api.c:233 #1 0xb5fd18db in sql_do_query (con=0xb6cd1e28, query=0xbfecd248, res=0xb6ce3438) at sql_api.c:410 #2 0xb5fd630d in sql_query (msg=0xb6ce8788, dbl=0xb6cd1e28 "\230\035Í¶\t", query=0xb70436a8 "\310Y\004\267P", res=0xb6ce3438 "\245\246=|\r3Î¶\006") at sqlops.c:209 ... goto error was executed when if(res->vals[i]==NULL) was true and at error sql_reset_result was called. there the crash happened here: if(res->vals) { for(i=0; i<res->nrows; i++) { for(j=0; j<res->ncols; j++) { if(res->vals[i][j].flags&PV_VAL_STR && res->vals[i][j].value.s.len>0) /* here */ looks to me that it should be tested if res->vals[i] is not null before executing the if statement. -- juha ps. it there any chance to find out from the core dump, why memory run out, i.e., how was most of it used? amount of pkg memory in this host was defined to be 8 MB. -- juha

2 2

dialog module with DB Backend
by jay binks 06 Mar '14

06 Mar '14

Hi all, im using the dialog module with db_cassandra backend.. I dont believe this issue is related to cassandra, but its worth mentioning anyways. so... I run kamailio, make calls, see dialogs in the DB.. and I Can use "kamctl mi dlg_list" and see that dialogs go away when I hangup a call.. When I query the DB Backend, I still see the queries, but they have a state of 5. I Initially thought this was a bug, but it seems dialogs in state 5 get cleaned up after a period. so I moved on. now , lets restart kamailio.. kamailio loads all dialogs on startup, after kamailio starts I call "kamctl mi dlg_list" again, and it shows all my dialogs from the DB. they DO show as "State 5" but for some reason, these dialogs appear to stick around for a long time, and the bigger issue it causes me is that my channel limiting ( using get_profile_size ) seems to consider these dialogs ( in state 5 ) as being active calls. Please someone point me in the right direction... :) what am I doing wrong ? ( or is this a bug somewhere ) Sincerely Jay

3 12

geoip crash
by Juha Heinanen 06 Mar '14

06 Mar '14

i made a typo in my script and $gip(src=>cc) was referenced before geoip_match() call. the reference resulted in crash. to reproduce, execute statement $var(test) = $gip(src=>cc); as first thing in your script. -- juha

2 17

Releasing 4.1.2, 4.0.6 and 3.3.7
by Daniel-Constantin Mierla 06 Mar '14

06 Mar '14

Hello, we are considering to release new versions from stable branches of Kamailio starting with Thursday, March 6. First is v4.1.2 from latest stable branch and if the time allows in the same day, the v4.0.6. The reason to release v3.3.7 is to have a proper debian packages built and hosted on the new repositories -- the specs had a conflict for latest 3.3 version of some sub-packages. If there are known issues that were not addressed, please report them to the tracker. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference - April 2-4, 2014, in Berlin, Germany http://www.kamailioworld.com

3 4

How to add some text at end of body line with subst_body
by Barthel Marco (CI/AFU1) 05 Mar '14

05 Mar '14

Hi, I'm trying to add some string at the end of some line in the body/sdp of a SIP INVITE for testing some interoperability. The following line a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:NwC8z5MsyCWbpJJo1n2BDS8DkGuUU2cIt9KRUqPU should be converted to a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:NwC8z5MsyCWbpJJo1n2BDS8DkGuUU2cIt9KRUqPU UNENCRYPTED_SRTCP I tried with this: subst_body('/(a=crypto.*)\r/\1 UNENCRYPTED_SRTCP\r/g'); but it does not match just using subst_body('/(a=crypto.*)/\1 UNENCRYPTED_SRTCP/g'); matches but results in this (carriage return between key and "UNENCRYPTED_SRTCP"): a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:NwC8z5MsyCWbpJJo1n2BDS8DkGuUU2cIt9KRUqPU\rUNENCRYPTED_SRTCP using Kamailio 3.3.6 Any ideas? Mit freundlichen Grüßen / Best regards Marco Barthel Robert Bosch GmbH (CI/AFU1) Postfach 30 02 20 70442 Stuttgart GERMANY www.bosch.com<http://www.bosch.com> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Wolf-Henning Scheider, Dr. Werner Struth, Peter Tyroller

2 1

msilo config
by Peter Villeneuve 05 Mar '14

05 Mar '14

Hi, Can someone share a working msilo config for 4.1.1? I've tried following older tutorials out there but they no longer seem to apply. I just want to test out msilo with the default kamailio config in 4.1.1, but the current example in http://kamailio.org/docs/modules/4.1.x/modules/msilo.html doesn't work for me. Specifically, I get an error regarding the syntax in t_on_failure("1"); Any help or pointers appreciated. Thanks

2 5

Incorrect Contact address
by Marc Soda 05 Mar '14

05 Mar '14

I have Kamailio setup as a proxy in front of a backend server (Asterisk). When I make a call through the proxy, the Contact header in the 200 OK that is returned to the client has the IP of the backend server in it. Thus, the client is sending it's ACK directly to the backend server. Is there a special method to rewrite the Contact header to be Kamailio's IP? Where is a good place in the config to do this? (my config is loosely based on this: http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb) Thanks! Marc

4 5

Re: [SR-Users] [Kamailio-Business] [sr-dev] New official Debian and Ubuntu repository
by Vik Killa 05 Mar '14

05 Mar '14

Can someone update the wiki page? I was confused for days on this: http://www.kamailio.org/dokuwiki/doku.php/packages:debs On Wed, Mar 5, 2014 at 8:21 AM, Vik Killa <vipkilla(a)gmail.com> wrote: > Can someone update the wiki page? I was confused for days on this: > http://www.kamailio.org/dokuwiki/doku.php/packages:debs > > > On Tue, Mar 4, 2014 at 6:54 AM, Klaus Darilion < > klaus.mailinglists(a)pernau.at> wrote: > >> Thanks to all involved >> >> >> On 03.03.2014 14:16, Victor Seva wrote: >> >>> The new build system for Debian and Ubuntu packages is now in place. >>> This service is kindly sponsored by SipWise [0] thanks to Andreas >>> Granig [1]. Sipwise is providing the hosting and man power to create >>> and manage this new system. >>> >>> deb.kamailio.org is based on jenkins-debian-glue[2] project running on >>> AWS EC2 environment thanks to Michael Prokop [3] and myself. All the >>> needed files, scripts and info to reproduce this system is kept public >>> at [4]. >>> >>> In [5] is described all the repositories available. >>> >>> * nightly builds are been built if a change is detected in the branch, >>> once by night. >>> - kamailiodev-nightly >>> branch: >>> - 'master' >>> distributions: jessie, wheezy, squeeze, precise >>> >>> - kamailio41-nightly >>> branch: >>> - '4.1' >>> distributions: jessie, wheezy, squeeze, precise >>> >>> - kamailio40-nightly >>> branch: >>> - '4.0' >>> distributions: lenny, squeeze, wheezy, lucid, precise >>> >>> - kamailio33-nightly >>> branch: >>> - '3.3' >>> distributions: lenny, squeeze, wheezy, lucid, precise >>> >>> * tags are been built if a new tag is detected once by night. >>> - kamailio41 >>> branch: >>> - '*/tags/4.1*' >>> distributions: jessie, wheezy, squeeze, precise >>> >>> - kamailio40 >>> branch: >>> - '*/tags/4.0*' >>> distributions: lenny, squeeze, wheezy, lucid, precise >>> >>> - kamailio33 >>> branch: >>> - '*/tags/3.3*' >>> distributions: lenny, squeeze, wheezy, lucid, precise >>> >>> Now there is no 4.1.1 package built so the default kamailio repository >>> is pointing to a empty repository. As soon as we release 4.1.2 this >>> will be fixed. >>> >>> Regards, >>> Victor Seva ( kamailio admin hat on ) >>> >>> [0] http://www.sipwise.com/ >>> [1] http://www.kamailio.org/w/andreas-granig/ >>> [2] https://github.com/mika/jenkins-debian-glue >>> [3] http://michael-prokop.at/ >>> [4] https://github.com/sipwise/kamailio-deb-jenkins >>> [5] http://deb.kamailio.org/index.html >>> >>> _______________________________________________ >>> sr-dev mailing list >>> sr-dev(a)lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev >>> >>> >> _______________________________________________ >> Kamailio (OpenSER) - Business mailing list >> Business(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/business >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/business >> > >

3 3

Reload memory leaks issues.
by Uri Shacked 05 Mar '14

05 Mar '14

Hi, kamailio ver 3.3.6. I load approximately 100Mb of data into memory. And my shared memory size is 4Gb. It is CARRIERROUTE, DIALPLAN, MTREE and HTABLE combimations. My system has to be synced with DB that is being updated frequently. So, I reload the data every 1-2 minutes. I notice that the shared memory usage is increasing at 1% every 18-19 reloads. I use mem_join = 1 and no mem_join at all. I compiled with C_DEFS+= -DMEM_JOIN_FREE and even with -DF_MALLOC. Tried different options, still, the issue keeps on going and it is very frustrating... Anyone has the same problem? BR, Uri

1 1

MSRP Relay
by Nandini madhu 05 Mar '14

05 Mar '14

Dear All, Can anybody please tel me, are there any MSRP relay (RFC 4976) compliant SIP clients for Android Platform ? Sorry for asking this question which is out of relevant here. Waiting for somebody's comments on this Regards, Nandini

1 0

Kamailio World 2014 - Exhibitors
by Daniel-Constantin Mierla 05 Mar '14

05 Mar '14

During Kamailio World 2014, the companies IT Center, Digium, Sipgate, NG Voice, Asipto and FhG Fokus will provide all day long demos and presentations of their products and services. You can contact them in advance to schedule an appointment if you want to reserve proper time to discuss about their offerings: - http://conference.kamailio.com/k02/exhibitors/ It is less than one month till the start of the event, the agenda is pretty much finalized: - http://conference.kamailio.com/k02/schedule/ It has over 30 sessions presented by world wide speakers, from technical tutorials to business use cases, with topics such WebRTC, IMS, anti-fraud & VoIP security, scalability with OpenStack, real time charging, various Kamailio use cases, Asterisk, FreeSwitch and SEMS. Once again we are grateful to event sponsors -- Asipto, FhG Fokus, Sipwise, IT Center, Sipgate, Simwood, Digium, NG Voice -- without their contributions is impossible to bring such an excellent group of speakers and support event logistics: - http://conference.kamailio.com/k02/sponsors/ Hurry up if you don't want to miss this event, it is no alternative in Europe for meeting professionals in large real time communications deployments and open source telephony. Registration details are available at: - http://conference.kamailio.com/k02/registration/ See you in Berlin! -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

invalid xmlrpc response from pkg.stats?
by Juha Heinanen 05 Mar '14

05 Mar '14

i tried make xmlrpc query on pkg.stats, but my xmlrpc lib was not able to parse the response (below). according to xmlrpc spec: The body of the response is a single XML structure, a <methodResponse>, which can contain a single <params> which contains a single <param> which contains a single <value>. according to the spec <value> is scalar value or <struct> or <array>. in sip proxy response below, there a several <struct>s in the <value>, which according to my understanding is violation of the spec. instead, the response should be like this: <?xml version="1.0"?> <methodResponse> <params> <param> <value> <array> <data> <value> <struct>...</struct> </value> <value> <struct>...</struct> </value> ... </data> </array> </param> </methodResponse> comments? -- juha -------------------------------------------------------------------------- Received the following response: HTTP/1.0 200 OK Via: SIP/2.0/TCP 127.0.0.1:36643 Server: OpenXg SIP Proxy (4.1.1-2 (i386/linux)) Content-Length: 6311 <?xml version="1.0"?> <methodResponse> <params> <param> <value><struct><member><name>entry</name><value><int>0</int></value></member><member><name>pid</name><value><int>5846</int></value></member><member><name>rank</name><value><int>0</int></value></member><member><name>used</name><value><int>4553004</int></value></member><member><name>free</name><value><int>559936</int></value></member><member><name>real_used</name><value><int>5731520</int></value></member></struct> <struct><member><name>entry</name><value><int>1</int></value></member><member><name>pid</name><value><int>5848</int></value></member><member><name>rank</name><value><int>1</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>2</int></value></member><member><name>pid</name><value><int>5849</int></value></member><member><name>rank</name><value><int>2</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>3</int></value></member><member><name>pid</name><value><int>5850</int></value></member><member><name>rank</name><value><int>3</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>4</int></value></member><member><name>pid</name><value><int>5851</int></value></member><member><name>rank</name><value><int>4</int></value></member><member><name>used</name><value><int>4557328</int></value></member><member><name>free</name><value><int>554652</int></value></member><member><name>real_used</name><value><int>5736804</int></value></member></struct> <struct><member><name>entry</name><value><int>5</int></value></member><member><name>pid</name><value><int>5852</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556356</int></value></member><member><name>free</name><value><int>556296</int></value></member><member><name>real_used</name><value><int>5735160</int></value></member></struct> <struct><member><name>entry</name><value><int>6</int></value></member><member><name>pid</name><value><int>5853</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556356</int></value></member><member><name>free</name><value><int>556296</int></value></member><member><name>real_used</name><value><int>5735160</int></value></member></struct> <struct><member><name>entry</name><value><int>7</int></value></member><member><name>pid</name><value><int>5854</int></value></member><member><name>rank</name><value><int>4294967294</int></value></member><member><name>used</name><value><int>4563012</int></value></member><member><name>free</name><value><int>549112</int></value></member><member><name>real_used</name><value><int>5742344</int></value></member></struct> <struct><member><name>entry</name><value><int>8</int></value></member><member><name>pid</name><value><int>5857</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556368</int></value></member><member><name>free</name><value><int>556236</int></value></member><member><name>real_used</name><value><int>5735220</int></value></member></struct> <struct><member><name>entry</name><value><int>9</int></value></member><member><name>pid</name><value><int>5863</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4556368</int></value></member><member><name>free</name><value><int>556236</int></value></member><member><name>real_used</name><value><int>5735220</int></value></member></struct> <struct><member><name>entry</name><value><int>10</int></value></member><member><name>pid</name><value><int>5873</int></value></member><member><name>rank</name><value><int>4294967295</int></value></member><member><name>used</name><value><int>4557616</int></value></member><member><name>free</name><value><int>554844</int></value></member><member><name>real_used</name><value><int>5736612</int></value></member></struct> <struct><member><name>entry</name><value><int>11</int></value></member><member><name>pid</name><value><int>5876</int></value></member><member><name>rank</name><value><int>5</int></value></member><member><name>used</name><value><int>4642360</int></value></member><member><name>free</name><value><int>467988</int></value></member><member><name>real_used</name><value><int>5823468</int></value></member></struct> <struct><member><name>entry</name><value><int>12</int></value></member><member><name>pid</name><value><int>5877</int></value></member><member><name>rank</name><value><int>6</int></value></member><member><name>used</name><value><int>4618200</int></value></member><member><name>free</name><value><int>493396</int></value></member><member><name>real_used</name><value><int>5798060</int></value></member></struct> <struct><member><name>entry</name><value><int>13</int></value></member><member><name>pid</name><value><int>5878</int></value></member><member><name>rank</name><value><int>7</int></value></member><member><name>used</name><value><int>4618200</int></value></member><member><name>free</name><value><int>493396</int></value></member><member><name>real_used</name><value><int>5798060</int></value></member></struct> <struct><member><name>entry</name><value><int>14</int></value></member><member><name>pid</name><value><int>5884</int></value></member><member><name>rank</name><value><int>4294967292</int></value></member><member><name>used</name><value><int>4035956</int></value></member><member><name>free</name><value><int>497228</int></value></member><member><name>real_used</name><value><int>5307880</int></value></member></struct> </value> </param> </params> </methodResponse>

2 3

INVITE proxy auth
by Marc Soda 04 Mar '14

04 Mar '14

Hey all, I have a pretty general SIP question that I'm hoping some of you can shed some light on. I hope this ok for the list. I am setting up a SIP proxy with Kamailio. The backend server (Asterisk in my case) requires authentication. Is it standard/best practice to require a proxy to authenticate to a backend server for INVITEs? I am already registering, with authentication, on behalf of the client, i.e, the client registers to the proxy, then the proxy registers to the backend server, all with authentication. I was hoping not to have to do this on INVITEs, but if I don't I'm left with the following: client proxy backend | -------INVITE-------> | | | <--------407--------- | | | ---------ACK--------> | | | ----INVITE(auth)----> | | | <--------100--------- | | | | -------INVITE-------> | | | <--------401--------- | | | ---------ACK--------> | | <--------401--------- | | | ---------ACK--------> | | | ----INVITE(auth)----> | | | <--------100--------- | | | | ----INVITE(auth)----> | | | <--------100--------- | | | <---------OK--------- | | <---------OK--------- | | | ---------ACK--------> | | | | ---------ACK--------> | It works, but, it's terrible... Before I try to make it work differently, what do you all think it should do? Marc

2 1

New official Debian and Ubuntu repository
by Victor Seva 04 Mar '14

04 Mar '14

The new build system for Debian and Ubuntu packages is now in place. This service is kindly sponsored by SipWise [0] thanks to Andreas Granig [1]. Sipwise is providing the hosting and man power to create and manage this new system. deb.kamailio.org is based on jenkins-debian-glue[2] project running on AWS EC2 environment thanks to Michael Prokop [3] and myself. All the needed files, scripts and info to reproduce this system is kept public at [4]. In [5] is described all the repositories available. * nightly builds are been built if a change is detected in the branch, once by night. - kamailiodev-nightly branch: - 'master' distributions: jessie, wheezy, squeeze, precise - kamailio41-nightly branch: - '4.1' distributions: jessie, wheezy, squeeze, precise - kamailio40-nightly branch: - '4.0' distributions: lenny, squeeze, wheezy, lucid, precise - kamailio33-nightly branch: - '3.3' distributions: lenny, squeeze, wheezy, lucid, precise * tags are been built if a new tag is detected once by night. - kamailio41 branch: - '*/tags/4.1*' distributions: jessie, wheezy, squeeze, precise - kamailio40 branch: - '*/tags/4.0*' distributions: lenny, squeeze, wheezy, lucid, precise - kamailio33 branch: - '*/tags/3.3*' distributions: lenny, squeeze, wheezy, lucid, precise Now there is no 4.1.1 package built so the default kamailio repository is pointing to a empty repository. As soon as we release 4.1.2 this will be fixed. Regards, Victor Seva ( kamailio admin hat on ) [0] http://www.sipwise.com/ [1] http://www.kamailio.org/w/andreas-granig/ [2] https://github.com/mika/jenkins-debian-glue [3] http://michael-prokop.at/ [4] https://github.com/sipwise/kamailio-deb-jenkins [5] http://deb.kamailio.org/index.html

4 3

Re: [SR-Users] Regd. Stored procedure support in Kamailio
by Alex Balashov 04 Mar '14

04 Mar '14

You can executed any SQL statements you want through 'sqlops', including invocation of stored procedures. Our Kamailio-based Class 4 routing/trunking product is built almost entirely on Postgres stored procedures. We have dozens of them. As to whether they are "really needed", I don't know how to answer that. :-) In our case, we decided they were really needed because they offer the opportunity to execute complex business logic beyond what Kamailio's relatively primitive route scripting language can offer, while eliminating unnecessary back-and-forth data interchange between Kamailio and the database. Stored procedures and triggers also execute in a transactional manner, which is additionally beneficial. Shankar <shankar.rk(a)plintron.com> wrote: >Hello All, > > > >Does Kamailio support invoking stored procedures instead of sending >plain DB >queries already? > > > >We have been asked to migrate to stored procedures. I am trying to >estimate >the effort involved in migrating Kamailio code to support stored >procedure. > > > >Other question that comes to my mind is whether stored procedures are >really >needed in Kamailio. Can someone please clarify? > > > >Regards, > >Shankar > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >sr-users(a)lists.sip-router.org >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard. Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0671 Web: http://www.evaristesys.com/, http://www.alexbalashov.com

1 0

Regd. Stored procedure support in Kamailio
by Shankar 04 Mar '14

04 Mar '14

Hello All, Does Kamailio support invoking stored procedures instead of sending plain DB queries already? We have been asked to migrate to stored procedures. I am trying to estimate the effort involved in migrating Kamailio code to support stored procedure. Other question that comes to my mind is whether stored procedures are really needed in Kamailio. Can someone please clarify? Regards, Shankar

1 0

REGISTER failure_route 401 problem
by Marc Soda 03 Mar '14

03 Mar '14

I have a Kamailio server setup which is registers to a back end server on behalf of endpoints. The endpoints can register to Kamailio but Kamailio is failing to register to the server when I put a NAT device in front of it. Without the NAT device it works fine. The problem is the 401 that comes back seems to be ignored by Kamailio. I have a failure route setup to auth, but it is never hit. I see the 401 in onrely_route, but not the failure_route. I'm assuming it's a NAT issue because removing the device fixes the issue. Anyone have any ideas? The 401 being ignored: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.0.10.11;branch=z9hG4bKe5d6.178378f7.0;received=198.XXX.XXX.XXX Via: SIP/2.0/UDP 127.0.0.1:12354 ;rport=6545;received=198.XXX.YYY.YYY;branch=z9hG4bK-1879-1-3 From: <sip:sip7878_spqa@64.YYY.YYY.YYY>;tag=1 To: <sip:sip7878_spqa@64.YYY.YYY.YYY>;tag=as00e32130 Call-ID: 1-1879(a)127.0.0.1 CSeq: 2 REGISTER User-Agent: CoreDialPBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces WWW-Authenticate: Digest algorithm=MD5, realm="fe-c7c5-9o.domain.com", nonce="151e4f60" Content-Length: 0 Thanks, Marc

2 6

usrloc preload
by Victor V. Kustov 03 Mar '14

03 Mar '14

Hi all! Please give expanded tips about usrloc preload(). What exactly it doing? modparam("usrloc", "db_mode", 0) modparam("usrloc", "preload", "location") This case kamailio load from db on startup and operate in memory after? -- WBR, Victor JID: coyote(a)bks.tv JID: coyote(a)bryansktel.ru I use FREE operation system: 3.12.9-calculate GNU/Linux

3 5

Ubuntu precise apt repositories unavailable
by Josef Stautner 03 Mar '14

03 Mar '14

Goor morning community, I received a notification that the repositories for Ubuntu Precise are not available anymore. /W: Failed to fetch //http://deb.kamailio.org/kamailio/dists/precise/Release.gpg// Could// //not connect to deb.kamailio.org:80 (87.106.140.63). - connect (110: Connection timed out)// / / //W: Failed to fetch //http://deb.kamailio.org/kamailio/dists/precise/main/source/Sources//// //Unable to connect to deb.kamailio.org:http:// / / //W: Failed to fetch// / /http://deb.kamailio.org/kamailio/dists/precise/main/binary-i386/Packages// Unable to// //connect to deb.kamailio.org:http:// / / //W: Failed to fetch// / /http://deb.kamailio.org/kamailio/dists/precise/main/i18n/Translation-en_US// Unable to// //connect to deb.kamailio.org:http:// / / //W: Failed to fetch// / /http://deb.kamailio.org/kamailio/dists/precise/main/i18n/Translation-en// Unable to// //connect to deb.kamailio.org:http:// / After I tried manually to fetch new updates I got a connection and downloaded some data but then the connection timed out. Is this just a temporary probleme and are there any fallback mirrors? Thanks in advance Josef Stautner

2 2

Adding Path header for the current request.
by MAXX ... 02 Mar '14

02 Mar '14

I found the solution myself, anyone having a similar issue in the future can use msg_apply_changes() from textopsx module after append_hf line.

1 0

Adding Path header for the current request.
by MAXX ... 02 Mar '14

02 Mar '14

Hello, I need to add a Path header to the current request so the save method of registrar module will save the location with the path value to the db. I made the necessary settings for the registrar module but I couldn't be able to add the header. Neither "append_hf" nor "add_path" of path module works since they don't add the header to the currently processing request. $hdr pseudovariable is readonly so I couldn't modify it as well. What can I do to make this happen? Also the reason I need this is to let people registered to different registrars to be able to call each other via their current tls connections to their respective registrars. Thanks In Advance.

1 0

XAVP in 3.1.6
by Jijo 01 Mar '14

01 Mar '14

Hi I'm trying to use XAVP but the script is showing parsing error. Do i need to include any module? I rebuild kamailio using the flag WITH_XAVP but didn' help. route[0] { $xavp(a=>bar) = 'bar'; } S-154:~ # /usr/sbin/kamailio -c -f /etc/kamailio/kam86x2.cfg loading modules under /usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/ 0(20184) ERROR: <core> [pvapi.c:516]: error searching pvar "xavp" 0(20184) ERROR: <core> [pvapi.c:720]: wrong char [a/97] in [$xavp(a=>bar)] at [6 (5)] 0(20184) : <core> [cfg.y:3461]: parse error in config file /etc/kamailio/kam86x2.cfg, line 555, column 5-17: unknown script pseudo variable $xavp(a=>bar) ERROR: bad config file (1 errors) Segmentation fault (core dumped) S-154:~ # /usr/sbin/kamailio -V version: kamailio 3.1.6 (i386/linux) af51bc flags: STATS: Off, USE_IPV6, 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, PKG_SIZE 25MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: af51bc compiled on 14:11:43 Feb 28 2014 with gcc 4.7.1 THANKS

1 0

How to configure Kamailio + Asterisk (on same server) to route between several disjoint networks?
by Alex Villacís Lasso 01 Mar '14

01 Mar '14

As part of a project, I have installed a CentOS 6 test system (a virtual machine) with Asterisk 11.7.0 and Kamailio 4.1.1 downloaded from http://download.opensuse.org/repositories/home:/kamailio:/telephony/CentOS_…. I am trying to setup a combination of Kamailio and Asterisk that will route SIP calls between all the configured networks in the test setup, in addition to being capable of using Asterisk in order to handle PSTN and IAX2 calls. I am using the following online guide to modify my kamailio.cfg: http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb . Based on this, I generated the attached patch for my Kamailio configuration My test setup has the following network interfaces: eth0: 10.1.0.3, on network 10.1.0.0/24 eth1: 192.168.5.18, on network 192.168.0.0/16 eth2: 10.0.0.2, on network 10.0.0.0/24 lo: 127.0.0.1, on network 127.0.0.0/8 I first configured Asterisk with SIP realtime support (with no Kamailio), and tested that all configured accounts could register from all interfaces, and that Asterisk could properly route media between any two disjoint networks. After installing Kamailio, the guide called for disabling Asterisk SIP authentication by setting passwords to NULL, and moving Asterisk SIP to a different port (I chose 5080) so that Asterisk and Kamailio could run on the same machine. At this point, the SIP clients (one softphone and one VoIP phone) can now register at port 5080 without authentication. In the process of changing my Kamailio configuration according to the attached patch, the guide says that I should configure the IP of the network interface as the value of asterisk.bindip and kamailio.bindip. After performing all required changes, Kamailio does take over authentication at the default port of 5060. Testing shows that for all SIP clients with IPs belonging to the same network as the configured asterisk.bindip, both registration and media exchange work correctly, and that the SIP clients are still capable of calling into the Asterisk dialplan, and therefore, routing into Asterisk resources. For SIP clients in disjoint networks, the failure mode depends on whether mhomed is enabled or disabled in kamailio.cfg. For mhomed=0 (or unset), I have the following situation between the two SIP clients (one at 10.1.0.1, the other at 10.0.0.3), as shown by "sip show peers" in Asterisk (when asterisk.bindip is set to 192.168.5.18): Privilege escalation protection disabled! See https://wiki.asterisk.org/wiki/x/1gKfAQ for more details. Name/username Host Dyn Forcerport ACL Port Status Description Realtime gatitoscomx64am_100/gatit 10.1.0.3 D N A 5060 OK (16 ms) Cached RT gatitoscomx64am_101/gatit 10.0.0.2 D N A 5060 OK (36 ms) Cached RT gatitoscomx64am_IM101 (Unspecified) D N A 0 UNREACHABLE Cached RT 3 sip peers [Monitored: 2 online, 1 offline Unmonitored: 0 online, 0 offline] If I try to call from one SIP client to an extension in the Asterisk dialplan that does NOT map to a SIP client in a disjoint network, the media exchange works (with negotiatied media IP in the same network as the SIP client), regardless of whether the calling client belongs in the same network as asterisk.bindip. If I try to call from the same SIP client to an extension that maps to a SIP client in a disjoint network, the call fails, and I get the spoken message about the user at extension such-and-such being unavailable. Additionally, I get the following error message in the Asterisk logs: [Feb 25 16:53:14] NOTICE[13807][C-00000003] chan_sip.c: Call from 'gatitoscomx64am_101' (10.0.0.2:5060) to extension 'gatitoscomx64am_101' rejected because extension not found in context 'gatitoscomx64am-from-internal'. For mhomed=1, the output of "sip show peers" changes to the following (when asterisk.bindip is set to 192.168.5.18): Privilege escalation protection disabled! See https://wiki.asterisk.org/wiki/x/1gKfAQ for more details. Name/username Host Dyn Forcerport ACL Port Status Description Realtime gatitoscomx64am_100/gatit 192.168.5.18 D N A 5060 OK (19 ms) Cached RT gatitoscomx64am_101/gatit 192.168.5.18 D N A 5060 OK (34 ms) Cached RT gatitoscomx64am_IM101 (Unspecified) D N A 0 UNREACHABLE Cached RT 3 sip peers [Monitored: 2 online, 1 offline Unmonitored: 0 online, 0 offline] From wireshark sniffing, I can see that the SDP payload sent from the client to Kamailio contains the IP address of the client, which is accessible by both Kamailio and Asterisk. However, the SDP payload in the OK response sent back to the client contains a media port with the IP address of asterisk.bindip (the one that appears in the "Host" column in the "sip show peers" report), not the IP address of the interface that received the INVITE. This results in broken media negotiation for all SIP clients belonging to networks other than the one that contains asterisk.bindip. In either case, I have to hardcode an IP address in kamailio.cfg, which is not satisfactory. IPs assigned to interfaces can and do change, especially if the interface is managed with DHCP. To escape this, I tried setting asterisk.bindip to 127.0.0.1, but since apparently localhost is also a disjoint network, all of the above described problems apply. Related to these issues, I am not satisfied with leaving Asterisk running unauthenticated SIP at the nonstandard port. Somebody suggested blocking the port with iptables, but I do not want to rely on this alone. I tried setting bindaddr=127.0.0.1 so that only Kamailio gets to talk to Asterisk, but this also has the side effect of restricting the media negotiation to localhost only. I am asking for help in building a Kamailio/Asterisk configuration that will support all of the networks and route media between all of them, just as if Asterisk were the only program running. Ideally, the configuration should not encode the current IP of any interface (except, maybe, localhost). What is the official name (if any) for the setup I am describing above? Does it have a standard setup procedure? How is Asterisk secured so that clients cannot bypass authentication using the Asterisk SIP port directly?

2 4

Replacing an ACME Packet Net-Net SBC
by Francesco Maria Magnini 01 Mar '14

01 Mar '14

Hi, I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly: - it is used as a SIP endpoint for SIP client registrations - it is used as a SIP endpoint for interconnection to multiple SIP carriers via SIP trunks - it is used for NAT traversal In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?

13 22

prevent relaying to myself
by Henry Fernandes 01 Mar '14

01 Mar '14

Is there a way to prevent relaying requests to myself in route[RELAY]? -H

3 3

fresh kamailio installation unable to connect through jitsi
by Michelle Jun 01 Mar '14

01 Mar '14

hi i just finished installation of kamailio on centos 6 64 bit following the docs on http://www.fredposner.com/voip/1457/kamailio-behind-nat/ the user able to chat through jitsi just fine, but when calling, one user able to connect, while the other showing only "connecting" (audio/video) any idea what did i do wrong? here is the /var/log./messages thank you Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session 2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0, tag 2d9e2107;1 requested, type strong Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session on a port 25982 created, tag 2d9e2107;1 Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: pre-filling caller's address with 192.168.168.1:5000 Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session 2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0, tag 2d9e2107;2 requested, type strong Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: new session on a port 25192 created, tag 2d9e2107;2 Feb 26 17:43:34 black96 rtpproxy[4293]: INFO:handle_command: pre-filling caller's address with 192.168.168.1:5002 Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: pre-filling callee's address with 192.168.168.1:5000 Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: pre-filling callee's address with 192.168.168.1:5002 Feb 26 17:43:39 black96 /usr/local/sbin/kamailio[4456]: NOTICE: acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1393465419;method=INVITE;from_tag=2d9e2107;to_tag=7175e4ad;call_id=2f6e045de764ae9e9252352d952359ae@0 :0:0:0:0:0:0:0;code=200;reason=OK;src_user=handy;src_domain=184.105.148.231;src_ip=192.168.168.1;dst_ouser=harri;dst_user=harri;dst_domain=192.168.113.2 Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:39 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:43:40 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:40 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:43:42 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25982/27044, session timer restarted Feb 26 17:43:42 black96 rtpproxy[4293]: INFO:handle_command: lookup on ports 25192/22432, session timer restarted Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:process_rtp: session timeout Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: session on ports 25982/27044 is cleaned up Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:process_rtp: session timeout Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped Feb 26 17:44:43 black96 rtpproxy[4293]: INFO:remove_session: session on ports 25192/22432 is cleaned up Feb 26 17:45:23 black96 rtpproxy[4293]: INFO:handle_command: delete request failed: session 2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0, tags 2d9e2107/7175e4ad not found Feb 26 17:45:53 black96 /usr/local/sbin/kamailio[4460]: NOTICE: acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1393465553;method=BYE;from_tag=2d9e2107;to_tag=7175e4ad;call_id=2f6e045de764ae9e9252352d952359ae@0:0:0:0:0:0:0:0;code=408;reason=Request Timeout;src_user=handy;src_domain=184.105.148.231;src_ip=192.168.168.1;dst_ouser=harri;dst_user=;dst_domain=184.105.148.231

3 7

What is required to enable TLS on non-standard port?
by info＠vintageelectronics.ca 01 Mar '14

01 Mar '14

Kamailio running in Fedora 19 box. The client (Jitsi) can only connect over TCP. If connecting over UDP, the clients connect, but cannot send/receive messages. Cannot connect over TLS at all. Ultimately I will need to run with TLS over 5065 port or higher. Tried using different listen directives, different port directive, but kamailio either does not start, or only listening on one TCP port. I've set up two SRV records, one for _sip on port 5065 and another for _sips on port 5066. Both pointing to the Fedora box. In Jitsi I have to specify port # and when I set it to 5065 over TCP it works, but 5066 over TLS never connects. What am I doing wrong? Thank you.

3 8

Kamailio crashes with double qm_free
by Tuan Viet Nguyen 28 Feb '14

28 Feb '14

Hello, I have another kamailio crash with 4.1.1. The scenario is simple: + call a number, fail + retry on another peer, fails In this case, I use t_reply("404", "Not found") then exit. It seems that we have a double qm_free. Log file Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29595]: WARNING: tm [t_lookup.c:1536]: t_unref(): WARNING: script writer didn't release transaction Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29583]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f9dedb3e110), called from tm: h_table.c: free_cell(157), first free tm: h_table.c: free_cell(157) - aborting Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29627]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 19 Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29576]: ALERT: <core> [main.c:775]: handle_sigs(): child process 29583 exited by a signal 6 Feb 28 13:15:56 kamailio23 /usr/local/sbin/kamailio[29576]: ALERT: <core> [main.c:778]: handle_sigs(): core was generated core.kamailio.29583 (gdb) bt full #0 0x00007f9df6afb475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f9df6afe6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x0000000000548253 in qm_free (qm=0x7f9ded878000, p=0x7f9dedb3e110, file=0x7f9df515b62d "tm: h_table.c", func=0x7f9df515b7d8 "free_cell", line=157) at mem/q_malloc.c:470 f = 0x7f9dedb3e0e0 size = 140316274568736 next = 0x0 prev = 0x0 __FUNCTION__ = "qm_free" #3 0x00007f9df50ee2b3 in free_cell (dead_cell=0x7f9dedb39490) at h_table.c:157 b = 0x0 i = 2 rpl = 0x0 tt = 0x177dd596e30 foo = 0x7fffdd597400 cbs = 0x7f9dedb39490 cbs_tmp = 0x7fffdd596f10 __FUNCTION__ = "free_cell" #4 0x00007f9df511c662 in t_unref (p_msg=0x7f9df68bfdb0) at t_lookup.c:1546 kr = 12 __FUNCTION__ = "t_unref" #5 0x00007f9df5146f4d in w_t_unref (foo=0x7f9df68bfdb0, flags=2147483649, bar=0x0) at tm.c:765 No locals. #6 0x00000000004d6f27 in exec_post_script_cb (msg=0x7f9df68bfdb0, type=REQUEST_CB_TYPE) at script_cb.c:195 cb = 0x7f9df68a97d0 flags = 2147483649 #7 0x00000000004a6e24 in receive_msg (buf=0x921620 "ACK sip:0123456789@10.100.8.7 SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.8.94;branch=z9hG4bKbcd8.9b0d4b2682a07fefaa22406761659624.0\r\nMax-Forwards: 15\r\nFrom: \"via_test\" <sip:0310193301@10.100.8.12>;tag=as4d03043"..., len=375, rcv_info=0x7fffdd5970d0) at receive.c:228 msg = 0x7f9df68bfdb0 ctx = {rec_lev = -581341280, run_flags = 32767, last_retcode = 5, jmp_env = {{__jmpbuf = {8857080, 0, 0, 0, 0, 140316433164786, 17179869189, 0}, __mask_was_saved = 8856992, __saved_mask = {__val = {1, 140316271892032, 1656210553, 3713626240, 1024, 8008593472, 140316271892032, 140736907014208, 5472467, 1577608202, 140316271892032, 50195, 140316271892032, 140316426284544, 8282899704, 140736907014272}}}}} ret = 0 inb = {s = 0x921620 "ACK sip:0123456789@10.100.8.7 SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.8.94;branch=z9hG4bKbcd8.9b0d4b2682a07fefaa22406761659624.0\r\nMax-Forwards: 15\r\nFrom: \"via_test\" <sip:0310193301@10.100.8.12>;tag=as4d03043"..., len = 375} __FUNCTION__ = "receive_msg" #8 0x000000000053c0d8 in udp_rcv_loop () at udp_server.c:536 len = 375 buf = "ACK sip:0123456789@10.100.8.7 SIP/2.0\r\nVia: SIP/2.0/UDP 10.100.8.94;branch=z9hG4bKbcd8.9b0d4b2682a07fefaa22406761659624.0\r\nMax-Forwards: 15\r\nFrom: \"via_test\" <sip:0310193301@10.100.8.12>;tag=as4d03043"... tmp = 0x13e0751a0eb8aa4f <Address 0x13e0751a0eb8aa4f out of bounds> from = 0x7f9df68a5408 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {1577608202, 4290224}, addr32 = {1577608202, 0, 4290224, 0}, addr16 = {25610, 24072, 0, 0, 30384, 65, 0, 0}, addr = "\nd\b^\000\000\000\000\260vA\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = { 117990410, 0}, addr32 = {117990410, 0, 0, 0}, addr16 = {25610, 1800, 0, 0, 0, 0, 0, 0}, addr = "\nd\b\a", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\304\nd\b^\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 1577608202}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1577608202, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7f9df6704da8, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #9 0x000000000046ec98 in main_loop () at main.c:1617 i = 5 pid = 0 si = 0x7f9df6704da8 si_desc = "udp receiver child=5 sock=10.100.8.7:5060\000\000\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000y\304\267b\000\000\000\000\260vA\000\000\000\000\000\000tY\335\377\177", '\000' <repeats 18 times>, "@rY\335\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #10 0x0000000000471c38 in main (argc=5, argv=0x7fffdd597408) at main.c:2533 cfg_stream = 0x164c010 c = -1 r = 0 tmp = 0x7fffdd597438 "\211~Y\335\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 4192398120 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" core.kamailio.29576 (gdb) bt full #0 0x00007f9df6afb475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f9df6afe6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x0000000000548253 in qm_free (qm=0x7f9ded878000, p=0x7f9dedb3e110, file=0x7f9df515b62d "tm: h_table.c", func=0x7f9df515b7d8 "free_cell", line=157) at mem/q_malloc.c:470 f = 0x7f9dedb3e0e0 size = 140316274568736 next = 0x0 prev = 0x0 __FUNCTION__ = "qm_free" #3 0x00007f9df50ee2b3 in free_cell (dead_cell=0x7f9dedb39490) at h_table.c:157 b = 0x7f9df464b480 "dialog: dlg_cb.c" i = 0 rpl = 0x7f9df464b8e0 tt = 0x7f9df4a8cc75 foo = 0x5000548a29 cbs = 0xd000000001 cbs_tmp = 0x1edb086c8 __FUNCTION__ = "free_cell" #4 0x00007f9df50ef480 in free_hash_table () at h_table.c:441 p_cell = 0x7f9dedb39490 tmp_cell = 0x7f9deda23d90 i = 36299 __FUNCTION__ = "free_hash_table" #5 0x00007f9df5102d35 in tm_shutdown () at t_funcs.c:122 __FUNCTION__ = "tm_shutdown" #6 0x00000000004f8101 in destroy_modules () at sr_module.c:817 t = 0x7f9df670fd50 foo = 0x7f9df670f588 __FUNCTION__ = "destroy_modules" #7 0x00000000004689b2 in cleanup (show_status=1) at main.c:560 memlog = 32669 __FUNCTION__ = "cleanup" #8 0x0000000000469aab in shutdown_children (sig=15, show_status=1) at main.c:702 __FUNCTION__ = "shutdown_children" #9 0x000000000046b146 in handle_sigs () at main.c:793 chld = 0 chld_status = 134 memlog = 0 __FUNCTION__ = "handle_sigs" #10 0x000000000046f549 in main_loop () at main.c:1746 i = 8 pid = 29627 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000y\304\267b\000\000\000\000\260vA\000\000\000\000\000\000tY\335\377\177", '\000' <repeats 18 times>, "@rY\335\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x0000000000471c38 in main (argc=5, argv=0x7fffdd597408) at main.c:2533 cfg_stream = 0x164c010 c = -1 r = 0 tmp = 0x7fffdd597438 "\211~Y\335\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 4192398120 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" Thanks for your help

2 2

kamailio crashes
by Tuan Viet Nguyen 28 Feb '14

28 Feb '14

Hello, I have a crash with the following scenario: I try to route an INVITE to a remote host, it fails, I route to the second suing the dispatcher module. It fails the second time and I stop the call. It seems that I did not release the transaction in this case 93454 Feb 28 11:39:08 kamailio23 /usr/local/sbin/kamailio[20225]: WARNING: tm [t_lookup.c:1536]: t_unref(): WARNING: script writer didn't release transaction And then, Kamailio receives BYE of other dialogs and it crashes Here is core bt of 2 kamailio processes (4.1.1) (gdb) bt full #0 0x0000000000534e4e in timer_list_expire (t=1283469267, h=0x7ff9219e99b8, slow_l=0x7ff9219e9c88, slow_mark=12) at timer.c:883 tl = 0x7ff921c6b8f0 ret = 32767 #1 0x00000000005351ba in timer_handler () at timer.c:959 saved_ticks = 1283469267 run_slow_timer = 0 i = 12 __FUNCTION__ = "timer_handler" #2 0x0000000000535453 in timer_main () at timer.c:998 No locals. #3 0x000000000046efa2 in main_loop () at main.c:1688 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000\243Mgf\000\000\000\000\260vA\000\000\000\000\000\020\201\351a\377\177", '\000' <repeats 18 times>, "P\177\351a\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #4 0x0000000000471c38 in main (argc=5, argv=0x7fff61e98118) at main.c:2533 cfg_stream = 0x1970010 c = -1 r = 0 tmp = 0x7fff61e98148 "\211\236\351a\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 519948236 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" (gdb) bt full #0 0x00007ff92abf3475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007ff92abf66f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x0000000000548253 in qm_free (qm=0x7ff921970000, p=0x7ff921c3b940, file=0x7ff92925362d "tm: h_table.c", func=0x7ff9292537d8 "free_cell", line=178) at mem/q_malloc.c:470 f = 0x7ff921c3b910 size = 5600 next = 0x7fff61e97ac0 prev = 0x7ff9291e571e __FUNCTION__ = "qm_free" #3 0x00007ff9291e64a9 in free_cell (dead_cell=0x7ff921c6b870) at h_table.c:178 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x5000548a29 cbs = 0x0 cbs_tmp = 0x7ff921c3b940 __FUNCTION__ = "free_cell" #4 0x00007ff9291e7480 in free_hash_table () at h_table.c:441 p_cell = 0x7ff921c6b870 tmp_cell = 0x7ff921a159f0 i = 37066 __FUNCTION__ = "free_hash_table" #5 0x00007ff9291fad35 in tm_shutdown () at t_funcs.c:122 __FUNCTION__ = "tm_shutdown" #6 0x00000000004f8101 in destroy_modules () at sr_module.c:817 t = 0x7ff92a807d50 foo = 0x7ff92a807588 __FUNCTION__ = "destroy_modules" #7 0x00000000004689b2 in cleanup (show_status=1) at main.c:560 memlog = 32761 __FUNCTION__ = "cleanup" #8 0x0000000000469aab in shutdown_children (sig=15, show_status=1) at main.c:702 __FUNCTION__ = "shutdown_children" #9 0x000000000046b146 in handle_sigs () at main.c:793 chld = 0 chld_status = 139 memlog = 0 __FUNCTION__ = "handle_sigs" #10 0x000000000046f549 in main_loop () at main.c:1746 i = 8 pid = 20250 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\001", '\000' <repeats 19 times>, "\020\000\000\000\000\000\000\000\243Mgf\000\000\000\000\260vA\000\000\000\000\000\020\201\351a\377\177", '\000' <repeats 18 times>, "P\177\351a\377\177\000\000\002\266K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x0000000000471c38 in main (argc=5, argv=0x7fff61e98118) at main.c:2533 cfg_stream = 0x1970010 c = -1 r = 0 tmp = 0x7fff61e98148 "\211\236\351a\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5de800 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 519948236 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x416bd9 "H\203\304\b\303" <Address 0x416bde out of bounds> __FUNCTION__ = "main" Thank you for your help

2 1

Add Header
by Tony Turner 28 Feb '14

28 Feb '14

Hi, customers PBX----trunk-----kamailio------------freeswitch-------------carrier We already add Trusted IP’s via SIREMIS 4.0 is it possible with Kamailio to have customers calls come in on a trusted IP and when they send calls we add a header with a [client id] which we can remove on the next ip switch upstream So example Call comes in from customer with IP: their trusted IP source xx.xx.xx.xx add header with their client ID route to PSTN Then my upstream switch will process the customers call and remove the header before sending to our voip carrier. Basically my ip switch will evaluate the client id header for billing, process and strip the header back out. Thanks Tony

2 2

proposed patch for the registrar module - crash fix
by Dragos Oancea 28 Feb '14

28 Feb '14

Hi We think that we found and fix a bug in the registrar module. The bug is hard to reproduce, and it crashes our Kamailio from time to time (once at 2-3 weeks for us) . In save.c, function update_contacts() there are two places where we free() a pointer and then we reuse it, line 700 and line 730: while(ptr){ ptr0 = ptr; if(ptr!=c) ul.delete_ucontact(_r, ptr); ptr=ptr0->next; } And then from inside delete_ucontact(_r,ptr) we call mem_delete_ucontact(_r, _c) which calls free_ucontact(_c) , which calls shm_free(_c) . _c is actually our ptr. If another process writes at the location pointed by ptr during the "while" loop , the current process will crash. The bug affects 4.0.4, 4.0.5 and maybe older versions. We keep the location table in memory, no database backend, and we do alot of REGISTER/un-REGISTER in our environment, and maybe that's why this bug was not spotted by the community before. Just to clarify, this fix is in relation with this post: http://lists.sip-router.org/pipermail/sr-dev/2014-February/022934.html Please take into consideration the attached patch provided by the Libon Voice Team. Regards, Dragos Oancea

2 1

Mobile 3G Block from provider
by Rene Montilva 28 Feb '14

28 Feb '14

Hi List I'm trying to call over 3G networks, but doesn't work, i think my mobile provider block voip traffic, is there any way to hide voip traffic or jump the provider block rule ??

2 1

keep buddy list - best way
by Mihai Marin 27 Feb '14

27 Feb '14

Hello Sirs, I'm a little confused getting a decision about implementing buddy list (step: presence & IM). What is the best way for keeping the contacts list: xmpp or xcap? You will say probably xcap server but even if I intend to use in the future an xmpp gateway in order to be able to communicate sip with with xmpp servers like google - google talk? And why xcap? Because most of the clients has the possibility to connect to a xcap server to get the buddy list? From web perspective I think both are OK because of the xhttp module power in kamailio to get the buddy list xml. Thank you. Best regards, Mihai M

1 0

kamailio error, failed to start.
by Arya Farzan 27 Feb '14

27 Feb '14

I just installed kamailio on Debian 7 and when I start it with init.d I get the following messages. root@voip:/etc/kamailio# /etc/init.d/kamailio start Starting Kamailio: loading modules under /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/ Listening on udp: 127.0.0.1:5060 udp: MYSERVERIP:5060 tcp: 127.0.0.1:5060 tcp: MYSERVERIP:5060 tls: 127.0.0.1:5061 tls: MYSERVERIP:5061 Aliases: tls: voip:5061 tls: localhost:5061 tcp: voip:5060 tcp: localhost:5060 udp: voip:5060 udp: localhost:5060 kamailio error, failed to start. root@voip:/etc/kamailio# How can I find out what the problem is?

3 4

Re: [SR-Users] Replacing an ACME Packet Net-Net SBC
by Raúl Alexis Betancor Santana 27 Feb '14

27 Feb '14

Sorry ... I disagree at all .... All that features you mention, could be done with kamalio ... BUT you have to work on your cfg to get them. You don't get then out of the box. Kamailio it's a powerfull tool ... It's not a final product as the AP Net SBC Best regards Luis Silva <luisfilsilva(a)gmail.com> wrote: >_______________________________________________ >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >sr-users(a)lists.sip-router.org >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

kamailio with mediaproxy-ng, 488 Not Acceptable Here
by Mihai Marin 26 Feb '14

26 Feb '14

Hello Sirs, I have a problem configuring kamailio with mediaproxy-ng and I'm asking for help. I managed to build everything, kamailio find support for mediaproxy-ng using rtpproxy-ng. When I'm trying to make a call from Web using my phone's internet provider to my computer's web I get 488 Not Acceptable Here. Swithing the caller I get no video. I have used the kamailio-advanced.cfg generated and added websocket support. The call in my network is working perfect. Can you help me with this? mediaproxy-ng log: mediaproxy-ng[14896]: Returning to SIP proxy: d7:createdi1390864117e7:streamslld3:tag10:trhh9viigs6:status34:known but unconfirmed peer address5:statsd3:rtpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address13:213.233.85.554:porti48279ee23:advertised peer addressd6:family4:IPv47:address13:213.233.85.554:porti48279ee10:local porti30008ee4:rtcpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address13:213.233.85.554:porti48280ee23:advertised peer addressd6:family4:IPv47:address13:213.233.85.554:porti48280ee10:local porti30009eeeed3:tag0:6:status20:unknown peer address5:statsd3:rtpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv67:address2:::4:porti0ee23:advertised peer addressd6:family4:IPv67:address2:::4:porti0ee10:local porti30010ee4:rtcpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv67:address2:::4:porti0ee23:advertised peer addressd6:family4:IPv67:address2:::4:porti0ee10:local porti30011eeeeee6:totalsd5:inputd3:rtpd7:packetsi0e5:bytesi0e6:errorsi0ee4:rtcpd7:packetsi0e5:bytesi0e6:errorsi0eee6:outputd3:rtpd7:packetsi0e5:bytesi0e6:errorsi0ee4:rtcpd7:packetsi0e5:bytesi0e6:errorsi0eeee6:result2:oke kamailio: 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=860 a=24 n=rtpproxy_manage 11(14926) DEBUG: rtpproxy-ng [rtpproxy.c:1333]: rtpp_function_call(): proxy reply: d7:createdi1390864117e7:streamslld3:tag10:trhh9viigs6:status34:known but unconfirmed peer address5:statsd3:rtpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address13:213.233.85.554:porti48279ee23:advertised peer addressd6:family4:IPv47:address13:213.233.85.554:porti48279ee10:local porti30008ee4:rtcpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv47:address13:213.233.85.554:porti48280ee23:advertised peer addressd6:family4:IPv47:address13:213.233.85.554:porti48280ee10:local porti30009eeeed3:tag0:6:status20:unknown peer address5:statsd3:rtpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv67:address2:::4:porti0ee23:advertised peer addressd6:family4:IPv67:address2:::4:porti0ee10:local porti30010ee4:rtcpd8:countersd7:packetsi0e5:bytesi0e6:errorsi0ee12:peer addressd6:family4:IPv67:address2:::4:porti0ee23:advertised peer addressd6:family4:IPv67:address2:::4:porti0ee10:local porti30011eeeeee6:totalsd5:inputd3:rtpd7:packetsi0e5:bytesi0e6:errorsi0ee4:rtcpd7:packetsi0e5:bytesi0e6:errorsi0eee6:outputd3:rtpd7:packetsi0e5:bytesi0e6:errorsi0ee4:rtcpd7:packetsi0e5:bytesi0e6:errorsi0eeee6:result2:oke 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=867 a=16 n=if 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=862 a=24 n=is_request 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=866 a=16 n=if 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=863 a=24 n=has_totag 11(14926) DEBUG: siputils [checks.c:103]: has_totag(): no totag 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=864 a=25 n=add_rr_param 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=873 a=16 n=if 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=867 a=24 n=is_reply 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=873 a=2 n=return 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=1009 a=16 n=if 11(14926) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio-advanced.cfg] l=989 a=24 n=t_is_canceled 11(14926) DEBUG: tm [t_lookup.c:1071]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T start=0x7f62174df4e0 11(14926) DEBUG: tm [t_lookup.c:1143]: t_check_msg(): DEBUG: t_check_msg: T already found! 11(14926) DEBUG: tm [t_reply.c:1827]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 11(14926) DEBUG: <core> [msg_translator.c:2007]: generate_res_buf_from_sip_res(): old size: 397, new size: 305 11(14926) DEBUG: <core> [msg_translator.c:2025]: generate_res_buf_from_sip_res(): copied size: orig:125, new: 33, rest: 272 msg= SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/WS ebhg3v0qb6fm.invalid;rport=1034;received=213.233.85.55;branch=z9hG4bK8048296 To: <sip:bob@93.187.138.214>;tag=r6dc2287g9 From: "Alice Test" <sip:alice@93.187.138.214>;tag=trhh9viigs Call-ID: fvgga4ikm8vrvuji0g0n CSeq: 6228 INVITE Content-Length: 0 11(14926) DEBUG: websocket [ws_frame.c:713]: ws_frame_transmit(): Tx message: SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/WS ebhg3v0qb6fm.invalid;rport=1034;received=213.233.85.55;branch=z9hG4bK8048296 To: <sip:bob@93.187.138.214>;tag=r6dc2287g9 From: "Alice Test" <sip:alice@93.187.138.214>;tag=trhh9viigs Call-ID: fvgga4ikm8vrvuji0g0n CSeq: 6228 INVITE Content-Length: 0 Thank you. Best regards, Mihai M

8 27

coredump on using jsonprc_request
by davy van de moere 26 Feb '14

26 Feb '14

Gents, I’ve stumbled upon a coredump when using jsonrpc_request. I might be expecting the wrong things from jsonrpc_request. I was hoping to use it in combination with CNXCC, and have jsonrpc_request get a maximum duration for every call, as a fraud avoidance mechanism. I tried this with the branch 4.1 and master. Both behave identical. So from the kamailio-basic.cfg example, I just added this line around line 350 (just above route(SIPOUT)): jsonrpc_request("bar.sendsms", "{'ru':'$rU','rb':'$rb'}", "JSONRESPONSE", "JSONERROR", "$var(result)"); Doing a ngrep on the netstrings I have: interface: venet0 (127.0.0.2/255.255.255.255) filter: (ip or ip6) and ( port 7080 ) # T 10.66.8.42:44995 -> 192.168.60.45:7080 [AP] 94:{ "id": 2, "jsonrpc": "2.0", "method": "bar.sendsms", "params": { "ru": "", "rb": "" } }, ## T 192.168.60.45:7080 -> 10.66.8.42:44995 [AP] 43:{"jsonrpc": "2.0", "result": "12", "id": 2}, ####^Cexit 7 received, 0 dropped I do get some results from the JSONRESPONSE route. But when launching a call, or when sending just a register packet, kamailio gives up with: Feb 26 06:29:11 SBC01 kamailio[18043]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction Feb 26 06:29:12 SBC01 kamailio[18033]: : [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xb4c01624), called from tm: h_table.c: free_cell(157), first free tm: h_table.c: free_cell(157) - aborting Feb 26 06:29:12 SBC01 kamailio[18023]: ALERT: [main.c:775]: handle_sigs(): child process 18033 exited by a signal 6 Feb 26 06:29:12 SBC01 kamailio[18023]: ALERT: [main.c:778]: handle_sigs(): core was generated Feb 26 06:29:12 SBC01 kamailio[18023]: INFO: [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD Feb 26 06:29:12 SBC01 kamailio[18041]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18047]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18043]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18048]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18023]: : [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xb4c01624), called from tm: h_table.c: free_cell(157), first free tm: h_table.c: free_cell(157) - aborting Using the jsonrpc_notification works like a charm. I got coredumps of it, if someone is interested. Side questions are offcourse, am I aiming to use jsonrpc_request for the correct purpose? Are there any other good alternatives? (next to using plain db queries?) Grtz, Davy -- davy van de moere

1 0

Kamailio World 2014 - Agenda
by Daniel-Constantin Mierla 26 Feb '14

26 Feb '14

The first version of the schedule during Kamailio World 2014 <http://www.kamailioworld.com> [1] has been published. Over 30 sessions grouped in two days of conference and pre-conference technical tutorials, spanning from various use cases for Kamailio to presentations approaching related VoIP applications such as Jitsi, Sems, Asterisk or FreeSwitch. Among the topics: WebRTC, IMS or VoIP security and fraud detection, tools for testing and troubleshooting VoIP systems, scalability with OpenStack and asynchronous processing, real time charging. First version of agenda has been published at: - http://conference.kamailio.com/k02/schedule/ Information about speakers can be found at: - http://conference.kamailio.com/k02/speakers/ Many thanks to the sponsors [2], they are making possible this event: FhG Fokus <http://www.fokus.fraunhofer.de/en/fokus/index.html>, Asipto <http://www.asipto.com>, Sipwise <http://www.sipwise.com>, Sipgate <http://www.sipgate.de>, IT Center <http://www.itcenter.com.pt/>, Simwood <http://www.simwood.com>, and NG Voice <http://www.ng-voice.com/>. Should you consider sponsoring, contact us via email at <conference [at] kamailio.com>**and we can present you more details. If you plan to attend, do not delay the registration, the number of seats is limited – see more details in Registration page <http://conference.kamailio.com/k02/registration/> [3]. /Looking forward to meeting many of you in Berlin! / Daniel/ / [1] - http://conference.kamailio.com [2] - http://conference.kamailio.com/k02/sponsors/ [3] - http://conference.kamailio.com/k02/registration/ -- Daniel-Constantin Mierla http://www.asipto.com

1 0

debian packages from opensuse.org
by Jöran Vinzens 26 Feb '14

26 Feb '14

Hi All, we are using Kamailio 4.1.0 packages from opensuse: http://download.opensuse.org/repositories/home:/kamailio:/telephony-debs/De… During installation it seems, the packages are malformed. Installation of kamailio-mysql-modules and kamailio-xml-modules stops during unpacking with failure: "trying to overwrite '/usr/lib64/kamailio/libsrdb2.so.1.0', which is also in package kamailio 4.1.0" it seem this one file is part of all three packages. There is a way to enforce the installation using dpkg -i --force-all.. but it seems not the right way. Does anyone have an idea how to solve without building own packages? Maybe this is an bug in kamailio Project? Many thanks for all proposals. BR Jöran -- Jöran Vinzens sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

2 1

Re: [SR-Users] RTPProxy/Mediaproxy issue
by Daniel Grotti 25 Feb '14

25 Feb '14

Hi, Yes packet loss is very high. Please investigate around that. Daniel Ravi <wingsravi777(a)gmail.com> wrote: >_______________________________________________ >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >sr-users(a)lists.sip-router.org >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

2 5

Problems while reading from location and parsing expires
by Jöran Vinzens 25 Feb '14

25 Feb '14

Hi All, we are upgrading from kamailio 3.1 to 4.1 and we got stuck at a Problem with usrloc module. While starting up kamailio reads location from DB and try to parse expires date from DB. this is the Problem: Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: <core> [db_ut.c:90]: db_str2int(): Unexpected characters: [-02-25 11:27:08] Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: <core> [db_val.c:75]: db_str2val(): error while converting integer value from string Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: db_mysql[km_row.c:68]: db_ mysql_convert_row(): failed to convert value Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: db_mysql [km_dbase.c:375]: db_mysql_fetch_result(): error while converting row #0 Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: usrloc [udomain.c:420]: preload_udomain(): fetching rows failed usrloc Module is configured with db_mode "1" so it saves it's entries by itself. When i have a look on the database it looks good and the expires field is an datetime. From logs it looks like it try to parse a unixtimestamp instead of the datetime. when i truncate the location table it starts perfectly, since there are no entries stored where it could fail parsing expires date. does anybody has similar issue or any suggestions how to solve? found in Version: 4.1.0 many thanks! BR Jöran -- Jöran Vinzens sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

2 4

Re: [SR-Users] Kamailio as redirect
by Daniel Tryba 24 Feb '14

24 Feb '14

On Monday 24 February 2014 14:45:18 Mike Claudi Pedersen wrote: > okay i somewhat get that.. but cant i use something like a lookup in a > textfile instead of a db? You can. alias_db also accepts dbtext as backend: http://kamailio.org/docs/modules/stable/modules/db_text.html But TIMTOWTDI, alias_db was just a suggestion. Please keep the mailing list included. -- POCOS B.V. - Croy 9c - 5653 LC Eindhoven Telefoon: 040 293 8661 - Fax: 040 293 8658 http://www.pocos.nl/ - http://www.sipo.nl/ K.v.K. Eindhoven 17097024

1 0

Re: [SR-Users] Configuring Kamailio as an upstream proxy for FreeSwitch and which RTP proxy to choose
by Fred Posner 24 Feb '14

24 Feb '14

On Mon Feb 24 10:50:07 CET 2014 Sean Kemball wrote: > New to Kamailio and FreeSwitch, loosely familiar with SIP mechanics, > and not a complete network idiot... but please be gentle. :) Welcome!s, > Questions: > > 1. Should the proposed topology, with Kamailio + an RTP proxy > behind a firewall, relaying to FS on an inside interface, work? > (Can't see why not) Yes, you said that your upstream is on the same private network. So it should be pretty straight forward. > 2. Does it need a local RTP proxy on the Kamailio box, particularly > if we turn off the ASA SIP inspect stuff? If you are all on the same private network, I would let FreeSWITCH handle the RTP, but you can do this a variety of ways. > 3. Can you recommend which RTP proxy to use? There seem to be at > least 3 that work with Kamailio. The box is CentOS 6.5, and it would > be nice to use known-to-work packages rather than compile from source. > (But eh, if I haveta). On your scenario, I'd just use FreeSWITCH for the media proxy. Again, many different ways to go here. > 4. Can anyone point me to some docs to explain what ports need to > be open between the Kamailio box and my upstream proxy/media server? > I can be more liberal between inside and DMZ I guess. Your upstream provider would generally tell you which rtp ports they would want opened. > 5. Is static NAT in this environment going to bite me, or should > it be OK? I've never had an upstream provider communicate with me on private nat. > 6. Is there any better documentation that we should be using to > make this easier, or should I just man up and try harder? Man up. =) Practive makes perfect. -- Fred Posner The Palner Group, Inc.

1 0

pcscf - removing registration entries from hash table
by Daniel Ciprus 24 Feb '14

24 Feb '14

Hello, Our current setup is Kamailio as IMS core and we're observing following behavior: Clients register themselves over TCP so pcscf creates hash table which keeps these information in memory. Once tcp reset occurs for any reason, registration entry stays in the memory and client re-registers himself with new pair ip:port. This kind of behavior creates problem because outbound SIP messages are being forked and requests are sent to non-existent tcp sessions which creates a lot of timeouts and confusion for AS. We're using ims_usrloc_pcscf module to keep reg entries in and as I noticed, with usrloc module, there was an option which automatically removed entry from hash table once tcp session was closed which is not the case in this module. Any suggestions how to get out of this ? thanks for any hints/suggestions. -- Daniel Ciprus Integration engineer http://www.acision.com 9954 Mayland Dr Suite 3100 Richmond, VA 23233 USA T: +1 804 762 5601 E: daniel.ciprus(a)acision.com<mailto:daniel.ciprus@acision.com> ________________________________ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.

1 0

Kamailio as redirect
by Mike Claudi Pedersen 24 Feb '14

24 Feb '14

i want to setup a test environment to see how kamailio handles redirection. i want to be able to reroute calls between servers, where do i insert the configuration for this? can i append a list of user and destination to make the configuration go through, to see where the call is going? im new at kamailio, and im having a really hard time finding the right documentation to support a redirect server. could somone please give me an example? lets say i have 3 user 1000 1001 1002 and they are at 3 different servers eg. 1000(a)192.168.1.10 1001(a)192.168.1.11 1002(a)192.168.1.12 then i call user 1002 from user 1000, through the kamailio redirect server, which redirects to corresponding servers. Mike Claudi Pedersen

2 1

Configuring Kamailio as an upstream proxy for FreeSwitch and which RTP proxy to choose
by Sean Kemball 24 Feb '14

24 Feb '14

Hi New to Kamailio and FreeSwitch, loosely familiar with SIP mechanics, and not a complete network idiot... but please be gentle. :) We're trying to get Kamailio set up in front of a FreeSwitch-based SIP application server, to do some simple policy controls and, using one of the RTP proxy modules, to help handle the media side of things. Our SIP trunks come from our provider on a VLAN addressed as 10.x, and they provide an upstream proxy/media server (10.y address). The link also carries Internet traffic so we're running it through a Cisco ASA which breaks out the VLANs and static NATs the SIP stuff to our DMZ (10.z address). This is where we want to put the Kamailio box, where it should receive the calls and route them back through the ASA to the internal address (10.w range - all 10.w/x/y/z are separate, non-overlapping networks). Outbound calls from the application server (there are very few) should pass back up to Kamailio which will validate the numbers against an approved list (the app should only dial a subset of numbers) and pass them to the upstream proxy if necessary. We need to ensure that inbound calls from outside trombone through our application server so that the caller doesn't get billed for any calls, but this should be the default I think as that side of things is handled by FS (the app stands up a new call and bridges it to the incoming). This topology should allow us to use Kamailio to hide details of the FS app from the outside world, and make life easier for the app developer who should just send/receive to the Kamailio box with no further thought or complexity. If we put the FreeSwitch box in the DMZ where we want to put Kamailio, and then turn on SIP packet inspection in the ASA, calls flow but quality is poor for some callers. If we turn off SIP packet inspection, we get no audio - I can't find any clear Cisco documentation for this but I think the SIP inspection stuff in the ASA seems to handle RTP NAT fixups and the like too. But with no docs it may as well be magic, and I want to remove it if possible. With Kamailio in the DMZ and FS internal, we loosely followed http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc and hacked out the voicemail and Lua stuff, but couldn't get calls to flow, whether or not we used the SIP inspection on the ASA. We were confused why this example isn't define as WITH_NAT and doesn't use a local RTP proxy. Surely that would be needed? Questions: 1. Should the proposed topology, with Kamailio + an RTP proxy behind a firewall, relaying to FS on an inside interface, work? (Can't see why not) 2. Does it need a local RTP proxy on the Kamailio box, particularly if we turn off the ASA SIP inspect stuff? 3. Can you recommend which RTP proxy to use? There seem to be at least 3 that work with Kamailio. The box is CentOS 6.5, and it would be nice to use known-to-work packages rather than compile from source. (But eh, if I haveta). 4. Can anyone point me to some docs to explain what ports need to be open between the Kamailio box and my upstream proxy/media server? I can be more liberal between inside and DMZ I guess. 5. Is static NAT in this environment going to bite me, or should it be OK? 6. Is there any better documentation that we should be using to make this easier, or should I just man up and try harder? TIA Sean Volunteer for our Red Puppy street appeal to help puppies like Gordy become guide dogs. ############################################################################# This email, including any attachments, is intended solely for the addressee(s) It is confidential and may be legally privileged. If you are not the intended recipient, you must not copy, disclose, distribute or otherwise use it or the information in it. Please notify the sender at once and delete it from your system immediately. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Blind Foundation. The Blind Foundation does not accept responsibility for any viruses or other malicious code that may be transmitted with this email. #############################################################################

1 0

Change from_uri
by arun Jayaprakash 24 Feb '14

24 Feb '14

Hello, I have a problem that my calls get rejected by he pstn gateway as my gateway is expecting a DID number instead of a 4 digit extension as the 'from user". Let me explain my situation: 1. I have set callfwd_busy in my user preference table. 2. In my failure route I check to see if callfwd_busy has been set, if it has then I execute the following script: if (t_check_status("486|408")) { $avp(dst_number) = $rU; if (avp_db_load("$avp(dst_number)", "$avp(callfwd_busy)")) { xlog("LOG: avp(callfwd_busy)=$avp(callfwd_busy), avp(dst_number)=$avp(dst_number)\n"); } xlog("LOG: Failure route with $rU $avp(dst_number) \n"); $rU = $avp(callfwd_busy); $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip); route(RELAY); exit; } When I call from extension 7004 to ext 7002 ( this has callfwd_busy set to a DID number) the trace looks as follows: U 172.10.30.15:5080 -> 172.10.30.15:5060 SIP/2.0 486 Busy Here. Via: SIP/2.0/UDP 54.200.xx.yy:5060;branch=z9hG4bKee75.ab791c5.0;received=172.10.30.15. Via: SIP/2.0/UDP 192.168.1.8:5060;received=71.252.219.63;branch=z9hG4bK209939211;rport=1025. From: "7004" <sip:7004@ajfmc1.myDomain.net>;tag=1830267367. To: <sip:7002@ajfmc1.myDomain.net>;tag=as17cd0b40. Call-ID: 876294364-5060-74(a)BJC.BGI.B.I. CSeq: 731 INVITE. Server: Asterisk PBX 1.8.17.0. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH. Supported: replaces, timer. Content-Length: 0. U 172.10.30.15:5060 -> 172.10.30.15:5080 INVITE sip:18455981234@64.136.xx.yy:5060 SIP/2.0. Record-Route: <sip:54.200.xx.xx;lr=on;ftag=1830267367;nat=yes>. Via: SIP/2.0/UDP 54.200.xx.xx:5060;branch=z9hG4bKee75.ab791c5.1. Via: SIP/2.0/UDP 192.168.1.8:5060;received=71.252.xx.yy;branch=z9hG4bK209939211;rport=1025. From: "7004" <sip:7004@ajfmc1.myDomain.net>;tag=1830267367. To: <sip:7002@ajfmc1.myDomain.net>. Call-ID: 876294364-5060-74(a)BJC.BGI.B.I. CSeq: 731 INVITE. Contact: "7004" <sip:7004@71.252.xx.yy:1025>. Max-Forwards: 16. User-Agent: Grandstream HT701 1.0.4.8. Privacy: none. P-Preferred-Identity: "7004" <sip:7004@ajfmc1.myDomain.net>. Supported: replaces, path, timer, eventlist. Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE. Content-Type: application/sdp. Accept: application/sdp, application/dtmf-relay. Content-Length: 453. . v=0. o=7004 8000 8000 IN IP4 172.10.30.1554.200.xx.xx. s=SIP Call. c=IN IP4 172.10.30.1554.200.xx.xx. t=0 0. m=audio 6248262482 RTP/AVP 0 18 4 8 2 97 101. a=sendrecv. a=rtpmap:0 PCMU/8000. a=ptime:20. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:4 G723/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:2 G726-32/8000. a=rtpmap:97 iLBC/8000. a=fmtp:97 mode=20. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16,32-36,54. a=nortpproxy:yes. a=nortpproxy:yes. # U 172.10.30.15:5080 -> 172.10.30.15:5060 SIP/2.0 503 Unavailable. Via: SIP/2.0/UDP 54.200.xx.xx:5060;branch=z9hG4bKee75.ab791c5.1;received=172.10.30.15. Via: SIP/2.0/UDP 192.168.1.8:5060;received=71.252.xx.yy;branch=z9hG4bK209939211;rport=1025. From: "7004" <sip:7004@ajfmc1.myDomain.net>;tag=1830267367. To: <sip:7002@ajfmc1.myDomain.net>;tag=as17cd0b40. Call-ID: 876294364-5060-74(a)BJC.BGI.B.I. CSeq: 731 INVITE. Server: Asterisk PBX 1.8.17.0. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH. Supported: replaces, timer. Content-Length: 0. It looks like my gateway is expecting to see a DID number in the from header. Can someone let me know how I can dot this? Thank you. Arun

3 4

Query about RTP flow
by Nandini madhu 23 Feb '14

23 Feb '14

Dear All, I have read about SIP and RTP packet flows but ended with a question about RTP packets flow logic between client-to client when the SIP session starts. I have a running Kamailio (V 4.0.4) server on ubuntu (12.04) platform which is also configured fro DNS and DHCP servers. And following are my test bed set-ups: Kamailio server (DNS+ DHCP+Kamailio) | Router <----------------------------> Switch<----------------------------> Router | | clientA <--------------------- RTP(audio/video) ? --------------------> client B Now when the SIP session established (SIP Packets have to pass through all the routers and switch to reach Kamailio server), RTP session will start between Client A and B. But What is meant by client to client here ? what is the RTP packets path between the clients to reach their destinations ? Is the RTP packets have to pass through Routers and switch to reach its destination client ? (i.e Client A--->Router 1---->switch -----> Router 2-----> client B) ? What if i connect both client A and client B to the same router ? PS: I have not configured any media-relays (RTPproxy/Media-proxy) Please help me in clarifying all this doubts. Anybody's help will greatly appreciate. Regards, Nandini

1 0

HTABLE update from DB
by Uri Shacked 23 Feb '14

23 Feb '14

It does not work...I tried with autoexpire=0, I tried with no autoexpires define, I Tried defining a number and see if the value is updated.... this is my table definition: modparam("htable", "htable", "A=>size=8,dbtable=aaaaaa;initial=0,dbmobe=0;") I remind you i need the memory to be updated from the DB every interval, and not the DB form the memory. thanks. >Declare the table without autoexpire. Check again the module README. >Regards, >Ovidiu Sas >On Feb 23, 2014 11:23 AM, "Uri Shacked" <ushacked at gmail.com <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>> wrote: >>* Hi, *>>>>* Following my issue with reloading data. I am thinking of a way to keep *>>* data updated in memory. *>>* I read the HTABLE module again and notice the "db_expires" option. *>>* It does not work for me... *>>>>* I try to set it so an item will expire in 60 sec, and when expired, it *>>* will be reloaded from DB and not deleted. *>>>>* Any ideas? *>>>>* Uri*

2 1

RTPProxy/Mediaproxy issue
by Wingsravi R 23 Feb '14

23 Feb '14

Dear Kamailio'ns, I have configured kamailio (V 4.0) with RTPproxy server. Audio/Video call establishments are just fine. With this i have some unknown behaviour in my set-up is that When i am running kamailio server with RTPproxy instance, i am experiencing Jitter, Latency, pixelled audio/video calls. But when i run only Kamailio server without RTPproxy service running, audio/video calls are just fine (no any jitter, latency kind of issues). I also tried with Mediaproxy (AG projects) server but the results are same as like in Kamailio/RTPproxy case. What could be the problem with this set-up ? How can i solve this issue ? Please anybody help me in resolving this problem. Any help will greatly appreciate. Regards. Ravi.

4 7

HTABLE update from DB
by Uri Shacked 23 Feb '14

23 Feb '14

Hi, Following my issue with reloading data. I am thinking of a way to keep data updated in memory. I read the HTABLE module again and notice the "db_expires" option. It does not work for me... I try to set it so an item will expire in 60 sec, and when expired, it will be reloaded from DB and not deleted. Any ideas? Uri

2 1

Using Kamailio as a websocket LB
by Luis Silva 22 Feb '14

22 Feb '14

Hi guys, Is it possible to use Kamailio as a Websocket LoadBalancer (transparent to the Websocket content, rather it's SIP or other protocol)? Many thanks, Luís

3 3

parallel forking and 30x
by Andreas Granig 21 Feb '14

21 Feb '14

Hi, What is the intended behaviour from a general point of view if you get a 1xx on one branch and a 30x on another branch for a parallel fork? >From my understanding, the 30x is a final reply, so it's kept in tm until all other branches are finished, then it enters failure-route with the highest error code (e.g. a 487 if you cancel the other branch). What I actually want is intercepting the 30x and send another INVITE to the Contact of the 30x in the failure route. This works fine if you only have one branch, but it doesn't enter failure route for 30x if you have another active branch (e.g. in ringing state). Would it be possible to create a new branch directly from the reply route, or force to enter failure route for a specific reply/branch? Andreas

3 5

Kamailio not starting
by Owais ul Haq 21 Feb '14

21 Feb '14

Hello, I have deployed Kamailio-3.1 on a fedora machine. And my database is placed on another windows 2008 server situated on the local network. Problem is when I run kamailio. I get the following error from logs. <core> [cfg.y:3416] : parse error in config gile /usr/local/kamailio-3.1/etc/kamailio//kamailio.cfg, line 311, column 31-35 : syntax error <core> [cfg.y:3416] : parse error in config gile /usr/local/kamailio-3.1/etc/kamailio//kamailio.cfg, line 311, column 31-35 : Invalid arguments Line 311 is kamailio.cfg is "modparam ("usrloc", "db_url", DBURL)" And 'DBURL' is defined as #! define DBURL "mysql://openser:5mil5My5ql@192.168.1.20/openser" Can some one please help me out in resolving this error. Secondly I am deploying my database on seperate server for the first time. I have deployed kamailio-3.1 already but with database placed on same machine. Can someone please guide what changings do I need to make in kamailio.cfg and kamctlrc file to make it work. I have made some as per my understanding. Maybe they are a cause of this error. Thanks, Regards, Owais

2 1

Information
by hfermi 21 Feb '14

21 Feb '14

Good morning I would like to receive more information about your platform web based voip. Many Thanks and Regards Henry Landi

1 0

Re: [SR-Users] FW: Regd. t_suspend() and t_continue()
by Shankar 21 Feb '14

21 Feb '14

Hi, We have found the root cause for the problem that was reported (refer below mail for details) in async module. Below is the brief description, - async_route("Resume", "1") - At time t, the async records are stored at slot 't+1' of async list. - Every second, async records from the async list are processed. - In function 'async_timer_exec', slot = ticks % ASYNC_RING_SIZE; since slot is based on the ticks and if the previous invocation of 'async_timer_exec' did not finish in time, the next tick is missed. Subsequent call to 'async_timer_exec' will be with t+2. Here slot t+1 will be missed and the same will be processed only during next cycle. That means the async records will be stored for the next 100 seconds before they are actually processed. TM module will drop those timed out transactions and hence the error "t_continue: transaction not found" Now we have modified the code in such a way that slot is incremented sequentially irrespective of the ticks that is sent to the function 'async_timer_exec' function. This way we do not see any call failures and all our load runs are successful. If someone is interested we can share the code as well. Regards, Shankar From: Shankar [mailto:shankar.rk@plintron.com] Sent: Thursday, January 23, 2014 12:18 PM To: 'Jason Penton'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List' Subject: RE: [SR-Users] FW: Regd. t_suspend() and t_continue() Hi, >From our repeated load tests what we can conclude irrespective of the number of simultaneous calls, there is always this error "t_continue: transaction not found" occurring. If I run say 20 cps, then after running 5000 calls, we observe exactly 20 calls failing with the above error. We doubt that there is something happening during a particular point in time (for a second) which impacts the saving of those new transactions into shared memory. For 10 cps run, we observe exactly 10 call failures. We repeated with different cps and found that error is exactly equal to the cps being run. Any configuration we are missing. Anyone can help? Regards, Shankar From: Shankar [mailto:shankar.rk@plintron.com] Sent: Tuesday, January 21, 2014 3:09 PM To: 'Jason Penton'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List' Subject: FW: [SR-Users] FW: Regd. t_suspend() and t_continue() Hi Jason, Below is our config, route[LOCATION] { if(is_method("INVITE")) { if(!route(FROMCSCF)) { setflag(FLT_ACC); setflag(FLT_ACCFAILED); dlg_manage(); dlg_setflag("4"); async_route("RESUME", "1"); exit; } } } route[RESUME] { route(TO_LOCATION); // here t_relay to REGISTRAR is done for user lookup. exit; } Regards, Shankar Date: Tue, 21 Jan 2014 11:14:21 +0200 From: Jason Penton <jason.penton(a)smilecoms.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org> Subject: Re: [SR-Users] FW: Regd. t_suspend() and t_continue() Message-ID: <CAE=KcrghqJHgnGDxqS1fYvUzM=HqRAcKWfEAsNJjm8xUDCq68w(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" We use it heavily, but not using the async module - we use it directly from the IMS code. Can you please provide your config (or a relevant snippet) file so I can see what exactly you are testing/trying to do Cheers jason From: Shankar [mailto:shankar.rk@plintron.com] Sent: Tuesday, January 21, 2014 2:25 PM To: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List' Subject: RE: [SR-Users] FW: Regd. t_suspend() and t_continue() Hi, Anyone who had used t_suspend() and t_continue() can share the performance details? I tried async module with one sec sleep time. I tried only 5 calls per second but still it was not successful. After sometime I see below logs, Jan 21 13:51:55 PLT-RA-RD-W167A PCscf[16520]: ERROR: tm [t_suspend.c:128]: t_continue(): ERROR: t_continue: transaction not found Jan 21 13:52:49 PLT-RA-RD-W167A last message repeated 15 times Jan 21 13:59:38 PLT-RA-RD-W167A last message repeated 12 times Jan 21 14:13:03 PLT-RA-RD-W167A last message repeated 5 times Any configuration changes can help here? Regards, Shankar From: Shankar [mailto:shankar.rk@plintron.com] Sent: Wednesday, January 15, 2014 1:26 PM To: 'Jason Penton' Cc: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List' Subject: RE: [SR-Users] FW: Regd. t_suspend() and t_continue() Hi Jason, I am using 4.0.2 Regards, Shankar From: Jason Penton [mailto:jason.penton@smilecoms.com] Sent: Wednesday, January 15, 2014 1:21 PM To: Shankar Cc: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List Subject: Re: [SR-Users] FW: Regd. t_suspend() and t_continue() Hi Shankar, What version of Kamailio are you running? Kamailio -V Cheers Jason On Wed, Jan 15, 2014 at 6:58 AM, Shankar <shankar.rk(a)plintron.com> wrote: Hi Jason, Please find below my response inline, I have some questions for you as we have used suspend/continue quite a lot in the IMS code and don't have any leaks. Firstly, why are you using pkg_mem for your hash_id and label? Remember that you will be in 2 different processes in the suspend and continue portions of the code... so pkg_mem will not work - you should use shm_mem instead. [Shankar] We use pkg_mem because we are invoking t_continue from the same process ( using thread ). Secondly, how are you using top to tell that you have a leak? Kamailio's memory is internally managed. [Shankar] After running for say 20minutes, we get out of shared memory error. Also in top output we observed incremental increase in the shared usage of shared memory for the process. Cheers Jason On Mon, Jan 13, 2014 at 1:29 PM, Shankar <shankar.rk(a)plintron.com> wrote: > Re-sending without the attachment. > > > > *From:* Shankar [mailto:shankar.rk@plintron.com] > *Sent:* Monday, January 13, 2014 4:57 PM > *To:* 'sr-users(a)lists.sip-router.org' > *Subject:* Regd. t_suspend() and t_continue() > > > > Hi, > > > > We are trying out the t_suspend() and t_continue() in our test setup. > We are facing memory leak ( both shm and pkg as per top command results). > > > > Please find below the scenario, > > > > 1) Do a t_newtran() > > 2) Allocate pkg memory for hashid and label. > > 3) Call t_suspend() > > 4) Do t_continue() when async result is available > > 5) De-allocate pkg memory reserved for hashid and label > > 6) Do a t_relay() which forwards the sip message to another sip node. > > > > In the step (6) above, we see t_newtran() allocates one more time > shared memory for the same transaction. > > > > We tried t_release() after step (4) to release the transaction as > t_relay() anyways allocates new shared memory. Nothing helped. > > > > Please let me know what are the logs you would require to debug the same. > I am attaching syslog for this run. > > > > Regards, > > Shankar -- Jason Penton Senior Manager: Applications and Services Smile Communications Pty (Ltd) Mobile: +27 (0) 83 283 7000 Skype: jason.barry.penton <mailto:name.surname@smilecoms.com> jason.penton(a)smilecoms.com <http://www.smilecoms.com/> www.smilecoms.com <http://196.33.227.129/~smlcoms/sigs/pty/images/smile_signature_07_09.jpg> This email is subject to the disclaimer of Smile Communications at http://www.smilecoms.com/disclaimer

1 0

Call Control for Credit and Rate
by Raj Roy Ghandhi 21 Feb '14

21 Feb '14

Hi, I want to implement the call control by 1. Validating the CLI and get the credit from DB 2. Check the Rate for the dialed number 3. set the call timeout for the call duration. ( credit/rate) 4. pass the call to remote PSTN GW Please guide me on this. Regards, Roy.

3 2

Debian packages not updated since august 2013?
by Johan Wilfer 21 Feb '14

21 Feb '14

Hi, Looking at http://www.kamailio.org/wiki/packages/debs the suggestion is to use http://deb.kamailio.org/ for debian packages. But the last version of kamailio 4.0 here is 4.0.3, and 4.1 doesn't exist. The most files are last modified in 2013-08.. Here for example: http://deb.kamailio.org/kamailio/dists/wheezy/main/binary-amd64/ Is there a new server to get the deb-packages from or should I build from source from now on? /Johan

3 3

Performance impact with AVP and VAR's
by Jijo 21 Feb '14

21 Feb '14

Hi All, I have around 300 AVP's and quite amount of VAR's are used in the config file? Does that impact performance?, If so how can i improve it? Thanks Jijo

4 5

Re: [SR-Users] Issue with Async module
by Daniel-Constantin Mierla 20 Feb '14

20 Feb '14

Hello, thanks for reporting, I pushed a slightly different patch in master, 4.1 and 4.0 branches -- free is done even when ai->act is null. Cheers, Daniel On 20/02/14 15:13, Surendra wrote: > Hi Daniel, > > > I am using async module to continue the transaction in > asynchronously. But I am observing a leak in shared memory. Then i checked > the code, we are not freeing the async_item_t after calling t_continue. > Same this has checked with MEMDBG=1. > > Original code: > while(1) { > lock_get(&_async_list_head->ring[slot].lock); > ai = _async_list_head->ring[slot].lstart; > if(ai!=NULL) > _async_list_head->ring[slot].lstart = ai->next; > lock_release(&_async_list_head->ring[slot].lock); > > if(ai==NULL) > break; > if(ai->act!=NULL) > tmb.t_continue(ai->tindex, ai->tlabel, ai->act); > } > > > Changed code: > > while(1) { > lock_get(&_async_list_head->ring[slot].lock); > ai = _async_list_head->ring[slot].lstart; > if(ai!=NULL) > _async_list_head->ring[slot].lstart = ai->next; > lock_release(&_async_list_head->ring[slot].lock); > > if(ai==NULL) > break; > if(ai->act!=NULL) > { > tmb.t_continue(ai->tindex, ai->tlabel, ai->act); > shm_free(ai); /* Added by surendra */ > } > } > > Please correct this if I am wrong. > > > Regards > @surendra > > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Re: [SR-Users] NAT traversal problem with Kamailio when trying to communicate between two different LANs
by Neo Quartz 20 Feb '14

20 Feb '14

Hi All, I installed Kamailio server on my ubuntu machine. And installed rtpproxy also in the same machine. I didm't make many changes to default configuration files, kamctlrc and kamailio.cfg. Now I am able to communicate between two SIP clients, if both sip clients are in the same LAN. But I am not able to communicate between one sip client in one LAN and the other SIP client in other LAN. Sip Call handling and ringing etc. is ok but there is no voice for this case. I don't have much experience in routing for NAT traversal. I tried to experiment with rtpproxy_manage function in kamailio.cfg file. But I was not successful. Please help me by providing any hints or pointers to proceed further. I am using only Kamailio and Rtpproxy. No other software like Asterisk or FreeSwitch. ************* These are defines I used in kamailio.cfg file: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_ALIASDB #!define WITH_USRLOCDB #!define WITH_ANTIFLOOD #!define WITH_NAT #!define WITH_PRESENCE listen ip address changed ******************* Kamailio is compiled with following modules: include_modules= db_mysql dialplan presence presence_xml ******** Regards, Sateesh

2 1

understanding the sqlops module and kamailio children
by Uri Shacked 20 Feb '14

20 Feb '14

Hi, Following my issue with the above.... 1. Is there a way to see if a worker (child) is processing a transaction for too long (let's say 2-3 sec)? 2. Is there an option to see if the DB connection is alive? (I am familiar with db_mysql options) 3. If all workers are stuck on this "long" transaction, is there a Q for the new INVITES? Can I see how many are there? What I was experiencing is that when my DB was very slow, kamailio crashed after a while.... I will configure db_mysql to ping every 30 sec and timeout after 1 sec. Still, it can create a 3 sec delay for transactions. Any one has an idea? Using the ASYNC module can help here? Does it free the worker to deal with new requests? BR, Uri

2 1

Asterisk Ignore "UNREGISTER" because retransmit
by pavel＠eremina.net 20 Feb '14

20 Feb '14

Hi, All! Try to register user in Kamailio and then relay REG massage to Asterisk. Asterisk register user and looks good. But when I send Unreg message to Kamailio, it unregister user successfully but Asterisk say: Message REGISTER Ignoring because retransmit (CSeq 1234 our CSeq 1234). Did someone know how solve this problem: i think that Asterisk need different CSeq for first REGISTER and Second after 401 code. dump my conf: At route[REGISTER]: if (!save("location")) { sl_reply_error(); } else { reg_fetch_contacts("location", "$tu", "cc"); $var(useragent) = $ulc(cc=>user_agent); xlog("L_INFO","EXpires in Contact: $ulc(cc=>expires)"); if ($ulc(cc=>expires)==0) { $var(query) = "insert into activity values (now(),'unr','"+$ci+"','"+$fu+"');"; sql_query("events", "$var(query)"); $var(string_temp) = "$(hdr(expires))"; xlog("L_INFO", "UNregistered $ru FROM $fu exp $var(string_temp)"); } else { if ($var(registered)==0) { $var(query) = "insert into activity values (now(),'reg','"+$ci+"','"+$fu+"');"; sql_query("events", "$var(query)"); } xlog("L_INFO", "Registered $ru FROM $fu exp $ulc(cc=>expires)"); } } xlog("L_INFO","DU(TD): $td"); if ($td == "mydomain.com") {route(TOASTERISK); } exit; } } route[TOASTERISK] { xlog("L_INFO","ROUTE to ASTERISK from $ru to $tu"); #append_branch(); t_on_failure("FAILAUTH"); $ru = "sip:"+ $td; consume_credentials(); route(RELAY); exit; } failure_route[FAILAUTH] { if (t_is_canceled()) { exit; } if (t_check_status("(401)|(407)")) { xlog("L_INFO", "Remote asked for authentication"); $avp(realm)=""; uac_auth(); } route(RELAY); }

1 0

Issue with Async module
by Surendra 20 Feb '14

20 Feb '14

Hi Daniel, I am using async module to continue the transaction in asynchronously. But I am observing a leak in shared memory. Then i checked the code, we are not freeing the async_item_t after calling t_continue. Same this has checked with MEMDBG=1. Original code: while(1) { lock_get(&_async_list_head->ring[slot].lock); ai = _async_list_head->ring[slot].lstart; if(ai!=NULL) _async_list_head->ring[slot].lstart = ai->next; lock_release(&_async_list_head->ring[slot].lock); if(ai==NULL) break; if(ai->act!=NULL) tmb.t_continue(ai->tindex, ai->tlabel, ai->act); } Changed code: while(1) { lock_get(&_async_list_head->ring[slot].lock); ai = _async_list_head->ring[slot].lstart; if(ai!=NULL) _async_list_head->ring[slot].lstart = ai->next; lock_release(&_async_list_head->ring[slot].lock); if(ai==NULL) break; if(ai->act!=NULL) { tmb.t_continue(ai->tindex, ai->tlabel, ai->act); shm_free(ai); /* Added by surendra */ } } Please correct this if I am wrong. Regards @surendra

1 0

Problem with special sip notify (trying to make central provisioning for endpoints)
by Pedro Niño 20 Feb '14

20 Feb '14

Hi, how are you all I have a lab setup for using Kamailio and asterisk, with realtime, and currently I am facing 2 problems. The first one, is when trying to get the phones to reboot. Asterisk send a notify with the message, reboot. But the phone answers with a 401, and asks for a digest. In a normal asterisk environment it would not be a problem, asterisk tries to answer with the user and password cipher with the digest. But because of using this design, asterisk sends the notify with the user and blank password (I am using realtime, so peers can register from kamailio with no password).of course this makes that the phone refuses, as the notify doesn't have the right password. Is there any way to make kamailio intercept the notify sent from the phone and answer with the right credentials? _------------------- Second: When having the users registered in the same scenario, and get an asterisk 'reload', and the users try to make a call before they re-register, only the first call make it thru Of course, as kamailio is in the middle, the users doesnt notice until they try to make a call. In asterisk, I keep seeing the kamailio trying to register and getting a 404. This keeps happening until I sent a sip reload at the asterisk side and wait for the users to register before making calls. Thanks for your time....

1 0

8 digit restriction on dialplan
by phillman25 20 Feb '14

20 Feb '14

Dear List I am trying to restrict 8 digit dial on my dialplan after the prefix 6859A , could someone help me with the correct syntax? Please see below what i have: Dpid: 1 Pr: 1 Match Op: 1 Match Exp: sip:6859A(only 8 additional digits allowed).* Match Len: 0 Subst Exp: sip:6859A(only 8 additional digits allowed).* Repl Exp: 3005A1883(a)xx.xx.xx.xx So basically any 8 digits after the prefix 6859A is allowed otherwise there shouldn't be a match, how could i go about doing this? Thanks in advance Phillip

1 0

Error in carrierroute in kamailio 4.1
by Eduardo Alonso 20 Feb '14

20 Feb '14

Hi all: It's my first mail to the community and I know that will be a great community to share knowledge. OS Debian 6.4 Kamailio 4.1 I have the same problem that Oliver Roth describes in http://lists.sip-router.org/pipermail/sr-users/2013-October/080096.html, but in Kamailio 4.1: Module carrierroute not working starting from version kamailio 4.1 trying to activate carrierroute in kamailio.cfg loadmodule "carrierroute.so" i get the following error when starting kamailio (5794) ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </usr/local/lib64/kamailio/modules/carrierroute.so>: /usr/local/lib64/kamailio/modules/carrierroute.so: undefined symbol: cfg_set_error_function 0(5794) : <core> [cfg.y:3408]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 245, column 12-28: failed to load module ERROR: bad config file (1 errors) Any idea? Maybe him o someone has the solution. Thanks all for your great work. Best regards. -- *Eduardo Alonso Gil* VoIP Systems Engineer @ Quobis <http://www.quobis.com/> | e: eduardo.alonso(a)quobis.com | t: +34902999465 Visit our booth at *MWC Barcelona*. CS60 Spanish Pavilion. More info<http://www.quobis.com/index.php?option=com_content&task=view&id=236&Itemid=…>

1 0

Issues with keepalive_timeout
by Kristian Kielhofner 20 Feb '14

20 Feb '14

Hello All, I'm trying to use keepalive_timeout with 4.1.1 as described here: http://lists.sip-router.org/pipermail/sr-users/2012-August/074337.html I believe I've followed these configuration steps and those defined in the nathelper module. Here are the relevant portions of my config: modparam("nathelper", "natping_interval", 60) modparam("nathelper", "keepalive_timeout", 180) modparam("nathelper", "ping_nated_only", 0) modparam("nathelper", "sipping_from", "sip:pinger@domain.com") modparam("nathelper", "sipping_method", "OPTIONS") modparam("nathelper", "sipping_bflag", 9) And of course a setting the correct branch flag (verified) during REGISTER handling: setbflag(9); My goal is to use SIP OPTIONS messages to verify the reachability of all of my endpoints (not just NATd ones). I would just lower my re-registration timeout but there are other issues associated with that kind of change. With my current configuration (after a successful registration) a SIP OPTIONS message is sent and replied to: U 4.2.2.1:5060 -> 4.2.2.2:5060 OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0. Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0. From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-9627292. To: sip:user372@4.2.2.2:5060;ob. Call-ID: 8af79586-93072f43-7c4cf55(a)4.2.2.1. CSeq: 1 OPTIONS. Content-Length: 0. . U 4.2.2.2:5060 -> 4.2.2.1:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 4.2.2.1:5060;received=4.2.2.1;branch=0. Call-ID: 8af79586-93072f43-7c4cf55(a)4.2.2.1. From: <sip:pinger@domain.com>;tag=uloc-5303810e-7c78-1-2273f0eb-9627292. To: <sip:user372@4.2.2.2:5060>;tag=0;ob. CSeq: 1 OPTIONS. Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS. Accept: application/sdp, application/pidf+xml, application/xpidf+xml, application/simple-message-summary, message/sipfrag;version=2.0, application/im-iscomposing+xml, text/plain. Supported: replaces, 100rel, timer, norefersub. Allow-Events: presence, message-summary, refer. User-Agent: My_UA. Content-Length: 0. . If I kill the registered UA (making it unavailable) Kamailio endlessly sends OPTIONS messages, never receives a reply, and never removes the registration from usrloc: U 4.2.2.1:5060 -> 4.2.2.2:5060 OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0. Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0. From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-b627292. To: sip:user372@4.2.2.2:5060;ob. Call-ID: 8af79586-b3072f43-f35cf55(a)4.2.2.1. CSeq: 1 OPTIONS. Content-Length: 0. . U 4.2.2.1:5060 -> 4.2.2.2:5060 OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0. Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0. From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-c627292. To: sip:user372@4.2.2.2:5060;ob. Call-ID: 8af79586-c3072f43-b75cf55(a)4.2.2.1. CSeq: 1 OPTIONS. Content-Length: 0. . U 4.2.2.1:5060 -> 4.2.2.2:5060 OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0. Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0. From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-d627292. To: sip:user372@4.2.2.2:5060;ob. Call-ID: 8af79586-d3072f43-7b5cf55(a)4.2.2.1. CSeq: 1 OPTIONS. Content-Length: 0. . U 4.2.2.1:5060 -> 4.2.2.2:5060 OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0. Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0. From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-e627292. To: sip:user372@4.2.2.2:5060;ob. Call-ID: 8af79586-e3072f43-3f5cf55(a)4.2.2.1. CSeq: 1 OPTIONS. Content-Length: 0. . (and on, and on, and...) Eventually the registration timeout kicks in, the usrloc entry is removed, and Kamailio stops sending OPTIONS to the (long) unreachable endpoint. Is this expected behavior? What am I doing wrong? Thanks! -- Kristian Kielhofner

3 11

Re: [SR-Users] Regd. MAX_LDG_LOCKS
by Daniel-Constantin Mierla 20 Feb '14

20 Feb '14

Hello, setting the hash size to 32MB is way too much, are you having like 100 000 000 active calls at the same time? The size of the hash is used for computing the number of slots in the hash table, not the capacity in terms of memory size of all items stored in hash table. Cheers, Daniel On 03/02/14 07:33, Shankar wrote: > > Hi Alex, > > We set the hash size to 32 MB and found that the hash size is not the > same as configured one. At the max it was taking 64KB. > > Regards, > > Shankar > > Date: Mon, 03 Feb 2014 00:27:29 -0500 > > From: Alex Balashov <abalashov(a)evaristesys.com > <mailto:abalashov@evaristesys.com>> > > To: sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> > > Subject: Re: [SR-Users] Regd. MAX_LDG_LOCKS > > Message-ID: <52EF28C1.5010204(a)evaristesys.com > <mailto:52EF28C1.5010204@evaristesys.com>> > > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 02/03/2014 12:22 AM, Shankar wrote: > > > Also we found that in ?dialog.c? the variable dlg_hash_size should be > > > ?unsigned int?. Hope this will be taken care in next release of > Kamailio. > > How did you arrive at that conclusion? > > -- > > Alex Balashov - Principal > > Evariste Systems LLC > > 235 E Ponce de Leon Ave > > Suite 106 > > Decatur, GA 30030 > > United States > > Tel: +1-678-954-0670 > > Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ > > *From:*Shankar [mailto:shankar.rk@plintron.com] > *Sent:* Monday, February 03, 2014 10:53 AM > *To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List' > *Subject:* Regd. MAX_LDG_LOCKS > > Hello, > > Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c? > > Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if > the hash size is increased? > > Also we found that in ‘dialog.c’ the variable dlg_hash_size should be > ‘unsigned int’. Hope this will be taken care in next release of Kamailio. > > Regards, > > Shankar > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Re: [SR-Users] Regd. MAX_LDG_LOCKS
by Daniel-Constantin Mierla 20 Feb '14

20 Feb '14

Hello, it is not a really necessary to increase the value of the locks. For better performances you can do it, but again, it is not a must. Cheers, Daniel On 04/02/14 06:50, Shankar wrote: > > Hi, > > Can someone clarify here please? > > Regards, > > Shankar > > *From:*Shankar [mailto:shankar.rk@plintron.com] > *Sent:* Monday, February 03, 2014 10:53 AM > *To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List' > *Subject:* Regd. MAX_LDG_LOCKS > > Hello, > > Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c? > > Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if > the hash size is increased? > > Regards, > > Shankar > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Kamailio 4.1 Installation from Source
by Francesco Maria Magnini 19 Feb '14

19 Feb '14

Hi, following the documentation, the following lines need to be updated on the init.d script. DAEMON=/usr/local/sbin/kamailio CFGFILE=/usr/local/etc/kamailio/kamailio.cfg Anyway, there is no CFGFILE already setted. Is it correct to add CFGFILE along with DAEMON? On top of this, in the check_fork () procedure, there’s a reference to a cfg_file that is nonexistent. In my installation i changed it to the real path of the kamailio.cfg file generated during installation. check_fork () { if grep -q "^[[:space:]]*fork[[:space:]]*=[[:space:]]*no.*" /usr/local/etc/kamailio/kamailio.cfg; then log_failure_msg "Not starting $DESC: fork=no specified in config file; run /etc/init.d/kamailio debug instead" exit 0 fi } Is it correct to change path in the check_fork procedure with the correct one? Regards,

2 2

Kamailio World - Presentations
by Daniel-Constantin Mierla 19 Feb '14

19 Feb '14

Only very few presentations accepted at Kamailio World Conference & Exhibition are not yet published. In a matters of days we should have the draft of the schedule published. It is again a good variety of topics around Kamailio and other open source VoIP applications, presenting experiences from the field, showing new product and solutions or open debate and demos panels. You can lean about various ways of deploying scalable platforms with Open Stack, Erlang or asynchronous, carrier grade charging systems, managing security in VoIP deployments or how to do real time troubleshooting. More details about presentations are available at: - http://conference.kamailio.com/k02/schedule/ Information about speakers can be found at: - http://conference.kamailio.com/k02/speakers/ In order to allow a fair enough time to see what the content of the event is going to be, the early registration deadline has now been set to this Friday, February 21. Don't miss the chance to learn from about 30 sessions and meet more than one hundred professionals in real time communications and open source technologies: - http://conference.kamailio.com/k02/registration/ Looking forward to meeting you in Berlin, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

uac_reg_request_to
by Isaac McDonald 19 Feb '14

19 Feb '14

Hello All, I need some clarification on the function uac_reg_request_to. The doc says "This function can be used to send an authenticated request to a remote user in the uac registrations table" Does this mean I can forward a SUBSCRIBE request, or any request for that matter, to an upstream server that's Kamailio is registered to via the UAC module? Secondly, I'm having trouble matching the user on this function. The error is: "ac [uac_reg.c:996]: uac_reg_request_to(): no user: 2503" User 2503 does exist in the uac_reg table in column "l_username". What if I want to match by UUID instead? How does that get mapped back to a local user? Thanks -- Isaac McDonald SusCall, LLC E-Mail: imcdona(a)suscall.com

1 0

Memory leak in http_query() function (utils module)
by Guillaume Bour 18 Feb '14

18 Feb '14

Hi folks, We identified a memory leak in *utils* module, when calling the http_query() function. a memory piece is allocated with malloc() to store http request result string (functions.c:54), but this memory is never freed. There is also a possible crash issue, because curl_easy_getinfo() is called *after* curl_easy_cleanup(), which must not be done (see http://curl.haxx.se/libcurl/c/curl_easy_cleanup.html) I attached patches to fix those issues (applies to 4.0 branch) Regards, Guillaume Bour

2 5

error using siremis
by Rubi Mazaki 18 Feb '14

18 Feb '14

Hi I successfully install siremis 4.0.0 +kamailio 4.1 on my ubuntu (32 bit) server. Kamailio was installed successfully and I can now run "kamctl moni" and see a nice status screen. I had to setup again siremis (by deleting the install.lock and opening the localhost/siremis setup again) but one that was achieved I can now login in to the siremis site without errors. Now to the problem: Once I enter "groups" and press "add" I get the following error displayed: [2014-02-12 20:46:33 (GMT)] An exception occurred while executing this script: Error message: #8192, preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead Script name and line number of error: /home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compiler.class.php:270 *function:* errorHandler ( 8192, "preg_replace(): The /e modifier is deprecated, use preg_replace_...", "/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compi...", 270, Array(8) ) @ /home/rubi/siremis-4.0.0/openbiz/bin/sysheader.inc 117 *function:* userErrorHandler ( 8192, "preg_replace(): The /e modifier is deprecated, use preg_replace_...", "/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compi...", 270, Array(8) ) @ *function:* preg_replace ( "~\{\*(.*?)\*\}|\{\s*literal\s*\}(.*?)\{\s*/literal\s*\}|\{\s*php...", "'{php' . str_repeat(" ", substr_count('\0', " ")) .'}'", "<form id="{$ form.name}" name="{$form.name}"> <div style="paddin..." ) @ /home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compiler.class.php 270 *function:* _compile_file ( "/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail....", "<form id="{$form.name}" name="{$form.name}"> <div style="paddin...", Null ) @ /home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty.class.php 1484 *function:* _compile_source ( "/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail....", "<form id="{$form.name}" name="{$form.name}"> <div style="paddin...", Null, "/home/rubi/siremis-4.0.0/siremis/themes/default/template/cpl/%%2..." ) @ /home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty.class.php 1417 *function:* _compile_resource ( "/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail....", "/home/rubi/siremis-4.0.0/siremis/themes/default/template/cpl/%%2..." ) @ /home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty.class.php 1256 *function:* fetch ( "/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail...." ) @ /home/rubi/siremis-4.0.0/openbiz/bin/easy/FormRenderer.php 95 *function:* renderSmarty ( Object(EasyForm), "/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail...." ) @ /home/rubi/siremis-4.0.0/openbiz/bin/easy/FormRenderer.php 45 *function:* render ( Object(EasyForm) ) @ /home/rubi/siremis-4.0.0/openbiz/bin/easy/EasyForm.php 1648 *function:* renderHTML ( ) @ /home/rubi/siremis-4.0.0/openbiz/bin/easy/EasyForm.php 1538 Can anyone tell me what I did wrong, or how can I re-install completely siremis? Hopefully that's not a bug :/ With Regards, Rubi Mazaki Email: rubimazaki(a)gmail.com

2 1

One more question 'bout db_mode
by Victor V. Kustov 18 Feb '14

18 Feb '14

Hi all! my usrloc database use postgress. In config I had: modparam("usrloc", "db_mode", 1) after day of work I see strange thing: # kamctl ul show --brief | grep -c AOR 26 psql -U kamailio -c "select * from location;" ... (1 row) 26 registered users in inner kamailio's memory and only 1 in database. See in doc: 1 - Write-Through scheme. All changes to usrloc are immediately reflected in database too. This is very slow, but very reliable. Use this scheme if speed is not your priority but need to make sure that no registered contacts will be lost during crash or reboot. I think saved locations in inner memory database must be identical. Am I wrong? -- WBR, Victor JID: coyote(a)bks.tv JID: coyote(a)bryansktel.ru I use FREE operation system: 3.12.9-calculate GNU/Linux

1 0

Change table type...
by arun Jayaprakash 18 Feb '14

18 Feb '14

Hello, I am planning to change the table type in the Kamailio Mysql db from MyISAM to Innodb. Could anyone let me know if this will be an issue? Thank you. Arun

2 2

modify To header, prefix + ip, using dispacher module.
by Helena Garcia-Nieto 17 Feb '14

17 Feb '14

Hey, Thank you in advanced for the time taken on my question! I have an environment phone---sbc---kamailio---gw1, gw2 I am using kamailio 4.2.0, quite basic config, using dispatcher module to route to the gw and to monitor them with options. I have a file dispatcher.list with the two gw ips: # $Id$ # dispatcher destination sets # # line format # setit(int) destination(sip uri) flags(int,opt) priority(int,opt) attributes(str,opt) # gateways 1 sip:10.X.X.38:5060 IP 1 sip:10.X.X.39:5060 AP I have to modify the TO header, it must be prefixed and gw ip must be placed there (gw requirements) I use on the routing function ds_select_domain("1", "8") t_on_failure("RTF_DISPATCH"); and just before the ROUTE(RELAY) I have: # Add profix to gw: 0199 subst_uri('/^sip:(.*)/sip:0199\1/i'); # add prefix to RURI subst_hf("To", "/(.*):(.*)@(.*)$/\1:0199\2@$rd>/", "a"); #add prefix to TO, modify ip on TO use ruri ip It works fine if the first gw is available, but if the first option (which is the last gw on the list) is not accessible, it waits for the 30s and then tries the second one, but the ip on the TO header is not correct anymore, since it is the first gw and not the second. Question: why does it wait until the timeout if it is monitoring it with option and seeing it is not reachable? I tried modifying again the TO header with: subst_hf("To", "/(.*)@(.*)$/\1@$rd>/", "a") before the route(relay) on the failure routine, but it does not work properly, I am getting strange TO header like: To: <sip:0199XXXX@10.X.X.39> <sip:XXXXXX@10.X.X.38> It looks like it is not parsing the to header it has before but adding a parsed version of the original header at the end of the other one.... I tried with subst as well but the result is more or less the same. Probably there is a better way to set the prefix and the correct IP on the to header... I'll appreciate any help with this issue. Thanks again for your time Helena Helena Garcia-Nieto de Mir Morodo Group VoIP Department E-mail: helena.gnieto(a)morodo.co.uk Morodo Limited voip(a)morodo.co.uk / www.mo-call.com Place of Registration: Companies House, England & Wales / Registered Office: 7 Breasy Place, 9 Burroughs Gardens Hendon, London NW4 4AU

4 12

deb.kamailio.org down?
by Paul Belanger 17 Feb '14

17 Feb '14

Anybody know why deb.kamailio.org is down? Is there a mirror setup some place else? -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belanger(a)polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger

3 2

Re: [SR-Users] Msilo message body type
by sipatse＠in.gr 16 Feb '14

16 Feb '14

2 1

Kamailio call forward help
by Sajan Thomas 16 Feb '14

16 Feb '14

Hi sir, I have 2 server running with kamailio.I have tested in both with creating two users and chat using jitsi client. Please help me with 1.How can i implement kamailio call forward? suppose if make achat or call to kamailio server on user shoud can access the same from kamailio server 2. 2.Is there any possible modules are available for kamailio Please help me i am really got stuck here. Expecting your kind reply.

1 1

Error with ACK from SIPML5
by Jayesh Nambiar 14 Feb '14

14 Feb '14

Hello All, I have a setup which is SIPML5 -> Kamailio(Websocket) -> Freeswitch. All I am trying to do is initiate a call from SIPML5 and Play a Music file from freeswitch. This works, but the call hangs up after 30 seconds due to ACK timeout from from the SIPML5. What I can see is the SIPML5 from Chrome does send an ACK on websocket, but I see the following error in kamailio syslog: *via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found* *ERROR: <core> [msg_translator.c:1725]: build_req_buf_from_sip_req(): could not create Via header* *ERROR: <core> [forward.c:607]: forward_request(): ERROR: forward_request: building failed* *ERROR: sl [sl_funcs.c:371]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL)* Can someone help me understand what I am missing here and why kamailio is not able to create a VIA header to forward this request towards freeswitch. I have built a simple config file by following https://gist.github.com/jesusprubio/4066845 as reference. Any help in understanding this is really appreciated. Thanks, --- Jayesh

4 11

websocket.so module not generated
by Alvaro Urionabarrenetxea Gomez 14 Feb '14

14 Feb '14

Hi. I have a problem when I'm trying to start with my Kamailio server. I have an error about not existing "websocket.so" module. Here is the error: root@kamailio:# /etc/init.d/kamailio start ** Not starting Kamailio SIP server: invalid configuration file!* *** ** 0 (8327) ERROR: <core> [sr_module.c:587]: load_module(): ERROR: load_module: could not find module <websocket> in </usr/local/lib/kamailio/modules/>* *0(8327) : <core> [cfg.y:3408]: yyerror_at(): parse_error in config file /usr/local/etc/kamailio/kamailio.cfg, line 318, column 12-25: failed to load module* *ERROR: bad config file (1 errors)* *** And here is the line 318 in kamailio.cfg: *loadmodule "websocket.so"* I looked for that module in the correspondent folder but isn't there. Can anyone upload the websocket.so file to another mirror, MEGA for example? I tried to generate another time, download another kamailio versions but the error stills there. Much apreciated. Thanks!

1 0

FW: Client site NAT negotiation with no STUN.
by Rob Moore 14 Feb '14

14 Feb '14

Hi there. So I'm fighting what must be a bit of a common problem here but the usual googling isn't really helping me out. A bit of background: Classic Nat scenario of a sip handset behind a NAT firewall over the internet to VoIP SBC setup using Kamailio 3.3 and RTPProxy and Freeswitch as the registrar / calls server behind kamailio. (please excuse the beautiful ASCI art) -------------- ---- ----| RTPproxy |------- --------------- ------------ | -------------- | --------------- |SIP Phone|--------|Firewall |---------internet-------------| kamailio |-----------|Freeswitch| --------------- ------------ -------------- --------------- SIP Phones can register fine (over TCP or TLS, Kam offloads TLS if used) however when establishing a call the SIPPhone sends its local network IP address within the SDP instead of the firewalls external address. Causing media to me miss directed by the RTP Proxy. I've put a phone in with STUN to check that this is the only issue and that phone works fine .Usually in this situation we would just use STUN or TURN / ICE to get around the issue however the handsets that we are working with (and have to work with for other reasons) do not support any of these technologies. So I've been forced to try and find another solution. I was hoping to find some method within kamailio / RTPproxy to resolve this. I could just rewrite the SDP in certain situations but that feels a little bit brutal if I'm honest. I've heard of RTPproxy being able to do some sort of rtp latching where it can correct its destination ip address after it receives its first rtp packets from the SIP Phone after being forwarded by the onsite firewall but other than this 'word of mouth' suggestion I've not managed to find any detail of this functionality in the usual online resources. Can anyone suggest any other potential methods for getting around this problem? Many Thanks Rob

2 3

SSL connection issue
by Owais ul Haq 14 Feb '14

14 Feb '14

Hello, I have installed kamailio server. Now I am trying to use SSL for my server - client connections. I have made certificates succesfully. Now when my client connects, I get the following error. [tcp_read.c:882] : ERROR : TLS accept : error : 1408F10B : SSL routines:SSL3_GET_RECORD:wrong version number I have tried finding solution online. I am asked to change the version number. Can some one please tell me where I have to change the version number ?? And change it to what ?? Thanks. Cheers, Owais

2 2

Problem with SSL version number
by Owais ul Haq 14 Feb '14

14 Feb '14

Hi kamailians, I am trying to connect kamailio and use TLS between kamailio and client. I could not get any tls_method to work. Openser error messages for each method are listed below: with tls_method=SSLv2: " tls_accept: Error in SSL: 3(8332) tls_error: error:140EC0AF:SSL routines:SSL2_READ_INTERNAL:non sslv2 initial packet " with tls_method=SSLv3 or tls_method=TLSv1: " 3(8386) tls_accept: Error in SSL: 3(8386) tls_error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number " With tls_method=SSLv23: " 3(8403) tls_accept: Error in SSL: 3(8403) tls_error: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol " I am making these changes in tls.cfg. Can someone please tell what changes are required ?? Thanks Cheers, Owais.

2 1

Re: [SR-Users] Suggestion for VOIP Solution
by DanB 14 Feb '14

14 Feb '14

That is not entirely true. We use MySQL without any kind of issues via ODBC driver. DanB On 14.02.2014 10:18, sr-users-request(a)lists.sip-router.org wrote: > Asterisk would be suitable solution, FREESwitch is also fine, but with > FREESwitch latest version uses postgreSQL, and removed support for MySQL, > if you are comfortable with postgreSQL for reporting stuffs like that then > you can proceed with FREESwitch. > > Regards > > > > Thank you with regards, > Gopalkrishnan N. > Mob: +91 99404 91346 > VoIP call -sip:saigop@gtalk2voip.com

1 0

Suggestion for VOIP Solution
by Vijay Thakur 14 Feb '14

14 Feb '14

Hi All List Members, I have worked on kamailio for one year. It is a great open source Skype like solution. Now i have to deploy a new solution with new requirements. Kindly suggest that what will be the best open source application will fulfill my requirements. I need the following facilities: (1) Call Recording (Outbound/Inbound) (2) On Demand Recording (3) Dictation Service (4) Complex Inbound Routing (5) IVR (Interactive Voice Response) (6) Auto Attendant (7) Client Recordings Mgmt & Playback Portal (8) Multi-level Client hierarchy / Subscription Plans (9) Voicemail (10) Time based Routing (Message Box) (11) Call Queuing & Conferencing (12) Bulk Download & Emailing (13) Call Whisper (14) Smartphone apps (SIP clients) Regards, /

5 4

understanding the sqlops module and kamailio children.
by Uri Shacked 13 Feb '14

13 Feb '14

Hi, Lately i am experiencing some issues with the sqlops module. let's say, for example, that i use sqlops to query some information about the subscriber when an INVITE arrives. I use kamailio 3.3.2, MySQL 5.6 and the DB server is remote and not local. Usually, the DB result is very fast and the call continues. But, when the DB is unavailable, or slow, the result is delayed or lost. In this case: 1. What is the query time out in kamailio? 2. If the database is available but slow, does it mean that no new INVITE will be dealt by the current child process until the sqlops is gone? 3. does anyone has a good idea for managing sqlops in a call? Thanks, Uri

2 2

How do I allow any user to register? And why doesn't a call reach the other end in my case?
by Victor Sergienko 13 Feb '14

13 Feb '14

Hi, I'm pretty ignorant about Kamailio, sorry for it and possible terminology mistakes. I'd like to allow any user to register. Ideally, I'd like to make some script (Lua/whatever) function to check some data encoded in a username and allow registering based on that username only. I undefined WITH_AUTH in kamailio.cfg, and it used to work for me; but sometimes I'm starting to get "SIP Progress: 100 trying -- your call is important to us ()" and the call never reaches the other party. Here's a sample of my logs during the failed call: https://gist.github.com/singalen/c343f09b67dcf7731fe0 What is the problem here? I start and stop the clients all the time, so there might be some garbage registrations accumulated. I assume I also need a user registration to discard all his previous registrations? Thank you!

1 0

$var binary operation
by Jijo 13 Feb '14

13 Feb '14

Hi I tried the binary operation using $var as per the documentation and its seems not working. Can somebody help me to understand it. http://kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x $var(a) = 3 + (7&(~2)); if( [ $var(a) & 4 ] ) { xlog("var a has third bit set\n"); } The format with square bracket in the conditional statement is showing parse error when i load the cfg. So it tried like below and that too not working $var(a) = 8; if( $var(a) & 4 ) { xlog("var a has third bit set\n"); } Please let me know if something missing here.? Thanks Jijo

2 2

core generated - 502 Bad gateway
by Tuan Viet Nguyen 13 Feb '14

13 Feb '14

Hello, Upon receipt an 502 Bad gateway, I have the following error then Kamailio crashed Feb 11 11:49:57 kamailio23 /usr/local/sbin/kamailio[28895]: WARNING: tm [t_lookup.c:1564]: t_unref(): WARNING: script writer didn't release transaction Feb 11 11:50:03 kamailio23 /usr/local/sbin/kamailio[28926]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 31 Feb 11 11:50:03 kamailio23 /usr/local/sbin/kamailio[28876]: ALERT: <core> [main.c:788]: handle_sigs(): child process 28903 exited by a signal 11 Feb 11 11:50:03 kamailio23 /usr/local/sbin/kamailio[28876]: ALERT: <core> [main.c:791]: handle_sigs(): core was generated (gdb) bt #0 0x000000000053a81d in qm_free (qm=0x7fd6f962a000, p=0x75d63ff100000000) at mem/q_malloc.c:476 #1 0x00007fd700c5581c in free_cell (dead_cell=0x7fd6f9777bf0) at h_table.c:162 #2 0x00007fd700c56783 in free_hash_table () at h_table.c:443 #3 0x00007fd700c6981b in tm_shutdown () at t_funcs.c:122 #4 0x00000000004ee6f0 in destroy_modules () at sr_module.c:790 #5 0x0000000000463baa in cleanup (show_status=1) at main.c:573 #6 0x0000000000464c32 in shutdown_children (sig=15, show_status=1) at main.c:715 #7 0x0000000000466223 in handle_sigs () at main.c:806 #8 0x000000000046a459 in main_loop () at main.c:1767 #9 0x000000000046ca85 in main (argc=5, argv=0x7fff2f13ec38) at main.c:2566 (gdb) bt full #0 0x000000000053a81d in qm_free (qm=0x7fd6f962a000, p=0x75d63ff100000000) at mem/q_malloc.c:476 f = 0x75d63ff0fffffff0 size = 4880 next = 0x7fd6f98c5380 prev = 0x7fd6f9634840 __FUNCTION__ = "qm_free" #1 0x00007fd700c5581c in free_cell (dead_cell=0x7fd6f9777bf0) at h_table.c:162 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x59e92da4 cbs = 0x0 cbs_tmp = 0x7fd6f98c5370 __FUNCTION__ = "free_cell" #2 0x00007fd700c56783 in free_hash_table () at h_table.c:443 p_cell = 0x7fd6f9777bf0 tmp_cell = 0x7fd6f98fb9c0 i = 3084 #3 0x00007fd700c6981b in tm_shutdown () at t_funcs.c:122 __FUNCTION__ = "tm_shutdown" #4 0x00000000004ee6f0 in destroy_modules () at sr_module.c:790 t = 0x7fd7022322f0 foo = 0x7fd702231cc0 #5 0x0000000000463baa in cleanup (show_status=1) at main.c:573 memlog = 32727 __FUNCTION__ = "cleanup" #6 0x0000000000464c32 in shutdown_children (sig=15, show_status=1) at main.c:715 __FUNCTION__ = "shutdown_children" #7 0x0000000000466223 in handle_sigs () at main.c:806 chld = 0 chld_status = 139 memlog = 0 __FUNCTION__ = "handle_sigs" #8 0x000000000046a459 in main_loop () at main.c:1767 i = 8 pid = 28926 si = 0x0 si_desc = "udp receiver child=7 sock=91.213.79.31:5060\000\326\177", '\000' <repeats 18 times>, "@\352\023/\377\177\000\000\244-\351Y\000\000\000\000\240mA\000\000\000\000\000\060\354\023/\377\177", '\000' <repeats 18 times>, "p\352\023/\377\177\000\000\030>K\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #9 0x000000000046ca85 in main (argc=5, argv=0x7fff2f13ec38) at main.c:2566 cfg_stream = 0xc36010 c = -1 r = 0 tmp = 0x7fff2f13ec68 "\233\356\023/\377\177" tmp_len = 0 port = 5 proto = 0 options = 0x5c7c18 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 3628627122 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0xbf p = 0x4162c9 "H\203\304\b\303" <Address 0x4162ce out of bounds> __FUNCTION__ = "main" (gdb) Regards,

2 2

Call forwarding from external did
by arun Jayaprakash 12 Feb '14

12 Feb '14

Hello, I have set up call forwarding in Kamailio using user_preference table. When I make a call from a local extension the callfwd funcition works. The call gets forwarded to an external did number. The problem happens when and external call ( from a DID) comes to this extension the call does not get forwarded. I had to comment out the following lines in the config file to make it work: # only local users allowed to call # if((from_uri!=myself)) { # sl_send_reply("403", "Not Allowed"); # exit; # } My question is if it is a risky think to comment out these lines? If so, what are my options. Thank you, Arun

2 3

ice problems
by jaflong jaflong 12 Feb '14

12 Feb '14

I am having problems with calls from webrtc to kamailio forwarded to Asterisk These are snippet of the debug logs Asterisk CSeq: 4910 BYE Reason: SIP ;cause=488; text="Not Acceptable Here" Supported: path, outbound, gruu User-Agent: JsSIP 0.3.0 Content-Length: 0 Jssip Cause: Bad Media Description Origin: remote Searching on google I get some indication this is to do with ice config? Please can some one suggest if this is so. In my scenerio the webrt clients will only call to the asterisk server (and not to other user agent). Considersing this I think maybe can do without ice. Is it possbile to disable ice.

3 2

About a bug when registering a Tandberg (Cisco) E20 to Kamailio - Crash Segfault at 18 IP - error 4 in auth_db.so
by Pedro Niño 12 Feb '14

12 Feb '14

Kamailio is having a crash (Segfault at 18 IP - error 4 in auth_db.so) when registering a cisco E20, via SIP Here is a full dbg backtrack, and the core dump, but have no ideas about how to proceed. Im using Kamailio 4.1.1: Got this Error at /var/log: [14629359.586980] kamailio[982]: segfault at 18 ip 00007f034db8dcfd sp 00007fff34702950 error 4 in auth_db.so[7f034db85000+c000] Kamailio Version: ---------- version: kamailio 4.1.1 (x86_64/linux) d6ffa1 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: d6ffa1 compiled on 16:28:48 Jan 29 2014 with gcc 4.4.5 ------------- Thanks in Advance.

2 2

reSIProcate v1.9.0 released
by Daniel Pocock 11 Feb '14

11 Feb '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The v1.9.0 release has been tagged (r10958) and made available for download: https://www.resiprocate.org/files/pub/reSIProcate/releases/ The release info page is here: http://www.resiprocate.org/ReSIProcate_1.9_Release and a direct link to the ChangeLog in SVN: https://svn.resiprocate.org/rep/resiprocate/tags/resiprocate-1.9.0/ChangeLog Debian, Fedora and Ubuntu packages have been updated, automated builds are in progress and they should be available shortly. Highlights of the v1.9.0 release: * Session/registration accounting * SIP over WebSocket support for WebRTC, with cookie authentication option * Python scripting for repro routes * repro dynamically-loaded routing plugins * UAS PRACK * Improvements to daemon processes for UNIX/Linux users * Android support * Multiple users in reTurn * Many stability/bug fixes SHA224 checksums for the files: resiprocate-1.9.0.tar.gz 914b01c4633e0fc03f085fdfc77199577ac079c848c35e7f04c8d344 resiprocate-contrib-1.9.0.tar.gz 444b05ae9986a43d25347e7ea4908ab3d02a1bba4d70f0744de1da11 Contributors to v1.9.x include Scott Godin, Eric Rescorla, Adam Roach, Byron Campen, Jason Fischl, Francis Joanis, Matthias Moetje, Catalin Constantin Usurelu and Daniel Pocock. We are also very grateful to all those who contributed feedback through the mailing list, testing the beta packages in Debian and all past contributors to previous releases of the reSIProcate project. Any and all feedback is welcome -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJS+m+0AAoJEOm1uwJp1aqD2v4P/2/QVY5WPJ6eb7sjf/ZQ5PDs 99ed+Yy7dIRw4KqX6b4qqADesHxrvABr0mAWFTjVqJa9qWDzSINspKZyP0cq4jEi Kj1rIaGPP9cDwrlc6zAPWx+XYJSSJG/79uZYa3y6y2yV1Yupd5QM4kgCj5ZhsshN nkgtzLvpxWqyXN8ISQ415Z2kmoIQGbLpcCcKb+zQUlmyYTyUny7NB31BSGQ5Ob8N 3/t/zvyA4vee0YhoY72TfHvpdfjmDDE98x5s2UWjHg1BWDcSzthFk41TYDiPFEJt YIHPQHFKFSoyW1oa5mmsMcFbumUnhElXQsIUC1EBYUtJIl//wEL+1cZayth4GkTz klhXM5OjFs1qWn30EyGnZPMJbdAey+P2nn/EE+8XgRBxHyYI0T7zOjrcXXdBaAbX VXlRaqkb9IvpAtVuNdQWrMFBAlejIKrQs3NKTLXdW9ym3SdF8E75jr5rzILq3aWk RzAdD4HZg2ym9BIW9+jYlEmIwC5eE+C89NBCwia7K+QYf77U4Yjf89LXFUZa0L4D eGQ+aBA21qtV4bfGPf0XR+kdjqkk4erQtKxPgwIIgpDyPNnomy5nTS37v4gd0+1y hkJO0rqHSl/LeA5L2hCxkHpP8FZZ/QlmKs8niv63vfTjfldEHAAxARZG6/BDqM6H hJbfoaw7Wm3EsXj9QWYg =vu2w -----END PGP SIGNATURE-----

1 0

Kamailio World Updates
by Daniel-Constantin Mierla 11 Feb '14

11 Feb '14

From the first edition, Kamailio World tried to connect people and companies that can help each other or complement. If anyone is looking for new challenges in their career, don't hesitate to approach us. You can see more details at: - http://conference.kamailio.com/k02/2014/02/career-jobs/ Check also the Speakers <http://conference.kamailio.com/k02/speakers/> [1] and Schedule <http://conference.kamailio.com/k02/schedule/> [2] pages for new information about who is going to present and the topics. B eware of early registration period ending soon, so hurry up if you plan to attend the event – how to do it and other related details are in the Registration page <http://conference.kamailio.com/k02/registration/> [3]. Enjoy using Kamailio and looking forward to meet many of you in Berlin! Daniel/ / [1] - http://conference.kamailio.com/k02/speakers/ [2] - http://conference.kamailio.com/k02/schedule/ [3] - http://conference.kamailio.com/k02/registration/ -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Problem with Port=5061
by Owais ul Haq 10 Feb '14

10 Feb '14

Hello, I have configured TLS on kamailio server. I am done with all procedure of creation and installation of CA and site certificates. Problem is that in kamailio.cfg, when I use command port =5061. Kamailio doesnot start and error given in logs is >> ERROR: tcp_init : bind(a, 0x9007f4, 16) on MyIP:5061 : Adress already in use >> ERROR: Error while initializing TCP port of TLS Socket MyIP:5061 Point to note is that kamailio works fine with port=5062. Can somebody please help me in this regard. I will be so thankful. Cheers, Owais

4 4

Determining size of INVITE
by Daniel Tryba 10 Feb '14

10 Feb '14

How can I get the determine the total size of an outgoing INVITE? The size of the body is $bs, but is there a way to get the size of all headers? Based on the size of the total request I have to chose between UDP and TCP, upstream provider requires IP packets>1300 to be transmitted over TCP. Is there an easy way (like $bs) or should I just call msg_apply_changes() and loop through all headers and sum the lengths of them? -- POCOS B.V. - Croy 9c - 5653 LC Eindhoven Telefoon: 040 293 8661 - Fax: 040 293 8658 http://www.pocos.nl/ - http://www.sipo.nl/ K.v.K. Eindhoven 17097024

2 3

Get information in 'Reason' header field
by Tuan Viet Nguyen 10 Feb '14

10 Feb '14

Hello, How to get ISUP cause in the 'Reason' header field of SIP error reply ? I've tried a few ways but it did not work @message.header.Reason.params["cause"] or $hdr(Reason) gives null Thanks,

3 4

SNMP Monitoring
by Volkan Oransoy 09 Feb '14

09 Feb '14

Hi all, I have activated snmpstats module for my sip proxy. What I wonder is, which sensors are important to monitor a registrar and proxy? Which sensors do you use to monitor production servers? Thanks. /Volkan

1 0

Kamailio Admin Book
by omid mohajerani 09 Feb '14

09 Feb '14

Dear All , Would you mind tell me when is the Kamailio admin Book release time ? I want to start working with kamailio but it is very hard to start . Im sure this book will help me a lot . Regards Omid

2 2

Re: [SR-Users] Dialog
by Daniel-Constantin Mierla 09 Feb '14

09 Feb '14

Hello, do you need it in kamailio config or from an external application? From external application the mi/rpc command has to be used. Cheers, Daniel On 06/02/14 21:45, John Murray wrote: > > Hi, > > I need to get call-id and from-tag from a call in ringing state (2). > > If I use dlg_manage() and put the call into a profile using > set_dlg_profile("usr",”1"). > > Then do a avp_db_query() I don’t see the call until it is connected. > > I am using db_mode 1. > > Yet if I do a sercmd dlg.dlg_list I see the call in ringing state and > when it is connected. > > How do I get the call-id when it is in ringing state? > > Regards > > John > > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

3 7

"Locating SIP-Servers" problem
by Franz Edler 09 Feb '14

09 Feb '14

Dear all, I have a problem to verify the correct RFC 3263 behavior of Kamailio SIP Server v4.1. I have a basic configuration of two SIP servers one domains "net1.test" and the other for domain "net2.test". When I now setup a session between both domains (from sip:alice@net1.test to sip:bob@net2.test) I expect a NAPTR-, SRV- and A-query before forwarding the INVITE to the (inbound) proxy server of net2.test. But I instead get an error: 0(3994) ERROR: <core> [resolve.c:1733]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "net2.test" The trace-protocol shows only two A-queries - A-query for net2.test - A-query for net2.test.net1.test Why do I not get the NAPTR- and SRV-queries? BR Franz

2 2

Troubles with PERL module in Kamailio 3.3.5 and 4.0.3
by neumann 09 Feb '14

09 Feb '14

Hi everybody. Sorry for my bad english. Then i trying to use OpenSER module in my perl script i got the error: Can't locate object method "bootstrap" via package "OpenSER" at /usr/lib64/kamailio/perl//OpenSER/Message.pm line 33. Compilation failed in require at /usr/lib64/kamailio/perl//OpenSER.pm line 34. BEGIN failed--compilation aborted at /usr/lib64/kamailio/perl//OpenSER.pm line 34. Compilation failed in require at ./qutest.pl line 4. BEGIN failed--compilation aborted at ./qutest.pl line 4. This module is supported now? this is my script =))) ------------------------------------------ #!/usr/bin/perl use strict; use lib '/usr/lib64/kamailio/perl/'; use OpenSER; exit 0 ————————————————————— I using PERL 5.14.2 from debian wheezy repo. perv -V Summary of my perl5 (revision 5 version 14 subversion 2) configuration: Platform: osname=linux, osvers=3.2.0-4-amd64, archname=x86_64-linux-gnu-thread-multi uname='linux babin 3.2.0-4-amd64 #1 smp debian 3.2.46-1+deb7u1 x86_64 gnulinux ' config_args='-Dusethreads -Duselargefiles -Dccflags=-DDEBIAN -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Dldflags= -Wl,-z,relro -Dlddlflags=-shared -Wl,-z,relro -Dcccdlflags=-fPIC -Darchname=x86_64-linux-gnu -Dprefix=/usr -Dprivlib=/usr/share/perl/5.14 -Darchlib=/usr/lib/perl/5.14 -Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5 -Dvendorarch=/usr/lib/perl5 -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl/5.14.2 -Dsitearch=/usr/local/lib/perl/5.14.2 -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Dsiteman3dir=/usr/local/man/man3 -Duse64bitint -Dman1ext=1 -Dman3ext=3perl -Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Ud_ualarm -Uusesfio -Uusenm -Ui_libutil -DDEBUGGING=-g -Doptimize=-O2 -Duseshrplib -Dlibperl=libperl.so.5.14.2 -des' hint=recommended, useposix=true, d_sigaction=define useithreads=define, usemultiplicity=define useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef use64bitint=define, use64bitall=define, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O2 -g', cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='4.7.2', gccosandvers='' intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='cc', ldflags =' -fstack-protector -L/usr/local/lib' libpth=/usr/local/lib /lib/x86_64-linux-gnu /lib/../lib /usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib /usr/lib libs=-lgdbm -lgdbm_compat -ldb -ldl -lm -lpthread -lc -lcrypt perllibs=-ldl -lm -lpthread -lc -lcrypt libc=, so=so, useshrplib=true, libperl=libperl.so.5.14.2 gnulibc_version='2.13' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib -fstack-protector' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY PERL_DONT_CREATE_GVSV PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP PERL_PRESERVE_IVUV USE_64_BIT_ALL USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF USE_REENTRANT_API Locally applied patches: DEBPKG:debian/arm_thread_stress_timeout - http://bugs.debian.org/501970 Raise the timeout of ext/threads/shared/t/stress.t to accommodate slower build hosts DEBPKG:debian/cpan_definstalldirs - Provide a sensible INSTALLDIRS default for modules installed from CPAN. DEBPKG:debian/db_file_ver - http://bugs.debian.org/340047 Remove overly restrictive DB_File version check. DEBPKG:debian/doc_info - Replace generic man(1) instructions with Debian-specific information. DEBPKG:debian/enc2xs_inc - http://bugs.debian.org/290336 Tweak enc2xs to follow symlinks and ignore missing @INC directories. DEBPKG:debian/errno_ver - http://bugs.debian.org/343351 Remove Errno version check due to upgrade problems with long-running processes. DEBPKG:debian/libperl_embed_doc - http://bugs.debian.org/186778 Note that libperl-dev package is required for embedded linking DEBPKG:fixes/respect_umask - Respect umask during installation DEBPKG:debian/writable_site_dirs - Set umask approproately for site install directories DEBPKG:debian/extutils_set_libperl_path - EU:MM: Set location of libperl.a to /usr/lib DEBPKG:debian/no_packlist_perllocal - Don't install .packlist or perllocal.pod for perl or vendor DEBPKG:debian/prefix_changes - Fiddle with *PREFIX and variables written to the makefile DEBPKG:debian/fakeroot - Postpone LD_LIBRARY_PATH evaluation to the binary targets. DEBPKG:debian/instmodsh_doc - Debian policy doesn't install .packlist files for core or vendor. DEBPKG:debian/ld_run_path - Remove standard libs from LD_RUN_PATH as per Debian policy. DEBPKG:debian/libnet_config_path - Set location of libnet.cfg to /etc/perl/Net as /usr may not be writable. DEBPKG:debian/m68k_thread_stress - http://bugs.debian.org/517938 http://bugs.debian.org/495826 Disable some threads tests on m68k for now due to missing TLS. DEBPKG:debian/mod_paths - Tweak @INC ordering for Debian DEBPKG:debian/module_build_man_extensions - http://bugs.debian.org/479460 Adjust Module::Build manual page extensions for the Debian Perl policy DEBPKG:debian/prune_libs - http://bugs.debian.org/128355 Prune the list of libraries wanted to what we actually need. DEBPKG:fixes/net_smtp_docs - [rt.cpan.org #36038] http://bugs.debian.org/100195 Document the Net::SMTP 'Port' option DEBPKG:debian/perlivp - http://bugs.debian.org/510895 Make perlivp skip include directories in /usr/local DEBPKG:debian/cpanplus_definstalldirs - http://bugs.debian.org/533707 Configure CPANPLUS to use the site directories by default. DEBPKG:debian/cpanplus_config_path - Save local versions of CPANPLUS::Config::System into /etc/perl. DEBPKG:debian/deprecate-with-apt - http://bugs.debian.org/580034 Point users to Debian packages of deprecated core modules DEBPKG:fixes/hurd-ccflags - [a190e64] http://bugs.debian.org/587901 [perl #92244] Make hints/gnu.sh append to $ccflags rather than overriding them DEBPKG:debian/squelch-locale-warnings - http://bugs.debian.org/508764 Squelch locale warnings in Debian package maintainer scripts DEBPKG:debian/skip-upstream-git-tests - Skip tests specific to the upstream Git repository DEBPKG:fixes/extutils-cbuilder-cflags - [011e8fb] http://bugs.debian.org/624460 [perl #89478] Append CFLAGS and LDFLAGS to their Config.pm counterparts in EU::CBuilder DEBPKG:fixes/module-build-home-directory - http://bugs.debian.org/624850 [rt.cpan.org #67893] Fix failing tilde test when run under a UID without a passwd entry DEBPKG:debian/patchlevel - http://bugs.debian.org/567489 List packaged patches for 5.14.2-21+deb7u1 in patchlevel.h DEBPKG:fixes/h2ph-multiarch - [e7ec705] http://bugs.debian.org/625808 [perl #90122] Make h2ph correctly search gcc include directories DEBPKG:fixes/index-tainting - [3b36395] http://bugs.debian.org/291450 [perl #64804] RT 64804: tainting with index() of a constant DEBPKG:fixes/document_makemaker_ccflags - http://bugs.debian.org/628522 [rt.cpan.org #68613] Document that CCFLAGS should include $Config{ccflags} DEBPKG:fixes/sys-syslog-socket-timeout-kfreebsd.patch - http://bugs.debian.org/627821 [rt.cpan.org #69997] Use a socket timeout on GNU/kFreeBSD to catch ICMP port unreachable messages DEBPKG:fixes/hurd-hints - http://bugs.debian.org/636609 Improve general GNU hints, needed for GNU/Hurd. DEBPKG:fixes/pod_fixes - [7698aed] http://bugs.debian.org/637816 Fix typos in several pod/perl*.pod files DEBPKG:debian/find_html2text - http://bugs.debian.org/640479 Configure CPAN::Distribution with correct name of html2text DEBPKG:fixes/digest_eval_hole - http://bugs.debian.org/644108 Close the eval "require $module" security hole in Digest->new($algorithm) DEBPKG:fixes/hurd-ndbm - [f0d0a20] [perl #102680] http://bugs.debian.org/645989 Add GNU/Hurd hints for NDBM_File DEBPKG:fixes/sysconf.t-posix - [8040185] [perl #102888] http://bugs.debian.org/646016 Fix hang in ext/POSIX/t/sysconf.t on GNU/Hurd DEBPKG:fixes/hurd-largefile - [1fda587] [perl #103014] http://bugs.debian.org/645790 enable LFS on GNU/Hurd DEBPKG:debian/hurd_test_todo_syslog - http://bugs.debian.org/650093 Disable failing GNU/Hurd tests in cpan/Sys-Syslog/t/syslog.t DEBPKG:fixes/hurd_skip_itimer_virtual - [rt.cpan.org #72754] http://bugs.debian.org/650094 Skip interval timer tests in Time::HiRes on GNU/Hurd DEBPKG:debian/hurd_test_skip_sigdispatch - http://bugs.debian.org/650188 Disable failing GNU/Hurd tests op/sigdispatch.t DEBPKG:debian/hurd_test_skip_stack - http://bugs.debian.org/650175 Disable failing GNU/Hurd tests dist/threads/t/stack.t DEBPKG:debian/hurd_test_skip_pipe - http://bugs.debian.org/650187 Disable failing GNU/Hurd tests io/pipe.t DEBPKG:debian/hurd_test_skip_io_pipe - http://bugs.debian.org/650096 Disable failing GNU/Hurd tests dist/IO/t/io_pipe.t DEBPKG:fixes/manpage_name_CPAN - http://bugs.debian.org/650448 [rt.cpan.org #73396] cpan/CPAN: add NAME headings in modules with POD DEBPKG:fixes/manpage_name_CPANPLUS - http://bugs.debian.org/650450 [rt.cpan.org #73398] cpan/CPANPLUS: add NAME headings in modules with POD DEBPKG:fixes/manpage_name_Test-Harness - http://bugs.debian.org/650451 [rt.cpan.org #73399] cpan/Test-Harness: add NAME headings in modules with POD DEBPKG:fixes/manpage_name_Term-UI - http://bugs.debian.org/650452 [rt.cpan.org #73400] cpan/Term-UI: add NAME headings in modules with POD DEBPKG:fixes/podlators_ae_ligature_fallback - http://bugs.debian.org/652851 Fix the ASCII fallback string for AE DEBPKG:fixes/fsf_postal_address - [de89470] Update references to the FSF's postal address DEBPKG:fixes/cpan_module_pod_fixes - [perl #106870] [rt.cpan.org #73447] [rt.cpan.org #73446] Fix POD formatting in Term-Cap and Pod-Parser DEBPKG:fixes/cgi_no_shellwords_pl - Use Text::ParseWords instead of shellwords.pl DEBPKG:fixes/path_max_fallback - [perl #109262] http://bugs.debian.org/656869 Don't use _POSIX_PATH_MAX as a fallback PATH_MAX DEBPKG:debian/makemaker-pasthru - http://bugs.debian.org/660195 [rt.cpan.org #28632] Make EU::MM pass LD through to recursive Makefile.PL invocations DEBPKG:fixes/propagate_tainted_errors.patch - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663158 [perl #111654] properly propagate tainted errors DEBPKG:debian/perl5db-x-terminal-emulator.patch - http://bugs.debian.org/668490 Invoke x-terminal-emulator rather than xterm in perl5db.pl DEBPKG:fixes/socket_cache_propagate - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659075 [rt.cpan.org #61577] [perl #112736] sockdomain and socktype undef on newly accepted sockets DEBPKG:fixes/ipc_open3 - [perl #114454] http://bugs.debian.org/683894 IPC::Open3::open3(..., '-') broken DEBPKG:fixes/string_repeat_overrun - http://bugs.debian.org/689314 [b675304] avoid calling memset with a negative count DEBPKG:debian/cpan-missing-site-dirs - http://bugs.debian.org/688842 Fix CPAN::FirstTime defaults with nonexisting site dirs if a parent is writable DEBPKG:fixes/kfreebsd-overrides - http://bugs.debian.org/689713 [perl #115324] [7dc6565] Remove unnecessary overrides in gnukfreebsd and gnuknetbsd hints. DEBPKG:fixes/tainted-smartmatch - [be88a5c] http://bugs.debian.org/690571 [perl #93590] $tainted ~~ [...] failing DEBPKG:fixes/regexp-matching-starter - [6e634c5] http://bugs.debian.org/690975 [perl #101710] Regression with /i, latin1 chars. DEBPKG:fixes/regexp-matching-fold - [399fb9c] http://bugs.debian.org/690976 regexec.c: Fix "\x{FB01}\x{FB00}" =~ /ff/i DEBPKG:fixes/regexp-matching-opposite-case - [dc91d5a] http://bugs.debian.org/690979 [perl #101970] /[[:lower:]]/i matches upper case DEBPKG:fixes/reading-glob-copy-handle - [fd1564b] http://bugs.debian.org/629363 [perl #92258] <$fh> hangs on a glob copy DEBPKG:fixes/smartmatch-rhs-precedence - http://bugs.debian.org/691102 [011be0b] Enforce Any ~~ Object smartmatch precedence DEBPKG:fixes/perlcheat-update - http://bugs.debian.org/691112 [ab0ae0a] Update PerlCheat to 5.14 DEBPKG:fixes/cgi-cr-escaping - http://bugs.debian.org/693420 CR escaping for P3P and Set-Cookie headers DEBPKG:fixes/maketext-code-execution - [1735f6f] http://bugs.debian.org/695224 Fix misparsing of maketext strings. DEBPKG:fixes/storable-security-warning - [664f237] http://bugs.debian.org/695223 add a note about security concerns in Storable DEBPKG:fixes/digest-sha-doublefree - [rt.cpan.org #82655] http://bugs.debian.org/698172 [a8c6ff7] Fix a double-free bug in Digest::SHA DEBPKG:fixes/64bitint-signedness-wraparound - http://bugs.debian.org/698320 [94e529c] Avoid wraparound when casting unsigned size_t to signed ssize_t. DEBPKG:fixes/stdin-sigchld - http://bugs.debian.org/700171 [perl #116621] [be48bbe] add a couple missing LEAVEs in perlio_async_run() DEBPKG:fixes/hsplit-rehash - [d59e31f] http://bugs.debian.org/702296 Prevent premature hsplit() calls, and only trigger REHASH after hsplit() DEBPKG:fixes/encode-memleak - http://bugs.debian.org/702416 [5814803] Encode: Fixed a memory leak that occurred in the UTF-8 encoding. DEBPKG:fixes/threads_shared_elements_crash - [perl #119089] http://bugs.debian.org/718438 threads::shared should not crash if shared elements outlive their aggregate. DEBPKG:fixes/perlbug-patchlist - [3541c11] http://bugs.debian.org/710842 [perl #118433] Make perlbug look up the list of local patches at run time DEBPKG:fixes/digest_sha_double_free - [ee8c6f4] [rt.cpan.org #86295] http://bugs.debian.org/711206 maint-5.18: Digest-SHA crash fix in 5.85 DEBPKG:fixes/pl_eval_start_use_after_free - [eae139f] [perl #115992] PL_eval_start use-after-free DEBPKG:fixes/regcomp_fix_segv - [ebb390a] [perl #115994] fix segv in regcomp.c:S_join_exact() DEBPKG:fixes/list_util_off_by_two - [623a911] fix off-by-two error in List::Util DEBPKG:fixes/sdbm_off_by_one - [7f5f08b] [perl #111586] sdbm.c: fix off-by-one access to global ".dir" DEBPKG:fixes/socket_unpack_sockaddr_un_heap_buffer_overflow - [e508642] [perl #111594] Socket::unpack_sockaddr_un heap-buffer-overflow Built under linux Compiled at Sep 30 2013 03:45:34 @INC: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl . ———————————— Timofeev Dmitry VoIP Engineer Linux, Asterisk, Cisco solutions Skype: itsroot icq: 227227933

2 1

Increasing MAX_RECV_BUFFER_SIZE
by Wingsravi R 09 Feb '14

09 Feb '14

Dear Kamailio'ns I am working on Kamailio (V 4.0)+ Mediaproxy server (2.5.2) running on Ubuntu 12.04. I am experiencing some Latency, jitter, pixelled, choppy video errors in my set-up. So i wanted to increase buffer sizes of my kamailio server , Mediaproxy server and Ubuntu also. In that regards i have increased Shared memory value to 512 MB and Package memory value 16 MB. BUFFER SIZE value to 8 MB in *config.h* file, But where can i change the value for 'MAX_RECV_BUFFER_SIZE' of kamailio? And are there any settings to increase Buffer Size of Mediaproxy server ? Is this changes will affect on my issues ? PS: I even changed ubuntu settings also : net.core.rmem_max= 8388608 net.core.wmem_max= 8388608 (but these values reset to default values again when i restarted system.) Please help me in resolving this issues. Any help will appreciate. Regards, Ravi

4 4

kamailo uses wrong ip address
by jaflong jaflong 07 Feb '14

07 Feb '14

I have this in my config $ru = "sip:"+$rU+"10.31.2.101:5090;transport=tls"; if (!t_relay_to_tls()) { sl_reply_error(); return; } My ip address dest is 10.31.2.101. Why has 130.31.2.101 been used? 13(10882) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 130.31.2.101 4(10883) ERROR: <core> [tcp_main.c:4422]: tcpconn_main_timeout(): connect 130.31.2.101:5090 failed (timeout)

2 1

My Kamailio + Asterisk != NOT realtime integration: TRANSFERERNAME and BLINDTRANSFER
by Alexandr Usov 07 Feb '14

07 Feb '14

Integration - works. Problem - dialing peer to peer via Kamailio OK but with missing VARs and extension number, on dialing/transferring. Maybe you know other way to configure Asterisk dialplan for users, registered on kamailio and alowing dial as SIP/UserNumber insted SIP/ UserNumber(a)kamailio.host.name What we have. My Kamailio config: *http://pastebin.com/p7YxsFaw <http://pastebin.com/p7YxsFaw>* Asterisk's user (peer) - registered on kamailio: [3] host=192.168.144.212 qualify=yes dtmfmode=rfc2833 canreinvite=no context=local-routing host=dynamic type=friend directmedia=no nat=no qualify=yes disallow=all allow=ulaw allow=alaw allow=g729 call-limit=2 limitonpeers=yes callcounter=yes callerid=Usov Mob <3> ### Asterisk queue members: ;syntax: member => interface,[,penalty][,membername][,state_interface][,ringinuse] member=SIP/1(a)sip.cloudpbx.com.ua,1,1001,SIP/1,no member=SIP/3(a)sip.cloudpbx.com.ua,1,1003,SIP/1,no ### Asterisk dialing local peer: ... exten => _X,n,Dial(SIP/${EXTEN}(a)sip.cloudpbx.com.ua,12,tT) ... ### Asterisk attended transfer from 1 to 9 exten: *http://pastebin.com/k9H4vMgx <http://pastebin.com/k9H4vMgx>* Problem #1: Peer 9 receive clid as asterisk(a)sip.cloudpbx.com.ua Need #1: 1(a)sip.cloudpbx.com.ua. Problem #2: TRANSFERERNAME=SIP/sip.cloudpbx.com.ua-000000b5 Need #2: TRANSFERERNAME=SIP/1(a)sip.cloudpbx.com.ua-000000b5 ### Asterisk blind transfer dump log: *http://pastebin.com/NXqXingR <http://pastebin.com/NXqXingR>* Problem #3: BLINDTRANSFER=SIP/sip.cloudpbx.com.ua-000000ba Need #3: BLINDTRANSFER=SIP/9(a)sip.cloudpbx.com.ua-000000ba Main problem it is missed peer number - SIP/*peer_number*@ sip.cloudpbx.com.ua. And asterisk(a)sip.cloudpbx.com.ua instead 1(a)sip.cloudpbx.com.ua on attended transfer. Asterisk sip.conf domain settings: realm=sip.cloudpbx.com.ua fromdomain=sip.cloudpbx.com.ua ;domain=sip.cloudpbx.com.ua ;; temporary not uses becaouse not accepting GOIP sim ports registration on asterisk with IP-address of sip proxy instead domain sip.cloudpbx.com.ua; and it's not helps to change asterisk(a)sip.cloudpbx.com.ua clid Any help from all - wellcome! P.S. domain sip.cloudpbx.com.ua not exist

1 1

CONFIRMED_NA dialog state timeout
by Alex Balashov 07 Feb '14

07 Feb '14

Hi, We frequently run into the situation where a call is simultaneously CANCEL'd by the caller and answered (2xx) by the callee. This results in the caller not sending an e2e ACK, since it CANCEL'd the branch. It results in retransmission of the 200 OK, since the proxy can't CANCEL the branch anymore. It leaves the dialog in state 3 #define DLG_STATE_CONFIRMED_NA 3 /*!< confirmed dialog without a ACK yet */ (dlg_hash.h) for up to 'dialog_timeout' time. Is there a straightforward hack for this situation? Does changing the dialog timeout AVP have any effect after the relay of the initial INVITE (and thus invocation of the registered dialog init TM callback)? More generally, I was wondering if there has been any thought given to the idea of separate timeout modparams for confirmed-nonACKed state, as well as early state perhaps. Thanks, -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/

1 0

ssl error
by jaflong jaflong 06 Feb '14

06 Feb '14

This is my tls.cfg for server [server:default] method = TLSv1 verify_certificate = no require_certificate = no private_key = /etc/asterisk/certs/proxy.key certificate = /etc/asterisk/certs/proxy.crt As far as I understand (verify_certificate = no), and (require_certificate = no) should allow a client connecting without certicates. Can anyone understand what this debug indicates What is causes this error tls_read_f(): TLS read:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca 7(14841) DEBUG: tls [tls_server.c:178]: tls_complete_init(): Using TLS domain TLSs<default> 7(14841) DEBUG: tls [tls_domain.c:609]: sr_ssl_ctx_info_callback(): SSL handshake started 7(14841) DEBUG: <core> [tcp_main.c:2556]: tcpconn_do_send(): tcp_send: sending... 7(14841) DEBUG: <core> [tcp_main.c:2590]: tcpconn_do_send(): tcp_send: after real write: c= 0x7eff24e41260 n=940 fd=5 7(14841) DEBUG: <core> [tcp_main.c:2591]: tcpconn_do_send(): tcp_send: buf= 7(14841) DEBUG: <core> [io_wait.h:390]: io_watch_add(): DBG: io_watch_add(0x8df1e0, 5, 2, 0x7eff24e41260), fd_no=1 7(14841) DEBUG: tls [tls_domain.c:621]: sr_ssl_ctx_info_callback(): SSL handshake done 7(14841) DEBUG: tls [tls_domain.c:624]: sr_ssl_ctx_info_callback(): SSL disable renegotiation 7(14841) DEBUG: tls [tls_server.c:348]: tls_accept(): TLS accept successful 7(14841) DEBUG: tls [tls_server.c:355]: tls_accept(): tls_accept: new connection from 10.1.2.3:35573 using TLSv1/SSLv3 AES256-SHA 256 7(14841) DEBUG: tls [tls_server.c:358]: tls_accept(): tls_accept: local socket: 10.1.2.4:6443 7(14841) DEBUG: tls [tls_server.c:369]: tls_accept(): tls_accept: client did not present a certificate 7(14841) DEBUG: <core> [tcp_main.c:2556]: tcpconn_do_send(): tcp_send: sending... 7(14841) DEBUG: <core> [tcp_main.c:2590]: tcpconn_do_send(): tcp_send: after real write: c= 0x7eff24e41260 n=250 fd=5 7(14841) DEBUG: <core> [tcp_main.c:2591]: tcpconn_do_send(): tcp_send: buf= 7(14841) DEBUG: <core> [tcp_read.c:296]: tcp_read_data(): EOF on 0x7eff24e41260, FD 5 7(14841) ERROR: tls [tls_server.c:1186]: tls_read_f(): TLS read:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca 7(14841) ERROR: <core> [tcp_read.c:1281]: tcp_read_req(): ERROR: tcp_read_req: error reading 7(14841) DEBUG: <core> [io_wait.h:617]: io_watch_del(): DBG: io_watch_del (0x8df1e0, 5, -1, 0x10) fd_no=2 called 7(14841) DEBUG: <core> [tcp_read.c:1437]: release_tcpconn(): releasing con 0x7eff24e41260, state -2, fd=5, id=2 7(14841) DEBUG: <core> [tcp_read.c:1438]: release_tcpconn(): extra_data 0x7eff24e3c200 10(14844) DEBUG: <core> [tcp_main.c:3385]: handle_tcp_child(): handle_tcp_child: reader response= 7eff24e41260, -2 from 1 10(14844) DEBUG: tls [tls_server.c:597]: tls_h_close(): Closing SSL connection 0x7eff24e3c200

2 1

Dialog
by John Murray 06 Feb '14

06 Feb '14

Hi, I need to get call-id and from-tag from a call in ringing state (2). If I use dlg_manage() and put the call into a profile using set_dlg_profile("usr","1"). Then do a avp_db_query() I don't see the call until it is connected. I am using db_mode 1. Yet if I do a sercmd dlg.dlg_list I see the call in ringing state and when it is connected. How do I get the call-id when it is in ringing state? Regards John

1 0

Change of source ip address
by Diego Alejandro Ozuna Escalada 06 Feb '14

06 Feb '14

Dear list, I'm having a problem. I have an SBC server with two network interfaces, one external IP (X.X.248.194) and other internal IP (X.X.248.21). Messages are sent to the proxy sip server through internal ip with this configuration: route [sip-serverr] { rewritehostport ("ip_sip_proxy: 5060"); force_send_socket (X.X.248.21: 5060); t_relay (); exit; } When a UA sends an INVITE to the SBC, the responses (back) to UA are being sent with the correct external source IP (X.X.248.194) but if there are retransmissions of these responses, after 6 seconds, the source IP changes to the internal ip (X.X.248.21) Does anyone from the list know how I can solve this? Thanks, Regards, -- Diego

2 2

FS#380 - fixes for memory leak in TLS module
by Ding Ma 06 Feb '14

06 Feb '14

Daniel, Klaus, Sorry to reply late to your comments, was busy doing some other things until now. Just provided some comments in https://sip-router.org/tracker/index.php?do=details&task_id=380 Please take a look and let me know if you agree with my assessment. Thanks, Ding

1 0

bug in authdb_mod ??
by jay binks 06 Feb '14

06 Feb '14

So when Im trying to use is_subscriber & load_credentials together, It seems I have either hit a bug or just a bad config ( but I dont think its the latter ) My symptom is that only the field on the far right of "load_credentials" ever returns the correct value, the other fields are always null. My config has this setting : modparam("auth_db", "load_credentials", "field1;field2") and I can see the following debug when running kamailio -ddddd 0(14174) DEBUG: auth_db [authdb_mod.c:291]: w_is_subscriber(): uri [sip: 1112(a)192.168.173.5] table [subscriber] flags [1] 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:807]: db_cassa_query(): query table=subscriber 0(14174) DEBUG: db_cassandra [dbcassa_table.c:461]: dbcassa_db_get_table(): found dbname=kamailio, table=subscriber 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:351]: cassa_constr_key(): query col = username 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:351]: cassa_constr_key(): query col = domain 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:376]: cassa_constr_key(): key = 1112 192.168.173.5 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:499]: cassa_translate_query(): Query col: field2 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:499]: cassa_translate_query(): Query col: field1; field2 0(14174) DEBUG: db_cassandra [dbcassa_base.cpp:501]: cassa_translate_query(): get 2 columns 0(14174) DEBUG: <core> [db_res.c:118]: db_new_result(): allocate 56 bytes for result set at 0x7fc6ce770e78 if I had to put money on where the bug is, I would look in parse_aaa_pvs in authdb_mod.c however, an initial glance revealed nothing glaring, also this file was last changed in *2013-01-20 ( and that was only a move from modules_k )* SURELY I cant be the only person wanting to use this for more than one field ? This code looks like its almost the same as when first committed in August 2011 .... Id love someone to see if they can confirm this and point me in the right direction ( if this is my fault ) or lets get this fixed, if its a bug :) -- Sincerely Jay

2 5

Handling RFC3578 (Overlap Dialing) in Kamailio/ Asynchronious transaction handling
by Moritz Graf 06 Feb '14

06 Feb '14

Hoho, i want to implement RFC3578 (transaction oriented) in Kamailio. Therefore I have to correlate two different Invites with same Call-ID. I see various ways of accomplishing this, but I am stuck at all of my solutions. Find the algorithm I want to implement attached. Shortly explained what RFC3578 is: In a open numbering plan you never know if the INVITE you received is already complete, or if there are more numbers coming in. One way of accomplishing this is to set up a timer. If the timer elapses you assume the number is complete. If not, you are receiving a new INVITE with one digit more. Now you have to close the old transaction with a "484 - Address Incomplete"-response and start the timer again. (Find the algorithm I want to implement attached) The following lines, I'm going to explain my thoughts. For reference I'm calling "Thread A" the first INVITE coming in and "Thread B" the second. ####################### ### using Module ASYNC * Thread A -> async_route("handle_overlap","<timer t99 value>"); * Thread B -> if new incoming transaction, ** set avp("<call-id>")= <digitlength of called number> and ** call async_route("handle_overlap","<timer t99 value>"); * in route[handle_overlap] ** if avp("call-id") greater than "<digitlength of called number>" *** cancel transaction with "484 -Address Incomplete" ** if avp("call-id") equals "<digitlength of called number>" *** handle call => the number is complete PROBLEM: The old transaction is not canceled immediately, but after t99 elapsed... ####################### ### using Module TMX using t_suspend() and t_continue(), but here i see the following problems: * Thread A calls "t_suspend()" ** How is it possible to cancel "Thread A"'s transaction from Thread B? ** If there is no Thread B, so the numbers were complete, how can I get Thread A to continue processing?? * General TMX-Question: Are there any examples available? ####################### ### using simple sleep() and shv()/avp() Sounds like dirty hacking... I'd appriciate a solution with one of aboves modules. But if there is a solution available, I'd try this. Thx in advise Moritz -- Moritz Graf, B.Sc. Betrieb NGN-Plattform G-FIT GmbH & Co. KG Greflingerstr. 26, 93055 Regensburg Telefon +49 (9 41) 69 85 - 1 86 Telefax +49 (9 41) 69 85 - 2 86 mailto:moritz.graf@g-fit.de http://www.g-fit.de G-FIT Gesellschaft für innovative Telekommunikationsdienste mbH & Co. KG, Kommanditgesellschaft, Sitz Regensburg, Registergericht Regensburg, HRA 7626; Geschäftsführer: Dipl.Inf. (FH) Alfred Rauscher

4 11

Kamailio + CDR-stats
by davy 06 Feb '14

06 Feb '14

Hi, I’ve recently tried out CDR-stats, and after a bumpy ride to get it going ;) , I’m happily surprised with it. Especially the fraud detection mechanisms (which could use some extra’s), and the eye-candy makes it attractive. It is based on a mongodb which has to be filled with CDRs. As there is no mongodb module in Kamailio, I was thinking of using the jsonrpc module to push cdrs from Kamailio to some Python thing which pushes it into MongoDB. Perhaps by using the async module. Netstrings seems a rather low overhead protocol, and the jsonrpc module allows to push over a cluster of servers, which makes it scalable. Would this be a good way to do this, or am I bluntly missing the better way? Thx, Davy

3 2

dialog module - dialogs not deleted on BYE
by jay binks 06 Feb '14

06 Feb '14

Im fairly use to the dialog module, and I can not seem to get the dialogs to be removed from the dialogs table on hangup ( BYE ). What am I missing here.. this seems very basic and is essential to using dialog module for for channel limiting. any help would be great. maybe there is an example config for this somewhere ? -- Sincerely Jay

2 3

MI commands ?
by arun Jayaprakash 06 Feb '14

06 Feb '14

Hello, what do I need to do to be able to run MI commands on Kamailio 4.0? When I run MI commands from Siremis no results come back. Thank you. Arun

2 4

kamailio as sip router and rtp proxy without reg on kamailio
by *sm1Ly 05 Feb '14

05 Feb '14

hello all again. trying the third day... my cfg is: http://pastebin.com/vMHd7kki I need scheme like: any_sip_device_on_internet_nated_and_not => kamailio ext ip (194.190.8.171) | kamailio int ip (50.0.0.1) => asterisk (50.0.0.10) a do not need realtime configuration of asterisk. I only need forward everything to asterisk. and after signalling will work, I need rtp too... but its the long way I think. so how I must config kamailio that it doesnt answer 200 when I send register? it looks like sip device send register, kamailio fwd it, but answer to device 200. and than my device doesnt resend register normal. some dump: 20:40:44.649660 IP (tos 0x0, ttl 121, id 14950, offset 0, flags [none], proto UDP (17), length 583) 77.37.241.151.5060 > 194.190.8.171.5060: SIP, length: 555 REGISTER sip:194.190.8.171 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.119:5060 ;branch=z9hG4bK009318ba288ce311b95a985a85ad1a82;rport From: <sip:1001@194.190.8.171>;tag=3041452802 To: <sip:1001@194.190.8.171> Call-ID: 00C48A3A-288C-E311-B956-985A85AD1A82(a)192.168.1.119 CSeq: 4 REGISTER Contact: <sip:1001@192.168.1.119:5060 >;Expires=0;+sip.instance="<urn:uuid:8012D316-1188-E311-99FF-536675A7CDE6>" Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE Max-Forwards: 70 User-Agent: SIPPER for PhonerLite Expires: 0 Content-Length: 0 20:40:44.651668 IP (tos 0x10, ttl 64, id 33739, offset 0, flags [none], proto UDP (17), length 422) 194.190.8.171.5060 > 77.37.241.151.5060: SIP, length: 394 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.119:5060 ;branch=z9hG4bK009318ba288ce311b95a985a85ad1a82;rport=5060;received=77.37.241.151 From: <sip:1001@194.190.8.171>;tag=3041452802 To: <sip:1001@194.190.8.171 >;tag=c5aea4efd01978ba46557f38f3d08cfc.63a1 Call-ID: 00C48A3A-288C-E311-B956-985A85AD1A82(a)192.168.1.119 CSeq: 4 REGISTER Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 20:40:44.653916 IP (tos 0x10, ttl 64, id 33740, offset 0, flags [none], proto UDP (17), length 582) 194.190.8.171.5060 > 77.37.241.151.5060: SIP, length: 554 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.119:5060 ;received=77.37.241.151;branch=z9hG4bK009318ba288ce311b95a985a85ad1a82;rport=5060 From: <sip:1001@194.190.8.171>;tag=3041452802 To: <sip:1001@194.190.8.171>;tag=as40c64a63 Call-ID: 00C48A3A-288C-E311-B956-985A85AD1A82(a)192.168.1.119 CSeq: 4 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="4cffbc95" Content-Length: 0 20:40:45.073854 IP (tos 0x0, ttl 121, id 14953, offset 0, flags [none], proto UDP (17), length 575) 77.37.241.151.5060 > 194.190.8.171.5060: SIP, length: 547 REGISTER sip:194.190.8.171 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.119:5060 ;branch=z9hG4bK009318ba288ce311b1713a64da149374;rport From: <sip:1001@194.190.8.171>;tag=3123771917 To: <sip:1001@194.190.8.171> Call-ID: 009318BA-288C-E311-B16F-3A64DA149374(a)192.168.1.119 CSeq: 1 REGISTER Contact: <sip:1001@192.168.1.119:5060 >;+sip.instance="<urn:uuid:8012D316-1188-E311-99FF-536675A7CDE6>" Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE Max-Forwards: 70 User-Agent: SIPPER for PhonerLite Expires: 900 Content-Length: 0 20:40:45.076169 IP (tos 0x10, ttl 64, id 33741, offset 0, flags [none], proto UDP (17), length 572) 194.190.8.171.5060 > 77.37.241.151.5060: SIP, length: 544 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.119:5060 ;branch=z9hG4bK009318ba288ce311b1713a64da149374;rport=5060;received=77.37.241.151 From: <sip:1001@194.190.8.171>;tag=3123771917 To: <sip:1001@194.190.8.171 >;tag=c5aea4efd01978ba46557f38f3d08cfc.795d Call-ID: 009318BA-288C-E311-B16F-3A64DA149374(a)192.168.1.119 CSeq: 1 REGISTER Contact: <sip:1001@192.168.1.119:5060>;expires=900;received="sip: 77.37.241.151:5060 ";+sip.instance="<urn:uuid:8012D316-1188-E311-99FF-536675A7CDE6>" Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 -- yours respectfully, Alexander Vasin. 8 926 1437200 icq: 9906064

2 1

NAT helper frustrations with multiple kamailios
by Daniel Tryba 05 Feb '14

05 Feb '14

I'm experiencing some problems getting 2 Kamailios to work together. A clients - A kamailio - B kamailio - B clients | the outside world A and B client may or may not be NATed to their own kamailio instance. A and B kamailio (with forced rtpproxies) are in the same public network. A-kamailio and its clients are essentially a reseller of my services on the B side. The problem arises when A or B incorrectly flag a message as needing NAT help so either an unnecessary add_contact_alias is added (which seems to happen when putting somebody on hold on an A-client). A-kamailio inserts an alias on the Contact header containing the ip/port of B-kamailio. Trying to resume the call sends the contact with the alias to B-kamailio, which does a handle_ruri_alias and thus sets $du to itself, the party that was on hold will never receive these messages. The problem I have with add_contact_alias/handle_ruri_alias is that any kamailio in the path will parse these hints whether or not it is actually ment for that kamailio. I'd rather see a scheme that somehow identifies if the added alias was generated locally and thus needs to be handled or can just be ignored. Anybody else got these problems/frustrations and maybe a hint for an other way to tackle this problem? Off to figure out why uac_test incorrectly flags the onhold process as needing the nat helper... -- POCOS B.V. - Croy 9c - 5653 LC Eindhoven Telefoon: 040 293 8661 - Fax: 040 293 8658 http://www.pocos.nl/ - http://www.sipo.nl/ K.v.K. Eindhoven 17097024

3 3

Re: [SR-Users] Kamailio not mdifying Contact in multi-homed (*sm1Ly)
by *sm1Ly 05 Feb '14

05 Feb '14

I got really modify my config, and now it looks like: http://pastebin.com/0M7938Mm but now I got loopback problems. kamailio just asking itself. ngrep -d lo port 5060 talks me: U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;branch=z9hG4bKc2bb.e627f45ee16a4b45ca99321b3bc8832c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.328c8c23df8e916010525f7f786cbc49.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060 ;branch=z9hG4bKc2bb.b8ec8f173657be182ad714f59d37d4a8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.7bec0e7c4a5962e90811bf082f0e6635.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6bbb824e92f328ce4053167b2e2c596a.0..V ia: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6f732fece1d8956bf5b075118b3dcb2f.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf4e758c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2 bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 1 94.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a 7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rpor t=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060 ;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988 c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x 86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.328c8c23df8e916010525f7f786cbc49.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b8ec8f173657be182ad714f59d37d4a8.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.7bec0e7c4a5962e90811bf082f0e6635.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6bbb824e92f328ce4053167b2e2c596a.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6f732fece1d8956bf5b075118b 3dcb2f.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf4e758c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SI P/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01d cad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190 .8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001 @194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b8ec8f173657be182ad714f59d37d4a8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.7bec0e7c4a5962e90811bf082f0e6635.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.6bbb824e92f328ce4053167b2e2c596a.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6f732fece1d8956bf5b075118b3dcb2f.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf 4e758c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SI P/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946 cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168 .1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757D AE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.7bec0e7c4a5962e90811bf082f0e6635.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6bbb824e92f328ce4053167b2e2c596a.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.6f732fece1d8956bf5b075118b3dcb2f.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf4e758c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c 09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SI P/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0ea f0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060 ;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..Fro m: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length : 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6bbb824e92f328ce4053167b2e2c596a.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6f732fece1d8956bf5b075118b3dcb2f.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf4e758c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b 43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SI P/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d 28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171 >;tag=c5aea4efd01978ba4655 7f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.6f732fece1d8956bf5b075118b3dcb2f.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf4e758c.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0 c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SI P/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branc h=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: < sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE ..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b4ab8b8de819be6fff9203bfdf4e758c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e 520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SI P/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=12744772 58..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.977524b1111849dd2cd8020d4c09090c.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf7 3e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SI P/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558 B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.cb7d178bf3fdb6596399beaf5b43e66d.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c 7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060 ;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14df b;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: < sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux) )..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.bd5d0e524121d2fd121fa6e8f0c69cbf.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66 b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branc h=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171 >;tag=c5a ea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.98352f1121cb37b6feb7814a0e520e4e.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173 b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77 .37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB(a)192.168.1.119.. CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.b670b117fb4d3a40912cb25cf73e9e32.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc28 04cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8. 171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.ac9e718c5fd57a7f73adc7761c7ba31b.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d 2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171 >;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call -ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.01dcad6cb7e8257bcbe8ad7b66b7b095.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060 ;received=77.37.241.151;branch=z9hG4bK00c46d3a558be3 11988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1 .1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.946cc81be473148e1a6dc5a173b2cfb1.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171 ;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.1 90.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.0eaf0b545ac8239ad5e105fc2804cae8.0..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119 :5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <sip:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DF B@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0.... # U 194.190.8.171:5060 -> 194.190.8.171:5060 SIP/2.0 483 Too Many Hops..Via: SIP/2.0/UDP 194.190.8.171;rport=5060;branch=z9hG4bKc2bb.c1d28c8a5ba1eeda8f8b296f6d2232e8.0..Via: SIP/2.0/UDP 192.168.1.119:5060;received=77.37.241.151;branch=z9hG4bK00c46d3a558be311988c4757dae14dfb;rport=5060..From: <si p:1001@194.190.8.171>;tag=1274477258..To: <sip:1001@194.190.8.171>;tag=c5aea4efd01978ba46557f38f3d08cfc.2793..Call-ID: 00C46D3A-558B-E311-988A-4757DAE14DFB@192.168.1.119..CSeq: 2 SUBSCRIBE..Server: kamailio (4.1.1 (x86_64/linux))..Content-Length: 0... . and how looks dump 1. from sip device to kamailio [root@kamaz sm1ly]# tcpdump -nn -i eth0 host 77.37.241.151 -v tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 19:54:51.205942 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 421) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 393 REGISTER sip:194.190.8.171 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5569 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bKe5bd1a6ceba7f0a0f4e7487cb17ca365353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Content-Length: 0 19:54:51.210060 IP (tos 0x10, ttl 64, id 35861, offset 0, flags [none], proto UDP (17), length 603) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 575 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKe5bd1a6ceba7f0a0f4e7487cb17ca365353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as518dbea9 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5569 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="31daf0f8" Content-Length: 0 19:54:51.257552 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 586) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 558 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5570 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bK440337c23337c9913220fd825f4d9ded353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Authorization: Digest username="1002",realm="asterisk",nonce="31daf0f8",uri="sip: 194.190.8.171:5060 ",response="2b0222b07da7af1c3b72c2eb36241f5f",algorithm=MD5 Content-Length: 0 19:54:51.261209 IP (tos 0x10, ttl 64, id 35862, offset 0, flags [none], proto UDP (17), length 603) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 575 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK440337c23337c9913220fd825f4d9ded353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as0716dea5 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5570 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2f70c759" Content-Length: 0 19:54:51.290458 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 586) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 558 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5571 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bK30fe030eee49e2eb50c619074c0f057b353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Authorization: Digest username="1002",realm="asterisk",nonce="2f70c759",uri="sip: 194.190.8.171:5060 ",response="9eb7d157cfd0d8e8575b59c94c5f82f6",algorithm=MD5 Content-Length: 0 19:54:51.295285 IP (tos 0x10, ttl 64, id 35863, offset 0, flags [none], proto UDP (17), length 566) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 538 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK30fe030eee49e2eb50c619074c0f057b353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as0716dea5 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5571 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Expires: 0 Date: Mon, 03 Feb 2014 15:54:51 GMT Content-Length: 0 19:54:51.314824 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 473) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 445 REGISTER sip:194.190.8.171 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2404 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bKdeb946998664720c2c93538625cc649e353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Content-Length: 0 19:54:51.319697 IP (tos 0x10, ttl 64, id 35864, offset 0, flags [none], proto UDP (17), length 602) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 574 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKdeb946998664720c2c93538625cc649e353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as0bba2324 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2404 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="023deb34" Content-Length: 0 19:54:51.344080 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 638) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 610 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2405 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bK60a6798f72024444a9870698b766a04c353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Authorization: Digest username="1002",realm="asterisk",nonce="023deb34",uri="sip: 194.190.8.171:5060 ",response="7fa5be98c7c0c395ed41f9e7da095629",algorithm=MD5 Content-Length: 0 19:54:51.350423 IP (tos 0x10, ttl 64, id 35865, offset 0, flags [none], proto UDP (17), length 602) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 574 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK60a6798f72024444a9870698b766a04c353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as065abeba Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2405 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="26886c3d" Content-Length: 0 19:54:51.370976 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 638) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 610 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2406 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bKf4d831e0612e1074bf49397d92907c80353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Authorization: Digest username="1002",realm="asterisk",nonce="26886c3d",uri="sip: 194.190.8.171:5060 ",response="cc17aae74d45f06e4712aa66b08e68df",algorithm=MD5 Content-Length: 0 19:54:51.380962 IP (tos 0x10, ttl 64, id 35866, offset 0, flags [none], proto UDP (17), length 636) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 608 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKf4d831e0612e1074bf49397d92907c80353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as065abeba Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2406 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Expires: 3600 Contact: <sip:1002@192.168.1.103:57288;transport=udp>;expires=3600 Date: Mon, 03 Feb 2014 15:54:51 GMT Content-Length: 0 19:54:51.406160 IP (tos 0x0, ttl 57, id 0, offset 0, flags [DF], proto UDP (17), length 395) 77.37.241.151.57288 > 194.190.8.171.5060: SIP, length: 367 OPTIONS sip:194.190.8.171 SIP/2.0 Call-ID: 28b382a24bc3e426f030593cec5f852a(a)192.168.1.103 CSeq: 1287 OPTIONS From: "1002" <sip:1002@194.190.8.171>;tag=3866552602 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bK9bddae72a5ccaf0df80be00ba2882dfd353236;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Content-Length: 0 19:54:51.407799 IP (tos 0x10, ttl 64, id 35867, offset 0, flags [none], proto UDP (17), length 458) 194.190.8.171.5060 > 77.37.241.151.57288: SIP, length: 430 SIP/2.0 484 Address Incomplete Call-ID: 28b382a24bc3e426f030593cec5f852a(a)192.168.1.103 CSeq: 1287 OPTIONS From: "1002" <sip:1002@194.190.8.171>;tag=3866552602 To: "1002" <sip:1002@194.190.8.171 >;tag=c5aea4efd01978ba46557f38f3d08cfc.5162 Via: SIP/2.0/UDP 192.168.1.103:57288 ;branch=z9hG4bK9bddae72a5ccaf0df80be00ba2882dfd353236;rport=57288;received=77.37.241.151 Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 2. from kamailio to asterisk. [root@kamaz sm1ly]# tcpdump -nn -i eth1 host 50.0.0.10 -v and port 5060 tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 19:54:41.906391 IP (tos 0x0, ttl 64, id 5618, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:34713;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:42.906385 IP (tos 0x0, ttl 64, id 5619, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:34713;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:43.906565 IP (tos 0x0, ttl 64, id 5620, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:34713;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:44.904726 IP (tos 0x10, ttl 64, id 34743, offset 0, flags [none], proto UDP (17), length 413) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 385 SIP/2.0 408 Request Timeout Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport=5060 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713 ;transport=udp>;tag=6f6209fafb0c4bc816e1e7aa854ee2dd-8578 Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 19:54:51.207422 IP (tos 0x10, ttl 64, id 34744, offset 0, flags [none], proto UDP (17), length 531) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 503 REGISTER sip:194.190.8.171 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5569 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bKd8a1.094de0504827adb22c7b874f77dfd698.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKe5bd1a6ceba7f0a0f4e7487cb17ca365353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Content-Length: 0 19:54:51.209052 IP (tos 0x0, ttl 64, id 5621, offset 0, flags [none], proto UDP (17), length 713) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 685 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bKd8a1.094de0504827adb22c7b874f77dfd698.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKe5bd1a6ceba7f0a0f4e7487cb17ca365353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as518dbea9 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5569 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="31daf0f8" Content-Length: 0 19:54:51.258759 IP (tos 0x10, ttl 64, id 34745, offset 0, flags [none], proto UDP (17), length 696) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 668 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5570 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK56b1.d46d0ab6448c5edd99f24aa7ba8a2881.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK440337c23337c9913220fd825f4d9ded353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Authorization: Digest username="1002",realm="asterisk",nonce="31daf0f8",uri="sip: 194.190.8.171:5060 ",response="2b0222b07da7af1c3b72c2eb36241f5f",algorithm=MD5 Content-Length: 0 19:54:51.259902 IP (tos 0x0, ttl 64, id 5622, offset 0, flags [none], proto UDP (17), length 713) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 685 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK56b1.d46d0ab6448c5edd99f24aa7ba8a2881.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK440337c23337c9913220fd825f4d9ded353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as0716dea5 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5570 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2f70c759" Content-Length: 0 19:54:51.292190 IP (tos 0x10, ttl 64, id 34746, offset 0, flags [none], proto UDP (17), length 696) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 668 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5571 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK66b1.0173e2524e6deda0f27b83591a62730f.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK30fe030eee49e2eb50c619074c0f057b353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Authorization: Digest username="1002",realm="asterisk",nonce="2f70c759",uri="sip: 194.190.8.171:5060 ",response="9eb7d157cfd0d8e8575b59c94c5f82f6",algorithm=MD5 Content-Length: 0 19:54:51.293302 IP (tos 0x0, ttl 64, id 5623, offset 0, flags [none], proto UDP (17), length 676) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 648 SIP/2.0 200 OK Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK66b1.0173e2524e6deda0f27b83591a62730f.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK30fe030eee49e2eb50c619074c0f057b353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as0716dea5 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5571 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Expires: 0 Date: Mon, 03 Feb 2014 15:54:51 GMT Content-Length: 0 19:54:51.317242 IP (tos 0x10, ttl 64, id 34747, offset 0, flags [none], proto UDP (17), length 583) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 555 REGISTER sip:194.190.8.171 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2404 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK2624.44980ae0ad3ba5026d6f044c24770539.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKdeb946998664720c2c93538625cc649e353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Content-Length: 0 19:54:51.318123 IP (tos 0x0, ttl 64, id 5624, offset 0, flags [none], proto UDP (17), length 712) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 684 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK2624.44980ae0ad3ba5026d6f044c24770539.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKdeb946998664720c2c93538625cc649e353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as0bba2324 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2404 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="023deb34" Content-Length: 0 19:54:51.346522 IP (tos 0x10, ttl 64, id 34748, offset 0, flags [none], proto UDP (17), length 748) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 720 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2405 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK3624.173cef757dc8f7da8b864ee1ab1bfe50.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK60a6798f72024444a9870698b766a04c353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Authorization: Digest username="1002",realm="asterisk",nonce="023deb34",uri="sip: 194.190.8.171:5060 ",response="7fa5be98c7c0c395ed41f9e7da095629",algorithm=MD5 Content-Length: 0 19:54:51.348056 IP (tos 0x0, ttl 64, id 5625, offset 0, flags [none], proto UDP (17), length 712) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 684 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK3624.173cef757dc8f7da8b864ee1ab1bfe50.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK60a6798f72024444a9870698b766a04c353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as065abeba Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2405 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="26886c3d" Content-Length: 0 19:54:51.373298 IP (tos 0x10, ttl 64, id 34749, offset 0, flags [none], proto UDP (17), length 748) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 720 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2406 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK0624.82ac15efd62f203c1b009e3ab3c711bc.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKf4d831e0612e1074bf49397d92907c80353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Authorization: Digest username="1002",realm="asterisk",nonce="26886c3d",uri="sip: 194.190.8.171:5060 ",response="cc17aae74d45f06e4712aa66b08e68df",algorithm=MD5 Content-Length: 0 19:54:51.374893 IP (tos 0x0, ttl 64, id 5626, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:57288;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:51 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:51.374906 IP (tos 0x0, ttl 64, id 5627, offset 0, flags [none], proto UDP (17), length 746) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 718 SIP/2.0 200 OK Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK0624.82ac15efd62f203c1b009e3ab3c711bc.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKf4d831e0612e1074bf49397d92907c80353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as065abeba Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2406 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Expires: 3600 Contact: <sip:1002@192.168.1.103:57288;transport=udp>;expires=3600 Date: Mon, 03 Feb 2014 15:54:51 GMT Content-Length: 0 19:54:52.375165 IP (tos 0x0, ttl 64, id 5628, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:57288;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:51 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:53.375333 IP (tos 0x0, ttl 64, id 5629, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:57288;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:51 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:54.342025 IP (tos 0x10, ttl 64, id 34750, offset 0, flags [none], proto UDP (17), length 413) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 385 SIP/2.0 408 Request Timeout Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport=5060 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288 ;transport=udp>;tag=6f6209fafb0c4bc816e1e7aa854ee2dd-1f6e Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 3. on asterisk to kamailio [root@astkamaz sm1ly]# tcpdump -nn -i eth0 -v host 50.0.0.1 and port 5060 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 19:54:41.906401 IP (tos 0x0, ttl 64, id 5618, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:34713;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:42.906581 IP (tos 0x0, ttl 64, id 5619, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:34713;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:43.906740 IP (tos 0x0, ttl 64, id 5620, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:34713;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:44.905366 IP (tos 0x10, ttl 64, id 34743, offset 0, flags [none], proto UDP (17), length 413) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 385 SIP/2.0 408 Request Timeout Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK75f42160;rport=5060 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40fc69ea To: <sip:1002@192.168.1.103:34713 ;transport=udp>;tag=6f6209fafb0c4bc816e1e7aa854ee2dd-8578 Call-ID: 7bacfa62676409266240568c5c9d055b@50.0.0.10:5060 CSeq: 102 OPTIONS Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 19:54:51.208464 IP (tos 0x10, ttl 64, id 34744, offset 0, flags [none], proto UDP (17), length 531) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 503 REGISTER sip:194.190.8.171 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5569 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bKd8a1.094de0504827adb22c7b874f77dfd698.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKe5bd1a6ceba7f0a0f4e7487cb17ca365353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Content-Length: 0 19:54:51.209176 IP (tos 0x0, ttl 64, id 5621, offset 0, flags [none], proto UDP (17), length 713) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 685 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bKd8a1.094de0504827adb22c7b874f77dfd698.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKe5bd1a6ceba7f0a0f4e7487cb17ca365353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as518dbea9 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5569 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="31daf0f8" Content-Length: 0 19:54:51.259436 IP (tos 0x10, ttl 64, id 34745, offset 0, flags [none], proto UDP (17), length 696) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 668 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5570 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK56b1.d46d0ab6448c5edd99f24aa7ba8a2881.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK440337c23337c9913220fd825f4d9ded353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Authorization: Digest username="1002",realm="asterisk",nonce="31daf0f8",uri="sip: 194.190.8.171:5060 ",response="2b0222b07da7af1c3b72c2eb36241f5f",algorithm=MD5 Content-Length: 0 19:54:51.260101 IP (tos 0x0, ttl 64, id 5622, offset 0, flags [none], proto UDP (17), length 713) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 685 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK56b1.d46d0ab6448c5edd99f24aa7ba8a2881.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK440337c23337c9913220fd825f4d9ded353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as0716dea5 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5570 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="2f70c759" Content-Length: 0 19:54:51.292708 IP (tos 0x10, ttl 64, id 34746, offset 0, flags [none], proto UDP (17), length 696) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 668 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5571 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK66b1.0173e2524e6deda0f27b83591a62730f.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK30fe030eee49e2eb50c619074c0f057b353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Authorization: Digest username="1002",realm="asterisk",nonce="2f70c759",uri="sip: 194.190.8.171:5060 ",response="9eb7d157cfd0d8e8575b59c94c5f82f6",algorithm=MD5 Content-Length: 0 19:54:51.293541 IP (tos 0x0, ttl 64, id 5623, offset 0, flags [none], proto UDP (17), length 676) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 648 SIP/2.0 200 OK Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK66b1.0173e2524e6deda0f27b83591a62730f.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK30fe030eee49e2eb50c619074c0f057b353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=2801080754 To: "1002" <sip:1002@194.190.8.171>;tag=as0716dea5 Call-ID: 676c32ab221a665a9bc9875ffb74930a(a)192.168.1.103 CSeq: 5571 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Expires: 0 Date: Mon, 03 Feb 2014 15:54:51 GMT Content-Length: 0 19:54:51.317704 IP (tos 0x10, ttl 64, id 34747, offset 0, flags [none], proto UDP (17), length 583) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 555 REGISTER sip:194.190.8.171 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2404 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK2624.44980ae0ad3ba5026d6f044c24770539.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKdeb946998664720c2c93538625cc649e353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Content-Length: 0 19:54:51.318355 IP (tos 0x0, ttl 64, id 5624, offset 0, flags [none], proto UDP (17), length 712) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 684 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK2624.44980ae0ad3ba5026d6f044c24770539.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKdeb946998664720c2c93538625cc649e353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as0bba2324 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2404 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="023deb34" Content-Length: 0 19:54:51.347429 IP (tos 0x10, ttl 64, id 34748, offset 0, flags [none], proto UDP (17), length 748) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 720 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2405 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK3624.173cef757dc8f7da8b864ee1ab1bfe50.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK60a6798f72024444a9870698b766a04c353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Authorization: Digest username="1002",realm="asterisk",nonce="023deb34",uri="sip: 194.190.8.171:5060 ",response="7fa5be98c7c0c395ed41f9e7da095629",algorithm=MD5 Content-Length: 0 19:54:51.348212 IP (tos 0x0, ttl 64, id 5625, offset 0, flags [none], proto UDP (17), length 712) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 684 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK3624.173cef757dc8f7da8b864ee1ab1bfe50.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bK60a6798f72024444a9870698b766a04c353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as065abeba Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2405 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="26886c3d" Content-Length: 0 19:54:51.373777 IP (tos 0x10, ttl 64, id 34749, offset 0, flags [none], proto UDP (17), length 748) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 720 REGISTER sip:194.190.8.171:5060 SIP/2.0 Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2406 REGISTER From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171> Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK0624.82ac15efd62f203c1b009e3ab3c711bc.0 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKf4d831e0612e1074bf49397d92907c80353236;rport=57288 Max-Forwards: 16 User-Agent: SIPAUA/0.1.001 Contact: "1002" <sip:1002@192.168.1.103:57288;transport=udp> Expires: 3600 Authorization: Digest username="1002",realm="asterisk",nonce="26886c3d",uri="sip: 194.190.8.171:5060 ",response="cc17aae74d45f06e4712aa66b08e68df",algorithm=MD5 Content-Length: 0 19:54:51.374731 IP (tos 0x0, ttl 64, id 5626, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:57288;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:51 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:51.374804 IP (tos 0x0, ttl 64, id 5627, offset 0, flags [none], proto UDP (17), length 746) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 718 SIP/2.0 200 OK Via: SIP/2.0/UDP 50.0.0.1;branch=z9hG4bK0624.82ac15efd62f203c1b009e3ab3c711bc.0;received=50.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.103:57288 ;received=77.37.241.151;branch=z9hG4bKf4d831e0612e1074bf49397d92907c80353236;rport=57288 From: "1002" <sip:1002@194.190.8.171>;tag=134783744 To: "1002" <sip:1002@194.190.8.171>;tag=as065abeba Call-ID: fffb7a09e489ce1cad6783709652b6f9(a)192.168.1.103 CSeq: 2406 REGISTER Server: Asterisk PBX 1.8.20.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Expires: 3600 Contact: <sip:1002@192.168.1.103:57288;transport=udp>;expires=3600 Date: Mon, 03 Feb 2014 15:54:51 GMT Content-Length: 0 19:54:52.375348 IP (tos 0x0, ttl 64, id 5628, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:57288;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:51 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:53.375562 IP (tos 0x0, ttl 64, id 5629, offset 0, flags [none], proto UDP (17), length 597) 50.0.0.10.5060 > 50.0.0.1.5060: SIP, length: 569 OPTIONS sip:1002@192.168.1.103:57288;transport=udp SIP/2.0 Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288;transport=udp> Contact: <sip:asterisk@50.0.0.10:5060> Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.8.20.0 Date: Mon, 03 Feb 2014 15:54:51 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Content-Length: 0 19:54:54.342525 IP (tos 0x10, ttl 64, id 34750, offset 0, flags [none], proto UDP (17), length 413) 50.0.0.1.5060 > 50.0.0.10.5060: SIP, length: 385 SIP/2.0 408 Request Timeout Via: SIP/2.0/UDP 50.0.0.10:5060;branch=z9hG4bK129c83a7;rport=5060 From: "asterisk" <sip:asterisk@50.0.0.10>;tag=as40306b56 To: <sip:1002@192.168.1.103:57288 ;transport=udp>;tag=6f6209fafb0c4bc816e1e7aa854ee2dd-1f6e Call-ID: 0e6d3cec7afd68275843c14303988ff3@50.0.0.10:5060 CSeq: 102 OPTIONS Server: kamailio (4.1.1 (x86_64/linux)) Content-Length: 0 ####### Defined Values ######### # - 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 ######### # Enable debugging only when kamailio is mading boo-boo ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR debug=3 log_stderror=no memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes 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="kamaz.ikatele.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:50.0.0.1:5060 advertise 194.190.8.171:5060 #listen=udp:194.190.8.171:5060 advertise 50.0.0.1:5060 listen=udp:194.190.8.171 listen=udp:50.0.0.1 dns=no rev_dns=no check_via=yes /* port to listen to * - can be specified more than once if needed to listen on many ports */ port=5060 mhomed=1 ####### Modules Section ######## # set paths to location of modules (to sources or installation folders) mpath="/usr/lib64/kamailio/modules/" 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 "cfg_rpc.so" loadmodule "mi_rpc.so" loadmodule "acc.so" loadmodule "nathelper.so" loadmodule "rtpproxy.so" #loadmodule "topoh.so" #modparam("topoh", "mask_key", "balalayka") #modparam("topoh", "mask_ip", "50.0.0.1") # ----------------- setting module-specific parameters --------------- # ----- 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", 3000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 12000) # ----- 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", 1) # ----- 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@194.190.8.171") # params needed for NAT traversal in other modules modparam("nathelper", "received_avp", "$avp(RECEIVED)") modparam("usrloc", "nat_bflag", FLB_NATB) ####### Routing Logic ######## # Main SIP request routing logic # - processing of any incoming SIP request starts with this route # - note: this is the same as route { ... } route { # per request initial checks route(REQINIT); # NAT detection xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) Main Route before ---NAT---\n"); route(NATDETECT); xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in Route[NATDETECT] fix_nat-register\n"); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) t_check_trans(); # 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); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } route(RELAY); } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("20")) { xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in MAX FDW HEADERS ALARMO\n"); sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Caller NAT detection route route[NATDETECT] { 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); } return; } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # 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 statelessy route(NATMANAGE); } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); } else { 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 { xlog("L_NOTICE","ACK without matching transaction ... ignore and discard\n"); # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not here"); } exit; } } # Routing to foreign domains route[SIPOUT] { if (!uri==myself) { append_hf("P-hint: outbound\r\n"); route(RELAY); } } # Handle SIP registrations route[REGISTRAR] { if (is_method("REGISTER")) { # if(isflagset(FLT_NATS)) # { # setbflag(FLB_NATB); # # uncomment next line to do SIP NAT pinging # xlog("L_NOTICE","--------------------- SIP NAT PINGING --------------------------------------\n"); # setbflag(FLB_NATSIPPING); # } # if (!save("location")) # sl_reply_error(); # xlog("L_NOTICE","--------------------- SL REPLY ERROR --------------------------------------\n"); if( t_check_trans() ) { xlog("L_NOTICE","Transaction already exist, forwarding\n"); } else { xlog("L_NOTICE","New transaction upcoming, creating\n"); # forward("50.0.0.10"); # save("sip:50.0.0.10","0x02"); t_relay_to_udp("50.0.0.10", "5060"); exit; } exit; } } route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. xlog("L_NOTICE","Default routing block raised!\n"); 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; } # RTPProxy control route[NATMANAGE] { if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { xlog("L_NOTICE","------------------------------------ SETBFLAG ----------------------------\n"); setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; rtpproxy_manage(); if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { xlog("L_NOTICE","------------------------------------ ADD RR PARAM NAT YES ----------------------------\n"); add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) xlog("L_NOTICE","------------------------------------ IS FIRST HOP SRT CONACT ALIAS ----------------------------\n"); set_contact_alias(); } xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in route[NATMANAGE] RTPproxy with EI Flags\n"); } return; } # URI update for dialog requests route[DLGURI] { if(!isdsturiset()) { handle_ruri_alias(); xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in route[DLGURI] RTPproxy with EI Flags\n"); } return; } # manage outgoing branches branch_route[MANAGE_BRANCH] { xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in MANAGE_BRANCH\n"); xdbg("new branch [$T_branch_idx] to $ru\n"); route(NATMANAGE); } # manage incoming replies onreply_route[MANAGE_REPLY] { xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in MANAGE_REPLY\n"); xdbg("incoming reply\n"); if(status=~"[12][0-9][0-9]") route(NATMANAGE); } # manage failure routing cases failure_route[MANAGE_FAILURE] { xlog("L_NOTICE","$rm from $fu (IP:$si:$sp) in MANAGE_FAILURE\n"); route(NATMANAGE); if (t_is_canceled()) { exit; } } route[DEBUG] { if (method==("PUBLISH|SUBSCRIBE|REGISTER|OPTIONS")) { return; } xlog("[$mi] Received SIP Message (method: $rm) ($ml bytes) to $Ri:$Rp from $si:$sp:\n$mb\n"); } > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 3 Feb 2014 15:14:19 +0400 > From: "*sm1Ly" <st.uzver(a)gmail.com> > To: dipak.biswas(a)mezocliq.com, sr-users(a)lists.sip-router.org > Subject: Re: [SR-Users] Kamailio not mdifying Contact in multi-homed > setup > Message-ID: > < > CABCivXiED_CDQiJtgQ-p_XQ1h8p3rbkE3fnxnS2iuUH+kdHZvA(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > hello, I got the same issue. my sip device getting ok from kamailio, but > asterisk reply 401. > but. > this is my config: http://pastebin.com/jGCak01E > > and I changed regfwd route to > $du = "sip:50.0.0.10:5060;transport=udp"; > forward(); > > and now I see this in logs: > > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status): > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:635]: parse_msg(): version: <SIP/2.0> > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:637]: parse_msg(): status: <200> > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:639]: parse_msg(): reason: <OK> > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, > <branch> = <0>; state=16 > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, > flags=2 > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the > first via > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [receive.c:152]: receive_msg(): After parse_msg... > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: tm > [t_lookup.c:1071]: t_check_msg(): DEBUG: t_check_msg: msg id=25 global > id=24 T start=(nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: > tag=006cfccc318be31188fc19977b3a5651 > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/parse_addr_spec.c:885]: parse_addr_spec(): end of header reached, > state=29 > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> > [63]; uri=[sip:77.37.241.151:5060] > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip: > 77.37.241.151:5060>] > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <1> > <OPTIONS> > *Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: tm > [t_lookup.c:1045]: t_reply_matching(): DEBUG: t_reply_matching: failure to > match a transaction* > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: tm > [t_lookup.c:1140]: t_check_msg(): DEBUG: t_check_msg: msg id=25 global > id=25 T end=(nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : > content_length=0 > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [parser/msg_parser.c:106]: get_hdr_field(): found end of header > *Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [forward.c:784]: do_forward_reply(): reply cannot be forwarded - no 2nd > via* > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying > list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying > list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying > list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying > list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying > list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying > list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) > Feb 3 15:13:38 kamaz /usr/sbin/kamailio[14502]: DEBUG: <core> > [receive.c:296]: receive_msg(): receive_msg: cleaning up > > > any ideas? > and show me ur conf please. > > > -- > > Hi All, > > I'm running into an issue, I'm not sure whether any of you seen this > yourselves and resolved it. Please share some pointers. My network is: > > clients <--> Public IP(Kamailio/RTPProxy)10.1.128.11 <--> 10.1.128.34 > (Freeswitch) > > The 200 OK response from Freeswitch (on the way back from called party to > caller) to Kamailio is shown below. Notice the Contact header URI host part > contains Freeswitch Private IP (10.1.128.34). Kamailio suppose to change > that to Public IP before forwarding the 200 OK (copied below) to Caller in > public domain. But, it's not. As a result, ACK from Caller is not reaching > back to Kamailio. > > How did you or anybody out there using Kamailio resolve this problem? If > needed, I can copy/paste my kamailio.cfg. > > -- > yours respectfully, Alexander Vasin. > > 8 926 1437200 > icq: 9906064 >

2 1

Re: [SR-Users] reg event support in subscribe
by Andrew Pogrebennyk 05 Feb '14

05 Feb '14

Hi, See presence_reginfo - Extension to Presence server for registration info replication (RFC3680) http://kamailio.org/docs/modules/stable/modules/presence_reginfo.html On 02/05/2014 07:56 AM, Premchandiran wrote: > Hi All, > > May I know whether kamailio supports event header with reg (EVENT:reg) > (rfc 3680) , if kamailio supports may I know the module whether it is in > presence or presence_xml or any other module? > > > > Regards, > > *Prem Chandiran M*** >

1 0

Problem with response of http_query of the moudule utils
by Aman Agarwal 05 Feb '14

05 Feb '14

Hi, I am using http_query to make some HTTP API calls. I have found that the response of the HTTP call always has the initial 1062 characters missing. The HTTP call is sending strings of different lengths but the initial 1062 characters are always missing. Can anybody help me with this issue or has any idea why this might be happening? Thanks Aman Agarwal

1 0

Msilo message body type
by sipatse＠in.gr 05 Feb '14

05 Feb '14

1 0

websocket relay
by jaflong jaflong 05 Feb '14

05 Feb '14

Hi Everyone, I want kamailio to do a single task, that is relay incoming (webrtc sip over websockets) connections to asterisk. All sip handling is to be done is asterisk. I have configured asterisk with tls settings. My sample conf file is below At the moment I am getting these errors ERROR: tm [ut.h:343]: uri2dst2(): no corresponding socket for af 2 ERROR: tm [t_fwd.c:520]: prepare_new_uac(): ERROR: can't fwd to af 2, proto 3 (no corresponding listening socket) Please can anyone provide any advise to complete this configuration listen=tcp:10.2.3.4:5080 enable_tls=yes tcp_connection_lifetime=3605 tcp_accept_no_cl=yes ####### Modules Section ######## # set paths to location of modules (to sources or installation folders) mpath="/usr/local/lib64/kamailio/modules/" loadmodule "mi_fifo.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 "mi_rpc.so" loadmodule "acc.so" loadmodule "sdpops.so" loadmodule "nathelper.so" loadmodule "xhttp.so" loadmodule "websocket.so" loadmodule "tls.so" # ----------------- setting module-specific parameters --------------- # ----- 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) /* 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) # ----- nathelper params ----- modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") # WITH_TLS # ----- tls params ----- modparam("tls", "config", "/usr/local/etc/kamailio/tls.cfg") ####### Routing Logic ######## event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); xlog("L_INFO", "HTTP Request Received\n"); if ($hdr(Upgrade)=~"websocket" && $hdr(Connection)=~"Upgrade" && $rm =~"GET") { if (ws_handle_handshake()) { exit; } } xhttp_reply("404", "Not Found", "", ""); } request_route { if ((($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT) && !(proto == WS || proto == WSS))) { xlog("L_WARN", "SIP request received on $Rp\n"); sl_send_reply("403", "Forbidden"); exit; } route(REQINIT); route(NATDETECT); route(RELAY); } route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } route[NATDETECT] { if (nat_uac_test(64)) { # Do NAT traversal stuff for requests from a WebSocket # connection - even if it is not behind a NAT! # This won't be needed in the future if Kamailio and the # WebSocket client support Outbound and Path. force_rport(); if (is_method("REGISTER")) fix_nated_register(); else { if (!add_contact_alias()) { xlog("L_ERR", "Error aliasing contact <$ct>\n"); sl_send_reply("400", "Bad Request"); exit; } } } } route[RELAY] { xlog("L_INFO", "Forwarding Request\n"); $ru = "sip:"+$rU+"10.2.3.5:5080;transport=tcp"; if (!t_relay_to_tls()) { sl_reply_error(); return; } exit; }

2 1

reg event support in subscribe
by Premchandiran 05 Feb '14

05 Feb '14

Hi All, May I know whether kamailio supports event header with reg (EVENT:reg) (rfc 3680) , if kamailio supports may I know the module whether it is in presence or presence_xml or any other module? Regards, Prem Chandiran M

1 0

GSM PDU Decoding
by Ramya Ramamurthy 04 Feb '14

04 Feb '14

Dear SR-Users, I am using kamailio for decoding of SIP Packets with Message Body as a GSM PDU. But I am not sure of the modules which i need to use for the same. Some help on this would be greatly appreciated. Thanks, ~Ramya.

5 7

Change the name of the location table for the usrloc module
by Alejandro Recarey 04 Feb '14

04 Feb '14

Hi everybody, I have been trying to setup a new installation of kamailio, and I need the user location table to have a specific name. This will allow two kamailio servers to use the same database for their registry information. I cannot find any modparam in the documentation that allows me to set the table name for the usrloc. Is there any way to do this? It seems like an oversight, every other module I have been able to change the table name without a problem. Thank you, Alex

2 2

Cluster: check/mark servers in cluster
by Victor V. Kustov 04 Feb '14

04 Feb '14

Hi, all! I had in config: #!define KAMDB "cluster://postcash" loadmodule "db_cluster.so" modparam("db_cluster", "connection","con1=>postgres://user1:password1@host1/kamailio") modparam("db_cluster", "connection","con2=>postgres://user2:password2@host2/kamailio") modparam("db_cluster", "cluster", "postcash=>con1=9s8p;con2=9s8p") modparam("usrloc", "db_url", KAMDB) and save registered user's locations in cluster after some server's restarts second base has empty set. How can I see server's list with status? How can I set second server worked? (I check - all OK with it) -- WBR, Victor JID: coyote(a)bks.tv JID: coyote(a)bryansktel.ru I use FREE operation system: 3.12.9-calculate GNU/Linux

1 0

Hello from newbie
by Alex Lake 04 Feb '14

04 Feb '14

Just trying to get to grips with Kamailio and thought I'd say hello to you all... Not sure if this is of any interest, but I've found it quite hard to get into Kamailio compared to (say) Freeswitch. This is not meant as criticism at all, but if you're looking to make it easier, I may be able to help! Installation was more or less OK, although a couple of slightly blind alleys and lack of concrete examples of config files. I believe I have a working server, but where to go next has left me a little stumped! What I'm trying to do is have a SIP load-balancer such that I can have a set of Freeswitch servers that can have traffic routed to them on a controlled basis, allowing me to point certain accounts at certain servers and take individual servers out of service for upgrade etc. I think this is SIP server redirection. If there was an example of how to do it - eg. what files need to be changed, any database entries, etc. that would be most useful. Unfortunately, all my Googling/list searching so far has only come up with questions that were either badly worded or not answered. Happy to turn anything I come up with into a beginner-friendly case-study.

2 5

Asterisk re-INVITE race condition, error 500.
by David K 04 Feb '14

04 Feb '14

Hello all, So I have three machines, we don't care about audio for this problem, so everything I mention here is SIP related. Freeswitch <--> Kamailio 3.3.2 <--> Asterisk 1. Asterisk sends an INVITE to Freeswitch through the Kamailio proxy. 2. Kamailio replies 100 Trying and forwards to Freeswitch 3. Freeswitch replies 100 Trying 4. Freeswitch replies 180 Ringing to Kamailio 5. Kamailio routes the answer to Asterisk 6. Freeswitch replies 200 OK to Kamailio 7. Kamailio replies 200 OK to Asterisk 8. Asterisk replies ACK to Kamailio 9. Asterisk sends a re-INVITE to Freeswitch through Kamailio 10. Kamailio routes the re-INVITE to freeswitch 11. Kamailio routes the ACK to freeswitch. 12. Freeswitch replies 500 Server error because it got a re-INVITE before the ACK. So, my problem is that Kamailio seems to process my re-INVITE more quickly than the ACK. So Freeswitch replies an error because it got the re-INVITE before the ACK. So my "solution" is to add a usleep(20); for re-INVITEs on Kamailio, but I think this is a lousy solution. Has anyone here had to deal with problems where Kamailio routes a re-INVITE faster than an ACK causing endpoints to return error messages? Has anyone had to deal with a similar issue? Thanks, David

6 11

Kamailio World 2014 - New speakers and presentations
by Daniel-Constantin Mierla 04 Feb '14

04 Feb '14

Slightly less than two months to the start of Kamailio World 2014 <http://www.kamailioworld.com> [1] the organization of the event is getting accelerated. We received plenty of interesting proposals so far, we expect to end the Call for Speakers very soon, earlier than previously announced. If you have plans to submit, you should really hurry up. The profiles of about 20 speakers have been published in Speakers page <http://conference.kamailio.com/k02/speakers/> [2], few others that were accepted already will be added soon. Details for about 15 sessions during the conference days (April 3-4, 2014) are available in the Schedule page <http://conference.kamailio.com/k02/schedule/> [3]. The technical workshop on the 2nd of April is getting to the final shape as well. Similar to last year, expect several exhibition spots where various companies will present their services or products during the conference days. In the evening of 3rd of April it will be the cocktail party, a relaxing event for social networking around good food and drinks. We are grateful to our sponsors [4], they are making possible this event: FhG Fokus <http://www.fokus.fraunhofer.de/en/fokus/index.html>, Asipto <http://www.asipto.com>, Sipwise <http://www.sipwise.com>, Sipgate <http://www.sipgate.de>, IT Center <http://www.itcenter.com.pt/> and NG Voice <http://www.ng-voice.com/>. Should you consider sponsoring, contact us via email at <conference [at] kamailio.com>**and we can present you more details. The event take place again at the very city center of Berlin, next to Island of Museums and Alexanderplatz. The number of seats is limited and they can fill up very quickly, if you plan to attend, do not delay the registration – see more details in Registration page <http://conference.kamailio.com/k02/registration/> [5]. /Looking forward to meeting many of you in Berlin! / Daniel/ / [1] - http://conference.kamailio.com [2] - http://conference.kamailio.com/k02/speakers/ [3] - http://conference.kamailio.com/k02/schedule/ [4] - http://conference.kamailio.com/k02/sponsors/ [5] - http://conference.kamailio.com/k02/registration/ -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Proxied authentication
by Pete Ashdown 04 Feb '14

04 Feb '14

I'm having trouble divining the proper way to authenticate calls to remote destinations that require it. I'm hoping someone can clear it up. Freeswitch client server A is authenticated to Kamailio. Freeswitch test server B is authenticated to Kamailio. Calls from A -> Kamailio -> B fail with rejection of the authentication information that A is using to Kamailio. As far as I understand, I need to rewrite the authentication information with UAC? However, UAC's uacreg table seems to tie remote users to remote destinations, when all I want to do is authenticate all calls routed to the destination regardless of what the user or the source is. Am I using the wrong module?

2 1

Re: [SR-Users] Regd. MAX_LDG_LOCKS
by Shankar 04 Feb '14

04 Feb '14

Hi, Can someone clarify here please? Regards, Shankar From: Shankar [mailto:shankar.rk@plintron.com] Sent: Monday, February 03, 2014 10:53 AM To: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List' Subject: Regd. MAX_LDG_LOCKS Hello, Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c? Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if the hash size is increased? Regards, Shankar

1 0

Media-proxy Query
by Nandini madhu 04 Feb '14

04 Feb '14

Dear All, Greetings, I have configured Kamailio (4.0.3) with mediaproxy server, with this set-up audio/video calls are going good and hence NAT issue has solved. I have used two soft clients: 1) IMSDroid 2) Bria. But i have a query about media-proxy statistics i.e in the syslog, the info about media-proxy activity is shown as below: *Case 1*: when Call between two IMSDroid clients. caller_codec : 'Unknown(73)' callee_codec : 'Unknown(73)' callee_ua : 'unknown agent'. *Case 2* : When call between two Bria clients. 'callee_ua': 'unknown agent'. (Calls using Bria clients media-proxy's syslog shows Audio codec names, but using IMSdroid clients it is showing 'Unknown' for Audio codec names ). Find the attachment below for the full syslog about the mentioned unknown behaviour. And also find my kamailio.cfg file. And also logging in the syslog as shown like RTP: Unknown , RTCP: Unknown. In this context, there is a jitter in audio calls and pixelled video sometimes, So is there any wrong with the above mentioned "unknown' factor in this problem of jitter/pixelled audio/video calls ? (AFAIK these payload type 73 (i.e 72-76) is reserved for RTCP conflict avoidance. right? ) What could be the problem for this 'Unknown' issue? How can i solve this issue ? Anything can be done in kamailio script? And how these RTCP payload types (72-76) plays a role in audio/video calls? Any suggestions will greatly help. please help me in clarifying these issues. Thanks in advance. Regards, Nandini

2 3

Buffer Size
by Wingsravi R 04 Feb '14

04 Feb '14

Dear Kamailio'ns I am working on Kamailio (V 4.0)+ Mediaproxy server (2.5.2) running on Ubuntu 12.04. I am experiencing Latency, jitter, pixel led, choppy video errors in my set-up. So i wanted increase buffer sizes in my kamailio server , Mediaproxy server and Ubuntu also. In that regards i have increased Shared memory value to 512 MB and Package memory value 16 MB. BUFFER SIZE value to 8 MB in *config.h* file, But where can i change the value for 'MAX_RECV_BUFFER_SIZE' ? And are there any settings to increase Buffer Size of Mediaproxy server ? Is this changes will affect on my issues ? PS: I even changed ubuntu settings also : net.core.rmem_max= 8388608 net.core.wmem_max= 8388608 (but these values reset to default values again when i restarted system.) Please help me in resolving this issues. Any help will appreciate. Regards, Ravi

1 0

Re: [SR-Users] dialog list query
by John Murray 03 Feb '14

03 Feb '14

From: Charles Chance <charles.chance(a)sipcentric.com> To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org> Subject: Re: [SR-Users] dialog list query Message-ID: Charles hi, >What db_mode are you using for dialog module? Mode 5. I Don't need to persist the dialog state so means table maintained in memory and not flushed to disk until shutdown but I can access it through normal avp_db_query right? >Are the entries in the db if you check manually? If I do sercmd dlg.dlg_list I see the call fine including callid etc. >Are you able to fetch other data using avp_db_query? Yes lots of queries to non dialog tables working fine. >And do you see any errors in the log? No logs show query happening fine and returning Null. Thanks John

2 4

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