[cisco-voip] Broadcast Algorithm for Hunt Group

[Jonathan Charles]

All phones have two lines, a shared-line and a regular line.

All calls go to a shared-line on all phones, with a busy trigger set to one.

CFB for that line goes to a hunt group, with the other phones.

However, this would cause the first call to ring all phones and the second
call to ring in a normal hunt fashion, it would not satisfy your requirement
that the 'second call ring the same extension that already has the first
call on it...'

That doesn't really make sense... so, whoever answers the first call, gets
all calls? Or am I misunderstanding this.



Jonathan

On 12/4/06, David Fielder (US) <David.Fielder at us.didata.com> wrote:
>
>  I have a customer who is using a hunt group. They are using the broadcast
> algorithm for call distribution. The first call to the Pilot number will
> ring all phones as it is suppose to. However, the second call that comes in
> while the first call is still active will only ring the phone DN that
> answered the first call. It does not ring the other members who are Idle.
> Has anyone seen this issue before?
>
>
>
> *David Fielder*
>
> Senior Engineer
>
> Dimension Data
>
> david.fielder at us.didata.com
>
>
>
> ------------------------------
>
> * Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleting
> it from your computer. Thank you. *
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061204/35a08401/attachment-0001.html