Hi all:
It's my first mail to the community and I know that will be a great
community to share knowledge.
OS Debian 6.4
Kamailio 4.1
I have the same problem that Oliver Roth describes in
http://lists.sip-router.org/pipermail/sr-users/2013-October/080096.html,
but in Kamailio 4.1:
Module carrierroute not working starting from version kamailio 4.1
trying to activate carrierroute in kamailio.cfg
loadmodule "carrierroute.so"
i get the following error when starting kamailio
(5794) ERROR: <core> [sr_module.c:599]: load_module(): ERROR:
load_module: could not open module
</usr/local/lib64/kamailio/modules/carrierroute.so>:
/usr/local/lib64/kamailio/modules/carrierroute.so: undefined symbol:
cfg_set_error_function
0(5794) : <core> [cfg.y:3408]: yyerror_at(): parse error in config
file /usr/local/etc/kamailio/kamailio.cfg, line 245, column 12-28:
failed to load module
ERROR: bad config file (1 errors)
Any idea?
Maybe him o someone has the solution.
Thanks all for your great work.
Best regards.
--
*Eduardo Alonso Gil*
VoIP Systems Engineer @ Quobis <http://www.quobis.com/> | e:
eduardo.alonso(a)quobis.com | t: +34902999465
Visit our booth at *MWC Barcelona*. CS60 Spanish Pavilion. More
info<http://www.quobis.com/index.php?option=com_content&task=view&id=236&Itemid=…>
Hello All,
I'm trying to use keepalive_timeout with 4.1.1 as described here:
http://lists.sip-router.org/pipermail/sr-users/2012-August/074337.html
I believe I've followed these configuration steps and those defined
in the nathelper module.
Here are the relevant portions of my config:
modparam("nathelper", "natping_interval", 60)
modparam("nathelper", "keepalive_timeout", 180)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "sipping_from", "sip:pinger@domain.com")
modparam("nathelper", "sipping_method", "OPTIONS")
modparam("nathelper", "sipping_bflag", 9)
And of course a setting the correct branch flag (verified) during
REGISTER handling:
setbflag(9);
My goal is to use SIP OPTIONS messages to verify the reachability of
all of my endpoints (not just NATd ones). I would just lower my
re-registration timeout but there are other issues associated with
that kind of change.
With my current configuration (after a successful registration) a SIP
OPTIONS message is sent and replied to:
U 4.2.2.1:5060 -> 4.2.2.2:5060
OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0.
Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0.
From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-9627292.
To: sip:user372@4.2.2.2:5060;ob.
Call-ID: 8af79586-93072f43-7c4cf55(a)4.2.2.1.
CSeq: 1 OPTIONS.
Content-Length: 0.
.
U 4.2.2.2:5060 -> 4.2.2.1:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 4.2.2.1:5060;received=4.2.2.1;branch=0.
Call-ID: 8af79586-93072f43-7c4cf55(a)4.2.2.1.
From: <sip:pinger@domain.com>;tag=uloc-5303810e-7c78-1-2273f0eb-9627292.
To: <sip:user372@4.2.2.2:5060>;tag=0;ob.
CSeq: 1 OPTIONS.
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
NOTIFY, REFER, MESSAGE, OPTIONS.
Accept: application/sdp, application/pidf+xml, application/xpidf+xml,
application/simple-message-summary, message/sipfrag;version=2.0,
application/im-iscomposing+xml, text/plain.
Supported: replaces, 100rel, timer, norefersub.
Allow-Events: presence, message-summary, refer.
User-Agent: My_UA.
Content-Length: 0.
.
If I kill the registered UA (making it unavailable) Kamailio endlessly
sends OPTIONS messages, never receives a reply, and never removes the
registration from usrloc:
U 4.2.2.1:5060 -> 4.2.2.2:5060
OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0.
Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0.
From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-b627292.
To: sip:user372@4.2.2.2:5060;ob.
Call-ID: 8af79586-b3072f43-f35cf55(a)4.2.2.1.
CSeq: 1 OPTIONS.
Content-Length: 0.
.
U 4.2.2.1:5060 -> 4.2.2.2:5060
OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0.
Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0.
From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-c627292.
To: sip:user372@4.2.2.2:5060;ob.
Call-ID: 8af79586-c3072f43-b75cf55(a)4.2.2.1.
CSeq: 1 OPTIONS.
Content-Length: 0.
.
U 4.2.2.1:5060 -> 4.2.2.2:5060
OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0.
Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0.
From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-d627292.
To: sip:user372@4.2.2.2:5060;ob.
Call-ID: 8af79586-d3072f43-7b5cf55(a)4.2.2.1.
CSeq: 1 OPTIONS.
Content-Length: 0.
.
U 4.2.2.1:5060 -> 4.2.2.2:5060
OPTIONS sip:user372@4.2.2.2:5060;ob SIP/2.0.
Via: SIP/2.0/UDP 4.2.2.1:5060;branch=0.
From: sip:pinger@domain.com;tag=uloc-5303810e-7c78-1-2273f0eb-e627292.
To: sip:user372@4.2.2.2:5060;ob.
Call-ID: 8af79586-e3072f43-3f5cf55(a)4.2.2.1.
CSeq: 1 OPTIONS.
Content-Length: 0.
.
(and on, and on, and...)
Eventually the registration timeout kicks in, the usrloc entry is
removed, and Kamailio stops sending OPTIONS to the (long) unreachable
endpoint.
Is this expected behavior? What am I doing wrong?
Thanks!
--
Kristian Kielhofner
Hello,
setting the hash size to 32MB is way too much, are you having like 100
000 000 active calls at the same time?
The size of the hash is used for computing the number of slots in the
hash table, not the capacity in terms of memory size of all items stored
in hash table.
Cheers,
Daniel
On 03/02/14 07:33, Shankar wrote:
>
> Hi Alex,
>
> We set the hash size to 32 MB and found that the hash size is not the
> same as configured one. At the max it was taking 64KB.
>
> Regards,
>
> Shankar
>
> Date: Mon, 03 Feb 2014 00:27:29 -0500
>
> From: Alex Balashov <abalashov(a)evaristesys.com
> <mailto:abalashov@evaristesys.com>>
>
> To: sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
>
> Subject: Re: [SR-Users] Regd. MAX_LDG_LOCKS
>
> Message-ID: <52EF28C1.5010204(a)evaristesys.com
> <mailto:52EF28C1.5010204@evaristesys.com>>
>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 02/03/2014 12:22 AM, Shankar wrote:
>
> > Also we found that in ?dialog.c? the variable dlg_hash_size should be
>
> > ?unsigned int?. Hope this will be taken care in next release of
> Kamailio.
>
> How did you arrive at that conclusion?
>
> --
>
> Alex Balashov - Principal
>
> Evariste Systems LLC
>
> 235 E Ponce de Leon Ave
>
> Suite 106
>
> Decatur, GA 30030
>
> United States
>
> Tel: +1-678-954-0670
>
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>
> *From:*Shankar [mailto:shankar.rk@plintron.com]
> *Sent:* Monday, February 03, 2014 10:53 AM
> *To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List'
> *Subject:* Regd. MAX_LDG_LOCKS
>
> Hello,
>
> Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c?
>
> Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if
> the hash size is increased?
>
> Also we found that in ‘dialog.c’ the variable dlg_hash_size should be
> ‘unsigned int’. Hope this will be taken care in next release of Kamailio.
>
> Regards,
>
> Shankar
>
>
>
> _______________________________________________
> 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://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hello,
it is not a really necessary to increase the value of the locks. For
better performances you can do it, but again, it is not a must.
Cheers,
Daniel
On 04/02/14 06:50, Shankar wrote:
>
> Hi,
>
> Can someone clarify here please?
>
> Regards,
>
> Shankar
>
> *From:*Shankar [mailto:shankar.rk@plintron.com]
> *Sent:* Monday, February 03, 2014 10:53 AM
> *To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List'
> *Subject:* Regd. MAX_LDG_LOCKS
>
> Hello,
>
> Can anyone brief about MAX_LDG_LOCKS in dlg_hash.c?
>
> Should I increase the value of MAX_LDG_LOCKS (hardcoded to 2048) if
> the hash size is increased?
>
> Regards,
>
> Shankar
>
>
>
> _______________________________________________
> 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://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi,
following the documentation, the following lines need to be updated on the init.d script.
DAEMON=/usr/local/sbin/kamailio
CFGFILE=/usr/local/etc/kamailio/kamailio.cfg
Anyway, there is no CFGFILE already setted.
Is it correct to add CFGFILE along with DAEMON?
On top of this, in the check_fork () procedure, there’s a reference to a cfg_file that is nonexistent.
In my installation i changed it to the real path of the kamailio.cfg file generated during installation.
check_fork ()
{
if grep -q "^[[:space:]]*fork[[:space:]]*=[[:space:]]*no.*" /usr/local/etc/kamailio/kamailio.cfg; then
log_failure_msg "Not starting $DESC: fork=no specified in config file; run /etc/init.d/kamailio debug instead"
exit 0
fi
}
Is it correct to change path in the check_fork procedure with the correct one?
Regards,
Only very few presentations accepted at Kamailio World Conference &
Exhibition are not yet published. In a matters of days we should have
the draft of the schedule published.
It is again a good variety of topics around Kamailio and other open
source VoIP applications, presenting experiences from the field, showing
new product and solutions or open debate and demos panels. You can lean
about various ways of deploying scalable platforms with Open Stack,
Erlang or asynchronous, carrier grade charging systems, managing
security in VoIP deployments or how to do real time troubleshooting.
More details about presentations are available at:
- http://conference.kamailio.com/k02/schedule/
Information about speakers can be found at:
- http://conference.kamailio.com/k02/speakers/
In order to allow a fair enough time to see what the content of the
event is going to be, the early registration deadline has now been set
to this Friday, February 21. Don't miss the chance to learn from about
30 sessions and meet more than one hundred professionals in real time
communications and open source technologies:
- http://conference.kamailio.com/k02/registration/
Looking forward to meeting you in Berlin,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hello All,
I need some clarification on the function uac_reg_request_to.
The doc says "This function can be used to send an authenticated request
to a remote user in the uac registrations table"
Does this mean I can forward a SUBSCRIBE request, or any request for
that matter, to an upstream server that's Kamailio is registered to via
the UAC module?
Secondly, I'm having trouble matching the user on this function. The
error is: "ac [uac_reg.c:996]: uac_reg_request_to(): no user: 2503" User
2503 does exist in the uac_reg table in column "l_username". What if I
want to match by UUID instead? How does that get mapped back to a local
user?
Thanks
--
Isaac McDonald
SusCall, LLC
E-Mail: imcdona(a)suscall.com
Hi folks,
We identified a memory leak in *utils* module, when calling the
http_query() function.
a memory piece is allocated with malloc() to store http request result
string (functions.c:54), but this memory is never freed.
There is also a possible crash issue, because curl_easy_getinfo() is
called *after* curl_easy_cleanup(), which must not be done (see
http://curl.haxx.se/libcurl/c/curl_easy_cleanup.html)
I attached patches to fix those issues (applies to 4.0 branch)
Regards,
Guillaume Bour
Hi
I successfully install siremis 4.0.0 +kamailio 4.1 on my ubuntu (32 bit)
server.
Kamailio was installed successfully and I can now run "kamctl moni" and see
a nice status screen.
I had to setup again siremis (by deleting the install.lock and opening the
localhost/siremis setup again) but one that was achieved I can now login in
to the siremis site without errors.
Now to the problem:
Once I enter "groups" and press "add" I get the following error displayed:
[2014-02-12 20:46:33 (GMT)] An exception occurred while executing this
script:
Error message: #8192, preg_replace(): The /e modifier is deprecated, use
preg_replace_callback instead
Script name and line number of error:
/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compiler.class.php:270
*function:* errorHandler ( 8192, "preg_replace(): The /e modifier is
deprecated, use preg_replace_...",
"/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compi...", 270,
Array(8) ) @ /home/rubi/siremis-4.0.0/openbiz/bin/sysheader.inc 117
*function:* userErrorHandler ( 8192, "preg_replace(): The /e modifier is
deprecated, use preg_replace_...",
"/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compi...", 270,
Array(8) ) @
*function:* preg_replace (
"~\{\*(.*?)\*\}|\{\s*literal\s*\}(.*?)\{\s*/literal\s*\}|\{\s*php...",
"'{php' . str_repeat(" ", substr_count('\0', " ")) .'}'", "<form id="{$
form.name}" name="{$form.name}"> <div style="paddin..." ) @
/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty_Compiler.class.php
270
*function:* _compile_file (
"/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail....",
"<form id="{$form.name}" name="{$form.name}"> <div style="paddin...", Null
) @ /home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty.class.php
1484
*function:* _compile_source (
"/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail....",
"<form id="{$form.name}" name="{$form.name}"> <div style="paddin...", Null,
"/home/rubi/siremis-4.0.0/siremis/themes/default/template/cpl/%%2..." ) @
/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty.class.php 1417
*function:* _compile_resource (
"/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail....",
"/home/rubi/siremis-4.0.0/siremis/themes/default/template/cpl/%%2..." ) @
/home/rubi/siremis-4.0.0/openbiz/others/Smarty/libs/Smarty.class.php 1256
*function:* fetch (
"/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail...." ) @
/home/rubi/siremis-4.0.0/openbiz/bin/easy/FormRenderer.php 95
*function:* renderSmarty ( Object(EasyForm),
"/home/rubi/siremis-4.0.0/siremis/modules/system/template/detail...." ) @
/home/rubi/siremis-4.0.0/openbiz/bin/easy/FormRenderer.php 45
*function:* render ( Object(EasyForm) ) @
/home/rubi/siremis-4.0.0/openbiz/bin/easy/EasyForm.php 1648
*function:* renderHTML ( ) @
/home/rubi/siremis-4.0.0/openbiz/bin/easy/EasyForm.php 1538
Can anyone tell me what I did wrong, or how can I re-install completely
siremis?
Hopefully that's not a bug :/
With Regards,
Rubi Mazaki
Email: rubimazaki(a)gmail.com
Hi all!
my usrloc database use postgress.
In config I had:
modparam("usrloc", "db_mode", 1)
after day of work I see strange thing:
# kamctl ul show --brief | grep -c AOR
26
psql -U kamailio -c "select * from location;"
...
(1 row)
26 registered users in inner kamailio's memory and only 1 in database.
See in doc:
1 - Write-Through scheme. All changes to usrloc are immediately
reflected in database too. This is very slow, but very reliable. Use
this scheme if speed is not your priority but need to make sure that no
registered contacts will be lost during crash or reboot.
I think saved locations in inner memory database must be identical. Am
I wrong?
--
WBR, Victor
JID: coyote(a)bks.tv
JID: coyote(a)bryansktel.ru
I use FREE operation system: 3.12.9-calculate GNU/Linux
