Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : The *NEW* Frank Coluccio Technology Forum -- Ignore unavailable to you. Want to Upgrade?

To: Frank A. Coluccio who wrote (17563)	10/31/2006 3:40:43 PM
From: Lhn5	Read Replies (1) \| Respond to of 46821

<<From CTO at Cistera>>: A talk group is a multicast channel, so you can have up to 10 channels per talk group. So they could be UHF, VHF, 800 Mhz, IDEN whatever There is no limit to the number of users per channel, only the number of channels you can multiplex. You actually can bring multiple groups and multiple servers so you can actually add more CPU resources to increase even that number. The limitation is that realtime transcoding is very intensive (we do it in software not hardware). We only have about 30ms to play with before latency is a problem. The example I know well is the work we are doing in Georgia with the Georgia Emergency Management Agency (GEMA). The governor office has a coordinator in GEMA that helps the counties and cities build out a response plan and they have an initiative to reequip all the responders within 3-5 years. Our solution has been supported by GEMA as a way to get funds underneath the Networking budget into the radio systems. If they move to IP based radio systems then it comes under the IT/Telephony budget and for some reason there is more money for that. We can link both the emergency responder, network and telephony budgets together making it easier for the city to purchase.