Hi all,
Is there anything special required to get radius support into the acc
module?
I have tried the following...
make distclean
make config modules_include="mediaproxy auth_radius group_radius uri_radius
misc_radius" group_include="mysql standard"
make deb
But alas it still seems to not have it.
I have confirmed that the radius libraries are installed aswell.
ii libradiusclient-ng-dev 0.5.6-1
Enhanced RADIUS client library development f
ii libradiusclient-ng2 0.5.6-1
Enhanced RADIUS client library
Cheers,
Kris
Hello,
I am testing a cellphone software that registers with an Asterisk server
through an outbound proxy (Kamailio+rtpproxy). I am capturing network
traffic using wireshark and i notice that the SIP Register message from
the cellphone has an extra byte in the Content-Length header, which
causes Kamailio to discard the message with the following error output :
- ERROR:core:parse_content_length: parse error near char [13][^M]
- ERROR:core:get_hdr_field: bad content_length header
Could it be that this byte was appended somewhere downstream(possibly at
the wireless router..) or can i be sure that the byte was added during
SIP Message construction by the cellphone software ?
Thanks in advance,
Vikram.
Hello,
please use public mailing list for such questions. Direct messages get
long delayed or lost in most of the cases. Mailing list has plenty of
developers and community users that can help you faster. Besides that,
new people can benefit of older discussions.
On 2/11/10 2:14 AM, Kris Amy wrote:
> Hi Daniel,
>
> It would seem to me that the stored procedure on
> http://siremis.asipto.com/install-accounting/ is for PostgreSQL. I'm
> going to try and getting it working with MySQL.
it is for mysql.
Cheers,
Daniel
>
> Just thougth you may want to update the page.
>
>
--
Daniel-Constantin Mierla
eLearning class for Kamailio 3.0.0
* http://www.asipto.com/
On 2/11/10 11:16 AM, Kris Amy wrote:
> On Thu, Feb 11, 2010 at 8:09 PM, Daniel-Constantin Mierla
> <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
>
> Hello,
>
> ok, then the only point in mod_init of siptrace that causes
> initialization error without printing a log message is when you
> haven't set the trace_flag parameter:
> http://kamailio.org/docs/modules/3.0.x/modules_k/siptrace.html#id2520001
>
> Cheers,
> Daniel
>
>
> Hi Daniel,
>
> That fixed it.
>
> Perhaps there is a bug in that it's not picking up the default of 0?
in the sources the default is -1, which means disabled -- docs needs to
be updated.
Thanks for pointing,
Daniel
--
Daniel-Constantin Mierla
eLearning class for Kamailio 3.0.0
*http://www.asipto.com/
Hello,
I am running Kamailio version 1.5 and rtpproxy version 1.2. I have
enabled NAT support in Kamailio.cfg. I have a UA behind NAT (UA
IP:192.168.2.101), and the UA registers with an Asterisk server (Public
IP) through an outbound proxy running Kamailio and rtpproxy with Public IP.
Registration succeeds, however when making an outbound call from the UA
to a cellphone, there is only one sided voice. This is happening because
Asterisk is addressing rtp streams to the UA's local IP address instead
of its PublicIP:port.
Why is the IP address not being rewritten in the SDP ? Is there an
alternate way of invoking rtpproxy (with flags) such that the IP address
in the SDP is rewritten ?
Thanks and Regards,
Vikram.
PS : Below is the main routing section of my kamailio.cfg
route{
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
exit;
}
# NAT detection
route(4);
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 {
if (is_method("SUBSCRIBE") && uri == myself) {
# 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;
}
# CANCEL processing
if (is_method("CANCEL"))
{
if (t_check_trans())
t_relay();
exit;
}
t_check_trans();
# record routing
if (!is_method("REGISTER|MESSAGE"))
record_route();
# account only INVITEs
if (is_method("INVITE")) {
setflag(1); # do accounting
}
if (!uri==myself)
{
append_hf("P-hint: outbound\r\n");
route(1);
}
# requests for my domain
if( is_method("PUBLISH|SUBSCRIBE"))
route(2);
if (is_method("REGISTER"))
{
if (isflagset(5)) {
setbflag(6);
# setbflag(7);
}
if (!save("location"))
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] {
if (check_route_param("nat=yes")) {
setbflag(6);
}
if (isflagset(5) || isbflagset(6)) {
route(5);
}
/* example how to enable some additional event routes */
if (is_method("INVITE")) {
#t_on_branch("1");
t_on_reply("1");
t_on_failure("1");
}
if (!t_relay()) {
sl_reply_error();
}
exit;
}
# Presence route
/* uncomment the whole following route for enabling presence server */
route[2]
{
# if presence enabled, this part will not be executed
if (is_method("PUBLISH") || $rU==null)
{
sl_send_reply("404", "Not here");
exit;
}
return;
}
# Caller NAT detection route
/* uncomment the whole following route for enabling Caller NAT Detection */
route[4]{
force_rport();
if (nat_uac_test("19")) {
if (method=="REGISTER") {
fix_nated_register();
} else {
fix_nated_contact();
setflag(6);#VR
}
setflag(5);
}
return;
}
# RTPProxy control
/* uncomment the whole following route for enabling RTPProxy Control */
route[5] {
if (is_method("BYE")) {
unforce_rtp_proxy();
} else if (is_method("INVITE")){
force_rtp_proxy();
}
if (!has_totag()) add_rr_param(";nat=yes");
return;
}
branch_route[1] {
xdbg("new branch at $ru\n");
}
onreply_route[1] {
xdbg("incoming reply\n");
if ((isflagset(5) || isbflagset(6)) && status=~"(183)|(2[0-9][0-9])") {
force_rtp_proxy();
}
if (isbflagset(6)) {
fix_nated_contact();
}
}
failure_route[1] {
if (is_method("INVITE")
&& (isbflagset(6) || isflagset(5))) {
unforce_rtp_proxy();
}
if (t_was_cancelled()) {
exit;
}
}
---------- Forwarded message ----------
From: Kris Amy <kris(a)amy.id.au>
Date: 2010/2/11
Subject: Re: [Kamailio-Users] Siptrace and Kamailio 3.0.0
To: Daniel-Constantin Mierla <miconda(a)gmail.com>
On Thu, Feb 11, 2010 at 8:09 PM, Daniel-Constantin Mierla <miconda(a)gmail.com
> wrote:
> Hello,
>
> ok, then the only point in mod_init of siptrace that causes initialization
> error without printing a log message is when you haven't set the trace_flag
> parameter:
> http://kamailio.org/docs/modules/3.0.x/modules_k/siptrace.html#id2520001
>
> Cheers,
> Daniel
>
Hi,
Just wondering if anyone is using Siptrace with Kamailio 3.0.0. The module
fails to load and I have no idea why (or how to get more information than
from debug = 99).
0(13453) DEBUG: <core> [sr_module.c:871]: DEBUG: init_mod: siptrace
0(13453) ERROR: <core> [sr_module.c:874]: init_mod(): Error while
initializing module siptrace
ERROR: error while initializing modules
Cheers,
Kris
Hello list,
I have fresh installation of Debian Squeeze on X86_64.
I downloaded source tarball
http://www.kamailio.org/pub/kamailio/latest/src/kamailio-3.0.0_src.tar.gz
and did 'make deb' there.
So, I got following debian packages:
kamailio_3.0.0_amd64.deb, kamailio-berkeley-modules_3.0.0_amd64.deb,
kamailio-carrierroute-modules_3.0.0_amd64.deb
kamailio-cpl-modules_3.0.0_amd64.deb,
kamailio-ldap-modules_3.0.0_amd64.deb,
kamailio-memcached-modules_3.0.0_amd64.deb
kamailio-mysql-modules_3.0.0_amd64.deb, kamailio-nth_3.0.0_amd64.deb,
kamailio-perl-modules_3.0.0_amd64.deb
kamailio-postgres-modules_3.0.0_amd64.deb,
kamailio-presence-modules_3.0.0_amd64.deb,
kamailio-purple-modules_3.0.0_amd64.deb
kamailio-radius-modules_3.0.0_amd64.deb,
kamailio-snmpstats-modules_3.0.0_amd64.deb,
kamailio-tls-modules_3.0.0_amd64.deb
kamailio-unixodbc-modules_3.0.0_amd64.deb,
kamailio-utils-modules_3.0.0_amd64.deb,
kamailio-xmlrpc-modules_3.0.0_amd64.deb
kamailio-xmpp-modules_3.0.0_amd64.deb
I installed packages:
kamailio_3.0.0_amd64.deb, kamailio-mysql-modules_3.0.0_amd64.deb,
kamailio-presence-modules_3.0.0_amd64.deb,
kamailio-xmlrpc-modules_3.0.0_amd64.deb
Created database, changed passwords for openser and openserro users in
MySQL as well as in kamailio config files, enabled MySQL.
DUMP_CORE=yes in /etc/default/kamailio, also added '-w
/var/run/kamailio' to options.
Created test user with kamctl.
Started kamailio with init script: /etc/init.d/kamailio start:
Feb 7 22:05:10 kamailio kamailio: INFO: <core> [tcp_main.c:4150]:
init_tcp: using epoll_lt as the io watch method (auto detected)
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: usrloc
[hslot.c:53]: locks array size 512
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[udp_server.c:166]: INFO: udp_init: SO_RCVBUF is initially 124928
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[udp_server.c:166]: INFO: udp_init: SO_RCVBUF is initially 124928
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[udp_server.c:166]: INFO: udp_init: SO_RCVBUF is initially 124928
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[udp_server.c:217]: INFO: udp_init: SO_RCVBUF is finally 262142
Feb 7 22:05:10 kamailio /usr/sbin/kamailio[2695]: INFO: ctl
[io_listener.c:224]: io_listen_loop: using epoll_lt io watch method
(config)
Then I tried to connect to kamailio server with softphone Zoiper, and
kamailio crashes immediately:
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2700]: : <core>
[pass_fd.c:283]: ERROR: receive_fd: EOF on 21
Feb 7 22:05:20 kamailio kernel: [ 1051.407643] kamailio[2689]: segfault
at c2 ip 00007fa8b5947b19 sp 00007fff48ff9700 error 4 in
tm.so[7fa8b5917000+72000]
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: ALERT: <core>
[main.c:722]: child process 2689 exited by a signal 11
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: ALERT: <core>
[main.c:725]: core was not generated
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: INFO: <core>
[main.c:737]: INFO: terminating due to SIGCHLD
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2691]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2699]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2698]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2687]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2697]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2690]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2696]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2688]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2695]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2680]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2694]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2693]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2692]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2686]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2685]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2681]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2684]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2682]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2700]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2683]: INFO: <core>
[main.c:788]: INFO: signal 15 received
Feb 7 22:05:20 kamailio /usr/sbin/kamailio[2678]: ERROR: ctl
[ctl.c:379]: ERROR: ctl: could not delete unix socket /tmp/ser_ctl:
Operation not permitted (1)
Feb 7 22:05:20 kamailio kernel: [ 1051.432646] kamailio[2678]: segfault
at 12 ip 00007fa8b592ae43 sp 00007fff48ff9f40 error 4 in
tm.so[7fa8b5917000+72000]
For unknown reason core was not generated.
Any ideas ?
Many thanks in advance,
Dmitri
Hi All,
It was to my understanding that this function was part of the core and thus
didn't come from a module.
The relevant code snippet is
if(!save("location"))
{
xlog("L_ERR", "Saving contact failed - M=$rm RURI=$ru F=$fu
T=$tu IP=$si ID=$ci\n");
sl_reply_error();
exit;
}
The error I'm getting is..
0(20467) DEBUG: <core> [sr_module.c:516]: find_export_record: <save> not
found
0(20467) DEBUG: <core> [sr_module.c:516]: find_export_record: <save> not
found
0(20467) : <core> [cfg.y:3329]: parse error in config file
/etc/kamailio/kamailio.cfg, line 656, column 21: unknown command, missing
loadmodule?
Cheers,
Kris