[cisco-voip] Broadcast Hunt Group query

[Anthony Holloway]

My gut feeling is that, since you have 4,000 phones, trying to do something
to the lot of them all at once will not be possible. You'd have a better
chance if you selected key phones in certain areas and used the speaker
phone. E.g., In a cubicle farm, 1 in 25 phones could be elected. Of course
this means you'd need a seating chart.

An ip overhead paging solution might be the ultimate solution, but I
realize you asked about phones.

Do you want to make the phones play a tone or do you want to have a human
voice speak?

The best option is probably going to avoid call signaling and instead
leverage the phones API. Possibly the play command or join multicast
command.

For either command, you might want to offload the authentication to a fast
web server that answers blindly with a "true."

The play command puts stress on your TFTP server and its max connections.

The join multicast command requires mroute on your network. This how single
wire informacast works. Have you used an ip multicast paging solution
before? Do you have one?
On Thu, Nov 6, 2014 at 7:27 AM Andy <andy.carse at gmail.com> wrote:

> I know that this is going to bring a smile to some people, but I’ll ask
> the question.
> I have a request come in
> “Can we use the phones to mark the start and finish time for marking the
> silence on 11 Nov”
>
> I thought about using a broadcast hunt group, but there are 4,000 handsets.
>
> I have read somewhere that you can only use a handfull of devices in a
> broadcast hunt group, so I’m looking for some divine inspiration should
> anyone have any to spare.
> obviously if it can’t be easily achieved then I do have the option to say
> no.
>
> Andy
> andy.carse at gmail.com
>
>
>
>
> _______________________________________________
> 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/20141106/3b6c3ca1/attachment.html>