Hi,
I have an inquiry on the licensing and terms and conditions for using
Kamailio to build my own application.
I want to use Kamailio to build my own Application Server.
I will write my own commercial application that will interact with Kamailio
using SEAS module, and I would like to know under which licensing scheme
will that fall, and what terms and conditions will apply?
Thank you in advance for your reply.
Ziad Habchi
Hello All,
I'm running Kamailio 4.0.2 on Ubuntu 12.04 (precise).
I have SIP messaging flowing nicely, with UACs registering via Kamailio (as a proxy) to a Registrar.
Now having problems trying to route messages via a Cisco router (12.4(25g)) using loose routing. The plan is to allow the router to see the SIP messaging but forward it to the original location.
RFC 3261 seems to cover this case in Section 16.6 part 6: "A proxy MAY have a local policy that mandates that a request visit a specific set of proxies before being delivered to the destination."
Cisco documentation (SIP Configuration Guide, Cisco IOS Release 12.4) states that it implements RFC 3261, including Loose-routing. However, from my observation the router doesn't like a request-URI with anything other than its own IP address (it returns 400 Bad Request - 'Invalid IP address'), but with any attempt to 'decorate' the URI with lr and/or maddr= parameters it returns 400 Bad Request - 'Malformed/Missing' URL. One of these messages is returned regardless of anything I've tried with Via, Record-Route or Route headers.
Desired behaviour is for the router to remain in the route-set. A different configuration has shown me that this will achieve the required outcome, the tricky part now is just getting that first request to route. I know several ways to make Kamailio send to the router, but the router is not behaving as I expect when I preload a route set (with Route: headers).
Recognising that this is probably more of a Cisco problem than Kamailio, can anyone confirm whether a Cisco router implements loose-routing when receiving messages, or only when sending?
Regards,
Dave.
Hello,
I am new user of Kamailio sip server. I am able install kamailio sip
server 4.0.2. Now I am trying modules also.
I need to make use of kamailio ims modules(Ims_cscf) so please help me
to install ims modules with kamailio server.
It will be more help full If details of step by step compilation from the
source code is given.
Thank you,
Kota.
in kamailio 4.0, what could cause these kind of error messages:
Aug 2 09:31:04 voip /usr/sbin/sip-proxy[1779]: ERROR: usrloc [ucontact.c:842]: db_update_ucontact_ruid(): updating record in database failed - empty ruid
Aug 2 09:31:04 voip /usr/sbin/sip-proxy[1779]: ERROR: usrloc [urecord.c:363]: wb_timer(): updating contact in db failed
Aug 2 09:32:04 voip /usr/sbin/sip-proxy[1779]: ERROR: usrloc [ucontact.c:842]: db_update_ucontact_ruid(): updating record in database failed - empty ruid
Aug 2 09:32:04 voip /usr/sbin/sip-proxy[1779]: ERROR: usrloc [urecord.c:363]: wb_timer(): updating contact in db failed
relevant usrloc params are:
modparam("usrloc", "db_mode", 1)
modparam("usrloc", "db_ops_ruid", 1)
modparam("usrloc", "db_check_update", 1)
modparam("usrloc", "timer_procs", 2)
how is it possible that ruid in memory record is empty?
when db_mode=1, why kamailio does try to update (rather than delete)
a record in database by timer?
-- juha
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to
sign in, when I do so , my registration is forwarded as per the trigger
point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is
mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
Thank you for your help
Ziad Habchi
Hi,
I installed kamailio v 3.1.6 rpm. I used the default configuration.
Kamailio started. I have two clients one is an android phone using native
sip client, and the other one x-lite. I can call x-lite to phone but not
the other way around. When I restarted kamailio, I can call phone to
x-lite but not the other way around. The first one I did when I restart
kamailio will be the only leg that will be working, then I have to restart
again if I want to do the reverse. Has anyone encountered this problem?
How do I fix it?
Thanks,
Jason
Hello,
Kamailio SIP Server v3.3.5 stable release is out.
This is a maintenance release of the previous stable branch, 3.3, that
includes fixes since release of v3.3.4. There is no change to database
schema or configuration language structure that you have to do on
installations of previous v3.3.x. Deployments running previous v3.x.x
versions are strongly recommended to be upgraded to v3.3.5.
For more details about version 3.3.5 (including links and hints to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2013/08/kamailio-v3-3-5-released/
Note that latest stable series is now 4.0.x, with upcoming v4.0.3 to be
released later this week.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi!
Does Kamailio has features of CCA for usage outside a compiled code
(cdp_avp)? There's a module *ims_ro_interface *listed at
http://www.kamailio.org/w/2013/05/ims-kamailio/#more-1664
What status does it have?
regards,
Alexey
Hello,
I'm adding some additional SIP headers to the INVITE received, but when I use the siptrace module to duplicate the messages to a capture server, the INVITE does not contain the additional headers.
I'm using a softphone to test my configuration, and it looks like Kamailio only sends the INVITE which is coming from the softphone to the capture server. When Kamailio relays the INVITE to its destination the headers are present.
Is there a way to duplicate the invite leaving kamailio to the capture server instead of the INVITE which is coming into kamailio? I already tried to put the sip_trace() function after the message is sent to its destination, but the extra headers didn't show up in the database.
Note, that I'm using the "X-" as a prefix.
Regards,
Grant
Dear All,
I am working on Kamailio (4.0.1) server with GUI package Siremis (4.0) of
it. I was successful in get through Calls and SMS features in our VoIP
phones using this kamailio sever. But i am encountering some issues related
to CDR data generation into mysql database.
I have activated WITH_ACCDB in kamailio cfg file.
Siremis is configured to kamailio DB properly as i am getting accounting
list in the siremis GUI well, but only the CDR data is not getting
reflecting in GUI.
But this CDR data is successfully logging into syslog (see the paragraph
below), but my requirement is to get the CDR data to be reflect in my GUI.
Here below is the CDR data that logged into syslog:
Aug 3 17:36:25 kamailio /usr/local/sbin/kamailio[12391]: INFO: acc
[acc.c:275]: acc_log_request(): ACC: transaction answered:
timestamp=1375531585;method=INVITE;from_tag=170287292812;to_tag=373699520912;call_id=
6595ee13-bfec-15a7-ae-4b-00210705d550(a)192.168.2.99;code=200;reason=OK;src=;dst=
Aug 3 17:36:25 kamailio /usr/local/sbin/kamailio[12393]: INFO: acc
[acc.c:275]: acc_log_request(): ACC: request acknowledged:
timestamp=1375531585;method=ACK;from_tag=170287292812;to_tag=373699520912;call_id=
6595ee13-bfec-15a7-ae-4b-00210705d550(a)192.168.2.99;code=200;reason=OK;src=;dst=
Aug 3 17:36:29 kamailio /usr/local/sbin/kamailio[12391]: INFO: acc
[acc_cdr.c:192]: write_cdr(): st=1375531585.654; et=1375531588.863;
duration=3.209; src_user=102; src_domain=192.168.2.41; src_ip=192.168.2.99;
dst_ouser=101; dst_user=101; dst_domain=192.168.2.77
And my kamailio.cfg script relating to CDR's is like this:
/* enhanced DB accounting */
#!ifdef WITH_ACCDB
modparam("acc", "db_flag", FLT_ACCDB) /* FLT_ACCDB is 2 */
modparam("acc", "db_missed_flag", FLT_ACCMISSED) /* FLT_ACCMISSED is 3 */
modparam("acc", "db_url", mysql://kamailio:kamailiorw@kamailio/kamailio)
#modparam("acc",
"db_extra","src_user=$fU;src_domain=$fd;src_ip=$si;""dst_ouser=$tU;dst_user=
$rU;dst_domain=$rd;""duration=$DLG_lifetime")
#modparam("acc", "db_extra","${cdr_extra}")
modparam("acc",
"db_extra","src_user=$fU;src_domain=$fd;src_ip=$si;""dst_ouser=$tU;dst_user=
$rU;dst_domain=$rd")
modparam("acc", "db_table_acc", "acc")
#modparam("acc", "db_table_acc", "acc_$time(year)_$time(mon)")
modparam("acc", "db_table_missed_calls", "missed_calls")
modparam("acc", "acc_method_column", "method")
modparam("acc", "acc_from_tag_column", "from_tag")
modparam("acc", "acc_to_tag_column", "to_tag")
modparam("acc", "acc_callid_column", "callid")
modparam("acc", "acc_sip_code_column", "sip_code")
modparam("acc", "acc_sip_reason_column", "sip_reason")
modparam("acc", "acc_time_column", "time")
modparam("acc", "db_insert_mode", 0)
#!endif
# -------- for siremis CDRs -----------
modparam("acc", "cdr_enable", 1)
modparam("acc", "cdr_start_on_confirmed", 1)
modparam("acc", "cdr_facility", "LOG_DAEMON")
#modparam("acc", "cdr_extra", "c1=$dlg_var(caller);c2=$dlg_var(callee)")
modparam("acc", "cdr_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;""dst_ouser=$tU;dst_user=$rU;dst_domain=$rd")
modparam("acc", "cdr_start_id", "st")
modparam("acc", "cdr_end_id", "et")
modparam("acc", "cdr_duration_id", "duration")
.
modparam("rtimer", "timer", "name=cdr;interval=300;mode=1;")
modparam("rtimer", "exec", "timer=cdr;route=2")
modparam("sqlops", "sqlcon",
"ca=>mysql://kamailio:kamailiorw@localhost/kamailio")
modparam("sqlops", "sqlres", "ra")
.
.
# Populate CDRs Table of Siremis
route[2] {
sql_query("ca","call kamailio_cdrs()","ra");
}
Can u guess where i am wrong ? how can i solve this issue ?
And for your notice, in acc module document it is said like this:
'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'.
What does it mean ? of course 'cdrs' table in kamailio database is empty.
Any help will greatly appreciate.
Regards,
Nandini.