And also when I(Application A) send the Subscribe message with the Dialog event to the kamailio server, The kamailio server is not forwarding that Subscribe message to party B.
Since kamailio acts as proxy it has to forward the Subscribe message to the party to whom I have Subscribed(ie Party B an x-lite phone).
The call flow is as follows.
REISTER
A(APP) kamailio B(x-lite) C(x-lite)
| | | |
200 OK
| | | |
| | | |
REGISTER
REGISTER
| | | |
| | | |
200 OK
| | | |
| | | |
200 OK
| | | |
| | | |
SUBSCRIBE
| | | |
| | | |
202 OK
| | | |
| | | |
NOTIFY
| | | |
Call Established between B and C
| | | |
200 OK
| | | |
| | | |
| | | |
| | | |
I am using kamailio-1.4.0-notls and trying to use dialog event package. The above call flow is as follows.
1) B an x-lite phone is Registered(B@kamailio) then C another x-lite phone is registered(c@kamailio)
2) Now from my application I am registering A and got registered(A@kamailio).
3) Now A is subscribing to B for the dialog event, so I am sending SUBSCRIBE message to kamailio server, that is I am sending SUBSCRIBE message from A@application to B@kamailio with the Event header.
4) Now I got 202 for the SUBSCRIBE.
5) Server Kamailio sends NOTIFY and then my application A sends 200 OK.
6) Now I will establish call between two x-lite phones B and C.
Now My Question?
When I establish call between B and C, I(Application A) have to get NOTIFY from kamailio server about the dialog event, I am not getting the NOTIFY for the dialog event since I have Subscribed to B for the Dialog event Package.
Finally I(A application) want to know that dialog changes in the B.
But Dialog module is present in the kamailio code. So for what purpose is it used?
Is there any modules I have to include or provision in the config file or make file, If yes then where I have to make the changes.
Thank You
Regards,
Sunil Teli
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 12, 2009 7:08 PM To: Sunil Teli Cc: users Subject: Re: [Kamailio-Users] About Kamailio-1.4.0-notls.
Hi Sunil!
Kamailio 1.4 does not support the "dialog" event package. You have to
use Kamailio "trunk" version. Trunk includes 2 new modules:
PUA_DIALOGINFO: generates PUBLISH requests to publish the dialog state
PRESENCE_DIALOGINFO: processes PUBLISH requests, aggregate dialog
information and send it with NOTIFY to the watcher
Please see the detailed READMEs of these modules.
http://www.kamailio.org/docs/modules/devel/
regards
klaus
============================================================================================================================
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 <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.
============================================================================================================================
Sunil Teli wrote:
And also when I(Application A) send the Subscribe message with the Dialog event to the kamailio server, The kamailio server is not forwarding that Subscribe message to party B.
it depends. If you are using end-to-end presence, then you have to configure kamailio to forward the request.
If you want to use server-based presence, then Kamailio will process the SUBSCRIBE.
regards klaus
Since kamailio acts as proxy it has to forward the Subscribe message to the party to whom I have Subscribed(ie Party B an x-lite phone).
The call flow is as follows.
REISTER
A(APP) kamailio B(x-lite) C(x-lite) | | | |
200 OK
| | | | | | | |
REGISTER
REGISTER
| | | | | | | |
200 OK
| | | | | | | |
200 OK
| | | | | | | |
SUBSCRIBE
| | | | | | | |
202 OK
| | | | | | | |
NOTIFY
| | | |
Call Established between B and C
| | | |
200 OK
| | | | | | | | | | | | | | | |
I am using kamailio-1.4.0-notls and trying to use dialog event package. The above call flow is as follows.
B an x-lite phone is Registered(B@kamailio) then C another
x-lite phone is registered(c@kamailio)
Now from my application I am registering A and got
registered(A@kamailio).
Now A is subscribing to B for the dialog event, so I am sending
SUBSCRIBE message to kamailio server, that is I am sending SUBSCRIBE message from A@application to B@kamailio with the Event header.
Now I got 202 for the SUBSCRIBE.
Server Kamailio sends NOTIFY and then my application A sends
200 OK.
Now I will establish call between two x-lite phones B and C.
Now My Question?
When I establish call between B and C, I(Application A) have to get NOTIFY from kamailio server about the dialog event, I am not getting the NOTIFY for the dialog event since I have Subscribed to B for the Dialog event Package.
Finally I(A application) want to know that dialog changes in the B.
But Dialog module is present in the kamailio code. So for what purpose is it used?
Is there any modules I have to include or provision in the config file or make file, If yes then where I have to make the changes.
Thank You
Regards,
Sunil Teli
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 12, 2009 7:08 PM To: Sunil Teli Cc: users Subject: Re: [Kamailio-Users] About Kamailio-1.4.0-notls.
Hi Sunil!
Kamailio 1.4 does not support the "dialog" event package. You have to
use Kamailio "trunk" version. Trunk includes 2 new modules:
PUA_DIALOGINFO: generates PUBLISH requests to publish the dialog state
PRESENCE_DIALOGINFO: processes PUBLISH requests, aggregate dialog
information and send it with NOTIFY to the watcher
Please see the detailed READMEs of these modules.
http://www.kamailio.org/docs/modules/devel/
regards
klaus
============================================================================================================================
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 and http://tim.techmahindra.com/Disclaimer.html internally within Tech Mahindra.
============================================================================================================================
The below is the kamailio.cfg file what I have modified for Dialog Event Package. But for the below configuration when I send Subscribe message form Application A to the B(x-lite phone) through Kamailio, here my request uri is
SUBSCRIBE sip:B@192.168.1.1 SIP/2.0 //Here 192.168.1.1 is the kamailio server, where B and C are registered.
For this Subscribe I got the 202 OK and NOTIFY from the server, But when I make a call from B(x-lite phone) to the C(another x-lite phone) there is a dialog event, so now the kamailio server has to send a NOTIFY message to the Application A since there is a dialog event.
Can you please go through the config file and let me know if there any changes to make in the config file for the above scenario to work.
The lines with bold fonts are the changes which I have made.
#
# $Id: kamailio.cfg 4576 2008-08-05 16:22:38Z klaus_darilion $
#
# Kamailion basic configuration script
# by Anca Vamanu anca@voice-system.ro
#
# Please refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php
# for a explanation of possible statements, functions and parameters.
#
####### Global Parameters #########
debug=3
log_stderror=no
log_facility=LOG_LOCAL0
fork=yes
children=4
/* uncomment the following lines to enable debugging */
debug=6
#fork=no
log_stderror=yes
/* uncomment the next line to disable TCP (default on) */
#disable_tcp=yes
/* uncomment the next line to enable the auto temporary blacklisting of
not available destinations (default disabled) */
#disable_dns_blacklist=no
/* uncomment the next line to enable IPv6 lookup after IPv4 dns
lookup failures (default disabled) */
#dns_try_ipv6=yes
/* uncomment the next line to disable the auto discovery of local aliases
based on revers DNS on IPs (default on) */
#auto_aliases=no
/* uncomment the following lines to enable TLS support (default off) */
#disable_tls = no
#listen = tls:your_IP:5061
#tls_verify_server = 1
#tls_verify_client = 1
#tls_require_client_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/home/test/OpenSER/etc/kamailio/tls/user/user-cert.pem"
#tls_private_key = "/home/test/OpenSER/etc/kamailio/tls/user/user-privkey.pem"
#tls_ca_list = "/home/test/OpenSER/etc/kamailio/tls/user/user-calist.pem"
#port=7010
port=5060
/* uncomment and configure the following line if you want Kamailio to
bind on a specific interface/port/proto (default bind on all available) */
#listen=udp:192.168.1.1:7010
listen=udp:192.168.1.1:5060
####### Modules Section ########
#set module path
mpath="/home/test/OpenSER/lib/kamailio/modules/"
/* uncomment next line for MySQL DB support */
loadmodule "db_mysql.so"
loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"
loadmodule "uri_db.so"
loadmodule "uri.so"
loadmodule "xlog.so"
loadmodule "acc.so"
#Added for dialog event package
loadmodule "dialog.so"
/* uncomment next lines for MySQL based authentication support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "auth.so"
loadmodule "auth_db.so"
/* uncomment next line for aliases support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "alias_db.so"
/* uncomment next line for multi-domain support
NOTE: a DB (like db_mysql) module must be also loaded
NOTE: be sure and enable multi-domain support in all used modules
(see "multi-module params" section ) */
loadmodule "domain.so"
/* uncomment the next two lines for presence server support
NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule "presence.so"
loadmodule "presence_xml.so"
# ----------------- setting module-specific parameters ---------------
# ----- mi_fifo params -----
modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")
# ----- rr params -----
# add value to ;lr param to cope with most of the UAs
modparam("rr", "enable_full_lr", 1)
# do not append from tag to the RR (no need for this script)
modparam("rr", "append_fromtag", 0)
# ----- rr params -----
modparam("registrar", "method_filtering", 1)
/* uncomment the next line to disable parallel forking via location */
# modparam("registrar", "append_branches", 0)
/* uncomment the next line not to allow more than 10 contacts per AOR */
#modparam("registrar", "max_contacts", 10)
# ----- uri_db params -----
/* by default we disable the DB support in the module as we do not need it
in this configuration */
modparam("uri_db", "use_uri_table", 0)
modparam("uri_db", "db_url", "")
# ----- acc params -----
/* what sepcial events should be accounted ? */
modparam("acc", "early_media", 1)
modparam("acc", "report_ack", 1)
modparam("acc", "report_cancels", 1)
/* by default ww do not adjust the direct of the sequential requests.
if you enable this parameter, be sure the enable "append_fromtag"
in "rr" module */
modparam("acc", "detect_direction", 0)
/* account triggers (flags) */
modparam("acc", "failed_transaction_flag", 3)
modparam("acc", "log_flag", 1)
modparam("acc", "log_missed_flag", 2)
/* uncomment the following lines to enable DB accounting also */
modparam("acc", "db_flag", 1)
modparam("acc", "db_missed_flag", 2)
# ----- usrloc params -----
modparam("usrloc", "db_mode", 0)
/* uncomment the following lines if you want to enable DB persistency
for location entries */
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "db_url",
"mysql://openser:openserrw@localhost/openser")
#Added for dialog event package
modparam("dialog", "dlg_flag", 4)
modparam("dialog", "db_mode", 1)
modparam("dialog", "table_name", "dialog")
modparam("dialog", "db_url",
"mysql://openser:openserrw@localhost/openser")
#modparam("dialog", "db_mode", 2)
#modparam("dialog", "db_url",
# "mysql://openser:openserrw@localhost/openser")
# ----- auth_db params -----
/* uncomment the following lines if you want to enable the DB based
authentication */
modparam("auth_db", "calculate_ha1", yes)
modparam("auth_db", "password_column", "password")
modparam("auth_db", "db_url",
"mysql://openser:openserrw@localhost/openser")
modparam("auth_db", "load_credentials", "")
# ----- alias_db params -----
/* uncomment the following lines if you want to enable the DB based
aliases */
modparam("alias_db", "db_url",
"mysql://openser:openserrw@localhost/openser")
# ----- domain params -----
/* uncomment the following lines to enable multi-domain detection
support */
modparam("domain", "db_url",
"mysql://openser:openserrw@localhost/openser")
#modparam("domain", "db_mode", 1) # Use caching
# ----- multi-module params -----
/* uncomment the following line if you want to enable multi-domain support
in the modules (dafault off) */
#modparam("alias_db|auth_db|usrloc|uri_db", "use_domain", 1)
# ----- presence params -----
/* uncomment the following lines if you want to enable presence */
modparam("presence|presence_xml", "db_url",
"mysql://openser:openserrw@localhost/openser")
modparam("presence_xml", "force_active", 1)
#modparam("presence", "server_address", "sip:192.168.1.2:5060")
#modparam("presence", "server_address", "sip:192.168.1.1:7010")
modparam("presence", "server_address", "sip:192.168.1.1:5060")
####### Routing Logic ########
# main request routing logic
route{
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
exit;
}
if (has_totag()) {
# sequential request withing a dialog should
# take the path determined by record-routing
if (loose_route()) {
if (is_method("BYE")) {
setflag(1); # do accounting ...
setflag(3); # ... even if the transaction fails
}
route(1);
} else {
/* uncomment the following lines if you want to enable presence */
if (is_method("SUBSCRIBE") && $rd == "your.server.ip.address") {
# in-dialog subscribe requests
route(2);
exit;
}
if ( is_method("ACK") ) {
if ( t_check_trans() ) {
# non loose-route, but stateful ACK; must be an ACK after a 487 or e.g. 404 from upstream server
t_relay();
exit;
} else {
# ACK without matching transaction ... ignore and discard.\n");
exit;
}
}
sl_send_reply("404","Not here");
}
exit;
}
#initial requests
# CANCEL processing
if (is_method("CANCEL"))
{
if (t_check_trans())
t_relay();
exit;
}
t_check_trans();
# authenticate if from local subscriber (uncomment to enable auth)
##if (!(method=="REGISTER") && from_uri==myself)
##{
## if (!proxy_authorize("", "subscriber")) {
## proxy_challenge("", "0");
## exit;
## }
## if (!check_from()) {
## sl_send_reply("403","Forbidden auth ID");
## exit;
## }
##
## consume_credentials();
## # caller authenticated
##}
# record routing
if (!is_method("REGISTER|MESSAGE"))
record_route();
# account only INVITEs
if (is_method("INVITE")) {
#setflag(1); # do accounting
setflag(4);
}
if (dst_port == 5060)# || dst_port == 7010) # For the x-lite phone for registration.
{
if (is_method("REGISTER"))
{
xlog("\n Received Registration ");
# authenticate the REGISTER requests (uncomment to enable auth)
##if (!www_authorize("", "subscriber"))
##{
## www_challenge("", "0");
## exit;
##}
##
##if (!check_to())
##{
## sl_send_reply("403","Forbidden auth ID");
## exit;
##}
if (save("location"))
{
xlog(" save location successful");
sl_send_reply("200","OK");
}
else
{
sl_reply_error();
}
exit;
}
}
if (!uri==myself)
/* replace with following line if multi-domain support is used */
##if (!is_uri_host_local())
{
append_hf("P-hint: outbound\r\n");
# if you have some interdomain connections via TLS
##if($rd=="tls_domain1.net") {
## t_relay("tls:domain1.net");
## exit;
##} else if($rd=="tls_domain2.net") {
## t_relay("tls:domain2.net");
## exit;
##}
route(1);
}
# requests for my domain
/* uncomment this if you want to enable presence server
and comment the next 'if' block
NOTE: uncomment also the definition of route[2] from below */
if( is_method("PUBLISH|SUBSCRIBE"))
route(2);
if (is_method("PUBLISH"))
{
sl_send_reply("503", "Service Unavailable");
exit;
}
if (dst_port == 5060)# || dst_port == 7010) # For the x-lite phone for registration.
{
if (is_method("REGISTER"))
{
xlog("\n Received Registration ");
# authenticate the REGISTER requests (uncomment to enable auth)
##if (!www_authorize("", "subscriber"))
##{
## www_challenge("", "0");
## exit;
##}
##
##if (!check_to())
##{
## sl_send_reply("403","Forbidden auth ID");
## exit;
##}
if (save("location"))
{
xlog(" save location successful");
sl_send_reply("200","OK");
}
else
{
sl_reply_error();
}
exit;
}
}
if ($rU==NULL) {
# request with no Username in RURI
sl_send_reply("484","Address Incomplete");
exit;
}
# apply DB based aliases (uncomment to enable)
##alias_db_lookup("dbaliases");
if (!lookup("location")) {
switch ($retcode) {
case -1:
case -3:
t_newtran();
t_reply("404", "Not Found");
exit;
case -2:
sl_send_reply("405", "Method Not Allowed");
exit;
}
}
# when routing via usrloc, log the missed calls also
setflag(2);
route(1);
}
route[1] {
# for INVITEs enable some additional helper routes
if (is_method("INVITE")) {
t_on_branch("2");
t_on_reply("2");
t_on_failure("1");
}
if (!t_relay()) {
sl_reply_error();
};
exit;
}
# Presence route
/* uncomment the whole following route for enabling presence
NOTE: do not forget to enable the call of this route from the main
route */
route[2]
{
if (!t_newtran())
{
sl_reply_error();
exit;
};
if(is_method("PUBLISH"))
{
handle_publish();
t_release();
}
else
if( is_method("SUBSCRIBE"))
{
handle_subscribe();
t_release();
}
exit;
}
branch_route[2] {
xlog("new branch at $ru\n");
}
onreply_route[2] {
xlog("incoming reply\n");
}
failure_route[1] {
if (t_was_cancelled()) {
exit;
}
# uncomment the following lines if you want to block client
# redirect based on 3xx replies.
##if (t_check_status("3[0-9][0-9]")) {
##t_reply("404","Not found");
## exit;
##}
# uncomment the following lines if you want to redirect the failed
# calls to a different new destination
##if (t_check_status("486|408")) {
## sethostport("192.168.2.100:5060");
## append_branch();
## # do not set the missed call flag again
## t_relay();
##}
}
Thank You
Regards,
Sunil Teli
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Tuesday, January 13, 2009 3:22 AM To: Sunil Teli Cc: users Subject: Re: [Kamailio-Users] About Kamailio-1.4.0-notls.
Sunil Teli wrote:
And also when I(Application A) send the Subscribe message with the
Dialog event to the kamailio server, The kamailio server is not
forwarding that Subscribe message to party B.
it depends. If you are using end-to-end presence, then you have to
configure kamailio to forward the request.
If you want to use server-based presence, then Kamailio will process the
SUBSCRIBE.
regards
klaus
============================================================================================================================
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 <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.
============================================================================================================================
2009/1/13 Sunil Teli tsunil@techmahindra.com:
SUBSCRIBE sip:B@192.168.1.1 SIP/2.0 //Here 192.168.1.1 is the kamailio server, where B and C are registered.
For this Subscribe I got the 202 OK and NOTIFY from the server, But when I make a call from B(x-lite phone) to the C(another x-lite phone) there is a dialog event, so now the kamailio server has to send a NOTIFY message to the Application A since there is a dialog event.
No, that's not correct.
- B calls C. - INVITE arrives to Kamailio which set a dialog. - It also set the pua_dialoginfo flag. - The pua_dialog_info module sends a *PUBLISH* to the configured server (in pua module settings). - The presence server (which could be co-located in the same proxy) receives the PUBLISH and sends a NOTIFY to the subscribers to that AoR dialog events.
So you must check if pua_dialoginfo is generating the PUBLISH when its flag is set (with the dialog flag), and check if your presence server is receiving it.
Iñaki Baz Castillo schrieb:
2009/1/13 Sunil Teli tsunil@techmahindra.com:
SUBSCRIBE sip:B@192.168.1.1 SIP/2.0 //Here 192.168.1.1 is the kamailio server, where B and C are registered.
For this Subscribe I got the 202 OK and NOTIFY from the server, But when I make a call from B(x-lite phone) to the C(another x-lite phone) there is a dialog event, so now the kamailio server has to send a NOTIFY message to the Application A since there is a dialog event.
No, that's not correct.
- B calls C.
- INVITE arrives to Kamailio which set a dialog.
- It also set the pua_dialoginfo flag.
- The pua_dialog_info module sends a *PUBLISH* to the configured
server (in pua module settings).
- The presence server (which could be co-located in the same proxy)
receives the PUBLISH and sends a NOTIFY to the subscribers to that AoR dialog events.
So you must check if pua_dialoginfo is generating the PUBLISH when its flag is set (with the dialog flag), and check if your presence server is receiving it.
Exactly. use "ngrep -d any port 5060" to see also the SIP messages sent via the loopback network device.
klaus