Hi Stefano,
A better approach (without the need of DB) is to use the
get_dialog_info() function. See:
http://www.opensips.org/html/docs/modules/1.6.x/dialog.html#id293888
The idea is that after the LB function, add the selected destination
(stored in $dd variable) and the agent name
Hi Ovidiu,
I got your point - I was making a comment to complete your statement.
I agree that rate limit and concurrent call limit are 2 protection
mechanism that normally are more suitable in different scenarios.
But more or less, this is up to the admin to decide :) (which to use and
in
Hi Brian,
Brian Artigas wrote:
Hi All,
I just built a new VM running CentOS 5.4 with the latest stable
version of OpenSIPS from svn – I’m assuming 1.6.4-2. I copied my cfg
file that worked perfectly on another VM that was running 1.6.1 to the
new VM. I tweaked a few things: IP address,
2011/2/27 Bogdan-Andrei Iancu bog...@opensips.org:
And when you have a 123 call for agent, search the to get the destination of
the ongoing call to that agent:
$var(x) = agent ??
get_dialog_info(dst,$var(dst),agent,$var(x));
works well, thanks!
(i improved with if(get_dialog_info(...)))
2011/2/24 Toyima Dias toyim...@gmail.com:
I have an Asterisk as a GW, i don't want to ask for authentication to
incoming calls (coming from the Asterisk), so i did the following:
Previously i added the IP of the Asterisk to the table domain so the
function is_from_local could check the from
Hello!
I found active dialog statistic problem
For example in dialog::active_dialogs I have 130 active calls, after restart
Opensips I already have dialog::active_dialogs nearly 260, i.e. the number of
active dialogs increase by 2.
Meanwhile, after restart, opensipsctl fifo dlg_list
