I am calling tcp_set_connection_lifetime(conid, 1),
which I understand is one sec after now,
but I see it taking upto 60 secs to kill the connection,
is there any other timer which has a larger interval which might affect
this.
--
View this message in context: http://sip-router.1086192.n5.nabble.com/tcp-set-connection-lifetime-does-no…
Sent from the Users mailing list archive at Nabble.com.
Hello Community,
We were facing a weird issue in one of our Kamailio servers where custom htable entries were removed which did not belong to a particular call.
Background Information:
We use htable to store the call-id and a uuid when an INVITE message is received and remove these entries when the call is completed/failed (so on CANCEL, BYE, 4XX, 5XX, 6XX, etc).
In this case the function sht_rm_name_re was causing incremented call-id's belonging to different calls to be removed from the htable, since the removal is based on regex and not the exact key.
On INVITE we do this:
$var(reference) = $uuid(g);
$sht(calls=>$ci) = $ci;
$sht(calls=>$ci::reference) = $var(reference);
On BYE/4XX,5XX,6XX, etc we did this:
sht_rm_name_re("calls=>$ci");
sht_rm_name_re("calls=>$ci::reference");
SIPP generates incremented call-id's, like this: 1-14875(a)1.0.0.1<mailto:1-14875@1.0.0.1>.
When you generate enough calls, for instance 30 calls, the 21st call will have the call-id 21-14875(a)1.0.0.1<mailto:21-14875@1.0.0.1>.
If for instance the BYE for the call-id 1-14875(a)1.0.0.1<mailto:1-14875@1.0.0.1> arrives before 21-14875(a)1.0.0.1<mailto:21-14875@1.0.0.1> , both htable entries will be removed by the sht_rm_name_re function, since it matches based on regex.
To fix this we made sure the function matches on the exact keys by doing this:
$var(callid) = '^' + $ci + '$';
$var(callid_reference) = '^' + $ci + '::reference' + '$';
sht_rm_name_re("calls=>$var(callid)");
sht_rm_name_re("calls=>$var(callid_reference)");
Hope this may help someone in the future facing the same issue.
Regards,
Grant Bagdasarian
CM
Hello,
Kindly note that I am configuring Kamailio for SIP capture with
"Registration" module (registrar.so). Before loading the "Sip Capture"
module (sipcapture.so) into Kamailio.cfg file, the registration of the SIP
Phone (X-lite) is successful. Yet, when we add the "Sip Capture" module
(sipcapture.so) into Kamailio.cfg file with the below parameters:
modparam("sipcapture", "db_url",
"postgres://postgres:postgres@localhost/kamailio")
modparam("sipcapture", "capture_on", 1)
modparam("sipcapture", "table_name", "sip_capture")
modparam("sipcapture", "raw_moni_capture_on", 1)
/* IP to listen. Port/Portrange apply only on mirroring port capturing */
modparam("sipcapture", "raw_socket_listen", "10.0.10.1:5060")
/* Name of interface to bind on raw socket */
modparam("sipcapture", "raw_interface", "eth0")
/* children for raw socket */
modparam("sipcapture", "raw_sock_children", 4)
/* insert delayed */
#modparam("sipcapture", "db_insert_mode", 1)
/* Linux only */
/* Promiscious mode RAW socket. Mirroring port. */
modparam("sipcapture", "promiscious_on", 1)
/* activate BPF */
modparam("sipcapture", "raw_moni_bpf_on", 1)
With the following routing logic:
####### Routing Logic ########
request_route {
#sip_capture();
# CANCEL processing
# record routing for dialog forming requests (in case they
are routed)
# - remove preloaded route headers
remove_hf("Route");
if (is_method("INVITE|SUBSCRIBE"))
record_route();
route(REGISTRAR);
if ($rU==$null) {
# request with no Username in RURI
sl_send_reply("484","Address Incomplete");
exit;
}
# user location service
}
route[REGISTRAR] {
if (is_method("REGISTER")) {
if (!save("location"))
{
sl_reply_error();
}
exit;
}
}
The registration of the SIP Phone fails and we are getting the following
error in Kamailio.log file:
2016-11-16T09:49:28.809247-08:00 ubuntu /usr/local/sbin/kamailio[10612]:
ERROR: <core> [udp_server.c:550]: udp_send():
sendto(sock,0x7f60c7593910,481,0,192.168.26.4:14661,16): Bad file
descriptor(9)
2016-11-16T09:49:28.856080-08:00 ubuntu /usr/local/sbin/kamailio[10612]:
ERROR: sl [../../forward.h:192]: msg_send(): udp_send failed
2016-11-16T09:49:28.860251-08:00 ubuntu /usr/local/sbin/kamailio[10612]:
ERROR: registrar [reply.c:734]: reg_send_reply(): failed to send 200 OK
It would be highly appreciated to check what went wrong here.
Thanks in advance.
Ali Dakroub
Hello Daniel,
Yes that good alternative. I will use sql to fetch or insert staff.
Slava
From: "Daniel-Constantin Mierla" <miconda(a)gmail.com>
To: "sr-users" <sr-users(a)lists.sip-router.org>
Sent: Wednesday, 16 November, 2016 04:37:24
Subject: Re: [SR-Users] msilo
Hello,
as an alternative, I think it should work by using sql_query(...) to insert whatever values one would like to have in msilo table. This might be a quick workaround until someone will code the extension to get the body via a function parameter.
Cheers,
Daniel
On 15/11/16 16:07, Federico Cabiddu wrote:
Hi Slava,
if I understand correctly your scenario,
you could call t_on_failure before relaying the MESSAGE. In this way you should have access to the original message in the failure route triggered after receiving a final reply and you should be able to store it with the regular msilo functions.
Hope this helps.
Cheers,
Federico
On 15 Nov 2016 3:47 pm, "Slava Bendersky" < volga629(a)skillsearch.ca > wrote:
BQ_BEGIN
Hello Daniel,
I am not programmer, but I want place request if kaamilio devs can complete it .
Thanks
Slava.
From: "Daniel-Constantin Mierla" < miconda(a)gmail.com >
To: "sr-users" < sr-users(a)lists.sip-router.org >
Sent: Tuesday, 15 November, 2016 03:00:19
Subject: Re: [SR-Users] msilo
Hello,
for me it is fine to add a new parameter to m_store() that takes the body content.
Are you asking for more details of how can be done?
Cheers,
Daniel
On 13/11/16 07:08, Slava Bendersky wrote:
BQ_BEGIN
Hello Everyone,
I asking question/request to add improvement for msilo module where will have ability set $avp(i:body) in mod params. That will allow use it in m_store() by specifying body message $avp. In my case registration is on B2BUA so kamailio pass through/proxy to destination. In order to check user status online/offline kamailio wait for reply from B2BUA on MESSAGE status if it return error 503 that mean user offline and m_store(0 should store message in db, but the issue that error 503 is in final stage and MESSAGE body is not available any more. The improvement will allow specify body $var in m_store() so new way will be m_store($tu, $avp(body)).
Any help thank you.
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
--
Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
_______________________________________________ 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
_______________________________________________ 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
BQ_END
BQ_END
--
Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
_______________________________________________
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
Hello list,
We’re using dev version of Kamailio:
version: kamailio 5.0.0-dev4 (x86_64/linux) ff63e5
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: ff63e5
compiled on 15:46:49 May 31 2016 with gcc 4.9.2
Sometimes we encounter such issue:
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: <core> [db_row.c:114]: db_allocate_row(): no private memory left
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: db_mysql [km_row.c:57]: db_mysql_convert_row(): could not allocate row
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: db_mysql [km_res.c:188]: db_mysql_convert_rows(): error while converting row #16
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: db_mysql [km_res.c:217]: db_mysql_convert_result(): error while converting rows
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: db_mysql [km_dbase.c:261]: db_mysql_store_result(): error while converting result
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: <core> [db_query.c:139]: db_do_query_internal(): error while storing result
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: permissions [trusted.c:91]: reload_trusted_table(): failed to query database
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: <core> [db_row.c:114]: db_allocate_row(): no private memory left
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: db_mysql [km_row.c:57]: db_mysql_convert_row(): could not allocate row
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: db_mysql [km_dbase.c:444]: db_mysql_fetch_result(): error while converting row #15
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: ERROR: htable [ht_db.c:234]: ht_db_load_table(): Error while fetching result
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12276]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f5ebda8ae18), called from db_mysql: km_dbase.c: db_mysql_free_result(305), first free db_mysql: km_dbase.c: db_mysql_free_result(305) - aborting
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12281]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 16
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12268]: ALERT: <core> [main.c:739]: handle_sigs(): child process 12276 exited by a signal 6
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12268]: ALERT: <core> [main.c:742]: handle_sigs(): core was not generated
Nov 9 23:30:01 sbc01 /usr/local/sbin/kamailio[12268]: INFO: <core> [main.c:754]: handle_sigs(): terminating due to SIGCHLD
The thing is we heavily use mysql module, but only to update the in-memory tables by kamcmd. Each N minutes a special script updates the trusted,address and htable executing kamcmd. Kamailio (and kamcmd as well) talks only with localhost mysql server.
What I saw when encountered that issue on a live machine is that issue happens only with one of child processes, any other are ok.
Interesting thing is that happens at the same time with machines on the same «set», I mean that issue happened simultaneously with two our test machines which actually didn’t have any load on them.
The common thing between those machines is that they are in same subnet and local mysql databases are filled by scripts which query same external db.
I can’t confirm if there were or there weren’t any networking issues at that time with those machines, but as soon as kamcmd queries localhost that shouldn’t be the source of the issue.
So my questions are:
1. Has anyone encountered such thing?
2. Maybe the issue is already localized so it has sense to update? We actually use that on production (pls don’t throw too much rocks at me), so maintenance should be properly planned and I must be sure update won’t break anything.
3. If update is proposed - how to do it? I mean - follow the guide https://www.kamailio.org/wiki/install/devel/git or there are some other tips? I suppose in ideal world I don’t even stop the binary, only restart after make all && make install are done, as everything is in-memory. Am I correct?
4. When can we expect stable 5.0 version? (at least tell if it’s months/years)
Thanks in advance!
Hi fellow Kamailio people:
I was using the Siremis (v2.0) to manage my Kamailio application. I received a
message labeled "System Internal Error"
It seems, assuming I understand it correctly, that a table called
"kamailio.uacreg" does not exist in the database.
I receive this error when I click on the following:
Main System > SIP Admin Menu > Server Services > UACReg List function.
Any help in pointing me in the right direction would be great.
Thanks.
Kevin
2016-11-16 22:29:23 (GMT)] An exception occurred while executing this script:
Error message: #0, Error in query:: SELECT T0.id, T0.l_uuid, T0.l_username,
T0.l_domain, T0.r_username, T0.r_domain, T0.realm, T0.auth_username,
T0.auth_password, T0.auth_proxy, T0.expires FROM uacreg T0 LIMIT 10.
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'kamailio.uacreg'
doesn't exist
Script name and line number of error:
/var/www/siremis/openbiz/bin/data/BizDataObj_Lite.php:447
*function:* _run_search ( Array(2) ) @
/var/www/siremis/openbiz/bin/data/BizDataObj_Lite.php 243
*function:* fetch ( ) @ /var/www/siremis/openbiz/bin/easy/EasyForm.php 690
*function:* fetchDataSet ( ) @
/var/www/siremis/openbiz/bin/easy/FormRenderer.php 69
*function:* renderSmarty ( Object(EasyForm),
"/var/www/siremis/siremis/modules/ser/template/grid.tpl" ) @
/var/www/siremis/openbiz/bin/easy/FormRenderer.php 45
*function:* render ( Object(EasyForm) ) @
/var/www/siremis/openbiz/bin/easy/EasyForm.php 1648
*function:* renderHTML ( ) @ /var/www/siremis/openbiz/bin/easy/EasyForm.php 1538
*function:* render ( ) @ /var/www/siremis/openbiz/bin/easy/ViewRenderer.php 83
*function:* renderSmarty ( Object(EasyView),
"/var/www/siremis/siremis/modules/ser/template/view.tpl" ) @
/var/www/siremis/openbiz/bin/easy/ViewRenderer.php 40
*function:* render ( Object(EasyView) ) @
/var/www/siremis/openbiz/bin/easy/EasyView.php 274
*function:* _render ( ) @ /var/www/siremis/openbiz/bin/easy/EasyView.php 237
*function:* render ( ) @ /var/www/siremis/openbiz/bin/BizController.php 221
*function:* renderView ( "ser.view.UacregListView", "", "", Null, "" ) @
/var/www/siremis/openbiz/bin/BizController.php 107
*function:* dispatchRequest ( ) @ /var/www/siremis/openbiz/bin/BizController.php 32
*function:* include_once ( "/var/www/siremis/openbiz/bin/BizController.php" ) @
Reminder: speaker's deadline tomorrow, 17 November at 23:59 UTC
The Free RTC dev-room has already received some really exciting
talk proposals but there is still time for people to propose talks or
encourage friends or colleagues to speak.
Many other dev-rooms also have a deadline in the next few days and if
your topic is applicable to more than one dev-room, you are welcome
to make more than one submission. Please contact us or put a note in
the memo field at the top of the talk proposal if you do that.
All projects are encouraged to consider making a lightning talk too,
it is an excellent opportunity to get exposure for your project:
even though you only have 15 minutes, it can be a much larger and more
diverse audience than in some dev-rooms.
For full details, please see the original call for participation:
https://danielpocock.com/fosdem-2017-rtc-cfp
We invite all potential speakers and participants to discuss the selection
process and other aspects of FOSDEM on the Free-RTC mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc
Hi Slava,
if I understand correctly your scenario,
you could call t_on_failure before relaying the MESSAGE. In this way you
should have access to the original message in the failure route triggered
after receiving a final reply and you should be able to store it with the
regular msilo functions.
Hope this helps.
Cheers,
Federico
On 15 Nov 2016 3:47 pm, "Slava Bendersky" <volga629(a)skillsearch.ca> wrote:
Hello Daniel,
I am not programmer, but I want place request if kaamilio devs can complete
it .
Thanks
Slava.
------------------------------
*From: *"Daniel-Constantin Mierla" <miconda(a)gmail.com>
*To: *"sr-users" <sr-users(a)lists.sip-router.org>
*Sent: *Tuesday, 15 November, 2016 03:00:19
*Subject: *Re: [SR-Users] msilo
Hello,
for me it is fine to add a new parameter to m_store() that takes the body
content.
Are you asking for more details of how can be done?
Cheers,
Daniel
On 13/11/16 07:08, Slava Bendersky wrote:
Hello Everyone,
I asking question/request to add improvement for msilo module where will
have ability set $avp(i:body) in mod params. That will allow use it in
m_store() by specifying body message $avp. In my case registration is on
B2BUA so kamailio pass through/proxy to destination. In order to check
user status online/offline kamailio wait for reply from B2BUA on MESSAGE
status if it return error 503 that mean user offline and m_store(0 should
store message in db, but the issue that error 503 is in final stage and
MESSAGE body is not available any more. The improvement will allow
specify body $var in m_store() so new way will be m_store($tu,
$avp(body)).
Any help thank you.
Slava.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
_______________________________________________
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
_______________________________________________
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
Hello Everyone,
I am trying just forward MESSAGE through kamailio and I reported issue with mod_sms in freeswitch https://freeswitch.org/jira/browse/FS-9701. So I was need add work around on kamailio side. The issue that my setup MSILO should work in intercept mode meaning check when user online of offline and act as m_store() or m_dump() without rely on lookup("location");, because registration on B2BUA side. If m_store() will have additional parameter to store body this will allow check user state and send when need it.
On reply I put something like this to fix To, as work around and forward MESSAGE to client, but when client send MESSAGE kamailio receive on public interface and push out of public interface instead RELAY through local interface and then to B2BUA.
route[MESSAGE_FORWARD] {
xlog("L_INFO", "Incoming new SMS [$rm] from $tU --> $td\n");
if(fnmatch("$rs", "202") && fnmatch("$rr", "Accepted") && allow_trusted("$si", "$proto")) {
$avp(from) = $fu;
$avp(to) = $tu;
$avp(new_to) = "<" + $avp(to) + ">" + ";messagetype=SMS";
xlog("L_INFO", "Message Accepted by B2BUA --> [$rs] with [$rr] from [$avp(from)] to [$avp(to)]\n");
if(fnmatch("$fU", "offline")) {
xlog("L_INFO", "OFFLINE SMS: from [$fU] user --> $fU\n");
$avp(from) = $(avp(to){uri.user});
xlog("L_INFO", "OFFLINE SMS: Searching destination user $avp(oexten)\n");
sql_pvquery("cb", "select contact from location where username = '$avp(from)'","$avp(dst)");
xlog("L_INFO", "OFFLINE SMS: set new destination --> $avp(dst)\n");
$avp(new_to) = "<" + $(avp(dst){tobody.uri}) + ">" + ";messagetype=SMS";
}
$sht(a=>to) = $avp(new_to);
xlog("SMS from --> $fU domain $fd\n");
xlog("-------------------------------------\n");
xlog("L_INFO", "FROM --> $avp(from)\n");
xlog("L_INFO", "OLD_TO --> $avp(to)\n");
xlog("L_INFO", "NEW_TO --> $avp(new_to)\n");
}
if(compare_ips("$td", "10.18.130.27")) {
xlog("L_INFO", "Message from B2BUA contain domain --> $td . Updating...\n");
$avp(new_dst) = $(hdr(Route){param.value,received});
xlog("L_INFO", "New destination --> $avp(new_dst)\n");
$avp(new_to) = "<" + $avp(new_dst) + ">" + ";messagetype=SMS";
$sht(a=>to) = $avp(new_to);
remove_hf("To");
insert_hf("To: $sht(a=>to)\r\n", "To");
$du = $sht(a=>to);
}
}
From: "Federico Cabiddu" <federico.cabiddu(a)gmail.com>
To: "sr-users" <sr-users(a)lists.sip-router.org>
Sent: Tuesday, 15 November, 2016 11:07:44
Subject: Re: [SR-Users] msilo
Hi Slava,
if I understand correctly your scenario,
you could call t_on_failure before relaying the MESSAGE. In this way you should have access to the original message in the failure route triggered after receiving a final reply and you should be able to store it with the regular msilo functions.
Hope this helps.
Cheers,
Federico
On 15 Nov 2016 3:47 pm, "Slava Bendersky" < volga629(a)skillsearch.ca > wrote:
Hello Daniel,
I am not programmer, but I want place request if kaamilio devs can complete it .
Thanks
Slava.
From: "Daniel-Constantin Mierla" < miconda(a)gmail.com >
To: "sr-users" < sr-users(a)lists.sip-router.org >
Sent: Tuesday, 15 November, 2016 03:00:19
Subject: Re: [SR-Users] msilo
Hello,
for me it is fine to add a new parameter to m_store() that takes the body content.
Are you asking for more details of how can be done?
Cheers,
Daniel
On 13/11/16 07:08, Slava Bendersky wrote:
BQ_BEGIN
Hello Everyone,
I asking question/request to add improvement for msilo module where will have ability set $avp(i:body) in mod params. That will allow use it in m_store() by specifying body message $avp. In my case registration is on B2BUA so kamailio pass through/proxy to destination. In order to check user status online/offline kamailio wait for reply from B2BUA on MESSAGE status if it return error 503 that mean user offline and m_store(0 should store message in db, but the issue that error 503 is in final stage and MESSAGE body is not available any more. The improvement will allow specify body $var in m_store() so new way will be m_store($tu, $avp(body)).
Any help thank you.
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
--
Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
_______________________________________________
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
_______________________________________________
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
BQ_END
_______________________________________________
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
