Telephony in a Multi-Facility Environment / Multi-Facility Inbound Redundancy Using DNIS |
Configure your PBX properly to ensure support for multi-facility inbound redundancy.
When multiple facilities share a PBX, you must specify separate Guest and Direct Access numbers for each facility to realize speech recognition benefits for incoming callers.
For example, let's consider this scenario when a deployment has three facilities: West Philadelphia, South Philadelphia, and Center City (the principal facility). The following table shows the grammars searched for speech recognition at the hunt group prompt when each facility has a separate hunt number and all facilities share a pool of lines for incoming calls. The system relies on the DNIS to determine which facility's grammars to use for the incoming call.
The following table shows information on shared telephony with one shared pool of lines for all facilities.
Facility |
Guest and Direct Access Numbers |
Grammars Searched |
---|---|---|
West Philadelphia |
215-549-1300 215-549-1301 |
|
South Philadelphia |
215-549-2300 215-549-2301 |
|
Center City |
215-549-3300 215-549-3301 |
|
The following figure illustrates inbound redundancy is achieved using shared telephony between multiple facilities.
Someone places a call to a Vocera device user.
The Central Office routes the call.
The PBX skips the VSTG that is down (even though it is in the routing table).
The call is routed to the VSTG that is online.
The call is received by the Voice Service, which knows which facility's grammars to use based on the dialed number.
The Vocera device user receives the call.