Hi,
since kamailio 3.2.1 I've had problems with using dlg_var to store extra accounting fields with the acc module (using db_extra and mysql). When I set a dlg_var in the request route, the first acc row (INVITE) appears as if the dlg_var was empty, but looks fine for the second (BYE) row. In 3.2.0 both rows got the value I assigned. missed_calls doesn't appear to have this problem. Any ideas? The problem also seems to exist in kamailio 3.2.2. I've done a git bisect and the problem seems to appear since commit 5bdee1ffe820d3e9e75898bb252d1660b4bbad60.
Thanks,
Jon
Hi,
any help will be graet....
* hi,
*>*
*>* when i moved the /etc/init.d/kamailio file. kamailio did not start at
boot.
*>* now, i set the debug level to 4 and run kamailio in both ways.
*>*
*>* 1. "/etc/init.d/kamailio start"
*>*
* the resault was :
*Feb 1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:202]: qm_malloc_init: QM_OPTIMIZE=16384, /ROUNDTO=2048
Feb 1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:204]: qm_malloc_init: QM_HASH_SIZE=2099, qm_block
size=218344
Feb 1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:205]: qm_malloc_init(0x7f1cf585b000, 2147483648),
start=0x7f1cf585b000
Feb 1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:213]: qm_malloc_init: size= 2147483648, init_overhead=218440
Feb 1 19:59:04 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/shm_mem.c:203]: shm_mem_init: success*
>*
*>* you can see the shm_mem size is 2048Mb.
*>*
*
2."kamailio"
the resault was :
*Feb 1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:202]: qm_malloc_init: QM_OPTIMIZE=16384, /ROUNDTO=2048
Feb 1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:204]: qm_malloc_init: QM_HASH_SIZE=2099, qm_block
size=218344
Feb 1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:205]: qm_malloc_init(0x7f8618310000, 33554432),
start=0x7f8618310000
Feb 1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/q_malloc.c:213]: qm_malloc_init: size= 33554432, init_overhead=218440
Feb 1 19:56:50 net-ivr-KamIN-J1 kamailio: DEBUG: <core>
[mem/shm_mem.c:203]: shm_mem_init: success*
**
the resault is 32Mb.
any ideas?
>*
*>* On Wed, Feb 1, 2012 at 5:01 PM, Jason Penton <jason.penton at
smilecoms.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>wrote:
*>*
*>>* I am not familiar with Centos but I suspect there is another script
being
*>>* run from somewhere. What I would do is move the /etc/init.d/kamailio
script
*>>* somewhere safe (your home directory for eg). Then reboot and see if
*>>* kamailio still starts - if it does you need to find out whihc script is
*>>* being called and where it is.
*>>*
*>>* If you are not running X by default you are prob in runlevel 3. If you
*>>* are running X, then it will be 5. check where you runlevel scripts are
*>>* pointing. e.g.
*>>*
*>>* ls -al /etc/rc3.d/SXXkamailio (X = [0-9])
*>>*
*>>* Cheers
*>>* Jason
*>>*
*>>* On Wed, Feb 1, 2012 at 4:26 PM, Uri Shacked <uri.shacked at
gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>wrote:
*>>*
*>>>* Hi,
*>>>*
*>>>* when i reboot the machine, it starts with 32Mb and i do not understand
*>>>* why...
*>>>* so, does it use a startup file that i am not familiar with?
*>>>* what is the appropriate runlevel? how do i set it and where?
*>>>*
*>>>* thanks,
*>>>* Uri
*>>>*
*>>>*
*>>>* >Hi Sammy,
*>>>* >
*>>>* >When you use the init script, it is starting Kamailio with the
correct
*>>>* >arguments to get the environment you wish (-m 2048 probably). If
*>>>* however,
*>>>* >you just call kamailio these args are not there. Im not sure why you
are
*>>>* >running with kamailio command directly. Why don't you add your init
*>>>* script
*>>>* >to the appropriate runlevel for auto startup?
*>>>* >
*>>>* >Cheers
*>>>* >Jason
*>>>*
*>>>* On Wed, Feb 1, 2012 at 3:06 PM, Uri Shacked <ushacked at gmail.com<
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
*>>>* wrote:
*>>>*
*>>>* >* Hi again....
*>>>* *>*
*>>>* *>* i installed kamailio 3.2.2 today.
*>>>* *>* i used the chkconfig tool to get kamailio run at boot.
*>>>* *>* i edited both /etc/init.d/kamailio and /etc/default/kamailio files
*>>>* to run
*>>>* *>* with 2048Mg of memory.
*>>>* *>* now, when i run /etc/init.d/kamailio start, it starts with the
right
*>>>* *>* amount of memory.
*>>>* *>* when i rum "kamailio" only, it starts with 32Mb....
*>>>* *>*
*>>>* *>* i use centos 6.2 64bit.
*>>>* *>* any ideas?
*>>>* *>*
*>>>* *>*
*>>>* *>*
*>>>* *>*
*>>>* *>*
*>>>* *>* On Tue, Oct 25, 2011 at 1:18 PM, Uri Shacked <ushacked at
gmail.com<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
*>>>* wrote:
*>>>* *>*
*>>>* *>>* Hi.
*>>>* *>>* I already checked it all. The kamailio start and stop command did
*>>>* not
*>>>* *>>* work. The init script i used was for debian. Now i use another
*>>>* script,
*>>>* *>>* for centos. It works. I add the kamailio proccess with chkconfig
*>>>* tool.
*>>>* *>>* Thanks.
*>>>* *>>*
*>>>* *>>* On 10/25/11, Sammy Govind <govoiper at gmail.com<
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
*>>>* wrote:
*>>>* *>>* > Thanks Alex,
*>>>* *>>* >
*>>>* *>>* > Hey Uri, can you check if you've /etc/init.d/kamailio file
*>>>* exists - open
*>>>* *>>* > that file if exists and cross verify few parameters.
*>>>* *>>* > Few of these are as follows
*>>>* *>>* >
*>>>* *>>* > PATH=/sbin:/bin:/usr/sbin:/usr/bin
*>>>* *>>* > DAEMON=*/usr/local/sbin/kamailio*
*>>>* *>>* > NAME=kamailio
*>>>* *>>* > DESC=kamailio
*>>>* *>>* > HOMEDIR=/var/run/
*>>>* *>>* > *PIDFILE*=$HOMEDIR/$NAME.pid
*>>>* *>>* > DEFAULTS=*/etc/default/kamailio.default*
*>>>* *>>* > RUN_KAMAILIO=yes
*>>>* *>>* >
*>>>* *>>* > Make sure /etc/default/kamailio.default file exits. here are
the
*>>>* *>>* contents of
*>>>* *>>* > my file.
*>>>* *>>* >
*>>>* *>>* > RUN_KAMAILIO=yes
*>>>* *>>* > USER=kamailio
*>>>* *>>* > GROUP=kamailio
*>>>* *>>* > MEMORY=64
*>>>* *>>* > DUMP_CORE=no
*>>>* *>>* >
*>>>* *>>* > On Tue, Oct 25, 2011 at 3:38 AM, Klaus Darilion <
*>>>* *>>* > klaus.mailinglists at pernau.at<
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>
*>>>* wrote:
*>>>* *>>* >
*>>>* *>>* >> Test the startupscript if they work:
*>>>* *>>* >>
*>>>* *>>* >> /etc/init.d/kamailio start
*>>>* *>>* >> /etc/init.d/kamailio stop
*>>>* *>>* >>
*>>>* *>>* >> If this works, then make sure to have proper symlinks from the
*>>>* *>>* >> corresponding runlevel to the startup script. Do it manually
or
*>>>* use the
*>>>* *>>* >> chkconfig tool.
*>>>* *>>* >>
*>>>* *>>* >> klaus
*>>>* *>>* >>
*>>>* *>>* >>
*>>>* *>>* >> On 24.10.2011 08:00, Uri Shacked wrote:
*>>>* *>>* >>
*>>>* *>>* >>> hi again,
*>>>* *>>* >>> i found out that on my centos 5.4 the command
*>>>* start-stop-daemon that
*>>>* *>>* the
*>>>* *>>* >>> /etc/init.d/kamailio uses is not recognized.
*>>>* *>>* >>> it is kamailio3.2 any ideas?
*>>>* *>>* >>>
*>>>* *>>* >>>
*>>>* *>>* >>> On Mon, Oct 24, 2011 at 3:03 PM, Uri Shacked <ushacked at
*>>>* gmail.com<
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
*>>>* *>>* >>> <mailto:ushacked at gmail.com<
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>>>
*>>>* wrote:
*>>>* *>>* >>>
*>>>* *>>* >>> Hi,
*>>>* *>>* >>> what is the best way to start kamailio at boot?
*>>>* *>>* >>> the example in the install is not working for me....
*>>>* *>>* >>>
*>>>* *>>* >>>
*>>>* *
*>>>*
*>>*
*>>* This email is subject to the disclaimer of Smile Communications (PTY)
Ltd. at http://www.smilecoms.com/disclaimer
*>>*
*>>*
*>*
*
Hi,
anyone knows why the dialog module leaves active dialogs even after a bye
was recieved when using sipp?
once i had issues with the record route and i forced sipp to deal with
that, is there something to set on the bye sent by sipp?
BR,
Uri
Hi all,
I have have been attempting to implement Remote-Party-ID support using
the app_lua module in Kamailio. Since more than one Remote-Party-ID
header may exist, this requires accessing the header pseudo-variable
with an index.
For example: $(hdr(Remote-Party-ID)[2])
Doing this causes Kamailio to output an error to the log when it fails
to parse the PV: 2012-02-02 16:38:58|E| 6(26940) ERROR: app_lua
[app_lua_sr.c:892]: invalid pv [$(hdr(remote-party-id)[0])] (-1/26)
This was triggered using sr.pv.get("$(hdr(remote-party-id)[0])") from
within Lua.
I have also tried sr.pv.get("$hdr(remote-party-id)[0]") which also
failed: 2012-02-02 18:26:28|E|15(26956) ERROR: app_lua
[app_lua_sr.c:892]: invalid pv [$hdr(remote-party-id)[0]] (21/24)
Am I doing something wrong? If not, any ideas for a workaround?
Thanks for your time.
Hello,
I have clients which register to Kamailio using an auth username. The from username is used for caller id on an INVITE. This causes a problem if the client does not use the auth username in the from for the REGISTER. The caller id number is then saved as the AOR username which doesn't correspond to a valid account. Is there a way I can store the authorized username instead of the From username in the AOR?
Thanks,
Spencer
hi,
i didn't fully understand the differences between the debug level set at
the Global Parameters section and the debugger module.
i would like to start kamailio with debug level 0, and to be able to raise
or lower the level in command line.
the log is set to be writen to /var/log/kamailio, and i can trace it using
"tail".
so, anyideas how to use the debug options with the option to change level
at runtime?
BR,
Uri
Hi guys! I'm facing some problems with dialog information while trying to
implement a HA environment.
We have 2 clustered SIP servers working as a Active/Standby failover and
the use of a Virtual IP address. We want to make sure that if proxy #1 goes
down during a call, proxy #2 would be able to handle the sequential
requests for that call, since both proxies are using the same database for
dialog module information and we have set the db_mode dialog parameter to 1
(REALTIME - any dialog information changes will be reflected into the
database immediately). Instead, what happened is proxy #2 was not aware of
the dialog and gave us a "500 Server error occurred" message after
receiving the BYE. Here are the log errors:
/usr/local/sbin/opensips[12617]: New request: BYE
/usr/local/sbin/opensips[12617]: The request has TO tag
/usr/local/sbin/opensips[12617]: cannot match request to a dialog
/usr/local/sbin/opensips[12617]: ERROR:dialog:w_validate_dialog: null
dialog /usr/local/sbin/opensips[12617]: in-dialog bogus request
/usr/local/sbin/opensips[12617]: validate_dialog return: -4
/usr/local/sbin/opensips[12617]: loose_route() performed, rr headers were
decoded /usr/local/sbin/opensips[12617]: ERROR:core:parse_uri: uri too
short: <0> (1) /usr/local/sbin/opensips[12617]:
ERROR:core:parse_sip_msg_uri: bad uri <0> /usr/local/sbin/opensips[12617]:
ERROR:tm:new_t: uri invalid /usr/local/sbin/opensips[12617]:
ERROR:tm:t_newtran: new_t failed /usr/local/sbin/opensips[12617]: Could not
execute t_relay()
Virtual IP address is working, a new call goes through with no problem.
Apparently, the dialog module is not saving all dialogs information to the
database right away. Does anyone know about any other info we should be
storing in the database, using some sort of module parameter or exported
function from config file? In other words, what do I need to do in order to
send an initial INVITE to one server and, when that server goes down, send
the BYE to another server with the same call dialog?
Thanks in advance.
Mariana.
Hello
I want to run Kamailio under FreeBSD. I compiled with the makefiles under
freebsd packages. But
It gives alotof errors. I want to use 3.2.2 version but I cannot compile.
Could you help me
To compile in FreeBSD ?
Another question, which is the best OS for Kamailio ? In the forums, they
are saying FreeBSD is more stable and
More performans.
Regards
Serhat
Hello
After much reading I have come to the realization that after years of
using Asterisk I know very little about Sip.
I have my Kamailio box up, I have Asterisk 1.8.x running with realtime
working. I thought it would be just a case of registering SIP trunks
from my provider to the kamailio and registering our internal asterisk
servers to the kamailio.
Much of what I read talks about using Asterisk as the PSTN interface,
but that interface is through a sip trunk purchased from a provider.
Won't Kamailio be the PSTN gateway? The idea here is to pool all the
sip trunks from the various hosted asterisk solutions (VM running
asterisk) and point them all to a proxy to facilitate the aggregation
of traffic.
I have been reading SIP tutorials and the mailing list archives. If
anyone has a sample config and perhaps a little direction it would be
highly appreciated.
Thank you
Greg
Hi,
I changed the location of the DB kamailio works with. i copied the relevalt
tables and changed the relevant names in the cfg file.
while trying to load kamailio i realized that it misses the "veresion"
table.
first - can someone explain the version table usage?
second, after creating and copying that data from the version table. i
tried to load kamailio again and got the follwing:
" DEBUG: carrierroute [cr_db.c:345]: loading, cycle 0 0(24689) ERROR:
<core> [daemonize.c:307]: Main process exited before writing to pipe"
any help?
thanks,
Uri
