Audio paging has been an essential feature in both Key Systems and PABX embodiments for decades.
While recognizing that Lync can scale to accommodate Fortune 100 class deployments, there are often departments or remote branches throughout the enterprise that operate as self-contained communities. Within those communities, having the ability to page individuals or groups of individuals is of high value.
Additionally, within the SMB market space currently occupied by feature-rich key systems, endpoint paging is often essential to the work flow in these environments.
Adding endpoint paging features to Lync has the potential to expand market adoption by being a direct replacement for key systems in business that rely on endpoint paging.
A paging endpoint may be a single IP telephone, a group of IP telephones, a Lync Client on a PC with multi-media hardware, or an external public address system. When the endpoint is an IP telephone, a USB tether to the PC is necessary for Lync client based control. From a RTP stream perspective, content delivery will be via unicast and leverage Lync A/V MCUs.
Audio content will emit from the endpoint speaker if the end point is idle. If a call is already in progress on the endpoint, paging will be blocked.
External paging systems are connected by means of a FXS gateway. Hardware interface to the customer's paging system is facilitated by the Customer or System Integrator.
A time stamped record for every page will be kept in a database for reporting purposes. Included in each record is the delivery status of the page indicating if the endpoint received the page or was blocked.
1. Real-time Audio Paging
2. Non Real-time queued audio paging
3. Stored Announcements
4. Text-to-Speech generated content in place of spoken audio
5. Dynamic location based paging