I've just released DruCall, the WebRTC module for Drupal.
http://danielpocock.com/announcing-drucall-webrtc-for-drupal
Making WebRTC available as a Drupal module hopefully means thousands of
blogs and small business web sites will start picking this up and
hopefully Kamailio will share in some of the demand for WebRTC capable
server infrastructure.
Hi,
I'd created an account with my domain shaluavita. My user id was
alamin(a)shaluavita.tk. Unfortunatly, I canceled the account. It war
about 2 moth ago. I tried to re-register many times but failed for
remaining the domain in the database. Now I want to use my account.
Please re-activate it.
Thanks
Hey all,
I am dealing with a possible race condition in the dialog module. About
one call in 50 isn't cleared from the database. I catch the calls by
joining the dialog table to my cdr table ( which is generated from acc
table ).
The call remains in the dialog table in the database.
I tested, and I am not hitting the destroy_dlg() function which is
called from the unref_dlg_unsafe macro. destroy_dlg() calls the
remove_dialog_from_db(). unref_dlg_unsafe is called but the ref counter
is still at one. I can see this from my logs :
11:22:55 [20195]: ERROR: dialog [dlg_hash.c:944]: dialog 0x7fab27f4aa88
changed from state 1 to state 3, due event 3 (ref 2) <== de ringing a
repondu
11:22:55 [20172]: ERROR: dialog [dlg_hash.c:944]: dialog 0x7fab27f4aa88
changed from state 3 to state 4, due event 6 (ref 3) <== answer
11:22:55 [20202]: ERROR: dialog [dlg_hash.c:944]: dialog 0x7fab27f4aa88
changed from state 4 to state 4, due event 6 (ref 3) <== answer
11:22:55 [20177]: ERROR: dialog [dlg_hash.c:944]: dialog 0x7fab27f4aa88
changed from state 4 to state 4, due event 6 (ref 4) <== answer
11:23:05 [20190]: ERROR: dialog [dlg_hash.c:944]: dialog 0x7fab27f4aa88
changed from state 4 to state 5, due event 7 (ref 3) <== BYE, hangup
11:23:05 [20183]: ERROR: dialog [dlg_hash.c:944]: dialog 0x7fab27f4aa88
changed from state 5 to state 5, due event 7 (ref 5) <== confirm hangup
The problem seems to be happening randomly and I can't find any
explanation for it.
So the number of references never reaches 0, because it never reaches 0,
the dialog is not unreferenced :
Here is the output from syslog ( grepped with the call hash ) :
Feb 26 11:21:41 kamailio-1 /usr/sbin/kamailio[20164]: ERROR: dialog
[dlg_hash.c:717]: ref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:21:41 kamailio-1 /usr/sbin/kamailio[20164]: ERROR: dialog
[dlg_hash.c:737]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 4 to state 5,
due event 7 (ref 3)
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:737]: ref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 2 -> 2
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20214]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20170]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:48 kamailio-1 /usr/sbin/kamailio[20170]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:53 kamailio-1 /usr/sbin/kamailio[20216]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:53 kamailio-1 /usr/sbin/kamailio[20216]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 2 -> 0
Feb 26 11:22:53 kamailio-1 /usr/sbin/kamailio[20216]: ERROR: dialog
[dlg_hash.c:757]: ref <=0 for dialog 0x7fab27f4aa88
Feb 26 11:22:53 kamailio-1 /usr/sbin/kamailio[20216]: ERROR: dialog
[dlg_hash.c:317]: destroying dialog 0x7fab27f4aa88 (ref 0)
Feb 26 11:22:53 kamailio-1 /usr/sbin/kamailio[20216]: ERROR: dialog
[dlg_hash.c:333]: removed timer for dlg 0x7fab27f4aa88 [7298:10958] with
clid '13b951b67f2704d51d25cf643b3469d1(a)pbx.omnity.biz' and tags
'as3a8e0df2' 'as4c79d466'
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20208]: ERROR: dialog
[dlg_hash.c:717]: ref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20208]: ERROR: dialog
[dlg_cb.c:230]: dialog=0x7fab27f4aa88
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20208]: ERROR: dialog
[dlg_hash.c:737]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20208]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20208]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20208]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 1 to state 3,
due event 3 (ref 2)
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_handlers.c:484]: dialog 0x7fab27f4aa88 confirmed (ACK pending)
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_hash.c:737]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_cb.c:256]: dialog=0x7fab27f4aa88, type=8
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20174]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20174]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20195]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20178]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20178]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20172]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20172]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 3 to state 4,
due event 6 (ref 3)
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20172]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20172]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20172]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20202]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20202]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 4 to state 4,
due event 6 (ref 3)
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20202]: ERROR: dialog
[dlg_cb.c:256]: dialog=0x7fab27f4aa88, type=32
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20177]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20177]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 4 to state 4,
due event 6 (ref 4)
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20177]: ERROR: dialog
[dlg_cb.c:256]: dialog=0x7fab27f4aa88, type=32
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20202]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20202]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20202]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20177]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20177]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:22:55 kamailio-1 /usr/sbin/kamailio[20177]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 3
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 4 to state 5,
due event 7 (ref 3)
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:737]: ref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_cb.c:256]: dialog=0x7fab27f4aa88, type=64
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20183]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 5
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20183]: ERROR: dialog
[dlg_hash.c:944]: dialog 0x7fab27f4aa88 changed from state 5 to state 5,
due event 7 (ref 5)
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20183]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20183]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 5
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20183]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 4
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 2 -> 2
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:590]: ref dlg 0x7fab27f4aa88 with 1 -> 2
Feb 26 11:23:05 kamailio-1 /usr/sbin/kamailio[20190]: ERROR: dialog
[dlg_hash.c:757]: unref dlg 0x7fab27f4aa88 with 1 -> 1
You can see the last refence is never removed, so the dialog isn't
destroyed. Here is the end of a healthy dialog :
Feb 26 08:03:00 kamailio-1 /usr/sbin/kamailio[4668]: ERROR: dialog
[dlg_hash.c:753]: unref dlg 0x7f74db910e60 with 2 -> 0
Feb 26 08:03:00 kamailio-1 /usr/sbin/kamailio[4668]: ERROR: dialog
[dlg_hash.c:753]: ref <=0 for dialog 0x7f74db910e60
Feb 26 08:03:00 kamailio-1 /usr/sbin/kamailio[4668]: ERROR: dialog
[dlg_hash.c:315]: destroying dialog 0x7f74db910e60 (ref 0)
You see it falls to 0 and the dialog is destroyed.
So, how do I debug this ? Should I maybe be posting to sr-dev ?
How do I determine who is incrementing the counter without decrementing it?
What information do I need to continue with this problem?
Thanks!
David
ps I used perl pie to replace LM_DBG with LM_ERROR in modules_k/dialog/*
version: kamailio 3.3.2 (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 09:17:03 Oct 18 2012 with gcc 4.4.3
Hi,
i use the AVPops module to store information about Call-Forwardings in
the database:
# Store new CF-Target in Database:
$avp(s:usr_cfnr) = $rU;
avp_db_store("$avp(s:caller_userid)", "$avp(s:usr_cfnr)/usr_preferences");
$avp(s:usr_cfnr_delay) = 20;
avp_db_store("$avp(s:caller_userid)", "$avp(s:usr_cfnr_delay)/usr_preferences");
(please not, that $avp(s:caller_userid) was not changed)
however this results into two different inserts, one for user 7736 (correct)
T 2013/02/25 14:25:11.704628 192.168.0.2:51460 -> 192.168.0.20:3306 [AP]
{....insert into usr_preferences
(uuid,attribute,value,type,username,domain ) values
('7736','usr_cfnr','491792021244',0,'','')
and one for user 7720 (20???, as in the delay, incorrect)
T 2013/02/25 14:25:11.705572 192.168.0.2:51460 -> 192.168.0.20:3306 [AP]
w....insert into usr_preferences
(uuid,attribute,value,type,username,domain ) values
('7720','usr_cfnr_delay','20',1,'','')
I am using Kamailio 3.3.2 from GIT-Trunk (nightly, checked out on
December 14th):
root@proxy1:/# kamailio -V
version: kamailio 3.3.2 (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS,
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
SHM_MMAP, PKG_MALLOC, F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST,
HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 01:57:11 Dec 14 2012 with gcc 4.4.5
Before i dig deeper into the code of the avpops module, has anyone
seen / fixed this issue?
Thanks,
Carsten
--
Carsten Bock
CEO (Geschäftsführer)
=============================================================
Visit us on the Kamailio World 2013, 16./17. April 2013
=> http://conference.kamailio.com/k01/ See
you there!
=============================================================
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 34927219
Fax +49 40 34927220
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/
Hello,
Last Thursday our kamailio process crashed. There are a lot of memory related errors in there. See attachment for details.
Did the machine run out of memory? How do I prevent this from happening again?
The machine has 4GB of memory.
Regards,
Grant
Hi!
I can see that there's been some discussion about SIP loop detection on the OpenSER and SER mailing lists, but I must have missed the conclusion. Apart from setting a max-forwards, how would you configure your Kamailio server to prevent looping?
Regards,
/O
Hello,
I've been having some issues with the syntax of Kamailio's config file.
I've been following the turorial here:
http://kb.asipto.com/asterisk:realtime:kamailio-3.3.x-asterisk-10.7.0-astdb
I'd like to setup Kamailio to act as an SBC providing NAT traversal, and
security for multiple asterisk boxes on the inside. Currently kamailio has
two NIC's, one public and one private. All traffic hits the external
interface and is then forwarded to an Asterisk box on the inside.
I'd like to modify the config from the tutorial above to support multiple
asterisk boxes. Authentication will be done via MySQL and depending on the
user domain, the request get's forwarded to the proper Asterisk box. Here
is what I've got so far:
if (is_method("REGISTER") && from_uri=~.*(a)10.55.55.5)
{
if(isflagset(FLT_NATS))
{
setbflag(FLB_NATB);
# uncomment next line to do SIP NAT pinging
## setbflag(FLB_NATSIPPING);
}
if (!save("location"))
sl_reply_error();
route(REGFWD);
exit;
}
else if (is_method("REGISTER") && from_uri=~".*asterisk.domain.tld")
{
if(isflagset(FLT_NATS))
{
setbflag(FLB_NATB);
# uncomment next line to do SIP NAT pinging
## setbflag(FLB_NATSIPPING);
}
if (!save("location"))
sl_reply_error();
route(REGFWDCLOUD);
exit;
}
}
Based on the domain I route the SIP message to another route block which is
esentally the same route block as the origional route[FROMASTERISK]
route[TOASTERISK] route[REGFWD]. I beleive there's an easier way of doing
this though. Creating separate route blocks per asterisk box would mean
creating a new route blocks for each asterisk box. Here's an example:
route[FROMASTERISK] {
if($si==$sel(cfg_get.asterisk.bindip)
&& $sp==$sel(cfg_get.asterisk.bindport))
return 1;
return -1;
# Send to Asterisk
route[TOASTERISK] {
$du = "sip:" + $sel(cfg_get.asterisk.bindip) + ":"
+ $sel(cfg_get.asterisk.bindport);
route(RELAY);
exit;
# Forward REGISTER to Asterisk
route[REGFWD] {
if(!is_method("REGISTER"))
{
return;
}
$var(rip) = $sel(cfg_get.asterisk.bindip);
$uac_req(method)="REGISTER";
$uac_req(ruri)="sip:" + $var(rip) + ":" +
$sel(cfg_get.asterisk.bindport);
$uac_req(furi)="sip:" + $au + "@" + $var(rip);
$uac_req(turi)="sip:" + $au + "@" + $var(rip);
$uac_req(hdrs)="Contact: <sip:" + $au + "@"
+ $sel(cfg_get.kamailio.bindip)
+ ":" + $sel(cfg_get.kamailio.bindport) +
">\r\n";
if($sel(contact.expires) != $null)
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$sel(contact.expires) + "\r\n";
else
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$hdr(Expires) + "\r\n";
uac_req_send();
}
route[FROMCLOUD] {
if($si==$sel(cfg_get.cloud.bindip)
&& $sp==$sel(cfg_get.asterisk.bindport))
return 1;
return -1;
}
route[TOCLOUD] {
$du = "sip:" + $sel(cfg_get.cloud.bindip) + ":"
+ $sel(cfg_get.asterisk.bindport);
route(RELAY);
exit;
}
route[REGFWDCLOUD] {
if(!is_method("REGISTER"))
{
return;
}
$var(rip) = $sel(cfg_get.cloud.bindip);
$uac_req(method)="REGISTER";
$uac_req(ruri)="sip:" + $var(rip) + ":" +
$sel(cfg_get.asterisk.bindport);
$uac_req(furi)="sip:" + $au + "@" + $var(rip);
$uac_req(turi)="sip:" + $au + "@" + $var(rip);
$uac_req(hdrs)="Contact: <sip:" + $au + "@"
+ $sel(cfg_get.kamailio.bindip)
+ ":" + $sel(cfg_get.kamailio.bindport) +
">\r\n";
if($sel(contact.expires) != $null)
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$sel(contact.expires) + "\r\n";
else
$uac_req(hdrs)= $uac_req(hdrs) + "Expires: " +
$hdr(Expires) + "\r\n";
uac_req_send();
}
I'm sure their is any easier way of doing this alhthough I'm not sure how.
Can anyone point me in the right direction?
Lastly, is there a way to modify the DBURL string on the fly so based on
the domain for example, I coudl query a different DB for user credentials?
Thanks!
Hello,
Kamailio SIP Server v3.3.4 stable release is out.
This is a maintenance release of the latest stable branch, 3.3, that
includes fixes since release of v3.3.3. There is no change to database
schema or configuration language structure that you have to do on
installations of v3.3.0, v3.3.1, v3.3.2 or v3.3.3. Deployments running
previous v3.x.x versions are strongly recommended to be upgraded to v3.3.4.
For more details about version 3.3.4 (including links and hints to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2013/02/kamailio-v3-3-4-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
- http://conference.kamailio.com -
Hi,
I am looking to build an SBC/SIP router made up from Kamailio and FreePBX.
Calls will then need to be passed to multiple Asterisk media gateways. Can
anyone point me to some documentation or help on how to do this?
--
Keith
