- sr-users - kamailio.org

Logging All Transactions
by Ryan Brindley 26 Jan '15

26 Jan '15

I've been working to try to get kamailio (4.1) to log every transaction to file, but can't seem to do it -- or even get it to reliably log. What the heck am i missing? It seems Kamailio logs the first time i try it on a day, but then won't do it again no matter what variation of configs I try. Is it something wrongly configured with flatstore? Permission issues? Any help/leads/hunches are greatly appreciated. The following is my truncated test config #!KAMAILIO #!define DBURL "flatstore:/var/log/kamailio-acc" #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 (the config and load mod stuff) modparam("acc", "log_level", 1) modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_facility", "LOG_LOCAL2") #confirmed in Ubuntu rsyslog LOG_LOCAL2 is configured modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) modparam("acc", "db_url", DBURL) modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) request_route { (non-invite request stuff) setflag(FLT_ACC); setflag(FLT_ACCMISSED); setflag(FLT_ACCFAILED); send_reply("420", "Test"); exit; } Ryan Brindley

2 5

Need help on WebRTC with Kamailio as proxy
by Rahul MathuR 26 Jan '15

26 Jan '15

Hello, I am totally struck at a point while implementing Kamailio as proxy for WebRTC enabled UAC (Jssip). I am using Google's TURN server (rfc5766-turn-server for ICE/STUN). I am able to get to the point where the SIP server sends 183 session in progress to kamailio but after that I can only see - "STUN: using this candidate" "Successful STUN binding request from .." "SRTP output wanted, but no crypto suite was negotiated" a) What should I do to resolve this issue ? b) Why is that I never get 200 OK for the INVITE ? I am attaching the logfile & configs herewith. Can somebody please help me out here... -- Warm Regds. MathuRahul

4 6

Dialog variable lost in ACC
by Pars3c 26 Jan '15

26 Jan '15

Hi , I've updated kamailio from 4.1.4 to 4.1.7 and some times dialog variables are not writed on the db by the ACC module. The variable that is not writed ,is setted in the on reply route ,when it receive the 200ok and method is invite. If i come back to the 4.1.4 all is ok. If i patch kamailio 4.1.4 with the code "dialog: Set the dialog context on incoming replies" (commit:b12a01e553699786953ec601197669314bf414c7) sometime the variable are not writed. Any ideas? Thanks

2 3

Dialog module generates error since upgrade to 4.2.2
by Jan Hazenberg 26 Jan '15

26 Jan '15

Hi All, I'm running into a issue with the dialog module since the upgrade from 4.2.1 to 4.2.2. I use the dialog module to add extra vars to the cdr's generated by the ACC module. I use the following config: # ----- dialog params ----- modparam("dialog", "enable_stats", 1) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "dlg_flag", FLT_DLG) modparam("dialog", "rr_param", "did") modparam("dialog", "wait_ack", 1) # Create dialog if (method=="INVITE") { # Create Dialog dlg_manage(); # Add test dialog var $dlg_var(src_ua) = $hdr(User-Agent); } This seems to work fine on kamailio 4.2.1 but after the upgrade i see the following errors in the logs: Jan 22 13:16:57 sip /usr/sbin/kamailio[2773]: CRITICAL: dialog [dlg_hash.c:901]: log_next_state_dlg(): bogus event 6 in state 1 for dlg 0x7f2f0332ed40 [3693:11222] with clid '9192c5fc24627a14c2ec42f084a96587(a)192.168.149.126' and tags '4017642921' '' Jan 22 13:17:01 sip /usr/sbin/kamailio[2770]: CRITICAL: dialog [dlg_hash.c:901]: log_next_state_dlg(): bogus event 7 in state 1 for dlg 0x7f2f0332ed40 [3693:11222] with clid '9192c5fc24627a14c2ec42f084a96587(a)192.168.149.126' and tags '4017642921' '' If i'm correct "bogus event 6 in state 1" indicates that a ACK whas received while the dialog still was in unconfirmed state. Should i catch the 200 OK on the INVITE to update the dialog? Thanks, Jan Hazenberg

3 9

ims_charging module
by Shane Harrison 26 Jan '15

26 Jan '15

Hi all, I am exploring the use of the ims_charging module having set up a freediameter server (all very new to me). I have loaded and configured the dependencies i.e. cdp, dialog_ng, tm, cdp_avp but the startup gets stuck on: Jan 26 03:57:05 host-172-16-0-82 /usr/sbin/kamailio[2931]: ERROR: ims_charging [mod.c:269]: mod_init(): Could not import ul_register_ulcb Jan 26 03:57:05 host-172-16-0-82 /usr/sbin/kamailio[2931]: ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module ims_charging (/usr/lib64/kamailio/modules/ims_charging.so) The corresponding code in mod.c is: /*Register for callback of URECORD being deleted - so we can send a SAR*/ if (ul.register_ulcb == NULL) { LM_ERR("Could not import ul_register_ulcb\n"); return -1; } But unfortunately this doesn't mean much to me - what is a URECORD, what is a SAR? Any words of wisdom around what a "ul.register_ulcb" is about would be appreciated. Kind regards Shane Shane Harrison Senior Software Engineer Imagination Technologies NZ Limited Level 2 1 Market Grove Lower Hutt, 5010 New Zealand PO Box 30-449 Lower Hutt, 5040 New Zealand Phone: +64 4 890-3681 ext 3361

2 1

How to forward sip message "statefully" so that the dialogue is preserved
by aft 26 Jan '15

26 Jan '15

We want to implement the following topology : INVITE--->kamailio1-----forward--->kamailio2--->route[NATMANAGE]--->Next Sip endpoint Client <---- route[NATMANAGE]<--------kamailio1<------forward-----kamailio2<---- reply with SDP So the caller to callee will be processed by one kamailio and callee to caller will be processed by another kamailio. Both kamailio will be up with a public IP. How this can be achieved?

1 0

lookup_branches and rtpengine_manage
by Yuriy Gorlichenko 26 Jan '15

26 Jan '15

Hello. I need parallel forking calls with the same username. (Call to all contacts with name for example User123), my endpoints may be WebSocket based and standart UDP endpoints. And I use rtpengine_manage for nmanaging calls wor webphones and standart softh/hard phones. I get all contacts manually and than at the branch route set rtpengine_manage settings for every call. It works fine but it works for one kamailio server. When I use 2 kamailio servers as load balansers Server that handle call get all endpoints from location but call to only one, that registred only at ths server for example I call user123 I have 3 contacts user123(a)1.2.3.4 - was registered at kamailio 1 user123(a)3.2.1.4 - was registered at kamailio 2 user123(a)4.3.2.1 - was registered at kamailio 1 So if call goes through kamailio 1 it call only to user123(a)1.2.3.4 and user123(a)4.3.2.1 I use this settings for usrloc at 2 kamailios to share all table between 2 servers modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 3) modparam("usrloc", "user_column", "username") modparam("usrloc", "contact_column", "contact") modparam("usrloc", "expires_column", "expires") modparam("usrloc", "q_column", "q") modparam("usrloc", "callid_column", "callid") modparam("usrloc", "cseq_column", "cseq") modparam("usrloc", "methods_column", "methods") modparam("usrloc", "cflags_column", "cflags") modparam("usrloc", "user_agent_column", "user_agent") modparam("usrloc", "received_column", "received") modparam("usrloc", "socket_column", "socket") modparam("usrloc", "path_column", "path") modparam("usrloc", "ruid_column", "ruid") modparam("usrloc", "instance_column", "instance") modparam("usrloc", "use_domain", 1) and this code for calling them [GET_CONTACTS] { sql_query("ca", "select contact from location where username='$tU'", "ra"); xlog("rows: $dbr(ra=>rows) cols: $dbr(ra=>cols)\n"); if($dbr(ra=>rows)>0){ $var(i)=0; while($var(i)<$dbr(ra=>rows)){ xlog("L_INFO","SQL query return contact {$dbr(ra=>[$var(i),0])} for {$tU} at step {$var(i)}\n"); if ($dbr(ra=>[$var(i),0])=~"transport=ws"){ xlog("L_INFO", "This is a Websocket call to endpoint"); sql_pvquery("ca", "select received from location where contact='$dbr(ra=>[$var(i),0])'","$var(recieved)"); $du=$var(recieved); xlog("L_INFO","SQL query return recieved {$var(recieved)} for {$tU}. Destination is {$du}\n"); append_branch("sip:$tU@$(du{s.select,1,:})"); } else { xlog("L_INFO", "This is a classic UDP call to endpoint"); $var(recieved)=''; sql_pvquery("ca", "select received from location where contact='$dbr(ra=>[$var(i),0])'","$var(recieved)"); xlog("L_INFO", "SQL query return RECIEVED {$var(recieved)}"); if ($var(recieved)==0){ xlog("L_INFO", "Recieved string is EMPTY"); $du="sip:"+$(dbr(ra=>[$var(i),0]){s.select,1,@}); } else { xlog("L_INFO", "Recieved string is {$var(recieved)}"); $du=$var(recieved); } $var(UDP_contact)="sip:"+$(dbr(ra=>[$var(i),0]){s.select,1,@}); append_branch("sip:$tU@$(du{s.select,1,:})"); xlog("L_INFO","Classic Destination URI is {$dbr(ra=>[$var(i),0])} for {$tU}}. Destination is {$du}\n"); } $var(i) = $var(i) + 1; } } t_on_branch("1"); return; } } } branch_route[1]{ if($du=~"transport=ws"){ xlog("L_INFO","Websocket Branch is {$du} for {$tU}\n"); rtpengine_manage("internal extenal force trust-address replace-origin replace-session-connection ICE=force RTP/SAVPF"); t_on_reply("REPLY_FROM_WS"); } else{ xlog("L_INFO","UDP Branch is {$du)} for {$tU}\n"); rtpengine_manage("replace-origin replace-session-connection ICE=remove RTP/AVP"); t_on_reply("MANAGE_CLASSIC_REPLY"); } } When it try to branch endpoint without registration at server that handle call I get errors that tm module can not build Via header **via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found* *ERROR: <core> [msg_translator.c:1725]: build_req_buf_from_sip_req(): could not create Via header* *ERROR: <core> [forward.c:607]: forward_request(): ERROR: forward_request: building failed* * UDP calls get errors something like above (sorry than can not share error code, This situation not often). So I think I have this trouble because I use manually handling call and tried to substitute to lookup_branches function. but I have no Idea how to set rtpengine_manage paraments for each endpoint depending this is websocket or standart call. IF there is write problem for callings thhrough 2 kamailios as loadbalansers pleas let me know about how to set rtpengine_manage parametrs wor endpoints for every fork. If not- can you tell me how I can call to all endpoints endepending of registration server (kamailio 1 or 2). Thanks.

1 0

Re: [SR-Users] remote mysql server
by Slava Bendersky 25 Jan '15

25 Jan '15

Hello Everyone, Thank you for help, fixed by adding to dialog module parameters. modparam("dialog", "db_url", DBURL) Slava. From: "Carsten Bock" <carsten(a)ng-voice.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Sunday, January 25, 2015 8:36:52 AM Subject: Re: [SR-Users] remote mysql server Hi Slava, is most modules a default database connection is defined. Probably this is the case here. As this error is coming from the dialog module: Did you configure some sort of "db_mode"? e.g.: modparam("dialog", "db_mode", 1) Thanks, Carsten 2015-01-25 9:27 GMT+02:00 Slava Bendersky <volga629(a)skillsearch.ca>: > Hello Everyone, > > I am trying start kamailio 4.2 with remote mysql server and on debug I see > DEBUG: db_mysql [km_my_con.c:94]: db_mysql_new_connection(): opening > connection: mysql://xxxx:xxxx@localhost/kamailio > but in cfg defined actual mysql server ip and not localhost > > 0(28885) DEBUG: <core> [sr_module.c:695]: find_mod_export_record(): > find_export_record: found <db_bind_api> in module db_mysql > [/usr/lib64/kamailio/modules/db_mysql.so] > 0(28885) DEBUG: <core> [db.c:213]: db_bind_mod(): using db bind api for > db_mysql > 0(28885) DEBUG: <core> [db.c:318]: db_do_init2(): connection 0x7faca59eced8 > not found in pool > 0(28885) DEBUG: db_mysql [km_my_con.c:94]: db_mysql_new_connection(): > opening connection: mysql://xxxx:xxxx@localhost/kamailio > 0(28885) ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): > driver error: Can't connect to local MySQL server through socket > '/var/lib/mysql/mysql.sock' (2 "No such file or directory") > 0(28885) ERROR: <core> [db.c:322]: db_do_init2(): could not add connection > to the pool 0(28885) ERROR: dialog [dlg_db_handler.c:147]: init_dlg_db(): > unable to connect to the database > > > Slava. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:carsten@ng-voice.com Office +49 40 5247593-0 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users oon why I see in log connection attempt to localhost ? From: "Carsten Bock" <carsten(a)ng-voice.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Sunday, January 25, 2015 8:36:52 AM Subject: Re: [SR-Users] remote mysql server Hi Slava, is most modules a default database connection is defined. Probably this is the case here. As this error is coming from the dialog module: Did you configure some sort of "db_mode"? e.g.: modparam("dialog", "db_mode", 1) Thanks, Carsten 2015-01-25 9:27 GMT+02:00 Slava Bendersky <volga629(a)skillsearch.ca>: > Hello Everyone, > > I am trying start kamailio 4.2 with remote mysql server and on debug I see > DEBUG: db_mysql [km_my_con.c:94]: db_mysql_new_connection(): opening > connection: mysql://xxxx:xxxx@localhost/kamailio > but in cfg defined actual mysql server ip and not localhost > > 0(28885) DEBUG: <core> [sr_module.c:695]: find_mod_export_record(): > find_export_record: found <db_bind_api> in module db_mysql > [/usr/lib64/kamailio/modules/db_mysql.so] > 0(28885) DEBUG: <core> [db.c:213]: db_bind_mod(): using db bind api for > db_mysql > 0(28885) DEBUG: <core> [db.c:318]: db_do_init2(): connection 0x7faca59eced8 > not found in pool > 0(28885) DEBUG: db_mysql [km_my_con.c:94]: db_mysql_new_connection(): > opening connection: mysql://xxxx:xxxx@localhost/kamailio > 0(28885) ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): > driver error: Can't connect to local MySQL server through socket > '/var/lib/mysql/mysql.sock' (2 "No such file or directory") > 0(28885) ERROR: <core> [db.c:322]: db_do_init2(): could not add connection > to the pool 0(28885) ERROR: dialog [dlg_db_handler.c:147]: init_dlg_db(): > unable to connect to the database > > > Slava. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:carsten@ng-voice.com Office +49 40 5247593-0 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

1 0

remote mysql
by Slava Bendersky 25 Jan '15

25 Jan '15

Hello Everyone, I am trying start kamailio 4.2 with remote mysql server and on debug I see DEBUG: db_mysql [km_my_con.c:94]: db_mysql_new_connection(): opening connection: mysql://xxxx:xxxx@localhost/kamailio but in cfg defined actual mysql server ip and not localhost Any help thank you, Slava.

3 2

CDRs and MongoDB
by Mickael Marrache 25 Jan '15

25 Jan '15

Hi, Is it possible to write CDRs directly to MongoDB using the new db_mongodb module? modparam("acc", "db_url", DB_MONGO_URL) modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_extra", " . ") modparam("acc", "cdr_log_enable", 0) modparam("acc", "cdrs_table", "cdrs") In the acc module documentation, I found the following statement: Note that CDR generation does not involve any kind of database storage (yet). In order to persist the CDRs into a database you will have to set up an exterior process (i.e., a script living outside of Kamailio) and implement the storage task yourself. Thanks, Mickael

2 2

Wrong dialog selected in on_reply/failure route in case of spirals.
by Julia Boudniatsky 25 Jan '15

25 Jan '15

After kamailio upgrade from v3.3 to v4.1.7 in production ~5% of calls with spirals dialog are failed with wrong dialog variables in on-reply/failure routes. The problem has been reproduced in the LAB (load test generated by SIPP). Please see the attached file with debug3 log. Scenario: Proxy Location Kamailio P1 Nbr translation Redirect | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |------------------------------->| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |<-------------------------------| | | | | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |<-------------------------------| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |------------------------------->| | | | | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | |-------------------------------------------------------------->| | 100 Trying | | dlg 0x7f8f8504cda0 !!!!!!!! | | Call-ID:(5-8286@10.25.153.150)| |<--------------------------------------------------------------| | 301 Moved Permanently | | dlg 0x7f8f8504cda0 !!!!!!!! | | Call-ID:(5-8286@10.25.153.150)| |<--------------------------------------------------------------| | | Thank you, Julia.

2 11

mistakenly detected NAT in IPv6 setup
by Sebastian Damm 23 Jan '15

23 Jan '15

Hi, it looks to me that Kamailio detects NAT without NAT being there, when used in IPv6 scenarios. I have a register, which comes in like this: U 2015/01/23 11:42:31.013284 2a01:1234:123:1234::2:16732 -> 2001:9876:98:9876::aa01:5060 REGISTER sip:domain SIP/2.0 Via: SIP/2.0/UDP [2a01:1234:123:1234::2]:16732;branch=z9hG4bK45528eba After it has run through Kamailio, the packet is sent out like this: U 2015/01/23 11:42:31.015126 1.2.3.4:5060 -> 9.8.7.6:5060 REGISTER sip:domain SIP/2.0 Via: SIP/2.0/UDP 1.2.3.4;branch=z9hG4bK8d21.7fa5fb060c2acc9583f05a93b93f9873.0 Via: SIP/2.0/UDP [2a01:1234:123:1234::2]:16732;received=2A01:1234:123:1234:0:0:0:2;branch=z9hG4bK45528eba As far as I know, the received part should only get appended, if the source IP of the packet differs from the IP advertised in the topmost Via header. But to me it looks like it always gets appended. In just IPv4 scenarios, the received parameter only gets appended if a difference is detected. And if it gets appended, shouldn't the received parameter IP be in square brackets, too? Later on, we have something like this in our code: if(method=="REGISTER") { if (nat_uac_test("23")) { append_hf("X-nathint: nat\r\n"); force_rport(); if (!add_path_received()) { sl_send_reply("503", "Internal Path Error"); }; } else { if (!add_path()) { sl_send_reply("503", "Internal Path Error"); }; }; } In our code, Kamailio always jumps into the add_path_received() part, so I guess, NAT detection triggers. But why? And then the Path header appended looks like this: Path: <sip:1.2.3.4;lr;received=sip:2A01:1234:123:1234:0:0:0:2:16732> The path module probably doesn't know anything about IPv6, too, so the IP in the received parameter is not enclosed in square brackets. When using the Path header later to send packets to the client, Kamailio complains about a parse error for the destination URI again. I tried looking into the path module, but I guess my C skills aren't sufficient to submit a patch. Best regards, Sebastian

2 2

Siremis Installation Web Page NOT Displayed.
by Mahmoud Ramadan Ali 23 Jan '15

23 Jan '15

Hi Dears, I'm trying to install Siremis 4.1 on Debian and whenever i open the URL in IE i get location.href='$url'"; exit; } ?> and in Firefox i see <?php if(is_file(dirname(__FILE__).'/install.lock')){ include 'bin/_forward.php'; }else{ $script_name = $_SERVER['SCRIPT_NAME']; $url = str_replace("index.php","install/",$script_name); echo "<script>location.href='$url'</script>"; exit; } ?> I've verified the permissions of - siremis/log - siremis/session - siremis/files - siremis/themes/default/template/cpl files without success also no logs gets written to the logs file...please help to fix this issue... Thanks in advance

1 0

RFC: best way to create dialogs
by Klaus Darilion 22 Jan '15

22 Jan '15

Hi! I use the dialog module to count and limit concurrent calls per user. It worked fine with 4.1.7 but fails with 4.2.2. My config basically looks like: route{ ... dlg_manage() ... authentication (stateless replies + exit) ... t_on_reply() t_on_branch() ... t_relay() exit; } initial_cbs_inscript uses the default value 1. Using 4.1.7, after stateless reply+exit, Kamailio executes dialog callbacks and deletes the dialog: [dlg_var.c:55]: dlg_cfg_cb(): new dialog with no trasaction after config execution [dlg_hash.c:872]: dlg_unref(): unref dlg 0xb233c3a0 with 1 -> 1 [dlg_hash.c:872]: dlg_unref(): unref dlg 0xb233c3a0 with 1 -> 0 [dlg_hash.c:872]: dlg_unref(): ref <=0 for dialog 0xb233c3a0 [dlg_hash.c:355]: destroy_dlg(): destroying dialog 0xb233c3a0 (ref 0) With 4.2.2, after stateless reply+exit, Kamailio just exits without calling any dialog callback (to destroy the dialog) I think I could work around the problem by creating the transaction later. Here are some ideas and I would be happy about your comments and best practices. - set initial_cbs_inscript to 0 - call dlg_manage() just before t_relay - do not use dlg_manage() but use the dialog flag and set the flag somewhere before t_relay Finally, do t_on_reply() and t_on_branch() already create the transaction or is it created with t_relay()? Thanks Klaus

1 0

reINVITE with uac_req_send()
by Le Truong Giang 22 Jan '15

22 Jan '15

Hi ! I have the following simple scenario A <---> Kamailio <---> Asterisk <---> B now i'm trying to handle Timeout reply when B is unavailable. First i suspend transaction and wait for B available. i use uac_reg_send() to reINVITE B .The problem is when B available, it receive INVITE but A doesn't receive ACK therefore the call is incomplete I guess the reason is source IP in reINVITE is Kamailio's not A's IP, so ACK can't reach A. How can i set this source IP to A's IP ? Any idea is appreciated Thank you !

1 0

RedHat 7 packages issue
by Alberto Panizzo 22 Jan '15

22 Jan '15

Hi all, Thanks for your hard working on Kamailio! I was just trying to install kamailio 4.2.X on a RedHat 7 machine but I got checksum mismatch: I took the yum configuration from: http://rpm.kamailio.org/ [kamailio] name=RPMs for Kamailio on RHEL 7 type=rpm-md baseurl=http://rpm.kamailio.org/stable/RHEL_7/ gpgcheck=1 gpgkey=http://rpm.kamailio.org/stable/RHEL_7/repodata/repomd.xml.key enabled=1 Than started yum update $ sudo yum update Loaded plugins: amazon-id, rhui-lb kamailio | 1.2 kB 00:00:00 kamailio/primary FAILED ] 0.0 B/s | 0 B --:--:-- ETA http://rpm.kamailio.org/stable/RHEL_7/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum] 0.0 B/s | 0 B --:--:-- ETA Trying other mirror. kamailio/primary | 7.4 kB 00:00:00 http://rpm.kamailio.org/stable/RHEL_7/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum Trying other mirror. Indeed http://rpm.kamailio.org/stable/RHEL_7/repodata/repomd.xml says: <data type="primary"> <checksum type="sha">4cc322a95d4a978e383903feaf8fbbe8ccc2ff9e</checksum> <open-checksum type="sha">9fd04e59185a8e844133b834a662cae3cc0837b7</open-checksum> <location href="repodata/primary.xml.gz"/> <timestamp>1413465311</timestamp> <size>7344</size> <open-size>70829</open-size> </data> while http://rpm.kamailio.org/stable/RHEL_7/repodata/primary.xml.gz I can download is: $ ls -l primary.xml.gz -rw-rw-r-- 1 alberto alberto 7562 gen 22 10:58 primary.xml.gz $ shasum primary.xml.gz e8e052970984feb0cdb16b98f05aefc516295aba primary.xml.gz Do I have to switch to other repository? Thank you, Best Regards -- Alberto Panizzo CTO - Co-Founder Amarula Solutions BV Cruquiuskade 47 Amsterdam 1018 AM NL T. +31(0)851119171 F. +31(0)204106211 www.amarulasolutions.com

1 0

How to make presence module allocating an etag only for an initial Publish??
by Nuno Reis 21 Jan '15

21 Jan '15

Hello all. I've been testing presence module for a while and I do notice that presentity table grows endlessly over time. Each time a call is made a new record is added in presentity with a different etag. In documentation, namely developers guide we can read this: int etag_not_new; /* * 0 - the standard mechanism (allocating new etag for each Publish) * 1 - allocating an etag only for an initial Publish */ How can I tell the presence module in kamailio config to work using the second form of the above? Looking forward to hear from you. BR, -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* [image: Description: Description: WavecomSignature] <http://www.wavecom.pt/pt/wavecom/premios.php> [image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php>

2 2

Kamailio doesn't response to some INVITE packages
by Volkan Oransoy 21 Jan '15

21 Jan '15

Hi, My Kamailio box works very well for a year, in front of a Freeswitch box. Nowadays, some of my users live problems about receiving calls. But this problem occurs on a couple of specific users. %1 of users complain about it. When I capture the traffic, I see that, Kamailio receives an invite package from freeswitch but takes no action. Normally it should response with a 100 trying message. Here is the INVITE package. 1.2.3.6 is the Freeswitch box and 1.2.3.2 is the Kamailio box. I captured this package on Kamailio box. U 1.2.3.6:5060 -> 1.2.3.2:5060 INVITE sip:2000@test.example.net SIP/2.0. Via: SIP/2.0/UDP 1.2.3.6;rport;branch=z9hG4bKZU1Z76FvDZ26r. Route: <sip:1.2.3.2>;lr. Max-Forwards: 65. From: "908508850000" <sip:908508850000@test.example.net>;tag=KjcgDe0NyKN0B. To: <sip:2000@88.235.112.33:1028>. Call-ID: 72b344f4-1c09-1233-ad8d-0050568e9066. CSeq: 70585075 INVITE. Contact: <sip:mod_sofia@1.2.3.6:5060>. User-Agent: FreeSWITCH-mod_sofia/1.4.14+git~20141119T221113Z~ca1d990cfc~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: timer, path, replaces. Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Content-Type: application/sdp. Content-Disposition: session. Content-Length: 270. X-AUTH-IP: 159.253.40.138. X-BF-SRC: 2. X-FS-Support: update_display,send_info. Remote-Party-ID: "908508850000" <sip:908508850000@test.example.net >;party=calling;screen=yes;privacy=off. . v=0. o=FreeSWITCH 1421813895 1421813896 IN IP4 1.2.3.6. s=FreeSWITCH. c=IN IP4 1.2.3.6. t=0 0. m=audio 28384 RTP/AVP 3 8 0 101 13. a=rtpmap:3 GSM/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. I use standart location lookup and relay procedure in Kamailio default script. Is there anything wrong with this INVITE package and how can I trace this issue on Kamailio box? Thank you. /Volkan

3 3

FW: KAMAILIO IMS Questions
by Zaka Ul Isam 21 Jan '15

21 Jan '15

Hello Folks: Hope you can see this and share your ideas as to how to fix it? Thanks and regards, Zaka ________________________________________ From: Zaka Ul Isam Sent: Wednesday, January 21, 2015 12:20 PM To: Carsten Bock Cc: miconda(a)gmail.com Subject: RE: KAMAILIO IMS Questions hello All: First of all many thanks for your kind response. In fact my last few emails did not make it to the list (and nor bounced). It seems there is an error on the receiving mail server! However, I am regularly receiving list emails and can respond to threads but due to unknown reason, can not initiate a thread! Yes, it is an install from stable version source. Inorder to bouble check, we even compiled this module from source and copied to the kamailio modules folder replacing the actual module,but without luck! Please suggest the fix. Thanks and regards, Zaka ________________________________________ From: Carsten Bock [carsten(a)ng-voice.com] Sent: Wednesday, January 21, 2015 11:56 AM To: Zaka Ul Isam Cc: miconda(a)gmail.com Subject: Re: KAMAILIO IMS Questions Hi Zaka, please forward the request to the sr-users list, as neither me or Daniel provide direct support. How did you install Kamailio? Are you sure, that you have the SIP-Trace in (/usr/local/lib64/kamailio/modules/)? >From your log, i can see, that you did not install it from the Debian-Packages.... Thanks, Carsten 2015-01-21 12:17 GMT+02:00 Zaka Ul Isam <Zaka.Ul(a)albtelecom.al>: > Hi Gentlemen: > > Yet another stumbling block! > Now it is not setting module parameters or finding module <SIPTRACE> > The module is there, I have confirmed it. Below is the error log & relevant > code snippet: > > Error LOG > > kamailio -cf /usr/local/etc/kamailio/pcscf/kamailio.cfg > loading modules under config path: /usr/local/lib64/kamailio/modules/ > 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module > matching <siptrace> found > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 366, column 42: Can't set > module parameter > 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module > matching <siptrace> found > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 368, column 35: Can't set > module parameter > 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module > matching <siptrace> found > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 369, column 44: Can't set > module parameter > 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module > matching <siptrace> found > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 370, column 37: Can't set > module parameter > 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module > matching <siptrace> found > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 371, column 38: Can't set > module parameter > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 372, column 1: syntax error > 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file > /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 372, column 1: > ERROR: bad config file (7 errors) > 0(22035) WARNING: <core> [ppcfg.c:219]: pp_ifdef_level_check(): different > number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1 > [root@IMS-dta1 pcscf]# locate modparam.c > bash: locate: command not found > > Source File > > } > > regfree(&preg); > pkg_free(reg); > if (!mod_found) { > LM_ERR("No module matching <%s> found\n", regex); > return -4; > } > return 0; > } > > > Please advise! > > Kindest regards, > > Zaka > > > > ________________________________________ > From: Zaka Ul Isam > Sent: Friday, January 09, 2015 4:07 PM > To: Carsten Bock > Subject: RE: KAMAILIO IMS Questions > > > Hi Carsten: > > Thanks a lot for your quick response and elaboration. > > As regards HSS, for testbed, we plan to use FOKUS HSS, Hope it will serve > the purpose. Please note that in addition to DIALOG_NG old DIALOG Module was > also required! > > > Thanks again & regards, > > Zaka > > ________________________________________ > From: Carsten Bock [carsten(a)ng-voice.com] > Sent: Friday, January 09, 2015 3:05 PM > To: Zaka Ul Isam > Subject: Re: KAMAILIO IMS Questions > > Hi Zaka, > > Thanks :-) > > You questions: > 1) you should be able to start the three components with "kamailio -f > /path/to/kamailio.cfg". > > You may need to modify the following line: > # ------------------ module loading ---------------------------------- > mpath="/usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/" > > This defines, where Kamailio will find it's modules. After the > source-code install, this is probably not correct :-) > > 2) The PCRF (and the pcscf.xml-Configuration) is optional (this > functionality has to be enabled by enabling "WITH_RX" in the > configuration, otherwise the pcscf.xml is ignored) > > 3) I assume, you also installed FHoSS from source instead from the > Package? In any case, you need to edit the hibernate.properties (e.g. > /opt/FHoSS/deploy/hibernate.properties). > > Regarding the errors of the Webinterface: It doesn't matter, if it's > 32 or 64 bit. FHoSS and it's Webinterface are for showcase and > scientific work only, so i assume, that's fine (as long as it works). > In production environments, we use e.g. a Nokia Siemens HSS (if > already present, e.g. for the LTE access) or our own drop in > replacement (with a totally different interface). > > Kind regards, > Carsten > > 2015-01-08 15:27 GMT+01:00 Zaka Ul Isam <Zaka.Ul(a)albtelecom.al>: >> Hi, Carsten: >> >> Thanks for the informative posts and responses on IMS related topics. I >> was >> trying to configure based on your last post at: >> >> http://www.kamailio.org/wiki/tutorials/ims/installation-howto >> >> With respect to above, I have few questions: >> >> 1: If the Kamailio based IMS, compiled from source (not package manager >> install) and all components in one machine. How do we start different >> components? >> >> kamailio -f /PATH/TO/RESPECTIVE COMPONENTS EXECUTABLE (kamailio.cfg with >> an >> include file P/I/S-CSCF.CFG) >> >> 2: In case of P-CSCF there are three config files as well (.xml for >> Diameter >> interface). The latter has reference to PCRF PEER >> Is it must? as there is no corresponding DNS entry in >> Kamailio-IMS.DNSZONE file. >> 3: As regards FOKUS HSS, in order to adapt the config to our scenario, do >> we >> also need to edit FHOSS/hibernate.properties file? Besides, we have errors >> with HSS WEB interface on 64 bit machines. Is 32 bit architecture the >> recommended one for HSS? >> >> Thanking you in anticipation, >> >> Zaka >> >> >> >> >> ________________________________ >> >> Albtelecom & Eagle Mobile invite you to protect together the Environment. >> Please do not print the e-mail unless really necessary. >> >> Albtelecom & Eagle Mobile iu ftojnë të mbrojmë së bashku Mjedisin. Lutemi >> të >> mos e printoni këtë komunikim elektronik nëse nuk është vërtet i >> nevojshëm. >> >> ________________________________ >> >> This e-mail and any files transmitted with it are confidential and >> intended >> solely for the use of the addressee/s. If you are not the intended >> recipient >> you are hereby notified that any dissemination, forwarding, copying or use >> of any of the information is strictly prohibited. If you receive this >> e-mail >> in error, please notify the sender immediately and delete it! Albtelecom >> makes no warranty as to the accuracy or completeness of any information >> contained in this message and hereby excludes any liability of any kind >> for >> the information contained therein or for the information transmission, >> reception, storage or use of such in any way whatsoever. The opinions >> expressed in this message may belong to sender alone and may not >> necessarily >> reflect the opinions of Albtelecom. Albtelecom shall bear no liability for >> any loss or damage caused by software or e-mail viruses. >> >> Ky mesazh dhe çdo informacion i transmetuar në përmbajtje te këtij mesazhi >> është konfidencial dhe është i destinuar vetëm për marrësin e destinuar. >> Nëse nuk jeni marrësi i destinuar, Ju bëjmë me dije se çdo përhapje, >> transmetim, kopjim apo përdorim i çdo informacioni është i ndaluar. Nëse e >> merrni këtë mesazh gabimisht, ju lutem kontaktoni urgjentisht nisësin e >> tij >> dhe fshijeni atë. Albtelecom nuk jep asnjë garanci për saktësinë apo >> plotësinë e informacionit në përmbajtje të këtij mesazhi dhe nuk mban >> asnjë >> përgjegjësi për informacionin e përmbajtur, transmetimin, marrjen, >> ruajtjen >> apo përdorimin e tij në çfarëdolloj mënyre. Mendimet e shprehura në këtë >> mesazh mund t'i përkasin vetë nisësit dhe nuk mund të reflektojnë >> domosdoshmërisht qëndrimet e Albtelecom. Albtelecom nuk do të mbaje asnjë >> përgjegjësi për humbje ose dëme te shkaktuara nga programet apo viruset. > > > > -- > Carsten Bock > CEO (Geschäftsführer) > > ng-voice GmbH > Schomburgstr. 80 > D-22767 Hamburg / Germany > > http://www.ng-voice.com > mailto:carsten@ng-voice.com > > Office +49 40 5247593-0 > Fax +49 40 5247593-99 > > Sitz der Gesellschaft: Hamburg > Registergericht: Amtsgericht Hamburg, HRB 120189 > Geschäftsführer: Carsten Bock > Ust-ID: DE279344284 > > Hier finden Sie unsere handelsrechtlichen Pflichtangaben: > http://www.ng-voice.com/imprint/ > > ________________________________ > > This e-mail and any files transmitted with it are confidential and intended > solely for the use of the addressee/s. If you are not the intended recipient > you are hereby notified that any dissemination, forwarding, copying or use > of any of the information is strictly prohibited. If you receive this e-mail > in error, please notify the sender immediately and delete it! Albtelecom > makes no warranty as to the accuracy or completeness of any information > contained in this message and hereby excludes any liability of any kind for > the information contained therein or for the information transmission, > reception, storage or use of such in any way whatsoever. The opinions > expressed in this message may belong to sender alone and may not necessarily > reflect the opinions of Albtelecom. Albtelecom shall bear no liability for > any loss or damage caused by software or e-mail viruses. > > Ky mesazh dhe çdo informacion i transmetuar në përmbajtje te këtij mesazhi > është konfidencial dhe është i destinuar vetëm për marrësin e destinuar. > Nëse nuk jeni marrësi i destinuar, Ju bëjmë me dije se çdo përhapje, > transmetim, kopjim apo përdorim i çdo informacioni është i ndaluar. Nëse e > merrni këtë mesazh gabimisht, ju lutem kontaktoni urgjentisht nisësin e tij > dhe fshijeni atë. Albtelecom nuk jep asnjë garanci për saktësinë apo > plotësinë e informacionit në përmbajtje të këtij mesazhi dhe nuk mban asnjë > përgjegjësi për informacionin e përmbajtur, transmetimin, marrjen, ruajtjen > apo përdorimin e tij në çfarëdolloj mënyre. Mendimet e shprehura në këtë > mesazh mund t'i përkasin vetë nisësit dhe nuk mund të reflektojnë > domosdoshmërisht qëndrimet e Albtelecom. Albtelecom nuk do të mbaje asnjë > përgjegjësi për humbje ose dëme te shkaktuara nga programet apo viruset. -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:carsten@ng-voice.com Office +49 40 5247593-0 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ ________________________________ This e-mail and any files transmitted with it are confidential and intended solely for the use of the addressee/s. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited. If you receive this e-mail in error, please notify the sender immediately and delete it! Albtelecom makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message may belong to sender alone and may not necessarily reflect the opinions of Albtelecom. Albtelecom shall bear no liability for any loss or damage caused by software or e-mail viruses. Ky mesazh dhe çdo informacion i transmetuar në përmbajtje te këtij mesazhi është konfidencial dhe është i destinuar vetëm për marrësin e destinuar. Nëse nuk jeni marrësi i destinuar, Ju bëjmë me dije se çdo përhapje, transmetim, kopjim apo përdorim i çdo informacioni është i ndaluar. Nëse e merrni këtë mesazh gabimisht, ju lutem kontaktoni urgjentisht nisësin e tij dhe fshijeni atë. Albtelecom nuk jep asnjë garanci për saktësinë apo plotësinë e informacionit në përmbajtje të këtij mesazhi dhe nuk mban asnjë përgjegjësi për informacionin e përmbajtur, transmetimin, marrjen, ruajtjen apo përdorimin e tij në çfarëdolloj mënyre. Mendimet e shprehura në këtë mesazh mund t'i përkasin vetë nisësit dhe nuk mund të reflektojnë domosdoshmërisht qëndrimet e Albtelecom. Albtelecom nuk do të mbaje asnjë përgjegjësi për humbje ose dëme te shkaktuara nga programet apo viruset.

1 0

Kamailio doesn't response to some INVITE packages
by Volkan Oransoy 21 Jan '15

21 Jan '15

My Kamailio box works very well for a year, in front of a Freeswitch box. Nowadays, some of my users live problems about receiving calls. But this problem occurs on a couple of specific users. %1 of users complain about it. When I capture the traffic, I see that, Kamailio receives an invite package from freeswitch but takes no action. Normally it should response with a 100 trying message. Here is the INVITE package. 1.2.3.6 is the Freeswitch box and 1.2.3.2 is the Kamailio box. I captured this package on Kamailio box. U 1.2.3.6:5060 -> 1.2.3.2:5060 INVITE sip:2000@test.example.net SIP/2.0. Via: SIP/2.0/UDP 1.2.3.6;rport;branch=z9hG4bKZU1Z76FvDZ26r. Route: <sip:1.2.3.2>;lr. Max-Forwards: 65. From: "908508850000" <sip:908508850000@test.example.net>;tag=KjcgDe0NyKN0B. To: <sip:2000@88.235.112.33:1028>. Call-ID: 72b344f4-1c09-1233-ad8d-0050568e9066. CSeq: 70585075 INVITE. Contact: <sip:mod_sofia@1.2.3.6:5060>. User-Agent: FreeSWITCH-mod_sofia/1.4.14+git~20141119T221113Z~ca1d990cfc~64bit. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: timer, path, replaces. Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Content-Type: application/sdp. Content-Disposition: session. Content-Length: 270. X-AUTH-IP: 159.253.40.138. X-BF-SRC: 2. X-FS-Support: update_display,send_info. Remote-Party-ID: "908508850000" <sip:908508850000@test.example.net >;party=calling;screen=yes;privacy=off. . v=0. o=FreeSWITCH 1421813895 1421813896 IN IP4 1.2.3.6. s=FreeSWITCH. c=IN IP4 1.2.3.6. t=0 0. m=audio 28384 RTP/AVP 3 8 0 101 13. a=rtpmap:3 GSM/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. I use standart location lookup and relay procedure in Kamailio default script. Is there anything wrong with this INVITE package and how can I trace this issue on Kamailio box? Thank you.

1 0

Removing unwanted characters from From-header
by Sebastian Thörn 21 Jan '15

21 Jan '15

Hi, Hello! I'm having trouble with matching massages for some Patton equipment, from the looks of it, Patton don't like </> in headers. The initial INVITE from Patton is sent without </> in To and From-headers. In the logs from Patton I can see that it matches the "100 trying" that Kamailio sends back to it, and this message has To and From-headers without </>, but the "180 Ringing" and "200 OK" that Kamailio sends is not matched, and these two has </>. I would like to remove < and > in my onreply_route, how can I do this? Or does anyone have experience on how Patton matches messages? Br Sebastian Thörn

1 0

need some help please
by mail＠sathees.co.uk 20 Jan '15

20 Jan '15

Hi need some help please, kamailio v-4.2.2 asterisk 13.1 ;#### sip.conf [general] context=incoming calls allowguest=yes bindport=5080 bindaddr=192.168.1.77 rtcachefriends=yes [kamailio] type=friend host=192.168.1.77 port=5060 context=kamailio-trunk canreinvite=no insecure=port,invite dtmfmode=rfc2833 nat=force_rport,comedia qualify=yes i have followed this tutorial http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb My DDI provider sending call to ip address via DDNS. DDI à DDNS à kamailio & asterisk in one server [192.168.1.77]. kamailio passing DDI to asterisk, but its sending to wrong context. If any of the sip users is registered, the calls were sending to registered user context. If no sip user is online then calls has been send to kamailio-trunk. How can I get all DDI to kamailio-trunk? How can I solve this problem? Many thanks Sathees

3 2

OMA/RCS Presence compliance
by Osbun, Alex 20 Jan '15

20 Jan '15

Hello, Are the Kamailio presence modules (presence, xcap, pua, rls, etc.) RCS 5.X and OMA Presence Simple spec compliant. I found the following bullet from this announcement - http://www.kamailio.org/w/2012/09/kamailio-at-11-years/ * SIMPLE Presence & IM extensions – embedded XCAP server, MSRP relay, RLS full OMA/RCS extensions implementation, IMS registrar records replication, a.s.o. Does that mean that only the RLS functionality is fully OMA/RCS compliant? Thanks and I appreciate any guidance. Regards, Alex

2 1

dialog module shared memory
by Grant Bagdasarian 20 Jan '15

20 Jan '15

Hello, I'm using the dialog module to control the maximum number of calls allowed to be passed through. Is it possible to share the dialogs stored in memory with multiple instances of kamailio? So if both kamailio instances process calls, and the maximum is set to a global of 10, both combined should never let more than 10 calls through. Regards, Grant

4 8

PCSCF Installation got issues
by Sravana R 20 Jan '15

20 Jan '15

Hi, Downloaded Kamailio-4.2.1.tar.gz file from Kamailio.org site and compiled it on RHEL 6.2 server. Configured as per setup instruction given in attached document. While start pcscf, getting the following errors: Jan 20 01:25:17 localhost pcscf: INFO: <core> [ppcfg.c:80]: pp_subst_add(): ### added subst expression: /PORT/4060/ Jan 20 01:25:17 localhost pcscf: INFO: <core> [ppcfg.c:80]: pp_subst_add(): ### added subst expression: /NETWORKNAME/open-ims.test/ Jan 20 01:25:17 localhost pcscf: INFO: <core> [ppcfg.c:80]: pp_subst_add(): ### added subst expression: /HOSTNAME/pcscf.open-ims.test/ Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: path [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: path [path_mod.c:147]: mod_init(): outbound module not available Jan 20 01:25:17 localhost ./pcscf[4201]: ERROR: registrar [reg_mod.c:352]: mod_init(): can't bind usrloc Jan 20 01:25:17 localhost ./pcscf[4201]: ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module registrar (/usr/local/lib64/kamailio/modules/registrar.so) Please help us to resolve above issue. Thanks, Sravan. ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

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