|
|
Use the BCGEN tool as a complement to the configuration tool (CT) to provision configurations with large numbers of bearer channels. The BGCEN tool allows you to omit the creation of traffic channels in the CT. Traffic channels are instead allocated based upon simple script files you create that are read by the BGCEN tool. The BCGEN tool is useful when provisioning large configurations with many bearer channels.
The BCGEN tool is automatically installed at the time of software installation if you use the automated install script. The present release is for configurations that map SS7 traffic to ISDN PRI over IP, such as the Cisco Dial Access Solution, and for Classic TransPath configurations that perform protocol conversion.
Step 1 Use the CT to configure a Classic TransPath setup. Perform the following tasks:
(a) Create one or more multiplexers (muxes).
(b) Create network, subscriber, and TransPath lines to carry the signaling. You still need to map lines carrying signaling channels together. Do not create lines that carry only bearer traffic. The BCGEN tool creates these bearer lines when it reads your scripts.
(c) Create traffic paths; however, do not assign circuit identification codes (CICs) or assign time slots.
(d) Create signal paths and assign signal channels.
Step 2 Build, deploy and transfer the data (.dat) files (using FTP) to your UNIX host server for the Cisco SC2200.
Step 1 Make sure that the software is not running by entering the following command:
ps -ef | grep tran
Step 2 If the system returns no response, the software is not running. If the response indicates that the software is running, make sure that you are logged in to the system as the root user and enter the following command:
/etc/init.d/transpath stop
Repeat Step 1 until the system returns no response, showing that the software is not running.
Step 1 Change to the TransPath directory and make a new directory called BCGen:
cd /opt/TransPath/etc
mkdir BCGen
The BCGen directory is used to store your scripts.
Step 2 Change to the BCGen directory by entering:
cd /opt/TransPath/etc/BCGen
Use a text editor to create your script files in the BCGen directory. Name the files with the extension .bcg; for example, rack1.bcg.
The first required field in the script is MAPTYPE. The arguments describe the two sides of a nailed bearer configuration. You can use the following maptypes:
Examples of each of these follow, with explanations of the script.
# Rack 1 bearer channels MAPTYPE:FAS:PC # FAS to SS7 #MMLName, TSStart, TSRange, TSSkip, DPC, Net_Ind., CICstart, CICRange, CICSkip SC-1, 1, 1F, 10, 2.2.1, 2, 1, 1F, 10
| FAS Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
TSStart | 1 | 1 |
TSRange | 1F | 31 |
TSSkip | 10 | 16 |
Notes:
| PC Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 1 | 1 |
CICRange | 1F | 31 |
CICSkip | 10 | 16 |
Notes:
# Rack 1 bearer channels MAPTYPE:PC:PC # SS7 to SS7 #DPC, Net_Ind., CICstart, CICRange, CICSkip, DPC, Net_Ind., CICstart, CICRange, CICSkip 3.21.2, 2, 1, 78, 18, 2.2.1, 2, 1, 78, 18 3.21.3, 2, 1, 78, 18, 2.2.1, 2, 101, 178, 178
| PC Side 1 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 1 | 1 |
CICRange | 78 | 120 |
CICSkip | 18 | 24 |
Notes:
| PC Side 2 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 1 | 1 |
CICRange | 78 | 120 |
CICSkip | 18 | 24 |
Notes:
| PC Side 1 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 1 | 1 |
CICRange | 78 | 120 |
CICSkip | 18 | 24 |
Notes:
| PC Side 2 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 101 | 257 |
CICRange | 178 | 376 |
CICSkip | 178 | 376 |
Notes:
# Rack 1 bearer channels MAPTYPE:FAS:FAS # FAS to FAS #MMLName, TSStart, TSRange, TSSkip, MMLName, TSStart, TSRange, TSSkip SC-1, 1, 18, 18, SC-3 1, 18, 18 SC-2, 1, 18, 18, SC-4, 1, 18, 18
| FAS Side 1 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| FAS Side 2 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| FAS Side 1 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| FAS Side 2 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
# Rack 1 bearer channels MAPTYPE:NFAS:PC # NFAS to SS7 #MMLName, SpanStart, SpanRange, TSStart, TSRange, TSSkip, DPC, Net_Ind., CICstart, CICRange, CICSkip SC-1, 1, 3, 1, 18, 18, 2.2.1, 2, 1, 46, 18
| NFAS Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 1 | 1 |
SpanRange | 3 | 3 |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| PC Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 1 | 1 |
CICRange | 46 | 70 |
CICSkip | 18 | 24 |
Notes:
# Rack 1 bearer channels MAPTYPE:NFAS:NFAS # NFAS to NFAS #MMLName, SpanStart, SpanRange, TSStart, TSRange, TSSkip, MMLName, SpanStart, SpanRange, TSStart, TSRange, TSSkip SC-1, 1, 3, 1, 18, 18, SC-3 4, 3, 1, 18, 18 SC-2, 1, 2, 1, 18, 18, SC-4, 4, 2, 1, 18, 18
| NFAS Side 1 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 1 | 1 |
SpanRange | 3 | 3 |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| NFAS Side 2 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 4 | 1 |
SpanRange | 3 | 3 |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| NFAS Side 1 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 1 | 1 |
SpanRange | 2 | 2 |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
| NFAS Side 2 | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 4 | 1 |
SpanRange | 2 | 2 |
TSStart | 1 | 1 |
TSRange | 18 | 24 |
TSSkip | 18 | 24 |
Notes:
To determine the MMLName of the path, perform the following steps:
Step 1 Look in the /opt/TransPath/etc directory at the sigPath.dat file to find the compID; for example, 00070001.
Step 2 Look in the components.dat file and find that compID. The MMLName is listed in the third column. Do not use the quotes in this file.
The other fields in the scripts are:
![]() | Tips Remember the following tips when creating the script. |
The point code information must match exactly with the entries you used when you configured the system with the CT. If you are unsure, you can print out the dpc.dat file and verify.
The number of CICs defined must match the number of time slots defined. If not, the BCGEN tool gives an error.
The BCGEN tool does not validate that CICs or time slots have not already been used. You must ensure that a CIC or time slot is not overcommitted.
Step 1 After you create the scripts, enter the following command:
bcgen
![]() | Caution All files in the /opt/TransPath/etc/BCGen directory with the .bgc extension will be processed. Do not store any unwanted scripts or backups in this directory. |
Step 2 Watch the screen for any error messages. Error messages direct you to .dat files you can view to get the correct values for fields in the script that cause the error.
For example, if you use an incorrect point code in your script, the error message directs you to the dpc.dat file. You would change to the /opt/TransPath/etc directory and view the dpc.dat file to obtain the correct point code and replace that value in your script.
![]() | Tips A common error is incorrectly configuring your bearer channels. Make sure your scripts follow the format in the examples shown in this document. |
Step 3 Restart the software by making sure that you are logged in as the root user and entering:
/etc/init.d/transpath start
Step 1 Use the configuration tool to configure your Dial Access Solution setup. Perform the following tasks:
(a) Create all of your network access servers (NASs).
(b) Create IP interfaces and IP services on the NASs.
(c) Create lines for signaling from the NAS to the Cisco SC2200. Do not create lines that carry only bearer traffic. The BCGEN tool creates these bearer lines when it reads your scripts.
(d) Create traffic paths; however, do not assign CICs.
(e) Create signal paths and assign signal channels.
![]() | Caution Do not create any access lines. No access lines should be connected to the NASs; these are created when the BGCEN tool reads your script files. |
Step 2 Build, deploy and transfer the data (.dat) files (using FTP) to your UNIX host server for the Cisco SC2200.
Step 1 Make sure that the software is not running by entering the following command:
ps -ef | grep tran
Step 2 If the system returns no response, the software is not running. If the response indicates that the software is running, make sure you are logged into the system as the root user and enter the following command:
/etc/init.d/transpath stop
Repeat Step 1 until the system returns no response, showing that the software is not running.
Step 1 Change to the TransPath directory and make a new directory called BCGen:
cd /opt/TransPath/etc
mkdir BCGen
The BCGen directory is used to store your scripts.
Step 2 Change to the BCGen directory by entering:
cd /opt/TransPath/etc/BCGen
Use a text editor to create your script files in the BCGen directory. Name the files with the extension .bcg; for example, rack1.bcg.
The first required field in the script is MAPTYPE. The arguments describe the two sides of a nailed bearer configuration. You can use the following maptypes:
This section shows an example of PC to PRIIP, with an explanation of the script. For examples of other types of scripts, see the "Creating Your Scripts" section.
# Rack 1 bearer channels MAPTYPE:PC:PRIIP # only one NAS for now #DPC, Net_Ind., CICstart, CICRange, CICSkip, NAS IP, IPPort, SpanStart, SpanRange, TimeSlotStart,range,skip 2.2.1, 2, 1, 78, 0, 2.33.12.1, 3000, 0, 4, 1, 1F, 10 2.2.1, 2, C8, 1E, 0, 2.1.2.1, 3000, 1, 1, 1, 1F, 10
| PC Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | 1 | 1 |
CICRange | 78 | 120 |
CICSkip | 0 | 0 |
Notes:
| PRIIP Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 0 | 0 |
SpanRange | 4 | 4 |
TSStart | 1 | 1 |
TSRange | 1F | 31 |
TSSkip | 10 | 16 |
Notes:
| PC Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
CICStart | C8 | 200 |
CICRange | 1E | 30 |
CICSkip | 0 | 0 |
Notes:
| PRIIP Side | ||
|---|---|---|
Field | Hex Value | Decimal Value |
SpanStart | 1 | 1 |
SpanRange | 1 | 1 |
TSStart | 1 | 1 |
TSRange | 1F | 31 |
TSSkip | 10 | 16 |
Notes:
The format for the PC:PRIIP contains the following fields:
![]() | Tips Remember the following tips when creating the script. |
The point code information and the IP information must match exactly with the entries you used when you configured the system with the CT. If you are unsure, you can print out the dpc.dat and sigChanDevIp.dat files and verify the numbers.
The number of CICs defined must match the number of time slots defined. If not, the BCGEN tool gives an error.
The BCGEN tool does not validate that CICs or time slots have not already been used. You must ensure that a CIC or time slot is not overcommitted.
Step 1 After you create the scripts, enter the following command:
bcgen
Step 2 Watch the screen for any error messages. Error messages direct you to .dat files you can view to get the correct values for fields in the script that cause the error.
For example, if you use an incorrect IP address in your script, the error message directs you to the sigChanDevIp.dat file. You would change to the /opt/TransPath/etc directory and view the sigChanDevIp.dat file to obtain the correct IP address and replace that value in your script.
![]() | Tips A common error is incorrectly configuring your bearer channels. Make sure your scripts follow the format in the examples shown in this document. |
Step 3 Restart the software by making sure that you are logged in as the root user and entering:
/etc/init.d/transpath start
For the Cisco Dial Access Solution, see the Configuration Tool Guide for Signaling Controller, available at:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/r2/ctg2/index.htm
For the TransPath Classic configuration, see the TransPath System Configuration Tool Guide, available at:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/r1/tct_gd.pdf
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Wed Oct 13 16:09:57 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.