Whoops I think I meant "longest Idle". This is how cisco defines the option
Longest Idle—Calls go to the directory number that has
been idle for the longest time, according to the time
stamp of the most recent call to the hunt group taken by
that extension. If that extension is unavailable, the
Whoops I meant Brad. Thanks. I will try to figure out how to do least
called->gets called and post.
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/Hunt-Group-with-Opensips-tp5459644p5464036.html
Sent from the OpenSIPS - Users mailing list archive at Nabb
That would my late night testing and copying code twice :)
On Wed, 2010-08-25 at 20:05 -0700, osiris123d wrote:
> Deon,
>
> Just wondering why you set the next hunt number twice in your else
> condition??
>
>
> } else {
> #Not the 1st time, let's pull the next in order
> $avp(s:hunt_n
Deon,
Just wondering why you set the next hunt number twice in your else
condition??
} else {
#Not the 1st time, let's pull the next in order
$avp(s:hunt_num) = $(avp(s:hunt_list){s.select,$avp(s:hunt_pos),,});
xlog("L_NOTICE","***Trying #$avp(s:hunt_pos) of $avp(s:total_hunts) in
Thanks Brad.
Really Appreciated.
This helps a lot.
Kind Regards
On Aug 25, 2010, at 9:11 AM, Brad Bendy wrote:
> Deon,
>
> It's kind of sloppy as was thrown together for testing, but it works.
>
> The IAD we were sending calls to sends a 486 if the line is in use, we then
> route advance on
Deon,
It's kind of sloppy as was thrown together for testing, but it works.
The IAD we were sending calls to sends a 486 if the line is in use, we
then route advance on the 486 until all destinations have been tried.
We made the hunt_list static for testing, but avp_db_load or memcached
it was w
Brad
would you be so kind and show a sample config for how you setup the serial fork?
I have to set this up but have no idea where to start.
Some sort of template would be great just to give an idea of how this is done.
I should be able to figure out the rest as I go along.
Thanks
Kind Regard
I just setup serial hunting and it was pretty easy.
We stored the list of users to be called in memcached, counted how many
total users need to be called and advanced to the next one in
failure_route as needed, set a ring timeout and then have it go to a
voicemail server or wherever it needed to g
I saw a post saying it was possible to do hunt groups with col, but i wasn't
sure how one would keep up with calls to each group user so that one could
do "least called user" or even the user that was next in line to be called.
I am guessing avps and contact array could help, but i was just wonde
