That's quite easy - that's a typical load-balancer setup.
Just store the mapping for example in a DB and then use the sqlops
module to query the DB and get the respective IP address of the user.
But before you add this "routing logic" I would recommend to add
Kamailio with a static forwarding
Hello,
On 11/28/13 5:58 PM, Adnan wrote:
Hi,
1. After adding t_newtran() as shown below, some how this got fixed
i.e. ACK got routed.
However, we are disputed in considering t_newtran() to have caused the
fix.
if (is_method("ACK")) {
if (t_check_trans()) {
Attaching with gdb and getting the backtrace (as Ovidiu said), will be
very useful
The function futex_wait_queue_me() is from kernel, so it might be an
operation from the kernel about reading the udp packages. So we cannot
tell without the full trace if a kamailio function is blocking the fute
Hi,
I have a Kamailio 3.3.3 server that currently reports the following
errors upon execution of t_relay() for certain initial INVITEs.
daemon.err /usr/sbin/kamailio[26916]: ERROR:
[sip_msg_clone.c:505]: ERROR: sip_msg_cloner: cannot allocate memory
daemon.err /usr/sbin/kamailio[26916]: ERRO
Hi Andrew
A very simple place to start -- have you tried upping the memory
allocations in /etc/default/kamailio to see if it fixes the issues? We had
some issues with shared memory that went away when we changed around these
settings.
All the best.
Will Ferrer
On Fri, Nov 29, 2013 at 11:30 A
