(Page 6 of 6 in this chapter)

3.5 MVIP-95 Switching Examples

The following four examples show MVIP-95 switch connections for typical applications that: Connect local resources on the same board. Connect a network interface on one board to DSP resources on a board with no switch. Connect a network interface on one board to DSP resources on a board with a switch. Connecting a network interface on one board to a network interface on another board.

3.5.1 Local DSP Resource to Network Interface

An AG-T1 board connects to one T1 trunk and has 24 ports of DSP resources. A typical configuration connects the voice data and signaling data from one channel to on-board DSP resources. Connection to the MVIP bus is not necessary; all connections are made on local streams.
In the example shown in Figure 54, the call on timeslot 2 of the T1 trunk is connected with the DSP resources on timeslot 5. MakeConnection( LOCAL:0:2 to LOCAL:5:5 ) T1 trunk voice to DSP voice MakeConnection( LOCAL:4:5 to LOCAL:1:2 ) DSP voice to T1 trunk voice MakeConnection( LOCAL:2:2 to LOCAL:7:5 ) T1 trunk signaling to DSP signaling MakeConnection( LOCAL:6:5 to LOCAL:3:2 ) DSP signaling to T1 trunk signaling Figure 54. MVIP-95: Local DSP Resource to Network Interface

An S Connect board connects to 24 operator workstations with no DSP resources. A typical configuration is connecting voice and signaling from one operator station on an S Connect board to DSP resources on an AG-24 board using MVIP bus streams 8 and 9 (voice) and 10 and 11 (signaling).
In the example shown in Figure 55, the AG-24 is nailed up to streams 8 and 9 (voice) and 10 and 11(signaling). The operator on timeslot 2 is connected to DSP resources on timeslot 5 across the MVIP bus. MakeConnection( LOCAL:0:2 to MVIP:9:5 ) S Connect voice to DSP voice (at CT_D9:5) MakeConnection( MVIP:8:5 to LOCAL:1:2 ) DSP voice (at CT_D8:5) to S Connect voice MakeConnection( LOCAL:2:2 to MVIP:11:5 ) S Connect signaling to DSP signaling (at CT_D11:5) MakeConnection( MVIP:10:5 to LOCAL:3:2 ) DSP signaling (at CT_D10:5) to S Connect signaling Figure 55. MVIP-95: Network Interface to DSP Resource

In this example, the voice and signaling data from one operator station on an S Connect board are connected to DSP resources on an AG-8/DSP board. The AG-8/DSP board contains a switch block. The DSP resources are not nailed up to the bus; switch connections are required to connect the resources to the MVIP bus. The operator on timeslot 2 is connected to DSP resources on timeslot 5.
On the S Connect board, the following connections are made: MakeConnection( LOCAL:0:2 to MVIP:9:5 ) S Connect voice to H.100 bus CT_D9:5 MakeConnection( MVIP:8:5 to LOCAL:1:2 ) H.100 bus CT_D8:5 to S Connect voice MakeConnection( LOCAL:2:2 to MVIP:11:5 ) S Connect signaling to CT_D11:5 MakeConnection( MVIP:10:5 to LOCAL:3:2 ) CT_D10:5 to S Connect signaling
The following connections are made on the AG-8/DSP: MakeConnection( LOCAL:4:5 to MVIP:8:5 ) DSP voice to H.100 bus CT_D8:5 MakeConnection( MVIP:9:5 to LOCAL:5:5 ) H.100 bus CT_D9:5 to DSP voice MakeConnection( LOCAL:6:5 to MVIP:10:5 ) DSP signaling to H.100 bus CT_D10:5 MakeConnection( MVIP:11:5 to LOCAL:7:5 ) H.100 bus CT_D11:5 to DSP signaling Figure 56. MVIP-95: Station Interface to Network Interface Connection

In this example, a caller on timeslot 2 on one AG-T1 board is connected to a caller on timeslot 5 of a second AG-T1. Streams 8 and 9 of the MVIP bus are used to connect the voice paths.
On the first AG-T1 board, the following connections are made: MakeConnection( LOCAL:0:2 to MVIP:9:5 ) T1 voice to H.100 bus CT_D9:5 MakeConnection( MVIP:8:5 to LOCAL:1:2 ) H.100 bus CT_D8:5 to T1 voice
The second AG-T1 board the following connections are made: MakeConnection( LOCAL:0:2 to MVIP:8:5 ) T1 voice to H.100 bus CT_D8:5 MakeConnection( MVIP:9:5 to LOCAL:1:2 ) H.100 bus CT_D9:5 to T1 voice Figure 57. MVIP-95: Network Interface to Network Interface

(Page 6 of 6 in this chapter)