Hi list,
I have Kamailio running behind NAT. (Amazon EC2)
When I use mslio module, storing messages for offline contact is working
fine,
however the stored messages are never sent to the contacts when they get
online.
My configuration is as below.
Any kind of help will be great appreciated.
Thank you!
----------------------------------------------------------------------------------------------------------------------
loadmodule "msilo.so"
...
modparam("msilo", "add_date", 0)
modparam("msilo", "db_url",DBURL)
...
route[REGISTRAR] {
if (is_method("REGISTER"))
{
if(isflagset(FLT_NATS))
{
setbflag(FLB_NATB);
# uncomment next line to do SIP NAT pinging
setbflag(FLB_NATSIPPING);
}
$avp(s:fu) = $fu;
$var(initialregister) = 1;
if( registered("location")){
$var(initialregister) = 0;
}
if (!save("location"))
sl_reply_error();
if( !is_present_hf("Expires") || $(hdr(Expires){s.int})!=0 &&
$var(initialregister)==1 ){
# Send messages recieved while offline
if (m_dump("$fu")){
xlog("L_INFO", "offline messages dumped for $avp(s:fu)
\n");
}
else{
xlog("L_INFO", "no offline messages dumped for
$avp(s:fu) \n");
}
}
exit;
}
}
# USER location service
route[LOCATION] {
if (!lookup("location")) {
switch ($rc) {
case -1:
...
if (is_method("MESSAGE")) {
$var(m_store_owner) = $tu;
if (m_store("$var(m_store_owner)"))
{
xlog("L_INFO", "(MSILO_STORE) offline message stored
for $var(m_store_owner)\n");
if (!t_reply("202", "Accepted")) sl_reply_error();
}
else {
xlog("L_ERR","BUG: dropped an offline MESSAGE: M=$rm S=$rs
D=$rr F=$fu T=$tu IP=$si ID=$ci UA=$ua Txt=$rb");
if (!t_reply("503", "Service Unavailable")) sl_reply_error();
};
}
exit;
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
if (is_method("INVITE"))
{
setflag(FLT_ACCMISSED);
}
}
Hi List,
I have a Kamailio3.1 server and RTPProxy running in WAN.
The calls between UA will automatically terminated in Callee UA side 36s
after connected, while no one sends a BYE.
While Kamailio and UA are in LAN at all , everything is just working well.
Is it my rtpproxy doesn't working correctly or something else is wrong?
What can I do to fix it.
Any hint??
BTW,
Kamailio is installed following official guide
http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git
The kamailio.cfg wasn't changed at all except for below:
-----------------------------------------------------------------------------------------
1) adding the following lines:
#!define WITH_MYSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
#!define WITH_NAT
2)uncommenting the line below in route[REGISTRAR],
setbflag(FLB_NATSIPPING);
3)change rtpproxy port corresponding
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:22222")
-----------------------------------------------------------------------------------------
and my rtpproxy1.2.1 was installed by apt-get install rtpproxy,
with
1) /etc/default/rtpproxy changed into:
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:22222
LISTEN_ADDR=xx.xx.xx.xx
# Additional options that are passed to the daemon.
EXTRA_OPTS="-l ${LISTEN_ADDR}"
2) and started by
rtpproxy -l xx.xx.xx.xx -s udp:localhost:22222 -u kamailio
Your help will be great appreciated.
Coca
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#124 - Add additional tm callbacks
User who did this - Timo Reimann (tr)
----------
Unfortunately, I do not have a patch since I didn't know where to call these callbacks from in the code.
Logically, I'd want the first callback (TMCB_REQUEST_OUT) to be triggered just after a request has been sent. That is, the message is gone, there is no way to modify it anymore (just like 1.5's TMCB_REQUEST_BUILT callback).
TMCB_REQUEST_READY, on the contrary, should be executed right before the message is sent. IMHO, it's OK if you are *not* allowed to change the message anymore (as with 1.5's TMCB_REQUEST_PRE_OUT). FWIW, there's already a TMCB_RESPONSE_READY callback in Sip-Router.
Let me know if you need any further input.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=124#comment246
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Module: sip-router
Branch: master
Commit: 0c3664778b50bee82c39194334729123164dcdf6
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0c36647…
Author: Alex Hermann <alex(a)speakup.nl>
Committer: Alex Hermann <alex(a)speakup.nl>
Date: Fri Jun 3 12:24:12 2011 +0200
modules_k/uac: Allow all type of PV's for uac auth_*_avp instead of just AVP's
Keep the parameter names as *_avp to keep backwards compatibility even though the
names make no sense anymore.
---
modules_k/uac/auth.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/modules_k/uac/auth.c b/modules_k/uac/auth.c
index 8fb8853..18a0cf1 100644
--- a/modules_k/uac/auth.c
+++ b/modules_k/uac/auth.c
@@ -432,7 +432,7 @@ int uac_auth( struct sip_msg *msg)
/* can we authenticate this realm? */
crd = 0;
/* first look into AVP, if set */
- if ( auth_realm_spec.type==PVT_AVP )
+ if ( auth_realm_spec.type!=PVT_NONE )
crd = get_avp_credential( msg, &auth.realm );
/* if not found, look into predefined credentials */
if (crd==0)