(Page 1 of 1 in this chapter)

Chapter 3

Specifying the Switch Configuration

3.1 Introduction
3.2 PPX Configuration File
3.2.1 Switch Fabric
3.3 Defining the Switch Fabric
3.4 Switch Fabric Attributes
3.5 Defining the Telephony Bus
3.5.1 Defining Multiple Independent Buses
3.5.2 Reserving Bus Streams and Timeslots
3.6 Defining a Board
3.6.1 Defining a Board With a Switch
3.6.2 Defining a Board Without a Switch
3.7 Specifying Switch Connections
3.8 Example PPX Configuration File

3.1 Introduction

The Point-to-Point Switching configuration file, ppx.cfg, specifies the switch configuration for the Point-to-Point Switching service. The Point-to-Point Switching configuration file defines:

The Point-to-Point Switching service reads the Point-to-Point Switching configuration file into an internal switch connection database. When switch connections are requested, the Point-to-Point Switching service accesses the connection database to determine how to make the desired connection.

For example, as shown in Figure 13:

  1. An application requests a connection between a DSP resource on an AG-8 board and a line interface on an AG-T1 board.

    

  2. The Point-to-Point Switching service accesses the connection database to determine how a connection can be made (e.g., both boards are connected to the MVIP-90 bus).
    

    

  3. The Point-to-Point Switching service sends the appropriate switch commands to the boards to make the connections.
    

    



    Figure 13.	 Point-to-Point Switching Configuration File
    








3.2	 PPX Configuration File





The active region of the Point-to-Point Switching configuration file begins with the string [PPX] on a line by itself and ends at the end of the file or at another word or phrase in square brackets on a line by itself. Any text outside that region is ignored by the Point-to-Point Switching service.



White space, such as indentation and space around an equals sign, is ignored, but is useful for clarity. Case is ignored. The pound sign (#) and semicolon (;) are both comment delimiters. The Point-to-Point Switching service ignores any text that follows a comment delimiter character on the same line.






3.2.1	 Switch Fabric





In the Point-to-Point Switching configuration file, the switch fabric defines the topology of boards which are connected by telephony buses. Each computer chassis contains one switch fabric. 



In the switch fabric definition, multiple telephony buses may be defined. Typically there is one telephony bus in the switch fabric.





Figure 14.	 Switch Fabric With One Telephony Bus




In systems containing an MVIP-90 bus and an H.100 bus connected with the MVIP Bus Adapter, the MVIP-90 bus and H.100 bus operate as one telephony bus in the chassis. MVIP-90 boards have access to only the first 16 streams on the H.100 bus.





Figure 15.	 MVIP-90 and H.100 Buses in the Same PC Chassis




For systems with multiple, independent MVIP buses in a single PC chassis, the Point-to-Point Switching configuration file specifies two telephony bus definitions in the switch fabric, one for each MVIP bus (shown in Figure 16). Connections cannot be made between boards on separate MVIP buses.





Figure 16.	 Separate MVIP Buses in One PC Chassis




In multi-chassis systems, each PC chassis operates independently. There is a separate Point-to-Point Switching configuration file for each chassis (as shown in Figure 17). MC1 boards located in each chassis are connected using the MC1 bus. In this configuration, the switch fabric in each Point-to-Point Switching configuration file specifies the input and output MC1 bus streams for each MC1 board.


 


Figure 17.	 Multi-Chassis System






3.3	 Defining the Switch Fabric





A switch fabric definition begins with a Fabric statement and ends with an End Fabric statement. All statements appearing between these two keywords define the switch fabric for the system. 



A switch fabric definition has four basic components:




The format of the Point-to-Point Switching configuration file is:


  [PPX]
  Fabric
   # fabric attribute(s)
   # bus definition(s)
   # switch definitions
   # switch connections
  End Fabric




All configuration information for the system must exist inside the Fabric statement.



Figure 18 is an overview of the Point-to-Point Switching configuration file and its structure. The example system contains three boards. The Point-to-Point Switching configuration file has a bus definition section describing the bus connecting the boards. Also, each board has a switch configuration section.





Figure 18.	 Point-to-Point Switching Configuration File






3.4	 Switch Fabric Attributes





The default silence pattern used by the PPX server may be specified by the switch fabric attribute:


   IdleCode = [MU_LAW | A_LAW]




This attribute must appear immediately following the configuration file keyword Fabric, but before any of the other configuration data, as the following example shows:


        [PPX]
        Fabric
                 IdleCode = MU_LAW
                 # bus definition(s)
                 # switch definitions
                 # switch connections
        End Fabric




If this attribute is not present within the file, the default value used is MU_LAW (0x7F).



The value of the IdleCode attribute is used as the default idle pattern for connections created with a NULL passed as the parameter pointer.






3.5	 Defining the Telephony Bus





In the Point-to-Point Switching configuration file, each telephony bus (H.100 or MVIP-90) in the switch fabric must be defined and assigned a name. A bus is defined with either a bus specification or a bus declaration statement:


  Bus name
   bus_specification | bus_declaration
  End Bus




A bus_specification has the following syntax:


bus:streams[(increment)]:timeslots[(increment)]




Each element is used as follows: 





 Element



 Description




 bus



 CTBUS, for MVIP-90 bus or H.100 bus




 streams



 Stream assignment, which can be one stream (e.g., CTBUS:0:0), multiple streams (e.g., CTBUS:0,2,4:0), or a range of streams (e.g., CTBUS:0..7:0)




 timeslots



 Timeslot assignment, which can be one timeslot (e.g., CTBUS:0:0), multiple timeslots (e.g., CTBUS:0:0,2,4), or a range of timeslots (e.g., CTBUS:0:0..7)




 increment



 Specifies a value to increment, (e.g., CTBUS:0..4(2):0 specifies streams 0, 2, 4)
















For example, a bus specification statement for the H.100 bus (32 streams; 128 timeslots) is:


   Bus my_H100_bus
    CTBUS:0..31:0..127
   End Bus




A bus_declaration defines a bus as it relates to a previously defined bus, and has the following syntax:


   Bus new_bus_name
    existing_bus_name ([bus_specification])
   End Bus




The brackets following the bus name can include a range of timeslots, which indicate that the bus is a subset of another bus. For example:


   Bus my_MVIP_90_bus
    Bus my_H100_bus (CTBUS:0..15:0..31)
   End Bus




For each telephony bus (MC1 or H.100) in the system, there can only be one top-level bus definition. A top-level bus is specified with the following syntax:


  CTBUS:streams:timeslots




Each top-level bus definition defines a separate telephony bus.



A bus can be defined as a sub-bus of the top-level bus to indicate how buses connect. In the following example, the MVIP-90 bus is defined as a subset of the H.100 bus:


  [PPX]
  Fabric
   Bus my_H100_bus       # H.100 bus definition
    CTBUS:0..15:0..31      # streams clocked at 2 MHz, 32 timeslots 
    CTBUS:16..23:0..63      # streams clocked at 4 MHz, 64 timeslots
    CTBUS:24..31:0..127      # streams clocked at 8 MHz, 128 timeslots
   End Bus
   Bus my_MVIP_90_bus       # MVIP-90 bus definition
    Bus my_H100_bus (CTBUS:0..15:0..31    )
   End Bus
  End Fabric





3.5.1	 Defining Multiple Independent Buses





In a system containing multiple independent telephony buses, each bus is represented by a separate top-level bus definition. 



In the following example, the Point-to-Point Switching service would define two separate MVIP buses, my_MVIP_1 and my_MVIP_2:


  Bus my_MVIP_1
   CTBUS:0..15:0..31
  End Bus

  Bus my_MVIP_2
   CTBUS:0..15:0..31
  End Bus




Connections cannot be made between a board located on my_MVIP_1 and a board located on my_MVIP_2.






3.5.2	 Reserving Bus Streams and Timeslots





If there are specific streams and timeslots on the telephony bus which are used by another application, the streams and timeslots can be reserved by specifying a subset of timeslots in the bus definition. The reserved streams and timeslots are not available to the Point-to-Point Switching service.



For example, to reserve the first 4 streams on the MVIP-90 bus, you can define a bus as:


  Bus my_MVIP_90_bus
   CTBUS:0..15:0..31
  End Bus
  Bus MVIP_AVAILABLE
   Bus my_MVIP_90_bus (CTBUS:4..15:0..31)
  EndBus




You reference the bus, MVIP_AVAILABLE, when defining the boards connected to the bus.






3.6	 Defining a Board





Each board in the system which connects to a telephony bus must have a switch definition in the switch fabric. A section defining a particular board starts with a Switch n statement and ends with an End Switch statement.


  Fabric
   # bus definitions for the switch fabric
   Switch 0
    # switch 0 definition
   End Switch
   Switch 1
    # switch 1 definition
   End Switch
   # switch connections
  End Fabric




Statements inside a switch definition apply only to that particular board. Each board in the switch fabric must have a unique switch number assigned in the Point-to-Point Switching configuration file. Boards without actual physical switches must also be assigned a switch number. These switch numbers must all be unique. The numbers are arbitrary identifiers and are unrelated to the physical board configuration.



The switch-specific section for each board includes the following statements:






3.6.1	 Defining a Board With a Switch





The switch-specific region for a board which contains a switch must include the switch attributes, telephony bus connection, and local inputs and outputs.


 Defining Switch Attributes



The switch attributes are:




The switch type is used by the Point-to-Point Switching service to determine the type of switch present on the board and is specified by:


   SwitchType = switch




Valid switch types include:


 





 Switch Type



 Description




 FMIC



 Flexible MVIP Interface Circuit providing a complete    enhanced-compliant interface to the MVIP-90 bus.




 HMIC



   H.100/MVIP Integrated Circuit, providing a complete interface to the   H.100 bus. 


 Note: The HMIC designation is used here in a general sense; it actually represents a set of different chips that implements the HMIC design, e.g., the Lucent T8100 chip being used on the AG4000.




 ATI



 Digital crosspoint switch, used only on ATI/ASI boards.

















The switch driver name is specified by:


  DeviceName = switch_driver




The device number is specified by:


  DeviceNumber = board_number




The device number specified in the Point-to-Point Switching configuration file is the board number assigned to the board. For AG boards, the board number is assigned in the AG configuration file. For QX boards, the board number is assigned in the QX configuration file. All other boards are assigned board numbers during the software installation of the board's driver.



The initial switch state is specified by:


   SwitchState = [disabled | enabled]




The presence of this attribute is optional, and is set to enabled, by default, if not present.  Use of this attribute is relevant to the presence of the Hot Swap service within the system.  This attribute is used to designate switches on boards that are planned to be inserted into currently unpopulated CompactPCI slots.



The switch attributes for an AG Quad T board are shown in the following example Point-to-Point Switching configuration file:


  [PPX]
  Fabric
   Bus my_H100_bus        # bus definition
    CTBUS:0..31:0..127
   End Bus
   Switch 0        # assigned as switch 0
    SwitchType = HMIC       # the switch on the AG Quad is an HMIC
    DeviceName = "agsw"       # AG board device driver - agsw   
    DeviceNumber = 1       # the board number assigned in ag.cfg
    # Bus declaration
    # Board inputs
    # Board outputs
   End Switch
  End Fabric




The valid switch drivers, switch type, and device number for each NMS board are shown in the following table:


 





 NMS Board



 DeviceName



 SwitchType



 Determining DeviceNumber




 AG-8, AG-T1, AG-E1



 agsw



 FMIC



 Assigned by the Board n statement in the AG configuration file (ag.cfg).




 AG Quad, 
AG Dual, 
Quad Connect,
AG 2000,
AG 4000,
CompactPCI AG Quad



 agsw



 HMIC



 Assigned by the Board n statement in the AG configuration file (ag.cfg).




 ATI, ASI, ATS



 atsdrv



 ATI



·	 Windows NT: Assigned when installing the ATS driver and software.


·	 UNIX: Determined by the order the address was selected during software installation.




 QX



 qxsw



 HMIC


 (FMIC for 
QX 2000/80L only)



 Assigned by the Board n statement in the QX configuration file (qx.cfg).




 AG Connect, 
(T Connect, S Connect, 
ST Connect)



 agcxsw



 FMIC



·	 Windows NT: Assigned when installing the AG Connect driver and software.


·	 UNIX: Determined by the order the address was selected during software installation.




 MC1



 mc1sw



 FMIC



·	 Windows NT: Assigned when installing the AG Connect driver and software.


·	 UNIX: Determined by the order the address was selected during software installation.




 AG Conference



 agcfsw



 FMIC



·	 Windows NT: Assigned when installing the AG Connect driver and software.


·	 UNIX: Determined by the order the address was selected during software installation.




 WTI-8



 wti8sw



 FMIC



·	 Windows NT: Assigned when installing the AG Connect driver and software.


·	 UNIX: Determined by the order the address was selected during software installation.














 Specifying the Telephony Bus



The telephony bus (MVIP-90 or H.100) connected to the board is specified by a bus declaration statement:


  Bus name ([bus_specification])




The bus name must have been previously defined in the bus definition section of the switch fabric.



For example, the H.100 bus is defined once and assigned the name my_H100_bus. This identifier, my_H100_bus, is used in the switch definitions for all boards connected to the H.100 bus.


  [PPX]
  Fabric
   Bus my_H100_bus        # H.100 bus definition
    CTBUS:0..31:0..127
   End Bus
   Switch 0        # assigned as switch 0
    DeviceName = "agsw"       # AG board switch driver - agsw   
    DeviceNumber = 1       # the board number assigned in ag.cfg
    SwitchType = HMIC       # the switch on the AG Quad is an HMIC
    Bus my_H100_bus ( )       # AG Quad is connected to H.100 bus
    # Board inputs
    # Board outputs
   End Switch
  End Fabric






The brackets which follow the bus name can include a range of timeslots which indicates the board supports a subset of a defined bus. 



For example, in a mixed H.100 and MVIP-90 system, the bus definition includes all streams on the H.100 bus:


  Bus my_H100_in_MVIP_mode
   CTBUS:0..15:0..31      # streams clocked at 2 MHz, 32 timeslots 
   CTBUS:16..23:0..63      # streams clocked at 4 MHz, 64 timeslots
   CTBUS:24..31:0..127      # streams clocked at 8 MHz, 128 timeslots
  End Bus




An AG Quad board can connect to all streams on the H.100 bus. In the switch definition for the AG Quad T board, the bus declaration is:


  Bus my_H100_bus ()




The AG-T1 is an MVIP-90 board and can only access the first 16 streams. The switch definition for the AG-T1 includes a subset of the H.100 bus:


  Bus my_H100_bus (CTBUS:0..15:0..31)


 Defining Local Resources




Resources (e.g., network interfaces, DSP resources) which are located on the local bus as inputs to the switch (e.g., voice stream coming from the telephone network) are specified by:


  Inputs
   LOCAL:streams[(increment)]:timeslots
  End Inputs




Resources which are located on the local bus as outputs from the switch (e.g., voice stream going out to the telephone network) are specified by:


  Outputs
   LOCAL:streams[(increment)]:timeslots
  End Outputs




Typically, local resources on a board are located on consecutive streams. By convention, inputs use even-numbered streams and outputs use odd-numbered streams. 



For example, for an AG Quad T board using channel associated signaling, the local resources are:


 





 AG Quad T Local Resources




 Trunk Voice Information



 Trunk 1: Streams 0 (input) and 1 (output), timeslots 0..23


 Trunk 2: Streams 4 (input) and 5 (output), timeslots 0..23


 Trunk 3: Streams 8 (input) and 9 (output), timeslots 0..23


 Trunk 4: Streams 12 (input) and 13 (output), timeslots 0..23




 Trunk Signaling Information



 Trunk 1: Streams 2 (input) and 3 (output), timeslots 0..23


 Trunk 2: Streams 6 (input) and 7 (output), timeslots 0..23


 Trunk 3: Streams10 (input) and 11 (output), timeslots 0..23


 Trunk 4: Streams 14 (input) and 15 (output), timeslots 0..23




 DSP Voice Information



 Streams 16 (input) and 17 (output), timeslots 0..127




 DSP Signaling Information



 Streams 18 (input) and 19 (output), timeslots 0..127















In the Point-to-Point Switching configuration file for the AG Quad T board, these local resources are defined as:


  [PPX]
  Fabric
   Bus my_H100_bus        # H.100 bus definition
    CTBUS:0..31:0..127
   End Bus
   Switch 0        # assigned as switch 0
    DeviceName = "agsw"       # AG board device driver - agsw   
    DeviceNumber = 1       # the board number assigned in ag.cfg
    SwitchType = HMIC       # the switch on the AG Quad is an HMIC
    Bus my_H100_bus   ()     # AG Quad is connected to H.100 bus
    Inputs
     LOCAL:0..14(2):0..23      # trunk voice and signaling
     LOCAL:16..18(2):0..127      # DSP voice and signaling
    End Inputs
    Outputs
     LOCAL:1..15(2):0..23      # trunk voice and signaling
     LOCAL:17..19(2):0..127      # DSP voice and signaling
    End Outputs
   End Switch
  End Fabric


 Defining the MC1 Bus




The Point-to-Point Switching service supports multi-chassis switch connections. However, the intervening MC1 timeslots must be specified when making the switch connection.



The MC1 bus has 22 streams. Each stream has 64 timeslots. Each MC1 board can receive input from all streams on the MC1 bus and can send output to up to four MC1 streams. See the MC1 Installation and Developer's Manual for information about configuring the input and output streams on an MC1 board.



In the Point-to-Point Switching configuration file, MC1 streams are configured as inputs and outputs to the MC1 board. For example, the following Point-to-Point Switching configuration file configures an MC1 board which is configured to send output to MC1 streams 1, 3, 5, and 7.


  [PPX]
  Fabric
   Bus MVIP_90        # MVIP-90 bus definition
    CTBUS:0..15:0..31
   End Bus
   Switch 1        # assigned as switch 1
    DeviceName = "mc1sw"       # MC1 board switch driver - mc1sw   
    DeviceNumber = 0       # the number assigned during install.
    SwitchType = FMIC       # the switch on the MC1 is an FMIC
    Bus MVIP_90   ()     # MC1 is connected to the MVIP-90 bus
    Inputs
     MC1:0..42(2):0..63      # 22 input streams
    End Inputs
    Outputs
     MC1:1..7(2):0..63      # 4 output streams
    End Outputs
   End Switch
  End Fabric




When making switch connections using over the MC1 bus using the Point-to-Point Switching service, each chassis must make a switch connection with one of the endpoints specifying the MC1 bus address. 



For example, in a multi-chassis system, the first chassis has an MC1 board and an AG-8 DSP board. The second chassis has an MC1 board and an AG-T1 board. 





Figure 19.	 MC1 Point-to-Point Switching Example




To connect a DSP resource on the AG-8 board to a channel on the AG-T1 board:


    


  1. Determine the MC1 bus stream and timeslot to use for the connection.
    

    

  2. In the first chassis, make a Point-to-Point Switching connection from the AG-8 DSP board to the timeslot on the MC1 bus. 
    

    
This connection requires making a switch connection on the AG-8 DSP board to connect the DSP to the MVIP bus and making another switch connection on the MC1 board to connect the MVIP bus timeslot to the MC1 bus timeslot. The MVIP bus timeslot does not have to be specified in the function call. The Point-to-Point Switching service manages the MVIP bus timeslots.
    

  3. In the second chassis, make a Point-to-Point Switching connection from a channel on the AG-T1 board to the timeslot on the MC1 bus. 
    

    
This connection requires making a switch connection on the AG-T1 board to connect the channel to the MVIP bus and making another switch connection on the MC1 board to connect the MVIP bus timeslot to the MC1 bus timeslot. The MVIP bus timeslot does not have to be specified in the function call. The Point-to-Point Switching service manages the MVIP bus timeslots.






3.6.2	 Defining a Board Without a Switch





Boards without switches are configured with nailed up connections to the telephony bus. The nailed up streams and timeslots are typically defined in a configuration file (e.g., ag.cfg). In the Point-to-Point Switching configuration file, you must specify where the nailed up DSP resources are located.



The Point-to-Point Switching service does not directly communicate to boards without switches; it makes connections between the nailed up DSP resources and another board by using the switch on the other board. Therefore, there is no switch attributes configuration. The only information which needs to be defined in the Point-to-Point Switching configuration file is an input and output definition specifying the location of the DSP resources.



For example, as specified in the AG configuration file, the 24 ports of DSP resources from an AG-24 board are nailed up to the following timeslots:


 





 Stream Description



 MVIP-95 Streams



 AG Configuration File Statement (using the MVIP-90 model)




 Voice input from DSP



 Stream 8: timeslots 0..23



 MVIPslots 4:0..23




 Voice output to DSP



 Stream 9: timeslots 0..23



 MVIPslots 4:0..23




 Signaling input from DSP



 Stream 10: timeslots 0..23



 MVIPslots 5:0..23




 Signaling output to DSP



 Stream 11: timeslots 0..23



 MVIPslots 5:0..23















The inputs and outputs of the AG-24 board are defined in the Point-to-Point Switching configuration file as a subset of the defined MVIP-90 bus:


  [PPX]
  Fabric
   Bus my_MVIP_90            # MVIP-90 bus
    CTBUS:0..15:0..31
   End Bus
   Switch 5            # AG-24
    Inputs
     Bus my_MVIP_90 (CTBUS:9..11(2):0..23)  
    End Inputs           # voice & signaling 
    Outputs
     Bus my_MVIP_90 (CTBUS:8..10(2):0..23      ) 
    End Outputs            # voice & signaling
   End Switch
  End Fabric



Note:  For AG boards, nailed-up connections for DSP resources are specified in the AG configuration file with the MVIPslots keyword. The streams specified with MVIPslots statements are addressed using the MVIP-90 switch model. In the Point-to-Point Switching service, all streams are addressed using the MVIP-95 switch model. See the Getting Started With MVIP Switching manual for details on the MVIP-90 and MVIP-95 switch models.





3.7	 Specifying Switch Connections





Switch connections are specified in the Point-to-Point Switching configuration file beginning with a Connect statement and ending with an End Connect statement. The switch connections are of the form:


 switch_number:bus:stream:timeslot TO switch_number:bus:stream:timeslot [NAILED] mode




The switch_number is the number assigned for the board with the Switch n statement in the Point-to-Point Switching configuration file. The bus may be CTBUS, LOCAL, or MC1. The stream and timeslot specify which stream and timeslot to connect.



NAILED specifies the connections cannot be broken with Point-to-Point switching commands. The mode may be SIMPLEX, DUPLEX, or QUAD.



For example, to connect the AG-T1 channels to the on-board DSP resources:


  [PPX]
  Fabric
   Bus MVIP_90        
    CTBUS:0..15:0..31
   End Bus
   Switch 0        # AG-T1 assigned as switch 0
    DeviceName = "agsw"       # AG board device driver - agsw   
    DeviceNumber = 1       # the board number assigned in ag.cfg
    SwitchType = FMIC       # the switch on the AG-T1 is an FMIC
    Bus MVIP_90   ()     # connected to the MVIP-90 bus
    Inputs
     LOCAL:0..2(2):0..23      # trunk voice and signaling
     LOCAL:4..6(2):0..23      # DSP voice and signaling
    End Inputs
    Outputs
     LOCAL:1..3(2):0..23      # trunk voice and signaling
     LOCAL:5..7(2):0..23      # DSP voice and signaling
    End Outputs
   End Switch
   Connect
    0:LOCAL:0:0..23 TO 0:LOCAL:5:0..23 NAILED QUAD
   End Connect
  End Fabric




Any switch connections must appear as the last statements in the switch fabric definition. Connections are made when the PPX server is started. Nailed up connections can be disconnected by an application using ppxDisconnect unless specified with the NAILED keyword.






3.8	 Example PPX Configuration File





The following PPX configuration file defines a system with two AG-8 boards, an AG Quad T board, and an AG-24 board.


[PPX]
Fabric
  Bus H100                         # H100 bus
   CTBUS:0..15:0..31
   CTBUS:16..23:0..63
   CTBUS:24..31:0..127
  End Bus
  Bus MVIP_90         # MVIP-90 bus
   Bus H100 (CTBUS:0..15:0..31)
  End Bus
  Switch 0         # AG-8  
   SwitchType = FMIC
   DeviceName = "agsw"
   DeviceNumber = 0
   Bus H100 (CTBUS:0..15:0..31)       # on the MVIP-90 bus
   Inputs                  
    LOCAL:0..6(2):0..7         # line interfaces & DSP resources
   End Inputs
   Outputs                     
    LOCAL:1..7(2):0..7         # line interfaces & DSP resources
   End Outputs
  End Switch                           
  Switch 1         # AG-8
   DeviceName = "agsw"
   DeviceNumber = 1
   Bus MVIP_90()       # on the MVIP-90 bus
   Inputs                             
    LOCAL:0..6(2):0..7         # line interfaces & DSP resources
   End Inputs
   Outputs                        
    LOCAL:1..7(2):0..7         # line interfaces & DSP resources
   End Outputs
  End Switch
  Switch 2         # AG Quad T
   SwitchType = HMIC
   DeviceName = "agsw"
   DeviceNumber = 2
   Bus H100 ()
   Inputs                       
    LOCAL:0..14(2):0..23       # Trunk
    LOCAL:16..18(2):0..127        # DSP
   End Inputs
   Outputs                           
    LOCAL:1..15(2):0..23        # Trunk
    LOCAL:17..19(2):0..127        # DSP
   End Outputs
  End Switch
  Switch 3         # AG 24
   Inputs
    Bus MVIP_90 (CTBUS:9..11(2):0..23)        # Connections nailed up
   End Inputs
   Outputs
    Bus MVIP_90 (CTBUS:8..10(2):0..23)
   End Outputs
  End Switch
End Fabric











 
    (Page 1 of 1 in this chapter)




 




tech_support@nmss.com



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