Customers can benefit from the BCM to Communication Sever 1000 networking on either PRI or IP trunks by taking advantage of centralized messaging, centralized trunking and centralized attendant.
Table 16 shows features of MCDN and their primary purposes: Table 16.
Features Purpose
NCT/NCRI/MWI Centralized Messaging
ICCL/TRO/TAT Centralized Trunking Camp-On/Break-In Centralized Attendant
Network Call Transfer
Network Call Transfer allows the transferee and the transfer destination to have each other’s name and number identification when a call is transferred in an MCDN network. The major benefit for a customer using this feature is Caller Line ID (CLID) for calls that are transferred from headquarters.
Figure 51 shows CLID on transferred calls. Figure 51.
Network Call Redirection Information (NCRI)
Network Call Redirection Information (NCRI) adds the ability to redirect a call across a private network and provide the necessary redirection information to the endpoint. The Network Call Redirection Information feature ensures that messages get to the correct mailbox and central messaging point.
Figure 52shows Set B using NCRI designating the correct mailbox. Figure 52.
Message Waiting Indication (MWI)
The Message Waiting Indication (MWI) feature complements centralized messaging networking because, using PRI or IP, it provides the ability to turn on a message waiting light at the remote sites that use the headquarters messaging system. This capability is supported between BCM and Communication 1000 systems only and is not supported between BCM systems.
In previous releases of BCM, the Business Series Terminals and the Norstar digital telephones (the M7000 series) informed the user that there was a voice message waiting by displaying the “Message for You” prompt on the LCD display.
BCM enables the Visual Ringing Indicator of the Business Series Terminals to also function as a MWI, or a message waiting lamp.
Figure 53 shows the MWI “lights” remote site message waiting lamp. Figure 53.
ISDN Call Connection Limitation (ICCL)
In an MCDN network it is possible for a call to be routed through many PBXs and create “loops.”
Endless loops can tie up trunks in a network, but not with the ISDN Call Connection Limitation feature enabled. The ICCL feature limits the number of call connections to prevent endless loops that can tie up the trunks in a network. On an IP call, only the signaling would be looped through many PBXs.
Figure 54 shows ICCL preventing endless loops by limiting call connections. In this scenario, the forwarding of the call would automatically stop once the number of sites in the call forwarding chain exceeded the ICCL limit. In the figures on the following pages, the arrows depict both the media and the signaling for PRI trunks. For IP trunks only the signaling is shown.
Figure 54.
Trunk Route Optimization (TRO)
Trunk Route Optimization is an MCDN feature that alleviates unnecessary tandeming and tromboning of trunks by searching for better call routes during the alerting phase of a call. When a call is made, TRO can create a loopback and occupy unused trunks. With the TRO feature enabled, the trunk routes can be optimized and logically connected from branch to branch.
Figure 55 and Figure 56 are examples of TRO that illustrate when Set A calls Set B which is forwarded to Set C. In the first figure (without TRO), the call utilizes two trunks, even when the call is forwarded from the
Communication Server 1000 to the second BCM. The second diagram depicts the call path with TRO enabled, showing that the end result is that the call is established directly between the two BCMs, using a single trunk.
Without TRO (2 PRI/IP Links) Figure 55.
With TRO (1PRI/IP Link) Figure 56.
Trunk Anti-Tromboning (TAT)
Like the Trunk Route Optimization feature, Trunk Anti-Tromboning is an MCDN feature that alleviates
unnecessary and tromboning of trunks by searching for better call routes during a transfer on an active call. The BCM is establishing a logical connection, always optimizing the best paths and routes for trunks.
Figure 57 and Figure 58 illustrate when Set A calls Set B and is transferred to Set C. In the case of a call being transferred from Set B to Set C when TAT is not enabled, two trunks on the same link are utilized: one for the original call from Set A to Set B and one for the second call from Set B to Set C. When TAT is enabled, the TAT signaling allows the originating switch (i.e. the first BCM) to transfer the call internally, freeing up both the outgoing and incoming trunks.
Without TAT (2PRI/IP Channels) Figure 57.
With TAT (1 PRI/IP Channels) Figure 58.
Camp-On
Camp-On allows an attendant on the Communication Server 1000 to camp-on a call to a user already on the phone. When the call is camped on, the user is informed that another call is waiting. The user can then accept the camped-on call by clearing one of his or her already established calls. The called party can also reject the camped- on call by using the Feature Reject code, F814, or the Do Not Disturb feature, F85.
Figure 59 shows the camp-on process. The red arrow depicts the call that Set A is actively engaged in, while the blue arrow shows the call flow for a call where the attendant at the Communication Server 1000 activates the Camp-On feature against Set A at the BCM.
Break-In
Break-In is a feature available to a centralized attendant in a network that allows the centralized attendant to reach a person who is already on a call. Sometimes critical situations require special attention and the Break-In feature lets the attendant politely interrupt if a matter of importance cannot wait for the called party to complete their phone conversation.
Figure 60 illustrates the call flow when the attendant at the Communication Server 1000 uses the Break-In functionality on an active call at the BCM.
Figure 60.
MCDN Tandem E. 164
This feature allows tandeming of Local, National, International and Special call types using a MCDN protocol variant. This includes MCDN over PRI and MCDN over IP.
Support for Messaging between BCM and DMS100
BCM may be connected directly with a DMS100 or SL100 via PRI-DMS100 or indirectly with these switches via a MCDN link with Meridian. The Message Waiting Indication (MWI) over PRI-DMS100 will be the same as over PRI-MCDN.
This supplements other functionality that allows Centralized Messaging with Meridian using MCDN, MCDN over IP supporting Meridian IPT and Communication Server for Enterprise, and BCM-to-BCM and BCM-to- Norstar