Re: [reSIProcate] hunt group using b2bua
Hi Daniel,
We implement hunt group through standard forking of INVITEs towards all
member extensions. The huntgroup mechanism allows a mix both serial and
parallel forks. The proxy decides when to do serial and parallel fork
by prioritizing through the Q-Value returned by the registrar. On top
of this, sipX also allows nesting of hunt groups. Thus, a hunt group
list can point to extensions which by themselves are also hunt groups.
Since this is all done using standard forking, there are a lot of
responses (provisional) that can reach the caller UA at once not to
mention that the proxy is also very busy trying to maintain transaction
states for each fork.
Joegen
On 08/23/2012 05:38 AM, Daniel Pocock wrote:
were looking at it to build a hunt group feature. Currently we've
>implemented hunt groups w/o a b2bua using sipXecs SIP tack but once
>the number of members hit's a 5 or 6 the amount of SIP traffic that is
>generate back to the caller is too much. I don't think this is
>limitation of the sipXecs SIP stack so much as it's a limitation of
>SIP in this area. I'm not a SIP expert but I can gather more details
>if nec. Our idea was that implementing this as a B2BUA would relieve
>the work from the client and allow the feature to scale.
>
>So my questions to group are:
>1. can large hunt groups be implemented w/o B2BUA
You would need to define hunt group and large in more specific detail.
Generally, a B2BUA may be able to do things that a proxy can't do, like
answering the A-leg of a call and keeping the caller occupied with hold
music while doing the hunt exercise. A proxy is not able to answer any
call itself.