(Page 1 of 1 in this chapter)

Chapter 3

The Switch Block Model

3.1 Introduction

3.2 MVIP-90 Switch Model

3.3 MVIP-90 Switching Examples

: 3.3.1 Local DSP Resource to Network Interface
: 3.3.2 Connecting Network Interface to DSP Resources (1 switch)
: 3.3.3 Connecting Network Interface to DSP Resources (2 switches)
: 3.3.4 Connecting Network Interface to Network Interface

3.4 MVIP-95 Switch Model

3.5 MVIP-95 Switching Examples

: 3.5.1 Local DSP Resource to Network Interface
: 3.5.2 Connecting Network Interface to DSP Resources (1 switch)
: 3.5.3 Connecting Network Interface to DSP Resources (2 switches)
: 3.5.4 Connecting Network Interface to Network Interface

3.1 Introduction

The switch block model is a convention of naming streams and timeslots connected to a switch block. A switch block model presents a logical interface to the application that hides any hardware dependencies. When making switch connections, applications address the switch block by using a switch block model.
The switch block model is represented by a switch model diagram as shown in Figure 29. The switch block model defines: The telephony bus input and output streams that are connected to the switch block. The board's local resources (network interfaces, DSP resources, conference bridges, etc.). The local resource input and output streams that are connected to the switch block. Figure 29. Example Switch Block Model
There are two switch models used for MVIP switching: MVIP-90 switch model MVIP-95 switch model
The MVIP-90 switch model is used with boards on the MVIP-90 bus. The MVIP-95 switch model is used by boards on the MVIP-90, H-MVIP, and H.100 busses. Figure 30. Switch Block Models

3.2 MVIP-90 Switch Model

The MVIP-90 bus has 16 physical wires labeled DSi0..7 and DSo0..7. In the MVIP-90 switch model, applications address the 16 MVIP bus wires as streams 0..15. Figure 31. MVIP-90 Bus Physical Wires
Local resources on the board (i.e., network interfaces, DSP resources, etc.) are also connected to the switch block. Local resources are located on streams starting at 16.
By convention, even numbered streams are used for voice information and odd numbered streams are used for signaling information.
The stream addressing in the MVIP-90 switch model is designed to facilitate full-duplex connections between DSP resources and network interfaces. A DSP resource to network connection involves two switch commands to connect: The network interface input to the DSP resource output. The network interface output to the DSP resource input. Figure 32. Full-Duplex Connection
DSP resources and network interfaces are connected over the MVIP bus. By convention, DSP resources receive input from timeslots on DSi streams. DSP resources send output to timeslots on DSo streams. Network interfaces receive input from timeslots on DSo streams and send output to timeslots on DSi streams. Figure 33. DSP Resources and Network Interfaces Connected to the MVIP Bus
The DSP resources are nailed up to the MVIP bus. For a full-duplex connection, the application makes two switch connections on the switch block of the network interface to connect: The network interface input located on a local stream:timeslot to the MVIP stream:timeslot of DSP resource output (DSo wire). The network interface output located on a local stream:timeslot to the MVIP stream:timeslot of the DSP resource input (DSi wire). Figure 34. DSP Resource to Network Interface Switch Connections
Each MVIP bus wire (DSo or DSi) is labeled differently on the input side and the output side of the switch block. On the input side, the DSo0..7 wires are addressed as streams 0..7 and DSi0..7 as streams 8..15. On the output side, the same DSi0..7 wires are addressed as streams 0..7 and DSo0..7 as streams 8..15.
The stream number used in switching commands refers to a different physical wire based on whether the stream is being used as an input or an output to the switch block. Figure 35. MVIP-90 Switch Block Connections to MVIP Bus
The naming convention is designed to facilitate a full-duplex DSP resource to network interface connection where input streams (DSi streams) are paired with output streams (DSo streams).
Using the MVIP-90 switch model, a full-duplex switch connection consists of two commands: MakeConnection ( A to B ) MakeConnection ( B to A )
For example, DSP resources are nailed up to the MVIP bus on stream 2. To connect a local resource on stream 16:1 to the MVIP bus stream 2:3, the switch command is: MakeConnection( 16:1 to 2:3 )
This connects the voice output to the MVIP bus. To make a full-duplex connection, the MVIP bus is connected to the voice input: MakeConnection( 2:3 to 16:1 )
In the first command, stream 2 is the input and stream 16 is the output. In the second command, stream 16 is the input and stream 2 is the output. The input and output always refer to the switch block. MakeConnection ( input to output )
As shown in Figure 36, stream n refers to DSi n and DSo n. The actual physical wire is determined by whether the stream is an input or an output in the switch command.
In the first command, stream 2 maps to the MVIP data stream DSo2. In the second command, stream 2 maps to the MVIP data stream DSi2. Stream 16 is a local stream which connects to the network voice interfaces. Figure 36. MVIP-90 Data Streams
The two switch commands correspond to: MakeConnection ( 2:3 to 16:1 ) DSo2:3 to network interface output:1 MakeConnection ( 16:1 to 2:3 ) network interface input:1 to DSi2:3 Figure 37. Example Switch Connections
Since a network interface receives input from DSo streams, the input of a switch command specifies the MVIP bus wires DSo0..7. For example, stream 0 in the input side of a connection command refers to DSo0. Since a network interface sends output onto DSi streams, the output of a switch command specifies MVIP bus wires DSi0..7. For example, stream 0 in the output side of a switch command refers to DSi0. Figure 38. Switch Command Stream Mapping
A DSP resource to network interface connection is referred to as a forward connection. In a forward connection, a network interface uses DSo streams for input and DSi streams for output. In the switch commands, the streams 0..7 are used to address the MVIP bus wires.
Streams 8..15 are the same DSo and DSi wires, but in the other direction. These streams are used to make a reverse connection. A network interface to network interface connection is referred to as a reverse connection. Reverse connections are made to connect a call to an operator station or to connect a call out to another phone line. Figure 39. Forward and Reverse Connections
When connecting two network interfaces together, one network interface must drive DSo and receive input from DSi. This connection would use streams 8..15.
In a network interface to network interface connection, there are no connections which are nailed up to the telephony bus. Each board must make two switch connections. Figure 40. Network to Network Connection
For example, connecting the fourth T1 channel (timeslot 3) from one AG-T1 to the first T1 channel (timeslot 0) on another AG-T1 requires the following commands. In the example, stream 4:timeslot 7 on the MVIP bus is used to connect the two channels.
On AG-T1 #1, connect the T1 channel to the MVIP bus: MakeConnection ( 4:7 to 16:3 ) MakeConnection ( 16:3 to 4:7 )
At this point, the channel from the first AG-T1 board is connected to the MVIP bus. It is sending output to DSi and receiving input from DSo. Now, connect the channel on the second AG-T1 board to drive DSo and receive input from DSi: MakeConnection ( 12:7 to 16:1 ) MakeConnection ( 16:1 to 12:7 )
The switch commands on board 1 are: MakeConnection ( 4:7 to 16:3 ) DSo4:7 to network interface input:3 MakeConnection ( 16:3 to 4:7 ) network interface output:3 to DSi4:7
The switch commands on board 2 are: MakeConnection ( 12:7 to 16:0 ) DSi4:7 to network interface input:0 MakeConnection ( 16:0 to 12:7 ) network interface output:0 to DSo4:7 Figure 41. Reverse Connection Commands
Figure 42 shows the mapping of MVIP streams in forward and reverse connections. For forward connections, the input of a switch command specifies the MVIP bus wires DSo0..7. The output of a switch command specifies the MVIP bus wires DSi0..7. For reverse connections, the input of a switch command refers to the MVIP bus wires DSi0..7. The output of a switch command refers to MVIP bus wires DSo0..7. Figure 42. Reverse Command Stream Mapping
The MVIP-90 switch block model for the AG-T1 board is shown in Figure 43. The specific use of each stream is as follows: MVIP-90 Streams Streams 0..15 Trunk Voice Information Stream 16 timeslots 0..23 Trunk Signaling Information Streams 17 timeslots 0..23 DSP Voice Information Stream 18 timeslots 0..23 DSP Signaling Information Stream 19 timeslots 0..23 HDLC controller Stream 20 Figure 43. AG-T1 MVIP-90 Switch Model

MVIP-90 Streams	Streams 0..15
Trunk Voice Information	Stream 16 timeslots 0..23
Trunk Signaling Information	Streams 17 timeslots 0..23
DSP Voice Information	Stream 18 timeslots 0..23
DSP Signaling Information	Stream 19 timeslots 0..23
HDLC controller	Stream 20

3.3 MVIP-90 Switching Examples

The following four examples show the 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 block. Connect a network interface on one board to DSP resources on a board with a switch block. Connect a network interface on one board to a network interface on another board.

3.3.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 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 44, the call on timeslot 2 of the T1 trunk is connected with the DSP resources on timeslot 5. MakeConnection( 16:2 to 18:5 ) connect T1 trunk voice to DSP voice MakeConnection( 18:5 to 16:2 ) connect DSP voice to T1 trunk voice MakeConnection( 17:2 to 19:5 ) connect T1 trunk signaling to DSP signaling MakeConnection( 19:5 to 17:2 ) connect DSP signaling to T1 trunk signaling Figure 44. MVIP-90: Local DSP Resource to Network Interface

3.3.2 Connecting Network Interface to DSP Resources (1 switch)

An S Connect board connects to 24 operator workstations with no on-board DSP resources. A typical configuration connects voice and signaling data from one operator station on an S Connect board to DSP resources on an AG-24 board.
In the example shown in Figure 45, the AG-24 is nailed up to streams 4 (voice) and 5 (signaling) using a configuration file. To connect the operator interface on timeslot 2 to DSP resources on timeslot 5, the following connections are made: MakeConnection( 16:2 to 4:5 ) connect S Connect voice to DSP voice (at DSi4:5) MakeConnection( 4:5 to 16:2 ) connect DSP voice (at DSo4:5) to S Connect voice MakeConnection( 17:2 to 5:5 ) connect S Connect signaling to DSP signaling (at DSi5:5) MakeConnection( 5:5 to 17:2 ) connect DSP signaling (at DSo5:5) to S Connect signaling Figure 45. MVIP-90: Network Interface to DSP Resource

3.3.3 Connecting Network Interface to DSP Resources (2 switches)

In this example, the voice and signaling from one operator station on an S Connect board is 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 across the MVIP bus.
On the S Connect board, the following connections are made: MakeConnection( 16:2 to 4:5 ) S Connect voice to MVIP bus DSi4:5 MakeConnection( 4:5 to 16:2 ) MVIP bus DSo4:5 to S Connect voice MakeConnection( 17:2 to 5:5 ) S Connect signaling to MVIP bus DSi5:5 MakeConnection( 5:5 to 17:2 ) MVIP bus DSo5:5 to S Connect signaling
The AG-8/DSP board must drive voice output on DSo4 and accept voice input on DSi4. The following reverse connections are made: MakeConnection( 18:5 to 12:5 ) DSP voice to MVIP bus DSo4:5 MakeConnection( 12:5 to 18:5 ) MVIP bus DSi4:5 to DSP voice MakeConnection( 19:5 to 13:5 ) DSP signaling to MVIP bus DSo5:5 MakeConnection( 13:5 to 19:5 ) MVIP bus DSi5:5 to DSP signaling Figure 46. MVIP-90: Network Interface to DSP Resource (2 Switches)

3.3.4 Connecting Network Interface to Network Interface

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. Stream 4:timeslot 5 of the MVIP bus is used to connect the voice paths.
On the first AG-T1 board, the following forward connections are made: MakeConnection( 16:2 to 4:5 ) T1 voice to MVIP bus DSi4:5 MakeConnection( 4:5 to 16:2 ) MVIP bus DSo4:5 to T1 voice
On the second AG-T1 board the following reverse connections are made: MakeConnection( 16:5 to 12:5 ) T1 voice to MVIP bus DSo4:5 MakeConnection( 12:5 to 16:5 ) MVIP bus DSi4:5 to T1 voice Figure 47. MVIP-90: Network Interface to Network Interface

3.4 MVIP-95 Switch Model

In the MVIP-90 switch model, the 16 MVIP data streams are addressed as streams 0..15, and local resources start at stream 16. Since the H-MVIP bus has 24 data streams and the H.100 bus has 32 data streams, the MVIP-95 switch model was created to accommodate more data streams.
The MVIP-95 switch model is used with the MVIP-90, H-MVIP, and H.100 buses. The MVIP-95 model is based on the premise that a given stream number corresponds to the same physical wire on both sides of the switch block.
The terminus is used in MVIP-95 switching commands to define a specific point on the switch block. The terminus specifies a bus, stream, and timeslot.
As shown in Figure 48, the bus in the terminus structure can be the MVIP bus, the Local bus, or the MC1 bus. The MVIP bus streams and the MC1 bus streams are used to make telephony bus connections. The Local bus streams interface to the board's local resources. The streams on each bus are numbered starting from 0. Figure 48. MVIP-95 Switch Model Busses
In the MVIP-95 switch model, telephony bus streams are addressed as streams 0..31. The following table defines the bus stream mapping for the three bus standards: MVIP-95 Stream H.100 Bus H-MVIP Bus MVIP-90 Bus MVIP bus: Stream 0 CT_D0 HDS0 DSo0 MVIP bus: Stream 1 CT_D1 HDS1 DSi0 MVIP bus: Stream 2 CT_D2 HDS2 DSo1 MVIP bus: Stream 3 CT_D3 HDS3 DSi1 MVIP bus: Stream 4 CT_D4 HDS4 DSo2 MVIP bus: Stream 5 CT_D5 HDS5 DSi2 MVIP bus: Stream 6 CT_D6 HDS6 DSo3 MVIP bus: Stream 7 CT_D7 HDS7 DSi3 MVIP bus: Stream 8 CT_D8 HDS8 DSo4 MVIP bus: Stream 9 CT_D9 HDS9 DSi4 MVIP bus: Stream 10 CT_D10 HDS10 DSo5 MVIP bus: Stream 11 CT_D11 HDS11 DSi5 MVIP bus: Stream 12 CT_D12 HDS12 DSo6 MVIP bus: Stream 13 CT_D13 HDS13 DSi6 MVIP bus: Stream 14 CT_D14 HDS14 DSo7 MVIP bus: Stream 15 CT_D15 HDS15 DSi7 MVIP bus: Stream 16..23 CT_D16..CT_D23 HDS16..HDS23 MVIP bus: Stream 24..31 CT_D24..CT_D31
By convention, streams are usually paired. For example, even stream n is paired with odd stream n+1 (e.g., streams 0 and 1, streams 2 and 3, etc.). If stream 0 is configured as an input stream, stream 1 is typically configured as the corresponding output stream.
In MVIP-90 switch model, the even streams carry voice data and the odd streams carry signaling data. For backward compatibility, the following convention is used in MVIP-95: Voice data is carried on stream pairs 4n and 4n+1. For example: - Streams 0 and 1 - Streams 4 and 5 - Streams 8 and 9, etc. Signaling data is carried on stream pairs 4n+2 and 4n+3. For example: - Streams 2 and 3 - Streams 6 and 7 - Streams 10 and 11, etc. Figure 49. MVIP-90 to MVIP-95 Stream Mappings
By convention, DSP resources send output to even numbered streams and receive input from odd numbered streams.
To make a full-duplex connection between a DSP resource and a network interface, make these two switch commands: Connect the network interface input located on a local stream:timeslot to the MVIP stream:timeslot of the DSP resource output (even numbered stream). Connect the network interface output located on a local stream:timeslot to the MVIP stream:timeslot of the DSP resource input (odd numbered stream). Figure 50. MVIP-95 Switch Commands
For example, DSP resources are nailed up to the bus on streams 4 and 5. Output is sent to stream 4 and input is received on stream 5. To connect a network interface to the DSP resources, the network interface must send output to stream 5 and receive input on stream 4.
The following switch commands are required: MakeConnection( LOCAL:0:5 to MVIP:5:9 )
The first switch command connects the network interface voice output to the MVIP bus. To make a full-duplex connection, the MVIP bus is connected to the voice input: MakeConnection( MVIP:4:9 to LOCAL:1:5 )
The two commands correspond to: Figure 51. Connecting DSP Resources to Network Interface
To connect a network interface to another network interface, one network interface must send output to the even numbered stream and receive input from the odd numbered stream. The other network interface sends output to the odd numbered stream and receives input on the even numbered stream.
On the first board, the network interface output is connected to the bus on stream 9. The network interface input is connected to stream 8. MakeConnection( LOCAL:0:8 to MVIP:9:2 ) MakeConnection( MVIP:8:2 to LOCAL:1:8 )
On the second board, the network interface output is connected to the bus on stream 8. The network interface output is connected to stream 9: MakeConnection( LOCAL:0:3 to MVIP:8:2 ) MakeConnection( MVIP:9:2 to LOCAL:1:3 ) Figure 52. Network Interface to Network Interface
The MVIP-95 switch model for the AG-T1 board is shown in Figure 53. The specific use of each stream is as follows: MVIP-90 Bus Streams MVIP bus: Streams 0..15 Trunk Voice Information Local bus: Streams 0 and 1, timeslots 0..23 Trunk Signaling Information Local bus: Streams 2 and 3, timeslots 0..23 DSP Voice Information Local bus: Streams 4 and 5, timeslots 0..23 DSP Signaling Information Local bus: Streams 6 and 7, timeslots 0..23 HDLC controllers Local bus: Streams 8 and 9 Figure 53. AG-T1 MVIP-95 Switch Model

MVIP-95 Stream	H.100 Bus	H-MVIP Bus	MVIP-90 Bus
MVIP bus: Stream 0	CT_D0	HDS0	DSo0
MVIP bus: Stream 1	CT_D1	HDS1	DSi0
MVIP bus: Stream 2	CT_D2	HDS2	DSo1
MVIP bus: Stream 3	CT_D3	HDS3	DSi1
MVIP bus: Stream 4	CT_D4	HDS4	DSo2
MVIP bus: Stream 5	CT_D5	HDS5	DSi2
MVIP bus: Stream 6	CT_D6	HDS6	DSo3
MVIP bus: Stream 7	CT_D7	HDS7	DSi3
MVIP bus: Stream 8	CT_D8	HDS8	DSo4
MVIP bus: Stream 9	CT_D9	HDS9	DSi4
MVIP bus: Stream 10	CT_D10	HDS10	DSo5
MVIP bus: Stream 11	CT_D11	HDS11	DSi5
MVIP bus: Stream 12	CT_D12	HDS12	DSo6
MVIP bus: Stream 13	CT_D13	HDS13	DSi6
MVIP bus: Stream 14	CT_D14	HDS14	DSo7
MVIP bus: Stream 15	CT_D15	HDS15	DSi7
MVIP bus: Stream 16..23	CT_D16..CT_D23	HDS16..HDS23
MVIP bus: Stream 24..31	CT_D24..CT_D31

MVIP-90 Bus Streams	MVIP bus: Streams 0..15
Trunk Voice Information	Local bus: Streams 0 and 1, timeslots 0..23
Trunk Signaling Information	Local bus: Streams 2 and 3, timeslots 0..23
DSP Voice Information	Local bus: Streams 4 and 5, timeslots 0..23
DSP Signaling Information	Local bus: Streams 6 and 7, timeslots 0..23
HDLC controllers	Local bus: Streams 8 and 9

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

3.5.2 Connecting Network Interface to DSP Resources (1 switch)

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

3.5.3 Connecting Network Interface to DSP Resources (2 switches)

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

3.5.4 Connecting Network Interface to Network Interface

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 1 of 1 in this chapter)

tech_support@nmss.com