I'm trying to setup custom aliases out of a sql db that will sometimes
need to fork and need some help realizing how I can assign q values and
process them correctly. I'm using kam 1.5.
Let's assume I query for our main support line and return 3 URIs from
the db along with a separate column for the q.
Sip:us-support@mycomp.com q=1.0
Sip:uk-support@mycomp.com q=1.0
Sip:in-support@mycomp.com q=0.90
Based on the values I'd want to parallel fork on the first two to send
this to my UK and US support line, if that fails cancel the first two
branches and route to India. Just to see if I was on the right track I
tried adding them as branches using $br, which from what I understand is
the only way to add branches from avps/variables. I added them by
appending ;q=1.0 on the end of the URI like you would see in a Contact
header but I don't think that's valid. Calls to $(branch(q) return
<null> so it obviously doesn't take.
If I were to just fork sequentially I could just load them into avps and
call it in a failure route, but how do I handle a combination of the
two? Am I wrong in trying to specify the q along with the URI?
I noticed serialize_branches was removed in 1.4, which is what I use in
production today in 1.3 - do I need to use the replacements in TM to
order them and add the branches?
Thanks in advance.
--------------------------------------------------------------------------
This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto.
Hi All,
First off - thank you for this module.
I have configured two redundant DB sources in my kamailio confiuration. The
DB's are accessed from Kamailio for redundancy pruposes.
Kamailio and the primary DB are on the same hardware node. The secondary DB
is on a remote host.
If Kamailio is up and both MySQL DB's are up, the config works like a
charm. If the primary or the secondary DB becomes unreachable while
Kamailio is up, the config handles the exception and all works well.
However, if any of the DB servers becomes unreachable and Kamailio is
restarted, Kamailio can no longer start.
Below is an excerpt from my config file:
# -- sqlops params
modparam("sqlops","sqlcon","pridb=>mysql://root:@localhost/db_table")
modparam("sqlops","sqlcon","secdb=>mysql://root:@192.168.1.231/db_table")
/var/log/messages
Jun 26 06:16:00 test-ser /sbin/kamailio[20217]:
ERROR:db_mysql:db_mysql_new_connection: driver error: Can't connect to local
MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Jun 26 06:16:00 test-ser /sbin/kamailio[20217]: ERROR:core:db_do_init: could
not add connection to the pool
Jun 26 06:16:00 test-ser /sbin/kamailio[20217]: ERROR:sqlops:sql_connect:
failed to connect to the database [pridb]
Jun 26 06:16:00 test-ser /sbin/kamailio[20217]: ERROR:core:init_mod_child:
failed to initializing module sqlops, rank 1
Jun 26 06:16:00 test-ser /sbin/kamailio[20217]: ERROR:core:main_loop:
init_child failed for UDP listener
What is the proper way of using multiple database servers with Kamailio?
Thanks in advance.
--JR
Hi all,
i'm pleased to announce that i give a talk about the kamailio project on
the linuxtag 2009 in Berlin.
The title of the talk is "Building carrier grade voice over IP systems
with kamailio", on wednesday the 24th june afternoon. Further details can
be found in the conference program at:
http://www.linuxtag.org/2009/de/program/freies-vortragsprogramm/mittwoch/vo…
I'll be also present on the linuxtag on thursday, so if you would like to
meet for some discussions, just drop me a mail (off-list).
With best regards,
Henning Westerholt