(Page 1 of 1 in this chapter)

Chapter 6

MVIP Connectivity

6.1 Introduction
6.2 Trunk Channels and MVIP Timeslots
6.2.1 T1 Channel Associated Signaling (CAS Mode)
6.2.2 T1 Common Channel Signaling (PRI Mode)
6.2.3 T1 NFAS Configurations (RAW Mode)
6.2.4 E1 Channels and MVIP Timeslots
6.2.5 E1 Channel Associated Signaling (CAS Mode)
6.2.6 E1 Common Channel Signaling (PRI Mode)
6.2.7 E1 Signaling in RAW Mode
6.3 Switch Models
6.3.1 MVIP-95 Switch Model
6.3.2 MVIP-90 Switch Model
6.4 Default MVIP Connections
6.4.1 Default Connections for Standalone Board
6.5 FMIC Switching Limitations
6.5.1 MVIP-90 Example
6.5.2 MVIP-95

6.1 Introduction

This chapter:

6.2 Trunk Channels and MVIP Timeslots

When the trunk transmission reaches the AG-T1 or AG-E1 board, the board places the voice and signaling information directly in timeslots in MVIP streams. The actual streams used depend upon:

6.2.1 T1 Channel Associated Signaling (CAS Mode)

If DigitalMode=CAS (its default setting), information is routed to accommodate a T1 channel-associated signaling configuration, where:

On the MVIP bus, this information is presented as follows (see Figure 24):

6.2.2 T1 Common Channel Signaling (PRI Mode)

If DigitalMode=PRI, signaling information is routed differently to accommodate the T1 ISDN common channel signaling configuration, where:

The AG-T1 routes this information as follows (see Figure 25);

6.2.3 T1 NFAS Configurations (RAW Mode)

If DigitalMode is set to RAW, information is routed to accommodate a Network Facility Associated Signaling (NFAS) configuration, where no D channel is present on the T1 trunk (see section Section 5.3.2):

The AG-T1 routes this information as follows (see Figure 26):

6.2.4 E1 Channels and MVIP Timeslots

With AG-E1s, DigitalMode only affects how signaling information is routed. Regardless of the DigitalMode setting, the AG-E1 routes the voice information as follows:

Figure 27 illustrates how voice channel data is assigned to MVIP timeslots:

Figure 27. Connecting E1 B Channels To MVIP Timeslots (All Modes)

6.2.5 E1 Channel Associated Signaling (CAS Mode)

If DigitalMode=CAS (its default setting), signaling information is routed to accommodate an E1 channel-associated signaling configuration, where E1 channel 16 carries signaling information for all other channels. The signaling information in E1 timeslot 16 for each channel is broken out and placed in a corresponding timeslot on MVIP-95 Local,2 and Local,3 (MVIP-90 stream 17). For example, the voice information for E1 timeslot 7 appears in MVIP-95 Local,0,6 and Local,1,6 (MVIP-90 stream:timeslot 16:6). The signaling information for E1 timeslot 7 appears in MVIP-95 Local,2,6 and Local,3,6 (MVIP-90 stream:timeslot 17:6).

Figure 28 illustrates how signaling data is distributed:

Figure 28. Breaking Out Signaling Information From E1 Stream 16 (CAS Mode)



Thus, to CT Access, there is a single set of streams carrying voice and signaling information to and from the E1 trunk, where each timeslot contains the voice or signaling information for one E1 channel.


 






6.2.6	 E1 Common Channel Signaling (PRI Mode)





If DigitalMode=PRI, signaling information is routed differently to accommodate an ISDN common channel signaling configuration, where CCS signaling packets are transmitted in channel 16 instead of CAS bits. All signaling information from channel 16 is routed to MVIP-95 Local,8,0 and Local,9,0 (MVIP-90 stream:timeslot 20:0) (See Figure 29.) This stream connects to the board's HDLC controller, which processes the D channel information from each frame.


 



Figure 29.	 Routing E1 Channel 16 Data To HDLC Controller (PRI Mode)



 






6.2.7	 E1 Signaling in RAW Mode





If DigitalMode is set to RAW:




The AG E1 routes this information as follows (see Figure 30):






6.3	 Switch Models





This section describes how the T1 or E1 trunk and processing resource streams fit in the context of the AG-T1 and AG-E1's MVIP switch model. For more information about MVIP switch models, see Getting Started With MVIP Switching.






6.3.1	 MVIP-95 Switch Model





Figure 31 shows the AG-T1 and AG-E1 switch model in MVIP-95 terms. The specific use of each MVIP stream is as follows:






6.3.2	 MVIP-90 Switch Model 





Figure 32 shows the AG-T1 and AG-E1 switch model in MVIP-90 terms. The specific use of each MVIP stream is as follows:






6.4	 Default MVIP Connections 





If MVIP switching is disabled in your AG configuration file (EnableMvip=NO), certain default MVIP connections are made on AG-T1 and AG-E1 boards. The exact settings depend upon the setting of DigitalMode, as shown in the following table:


  





 DigitalMode



 Default Connection




 CAS



 MVIP-95 streams Local 0:0... max and Local 1:0...max (MVIP-90 stream 16:0...max) carrying voice information to and from the trunk are connected to Local 4:0...max and Local 5:0...max (MVIP-90 stream 18:0...max) for carrying voice information to and from the DSP resources. The connection is full duplex. With AG-T1s, timeslots 0...23 are connected. With AG-E1s, timeslots 0...29 are connected.


 MVIP-95 streams Local 2:0...max and Local 3:0...max (MVIP-90 stream 17:0...max) carrying signaling information to and from the trunk are connected to streams Local 6:0...max and Local 7:0...max (MVIP-90 stream 19:0...max) for carrying signaling information to and from the DSP resources. The connection is full duplex. With AG-T1s, timeslots 0...23 are connected. With AG-E1s, timeslots 0...29 are connected.


 These settings channel all information from the network voice and signaling streams to DSP processing resources. This allows the board to process the information, send or receive faxes, etc.




 PRI or RAW



 MVIP-95 streams Local 0:0...max and Local 1:0...max (MVIP-90 stream 16:0...max) carrying voice information to and from the trunk are connected to streams Local 4:0...max and Local 5:0...max (MVIP-90 stream 18:0...max) for carrying voice information to and from the DSP resources. The connection is full duplex. With AG-T1s, timeslots 0...23 are connected. With AG-E1s, timeslots 0...29 are connected.


 MVIP-95 streams Local 8:0...max and Local 9:0...max (MVIP-90 stream 20:0...max) carrying information to and from the HDLC controller is connected to Local 2:0...max and Local 3:0...max (MVIP-90 stream 17:0...max). This is done because the runfile can only access information on this stream.
















You may wish to change this default routing, so the board can interoperate with other boards connected to it via the MVIP bus. To do so, enable MVIP switching.



With MVIP switching enabled, there is no default routing. You can control the routing using any of the software tools described in Section 1.3.3.






6.4.1	 Default Connections for Standalone Board





Default connections are made on AG T1 and AG E1 boards to connect the voice and signaling information to DSP resources. The exact settings depend upon the setting of DigitalMode, as shown below:


  





 DigitalMode



 Default Routing for AG-T1




 CAS



 Full duplex connection between trunk voice information and DSP resources:


 0:0...23 => 5:0...23, 4:0...23 => 1:0...23


 Full duplex connection between trunk signaling information and DSP resources:


 2:0...23 => 7:0...23, 6:0...23 => 3:0...23




 PRI



 Full duplex connection between trunk voice information and DSP resources: 


 0:0...22 => 5:0...22, 4:0...22 => 1:0...22


 Full duplex connection between HDLC controller and the signaling streams. This is done because the runfile can only access information on these streams:


  2:0 => 9:0, 8:0 => 3:0




 RAW



 Full duplex connection between trunk voice information and DSP resources:


  0:0...23 => 5:0...23, 4:0...23 => 1:0...23















  





 DigitalMode



 Default Routing for AG-E1




 CAS



 Full duplex connection between trunk voice information and DSP resources:


 0:0...29 => 5:0...29, 4:0...29 => 1:0...29


 Full duplex connection between trunk signaling information and DSP resources:


 2:0...29 => 7:0...29, 6:0...29 => 3:0...29




 PRI



 Full duplex connection between trunk voice information and DSP resources: 


 0:0...29 => 5:0...29, 4:0...29=> 1:0...29


 Full duplex connection between HDLC controller and the signaling streams. This is done because the runfile can only access information on these streams:


  2:0 => 9:0, 8:0 => 3:0




 RAW



 Full duplex connection between trunk voice information and DSP resources:


  0:0...30 => 5:0...30, 4:0...30 => 1:0...30















 






6.5	 FMIC Switching Limitations 





The MVIP-90 Switching Standard is designed to use full duplex streams. When making a full duplex connection using stream 0, the timeslot on DSo0 is used to receive input, and output is driven onto the same timeslot on DSi0. For example:



MakeConnection ( 0:3 to 2:6 )    /* Connects DSo0:3 to DSi2:6 */



MakeConnection ( 2:6 to 0:3 )    /* Connects DSo2:6 to DSi0:3 */



The FMIC chip was built for implementing MVIP-90 switching. It has a direction bit in its connection memory for each timeslot, that selects either of the following modes:




The FMIC cannot simultaneously send output to both DSi and DSo on the same timeslot on the same-numbered stream, and also cannot simultaneously receive input from both DSi and DSo on the same timeslot.






6.5.1	 MVIP-90 Example





Assume a simplex connection from 8:0 to 16:0 has been established. This is considered a reverse connection.Data is read from DSi0 and copied to 16:0.The switch block output 8:0 is tri-stated. Given the connection  8:0  -> 16:0:




Once all connections to timeslot 0 on stream 8 on both sides have been broken (in this case by disabling output on 16:0), you can change direction by making connections that involve 0:0 either as an input or as an output.



For another example, assume that switch block input 8:0 is simplex connected to network stream 16:0, as in the preceding example. Assume further that switch block output 8:0 is in pattern mode, writing pattern 0x0F to DSo0 during timeslot 0. Given the connection:



8:0  -> 16:0



8:0  P  0x0F






6.5.2	 MVIP-95





When using the MVIP-95 switch model, a full duplex connection is:



MakeConnection ( mvip:0:3 to mvip:5:6 )    /* Connects DSo0:3 to DSi2:6 */



MakeConnection ( mvip:4:6 to mvip:1:3 )    /* Connects DSo2:6 to DSi0:3 */






When a connection is made using stream 0 timeslot 3, the direction is set for timeslot 3 on stream 1. Stream 0 corresponds to DSo0, and stream 1 corresponds to DSi0 (see Figure 33).



In most applications, this switching restriction is completely invisible. However, for any board with an FMIC switch, you cannot connect the local DSP resources to the local network interfaces over the MVIP bus. Those connections must be made using the local streams. Likewise, you cannot connect two trunk channels on the same board over the MVIP bus.



Making a connection of any type involving a timeslot on an MVIP stream establishes the direction for that timeslot pair. The direction may not be changed until all connections involving the timeslot have been broken.



If you make arbitrary simplex connections, you may encounter blocking from an unavailable connection, where the direction bit on the connection has already been set in the opposite direction. 


Note:  There is no direction associated with local streams.

 



Figure 33.	 FMIC Connection Limitations












 
    (Page 1 of 1 in this chapter)




 




tech_support@nmss.com



Copyright © 1999, Natural MicroSystems, Inc.   All rights
reserved.