- sr-users - kamailio.org

(no subject)
by Nelson Migliaro 01 Jul '15

01 Jul '15

Hello everybody, My SIP vendor request me to replace FROM before sending the traffic. In order to achieve this I use uac_replace_from. UAC module is setup in restore_mode = auto. In my insfrastructure I have an Asterisk and then a Kamailio that connects to vendor via internet. Softphone -> Asterisk -> Kamailio -> Internet -> SIP vendor If caller ID is setup in Asterisk using CALLERID(num)=34888888888 and then INVITE is forwarded to Kamailio, the call is established and finished … [View More]correctly but the URI in TO field in BYE request from Kamailio to Asterisk contains garbage. In the scenario the callee hangs up the call. Example of TO Field with garbage: 34888888888 <sip:50026896@no{soy,ns^^> What I do see is that the number "50026896" that is part of the URI is the same I use in: uac_replace_from("50026896", "sip:50026896@sip.vendor.es"); Something else that I have found is that vsf field is the same in the INVITE and in the BYE. ---------------------------------------------------------------------------------------------------------------- 2015/06/23 17:48:38.552442 192.168.0.2:5060 -> 192.168.0.1:5060 BYE sip:34888888888@192.168.0.1:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.0.2;branch=z9hG4bKfb49.73c6517609cdb6f7ec00b1f40a05dbe9.0 Via: SIP/2.0/UDP 8.8.8.8.8;rport=5060;branch=z9hG4bKfcdf.3767c59c2d0e3d8ab695669845ce4cea.0 branch=z9hG4bK04boo6104o5hcso0c2a1sd0000g00.1 Call-ID: 4bf8effb45b0ae8e049366297924cbba@192.168.0.1:5060 From: <sip:28999999999@192.168.0.2;tag=k0eci3x3-CC-30 To: 34888888888 <sip:50026896@no{soy,ns^^>;tag=as041b7d84 CSeq: 1 BYE Reason: Q.850;cause=16;text="normal call clearing" Max-Forwards: 67 Content-Length: 0 ------------------------------------------------------------------------------------------------------------------ DEBUG: uac [replace.c:525]: restore_uri(): getting 'vsf' Route param DEBUG: uac [replace.c:533]: restore_uri(): route param is 'AAAAAAEECQkCAgsNAXBeL0NGQUsfVl02Ni44Mw--' (len=40) DEBUG: uac [replace.c:607]: restore_uri(): decoded uris are: new=[sip:50026896@no{soy,ns#005#007] old=[sip:34888888888@8.8.8.8] DEBUG: uac [replace.c:525]: restore_uri(): getting 'vst' Route param DEBUG: uac [replace.c:533]: restore_uri(): route param is 'AAAAAAQPAw8MDgsAAHZBKRVdAhoVHQ4XH1BdYWJhbnRlLmVz' (len=48) DEBUG: uac [replace.c:607]: restore_uri(): decoded uris are: new=[ sip:28999999999@192.168.0.1] old=[sip:999999999@sip.vendor.es] ----------------------------------------------------------------------------------------------------------------------------------- [View Less]

2 1

Kamailio no recieved 480/486 messages
by Yuriy Gorlichenko 01 Jul '15

01 Jul '15

At my confiig I have route like this onreply_route[REPLY_FROM_WS] { if(status=~"[12][0-9][0-9]") { xlog("L_INFO", "Manage_Reply from webrtc client {$si:$sp} for method {$rm}: $rs"); rtpengine_manage("force trust-address replace-origin replace-session-connection DTLS=passive ICE=remove RTP/AVP"); route(NATMANAGE); } } This route successfully handling replies 180 183 and 200 and then (after natmanage route) resend to mediaserver. When callee client reject call it send 480 ot 486 message … [View More]

2 3

dialog flags vs dialog variables vs dialog profiles
by Muhammad Shahzad 01 Jul '15

01 Jul '15

Hi, Lasting night i was doing some tests and identified a strange behavior from dialog module. I am using Kamailio v4.3.0 rev. c6aa95. I basically wanted to identify if an incoming sequential ACK (from caller for an answered call) or a BYE (from callee who wants to hangup the call) belong to an existing dialog. First I tried to use dialog profiles as they were already enabled in my kamailio.cfg for every call. Calling the function "is_in_profile" after loose_route in WITHINDLG route, does … [View More]

2 1

TLS certificate verification failed
by Austin Einter 01 Jul '15

01 Jul '15

Hi All I am having a sip client, I am using GNU tls for transport layer security. I am using Kamailio (TLS enabled) to test all the functionalities. I did registration over TLS. It was fine. I tried to make call. I was able to send INVITE. Kamaiio trying to connect to called party (which is again my sip endpoint). That time certificate verification failed. *Error log* * 8(14180) ERROR: tls [tls_server.c:1193]: tls_read_f(): TLS write:error:14090086:SSL routines:… [View More]

2 1

Media timeout using RTPProxy
by Sharath Kumar 01 Jul '15

01 Jul '15

Hello, Is there an API that can notify Kamailio of media inactivity in the RTPProxy? The documentation has something called "timeout_socket" . I don't understand how to use it though. Any help will be greatly appreciated. Thanks Sharath

2 1

How can I figure out the problem why call is not establish?
by zhangkai.gis 01 Jul '15

01 Jul '15

Hello. When I installed kamailio I add users then I can make a call.But When I install asterisk I found the asterisk take over the kamailio and I can register users.But When I make a call.It shows me can not establish the call.How can find the problem?Any logs?Or tools? Thanks, zhangkai

2 1

Fwd: websocket devices keepalive not working
by Yuriy Gorlichenko 01 Jul '15

01 Jul '15

As I read at README to Nathelper it may not work with usrloc table, Is it write? now I use NAT traversal module and Websocket module to keepalive mechanisms, that uses UDP or WS. with UDP it is wery simple method - OPTIONS replies. With WebSocket module keepalive mechanism uses thomething else. Not a SIP methods, I see at TCPDUMP packets that marks with modparam("websocket", "ping_application_data", "WebSockets rock") I need to handle replies of keepaliwe mechanism. How I may handle replies … [View More]

1 0

WWW-Authenticate header Query
by Anil Kumar 01 Jul '15

01 Jul '15

Hi, I am using Kamailio(4.2.5) as my SIP proxy also enabled authentication. Added two users xyz_0 and xyz_1 to the kamailio database. While Registration I am getting 401 Unauthorized as shown below SIP/2.0 401 Unauthorized Via: SIP/2.0/TCP 192.168.1.107:48601;branch=z9hG4bK858339335 From: <sip:xyz_0@192.168.1.107>;tag=251958751 To: <sip:xyz_0@192.168.1.107 <sip%3Axyz(a)192.168.1.107> >;tag=ca5a1db24813f1937965921e320b98e4.6232 Call-ID: 1808202998(a)192.168.1.107 CSeq: 2 … [View More]

2 1

REST API
by Marek Cervenka 01 Jul '15

01 Jul '15

hello, is there REST API for kamailio for basic functions like subscribers, dispatcher, blacklist/whitelist, ACL, dial plan table, ... ? thank you -- --------------------------------------- Marek Cervenka =======================================

2 1

websocket devices keepalive not working
by Yuriy Gorlichenko 30 Jun '15

30 Jun '15

I try to send keepalive requests (options) to clients at usrloc I tried 4 mechanisms 1) nathelper modparam("nathelper", "sipping_method", "OPTIONS") modparam("nathelper", "natping_interval", 15) modparam("nathelper", "ping_nated_only", 0) modparam("nathelper", "sipping_bflag", 7) modparam("nathelper", "sipping_from", "sip:pinger@mydomain") but it didn't send keepalives to noone client 2)nat_traversal I tried to trigger keepalives with nat_keepalive() when REGISTER coming to my service It … [View More]

3 3

REST API
by Marek Červenka 30 Jun '15

30 Jun '15

hello, is there REST API for kamailio for basic functions like subscribers, dispatcher, blacklist/whitelist, ACL, dial plan table, ... ? thank you -- --------------------------------------- Marek Cervenka =======================================

1 0

interconnect 2 Kamailio server
by kai.ohnacker＠cbc.de 30 Jun '15

30 Jun '15

Hello, after some trying with SEMS and Blox as SBC, I changed my idea of SIP infrastructure from Kamailio (private) -SBC in DMZ (Private & Public) - www (Public) to Kamailio (private) - Kamailio with rtpproxy in DMZ (Private & Public) - www (Public). Now, my questions are: How can I connect 2 Kamailio SIP server together? Which modules I need? Is there somewhere a good howto? Cheers, Kai Ohnacker

2 5

BYE from CANCLEd path gets forwarded to caller
by Daniel Tryba 30 Jun '15

30 Jun '15

I was testing a scenario whith parallel forking (multiple registers) where 2 endpoints answer near simultaniously. When phone that was just a bit slower hangs up, the BYE gets forwarded to the caller and thus the connection is terminated. This is as far as I know for stateful transactions (t_relay()) I always assumed in this scenario the state machine in kamailio would prevent this kind of behavior by itself. Is there a way to prevent these messages being forwarded?

2 2

Which Open Source IVR can be used with Kamailio and how?
by zhangkai.gis 30 Jun '15

30 Jun '15

Hello, Which Open Source IVR can be used with Kamailio and how? Thanks, zhangkai

2 8

invalid char in json text
by Kelvin Chua 30 Jun '15

30 Jun '15

Playing around with ndb_mongodb getting this error: ERROR: ndb_mongodb [mongodb_client.c:262]: mongodbc_exec_cmd(): Failed to run command: lexical error: invalid char in json text query is very simple: db.cdrs.insert({time:new Date(),src_user:"kelvin",term_ani:"14112",src_domain:"domain.com ",src_ip:"0",dst_ouser:"18188",dst_user:"18112",dst_domain:"domain.com"}) which is inside a pv mongodb_cmd("mgs1", "datab", "cdrs", "$var(MNG_MISSED)", "mgr1"); tried this: insert({time:new Date(),… [View More]

3 7

Siremis Register Page problem.
by Sven Juhkam 29 Jun '15

29 Jun '15

Hi! In SIREMIS I am getting the info after trying to register, that "Public registration is not enabled!" but i have set siremis/modules/ser/config/common.Main.php to $cfg_siremis_public_registrations = true; What is the problem? Thanks and Greetings, Sven

1 0

answer back from wrong IP / Interface
by Mihaly Zachar 27 Jun '15

27 Jun '15

Hi Gents, We have a redirect server based on Kamailio (4.2.3). The server has multiple IPs, but Kamailio is bound to only one address: http://view.xscreenshot.com/9dfdf449a387bdc6f9a719eae3620416 *Sometimes* it answers back from a wrong IP address, here is the proof: http://view.xscreenshot.com/ac661d6b303eda6653b37be7cf65aa65 The interesting thing is that if I do: root@tralab-route-01:~# ip ro get 10.121.24.51 10.121.24.51 via 10.121.43.30 dev vlan486 src 10.121.43.17 cache ipid … [View More]

1 1

don't fragment flag in rtpengine request
by Juha Heinanen 27 Jun '15

27 Jun '15

i was wondering why sometimes requests to rtpengine don't get through and icmp unreachable destination error message is received. it turned out that in these error cases ip packet containing the rtpengine request has 0x02 (don't fragment) flag set even when the packet was bigger than 4 KB. in this case kamailio was running in an amazon container which may be doing something weird. is it somehow possible from the application (= kamailio) to control setting of that flag? -- juha

1 0

deb building system
by Victor Seva 26 Jun '15

26 Jun '15

Hello, I would like to inform that the deb nightly builds are going to be disabled. I'm having problems with the actual configuration and until I found the time to fix them the service will be out of order. No new debs will be produced until further notice. Cheers, Victor

2 1

limit calls to incoming only?
by Peter Villeneuve 26 Jun '15

26 Jun '15

Hi, Is it possible for Kamailio to restrict certain users (like in a group) to only receive calls but never dial out or send SIP Simple messages outbound, while allowing all other "regular" users to make outgoing calls and text messages as well as receive them? If so, which module do you guys recommend I look into? Cheers, Peter

2 3

fix_nated_contact NAT rtpproxy problems
by Vik Killa 25 Jun '15

25 Jun '15

Hello, We are trying to get Kamailio working as an SBC using rtpproxy(); The config seems to work except with some carriers, kamailio does not recognize the ACK because it does not match the contact header of the OK I've been trying to figure out how to get kamailio to send the OK back using the public IP address but I cannot figure out how. I've tried using various deployments of the nathelper module such as fix_nated_contact() set_contact_alias() No matter what though, Kamailio will not … [View More]

1 0

"00" prefix record problem on ACC
by Yasin CANER 25 Jun '15

25 Jun '15

3 2

linking math.h while compiling a module
by Shouvanik Chakrabarti 25 Jun '15

25 Jun '15

Hello, I have developed a Kamailio module to handle group messaging and am using certain functions from the libm.so library. Compilation happens fine, but Kamailio subsequently fails to start because the math.h symbols are unlinked/undefined. Could someone please suggest a workaround for this. Thanks, Shouvanik.

2 4

How to disable retransmits via TCP connection? etc.
by Andrey Utkin 25 Jun '15

25 Jun '15

Hi! We meet such an issue with some kinds of client internet connections (e.g. reproduces always on local wifi, but doesn't repr. on 3g inet). We don't know what are exact network characteristics, but what happens from perspective of traffic on SIP server is the following: 1. the SIP client registers successfully to Kamailio (which is recent git master HEAD) with TCP transport for SIP; 2. another client calls this user; 3. Kamailio relays INVITE, it gets transmitted fully and ACK-ed on TCP … [View More]

4 11

Kamailio Server Maintenance - Wed-Thu Night
by Daniel-Constantin Mierla 25 Jun '15

25 Jun '15

Hello, during the night between Wed (June 24) and Thu (June 25), planned to start not early than 00:00 GMT+1, there will be some schedule maintenance work to the infrastructure that is hosting some of the kamailio.org servers. The main affected services will be: - main website (www.kamailio.org) - wiki portals - mailing lists (lists.sip-router.org) - git mirror (git.kamailio.org) It is expected to have short downtimes of few minutes. Cheers, Daniel -- Daniel-Constantin Mierla … [View More]

1 1

Kamailio + RTPEngine + Asterisk
by Javier Aristizábal 24 Jun '15

24 Jun '15

Hello folks, I am trying to configure this on the same server: Kamailio v4.2 port 5060 RTPEngine v2.3 port 22222 Asterisk v11.18.0 port 5080 I am follow the Asipto tutorials, for the Kamailio and the real time configuration. Now, I can talk between extension and PSTN without issues. But the trouble is with the Status registration with Asterisk. And I need that Status OK because I am using queues in asterisk for call centre. I got this from with: sip show peers Name/username … [View More]

2 16

Kamailio proxy at Amazon EC2 (behind NAT)
by Alexandru Covalschi 24 Jun '15

24 Jun '15

Hello. I'm trying to set up this (v 4.2 stable): peer <--> ec2 <--kamailio+rtpengine--> asterisk scheme I use advertised adress for SIP and WS connections. The problem is that on SIP I get one way audio - I can receive audio from asterisk, but I can't transmit audio there - my SIP UA tries to send data to Kamailio-s local EC2 IP. In case of WebRTC I get lot's of erros: Jun 23 01:58:57 kamailio /usr/sbin/kamailio[18325]: WARNING: <core> [msg_translator.c:2778]: via_builder(): … [View More]

2 15

Kannot start kamailio 4.3
by Yuriy Gorlichenko 23 Jun '15

23 Jun '15

Try to start kamailio on Ubuntu 14.04.02 Get this errors ERROR: ctl [init_socks.c:115]: init_unix_sock(): ERROR: init_unix_sock: bind: No such file or directory [2] Jun 23 08:54:29 kamailio-test kamailio[3706]: ERROR: ctl [ctl.c:273]: mod_init(): ERROR: ctl: mod_init: init ctrl. sockets failed Jun 23 08:54:29 kamailio-test kamailio[3706]: ERROR: <core> [sr_module.c:945]: init_mod(): Error while initializing module ctl (/usr/local/lib64/kamailio/modules/ctl.so) my params for ctl # ----- … [View More]

4 9

kamailio fails after start
by Yuriy Gorlichenko 22 Jun '15

22 Jun '15

Hello. I Installed kamailio on ubuntu 14.04 that runs as virtual systemOpenVZ. after starting kamailio I see that it runs ok with kamailio start or kamctl start at ps -ax I see working processes. But after one minute of working kamailio fails with kamailio: ERROR: <core> [daemonize.c:315]: daemonize(): Main process exited before writing to pipe I see nothing more at debug file. No errors. (I run with debug=4) my cfg parameters at start mhomed=1 memdbg=5 memlog=5 fork=yes children=6 … [View More]

2 2

Kamailio transformation
by Ali Taher 22 Jun '15

22 Jun '15

Hello, Suppose I have $var(a) = 1234#5678 and $var(b)=123455667 I need to get the number before '#' character if exists , meaning that from $var(a) I must get 1234# and from $var(b) I must get empty string. I tried $var(pref)= $(var(a){s.select,0,#}); but I'm getting the whole string if # doesn't exists. There is a way to check if # exists by subtracting the length of the string before and after removing # character and check if length changes , but I want a cost-less method. … [View More]

3 2

Capture a Match from Regex comparison
by Sebastian Damm 22 Jun '15

22 Jun '15

Hi, we have some cases, where we get multiple PCMA lines with different numbers from a peer. One of our backend systems doesn't handle that correctly. So what I want to do is detect whether there is a PCMA line with a non-standard number in the SDP. This is how an SDP looks like: v=0 o=hiQ9200 2990220150519102450 1229717573 IN IP4 1.2.3.4 s=Phone Call c=IN IP4 1.2.3.4 t=0 0 m=audio 40174 RTP/AVP 8 0 18 96 97 13 100 98 99 a=rtpmap:8 PCMA/8000 a=fmtp:8 vad=no a=rtpmap:0 PCMU/8000 a=fmtp:0 vad=… [View More]

2 3

Kamailio with Blox SBC (opensips based) - Wrong CSeq
by kai.ohnacker＠cbc.de 22 Jun '15

22 Jun '15

Hello, my setup is a kamailio server as registrar and Blox as SBC. Blox is a freeware GUI with Opensips as framework. Kamailio is located in the private network and Blox operates with 2 NICs (private and public) Now the following problem: If I make a call from public (phonerlite) to private (mayah), the connection don’t reach the “framed” state and is “broken” after 30 sec. After evaluating the log files, I found that the CSeq from Kamailio is wrong. The invite comes from CSeq: 9 INVITE The … [View More]

3 4

Redirect with path
by Kelvin Chua 22 Jun '15

22 Jun '15

on my registrar server: after calling lookup, and getting AOR with path, how do I send the path info back as a redirect? Kelvin Chua

2 2

event_route: what modules/functions are likely to work or not work
by Armen Babikyan 22 Jun '15

22 Jun '15

Hello, With respect to *_route blocks in kamailio configs, I gather that event_route is the newest type of route in the config vocabulary. However, many modules have functions that specifically state that they work within certain routes, like REQUEST_ROUTE and FAILURE_ROUTE, with the implication that they won't work in other routes. For example, there are some functions that "work" in EVENT_ROUTE as well, and that this could be a matter of either documentation not being updated yet, or funny/… [View More]

2 1

Installation problem, kamailio 4.3.0 on ubuntu 14.04.02
by Edin Fejzić 22 Jun '15

22 Jun '15

I just installed kamailio 4.3.0 with apt-get. But it won't start. mysql and /etc/kamailio/kamctlrc done. Minimum change to kamailio.cfg Any idea? syslog output: /usr/sbin/kamailio[1291]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob /usr/sbin/kamailio[1291]: INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available /usr/sbin/kamailio[1291]: INFO: usrloc [hslot.c:51]: ul_init_locks(): locks array size 1024 /usr/sbin/kamailio[1291]: ERROR: ctl [init_socks.… [View More]

2 1

Kamailio invite counter
by Ali Taher 19 Jun '15

19 Jun '15

Hello, I want to define a counter that increase in every invite. I tried the below : if (is_method("INVITE")) { $var(u)=$var(u)+1; xlog("L_INFO","Counter : $var(u) " ); } But the counter is reset to 1 randomly (even before restarting kamailio service) How can have a proper counter that count invite messages. Thanks Ali

4 7

Port 5061 issue
by Ankhit Vivekananda 19 Jun '15

19 Jun '15

Hello, I have configured kamailio 4.0.4 long back. Now, I wanted to enable the usage of port 5061 with TLS. By doing so, the client(video camera) can place outgoing calls fine. But while receiving an incoming call, the message does not get sent out to the other client. Hence, the call fails. I can place and receive calls on port 5060 successfully without any issues. Can anyone please tell me why port 5061 is giving me a problem. Also, as a test, I set up kamailio on another machine(version 4.… [View More]

2 1

SIP-I trunking
by Jérôme Simionato 19 Jun '15

19 Jun '15

Hello, I'm planning to interconnect kamailio with a SIP-I provider (an i have no more information at this time from my telco). I read the documentation about the SIP-I module, who need to be completed to match our needs. basically, we need to read the location parameter for incoming call, and be able to set redirecting number for outgoing call Does anybody use this module for SIP-I ? Have you experiences of SIP-I trunking with telco ? And another question: when you make an ISUP (SS7) … [View More]

2 3

SIP Ping a device using Kamailio
by Nelson Migliaro 19 Jun '15

19 Jun '15

Hello, Is there a way to ping a device using Kamailio. In my scenario I need to access a Kamailio located in my DMZ over a firewall that is only open in LAN > DMZ direction. It is close in the other way round. In my current configuration I keep the link open using Asterisk qualify option in SIP. I would like to replace Astersik located in LAN with Kamailio thus I need to keep the link open. I know there is an option using dispatch but I would like to avoid using this module in order to … [View More]

2 1

WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction
by Roberto Fichera 19 Jun '15

19 Jun '15

Hi All, I'm getting the warning in the subject after replacing a route() with a async_task_route(). In the called route() I'm doing some db query and send notify messages using the uac module. The async_task_route() is called once received a register message. Any idea what's is going on? Cheers, Roberto Fichera.

2 3

users with or without asterisk integration on the same kamailio database
by asterisk asterisk 19 Jun '15

19 Jun '15

I wish to know how I can have two kinds of users 1. some users with real time integration with asterisk 2. other users do not How can I achieve in the same kamailio instance?

3 3

Dispatcher and options_reply
by jay binks 19 Jun '15

19 Jun '15

Hello, So Im using dispatcher to poll SBC's behind my kamailio load balancer. What I need to do is get a count of how many "active" SBC's there are in the dispatcher module. ( how many SBC's are actively responding to their options ping ) so that I can then use this info when I reply to an OPTIONS on the load balancer. effectively , if there are no SBC's active, the LB needs to not reply to options. I COULD use ds_select_dst or something , but is that going to be overkill from a CPU … [View More]

2 1

siremis with postgres
by Tomas Zanet 19 Jun '15

19 Jun '15

Hi all, I need to install Kamailio, and Siremis as well, with Postgres backend. My current versions are the following: - Kamailio 4.2.1 - Siremis 4.2.0 - PHP 5.3.10-1ubuntu3.18 - postgres 9.1.3 To do so, I installed libpq-dev and compiled Kamailio with db_postgres module. After that, I create the Kamailio database using kamdbctl create No problems so far....while I’m facing some problem when I tried to install Siremis with Postgres. To do so, I installed php5-pgsql before and then I did the … [View More]

2 4

kamcmd
by asterisk asterisk 18 Jun '15

18 Jun '15

I am compiling the kamailio 4.3 in raspberry Pi 2. It compiled and worked. However, kamcmd did not work as it looks for the file /var/run/kamailio/kamailio.ctl which is not present. Similar issue found for kamctl but I fixed it by change the /tmp directory to /var/run/kamailio Did I miss something?

2 1

404 Not found error when login Siremis-4.2.0
by Chathura Senanayake 18 Jun '15

18 Jun '15

Hello, I need a help with siremis-4.2.0. I have installed Kamailio-4.3 and have it running. Then I installed Siremis-4.2.0. When I try to login to the Siremis by using login name "admin" and password "admin", it shows a 404 Not found error message as follow. Not Found The requested URL /siremis/system/general_default was not found on this server. ------------------------------ *Apache/2.4.7 (Ubuntu) Server at 172.16.2.9 Port 80* I have run the #a2enmod > rewrite and Restart the apache2. … [View More]

3 7

Kamailio number of matches of specific character in a string
by Ali Taher 18 Jun '15

18 Jun '15

Hello, I just need to count the number of a specific character in a string. For example I want to count the number of "a" in the following string : "bbbaddaa34" I searched among transformations but didn't find such tool. Any help would be appreciated. Thanks Ali

2 1

using uac_replace_from( )
by Al S 18 Jun '15

18 Jun '15

Hi, I am trying to change only the "display name" of the FROM header using uac_replace_from().However, the value is not being changed (see below) request_route { .... xlog ("L_INFO", "fu=$fu"); uac_replace_from("pbx", ""); xlog ("L_INFO", "fu=$fu"); # authentication route(AUTH); ....} Am I missing anything? Any help in this regard would be greatly appreciated. Thanks,Al

3 2

Re: [SR-Users] loose_route to find transport=tcp
by Ryan Kendrick 17 Jun '15

17 Jun '15

After enabling and deciphering debugging it appears there may be a bug. I also reviewed https://tools.ietf.org/html/rfc5658#section-6 I cross-referenced my pcap to ensure I was looking at the reINVITE and see: Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: rr [loose.c:785]: after_loose(): *Topmost route URI: 'sip:xx.xxx.x.xx;lr;r2=on;ftag=a30a720a;did=b75.65a1;nat=yes' is me* Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:583]: … [View More]grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [xx.xxx.x.xx] == [xx.xxx.x.xx] Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5061 Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [xx.xxx.x.xx] == [xx.xxx.x.xx] Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5070 (advertise 0) matches port 5061 Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [xx.xxx.x.xx] == [xx.xxx.x.xx] Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5090 (advertise 0) matches port 5061 Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [xx.xxx.x.xx] == [xx.xxx.x.xx] Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5061 (advertise 0) matches port 5061 Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: rr [loose.c:181]: find_next_route(): *No next Route HF found* Jun 16 15:01:29 xxxxxxxxxxxxx /usr/sbin/kamailio[643]: DEBUG: rr [loose.c:847]: after_loose(): no next URI found There is definitely another Route header immediately below the one found above, but find_next_route() doesn't find it . I added my own debugging to loose.c and if ((_m->last_header->type!=HDR_ROUTE_T) || (_m->last_header==*_hdr)) { LM_DBG("No next Route HF found\n"); LM_DBG("_m->last_header->type: %d\n", _m->last_header->type); return 1; } logs find_next_route(): _m->last_header->type: 12 which is HDR_CONTENTLENGTH_T which is indeed the LAST header in the message. We have done very little work in the Kamailio source...just some database escaping in odbc for things to work properly with our database engine...but unless I'm missing something isn't it very wrong to be looking at the last header right here? I may attempt to figure out the message and/or hdr_field data structures and change it. It may also be that the issue doesn't occur when find_next_route is called with a valid _hdr which does seem to search for the "next" one vs going straight to the final header in the entire message. If this is getting overly complicated for this mailing list please let me know... Ryan On Tue, Jun 16, 2015 at 11:40 AM, Ryan Kendrick <kendrick.ryan.c(a)gmail.com> wrote: > > We are using Kamailio 4.2.5 as a registrar and proxy between many > dispersed end-users of a soft phone app and our calling platform / switch. > > Until now we have used udp exclusively but are trying to introduce tcp > between end-users and Kamailio, leaving udp between Kam and our > switch...while maintaining the ability for some end-users to use udp to Kam. > > With some simple address checks I am able to always send to our switch > over udp. If all end-users used tcp I could send everything else tcp, but I > need to maintain udp support. > > The specific problem I am having is on a reINVITE such as this one from > our platform to the a-leg: > > INVITE sip:xxxxxx@xxxxxxxxxxxxx:42679;user=phone SIP/2.0 > Via: SIP/2.0/UDP > xxxxxxxxxxxxx:5060;branch=z9hG4bK218cc8e12ll5035f67INV6a67885312aad > Max-Forwards: 35 > Route: <sip:xxxxxxxxxxx;lr;r2=on;ftag=daba971c;did=b57.4872;nat=yes> > Route: > <sip:xxxxxxxxxxx:5070;transport=tcp;lr;r2=on;ftag=daba971c;did=b57.4872;nat=yes> > Contact: <sip:xxxxxxxxxx@xxxxxxxxxxxxx:5060> > To: "xxxxxx"<sip:xxxxxx@xxxxxxxxxxxxxxxxxxxxxxxxxxx:5070>;tag=daba971c > From: <sip:xxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxxxxxxxx > :5070>;tag=6a678853-co76461-INS002 > Call-ID: MDI4ZmFjNmZhN2Y1NWE2ZTViNTkyZGUwNWE2YzUzYmU > CSeq: 7646101 INVITE > Allow: > INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,INFO,UPDATE > Content-Type: application/sdp > Date: Mon, 15 Jun 2015 20:10:18 GMT > User-Agent: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > Content-Length: 262 > > As you might notice, we have rr:enable_double_rr set: > > *There are some situations when the server needs to insert two > Record-Route header fields instead of one. For example when using two > disconnected networks or doing cross-protocol forwarding from UDP->TCP. > This parameter enables inserting of 2 Record-Routes. The server will later > remove both of them. * > > and I believe it is necessary to keep this way. Without it Kamailio > doesn't even see the reINVITE...the switch probably tries tcp and that's > not setup between the two. > > The invite above is sent to the a-leg over udp but I would expect and need > it to be tcp in this case. The reINVITE is part of an existing dialog. We > call loose_route() followed by some simple bflag setting and flag checking, > t_on_reply(), ... then t_relay(). > > I do have a functional workaround but would prefer to avoid such manual > handling by utilizing built-in functionality properly. > > # > # relay the message > # > if(route(TEST_TOGW)) { > if (!t_relay_to_udp()) { > sl_reply_error(); > } > } > else { > if ($(hdr(Route)[-1]) =~ "tcp") { > if(!t_relay_to_tcp()) { > sl_reply_error(); > } > } > else if (!t_relay()) { > sl_reply_error(); > } > } > > I'm not 100% sure how reliable or fast this will be, but it does work so > far in my simple tests. > > Is loose_route supposed to see and use the transport=tcp but isn't for > some reason? It seems like the right thing to do to me. If not, is there > anything else I can/should be doing in the tm and/or rr modules to make > Kamailio realize it needs to send this message over TCP? If not in those > two modules is there some recommended way perhaps via registrar or usrloc > etc. to make Kamailio remember/store when a user is connected via TCP and > be able to do a quick lookup before sending to them? Anything else I'm > missing or not thinking of? > > Please let me know if I can further explain and rest assured any > assistance will be much appreciated!!! > [View Less]

2 2

Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
by Jonathan Hunter 17 Jun '15

17 Jun '15

Hi Guys, Has anyone recently performed tests on kamailio 4.2 running up to 200 CPS? It would be great to know the hardware requirements for this setup. Thanks Jon

5 8

siptrace: how to log sent ACK within dialog
by Seudin Kasumovic 17 Jun '15

17 Jun '15

Hi, TM forward ACK statelessly (see log below), so there is no call of installed callback on TMCB_REQUEST_(IN)SENT in siptrace module, so I can't see way how to log ACK sent packet. Any work around to get sent ACK logged? DEBUG: sl [sl_funcs.c:388]: sl_filter_ACK(): DEBUG : sl_filter_ACK: to late to be a local ACK! DEBUG: <script>: 408:172.16.23.130:5060 <-- 198.51.100.137:52150 ACK sip:8807@127.0.0.1:5080;transport=udp DEBUG: <script>: 425: start trace ACK DEBUG: siptrace [… [View More]

2 2

Getting 407 response when calling out (on bulk registration)
by Al S 17 Jun '15

17 Jun '15

Hi, A bulk registration has been added to the "location" table:*************************** 1. row *************************** id: 113 ruid: uloc-55808d5a-33bc-1 username: pbx domain: NULL contact: sip:pbx@10.10.10.157:5060;bnc received: NULL path: NULL expires: 2015-06-17 10:08:42 q: -1.00 callid: 1-15061(a)10.10.10.157 cseq: 2last_modified: 2015-06-17 09:08:42 flags: 0 cflags: 0 user_agent: SIPp/Win32 … [View More]

1 0

kamailio sending 408 request time out
by Priyaranjan Nayak 17 Jun '15

17 Jun '15

Hi All, I am using kamailio-4.2.5 for testing setup. After starting the kamailio I am getting below message /usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -N 20 -m 512 -M 8 /usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -E loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(24471) WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 192.168.1.118 0(24471) WARNING: <core> [socket_info.c:1392]: … [View More]fix_hostname(): could not rev. resolve 192.168.1.118 Listening on udp: 192.168.1.118:4060 tcp: 192.168.1.118:4060 Aliases: 0(24471) INFO: <core> [tcp_main.c:4748]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(24473) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(24473) INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available 0(24473) INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 0(24473) INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(24473) INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 8(24481) INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Once I sent the request to kamailio server, I am not getting 408 request time out from kamailio and getting below log 12(24485) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) 12(24485) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading 9(24482) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) 9(24482) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading 12(24485) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) 12(24485) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading 10(24483) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) 10(24483) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading 13(24486) ERROR: <core> [tcp_main.c:4162]: handle_tcpconn_ev(): connect 192.168.1.114:61945 failed 13(24486) ERROR: <core> [tcp_main.c:4162]: handle_tcpconn_ev(): connect 192.168.1.114:19129 failed 13(24486) ERROR: <core> [tcp_main.c:4162]: handle_tcpconn_ev(): connect 192.168.1.114:6050 failed Could you please give me any idea how to resolve this issue ? Thanks Priyaranjan [View Less]

2 1

http_query failed to perform curl (28) errors
by Armen Babikyan 17 Jun '15

17 Jun '15

Hello, I am running across the same issue as described here: http://lists.sip-router.org/pipermail/sr-users/2015-February/086796.html Was there a resolution to this issue? I come across this issue fairly regularly. Unlike the OP, however, I do not have any luck by retrying my query: when I place my http_query within a while loop and keep 1-second delays between calls, all consistently fail with error 28. After long pauses, http_query()s start to work as expected. I think that previous … [View More]

2 1

Not found error when Siremis login
by Chathura Senanayake 17 Jun '15

17 Jun '15

Hello, I need a help with siremis-4.2.0. When I try to login the the Siremis, it shows a 404 Not found error message as follow. Not Found The requested URL /siremis/system/general_default was not found on this server. ------------------------------ *Chathura Senanayake* Associate Software Engineer (DA) hSenid Mobile Solutions *Head Office* (Singapore)*P*: +65 65 332 140*M*: *F*: +65 62 910 023 *R&D* (Sri Lanka)*P*: +94 11 268 3751*M*: +94 71 757 9646*F*: +94 11 268 3951 <http://www.… [View More]

1 0

Kamailio Crash
by Marc Soda 17 Jun '15

17 Jun '15

Is it normal for Kamailio to segfault on a duplicate key in the usrloc DB? Jun 15 18:15:23 vproxy2 /usr/sbin/kamailio[13646]: ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Duplicate entry 'uloc-557a96c1-3577-4e5f1' for key 'ruid_idx' Jun 15 18:15:23 vproxy2 /usr/sbin/kamailio[13646]: ERROR: <core> [db_query.c:337]: db_do_update(): error while submitting query Jun 15 18:15:23 vproxy2 /usr/sbin/kamailio[13646]: ERROR: usrloc [ucontact.c:800]: … [View More]

4 4

loose_route to find transport=tcp
by Ryan Kendrick 16 Jun '15

16 Jun '15

We are using Kamailio 4.2.5 as a registrar and proxy between many dispersed end-users of a soft phone app and our calling platform / switch. Until now we have used udp exclusively but are trying to introduce tcp between end-users and Kamailio, leaving udp between Kam and our switch...while maintaining the ability for some end-users to use udp to Kam. With some simple address checks I am able to always send to our switch over udp. If all end-users used tcp I could send everything else tcp, … [View More]but I need to maintain udp support. The specific problem I am having is on a reINVITE such as this one from our platform to the a-leg: INVITE sip:xxxxxx@xxxxxxxxxxxxx:42679;user=phone SIP/2.0 Via: SIP/2.0/UDP xxxxxxxxxxxxx:5060;branch=z9hG4bK218cc8e12ll5035f67INV6a67885312aad Max-Forwards: 35 Route: <sip:xxxxxxxxxxx;lr;r2=on;ftag=daba971c;did=b57.4872;nat=yes> Route: <sip:xxxxxxxxxxx:5070;transport=tcp;lr;r2=on;ftag=daba971c;did=b57.4872;nat=yes> Contact: <sip:xxxxxxxxxx@xxxxxxxxxxxxx:5060> To: "xxxxxx"<sip:xxxxxx@xxxxxxxxxxxxxxxxxxxxxxxxxxx:5070>;tag=daba971c From: <sip:xxxxxxxxxx@xxxxxxxxxxxxxxxxxxxxxxxxxxx :5070>;tag=6a678853-co76461-INS002 Call-ID: MDI4ZmFjNmZhN2Y1NWE2ZTViNTkyZGUwNWE2YzUzYmU CSeq: 7646101 INVITE Allow: INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,INFO,UPDATE Content-Type: application/sdp Date: Mon, 15 Jun 2015 20:10:18 GMT User-Agent: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Content-Length: 262 As you might notice, we have rr:enable_double_rr set: *There are some situations when the server needs to insert two Record-Route header fields instead of one. For example when using two disconnected networks or doing cross-protocol forwarding from UDP->TCP. This parameter enables inserting of 2 Record-Routes. The server will later remove both of them. * and I believe it is necessary to keep this way. Without it Kamailio doesn't even see the reINVITE...the switch probably tries tcp and that's not setup between the two. The invite above is sent to the a-leg over udp but I would expect and need it to be tcp in this case. The reINVITE is part of an existing dialog. We call loose_route() followed by some simple bflag setting and flag checking, t_on_reply(), ... then t_relay(). I do have a functional workaround but would prefer to avoid such manual handling by utilizing built-in functionality properly. # # relay the message # if(route(TEST_TOGW)) { if (!t_relay_to_udp()) { sl_reply_error(); } } else { if ($(hdr(Route)[-1]) =~ "tcp") { if(!t_relay_to_tcp()) { sl_reply_error(); } } else if (!t_relay()) { sl_reply_error(); } } I'm not 100% sure how reliable or fast this will be, but it does work so far in my simple tests. Is loose_route supposed to see and use the transport=tcp but isn't for some reason? It seems like the right thing to do to me. If not, is there anything else I can/should be doing in the tm and/or rr modules to make Kamailio realize it needs to send this message over TCP? If not in those two modules is there some recommended way perhaps via registrar or usrloc etc. to make Kamailio remember/store when a user is connected via TCP and be able to do a quick lookup before sending to them? Anything else I'm missing or not thinking of? Please let me know if I can further explain and rest assured any assistance will be much appreciated!!! [View Less]

1 0

Keep-Alive in dialog "freeing a free fragment"
by Dirk Teurlings - SIGNET B.V. 16 Jun '15

16 Jun '15

Hi, (Kamailio 4.2.3) Working to get dialogs closed and cleaned up nicely I'm looking into the ka_interval and ka_timer parameter of the dialog module. The following is now happening. Scenario: 1. Call gets setup 2. Callee's internet connection drops 3. Call gets terminated (nicely) due to ka_timer/ka_interval 4. Log fills with "freeing a free fragment" after about 10 seconds Digging into this I saw that the dialog is being closed and cleaned properly in step 3. But it fails to remove/… [View More]

2 12

CANCEL request and subsequent 487 response to INVTE configuration problem
by Joao Alves 16 Jun '15

16 Jun '15

Hi, I'm creating a configuration is for a SIP <> HTTP gateway (performing protocol conversion) and thus all SIP messages and responses needs to be generated from the kamailio config file. I'm failing to create the case where the calling user abandons the session, and thus, following the reception of a CANCEL a 200 "OK" needs to be sent to this transaction and later the 487 "Request Terminated" to the SIP INVITE original session. On the traces I see: SIP INVITE (Cseq 1 INVITE) --> … [View More]

2 4

Kamailio license usage
by Alexandru Covalschi 15 Jun '15

15 Jun '15

Maybe it may be an offtopic, but I'm not really into legal issues - so I'm sorry if this message is not fully related to this mailing list. Can I use Kamailio to provide VoIP backend for kind of CRM system in case of SaaS? --- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

3 3

Re: [SR-Users] Kamailio number of LCR rules
by Juha Heinanen 15 Jun '15

15 Jun '15

Henry Fernandes writes: > But we didn¹t want to add hundreds of thousands or millions of extra rules > just to deal with this problem. We didn¹t consider that a good > workaround. OK, I got it. Now priorities choose from equally long prefixes instead of all matching prefixes. I'll take a look at the code to check if the latter could be easily added as an option. -- Juha

1 1

Re: [SR-Users] Kamailio number of LCR rules
by Juha Heinanen 15 Jun '15

15 Jun '15

Henry Fernandes writes: > Let’s say you have the following info in your LCR. > > Prefix, Carrier/Route, Rate > 1306, A, 1.5 > 1306343, A, 1.7 > 1306, B, 1.4 > > If you have phone number 13063431111, the LCR module matches it to the > longest prefix (1306343) and routes the call to Carrier A. However, that > is incorrect. It should match it to Carrier B which is the cheapest. > Carrier B has provided a rate of 1.4 for all calls with prefix 1306. why can't … [View More]

2 1

Kamailio number of LCR rules
by Ali Taher 15 Jun '15

15 Jun '15

Hello, I'm testing LCR module in Kamailio and everything works as expected so far. Before going further , I just want to ask about how much rule in LCR_rule table and target in LCR_rule_target can Kamailio support . We are dealing with hundreds of millions of rules and targets. Kindly advise if Kamailio can support this number of rules. Thanks Ali

3 4

Removing parameters from user part of URI
by Alex Balashov 15 Jun '15

15 Jun '15

Hi, If I have an RURI like this: INVITE sip:4045551212;param=xyz@domain:port SIP/2.0 which transformations can I best string together in order to remove the ';param=xyz' bit and extract just the core user part value (4045551212)? {uri.user} returns '4045551212;param=xyz'. There are numerous transformations to help one access the parameters. What if I want to exclude the parameters? I've already scoured the available transformations, just hoping a second pair of eyes can tell me I'… [View More]

5 19

SIP-over-Websocket Load Balancing
by Murugan Pandian 15 Jun '15

15 Jun '15

HI, how to handle sip-over-websocket load balancing (WebRTC)

4 15

Websocket Load Balancing
by W5RTC 14 Jun '15

14 Jun '15

HI, how to handle SIP-OVER-Websocket loab balancing (WebRTC)

3 2

ASYNC Module
by Aaron Hamstra 13 Jun '15

13 Jun '15

We just updated our development environment from 4.2.2 to 4.2.5 and started noticing the server sending a 500 I'm terribly sorry, server error occurred (1/TM) error back as soon as the async_route block gets called. I have removed everything from our async route other than an xlog statement trying to determine if something in that route block was causing the 500 to occur. It still happens even with only the xlog. If the async_route is not in the config, then the server does not send the … [View More]

2 11

lookup("location") question
by Al S 12 Jun '15

12 Jun '15

Hi, lookup("location") functions extracts username from Request-URI and relay INVITE without any username, causing UAC sends a CANCEL message. Is the function suppose to replace uri with "contact" field in the found entry in "location" table? INVITE uri arrives at Kamailio:Request-Line: INVITE sip:8181111111@example.net:5060 SIP/2.0 INVITE uri leaves Kamilio:Request-Line: INVITE sip:10.10.10.1:5060 SIP/2.0 lookup("location") function finding match and returns 1: $rc=1 entry in "location" … [View More]

2 2

How to prevent multiple registration entries in module ims_registrar_scscf
by jyaim 12 Jun '15

12 Jun '15

Hi all, I have an issue with mobile devices which get a different IP address each time they lose network. The scscf keeps the registration datas from the previous registrations, and forks requests toward all known identities. Is it possible to override the contact address at each register and keep only the last registration address per impi ? Thanks Regards JM

2 1

Problems with http_query(POST)
by Joao Alves 12 Jun '15

12 Jun '15

Hi, I'm finding a problem submitting a HTTP POST using the http_query(). Currently running on kamailio version: 4.1.8 on Debian wheezy. Normally this command has been worked fine, but since the body of the message increased (the POST data size is around 2000 bytes ) I start to get the following problem: 8(49381) ERROR: <core> [pvapi.c:1338]: pv_printf(): no more space for spec value 8(49381) ERROR: <core> [pvapi.c:1347]: pv_printf(): buffer overflow -- increase the buffer size...… [View More]

3 7

Mark CANCEL of one fork when another answers the call - old Kamailio
by Sebastian Damm 11 Jun '15

11 Jun '15

Hi, I'm looking for an option to mark CANCELs which are generated locally by Kamailio after receiving a 200 OK for another fork of the same call. In the tm module documentation I found the option local_cancel_reason which enables this. This option is available (and turned on by default) in newer Kamailios. But we have a legacy system still running 1.5 (and we don't want to upgrade it anymore, it will be obsolete pretty soon), which doesn't have this option yet. Is there a possibility to … [View More]

2 1

Kamailio LCR module memory concern
by Ali Taher 11 Jun '15

11 Jun '15

Hello, I'm using LCR module where I have 44 million rules and 13 million rule targets (not all rules have destinations). Noting that I'm running Ubuntu on virtual machine with 8GB allocated memory. When I'm setting lcr_rule_hash_size parameter to 268435456 (2 power 28) I got the following error : "no memory for rules hash table" in the log , noting that when I run ipcs -lm command I got max total shared memory shared memory (kbytes) : 8388608. When I'm setting lcr_rule_hash_size … [View More]

5 24

Kamailio v4.3.0 Released - new major version is out
by Daniel-Constantin Mierla 10 Jun '15

10 Jun '15

Kamailio v4.3.0 is out – a new major release, bringing more features, flexibility and improvements. You can read detailed release notes at: * http://www.kamailio.org/w/kamailio-v4-3-0-release-notes/ Many thanks to all developers and community members that made possible this release. Enjoy Kamailio v4.2.0! Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Releasing Kamailio v4.3.0
by Daniel-Constantin Mierla 10 Jun '15

10 Jun '15

Hello, I am considering to release next major version of Kamailio (v4.3.0) next week, on Wednesday (June 10) or Thursday (June 11). The pool of things to fix is minor, Victor already updated deb packaging for 4.3, left to do: add docs for 4.3 series in wiki, prepare RPM packaging and build proper 'what is new' list of features. Testing didn't reveal new issues for me in the recent past as I run in two servers with live traffic. If you have issues with 4.3 branch, be sure you report them on … [View More]

2 4

several uac_replace_from in one dialog
by Никитенко Виталий 10 Jun '15

10 Jun '15

Hi! Making calls via different trunks through kamailio for simply so uac_replace_from ("sip:regname@ipaddress"); if (! t_relay ()) { uac_replace_from ("sip:regname2@ipaddress"); t_relay () } exit and run tcpdump i see in fisrt INVITE From: "testname" <sip: regname @ ipaddress>; tag = as21aea6e0 in second INVITE From: "testname" <sip: regname @ ipaddress sipregname2 @ ipaddress>; tag = as21aea6e0 and in the log file EROOR: can not parse From URI, and … [View More]

2 1

kamcmd permissions problem
by Uri Shacked 10 Jun '15

10 Jun '15

Hi, I am using exec_avp() command from kamailio. The command execute a shell script that runs kamctl and kamcmd commands. kamailio runs with user 'kamailio' and group 'kamailio' (defaults). There is not problem with the kamctl commands. But, the kamcmd commands fails due to permissions issues. Any ideas? Cheers, Uri

2 1

403 not relaying
by jaflong jaflong 09 Jun '15

09 Jun '15

Hi, I am getting a 403 not relaying response. This is the part of the config How would I print the value of var myself, from_uri and uri # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; }

2 1

IP fragment
by Tuan Viet Nguyen 09 Jun '15

09 Jun '15

Hello, I would like to know if Kamailio handles the case where we receive a big SIP message fragmented in IP layer? Thanks,

2 2

Testing RPMs for v4.3.0
by Daniel-Constantin Mierla 09 Jun '15

09 Jun '15

Hello, in preparation for releasing v4.3.0 next week, I updated the specs for building RPMs from branch 4.3. However, I am not able to test the results, just made sure the build is ok. Packages are available at: - https://build.opensuse.org/package/show/home:kamailio:v4.3.x-rpms/kamailio43 I hope people here using RPMs will do some tests and provide feedback, interested mainly in: - it installs ok - after install, it starts ok with default configuration file - fifo and unix sockets are … [View More]

2 4

Need information regarding kamilio setup to support IPSec
by Priyaranjan Nayak 09 Jun '15

09 Jun '15

Hi All, I have a ims client endpoint supporting rfc 3329(IPSec).Now I am sending register message to kamailio server with Security-Client header and not getting any Security-Server header in response. Could you please tell me below queries - Whether kamailio server supporting rfc 3329 (IPSec) or not ? - If yes,how can we setup kamailio server to support Security-Client,Security-Server and Security-varify(as per rfc 3329) header ? Thanks Priyaranjan

3 3

Private IP in SDP packet headers
by Alex 08 Jun '15

08 Jun '15

Hello! Please help to fix problem with sdp headers UAC Inet -> (X.X.X.X) Kamailio (192.168.30.250) -> Asterisk (192.168.30.2) When i call from UAC to 9002 i received INVITE/SDP from kamailio SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.52:27080 ;received=10.10.101.50;branch=z9hG4bK-d8754z-027c786dac17bf68-1---d8754z-;rport=27080 Record-Route: <sip :192.168.30.2;line=sr-mYtaP6eErk-dx6VfrLzfr6BaPGj0OHFfPYd0OHFfPYIQpHmFr9mQPKDEx9VlvZ8QO4ttma**> Record-Route: <sip:X.… [View More]

2 1

Need to add extra header in 200 OK message by using kamailio.cfg file
by Priyaranjan Nayak 08 Jun '15

08 Jun '15

Hi All, I wanted to send a extra header(i.e. Security-Server ) in the 200 OK from kamailio server. Could you please suggest me how can I add extra header in 200 OK message by using kamailio.cfg file ? Thanks Priyaranjan

3 4

msilo storage of message id
by Shouvanik Chakrabarti 07 Jun '15

07 Jun '15

Hello. We have been using the msilo module to handle offline SIP messaging. I have noticed that the m_store function ends up storing all the records with the default message id which is zero. However m_dump uses this id to figure which messages have already been sent. Thus on calling m_dump on registration, no messages are dumped. We simply get a 'message already sent' debug log. Is there a way around this? Any help would be deeply appreciated. Thanks, Shouvanik.

2 2

Kamailio second contact header
by Ali Taher 05 Jun '15

05 Jun '15

Hello, I'm trying to build new contact header that will be sent from Kamailio as below : load_gws(1, $rU, $fu); append_to_reply("Contact:"); while (next_gw()) { append_to_reply("$ru"); } append_to_reply("\r\n"); sl_send_reply("300","Multiple Choices"); exit; yet I'm getting … [View More]

2 12

Misc Radius can't parse sip-avps?
by Yasin CANER 05 Jun '15

05 Jun '15

Hello all; i am working on misc_radius modulü. i configured system like below. and when i try to write debug , it gives <null> Could you take a look what i am doing wrong Thanks -----FREERADIUS----- 101(a)192.168.0.188 Auth-Type := Accept, Service-Type == "SIP-Caller-AVPs" Sip-Avp = "#3#1" --------------------------- -----------Kamailio.cfg modparam("misc_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("misc_radius", "group_service_type", 12) … [View More]

3 6

Kamailio fails to start if cannot connect to MySQL
by Al S 05 Jun '15

05 Jun '15

Hi, We have verified if MySQL server is offline when Kamailio is starting, Kamailio fails to start correctly.Is this a bug? Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: db_mysql [km_my_con.c:109]: driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)Jun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: <core> [db.c:320]: could not add connection to the poolJun 4 10:53:22 ape /usr/sbin/kamailio[10630]: ERROR: usrloc [dlist.c:518]: … [View More]

3 2

Private IP in SDP packet headers
by Alex 05 Jun '15

05 Jun '15

Hello! Please help to fix problem with sdp headers UAC Inet -> (X.X.X.X) Kamailio (192.168.30.250) -> Asterisk (192.168.30.2) When i call from UAC to 9002 i received INVITE/SDP from kamailio SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.52:27080 ;received=10.10.101.50;branch=z9hG4bK-d8754z-027c786dac17bf68-1---d8754z-;rport=27080 Record-Route: <sip:192.168.30.2;line=sr-mYtaP6eErk-dx6VfrLzfr6BaPGj0OHFfPYd0OHFfPYIQpHmFr9mQPKDEx9VlvZ8QO4ttma**> Record-Route: <sip:X.X.… [View More]

2 1

How should a PBX behave when a user dials a DID configured for the same or another tenant on that PBX?
by Antonio Gómez Soto 04 Jun '15

04 Jun '15

Hello, This is question on PBX behavior, what is the right thing to do, and how do PBX's generally behave. If a user on a phone, dials a number, which happens to be configured on the same phone system (for example another tenant), there are two options: 1. The PBX notices this, and directly connects the phone to the DID on that system 2. The PBX sends the call out on the SIP trunk, and the provider-routing sends the call back as an incoming call. What are the pros and cons of … [View More]

2 1

Getting 404 From Kamailio for PRACK
by Austin Einter 04 Jun '15

04 Jun '15

Hi All I am trying ti implement a IMS client. For testing I am using Kamailio proxy. During call setup, I get 404 for Prack message. Whats going wrong not able to figure out. Here is the Kamailio log below, can somebody help me too find whats wrong her. … [View More] *11(25376) DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl)11(25376) DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.1.195, 192.168.1.195, 0)11(25376) DEBUG: <core> [tcp_main.c:2281]: tcpconn_send_put(): tcp_send: send from reader (25376 (11)), reusing fd11(25376) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...11(25376) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fe2ebd05390 n=386 fd=511(25376) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=SIP/2.0 200 OKVia: SIP/2.0/TCP 192.168.1.195:40611;branch=z9hG4bK1186661565From: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1307796831To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=25fbdd2b0c9b93b0791296269f5ae411.38a0Call-ID: 835380265(a)192.168.1.195 <835380265(a)192.168.1.195>CSeq: 2 REGISTERContact: <sip:linux_ua_1@192.168.1.195:40611;transport=tcp>;expires=3600Server: kamailio (4.2.3 (x86_64/linux))Content-Length: 011(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)11(25376) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up11(25376) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa33180, 5, 2, 0x7fe2ebd05390), fd_no=111(25376) DEBUG: <core> [tcp_read.c:1362]: tcp_read_req(): tcp_read_req: content-length= 011(25376) DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request:11(25376) DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <SUBSCRIBE>11(25376) DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>11(25376) DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0>11(25376) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1577674881>; state=1611(25376) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=511(25376) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=211(25376) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via11(25376) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg...11(25376) DEBUG: <core> [receive.c:197]: receive_msg(): preparing to run routing scripts...11(25376) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=1011(25376) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [28]; uri=[sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>] 11(25376) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>]11(25376) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <SUBSCRIBE>11(25376) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 11(25376) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=011(25376) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header11(25376) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=133567903511(25376) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2911(25376) DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 111(25376) DEBUG: siputils [checks.c:103]: has_totag(): no totag11(25376) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=(nil)11(25376) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=34123, isACK=011(25376) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed11(25376) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found11(25376) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil)11(25376) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]11(25376) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4060 (advertise 0) matches port 506011(25376) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]11(25376) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4060 (advertise 0) matches port 506011(25376) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]11(25376) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4090 (advertise 0) matches port 506011(25376) DEBUG: registrar [lookup.c:203]: lookup_helper(): contact for [linux_ua_1] cannot handle the SIP method11(25376) DEBUG: registrar [lookup.c:211]: lookup_helper(): 'linux_ua_1' has no valid contact in usrloc11(25376) DEBUG: tm [t_lookup.c:1373]: t_newtran(): DEBUG: t_newtran: msg id=2 , global msg id=2 , T on entrance=(nil)11(25376) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=34123, isACK=011(25376) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed11(25376) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found11(25376) DEBUG: tm [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: trans=0x7fe2ebd10e68, callback type 1, id 0 entered11(25376) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): DEBUG: MD5 calculated: c17c6f2bd5d60787072aef8ffcf5bfe611(25376) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T start=0x7fe2ebd10e6811(25376) DEBUG: tm [t_lookup.c:1144]: t_check_msg(): DEBUG: t_check_msg: T already found!11(25376) DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.1.195, 192.168.1.195, 0)11(25376) DEBUG: <core> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called11(25376) DEBUG: tm [t_reply.c:1653]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset11(25376) DEBUG: <core> [tcp_main.c:2281]: tcpconn_send_put(): tcp_send: send from reader (25376 (11)), reusing fd11(25376) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...11(25376) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fe2ebd05390 n=334 fd=511(25376) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=SIP/2.0 405 Method Not AllowedVia: SIP/2.0/TCP 192.168.1.195:40611;branch=z9hG4bK1577674881From: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1335679035To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=ff272440259f71af2c767e7942717037-95d5Call-ID: 1397060040(a)192.168.1.195 <1397060040(a)192.168.1.195>CSeq: 2 SUBSCRIBEServer: kamailio (4.2.3 (x86_64/linux))Content-Length: 011(25376) DEBUG: tm [t_reply.c:728]: _reply_light(): DEBUG: reply sent out. buf=0x7fe30fea65c0: SIP/2.0 405 Method N..., shmem=0x7fe2ebd135a8: SIP/2.0 405 Method N11(25376) DEBUG: tm [t_reply.c:738]: _reply_light(): DEBUG: _reply_light: finished11(25376) DEBUG: sl [sl.c:288]: send_reply(): reply in stateful mode (tm)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)11(25376) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)11(25376) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up 9(25374) DEBUG: websocket [ws_conn.c:459]: wsconn_get_list(): wsconn_get_list 9(25374) DEBUG: websocket [ws_conn.c:503]: wsconn_get_list(): wsconn_get_list returns list [(nil)] with [0] members10(25375) DEBUG: <core> [tcp_read.c:1362]: tcp_read_req(): tcp_read_req: content-length= 35910(25375) DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request:10(25375) DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <INVITE>10(25375) DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>10(25375) DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0>10(25375) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1970975121>; state=1610(25375) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=510(25375) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=210(25375) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via10(25375) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg...10(25375) DEBUG: <core> [receive.c:197]: receive_msg(): preparing to run routing scripts...10(25375) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=1010(25375) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [28]; uri=[sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>] 10(25375) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>]10(25375) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <INVITE>10(25375) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 10(25375) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=35910(25375) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header10(25375) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=60426366410(25375) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2910(25375) DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 110(25375) DEBUG: siputils [checks.c:103]: has_totag(): no totag10(25375) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=3 global id=2 T start=0xffffffffffffffff10(25375) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=12870, isACK=010(25375) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed10(25375) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found10(25375) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=3 global id=3 T end=(nil)10(25375) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]10(25375) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4060 (advertise 0) matches port 506010(25375) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]10(25375) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4060 (advertise 0) matches port 506010(25375) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]10(25375) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4090 (advertise 0) matches port 506010(25375) DEBUG: registrar [lookup.c:198]: lookup_helper(): contact for [linux_ua_1] found by address10(25375) DEBUG: tm [t_lookup.c:1373]: t_newtran(): DEBUG: t_newtran: msg id=3 , global msg id=3 , T on entrance=(nil)10(25375) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=12870, isACK=010(25375) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed10(25375) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found10(25375) DEBUG: tm [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: trans=0x7fe2ebd13848, callback type 1, id 0 entered10(25375) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): DEBUG: MD5 calculated: c4c3d26baa62dea619271f186d6344fc10(25375) DEBUG: tm [t_funcs.c:347]: t_relay_to(): SER: new INVITE10(25375) DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.1.195, 192.168.1.195, 0)10(25375) DEBUG: <core> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called10(25375) DEBUG: <core> [tcp_main.c:2281]: tcpconn_send_put(): tcp_send: send from reader (25375 (10)), reusing fd10(25375) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...10(25375) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fe2ebd096b0 n=307 fd=510(25375) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=SIP/2.0 100 trying -- your call is important to usVia: SIP/2.0/TCP 192.168.1.195:19009;branch=z9hG4bK1970975121From: <sip:linux_ua_0@192.168.1.195 <sip%3Alinux_ua_0(a)192.168.1.195>>;tag=604263664To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>Call-ID: 734015646(a)192.168.1.195 <734015646(a)192.168.1.195>CSeq: 2 INVITEServer: kamailio (4.2.3 (x86_64/linux))Content-Length: 010(25375) DEBUG: tm [t_reply.c:728]: _reply_light(): DEBUG: reply sent out. buf=0x7fe30fea6968: SIP/2.0 100 trying -..., shmem=0x7fe2ebd163f0: SIP/2.0 100 trying -10(25375) DEBUG: tm [t_reply.c:738]: _reply_light(): DEBUG: _reply_light: finished10(25375) DEBUG: <script>: new branch [0] to sip:linux_ua_1@192.168.1.195:40611;transport=tcp10(25375) DEBUG: <core> [msg_translator.c:2893]: create_via_hf(): create_via_hf: id added: <;i=2>, rcv proto=210(25375) DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.1.195, 192.168.1.195, 0)10(25375) DEBUG: <core> [tcp_main.c:1818]: tcp_send(): tcp_send: no open tcp connection found, opening new one10(25375) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 192.168.1.19510(25375) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 40611, type 210(25375) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 3453:3998:0, 310(25375) INFO: <core> [tcp_main.c:2753]: tcpconn_1st_send(): quick connect for 0x7fe2ebd1703010(25375) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)14(25379) DEBUG: <core> [tcp_main.c:3565]: handle_ser_child(): handle_ser_child: read response= 7fe2ebd17030, 6, fd 28 from 10 (25375)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)14(25379) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9eeee0, 28, 2, 0x7fe2ebd17030), fd_no=1910(25375) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up14(25379) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9eeee0, 28, -1, 0x0) fd_no=20 called14(25379) DEBUG: <core> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 114(25379) DEBUG: <core> [tcp_main.c:3902]: send2child(): selected tcp worker 2 12(25377) for activity on [tcp:192.168.1.195:4060 <http://192.168.1.195:4060>], 0x7fe2ebd1703012(25377) DEBUG: <core> [tcp_read.c:1554]: handle_io(): received n=8 con=0x7fe2ebd17030, fd=512(25377) DEBUG: <core> [tcp_read.c:1362]: tcp_read_req(): tcp_read_req: content-length= 38812(25377) DEBUG: <core> [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status):12(25377) DEBUG: <core> [parser/msg_parser.c:635]: parse_msg(): version: <SIP/2.0>12(25377) DEBUG: <core> [parser/msg_parser.c:637]: parse_msg(): status: <183>12(25377) DEBUG: <core> [parser/msg_parser.c:639]: parse_msg(): reason: <Session Progress>12(25377) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK6423.c4c3d26baa62dea619271f186d6344fc.0>; state=612(25377) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 236, <i> = <2>; state=1612(25377) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=512(25377) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=212(25377) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via12(25377) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg...12(25377) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=0 T start=0xffffffffffffffff12(25377) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1970975121>; state=1612(25377) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=512(25377) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=6212(25377) DEBUG: <core> [parser/msg_parser.c:526]: parse_headers(): parse_headers: this is the second via12(25377) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=165643220412(25377) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2912(25377) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [43]; uri=[sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>] 12(25377) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>]12(25377) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <INVITE>12(25377) DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 12870 label 0 branch 012(25377) DEBUG: tm [t_lookup.c:1004]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0x7fe2ebd13848)!12(25377) DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fe2ebd13848, callback type 2, id 0 entered12(25377) DEBUG: acc [acc_logic.c:644]: tmcb_func(): acc callback called for t(0x7fe2ebd13848) event type 2, reply code 18312(25377) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=1 global id=1 T end=0x7fe2ebd1384812(25377) DEBUG: tm [t_reply.c:2200]: reply_received(): DEBUG: reply_received: org. status uas=100, uac[0]=0 local=0 is_invite=1)12(25377) DEBUG: <script>: incoming reply12(25377) DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): ->>>>>>>>> T_code=100, new_code=18312(25377) DEBUG: tm [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=012(25377) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=38812(25377) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header12(25377) DEBUG: <core> [msg_translator.c:2278]: generate_res_buf_from_sip_res(): old size: 948, new size: 85312(25377) DEBUG: <core> [msg_translator.c:2296]: generate_res_buf_from_sip_res(): copied size: orig:125, new: 30, rest: 823 msg=SIP/2.0 183 Session ProgressVia: SIP/2.0/TCP 192.168.1.195:19009;branch=z9hG4bK1970975121Record-Route: <sip:192.168.1.195:4060;transport=tcp;lr>From: <sip:linux_ua_0@192.168.1.195 <sip%3Alinux_ua_0(a)192.168.1.195>>;tag=604263664To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1656432204Call-ID: 734015646(a)192.168.1.195 <734015646(a)192.168.1.195>CSeq: 2 INVITEContact: <sip:linux_ua_1@192.168.1.195:40611;transport=TCP>Content-Type: application/sdpUser-Agent: Linux 64 US-UA 1.0.1Require: 100relRSeq: 1Content-Length: 388v=0o=- 0 0 IN IP4 192.168.1.195s=IMS_Callc=IN IP4 192.168.1.195t=0 0m=audio 21720 RTP/AVP 99 0 8 101 b=AS:64a=curr:qos remote nonea=curr:qos local nonea=des:qos mandatory remote sendrecva=conf:qos remote sendrecva=des:qos mandatory local sendrecva=rtpmap:101 telephone-event/8000a=fmtp:101 0-15a=rtpmap:99 AMR/8000a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/800012(25377) DEBUG: <core> [tcp_main.c:2297]: tcpconn_send_put(): tcp_send: tcp connection found (0x7fe2ebd096b0), acquiring fd12(25377) DEBUG: <core> [tcp_main.c:2307]: tcpconn_send_put(): tcp_send, c= 0x7fe2ebd096b0, n=1614(25379) DEBUG: <core> [tcp_main.c:3565]: handle_ser_child(): handle_ser_child: read response= 7fe2ebd096b0, 2, fd -1 from 12 (25377)12(25377) DEBUG: <core> [tcp_main.c:2337]: tcpconn_send_put(): tcp_send: after receive_fd: c= 0x7fe2ebd096b0 n=8 fd=812(25377) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...12(25377) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fe2ebd096b0 n=853 fd=812(25377) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=SIP/2.0 183 Session ProgressVia: SIP/2.0/TCP 192.168.1.195:19009;branch=z9hG4bK1970975121Record-Route: <sip:192.168.1.195:4060;transport=tcp;lr>From: <sip:linux_ua_0@192.168.1.195 <sip%3Alinux_ua_0(a)192.168.1.195>>;tag=604263664To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1656432204Call-ID: 734015646(a)192.168.1.195 <734015646(a)192.168.1.195>CSeq: 2 INVITEContact: <sip:linux_ua_1@192.168.1.195:40611;transport=TCP>Content-Type: application/sdpUser-Agent: Linux 64 US-UA 1.0.1Require: 100relRSeq: 1Content-Length: 388v=0o=- 0 0 IN IP4 192.168.1.195s=IMS_Callc=IN IP4 192.168.1.195t=0 0m=audio 21720 RTP/AVP 99 0 8 101 b=AS:64a=curr:qos remote nonea=curr:qos local nonea=des:qos mandatory remote sendrecva=conf:qos remote sendrecva=des:qos mandatory local sendrecva=rtpmap:101 telephone-event/8000a=fmtp:101 0-15a=rtpmap:99 AMR/8000a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/800012(25377) DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fe2ebd13848, callback type 512, id 0 entered12(25377) DEBUG: acc [acc_logic.c:644]: tmcb_func(): acc callback called for t(0x7fe2ebd13848) event type 512, reply code 18312(25377) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)12(25377) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)12(25377) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)12(25377) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)12(25377) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)12(25377) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)12(25377) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)12(25377) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up12(25377) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa33180, 5, 2, 0x7fe2ebd17030), fd_no=110(25375) DEBUG: <core> [tcp_read.c:1362]: tcp_read_req(): tcp_read_req: content-length= 39210(25375) DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request:10(25375) DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <PRACK>10(25375) DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:linux_ua_1@192.168.1.195:40611;transport=TCP>10(25375) DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0>10(25375) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1576634775>; state=1610(25375) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=510(25375) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=210(25375) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via10(25375) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg...10(25375) DEBUG: <core> [receive.c:197]: receive_msg(): preparing to run routing scripts...10(25375) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=165643220410(25375) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2910(25375) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [43]; uri=[sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>] 10(25375) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>]10(25375) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <3> <PRACK>10(25375) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 10(25375) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=39210(25375) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header10(25375) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=60426366410(25375) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2910(25375) DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 110(25375) DEBUG: siputils [checks.c:106]: has_totag(): totag found10(25375) DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No10(25375) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]10(25375) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4060 (advertise 0) matches port 4061110(25375) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]10(25375) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4060 (advertise 0) matches port 4061110(25375) DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 13==13 && [192.168.1.195] == [192.168.1.195]10(25375) DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 4090 (advertise 0) matches port 4061110(25375) DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:192.168.1.195:4060;transport=tcp;lr' is loose router10(25375) DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:192.168.1.195:4060;transport=tcp;lr'10(25375) DEBUG: tm [t_lookup.c:1373]: t_newtran(): DEBUG: t_newtran: msg id=4 , global msg id=3 , T on entrance=0xffffffffffffffff10(25375) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=12871, isACK=010(25375) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed10(25375) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found10(25375) DEBUG: tm [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: trans=0x7fe2ebd1b780, callback type 1, id 0 entered10(25375) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): DEBUG: MD5 calculated: 0dd1edaf37f3874c5176befe76ed5b3e10(25375) DEBUG: <core> [msg_translator.c:2893]: create_via_hf(): create_via_hf: id added: <;i=2>, rcv proto=210(25375) DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.1.195, 192.168.1.195, 0)10(25375) DEBUG: <core> [tcp_main.c:1818]: tcp_send(): tcp_send: no open tcp connection found, opening new one10(25375) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 192.168.1.19510(25375) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 4060, type 210(25375) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 3360:0:0, 410(25375) INFO: <core> [tcp_main.c:2753]: tcpconn_1st_send(): quick connect for 0x7fe2ebd1e5c010(25375) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed14(25379) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 192.168.1.19510(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)14(25379) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 19785, type 210(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)14(25379) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 3888:3539:528, 510(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)10(25375) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up14(25379) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9eeee0, 29, 2, 0x7fe2ebd228e0), fd_no=1914(25379) DEBUG: <core> [tcp_main.c:3565]: handle_ser_child(): handle_ser_child: read response= 7fe2ebd1e5c0, 6, fd 30 from 10 (25375)14(25379) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9eeee0, 30, 2, 0x7fe2ebd1e5c0), fd_no=2014(25379) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9eeee0, 29, -1, 0x0) fd_no=21 called14(25379) DEBUG: <core> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 114(25379) DEBUG: <core> [tcp_main.c:3902]: send2child(): selected tcp worker 3 13(25378) for activity on [tcp:192.168.1.195:4060 <http://192.168.1.195:4060>], 0x7fe2ebd228e013(25378) DEBUG: <core> [tcp_read.c:1554]: handle_io(): received n=8 con=0x7fe2ebd228e0, fd=513(25378) DEBUG: <core> [tcp_read.c:1362]: tcp_read_req(): tcp_read_req: content-length= 39213(25378) DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request:13(25378) DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <PRACK>13(25378) DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:192.168.1.195:4060;transport=tcp;lr>13(25378) DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0>13(25378) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK7423.0dd1edaf37f3874c5176befe76ed5b3e.0>; state=613(25378) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 236, <i> = <2>; state=1613(25378) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=513(25378) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=213(25378) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via13(25378) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg...13(25378) DEBUG: <core> [receive.c:197]: receive_msg(): preparing to run routing scripts...13(25378) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1576634775>; state=1613(25378) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=513(25378) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=10013(25378) DEBUG: <core> [parser/msg_parser.c:526]: parse_headers(): parse_headers: this is the second via13(25378) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=165643220413(25378) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2913(25378) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [43]; uri=[sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>] 13(25378) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>]13(25378) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <3> <PRACK>13(25378) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 69 13(25378) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=39213(25378) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header13(25378) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=60426366413(25378) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2913(25378) DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 113(25378) DEBUG: siputils [checks.c:106]: has_totag(): totag found13(25378) DEBUG: rr [loose.c:113]: find_first_route(): No Route headers found13(25378) DEBUG: rr [loose.c:929]: loose_route(): There is no Route HF13(25378) DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(192.168.1.195, 192.168.1.195, 0)13(25378) DEBUG: <core> [tcp_main.c:2281]: tcpconn_send_put(): tcp_send: send from reader (25378 (13)), reusing fd13(25378) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...13(25378) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fe2ebd228e0 n=386 fd=514(25379) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9eeee0, 30, -1, 0x0) fd_no=20 called13(25378) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=SIP/2.0 404 Not hereVia: SIP/2.0/TCP 192.168.1.195:4060;branch=z9hG4bK7423.0dd1edaf37f3874c5176befe76ed5b3e.0;i=2Via: SIP/2.0/TCP 192.168.1.195:19009;branch=z9hG4bK1576634775From: <sip:linux_ua_0@192.168.1.195 <sip%3Alinux_ua_0(a)192.168.1.195>>;tag=604263664To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1656432204Call-ID: 734015646(a)192.168.1.195 <734015646(a)192.168.1.195>CSeq: 3 PRACKServer: kamailio (4.2.3 (x86_64/linux))Content-Length: 014(25379) DEBUG: <core> [tcp_main.c:4219]: handle_tcpconn_ev(): tcp: DBG: sending to child, events 114(25379) DEBUG: <core> [tcp_main.c:3898]: send2child(): WARNING: send2child: no free tcp receiver, connection passed to the least busy one (1)14(25379) DEBUG: <core> [tcp_main.c:3902]: send2child(): selected tcp worker 0 10(25375) for activity on [tcp:192.168.1.195:4060 <http://192.168.1.195:4060>], 0x7fe2ebd1e5c013(25378) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)13(25378) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [tcp_read.c:1554]: handle_io(): received n=8 con=0x7fe2ebd1e5c0, fd=1013(25378) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)13(25378) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)13(25378) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)13(25378) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [tcp_read.c:1362]: tcp_read_req(): tcp_read_req: content-length= 013(25378) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)10(25375) DEBUG: <core> [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status):13(25378) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up10(25375) DEBUG: <core> [parser/msg_parser.c:635]: parse_msg(): version: <SIP/2.0>10(25375) DEBUG: <core> [parser/msg_parser.c:637]: parse_msg(): status: <404>10(25375) DEBUG: <core> [parser/msg_parser.c:639]: parse_msg(): reason: <Not here>10(25375) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK7423.0dd1edaf37f3874c5176befe76ed5b3e.0>; state=613(25378) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa33180, 5, 2, 0x7fe2ebd228e0), fd_no=110(25375) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 236, <i> = <2>; state=1610(25375) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=510(25375) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=210(25375) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via10(25375) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg...10(25375) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=5 global id=4 T start=0xffffffffffffffff10(25375) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK1576634775>; state=1610(25375) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=510(25375) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=6210(25375) DEBUG: <core> [parser/msg_parser.c:526]: parse_headers(): parse_headers: this is the second via10(25375) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=165643220410(25375) DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=2910(25375) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [43]; uri=[sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>] 10(25375) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [<sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>]10(25375) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <3> <PRACK>10(25375) DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 12871 label 0 branch 010(25375) DEBUG: tm [t_lookup.c:1004]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0x7fe2ebd1b780)!10(25375) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=5 global id=5 T end=0x7fe2ebd1b78010(25375) DEBUG: tm [t_reply.c:2200]: reply_received(): DEBUG: reply_received: org. status uas=0, uac[0]=0 local=0 is_invite=0)10(25375) DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=40410(25375) DEBUG: tm [t_reply.c:1812]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=010(25375) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=010(25375) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header10(25375) DEBUG: <core> [msg_translator.c:2278]: generate_res_buf_from_sip_res(): old size: 386, new size: 29110(25375) DEBUG: <core> [msg_translator.c:2296]: generate_res_buf_from_sip_res(): copied size: orig:117, new: 22, rest: 269 msg=SIP/2.0 404 Not hereVia: SIP/2.0/TCP 192.168.1.195:19009;branch=z9hG4bK1576634775From: <sip:linux_ua_0@192.168.1.195 <sip%3Alinux_ua_0(a)192.168.1.195>>;tag=604263664To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1656432204Call-ID: 734015646(a)192.168.1.195 <734015646(a)192.168.1.195>CSeq: 3 PRACKServer: kamailio (4.2.3 (x86_64/linux))Content-Length: 010(25375) DEBUG: <core> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called10(25375) DEBUG: <core> [tcp_main.c:2281]: tcpconn_send_put(): tcp_send: send from reader (25375 (10)), reusing fd10(25375) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending...10(25375) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fe2ebd096b0 n=291 fd=510(25375) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf=SIP/2.0 404 Not hereVia: SIP/2.0/TCP 192.168.1.195:19009;branch=z9hG4bK1576634775From: <sip:linux_ua_0@192.168.1.195 <sip%3Alinux_ua_0(a)192.168.1.195>>;tag=604263664To: <sip:linux_ua_1@192.168.1.195 <sip%3Alinux_ua_1(a)192.168.1.195>>;tag=1656432204Call-ID: 734015646(a)192.168.1.195 <734015646(a)192.168.1.195>CSeq: 3 PRACKServer: kamailio (4.2.3 (x86_64/linux))Content-Length: 010(25375) DEBUG: tm [t_reply.c:1653]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)10(25375) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)10(25375) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up10(25375) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0xa33180, 10, 2, 0x7fe2ebd1e5c0), fd_no=214(25379) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 1314(25379) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 4, pid 25369 (shutting down?)14(25379) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9eeee0, 13, -1, 0x0) fd_no=19 calledroot@Kamal:/usr/local/etc/kamailio# * [View Less]

2 1

Increase Simultaneous Registration
by Austin Einter 04 Jun '15

04 Jun '15

Hi All I am using Kamailio 4.0.4 (x86_64/linux). I wanted to do simultaneous registrations of large number of endpoints. Many times I see only 2048 endpoints registered and for other endpoints Kamailio did not respond for REGISTER message. I am tcp as transport. Now my questions are 1. What are the different configurations available to increase Kamailio performance 2. If I put Kamailio in a Linux 64 Bit, 2GHz, 8GB RAM machine, how much simultaneous and total registrations can be achieved. I … [View More]

2 1

Problem with command kamcmd pkg.stats on Kamailio 4.2.5
by Dao Hai Dang 04 Jun '15

04 Jun '15

Hi, I need help with kamcmd pkg.stats on Kamailio 4.2.5. When I used this command to check kamailio process, I get an entry with no pid and total_size param. I used kamcmd ps and the process error was MI FIFO. Same thing happened when I added snmpstats module, I get process SNMP AgentX with no pid and total_size param. This didn't happen when I use kamailio 4.1.x . Below are logs : [root@localhost ~]# kamcmd pkg.stats { entry: 0 pid: 1532 rank: 0 … [View More]

2 6

Strange core.tcp_list / tls.list output
by Mikko Lehto 04 Jun '15

04 Jun '15

Hi, I noticed thath command core.tcp_list in kamcmd gives output that does not make sense to me: --- kamcmd> core.tcp_list { id: 1 type: TLS state: CONN_OK timeout: 3599 ref_count: 1 src_ip: 192.168.47.132 src_port: 5061 dst_ip: 10.10.235.9 dst_port: 54769 } { id: 2 type: TLS state: CONN_OK timeout: 3599 ref_count: 1 src_ip: 192.168.47.132 src_port: 32854 … [View More]

2 3

Kamailio Contact header read-only
by Ali Taher 04 Jun '15

04 Jun '15

Hello, I'm trying to change contact header in SIP response message by stripping first characters (for testing only) as below : $ct = $(ct{s.strip,25}); But I got below error saying that $ct is read-only: 0(15410) : <core> [cfg.y:3419]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 575, column 5-7: read only pvar in assignment left side ERROR: bad config file (1 errors) The question is how can I change contact header before it's sending … [View More]

2 7

SIP Auth Realm - From domain or Request domain ?
by jay binks 04 Jun '15

04 Jun '15

I have a questions in regards to SIP Auth, and specifically how Asterisk 13 with PJSIP appears to send Invites. It seems that the typical Kamailio config sends the SIP auth challenge with the from domain as the auth realm. however in the case of the Asterisk 13 ( PJSIP ) invite, the from domain is an RFC1918 IP address and I would have to use the domain from the request. What im wanting to know is what the consensus is on where the auth realm comes from. does everyone 100% agree that you send … [View More]

2 1

Fwd: Kamailio start failed
by Gopalakrishnan N 03 Jun '15

03 Jun '15

Hi, I have added the ASTERISK integration in kamailio.cfg, after adding those, am not able to start kamailio service, its getting failed, attached is the script. Any help would be appreciated. Thank you with regards, Gopalkrishnan N. Mob: +91 99404 91346 VoIP call - sip:saigop@gtalk2voip.com

2 4

Need help to configure rtpporyx
by Mir Jee 03 Jun '15

03 Jun '15

Hi! Please help me to configure rtpproxy on centos + kamailio.

2 1

lookup() to fork execution of routing script?
by Andrey Utkin 03 Jun '15

03 Jun '15

Hi! Currently we have the following logic in our Kamailio routing script. On incoming INVITE, we lookup() the location of called party, then we analyse the updated Request-URI ($ru) regarding callee contact protocol: is it websocket-based or not, to distinguish web-based useragents from classic SIP agents and provide RTP profiles interconnection with rtpengine (RTP/SAVPF for web-based, RTP/AVPF for the rest). After that, we relay the mangled INVITE to callee location(s) with t_relay(). The … [View More]

2 2

Kamailio LCR Multiple choices
by Ali Taher 03 Jun '15

03 Jun '15

Hello, I'm using LCR module to send multiple choices. Everything works fine so far , yet I have a problem that last gateway comes first, then gateways are ordered correctly. Below is correct sorting of gateways: First gateway : 192.168.26.4 Second gateway: 192.168.26.1 Third gateway : 192.168.26.6 Below is Invite response I'm getting, as you can see 192.168.26.6 (last gateway) is included as the first gateway , then 192.168.26.4 (first gateway) comes next. Via: SIP/2.0/UDP … [View More]

2 7

delay on "location" table update
by Al S 03 Jun '15

03 Jun '15

Hi, I was wondering if it's normal for "location" table to be updated almost 10 sec after receiving REGISTER. Thanks,Al

2 1

Potential CNXCC bug
by Jay Patel 02 Jun '15

02 Jun '15

I am trying to use cnxcc for credit control . It seems like dialog and cnxcc modules are getting out of sync. For some reason , I see cnxcc.active_clients gets stuck and they never clear up. Interestingly only calls that gets failure 5xx and 4xx from PSTN gateway gets stuck, all successful calls are cleared . I have made sure , I have setflag(DLG_FLAG) 1st line in my routing logic. If you need my routing script, I can share with you . Am I missing anything obvious? As you can see , "… [View More]

1 0

Kamailio LCR rule matching
by Ali Taher 02 Jun '15

02 Jun '15

Hi, I'm using LCR module in Kamailio , where matching of the rule (From-URI in LCR-rule table) is currently based on user part of sip address in From field (highlighted below in blue). While we need to change the identification to be on the otg value sent in the sip address in From field (highlighted below in yellow). INVITE sip:86532917453592@172.16.5.108:5060 <http://sip:86532917453592@172.16.5.108:5060> SIP/2.0 Via: SIP/2.0/UDP 172.16.5.112:5060;branch=… [View More]

3 2

RTPengine+Kamailio, 200 OK without DTLS fingerprint
by Vasiliy Ganchev 02 Jun '15

02 Jun '15

Hello list! Have some difficulties with RTPengine: My test scheme is: UA(WS) -> Kamailio (WS proxy) -> Kamailio (SIP REGISTRAR, proxy) -> ASTERISK (media server) -> UA (SIP) Kamailio (WS) use RTPengine. Kamailio (WS proxy) - 4.2.3 Kamailio (SIP REGISTRAR, proxy) - 4.1.4 RTPengine - 3.3.0.0+0~mr3.8.0.0 I make a test call and have troubles in negotiation between UA(WS) -> Kamailio (WS proxy): UA(WS) -> INVITE -> Kamailio WS ...... rtpengine_manage("trust-address replace-… [View More]

3 8

RFC 6140
by Al S 02 Jun '15

02 Jun '15

Hi, I was wondering if Kamailio support RFC 6140 to register Addresses of Record (AORs) in bulk map to a unique set of contacts. REGISTER sip:kamailio.example.com SIP/2.0 Via: SIP/2.0/UDP 198.51.100.3:5060;branch=z9hG4bKnashds7 Max-Forwards: 70 To: <sip:pbx@kamailio.example.com> From: <sip:pbx@kamailio.example.com>;tag=a23589 Call-ID: 843817637684230@998sdasdh09 CSeq: 1826 REGISTER Proxy-Require: gin Require: gin Supported: path Contact: <sip:198.… [View More]

2 3

next via branch value
by Juha Heinanen 01 Jun '15

01 Jun '15

when kamailio forwards invite request, it adds to it a new via header. for example, incoming invite: SIP/2.0/TCP 192.168.43.192:48089;branch=z9hG4bK4e1ab219cbde6190;rport outgoing invite: SIP/2.0/TCP 192.98.102.10;branch=z9hG4bK27b9.597e97c43da7ddd6be8520b662d616b9.0;i=5 SIP/2.0/TCP 192.168.43.192:48089;received=192.98.102.10;branch=z9hG4bK4e1ab219cbde6190;rport=49582 is it somehow possible to find out in the config script, what will the branch value of the new via header be? if that … [View More]

4 14

Request of advice about TAS for IMS
by dfretes＠ing.una.py 01 Jun '15

01 Jun '15

I am trying to setup a really simple (I hope so) IMS platform, with some basic services (like voicemail, IVR, videoconference), but I'm kind of stuck. I have installed Kamailio IMS on debian and a OpenIMS VM also. But my little problem begins when I try to configure a application server (in this case, a TAS). I have tried with Elastix 3.0 (kamailio+asterisk), asterisk alone, and read some about Restcomm. For Elastix and asterisk, I get stuck trying to setup the trigger point. For … [View More]

2 1

Select a network
by Nelson Migliaro 01 Jun '15

01 Jun '15

Hello everybody, I need to apply a specific configuration to softphones registering from a specific network range. Is there something like:

2 2

Invalid SDP line (no '=' delimiter) error !
by Badri Ranganathan 01 Jun '15

01 Jun '15

Hi all, I am answering a SIP call made to my softphone. The softphone rings and also sends a 200 OK correctly. But the other end that made the call is seeing a failure in the SDP of the 200 OK packet. This error is seen in SDP header => Invalid SDP line (no '=' delimiter) error w.r.t w_frame4_public_ip.pcap It looks like the failure as seen in wireshark is because line "audio 5000 RTP/AVP 8 101" should really be "m= audio 5000 RTP/AVP 8 101" so it doesn't see the '=' delimiter. But if … [View More]

2 1

Re: [SR-Users] Regarding presence conference
by Daniel-Constantin Mierla 01 Jun '15

01 Jun '15

Hello, the conference mixer is supposed to send PUBLISH requests with information about who is in the conference room, who is speaking at that moment and so. That is not the job of the presence_conference module. Eventually, that could be a pua_conference module that has to be implemented. The presence_conference module was implemented as part of GSoC and the PUA was supposed to be inside SEMS, but the other project failed. If you want to get it all working, you have to implement the PUA … [View More]

1 0

Forward register to multiple Asterisk
by Nelson Migliaro 01 Jun '15

01 Jun '15

Hello, I am trying to forward the register to multiple Asterisk using Kamailio. The basic Idea is: Softphone A---->Kamailio-----> Asterisk 1 ------> Asterisk 2. I follow Asipto howto http://lylix.net/kamailio, but the problem I see in my case, is that registration IP in Asterisk is Kamailio´s IP. This causes calls going from kamailio to asterisk and then back to kamailio. In my scenario, I need that softphone A IP appeard in Asterisk realtime … [View More]

2 1

Kamailio , RTPProxy and NAT
by Mir Jee 01 Jun '15

01 Jun '15

HI! I need help to configure RTPProxy. I have working Kamailio on Centos 6.5, On LAN everything is working fine. Now I want my other users to connect using 3G or any other network. Please help me with that. Statis Public IP (DSL Modem) ----- Proxy Box with 2 Lan cards --- 192.168.2.0 and 192.168.0.0 (Lan Side)

2 1

Kamailio 300 Multiple choices
by Ali Taher 29 May '15

29 May '15

Hello, We need to integrate Kamailio with an exchange switch in order to have routing decision. Kamailio must send to the switch the list of available gateways in the contact tag of SIP response as shown in the below example: SIP/2.0 300 Multiple choices Via: SIP/2.0/UDP 172.16.5.112:5060;branch=z9hG4bK1sansay9906915rdb2243 Via: SIP/2.0/UDP 216.53.4.5:5060;branch=z9hG4bK_1852370774_4741_1 To: <sip:86532917453592@69.41.186.186:5060 <http://sip:86532917453592@69.41.186.186:5060&… [View More]

2 7

"Multiple Phone Numbers" registration
by Al S 29 May '15

29 May '15

Hi, Does Kamilio have a predefined module to support "Multiple Phone Numbers" registration with a single Registration?I am trying to register multiple numbers on behalf of IP-PBXs. Thanks,Al

2 3

hash table not loading
by Olli Attila 29 May '15

29 May '15

Hello, I am trying to load a test hash table on kamailio startup but I keep getting the following error with kamctl after i restart Kamailio and try to list all the tables in memory: kamcmd> htable.listTables error: 500 - No htables I have the following configured in kamailio.cfg: # ---- loading the htable module loadmodule "htable.so" # ----- htable params ----- modparam("htable", "htable", "abc=>size=8;autoexpire=0;dbtable=htable;") modparam("htable", "db_url", DBURL) modparam("… [View More]

3 8

Kamailio V4.2.5 append prefix to Request Uri problem.
by Yasin CANER 29 May '15

29 May '15

Hello; i try to append prefix to $rU like below in Kamailio V4.2.5 . i get error even if i set string value. it works only when i append like that $rU="3002"+$rU; --------- 1 test------------ $var(prefix)=$avp(s:69); $rU=$var(prefix)+$rU; -FAILED ---------2 test ------------ $rU=$avp(s:69)+$rU; -FAILED ------- 3 test ------------ $rU=$avp(i:69)+$rU; -FAILED -------ERROR--------- May 29 12:06:57 group1-imslab11 /usr/local/sbin/kamailio[26196]: ERROR: pv [pv_core.c:2115]: … [View More]

3 3

Kamailio users creation mechanism
by Alexandru Covalschi 29 May '15

29 May '15

Hello! My goal is to create a mechanism for dynamic creation/deletion of SIP users on Kamailio. First question: is it possible to create users not via kamctl command, but directly inserting new entries to this tables? And the second one: if it is possible, which hash alghorythm Kamailio uses when creating a new user on subscriber table? Becase I see 2 fields with hashes. Thank you -- Alexandru Covalschi VoIP engineer and system administrator phone: +37367398493 <http://abs-telecom.com/>

2 1

Elastix MT (3.0) issue with NAT (ACK is not received for 200 OK)
by Mainul Haque 28 May '15

28 May '15

Hello. I think I understand the problem, but I do not know how to fix it. I have done the following when the problem accord: -Download Elastix MT 64bit (downloaded from - http://www.elastix.com/en/downloads/) -Install it in VMware ESXi 5.1. Elastix works fine within the LAN -Then I pushed the VM to EC2 by exporting VMware OVF -I noticed that I could not registered my softphone (eyebeam 1.5) -After doing research online, I had to modify /etc/kamailio/kamailio-mhomed-elastix.cfg to know about … [View More]the new IP of EC2 instance. See below of what I had to change: Old settings: [root@new-host-2 endpoint_configurator]# grep 192 /etc/kamailio/kamailio-mhomed-elastix.cfg if (is_in_subnet($var(target_remote_ip), "192.168.1.0/24")) { $var(rtpproxy_if) = "192.168.1.62"; $var(rtpproxy_if) = "192.168.1.6"; To New Settings: [root@new-host-2 ~]# grep 172 /etc/kamailio/kamailio-mhomed-elastix.cfg if (is_in_subnet($var(target_remote_ip), "172.31.48.0/18")) { $var(rtpproxy_if) = "172.31.55.101"; $var(rtpproxy_if) = "172.31.55.101"; -Now I can register my eyebeam softphone. -When ever I dial anything, the connection would *drop after 10 to 30 seconds.* -When I enable SIP debug, I get the following: ############################################################# [May 28 16:07:58] VERBOSE[2688] chan_sip.c: <--- SIP read from UDP:127.0.0.1:5060 ---> INVITE sip:*65@voiptosave.com SIP/2.0 Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Record-Route: <sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK0499.3cc1dc7f932835a200ec1f8feafd0895.0 Via: SIP/2.0/UDP 192.168.1.6:29470 ;branch=z9hG4bK-d87543-182127345f1d7b4f-1--d87543-;rport=29470 Max-Forwards: 69 Contact: <sip:110@192.168.1.6:29470> To: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080> From: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Content-Type: application/sdp User-Agent: eyeBeam release 1011w stamp 42237 Content-Length: 457 v=0 o=- 2 2 IN IP4 192.168.1.62 s=CounterPath eyeBeam 1.5 c=IN IP4 192.168.1.62 t=0 0 m=audio 18598 RTP/AVP 100 106 6 0 105 8 18 3 5 101 a=alt:1 1 : KjAnzMl+ lOdYVIyR 192.168.1.6 15880 a=fmtp:18 annexb=yes a=fmtp:101 0-15 a=rtpmap:100 SPEEX/16000 a=rtpmap:106 SPEEX-FEC/16000 a=rtpmap:105 SPEEX-FEC/8000 a=rtpmap:18 G729/8000 a=rtpmap:101 telephone-event/8000 a=sendrecv a=x-rtp-session-id:60C3A67CD0E643D8A6945053F94B1D3E a=nortpproxy:yes <-------------> [May 28 16:07:58] VERBOSE[2688] chan_sip.c: --- (15 headers 17 lines) --- [May 28 16:07:58] VERBOSE[2688] chan_sip.c: Sending to 127.0.0.1:5060 (NAT) [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Sending to 127.0.0.1:5060 (NAT) [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Using INVITE request as basis request - Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found peer ' 110_voiptosave.com' for '110_voiptosave.com' from 127.0.0.1:5060 [May 28 16:07:58] VERBOSE[2688][C-00000021] netsock2.c: == Using SIP RTP TOS bits 184 [May 28 16:07:58] VERBOSE[2688][C-00000021] netsock2.c: == Using SIP RTP CoS mark 5 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 100 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 106 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 6 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 0 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 105 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 8 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 18 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 3 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 5 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found RTP audio format 101 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found audio description format SPEEX for ID 100 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found unknown media description format SPEEX-FEC for ID 106 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found unknown media description format SPEEX-FEC for ID 105 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found audio description format G729 for ID 18 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Found audio description format telephone-event for ID 101 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Capabilities: us - (gsm|ulaw|alaw), peer - audio=(gsm|ulaw|alaw|adpcm|g729|speex16)/video=(nothing)/text=(nothing), combined - (gsm|ulaw|alaw) [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Non-codec capabilities (dtmf): us - 0x1 (telephone-event|), peer - 0x1 (telephone-event|), combined - 0x1 (telephone-event|) [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Peer audio RTP is at port 192.168.1.62:18598 [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: Looking for *65 in voiptosave.com-from-internal (domain voiptosave.com) [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: list_route: hop: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: list_route: hop: <sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> [May 28 16:07:58] VERBOSE[2688][C-00000021] chan_sip.c: <--- Transmitting (NAT) to 127.0.0.1:5060 ---> SIP/2.0 100 Trying Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK0499.3cc1dc7f932835a200ec1f8feafd0895.0;received=127.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.6:29470 ;branch=z9hG4bK-d87543-182127345f1d7b4f-1--d87543-;rport=29470 Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Record-Route: <sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> From: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e To: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080> Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 2 INVITE Server: Asterisk PBX 11.13.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Contact: <sip:*65@127.0.0.1:5080> Content-Length: 0 <------------> [May 28 16:07:58] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:1] Answer("SIP/110_voiptosave.com-0000001a", "") in new stack [May 28 16:07:58] VERBOSE[9110][C-00000021] chan_sip.c: Audio is at 17370 [May 28 16:07:58] VERBOSE[9110][C-00000021] chan_sip.c: Adding codec 100003 (ulaw) to SDP [May 28 16:07:58] VERBOSE[9110][C-00000021] chan_sip.c: Adding codec 100004 (alaw) to SDP [May 28 16:07:58] VERBOSE[9110][C-00000021] chan_sip.c: Adding codec 100002 (gsm) to SDP [May 28 16:07:58] VERBOSE[9110][C-00000021] chan_sip.c: Adding non-codec 0x1 (telephone-event) to SDP [May 28 16:07:58] VERBOSE[9110][C-00000021] chan_sip.c: <--- Reliably Transmitting (NAT) to 127.0.0.1:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK0499.3cc1dc7f932835a200ec1f8feafd0895.0;received=127.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.6:29470 ;branch=z9hG4bK-d87543-182127345f1d7b4f-1--d87543-;rport=29470 Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Record-Route: <sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> From: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e To: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080>;tag=as3a404cf6 Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 2 INVITE Server: Asterisk PBX 11.13.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Contact: <sip:*65@127.0.0.1:5080> Content-Type: application/sdp Content-Length: 275 v=0 o=root 153043023 153043023 IN IP4 127.0.0.1 s=Asterisk PBX 11.13.0 c=IN IP4 127.0.0.1 t=0 0 m=audio 17370 RTP/AVP 0 8 3 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv <------------> [May 28 16:07:58] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:2] Wait("SIP/110_voiptosave.com-0000001a", "1") in new stack [May 28 16:07:58] VERBOSE[2688] chan_sip.c: Retransmitting #1 (NAT) to 127.0.0.1:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK0499.3cc1dc7f932835a200ec1f8feafd0895.0;received=127.0.0.1;rport=5060 Via: SIP/2.0/UDP 192.168.1.6:29470 ;branch=z9hG4bK-d87543-182127345f1d7b4f-1--d87543-;rport=29470 Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Record-Route: <sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> From: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e To: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080>;tag=as3a404cf6 Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 2 INVITE Server: Asterisk PBX 11.13.0 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Contact: <sip:*65@127.0.0.1:5080> Content-Type: application/sdp Content-Length: 275 v=0 o=root 153043023 153043023 IN IP4 127.0.0.1 s=Asterisk PBX 11.13.0 c=IN IP4 127.0.0.1 t=0 0 m=audio 17370 RTP/AVP 0 8 3 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv --- [May 28 16:07:58] VERBOSE[2688] chan_sip.c: <--- SIP read from UDP:127.0.0.1:5060 ---> ACK sip:*65@127.0.0.1:5080 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK0499.1131e459ea9f93c78896b0fdaf99b3be.0 Via: SIP/2.0/UDP 192.168.1.6:29470 ;branch=z9hG4bK-d87543-9f74bc13426dd510-1--d87543-;rport=29470 Max-Forwards: 69 Contact: <sip:110@192.168.1.6:29470> To: "*65"<sip:*65@voiptosave.com>;tag=as3a404cf6 From: "Manny"<sip:110@voiptosave.com>;tag=f133137e Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 2 ACK Proxy-Authorization: Digest username="110",realm="voiptosave.com ",nonce="VWd2ylVndZ5Yo3kaAdjLh/W6zc+CeoE1",uri="sip:*65@voiptosave.com ",response="ed5ad3dd093d74414340aa68dca6a246",algorithm=MD5 User-Agent: eyeBeam release 1011w stamp 42237 Content-Length: 0 <-------------> [May 28 16:07:58] VERBOSE[2688] chan_sip.c: --- (12 headers 0 lines) --- [May 28 16:07:58] VERBOSE[2688] chan_sip.c: <--- SIP read from UDP:127.0.0.1:5060 ---> ACK sip:*65@127.0.0.1:5080 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK0499.1131e459ea9f93c78896b0fdaf99b3be.0 Via: SIP/2.0/UDP 192.168.1.6:29470 ;branch=z9hG4bK-d87543-9f74bc13426dd510-1--d87543-;rport=29470 Max-Forwards: 69 Contact: <sip:110@192.168.1.6:29470> To: "*65"<sip:*65@voiptosave.com>;tag=as3a404cf6 From: "Manny"<sip:110@voiptosave.com>;tag=f133137e Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 2 ACK Proxy-Authorization: Digest username="110",realm="voiptosave.com ",nonce="VWd2ylVndZ5Yo3kaAdjLh/W6zc+CeoE1",uri="sip:*65@voiptosave.com ",response="ed5ad3dd093d74414340aa68dca6a246",algorithm=MD5 User-Agent: eyeBeam release 1011w stamp 42237 Content-Length: 0 <-------------> [May 28 16:07:58] VERBOSE[2688] chan_sip.c: --- (12 headers 0 lines) --- [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:3] Macro("SIP/110_voiptosave.com-0000001a", "voiptosave.com-user-callerid,") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:1] Set("SIP/110_voiptosave.com-0000001a", "EXTUSER=110") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:2] GotoIf("SIP/110_voiptosave.com-0000001a", "0?report") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:3] ExecIf("SIP/110_voiptosave.com-0000001a", "1?Set(REALCALLERIDNUM=110)") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:4] Set("SIP/110_voiptosave.com-0000001a", "EXTUSER=110") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:5] Set("SIP/110_voiptosave.com-0000001a", "EXTUSERCIDNAME=User_110") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:6] GotoIf("SIP/110_voiptosave.com-0000001a", "0?report") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:7] Set("SIP/110_voiptosave.com-0000001a", "EXTUSERCID=110") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:8] Set("SIP/110_voiptosave.com-0000001a", "CALLERID(all)="User_110" <110>") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:9] ExecIf("SIP/110_voiptosave.com-0000001a", "1?Set(CHANNEL(language)=en)") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:10] ExecIf("SIP/110_voiptosave.com-0000001a", "1?Set(CHANNEL(language)=en)") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:11] GotoIf("SIP/110_voiptosave.com-0000001a", "0?continue") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:12] Set("SIP/110_voiptosave.com-0000001a", "__TTL=64") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:13] GotoIf("SIP/110_voiptosave.com-0000001a", "1?continue") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-user-callerid,s,20) [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:20] Set("SIP/110_voiptosave.com-0000001a", "CALLERID(number)=110") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:21] Set("SIP/110_voiptosave.com-0000001a", "CALLERID(name)=User_110") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-user-callerid:22] NoOp("SIP/110_voiptosave.com-0000001a", "Using CallerID "User_110" <110>") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:4] Playback("SIP/110_voiptosave.com-0000001a", "your") in new stack [May 28 16:07:59] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'your.gsm' (language 'en') [May 28 16:08:00] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:5] Playback("SIP/110_voiptosave.com-0000001a", "extension") in new stack [May 28 16:08:00] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'extension.gsm' (language 'en') [May 28 16:08:01] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:6] Playback("SIP/110_voiptosave.com-0000001a", "number") in new stack [May 28 16:08:01] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'number.gsm' (language 'en') [May 28 16:08:02] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:7] Playback("SIP/110_voiptosave.com-0000001a", "is") in new stack [May 28 16:08:02] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'is.gsm' (language 'en') [May 28 16:08:03] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:8] SayDigits("SIP/110_voiptosave.com-0000001a", "110") in new stack [May 28 16:08:03] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'digits/1.gsm' (language 'en') [May 28 16:08:03] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'digits/1.gsm' (language 'en') [May 28 16:08:04] VERBOSE[9110][C-00000021] file.c: -- <SIP/110_voiptosave.com-0000001a> Playing 'digits/0.gsm' (language 'en') [May 28 16:08:05] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:9] Wait("SIP/110_voiptosave.com-0000001a", "2") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [*65@voiptosave.com-from-internal:10] Hangup("SIP/110_voiptosave.com-0000001a", "") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: == Spawn extension (voiptosave.com-from-internal, *65, 10) exited non-zero on 'SIP/110_voiptosave.com-0000001a' [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [h@voiptosave.com-from-internal:1] Macro("SIP/110_voiptosave.com-0000001a", "voiptosave.com-hangupcall") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:1] ExecIf("SIP/110_voiptosave.com-0000001a", "1?Set(CDR(organization_domain)= voiptosave.com)") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:2] GotoIf("SIP/110_voiptosave.com-0000001a", "1?endmixmoncheck") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,7) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:7] NoOp("SIP/110_voiptosave.com-0000001a", "End of MIXMON check") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:8] GotoIf("SIP/110_voiptosave.com-0000001a", "1?nomeetmemon") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,14) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:14] NoOp("SIP/110_voiptosave.com-0000001a", "MEETME_RECORDINGFILE=") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:15] GotoIf("SIP/110_voiptosave.com-0000001a", "1?noautomon") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,23) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:23] NoOp("SIP/110_voiptosave.com-0000001a", "TOUCH_MONITOR_OUTPUT=") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:24] GotoIf("SIP/110_voiptosave.com-0000001a", "1?noautomon2") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,31) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:31] NoOp("SIP/110_voiptosave.com-0000001a", "MONITOR_FILENAME=") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:32] GotoIf("SIP/110_voiptosave.com-0000001a", "1?skiprg") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,35) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:35] GotoIf("SIP/110_voiptosave.com-0000001a", "1?skipblkvm") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,38) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:38] GotoIf("SIP/110_voiptosave.com-0000001a", "1?theend") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Goto (macro-voiptosave.com-hangupcall,s,40) [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: -- Executing [s@macro-voiptosave.com-hangupcall:40] Hangup("SIP/110_voiptosave.com-0000001a", "") in new stack [May 28 16:08:07] VERBOSE[9110][C-00000021] app_macro.c: == Spawn extension (macro-voiptosave.com-hangupcall, s, 40) exited non-zero on 'SIP/110_voiptosave.com-0000001a' in macro 'voiptosave.com-hangupcall' [May 28 16:08:07] VERBOSE[9110][C-00000021] pbx.c: == Spawn extension (voiptosave.com-from-internal, h, 1) exited non-zero on 'SIP/110_voiptosave.com-0000001a' [May 28 16:08:07] VERBOSE[9110][C-00000021] chan_sip.c: Scheduling destruction of SIP dialog 'Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA.' in 6400 ms (Method: ACK) [May 28 16:08:07] VERBOSE[9110][C-00000021] chan_sip.c: set_destination: Parsing <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> for address/port to send to [May 28 16:08:07] VERBOSE[9110][C-00000021] chan_sip.c: set_destination: set destination to 127.0.0.1:5060 [May 28 16:08:07] VERBOSE[9110][C-00000021] chan_sip.c: Reliably Transmitting (NAT) to 127.0.0.1:5060: BYE sip:110@192.168.1.6:29470 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2355deaa;rport Route: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes>,<sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Max-Forwards: 70 From: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080>;tag=as3a404cf6 To: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 102 BYE User-Agent: Asterisk PBX 11.13.0 X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 Content-Length: 0 --- [May 28 16:08:07] VERBOSE[2688] chan_sip.c: Retransmitting #1 (NAT) to 127.0.0.1:5060: BYE sip:110@192.168.1.6:29470 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2355deaa;rport Route: <sip:127.0.0.1;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes>,<sip:192.168.1.62;r2=on;lr=on;ftag=f133137e;vsf=BhoZSgsAAW82GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;vst=HxoZShAcA2o2GQYZBBscEhcTS00MAi0xMjcuMC4wLjE6NTA4MA--;nat=yes> Max-Forwards: 70 From: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080>;tag=as3a404cf6 To: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 102 BYE User-Agent: Asterisk PBX 11.13.0 X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 Content-Length: 0 --- [May 28 16:08:07] VERBOSE[2688] chan_sip.c: <--- SIP read from UDP:127.0.0.1:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK2355deaa;rport=5080 Contact: <sip:110@192.168.1.6:29470> To: "Manny"<sip:110_voiptosave.com@127.0.0.1:5080>;tag=f133137e From: "*65"<sip:*65_voiptosave.com@127.0.0.1:5080>;tag=as3a404cf6 Call-ID: Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA. CSeq: 102 BYE User-Agent: eyeBeam release 1011w stamp 42237 Content-Length: 0 <-------------> [May 28 16:08:07] VERBOSE[2688] chan_sip.c: --- (9 headers 0 lines) --- [May 28 16:08:07] VERBOSE[2688][C-00000021] chan_sip.c: SIP Response message for INCOMING dialog BYE arrived [May 28 16:08:07] VERBOSE[2688] chan_sip.c: Really destroying SIP dialog 'Mjk2YjBjZjA2NDYzOTUxZDVmOGZjNTgwYzVmMjg3YjA.' Method: ACK [May 28 16:08:08] VERBOSE[2688] chan_sip.c: Reliably Transmitting (NAT) to 127.0.0.1:5060: OPTIONS sip:110@192.168.1.6:29470;rinstance=3180b40a89f2e3f4 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK0bcd981c;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@127.0.0.1:5080>;tag=as68358641 To: <sip:110@192.168.1.6:29470;rinstance=3180b40a89f2e3f4> Contact: <sip:asterisk@127.0.0.1:5080> Call-ID: 03d50e985a2f08445ad315c83a591412@127.0.0.1:5080 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 11.13.0 Date: Thu, 28 May 2015 20:08:08 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Length: 0 --- [May 28 16:08:08] VERBOSE[2688] chan_sip.c: <--- SIP read from UDP:127.0.0.1:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK0bcd981c;rport=5080 Contact: <sip:192.168.1.6:29470> To: <sip:110@192.168.1.6:29470;rinstance=3180b40a89f2e3f4>;tag=86756729 From: "asterisk"<sip:asterisk@127.0.0.1:5080>;tag=as68358641 Call-ID: 03d50e985a2f08445ad315c83a591412@127.0.0.1:5080 CSeq: 102 OPTIONS Accept: application/sdp Accept-Language: en Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: eyeBeam release 1011w stamp 42237 Content-Length: 0 <-------------> [May 28 16:08:08] VERBOSE[2688] chan_sip.c: --- (12 headers 0 lines) --- [May 28 16:08:08] VERBOSE[2688] chan_sip.c: Really destroying SIP dialog ' 03d50e985a2f08445ad315c83a591412@127.0.0.1:5080' Method: OPTIONS ################################################################## Please let me know if you need any settings. I am more than happy to provide it. Thank you. [View Less]

1 1

log the value of "from_uri" and "myself"
by Al S 28 May '15

28 May '15

Hi, I would like to know how to log the value of "from_uri" and "myself" attributes on kamailio 3.3.7 ?None of the following works: xlog("L_INFO","from_uri: $dlg(from_uri)"); $var(x) = from_uri;xlog("L_INFO","$var(x)"); Thanks,Al

2 3

Kamailio not receiving BYE request
by Ali Taher 28 May '15

28 May '15

Hello, Kamailio is not receiving the BYE request when the call is ended by any of call parties. Noting that when the call is connected, a direct RTP session is established between the user and the gateway , and kamailio doesn't receive since then any message related to this call. Is there any trick to do in order to let kamailio gets the BYE request? Attached is the used configuration. Appreciate your help. Regards, Ali

3 11

Regarding presence conference
by Surendra Pullaiah 28 May '15

28 May '15

Hello Daniel, I am implementing conference bridge using kamalio and RTP porxy without media mixing. Since for now we are ok with this. My question is as per the flow of RFC 4579, UA may send SUBSCRIBE to the conference URI with event as conference. In kamalio modules presence_conference where they mentioned such way that it will support the same what I am looking for. But I simulated using sipP by sending subscriber with conference event. I am not seeing any notify XML … [View More]

1 0

Kamailio drouting failure not working
by Ali Taher 28 May '15

28 May '15

Dears, I'm trying drouting module in kamailio , it's working good when first gateway in the list is up , yet when first gateway is unrecheable , it's not rerouted to second destination, meaning that fail over is not working. Kindly find attached wireshark trace I'm getting . Below is db entries I'm using : dr_gateways: Dr_gw_lists Dr_groups: Dr_rules: Below is routing block I'm using : request_route{ if (is_method("INVITE")) { … [View More]

3 22

kamailio crash periodically in timer handler
by Péter Barabás 27 May '15

27 May '15

Hi, we have a serious problem with Kamailio v4.2.3, it crashes after some days. We have checked the core dump and the gdb output is the following for bt and full backtrace: #0 0x0000000000602291 in timer_list_expire (t=1432559962, h=0x7f64eb5b6bd0, slow_l=0x7f64eb5ba328, slow_mark=43873) at timer.c:877 #1 0x0000000000602746 in timer_handler () at timer.c:953 #2 0x0000000000602bb9 in timer_main () at timer.c:992 #3 0x00000000004a833c in main_loop () at main.c:1700 #4 0x00000000004ad857 in … [View More]main (argc=13, argv=0x7fff96697d38) at main.c:2578 #0 0x0000000000602291 in timer_list_expire (t=1432559962, h=0x7f64eb5b6bd0, slow_l=0x7f64eb5ba328, slow_mark=43873) at timer.c:877 tl = 0x7f64ebc3a908 ret = 0 #1 0x0000000000602746 in timer_handler () at timer.c:953 saved_ticks = 1432559962 run_slow_timer = 0 i = 865 __FUNCTION__ = "timer_handler" #2 0x0000000000602bb9 in timer_main () at timer.c:992 No locals. #3 0x00000000004a833c in main_loop () at main.c:1700 i = 4 pid = 0 si = 0x0 si_desc = "udp receiver child=3 sock=127.0.0.1:5060\000\375\362\250/\313\345\v\004\000\000\000\000\000\000\000\004\257\263=\000\000\000\000\200TA\000\000\000\000\000\060}i\226\377\177", '\000' <repeats 19 times>, "{i\226\377\177\000\000\376\366R\000\000\000\000\000\377\377\377\377\377\177\000\000@\350\250\000\000\000\000" nrprocs = 4 __FUNCTION__ = "main_loop" #4 0x00000000004ad857 in main (argc=13, argv=0x7fff96697d38) at main.c:2578 cfg_stream = 0x1b94010 c = -1 r = 0 tmp = 0x7fff96699b17 "" tmp_len = 0 port = 1 proto = 32767 options = 0x703e08 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 2591880768 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x7fff96697c50 "" __FUNCTION__ = "main" In the logs it can be seen: Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4635]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 21 Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: ALERT: <core> [main.c:784]: handle_sigs(): child process 4623 exited by a signal 11 Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: ALERT: <core> [main.c:787]: handle_sigs(): core was generated Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4631]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4628]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4634]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4615]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4617]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4626]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4625]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4624]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4632]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4622]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4621]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4620]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4619]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4618]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4616]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4635]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4614]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4629]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4627]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4633]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4630]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: INFO: <core> [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7f64eca19950/0x7f64eca19988) - ignore Apr 23 08:07:31 ctsip1 /usr/local/sbin/kamailio[4612]: INFO: <core> [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7f64ed587f20/0x7f64ed587f58) - ignore Kamailio runs on Ubuntu trusty. The interesting thing that we run Kamailio 4.2.3 in an other environment (on Debian Squeeze) and it works perfect, no crashes. The main difference is that in Debian environment we have less number of users and the firewall is not so strength. But the configuration and the source is the same for both. Please help us to solve this problem. Thanks. Dr. Péter Barabás Director of Software Development Arenim Technologies AB. Mob: +36 70 314 56 57 Tel: +36 1 8 555 602 E-mail: peter.barabas(a)arenim.com<mailto:peter.barabas@arenim.com> Postal: Sweden - 11435 Stockholm, Stureplan 4c, 4th. Floor [Arenim_logo]<http://www.arenim.com/> [CryptTalk_Logo]<http://www.crypttalk.com/> [View Less]

2 11

Kamailio with public ip, users behind nat
by MtK - SmartMtK 27 May '15

27 May '15

Hi, I'm trying to install Kamailio on a server with a public IP, but my users are mostly at their homes (a.k.a behind NAT). I understood I need to install RTPproxy, but all tutorials out there are for servers behind nat, and they talk about the server's private IP, which does not exists in this case. how would I configure RTPproxy and Kamailio to allow users to subscribe to the server and have audio calls between them? MtK

3 2

dbcassandra schema files
by jay binks 26 May '15

26 May '15

Hi all, Im wondering if anyone can share their schema files for dbcassandra. Ive managed to construct a bunch based on what ive found in git, wiki all over the place, I just want to compare my ones, with some others. specifically the location table. -- Sincerely Jay

2 1

Development open again for master branch
by Daniel-Constantin Mierla 26 May '15

26 May '15

Hello, as branch 4.3 was created to host the upcoming release series 4.3, new features can be now pushed to master branch. They will be part of the next future release, likely to be numbered 4.4. Any fixes that affect existing code in branches 4.3 or older version have to be backported - push first to master and then cherry pick -- some guidelines exemplified with branch 3.2 are available at: - https://www.kamailio.org/wiki/devel/backporting-to-3.2.x As usual, the next future release … [View More]

1 0

Branch 4.3 created
by Daniel-Constantin Mierla 26 May '15

26 May '15

Hello, the GIT branch 4.3 was created, it will host the release series 4.3.x. To get this branch from GIT, you can use: git clone https://github.com/kamailio/kamailio.git kamailio cd kamailio git checkout -b 4.3 origin/4.3 Notes about installing Kamailio from this branch are available at: - http://www.kamailio.org/wiki/install/4.3.x/git Hopefully in about two weeks or so the full release of 4.3.0 will be out. >From now on, any corresponding fix has to be pushed first to master branch … [View More]

1 0

Using $avp in evapi:message-received
by DanB 25 May '15

25 May '15

Hey Guys, Was wondering what would be the recommended way to share information between $evapi(msg) received and transaction processors? I have tried $avp() but they do not appear to be available in evapi:message-received route. Trying to avoid here $sht() so I don't need to do extra management to destroy them. Is there any way to "activate" the $avp or $dlg_var based on dialog index, label maybe? Thanks in advance for any kind of tip! DanB //

3 7

info
by Walter Josef 25 May '15

25 May '15

Hi, Do you have any phonenumber for info about your iptel voip phone service ?

2 1

Creating branch 4.3
by Daniel-Constantin Mierla 25 May '15

25 May '15

Hello, I am planning to branch the code for upcoming major release on next Monday, May 25. Testing went fine so far in my side and I don't expect new consistent changes. Any fixes afterwards will be backported as usual to a stable branch. From that moment, master branch will be open again for new features. If someone else has different proposal, let's discuss it on sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/… [View More]

1 1

Re: [SR-Users] Getting 404 From Kamailio for PRACK
by DanB 24 May '15

24 May '15

Hi Austin, Kamailio will not reject by himself (nor handle) PRACK (or any other methods) unless you tell him so. The logic for handling it should be in your .cfg file. I suggest adding xlog statements through your config script and see where that is rejected. 404 would tell me you are trying to locate your endpoint and send the PRACK there but the endpoint is not registered. DanB

1 0

Re: [SR-Users] Increase Simultaneous Registration
by DanB 24 May '15

24 May '15

Hi Austin, Kamailio should be pretty fast on these things. Here are things which you can check: * Increase number of TCP workers/make sure you are using async TCP. * Use in-memory store for your registrations, not DB ones (at least dump async your contacts in DB). * Make sure you allow enough files to be opened in case of TCP connections (I suspect this is your issue there). Regarding performance tests, not sure if you saw already these links: http://www.kamailio.org/docs/openser-… [View More]

1 0

disabling Server header in kamailio
by NITESH BANSAL 22 May '15

22 May '15

Hello, I noticed that Kamailio adds a Server header in the replies generated by it, is there anyway to disable it? Thanks in advance for your help, Nitesh

2 1

Find if client is connected.
by Dmytro Bogovych 22 May '15

22 May '15

Greetings. I want to modify INVITE answers processing in this way: 1) receive INVITE answer 2) check if recipient is registered but has no TCP/TLS connection now 3) suspend answer for 30 seconds (for example) 4) resume answer if REGISTER comes from lost client in these 30 seconds 5) terminate INVITE session if 30 seconds are expired What I do not understand - is it possible to find if client is connected now to kamailio? I talk about TCP/TLS connection only - not about registration record. Thank you!

3 7

issues with domain names in the record route
by NITESH BANSAL 22 May '15

22 May '15

Hello, I am trying to play with domain names in the Record-Route header. This is for a case when kamailio is doing the translation between UDP and TLS, so it is doing double record routing. I want to use the ip addresses on inbound UDP leg and domain names on the outbound TLS leg in record-route headers. I'm doing this by calling the following function -- record_route_preset("xyz.com;transport=tls", "1.1.1.1"); ---- This does the trick of adding a Record-Route in initial TLS invite on the … [View More]

3 3

rtpproxy 2.0
by Klaus Darilion 22 May '15

22 May '15

Hi! I just found out that there is a new rtpproxy release: http://www.rtpproxy.org/post/v2release/ Has anybody tested it and want to share some experiences? Or have people turned to rtpengine meanwhile? (I am still using rtpproxy 1.2 as I do not need new features). regards Klaus

3 2

Re: [SR-Users] Kamailio proxy for far-end nat traversal
by rahul.ultimate 21 May '15

21 May '15

Hi Daniel I have rtpproxy to perform media relaying. The case where it just timeouts: 1. Client A behind NAT (wifi) calling Client B on 3G Sent from Samsung Mobile -------- Original message -------- From: Daniel-Constantin Mierla <miconda(a)gmail.com> Date:05/05/2015 12:52 (GMT+05:30) To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org> Subject: Re: [SR-Users] Kamailio proxy for far-end nat traversal Hello, do you have rtpproxy or rtpengine … [View More]

4 5

XLOG Problem
by Nahum Nir 21 May '15

21 May '15

Hi All, I am using Kamailio 4.0.3 and can't logs. .cfg: #!define WITH_DEBUG ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 When the server starts there outputs about xlog: 0(20266) DEBUG: <core> [cfg.y:1791]: yyparse(): loading module xlog.so 0(20266) DEBUG: <core> [sr_module.c:499]: load_module(): load_module: module file not found </usr/… [View More]local/lib/kamailio/modules_k/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:522]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:564]: load_module(): load_module: trying to load </usr/lib64/kamailio/modules/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:343]: register_module(): register PV from: xlog 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20268) DEBUG: <core> [sr_module.c:935]: init_mod(): DEBUG: init_mod: xlog 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() At the beginning of the Main routing block I put: log("~~~~~~~~~~~~route~~~~~~~~~~~~~~~~~~~~\n"); xdbg("~~~~~~~~~ xdbg - route~~~~~~~~~~~~~~~~~~~~\n"); xlog("L_ALERT","~~~~~~~~~ xlog - route~~~~~~~~~~~~~~~~~~~~\n"); But nothing is logging when I send INVITEs Any help? Thanks, Nir [View Less]

4 3

Kamailio 4.2.4 segfault and crash
by Federico San Martín 21 May '15

21 May '15

Hi all, I just experienced a sudden crash from one of my Kamailio servers. I'm using v4.2.4 built from git repository (branch remotes/origin/4.2). The error logs show this at the time of the crash (I'm using debug=1 on config file) May 15 15:59:53 KAMAILIO-ERS1 kamailio[21162]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 19 May 15 15:59:53 KAMAILIO-ERS1 kamailio[21141]: ALERT: <core> [main.c:784]: handle_sigs(): child process 21149 exited by a signal 11 May 15 15:59:… [View More]

2 3

Clear To-tag on '181 Call Is Being Forwarded'
by John Murray 21 May '15

21 May '15

Hello, I am forwarding an incoming call to a destination and on time-out forward to another and them another. I need to send a '181 Call Is Being Forwarded' to my SBC to reset the early media stream when forwarding to the next destiation which I can do with sl_send_reply("181","Call Is Being Forwarded"). However the SBC vendor requires that the To-tag in the 181 is cleared for this to work. How can I clear the To-tag from this 181 response? Thanks John

2 1

setup dbtext issues
by jaflong jaflong 21 May '15

21 May '15

I need some instructions on how to setup dbtext properly I generated dbtext files through "./kamdbctl create" I then add user through "./kamctrl add user1 user1" It seems to have added the user because when I do the show './kamctl show user1' command it displays [1, ' user1', '10.1.1.1', ' user1', '', 'ee2820706921ce44a3f760e03ff19a22', '9e2c9e7df27f474d2b995c7e94ab32f2', ''] However viewing the subscriber file /usr/local/etc/kamailio/dbtext/subscriber id(int,auto) username(string) … [View More]

2 1

Debian package kamailio-tls-modules potential bug ?
by jay binks 20 May '15

20 May '15

I just found something odd in the Debian package for kamailio-als-modules and I'm looking for someone to verify it for me. I verified that I'm using Kamailio 4.2 # Kamailio -v version: kamailio 4.2.0 (x86_64/linux) 36e695 the docs http://kamailio.org/docs/modules/4.2.x/modules/tls.html#tls.p.tls_method show that I should be able to use "*TLSv1+" however Kamailio crashes on startup with * [tls_mod.c:287]: mod_init(): Invalid tls_method parameter value I have verified that TLSv1.1 and TLSv1.… [View More]

2 1

Kamailio v4.2.5 Released
by Daniel-Constantin Mierla 19 May '15

19 May '15

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

2 1

log_prefix not working in reply_route
by Klaus Darilion 19 May '15

19 May '15

Hi! Should log_prefix also work for xlog in reply routes? In my case it doesn't (Kamailio 4.2.2) Thanks Klaus

2 3

rtpproxy-ng and late SDP
by Sebastian Damm 19 May '15

19 May '15

Hi, I'm working on a setup, where I have to support late SDP. It is working right now, but I have to use an explicit rtpproxy_offer() when processing the reply to an INVITE without SDP. Is there a way to have rtpproxy_manage() handle those calls automatically? I was thinking of setting a flag in the request which is used by the rtpproxy_manage() function later. Best Regards, Sebastian

3 3

SIP Packet identifier
by jay binks 19 May '15

19 May '15

So im logging lots of information to Syslog to assist our helpdesk in diagnosing customer issues. Im seeing LOTS of user agents that re-use the sip Call-ID ( especially in registers ). What im wanting to be able to do is link a log message ( that I log at some point in my dialplan ) to a specific SIP packet ( viewed from voipmonitor, HOMER, wireshark ). I cant REALLY see anything in the SIP to uniquely identify a packet, however if kamailio provided the UDP packet checksum in a pseudo … [View More]

4 3

Planning to release Kamailio v4.2.5
by Daniel-Constantin Mierla 19 May '15

19 May '15

Hello, I am considering to release a new maintenance version from latest stable branch - to be v4.2.5 - next week, most likely on Tuesday (May 19) or Wednesday (May 20). If there is anything important to get in and not discussed yet, bring the topic on development mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 1

NO VOICE AFTER MSILO
by sscc 19 May '15

19 May '15

i have configured msilo module successful but there isn't any voice with msilo. i debug and compare the call flow with and without msilo. with msilo in call flow it didn't follow to relay and consequently didnt activate rtpproxy befor the call is answered. due to which during call there isn't any voice. please help -- View this message in context: http://sip-router.1086192.n5.nabble.com/NO-VOICE-AFTER-MSILO-tp137430.html Sent from the Users mailing list archive at Nabble.com.

3 8

sems-rtpengine-webrtc client audio problem
by Juha Heinanen 19 May '15

19 May '15

i have not been able to figure out, why i can't hear any audio when i call from webrtc client (using UDP/TLS/RTP/SAVPF profile) to sems echo server (using RTP/AVP profile): 1) webrtc client - UDP/TLS/RTP/SAVPF - rtpengine - RTP/AVP - sems echo server if i call from the same webrtc client to baresip, audio works fine: 2) webrtc client - UDP/TLS/RTP/SAVPF - rtpengine - RTP/AVP - baresip also, if i call from baresip using UDP/TLS/RTP/SAVPF profile to sems, audio works fine: 3) basesip - UDP/… [View More]TLS/RTP/SAVPF - rtpengine - RTP/AVP - sems echo server below is level 7 debug from the problem case (1). stats at the bottom tell that audio packets were flowing both ways fine. what does not seem correct is that the webrtc client is constantly sending "Successful STUN binding requests" to rtpengine. any advise for further debugging this problem would be highly appreciated. -- juha ------------------------------------------------------------------------------ May 18 11:47:34 box /usr/bin/sip-proxy[18299]: INFO: ===== rtpengine_offer(ICE=force replace-session-connection replace-origin via-branch=1 rtcp-mux-demux RTP/AVP) May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Received command 'offer' from 127.0.0.1:43378 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Dump for 'offer' from 127.0.0.1:43378: { "sdp": "v=0#015#012o=- 4880355588178147449 2 IN IP4 127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE audio#015#012a=msid-semantic: WMS k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012m=audio 35551 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 126#015#012c=IN IP4 93.106.207.11#015#012a=rtcp:35551 IN IP4 93.106.207.11#015#012a=candidate:1603072777 1 udp 2122260223 192.168.43.146 35551 typ host generation 0#015#012a=candidate:1603072777 2 udp 2122260223 192.168.43.146 35551 typ host generation 0#015#012a=candidate:2861 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... 99801 1 tcp 1518280447 192.168.43.146 0 typ host tcptype active generation 0#015#012a=candidate:286199801 2 tcp 1518280447 192.168.43.146 0 typ host tcptype active generation 0#015#012a=candidate:2466368666 1 udp 1686052607 93.106.207.11 35551 typ srflx raddr 192.168.43.146 rport 35551 generation 0#015#012a=candidate:2466368666 2 udp 1686052607 93.106.207.11 35551 typ srflx raddr 192.168.43.146 rport 35551 generation 0#015#012a=ice-ufrag:U+gG6hyUzfrt859a#015#012a=ice-pwd:FQwGMInhUjWl8bbYIbSJS1pz#015#012a=fingerprint:sha-256 09:D6: ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... AA:5B:F2:9E:D6:A7:CE:69:D3:76:67:EF:36:A6:F4:87:94:B7:37:82:AF:17:9E:4B:E8:B7:F4:F1:8C:A0#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time#015#012a=sendrec… opus/48000/2#015#012a=fmtp:111 minptime=10; useinbandfec=1#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... #012a=rtpmap:13 CN/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:2202238380 cname:zcLA/sUaZsuYHC73#015#012a=ssrc:2202238380 msid:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM 2053b0c2-35f2-48f8-ae79-419a078169f4#015#012a=ssrc:2202238380 mslabel:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012a=ssrc:2202238380 label:2053b0c2-35f2-48f8-ae79-419a078169f4#015#012", "ICE": "force", "replace": [ "session-connection", "origin" ], "transport-protocol": "RTP/AVP", "rtcp-mux": [ "demux" ], "call-id": "e91aj9gq39qr07b6dn6u", "vi ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... a-branch": "z9hG4bK1294663", "received-from": [ "IP4", "<sip-proxy-rtpengine-ip>" ], "from-tag": "0m9av72lp5", "command": "offer" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Creating new call May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Opened ports 8012..8013 for media relay May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Opened ports 8028..8029 for media relay May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 1603072777:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Created candidate pair MmPVRTRG3mIW6Esg:1603072777:1 between <sip-proxy-rtpengine-ip> and 192.168.43.146:35551, type host May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 1603072777:2 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Created candidate pair MmPVRTRG3mIW6Esg:2466368666:1 between <sip-proxy-rtpengine-ip> and 93.106.207.11:35551, type srflx May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Learning new ICE candidate 2466368666:2 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Replying to 'offer' from 127.0.0.1:43378 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Response dump for 'offer' to 127.0.0.1:43378: { "sdp": "v=0#015#012o=- 4880355588178147449 2 IN IP4 <sip-proxy-rtpengine-ip>#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012m=audio 8012 RTP/AVP 111 103 104 9 0 8 106 105 13 126#015#012c=IN IP4 <sip-proxy-rtpengine-ip>#015#012a=rtpmap:111 opus/48000/2#015#012a=fmtp:111 minptime=10; useinbandfec=1#015#012a=rtpmap:103 ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106 CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... CN/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:2202238380 cname:zcLA/sUaZsuYHC73#015#012a=ssrc:2202238380 msid:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM 2053b0c2-35f2-48f8-ae79-419a078169f4#015#012a=ssrc:2202238380 mslabel:k2qrqNs5yzQcMjup0H0E85yNYAP5aA0w4SeM#015#012a=ssrc:2202238380 label:2053b0c2-35f2-48f8-ae79-419a078169f4#015#012a=sendrecv#015#012a=rtcp:8013#015#012a=ice-ufrag:aEaiKI4d#015#012a=ice-pwd:S0ET0fRwnGLZ6lYSdXuAfvCo9K#015#012a=candidate:MmPVRTRG3mIW6Esg 1 UDP 2130706431 <sip-proxy-rtpengine-ip> 8012 typ host#015#012a=candidate:MmP ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... VRTRG3mIW6Esg 2 UDP 2130706430 <sip-proxy-rtpengine-ip> 8013 typ host#015#012", "result": "ok" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box /usr/bin/sip-proxy[18242]: INFO: ===== rtpengine_answer(ICE=force via-branch=2 trust-address) May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Received command 'answer' from 127.0.0.1:49396 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Dump for 'answer' from 127.0.0.1:49396: { "sdp": "v=0#015#012o=sems 1244512444 1372754 IN IP4 <sip-proxy-rtpengine-ip>#015#012s=sems#015#012c=IN IP4 <sip-proxy-rtpengine-ip>#015#012t=0 0#015#012m=audio 8064 RTP/AVP 0 8 126#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=sendrecv#015#012a=direction:both#015#012", "ICE": "force", "flags": [ "trust-address" ], "call-id": "e91aj9gq39qr07b6dn6u", "via-branch": "z9hG4bK1294663", "received-from": [ "IP4", "127.0.0.1" ], "from-tag": "0m9av72lp5", "to-tag": "627A71DC-5559A726000163C1 ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... -AA759700", "command": "answer" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Shutting down ICE agent (nothing to do) May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Replying to 'answer' from 127.0.0.1:49396 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Response dump for 'answer' to 127.0.0.1:49396: { "sdp": "v=0#015#012o=sems 1244512444 1372754 IN IP4 <sip-proxy-rtpengine-ip>#015#012s=sems#015#012c=IN IP4 <sip-proxy-rtpengine-ip>#015#012t=0 0#015#012m=audio 8028 UDP/TLS/RTP/SAVPF 0 8 126#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:126 telephone-event/8000#015#012a=direction:both#015#012a=sendrecv#015#012a=rtcp:8028#015#012a=rtcp-mux#015#012a=setup:active#015#012a=fingerprint:sha-1 B0:27:8A:76:DE:C4:2A:18:7D:C9:32:F6:78:79:5E:7B:1D:7C:DB:68#015#012a=ice-ufrag:joFSF896#015#012a=ice-pwd:AMtcYr30DYw7PhCsz1LU1Eoi12#015#012a=candidate:MmPVRTRG ... May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... 3mIW6Esg 1 UDP 2130706431 <sip-proxy-rtpengine-ip> 8028 typ host#015#012", "result": "ok" } May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8012] SRTP output wanted, but no crypto suite was negotiated May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Triggering check for MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] ICE pair MmPVRTRG3mIW6Esg:2466368666:1 has been nominated by peer May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] ICE not completed yet May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Triggering check for MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from <sip-proxy-rtpengine-ip> to 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Received ICE/STUN response code 0 for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from 93.106.207.11:35551 to <sip-proxy-rtpengine-ip> May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Setting ICE candidate pair MmPVRTRG3mIW6Esg:2466368666:1 as succeeded May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Best succeeded ICE pair with all components is MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] ICE completed, using pair MmPVRTRG3mIW6Esg:2466368666:1 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Received ICE/STUN response code 0 for candidate pair MmPVRTRG3mIW6Esg:2466368666:1 from 93.106.207.11:35551 to <sip-proxy-rtpengine-ip> May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS: Peer certificate accepted May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS handshake successful May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS-SRTP successfully negotiated May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, incoming: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key jZlg8WlCjfEiFoilpz7BQg== salt gUcb/yOXBOIuNY1ItSw= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, outgoing: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key e3hQ8pCcc04HD8I7KWdl/g== salt mrNX5VDOk0+Tif2xv5I= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] DTLS-SRTP successfully negotiated May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, incoming: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key jZlg8WlCjfEiFoilpz7BQg== salt gUcb/yOXBOIuNY1ItSw= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] SRTP keys, outgoing: May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] --- AES_CM_128_HMAC_SHA1_32 key e3hQ8pCcc04HD8I7KWdl/g== salt mrNX5VDOk0+Tif2xv5I= May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:37 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:37 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:37 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8012] Confirmed peer address as <sip-proxy-rtpengine-ip>:8064 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Confirmed peer address as 93.106.207.11:35551 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Kernelizing media stream May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8012] Kernelizing media stream May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:38 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:39 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:39 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:40 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:40 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:40 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:41 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:41 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:42 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:42 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:43 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:43 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:43 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:44 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:44 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:45 box proxy_monitor[24109]: SIP test succeeded with proxy 192.98.100.34! May 18 11:47:45 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:45 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:46 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:46 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:46 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:47 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:47 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:48 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:48 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:49 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:49 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:50 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:50 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:51 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:51 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:52 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:52 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:53 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:53 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:54 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:54 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:55 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:55 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:55 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:56 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:56 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:57 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:57 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:58 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:58 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:59 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:47:59 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Sending ICE/STUN request for candidate pair MmPVRTRG3mIW6Esg:1603072777:1 from <sip-proxy-rtpengine-ip> to 192.168.43.146:35551 May 18 11:47:59 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:00 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:00 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:01 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:01 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:02 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:02 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:03 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:03 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:04 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:04 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:05 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:05 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:07 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:07 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:07 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:08 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:08 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:09 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:09 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:10 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:10 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:11 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:11 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:12 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:12 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:13 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:13 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:14 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:14 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:15 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:15 box proxy_monitor[24109]: SIP test succeeded with proxy 192.98.100.34! May 18 11:48:15 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:16 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:16 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:17 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:17 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:18 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:18 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:19 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:19 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:20 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:20 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:20 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:21 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:21 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:22 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:22 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:23 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:23 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:24 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:24 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:25 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u/0m9av72lp5/1] Setting ICE candidate pair MmPVRTRG3mIW6Esg:1603072777:1 as failed May 18 11:48:25 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:25 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:26 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:26 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:27 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:27 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:28 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:28 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:29 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:29 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:30 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:30 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:31 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:31 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:32 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:32 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:32 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:33 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:33 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:34 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:35 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u port 8028] Successful STUN binding request from 93.106.207.11:35551 May 18 11:48:36 box /usr/bin/sip-proxy[18297]: INFO: ===== rtpengine_delete(via-branch=1) May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Received command 'delete' from 127.0.0.1:60722 May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Dump for 'delete' from 127.0.0.1:60722: { "call-id": "e91aj9gq39qr07b6dn6u", "via-branch": "z9hG4bK3605983", "received-from": [ "IP4", "<sip-proxy-rtpengine-ip>" ], "from-tag": "0m9av72lp5", "command": "delete" } May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Scheduling deletion of call branch '0m9av72lp5' in 30 seconds May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Replying to 'delete' from 127.0.0.1:60722 May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Response dump for 'delete' to 127.0.0.1:60722: { "created": 1431938854, "last signal": 1431938854, "tags": { "0m9av72lp5": { "tag": "0m9av72lp5", "created": 1431938854, "in dialogue with": "627A71DC-5559A726000163C1-AA759700", "medias": [ { "index": 1, "type": "audio", "protocol": "UDP/TLS/RTP/SAVPF", "streams": [ { "local port": 8028, "endpoint": { "family": "IPv4", "address": "93.106.207.11", "port": 35551 }, "advertised endpoint": { "family": "IPv4", "address": "93.106.207.11", "port": 35551 ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... }, "crypto suite": "AES_CM_128_HMAC_SHA1_32", "last packet": 1431938916, "flags": [ "RTP", "RTCP", "filled", "confirmed", "kernelized", "DTLS fingerprint verified" ], "stats": { "packets": 3084, "bytes": 540700, "errors": 0 } }, { "local port": 8029, "endpoint": { "family": "IPv6", "address": "::", "port": 0 }, "advertised endpoint": { "family": "IPv6", "address": "::", "port": 0 }, "crypto suite": "AES_CM_128_HMAC_SHA1_32", "last packet": 1431938854, "flags": [ "RTCP", "fallback RTCP", "filled" ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... ], "stats": { "packets": 0, "bytes": 0, "errors": 0 } } ], "flags": [ "initialized", "send", "recv", "rtcp-mux", "DTLS-SRTP", "DTLS role active", "ICE" ] } ] }, "627A71DC-5559A726000163C1-AA759700": { "tag": "627A71DC-5559A726000163C1-AA759700", "created": 1431938854, "in dialogue with": "0m9av72lp5", "medias": [ { "index": 1, "type": "audio", "protocol": "RTP/AVP", "streams": [ { "local port": 8012, "endpoint": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8064 }, "advertised endpoin ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... t": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8064 }, "last packet": 1431938916, "flags": [ "RTP", "filled", "confirmed", "kernelized" ], "stats": { "packets": 3095, "bytes": 533040, "errors": 0 } }, { "local port": 8013, "endpoint": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8065 }, "advertised endpoint": { "family": "IPv4", "address": "<sip-proxy-rtpengine-ip>", "port": 8065 }, "last packet": 1431938854, "flags": [ "RTCP", "filled" ], "stats": { "packets": 0, "bytes": 0, "error ... May 18 11:48:36 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ... s": 0 } } ], "flags": [ "initialized", "send", "recv" ] } ] } }, "totals": { "RTP": { "packets": 6179, "bytes": 1073740, "errors": 0 }, "RTCP": { "packets": 0, "bytes": 0, "errors": 0 } }, "result": "ok" } May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Call branch '0m9av72lp5' deleted, no more branches remaining May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] Final packet stats: May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --- Tag '627A71DC-5559A726000163C1-AA759700', created 1:32 ago, in dialogue with '0m9av72lp5' May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ------ Media #1 (audio over RTP/AVP) using PCMU/8000 May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --------- Port 8012 <> <sip-proxy-rtpengine-ip>:8064 , 3110 p, 535620 b, 0 e, 1431938917 last_packet May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --------- Port 8013 <> <sip-proxy-rtpengine-ip>:8065 (RTCP), 0 p, 0 b, 0 e, 1431938854 last_packet May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --- Tag '0m9av72lp5', created 1:32 ago, in dialogue with '627A71DC-5559A726000163C1-AA759700' May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] ------ Media #1 (audio over UDP/TLS/RTP/SAVPF) using PCMU/8000 May 18 11:49:06 box rtpengine[4025]: [e91aj9gq39qr07b6dn6u] --------- Port 8028 <> 93.106.207.11:35551, 3101 p, 543584 b, 0 e, 1431938917 last_packet [View Less]

1 1

Issue with Asterisk interconnection for VoiceMail
by Igor Potjevlesch 18 May '15

18 May '15

Hello, I experienced a strange issue with some of VoIP accounts. When the INVITE comes into MANAGE_FAILURE, after timeout, the config identifies, with "dialplan", the right Asterisk instance that should handle the call for voicemail. This part is okay, and results in a new INVITE with the Request-URI formed with the right domain (eg. sip: <sip:%3cNUMBER%3e@asterisk3> <NUMBER>@asterisk3). Then, the request goes to RELAY. Here is the issue: sometimes, the request is … [View More]forwarded to the IP of the UA (the one initially contacted) instead of the IP of Asterisk. I can't figure out the difference between a succeeded call and a failed one. If someone has an idea. Here is the config that handles the VoiceMail: failure_route[MANAGE_FAILURE] { [.] if (isflagset(24)) { $avp(s:inv_timeout) = "5"; t_set_fr($avp(s:inv_timeout)*1000); if (avp_db_load("$to/username","$avp(s:vm_uri)/usr_vm")) { resetflag(24); avp_pushto("$ruri","$avp(s:vm_uri)"); # Dynamic routing if (avp_db_load("$ruri/username","$avp(s:client)/usr_fai")) { if (dp_translate("2","$avp(s:client)/$avp(s:dest)") == 1) { $ru = "sip:" + $rU + "@" + $avp(s:dest); } else { # Load default voicemail $avp(s:client) = "DEFAULT_VM"; dp_translate("2","$avp(s:client)/$avp(s:dest)"); $ru = "sip:" + $rU + "@" + $avp(s:dest); }; } else { # Load default voicemail $avp(s:client) = "DEFAULT_VM"; dp_translate("2","$avp(s:client)/$avp(s:dest)"); $ru = "sip:" + $rU + "@" + $avp(s:dest); } } else { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], User have no mail box\n"); exit; }; prefix("710"); xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], failure route to Voice Mail\n"); route(RELAY); exit; } Regards, Igor. [View Less]

3 5

dbtext why is my user not recognised
by jaflong jaflong 18 May '15

18 May '15

cat > /usr/local/etc/kamailio/dbtext/subscriber username(str) password(str) ha1(str) domain(str) ha1b(str) user1:user1:xxx:10.1.1.1:xxx 9350) DEBUG: auth_db [authorize.c:498]: auth_check(): realm [10.31.8.1] table [subscriber] flags [1] 2(9350) DEBUG: auth [api.c:96]: pre_auth(): auth: digest-algo: MD5 parsed value: 1 2(9350) DEBUG: db_text [dbt_file.c:102]: dbt_load_file(): request for table [subscriber] 2(9350) DEBUG: db_text [dbt_file.c:109]: dbt_load_file(): db is [/usr/local/etc/… [View More]

1 1

Setting up a presence AS with Kamailio IMS.
by Mihail Dakov 18 May '15

18 May '15

Hi all, I have successfully setup a Kamailio IMS environment using just a single machine running three kamailio instances. I am using kamailio 4.2.4 compiling it myself. I followed this guide: http://nil.uniza.sk/instant-messaging/simple/configuring-im-and-presence-ka… to setup a presence AS using the scscf instance. I used kamdbctl script to create the presence tables with one inconsistence with the guide. I had to create a db in which I created a couple of columns (table_name, … [View More]

1 0

critical crash with dbtext
by jaflong jaflong 18 May '15

18 May '15

HI When using dbtext setup I receive a CRITICAL error and shut down. This is the debug log. My config settings are described below. Please advise how I should fo the correct dbtext config 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): acc 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): auth_db 9(21196) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-4): debugger 9(… [View More]21196) DEBUG: debugger [debugger_mod.c:179]: child_init(): rank is (-4) 9(21196) DEBUG: <core> [local_timer.c:74]: init_local_timer(): init_local_timer: timer_list between 0x9e7268 and 0xa2b268 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 8, 4, 0x7f5aaa402364), fd_no=0 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 9, 4, 0x7f5aaa4023f0), fd_no=1 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 10, 4, 0x7f5aaa40247c), fd_no=2 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 11, 4, 0x7f5aaa402508), fd_no=3 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 12, 4, 0x7f5aaa402594), fd_no=4 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 13, 4, 0x7f5aaa402620), fd_no=5 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 14, 4, 0x7f5aaa4026ac), fd_no=6 9(21196) DEBUG: <core> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9e70a0, 15, 4, 0x7f5aaa402738), fd_no=7 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 8 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 1, pid 21188 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 8, -1, 0x0) fd_no=8 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 9 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 2, pid 21189 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 9, -1, 0x0) fd_no=7 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 10 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 3, pid 21190 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 10, -1, 0x0) fd_no=6 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 11 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 4, pid 21191 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 11, -1, 0x0) fd_no=5 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 12 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 5, pid 21192 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 12, -1, 0x0) fd_no=4 called 9(21196) CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 13 9(21196) DEBUG: <core> [tcp_main.c:3537]: handle_ser_child(): DBG: handle_ser_child: dead child 6, pid 21193 (shutting down?) 9(21196) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0x9e70a0, 13, -1, 0x0) fd_no=3 called 8(21195) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/dbtext 8(21195) DEBUG: db_text [dbt_lib.c:129]: dbt_cache_get_db(): looking for db /usr/local/etc/kamailio/dbtext! 8(21195) DEBUG: db_text [dbt_lib.c:139]: dbt_cache_get_db(): db already cached! 8(21195) DEBUG: <core> [sruid.c:101]: sruid_init(): root for sruid is [ulcx-5555c137-52cb-] (0 / 19) 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): acc 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): auth_db 8(21195) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/dbtext 8(21195) DEBUG: db_text [dbt_lib.c:129]: dbt_cache_get_db(): looking for db /usr/local/etc/kamailio/dbtext! 8(21195) DEBUG: db_text [dbt_lib.c:139]: dbt_cache_get_db(): db already cached! 8(21195) DEBUG: <core> [sr_module.c:920]: init_mod_child(): DEBUG: init_mod_child (-2): debugger 8(21195) DEBUG: debugger [debugger_mod.c:179]: child_init(): rank is (-2) 8(21195) DEBUG: ctl [ctl.c:325]: mod_child(): ctl: mod_child(0), fork_process=0, csl=0x2682080 8(21195) DEBUG: ctl [ctl.c:332]: mod_child(): ctl: 0 io_listen_loop(1, 0x2682080) 8(21195) INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 8(21195) DEBUG: ctl [io_listener.c:257]: io_listen_loop(): io_listen_loop: adding socket 4, type 2, transport 3 (/tmp/kamailio_ctl) 8(21195) DEBUG: ctl [../../io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x7f5aaf2a36c0, 4, 2, 0x2682080), fd_no=0 --------------------------------------------- cd /usr/local/etc/kamailio mkdir dbtext cd dbtext --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/version table_name(str) table_version(int) subscriber:6 location:6 aliases:6 --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/location username(str) contact(str) expires(int) q(double) callid(str) cseq(int) --------------------------------------------- cat > /usr/local/etc/kamailio/dbtext/subscriber username(str) password(str) ha1(str) domain(str) ha1b(str) testuser:testuser:xxx:10.1.1.5:xxx --------------------------------------------- #!define DBURL "text:///usr/local/etc/kamailio/dbtext" #!endif --------------------------------------------- # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) #!endif # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) --------------------------------------------- [View Less]

2 3

Repeated 200 OK from Enswitch
by Darren Campbell (Primar) 18 May '15

18 May '15

Hi all Experiencing a commonly reported issue where calls drop out after 30 seconds or so. Mainly because the provider hangs up after not recognising/receiving ACK in response to 200 OK. Unfortunately (or maybe fortunately), I haven't had much experience with Enswitch so was hoping someone in the community might help guide me as to which rules Enswitch might be using to match ACKs to calls in progress. Maybe there is another avenue I should be investigating. Here's a sample of the 200 OK … [View More]

2 8

RADIUS Digest Problem
by Sanaii, Maziar 18 May '15

18 May '15

Hello there, I'm trying to configure Kamailio 4.2.4 to authenticate client REGISTERs against a test FreeRADIUS on the localhost, however I have yet to succeed. My installation includes Kamailio 4.2.4, radiusclient 1.1.6, FreeRADIUS 2.2.5 and all of them on a Debian 8.0 machine. I believe I have got all the configurations correct in kamailio.cfg, radiusclient.conf, radius servers file, and freeradius server since the communication between the components are ok. My problem is that when I use … [View More]

2 1

XLOG To STDERR Not Working
by Nahum Nir 18 May '15

18 May '15

Hi All, I am using Kamailio 4.0.3 and can't logs. .cfg: #!define WITH_DEBUG ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 When the server starts there outputs about xlog: 0(20266) DEBUG: <core> [cfg.y:1791]: yyparse(): loading module xlog.so 0(20266) DEBUG: <core> [sr_module.c:499]: load_module(): load_module: module file not found </usr/… [View More]local/lib/kamailio/modules_k/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:522]: load_module(): load_module: module file not found </usr/local/lib/kamailio/modules_k/xlog/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:564]: load_module(): load_module: trying to load </usr/lib64/kamailio/modules/xlog.so> 0(20266) DEBUG: <core> [sr_module.c:343]: register_module(): register PV from: xlog 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xlog> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20266) DEBUG: <core> [sr_module.c:674]: find_mod_export_record(): find_export_record: found <xdbg> in module xlog [/usr/lib64/kamailio/modules/xlog.so] 0(20268) DEBUG: <core> [sr_module.c:935]: init_mod(): DEBUG: init_mod: xlog 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() 0(20268) DEBUG: <core> [route.c:928]: fix_actions(): fixing xlog() At the beginning of the Main routing block I put: log("~~~~~~~~~~~~route~~~~~~~~~~~~~~~~~~~~\n"); xdbg("~~~~~~~~~ xdbg - route~~~~~~~~~~~~~~~~~~~~\n"); xlog("L_ALERT","~~~~~~~~~ xlog - route~~~~~~~~~~~~~~~~~~~~\n"); But nothing is logging when I send INVITEs Any help? Thanks, Nir [View Less]

2 1

How to Change IP on Kamailio
by Mudasar Choudhary 18 May '15

18 May '15

Hi, Hope you are doing fine. Can you please assist me how can I change the IP for Kamailio. Right now its up on this IP: loading modules under /usr/lib/kamailio/modulesListing onudp: 98.212.180.96 [98.212.180.96] :5060tcp: 192.168.18.99 [192.168.18.99] :8888 I want to change both upd and tcp. Please advise. ThanksMudasar

2 1

Kamailio Load balancing multiple asterisk boxes
by Eric Koome 15 May '15

15 May '15

Hi I have two boxes with internal and external interfaces. Each has Kamailio at the public interface and asterisk on the internal one. Making calls within a box is fine but would like to load balance using the other asterisk box. However using dispatcher I have noticed packets are not being routed from Kamailo to the second asterisk. Packets from Kamailo are originating from the external interface and sent to the second asterisk box using private ip address. Off course this is not routable. … [View More]

2 1

misc_radius and auth_radius configuration question
by Yasin CANER 15 May '15

15 May '15

Hello; i am testing to radius modules. i have found this tutorial http://www.kamailio.org/docs/openser-radius-1.0.x.html . it is old but i changed some variables. i configured radiusclient-ng and free radius. But kamailio cann't start because of 0(17813) ERROR: misc_radius [misc_radius.c:208]: mod_init(): misc_radius: can't get code for the SIP-AVP attribute 0(17813) ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module misc_radius (/usr/local/… [View More]lib64/kamailio/modules/misc_radius.so) i already defined SIP-AVP in dictionary.kamailio. And when i set radius_config in misc_radius , it try to find in default path (/usr/local/etc/radiusclient-ng). So i linked to path /usr/local/etc/radiusclient-ng to solve this problem. ---- kamailio V 4.2.4 ---- ------------------dictionary.kamailio------------ #### Attributes ### ATTRIBUTE Sip-Method 101 integer # Schulzrinne, acc ATTRIBUTE Sip-Response-Code 102 integer # Schulzrinne, acc ATTRIBUTE Sip-Cseq 103 string # Schulzrinne, acc ATTRIBUTE Sip-To-Tag 104 string # Schulzrinne, acc ATTRIBUTE Sip-From-Tag 105 string # Schulzrinne, acc ATTRIBUTE Sip-Translated-Request-URI 107 string # Proprietary, acc ATTRIBUTE Sip-Src-IP 108 string # Proprietary, acc ATTRIBUTE Sip-Src-Port 109 string # Proprietary, acc ATTRIBUTE Digest-Response 206 string # Sterman, auth_radius ATTRIBUTE Sip-Uri-User 208 string # Proprietary, auth_radius ATTRIBUTE Sip-Group 211 string # Proprietary, group_radius ATTRIBUTE Sip-Rpid 213 string # Proprietary, auth_radius ATTRIBUTE SIP-AVP 225 string # Proprietary, avp_radius ATTRIBUTE Digest-Realm 1063 string # Sterman, auth_radius ATTRIBUTE Digest-Nonce 1064 string # Sterman, auth_radius ATTRIBUTE Digest-Method 1065 string # Sterman, auth_radius ATTRIBUTE Digest-URI 1066 string # Sterman, auth_radius ATTRIBUTE Digest-QOP 1067 string # Sterman, auth_radius ATTRIBUTE Digest-Algorithm 1068 string # Sterman, auth_radius ATTRIBUTE Digest-Body-Digest 1069 string # Sterman, auth_radius ATTRIBUTE Digest-CNonce 1070 string # Sterman, auth_radius ATTRIBUTE Digest-Nonce-Count 1071 string # Sterman, auth_radius ATTRIBUTE Digest-User-Name 1072 string # Sterman, auth_radius ### Acct-Status-Type Values ### #VALUE Acct-Status-Type Start 1 # RFC2866, acc #VALUE Acct-Status-Type Stop 2 # RFC2866, acc #VALUE Acct-Status-Type Failed 15 # RFC2866, acc ### Service-Type Values ### #VALUE Service-Type Call-Check 10 # RFC2865, uri_radius VALUE Service-Type Group-Check 12 # Proprietary, group_radius ##VALUE Service-Type Sip-Session 15 # Schulzrinne, acc, auth_radius VALUE Service-Type SIP-Caller-AVPs 30 # Proprietary, avp_radius VALUE Service-Type SIP-Callee-AVPs 31 # Proprietary, avp_radius ### Sip-Method Values ### VALUE Sip-Method Undefined 0 VALUE Sip-Method Invite 1 VALUE Sip-Method Cancel 2 VALUE Sip-Method Ack 4 VALUE Sip-Method Bye 8 VALUE Sip-Method Info 16 VALUE Sip-Method Options 32 VALUE Sip-Method Update 64 VALUE Sip-Method Register 128 VALUE Sip-Method Message 256 VALUE Sip-Method Subscribe 512 VALUE Sip-Method Notify 1024 VALUE Sip-Method Prack 2048 VALUE Sip-Method Refer 4096 VALUE Sip-Method Other 8192 ---------------------------Kamailio.cfg-------------------------------------------------------- #modparam("acc", "log_flag", FLT_ACC) modparam("acc_radius", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp") modparam("acc_radius", "radius_config","/etc/radiusclient-ng/radiusclient.conf") modparam("acc_radius", "radius_flag", FLT_ACC) modparam("acc_radius", "radius_missed_flag", FLT_ACCMISSED) modparam("acc_radius", "service_type", 15) modparam("misc_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("misc_radius", "group_service_type", 12) modparam("misc_radius", "uri_service_type", 10) modparam("misc_radius", "caller_extra", "Calling-Station-Id=$fu") modparam("misc_radius", "callee_extra", "SIP-URI-User=$rU;SIP-URI-Host=$rd") modparam("misc_radius", "group_extra", "My-Special=$avp(i:100)") modparam("misc_radius", "uri_extra", "Called-Station-Id=$tu") ------------------------------------------------------------------------------------------------ Thanks [View Less]

3 6

t_lookup_request()
by Alex Balashov 13 May '15

13 May '15

Hello, From the documentation for t_lookup_request()[1], it is not clear whether it creates a new transaction if one does not exist: "Checks if a transaction exists. Returns a positive value if so, negative otherwise. Most likely you will not want to use it, as a typical application of a look-up is to introduce a new transaction if none was found. However this is safely (atomically) done using t_newtran." This language is quite unclear in the following respects: 1) … [View More]

2 1

how to delete key from htable?
by Juha Heinanen 13 May '15

13 May '15

there exists rpc command htable.delete that can be used to delete a key from htable. is there a way to delete a key in the config file like assigning $null to it or do i need to use sht_rm_name_re function that feels like an overkill? -- juha

2 4

Kamailio-4.1.5 memory leak
by Bui Minh Yen 13 May '15

13 May '15

Hi everyone, I am using Kamailio-4.1.5. Sometime kamailio was crash because memory leak. Log when out of mem May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1332]: new_t(): ERROR: new_t: out of mem: May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed May … [View More] 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [ucontact.c:103]: new_ucontact(): no more shm memory May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:155]: mem_insert_ucontact(): failed to create new contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:547]: insert_ucontact(): failed to insert contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: registrar [save.c:708]: update_contacts(): failed to insert contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1332]: new_t(): ERROR: new_t: out of mem: May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: tm [t_lookup.c:1472]: t_newtran(): ERROR: t_newtran: new_t failed May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [ucontact.c:103]: new_ucontact(): no more shm memory May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:155]: mem_insert_ucontact(): failed to create new contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: usrloc [urecord.c:547]: insert_ucontact(): failed to insert contact May 2 09:49:00 vnpsip01 /usr/local/sbin/kamailio[30821]: ERROR: registrar [save.c:521]: insert_contacts(): failed to insert contact Log when kamailio was crash May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30818]: ALERT: <core> [main.c:775]: handle_sigs(): child process 30821 exited by a signal 11 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30818]: ALERT: <core> [main.c:778]: handle_sigs(): core was not generated May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30818]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: used= 1110960, used+overhead=1663384, free=748068456 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30828]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 2. N address=0x7f6af599dae8 frag=0x7f6af599dab8 size=176 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: counters.c: cnt_hash_add(339) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 3. N address=0x7f6af599dbf8 frag=0x7f6af599dbc8 size=240 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: counters.c: cnt_hash_add(339) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 4. N address=0x7f6af599dd48 frag=0x7f6af599dd18 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: counters.c: init_counters(129) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 5. N address=0x7f6af599de28 frag=0x7f6af599ddf8 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: modparam.c: set_mod_param_regex(124) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 6. N address=0x7f6af599de98 frag=0x7f6af599de68 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 7. N address=0x7f6af599df78 frag=0x7f6af599df48 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: route_add(159) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 8. N address=0x7f6af599e008 frag=0x7f6af599dfd8 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: init_rlist(181) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 9. N address=0x7f6af599e078 frag=0x7f6af599e048 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 10. N address=0x7f6af599e158 frag=0x7f6af599e128 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: route_add(159) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 11. N address=0x7f6af599e1e8 frag=0x7f6af599e1b8 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: init_rlist(181) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 12. N address=0x7f6af599e258 frag=0x7f6af599e228 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 13. N address=0x7f6af599e338 frag=0x7f6af599e308 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: route_add(159) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 14. N address=0x7f6af599e3c8 frag=0x7f6af599e398 size=16 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: route.c: init_rlist(181) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 15. N address=0x7f6af599e438 frag=0x7f6af599e408 size=128 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: used= 1110768, used+overhead=1663192, free=748068648 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30833]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30827]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30828]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: used= 1110768, used+overhead=1663192, free=748068648 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30828]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: heap size= 749731840 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: used= 1110768, used+overhead=1663192, free=748068648 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: max used (+overhead)= 1825240 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: dumping all alloc'ed. fragments: May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: 0. N address=0x7f6af599d528 frag=0x7f6af599d4f8 size=1024 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: alloc'd from <core>: str_hash.h: str_hash_alloc(69) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30834]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: 2. N address=0x7f6af599dae8 frag=0x7f6af599dab8 size=176 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30830]: NOTICE: qm_status: alloc'd from <core>: counters.c: cnt_hash_add(339) May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: start check=f0f0f0f0, end check= c0c0c0c0, abcdefed May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30832]: NOTICE: qm_status: 1. N address=0x7f6af599d988 frag=0x7f6af599d958 size=256 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30834]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30823]: NOTICE: qm_status: 16. N address=0x7f6af599e518 frag=0x7f6af599e4e8 size=48 used=1 May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30834]: NOTICE: qm_status: (0x7f6af5968010): May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30822]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 2 10:50:41 vnpsip01 /usr/local/sbin/kamailio[30822]: NOTICE: <core> [main.c:852]: sig_usr(): Memory status (pkg): Could you help me to fix this problem! Thanks so much! -- --------------------------- *Bui Thi Minh Yen* [View Less]

2 5

Memory leak or bad setting.
by Kjeld Flarup 13 May '15

13 May '15

Hello We experienced a failure on our kamailio (4.2.1+trusty), which required a restart. May 6 07:40:41 rtpproxy01 /usr/sbin/kamailio[5467]: ERROR: <core> [msg_translator.c:2270]: generate_res_buf_from_sip_res(): out of mem Afterwards we inspected all the settings to be using default, but at a much higher level than an other older kamailio which runs much more traffic. The big difference, is that this kamailio works with rtpengine. Does that require more memory? We also observed that … [View More]the free memory is constantly falling on some instances. They all started with 16MB but after 1½ day some are on 11.6 Is this normal behaviour that will find a natural level or is there something bad going on? We can also see that there are frags. Is that to be worried about, or is this natural? kamcmd pkg.stats | egrep -e 'free|frag' free: 16362760 total_frags: 17 free: 15835176 total_frags: 232 free: 15845760 total_frags: 205 free: 15829288 total_frags: 188 free: 15847456 total_frags: 181 free: 15853024 total_frags: 183 free: 15873232 total_frags: 225 free: 15858584 total_frags: 231 free: 15834592 total_frags: 205 free: 15852520 total_frags: 132 free: 15869048 total_frags: 120 free: 15824872 total_frags: 100 free: 15828448 total_frags: 113 free: 15858216 total_frags: 109 free: 15861992 total_frags: 82 free: 15871712 total_frags: 110 free: 15813824 total_frags: 109 free: 11583736 total_frags: 121 free: 11588896 total_frags: 106 free: 11580448 total_frags: 118 free: 11586312 total_frags: 134 free: 11592840 total_frags: 159 free: 11632536 total_frags: 120 free: 11582368 total_frags: 127 free: 11660104 total_frags: 97 free: 16352192 total_frags: 14 free: 16351088 total_frags: 13 free: 16341248 total_frags: 46 free: 16351184 total_frags: 19 We use 4.2.1+trusty with these modules, is it possible that a newer version has fixed some memory leak? loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "mi_rpc.so" loadmodule "acc.so" loadmodule "dispatcher.so" loadmodule "permissions.so" loadmodule "sdpops.so" loadmodule "rtpengine.so" -- Med venlig hilsen / Best regards Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef Viptel ApS, Benslehøjvej 3, DK-7470 Karup J Telefon: +45 46949949, Telefax: +45 46949950, http://viptel.dk [View Less]

2 3

Multi-homed Kamailio Modifies ACK
by SamyGo 13 May '15

13 May '15

Hi all, I'm having a scenario where I'm sending call to CISCO IAD2431. The call establishes with 200OK from CISCO and Kamailio sends back modified ACK. Cisco at this points gives out an error and sends 200OK again, Kamailio replies with ACK, and this cycle goes on until the call drops. Here is the error from CISCO: Failed FROM/TO Request check old_from: "Test Phone" <sip:+14432232221@192.168.1.106>;tag=as370915fc old_to: <sip:+14444812211@sip.iamip.com:5041>;tag=9FEC572E-… [View More]

2 3

kamailio slow/no response for requests on particular ports
by Karthik Srinivasan 12 May '15

12 May '15

Hi, I have encountered an issue with kamailio and am hoping someone on this email distro can help: Here's my setup and description of the issue: I am running kamailio version 3.1.4. I have the kamailio process bound to ports 5060, 5070, and 5090. all UDP. I have several client devices registering to the kamailio registrar. The issue I have encountered is this: SIP registrations to port 5070 are fine for a period of time; by fine I mean clients send SIP registration requests to kamailio;… [View More] and kamailio responds promptly to the request. by period of time I mean (this could be somewhat random) that for10 hours; 12 hours; 1 hour; that kamailo has no issue processing requests. after this random time period has elapsed, kamailo isn't able to respond to sip registrations and other messages in timely manner; to the point where the clients timeout and have to resend their registration requests. at times, kamailio does respond to the requests (with a significant delay) and at other times no response is received by the client. the user experience is intermittent registration delays/failures. The same behavior is seen on port 5090. I have not encountered the issue yet on port 5060. During times when kamailio isn't able to respond timely to requests on a particular port, requests to other ports are responded to timely. for ex: if port 5070 encounters the issue; port 5060 and 5090 seem fine. meaning, I can point my client devices to 5060 or 5090 and kamailio processes the requests timely. I have studied a tcp dump on the server end (kamailio side) and noticed that the network layer shows the messages from the client to be received timely while kamailio is encountering this issue. which indicates to me that it probably isn't a network lag related issue. Something at the application layer is probably causing kamailio to not respond timely. Furthermore the issue resolves itself after a period of time; that is, kamailio begins to respond to messages timely on the problematic port. I haven't had a chance yet to determine exactly how long it takes to recover. it certainly takes some time though. at least 30 minutes; maybe more. I can also state that the load on the kamailio system is minimal. far below than what the performance metrics state it can handle. Has anyone encountered this issue where kamalio isn't responding to registration and other requests timely on a particular port but does so fine for other ports? Any help on this would be appreciated. Thanks, Karthik [View Less]

2 5

Ims_charging lose all charging information when restart
by Yasin CANER 12 May '15

12 May '15

3 4

DMQ htable replication issue.
by José Seabra 12 May '15

12 May '15

Hello there, I'm using DMQ module to replicate an htable between several kamailio servers, what i'm noticing is that DMQ is sending the information from one server to another, but the htable name is not the same, for example: The original htable name is $sht(fscache=>queue:2), this htable is replicated to another server and the name (queue:2) will be replaced to some random value like this: $sht(fscache=>3c34e55ae6f9-rsf8qhhwntvw) What happens is that the other server cannot get the … [View More]

3 7

Handling 407 Proxy Authentication, Elastix MT
by Darren Campbell (Primar) 12 May '15

12 May '15

Hi all Have Asterisk listening on 127.0.0.1 and aiming to route all inbound/outbound SIP via Kamailio listening on 127.0.0.1 and external interface. Inbound calls from the SIP PROVIDER work just fine. Have NAT, rtpproxy configured for successful registration and subsequent INVITEs etc. Experiencing some challenges with the outgoing INVITES, primarily authenticating the outbound INVITEs. The current situation is this: Asterisk > INVITE > Kamailio > INVITE > SIP PROVIDER SIP … [View More]

2 8

Media Proxy and STUN
by Nahum Nir 11 May '15

11 May '15

Hi All, After reading the docs I got that it is possible to configure the server so it will change the SDP so clients will send the media to the media proxy. But, what if the clients are not behind a symmetric NAT and using ICE where able to get their real IP:port? How can the server be aware to this and not change the SDP? Thanks, Nir

2 1

Kamailio authentication method
by Mathys Frédéric 10 May '15

10 May '15

Hello, In my scenario with a Kamailio server, I have a VOIP client connecting to the server which, for some reasons, cannot calculate MD5 hashes but only SHA. In this situation, would it be possible to change the authentication algorithm by either modifying Kamailio scripts or writing an external module to do that? As far as I know, the authentication response is calculated as follow (standard HTTP Digest authentication) : HA1=MD5(username:realm:password) HA2=MD5(method:digestURI) response=… [View More]

3 6

Diameter message AAR/AAA
by Ramjee Yadav 10 May '15

10 May '15

Dear, With changes incorporate in kamalio.cfg, I am able to REGISTER 200 ok with Rx interface. But I want to send AAR message only after receiving 200 ok at pcscf. Currently message sequences are CER -------> <-------CEA AAR ---------> <------AAA REGISTER---> <-------401 REGISTER----> <----200 ok Screen shot is attached for reference. But I want to Send AAR/AAA only after 200 ok. Below is the Sequence CER -------> <-------CEA REGISTER---&… [View More]

1 0

Recommended configuration for TCP support
by Mickael Marrache 08 May '15

08 May '15

Hi, We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP. What is the recommended configuration when TCP is used? Currently, I only have the following: children=16 listen=udp:<ip>:5060 listen=tcp:<ip>:5060 disable_tcp=no tcp_connection_lifetime=605 (registration expiry is 600) Also, is there a difference with UDP regarding NAT handling? Thanks, Mickael

3 7

db_text error
by jaflong jaflong 08 May '15

08 May '15

db_text error I am getting the following error on using db_text 0(6638) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/ 0(6638) ERROR: db_text [dbt_base.c:207]: dbt_query(): table version not loaded! (too few columns) 0(6638) ERROR: db_text [dbt_base.c:306]: dbt_query(): failed to query the table! I have thisin my kamailio.cfg #!define DBURL "text:///usr/local/etc/kamailio/dbtext" I created the following files cat > /usr/local/etc/kamailio/… [View More]

2 3

Timer Process versus Slow Timer Process
by Mack Hendricks 08 May '15

08 May '15

Hi All, I'm looking to have a better understanding of when to use the Timer process versus the "Slow Timer" Process. This is what I came up with, but please correct me: - The “*Timer*” process is used to handle core processing within Kamailio. Therefore, you don’t want to put long running logic into the routing handler - The “*Slow Timer*” process can be used for long running processes

2 1

kamailio V 4.2.4 IMS_Charging ro_session_timeout question
by Yasin CANER 08 May '15

08 May '15

Hello; i am trying to understand how is ims_charging working . Kamailio is a S-CSCF here. kamailio and call dont have a problem but ro_session. i always get ro_session_ontimeout() ERROR. when look diameter trace , ims_charging module dont request for 30 more sec for granted and kill dialog. Thanks for helps. 14:22:51 S-CSCF ----->CC-Time 15 .. Sec CCR ---> Java-Diamaeter Server (INITIAL REQ) 14:22:51 S-CSCF <-----CC-Time 15 .. Sec CCA <--- Java-Diamaeter … [View More]

3 2

Make deb
by jay binks 07 May '15

07 May '15

is there any way to make deb packages for only 1 of the modules ?? currently it takes a long time to run "make deb" im simply trying to build and package db_cassandra ( need the package for my environment ) As a side note, is there any chance db_cassandra could be added to the kamailio deb packages ? -- Sincerely Jay

4 12

permissions module, regular expression matching Request URI
by Vik Killa 07 May '15

07 May '15

Hello, We would like to match specific calls based on two factors: 1. the source IP address 2. the Request URI I see in the permissions module, it is possible to match based on the Source IP + the From URI. We need two match both in order to return the appropriate 'tag' attribute from table. Would anyone know of a way to accomplish this? Also, I noticed that matching source IP + from uri, you cannot control which result is returned by permissions module based on regular expression. In other … [View More]

3 3

db_mongodb get columns error
by Mickael Marrache 07 May '15

07 May '15

Hi, After restarting Kamailio, I got the following errors during the startup: kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [caller_sock] not found in result iterator kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:927]: … [View More]

2 4

TCP connection reset by peer
by Mickael Marrache 07 May '15

07 May '15

Hi, I sometimes see the following in the logs: kamailio[14433]: ERROR: <core> [tcp_read.c:271]: tcp_read_data(): error reading: Connection reset by peer (104) kamailio[14433]: ERROR: <core> [tcp_read.c:1296]: tcp_read_req(): ERROR: tcp_read_req: error reading It looks like Kamailio tries to read a request from a TCP socket but the connection has been reset (not properly ended) by the remote peer. Is it an error? Does it prevent Kamailio from working properly? If yes,… [View More]

2 1

RFC: Config files installation
by Daniel-Constantin Mierla 06 May '15

06 May '15

Hello, cross posting to get heads up of everyone that wants to join the discussion, however, do reply to sr-dev(a)lists.sip-router.org, being more related to development and project files structure. At this moment we install three kamailio configuration files: - kamailio.cfg - the default one to be used when starting kamailio - kamailio-basic.cfg - a more simple version of configuration - kamailio-advanced.cfg - a more complex version (equivalent of kamailio-oob.cfg in etc/ source tree) … [View More]

1 0

Re: [SR-Users] issue with TLS and 2 NIC interfaces
by Slava Bendersky 06 May '15

06 May '15

Hello Vik, I don't have same problem it works fine for me, but I have same setup on public side where multiply aliases on interface is involved. Slava. From: "Vik Killa" <vipkilla(a)gmail.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Monday, May 4, 2015 12:54:21 PM Subject: Re: [SR-Users] issue with TLS and 2 NIC interfaces Are you having the same problem as myself? Thanks, V On Fri, May 1, 2015 at 8:20 PM, Slava Bendersky < volga629(a)networklab.ca &… [View More]

3 3

Strange behavior for TCP and UDP SIP Routing
by Grant Bagdasarian 06 May '15

06 May '15

Hello, I have a Kamailio machine configured with two interfaces. One public, one private. Public Address: 10.10.10.10 Private Address: 192.168.1.10 Kamailio forwards the SIP packet to another local endpoint: 192.168.1.20 When a client sends a SIP packet using TCP to the public address of Kamailio, Kamailio relays the packet using its private interface (private address) to the other endpoint. TCP: Client -> 10.10.10.10 -> 192.168.1.10 -> 192.18.1.20 When a client sends a SIP packet … [View More]

2 2

rtpengine, turn fallback
by Isuru Wijesinghe 06 May '15

06 May '15

Hi All I'm using rtpengine to in my implementation of webrtc. In my client side browser I have used following code snippet to configure stun/turn servers to identify ice candidates and turn fall back. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> var pcConfig = {"iceServers": [ {'url': 'turn:52.6.57.126:3478?transport=tcp'}]}; … [View More]

2 1

Double record routes
by Mickael Marrache 06 May '15

06 May '15

Hi, We are adding TCP support to our load balancer and for some reason it adds two record route headers. The instance have two IP addresses on which it binds: one if the VIP address and the second is the non-VIP address. I explicitly set the tcp_source_ipv4 parameter with the VIP address so that it is used as source address for outbound TCP connection. So, we get the following INVITE going from the load balancer to a proxy: T 2015/05/05 12:08:49.715822 VIP:54667 -> PROXY:… [View More]

3 5

sht_rm_name_re() question
by Yufei Tao 05 May '15

05 May '15

Hi I've hit a problem with sht_rm_name_re() in htable module. I was calling it like this: sht_rm_name_re("Dlg=>$var(callid)::tenant"); But when I used sipp to generate 600 concurrent calls for example, I called this function when receiving BYE. But it removed more entries than it should. Seems when removing removing some entry with callid 1-3798(a)192.168.60.80, it also removed entries for [1-9]1-3798(a)192.168.60.80. How do I add '^' in front and '$' at the end of the regexp string … [View More]

2 1

UAC not answer with new register after 401 reply from porvider
by Yuriy Gorlichenko 05 May '15

05 May '15

Hello. We have an issue with REGISTER to Provider. When Provider answers 401 Kamailio don't send any REGISTER with digest auth IP ourservice.com.5068 > provider.dev.5060: UDP, length 468 E...U...@.3' ..............AREGISTER sip:provider.dev SIP/2.0 Via: SIP/2.0/UDP ourservice.com:5068 ;branch=z9hG4bK4238.45a4a626000000000000000000000000.0 To: <sip:login@provider.dev> From: <sip:login@provider.dev>;tag=6a39af2190f8b2c99cc63bfeb3a3959c-1ff8 CSeq: 10 REGISTER Call-ID: … [View More]

2 3

Kamailio proxy for far-end nat traversal
by rahul.ultimate 05 May '15

05 May '15

Hello I need a small guidance on creating a light weight proxy which only forwards the msgs to my sip server and also does supports symmetrical nated clients. The way I have created the configuration is a slight modification of : https://github.com/xlab1/sipfe_kamailio/blob/master/kamailio.cfg Problem is unless the sip clients use STUN media packets are not routed. And sometimes even the signalling does not pass through. Should i not use fix_nated_register and switch to fix _ nated_contact … [View More]

2 1

Re: [SR-Users] issue with TLS and 2 NIC interfaces
by Slava Bendersky 04 May '15

04 May '15

Hello Vik, I have similar setup, try define you server configuration in tls.cfg [server:ip address of alias interface:port of alias interface] method = TLSv1 verify_certificate = no require_certificate = no private_key = certificate = ca_list = crl = Slava From: "Vik Killa" <vipkilla(a)gmail.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Wednesday, April 29, 2015 4:32:21 PM Subject: [SR-Users] issue with TLS and 2 NIC interfaces Hello, if i have … [View More]

2 1

kamcli - kamailio command line control tool
by Daniel-Constantin Mierla 04 May '15

04 May '15

Hello, we just published a new command line tool for Kamailio management, named now kamcli, available at: * https://github.com/asipto/kamcli It is written in Python and adapted from a tool provided originally by a subcontractor for a specific deployment. While not being Python developers here, the benefits and flexibility proved extremely good. At this stage it is more an attempt to see if the community finds it useful and worth to get it developed further as part of Kamailio project. … [View More]Short about the benefits/flexibility: - python is by default installed on OSes (including Mac OS X) (as opposite to Lua, for example) - became rather fast since Google invested in it - lot more knowledge base and developers out there (as opposite to Lua or Perl), along with tons of extensions - implementation is based on a CLI framework (Click) that makes it extremely easy to add new commands in a plugin-like fashion, therefore is easy to have custom commands when having specific needs (e.g., managing a custom database table used in kamailio.cfg via sqlops => add a new cmd_xyz.py in commands subfolder, without touching other files, not even the config) - help message is embedded in the command code file, making it easier to document commands - easy to validate parameters as well as format the output - handling kamcli configuration file options is also easy (ini format) One of my reasons of pushing this out was in the perspective of deprecating MI and working with JSONRPC fifo from command line -- I couldn't find easy ways to manage json docs with shell and common tools (e.g., cat, echo, grep, awk) only. Kamcli has implemented the JSONRPC over fifo command (see also jsonrpc-s kamailio module). Still, given the old initial implementation, at this moment, kamcli is relying on MI via fifo (mi_fifo) for some of the commands (e.g., dumping usrloc records from memory) -- (Just as side note: perhaps here we need to do a mapping, because name of commands are different, if we want to make a 'ctl transport agnostic' tool.) Here are few things to decide: - does it sound useful and are people finding it worth to develop it further? - what about the name, is it ok? Another one? If worth developing and deciding on the name, then the plan is to host the project on kamailio organization on github so each kamailio developer can code on it (it won't be inside kamailio source code tree, but a separate project inside same organization). So far, couple of commands were implemented when comparing with kamctl: - subscriber management (kamctl add/rm/passwd...) - user location management (kamctl ul ...) - database querying (kamctl db ...) - statistics (kamctl stats ...) - mi commands (kamctl mi ...) - jsonrpc commands (not in kamctl) While cross posted for the sake of getting the info to everyone in the community, let's have further discussions on sr-dev. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com [View Less]

2 1

TLSv1.2 and weak ciphers
by Attila Megyeri 04 May '15

04 May '15

Hi Daniel, Kamailio folks, We are trying to make our server more secure, but we have some issues. Right now, we have set the TLS method to method = TLSv1+ and cipher_list = HIGH The problem is, that there are still cipher suites offered which are not secure. E.g. If I check with the SSLLabs analizer, I see: This server supports anonymous (insecure) suites (see below for details). Grade set to F. Cipher Suites (SSL 3+ suites in server-preferred order; deprecated and SSL 2 suites always … [View More]at the end) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH 256 bits (eq. 3072 bits RSA) FS 256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 256 TLS_ECDH_anon_WITH_AES_256_CBC_SHA (0xc019) INSECURE 256 TLS_DH_anon_WITH_AES_256_GCM_SHA384 (0xa7) INSECURE 256 TLS_DH_anon_WITH_AES_256_CBC_SHA256 (0x6d) INSECURE 256 TLS_DH_anon_WITH_AES_256_CBC_SHA (0x3a) INSECURE 256 TLS_DH_anon_WITH_CAMELLIA_256_CBC_SHA (0x89) INSECURE 256 TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d) 256 TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d) 256 TLS_RSA_WITH_AES_256_CBC_SHA (0x35) 256 TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84) 256 TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (0xc012) ECDH 256 bits (eq. 3072 bits RSA) FS 112 TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x16) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 112 TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA (0xc017) INSECURE 112 TLS_DH_anon_WITH_3DES_EDE_CBC_SHA (0x1b) INSECURE 112 TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) 112 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH 256 bits (eq. 3072 bits RSA) FS 128 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x67) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x45) DH 3072 bits (p: 384, g: 1, Ys: 384) FS 128 TLS_ECDH_anon_WITH_AES_128_CBC_SHA (0xc018) INSECURE 128 TLS_DH_anon_WITH_AES_128_GCM_SHA256 (0xa6) INSECURE 128 TLS_DH_anon_WITH_AES_128_CBC_SHA256 (0x6c) INSECURE 128 TLS_DH_anon_WITH_AES_128_CBC_SHA (0x34) INSECURE 128 TLS_DH_anon_WITH_CAMELLIA_128_CBC_SHA (0x46) INSECURE 128 TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c) 128 TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c) 128 TLS_RSA_WITH_AES_128_CBC_SHA (0x2f) 128 TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x41) 128 How can we get rid of these _anon_ cipher suites? Thanks Attila [View Less]

1 1

Auth User & is_subscriber
by jay binks 04 May '15

04 May '15

Hey, from the examples it looks like the typical usage of is_subscriber is with $fu ( From User ), however im not 100% sure I want this. in-fact, I want it to be the Auth User that is used. After all if a call was Authed, then we authoritatively know what user it is, and I think this should be used over and above the from user ( which could even be set to caller Id in some cases ). Im having some trouble getting is_subscriber to work with the Auth user, does anyone have an example of this … [View More]

2 1

WebSocket data in TCP connection
by mayamatakeshi 04 May '15

04 May '15

Hello, about module websocket, is it possible to associate a value with the TCP connection and have this value readable when handling SIP requests on that connection?

1 4

Regd: Message Routing
by suryakiiran vanam 04 May '15

04 May '15

Hi Team, I am using Jitsi client with Kamailio. I was able to IM between the clients. How can I control the Message routing in Kamailio script. Please help me with any link. Regards, Surya.

2 1

WebRTC video calls
by Ivan Vujisic 04 May '15

04 May '15

I made successful audio calls from browser to browser using Asterisk 13.1 and SIPML5 browser phone. Asterisk can't manage WebRTC video calls due to lack of codec negotiation module, but I also faced RTP ports NAT traversal issue. To my understanding Kamailio is capable to resolve this. Can anybody confirm that he made successful browser to browser video calls with Kamailio sip proxy / registrar in front of Asterisk PBX. Also, any link to good tutorial or doc pages will be appreciated. … [View More]

2 1

UAC Module
by Ali Jibran 02 May '15

02 May '15

Hi all. I have this setup. Trunk--->Kamailio---->FreeSWITCH I have a trunk from a sip provided and registered successfully with the UAC module. Incoming is working fine. I need to make out going through kamailio too. I have it in the dialplan to forward the invite to kamailio from FreeSWITCH. I can see it the logs that it reaches kamailio. Now how do I make the call via the trunk? Basically this is what I'm trying to workout FS---->kamailio---->trunk. Any help will be much appreciated. Thanks. AJ

3 7

Re: [SR-Users] [SR_USers] Authenticate asterisk-kamailio
by Mauricio Tejeda 30 Apr '15

30 Apr '15

Hi. Asterisk users are fine. Register subscribers Kamailio is my problem. #!ifdef WITH_ASTERISK if (!auth_check("$fd", "sipusers", "1")) { ##### OK Asterisk Users are no problem #!else ##### But if the user is no asterisk , simply refuse registration, without Respect the jump to validate users Kamailio … [View More]

2 2

[SR_USers] Authenticate asterisk-kamailio
by Mauricio Tejeda 30 Apr '15

30 Apr '15

Hello All. My English is bad so I hope you can understand. I have been working with Kamailio some time, I following some of Guides of http://kb.asipto.com, http://saevolgo.blogspot.com and http://nil.uniza.sk. To Authenticate Asterisk sipusers I'm not have problems, but subscriber of Kamailio authenticate is my problem. Autenticate are denied to subscriber Kamailio. In spanish I can explain it better :-) best regards my Settings: ####################### # ----- … [View More]auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "load_credentials", "") #!ifdef WITH_ASTERISK modparam("auth_db", "user_column", "name") modparam("auth_db", "password_column", "sippasswd") modparam("auth_db", "db_url", DBASTURL) modparam("auth_db", "version_table", 0) #!else modparam("auth_db", "db_url", DBURL) modparam("auth_db", "password_column", "password") modparam("auth_db", "use_domain", MULTIDOMAIN) #!endif #################### #!ifdef WITH_AUTH #!ifdef WITH_ASTERISK # do not auth traffic from Asterisk - trusted! if(route(FROMASTERISK)) return; #!endif #!ifdef WITH_IPAUTH if((!is_method("REGISTER")) && allow_source_address()) { # source IP allowed return; } #!endif if (is_method("REGISTER") || from_uri==myself) { # authenticate requests #!ifdef WITH_ASTERISK if (!auth_check("$fd", "sipusers", "1")) { #### Aquí autentifica sin problemas en caso de ser un usuario asterisk #!else #### Pero hace caso omiso al switch. if (!auth_check("$fd", "subscriber", "1")) { #### No autentifica subscriber de la base de datos de kamailio #!endif auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } #!endif return; } ######################### DEBUG KAMAILIO Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request: Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <REGISTER> Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:192.168.65.132> Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=10 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [29]; uri=[sip:107@192.168.65.132] Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [107<sip:107@192.168.65.132>#015#012] Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d87543-733510592-1--d87543->; state=6 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg... Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [receive.c:197]: receive_msg(): preparing to run routing scripts... Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <1> <REGISTER> Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=306ac106 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=29 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: siputils [checks.c:103]: has_totag(): no totag Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=16161, isACK=0 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [192.168.65.132] == [192.168.65.132] Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [select.c:429]: run_select(): Calling SELECT 0x7f213171d950 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [select.c:429]: run_select(): Calling SELECT 0x7f21317216c0 Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: auth_db [authorize.c:498]: auth_check(): realm [192.168.65.132] table [sipusers] flags [1] Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: auth [api.c:86]: pre_auth(): auth:pre_auth: Credentials with realm '192.168.65.132' not found Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: auth_db [authorize.c:264]: digest_authenticate_hdr(): no credentials Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='192.168.65.132' Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest realm="192.168.65.132", nonce="VUDgjFVA32CFnv6lYnT/fxOzv3M7Mw7n"#015#012' Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) Apr 29 10:40:48 labkamailio kamailio[11304]: DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request: Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <REGISTER> Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:192.168.65.132> Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=10 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [29]; uri=[sip:107@192.168.65.132] Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [107<sip:107@192.168.65.132>#015#012] Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d87543-600273073-1--d87543->; state=6 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg... Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [receive.c:197]: receive_msg(): preparing to run routing scripts... Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <REGISTER> Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=306ac106 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=29 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: siputils [checks.c:103]: has_totag(): no totag Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=16158, isACK=0 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [192.168.65.132] == [192.168.65.132] Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [select.c:429]: run_select(): Calling SELECT 0x7f213171d950 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [select.c:429]: run_select(): Calling SELECT 0x7f21317216c0 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: auth_db [authorize.c:498]: auth_check(): realm [192.168.65.132] table [sipusers] flags [1] Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: auth [api.c:96]: pre_auth(): auth: digest-algo: MD5 parsed value: 1 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:118]: db_new_result(): allocate 56 bytes for result set at 0x7f213171c1a0 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: db_mysql [km_res.c:68]: db_mysql_get_columns(): 1 columns returned from the query Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:156]: db_allocate_columns(): allocate 8 bytes for result names at 0x7f21317236a8 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:167]: db_allocate_columns(): allocate 4 bytes for result types at 0x7f2131739f10 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: db_mysql [km_res.c:86]: db_mysql_get_columns(): allocate 16 bytes for RES_NAMES[0] at 0x7f21317605f8 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: db_mysql [km_res.c:93]: db_mysql_get_columns(): RES_NAMES(0x7f21317605f8)[0]=[sippasswd] Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: db_mysql [km_res.c:137]: db_mysql_get_columns(): use DB1_STRING result type Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: db_mysql [km_res.c:170]: db_mysql_convert_rows(): no rows returned from the query Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: auth_db [authorize.c:196]: get_ha1(): no result for user '107@' Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:81]: db_free_columns(): freeing 1 columns Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f21317605f8 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:94]: db_free_columns(): freeing result names at 0x7f21317236a8 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:99]: db_free_columns(): freeing result types at 0x7f2131739f10 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0x7f213171c1a0 Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='192.168.65.132' Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest realm="192.168.65.132", nonce="VUDgjFVA32CFnv6lYnT/fxOzv3M7Mw7n"#015#012' Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) Apr 29 10:40:48 labkamailio kamailio[11302]: DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up Ngrep sipusers asterisk U 192.168.65.1:6018 -> 192.168.65.132:5060 REGISTER sip:192.168.65.132 SIP/2.0. To: 101<sip:101@192.168.65.132>. From: 101<sip:101@192.168.65.132>;tag=622d132b. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-11473800-1--d87543-;rport. Call-ID: 45522f4e99747d39. CSeq: 1 REGISTER. Contact: <sip:101@192.168.65.1:6018>. Expires: 3600. Max-Forwards: 70. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 3004w stamp 16863. Content-Length: 0. . # U 192.168.65.132:5060 -> 192.168.65.1:6018 SIP/2.0 401 Unauthorized. To: 101<sip:101@192.168.65.132>;tag=65b56d053bca97da69d7accef5da903f.bfcc. From: 101<sip:101@192.168.65.132>;tag=622d132b. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-11473800-1--d87543-;rport=6018;recei ved=192.168.65.1. Call-ID: 45522f4e99747d39. CSeq: 1 REGISTER. WWW-Authenticate: Digest realm="192.168.65.132", nonce="VUDfOlVA3g5sSAKxFPg/zsB0qvueMh8Y". Server: kamailio (4.2.4 (x86_64/linux)). Content-Length: 0. . # U 192.168.65.1:6018 -> 192.168.65.132:5060 REGISTER sip:192.168.65.132 SIP/2.0. To: 101<sip:101@192.168.65.132>. From: 101<sip:101@192.168.65.132>;tag=622d132b. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-426128389-1--d87543-;rport. Call-ID: 45522f4e99747d39. CSeq: 2 REGISTER. Contact: <sip:101@192.168.65.1:6018>. Expires: 3600. Max-Forwards: 70. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 3004w stamp 16863. Authorization: Digest username="101",realm="192.168.65.132",nonce="VUDfOlVA3g5sSAKxFPg/zsB0qvueMh8 Y",uri="sip:192.168.65.132",response="792b60f48b2da3bb93f5d808fd87c09c",algo rithm=MD5. Content-Length: 0. . # U 192.168.65.132:5060 -> 192.168.65.1:6018 SIP/2.0 200 OK. To: 101<sip:101@192.168.65.132>;tag=65b56d053bca97da69d7accef5da903f.92bc. From: 101<sip:101@192.168.65.132>;tag=622d132b. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-426128389-1--d87543-;rport=6018;rece ived=192.168.65.1. Call-ID: 45522f4e99747d39. CSeq: 2 REGISTER. Contact: <sip:101@192.168.65.1:6018>;expires=3600. Server: kamailio (4.2.4 (x86_64/linux)). Content-Length: 0. Ngrep subscriber Kamailio U 192.168.65.1:6018 -> 192.168.65.132:5060 REGISTER sip:192.168.65.132 SIP/2.0. To: 107<sip:107@192.168.65.132>. From: 107<sip:107@192.168.65.132>;tag=7b070e2d. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-536609279-1--d87543-;rport. Call-ID: 77019a2d9e70df3f. CSeq: 1 REGISTER. Contact: <sip:107@192.168.65.1:6018>. Expires: 3600. Max-Forwards: 70. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 3004w stamp 16863. Content-Length: 0. . # U 192.168.65.132:5060 -> 192.168.65.1:6018 SIP/2.0 401 Unauthorized. To: 107<sip:107@192.168.65.132>;tag=65b56d053bca97da69d7accef5da903f.1c0e. From: 107<sip:107@192.168.65.132>;tag=7b070e2d. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-536609279-1--d87543-;rport=6018;rece ived=192.168.65.1. Call-ID: 77019a2d9e70df3f. CSeq: 1 REGISTER. WWW-Authenticate: Digest realm="192.168.65.132", nonce="VUDf21VA3q+Px29K8cRa5tWIadNTI5e6". Server: kamailio (4.2.4 (x86_64/linux)). Content-Length: 0. . # U 192.168.65.1:6018 -> 192.168.65.132:5060 REGISTER sip:192.168.65.132 SIP/2.0. To: 107<sip:107@192.168.65.132>. From: 107<sip:107@192.168.65.132>;tag=7b070e2d. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-1058472151-1--d87543-;rport. Call-ID: 77019a2d9e70df3f. CSeq: 2 REGISTER. Contact: <sip:107@192.168.65.1:6018>. Expires: 3600. Max-Forwards: 70. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 3004w stamp 16863. Authorization: Digest username="107",realm="192.168.65.132",nonce="VUDf21VA3q+Px29K8cRa5tWIadNTI5e 6",uri="sip:192.168.65.132",response="c9ca6eff16e3b661337b6d99d74027de",algo rithm=MD5. Content-Length: 0. . # U 192.168.65.132:5060 -> 192.168.65.1:6018 SIP/2.0 401 Unauthorized. To: 107<sip:107@192.168.65.132>;tag=65b56d053bca97da69d7accef5da903f.8cc0. From: 107<sip:107@192.168.65.132>;tag=7b070e2d. Via: SIP/2.0/UDP 192.168.65.1:6018;branch=z9hG4bK-d87543-1058472151-1--d87543-;rport=6018;rec eived=192.168.65.1. Call-ID: 77019a2d9e70df3f. CSeq: 2 REGISTER. WWW-Authenticate: Digest realm="192.168.65.132", nonce="VUDf21VA3q+Px29K8cRa5tWIadNTI5e6". Server: kamailio (4.2.4 (x86_64/linux)). Content-Length: 0. . [View Less]

2 2

Transaction good practices with t_relay t_newtran and t_release
by Dirk Teurlings - SIGNET B.V. 30 Apr '15

30 Apr '15

Hi, In our config we don't use presence, but I do have a question about transactions. We're using dialogs as well as transactions in the routing. To keep things simplyfied, let's assume we have the following stripped out route setup: request_route { if (is_method("CANCEL")) { if (t_check_trans()) { t_relay(); } exit; } # As stated in documentation, this call could stop further # routing from here on … [View More]

4 5

SIP INVITE and To Header
by Andres 30 Apr '15

30 Apr '15

I have a general question maybe somebody can help me out with. We have a new SIP Trunk setup with a provider. The SIP Trunk has a username of 'jane' and it handles 400 DIDs. When the incoming INVITE from the provider comes in, the URI in the Invite is the username of the trunk while the To header actually has the dialed number. As long as I can remember I have always seen the Invite as having the same URI as the To Header in the initial INVITE but not so here. 18:17:34.786 SIP.STACK … [View More]

2 4

Re: [SR-Users] sr-users Digest, Vol 119, Issue 28
by Yufei Tao 30 Apr '15

30 Apr '15

Hi I've realised that I should put '^' after "Dlg=>" (rather than before), i.e. sht_rm_name_re("Dlg=>^$var(callid)::tenant"); - this works. But it doesn't seem to like '$' at the end of the regexp - Kamailio failed to start up with error: "ERROR: htable [ht_var.c:176]: pv_parse_ht_name(): wrong format". Any way to use the end-of-line symbol? Cheers, Yufei > ------------------------------ > > Message: 10 > Date: Wed, 29 Apr 2015 18:01:26 +0100 > From: Yufei Tao <… [View More]

1 0

SBC and HA with Kamailio
by kai.ohnacker＠cbc.de 30 Apr '15

30 Apr '15

Hello, I'm new with Kamailio and have to do a research project with Kamailio server. My task is to realize a SIP infrastructure with NATing and a High Availability Cluster with two Kamailio server. For the NAT problem I found a solution with SEMS, but for security I need authentication on the SBC. I have no idea to synchronize the user authentication information from Kamailio to SEMS. Perhaps there is a more useful solution available? The SIP server is behind the NAT in a private network and … [View More]

2 1

NO VOICE AFTER MSILO
by sscc 30 Apr '15

30 Apr '15

hello i have configured msilo module successful but there isn't any voice with msilo. i debug and compare the call flow with and without msilo. with msilo in call flow it didn't follow to relay and consequently didnt activate rtpproxy befor the call is answered. due to which during call there isn't any voice. please help -- View this message in context: http://sip-router.1086192.n5.nabble.com/NO-VOICE-AFTER-MSILO-tp137429.html Sent from the Users mailing list archive at Nabble.com.

1 0

issue with TLS and 2 NIC interfaces
by Vik Killa 29 Apr '15

29 Apr '15

Hello, if i have two interfaces (eth0 and eth0:0) I set kamailio to listen to the IP on eth0:0 This works great except when I try using TLS, kamailio routes traffic from eth0:0 to eth0 then to correct destination It should be just doing eth0:0 -> correct destination If I use UDP/TCP I am not seeing this behavior. If I set kamailio to listen to eth0 and remove eth0;0, TLS works fine. I'm running kamailio compiled from source git master a few days ago. Is anyone else having this problem? I'… [View More]

1 0

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