|
|
This chapter describes the process of configuring a Cisco Software Release 4 telephony controller system.
The telephony controller works in conjunction with a call unit (CU) to provide a campuswide voice over asynchronous transfer mode (VOATM) solution. In this application, the CU is an LS1010.
Each CU is connected to a PBX (private branch exchange).
Simple Gateway Control Protocol (SGCP) was designed for controlling Voice over IP gateways by an external call control element (called a call-agent in SGCP). Cisco has adapted SGCP to control ATM Circuit Emulation Services (CES) circuits (called endpoints in SGCP).
The resulting system allows the call-agent, in this case the VSC2700, to engage in CCS over a 64kbps CES circuit. This CCS engagement governs the interconnection of bearer channels on the CES interface, in this case, the LS1010.
The following SGCP messages are exchanged between the VSC and the LS1010.
| Message | Usage |
|---|---|
CreateConnection | Used by VSC to set up a reserve Soft-PVC ATM CES connection on LS1010. |
ModifyConnection | Used by the VSC to nail down the Soft-PVC ATM CES connection on the LS1010. |
DeleteConnection | Used by the VSC to tear down Soft-PVC at call completion. |
The LS1010 sets up point-to-point bidirectional connections. All communication between the VSC2700 and the LS1010 uses SGCP over ATM.
Multiple telephony controllers communicate via a proprietary Cisco protocol based on ISUP known as C-ISUP. C-ISUP uses a sub-set of ISUP messages.
The C-ISUP message formatting contains many of the same characteristics of the existing ISUP message format. The primary difference between existing ISUP messages and C-ISUP is in the area of the routing label and a new information element (IE) to carry CU-related data between telephony controllers.
The following ISUP messages are supported in C-ISUP.
| Message | Usage |
|---|---|
Initial Address Message (IAM) | Similar to the ISUP IAM. In addition to ISUP IEs for A-number, B-number, bearer capabilities, etc., the IAM carries a Connection Descriptor end-to-end. This field is necessary for telephony controllers to communicate connection information to CUs. An ISUP Generic Digits IE is used to deliver this information. |
Address Complete Message (ACM) | Similar to the ISUP ACM. In addition to ISUP IEs the ACM carries a Connection Descriptor end-to-end. This field is necessary for telephony controllers to communicate connection information to CUs. C-ISUP supports the ISUP Generic Digits IE as an extension to the standard IEs defined in ISUP. |
Subsequent Address Message (SAM) | Used Similar to the ISUP ANM. |
Answer Message (ANM) | Similar to the ISUP ANM. In addition to ISUP IEs, the ANM carries a Connection Descriptor end-to-end. This field is necessary for telephony controllers to communicate connection information to CUs. C-ISUP supports the ISUP Generic Digits IE as an extension to the standard IEs defined in ISUP. |
Release Message (REL) | Similar to the ISUP REL. In addition to ISUP IEs the REL message will carry a Connection Descriptor end-to-end. This field is necessary for telephony controllers to communicate connection information to CUs. An ISUP Generic Digits IE is used to deliver this information. |
Release Complete Message (RLC) | Similar to the ISUP RLC. Presently no additional IEs are required for C-ISUP. |
C-ISUP uses a reliable IP as its transport layer.
A VSC2700 configuration consists of at least one site and the site contains at least one TransPath and one LS1010.
Each site in the NEMS for the VSC2700 configuration is essential for the network.
Because all sites must be aware of each other (for routing purposes), every site in the NEMS must be built and deployed with each new site added to your network.
The site is a control domain consisting of, at minimum, one TransPath and one CU. Each CU receives PRIs from the PBX.
Step 1 Right-click on Net and select Add Site.
The Add Site window displays.
Step 2 Type XX-VSC in the Name field, where XX is your initials.
Step 3 Complete the remaining fields and click OK.
For more information about the Sites tab and creating sites, see "Sites."
The VSC2700 uses the following types of lines:
Channel 24 on T1s and channel 16 on E1s need to be set for signaling.
The procedure to add lines is as follows:
Step 1 Select your VSC2700 and click on the Lines tab.
Step 2 Add the Access and Access Server lines. For example:
| Type | Name | Description |
|---|---|---|
Access | CU1-1 | CU1-line-1 |
CU2-1 | CU2-line-1 | |
Access Server | VSC1-1 | VSC1-to-CU1 |
VSC1-2 | VSC1-to-CU2 |
Step 3 Expand line CU1-1.
Displays all 24 bearer channels in the T1.
Step 4 Select Channel 24, right-click, select Set Channel Function, and select D (Data).
Sets channel 24 for signaling.
Step 5 Set channel 24 on line CU2-1 for signaling.
Step 6 Save your work. (Click on the Save button.)
For more information about the Lines tab and adding lines, see "Lines."
Add your access device from the Sites tab. A site can have multiple access devices, which are the CU type for a VSC2700. Three subtasks are associated with adding an access device:
The procedure to add an access device is as follows:
Step 1 Click on the Site tab.
The site window displays.
Step 2 Select your site.
Step 3 Right-click on the site and select Add Access Device.
The Add Access Device dialog box displays.
Step 4 Provide an alphanumeric identifier (up to 4 characters) for your access device; this identifies the access server in the list of elements for your sites. For example:
Enter CU1 in the ID field and press Tab.
Step 5 Describe your access device. For example:
Enter XX-Training-CU1 in the Description field.
Step 6 Click on the Access Type down arrow and select CU.
The access type defines the function of your access device in your system.
Step 7 Click on OK.
Your access device is added to the site.
Step 8 Save your work.
Step 9 Add any other access devices (for example, CU2) to your site. (Repeat steps 3 through 8).
Next, you must identify the IP interface and service on the CU. The IP Interface tab has two sub-tabs:
The CU uses the SGCP service on port 2427.
The procedure to add an IP interface is as follows:
Step 1 Click on the IP Interface tab
The IP Interface tab displays with its subtabs, General and IP Service.
Step 2 Click on the IP Interfaces down arrow and select Add IP Interface.
Step 3 Enter CU1 in the IP Interface Logical Name field.
Step 4 Enter the IP address of the CU in the IP Address field. For our example:
175.200.15.05
Step 5 Select A for IP Network and click on OK.
The configuration tool creates the IP interface and clears the screen.
Step 6 Click on the IP Interfaces down arrow and select CU1.
The IP interface information displays.
Step 7 Click on the IP Service subtab.
Step 8 Right-click in the gray area (not in the box) and select Add IP Service.
The IP Services Parameters window displays at the bottom of the subtab.
Step 9 Click inside the Service Name field and enter SGCP-CU-1.
Step 10 Click inside the Port field and enter 2427.
The LS1010 listens for SGCP messages on port 2427.
Step 11 Click on the down arrow of the Service Families field and select SGCP_IP.
Step 12 Click on OK.
Step 13 Save your work.
Step 14 Add and configure another IP interface for SGCP on CU2 with an IP address of 175.200.176.01.
Use the Connect Access Lines tab to connect the access lines to the CU. When you connect an access line to the CU, you provide a span ID for each line. For the CU, Span IDs identify the T1/E1 connection from the PBX to the ATM switch.
The procedure to connect access lines is as follows:
Step 1 Select the Connect Access Lines tab.
Step 2 Select CU1-1 in the Access Lines box, right-click, and select Connect.
The Span ID window displays.
Step 3 Enter CBR0.0.0 for a Span ID.
Step 4 Click on OK.
Step 5 Select VSC1-1, right click, and select Connect.
This connects line VSC1-1 to CU1.
Step 6 Connect lines CU2-1 and VSC1-2 to the appropriate CU.
Step 7 Save your work.
Add a TransPath component from the Sites tab. Adding a TransPath component requires an ID, name, description, and IP address. You must also select the access types based on the product implementation; in this case it is CU because LS1010s are connected to a PBX and a TransPath. The Signal channels are groomed off the PRI and sent to the TransPath for routing.
Complete the following tasks to configure your TransPath:
The Network field defaults to A and the configuration tool assumes a single TransPath (non-failover) configuration.
Select Failover to configure a failover TransPath configuration. This option requires an IP address for the standby unit.
Auxiliary Signaling Network (ASN) will be used to configure the system for feature transparency, which is not supported in this release of the VSC.
An ASN port (the port that carries ASN messaging) and IP address are required fields for this option
The procedure to add a TransPath component is as follows:
Step 1 Click on the Sites tab.
The site window displays.
Step 2 Select your site.
Step 3 Right-click on the site and select Add TransPath.
The Add TransPath dialog box displays.
Step 4 Enter xxx in the ID field, where xxx is a unique 3-digit, hex identifier for your TransPath, and press Tab.
Step 5 Enter VSC1 in the Name field and press Tab.
This is a 4-digit, alphanumeric name.
Step 6 Enter xx-Training-VSC1 in the Description field.
Step 7 Click on the Access Type down arrow and select CU.
Step 8 Enter 173.172.255.16 in the IP Address field.
This is the IP address of the TransPath.
Step 9 Click on OK.
Your TransPath is added to the site.
Step 10 Save your work.
The SNMP Manager runs on the NT server (or any platform that understands SNMP) and listens for alarms forwarded from the SNMP Agent by the SNMP daemon on the TransPath. The SNMP Manager requires the IP address of the NT server (or other platform) the SNMP resides on. The SNMP Manager runs on any SNMP Manager software (for example, the HP OpenView software).
The procedure to add an SNMP Manager is as follows:
Step 1 Click on the SNMP tab.
The SNMP window displays.
Step 2 Select Add SNMP Manager from the Choose an SNMP Manager drop down menu.
The dialog box displays with a blank field for the IP address.
Step 3 Enter 172.255.12.01 in the IP Address field.
This is the IP address of the NT server where the HP OpenView software resides.
Step 4 Click on OK and then click on Save.
SNMP Manager 001 is created.
Use the Cards tab to add and connect TransPath cards to access server lines. The TransPath "box" is referred to as a cage. Each cage contains slots for the signaling interface cards (ITK). Depending on the type of cage selected (Netra/E450/Ultra 5), the appropriate number of empty slots display.
Use the pop-up menu to populate the slots with the correct type of interface card (E1/T1). To set up an E1/T1 card, specify a name, description, and card type. The slot IDs on the TCT do not match the physical slot IDs on the Netra or 450E.
This table matches the TCT slots to the physical slots:
TransPath | Physical Slot Number | TCT Slot Number |
|---|---|---|
Sun Netra | 0 | Not available |
1 | 0 | |
2 | 1 | |
3 | 2 | |
Sun 450E | 1 | 0 |
| 2 | 1 |
| 3 | 2 |
| 4 | Not used |
| 5 | Not used |
| 6 | Not used |
| 7 | 3 |
| 8 | 4 |
| 9 | 5 |
| 10 | 6 |
After adding the cage and cards, expand the card and right click to select connection options to the line interface (LIF).
The following options are available from the pop-up menu:
The procedure to add Cages and Cards is as follows:
Step 1 Click on the Cards tab.
The blank Cards window displays with a TransPath at the top of the tree.
Step 2 Select the TransPath and right-click the mouse.
A pop up window displays.
Step 3 Select Add Cage.
The Add Cage dialog box displays.
Step 4 Type XXCage in the Name field and VSC Cage in the Description field.
Step 5 Select the Netra Cage Type from the list box.
Step 6 Click on OK.
The Netra cage is added to the TransPath in the tree window.
Step 7 Double-click on the Cage.
A list of empty slots display.
Step 8 Right-click on the Slot_0 and select Add Card.
The Add Card dialog box displays.
Step 9 Enter PRI In in the Card Name field and PRI-LIF in the Description field.
Step 10 Select the T1 Card Type from the pull-down menu.
The card type corresponds with line type.
Step 11 Click on OK.
This indicates the type of line going into the card.
Step 12 Click on plus sign to the left of the card.
The LIF displays in blue.
Step 13 Right-click in the Cards tab and select Show Access Signal Lines.
The TransPath line(s) display.
Step 14 Click on the LIF for Card Slot_0/PRI and the VSC1-1, right-click and select Connect.
The LIF and Line turn green.
Step 15 Save your work.
Step 16 Connect VSC1-2 to the TransPath.
Use the IP Interface tab to identify an IP service on the TransPath. Create an IP service for each IP port used on your TransPath. The TCT creates an IP interface automatically---IP_Addr1. The interface creates both SGCP and C-ISUP (LISUP) services.
The procedure to add a TransPath IP interface is as follows:
Step 1 Click on the IP Interface tab.
The IP Interface tab displays with 2 sub tabs --- General and IP Service.
Step 2 Click on the down arrow and select Add IP Interface.
The TCT creates IP_Addr1 automatically.
Step 3 Click on the IP Service sub tab.
Step 4 Right-click and select Add IP Service.
The IP Services Parameters window displays at the bottom of the sub tab.
Step 5 Click inside the Service Name field and enter VSC1-SGCP-1.
Step 6 Enter 2427 in the Port field.
Step 7 Click on the down arrow of the Service Families field and select SGCP.
If you have multiple telephony controllers in your network, configure a second IP Service for C-ISUP (LISUP) on port 3000.
Step 8 Click on OK.
Step 9 Save your work.
Two separate elements carry the signaling and the bearer traffic. The signaling traffic controls the bearer traffic. To facilitate that control, the signaling traffic needs to be aware of where the bearer traffic is coming from and going to.
Therefore, when you set up a traffic path, you are informing the control network where the traffic is originating. Signal paths establish the environment to control the bearers.
You create a traffic path for each access device connected to your TransPath. A single traffic path supports multiple access lines. Create a traffic path for each ATM switch connecting to the telephony controller. There are four sub tabs under the Traffic Path tab:
The ASP_part string property defaults to Y; set it to N.
The procedure to add a Traffic Path is as follows:
Step 1 Click on the Traffic Path tab.
A blank Traffic Path window displays.
Step 2 Click on the down arrow to the right of the Traffic Path field and select Add Traffic Path.
The General tab displays.
Step 3 Click on the down arrow in the Protocol Family field and select the ISDN-PRI.
Step 4 Click on the down arrow in the Variant field and select the ANSI-ATT.
You have just selected the protocol family and variant for this particular line.
Step 5 Click on the Access radio button.
Step 6 Select your CU1 and click on Select Access Device button.
Step 7 Select CU1-SGCP Access Device IP Services.
Step 8 Enter CU1 in the Path Name field.
Step 9 Enter PBX1 to CU1 in the Description field.
Step 10 Enter 1 in the Traffic Path Tag field.
Step 11 Click On OK.
Step 12 Click on the Channels tab.
Step 13 Click on CU1-1, right-click, and select Add Bearer Channels.
Step 14 Click on the Properties tab.
Step 15 Select the ASP_part string property and click on Override.
Turns off ASN. Valid values are Y and N.
Step 16 Enter N in the Override Value field and click on OK.
Step 17 Save your work.
Create a signal path for each ATM switch connected to you TransPath. The Signal Paths window contains three sub tabs---General, Channels, and Properties.
The procedure to add a Signal Path is as follows:
Step 1 Click on the Signal Paths tab.
The blank Signal Paths window displays with three tabs; General, Channels, Properties.
Step 2 Click on the down arrow of the Signal Path field and select Add Signal Path.
The General sub tab displays with blank fields.
Step 3 Select the ISDNPRI from the Protocol Family list box.
Step 4 Select the ANSI-ATT variant from the Variant list box.
Step 5 Click on the Access radio button.
This line is coming from the network into the TransPath.
Step 6 Enter PBX1 in the Description field.
Step 7 Enter 1 in the SigPath tag number field.
Step 8 Click on the CU1 in the Traffic Path box and click on the Add Dest. button.
Adds the traffic path to this signal path.
Step 9 Click on OK.
Step 10 Click on the Channels tab.
Step 11 Select CU1-1 and navigate to the D channel.
Step 12 Right-click on channel D1 and select Add to Signal Channel.
Step 13 Click on Save.
After you've finished configuring your system, you must perform the Build and Deploy functions. The Build function writes the configuration to a set of flat files. The Deploy function copies the flat files to a directory on the NT server.
The configuration tool stores built and deployed files in the c:/lightspeed/TransPathCM/Install directory. The files are stored by TransPath ID number.
You will use a UNIX command on the TransPath to retrieve the files. You can only build and deploy a single site at a time. A confirmation message displays at the bottom of the window when the Build or the Deploy runs successfully.
When the Build or Deploy is not successful, the configuration tool displays an error message providing a brief description of possible error(s).
Incomplete or missing information is the likely cause of a Build or Deploy failure.
The procedure to Build and Deploy is as follows:
Step 1 Right-click on XX-VSC and select Build.
The System Message box displays progress messages for the build.
Step 2 Right-click on XX-VSC and select Deploy.
Posted: Fri Nov 12 16:22:39 PST 1999
Copyright 1989-1999©Cisco Systems Inc.