4 Commands
This chapter describes the command conventions for commands that are not pass-through or debug commands. The commands are listed in alphabetical order.
act-alm-trns
Use this command to transfer all alarm indications from the local office to the remote maintenance center.
Parameters
This command has no parameters.
Example
act-alm-trns
Dependencies
No other action command can be in progress when this command is entered.
Notes
After this command is entered, use the rept-stat-alm command to verify the action.
New alarms cause the local maintenance center audible alarms to sound for a short period.
Output
act-alm-trns
rlghncxa03w 04-01-09:50:17 EST EAGLE 31.3.0
Alarms transferred to Remote Maintenance Center
Command Completed.
;
Related Topics
act-cdl
Use this command to initiate a command driven loopback for testing a signaling link.
Command Driven Loopback is the ability to locally drive a signaling link into a manual line loopback. The data received on the signaling link is echoed (transmitted) back. This is effectively the reverse of the tst-slk:loopback=lxvr, which loops the transmitted data back to the receiver.
Parameters
- link (mandatory)
- SS7 signaling links. The SS7 signaling link to be tested.
- Synonym:
- port
- Range:
- a, b, a1 - a31, b1 - b31
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling links.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
act-cdl:loc=1205:link=b
Dependencies
The card location specified in the loc parameter must be equipped.
The signaling link specified in the link parameter must be equipped.
LFS processing must be stopped or must be allowed to complete on the specified signaling link before this command can be entered.
The loopback=payload parameter is valid only for LIM-ATM and E1-ATM cards.
Command Driven Loopback testing is not available during upgrade.
A Command Driven Loopback test cannot be in progress on the specified link when this command is entered.
A tst-slk command cannot be in progress on the specified link when this command is entered. The tst-slk processing must be stopped or must be allowed to complete before this command can be entered
The card location specified in the loc parameter must be in the In-Service-Normal (IS-NR) state.
The card location specified in the loc parameter must support Command Driven Loopback testing.
The signaling link specified in the link parameter must not be active.
The card location specified in the loc parameter cannot be reserved by the system.
Notes
None
Output
act-cdl:loc=1205:link=b
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Command Accepted: Command Driven Loopback message is sent.
;
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Command Completed.
;
act-dlk
Use this command to activate an IP data link and put the link into service. The state of the link is changed from out of service maintenance disabled (OOS-MT-DSBLD) to in service normal (IS-NR).
Parameters
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
act-dlk:loc=1308
Dependencies
No other action command can be in progress when this command is entered.
The shelf and card must be equipped.
The card location must contain a card that is running the STPLAN application.
The card location, frame, shelf, or slot must be within the allowed range.
A card location that is valid and defined in the database must be specified.
The card in the location specified by the loc parameter must be in service.
The ipaddr parameter must specify a valid IP address.
Notes
None
MTT 2373 deleted per PR 204449 - MB
Output
act-dlk:loc=1308
rlghncxa03w 04-01-17:00:36 EST EAGLE 31.3.0
Activate Link message sent to card.
Command Completed.
;
act-echo
Use this command to force responses from the scroll area of a terminal to be printed to a specified terminal or printer. The command supports one terminal echoing to many terminals or many terminals echoing to one terminal.
Caution:
Exercise restraint in using this command, because excessive echoing can cause a loss of output at the receiving terminal.Example
act-echo:trm=3
Dependencies
Terminal output cannot be echoed to a terminal that is out of service.
If a terminal is already echoing to a specified terminal, this command cannot be entered to echo the terminal’s output to that same terminal.
Echo is not allowed to the terminal from which the command is issued.
Echo is not allowed to or from IP User Interface telnet ports (terminals 17-40).
Terminal output cannot be echoed to a terminal that is inhibited.
The trm parameter must be specified.
Notes
This command can be used to echo only command output responses to a terminal. For alarm and network messages to be sent to a terminal, the chg-trm command must be used.
To echo output to a destination port, a user must be logged in at the destination port. The following warning message appears in the scroll area of the issuing terminal if echo is attempted to a terminal that has no user logged in:
No user logged in at Terminal X. No echo will occur until a user
logs in.
where X is the trm parameter value specified in the act-echo command.
Output
act-echo:trm=2
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
act-echo:trm=2
Command entered at terminal #1.
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
Scroll Area Output is echoed to terminal 2.
Caution: Loss of output may occur if too many terminals are echoed.
;
act-echo:trm=3
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
act-echo:trm=3
Command entered at terminal #1.
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
Scroll Area Output is echoed to terminal 2.
Scroll Area Output is echoed to terminal 3.
Caution: Loss of output may occur if too many terminals are echoed.
;
act-file-trns
Use this command to start a file transfer between the system and a remote computer.
Parameters
- loc (optional)
- The location of the fixed disk to or from which the file is to be uploaded or downloaded.
Example
act-file-trns:loc=1116
Dependencies
The loc parameter must specify a TDM card.
Only one file transfer can be active at a time.
This command cannot be entered on a telnet terminal (IDs 17-40).
Notes
Output messages indicating transfer initiated and transfer terminated (whether successful or not) are sent to the output devices in the Security Administration output group.
When used to output seculog, the copy-seculog command sends data to the FTA. Extracting seculog data from the FTA requires:
- A computer with a VT320 or KSR connection to the system
- A communication program that both emulates VT terminals and supports Kermit file transfer
- A spreadsheet program that can import Comma Separated Value (CSV) text files
A PC running ProComm© for Windows and Microsoft Excel© can be used.
Extracting seculog file from the FTA
-
Display the contents of the FTA. Enter
disp-fta-dir:loc=xxxx.Where xxxx = the active TDM (1114 or 1116)
-
Delete any existing files from the FTA. Enter
dlt-fta:loc=xxxx:all=yes.Where xxxx = the active TDM (1114 or 1116)
-
Enter the command to send seculog to the FTA. For example:
copy-seculog:slog=act:dloc=stb:dfile="seculog_copy" -
Activate the file transfer. Enter
act-file-trns:loc=xxxx.Where xxxx = the active TDM (1114 or 1116)
-
Display a list of the files transferred to the FTA. Enter
disp-fta-dir:loc=xxxx.Where xxxx = the active TDM (1114 or 1116)
-
Use the
getcommand from within the communications program configured to run Kermit in ASCII mode to transfer the desired files (with the .csv suffixes) to the PC.For example:
> get seculog_copy.csv> finish -
After all files are successfully transferred and confirmed, remove the files from the FTA. Enter
dlt-fta:loc=xxxx:all=yes.Where xxxx = the active TDM (1114 or 1116)
Output
Normal session output to non-Security Administration user's terminal.
act-file-trns:loc=1114:timeout=20:retries=2
rlghncxa03w 04-01-05 14:37:05 EST EAGLE 31.3.0
act-file-trns:loc=1114:timeout=20:retries=2
Command entered at terminal #1.
;
rlghncxa03w 04-01-05 14:37:05 EST EAGLE 31.3.0
Awaiting File Transfer with remote.
Please initiate binary Kermit session on local computer
;
rlghncxa03w 04-01-05 14:38:33 EST EAGLE 31.3.0
File Transfer : 0 file(s) DOWNLOADED from location 1114 successfully
File Transfer : 1 file(s) UPLOADED to location 1114 successfully
File Transfer : Kermit Session terminated NORMALLY
Normal session output to Security Administration group terminals.
act-file-trns:loc=1114:timeout=20:retries=2
rlghncxa03w 04-01-05 14:40:42 EST EAGLE 31.3.0
File Transfer : INITIATED on terminal #1
;
rlghncxa03w 04-01-05 14:41:07 EST EAGLE 31.3.0
File Transfer: 511_byte.bin UPLOADED to location 1114 successfully.
;
rlghncxa03w 04-01-05 14:41:44 EST EAGLE 31.3.0
File Transfer : terminated NORMALLY on terminal #1
Normal session output to Security Administration user's terminal.
act-file-trns:loc=1114:timeout=20:retries=2
rlghncxa03w 04-01-05 14:42:51 EST EAGLE 31.3.0
act-file-trns:loc=1114:timeout=20:retries=2
Command entered at terminal #1.
;
rlghncxa03w 04-01-05 14:43:29 EST EAGLE 31.3.0
File Transfer : INITIATED on terminal #1
;
rlghncxa03w 04-01-05 14:43:53 EST EAGLE 31.3.0
Awaiting File Transfer with remote.
Please initiate binary Kermit session on local computer
rlghncxa03w 04-01-05 14:44:19 EST EAGLE 31.3.0
File Transfer: 511_byte.bin UPLOADED to location 1114 successfully.
;
rlghncxa03w 04-01-05 14:44:52 EST EAGLE 31.3.0
File Transfer : 0 file(s) DOWNLOADED from location 1114 successfully
File Transfer : 1 file(s) UPLOADED to location 1114 successfully
File Transfer : Kermit Session terminated NORMALLY
;
rlghncxa03w 04-01-05 14:45:31 EST EAGLE 31.3.0
File Transfer : terminated NORMALLY on terminal #1
;
act-flash
Use this command to activate the trial FLASH GPL that is currently running on one target card or on a range of cards.
Parameters
- gpl (optional)
- Generic program load. The flash GPL type that is
running on the cards in the specified range of cards.
Use "gpl=multiple" to simultaneously flash multiple E5-class cards running different GPLs, such as BLMCAP, etc. The command will then flash all E5-class cards in the specified range.
Note:
This parameter must be specified for cards that have more than one flash image (GPL).
Example
act-flash:loc=1105
act-flash:sloc=1101:eloc=1112:gpl=blmcap
Dependencies
The card, or cards, in the specified location or range of locations for this command must be actively running a flash GPL in trial mode.
The allowed cards are E5-ENET-B, E5-E1T1-B, E5-MCAP, or Service Module. Card locations xy09 and xy10 (x is the frame, y is the shelf) can be specified only for MUX cards.
Each specified card does not have to be defined in the database, but it does have to be aligned on the IMT bus.
If the target card is a MUX card, then both card locations specified in the sloc and eloc parameters must contain MUX cards on the same IMT bus. For these cards, the bus is implicit based on the specified location. Location xy09 specifies a MUX A Bus, and location xy10 specifies a MUX B Bus (x is the frame and y is the shelf). For example, sloc=1109:eloc=6109 specifies all MUX cards on the A Bus only; sloc=1110:eloc=6110 specifies all MUX cards on the B Bus only. MUX cards from both the A bus and B bus cannot be flash downloaded simultaneously.
The card must be running an inactive flash GPL when this command is executed.
The provisioning subsystem mode (simple, duplex) must be established prior to executing the command.
The loc parameter cannot be specified with the eloc and sloc parameters.
Either the loc parameter or the eloc and sloc parameters must be specified.
The eloc and sloc parameters must be specified together in the command; one parameter cannot be specified without the other parameter.
The sloc parameter value cannot be greater than the eloc parameter value.
MUX cards in the specified sloc and eloc card locations must be present and able to communicate over the IMT. The cards do not have to be provisioned in the database.
The gpl parameter must be specified if the eloc and sloc parameters are specified.
The gpl parameter must be specified for cards that have more than one flash image (GPL).
MUX cards in the locations specified by the sloc and eloc parameters must be running the specified GPL. If the GPL specified is not multiple, then other cards in the range of locations can be running other GPLs but will not be activated, and only cards that are within the range and running the specified GPL will be activated.
A card that is the active MASP cannot be specified for the loc, sloc, or eloc parameter.
No other action command can be in progress when this command is entered.
A card location that is valid and defined in the database must be specified.
MUX cards specified in the sloc and eloc location parameters must be running the specified general program load (gpl). For other GPLs including multiple, all cards within the range running the specified GPL will be activated.
This command cannot be entered during an Extended Bit Error Rate Test (BERT).
The gpl=multiple parameter can be specified only if the sloc and eloc parameters are specified.
The gpl=multiple parameter can be specified only if the cards in the locations specified in the sloc and eloc parameters are E5-class cards.
Notes
None
Output
act-flash:loc=1105
rlghncxa03w 04-01-04 13:05:05 EST EAGLE 31.3.0
FLASH Memory Activation for card 1105 Started.
;
rlghncxa03w 04-01-04 13:05:05 EST EAGLE 31.3.0
FLASH Memory Activation for card 1105 Completed.
;
rlghncxa03w 04-01-04 13:05:05 EST EAGLE 31.3.0
Command Completed.
;
act-flash:sloc=1101:eloc=1112:gpl=blmcap
tekelecstp 18-01-15 02:30:23 EST EAGLE 46.6.0.0.0-71.5.0
FLASH activation for cards 1101 - 1112 Completed.
LOC 1101 : PASSED
LOC 1102 : PASSED
LOC 1112 : PASSED
ALL CARD RESULTS PASSED
;
Command Completed.
;
act-ftp-trns
Use this command to activate an FTP transfer to send database tables from the system to the customer’s FTP server.
Note:
This command is not for customer use. It is for Tekelec use only.Parameters
- filetype (mandatory)
- The system table type to be transferred.
- Range:
-
- all
- Transfer all types of tables
- enum
- Transfer all ENUM tables
- exts
- Transfer the Extended Statistics table
- ip
- Transfer all IP tables
- gtt
- Transfer all Global Title Translation tables
- gws
- Transfer all Gateway Screening tables
- mtp
- Transfer all Message Transfer Part tables
- vflex
- Transfer all V-Flex tables
Example
act-ftp-trns:action=put:filetype=gtt
Dependencies
This command cannot be entered if another file transfer is already in progress.
The action and filetype parameters must be specified in the command.
The FTP Server table must be accessible.
The FTP Server table must contain at least one FTP server entry that specifies the user application
An IPSM card must be in service before this command can be entered.
This command cannot be entered when CAT2 IPSM to OAM syncing is in progress.
Notes
This command communicates with the user application, defined in the FTP Server table. The IP address and server details necessary for an FTP transfer are also stored in the FTP Server table. One such user application is the FTP-based Table Retrieve Application (FTRA). Refer to the FTP-Based Table Retrieve Application (FTRA) User Guide for assistance.
Output
act-ftp-trns:action=put:filetype=ip
tekelecstp 09-05-06 06:41:17 EST EAGLE 41.0.0
FTP command sent to IPSM card - Processing
;
tekelecstp 09-05-06 06:41:17 EST EAGLE 41.0.0
Copy-table started - tablexxx.tbl
Copy-table COMPLETE.
;
tekelecstp 09-05-06 06:41:17 EST EAGLE 41.0.0
FTP file transfer started - tablexxx.tbl
FTP file transfer SUCCESSFUL.
;
tekelecstp 09-05-06 06:41:17 EST EAGLE 41.0.0
FTP transfer COMPLETE.
;
act-gpl
Use this command to change the status of the trial GPL from “trial” to “approved.” The status of the previously approved GPL is changed to “trial.”
Parameters
- gpl (mandatory)
- Generic program load. The name of the GPL
identifier to be moved from "trial" to "approved" status on the disk.
- Range:
- xyyyyyyy
1 alphabetic character followed by up to 7 alphanumeric characters. Valid GPLs are:
atmhc—Used by E5-ATM-B cards to allow the card to support up to 3 signaling links.
bldc32—Flash GPL containing a tar image with all code required on E5-MCAP cards to support VxWorks6.9 32-bit application, as in OAMHC69.
bldc64—Flash GPL containing a tar image with all code required on E5-SM8G-B cards for SCCP64, ENUM64, SIP64 and DEIR64 applications.
blmcap—Flash GPL containing a tar image with all code required on E5-MCAP, E5-E1T1-B, E5-MCPM-B, E5-ATM-B, E5-ENET-B, and E5-SM8G-B cards
blslc32—Flash GPL containing a tar image with all code required on SLIC cards for 32-bit application i.e. MCPHC, IPSHC etc.
blslc64—Flash GPL containing a tar image with all code required on SLIC cards for 64-bit application i.e. SCCP64, ENUM64, SIP64 and DEIR64.
blsl932—Flash GPL containing a tar image with all code required on SLIC cards for 32-bit application on VxWorks6.9, as in IPSHC69 and MCPHC69.
deirhc— Used by E5-SM8G-B cards to support the S13/S13' EIR feature.
enumhc—Used by E5-SM8G-B cards to support the ENUM Mobile Number Portability and Tier One Address Resolution application.
erthc—Used by E5-ENET-B cards for EAGLE 5 Integrated Monitoring Support functions
hipr2—Communication software used on the High Speed IMT Packet Router (HIPR2) card
ipsg—Used by E5-ENET-B cards to support the combined functionality of IPLIMx M2PA and IPGWx M3UA
ipsg32—Used by SLIC cards to support IPSG application with 64-bit addressing either with GTT functionality or without it.
ipshc—Used by E5-ENET-B cards to support the IPS application.
ipshc69—Used by E5-ENET-B and SLIC cards to support the IPS application when running on VxWorks69.
mcphc— Used by E5-MCPM-B cards for the Measurements Platform feature.
mcphc69—Used by E5-MCPM-B and SLIC cards for the Measurements Platform feature when running on VxWorks69.
oamhc—Used by E5-MCAP cards for enhanced OAM functions.
oamhc69—Used by E5-MCAP cards for enhanced OAM functions, when running on VxWorks 69.
sccphc—Used by E5-SM8G-B cards to support EPAP-based features and the LNP ELAP Configuration feature. If no EPAP-based or LNP ELAP Configuration feature is turned on, and an E5-SM8G-B card is present, then the GPL processes normal GTT traffic.
sfapp—Used by SLIC cards to support the Stateful Firewall Application.
siphc— Used by E5-SM8G-B Cards to support the SIP application.
ss7hc—Application GPL used by E5-E1T1-B and SLIC cards to support E1 and T1 signaling links.
Example
act-gpl:gpl=ss7hc:ver=125-1-0
act-gpl:gpl=deirhc:ver=134-60-0
act-gpl:gpl=enumhc:ver=135-20-0
act-gpl:gpl=ipsg32:ver=140-12-0
Dependencies
No other activate, change, copy, or retrieve GPL commands, nor a GPL audit, can be in progress when this command is entered.
The value specified for the gpl parameter must be supported. See the gpl definition for a list of supported GPLs.
Notes
Test the trial GPL by loading to a card before activating the GPL. Activating the GPL changes it from trial to approved.
The generic program load is committed on the active system and on the standby system.
Trial GPLs are downloaded to cards manually. Only approved GPLs can be downloaded to cards by the system.
Use the
rtrv-gpl command to determine the
version of the GPL.
Output
The output indicates that the specified GPL is activated on each TDM card.
act-gpl:gpl=ss7hc:ver=125-1-0
tekelecstp 05-01-03 16:53:23 EST EAGLE5 33.0.0
SS7HC activate to 1114 completed
SS7HC activate to 1116 completed
;
The output indicates that the specified GPL is activated on each TDM card.
act-gpl:gpl=deirhc:ver=134-60-01
tekelecstp 13-03-15 19:08:39 EST EAGLE 45.1.0
DEIRHC activate to 1114 completed
DEIRHC activate to 1116 completed
;act-gpl:gpl=enumhc:ver=135-20-0
tekelecstp 14-05-20 14:18:32 EST EAGLE 46.1.0
ENUMHC activate to 1114 completed
ENUMHC activate to 1116 completed
;
act-gpl:gpl=ipsg32:ver=140-12-0
tekelecstp 12-08-16 09:35:00 EST EAGLE 46.5.0
IPSG32 activate to 1114 completed
IPSG32 activate to 1116 completed
;
The number of "cards of x complete" represents the total number of cards that can communicate on the IMT at the instant that this information is displayed.
act-gpl:gpl=hipr2:ver=135-041-000
act-gpl:gpl=hipr2:ver=135-041-000
tekelecstp 15-04-16 11:12:45 EST EAGLE5 46.2.0-65.42.0
5575.1104 CARD 1107,A INFO IP Connection Failed
tekelecstp 15-04-16 11:12:49 EST EAGLE5 46.2.0-65.42.0
act-gpl:gpl=hipr2:ver=135-041-000
Command entered at terminal #20.
;
Command Accepted - Processing
tekelecstp 15-04-16 11:12:50 EST EAGLE5 46.2.0-65.42.0
HIPR2 activate on 1116 completed
HIPR2 activate on 1114 completed
;
act-lbp
Use this command to activate one or more loopback point tests for testing data signaling link elements in an SS7 transmission path. Use this command to:
- Activate a test for a specified loopback point that is defined in the LFS database table
- Activate a test for one loopback point that is not defined in the LFS database table
- Activate tests for all loopback points that have been defined in the LFS database table. See Summary of Loopback Testing Commands and Functions for information about loopback testing commands and functions.
The ent-lbp command can be used to define a maximum of 32 loopback points in the LFS database table.
Parameters
To activate a test for a single loopback point that is defined in the LFS database table, specify the loopback point number in the lbp parameter and do not specify the lfst, rle, rep, or clli parameter in the command. Information from the LFS database is used to activate the test for the specified loopback point.
To activate a test for a single loopback point that is not defined in the LFS database table, specify one or more of the lfst, rle, rep, and clli parameters in the command. (If the clli parameter is not specified, then the value is blank, a null string. If the rep parameter is not specified, the default value is 0.)
To activate tests for all loopback points defined in the LFS database, do not specify the lbp, lfst, rle, rep, or clli parameter in the command. Information from the LFS database table is used to activate tests for all defined loopback points.
- link (mandatory)
- SS7 signaling link. The SS7 signaling link to be tested.
- Synonym:
- port
- Range:
- a, b, a1 - a31, b1 - b31
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling link ports.
- loc (mandatory)
- The location of the card containing the signaling link to use for loopback point testing.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
- clli (optional)
- Common language location identifier. The CLLI code or other mnemonic identifier, used to refer to the given loopback point.
- force (optional)
- The force=yes parameter must be specified to start a test when there are 256 or more tests already running.
- lbp (optional)
- Loopback point ID. A far-end loopback point that lies along an SS7 signaling link path between the STP and the target device (up to and including the target device).
- lfst (optional)
- Link fault sectionalization test.
Note:
This parameter is mandatory if the rle, clli, or rep parameter is specified.- Range:
-
- llt
- latching loopback test; a software latch is set at the test point to reverse everything that is received and return it to the sender until the test is complete
- mlt
- manual latch loopback test; an external hardware latch is set to reverse everything that is received and return it to the sender until the test is complete (for equipment that cannot set a software latch for the test)
- nlt
- nonlatching loopback test; no permanent latch is set. Loopback codes are alternated with test data until the test is complete.
- Default:
- The value in the LFS database, as shown in the
rtrv-lbpcommand output
- maxerr (optional)
- Bit error threshold. This parameter specifies the actual number of errors allowed for a specific time period during which loopback testing is being performed. If this threshold is exceeded, the TEST STATUS field in the output report indicates an error.
- pattern (optional)
- This parameter specifies the type of test pattern used to perform the LFS test.
- Range:
-
- b2047
- 047-bit BERT pattern sent until it is stopped by software
- b511
- 511-bit BERT pattern sent until it is stopped by software
- octet
- Data (from the data parameter) sent continuously until it is stopped by software
- alternate
- Alternately, a count of 100 octets of the specified data (from the data parameter) followed by 100 octets of 0, sent until it is stopped by the software
The octet and alternate values are valid only when lfst=llt is specified.
- Default:
- b2047
- rep (optional)
- Repetition count. The number of link elements of the same type (not including the target device) that lie between the STP and the link element to be tested.
- rle (optional)
- Remote link element. The link element to be looped back for testing.
Note:
This parameter is mandatory if the lfst, clli, or rep parameter is specified.
Example
Activate tests for all loopback points that are defined in the LFS database table:
act-lbp:loc=1205:link=b:pattern=alternate:maxerr=10:time=000200
Activate a test for a single loopback point that is not defined in the LFS database table:
act-lbp:loc=1205:link=b:lbp=1:rle=ds0:lfst=llt:clli=rlghncxa05w
act-lbp:loc=1205:link=b:lbp=1:rle=ds0:lfst=llt:clli=rlghncxa05w:pattern=octet:data=h’ff
act-lbp:loc=1205:link=b:lbp=1:rle=ds0:lfst=llt:clli=rlghncxa05w:maxerr=40:time=12000
Activate a test for a single loopback point that is defined in the LFS database table:
act-lbp:loc=1205:link=b:lbp=3:pattern=alternate:maxerr=10:time=000200
Dependencies
The Link Fault Sectionalization (LFS) feature must be on before this command can be entered.
If the rle=nei parameter is specified, the rep=0 parameter must be specified.
The rep parameter can be specified only if the lfst=llt parameter is specified.
The rle=ds0 or the rle=nei parameter cannot be specified if the lfst=nlt parameter is specified. The DS0 and Network Element Interface (NEI) link elements do not support non-latching loopbacks.
If one or more of the rle, rep, lfst, or clli parameters are specified, the database is not used to look up their values; therefore, the lfst and rle parameters must be specified when the rep or clli parameter is specified.
The data parameter can be specified only if the pattern=octet parameter or pattern=alternate parameter is specified.
The pattern=octet and pattern=alternate parameters cannot be specified for non-latching tests (rle=nlt).
The card location (loc parameter) must contain a provisioned and equipped E5-E1T1-B card, provisioned with the LIMT1 card type, running the SS7ANSI or CCS7ITU application.
The card in the loc parameter location must be in the In-Service-Normal state.
The signaling link that is used for LFS testing must be equipped, and must be deactivated before this command is entered.
The loopback points (LBPs) must have been previously defined in the database.
Only one LFS test can be active on a signaling link at a time.
This command cannot be entered for a signaling link LFS test when the maximum number of LFS tests are active for the card. At least one LFS test must complete before this command can be entered again.
Up to 8 LFS tests at a time can be active on an E5-E1T1-B card used as a T1 card.
This command cannot be entered when the maximum combined total number of LFS and link tests (1024) are in progress in the system. At least one test must complete before this command can be entered again.
The force=yes parameter must be specified to activate a test when there are 256 or more tests already running in the system.
The specified signaling link must not be running a tst-slk test when this command is entered. The tst-slk test must be stopped or allowed to complete before this command can be entered for the link.
The specified signaling link must not be in Command Driven Loopback (CDL) when this command is entered. The link must be removed from CDL before this command can be entered for the link.
This command cannot be entered for a link that is already blocked by another link diagnostic test. The test must be canceled or allowed to complete before this command can be entered for the link.
LFS testing is not available during upgrade.
The maximum number of loopback point entries allowed in the LFS table is 32.
Notes
This command is not supported for E5-ATM-B cards.
If an LFS test is aborted by a card reset, it can leave the remote far-end loopback condition active. Use the dact-lbp command to cancel LFS tests.
The E5-E1T1-B cards support this command on up to 8 T1 channels at a time; the command is not supported for E1.
The test can terminate with the status "ERROR, bit error exceeded threshold" for two reasons.
- The number of cumulative bit errors exceeds the specified maxerr parameter value.
- The number of bit errors for one second reaches or exceeds 255, without considering the maxerr parameter value.
Output
The LFS report is displayed when the LFS test completes.
This example shows how the test failed because the bit error rate exceeded the threshold. The maxerr=10 parameter is used for a test time of 2 minutes. Because more than 10 errors occurred within 2 minutes, the test is considered a failure and the TEST STATUS field displays the cause. The parameter values are applied to each loopback point. The maxerr value is per test, not cumulative for all tests.
act-lbp:loc=1205:link=b:pattern=alternate:maxerr=10:time=002000
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
LOC = 1205 Link = B LSN = ls11345678 Start time = 11:10:34
PATTERN = ALTERNATE DATA= FF MAXERR = 10 TIME = 00:02:00
TEST STATUS = ERROR, bit error exceeded threshold.
LBP CLLI RLE REP LFST BIT_ERROR ERRORED_SEC DURATION
2 rlghncxa05w DS0 0 LLT 0 0 00:02:00
3 ------------ OCU 0 NLT 8 2 00:02:00
5 ------------ NEI 0 LLT 15 1 00:01:20
;
In this example, the test failed because the loopback could not be established.
act-lbp:loc=1205:link=b:pattern=alternate:maxerr=10:time=000200
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
LOC = 1205 Link = B LSN = ---------- Start time = 11:10:34
PATTERN = ALTERNATE DATA= FF MAXERR = 10 TIME = 00:02:00
TEST STATUS = ERROR, loopback was not established.
LBP CLLI RLE REP LFST BIT_ERROR ERRORED_SEC DURATION
1 rlghncxa05w DS0 0 LLT 0 0 00:00:00
;
Legend
- LOC—Card location that contains the signaling being tested
- LINK—Signaling link that is being tested on the card
- LSN—Name of the linkset that contains the link being tested
- Start time—Time that the test started
- PATTERN—Type of test pattern used to perform the LFS test
- DATA—Data used with the octet or alternate patterns
- MAXERR—Bit error threshold; actual number of errors allowed for the specific time period during which loopback testing is being performed. If this threshold is exceeded in the specified time period, the TEST STATUS field in the output report indicates an error.
- TIME—Specified length of time to run the test in order to determine success or failure. If the number of errors that actually occur during this time exceeds the threshold set by the maxerr parameter, the loopback test is identified as a failure.
- TEST STATUS—Any one of the following TEST STATUS values can appear:
- PASS
- ERROR, LFS HARDWARE is not available.
- ERROR, loopback could not be established.
- ERROR, bit error exceeded threshold.
- ERROR, LFS test aborted.
- ERROR, LFS hardware failed.
- LBP—Loopback point used to perform the LFS test
- CLLI—Common Language Location Identifier (CLLI) code, or other mnemonic identifier, used to refer to the given loopback point
- RLE—Remote link element to be looped back for testing
- REP—Repetition count. The number of link elements of the same type (not including the target device) that lie between the STP and the link element to be tested.
- LFST—Type of link fault sectionalization loopback test to be performed
- BIT_ERROR—The number of bit errors observed during the test
- ERRORED_SEC—The number of seconds that contained bit errors during the test. (Bit errors are sampled once per second; each sample that contains bit errors adds one second to this count.)
- DURATION—Length of time that the test actually ran for the loopback point. For successful test, the TIME and the DURATION should be the same. If a test ran for less than the specified amount of time, the DURATION will be less than the TIME.
act-lg-card
Use this command to activate LG event generation/reception on a given LG card
The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.Parameters
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
act-lg-card:loc=1302
act-lg-card:loc=1302:dir=tx
act-lg-card:loc=1302:dir=rx
Dependencies
The card location must not be 1113-1118, xy09, or xy10 where x is the frame and y is the shelf.
The LG Card table is corrupt or cannot be found.
The card location specified in the loc parameter must be of a provisioned LG card.
Loc is mandatory
Activating the state of an LG object that is already activated or deactivating the state of an LG object that is already deactivated has no effect.
Output
None.
act-lg-engine
Use this command to activate LG event generation/reception on an LG engine hosted on a LG card.
The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.
Parameters
- loc (optional)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
act-lg-engine:loc=1301
act-lg-engine:engine=txengine1
act-lg-engine:loc=1301:dir=tx
act-lg-engine:engine=txengine1:test=yes
Dependencies
The engine name specified must pre-exist in the LG Engine table.
The loc parameter cannot be specified with the engine parameter.
Atleast one optional parameter must be specified.
The card location specified in the loc parameter must be of a provisioned LG card.
DIR parameter can only be specified along with LOC parameter.
Activating the state of an LG object that is already activated or deactivating the state of an LG object that is already deactivated has no effect.
Test parmameter can only be specified with Tx engine.
Output
None.
act-lg-grp
Use this command to activate event generation/reception for a LG group. The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.
Example
act-lg-grp:grp=lggroup1:dir=tx
act-lg-grp:grp=lggroup1:dir=rx
act-lg-grp:grp=lggroup2
Dependencies
The group name specified must pre-exist in the LG Group table
The LG Group table is corrupt or cannot be found.
The grp parameter must be specified.
Activating the state of an LG object that is already activated or deactivating the state of an LG object that is already deactivated has no effect.
Output
None.
act-lg-sys
Use this command to activate the LG event generation/reception on all LG cards configured in the system.
The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.Parameters
Example
act-lg-sys:dir=tx
act-lg-sys:dir=rx
act-lg-sys:dir=all
Dependencies
The LG System table is corrupt or cannot be found.
dir is mandatory
Activating the state of an LG object that is already activated or deactivating the state of an LG object that is already deactivated has no effect.
Output
None.
act-lpo
Use this command to force a processor outage on the specified link. The system begins sending link status signal units (LSSUs) with a status of SIPO to the adjacent signaling point. Level 2 status remains in service, except when the link is an ATM high-speed signaling link.
Note:
The signaling link’s blocked status is not preserved across a LIM reboot.Parameters
- link (mandatory)
- The signaling link on the card specified in the loc parameter. The links can be specified in any sequence or pattern.
- Synonym:
- port
- Range:
- a, b, a1 - a63, b1 - b63
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling links.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
act-lpo:loc=1101:link=a
act-lpo:loc=1102:link=a40
Dependencies
A card location that is valid and defined in the database must be specified.
No other action command can be in progress when this command is entered.
This command is not valid for cards running the IPGHC GPL.
The card must contain signaling links.
The signaling link must be equipped in the database.
This command is not valid for links belonging to proxy linksets.
The value specified for the loc parameter must refer to one of the following cards, and the referenced card must be equipped:
- E5-E1T1-B card running the SS7ANSI or CCS7ITU application
- E5-ATM-B card running the ATMANSI or ATMITU application
- E5-ENET-B card running the IPLHC or IPSG application
An appropriate value must be specified for the link parameter when an ATM card is used:
- a-a1, b—E5-ATM-B card running the ATMANSI or ATMITU application
The act-lpo command is not supported for ITU-N16 links.
This command is not valid for IPSG-M3UA signaling links.
Notes
The function of this command is the same as the blk-slk command.
This command generates an alarm.
If this command is followed by the init-card command, the local processor outage is not preserved after the init-card command completes.
The Installation Guide provides an illustration of card locations.
If the blk-slk or act-lpo command is issued for an IPSG signaling link, then an MTP3 local processor outage is initiated.
Output
act-lpo:loc=1101:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Local processor outage being set.
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
* 0014.0208 * SLK 1101,A nc00027 slk local blocked
act-lpo:loc=1102:link=a40
tekelecstp 16-05-27 17:00:36 EST EAGLE 69.1.0
Local processor outage being set.
tekelecstp 16-05-27 17:00:36 EST EAGLE 69.1.0
* 0014.0208 * SLK 1101,A40 lsna40 slk local blocked
act-slk
Use this command to change the link from OOS-MT-DSBLD (Out-of-Service-Maintenance-Disabled) to IS-NR (In-Service-Normal).
Note:
The signaling link’s activated status is preserved across a card reboot.Parameters
- link (mandatory)
- The signaling link on the card specified in the loc parameter. The links can be specified in any sequence or pattern.
- Synonym:
- port
- Range:
- a, b, a1 - a31, b - b31
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have a location specified in the loc parameter.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
act-slk:loc=1301:link=a
Dependencies
The value specified for the loc parameter must refer to one of the following cards, and the referenced card must be equipped:
- E5-E1T1-B, card running the SS7ANSI or CCS7ITU application
- E5-ATM-B card running the ATMANSI or ATMITU application
- E5-ENET-B card running the IPGWI, IPLIMI, IPSG, or SS7IPGW application
- E5-ENET-B or SLIC card running the IPSG application
This command cannot be entered while the tst-slk command is in progress.
A card location that is defined in the database must be specified.
The card must contain signaling links.
No other action command can be in progress when this command is entered.
The specified signaling link must be provisioned in the database.
An appropriate value must be specified for the link parameter when an ATM card is used:
- a-a1, b— E5-ATM-B card running the ATMANSI or ATMITU application
A link cannot be activated if the tst-j1 command is in progress on the same port on which the particular link being activated is configured.
This command is not valid for IPSG-M3UA signaling links.
Notes
Installation Guide provides an illustration of card locations.
If Port A32-A63 and B32-B63 is configured when card is not in IS-NR state, then the card won't come up if it's NON-SLIC card.
Output
act-slk:loc=1301:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Activate Link message sent to card
;
act-user
Use this command to log into the system. This command is an alternate to the login command. After the command is entered, the system requests a password. For security reasons the password is not echoed to the terminal.
Parameters
Example
act-user:uid=john
Dependencies
The first character of the user ID must be a letter.
Notes
Caution:
If the OA&M IP Security Enhancements feature is not turned on, a serial terminal (terminals 1-16) must be used to log in with a new Userid and password for the first time or to change an expired password. The OA&M IP Security Enhancements feature must be turned on before the password can be changed at the prompt from an IP User Interface telnet terminal (IDs 17-40) when it is the first time the user is logging in with an assigned Userid and password or the password has expired. The login command can be used instead of act-user. The command act-user has been provided in accordance with OTGR standards.
When a new system is shipped, the user ID and password are set to the system. Change these immediately to ensure system security.
Output
Not applicable.
alw-card
Use this command to change the card from OOS-MT-DSBLD (Out-of-Service-Maintenance-Disabled) to IS-NR (In-Service-Normal) if the loading is successful.
Parameters
- code (optional)
-
The GPL type to be loaded.
Note:
In case code is provided along with sloc and eloc parameters in the command, then code parameter's value is applied to all the cards within sloc-eloc range, including sloc and eloc.Caution:
Do not enter the pktgen or inactiveprtn values for this parameter unless instructed to do so by Oracle personnel.- Range:
-
- appr
- Downloads the approved GPL
- inactiveprtn
- Downloads the MASP with associated GPL from the inactive partition of the TDM. This value should be specified only during a software upgrade.
- pktgen
- Downloads the PKTGEN GPL for the
appropriate hardware type. This GPL is to be used only for engineering test
purposes and must not be used in customer installations without engineering
oversight.
Note:
After the PKTGEN GPL is initially downloaded to a card by this command, the PKTGEN GPL will continue to be downloaded to the card until anotheralw-cardcommand is issued. - trial
- Downloads the trial GPL
- Default:
- appr
- data (optional)
- High memory refresh. This parameter causes data to
be reloaded to the specified card.
Note:
Various conditions in the system may prevent the persistence of the data on the cards. In case data parameter is provided along with sloc and eloc parameters in the command, then data parameter's value is applied to all the cards within sloc-eloc range, including sloc and eloc.- Range:
-
- persist
- Indicates that the database is not to be reloaded to the card. This parameter is used to request that the EAGLE perform a warm restart of the requested cards. The EAGLE performs various checks to ensure that all conditions necessary to initiate the warm restart are in place. During the card initialization and loading sequence, a warm restart is performed if the card meets the warm restart conditions, as described in the Notes section of this command.
- refresh
- Causes data to be reloaded to the specified card.
- Default:
- refresh
- loc (optional)
- The card location as stenciled on the shelf of the
system.
- Range:
- 1101 - 1108, 1111 - 1113, 1115, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
alw-card:loc=2301:code=trial
alw-card:loc=1101:data=persist
alw-card:loc=1106:data=persist:perdata=gtt
Dependencies
The shelf and card must be equipped.
No other action command can be in progress when this command is entered.
An EPAP-based feature or an LNP feature that is warm-restart capable must be enabled; SIP or DEIR must be enabled, or at least one ENUM or one GTT-enabled IPSG card must be present before this command can be entered with the data=persist parameter.
The data parameter is valid only for SCCP card locations or GPLs, or MPS database (VSCCP) card locations or GPLs, or GTT-enabled IPSG card locations or GPLs.
The card location (loc) must be within the allowed range.
A card that is the active MASP cannot be specified for the loc/sloc/eloc parameter.
- Card location equipped with an E5-APP-B card cannot be specified.
- Card location equipped with a Telco Switch cannot be specified.
If an OAM card is installed in the location specified by the loc parameter, then only a value of inactiveprtn is supported for the code parameter.
The S13 EIR feature must be activated before allowing a card running the DEIRHC GPL.
The PERDATA parameter is valid only with the DATA parameter.
The SIP NP feature must be activated before allowing a card running the SIPHC GPL.
Notes
Installation Guide provides an illustration of card locations.
The system previously supported the data parameter for reloading GTT data. The system does not support persistent GTT data loading, and the data parameter is now used in support of a warm restart feature.
A number of reasons exist for not being able to warm restart. If none of these conditions exists, a warm restart is possible and will be attempted following a Service Module card reset.
- The following conditions require a full data reload:
- AUDIT FAILED—Checksum comparisons of the LNP database failed during card initialization. Data on the card is determined to be corrupted after the reset (was not yet detected by normal auditing).
- AUDIT TIMEOUT—LNP initialization audit timed out (software failure)
- DB LEVEL—Database level is not supported, or the difference exceeds incremental loading capability. This condition is caused by the reset of OAMs or if the number of updates exceeds the incremental loading capability.
- DB STATUS—Database status of the card is incoherent at the time of a reset. This condition can be caused by a failed network card update or a reset during a database update to the card.
- DB VERSION—LNP Database
version has changed from the previous version. An import, or bulk downloads
(
chg-db), or changes from release to release may alter the database version. - HW ERROR—Hardware error bit checks on the card failed during card initialization
- NO AUDIT—Unable to perform an LNP audit. The LNP audit is not on (for example, LNP options has audit=off). This condition can occur if the rate of LNP updates exceeds the ability of the LNP audit to compute checksums (excessive unknown checksums). This condition is more likely on a small database where there are fewer checksums. The percentage of known checksums must be 99% or more. The percentage is based on the number of checksums in use, which is smaller for small databases (such as two million TNs or fewer).
- POWER ON—A power on reset (the card is pulled and reinserted)
- UNKNOWN/OTHER—Unknown or other type of software failure.
- USER REQUEST—User-initiated
init-cardorinit-syscommand reload type=cold. The default restart type for these commands is a cold or full LNP data reload. The user must specify data=persist for a warm restart on command. - XILINX VERSION—The M256 Xilinx program version has changed from the previous version.
- The following conditions require a cold restart for
the MCPM card:
- DB STATUS—Database status of the card is incoherent at the time of a reset. This condition can be caused by a failed network card update or a reset during a database update to the card.
- MEAS DB–Measurements database initialization failure or corruption.
- POWER ON—A power on reset (card is pulled and reinserted).
- UNKNOWN/OTHER—Unknown or other type of software failure.
- XILINX VERSION—D1G Xilinx program version has changed from previous version.
- The following conditions require a cold restart for
the GTT-enabled IPSG card:
- GTT DB LEVEL— GTT Database level is incoherent at the time of reset. This condition is caused by the reset of OAMs.
- GTT DB STATUS— GTT Database status of the card is incoherent at the time of a reset. This condition can be caused by a failed network card update or a reset during a database update to the card.
- POWER ON— A power on reset (the card is pulled and reinserted)
- UNKNOWN/OTHER— Unknown or other type of software failure.
- USER REQUEST— User-initiated init-card or init-sys command reload type=cold. The default restart type for these commands is a cold or full GTT data reload. The user must specify data=persist for a warm restart on command.
- XILINX VERSION— The SLIC Xilinx program version has changed from the previous version.
Caution:
This command can be used to enable Measurements Platform measurements collection after the collection function has been disabled with theinh-card command for ALL MCPM cards in
the system. To enable collection, at least 1 MCPM card must be allowed in the
system. Disabling collection by inhibiting all MCPM cards CAN RESULT IN LOSING
ALL PAST MEASUREMENT DATA ON THE CARDS.
When the OA&M IP Security feature is turned on, and an IPSM card is inserted and initialized for the first time or is removed, inserted, and initialized again, the "SSH Host Keys Regenerated" UIM is displayed. The UIM shows the generated SSH Host Key fingerprint that must be provided at the secure client in order for secure information transfer to occur. The SSH Host Key fingerprint is changed whenever power is lost and restored to an IPSM card.
rlghncxa03 03-07-11 07:05:00 EST EAGLE 30.2.0
0021.1493 CARD 1111 INFO SSH Host Keys Regenerated
84 7c 92 8b c 7c ds 19 1c 6 4b de 5c 8f c5 4d
Report Date:03-07-11 Time:22:27:36
; When the OA&M IP Security feature is turned on, and an IPSM card is restarted with this command, the "SSH Host Keys Loaded" UIM is displayed. The UIM shows the current SSH Host Key fingerprint. The SSH Host Key fingerprint is not changed if the IPSM card does not lose power.
rlghncxa03 03-07-11 07:05:00 EST EAGLE 30.2.0
0021.1493 CARD 1111 INFO SSH Host Keys Regenerated
DSA Server Host Key FTRA-formatted Fingerprint=
84 7c 92 8b c 7c ds 19 1c 6 4b de 5c 8f c5 4d
Report Date:03-07-11 Time:22:27:36
;If a location for an E5-E1T1-B (type LIME1 or LIMT1), or E5-ATM-B (type LIMATM or LIME1ATM) card is specified, then at least one signaling link must be provisioned for the card before it can be allowed.
When SLOC and ELOC are given in the
alw-card command, along with DATA and
PERDATA parameters, instead of displaying an MTT, a list of card locations will
be displayed pointing out the cards on which data was persisted and the cards
on which it wasn't.
Output
alw-card:loc=2301:code=trial
rlghncxa03w 06-06-01 11:11:28 EST EAGLE 35.0.0
Card has been allowed.
;
alw-card:sloc=1103:eloc=1106:data=persist:perdata=all
tekelecstp 16-09-08 17:58:00 EST EAGLE 46.5.0.0.0-70.4.0
Card 1103 – 1106 have been allowed.
LOC 1103 : ALLOW OPERATION COMPLETED.
LOC 1104 : ALLOW OPERATION COMPLETED: Data not persisted.
LOC 1105 : ALLOW OPERATION COMPLETED.
LOC 1106 : ALLOW OPERATION COMPLETED.
alw-imt
Use this command to change the state of the specified Interprocessor Message Transport (IMT) bus from OOS-MT-DSBLD (Out-of-Service-Maintenance-Disabled) to IS-NR (In-Service-Normal), if the command is successful. If the command fails, the status is IS-ANR (In-Service-Abnormal). The IMT bus is comprised of two 125 Mbps counter-rotating serial busses. If one bus fails, the other immediately assumes control of all messages.
Example
alw-imt:bus=a
Dependencies
This command cannot be entered during an IMT Fault Isolation Test or an Extended Bit Error Rate Test (BERT).
This command cannot be entered if an IMT Rate Change sequence is in progress.
Valid IMT bus entries are "A" or "B".
Notes
This command returns an inhibited IMT bus to service.
The function of this command is the same as the rst-imt command.
See the tst-imt command to determine the location of faults on a failed or abnormal IMT bus.
Output
alw-imt:bus=a
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
Allow IMT Bus A command issued.
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
0100.0097 IMT BUS A Imt allowed
;
alw-map-ss
Use this command to activate a subsystem and bring it online. The AIQ, ATINPQ, EIR, INP, INPQS, LNP, LNPQS, and V-Flex subsystems can be allowed and inhibited.
Example
alw-map-ss:ssn=10
Dependencies
No other action command can be in progress when this command is entered.
The system must be configured with at least one Service Module card running the VSCCP application.
The EIR, INP, LNP, or V-Flex feature must be turned on, or the ANSI41 AIQ or ATINPQ feature must be enabled before this command can be entered.
The value specified for the ssn parameter must be the AIQ, ATINPQ, EIR, INP, LNP or V-Flex subsystem number.
The LNP subsystem must be online before the LNPQ subsystem number can be specified as a value for the ssn parameter.
The V-Flex subsystem must be online before the V-Flex subsystem number can be specified as a value for the ssn parameter.
The ATINPQ subsystem must be online before the ATINPQ subsystem number can be specified as a value for the ssn parameter.
The INP subsystem must be online before the INP subsystem number can be specified as a value for the ssn parameter.
The EIR subsystem must be online before the EIR subsystem number can be specified as a value for the ssn parameter.
The AIQ subsystem must be online before the AIQ subsystem number can be specified as a value for the ssn parameter.
Notes
None
Output
alw-map-ss:ssn=11
integrat40 00-05-24 10:37:22 EST EAGLE5 31.0.0
Allow map subsystem command sent to all SCCP cards.
Command Completed.
;
alw-slk
Use this command to return an inhibited signaling link to service. If the link was aligned when it was inhibited, a changeover occurred. This command causes a changeback on the specified link. MSUs are transmitted on the link after the changeback is issued.
Note:
The signaling link’s inhibited status is not preserved across a card reboot.Parameters
- link (mandatory)
- The signaling link defined on the card specified in the loc parameter. The links can be specified in any sequence or pattern.
- Synonym:
- port
- Range:
- a, b, a1 - a63, b1 - b63
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have a location specified by the loc parameter.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
alw-slk:loc=1301:link=b
Dependencies
A card location that is valid and defined in the database must be specified.
No other action command can be in progress when this command is entered.
The card must contain signaling links.
The signaling link must be equipped in the database.
This command is not valid for cards running the IPGHC GPL.
The card that contains the specified signaling link must be equipped in the specified card location.
The card in the specified card location cannot be a MUX card or the cards running the OAM application.
If IPSG-M3UA signaling links are used, then this command cannot be entered.
An appropriate value must be specified for the link parameter when an ATM card is used:
- a-a1, b—E5-ATM-B card running the ATMANSI or ATMITU application
This command is not valid for IPSG-M3UA signaling links.
Notes
The function of this command is the same as the unhb-slk command.
Not every card location represents a signaling link. Be sure to address a signaling link in this command.
The Installation Guide provides an illustration of card locations.
Output
alw-slk:loc=1301:link=b
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Allow Link message sent to card
;
alw-trm
Use this command to return the specified serial port to the state IS‑NR (in‑service normal) from the state OOS-MT-DSBLD (out-of-service maintenance-disabled) if the command is successful. If the command is not successful, the terminal’s state is OOS-MT (out-of-service maintenance).
Parameters
Example
alw-trm:trm=5
Dependencies
No other action command can be in progress when this command is entered.
The IP User Interface feature must be enabled before terminal ports 17 through 40 can be specified in the trm parameter.
The terminal specified by the trm parameter must be equipped.
If a SEAS terminal is configured, then the IP address for the associated IPSM card must be specified before this command can be entered.
The SEAS Over IP feature must be turned on before a SEAS terminal can be specified.
The specified SEAS terminal cannot be auto-inhibited.
If a critical thermal alarm is raised against the IPSM card hosting the terminal, then the specified Telnet terminal cannot be returned to the IS-NR state.
The terminal specified by the trm parameter cannot be configured as type=none (see the chg-trm command).
Notes
The function of this command is the same as the rst-trm command.
When you attempt to return to service a terminal that is already in service, a warning message is echoed to the scroll area but no action is taken.
If a SEAS terminal is configured, then the corresponding card must be an IPSM card, and the SEAS Over IP feature must be turned on before the SEAS terminal is allowed. The SEAS terminal is auto-inhibited if the IP Address for the corresponding card is invalid.
Output
alw-trm:trm=12
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
Allow message sent to terminal
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
1062.0046 TERMINAL 12 Terminal Enabled
;
aud-data
Use this command to perform a data audit, which is used to determine the integrity of the static and dynamic databases. This command can also be used to perform a separate GPL audit.
Parameters
- ddbqp (optional)
- DDB quiet period. The minimum DDB idle time, in milliseconds, during which no DDB updates are applied. After the quiet period, it is assumed that all DDB updates in the system have been processed, and no outstanding in-flight multi-cast updates exist.
If the idle period that is reported by the network card is less than the quiet period, then additional network responses are discarded, and the DDB audit process restarts. Up to three retries of the DDB audit process are performed by system. If all of the retry efforts fail, then the system status of the DDB audit report is marked as ABORTED.
- display (optional)
- This parameter specifies whether a brief or full display is provided for the audit.
This parameter applies to static and dynamic STP databases.
- Range:
-
- all
- For the static database, displays the checksum values, in hexadecimal, and details for each GPL and each subset of the current and backup database. For the dynamic database, displays the checksum values, in hexadecimal, for each dynamic database table on MTP cards.
- brief
- For the static database, displays the data collections for the current database, the backup database on the fixed disk, and the approved and trial GPLs. For the dynamic database, displays the system status with number of cards responded with or without checksum, the list of inconsistent cards, list of non-responding cards, number of cards not meeting quiet period requirement, number of cards responded with "DDB update in progess", and active MTP cards in system.
- except
- For GPLs or database subsets with problems, displays the same information as display=all
- Default:
- brief
Example
aud-data:type=ddb:display=brief
aud-data:type=ddb:ddbqp=1000
aud-data:display=except
aud-data:tblid=127
aud-data:gplqp=3
Dependencies
Only one aud-data command can be in progress at a time.
If the type=ddb parameter is specified, then the except parameter cannot be specified.
If the ddbqp parameter is specified, then the type=ddb parameter must be specified.
If the gplqp parameter is specified, then the tblid, ddbqp, and type=ddb parameters cannot be specified.
The display and tblid parameters cannot be specified together in the command.
The DMS table specified by the tblid parameter must already exist.
If the system is in upgrade mode, then this command cannot be entered.
Notes
Static Audit
The standby OAM must be available when the aud-data command for audit begins so that the standby OAM can receive the signal to begin auditing. If the standby OAM is not available when aud-data is issued, then the following messages are issued:
Extended Processing Time Required
Standby MASP is (or was) not available at audit start.
The above messages may also appear if the standby OAM is not available when the hourly periodic audit, which uses the aud-data command, automatically starts. The standby OAM is not performing any data auditing, so no audit results for the standby OAM are displayed in the audit report. Instead, the standby’s audit results are as follows:
No information currently available
If an auditing cycle completes on either the active or standby OAM and does not produce the full set of expected results (checksums), the following message appears:
Audit results may be incomplete
The audit results may be missing some of the checksums that would normally be displayed (display=all or display=except). The results may also contain summary status information (display=brief) that might have been calculated differently had some of the missing checksums been available. This condition can be caused if the audit results for the backup database are missing, probably because a backup database has not been created.
If the "Audit results may be incomplete" message appears in the audit report, perform the following procedure:
Audit Data
- Ensure that the standby OAM is online and ready.
- Ensure that a backup database has been created. Use
rept-stat-dbcommand to check whether a backup database has been created.If no backup has ever been created, the output of
rept-stat-dbcommand shows the fixed disk backup (FD BKUP) database at level 1. There will be no information under the heading "Time Last Backup." - If necessary, create a backup on the fixed disk by entering the following command:
chg-db:action=backup:dest=fixed. - Re-enter the
aud-datacommand.
If the standby OAM does not run a audit cycle and no audit information is available, the following message appears:
Audit results are not available
This condition is probably caused by the standby OAM rebooting while a audit cycle is underway. If this message appears, ensure that the standby OAM is available and re-enter the aud-data command. Ensure that the standby OAM remains up (is not rebooted) for the duration of the audit cycle.
Dynamic Audit
The aud-data command is enhanced to allow a Dynamic data audit to be triggered manually.
If a dynamic background audit is already running, and the aud-data command is issued for a dynamic audit, then the following message appears.
Periodic dynamic database audit is running with default quiet period.
Results will be displayed on completion.
The Standby OAM is not required for a dynamic audit.
Output
This example shows output for a full display of a fixed database audit:
aud-data:display=all
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3)
CARD LOC DATA STATUS NEW CS OLD CS REF CS
TDM-ACTV 1114 CRNT MTP SUBSET OK H'ffaf H'ffaf H'ffaf
CRNT GTT SUBSET OK H'5864 H'5864 H'5864
CRNT GWS SUBSET OK H'd089 H'd089 H'd089
CRNT MISC SUBSET OK H'2735 H'2735 H'2735
CRNT DBMM SUBSET OK H'1001 H'1001 H'1001
BKUP MTP SUBSET OK H'2b85 H'2b85 H'2b85
BKUP GTT SUBSET OK H'5864 H'5864 H'5864
BKUP GWS SUBSET OK H'd089 H'd089 H'd089
BKUP MISC SUBSET OK H'5af1 H'5af1 H'5af1
BKUP DBMM SUBSET OK H'1001 H'1001 H'1001
APPR ATMANSI GPL OK H'1372 H'1372 H'1372
TRI ATMANSI GPL OK H'1372 H'1372 H'1372
APPR VSCCP GPL OK H'9251 H'9251 H'9251
TRI VSCCP GPL OK H'9251 H'9251 H'9251
APPR GLS GPL OK H'8887 H'8887 H'8887
TRI GLS GPL OK H'8887 H'8887 H'8887
APPR UTILITY GPL OK H'18de H'18de H'18de
TRI UTILITY GPL OK H'18de H'18de H'18de
APPR OK H'b6c6 H'b6c6 H'b6c6
TRI OK H'b6c6 H'b6c6 H'b6c6
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3)
CARD LOC DATA STATUS NEW CS OLD CS REF CS
TDM-STDBY 1116 CRNT MTP SUBSET OK H'ffaf H'ffaf H'ffaf
CRNT GTT SUBSET OK H'5864 H'5864 H'5864
CRNT GWS SUBSET OK H'd089 H'd089 H'd089
CRNT MISC SUBSET OK H'2735 H'2735 H'2735
CRNT DBMM SUBSET OK H'1001 H'1001 H'1001
BKUP MTP SUBSET OK H'2b85 H'2b85 H'2b85
BKUP GTT SUBSET OK H'5864 H'5864 H'5864
BKUP GWS SUBSET OK H'd089 H'd089 H'd089
BKUP MISC SUBSET OK H'5af1 H'5af1 H'5af1
BKUP DBMM SUBSET OK H'1001 H'1001 H'1001
APPR ATMANSI GPL OK H'1372 H'1372 H'1372
TRI ATMANSI GPL OK H'1372 H'1372 H'1372
APPR VSCCP GPL OK H'9251 H'9251 H'9251
TRI VSCCP GPL OK H'9251 H'9251 H'9251
APPR GLS GPL OK H'8887 H'8887 H'8887
TRI GLS GPL OK H'8887 H'8887 H'8887
APPR UTILITY GPL OK H'18de H'18de H'18de
TRI UTILITY GPL OK H'18de H'18de H'18de
APPR OK H'b6c6 H'b6c6 H'b6c6
TRI OK H'b6c6 H'b6c6 H'b6c6
;
aud-data:display=except
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
Extended Processing Time Required
Results will be displayed on completion
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3):
CARD LOC DATA STATUS NEW CS OLD CS REF CS
TDM-ACTV 1116 CRNT MTP SUBSET DIFFERENT H'aaaa H'aaaa H'cccc
CRNT GTT SUBSET CORRUPTED H'aaaa H'bbbb H'aaaa
APPR MCM GPL CORRUPTED H'4321 H'3456 H'4321
APPR GLS GPL CORRUPTED H'4321 H'3456 H'4321
APPR VSCCP GPL CORRUPTED H'4321 H'3456 H'4321
rlghncxa03w 09-07-07 10:39:01 EST EAGLE 41.1.0
Extended Processing Time Required
Results will be displayed on completion
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3):
CARD LOC DATA STATUS NEW CS OLD CS REF CS
TDM-STDBY 1114 CRNT MTP SUBSET DIFFERENT H'aaaa H'aaaa H'cccc
CRNT GTT SUBSET CORRUPTED H'aaaa H'bbbb H'aaaa
APPR MCM GPL CORRUPTED H'4321 H'3456 H'4321
APPR GLS GPL CORRUPTED H'4321 H'3456 H'4321
APPR VSCCP GPL CORRUPTED H'4321 H'3456 H'4321
;
This example shows output for a brief display of a fixed database audit:
aud-data or aud-data:display=brief
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3):
CARD LOC DATA STATUS
TDM-ACTV 1114 CRNT DB OK
BKUP DB OK
GPLS OK
rlghncxa03w 09-07-07 10:39:04 EST EAGLE 41.1.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3):
CARD LOC DATA STATUS
TDM-STDBY 1116 CRNT DB OK
BKUP DB OK
GPLS OK
;
This example shows output for a full dynamic database audit:
aud-data:type=ddb:display=all
tekelecstp 09/07/21 17:04:47 GMT EAGLE 41.1.0
DDB AUDIT REPORT
SYSTEM STATUS : INCONSISTENT
ACTIVE MTP CARDS : 21
NON RESPONDING CARDS : 7: 1207 1208 1211 1212 2108 2111 2112
RESPONDING CARDS : 14
CARDS WITH NO DATA : 2
CARDS WITH DATA : 12
CARDS FAILING QUIET PRD : 0
CARDS WITH DDB UPD IN PRG : 3
CARDS CONSIDERED FOR CKSM : 9
INCONSISTENT CARDS : 2: 1203 2103
CONSISTENT CARDS : 7
AUDIT START TIME : 21/07/2009 17:04:46
QUIET PERIOD : 600 ms
RTE LINK SET LINK CM CARD CM CLSTR MATED APPL MTP GLOBLS
LOC STATUS CAUSE IDLE DDB UPD ADDN'L STATUS
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1201 CONSISTENT 700 1000
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1202 CONSISTENT 700 1000
H'000007d0 H'000007d0 H'000007d0 H'000007d0 H'000007d0 H'000007d0 H'000007d0
1203 INCONSISTENT 700 1000
---------- ---------- ---------- ---------- ---------- ---------- ----------
1204 NODATA (DDB INIT) ---------- ----------
H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8
1205 IN UPDATE 1 (TSRC,DDB) 700 1000 (IGNORED)
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1206 CONSISTENT 700 1000
---------- ---------- ---------- ---------- ---------- ---------- ----------
1207 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1208 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1211 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1212 NORESP ---------- ----------
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1213 CONSISTENT 700 1000
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 ---------- H'000003e8
2101 CONSISTENT 700 1000
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 ---------- H'000003e8
2102 CONSISTENT 700 1000
H'000007d0 H'000007d0 H'000007d0 H'000007d0 H'000007d0 ---------- H'000007d0
2103 INCONSISTENT 700 1000 (WWA UPD=2)
---------- ---------- ---------- ---------- ---------- ---------- ----------
2104 NODATA (DDL XLOAD) ---------- ----------
H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 ---------- H'00000bb8
2105 IN UPDATE 2 (DDB) 700 1000 (IGNORED)
H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 H'00000bb8 ---------- H'00000bb8
2106 IN UPDATE 2 (TSRC,DDB) 700 1000 (IGNORED)
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 ---------- H'000003e8
2107 CONSISTENT 700 1000
---------- ---------- ---------- ---------- ---------- ---------- ----------
2108 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2111 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2112 NORESP ---------- ----------
;
This example shows output for a brief dynamic database audit:
aud-data:type=ddb:display=brief
tekelecstp 09-07-15 07:34:13 GMT EAGLE 41.1.0
DDB AUDIT REPORT
SYSTEM STATUS : OK
ACTIVE MTP CARDS : 10
NON RESPONDING CARDS : 0
RESPONDING CARDS : 10
CARDS WITH NO DATA : 0
CARDS WITH DATA : 10
CARDS FAILING QUIET PRD : 0
CARDS WITH DDB UPD IN PRG : 0
CARDS CONSIDERED FOR CKSM : 10
INCONSISTENT CARDS : 0
CONSISTENT CARDS : 0
AUDIT START TIME : 15/07/2009 07:34:12
QUIET PERIOD : 20 ms
;
aud-data:tblid=127
audit 09-08-12 15:49:28 EST EAGLE 41.1.0
Extended processing time required.
Results will be displayed on completion.
;
audit 09-08-12 15:50:08 EST EAGLE 41.1.0
CARD LOC TABLE ID STATUS NEW CS OLD CS REF CS
TDM-ACTV 1114 127 OK H'cb03 H'cb03 H'cb03
;
TABLE mtt.tbl AUDIT COMPLETE:
CARD LOC TABLE ID STATUS NEW CS OLD CS REF CS
TDM-STDBY 1116 127 OK H'cb03 H'cb03 H'cb03
This example shows output for a full DDB audit when the status is ABORTED. Cards marked ("?") reported correct replies but their status was not evaluted.
aud-data:type=ddb:display=all:ddbqp=600
tekelecstp 09-07-21 21:07:57 GMT EAGLE 41.1.0
DDB AUDIT REPORT
SYSTEM STATUS : ABORTED
ACTIVE MTP CARDS : 21
NON RESPONDING CARDS : 18: 1207 1208 1211 1212 2108 2111 2112 2113
RESPONDING CARDS : 3
CARDS WITH NO DATA : 0
CARDS WITH DATA : 3
CARDS FAILING QUIET PRD : 1
CARDS WITH DDB UPD IN PRG : 1
CARDS CONSIDERED FOR CKSM : 0
INCONSISTENT CARDS : 0
CONSISTENT CARDS : 0
AUDIT START TIME : 21/07/2009 21:07:54
QUIET PERIOD : 600 ms
RTE LINK SET LINK CM CARD CM CLSTR MATED APPL MTP GLOBLS
LOC STATUS CAUSE IDLE DDB UPD ADDN'L STATUS
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1201 NQUIET 100 1000
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1202 IN UPDATE 1 (DDB) 700 1000
H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8 H'000003e8
1203 ? 700 1000
---------- ---------- ---------- ---------- ---------- ---------- ----------
1204 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1205 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1206 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1207 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1208 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1211 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1212 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
1213 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2101 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2102 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2103 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2104 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2105 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2106 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2107 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2108 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2111 NORESP ---------- ----------
---------- ---------- ---------- ---------- ---------- ---------- ----------
2112 NORESP ---------- ----------
;
aud-data:display=alltekelecstp 16-08-25 10:39:04 EST EAGLE 46.5.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3)
CARD LOC DATA STATUS NEW CS OLD CS REF CS
TDM-ACTV 1114 CRNT MTP SUBSET OK H'ffaf H'ffaf H'ffaf
CRNT GTT SUBSET OK H'5864 H'5864 H'5864
CRNT GWS SUBSET OK H'd089 H'd089 H'd089
CRNT MISC SUBSET OK H'2735 H'2735 H'2735
CRNT DBMM SUBSET OK H'1001 H'1001 H'1001
BKUP MTP SUBSET OK H'2b85 H'2b85 H'2b85
BKUP GTT SUBSET OK H'5864 H'5864 H'5864
BKUP GWS SUBSET OK H'd089 H'd089 H'd089
BKUP MISC SUBSET OK H'5af1 H'5af1 H'5af1
BKUP DBMM SUBSET OK H'1001 H'1001 H'1001
APPR ATMANSI GPL OK H'1372 H'1372 H'1372
TRI ATMANSI GPL OK H'1372 H'1372 H'1372
APPR VSCCP GPL OK H'9251 H'9251 H'9251
TRI VSCCP GPL OK H'9251 H'9251 H'9251
APPR IPSG32 GPL OK H'4261 H'4261 H'4261
TRI IPSG32 GPL OK H'4261 H'4261 H'4261
APPR GLS GPL OK H'8887 H'8887 H'8887
TRI GLS GPL OK H'8887 H'8887 H'8887
APPR UTILITY GPL OK H'18de H'18de H'18de
TRI UTILITY GPL OK H'18de H'18de H'18de
APPR OK H'b6c6 H'b6c6 H'b6c6
TRI OK H'b6c6 H'b6c6 H'b6c6
tekelecstp 16-08-25 10:39:04 EST EAGLE 46.5.0
DATA AUDIT COMPLETE (GPL AUD Quiet Period set to 3)
CARD LOC DATA STATUS NEW CS OLD CS REF CS
TDM-STDBY 1116 CRNT MTP SUBSET OK H'ffaf H'ffaf H'ffaf
CRNT GTT SUBSET OK H'5864 H'5864 H'5864
CRNT GWS SUBSET OK H'd089 H'd089 H'd089
CRNT MISC SUBSET OK H'2735 H'2735 H'2735
CRNT DBMM SUBSET OK H'1001 H'1001 H'1001
BKUP MTP SUBSET OK H'2b85 H'2b85 H'2b85
BKUP GTT SUBSET OK H'5864 H'5864 H'5864
BKUP GWS SUBSET OK H'd089 H'd089 H'd089
BKUP MISC SUBSET OK H'5af1 H'5af1 H'5af1
BKUP DBMM SUBSET OK H'1001 H'1001 H'1001
APPR ATMANSI GPL OK H'1372 H'1372 H'1372
TRI ATMANSI GPL OK H'1372 H'1372 H'1372
APPR VSCCP GPL OK H'9251 H'9251 H'9251
TRI VSCCP GPL OK H'9251 H'9251 H'9251
APPR IPSG32 GPL OK H'4261 H'4261 H'4261
TRI IPSG32 GPL OK H'4261 H'4261 H'4261
APPR GLS GPL OK H'8887 H'8887 H'8887
TRI GLS GPL OK H'8887 H'8887 H'8887
APPR UTILITY GPL OK H'18de H'18de H'18de
TRI UTILITY GPL OK H'18de H'18de H'18de
APPR OK H'b6c6 H'b6c6 H'b6c6
TRI OK H'b6c6 H'b6c6 H'b6c6
;
Legend
Fixed Audit
- CARD—Card type
- LOC—Card location
- DATA—Type of data being audited:
- APPR—Approved GPL
- BKUP—Database in the backup partition
- CRNT—Database in the current partition
- DBMM—Database management mechanism database
- GLS—GLS GPL
- GTT—Global title translation database
- GWS—Gateway screening database
- MISC—Miscellaneous system configuration database
- MTP—Message transfer part database (links, linksets, routing tables)
- VSCCP—VSCCP GPL
- IPSG32— IPSG32 GPL (GPL to be loaded on SLIC cards to run IPSG application with GTT functionality or without it)
- ATMANSI—ATMANSI GPL
- SUBSET orGPL—Indicates whether the data is a part of the database or a generic program load.
- TRI—Trial GPL
- STATUS—Status of the database or GPL:
- CORRUPTED—The database or GPL has been changed by some abnormal process. The GPL cannot be used.
- DIFFERENT—The database or GPL contains information that is not consistent with the reference database or GPL
- OK—The database or GPL is not corrupted and contains the same information as the reference database or GPL
- NEW CS—New checksum value calculated by this command
- OLD CS—Checksum value stored in the database or GPL
- REF CS—Reference checksum value stored on the active MASP
Dynamic DDB Audit
- SYSTEM STATUS:
- OK—DDB is consistent on all active MTP cards or no active MTP card is present in system
- INCONSISTENT—DDB is inconsistent
- UNKNOWN—"All active MTP cards in the system responded without the checksum of DDB table" or "No active MTP card in the system responded to audit request"
- ABORTED—"Checksums collected failed to meet the quiet period requirement" or "Number of cards responded with "DDB update in progess" greater than 25% number of cards responded with data"
- ACTIVE MTP CARDS—Number of active MTP cards
- NON RESPONDING CARDS—Number of non-responding cards
- RESPONDING CARDS—Number of responding cards
- CARDS WITH NO DATA—Cards sending replies without the checksum of dynamic tables, due to incomplete DDL crossload or DDB initialization
- CARDS WITH DATA—Cards sending replies with checksums
- CARDS FAILING QUIET PRD—Cards failing quiet time requirement
- CARDS WITH DDB UPD IN PRG—Cards sending replies marked as "DDB update in progess" due to DDB checksum not evaluated completely or TSRC task is incomplete
- CARDS CONSIDERED FOR CKSM—Cards sending correct replies. Replies are not marked with "DDB update in progess" or "Reply with no data".
- INCONSISTENT CARDS—Cards that are inconsistent
- CONSISTENT CARDS—Cards that are consistent
- AUDIT START TIME—Time that the audit started (DD/MM/YYYYY hh:ms:ss format)
- QUIET PERIOD—Minimum DDB idle time, in milliseconds, during which no DDB updates are applied
- RTE—Checksum of RTE Table
- LINK SET—Checksum of Link Set Table
- LINK—Checksum of Link Table
- CM CARD—Checksum of CM Card
- CM CLSTR—Checksum of CM Cluster
- MATED APPL—Checksum of Mated Application
- MTP GLOBLS—Checksum of MTP Globals Table
- IDLE (PERIOD)—Time elapsed, in milliseconds, since the last DDB update was received by this card
- DDB UPD—Total DDB updates received on the card
- ADDN'L STATUS—Display more information for the card, including WWA updates or whether card is considered for audit calculations
- CAUSE—Display the reason for sending replies of type "reply with no data " or "DDB update in progress". This value can be DDL (crossload not completed), DDB (dynamic database is not initialised), (TSRC, DDB) (TSRC task is not completed) or DDB (checksums still needs to apply on tables).
- ?—Card status is not evaluated (inconsistent/consistent) if the system status is marked as "ABORTED"
- IGNORED—Card responded with "DDB update in progess" and is not considered for calculating system status
- WWA UPD—Number of entries that were updated by the WWA
blk-slk
Use this command to force a local processor outage (LPO) on the specified link. The system begins sending link status signal units (LSSU) with status of processor outage (SIPO) to the adjacent signaling point.
Caution:
Maintenance personnel should use this command only to block MSUs from being sent to the system. Level 2 status remains in service, except when the link is an ATM high-speed signaling link.Note:
The signaling link’s blocked status is not preserved across a card reboot.Parameters
- link (mandatory)
- The signaling link defined on the card specified in the loc parameter. The links can be specified in any sequence or pattern.
- Synonym:
- port
- Range:
- a, b, a1 - a63, b1 - b63
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have a location specified by the loc parameter.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
blk-slk:loc=2311:link=a
Dependencies
A card location that is valid and defined in the database must be specified.
No other action command can be in progress when this command is entered.
The card must contain signaling links.
The signaling link must be equipped in the database.
The card that contains the specified signaling link must be equipped in the specified card location.
The card in the specified card location cannot be a MUX card or the cards running the OAM application.
This command is not valid for links belonging to proxy linksets.
This command is not valid for cards running IPGHC links.
An appropriate value must be specified for the link parameter when an ATM card is used:
- a-a1, b—E5-ATM-B card running the ATMANSI or ATMITU application
The blk-slk command is not supported for links associated with J7 APCs.
Notes
The function of this command is the same as the act-lpo command.
This command generates a minor alarm. Refer to Maintenance Guide for information on MRNs 0201 and 0208.
If this command is followed by the init-card command, the signaling link blockage is not preserved after the init-card command completes.
Installation Guide provides an illustration of card locations.
If the blk-slk or act-lpo command is issued for an IPSG signaling link, then one of the following events occurs:
- IPSG-M2PA signaling link—MTP3 local processor outage is initiated.
- IPSG-M3UA signaling link—The link is prohibited from entering service by rejecting received AS-ACTIVE messages.
Output
blk-slk:loc=2311:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Local processor outage being set.
;
This example shows the output when no signaling link is defined for link A:
blk-slk:loc=2312:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Link is UNEQUIPPED in the database.
Local processor outage being set.
;
This example shows the output when slot 55 in the card location is not valid:
blk-slk:loc=2355:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Command Rejected: Slot ID out of range
;
blk-slk:loc=1101:port=a
tekelecstp 13-06-20 12:37:33 EST 45.0.0-64.56.0
blk-slk:loc=1101:port=a
Command entered at terminal #4.
E2810 Command Rejected: Command is not valid for ITU-N16 links.
canc-alm-trns
Use this command to return all audible alarm indications to the local office.
Parameters
This command has no parameters.
Example
canc-alm-trns
Dependencies
No other action commands can be in progress when this command is entered.
Notes
The function of this command is the same as the dact-alm-trns command.
After this command is entered, the rept-stat-alm command can be entered to verify the status of the alarms.
Output
canc-alm-trns
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
Alarms returned to Local Maintenance Center
Command Completed.
;
canc-cmd
This command halts processing and output of the copy-ext-stats, rept-imt-info, rept-stat-applsock, rept-stat-as, rept-stat-assoc, rept-stat-card, rept-stat-clk, rept-stat-dstn, rept-stat-ls, rept-stat-rte, rept-stat-slk, rept-stat-trbl, rtrv-appl-rtkey, rtrv-as, rtrv-assoc, rtrv-cmd, rtrv-dstn, rtrv-gta, rtrv-gtt, rtrv-lbp, rtrv-log, rtrv-ls, rtrv-map, rtrv-mrn, rtrv-obit, rtrv-rte, rtrv-scr-aftpc, rtrv-scr-blkdpc, rtrv-scr-blkopc, rtrv-scr-cdpa, rtrv-scr-cgpa, rtrv-scr-destfld, rtrv-scr-dpc, rtrv-scr-isup, rtrv-scr-opc, rtrv-scrset, rtrv-scr-sio, rtrv-scr-tt, rtrv-seculog, rtrv-secu-user, rtrv-slk, rtrv-tbl-capacity, rtrv-trbltx, rtrv-uaps, rtrv-vflx-cd, rtrv-vflx-rn, rtrv-vflx-vmsid, commands.
Entering this command without the trm parameter executes the command on the terminal that is running the canc-cmd command. Entering the command with the trm parameter executes the command on the terminal specified by the trm parameter.
Example
canc-cmd
canc-cmd:trm=3
Dependencies
The trm parameter cannot be specified in a canc-cmd command that is entered on the same terminal that is running the command that is to be cancelled. The terminal will return an error: system is busy.
The canc-cmd:trm= command requires the Security Administration command class for the terminal and for the user.
The canc-cmd:trm= command requires a Security Administration command class for the terminal.
Notes
The canc-cmd command (without the trm parameter) must be entered on the same terminal that is running the command to be cancelled.
If this command is entered on a terminal that is not running a command, the command completes successfully without returning an error. Likewise, if the canc-cmd:trm= command is entered and there is no command running on the specified terminal, the command completes successfully without returning an error.
When canc-cmd with no parameter is entered, a scroll area message appears to indicate that the command has been cancelled. For example:
Command aborted on terminal 2.
Some output can still appear after the above abort message if output accumulated in the output queue before the command was entered. When a command is cancelled, the cancellation should take no longer than 25 seconds to take effect.
The F9 function key provides the same function as this command without the trm parameter. On a terminal in KSR mode, pressing <CTRL>I also provides the same function.
This command and the F9 function key cannot be used for pure SEAS commands.
If this command is entered to cancel a command other than ones listed, the terminal will accept another command, but output and processing of the current command continue.
When this command is entered, a command status code of AB (command aborted) is logged in the security log as follows:
- When
canc-cmd(without the trm parameter) is entered, no entry is logged. - When
canc-cmd:trm=is entered, an entry is logged. - When
canc-cmd(without the trm parameter) is entered as a SEAS flow-thru command, an entry is logged. Thecanc-cmd:trm=command is not allowed as a SEAS flow-thru command because thecanc-cmd:trm=command belongs to the Security Administration Command Class.
For examples of the security log entries, see the rtrv-seculog command.
Output
canc-cmd
rlghncxa03w 04-07-27 17:00:36 EST EAGLE 31.6.0
canc-cmd
Command entered at terminal #2.
rlghncxa03w 04-07-27 17:00:36 EST EAGLE 31.6.0
Command aborted on terminal 2.
;
Related Topics
- copy-ext-stats
- rept-imt-info
- rept-stat-applsock
- rept-stat-as
- rept-stat-assoc
- rept-stat-card
- rept-stat-clk
- rept-stat-dstn
- rept-stat-ls
- rept-stat-rte
- rept-stat-slk
- rept-stat-trbl
- rtrv-appl-rtkey
- rtrv-as
- rtrv-assoc
- rtrv-cmd
- rtrv-dstn
- rtrv-gta
- rtrv-gtt
- rtrv-lbp
- rtrv-log
- rtrv-ls
- rtrv-map
- rtrv-mrn
- rtrv-obit
- rtrv-rte
- rtrv-scr-aftpc
- rtrv-scr-blkdpc
- rtrv-scr-blkopc
- rtrv-scr-cdpa
- rtrv-scr-cgpa
- rtrv-scr-destfld
- rtrv-scr-dpc
- rtrv-scr-isup
- rtrv-scr-opc
- rtrv-scrset
- rtrv-scr-sio
- rtrv-scr-tt
- rtrv-seculog
- rtrv-secu-user
- rtrv-slk
- rtrv-tbl-capacity
- rtrv-trbltx
- rtrv-uaps
- rtrv-vflx-cd
- rtrv-vflx-rn
- rtrv-vflx-vmsid
canc-dlk
Use this command to remove an IP data link from service. The state of the link is changed from in service normal (IS-NR) to out of service maintenance disabled (OOS-MT-DSBLD).
Parameters
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
canc-dlk:loc=1308
Dependencies
No other action command can be in progress when this command is entered.
The shelf and card must be equipped.
The card location must contain a STPLAN card.
The card location, frame, shelf, or slot must be within the allowed range.
The signaling link must be equipped in the database.
A card location that is valid and defined in the database must be specified.
Notes
None
Output
canc-dlk:loc=1308
rlghncxa03w 04-01-27 17:00:36 EST EAGLE 31.3.0
Deactivate Link message sent to card.
Command Completed.
;
canc-echo
Use this command to halt the echoing of command responses from the user’s terminal to other terminals or printers.
Parameters
Example
canc-echo
canc-echo:trm=7
Dependencies
The echo cannot be cancelled to the same terminal from which the canc-echo command is entered.
An act-echo command must be active at the specified terminal before this command can be entered to cancel the echo.
Notes
Only the echoing of command output responses can be halted by this command. To halt the printing of alarm and network messages, the chg-trm command must be used.
Output
canc-echo
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
canc-echo
Command entered at terminal #6.
Scroll Area Output echo disabled to all terminals.
;
canc-echo:trm=7
rlghncxa03w 04-01-07 11:11:28 EST EAGLE 31.3.0
canc-echo:trm=7
Command entered at terminal #6
Scroll Area Output echo disabled for terminal 7.
;
canc-lpo
Use this command to cancel a processor outage and restore the link to its previous state. LSSUs with status of processor outage are terminated, and the link begins sending MSUs.
Note:
The signaling link’s blocked status is not preserved across a card reboot.Parameters
- link (mandatory)
- The signaling link defined on the card specified in the loc parameter. The links can be specified in any sequence or pattern.
- Synonym:
- port
- Range:
- a, b, a1 - a63, b1 - b63
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have a location specified in the loc parameter.
- loc (mandatory)
- The address of the card containing the signaling link to be unblocked.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
canc-lpo:loc=2311:link=b
Dependencies
A card location must be specified that is valid and defined in the database.
No other action command can be in progress when this command is entered.
The value specified for the loc parameter must refer to one of the following cards, and the referenced card must be equipped:
- E5-E1T1-B, card running the SS7ANSI or CCS7ITU application
- E5-ATM-B card running the ATMANSI or ATMITU application
- E5-ENET-B card running the IPLIMI, or IPSG application
- SLIC card running the IPSG application
The card must contain signaling links.
The signaling link must be equipped in the database.
This command is not valid for links belonging to proxy linksets.
An appropriate value must be specified for the link parameter when an ATM card is used:
- a-a1, b—E5-ATM-B card running the ATMANSI or ATMITU application
canc-lpo command is not supported for links associated with J7 APCs.
This command is not valid for IPSG-M3UA signaling links.
Notes
The function of this command is the same as the ublk-slk command.
Unblocking a signaling link removes a Level 2 failure resulting from a blk-slk of an ATM high-speed signaling link.
Installation Guide provides an illustration of card locations.
Output
canc-lpo:loc=2311:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Local processor outage being cleared.
;
In the following example, card location 1113 is not valid:
canc-lpo:loc=1113:link=a
tekelecstp 05-01-21 17:00:36 EST EAGLE5 33.0.0
Command Rejected : Location is not valid for command
;
canc-slk
Use this command to change the state of the specified link to OOS‑MT-DSBLD (Out-Of-Service Maintenance Disabled).
Caution:
This command impacts network performance and should be used only during periods of low traffic.Parameters
- link (mandatory)
- Signaling link defined on the card specified in the loc parameter. The links can be specified in any sequence or pattern.
- Synonym:
- port
- Range:
- a, b, a1 - a63, b1 - b63
Not all card types support all link parameter values.
See Table A-1 for valid link values for each type of card that can have a location specified in the loc parameter.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
canc-slk:loc=1301:link=a
Dependencies
A card location must be specified that is valid and defined in the database.
No other action command can be in progress when this command is entered.
The card must contain signaling links.
The signaling link must be equipped in the database.
The card that contains the specified signaling link must be equipped in the specified card location.
The card in the specified card location cannot be a MUX card or the cards running the OAM application.
An appropriate value must be specified for the link parameter when an ATM card is used:
- a-a1, b—E5-ATM-B card running the ATMANSI or ATMITU application
Notes
Not every card location represents a signaling link. Be sure to address a signaling link in this command.
Installation Guide provides an illustration of card locations.
After this command is entered, the rept-stat-slk command can be entered to verify the cancellation.
Output
canc-slk:loc=1301:link=a
rlghncxa03w 05-02-07 11:11:28 EST EAGLE5 33.0.0
Deactivate Link message sent to card
;
canc-user
Use this command to end a user session.
Parameters
This command has no parameters.
Example
canc-user
Dependencies
None
Notes
The dact-echo or logout command can be used in place of this command.
Output
Not applicable.chg-acg-mic
Use this command to change the values of ACG controls assigned to certain queries. The control can apply to all queries or to specific query services and called party digits. A particular control is selected to be changed by either specifying that it is the type=all control or specifying its service and digits.
Parameters
- drtn (optional)
- Duration index. The amount of time that the ACG is in effect. This number is mapped to a time value at the LNP node.
Example
To change the type=all MIC to use 3 digits:
chg-acg-mic:type=all:nd=3
To change the MIC for AIN queries for 919-460-2132 to use an interval index of 15:
chg-acg-mic:serv=ain:dgts=9194602132:aintvl=15
To change the MIC for IN queries for 919-xxx-xxxx to use a duration index of 9 and an interval index of 5:
chg-acg-mic:serv=in:dgts=919:drtn=9:intvl=5
Dependencies
If the type=all parameter is specified, then the nd, drtn, intvl, or aintvl parameter must be specified.
If the type=all parameter is specified, then the serv and dgts parameters cannot be specified.
If the type=sd parameter is specified, then the serv and dgts parameters must be specified.
If the type=sd parameter is specified, then the nd parameter cannot be specified.
If the serv=ain parameter is specified, then the drtn or aintvl parameter must be specified.
If the serv=ain parameter is specified, then the intvl parameter cannot be specified.
If the serv=in parameter is specified, then the drtn or intvl parameter must be specified.
If the serv=in parameter is specified, then the aintvl parameter cannot be specified.
The dgts parameter value must be either 3 digits in the range 000-999 or 6-10 digits in the range 000000-9999999999.
The nd parameter value must be 3 or 6-10 to indicate the number of new digits.
The LNP feature must be turned on before this command can be entered.
If the type=all parameter is specified, then a MIC with type=all must exist.
If the type=sd parameter is specified, then a MIC with the same service and digits must exist.
Notes
None
Output
chg-acg-mic:type=all:nd=31
rlghncxa03w 04-01-28 08:50:12 EST EAGLE 31.3.0
ACG MIC table is (11 of 256) 4% full of type SD
CHG-ACG-MIC: MASP A - COMPLTD
;
chg-acg-noc
Use this command to change the definition of a node overload level. The definition is comprised of the threshold LNP query rates for node overload levels and the values for the automatic call gappings (ACG) to be sent when at the specified level.
Parameters
- and (optional)
- AIN number of digits. The number of digits in the global title address of an AIN query.
- drtn (optional)
- Duration index. The amount of time that the ACG is in effect. This number is mapped to a time value at the LNP node.
- ind (optional)
- IN number of digits. The number of digits in the global title address of an IN query.
Example
To change level 10’s query rate and AIN number of digits:
chg-acg-noc:lvl=10:qr=900000:and=6To change level 3’s duration and interval indexes:
chg-acg-noc:lvl=3:drtn=7:intvl=3Dependencies
At least one optional parameter must be specified.
The and parameter value must be either 6 or 10.
The specified overload level must be defined.
The ACG NOC table must be accessible.
The LNP feature must be turned on before this command can be entered.
The ind parameter value must be either 6 or 10.
Notes
None
Output
chg-acg-noc:lvl=10:qr=900000:and=6
rlghncxa03w 03-02-28 08:50:12 EST EAGLE 28.1.0
CHG-ACG-NOC: MASP A - COMPLTD
;
chg-ainpopts
Use this command to provision AINPQ-specific data. This command updates the AINPOPTS table.
Parameters
Note:
The nature of address indicator parameters (rnaiv or rnai) and numbering plan parameters (rnp or rnpv) can be specified using a mnemonic or an explicit value. The mnemonic and explicit values cannot be specified at the same time for the same parameter.- defrn (optional)
- Default routing number. This parameter specifies a default routing number that is used for own-network subscribers.
- lnpentpref (optional)
- LNP entity preference is the first preference for the RTDB data / entity associated with a DN to be used as LRN.
Note:
The option is applied only if SPORT is not applied and EPAP lookup results in more than one entity.
- lnpogdnnai (optional)
- LNP outgoing DN nature of address indicator. This parameter overrides the outgoing Nature of Number if DN is being returned.
- Range:
-
- inc
- Use the incoming NoN
- sub
- Subscriber
- natl
- National Significant
- intl
- International
- diglen
- If the outgoing digit length is less than or equal to LNPSUBDIGLEN then set NoN = SUBSCRIBER.
If the outgoing digit length is greater than LNPSUBDIGLEN and is less than or equal to LNPNATLDIGLEN then set NoN = NATIONAL Significant.
- Default:
- No change to the current value
- System Default:
- inc
- lnpoglrnnai (optional)
- LNP outgoing LRN nature of address indicator. This parameter overrides the outgoing Nature of Number if LRN is being returned.
- lnpsnai (optional)
- LNP service nature of address indicator. This parameter overrides the incoming Nature of Number in AIN Info_Analyzed CalledPartID.
- Range:
-
- inc
- Use the incoming NoN
- sub
- Subscriber
- natl
- National Significant
- intl
- International
- diglen
- If the incoming NoN of AIN Info_Analyzed CalledPartyID is SUBSCRIBER, then do the following, else use the incoming NoN:
If digit length of CalledPartyID = LNPSUBDIGLEN, assume the NoN is Subscriber.
If digit length of CalledPartyID = LNPNATLDIGLEN, assume the NoN is NATIONAL (SIGNIFICANT).
If digit length of CalledPartyID is not equal to LNPNATLDIGLEN or LNPSUBDIGLEN, raise an error.
- Default:
- No change to the current value
- System Default:
- inc
- lnpsport (optional)
- LNP service portability.
- rfmt (optional)
- Routing address format. This parameter specifies the routing address format that is suported in the AINPQ "Return Result" response messages.
- Range:
-
- asdrn
- ASD + RN
- asdrndn
- ASD + RN + [DIALPFX] + DN
- asdrnnecdn
- ASD + RN + [DIALPFX] + NEC + DN
- asdrnccdn
- ASD + RN + [DIALPFX] + CC + DN
- ccasdrndn
- [DIALPFX] + CC + ASD + RN + DN
- ccgrndn
- [DIALPFX] + CC + GRN + DN
- ccrngrndn
- [DIALPFX] + CC + RN + GRN + DN
- ccgrnrndn
- [DIALPFX] + CC + GRN + RN + DN
- ccrndn
- [DIALPFX] + CC + RN + DN
- ccrnasddn
- [DIALPFX] + CC + RN + ASD + DN
- homerndn
- Home Routing Number
- grn
- GRN
- grndn
- GRN + [DIALPFX] + DN
- grnrndn
- GRN + RN + [DIALPFX] + DN
- grnrn
- GRN + RN
- grnrnccdn
- GRN + RN + [DIALPFX] + CC + DN
- grnrnnecdn
- GRN + RN + [DIALPFX] + NEC + DN
- rn
- Routing Number
- rnasd
- RN + ASD
- rnasddn
- RN + ASD + [DIALPFX] + DN
- rnasdccdn
- RN + ASD + [DIALPFX] + CC + DN
- rnasdnecdn
- RN + ASD + [DIALPFX] + NEC + DN
- rndn
- RN + [DIALPFX] + DN
- rngrn
- RN + GRN
- rngrndn
- RN + GRN + [DIALPFX] + DN
- rngrnccdn
- RN + GRN + [DIALPFX] + CC + DN
- rngrnnecdn
- RN + GRN + [DIALPFX] + NEC + DN
- rnnecdn
- RN + [DIALPFX] + NEC + DN
- Default:
- No change to the current value
- System Default:
- rndn
- sporttype (optional)
- Service Portability type. This parameter specifies whether Service Portability is performed for the associated feature.
Note:
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’entity id ) is applied.The S-Port feature must be enabled before this parameter can be specified. The S-Port feature must be turned on before any change to the parameter will impact the associated feature.
Example
chg-ainpopts:rfmt=rn:rnp=e164:rnai=intl:dialpfx=fac:dltpfx=yes
chg-ainpopts:rfmt=rndn:rnp=e212:rnai=intl:dialpfx=fac:dltpfx=no :dialnai=1:snai=natl
chg-ainpopts:rfmt=rngrnccdn:rnp=e164:rnai=intl:dialpfx=fac:dltpfx=yes
chg-ainpopts:sprestype=rrwdgts:rfmt=rnnecdn:nec=abcd1
chg-ainpopts:rfmt=rnnecdn:nec=abcd1
chg-ainpopts:rfmt=rnnecdn:nec=0
chg-ainpopts:rfmt=asdrnccdn:rnp=e164:rnai=intl:dialpfx=fac:dltpfx=yes
chg-ainpopts:rfmt=rn:rnp=e164:lnpsnai=sub:lnpnatldiglen=10:lnpentpref=rn
Dependencies
At least one optional parameter must be specified.
The rnp and rnpv parameters cannot be specified together in the command.
The rnai and rnaiv parameters cannot be specified together in the command.
If the ndialpfx or dltpfx parameter is specified, then the dialpfx parameter must be specified.
The dialpfx=none parameter cannot be specified.
If the ndialpfx=none parameter is specified, then the dltpfx parameter cannot be specified.
If the ndialpfx and dialpfx parameters are specified, then the value specified for the dialpfx parameter must already exist in the AINPOPTS table.
The value specified for the ndialpfx parameter cannot already exist in the AINPOPTS table.
A maximum of 2 Dialed Party Number Nature of Address values are allowed.
The dialnai and snai parameters must be specified together in the command.
If the snai=none parameter is specified, then the value specified for the dialnai parameter must already exist in the AINPOPTS table.
The National Escape Code ( nec parameter) can contain between 1 and 5 digits. Otherwise the value is none.
A maximum of 40 Dialed Party Number Prefix values can be provisioned.
If the nec=none parameter is specified, then values of asdrnnecdn, rnasdnecdn, rnnecdn, rngrnnecdn, and grnrnnecdn cannot be specified for the rfmt parameter.
The S-Port feature must be enabled before the sporttype or lnpsport parameter can be specified.
The AINPQ feature must be enabled before this command can be entered.
The LNPSUBDIGLEN value should be less than value of LNPNATLDIGLEN.
Output
chg-ainpopts:rfmt=rnasd:nec=0
tekelecstp 09-06-03 15:15:44 EST EAGLE 41.1.0
CHG-AINPOPTS: MASP A - COMPLTD
;
chg-aiqopts
Use this command to provision AIQ specific data. This command updates the AIQOPTS table.
Parameters
- digmaxlen (optional)
- Maximum Length of Digit String. The maximum length of a digit string that is considered valid in the Digits (Dialed) field of an AnalyzedInformation query.
- digminlen (optional)
- Minimum Length of Digit String. The minimum length of a digit string that is considered valid in the Digits (Dialed) field of an AnalyzedInformation query.
- pfx (optional)
- Digit String. The digit string associated with a Trigger Type (value of trigtype parameter). The value specified for the pfx parameter is encoded in the response message.
- resfmt (optional)
- Response format. The format of outgoing routing digits in the AnalyzedInformation response message.
- respar (optional)
-
Response Digits. The TCAP field used to encode the AnalyzedInformation response message.
- tcaperr (optional)
-
TCAP Error Code. The TCAP error code used in a Return Error response.
- Range:
- 129 - 255
- 129—UnrecognizedMIN
- 130—UnrecognizedESN
- 131—MIN/HLR Mismatch
- 132—OperationSequenceProblem
- 133—ResourceShortage
- 134—OperationNotSupported
- 135—TrunkUnavailable
- 136—ParameterError
- 137—SystemFailure
- 138—UnrecognizedParameterValue
- 139—FeatureInactive
- 140—MissingParameter
- 141-239—Reserved
- 240-255—Reserved for Protocol Extension
- Default:
- No change to the current value
- System Default:
- 138
- trigtype (optional)
-
TriggerType Value. An individual trigger used to specify an association between a trigger and a corresponding address digit string (value of pfx parameter).
A maximum of 20 trigtype - pfx entries are supported. The pfx digit string corresponding to the specified Trigger Type present in the Incoming AnalyzedInfo Query is encoded in the Response message.
- Range:
- 0 - 255
Table 4-1 lists the mnemonic for each TRIGTYPE decimal value.
Example
This example specifies the provisioning of a Trigger Type – Prefix string pair:
chg-aiqopts:trigtype=2:pfx=65432This example deletes an already provisioned Trigger Type:
chg-aiqopts:trigtype=2:pfx=noneThis example specifies the digminlen-digmaxlen range (5-7):
chg-aiqopts:digminlen=5:digmaxlen=7This example provisions the response parameter and response format:
chg-aiqopts:respar=rtdigits:resfmt=pfxDependencies
The ANSI41 AIQ feature must be enabled before this command can be entered.
The AIQOPTS table is corrupt or cannot be found.
The pfx and trigtype parameters must be specified together in the command.
The value specified for the digminlen parameter must be less than or equal to the value specified for the digmaxlen parameter.
A maximum of 20 trigtype - pfx entries can be specified in the AIQOPTS table.
A pfx - trigtype pair must be specified with a supported value for the trigtype parameter before the pfx=none parameter can be specified.
Notes
If the same value is specified for the digminlen and digmaxlen parameters, then only MSUs with dialed digits of the specified length are accepted for processing.
The value of the Digits (Dialed) length must be between the values specified for the digminlen and digmaxlen parameters.
A maximum of 20 pfx - trigtype pairs can be specified.
Table 4-1 lists the decimal value and mnemonic for each TRIGTYPE parameter value.
Table 4-1 TRIGTYPE Parameter Values
| Decimal Value | Mnemonic | Decimal Value | Mnemonic |
|---|---|---|---|
|
0 |
Unspecified. |
24 |
Local_Call. |
|
1 |
All_Calls. |
25 |
Local_Toll_Call. |
|
2 |
Double_Introducing_Star. |
26 |
Non-Local_Toll_Call |
|
3 |
Single_Introducing_Star. |
27 |
World_Zone_Call. |
|
4 |
Reserved [for Home_System_Feature_ Code] |
28 |
International_Call. |
|
5 |
Double_Introducing_Pound. |
29 |
Unrecognized_Number. |
|
6 |
Single_Introducing_Pound. |
30 |
Prior_Agreement. |
|
7 |
Revertive_Call. |
31 |
Specific_called_Party_ Digit_String. |
|
8 |
0_Digit. |
32 |
Mobile_Termination. |
|
9 |
1_Digit. |
33 |
Advanced_Termination. |
|
10 |
2_Digit. |
34 |
Location. |
|
11 |
3_Digit. |
35-63 |
Reserved. Treat a reserved value the same as value 0, Unspecified. |
|
12 |
4_Digit. |
64 |
Terminating_Resource_ Available. |
|
13 |
5_Digit. |
65 |
T_Busy. |
|
14 |
6_Digit. |
66 |
T_No_Answer. |
|
15 |
7_Digit. |
67 |
T_No_Page_Response. |
|
16 |
8_Digit. |
68 |
T_Unroutable. |
|
17 |
9_Digit. |
69-219 |
Reserved. Treat a reserved value the same as value 0, Unspecified. |
|
18 |
10_Digit. |
220 |
Reserved for TDP-R DP value. |
|
19 |
11_Digit. |
221 |
Reserved for TDP-N DP value. |
|
20 |
12_Digit. |
222 |
Reserved for EDP-R DP value. |
|
21 |
13_Digit. |
223 |
Reserved for EDP-N DP value. |
|
22 |
14_Digit. |
224-255 |
Reserved for TIA-41 protocol extension. If unknown, treat the same as value 0, Unspecified. |
|
23 |
15_Digit. |
Output
chg-aiqopts:trigtype=2:pfx=65432:respar=rtdigits:tcaperr=135
tekelecstp 09-12-03 12:40:16 EST EAGLE 42.0.0
CHG-AIQOPTS: MASP A - COMPLTD
;
chg-appl-rtkey
Use this command to change static entries in the Routing Key table. Only one attribute can be changed at a time.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.Note:
See Table A-2 for valid CIC values for specified SI and MSU types.- cice (optional)
- The end range of circuit identification codes assigned to the routing key. The cice and cics parameters identify the routing key to be changed.
- cics (optional)
- The start range of circuit identification codes assigned to the routing key. The cics and cice parameters identify the routing key to be changed.
- dpc (optional)
- ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- dpci (optional)
- ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)
- dpcn (optional)
- ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- dpcn24 (optional)
- 24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- dpcn16 (optional)
- 16-bit ITU national point code with subfields unit number--sub number area--main number area (un-sna-mna).
- ncics (optional)
- The new start range of circuit identification codes assigned to the routing key. Specify the ncics and/or ncice parameter to change the range of the circuit identification codes assigned to the routing key.
- ncice (optional)
- The new end range of circuit identification codes assigned to the routing key. Specify the ncice and/or ncics parameter to change the range of the circuit identification codes assigned to the routing key.
- nrcontext (optional)
- This parameter modifies the routing context value assigned to this routing key.
Routing context is mandatory for routing keys associated with SUA Application Servers. Routing context is optional for routing keys associated with M3UA Application Servers.
An AS can be associated with only 1 routing key with routing context. An AS can be associated with multiple routing keys that do not contain routing context. An AS cannot be simultaneously assigned to a routing key with routing contexts and to routing keys without routing contexts.
- opc (optional)
- ANSI originating point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- opca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- opc/opca/opci/opcn/opcn24/opcn16 (optional)
- Originating point code. Valid only (and required) if si=4, 5, or 13.
- opci (optional)
- ITU international originating point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)
- opcn (optional)
- ITU national originating point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- opcn24 (optional)
- 24-bit ITU national originating point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- opcn16 (optional)
- 16-bit ITU national point code with subfields unit number sub number area main number area (un-sna-mna).
- rcontext (optional)
- This parameter specifies a routing key by its routing context when a routing key needs to be changed as an alternative to entering the dpc/si/ssn/opc/cics/cice/type parameters.
Split operations are invalid for routing keys with routing context.
- split (optional)
- The CIC value where the routing key with the specified CICS and CICE range will be split. The specified routing key is split into two entries with adjacent CIC ranges. The existing routing key retains the range of CICs that is lower than the split value. The value of split minus 1 is used as the end range for this entry. The range of CICs assigned to the original entry is the values of cics to split minus 1.
A new routing key entry is created with the high end of the original range. The split value is used as the start of the CIC range for this entry. The range of CICs assigned to the new entry is the values of split to cice.
This parameter is valid only if si=4, 5, or 13 and is not valid with ncics or ncice. See Table A-2 and Table 4-2.
Example
chg-appl-rtkey:dpc=123-230-245:si=5:opc=123-230-244:cics=1:cice=100:split=50
chg-appl-rtkey:dpc=123-230-245:si=5:opc=123-230-244:cics=1:cice=50:ncice=100
chg-appl-rtkey:dpcn24=10-100-10:si=5:opcn24=10-100-11:cics=1:cice=100:ncice=200
chg-appl-rtkey:dpc=8-8-8:si=3:ssn=5:rcontext=500
chg-appl-rtkey:dpci=s-3-11-1:si=5:opci=s-4-11-1:cics=1:cice=1000:ncice=500
chg-appl-rtkey:rcontext=5:ncice=100
chg-appl-rtkey:rcontext=1:nrcontext=2
chg-appl-rtkey:dpcn16=121-10-15:si=5:opcn16=121-10-15:cics=1:cice=50:ncice=100
Dependencies
Optional parameters that must be specified with the chg-appl-rtkey command depend on the type of routing key being changed. See Table 4-2 for valid parameter combinations.
For SS7IPGW and IPGWI applications running on E5-ENET-B cards, there is a limit of
2500 routing keys in the system. The srkq
parameter (see the chg-sg-opts command) limits the
maximum number of static routing keys that can be provisioned with the ent-appl-rtkey command.
The subsystem number is mandatory and valid only when the si=3 (or sccp) parameter is specified; if the si parameter does not equal 3 (or sccp), the ssn parameter cannot be specified.
The value entered for the starting circuit identification code (cics) must be less than or equal to the value entered for the ending circuit identification code (cice).
The value entered for the new starting circuit identification code (ncics) must be less than or equal to the value entered for the new ending circuit identification code (ncice).
A circuit identification code range (cics to cice) cannot be specified that overlaps an existing routing key.
When si=4, 5, or 13 (or tup, isup, or qbicc), the opc, cics, and cice parameters are required. The opc, cics, and cice parameters can be specified only if si=4, 5, or 13.
The value entered for the split parameter must be greater than the value entered for the cics parameter and less than or equal to the value entered for the cice parameter.
The value entered for the ncics parameter must be less than or equal to the value entered for the cice parameter when the ncice parameter is not specified.
The value entered for the ncice parameter must be greater than or equal to the value entered for the cics parameter when the ncics parameter is not specified.
The si parameter must have a value of 4, 5, or 13 (or tup, isup, or qbicc) before the split, ncics, and ncice parameters can be specified.
A DPC/SI routing key must be specified when the DPC is ANSI and the si=4 parameter is specified (TUP is used only in an ITU network).
Table A-2 shows valid CIC values for SI types 4, 5, and 13.
Partial point codes are not allowed; no asterisks can be specified in the point codes in the command.
Mixed point code types are not allowed; opc and dpc types must match.
If the type=partial or type=default parameter is specified, then the split and resize parameters cannot be specified.
If the type=default parameter is specified, then the dpc, si, ssn, opc, cics, and cice parameters cannot be specified.
When the type=full parameter is specified, the dpc and si parameters must be specified.
The following types of partial routing keys are supported:
- DPC-SI-OPC (ignore CIC) can be used as a partial match key for CIC- based traffic.
- DPC-SI (ignore all other fields) can be used as a partial match key for CIC- based traffic or SCCP traffic.
- DPC only (ignore all other fields) can be used as a partial match for any type of traffic.
- SI only (ignore all other fields) can be used as a partial match for any type of traffic.
If the rcontext parameter is specified, then the split, ncics and ncice parameters cannot be specified.
The rcontext parameter must be specified for routing keys that are associated with SUA Application Servers.
The specified rcontext parameter value must already exist in the database.
If specified, the service indicator parameter must be si=3 for routing keys that are associated with SUA Application Servers.
An AS cannot be simultaneously assigned to a routing key with routing contexts and routing keys without routing context. To assign an M3UA or SUA association to multiple routing keys with routing context, the M3UA/SUA association must be assigned to more than one AS, and each AS must be assigned to a routing key with routing context.
The AS name and parameters specified for a routing key must use an address format that is valid for the adapter type assigned to the AS.
The routing context value should be unique.
Table 4-2 Valid Parameter Combinations for chg-appl-rtkey Routing Key Types
| Action | dpc | si | ssn | opc | cics | cice | ncics | ncice | split | type |
|---|---|---|---|---|---|---|---|---|---|---|
|
Split CIC Range |
X |
X |
X |
X |
X |
X |
full |
|||
|
Re-size CIC Range |
X |
X |
X |
X |
X |
X |
X |
full |
||
|
Socket Name Override (SI=ISUP or 5) |
X |
X |
X |
X |
X |
full |
||||
|
Socket Name Override (SI = SCCP or 3) |
X |
X |
X |
full |
||||||
|
Socket Name Override (SI = not 3, 4, 5, or 13) |
X |
X |
full |
|||||||
|
Socket Name Override (SI = 4, 5, or 13) |
X |
X |
X |
partial |
||||||
|
Socket Name Override (SI = 3, 4, 5 or 13) |
X |
X |
partial |
|||||||
|
Socket Name Override SI-only key |
X |
partial |
||||||||
|
Socket Name Override DPC-only key |
X |
partial |
||||||||
|
Socket Name Overrride Default key |
default |
The value of the nrcontext parameter cannot be changed for a routing key if the rcontext parameter has not been configured for that routing key.
The attributes that are required to change a routing key must be specified in the command.
The maintenance data must be accessible.
J7 support feature must be enabled before the dpcn16/opcn16 parameter can be specified.
The opc, cics, and cice parameters can be specified with the si parameter only if the si parameter has a value of 4, 5, or 13 (or tup, isup, or qbicc).
Notes
A routing key entry associates a routing key with a socket name or Application Server (AS) name.
The dpc, si, ssn, opc, cics, and cice parameters are used to identify the routing key to be changed.
The split, ncics, and ncice parameters are used to specify new values for the routing key.
The opc, cics, and cice parameters are not required for partial routing keys.
The cics, cice, ncice, ncice, and split parameters are required when si=4 and ITU DPCs (dpci, dpcn) are specified. These parameters are not valid when an ANSI DPC (dpc, dpca) is specified and si=4.
The following changes can be made for routing keys. Only one of these changes is allowed per command.
- A routing key can be split into two entries with adjacent CIC ranges. The resulting entries retain the socket associations of the original entry.
- The range of CICs assigned to a routing key can be changed as long as it does not overlap another routing key. The new entry retains the socket associations of the original entry.
Group codes are required for ITU-N point codes (DPCN/OPCN) when the Duplicate Point Code feature is turned on.
Routing context is a routing key parameter that uniquely identifies routing keys. Routing context is mandatory for routing keys associated with SUA Application Servers and optional for routing keys associated with M3UA Application Servers.
An AS cannot be simultaneously assigned to a routing key with routing contexts and routing keys without routing contexts.In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).
Output
chg-appl-rtkey:dpc=123-230-245:si=3:ssn=250:nsname=socket5
rlghncxa03w 04-01-28 08:50:12 EST EAGLE 31.3.0
CHG-APPL-RTKEY: MASP A - COMPLTD
;
chg-as
Use this command to change the characteristics of an existing Application Server (AS).
Parameters
Example
chg-as:asname=asx:mode=override
Dependencies
The value specified for the asname parameter must already exist in the AS table.
Association connection parameters must be unique.
The connection state for all associations assigned to the AS must be open=no before the mode parameter can be changed.
Notes
By default, the AS recovery timer value is set to 200 ms when an AS is entered. This value can be changed at any time using the chg-as command. The new timer value will be used the next time the AS enters the AS-Pending state.
Output
chg-as:asname=asx:mode=override
rlghncxa03w 04-01-17 15:35:05 EST EAGLE 31.3.0
CHG-AS: MASP A - COMPLTD
;
chg-assoc
Use this command to configure existing SCTP associations in the IPAPSOCK table.
Parameters
- alhost (optional)
- Alternate local host name. This parameter
configures the SCTP association as a multi-homed endpoint.
- Range:
-
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Any string of characters beginning with a letter and comprising up to 60 characters in length
Valid characters are a–z, A–Z, 0–9, - (dash), . (period)
none —The alhost is not configured; the SCTP association is configured as a uni-homed endpoint.
- alw (optional)
- The parameter specifies whether the connection manager should allow or disallow the association to carry SS7 traffic.
- cwmin (optional)
- Minimum congestion window. The minimum and initial sizes, in bytes, of the association’s congestion window.
- hbtimer (optional)
- Heartbeat timer in milliseconds. The Heartbeat timer value + RTO (Retransmission Time Out) is the value of heartbeat interval at which heartbeat request should be sent.
- istrms (optional)
- SCTP Inbound Stream Value. A 16-bit unsigned integer that defines the number of streams the sender allows the peer end to create in this association.
- lhost (optional)
- Local host name. The local host name as defined in the IP Host table.
- link (optional)
-
Signaling link for the association.
- Synonym:
- port
- Range:
- a, b, a1 - a63, b1 -
b63
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling links.
- Default:
- No change to the current value
- open (optional)
- Connection state (open or closed) that the
connection manager is to put the association in when the socket is operational.
The
chg-assoccommand allows initiation of SCTP graceful shutdown on a per association basis for IPSG M3UA associations or diameter connections (maintained in the DCONN table) . Thechg-assoc:open=nocommand aborts the association and closes the diameter connection (if associated) unless graceful shutdown is provisioned (see thechg-uapscommand). If provisioned, then SCTP graceful shutdown for an association occurs after execution ofchg-assoc:open=no.
- ostrms (optional)
- SCTP Outbound Stream Value. The 16-bit unsigned integer that defines the number of streams the sender wants to create in this association.
- rhost (optional)
- Remote host. The name of the remote host as defined in the IP Host table.
- rhosttype (optional)
- Remote host type. This parameter specifies whether
the remote host is a primary or alternate remote address.
Note:
The alternate remote address is used for multi-homed remote hosts.
- rhostval (optional)
- Remote host validation. The validation mode for
the association when an SCTP INIT/INIT-ACK message is received.
- Range:
-
- match
-
accept the message if the message contains the primary remote host value and the alternate remote host value (if the alternate remote host is provisioned). If the alternate remote host is not provisioned, then accept the message if the message contains the primary remote host value. Reject the message if it contains any IP address other than that of the primary or alternate remote host.
The rules determining the use of the relaxed and match modes depend on multiple conditions, including whether an alternate remote host is provisioned. See Table 4-4 for validation rules that are used to establish an association for the relaxed and match modes.
- relaxed
- accept the message if the IP address for the primary or alternate remote host matches the IP address, source IP address, or host name in the message
- Default:
- No change to the current value
- System Default:
- relaxed
- rmax (optional)
- Maximum retransmission timeout. The maximum value of the calculated retransmission timeout in milliseconds.
- rmin (optional)
- Minimum retransmission timeout. The minimum value of the calculated retransmission timeout in milliseconds.
- rmode (optional)
- Retransmission mode. The retransmission policy
used when packet loss is detected.
- Range:
-
- lin
- The Oracle Linear Retransmission Policy where each retransmission timeout value is the same as the initial transmission timeout, and only the slow start algorithm is used for congestion control.
- rfc
- Standard RFC 2960 algorithm in the retransmission delay doubles after each retransmission. The RFC 2960 standard for congestion control is also used.
- Default:
- No change to the current value
- System Default:
- lin
- rtimes (optional)
- Maximum retransmission retries. The number of times a data retransmission will occur before closing the association.
- rtxthr (optional)
- Retransmission threshold. The value of the retransmission threshold to tune the IP Connection Excess Retransmits alarm.
- uaps (optional)
- User adapter parameter set. The set used by the M3UA, SUA or M2PA associations for various timer and parameter values including False IP Connection Congestion Timer, UA Heartbeat Period Timer, UA Heartbeat Received Timer, ASP SNM options, ASP/AS Notifications, UA Serviceability options, and Payload Protocol Indicator byte order option.
Example
chg-assoc:aname=a1:lhost=gw105.nc.tekelec.com:lport=1030: rhost=gw100.nc.tekelec.com:rport=1030:open=yes:alw=yes:uaps=10
chg-assoc:aname=m3ua03:rtxthr=65535
chg-assoc:aname=a1:lhost=tek1.com:lport=1030:rport=1030:rhost=tek2.com: rhostval=match:rhosttype=primary
chg-assoc:aname=a1:rhost=tek.com:rhostval=relaxed:rhosttype=alternate
chg-assoc:aname=assoc1:adapter=diam
chg-assoc:aname=a1:hbtimer=1000
Dependencies
At least one optional parameter must be specified.
The value specified for the aname parameter must already exist in the IPAPSOCK table.
An association’s connection parameters (lhost, rhost, lport, rport) must be unique.
The connection state must be open=no to change the lhost, rhost, lport, rport, port, alhost, adapter, m2patset, istrms, ostrms, rmode, rmin, rmax, rtimes, cwmin, bufsize, and hbtimer parameters.
The lhost, lport, rhost, and rport parameters must be specified before the open=yes parameter can be specified. The aname parameter and at least one other optional parameter must be specified before the open=no parameter can be specified.
The value of the uaps parameter can be changed for an association if the open=yes parameter is specified.
The hostnames specified in the lhost and alhost parameters must refer to different IP addresses.
The hostnames specified in the lhost and alhost parameters must refer to IP addresses on the same IP card.
If the LHOST is defined on Port A its ALHOST must be on PORT B.
If the LHOST is defined on Port B its ALHOST must be on PORT A.
If the LHOST is defined on Port C, its ALHOST must be PORT D.
An association with an SUA or M3UA adapter cannot be specified as a local host on a card running the IPLIMI application.
An association with an M2PA adapter cannot be specified as a local host on a card running the SS7IPGW or IPGWI application.
An association with an SUA adapter cannot be specified as the local host on a card running the IPSG application.
The local host must have a signaling link assigned to its associated signaling link port before the open=yes parameter can be specified.
An association’s lhost and alhost cannot be assigned to the cards Ethernet interface.
The LHOST cannot be PORT D.
The ALHOST cannot be PORT C.
The adapter layer cannot be changed for an association that is already associated with an Application Server (AS).
Before the local host can be changed, the new local host must have a signaling link assigned to its associated signaling link port.
Links A-A7 and B-B7 can be specified for an E5-ENET-B or SLIC card running the IPLIMI application.
The card location for the card associated with the lhost and alhost must exist in the IP Link table.
The allowed maximum is 1 association per signaling link on IPLIMx cards.
A maximum of 50 connections (association-to-AS assignments) can be specified per local host on IPGWx cards.
A maximum of 4000 connections (association-to-AS assignments + sockets) are allowed per system.
Table 4-3 shows the maximum number of associations and links for E5-ENET-B cards.
Table 4-3 Maximum IP Associations and Links
| GPL | Max # of Associations | Max # of Links |
|---|---|---|
|
IPLHC |
16 |
16 |
|
IPGHC |
50 |
1 |
|
IPSG |
32 |
32 |
|
IPSG on SLIC |
128 |
128 |
|
DEIRHC |
32 |
- |
The rmin parameter value must be less than or equal to the rmax parameter value.
The cwmin parameter value must be less than or equal to the bufsize parameter value.
If the m2patset parameter is specified, the adapter=m2pa parameter must be specified.
The trade ratio states the quantity of associations to sockets that may be provisioned on a certain card, as follows:
- Trade Ratio = a:s
- Where: a=associations and s=sockets
The requested buffer size increase cannot exceed
available buffer space on the card. Use the
rtrv-assoc command with the aname, lhost, or
alhost parameter to display used and
total buffer space on the card.
The ver parameter can only be specified if the adapter=m2pa parameter is specified.
If the value specified for the lhost parameter indicates an IPSG card or DEIR card running the DEIRHC GPL, then the link parameter cannot be specified.
If an IPSG card is being used, and if the association is referenced by a signaling link, then new values cannot be specified for the lhost or adapter parameters.
An IPSG card running on E5--ENET-B card or DEIR card can contain a maximum of 32 associations.
An IPSG application running on the SLIC card can contain a maximum of 128 associations.
If the value specified for the aname parameter refers to an M3UA association on an IPSG card, then the alw parameter cannot be specified.
The value specified for the lhost parameter cannot change the local host for the association from an IPLIMx or IPGWx card to an IPSG card or from an IPSG card to an IPLIMx or IPGWx card.
The rhosttype=primary parameter must be specified before the rhosttype=alternate parameter can be specified.
If the rhosttype parameter is specified, then the rhost parameter must be specified.
The value specified for the alternate remote host cannot be the same as the value specified for the lhost, alhost, or rhost parameter in the same association.
The value specified for the rhost parameter cannot be the same as the value specified for the alternate remote host or for the lhost or alhost parameter in the same association.
The host name specified by the lhost parameter must exist in the IP Host table and must be provisioned as local to this EAGLE.
A valid value must be specified for the host parameter. If the host name contains a hyphen, then the host name must be enclosed within quotation marks.
Realm must be associated with the RHOST specified in the IPHOST table for diameter association.
RHOST must be present in the IPHOST table.
Remote IP address (RHOST) must not exist in the IPLINK table.
The local host name (lhost) parameter must be configured before the alternate local host name (alhost) parameter is configured.
The allowed maximum is 1 connection per signaling link on IPLIMx cards.
No two open associations can have the same value for the LHOST/LPORT parameters.
IP address associated with the LHOST and ALHOST should be of the same IP version.
IP address associated with the LHOST and RHOST should be of the same IP version.
Notes
The command that is entered cannot exceed a total of 150 characters in length.
The IPAPSOCK table is used to associate the Local Host/Local Port to a Remote Host/Remote Port. This fully specifies the connection.
If the open=yes parameter is specified, the association’s lhost and lport configuration must not match that of any open association.
If the card’s application is IPLIMI, then the adapter parameter value and the ipliml2 value for the assigned signaling link must be m2pa.
An association with an adapter value of m2pa cannot be assigned to an SS7IPGW or IPGWI host.
For diameter associations (adapter=DIAM), realm must be associated with lhost and rhost parameters before open=yes parameter can be specified.
The link parameter is not allowed with diameter associations (adapter=DIAM).
While entering arhost for an alhost, the user needs to specify rhost parameter with rhosttype= alternate.
If none is specified for either alhost or rhost, that parameter is removed from the association's entry.
To delete an arhost, the user needs to specify rhost=none with rhosttype=alternate.
The M2PA version is supported if the application is IPLIMx and the adapter=m2pa parameter is specified. When changing the association adapter type to m2pa and a version is not specified, the m2pa=rfc value is assigned by default.
Table 4-4 shows the validation rules used to establish an association.
Table 4-4 Validation Rules for Association Establishment
| RHOSTVAL | RHOST Configured | ARHOST Configured | Source Parameter in IP Header | IP Address List in INIT/INIT ACK | Host Name Address Present in INIT/INIT ACK |
|---|---|---|---|---|---|
|
RELAXED |
Y |
N |
RHOST |
NA (1 or more IP addresses can be present, not necessarily match RHOST.) |
N |
|
RELAXED |
Y |
N |
NA |
RHOST (other IP addresses can also be present) |
N |
|
RELAXED |
Y |
N |
RHOST |
NA |
RHOST |
|
MATCH |
Y |
N |
RHOST |
N |
N |
|
MATCH |
Y |
N |
RHOST |
RHOST only (no additional addresses can be present) |
N |
|
MATCH |
Y |
N |
RHOST |
NA |
RHOST only |
|
RELAXED |
Y |
Y |
RHOST or ARHOST |
NA |
N |
|
RELAXED |
Y |
Y |
NA |
RHOST or ARHOST |
N |
|
RELAXED |
Y |
Y |
Same as Hostname |
NA (Ignore any IP addresses present) |
RHOST or ARHOST |
|
MATCH |
Y |
Y |
RHOST |
ARHOST must be present. RHOST can also be present. No other additional addresses. |
N |
|
MATCH |
Y |
Y |
ARHOST |
RHOST must be present. ARHOST can also be present. No other additional addresses |
N |
Output
chg-assoc:aname=a1:lhost=gw105.nc.tekelec.com:lport=1030:rport=1030:
uaps=10:rhost=gw100.nc.tekelec.com:alw=yes:rhostval=match:rhosttype=primary
rlghncxa03w 09-03-19 15:35:05 EST EAGLE 41.0.0
CHG-ASSOC: MASP A - COMPLTD
;
chg-atinpqopts
Use this command to provision ATINP-specific data. This command updates the ATINPQOPTS table.
Parameters
- atiackimsi (optional)
-
ATIACK IMSI parameter for ATI ACK response message. This parameter specifies formatting of IMSI digits in the ATI ACK response message. The result of formatting determines whether the IMSI parameter will be included in the response.
- Range:
-
- srfimsi
- If an entity was found during RTDB lookup, and SRFIMSI was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as the SRFIMSI.
- asd
- If an entity was found during RTDB lookup and ASD (Additional Subscriber Data) was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as ASD.
- grn
- If an entity was found during RTDB lookup, and GRN (Generic Routing Number) was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as GRN.
- none
- Do not include the IMSI parameter in the response message.
- Default:
- none
- atiackmsisdn (optional)
- MSISDN parameter for ATI ACK response message. This parameter specifies the formatting of MSISDN parameter in the ATI ACK response message. The result of formatting determines whether the MSISDN parameter will be included in the response.
- Range:
-
- msisdn
- Include the MSISDN parameter in the ATI ACK response and encode MSISDN digits as the MSISDN from the incoming ATI query.
- asd
- If an entity was found during RTDB lookup and ASD (Additional Subscriber Data) was provisioned in the entity, then include the MSISDN parameter and encode the MSISDN digits as ASD.
- asddlmmsisdn
- Include the MSISDN parameter in the ATI ACK response and encode MSISDN digits as ASD + delimiter (atidlm) + MSISDN. ASD is encoded if an entity is found and ASD is provisioned. The specified outbound message digits delimiter (atidlm) value is encoded if the value is not none. MSISDN is encoded as the MSISDN from the incoming ATI query.
- grn
- If an entity was found during RTDB lookup and GRN (Generic Routing Number) was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as GRN.
- grndlmmsisdn
- Include the MSISDN parameter in the ATI ACK response and encode MSISDN digits as GRN + delimiter (atidlm) + MSISDN. GRN is encoded if GRN entity is found. The specified outbound message digits delimiter (atidlm) value is encoded if the value is not none. MSISDN is encoded as the MSISDN from the incoming ATI query.
- none
- Do not include the MSISDN parameter in the response message.
- Default:
- msisdn
- atiackrn (optional)
- Routing number parameter for ATI ACK response message. This parameter specifies the formatting of the routing number parameter in the ATI ACK response message. The result of formatting determines whether the routing number parameter will be included in the response.
- Range:
-
- rn
- Routing number.
- If an entity was found in RTDB lookup and the entity type was RN, include the routing number parameter and encode routing number digits as found in the entity ID.
- If MSISDN was found in RTDB lookup, but no entity was found and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If MSISDN was not found in RTDB lookup and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If an entity was found in RTDB lookup, the entity type is SP, and the atidfltrn value is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- rnsp
- Routing number or signaling point.
- If an entity was found in RTDB lookup and the entity type was either SP or RN, include routing number parameter and encode routing number digits as found in the entity ID.
- If MSISDN was found in RTDB lookup but no entity was found and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If MSISDN was not found in RTDB lookup and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If an entity was found in RTDB lookup and the entity type was not SP or RN and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn Entity.
- asddlmrnsp
- ASD, delimiter and routing number or signaling point.
Format routing number digits as ASD (if supported and available from lookup entity) + atidlm (if not none) + entity digits (as described in the atiackrn=rnsp parameter).
- If this format results in 0 digits (no ASD, atidlm=none, and no entity digits), the routing number will not be included in the response message.
- If the formatting results only in the specified outbound message digits delimiter (atidlm) digits, the routing number parameter will not be encoded in the response.
- If no entity digits (atiackrn=rnsp) are found, the result is ASD + delimiter digits.
- rnspdlmasd
- Routing number or signaling point, delimiter, ASD
Format routing number digits as entity digits (as described in atiackrn=rnsp) + delimiter (if atidlm is not none) + ASD (if supported and available from lookup entity).
- If this formatting results in 0 digits (no ASD, atidlm=none, and no RN digits, the routing number will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number will not be encoded in the response.
-
If there are outbound message delimiter digits (the atidlm value is not none) and ASD digits are available, the delimiter will be included even if entity digits are not found (resulting in delimiter + ASD).
- srfimsi
- Encode routing number digits as SRFIMSI configured in the entity data.
If SRFIMSI was not found (MSISDN not found in RTDB lookup, or MSISDN found but no entity found, or entity found but SRFIMSI not configured) then the routing number will not be included in the response message.
- srfimsidlmasd
- SRFIMSI, delimiter, ASD
Encode routing number digits as SRFIMSI + delimiter (if atidlm is not none) + ASD (if supported and available from lookup entity). SRFIMSI is encoded as described in the atiackrn=srfimsi option.
- If this formatting results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response message.
- asddlmsrfimsi
- ASD, delimiter, SRFIMSI
Encode routing number as ASD (if supported and available from lookup entity) + delimiter (if atidlm is not none) + SRFIMSI(encoded as specified in the atiackrn=srfimsi parameter).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and ASD digits are available, the delimiter will be included even if SRFIMSI does not have any digits (resulting in ASD + delimiter).
- grndlmrnsp
- GRN, delimiter, Routing number or signaling point
Encode routing number as GRN (if supported and available from RTDB lookup) + delimiter (if atidlm is not none) + RNSP (encoded as specified in the atiackrn=rnsp parameter).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and GRN digits are available, the delimiter will be included even if RNSP does not have any digits (resulting in GRN + delimiter).
- rnspdlmgrn
- Routing number or signaling point, delimiter, GRN
Encode routing number as entity digits (as described in atiackrn=rnsp) + delimiter (if atidlm is not none) + GRN (if supported and available from RTDB lookup).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is notnoneand GRN digits are available, the delimiter will be included even if RNSP does not have any digits (resulting in delimiter + GRN).
- srfimsidlmgrn
- SRFIMSI, delimiter, GRN
Encode routing number as SRFIMSI (encoded as specified in the atiackrn=srfimsi parameter) + delimiter (if atidlm is not none) + GRN (if supported and available from RTDB lookup).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and GRN digits are available, the delimiter will be included even if SRFIMSI does not have any digits (resulting in delimiter + GRN).
- grndlmsrfimsi
- GRN, delimiter, SRFIMSI
Encode routing number as GRN (if supported and available from RTDB lookup) + delimiter (if atidlm is not none) + SRFIMSI (encoded as specified in the atiackrn=srfimsi parameter).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and GRN digits are available, the delimiter will be included even if SRFIMSI does not have any digits (resulting in GRN + delimiter).
- none
- Do not include the Routing Number field in the response message.
- Default:
- rn
- atiackvlrnum (optional)
-
The formatting of the VLR-number in the ATI ACK response message.
- Range:
-
- rn
- routing number
- If an RN entity was found in RTDB lookup, the VLR-number is formatted as RN.
- If RN entity was found in RTDB lookup, the portability type is zero, and the S-Port feature is enabled or the IGM feature is on, the VLR-number is formatted as GRN (if provisioned).
- If MSISDN was found in RTDB lookup, no entity was found, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If MSISDN was not found in RTDB lookup, atinptype=always and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If an SP entity was found in RTDB lookup, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If the format results in 0 digits (no entity digits), the VLR-number is formatted as the incoming MSISDN.
- rnsp
- Routing number or signaling point.
- If an RN or SP entity was found in RTDB lookup, the VLR-number is formatted as the entity ID.
- If MSISDN was found in RTDB lookup, no entity was found, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If MSISDN was not found in RTDB lookup, atinptype=always, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If an entity was found in RTDB lookup, the entity type was not RN or SP, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If the format results in 0 digits (no entity digits), the VLR-number is formatted as the incoming MSISDN.
- asddlmrnsp
- ASD, delimiter and routing number or signaling point.
Format the VLR-number as ASD (if provisioned) + atidlm (if not none) + entity digits (RN or SP).
- If the formatting results in 0 digits (no ASD, atidlm=none, and no entity digits), the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in atidlm digits, the VLR-number is formatted as the incoming MSISDN.
- If no entity digits are found, the VLR-number is formatted as ASD + delimiter digits.
- rnspdlmasd
- Routing number or signaling point, delimiter, ASD
- If the formatting results in 0 digits (no ASD, atidlm=none, and no RN digits), the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN. If there are outbound message delimiter digits (the atidlm value is not none) and ASD digits are available, the delimiter is included even if entity digits are not found (resulting in delimiter + ASD).
- srfimsi
- Format the VLR-number as SRFIMSI configured in the entity data.
If SRFIMSI was not found (MSISDN not found in RTDB lookup, or MSISDN found but no entity found, or entity found but SRFIMSI not configured) then the VLR-number is formatted as the incoming MSISDN.
- srfimsidlmasd
- SRFIMSI, delimiter, ASD
Format the VLR-number as SRFIMSI + delimiter (if atidlm is not none) + ASD (if provisioned).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If atidlm value is not none and ASD digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in delimiter + ASD).
- asddlmsrfimsi
- ASD, delimiter, SRFIMSI
Format the VLR-number as ASD (if provisioned) + delimiter (if atidlm is not none) + SRFIMSI.
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm value is not none and ASD digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in ASD + delimiter).
- grndlmrnsp
- GRN, delimiter, Routing number or signaling point
Format VLR-number as GRN (if provisioned) + delimiter (if atidlm is not none) + entity digits (RN or SP).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm value is not none and GRN digits are available, the delimiter is included even if RNSP does not have any digits (resulting in GRN + delimiter).
- rnspdlmgrn
- Routing number or signaling point, delimiter, GRN
Format VLR-number as entity digits (RN or SP) + delimiter (if atidlm is not none) + GRN (if provisioned).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm is not none and GRN digits are available, the delimiter is included even if RNSP does not have any digits (resulting in delimiter + GRN).
- srfimsidlmgrn
- SRFIMSI, delimiter, GRN
Format VLR-number as SRFIMSI + delimiter (if atidlm is not none) + GRN (if provisioned).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm is not none and GRN digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in delimiter + GRN).
- grndlmsrfimsi
- GRN, delimiter, SRFIMSI
Format VLR-number as GRN (if provisioned) + delimiter (if atidlm is not none) + SRFIMSI.
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm value is not none and GRN digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in GRN + delimiter).
- rnmsisdn
-
- If an RN entity was found in RTDB lookup, the VLR-number is formatted as RN + incoming MSISDN.
- If an SP entity was found in RTDB lookup, and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn + incoming MSISDN
- If MSISDN was found in RTDB lookup, but no entity was found and the atidfltrn value is not none, then VLR-number is formatted as atidfltrn value + incoming MSISDN.
- If MSISDN was not found in RTDB lookup, atinptype=always, and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn value + incoming MSISDN.
- If RN/PT=0 is found in RTDB lookup, the S-Port feature is enabled or the IGM feature is on, and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn + incoming MSISDN. RN/PT=0 is treated as an SP entity.
- rnspmsisdn
-
- If an RN or SP entity was found in RTDB lookup, the VLR-number is formatted as entity digits + incoming MSISDN.
- If MSISDN was found in RTDB lookup, but no entity was found and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn value + incoming MSISDN.
- If an entity was found in RTDB lookup, the entity type was not RN or SP, and the atidfltrn value is not none, then the VLR-number is formatted as the atidfltrn value + incoming MSISDN.
- If MSISDN was not found in RTDB lookup, atinptype=always, and the atidfltrn value is not none, then the VLR-number in the ATI ACK response is formatted as atidfltrn value + incoming MSISDN.
- msisdn
- Format the VLR-number as incoming MSISDN
- asd
- Format the VLR-number in the ATI ACK message as ASD (if provisioned).
If the formatting results in 0 digits, the VLR-number is formatted as incoming MSISDN.
- asdmsisdn
- Format the VLR-number in the ATI ACK message as ASD (if provisioned) + incoming MSISDN.
- Default:
- rnspmsisdn
- atidfltrn (optional)
- Default Routing Number. The routing number to be used in outgoing message formats while encoding outgoing digit formats in the ATI ACK response in cases where an RN is not returned from an RTDB lookup.
- atidlm (optional)
- Outbound message digits delimiter. This delimiter is used in outgoing message formats while encoding outbound digits in the ATI ACK response.
- atinptype (optional)
- Number Portability Type. The criteria for a successful RTDB lookup.
- entitylen (optional)
- Entity Length. The maximum number of digits to be used from entity data (SRFIMSI or entity ID) in the specified encoding format.
- off
- Disables or turns off the specified feature options. A comma-separated list of feature options that are requested to be turned off. Up to 8 feature options can be specified in the list.
- on
- Disables or turns on the specified feature options. A comma-separated list of feature options that are requested to be turned off. Up to 8 feature options can be specified in the list.
- snai (optional)
- Service NAI. The number conditioning that is performed on the MSISDN digits in the incoming ATI query message before RTDB lookup is performed.
- Range:
-
- intl
- Number conditioning is not performed.
- nat
- The default country code (defined in the
chg-stpopts:defcc=command) is pre-pended to the MSISDN before RTDB lookup. - nai
- The NAI from the MSISDN in the incoming ATI query is used to perform number conditioning.. If the message NAI is International (0x1) or Network Specific Number (0x3), then no conditioning is performed. In all other cases, the default country code (defined in the
chg-stpopts:defcc=command) is pre-pended to the MSISDN before RTDB lookup.
- Default:
- nai
- sporttype (optional)
- Service Portability type. The application of Service Portability that is applied to the associated feature.
The S-Port feature must be enabled before this parameter can be specified. The S-Port feature must be turned on before any change to the parameter will impact the associated feature.
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’ entity id) is applied.
Example
This example specifies that the outbound message delimiter will not be used in outgoing message formats:
chg-atinpqopts:atidlm=noneThis example specifies that the NAI of the incoming MSISDN digits will be considered to be National, and that the IMSI parameter will not be included in the ATI ACK response message:
chg-atinpqopts:snai=nai:atiackimsi=noneThis example specifies that the lookup is always considered to be successful and that the NAI of the incoming MSISDN digits will be considered to be National:
chg-atinpqopts:atinptype=always:snai=natThis example specifies that the Routing Number field will not be included in the response, and that the MSISDN in the ATI ACK response will be encoded as the ASD.
chg-atinpqopts:atiackrn=none:atiackmsisdn=asdThe example specifies that the Routing Number field will not be included in the response:
chg-atinpqopts:atiackrn=noneThis example specifies that the IMSI and MSISDN in the ATI ACK response will be encoded as GRN:
chg-atinpqopts:atiackimsi=grn:atiackmsisdn=grnThis example specifies that the Location information request in ATI query is supported and the VLR-number in the ATI ACK response will be encoded as rnspmsisdn :
chg-atinpqopts:atiackvlrnum=rnspmsisdn:on=atisupplocinfoDependencies
At least one optional parameter must be specified.
The ATINP feature must be enabled before this command can be entered.
The EGLEOPTS table is corrupt or cannot be found.
The Service Portability feature must be enabled before the sporttype parameter can be specified.
The same value cannot be specified for the on and off parameters.
Notes
- The ATINP feature must be turned on
- The on=atisupplocinfo parameter must be specified.
Output
chg-atinpqopts:atiackimsi=grn:atiackmsisdn=grndlmmsisdn:atiackrn=grndlmrnsp
tekelecstp 09-06-05 12:40:16 EST EAGLE 41.1.0
CHG-ATINPQOPTS: MASP A - COMPLTD
;
chg-atm-lps
Use this command to configure a link parameter set with timers and other parameters used by the system to provide level 2 functions for each ATM high-speed signaling link and to copy values from lpset 20 and 30, as well as any lpset to another.
Parameters
Note:
Unless specified, the system default values are meant for both ANSI (T1) and ITU (E1) standards.- lpset (mandatory)
- Link parameter set being changed.
Note:
Sets 1 -19 and 21 -29 can be configured. Link parameter sets 20 and 30 are not configurable and are used to contain the recommended default values for a set.
- action (optional)
- This parameter copies a set of ATM signaling link parameters from one set to another.
- tmrcc (optional)
- Timer value, in milliseconds, used during the connection phase to guard against unacknowledged BGN, END, ER or RS PDUs.
- tmridle (optional)
- Timer value, in milliseconds, used during the idle phase when no SD PDUs are being sent to limit time in the idle phase.
- tmrkalive (optional)
- Timer value, in milliseconds, used during the transient phase when no SD PDUs are being sent to keep connection up.
- tmrnocred (optional)
- The timer, in milliseconds, used when the no credit exists and PDUs are available to be sent.
- tmrnorsp (optional)
- Timer value, in milliseconds, used to check that STAT PDUs are arriving often enough.
- tmrpoll (optional)
- Timer value, in milliseconds, used to guarantee that POLL PDUs are sent often enough.
- tmrprov (optional)
- The timer, in milliseconds, used to monitor the status of a link after it is placed into service.
- tmrsrec (optional)
- Timer value, in milliseconds, used to prohibit closely spaced SSCOP recoveries from occurring.
- tmrt1 (optional)
- Time, in milliseconds, between link release action and the next link reestablish action during alignment.
Example
chg-atm-lps:lpset=5:tmrprov=1000:tmridle=55
chg-atm-lps:lpset=3:srclpset=5:action=copy
Dependencies
The values in link parameter sets 20 and 30 are the system default values. They cannot be changed but can be copied to another link parameter set.
The same value cannot be specified for the lpset and srclpset parameters.
The action and srclpset parameters must be specified together.
If action=copy parameter is specified, only the lpset and scrlpset parameters can be specified.
At least one optional parameter must be specified.
The Link Parameter Set table is corrupt or cannot be found.
Notes
If no parameter value for the lpset parameter is included when the ent-slk command is entered, the system default value of 1 is assigned for ANSI links and the system default value of 21 is assigned for ITU links.
All timer values for link parameter sets are initialized to the system default values.
Output
chg-atm-lps:lpset=5:tmrprov=1000:tmridle=55
rlghncxa03w 04-01-05 16:40:40 EST EAGLE 31.3.0
CHG-ATM-LPS: MASP A - COMPLTD
;
Related Topics
chg-attr-seculog
Use this command to modify attributes that affect the operation of the security logging feature.
Parameters
- upldalm (optional)
- Enable or disable log alarms that pertain to uploading of the security log.
- upslg (optional)
- Percent full threshold. The percent full threshold for the security logs. If the upldalm=yes parameter is specified, an alarm is raised for the security log when the %full field (see the
rept-stat-seculogcommand) in the log, on the active OAM, reaches or exceeds the value specified for upslg. This alarm indicates that the administrator must upload the log.
- purgeperiod (optional)
-
Purge period (in Days). Number of days beyond which security logs will be deleted. If
purgeperiodis greater than 0, then all the security logs which are older thanpurgeperiodwill be deleted from OAM (seertrv-seculogandrept-stat-seculog). Log entries will be deleted in background at the rate of one every few seconds until all stale entries have been removed.
Example
chg-attr-seculog:upslg=80:upldalm=yes
Dependencies
At least one optional parameter must be specified.
The Security Log Attributes table is corrupt or cannot be found by the system.
Notes
None
Output
chg-attr-seculog:upslg=80:upldalm=yes
rlghncxa03w 04-01-05 16:40:40 EST EAGLE 31.3.0
CHG-ATTR-SECULOG: MASP B - COMPLTD
;
chg-attr-seculog:purgeperiod=2
Command Accepted - Processing
stpc1081301 20-05-13 17:24:56 EST EAGLE 46.9.0.0.0-76.9.0
chg-attr-seculog:purgeperiod=2
Command entered at terminal #1.
;
stpc1081301 20-05-13 17:24:56 EST EAGLE 46.9.0.0.0-76.9.0
CHG-ATTR-SECULOG: MASP B - COMPLTD
;chg-card
- Change the configuration of a card in the database from an IPLIMx configuration to an IPSG configuration and from an E5-ENET-B or SLIC card.
- Configure the type of EPAP data (DN or IMSI) that is loaded to an E5-SM8G-B or SLIC card.
- If the IPSG application is running on SLIC hardware,
the
chg-cardcommand can be optionally used to change the data type from 'gtt' to 'nosccp' and vice-versa.
Parameters
- loc (mandatory)
- The card location as stenciled on the shelf of the
system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
- data (optional)
-
Type of OAM/MPS data that can be loaded on an E5-SM8G-B or SLIC card.
- Range:
-
- dn
- only DN related data from EPAP is loaded on the card
- epap
- all RTDB data (DN+IMSI) from EPAP are
loaded on the card
Note:
The epap value cannot be specified when the EPAP Data Split feature is ON. - elap
- ELAP data are loaded on the card.
- gtt
- Only OAM data, including GTT data, are loaded on the card. This card will not load any ELAP or EPAP data at all.
- imsi
- Only IMSI related data from EPAP is loaded on the card
- nosccp
- Only OAM data, excluding GTT data is
loaded on the card. No GTT or MPS data will be downloaded on the card. This
value (=nosccp) of the
data parameter is
valid only for IPSG card(s) with the
type=slic.
Note:
The nosccp value signifies the absence of SCCP functionality on the IPSG card, and that it behaves as a regular IPSG card.
Example
chg-card:loc=1105:nappl=ipsg
chg-card:loc=1305:type=enetb
chg-card:loc=1201:data=imsi
chg-card:loc=1101:type=slic
Dependencies
The card location specified by the loc parameter cannot be 1113-1118, xy09, or xy10 where x is the frame and y is the shelf.
The specified shelf location must be provisioned and present in the frame.
The Shelf table is corrupt or cannot be found.
The IMT (Card) table is corrupt or cannot be found.
Only M2PA associations can be configured for the IP link host address for the card indicated by the loc parameter value. M3UA IP associations are not supported.
If the HIPR2 High Rate Mode feature is turned off, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 500,000. If the HIPR2 High Rate Mode feature is turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 750,000. If the HIPR2 High Rate Mode and 1M System TPS features are turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 1,000,000.
The resulting total TPS of all signaling links configured for an E5-ENET-B or SLIC card when the type=enetb parameter is specified cannot exceed 6500 TPS. The resulting total TPS of all signaling links configured for a SLIC card when the type=slic parameter is specified cannot exceed 12,000 TPS
A SLIC card must be installed at the location indicated by the loc parameter.
A value of ipsg must be specified for the nappl parameter.
The card in the location indicated by the loc parameter must already be equipped.
The value specified by the loc parameter must be within the allowed range.
The Link table is corrupt or cannot be found.
The loc parameter must be specified.
All links on the SLIC card must have a matching association configured. For
IPSG-hosted associations, a link and association are matched using the aname parameter for the ent-slk command.
The nappl or type parameter must be specified.
If DN or IMSI is specified for the data parameter for VSCCP, the EPAP Data Split feature must be turned on.
Note:
The DATA parm is valid only for SLIC IPSG cards, and not ENET/ENETB IPSG cards.If ELAP or EPAP is specified for the data parameter for VSCCP, the Dual ExAP Config feature must be enabled.
When data=gtt is specified for VSCCP, either Dual ExAP Config must be enabled or EPAP Data Split feature must be turned ON.
The data=gtt parameter cannot be specified for VSCCP if an IP link has been configured for the card.
To provision card type=ENETB or SLIC, the shelf FAN bit must be turned ON for the card's shelf.
If the IPSG32 GPL is running on the location specified by the loc parameter, then data=gtt and data=nosccp are the only valid values for the DATA parameter. If the GPL is anything but IPSG32 GPL, data=nosccp cannot be used for the card on that location.
If card is type=SLIC with data=GTT and is changed to type=ENET/ENETB, then data must be changed to NOSCCP first.
A GTT-enabled IPSG card can only have 32 equipped SS7 links. A SLIC IPSG card with more than 32 equipped SS7 links cannot be a GTT-enabled IPSG card.
The data parameter can only be specified for IPSG application running on SLIC card.
Notes
If a SLIC card is plugged into a slot provisioned for E5-ENET-B, this command can be used to change the card type from enet to slic or enetb to slic. The card must be manually inhibited first in order to allow the command to be processed.
Output
chg-card:loc=1206:nappl=ipsg
rlghncxa03w 10-03-01 11:11:28 EST EAGLE 42.0.0
CHG-CARD: MASP A - COMPLTD
;
chg-clkopts
Use this command to perform a software update of the clock elements and settings.
Parameters
- force (optional)
- The force=yes parameter is used to change the hsclksrc parameter value when the TDMs are reporting that the high speed system clocks are currently valid.
- hsclksrc (optional)
- High speed master clock source. The force=yes parameter must be specified with this parameter to change the clock source when the TDMs are reporting that the high speed system clocks are currently valid.
Caution:
Changing the high speed master clock source can result in clock outage and loss of traffic on all links, if the new source type does not match the provisioned source for the E1 or T1 cards (what is actually plugged into the backplane).
Example
chg-clkopts:clock=primary:hsclksrc=t1framed
chg-clkopts:clock=all:hsclksrc=rs422:force=yes
chg-clkopts:hsclkll=shorthaul:clock=secondary
Dependencies
The STPOPTS table is corrupt or cannot be found.
The parameters entered are not compatible with the card where the clock resides.
If the hsclksrc and clock=all parameters are specified, and the high speed clocks are reporting, then the force=yes parameter must be specified.
Notes
None.
Output
chg-clkopts:clock=primary:hsclksrc=t1framed
e5oam 09-01-01 17:25:22 MST EAGLE 40.1.0
CHG-CLKOPTS: MASP B - COMPLTD
;
chg-cmd
Use this command to change the attributes of a command.
Parameters
Note:
All class(X) parameters consist of a configurable command class name (ayy), and indicator (-yes or-no) to specify whether the command class is allowed. A value ofayy-yes indicates that the value is allowed. A value ofayy-no indicates that the value is not allowed.- class1 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
- class2 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
- class3 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
- class4 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
- class5 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
- class6 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
- class7 (optional)
- This parameter specifies a configurable command class name and indicator to indicate whether the command class is allowed.
Example
chg-cmd:cmd=ent-rte:class1=u11-yes
chg-cmd:cmd=rept-stat-slk:class7=dab-no
Dependencies
At least one optional parameter must be specified.
The Command Class Management feature must be enabled before this command can be entered.
The cmd parameter value must be a valid system command.
The CCCNAMES table is corrupt or cannot be found.
The CCCMD table is corrupt or cannot be found.
The class1 - class8 parameter values must be valid default or provisioned configurable command class names.
The login command is available to all users and therefore cannot be assigned to a configurable class. If the login command is used as a parameter, it will be rejected.
Notes
Up to 8 configurable command class names can be specified in one command. More than 8 command classes can be updated by entering additional commands. To update all 32 available configurable command classes, you could enter 4 commands with 8 command classes specified in each command.
Output
chg-cmd:cmd=ent-rte:class1=u11-yes
rlghncxa03w 04-01-05 16:40:40 EST EAGLE 31.3.0
CHG-CMD: MASP B - COMPLTD
;
chg-cmdclass
Use this command to change the name or description of a configurable command class.
Parameters
Example
chg-cmdclass:class=abc:descr=”my command class description”
chg-cmdclass:class=u23:nclass=dab:descr=”his command class description”
chg-cmdclass:class=dab:nclass=krb
Dependencies
At least one optional parameter must be specified.
The Command Class Management feature must be enabled and turned on before this command can be entered.
The class parameter value must be a valid configurable command class name (one of the default configurable command class names or a user-defined command class name).
The CCCNAMES table is corrupt or cannot be found.
The value specified for the nclass parameter cannot be the same as an existing configurable or non-configurable command class name.
Notes
None
Output
chg-cmdclass:class=abc:descr=”my command class description”
rlghncxa03w 04-01-05 16:40:40 EST EAGLE 31.3.0
CHG-CMDCLASS: MASP B - COMPLTD
;
chg-csl
Use this command to change an existing entry in the Common Screening List (CSL). The Common Screening List commands are used to tailor certain types of general screening information to specific features.
Parameters
- ds (optional)
- Digit string. A unique string of digits used by the specified screening feature
- Range:
- 1 - 15 hexadecimal digits.
Valid digits are 0-9, a-f, A-F
- 1-6 digits—Prepaid IDP Query Relay ccnc list
- 1-15 digits—Prepaid IDP Query Relay gt list
- 1-10 digits—Prepaid IDP Query Relay skbcsm list
- 4 digits—IDP Screening for Prepaid skts list
- 1-15 digits—IDP Screening for Prepaid insl list
- 1-15 digits—VFLEX vmpfx list
- 1-6 digits—Info Analyzed Relay Base ccnc list
- 1-15 digits—Info Analyzed Relay Base gt list
- 2 digits—Info Analyzed Relay Base trig list
- 1-15 digits — EIR imsipfx list
Table 4-23 lists valid hexadecimal values for the Info Analyzed Relay Base trig list ds entries.
- feature (optional)
- Feature name. The name of the enabled screening feature for which the command is entered.
Note:
The pn or feature parameter must be specified to identify the feature.- Range:
- azzzzzzzzzzzzzzzzzzzzzzzz
1 alphabetic character followed by up to 24 optional alphanumeric characters, including spaces and special characters, enclosed in double quotation marks (" ").
Enter enough of the feature name to make the name unique if two features begin with the same word or acronym. The following feature names are valid for this command:
- EIR
- IDP Screening for Prepaid
- IDP Service Key Routing
- Info Analyzed Relay Base
- Prepaid IDP Query Relay
- SIP Number Portability
- VFLEX
- list (optional)
- Common Screening List associated with the feature.
- Range:
-
- ccnc
- CC+NC List
- delpfx
- Delete Prefix List
- gt
- Global Title List
- imsipfx
- IMSI Screening Prefix List
- insl
- In Network Subscriber List
- npbypass
- SIP NPBYPASS list
- skbcsm
- SK+BCSM List
- skts
- SK+TS List
- trig
- Trigger List
- vmpfx
- Voice Mail Prefix LIst
The following screening lists are valid for the indicated features:
- ccnc, gt— Prepaid IDP Query Relay, Info Analyzed Relay Base
- imsipfx— EIR
Note:
If list argument is not specified in this command for EIR feature then list = imsipfx by default is taken. - npbypass— SIP Number Portability
- skbcsm—Prepaid IDP Query Relay and IDP Service Key Routing
- skts, insl—IDP Screening for Prepaid
- trig—Info Analyzed Relay Base
- vmpfx—VFLEX
The delpfx list is not supported at this time. This list should only be used by Oracle personnel.
- p1 (optional)
- Parameter Value 1. This parameter is specific to the feature and list that use the parameter.
- Range:
- zzzzzzzzzz
Valid values for the IDP Service Key Routing feature are:
- 3 or prepaid1—Prepaid Portability Type 3 for the SKBCSM list
- 4 or prepaid2—Prepaid Portability Type 4 for the SKBCSM list
- 6-35 or prepaid3-prepaid32—Prepaid Portability Types 6 through 35 for the SKBCSM list
- 255 or prepaidno—No Prepaid Portability Type for the SKBCSM list
Valid values for EIR feature are:- 1 or range— Check only range IMEI table for the IMSIPFX list
- 2 or individual — Check only individual IMEI table for the IMSIPFX list
- 3 or both --- Check individual IMEI table first and then range table for the IMSIPFX list
- 4 or none --- No check in either Individual IMEI Table or Range IMEI Table for the IMSIPFX list.
Valid values for the Prepaid IDP Query Relay feature are:
- 0, 1—National or International for the DELPFX list, which is for Tekelec personnel use ONLY.
Note:
The p1 parameter is used by the IDP Service Key Routing feature or EIR feature.
- p2 (optional)
- Parameter Value 2. The IDP Relay Service that is associated with an SKBCSM list DS entry. Multiple IDP Relay Services can be provisioned for use with NPP or Response Type for EIR feature that is associated with an imsipfx list DS Entry.
- p3 (optional)
- Parameter Value 3. The parameter value is specific to the feature and list name that use this parameter. No feature currently uses this parameter.
- pc (optional)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- pc/pca/pci/pcn/pcn24 (optional)
- Point code. The ds parameter or a point code parameter must be specified.
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and example.
- pcn (optional)
- ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc).
- pcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- pfxstrip (optional)
- This parameter in NPBYPASS list indicates whether matched prefix must be deleted or not.
- pn (optional)
- Part Number. The 9-digit "893xxxxxx" part number of the feature for which the command is entered. The
rtrv-ctrl-featcommand description shows the part number in the command output example.Note:
The pn or feature parameter must be specified to identify the feature.- Range:
- 893000000 - 893999999 The first 3 digits are 893. Do not separate the digits with dashes or spaces. The following part numbers are valid for this command:
- 893012301 --- EIR
- 893015501—IDP Screening for Prepaid
- 893016001—Prepaid IDP Query Relay
- 893016701—VFLEX
- 893034201—Info Analyzed Relay Base
- 893040601— SIP Number Portability
Example
chg-csl:feature="IDP Screening for Prepaid":list=insl:ds=123456789bcdEF
chg-csl:feature="VFLEX":list=vmpfx:ds=123456789abcdEF
chg-csl:feature="Prepaid IDP Query Relay":list=skbcsm:ds=0000000056:p2=idprcdpn4:scpgta=abce9875
chg-csl:pn=893040601:list=npbypass:ds=0000046:pfxstrip=yes
chg-csl:feature="SIP NUMBER PORTABILITY":list=npbypass:ds=000036:pfxstrip=no
chg-csl:feature="EIR":list=imsipfx:ds=401134134:p1=range:p2=whitelist
Dependencies
An enabled feature must be specified using a valid part number (pn) or feature name (feature). The specified feature must use a Common Screening List.
The feature that is specified by the feature parameter must already be enabled.
The list parameter must be specified for features that use more than one type of screening list.
The value specified for the list parameter must be valid for the specified screening feature.
The specified screening list entry must exist in the screening list that is used by the feature.
The length of the digit string that is specified for the ds parameter must be valid for the screening feature and list type.
A valid ds parameter value is required for the specified feature and list type.
The following parameters are allowed with the indicated common screening list type:
- list=gt—ds parameter
- list=ccnc—ds parameter
- list=skbcsm—ds and scpgta parameters
- list=skts—ds parameter
- list=insl—ds parameter
- list=vmpfx—ds parameter
- list=trig—ds parameter
- list=imsipfx--- ds parameter
The leading digit pattern of the value specified for the ds parameter must be unique in the specified screening list for the indicated feature.
The Common Screening List table is corrupt or cannot be found.
The pc or ds parameter must be specified. The parameters cannot be specified together in the command.
The value specified for the feature parameter must be valid feature name for a feature that uses a Common Screening List. The feature name must be specified as it appears in the rtrv-ctrl-feat command output. Enough of the name must be specified to make the name unique when two features begin with the same word or acronym.
The scpgta and pc parameters cannot be specified together in the command.
If the scpgta parameter is specified, then the ds parameter must be specified.
A valid p1 and p2 parameter value is required for the specified feature and list type.
The SIPNP feature must be enabled before changing NP prefix entries for the NPBYPASS list.
PFXSTRIP must be changed when the list specified is NPBYPASS with the SIPNP Feature.
The DS (Digit String) must be between 1 - 15 digits in length for SIPNP Feature
Notes
None
Output
chg-csl:pn="Prepaid IDP Query Relay":list=skbcsm:ds=0000000056:p2=idprcdpn4:scpgta=abce9875
tekelecstp 10-10-20 14:46:49 EST EAGLE 43.0.0
SK+BCSM List ( 7 of 150) 5%
CHG-CSL: MASP A - COMPLTD
;
chg-csl:feature="SIP Number Portability":list=npbypass:ds=0000000034:pfxstrip=yes
tekelecstp 12-06-25 15:29:14 EST EAGLE 45.0.0
chg-csl:feature="SIP Number Portability":list=npbypass:ds=0000000034:pfxstrip=yes
Command entered at terminal #4.
PFX List ( 2 of 1000) 1%
CHG-CSL: MASP A- COMPLTD
;chg-csl:pn=893040601:list=npbypass:ds=0000000056:pfxstrip=yes
tekelecstp 12-06-025 15:29:14 EST EAGLE 45.0.0
chg-csl:pn=893040601:list=npbypass:ds=0000000056:pfxstrip=yes
Command entered at terminal #4.
PFX List (3 or 1000) 1%
CHG-CSL: MASP A-COMPLTD
;chg-ctrl-feat
Use this command for controlled features that have been
enabled with the
enable-ctrl-feat command to turn on or
turn off On/Off features and to turn on Permanently On features (cannot be
turned off after they have been turned on)
Example
chg-ctrl-feat:partnum=893xxxxxx:status=on
chg-ctrl-feat:partnum=893xxxxxx:alarm=clear
Dependencies
The controlled feature specified by the
partnum parameter must be enabled
(see the
enable-ctrl-feat command) before this
command can be entered.
One of the optional parameters, but not both, must be specified in the command.
To use this command to turn off a feature, the Part Number specified in the command must be for one of the following On/Off features that is currently on. (A Permanently On feature is turned on with this command; after the feature has been turned on, it cannot be turned off with this command):
- 893018001 1100 TPS/DSM for ITU NP
- 893022101 ATI Number Portability Query (ATINP)
- 893017601 Circ Route Auto-Recovery
- 893005801 Command Class Management
- 893400001 EAGLE OA&M IP Security
- 893018101 Enhanced Far-End Loopback
- 893015401 Flexible GTT Load Sharing (FGTTLS)
- 893027401 GTT Load Sharing with Alternate Routing Indicator (GTT LS ARI)
- 893020101 HIPR2 High Rate Mode
- 893025701 IDPR ASD
- 893025601 IDPR GRN
- 893035001 Info Analyzed Relay ASD
- 893035101 Info Analyzed Relay GRN
- 893026101 Info Analyzed Relay NP
- 893038901 Integrated GLS
- 893006901 Intermediate GTT Load Sharing (IGTTLS)
- 893005701 IP User Interface (Telnet)
- 893018401 Large BICC MSU Support for IP Signaling
- 893006601 LNP Short Message Service (LNP SMS)
- 893007001 MNP Circular Route Prevention
- 893026701 MO SMS ASD
- 893024601 MO SMS B-Party Routing
- 893026601 MO SMS GRN
- 893026201 MO SMS IS41-to-GSM Migration
- 893013501 MTP Map Screening
- 893009101 Network Security Enhancement
- 893039301 NPP Unlimited SDWC Characters
- 893009301 Portability Check for Mobile Originated SMS
- 893006701 Prepaid SMS Intercept Phase 1 (PPSMS)
- 893018801 SEAS over IP
- 893034301 Service Portability
- 893024501 TIF ASD
- 893025501 TIF GRN
- 893022501 TIF Number Substitution
- 893037701 TIF Range CgPN Blacklist
- 893037601 TIF Subscriber CgPN Blacklist
Turning on a feature that is already on or turning off a feature that is already off has no effect.
The GTT feature must be turned on (see the
chg-feat command) before the following
features can be turned on:
- Intermediate Global Title Translation Load-Sharing (IGTTLS)
- LNP ELAP Configuration
- SCCP Loop Detection
All IPSM cards in the system must be inhibited before the IP User Interface (Telnet) feature can be turned on or off.
All IPSM cards in the system must be inhibited before the EAGLE OA&M IP Security Enhancements feature can be turned on or off.
Only one of the optional parameters, not both, can be specified in the command.
After a Permanently On feature is turned on, it cannot be turned off with this command. All controlled features with quantity feature access keys (like LNP ported TNs) and the following features are Permanently On features:
- 15 Minute Measurements
- Advanced GTT Modification (AMGTT)
- Advanced GTT Modification Called Party Only (AMGTT CdPA Only)
- Advanced GTT Modification Calling Party Upgrade (AMGTT CgPA Upgrade)
- ANSI-41 INP Query
- ANSI-41 Mobile Number Portability (A-Port)
- ANSI/ITU SCCP Conversion
- Diameter S13/S13' Interface for EIR
- E5-OAM Integrated Measurements (Integrated Measurements)
- Enhanced GSM MAP Screening (EGMS)
- Equipment Identity Register (EIR)
- Flexible Linkset Optional Based Routing (FLOBR)
- G-Flex MAP Layer Routing
- G-Port SRI Query for Prepaid
- GSM Flexible Numbering (G-Flex)
- GSM MAP Screening (GMS)
- GSM MAP SRI Redirect for Serving HLR
- GSM Mobile Number Portability (G-Port)
- GTT Action - DISCARD
- GTT Action - DUPLICATE
- GTT Action - FORWARD
- Hex Digit Support for GTT
- IDP A-Party Blacklist
- IDP A-Party Routing
- IDP Screening for Prepaid
- IDP Service Key Routing
- Info Analyzed Relay Base (IAR)
- INP
- IS41 GSM Migration (IGM)
- ISUP NP with EPAP
- ITU TCAP LRN Query (LRNQT)
- ITUN-ANSI SMS Conversion
- LNP ELAP Configuration
- LOCREQ Query Response
- MO-based GSM SMS NP
- MO-based IS41 SMS NP
- MT-Based GSM SMS NP
- MT-Based GSM MMS NP
- MT-Based IS41 SMS NP
- MTP Msgs for SCCP Apps
- Multiple Linkset to a Single Adjacent Point Code
- Origin-Based MTP Routing
- Origin-based SCCP Routing
- PC & CIC Translation (PCT)
- Prepaid IDP Query Relay
- SCCP Loop Detection
- Service Portability (S-Port) Subscriber Differentiation
- SIP Number Portability
- SLS Bit Rotation by Incoming Linkset (ISLSBR)
- Spare Point Code Support
- Support for 16 GTT Lengths in VGTT
- TCAP Opcode Based Routing (TOBR)
- TCAP Opcode Quantity
- TIF Number Portability
- TIF SCS Forwarding
- TIF Simple Number Substitution
- Transaction-based GTT Loadsharing (TBGTTLS)
- Voice Mail Router (V-Flex)
- Weighted GTT Loadsharing (WGTTLS)
- XUDT UDT Conversion
The value specified for the partnum parameter must be the correct part number for the feature.
The platformenable=on or the
oamhcmeas=on parameter must be
specified (see the
chg-measopts command) before the 15
Minute Measurements feature can be turned on.
If the Measurements Platform feature is turned on (see
the
chg-feat
command) as a precursor to turning on the 15 Minute
Measurements feature, then at least one MCPM card must be available in the
IS-NR state before the 15 Minute Measurements feature can be turned on. The
platformenable=on parameter must be
specified (see the
chg-measopts
command) before an MCPM card can be placed in the IS-NR
state.
The 15 Minute Measurements feature cannot be turned on when 30 minute measurements collection is in progress.
The Global Title Translation (GTT) feature must be
turned on (using the
gtt=on parameter for the
chg-feat
command ) before the Intelligent Network Application Part
(INAP) Number-based Portability (INP) feature or the ANSI-41 INP Query
(AINPQ) feature can be turned on.
The A-Port, G-Port, or IGM feature must be turned on before the MNP Circular Route Prevention feature can be turned on.
The SEASCLLI must be provisioned (see the
chg-seas-config command) before the
SEAS Over IP feature can be turned on.
At least one SEAS terminal must be configured (see the
chg-trm command) before the SEAS Over
IP feature can be turned on.
The IP address of at least one IPSM card associated with a SEAS terminal must be configured before the SEAS Over IP feature can be turned on.
The IP User Interface feature must be turned on before the SEAS Over IP feature can be turned on.
The
login
and
hname parameters must be provisioned
(see the
chg-seas-config
command) before the SEAS Over IP feature can be turned on.
If the SEAS Over IP feature is turned on, then the IP User Interface feature cannot be turned off.
All card locations that correspond to SEAS terminals must be provisioned with IPSM cards before the SEAS Over IP feature can be turned on.
The A-Port feature must be turned on before the MT-Based IS41 SMS NP feature can be turned on.
The G-Port feature must be turned on before the MT-Based GSM SMS NP feature can be turned on.
HIPR2 cards must be installed in all MUX locations before the HIPR2 High Rate Mode feature can be turned on.
The
defcc system option (see the
chg-stpopts command) must be
provisioned before the IAR Base feature can be enabled and before the ATINP,
MT-based GSM SMS NP, or MT-Based IS41 SMS NP feature can be turned on.
The
defmcc GSM option (see the
chg-gsmopts command) must be
provisioned before the MT-Based GSM SMS NP feature can be turned on.
The MT-Based GSM SMS NP feature must be turned on before the MT-Based GSM MMS NP feature can be turned on.
An IDPRCDPN(X) NPP service must be ON before the Prepaid IDP Query Relay feature can be turned on.
The defcc and
defndc system options (see the
chg-stpopts command) must be
provisioned before the V-Flex feature can be turned on.
The Prepaid IDP Query Relay feature must be turned on before the IDPR ASD or IDPR GRN feature can be turned on.
The
matchseq=dn parameter must be
specified (see the
chg-tifopts command) before the TIF
ASD feature can be turned on.
The GTT LS ARI feature must be turned off before the IGTTLS feature can be turned off.
The HIPR2 High Rate Mode feature cannot be turned on or off if an IMT Rate Change sequence is in progress.
If the provisioned System TPS (SIGTRAN TPS + ATM TPS) is greater than 500,000, then the HIPR2 High Rate Mode feature cannot be turned off.
The flashing process must be complete on all MUX cards before the HIPR2 High Rate Mode feature can be turned on or off.
The HIPR2 High Rate Mode feature cannot be turned on or off during an Extended Bit Error Rate Test (BERT).
The
matchseq=dn parameter must be
specified (see the
chg-tifopts command) before the TIF
Subscriber CgPN Blacklist feature can be turned on.
The
crptt parameter must have a value of
none (see the
chg-gsmopts command) before the MNP
CRP feature can be turned off.
The HIPR2 High Rate Mode feature cannot be turned on or off during upgrade.
The Default Country Code must be provisioned (see the
defcc parameter in the
chg-stpopts command) before the
Prepaid IDP Query Relay feature can be turned on.
The EGLEOPTS table is corrupt or cannot be found.
The SEASCFG Table must be accessible.
At least one terminal without a Thermal Alarm must exist before the SEAS Over IP feature can be turned on.
The INP and AINPQ features cannot be turned on if the LNP (an LNP ported TNs quantity), LNP 150,000 LRNs, or LNP 300,000 NPANXX feature is enabled and on.
The LNP ELAP Configuration feature and the WNP feature must be turned on before the LNP SMS feature can be turned on.
The STP Options table is corrupt or cannot be found by the system.
If a
chg-ctrl-feat command is already in
progress, then another
chg-ctrl-feat command cannot
be entered.
The Linkset table is corrupt or cannot be found.
The Link table is corrupt or cannot be found.
If a single digit wildcard (?) is specified as a value for the
fpfx parameter more than 25 times
across all of the rules for an NPP service (see the
ent-npp-srs
command), then the NPP Unlimited SDWC Characters feature
cannot be turned off.
If more than three single digit wildcard characters
(?) are specified for the
fpfx parameter in an NPP Service
rule (see the
ent-npp-srs command), then the NPP
Unlimited SDWC Characters feature cannot be turned on.
If a single digit wildcard (?) is specified after the sixth digit of the value
specified for the
fpfx parameter for an NPP Service
rule (see the
ent-npp-srs command), then the NPP
Unlimited SDWC Characters feature cannot be turned on.
A database error occurred while trying to access the NPPFILT table.
The E5-ENET-B IPSG High Throughput feature cannot be turned off if an E5-ENET-B card running the IPSG application in the system has a configured card capacity above 6500 TPS.
The HIPR2 High Rate Mode feature must be ON before the 1M System TPS feature may be turned ON. The HIPR2 High Rate Mode feature cannot be turned OFF if the 1M System TPS feature is turned ON.
If the System TPS is more than 750K then the 1M System TPS feature cannot be turned OFF.
Notes
SEAS Terminals
All terminals that are configured as SEAS are automatically allowed or inhibited when the SEAS Over IP feature is turned on or off, respectively.
Commands blocked during IMT Rate Change sequence:
If the HIPR2 High Rate Mode feature is turned on or
off, then an IMT Rate Change sequence is carried out (if required). The
alw-imt,
disc-imt,
flash-card,
inh-imt,
init-flash,
init-mux, and
tst-imt commands cannot be entered if
an IMT Rate Change sequence is in progress.
Service Portability
If the Service Portability feature is turned on before a dependent feature is turned on, then a warning is issued:
WARNING: No Service Portability dependent feature is on.If the Service Portability feature is turned off when more than one dependent feature is turned on, then a warning is issued:
WARNING: Service Portability is OFF.
Output
chg-ctrl-feat:partnum=893xxxxxx:status=on
tekelecstp 06-07-26 14:47:49 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893xxxxxx:status=on
Command entered at terminal #4.
CHG-CTRL-FEAT: MASP A - COMPLTD
;
chg-ctrl-feat:partnum=893xxxxxx:alarm=clear
tekelecstp 06-07-26 14:47:49 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893xxxxxx:alarm=clear
Command entered at terminal #4.
CHG-CTRL-FEAT: MASP A - COMPLTD
;
tekelecstp 06-07-26 14:47:49 EST EAGLE 36.0.0
0367.0181 * SYSTEM Temp Key(s) expiration alarm cleared.
;
This example shows the output when the 1100 TPS/DSM for
ITU NP feature is on, and the
chg-ctrl-feat command is re-entered
within 30 seconds for confirmation:
chg-ctrl-feat:partnum=893018001:status=on
tekelecstp 06-07-26 14:47:49 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893018001:status=on
Command entered at terminal #4.
CAUTION:Rated TPS for this feature supports an engineered GTT
traffic mix of no more than 70 percent EPAP-based traffic.
Re-enter the command within 30 seconds to confirm change.
CHG-CTRL-FEAT: MASP A - Command Aborted
Command is re-entered within 30 seconds
chg-ctrl-feat:partnum=893018001:status=on
tekelecstp 06-07-26 14:47:58 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893018001:status=on
Command entered at terminal #4.
CHG-CTRL-FEAT: MASP A - COMPLTD
This example shows the output when the 1100 TPS/DSM for
ITU NP feature is on, and the
chg-ctrl-feat command is not
re-entered within 30 seconds:
chg-ctrl-feat:partnum=893018001:status=on
tekelecstp 06-07-26 14:47:49 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893018001:status=on
Command entered at terminal #4.
CAUTION:Rated TPS for this feature supports an engineered GTT
traffic mix of no more than 70 percent EPAP-based traffic.
Re-enter the command within 30 seconds to confirm change.
CHG-CTRL-FEAT: MASP A - Command Aborted
Command is not re-entered within 30 seconds.
CHG-CTRL-FEAT command aborted due to confirmation timeout.
This example shows the output when the 1100 TPS/DSM for
ITU NP feature is not on, and the
chg-ctrl-feat command is re-entered
within 30 seconds for confirmation:
chg-ctrl-feat:partnum=893018001:status=off
tekelecstp 06-07-26 14:47:49 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893018001:status=off
Command entered at terminal #4.
CAUTION: This command decreases the total TPS of the
SCCP system from 1100 to 850 TPS for each DSM.
Re-enter the command within 30 seconds to confirm.
CHG-CTRL-FEAT: MASP A - Command Aborted
Command is re-entered within 30 seconds
chg-ctrl-feat:partnum=893018001:status=off
tekelecstp 06-07-26 14:47:58 EST EAGLE 36.0.0
chg-ctrl-feat:partnum=893018001:status=off
Command entered at terminal #4.
CHG-CTRL-FEAT: MASP A - COMPLTD
chg-db
Use this command to manipulate elements of the database.
Caution:
When this command is entered, all other database operations are locked out while the command executes.Caution:
The cards that run both the active and standby OAM reboot whenever the restore operation completes successfully. When a database is repaired successfully, the card with the standby OAM reboots. This action purges old database data from memory and reloads the MASPs with the new data. When the card with the active OAM reboots, all terminals reinitialize, automatically logging off all users. Depending on the new database, the terminals may be initialized to a different configuration, and user IDs and passwords may change.Parameters
- action (mandatory)
- The database management action.
- Range:
-
- backup
- Copies the database from the current data partitions to the backup partitions on both fixed disks, the backup partition on the removable drive, or to a compressed tar file on a remote FTP server. If the destination is the server a database file with the following naming convention will be created: 'CLLI string' - 'Release number string' - 'yymmddhh'.tar.gz (tekelecstp-37.5.0-08012212.tar.gz)
- repair
- Copies the current and backup databases from the active to the standby fixed disk.
- restore
- Copies the backup partitions to the current data partitions on both fixed disks, or copies the database from the removable drive or the remote FTP server to the current data partitions on both fixed disks.
Caution:
The action=restore parameter initiates an emergency recovery procedure and requires theinit-syscommand to download the restored database to all the cards in the system.
- file (optional)
- The name of the TAR file on the remote server that
contains the database to be restored to the system.
The src=server parameter must be specified before this parameter can be specified.
Example
chg-db:action=backup:dest=server
chg-db:action=restore:src=remove
chg-db:action=repair
chg-db:action=restore:src=server:file="CLLI-37.5.0-08012212.tar.gz"
Dependencies
This command cannot be entered while the system is in upgrade mode.
The removable drive must be accessible and ready and must be formatted as a system removable disk, NOT as a measurement removable disk.
The dest parameter can be specified only when action=backup. If the dest=fixed parameter is specified, or the dest parameter is not specified, the database on the current partition of the fixed disk is copied to the backup partition of the fixed disk. This action is shown in Figure 4-1.
Figure 4-1 chg-db:action=backup:dest=fixed
The current database partition of both fixed disks must be free of integrity violations (for example, incoherency, inconsistency, and data corruption) when action=backup is specified.
Figure 4-2 chg-db:action=restore:src=fixed
The backup database partition of both fixed disks must
be coherent when
chg-db:action=restore:src=fixed is
specified.
The database on the removable drive must be coherent
when
chg-db:action=restore:src=remove is
specified.
The current and backup database partitions of the active fixed disk must be free of integrity violations (for example, incoherency and data corruption) when action=repair is specified.
When the action=repair/restore parameter is specified, the database(s) serving as the source of data for the operation must be free of integrity violations (for example, incoherency and data corruption).
All databases involved in the operation must contain valid database version information.
The action=restore and src=server parameters must be specified before the file parameter can be specified. If the src=server parameter is specified, then the file parameter must be specified.
The action=restore and src=remove parameters must be specified before the sloc parameter can be specified.
The DB application server must be provisioned (see the
ent-ftp-serv command) before the
chg-db:action=backup:dest=server or
chg-db:action=restore:src=server
command can be entered.
An IPSM card must be provisioned before the
chg-db:action=restore:src=server or
chg-db:action=backup:dest=server
commands can be entered.
The standby MASP must be in the Active state before this command can be entered.
If the src=usb or dest=usb parameter is specified, then a flash drive must be inserted into the Active OAM's flush-mounted USB port.
During a restore procedure, if removable drives
installed in the latched USB port on active and standby E5-MASPs have different
DB levels, then the
sloc parameter must be specified in
the
chg-db:action=restore:src=remove
command to specify the removable drive to be used.
The value specified for the file parameter must have the correct extension.
A value of 1113 or 1115 must be specified for the sloc parameter.
The chg-db command cannot be issued when SFAPP(P)->OAM sync is
ON.
This command cannot be entered when CAT2 IPSM to OAM syncing is in progress.
Notes
When the action=backup parameter is specified, the following message appears when an audit is in progress:
Command In Progress: waiting for database audit to complete
The command executes when the audit is finished.
Performance
The performance time to execute this command varies depending on the number of records allocated for the database, system activity, and system setup. These operations should typically take no longer than 30 minutes. If one of these operations exceeds one hour, contact My Oracle Support. See the "My Oracle Support" section in Chapter 1 of this manual.
If the dest=remove parameter is specified, the database on the current partition of the active fixed disk is copied to the removable drive. This action is shown in Figure 4-3.
Figure 4-3 chg-db:action=backup:dest=remove
If the
chg-db:action=restore:src=server:filename=xxxxxx.tar or
chg-db:action=backup:dest=server
command is entered, the database partitions are copied from or to the remote
server application through an
IPSM card. This action is shown in
Figure 4-4.
Figure 4-4 Remote Backup or Restore
If the action=repair parameter is specified, the current and backup database partitions are copied from the active fixed disk to the standby fixed disk. This action is shown in Figure 4-5.
Figure 4-5 chg-db:action=repair
Figure 4-6 chg-db:action=restore:src=remove
If the action=restore and src=remove parameters are specified on the E5-MASP hardware, the database of the removable drive (in the latched USB port) is copied to the current partition of each fixed disk. The default is to use the removable drive in the active E5-MASP. The sloc parameter can be used to specify the removable drive in the active or standby E5-MASP.
If the dest=remove parameter is specified for an E5-MCAP card, the database on the current partition of each fixed disk is copied to the removable drive in both latched USB ports. If only the active OAM has a removable drive, then only the current partition on the active OAM is copied to the removable drive in the active OAM's latched USB port.
If the
chg-db:action=restore:src=usb or
chg-db:action=backup:dest=usb command
is entered, then the database partitions are copied from or to the flash drive
(inserted in the active OAM's flush-mounted USB port). This action is shown in
Figure 4-4.
Output
Messages such as UIMs might appear at your terminal.
chg-db:action=backup
BACKUP (FIXED): MASP B - Backup starts on active MASP.
BACKUP (FIXED): MASP B - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP B - Backup starts on standby MASP.
BACKUP (FIXED): Backup on standby MASP to fixed disk complete.
chg-db:action=restore
RESTORE (FIXED): MASP A - Restore starts on active MASP.
RESTORE (FIXED): MASP A - Restore from fixed disk on active MASP complete.
RESTORE (FIXED): MASP A - Restore starts on standby MASP.
RESTORE (FIXED): MASP A - Restore from fixed disk on standby MASP complete.
RESTORE (FIXED): MASP A - MASP(s) will reboot to load data.
chg-db:action=backup:dest=remove
BACKUP (REMOVABLE) : MASP A - Backup starts on active MASP.
BACKUP (REMOVABLE) : MASP A - Backup to removable media complete.
chg-db:action=backup:dest=fixed
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
chg-db:action=restore:src=remove
RESTORE (REMOVABLE) : MASP A - Restore starts on active MASP.
RESTORE (REMOVABLE) : MASP A - Restore starts on standby MASP.
RESTORE (REMOVABLE) : MASP A - MASP(s) will reboot to load data.
RESTORE (REMOVABLE) : MASP A - Restore from removable media complete.
chg-db:action=restore:src=fixed
RESTORE (FIXED) : MASP A - Restore starts on active MASP.
RESTORE (FIXED) : MASP A - Restore from fixed disk on active MASP complete.
RESTORE (FIXED) : MASP A - Restore starts on standby MASP.
RESTORE (FIXED) : MASP A - MASP(s) will reboot to load data.
RESTORE (FIXED) : MASP A - Restore from fixed disk on stdby MASP complete.
chg-db:action=repair
REPAIR: MASP A - Repair starts on standby MASP.
REPAIR: MASP A - Standby MASP will reboot to load data.
REPAIR: MASP A - Repair from fixed disk complete.
chg-db:action=backup:dest=server
BACKUP (SERVER): MASP A - Backup starts on active MASP.
BACKUP (SERVER) : Copy Database to card memory for processing.
BACKUP (SERVER) : Compress Database before archiving.
BACKUP (SERVER) : Send database archive to server.
BACKUP (SERVER): MASP A - Backup to remote server complete.
chg-db:action=restore:src=server:file="CLLI-37.5.0-08011112.tar.gz"
RESTORE (SERVER) : Retrieve database archive from server.
RESTORE (SERVER) : Validate database archive.
RESTORE (SERVER) : Restore starts on active MASP.
RESTORE (SERVER) : Restore from server on active MASP complete.
RESTORE (SERVER) : Restore starts on standby MASP.
RESTORE (SERVER) : Restore from server on standby MASP complete.
RESTORE (SERVER) : MASP(s) will reboot to load data.
chg-dconn
Use this parameter to change the DEIR connection information. The DCONN table supports the provisioning information related to the Diameter connections.
Parameters
- dcname (mandatory)
- Diameter connection name. This parameter specifies the unique logical name assigned to each diameter connection.
- maxtps (optional)
- Maxmium TPS. This is the maximum TPS for a diameter connection. The unused card capacity will be allocated among the connections that have exceeded their RSVDTPS up to limit of MAXTPS value provisioned for the particular connection.
- rsvdtps (optional)
- Reserved TPS. This is the guaranteed TPS (Transactions per second) for a diameter connection. Total RSVDTPS on a card cannot exceed 8000.
- td (optional)
- Diameter Peer Disconnect timer. This timer is used to control how long the DEIR process will wait for a DPA response (Diameter Peer Answer) to a send DPR (Diameter Peer Request). The value given to a timer is in seconds.
Example
chg-dconn:dcname=conn1:rsvdtps=1000:maxtps=5000:td=5:tw=15
chg-dconn:dcname=conn2:td=6:maxtps=6000
Dependencies
S13/S13' EIR feature must be enabled before changing any parameter of diameter connection.
DCONN table should be accessible.
At least one optional parameter must be specified.
Diameter connection name is not present in DCONN table.
Sum of RSVDTPS of all the diameter connections on a particular card must not exceed the diameter card TPS (8000).
RSVDTPS of a diameter connection must be less than or equal to its MAXTPS.
Notes
None.
Output
chg-dconn:dcname=conn1:rsvdtps=1000:maxtps=5000:td=5:tw=15
tekelecstp 13-03-20 15:44:10 EST EAGLE 45.1.0
chg-dconn:dcname=conn1:rsvdtps=1000:maxtps=5000:td=5:tw=15
Command entered at terminal #4.
CHG-DCONN: MASP A - COMPLTD
;
chg-deiropts
Use this command to change the S13/S13' EIR configuration. This command updates the DEIROPTS (Diameter Options) table.
Parameters
- applid (optional)
- Authentication Application ID. The application id configured should match with the Auth-Application-Id (AVP Code 258) value in Vendor-Specific-Application-ID AVP. This value is fixed to 16777252 and cannot be changed.
- congerr (optional)
- This parameter defines the diameter response to be sent by the DEIRHC card at the time of card congestion. If the card fails in processing the incoming messages, then it shall discard the message and respond with the error code.
- deirdfltimsilkup (optional)
- Diameter Equipment Identity Register (EIR) default IMSI lookup status. This parameter specifies the order of IMEI table lookup for default IMSI screening. This parameter is analogous to the P1 parameter in the IMSIPFX CSL list but is used only when there is no matching IMSI prefix in the IMSIPFX CSL.
- deirdfltimsiresp (optional)
- Diameter Equipment Identity Register (EIR) default IMSI response. This parameter specifies the default IMEI status for default IMSI screening. This parameter is analogous to the P2 parameter in the IMSIPFX CSL list but is used only when there is no matching IMSI prefix in the IMSIPFX CSL.
- deirrsptype (optional)
- Diameter Equipment Identity Register (EIR) Response Type. The Response Type is used to determine how the lists are to be searched.
EIR Response Type Values contains information to help select the value for this parameter.
Presence in List EIR Response Type (Equipment Status) White Gray Black Type 1 Type 2 Type 3 X in white list in white list in white list X X in gray list in gray list in gray list X X X in black list in black list in black list X X in black list in black list in black list X in gray list in gray list unknown X X in black list in black list unknown X in black list in black list unknown in white list * Unknown* unknown * *Indicates no match was found for the IMEI in an incoming message within the database.
- off (optional)
- This parameter turns off the specified options. Up to 8 comma-separated unique options can be specified.
- on (optional)
- This parameter turns on the specified options. Up to 8 comma-separated unique options can be specified.
Example
chg-deiropts:on=deirimsichk:deirrsptype=type2:product=abc123
chg-deiropts:deirgrsp=off:off=deirimsichk:dprcause=1
chg-deiropts:dprcause=0
chg-deiropts:on=deirimsiscrn,deirlogwl,deirdfltimsiscrn,deirimsichk
chg-deiropts:off=deirimsiscrn,deirlogwl,deirdfltimsiscrn,deirimsichk
chg-deiropts:deirdfltimsilkup=range
chg-deiropts:deirdfltimsiresp=whitelist
Dependencies
The S13 feature must be enabled before changing any DEIR configuration.
The DEIROPTS table should be accessible.
At least one optional parameter must be specified.
The product name must be alphanumeric.
The S13 Application ID cannot be changed.
The same value cannot be specified for the on and off parameters.
- deirimsiscrn --- Specifies whether the IMSI Screening for Diameter Equipment Identity Register (EIR) shall be done before the IMEI check. This option has a default of OFF.
- deirlogwl --- Specifies whether the white list logging for Diameter Equipment Identity Register (EIR) shall be on. This option has a default of OFF.
- deirdfltimsiscrn --- Specifies whether the default IMSI Screening for Diameter Equipment Identity Register (EIR) shall be on. This option has a default of OFF.
- deirimsichk --- Specifies the use of Diameter Equipment Identity Register (EIR) IMSI Check status. It specifies whether IMSI lookup shall be performed along with IMEI for blklst numbers. This option has a default of OFF.
Output
chg-deiropts:on=deirimsichk:deirrsptype=type2
tekelecstp 13-04-13 17:25:00 EST EAGLE 45.1
chg-deiropts:on=deirimsichk:deirrsptype=type2
Command entered at terminal #4.
CHG-DEIROPTS: MASP A – COMPLTD
;
Related Topics
chg-dstn
Use this command to change the characteristics of the point codes that are considered destinations from this signal transfer point (STP). A destination does not have to be an adjacent signaling point, but the system must be able to route traffic to this destination.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- dpc (optional)
- ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- dpca
- Range:
- p-, 000-255, *
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
The asterisk value (*) is not valid for the ni subfield.
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- dpci (optional)
- ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- dpcn (optional)
- ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- dpcn24 (optional)
- 24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).
- dpcn16 (optional)
- 16-bit ITU national point code with subfields unit number, sub number area, main number area (un-sna-mna). The prefix indicates a private point code (prefix-un-sna-mna).
- aliasa (optional)
- ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Range:
- 000-255, none
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.Enter none to delete the point code.
The point code 000-000-000 is not a valid point code.
- aliasi (optional)
-
ITU international alias point code list with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
If an ITU international destination (dpci) point code is entered, the dpci and aliasi prefix subfields cannot be the same, (both spare or both non-spare). Up to 2 comma-delimited entries can be entered in the point code list.
- aliasn (optional)
-
ITU national alias point code list in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).If an ITU national destination (dpcn) point code is entered, then the dpcn and aliasn prefix subfields cannot be the same (both spare or both non-spare). Up to 2 comma-delimited entries can be entered in the point code list.
- aliasn24 (optional)
- 24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- aliasn16 (optional)
- 16-bit ITU national destination point code with subfields unit number, sub number area, main number area (un-sna-mna).
- bei (optional)
- Broadcast exception indicator. This parameter specifies whether the STP broadcasts network management messages to adjacent signaling points. The network management messages contain information about the indicated cluster and any of that cluster’s member signaling points that are on its exception list. The messages whose broadcast is determined by this parameter are:
- TFP—Transfer Prohibited
- TCP—Transfer Cluster Prohibited
- TFA—Transfer Allowed
- TCA—Transfer Cluster Allowed
- elei (optional)
- Exception-list exclusion indicator, for cluster destinations only. This parameter specifies whether the system excludes or includes (maintains) a dynamic status exception list (x-list) for each cluster route used to reach the member signaling points that make up the cluster.
- homescp (optional)
-
This parameter specifies whether the destination point code is considered a Home SCP when performing SCCP processing for messages with no Global Title Address Digits (Global Title Indicator (GTI) is set to zero).
This parameter can only be set to "yes" for full DPCs.
- homesmsc (optional)
-
This parameter specifies whether the DPC is considered a Home SMSC when performing SCCP processing for messages with no Global Title Address Digits (GTI is set to zero).
This parameter can only be set to "yes" for full DPCs.
- ncai (optional)
- Nested cluster allowed indicator. Specifies whether the route to the cluster point code can be different for provisioned members of the cluster. A point code is a member of a cluster point code if it has the same network identifier (NI) and network cluster (NC) values as the cluster point code. This parameter can only be specified for cluster point codes. Nested cluster routing is allowed if this parameter is set to yes and the CRMD and NCR features are turned on.
- Range:
-
- yes
- The cluster point code is a nested cluster point code. Point codes that are members of this cluster point code can be assigned to route sets that are different from the route set assigned to the cluster point code.
- no
- The cluster point code is not a nested cluster point code. Point codes that are members of this cluster point code must be assigned to the same route set assigned to the cluster point code.
- Default:
- Current value.
- nprst (optional)
- NM bits reset. This parameter specifies whether the NM bits should be set to00.
This parameter applies only to ITU IAM messages. The nptype=nm parameter must be specified (see the
chg-tifoptscommand) before this parameter can be specified.
- prx (optional)
- Proxy point code indicator. This parameter specifies whether a destination point code is used as a proxy point code.
- rcause (optional)
- Release cause. The value to be used as the release cause on REL messages.
If the TIFOPTS rlcopc parameter is specified (see the
chg-tifoptscommand), and a value of 0 - 127 is specified for the rcause parameter, then the rcause parameter value overrides the values specified for the TIFOPTS rcausenp and rcausepfx parameters.
- sccpmsgcnv (optional)
- SCCP UDT(S)/XUDT(S) Message Conversion Indicator. The type of conversion performed on messages for the specified destination.
- Range:
-
- none
- conversion is not required on messages for the destination
- udt2xudt
- convert all UDT(S) messages for the destination to XUDT(S) messages
- xudt2udt
- convert all non-segmented XUDT(S) messages for the destination to UDT(S) messages
- sxudt2udt
- convert all segmented and non-segmented XUDT(S) messages for the destination to UDT(S) messages
- Default:
- No change to the current value
- spc (optional)
- ANSI secondary point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- spca
- Range:
-
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
p-, 000-255, none
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid for ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.Enter none to delete the point code.
The point code 000-000-000 is not a valid point code.
- Default:
- No change to current value
- spci (optional)
- ITU international secondary point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- Range:
- s-, p-, ps-, 0-255, none
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—s-, p-, ps
zone—0-7
area—000-255
id—0-7
The point code 0-000-0 is not a valid point code.
Enter none to delete the point code.
- Default:
- No change to current value
- spcn (optional)
- ITU national secondary point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).- Range:
- s-, p-, ps-, 0-16383, aa-zz, none
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—s-, p-, ps
nnnnn—0-16383
gc—aa-zz
m1-m2-m3-m4—0-14 for each member; values must sum to 14
Enter none to delete the point code.
- Default:
- No change to current value
- spcn24 (optional)
- 24-bit ITU national secondary point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).
- spcn16 (optional)
- 16-bit ITU national secondary point code with subfields unit number, sub number area, main number area (un-sna-mna). The prefix subfield indicates a private point code (prefix-un-sna-mna).
- splitiam (optional)
-
This parameter specifies when and how to split an ITU IAM message into 1 IAM message + 1 SAM message.
Note:
This parameter applies only to ITU IAM messages.- Range:
- 15-31, none
15 - 31 -Maximum number of CdPN digits allowed in the IAM message before splitting occurs. The remaining digits, up to a total of 32, are encoded in the SAM message.
none -use the value specified for the TIFOPTS splitiam parameter to determine when to split the IAM message
- Default:
- No change to the current value
Example
To change the CLLI of destination 111-222-111 to RLGHNCXA01A:
chg-dstn:dpc=111-222-111:clli=rlghncxa01aTo change the exception-list exclusion indicator for cluster 20-2-* to yes:
chg-dstn:dpca=20-2-*:elei=yesTo change an existing destination to contain an SPC:
chg-dstn:dpc=20-2-2:spc=5-5-5To change Nested Cluster Allowed Indicator for cluster 20-2-* to yes:
chg-dstn:dpc=20-2-*:ncai=yesTo change a network destination:
chg-dstn:dpc=25-*-*:clli=tklcTo change the BEI parameter value of ITU national destination 8111-aa to yes:
chg-dstn:dpcn=8111-aa:bei=yesTo change the BEI parameter value of 24-bit ITU-N destination 15-100-10 to yes:
chg-dstn:dpcn24=15-100-10:bei=yesTo change an existing 24-bit ITU-N destination to contain a 24-bit ITU-N SPC:
chg-dstn:dpcn24=12-12-12:spcn24=25-25-25To change ITU-I spare destination point code s-2-100-1 to contain an ITU-I spare secondary point code, ANSI alias, and ITU-N spare alias:
chg-dstn:dpci=s-2-100-1:spci=s-2-129-9:aliasa=121-120-120:aliasn=s-129To prevent a destination point code from being used as a proxy point code:
chg-dstn:dpc=11-11-11:prx=noTo change ITU-N destination point code 10805-nz to delete its ANSI alias and add both ITU-I spare and non-spare aliases:
chg-dstn:dpcn=10805-nz:aliasa=none:aliasi=s-5-80-0,5-80-1To change ITU-I spare destination point code s-5-60-3 to add ITU-N non-spare and spare aliases:
chg-dstn:dpci=s-5-60-3:aliasn=10723-gr,s-10723-grTo change ITU-I spare destination point code s-5-60-5 to add ITU-N spare and ITU-I non-spare aliases:
chg-dstn:dpci=s-5-60-5:aliasn=s-10725-gr:aliasi=5-60-5To change sccpmsgcnv type to udt2xudt for destination 11:
chg-dstn:dpc=11-11-11:sccpmsgcnv=udt2xudtDependencies
Note:
A full point code contains numerical values for all three segments of the point code.At least one optional parameter must be specified.
The specified destination point code value must already be defined in the Destination point code table.
The destination address must be a full point code, a network destination, or a cluster point code.
The ANSI self-ID destination point code for the STP must be defined before ANSI destinations can be changed.
The ITU-I self-ID destination point code for the STP must be defined before ITU-I destinations can be changed.
The ITU-N self-ID destination point code for the STP must be defined before ITU-N destinations can be changed.
The Spare Point Code Support feature must be enabled before the spare point code prefix s- can be specified for an ITU-I or ITU-N destination, secondary, or alias point code.
If the dpcn or aliasn parameter is specified, the format must match the format that was assigned with the chg-stpopts:npcfmti parameter.
If the 7000 Routesets or 8000 Routesets feature is enabled, then the total number of provisioned aliases in the system cannot exceed 8000. If the 10,000 Routesets feature is enabled, then the total number of provisioned aliases in the system cannot exceed 10000.
Alias point codes are allowed only for full point code destinations.
Alias point codes for destinations must be full point codes.
A specified alias type cannot already be defined as a destination address.
The aliasa and dpca parameters cannot be specified together in the command. The aliasi and dpci parameters and the aliasn and dpcn parameters cannot be specified together in the command if the prefix subfields are the same (both are spare or both are non-spare).
Alias ANSI point codes cannot be members of a cluster or network destination.
The specified alias network type must be different from the destination point code network type.
A 24-bit ITU-N point code cannot have a 14-bit ITU-N alias point code or an ANSI alias point code.
A 24-bit ITU-National point code can have an ITU-I point code alias. This allows conversion of 14-bit ITU-I routing label to 24-bit routing label and vice versa.
A 14-bit ITU-N point code cannot have a 24-bit ITU-N alias point code.
If an ITU-I point code is specified, either the aliasn or the aliasn24 parameter can be specified, but not both.
Cluster destinations are allowed only if the CRMD feature is turned on.
The ncai parameter can be specified only for cluster destinations.
The elei parameter can be specified only for cluster destinations (for example, dpc=ni-nc-*).
The NCR (Nested Cluster Routing) feature must be turned on before the ncai parameter can be specified.
Network routing is valid only if the Network Routing (NRT) feature is turned on.
When using network routing, if the destination point code has a value of * in the nc subfield, the ncm subfield must also be * (for example, dpc=21-*-*).
If a provisioned nested cluster point code is being changed to a non-nested cluster point code (ncai=no), previously provisioned members of the cluster must have the same route set.
If a provisioned non-nested cluster point code is being changed to a nested cluster point code (ncai=yes), the maximum number of provisioned nested clusters must be no greater than 500.
If specified, the spc parameter value must be already be configured as a secondary point code in the Secondary Point Code table.
The value specified for the spc parameter must be a full point code.
If the spc parameter is specified, the domain=ss7 parameter must be specified.
If the spc parameter is specified, then the value specified for the dpc parameter must be a full point code.
The network type of the value specified for the spc parameter must match the network type of the value specified for the dpc parameter.
If a new CLLI for the destination point code is specified, it cannot match the CLLI of the system.
If the corresponding destination for the specified destination point code is an adjacent signaling point (matched a Far End point code in its linkset entity set), the CLLI of the specified destination point code cannot be assigned to any other destination address.
A reserved word cannot be specified for the destination identifier (CLLI).
If the destination does notuse an SPC, the group code of the destination must be the same as the group code of the ITU national true point code. If the destination uses an SPC, then the group code of the destination must match the group code of the SPC.
If an ITU national destination is being changed and the ITUDUPPC feature is turned on, this applies depending on whether the destination uses an SPC (secondary point code). For example, if the ITU national true point code has a group code of ee, then destinations with group codes of ee can be added without using an SPC. Destinations with a group code of ff must use an SPC with a group code of ff.
The Route table is corrupt or cannot be found.
The STP Self-identity table is corrupt or cannot be found.
The ICNP feature must be enabled and turned on in order to specify the icnpxlat, cgpafmt, and cdpafmt parameters.
Alias point codes cannot already be defined as another destination.
The value specified for the spc parameter cannot already be specified as a secondary point code for the destination point code.
The Linkset table is corrupt or cannot be found.
The Proxy Point Code feature must be enabled before the prx parameter can be specified.
If the prx=yes parameter is specified, then the value of the dpc parameter must be a full point code.
If the value of the dpc parameter is used as a proxy point code, then the prx=no parameter cannot be specified.
The number of proxy destinations cannot exceed the value allowed by the enabled Proxy Point Code quantity feature.
If the prx=yes parameter is specified, then the spc/spca/spci/spcn/spcn24 parameter cannot be specified.
The prx parameter must have a value of yes or no.
If the value specified for the dpc parameter is a private point code, then the prx=yes parameter cannot be specified.
The total number of proxy destinations cannot exceed the total capacity (100) of the Proxy Point Code feature.
If an IPGW linkset is used, then the prx=yes parameter cannot be specified.
The network type of the routeset must be the same as the network type of the destination point code. For example, a destination point code with an ANSI network type cannot use a routeset with an ITU network type.
If the specified destination point code is assigned a proxy point code (PPC) in the DSTN table, then the specified routeset must contain a linkset for the destination point code, and the PPC of the linkset must be equal to the PPC of the destination point code.
The value specified for the spc parameter must differ from the secondary point code of the destination/route entry specified by the dpc parameter.
The value specified for the ncai parameter cannot be same as the NCAI that is already assigned to the destination point code.
If the specified destination point code is a cluster or network destination point code, then the specified routeset cannot contain a route over proxy linksets.
If the destination point code and adjacent point code of the routes in the specified routeset are ITU point codes, then the following conditions must apply.
- If one point code is an ITUI point code, and the other is an ITUN or ITUN24 point code, then the network type of the secondary adjacent point code must match the network type of the destination point code.
- If both point codes have the same network type, then either both must be spare point codes or both must not be spare point codes.
- If the destination point code is an ITUN point code, and the ITUDUPC feature is turned on, then the group code of the destination point code must match the adjacent or the secondary adjacent point code.
A maximum of two aliases can be specified per destination.
If the dpci parameter is specified, then a combination of ITUI and ANSI aliases cannot be specified. If the dpcn parameter is specified, then a combination of ITUN and ANSI aliases cannot be specified.
Two ITUI or two ITUN aliases can be specified for the same destination point code only if the aliases have different prefixes. One alias must be spare and one non-spare.
The TIF Number Portability feature must be enabled before the rcause or nprst parameter can be specified.
A TIF feature must be enabled before the splitiam parameter can be specified.
The XUDT UDT Conversion feature must be turned on before the sccpmsgcnv parameter can be specified.
The J7 Support feature must be enabled before the aliasn16 parameter can be specified.
If the J7 Support feature is enabled then aliasa and aliasn24 cannot be specified.
Notes
One of dpc/dpca/dpci/dpcn/dpcn24/dpcn16 is mandatory and they are mutually exclusive.
Only one of aliasa/aliasi/aliasn/aliasn24/aliasn16 can be specified as they are mutually exclusive.
Only one of spc/spca/spci/spcn/spcn24/spcn16 can be specified as they are mutually exclusive.
The domain parameter of a destination cannot be changed with this command. To change the domain parameter, the destination must be removed with the dlt-dstn command and re-entered with the ent-dstn command.
In this command, only ITU-international and ITU national point codes and aliases support the spare point code subtype prefix (s-). Only ITU-international and ITU national point codes support the private and spare point code subtype prefix (ps-). All of the point code types support the private (internal) point code subtype prefix (p-). Aliases do not support the private (internal) point code prefix.
The value specified for the DPC parameter must be a full point code in order to be used as a proxy point code. Cluster point codes and private point codes cannot be used as proxy point codes.
Invalid usage of none with aliasi and aliasn:
- alias=none,none: parser code expects none to be the last argument
- alias=none,pointcode: parser code expects none to be the last argument
- alias=,pointcode: invalid usage of comma separator
Alias Combination Matrix
Table 4-5 Alias Combination Matrix
| specified | result | ||||
|---|---|---|---|---|---|
| Destination | aliasN/aliasN24 | alias1 | aliasA/aniasN16 | alias1 | alias2 |
| ANSI | none | 0 | |||
| pci | pci | ||||
| none | 0 | ||||
| pcn | pcn | ||||
| pcn24 | pcn24 | ||||
| none | none | 0 | 0 | ||
| none | pci | pci | 0 | ||
| pcn | none | 0 | pcn | ||
| pcn24 | none | 0 | pcn24 | ||
| pcn | pci | pci | pcn | ||
| pcn24 | pci | pci | pcn24 | ||
| ITUI | none | 0a | |||
| pca | pca | ||||
| none | 0i | ||||
| pci | pci | ||||
| none | none | 0a, i | |||
| none | pca | pca | |||
| pci | none | pci | |||
| pci | pca | E5074 | |||
| none | 0n | 0 | |||
| pcn | 0n | pcn | |||
| pcn, none | 0n | pcn | |||
| pcn1, pcn2 | pcn2 | pcn1 | |||
| pcn24 | pcn24 | ||||
| none | none | 0a, n | 0 | ||
| none | pca | pca | 0 | ||
| pcn | none | 0a, n | pcn | ||
| pcn | pca | pca | pcn | ||
| pcn, none | none | 0a, n | 0 | ||
| pcn, none | pca | 0a, n | pcn | ||
| pc1, pcn2 | none | pcn1 | pcn2 | ||
| pcn1, pcn2 | pca | E5001 | |||
| pcn24 | none | 0a | pcn24 | ||
| pcn24 | pca | pca | pcn24 | ||
| none | none | 0i, n | 0 | ||
| none | pci | pci | 0 | ||
| pcn | none | 0i, n | pcn | ||
| pcn | pci | pci | pcn | ||
| pcn1, none | none | 0i, n | pcn | ||
| pcn1, none | pci | pci | pcn | ||
| pcn1, pcn2 | none | pcn2 | pcn1 | ||
| pcn1, pcn2 | pci | E5001 | |||
| pcn24 | none | 0i | pcn24 | ||
| pcn24 | pci | pci | pcn24 | ||
| none | none | none | 0a, i, n | 0 | |
| none | none | pca | pca | 0 | |
| none | pci | none | pci | 0 | |
| none | pci | pca | E5074 | ||
| pcn | none | none | 0a,i,n | pcn | |
| pcn | none | pca | pca | pcn | |
| pcn | pci | none | pci | pcn | |
| pcn | pci | pca | E5001 | ||
| pcn, none | none | none | 0a,i,n | pcn | |
| pcn, none | none | pca | pca | pcn | |
| pcn, none | pci | none | pci | pcn | |
| pcn, none | pci | pca | E5001 | ||
| pcn2, pcn1 | none | none | pcn2 | pcn1 | |
| pcn2, pcn1 | none | pca | E5001 | ||
| pcn2, pcn1 | pci | none | E5001 | ||
| pcn2, pcn1 | pci | pca | E5001 | ||
| pcn24 | none | none | 0a,i | pcn24 | |
| pcn24 | none | pca | pca | pcn | |
| pcn24 | pci | none | pca | pcn | |
| pcn24 | pci | pca | E5001 | ||
| pcn16 | pcn16 | ||||
| none | pcn16 | pcn16 | |||
| pci | pcn16 | E2325 | |||
| none | pci | pcn16 | E2325 | ||
| none | pcn16 | pcn16 | |||
| pcn | pcn16 | pnc16 | pcn | ||
| pcn | none | pcn16 | pcn16 | pcn | |
| pcn, none | pcn16 | pcn16 | pcn | ||
| pcn1,pcn2 | pcn16 | E5001 | |||
| none | none | pcn16 | E5074 | ||
| pcn, none | none | pcn16 | pcn16 | pcn | |
| pcn2,pcn1 | none | pcn16 | E5001 | ||
| ITUN | none | 0a | |||
| pca | pca | ||||
| none | 0 | ||||
| pci | pci | ||||
| pci, none | 0 | pci | |||
| pci1, pci2 | pci2 | pci1 | |||
| none | none | 0a,i | 0 | ||
| none | pca | pca | 0 | ||
| pci | none | 0,a | pci | ||
| pci | pca | pca | pci | ||
| pci, none | none | 0,a,i | pci | ||
| pci, none | pca | pca | pci | ||
| pci1, pci2 | none | pci2 | pci1 | ||
| pci1, pci2 | pca | E5001 | |||
| none | 0,n | ||||
| pcn | pcn | ||||
| pcn24 | pcn24 | ||||
| none | none | 0,a,n | |||
| none | pca | pca | |||
| pcn | none | pcn | |||
| pcn | pca | E5074 | |||
| pcn24 | none | pcn24 | |||
| pcn24 | pca | E5074 | |||
| none | none | 0,i,n | 0 | ||
| none | pci | 0,i,n | pci | ||
| none | pci, none | 0,i,n | pci | ||
| none | pci1, pci2 | pci2 | pci1 | ||
| pcn | none | pcn | 0 | ||
| pcn | pci | pcn | pci | ||
| pcn | pci, none | pcn | pci | ||
| pcn | pci1, pci2 | E5001 | |||
| pcn24 | none | pcn24 | 0 | ||
| pcn24 | pci | pcn24 | pci | ||
| pcn24 | pci | none | pcn24 | pci | |
| pcn24 pci1, pci2 | E5001 | ||||
| none | none | none | 0a,i,n | 0 | |
| none | none | pca | pca | 0 | |
| none | pci | none | 0a,i,n | pci | |
| none | pci | pca | pca | pci | |
| none | pci, none | none | 0a,i,n | 0 | |
| none | pci, none | pca | pca | pci | |
| none | pci1, pci2 | none | pci2 | pci1 | |
| none | pci1, pci2 | pca | E5001 | ||
| pcn | none | none | pcn | 0 | |
| pcn | none | pca | E5074 | ||
| pcn | pci | none | pcn | pci | |
| pcn | pci | pca | E5001 | ||
| pcn | pci, none | none | pcn | pci | |
| pcn | pci, none | pca | E5001 | ||
| pcn | pci1, pci2 | none | E5001 | ||
| pcn | pci1, pci2 | pca | E5001 | ||
| pcn24 | none | none | pcn24 | 0 | |
| pcn24 | none | pca | E5074 | ||
| pcn24 | pci | none | pcn24 | pci | |
| pcn24 | pci | pca | E5001 | ||
| pcn24 | pci, none | none | pcn24 | pci | |
| pcn24 | pci, none | pca | E5001 | ||
| pcn24 | pci1, pci2 | none | E5001 | ||
| pcn24 | pci1, pci2 | pca | E5001 | ||
| pcn16 | pcn16 | ||||
| none | pcn16 | pcn16 | |||
| pci, none | pcn16 | pcn16 | |||
| pci | pcn16 | pcn16 | pci | ||
| pci1,pci2 | pcn16 | E5001 | |||
| none | none | pcn16 | pcn16 | 0 | |
| none | pci | pcn16 | pcn16 | pci | |
| none | pci, none | pcn16 | pcn16 | pci | |
| none | pci1,pci2 | pcn16 | E5001 | ||
| pcn | pci | pcn16 | E2325 | ||
| pcn | none | pcn16 | E5074 | ||
| pcn | pci, none | pcn16 | E5001 | ||
| ITUN24 | none | 0 | |||
| pca | pca | ||||
| none | none | ||||
| pci | pci | ||||
| none | none | 0 | 0 | ||
| none | pca | pca | 0 | ||
| pci | none | 0 | pci | ||
| pci | pca | pca | pci | ||
| ITUN16 | - | none | - | 0 | - |
| - | pci | - | pci | - | |
| none | - | 0 | |||
| pcn | - | - | pcn | ||
| none | pci | - | pci | 0 | |
| none | none | - | pci | 0 | |
| pcn | none | - | 0 | pcn | |
| pcn | pci | - | pci | pcn | |
Legend
0—clear alias if provisioned regardless of its point code type
0A—clear alias if provisioned and point code is ANSI
0I—clear alias if provisioned and point code is ITUI
0N—clear alias if provisioned and point code is ITUN
0A,I—clear alias if provisioned and point code is ANSI or ITUI
0A,N—clear alias if provisioned and point code is ANSI or ITUN
0I,N—clear alias if provisioned and point code is ITUI or ITUN
0A,I,N—clear alias if provisioned and point code is ANSI or ITUI or ITUN
Output
This example shows the output when the NCR, NRT, and CRMD features are off and all Routes and Routesets features are off:
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-17 15:35:05 EST EAGLE 31.8.0
Destination table is (10 of 2000) 1% full
Destination table is (10 of 2000) 1% full
Alias table is (8 of 12000) 1% full
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when the NCR, NRT, and CRMD features are off and the 5000 Routes feature is on:
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-18 08:29:15 EST EAGLE 31.8.0
Destination table is (10 of 5000) 1% full
Alias table is (8 of 12000) 1% full
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when one or more of the NCR, NRT, or CRMD features and the DSTN5000 (5000 Routes) feature is on:
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-18 08:29:15 EST EAGLE 31.8.0
DESTINATION ENTRIES ALLOCATED: 5000
FULL DPC(s): 9
NETWORK DPC(s): 0
CLUSTER DPC(s): 1
TOTAL DPC(s): 10
CAPACITY (% FULL): 1%
ALIASES ALLOCATED: 12000
ALIASES USED: 8
CAPACITY (% FULL): 1%
X-LIST ENTRIES ALLOCATED: 500
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when the NCR, NRT, and CRMD features are off and the 6000 Routesets feature is on:
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-18 08:29:15 EST EAGLE 31.8.0
Destination table is (60 of 6000) 1% full
Alias table is (8 of 12000) 1% full
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when one or more of the NCR, NRT, or CRMD features and the 6000 Routesets feature is on:
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-18 08:29:15 EST EAGLE 31.8.0
DESTINATION ENTRIES ALLOCATED: 6000
FULL DPC(s): 46
NETWORK DPC(s): 1
CLUSTER DPC(s): 1
TOTAL DPC(s): 12
CAPACITY (% FULL): 1%
ALIASES ALLOCATED: 12000
ALIASES USED: 8
CAPACITY (% FULL): 1%
X-LIST ENTRIES ALLOCATED: 500
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when the NCR, NRT, and CRMD features are off. When the 7000 Routesets quantity feature is on, the Destination table line shows "...of 7000". When the 8000 Routesets quantity feature is on, the Destination table line shows "...of 8000."
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-18 08:29:15 EST EAGLE 31.8.0
Destination table is (60 of 7000) 1% full
Alias table is (8 of 8000) 1% full
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when one or more of the NCR, NRT, or CRMD features is on. When the 7000 Routesets quantity feature is on, the DESTINATION ENTRIES ALLOCATED line shows "8000". When the 7000 Routesets quantity feature is on, the DESTINATION ENTRIES ALLOCATED line shows "7000."
chg-dstn:dpca=111-222-111:aliasn=321
rlghncxa03w 04-08-18 08:29:15 EST EAGLE 31.8.0
DESTINATION ENTRIES ALLOCATED: 8000
FULL DPC(s): 9
NETWORK DPC(s): 0
CLUSTER DPC(s): 1
TOTAL DPC(s): 10
CAPACITY (% FULL): 1%
ALIASES ALLOCATED: 8000
ALIASES USED: 8
CAPACITY (% FULL): 1%
X-LIST ENTRIES ALLOCATED: 500
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when one or more of the NCR, NRT, or CRMD features is on. In this example, a destination is defined as a proxy point code:
chg-dstn:dpc=1-1-1:prx=yes
tekelecstp 07-03-05 17:34:18 EST EAGLE 37.5.0
DESTINATION ENTRIES ALLOCATED: 2000
FULL DPC(s): 27
EXCEPTION DPC(s): 0
NETWORK DPC(s): 1
CLUSTER DPC(s): 1
PROXY DPC(s): 1
TOTAL DPC(s): 30
CAPACITY (% FULL): 2%
ALIASES ALLOCATED: 12000
ALIASES USED: 0
CAPACITY (% FULL): 0%
X-LIST ENTRIES ALLOCATED: 500
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when the secondary point code is changed:
chg-dstn:dpc=1-1-1:spc-144-23-48
tekelecstp 07-03-05 17:34:18 EST EAGLE 37.5.0
CAUTION: Dstn's SPC has changed - verify remote node's route.
DESTINATION ENTRIES ALLOCATED: 2000
FULL DPC(s): 27
EXCEPTION DPC(s): 0
NETWORK DPC(s): 1
CLUSTER DPC(s): 1
PROXY DPC(s): 1
TOTAL DPC(s): 30
CAPACITY (% FULL): 2%
ALIASES ALLOCATED: 12000
ALIASES USED: 0
CAPACITY (% FULL): 0%
X-LIST ENTRIES ALLOCATED: 500
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when the NCR, NRT, and CRMD features are off and the 10,000 Routesets feature is on:
chg-dstn:dpca=11-22-11:aliasn=321
rlghncxa03w 10-08-17 08:29:15 EST EAGLE 43.0.0
Destination table is (10 of 10000) 1% full
Alias table is (8 of 10000) 1% full
CHG-DSTN: MASP A - COMPLTD
;
This example shows the output when one or more of the NCR, NRT, or CRMD features and the 10,000 Routesets feature is on:
chg-dstn:dpca=11-22-11:aliasn=321
rlghncxa03w 10-08-17 08:29:15 EST EAGLE 43.0.0
DESTINATION ENTRIES ALLOCATED: 10000
FULL DPC(s): 9
NETWORK DPC(s): 0
CLUSTER DPC(s): 1
TOTAL DPC(s): 10
CAPACITY (% FULL): 1%
ALIASES ALLOCATED: 10000
ALIASES USED: 8
CAPACITY (% FULL): 1%
X-LIST ENTRIES ALLOCATED: 500
CHG-DSTN: MASP A - COMPLTD
;
This command shows the output when J7 Support feature is enabled.
chg-dstn:dpcn16=1-1-1:aliasi=2-2-4
tekelecstp 13-02-27 14:39:25 EST 45.0.0-64.56.0
chg-dstn:dpcn16=1-1-1:aliasi=2-2-4
Command entered at terminal #4.
Destination table is (2 of 2000) 1% full
Alias table is (1 of 12000) 1% full
CHG-DSTN: MASP A - COMPLTD
;
chg-e1
Use this command to change an interface for an E1 card in the system. An E1 card can consist of an E5-E1T1-B card used as an E1 or SE-HSL card.
Parameters
- e1port (mandatory)
- E1 port number. The value must be an E1 port that has already been configured with an E1 interface on the specified E1 card.
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
- minsurate (optional)
- Minimum signal unit rate. The minimum number of SUs present on a link that are uniformly distributed.
Example
chg-e1:loc=1205:e1port=1:crc4=off:cas=on:encode=hdb3:si=2:sn=12
chg-e1:loc=1205:e1port=2:encode=ami
chg-e1:loc=1205:e1port=1:minsurate=1000
chg-e1:loc=1201:e1port=2:e1tsel=external
Dependencies
At least one optional parameter must be specified.
The specified card location (loc parameter) must be equipped.
The card specified by the loc parameter must be a LIME1 card type.
The port specified by the e1port parameter must already be equipped with an E1 interface.
If the value specified for the loc parameter indicates an E1 card, then all signaling links that are serviced by the card must be deactivated (see the dlt-slk command) before the values for the crc4, cas, encode, and e1tsel parameters can be changed.
The encode=ami parameter is supported only for cards used as E1 cards (not as SE-HSL cards).
The linkclass=unchan parameter must be specified before the minsurate parameter can be specified.
The E1/T1 table must be accessible.
The Card table must be accessible.
HIPR2 cards must be equipped in card locations xy09 and xy10 (x is the frame, y is the shelf) on each EAGLE shelf that contains one or more E5-E1T1-B cards.
The Shelf FAN bit must be turned ON for the shelf on which an E5-E1T1-B card is being used as an E1 or SE-HSL card.
Card locations 1113 - 1118 (E5-MASP and E5-MDAL cards) cannot be specified as values for the loc parameter.
Locations xy09 and xy10, where x is the frame and y is the shelf, cannot be specified as values for the loc parameter.
Notes
External timing is derived from the EAGLE High-Speed Master Clock (1.544 MHz for T1 or 2.048 MHz for E1); therefore, the Master Timing feature is required. Line timing is derived from its received data stream, if present.
Output
chg-e1:loc=1205:e1port=2:encode=ami
rlghncxa03w 04-01-20 09:07:58 EST EAGLE 31.3.0
CHG-E1: MASP A - COMPLTD
;
chg-eisopts
Use this command to enable and disable the copy functions that are associated with the EAGLE 5 Integrated Monitoring Support (E5IS) feature.
Parameters
- fcgpl (optional)
- This parameter applies the functionality specified by the fcmode parameter to cards running the specified Fast Copy GPL.
Example
chg-eisopts:eiscopy=on
chg-eisopts:fcmode=fcopy:fcgpl=all
Dependencies
At least one parameter must be specified.
The E5IS feature must be turned on before this command can be entered
The NETOPTS table must be accessible.
Before the E5IS copy function can be enabled, at least 2 STC cards must be installed and in the IS-NR state in the system.
The eiscopy=on parameter must be specified before a value of stc or fcopy can be specified for the fcmode parameter.
The fcmode=off parameter must be specified before the eiscopy=off parameter can be specified and before the value of the fcmode parameter can be changed between stc and fcopy .
At least one card must be running the IPSG GPL and must be in the IS-NR state before a value of ipsg or all can be specified for the fcgpl parameter.
If the fcgpl parameter is specified, then the fcmode parameter must be specified.
The host portion of the PVN network address must
be 0 based on the PVN subnet mask (see the
chg-netopts command) before the
eiscopy=on parameter can be
specified.
The destination of a static IP route (see the
ent-ip-rte command) and the local
interface network address of an IP card (see the
ent-ip-host command) must be different
from the PVN, FCNA, and FCNB network addresses (see the
chg-ip-lnk command) before the
eiscopy=on parameter can be
specified.
The FCMODE cannot be changed to FCOPY due to Signaling Link(s) provisioned on Port C or Port D.
If the same value is specified for the PVN, FCNA, or
FCNB network addresses (see the
chg-netopts command), then the
eiscopy=on parameter cannot be
specified.
Notes
Fast Copy Cards
E5-ENET-B cards running the IPSG GPL are considered to be FC- capable. An FC- capable card is considered FC- enabled when Fast Copy monitoring is enabled for the respective GPL.
Output
chg-eisopts:fcmode=fcopy:fcgpl=all
rlghncxa03w 10-02-02 09:08:58 EST EAGLE 42.0.0
CHG-EISOPTS: MASP A - COMPLTD
chg-enumopts
Use this command to provision ENUM-specific data. This command updates the ENUMOPTS table.
Parameters
- cngrcode (optional)
- RCODE values in ENUM error response message to be sent due to congestion on ENUM card.
Example
chg-enumopts:maxdndigs=10
chg-enumopts:conglvl1=50
chg-enumopts:conglvl2=10
chg-enumopts:cngntfy=yes
chg-enumopts:cngrcode=6
chg-enumopts:excludesp=yes
chg-enumopts:rncontext=yes
chg-enumopts:incprefix=yes
Dependencies
The ENUMOPTS table should be accessible.
Congestion level 1 must be less than congestion level 2.
Output
>chg-enumopts:maxdndigs=10
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enumopts:maxdndigs=10
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
>chg-enumopts:conglvl1=50
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enumopts:conglvl1=50
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
>chg-enumopts:conglvl2=90
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enumopts:conglvl2=90
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
>chg-enumopts:cngntfy=yes
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enumopts:cngntfy=yes
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
>chg-enumopts:cngrcode=6
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enumopts:cngrcode=6
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
>chg-enumopts:excludesp=yes
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.5.0
chg-enumopts:excludesp=yes
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
>chg-enumopts:rncontext=yes
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.5.0
chg-enumopts:rncontext=yes
Command entered at terminal #4.
CHG-ENUMOPTS: MASP A - COMPLTD
;
This example displays output when incprefix is specified:
> chg-enumopts:incprefix=yes
Command Accepted - Processing
tekelecstp 19-05-03 16:53:17 MST EAGLE 46.8.0.0.0-75.18.14
chg-enumopts:incprefix=yes
Command entered at terminal #4.
tekelecstp 19-05-03 16:53:17 MST EAGLE 46.8.0.0.0-75.18.14
CHG-ENUMOPTS: MASP A - COMPLTD
;
chg-enum-prof
Use this command to change the existing profile entry which has data to generate the ENUM response for three supported resource record formats such as NAPTR, NS and CNAME. The ENUMPROF table stores the profile entry.
Parameters
- pref (optional)
- Preferred Response. This parameter will decide the values for the Order and Preference fields to be encoded for each NAPTR resource record. The values of these fields are only applicable when there are two NAPTR resource records in the ENUM response. This parameter is only valid for the NAPTR response type.
- rpdomain (optional)
- Replacement domain name. This parameter specifies the domain name of the name server in the NS record and the Canonical Name of the domain server in the CNAME record. This parameter is valid for NS and CNAME response types.
- rrdomain (optional)
- Domain name present in regular expression. This parameter specifies the domain name used in SIP or PSTNSIP URI for both ported and non-ported numbers. This parameter is only valid for NAPTR response type.
- rtype (optional)
- Response type. This parameter specifies the response type for the profile. Response type can only be modified for the "default" profile.
Example
chg-enum-prof:prn=pr1:rrdomain=abc.oracle.com
chg-enum-prof:prn=pr2:rrdomain=abc1.oracle.com:pref=yes
chg-enum-prof:prn=pr3:rpdomain=def.oracle.com
chg-enum-prof:prn=pr4:rpdomain=cname.123
chg-enum-prof:prn=pr5:prefix=007
Dependencies
The ENUM Profile Table should be accessible.
The SPARM, PREF and RRDOMAIN parameters cannot be specified with a profile name having a response type of NAPTR.
The RRDOMAIN parameter is valid for the SPARM=SIP or SPARM=PSTNSIP value.
The profile name must be present in the ENUM Profile Table.
RRDOMAIN must be specified for the NAPTR response type.
For the RTYPE=NS or RTYPE=CNAME parameter, the replacement domain name (RPDOMAIN) must be specified.
RTYPE can only be changed for the default profile.
SPARM=SIP or SPARM=PSTNSIP is not supported for the default profile.
Notes
The requirement of using PREFIX in the regular expression is only for PSTN-SIP (NAPTR query). As such, PREFIX will not be applied for PSTN-TEL and SIP (NAPTR queries).
PREFIX can be configured for PSTN-TEL and SIP profiles, but it will not be used.
Output
> chg-enum-prof:prn=pr1:rrdomain=abc.oracle.com
tekelecstp 18-05-29 03:35:20 MST EST EAGLE 46.1.0
chg-enum-prof:prn=pr1:rrdomain=abc.oracle.com
Command entered at terminal #19.
;
Command Accepted - Processing
tekelecstp 18-05-29 03:35:20 MST EST EAGLE 46.1.0
CHG-ENUM-PROF: MASP B - COMPLTD
;
> chg-enum-prof:prn=pr2:rrdomain=abc.oracle.com:pref=yes
tekelecstp 18-05-29 03:38:20 MST EST EAGLE 46.1.0
chg-enum-prof:prn=pr2:rrdomain=abc.oracle.com:pref=yes
Command entered at terminal #19.
;
Command Accepted - Processing
tekelecstp 18-05-29 03:38:20 MST EST EAGLE 46.1.0
CHG-ENUM-PROF: MASP B - COMPLTD
;
> chg-enum-prof:prn=pr3:rpdomain=def.oracle.com
tekelecstp 18-05-29 03:40:20 MST EST EAGLE 46.1.0
chg-enum-prof:prn=pr3:rpdomain=def.oracle.com
Command entered at terminal #19.
;
Command Accepted - Processing
tekelecstp 18-05-29 03:40:20 MST EST EAGLE 46.1.0
CHG-ENUM-PROF: MASP B - COMPLTD
;
> chg-enum-prof:prn=default:rtype=naptr:prefix=1159
Command Accepted - Processing
tekelecstp 19-02-01 12:39:44 EST EAGLE 46.8.0.0.0-75.18.11
chg-enum-prof:prn=default:rtype=naptr:prefix=1159
Command entered at terminal #2.
;
tekelecstp 19-02-01 12:39:45 EST EAGLE 46.8.0.0.0-75.18.11
CHG-ENUM-PROF: MASP B - COMPLTD
chg-enum-profsel
Use this command to change an entry in the ENUM Profile Selection Table or the ENUM DN Block Table. The ENUM Profile Selection Table supports the provisioning information related to mapping of Entity Id to Profile Id. The ENUM DN Block Table supports the provisioning information related to mapping of DN Block to Profile Id.
Parameters
Example
chg-enum-profsel:entityid=12345:prn1=ns2:prn2=cname1
chg-enum-profsel:sdn=12345:edn=12400:prn3=naptr1:prn4=none
Dependencies
The ENUM Profile Selection Table should be accessible.
The ENUM DN Block Table should be accessible.
The ENUM Profile Table should be accessible.
ENTITY ID or SDN or EDN must be specified.
At least one profile must be specified.
The profile name specified by the prnX (x=1, 2, 3, 4) parameter must be provisioned in the ENUM Profile Table.
The response type specified by profile name prn1, prn2, prn3 and prn4 should be NS, CNAME, NAPTR and NAPTR respectively.
The last profile name for a particular entry cannot be none.
NAPTR profile names must be unique.
The default profile cannot be associated with any profile selection entry.
Entity Id cannot be specified with SDN or EDN.
Notes
Response type specified by profile name prn1, prn2, prn3 and prn4 should be NS, CNAME, NAPTR and NAPTR respectively.
Output
chg-enum-profsel:entityid=1234:prn1=ns1:prn2=cname1:prn3=naptr1:prn4=naptr2
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enum-profsel:entityid=1234:prn1=ns1:prn2=cname1:prn3=naptr1:prn4=naptr2
Command entered at terminal #4.
CHG-ENUM-PROFSEL: MASP A - COMPLTD
;
chg-enum-profsel:sdn=1234:prn1=ns1:prn2=cname1:prn3=naptr1:prn4=naptr2
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enum-profsel:sdn=1234:prn1=ns1:prn2=cname1:prn3=naptr1:prn4=naptr2
Command entered at terminal #4.
CHG-ENUM-PROFSEL: MASP A - COMPLTD
;
chg-enum-prosel:edn=2345:prn1=ns1:prn2=cname1:prn3=naptr1:prn4=naptr2
tekelecstp 14-05-28 15:04:28 EST EAGLE 46.1.0
chg-enum-profsel:edn=1234:prn1=ns1:prn2=cname1:prn3=naptr1:prn4=naptr2
Command entered at terminal #4.
CHG-ENUM-PROFSEL: MASP A - COMPLTD
;
chg-feat
Use this command to activate the optional features available on the system.
Some optional features must be purchased before you turn the feature on. If you are not sure whether you are entitled to turn a feature on, contact your Oracle Sales Representative or Account Representative.
Caution:
The features are off when the system is installed. A feature that is turned on with this command cannot be turned off.Parameters
- crmd (optional)
- This parameter turns on the Cluster Routing and Management Diversity (CRMD) feature.
- ituduppc (optional)
- This parameter turns on the ITU National Duplicate Point Code (ITUDUPPC) feature.
- measplat (optional)
- This parameter turns on the Measurements Platform feature. The
chg-measopts:platformenable=oncommand must be entered to enable the Measurement Platform collection function (which cannot be disabled after it is enabled in the system).
- nrt (optional)
- This parameter turns on the Network Routing feature.
Caution:
When using this feature, limited network management is provided for point codes not covered by full point code routing, Cluster Routing, or Nested Cluster Routing.
- plnp (optional)
- This parameter turns on the PCS (Personal Communication Service) 1900 Number Portability feature.
- slsocb (optional)
- This parameter turns on the Other CIC (Circuit Identification Code) Bit Used feature.
- tscsync (optional)
- This parameter turns on the Time Slot Counter Synchronization (TSC) feature that is used with GPSM-II cards. This feature is required, along with use of STC cards, for the EAGLE 5 Integrated Monitoring Support feature ( e5is=on ).
Example
chg-feat:gtt=on
chg-feat:gws=on:cncf=on
chg-feat:sccpcnv=on:tcapcnv=on
chg-feat:tscsync=on:e5is=on
Dependencies
Note:
The "LNP feature" is turned on when the LNP ported TNs quantity appears in thertrv-ctrl-feat command output. An LNP quantity feature access key has been enabled and turned on. See the enable-ctrl-feat and chg-ctrl-feat commands for more information about turning on the LNP feature.
At least one optional parameter must be specified.
The Gateway Screening feature must be turned on before the STP LAN or CNCF feature can be turned on.
The SCCP Conversion feature must be turned on before the TCAP Conversion feature can be turned on.
The LNP feature must be turned on before the Wireless Number Portability or PCS 1900 LNP features can be turned on.
The LNP and Gateway Screening features must be turned on before the Triggerless LNP feature can be turned on.
The Cluster Routing and Management Diversity feature must be turned on before the Nested Cluster Routing feature can be turned on.
The Global Title Translation feature must be turned on before the Enhanced Global Title Translation feature can be turned on.
The Multiple Point Code feature must be turned on before the ITU National Duplicate Point Code feature can be turned on.
The Global Title Translation feature must be turned on before the Variable Length GTT feature can be turned on.
The Time Slot Counter Synchronization feature must be turned on before the EAGLE 5 Integrated Monitoring Support feature can be turned on. These parameters can be specified together in the command to turn them both on at the same time.
If the ANSI/ITU SCCP Conversion feature is enabled, then the SCCP and TCAP conversion features cannot be turned on.
The Gateway Screening feature must be turned on before the Calling Number Conversion Facility feature can be turned on.
The Global Title Translation feature must be turned on before the Padded Variable Length Global Title Translation feature can be turned on.
The Global Title Translation feature must be turned on before the Prefix Deletion of GT feature can be turned on.
The Global Title Translation feature must be turned on before Global System for Mobile Screening feature can be enabled.
The current hardware configuration cannot be determined.
The MAS configuration table must be accessible.
A null pointer was sent into the command handler.
The IMT table must be accessible.
Notes
This command is not allowed in upgrade mode.
After a feature bit is turned on, it cannot be turned off. Take care in turning on features that are not used in the network configuration.
The Calling Name Conversion Facility (CNCF) feature provides a conversion of ISUP IAM messages. The facility uses the following two versions of calling name identification presentation (CNIP) for calling name information delivery:
- The nonstandard, proprietary ISUP party information (PIP) parameter.
- The ANSI standard ISUP generic name (GN) parameter.
The conversion either replaces the PIP parameter with the GN parameter or the GN parameter with the PIP parameter in the ISUP IAM message. The user can set up GWS screens to apply the CNCF feature on a per-point-code or range-of-point-code basis.
The CRMD feature allows the system to configure one route set to an entire cluster of destinations, thus enabling the system to manage and switch traffic to more end nodes.
The GTT feature allows the system to provide translation of the global title digits located in the called party address of an SCCP message. The translation consists of a point code and subsystem number. This feature requires Service Module cards loaded with the VSCCP application.
The EGTT feature provides enhancements to the way the system performs GTT for both ITU and ANSI messages. The feature allows the combination of domain (ANSI or ITU), global title indicator (GTI), translation type (TT), numbering plan (NP), and nature of address indicator (NAI) selectors to be used to select a translation table when the system receives a message requiring EGTT. The feature also allows inclusion of the translated subsystem number (SSN) in the called party address (CDPA) and inclusion of the originating point code (OPC) in the calling party address (CGPA). The feature also provides deletion capability of the GT (global title) in the CDPA.
The GWS feature allows the system to screen specific message types with selected parameters from entering the network through this STP. This feature requires E5-OAM cards.
The STP LAN feature allows selected SS7 messages to be copied and sent to a remote host over an Ethernet LAN using the TCP/IP protocol. This feature requires up to 32 cards running the STPLAN application, and requires the GWS feature.
The TLNP feature gives service providers a method to route calls to ported numbers without having to upgrade their signaling switch (end office or mobile switching center) software. This feature uses the gateway screening stop action TLNP to intercept through-switched ISUP messages on the LIM.
The LFS feature allows the system to perform a series of far end loopback tests that identify faulty segments of an SS7 transmission path up to and including the remote network element.
The MTPRS feature provides an orderly process for bringing signaling links back into service after the system has been isolated and restarted. A greater preference is given to restoring the STP to network service in an orderly fashion than to the speed of recovery. The time required is system dependent as shown:
- Up to 64 LIMs—62 seconds (Link Alignment Delay)
- 64 - 127 LIMs—97 seconds
- 128-191 LIMs—132 seconds
- More than 191 LIMs—167 seconds
The ITUMTPRS feature provides MTP restart support for ITU networks and extends the system’s ANSI MTP restart support to mixed ITU and ANSI networks. The performance of ITU MTP Restart is comparable to the performance of ANSI MTP Restart.
The SCCPCNV and TCAPCNV features allow the system to convert MTP-routed SCCP and TCAP messages from ANSI to ITU format and to convert ITU formatted messages to ANSI.
The PLNP feature provides for LNP query/response in a PCS wireless environment using the LRN method to support Service Provider Number Portability.
The NCR feature allows the system to support full point code entries on different routes within a cluster.
The Other CIC Bit Used feature is one of two methods provided as ITU SLS enhancements for distributing the load across links in a combined and single linkset. The Other CIC Bit Used feature lets the system derive the LSB (Least Significant Bit) from bits 2 through 4 of the CIC to serve as the three lower bits of the SLS (Signaling Link Selection) and one other bit of the CIC to serve as the MSB (Most Significant Bit) of the SLS. The SLSOCB feature applies only to ITU-ISUP messages. The other method of distributing the load is rotation of the four bits of the SLS to change the LSB of the SLS. For additional information on bit rotation, see the ent-ls command.
The NR feature allows provisioning of a single routeset to be used for all MSUs destined to members of that network.
The DSTN5000 feature provides the ability to administer up 5000 routes on the system. If dstn5000=on, the values of the mtpdpcq (destination point code) and mtpxlq (exception list entries) parameters of the chg-stpopts command can total 5500. Otherwise, the sum total for mtpdpcq and mtpxlq cannot exceed 2500. The Cluster Routing and Management Diversity (CRMD) feature must be turned on before the mtpxlq parameter can be specified.
The MPC feature enables the user to use SPCs (secondary point codes) in addition to the true point codes that the EAGLE uses. The SPCs are used for provisioning and routing as if they were the true point code of the EAGLE. SPCs can be provisioned in any of the three domains (ANSI, ITU-N, and ITU-I). SPCs are supported for any type of link.
The ITUDUPPC feature allows an EAGLE mated pair to route traffic for two or more countries that may have overlapping point code values.
The VGTT feature provides the ability to provision global title entries of varying lengths to a single translation type or GTT set. Users are able to assign global title entries of up to 10 different lengths to a single translation type or GTT set.
The TSCSYNC feature allows the system’s A (Active) and B (Standby) internal clocks to be synchronized by the GPSM-II card that is running the standby OAM .
The E5IS feature provides an Ethernet interface between the EAGLE and the Integrated Message Feeder (IMF), to eliminate the need for cabling between each SS7 link and IMF to monitor SS7 traffic.
The Measurements Platform feature provides a dedicated processor for collecting and reporting STP, LNP, INP, G-Flex, and G-Port Measurements data, with support for EAGLE growth to more than 700 links.
Output
chg-feat:gtt=on
rlghncxa03w 04-01-11 11:34:04 EST EAGLE 31.3.0
CHG-FEAT: MASP A - COMPLD
;
chg-frm-pwr
Use this command to change the power threshold value in the Frame Power Threshold table for a specified frame.
The entries in the Frame Power Threshold table contain a Frame ID and the corresponding power threshold value.
Use the following commands to display the threshold and calculated maximum power consumption for the frames in the system.
- The
rtrv-frm-pwrcommand displays the current provisioned frame power threshold for each provisioned frame. - The
rtrv-stp:display=powercommand displays the provisioned frame power threshold for each provisioned frame, and displays the maximum calculated power consumption for each frame, based on card population. - The
rtrv-stp:display=power:frm=xxxxcommand displays the provisioned frame power threshold for the specified frame, the maximum calculated power consumption for the frame based on card population, and the maximum power consumption for each card in the frame and for a fan assembly for each shelf.
Note:
The frame-level power threshold value needs to be determined from the capacity in Amps of the fuse alarm panel (FAP) for the frame. Contact your site engineer to determine the FAP capacity.Parameters
- thrshld (mandatory)
- Threshold. This parameter specifies the frame-level power threshold, in Amps. This value is compared with the current calculated maximum power consumption for the frame (use the
rtrv-stp:display=power:frm=command to obtain the maximum power consumption value), and the appropriate alarms are raised if that power comsumption exceeds the threshold limit.The value of the thrshld parameter needs to be determined from the capacity of the fuse alarm panel (FAP) for the frame. Contact your site engineer to determine the frame FAP capacity.
Example
Change the frame power threshold value for the first extension frame.
chg-frm-pwr:frm=ef00:thrshld=58
Dependencies
The following values are valid for the frm parameter: cf00, ef00, ef01, ef02, ef03, ef04.
The valid range of values for the thrshld parameter is 30-65 Amps.
A power threshold value must already be provisioned for the specified frame.
The Frame Power Threshold table must be accessible.
Notes
The maximum calculated power for a frame is based on the cards that are populated in the system, and includes a fan tray assembly for every shelf (the system cannot detect the presence or absence of a fan tray, and assumes presence for the calculation). These values are typically much higher than the actual power being drawn; the values cannot be used as a gauge of the actual power consumption of the EAGLE.
Output
chg-frm-pwr:frm=ef00:thrshld=58
tekelecstp 06-06-01 15:18:41 EST EAGLE 35.0.0
FRAME POWER THRESHOLD table is (4 of 10) 40% full
CHG-FRM-PWR: MASP A – COMPLTD
;
chg-ftp-serv
Use this command to change an entry for an FTP server in the FTP Server table.
Caution:
Contact the Customer Care Center before specifying the user parameter value. The FTP-based Table Retrieve Application (FTRA) sends the necessary FTP Server information to the system, and the system overwrites any entry that is already in the FTP Server table for that server.Parameters
- app (mandatory)
- Application. This parameter specifies the FTP Client application that interfaces with the FTP server.
Example
chg-ftp-serv:app=meas:ipaddr=1.255.0.102:login=ftpmeas1:path="~meas":prio=1
chg-ftp-serv:app=user:ipaddr=1.255.0.102:login=tekperson1:path="~\data":prio=1
chg-ftp-serv:app=sflog:ipaddr=1.255.0.102:login=tekperson1:path="~\data":prio=2
Dependencies
At least one optional parameter must be specified.
The app parameter must specify an application that uses the FTP Support feature.
The ipaddr parameter must specify a valid IP address for the FTP server.
The path parameter value must be in a valid FTP path format.
The prio parameter specifies a priority for use of an FTP server by an application when the application has more than one FTP server defined in the table. Each FTP server defined for use by the application must have a priority from 1 to 10 assigned. The available FTP server with the highest priority (smallest number) will be used first by the application.
If the login parameter is specified, a separate prompt appears for entry of the FTP server password. You must enter a password that is at least 1 and not more than 15 characters long. If an invalid password is entered or the Return key is pressed without entering a password, the entire command must be entered again to cause the password prompt to appear again. The password is not displayed as it is entered.
An entry for the specified application ID at the specified priority cannot already exist.
The FTP server entry to be changed with this command must already exist in the FTP Server table for the specified IP address and application.
The security parameter cannot be set to OFF with application (app = sflog).
Notes
The same FTP server can be defined more than once, but the specified application must be different for each entry.
The FTP connection will be secure when the security parameter is ON. The secure FTP connection (SFTP) uses port 22, which must be opened in the customer's network.
Output
chg-ftp-serv:app=meas:ipaddr=1.255.0.102:path="-ftpmeas1"
rlghncxa03w 04-01-20 09:07:58 EST EAGLE 31.3.0
CHG-FTP-SERV: MASP A - COMPLTD
;
chg-ftp-serv:app=meas:ipaddr=1.255.0.102:login=ftpmeas1
rlghncxa03w 04-01-20 09:07:58 EST EAGLE 31.3.0
Enter Password:*****
CHG-FTP-SERV: MASP A - COMPLTD
;
chg-ftp-serv:app=user:ipaddr=1.22.10.2:prio=3
rlghncxa03w 04-01-20 09:07:58 EST EAGLE 31.3.0
CHG-FTP-SERV: MASP A - COMPLTD
;
chg-ftp-serv:ipaddr=10.248.13.9:app=meas:security=on
tekelecstp 12-09-19 15:12:54 EST 45.0.0-64.42.0
chg-ftp-serv:ipaddr=10.248.13.9:app=meas:security=on
Command entered at terminal #4.
CHG-FTP-SERV: MASP A-COMPLTD.
;chg-ftp-serv:app=sflog:ipaddr=10.248.13.9:prio=2
tekelecstp 15-05-27 15:43:58 EST Eagle 46.3.0
chg-ftp-serv:app=sflog:ipaddr=10.248.13.9:prio=2
Command entered at terminal #4.
CHG-FTP-SERV: MASP A - COMPLTD
;
Related Topics
chg-gpl
Use this command to copy a generic program load from the system removable drive to the destination active and standby system disks as a "trial" version. The system release identification file is uploaded from the system removable drive to the active and standby fixed drives along with each GPL. This command also provides a parameter to turn GPL auditing “on” and “off”.
Parameters
- audit (optional)
- This parameter specifies whether the active MASP
system release running version is to be audited every 90 seconds. The audit
state is preserved through a system restart or power up.
Note:
When audit is turned off, the system release audit process is stopped. The detection, marking, and reporting of corrupt GPLs is continuous and not affected by turning audit off.
- gpl (optional)
- Generic program load. The name of the GPL
identifier to be
copied from
the system removable drive to the
active and standby
system
disks.
- Range:
- xyyyyyyy
1 alphabetic character followed by up to 7 alphanumeric characters. Valid GPLs are:
atmhc—Used by E5-ATM-B cards to allow the card to support up to 3 signaling links
bldc32—Flash GPL containing a tar image with all code required on E5-MCAP cards to support VxWorks6.9 32-bit application, as in OAMHC69.
bldc64—Flash GPL containing a tar image with all code required on E5-SM8G-B cards for SCCP64, ENUM64, SIP64 and DEIR64 applications.
blmcap—Flash GPL containing a tar image with all code required on E5-MCAP, E5-E1T1-B, E5-MCPM-B, E5-ATM-B, E5-ENET-B, and E5-SM8G-B cards
blslc32—Flash GPL containing a tar image with all code required on SLIC cards for 32-bit application i.e. MCPHC, IPSHC etc.
blslc64—Flash GPL containing a tar image with all code required on SLIC cards for 64-bit application i.e. SCCP64, ENUM64, SIP64 and DEIR64.
blsl932—Flash GPL containing a tar image with all code required on SLIC cards for 32-bit application on VxWorks6.9, as in IPSHC69 and MCPHC69.
deirhc— Used by E5-SM8G-B cards to support the S13/S13' EIR feature
enumhc—Used by E5-SM8G-B cards to support the ENUM Mobile Number Portability and Tier One Address Resolution application
erthc—Used by E5-ENET-B cards for EAGLE 5 Integrated Monitoring Support functions
hipr2—Communication software used on the High Speed IMT Packet Router (HIPR2) card
ipsg—Used by E5-ENET-B cards to support the combined functionality of IPLIMx M2PA and IPGWx M3UA
ipsg32—Used by SLIC cards to support IPSG application with 64-bit addressing either with GTT functionality or without it.
ipshc—Used by E5-ENET-B and SLIC cards to support the IPS application
ipshc69—Used by E5-ENET-B and SLIC cards to support the IPS application when running on VxWorks69.
mcphc— Used by E5-MCPM-B cards for the Measurements Platform feature
mcphc69—Used by E5-MCPM-B and SLIC cards for the Measurements Platform feature when running on VxWorks69.
oamhc—Used by E5-MCAP cards for enhanced OAM functions
oamhc69—Used by E5-MCAP cards for enhanced OAM functions, when running on VxWorks 69.
sccphc—Used by E5-SM8G-B cards to support EPAP-based features and the LNP ELAP Configuration feature. If no EPAP-based or LNP ELAP Configuration feature is turned on, and an E5-SM8G-B card is present, then the GPL processes normal GTT traffic.
sfapp—Used by SLIC cards to support the Stateful Firewall Application.
siphc— Used by E5-SM8G-B Cards to support the SIP application.
ss7hc—Application GPL used by E5-E1T1-B and SLIC cards to support E1 and T1 signaling links.
Example
chg-gpl:audit=on
chg-gpl:gpl=atmhc:ver=138-19-0
chg-gpl:gpl=siphc:ver=134-35-0
chg-gpl:gpl=enumhc:ver=135-20-0
chg-gpl:gpl=ipsg32:ver=140-20-0
chg-gpl:gpl=sfapp:ver=141-012-1
Dependencies
No other activate, change, copy, or retrieve GPL command can be in progress when this command is entered.
If the ver or gpl parameter is specified, then both parameters must be specified.
The audit parameter, the ver and gpl parameters, or the audit and ver and gpl parameters must be specified.
A system removable drive must be inserted in the Active OAM.
A valid value must be specified for the gpl parameter.
Notes
If there is a failure changing the active system, the operation is stopped. If there is a failure changing the standby system, the active system is still updated.
A system removable drive must be inserted into the latched USB port, initialized, and formatted as a system disk.
Use the
rtrv-gpl command to determine the
version number and audit state of a GPL.
The ver and gpl parameters are mandatory if a generic program load is being uploaded from a system removable drive.
The audit parameter is required only when turning GPL auditing on or off and the ver and gpl parameters are optional.
When the audit=off parameter is specified, the system release audit process is stopped. The detection, marking, and reporting of corrupt GPLs is continuous and not affected by turning audit off.
Output
This example shows the output for a successful command execution:
chg-gpl:gpl=ss7hc:ver=125-1-0
rlghncxa03w 09-03-01 11:43:04 EST EAGLE 40.1.0
SS7HC upload to 1114 completed
SS7HC upload to 1116 completed
System Release ID table upload to 1116 completed
System Release ID table upload to 1114 completed
;
chg-gpl:gpl=siphc:ver=134-35-0
tekelecstp 12-07-09 19:08:39 EST EAGLE 45.0.0
SIPHC upload to 1114 completed
SIPHC upload to 1116 completed
System Release ID table upload to 1116 completed
System Release ID table upload to 1114 completed
;
chg-gpl:gpl=enumhc:ver=135-20-0
tekelecstp 14-05-20 15:19:30 EST EAGLE 46.1.0
ENUMHC upload to 1114 completed
ENUMHC upload to 1116 completed
System Release ID table upload to 1116 completed
System Release ID table upload to 1114 completed
;
chg-gpl:gpl=ipsg32:ver=140-20-0
tekelecstp 14-05-20 15:19:30 EST EAGLE 46.1.0
IPSG32 upload to 1114 completed
IPSG32 upload to 1116 completed
System Release ID table upload to 1116 completed
System Release ID table upload to 1114 completed
;
chg-gpl:gpl=sfapp:ver= 141-012-1
tekelecstp 17-11-29 16:18:04 MST EAGLE 46.5.1.5.0-73.2.0
SFAPP activate to 1114 completed
SFAPP activate to 1116 completed
;
chg-gsm-msg
Use this command to provision GSM test messages. These messages are used by the MO SMS NPP Test Tool to test MO-based GSM SMS message processing by the NPP.
Parameters
- active (optional)
- This parameter specifies whether the GSM test message is sent to the network card for processing.
- cdpagti (optional)
- Called party address global title indicator. The SCCP CdPA GT for the GSM test message.
- cdpagtnai (optional)
- Called party address global title nature of address indicator. The SCCP CdPA GT NAI for the GSM test message.
- cdpndgts (optional)
- Called party number digits. The TCAP CdPN (SM-RP-UI TP-DA) digits for the GSM test message.
- cdpnnai (optional)
- Called party number nature of address indicator. The TCAP CdPN (SM-RP-UI TP-DA) NAI for the GSM test message.
- cdpnnp (optional)
- Called party numbering plan. The TCAP CdPN (SM-RP-UI TP-DA) NP for the GSM test message.
- cgpagti (optional)
-
Calling party address global title indicator. The SCCP CgPA GT for the GSM test message.
- cgpagtnai (optional)
- Calling party address global title nature of address indicator. The SCCP CgPA GT NAI for the GSM test message.
- cgpndgts (optional)
- Calling party number digits. The TCAP CgPN (SM-RP-OA MSISDN) for the GSM test message.
- cgpnnai (optional)
- Calling party number nature of address indicator. The TCAP CgPN (SM-RP-OA MSISDN) NAI for the GSM test message.
Example
chg-gsm-msg:msgn=1:cdpnnai=4:cdpadgts=12457896abcd:cgpnnai=2:cgpndgts=919818541560
chg-gsm-msg:msgn=1:reset=yes
Dependencies
The TSTMSG table is corrupt or cannot be found.
If the reset parameter is specified, then no other parameter can be specified.
At least one optional parameter must be specified.
Output
chg-gsm-msg:msgn=1:cdpnnai=4:cdpndgts=987654321:cgpnnai=4
tekelecstp 09-03-02 10:46:51 EST EAGLE 40.1.0
CHG-GSM-MSG: MASP A - COMPLTD
;
Related Topics
chg-gsmmap-scrn
Use this command to change the attributes of GSM Map Screening CgPA and CdPA entries that are used to filter out or allow SCCP messages containing Map Op-Codes, CgPA GTA+NPV+NAIV, CdPA GTA+NPV+NAIV, and forbidden parameters.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- opname (mandatory)
- The user-defined name for the operation code. The opname value references the operation code (opcode) defined with the
ent-gsms-opcodecommand. GSM MAP Screening is performed on the specified address or addresses for the referenced operation code.
- force (optional)
- Check Mated Application Override. This parameter must be used to complete command execution if the npc/npca/npci/npcn and nssn parameter combination specified in the command is not already defined in the SCCP Application entity set (Remote Point Code/Mated Application Table).
- naction (optional)
- The new screening action to take if a message is forbidden as defined by the forbid parameter.
- Range:
-
- atierr
- Do not route the MSU. An ATI (Any Time Interrogation) reject message is generated to the originator. This value is valid only for ATI MAP operation codes.
- discard
- Do not route the MSU. The MSU is discarded (thrown away) and an appropriate UIM is issued.
- dupdisc
- Route the original message to the duplicate node. The original message will not be sent to the original node. If, however, the duplicate node is not available for routing, the MSU is discarded.
- duplicate
- Route the message as normal to the original destination and route a copy of the original message to the duplicate node. If the MSU fails to route to the duplicate node, a UIM is generated indicating the duplicate routing failure.
- forward
- Route the original message to the forward node. The original message will not be sent to the original node. If, however, the forward node is not available for routing, the MSU is routed to the original node.
- pass
- Route the message as normal to the destination; a UIM will be issued. This is intended to be a test mode and is recommended when setting up GSM Map Screening during the initial phase to assure that no MSUs will be inadvertently thrown away.
- route
- Route the message as normal to the original destination node; no UIM will be generated. The original destination is the node to which normal GTT would be sent if no GSM MAP actions are taken.
- Default:
- No change to current value
- nforbid (optional)
- The new forbidden parameter value. Indicates a forbidden parameter for the specified entry. If a forbidden parameter is detected, the message is handled with the action defined by the action/naction parameter.
- Range:
-
- all
- All parameters are forbidden. Take the specified screening action defined by the naction parameter for messages arriving at the system.
- none
- None of the parameters are forbidden. Route the message to its destination.
- state
- Take the specified screening action defined by the naction parameter for messages arriving at the system that contain state as the forbidden parameter for the entered address/operation code combination.
Note:
The state parameter is valid only for GSM ATI messages. - location
- Take the specified screening action defined by the naction parameter for messages arriving at the system that contain location as the forbidden parameter for the entered address/operation code combination.
Note:
This value is valid only for GSM ATI messages.
- Default:
- No change to current value
- npc (optional)
- New ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- npc/npca/npci/npcn/npcn24 (optional)
- New point code. The npc/npca/ npci/npcn /npcn24 and nssn parameters are used when the new screening action (naction) is forward, duplicate, or dupdisc (duplicate and discard). These parameters allow the user to change the defined node to which the input message will be routed.
- npci (optional)
- New ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- npcn (optional)
- New ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc,m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- npcn24 (optional)
- New 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- nri (optional)
- New routing indicator. This parameter specifies whether a subsequent global title translation is required.
Example
chg-gsmmap-scrn:opname=xyz:cgsr=fela:naction=pass
chg-gsmmap-scrn:opname=xyz:cgsr=fela:cdsr=fall:naction=discard
chg-gsmmap-scrn:opname=test2:cgsr=pcn1:npcn=s-333:nssn=254
chg-gsmmap-scrn:opname=test1:naction=forward:npc=2-2-2:nssn=20:nmapset=12
chg-gsmmap-scrn:opname=test2:naction=duplicate:npc=1-1-2:nssn=20:cgsr=cg1:nmapset=dflt
chg-gsmmap-scrn:opname=test3:cgsr=ad:nri=ssn
chg-gsmmap-scrn:opname=test4:cgsr=ksl:ntt=12
Dependencies
At least one optional parameter must be specified.
If the cdsr parameter is specified, at least one additional optional parameter must be specified.
If the ncdsr parameter is specified, then the cdsr parameter must be specified.
If the cdsr parameter is specified, then the ncgsr parameter cannot be specified.
The ncgsr parameter and the ncdsr parameter cannot be specified together in the same command.
The specified cgsr parameter value must exist in the database.
The specified cdsr parameter value must exist in the database.
The specified ncgsr parameter value cannot already exist in the database.
The specified ncdsr parameter value cannot already exist in the database.
The GSM Map Screening feature must be turned on before this command can be entered.
The Enhanced GSM Map Screening (EGMS) feature must be turned on before the cdsr, ncdsr, pc, and pca parameters can be specified.
The specified opname parameter value must exist in the GSM Map Op-Code table.
A value of state or location cannot be specified for the nforbid parameter unless the operation code (opcode) referenced by the opname parameter is 71. The opcode=71 parameter signifies an ATI MAP operation code.
A value of atierr cannot be specified for the naction parameter unless the operation code (OPCODE) referenced by opname is 71.
If specified, the npc/npca/npci/ npcn/npcn24 parameter must be a full point code.
If the naction parameter is specified, and its value is forward, duplicate, or dupdisc, then the npc/npca/npci/npcn/npcn24 parameter and the nssn parameter must be specified.
The npc/npca/npci/npcn/npcn24 and nssn parameters must be specified before the force parameter can be specified.
If the npc/npca/npci/npcn/npcn24 parameter and the nssn parameter are specified, and the force parameter is not specified as yes, the PC-SSN must be populated in the SCCP Application entity set (Remote Point Code / Mated Application Table).
The GSM Map screening table must be accessible.
The GSM Map Op-Code table must be accessible.
The Route table must be accessible.
If specified, the npc/npca/npci/npcn/npcn24 parameter value must exist as a destination in the Ordered Route entity set (ANSI only), or must reside in a cluster that exists as a destination in the Ordered Route entity set (for global title routing).
The npc/npca/npci/npcn/npcn24 and nssn parameters can be specified only if the naction parameter is specified and its value is forward, duplicate, or dupdisc.
The opname parameter must be entered.
The cgsr parameter must be entered.
The opname parameter must be alphanumeric.
The (n)cgsr and (n)cdsr parameters must begin with an alphabetic character.
The (n)cgsr and (n)cdsr parameters must have 1-4 alphanumeric characters each.
If the value of the naction parameter is forward, duplicate, or dupdisc, then the nmapset parameter must be specified.
The naction parameter must have a value of forward, duplicate, or dupdisc before the npc/npca/npci/npcn/npcn24, nssn,nri, ntt, or naction parameters can be specified.
If the naction parameter has a value of forward, duplicate, or dupdisc, then the npc/npca/npci/npcn/npcn24 parameter and the nssn parameter must be specified.
The Flexible GTT Load Sharing feature must be enabled before the nmapset parameter can be specified.
The specified new MAP set must exist in the MAP table.
If the value of the nmapset parameter is not dflt, or if the nmapset=dflt parameter is specified, but the value of the force parameter is not yes, then the values for the npc and nssn parameters must exist in the new MAP set.
If the nmapset, nri, or ntt parameter is specified, and the naction parameter is not specified, then the action parameter (see the ent-gsmmap-scrn command) must have a value of forward, duplicate, or dupdisc.
The MAP table must be accessible.
The force parameter can be specified only if the nmapset parameter is specified.
If the value of the naction parameter is forward, duplicate, or dupdisc, then the value specified for the npc/npca/npci/npcn/npcn24 parameter cannot be associated with a proxy point code.
If the nri=ssn parameter is specified, then the nssn=none parameter cannot be specified.
If the nforbid=none parameter is specified, then the naction parameter must have a value of pass.
If the Flexible GTT Load Sharing feature is enabled, and the new or previously provisioned subsystem number has a value of none, then MAP set and point code combination must already exist in the MAP table.
If the Flexible GTT Load Sharing feature is not enabled, and the new or previously provisioned subsystem number has a value of none, then the point code must already exist in the MAP table.
Notes
Unlike GTT (Global Title Translation) entries, the GSM MAP Screening commands do not support splits of ranges during deletion or changes of entries.
In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).
Output
chg-gsmmap-scrn:opname=test4:cgsr=ksl:ntt=12
tekelecstp 08-08-20 19:13:01 EST EAGLE 39.2.0
GSM MAP Screening Table (1 of 4000) is 1% full
CHG-GSMMAP-SCRN: MASP A - COMPLTD
;
Related Topics
chg-gsmopts
Use this command to enter GSM (Global System for Mobile Telecommunications) system options in the database. This command updates the GSMOPTS Table.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.Note:
The options for the on, off, maplyrrtgon, and maplyrrtgoff parameters are described in the Notes section.- dfltrn (optional)
- Default routing number. The digits to use as the routing number portion of the msrndig parameter when an SRI is processed by the SRI Query for Prepaid feature, an RTDB match is found for an own-network subscriber, and Service Portability is not applied.
- eirdfltimsilkup (optional)
-
Equipment Identity Register (EIR) default IMSI lookup status. This parameter specifies the order of the IMEI table lookup for default IMSI screening. This parameter is analogous to the P1 parameter in the IMSIPFX CSL list but is used only when there is no matching IMSI prefix in the IMSIPFX CSL.
- eirdfltimsiresp (optional)
-
Equipment Identity Register (EIR) default IMSI response. This parameter specifies the default IMEI status for default IMSI screening. This parameter is analogous to the P2 parameter in the IMSIPFX CSL list but is used only when there is no matching IMSI prefix in the IMSIPFX CSL.
- eirgrsp (optional)
- Equipment Identity Register (EIR) Global Response status.
- Range:
-
- off
- EIR Global Response is not used
- whitelst
- The IMEI is “valid”. Registration should be allowed for the handset.
- graylst
- The IMEI is “questionable.” Registration should be allowed, but the event is logged in the EIR log and a special measurement peg is incremented.
- blklst
- The IMEI is “invalid”. Registration should not be allowed for this handset.
- unknown
- The IMEI is not in the White, Gray, or Black list. Registration should not be allowed for this handset.
- Default:
- No change to the current value
- System Default:
- off
- eirimsichk (optional)
- Equipment Identity Register (EIR) IMSI Check status. This parameter is not valid for IMEI ranges.
- eirrsptype (optional)
- Equipment Identity Register (EIR) Response Type.
- Range:
-
Table 4-6 contains information to help select the value for this parameter.
Table 4-6 EIR Response Type Values
Presence in List EIR Response Type White Gray Black Type 1 Type 2 Type 3 X white list white list white list X X gray list gray list gray list X X X black list black list black list X X black list black list black list X gray list gray list unknown X X black list black list unknown X black list black list unknown white list* unknown* unknown* *Indicates no match was found for the IMEI in an incoming message within the database.
- gflexmaplayerrtg (optional)
- G-Flex MAP layer routing. The message parameter used in the database lookup performed during G-Flex MAP layer routing.
The gflexmaplayerrtg parameter applies G-Flex MLR to the following MAP operations:
- updateLocation
- sendParameters
- sendAuthenticationInfo
- updateGPRSLocation
- AnyTimeInterrogation
Use the maplyrrtgon and maplyrrtgoff parameters to apply G-Flex MLR to additional MAP operations.
- maplyrrtgoff (optional)
-
MAP Layer Routing Off. This parameter turns off G-Flex MLR for a comma-separated list of MAP operations. Up to 10 operations can be specified in the list.
- Range:
- regss, actss, dactss, intss, authfailrpt, rstdata, procunstrqt, rdyforsm, purgmobss, sriloc, all
all —Turns off G-Flex MLR for all MAP operations supported by the maplyrrtgoff parameter.
Note:
If the all MAP operation is specified, then no other MAP operations can be specified in the same command. - Default:
- No change to the current value
- maplyrrtgon (optional)
- MAP Layer Routing On. This parameter turns on G-Flex MLR for a comma-separated list of MAP operations. Up to 10 operations can be specified in the list.
- Range:
- regss, actss, dactss, intss, authfailrpt, rstdata, procunstrqt, rdyforsm, purgmobss, sriloc, all all —Turns on G-Flex MLR for all MAP operations supported by the maplyrrtgon parameter.
Note:
If the all MAP operation is specified, then no other MAP operations can be specified in the same command. - Default:
- No change to the current value
- migrpfx (optional)
- Migration prefix. This parameter specifies whether the database routing number (RN) or the GSM to IS-41 Migration prefix is used as the source for the prefix in the SRI Ack response message for a migrated subscriber.
- msisdntrunc (optional)
- MS ISDN truncation digits. The number of digits to delete from the beginning of the National MSISDN (MSISDN without Country Code) before formulating the MSRN parameter of the SRI Ack response.
- msrndig (optional)
- The routing number to be used as is or concatenated with the MSISDN.
- Range:
-
- rn
- Routing number
- rndn
- Routing number prefix and the international DN (dialed/directory number)
- ccrndn
- Country code, routing number, and national directory number
- rnccdn
- Routing number, country code and directory number
- rnasd
- Routing number and additional subscriber data
- asdrn
- Additional subscriber data and routing number
- rnasddn
- Routing number, additional subscriber data, and directory number
- asdrndn
- Additional subscriber data, routing number, and directory number
- ccrnasddn
- Country code, routing number, additional subscriber data, and directory number
- ccasdrndn
- Country code, additional subscriber data, routing number and directory number
- rnasdccdn
- Routing number, additional subscriber data, country code, and directory number
- asdrnccdn
- Additional subscriber data, routing number, country code, and directory number
- rngrn
- Routing number and generic routing number
- grnrn
- Generic routing number and routing number
- rngrndn
- Routing number, generic routing number, and directory number
- grnrndn
- Generic routing number, routing number, and directory number
- ccrngrndn
- Country code, routing number, generic routing number, and directory number
- ccgrnrndn
- Country code, generic routing number, routing number, and directory number
- rngrnccdn
- Routing number, generic routing number, country code, and directory number
- grnrnccdn
- Generic routing number, routing number, country code, and directory number
- Default:
- No change to the current value
- System Default:
- rn
- msrnlen (optional)
- The number of digits in the MAP Routing Info portion of the returned SRI_ACK message.
- msrnnp (optional)
- The numbering plan value for the MSRN.
Note:
This parameter is mandatory if the msrnnai parameter is specified.
- off (optional)
- This parameter turns off the specified options. Up to 8 comma-separated unique options can be specified.
- on (optional)
- This parameter turns on the specified options. Up to 8 comma-separated unique options can be specified.
- sporttype (optional)
- Service Portability type. This parameter specifies whether Service Portability applies to SRI Query for Prepaid messages for own-network subscribers.
Note:
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’entity id) is applied.Note:
The S-Port feature must be turned on before any change to the parameter will impact the G-Port SRI Query for Prepaid feature.
- sridnnotfound (optional)
- The processing used when G-Port encounters an RTDB query result that indicates that the specified directory number is not known.
- srirdctent (optional)
- This indicates whether existing SRI REDIRECT feature (SP) or Intra Network Number Portability feature (GRN) is to be used.
Example
chg-gsmopts:msisdntrunc=1:srfaddr=123456789abcdef:srfnai=0:srfnp=0
chg-gsmopts:msrnnai=1:msrnnp=1:msrndig=ccrndn:defmapvr=2
chg-gsmopts:sridn=sccp
chg-gsmopts:is412gsm=1234:gsm2is41=1234
chg-gsmopts:serverpfx=1000
chg-gsmopts:multcc=011
chg-gsmopts:multcc=011:nmultcc=11
chg-gsmopts:ccnc=33322123:mccmnc=21434
chg-gsmopts:eirimsichk=on:eirrsptype=type2:eirgrsp=blklst
chg-gsmopts:migrpfx=multiple
chg-gsmopts:sridnnotfound=srinack
chg-gsmopts:defmcc=214:defmnc=34
chg-gsmopts:msrndig=rnasd
chg-gsmopts:on=eirimsichk,eirimsiscrn,eirlogwl,eirdfltimsiscrn:eirrsptype=type2:
eirgrsp=blklst
chg-gsmopts:on=encodecug,encodenps,srismgrnrtg:off=eirimsichk,eirimsiscrn,eirlogwl,
eirdfltimsiscrn:crptt=50
chg-gsmopts:on=encdnpsptnone,encdnpsdnnotfound
chg-gsmopts:maplyrrtgon=regss,actss,sriloc:maplyrrtgoff=dactss,rstdata
chg-gsmopts:eirdfltimsilkup=range
chg-gsmopts:eirdfltimsiresp=whitelist
chg-gsmopts:srirdctent=grn
chg-gsmopts:ownnetworksetname=cdgta1
Dependencies
At least one parameter must be specified.
The G-Flex feature must be turned on before the defmnc, ccnc, or mccmnc parameter can be specified.
The G-Port or IGM feature must be enabled before the srfaddr, msrndig, msrnnai, sridn, msisdntrunc, migrpfx, gsm2is41, or serverpfx parameter can be specified and before a value of encodecug, encodenps, srismgttrtg, encdnpsptnone, or encdnpsdnnotfound can be specified for the on or off parameter.
An is412gsm parameter value must exist in the database before the serverpfx parameter can be specified.
The serverpfx=none parameter must be specified before the is412gsm=none parameter can be specified.
The EIR feature must be turned on before the eirgrsp, eirrstype, eirimsichk, eirdfltimsilkup, or eirdfltimsiresp parameters can be specified and before the eirimsichk, eirimsiscrn, eirlogwl or eirdfltimsiscrn options can be specified for the on or off parameter.
The ccnc and mccmnc parameter values must be specified together in the command.
A maximum of 10 ccnc records can exist in the database.
The value specified for the ccnc parameter cannot already exist in the database unless the mccmnc=none parameter is specified.
The srfaddr, srfnai, and srfnp parameters must be specified together in the command.
The msrnnai and msrnnp parameters must be specified together in the command.
The value specified for the ccnc parameter must already exist in the database if the mccmnc=none parameter is specified.
A maximum of 10 entries can be defined in the multiple country code list (in addition to the STP options defcc value).
A multiple country code cannot be entered when the STP options defcc value is none. A defcc value must first be defined before the first multiple country code can be entered. See the chg-stpopts command.
The value specified for the nmultcc parameter cannot already exist in the multiple country code list.
If the multcc and nmultcc parameters are specified to change the multcc value to the nmultcc value, then the multcc value must already exist in the multiple country code list.
The specified multcc and nmultcc values cannot already be defined as the STP options defcc parameter value.
The STP Options table is corrupt or cannot be found.
The IGM feature must be enabled before the is412gsm, gsm2is41, or migrpfx parameter can be specified.
The G-Port, IGM, MO SMS ASD, MO SMS B-Party Routing, MO SMS GRN, MO SMS IS41-to-GSM Migration, MO-based GSM SMS NP, or Prepaid SMS Intercept Ph1 feature must be enabled, or the G-Flex, EIR, or V-Flex feature must be turned on before this command can be entered.
The G-Port or IGM feature must be enabled or the V-Flex feature must be turned on before the multcc and nmultcc parameters can be specified.
The G-Flex MAP Layer Routing feature must be enabled and turned on before the gflexmaplayerrtg, maplyrrtgon, or maplyrrtgoff parameter can be specified.
The G-Flex or G-Port feature must be turned on or the MT-Based GSM SMS NP or IGM feature must be enabled before the defm or cc parameter can be specified.
If the MT-Based GSM SMS NP feature is turned on, then the defmcc=none parameter cannot be specified.
The nmultcc and multcc parameters must be specified together in the command.
If the multcc parameter is specified to enter a new value in the multiple country list, then the specified value cannot already exist in the list.
The IGM or MO SMS IS41-to-GSM Migration feature must be enabled before the is412gsm parameter can be specified.
The G-Port feature must be enabled before the sridnnotfound parameter can be specified.
The G-Port feature must be turned on before the migrpfx=multiple parameter can be specified.
The EGLEOPTS table is corrupt or cannot be found.
The G-Port, IGM, MO SMS ASD, MO SMS B-Party Routing, MO SMS GRN, MO-based GSM SMS NP, or Prepaid SMS Intercept Ph1 feature must be enabled before the defmapvr parameter can be specified.
The G-Port SRI Query for Prepaid feature must be enabled before the dfltrn parameter can be specified.
The S-Port and G-Port SRI Query for Prepaid features must be enabled before the sporttype parameter can be specified.
The G-Flex feature must be turned on or the G-Port or IGM feature must be enabled before the ccnc and mccmnc parameters can be specified.
The G-Flex feature must be turned on or the G-Port or IGM feature must be enabled before the ccnc and mccmnc parameters can be specified.
The MNP Circular Route Prevention feature must be turned on before the crptt parameter can be specified.
The eirimsichk parameter and the on or off parameter cannot be specified together in the command.
The same value cannot be specified for the on and off parameters.
The same MAP operation cannot be specified by the maplyrrtgon and maplyrrtgoff parameters in the same command.
If the all MAP operation is specified for the maplyrrtgon or maplyrrtgoff parameter, then no other operation can be specified for these parameters in the same command.
If the maplyrrtgon=all parameter is specified, then the maplyrrtgoff parameter cannot be specified in the same command.
If the maplyrrtgoff=all parameter is specified, then the maplyrrtgon parameter cannot be specified in the same command.
The GSM MAP SRI Redirect feature must be enabled before the srirdctent parameter can be set to grn or sp.
Notes
The sridn parameter can be used with the G-Port feature only or with the G-Port feature and the MNP Circular Route Prevention feature. Refer to G-Port User's Guide for more information.
If the IGM feature was turned on prior to upgrade to Release 36.0, then the migration prefix is hard-coded to a value of multiple. After upgrade, if the chg-gsmopts:migrpfx=single command is used to change the migration prefix to single, then the G-Port feature must be turned on before the migration prefix can be changed back to multiple (chg-gsmopts:migrpfx=multiple).
In 39.2.4, the gflexmaplayerrtg values changed from off/on to none/imsi/msisdn/all. The value off was changed to none. The value on was changed to imsi. The message processing did not change, just the text description that is displayed to the user. The numeric values did not change, so no upgrade is necessary.
SRIRDCTENT is a system-wide option that can be set to use either the Intra Network Number Portability feature or the GSM MAP SRI Redirect feature.
on/off options
- eirimsichk —Specifies the use of the Equipment Identity Register (EIR) IMSI Check status. This option is not valid for IMEI ranges. This option has a default of OFF.
- encodecug —Specifies whether the Closed User Group (CUG) Checkinfo from the SRI message is included in the SRI Ack message. This option has a default of OFF.
- enodenps — Specifies whether the Number Portability Status Indicator (NPSI) is included in SRI Ack messages when the portability type (PT) has a value of 0, 1, 2 or 36. This option has a default of ON.
- srismgttrtg —Specifies whether the SRI_SM routing feature is on. This option has a default of OFF.
- encdnpsptnone —Specifies whether the NPSI is included in SRI Ack messages when the PT has a value of none (255). This option has a default of OFF.
- encdnpsdnnotfound —Specifies whether the NPSI is included in SRI Ack messages when the DN is not found. This option has a default of OFF.
- eirimsiscrn ---- Specifies the use of Equipment Identity Register (EIR) IMSI screening status. This option specifies whether the IMSI Screening shall be done before the IMEI check. This option has a default of OFF.
- eirlogwl ---- Specifies the use of Equipment Identity Register (EIR) white list logging status. This option specifies whether the white list logging for EIR shall be on. This option has a default of OFF.
- eirdfltimsiscrn ---- Specifies the use of Equipment Identity Register (EIR) default IMSI screening status. This option specifies whether the default IMSI screening shall be on. This option has a default of OFF.
MAP Operations Supported by the maplyrrtgon and maplyrrtgoff Parameters
The maplyrrtgon and maplrrtgoff parameters are used to turn G-Flex MLR on and off, respectively, for the following MAP operations:
- regss : registerSS —Register Supplementary Service
- actss : activateSS —Activate Supplementary Service
- dactss : deactivateSS —Deactivate Supplementary Service
- intss : interrogateSS —Interrogate Supplementary Service
- authfailrpt : authenticationFailureReport —Authentication Failure Report
- rstdata : restoreData —Restore Data
- procunstrqt : processUnstructuredSS-Request —Process Unstructured SS Request
- rdyforsm : readyForSM —Ready For Short Message
- purgmobss : purgeMS —Purge Mobile Subscriber
- sriloc : sendRoutingInfoForLCS —Send Routing Information for Location Service
Output
chg-gsmopts:msrnnai=1:msrnnp=1:msrndig=ccrngrndn:defmapvr=2
tekelecstp 09-05-05 12:28:07 EST EAGLE 41.1.0
CHG-GSMOPTS: MASP A – COMPLTD
;
chg-gsmopts:srirdctent=grn
tekelecstp 14-05-30 16:39:41 EST EAGLE 46.1.0
CHG-GSMOPTS: MASP A - COMPLTD
;
Related Topics
chg-gsms-opcode
Use this command to change the attributes of the GSM (Global System for Mobile Telecommunication) MAP (mobile application part) screening operation codes. The command allows you to change the default screening action and the operation-code name for a specific operation code.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- force (optional)
- Check Mated Application Override. This parameter is used to complete command execution if the npc/npca/npci/npcn/npcn24 and nssn parameter combination specified in the command is not already defined in the SCCP Application entity set (Remote Point Code/Mated Application Table).
- ndfltact (optional)
- New default screening action.
- Range:
-
- pass
- Route the message as normal to the destination; a UIM will be issued. This is intended to be a test mode and is recommended when setting up GSM Map Screening during the initial phase to assure that no MSUs will be inadvertently thrown away.
- discard
- Do not route the MSU. The MSU is discarded (thrown away) and an appropriate UIM is issued.
- atierr
- Do not route the MSU. An ATI (Any Time Interrogation) reject message is generated to the originator. This value is valid only for ATI MAP operation codes.
- route
- Route the message as normal to the original destination node; no UIM will be generated. The original destination is the node to which normal GTT would be sent if no GSM MAP actions are taken.
- forward
- Route the original message to the forward node. The original message will not be sent to the original node. If, however, the forward node is not available for routing, the MSU is routed to the original node.
- duplicate
- Route the message as normal to the original destination and route a copy of the original message to the duplicate node. If the MSU fails to route to the duplicate node, a UIM is generated indicating the duplicate routing failure.
- dupdisc
- Route the original message to the duplicate node. The original message will not be sent to the original node. If, however, the duplicate node is not available for routing, the MSU is discarded.
- Default:
- No change to the current value
- npc (optional)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- npca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- npc/npca/npci/npcn/npcn24 (optional)
- New point code. The npc/npca/npci /npcn/npcn24 and nssn parameters are used when the default screening action (dfltact) is forward, duplicate, or dupdisc (duplicate and discard). These parameters allow the user to change the defined node to which the input message will be routed.
- npci (optional)
- New ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- npcn (optional)
- New ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- npcn24 (optional)
- New 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
Example
chg-gsms-opcode:opname=ati:ndfltact=atierr
chg-gsms-opcode:opname=ati:ndfltact=forward:npci=1-1-1:nssn=5:force=yes
chg-gsms-opcode:opname=xyz:npca=9-9-9:nssn=3
chg-gsms-opcode:opname=test2:npci=s-1-1-1
chg-gsms-opcode:opname=test2:ndfltact=dupdisc:npci=1-1-1:nssn=5:nmapset=8
chg-gsms-opcode:opname=ts4:ndfltact=forward:npc=1-1-2:nssn=5:nmapset=dflt
chg-gsms-opcode:opname=test:nri=ssn
chg-gsms-opcode:opname=test4:ntt=12
Dependencies
At least one optional parameter must be specified.
If the ndfltact parameter is specified, one of the following values must be specified: pass, discard, atierr, route, forward, duplicate, or dupdisc.
If the ndfltact parameter is specified and its value is forward, duplicate, or dupdisc, the npc/npca/npci /npcn/npcn24 and nssn parameters must be specified.
The word none cannot be specified as a value for the opname or nopname parameter.
If the npc/npca/npcinpcn/npcn24 and nssn parameters are specified with the ndfltact parameter, the ndflact parameter must have a value of forward, duplicate, or dupdisc.
The npc/npca/npci/npcn/npcn24 and nssn parameters must be specified before the force parameter can be specified.
The value specified for the opname parameter must already exist in the GSM Map Op-Code table.
The GSM Map Screening feature must be turned on before this command can be entered.
The EGMS feature must be enabled and turned on before the npc or npca parameters can be specified.
The ndfltact=atierr parameter cannot be specified unless the value of the operation code referenced by the opcode parameter is 71 . The atierr option is valid only for ATI MAP operation codes, and the opcode=71 parameter signifies an ATI MAP operation code.
The value specified for the npc/npca/npci/npcn /npcn24 parameter must be a full point code.
The GSM Map Op-Code table must be accessible.
The Route table must be accessible.
If the npc/npca/npci/npcn/npcn24 parameter and the nssn parameter are specified, and the force parameter is not specified as yes, the PC-SSN must be populated in the SCCP Application entity set (Remote Point Code / Mated Application Table).
If specified, the npc/npca/npci/npcn/npcn24 parameter value must exist as a destination in the Ordered Route entity set or reside in a cluster (ANSI only) that exists as a destination in the Ordered Route entity set (for global title routing).
If the opname parameter is specified, the value must be alphanumeric.
The opname parameter value and the nopname parameter value must be no more than 8 characters long.
The nmapset parameter must be specified if the value of the ndfltact parameter is forward, duplicate, or dupdisc.
If the ndfltact parameter is specified with the nmapset, nri, ntt, pc, or ssn parameter, then the ndfltact parameter must have a value of forward, duplicate, or dupdisc.
The nmapset parameter must be specified before the force parameter can be specified.
The Flexible GTT Load Sharing feature must be enabled before the nmapset parameter can be specified.
The specified new MAP set must exist.
If the nmapset=dflt parameter is not specified, or the nmapset=dflt parameter is specified, but the force=yes parameter is not specified, then the new PC and new SSN must exist in the new MAP set.
If the nmapset, nri, or ntt parameter is specified, and the ndfltact parameter is not specified, then the dfltact parameter must have a previously provisioned value of forward, duplicate, or dupdisc .
The MAP table must be accessible.
If the value of the ndfltact parameter is forward, duplicate, or dupdisc, then the value specified for the npc/npca/npci/npcn/npcn24 parameter cannot be associated with a proxy point code.
If the nri=ssn parameter is specified, then the ssn=none parameter cannot be specified.
If the Flexible GTT Load Sharing feature is enabled, and the new or previously provisioned subsystem number has a value of none, then the new or previously provisioned MAP set and point code combination must already exist in the MAP table.
If the Flexible GTT Load Sharing feature is not enabled, and the new or previously provisioned subsystem number has a value of none (the nssn=none parameter is specified in this command, or the ssn=none parameter was specified in the ent-gsms-opcode command), then the point code must already exist in the MAP table.
Notes
In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).
Output
chg-gsms-opcode:opname=test4:ntt=12
tekelecstp 08-08-20 19:13:01 EST EAGLE 39.2.0
CHG-GSM-OPCODE: MASP A - COMPLTD
;
Related Topics
chg-gsmsmsopts
Use this command to enter GSM SMS system options in the database. This command updates the GSMSMSOPTS table.
Parameters
- bpartygttsn (optional)
- MO SMS B-Party Routing GTT Set name. The GTT set where Global Title Translation lookup on B-Party digits is performed.
- defis41smsc (optional)
- Default IS41 short message service center. The default SMSC where an SRI_SM message received for an own network IS41 subscriber is relayed.
- igmsmsrelay (optional)
- IGM - based SMS relay. This parameter specifies whether IGM relays an SRI_SM message that is received for an own network IS41 subscriber to a default SMSC or sends an SRI_SM-NACK error message.
- is41smscgttsn (optional)
- IS41 SMSC GTT Set name. The GTT set where Global Title Translation lookup on default IS41 SMSC digits is performed.
- mosmsaclen (optional)
-
The number of the digits that are taken from the MO SMS CgPA and used as the Area Code in the MO SMS CdPA.
- mosmsdigmat (optional)
- MO-based SMS Home SMSC match. The method used by the Portability Check for MO SMS or the MO-based GSM SMS NP feature to find a Home SMSC match.
- mosmsfwd (optional)
- MO-based SMS forward. This parameter specifies whether the value of the SCCP CDPA in the MO-based SMS message is modified to the GTA value that is specified by the mosmsgta parameter.
- mosmsgta (optional)
- MO-based SMS GTA. The GTA value that is used to replace the SCCP CDPA value in the MO-based SMS message.
- mosmsgttdig (optional)
-
MO SMS B-Party Routing GTT digits. The digits used for Global Title Translation.
- mosmsnai (optional)
- MO-based SMS NAI. The number conditioning performed on the SMS message destination address before lookup in the number portability database is performed.
- Range:
-
- intl
- Number is treated as INTL (1) for number conditioning
- nai
- The NAI from the SMS message is used to perform number conditioning
- nat
- Number is treated as NATL (2) for number conditioning
- unknown
- Number is treated as UNKNOWN (0) for number conditioning
A value of nai must be specified before the intl, natl, nai1, nai2, nai3, and unkn parameters in the
chg-npp-servcommand can be changed to non-default values for the MOSMSGCDPN service. - Default:
- No change to the current value
- System Default:
- intl
- mosmssa (optional)
- MO-based SMS sub-address. This parameter specifies whether the sub-address is searched in the SMS called party (destination address).
- mosmstcapseg (optional)
- MO-based SMS TCAP Segmentation for GSM. This parameter specifies whether Mobile-Originated segmented TCAP messages are supported.
- mosmstype (optional)
- MO-based SMS type. The value of the entity type that indicates that a successful lookup occurred in the number portability database.
- mtmmsackn (optional)
- MT-Based MMS acknowledgement. The message that is generated in response to a successful number portability database lookup for an SRI_SM message from a Home MMSC.
- mtmmsentylen (optional)
- MT-Based MMS Entity length. The maximum number of digits used from the entity value of a returned RN, SP, or SRFIMSI entity for Multimedia Service (MMS) processing.
- mtmmsgta (optional)
- MT-Based MMS GTA. The GTA that is compared with the SCCP CgPA GTA of an SRI_SM message to determine whether the originator of the message is a Home MMSC.
- mtmmslen (optional)
-
MT-Based MMS Length. The maximum number of digits used in the returned IMSI and/or NNI fields for MMS processing.
- mtmmstype (optional)
- MT-Based MMS type. The value of the entity type that indicates that a successful lookup occurred in the number portability database.
- mtsmsackn (optional)
- MT-Based SMS acknowledgement. The message generated in response to a successful number portability database lookup for an SRI_SM message from a Home SMSC.
- mtsmschksrc (optional)
- MT-Based SMS check source. This parameter specifies whether the SCCP CgPA GTA of a SRI_SM message is validated to determine if the source of the message is a Home SMSC.
- Range:
-
- yes
- The SCCP CgPA GTA of an SRI_SM message is validated
- no
- The SCCP CgPA GTA of an SRI_SM message is not validated
If the mtsmschksrc=yes parameter is specified, and if the incoming SRI_SM message has SCCP CgPA GTA, then the SCCP CgPA GTA must be found in the Home SMSC list for the source of the message to be considered a Home SMSC. If the message is not found in the Home SMSC list, then the MT-Based GSM SMS NP feature does not process the message.
If the mtsmschksrc=no parameter is specified, or if SCCP CgPA GTA does not exist in the incoming message, then the source of the message is considered to be a Home SMSC, and the MT-Based GSM SMS NP feature considers the message for processing.
- Default:
- No change to the current value
- System Default:
- no
- mtsmsdltr (optional)
- MT-Based SMS delimiter. This parameter specifies whether to insert a delimiter digit string before or after the routing number (RN) if the RN is used in the outbound digit format.
Note:
The delimiter string that is inserted is determined by the mtsmsdltrv parameter.
- mtsmsdltrv (optional)
- MT-Based SMS delimiter value. The delimiter digit string that is inserted before or after the RN when the RN is used in the outbound digit format.
- mtsmsimsi (optional)
- MT-Based SMS IMSI. The required format of digits that are encoded in the “IMSI” parameter of the SRI_SM response message.
- Range:
-
- rn
- routing number
- rndn
- routing number and the international dialed or directory number
- ccrndn
- country code, routing number, and national directory or dialed number
- dn
- directory or dialed number
- srfimsi
- IMSI is encoded as the “SRFIMSI” parameter from the number portability database
- mccrndn
- mobile country code, routing number, and directory or dialed number
- Default:
- No change to the current value
- System Default:
- mccrndn
- mtsmsnakerr (optional)
- MT-Based SMS negative acknowledgement error. The TCAP error choice code used in the NACK response message generated for SRI_SM messages.
- mtsmsnni (optional)
- MT-Based SMS network node indicator. The required format of digits that are encoded in the “Network Node Number” parameter of the SRI_SM response message.
- Range:
-
- rn
- routing number
- rndn
- routing number and the international dialed or directory number
- ccrndn
- country code, routing number, and national directory or dialed number
- dn
- Directory or Dialed Number
- srfimsi
- IMSI is encoded as the “SRFIMSI” parameter from the number portability database
- mccrndn
- mobile country code, routing number, and directory or dialed number
- none
- The Network Node Number parameter is not encoded in the response message
- Default:
- No change to the current value
- System Default:
- rn
- mtsmstype (optional)
- MT-Based SMS type. The value of the entity type that indicates that a successful lookup occurred in the number portability database for messages that are modified by the MT-Based GSM SMS NP feature.
- spfill (optional)
- This parameter specifies whether the Numbering Plan Processor (NPP) can populate SP and RN entities for own network subscribers at the same time.
- sporttype (optional)
- Service Portability type. This parameter specifies whether Service Portability is performed for the associated feature.
The S-Port feature must be enabled before this parameter can be specified. The S-Port feature must be turned on before any change to the parameter will impact the associated feature.
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’entity id) is applied.
Example
chg-gsmsmsopts:mosmsnai=intl:mosmstype=sp:mosmssa=no
chg-gsmsmsopts:mosmsfwd=no:mosmsgta=987654321
chg-gsmsmsopts:srismdn=tcap
chg-gsmsmsopts:mtsmsackn=nack:mtsmsdltr=no:mtsmsdltrv=125:mtsmschksrc=no
chg-gsmsmsopts:mtmmsgta=51111:mtmmstype=sp:mtmmsackn=nack:mtmmsentylen=7:mtmmslen=10
chg-gsmsmsopts:mosmsdigmat=bestfit
chg-gsmsmsopts:bpartygttsn=setint001:mosmsgttdig=mapbparty
chg-gsmsmsopts:mosmsaclen=4
chg-gsmsmsopts:mosmstcapseg=on
Dependencies
At least one parameter must be specified.
The Hex Digit Support for GTT feature must be enabled before a hexadecimal value for the mosmsgta parameter can be specified.
The mosmsgta parameter must be specified before the mosmsfwd=yes parameter can be specified.
The mtsmsdltrv parameter must be provisioned before a value of prern or postrn can be specified for the mtsmsdltr parameter.
The value specified for the bpartygttsn or is41smscgttsn parameter must match the name of an existing GTT Set.
The mosmsgttdig=sccpcdpa parameter must be specified before the bpartygttsn=none parameter can be specified.
The GTT set specified for the bpartygttsn or is41smscgttsn parameter must have settype=cdgta (see the ent-gttset command).
If the bpartygttsn=none parameter is specified, then the mosmsgttdig=mapbparty parameter cannot be specified.
The GTT Set table is corrupt or cannot be found.
The EGLEOPTS table is corrupt or cannot be found.
The MO-based GSM SMS NP, MO SMS ASD, or MO SMS GRN feature must be enabled before the mosmsfwd or mosmsgta parameter can be specified.
The Portability Check for MO SMS feature or the MO-based GSM SMS NP feature must be turned on before the mosmsdigmat or mosmstcapseg parameter can be specified.
The MT-Based GSM SMS NP feature must be enabled before the mtsmsimsi, mtsmsnni, mtsmstype, mtsmsackn, mtsmsdltr, mtsmsdltrv, mtsmsnakerr, mtsmschksrc, or srismdn parameter can be specified.
The MT-Based GSM MMS NP feature must be enabled before the mtmmsgta, mtmmstype, mtmmsackn, mtmmsentylen, or mtmmslen parameter can be specified.
The MO SMS B-Party Routing feature must be enabled before the bpartygttsn or mosmsgttdig parameter can be specified.
The MO-based GSM SMS NP feature must be enabled before the mosmstype, defrn, or spfill parameter can be specified.
The MO SMS ASD, MO SMS GRN, MO-based GSM SMS NP, or Prepaid SMS Intercept Phase 1 feature must be enabled before the mosmsaclen, mosmsnai, or mosmssa parameter can be specified.
If a digit string value has already been specified for the mosmsgta or mtsmsdltrv parameter, then a value of none cannot be specified subsequently for that parameter.
The IS41 GSM Migration feature must be turned on before the igmsmsrelay, is41smscgttsn, or defis41smsc parameter can be specified.
If the defis41smsc=none parameter is specified, then the igmsmsrelay=yes parameter cannot be specified.
If the defis41smsc parameter has a value other than none, then the is41smscgttsn=none parameter cannot be specified.
The S-Port feature must be enabled before the sporttype parameter can be specified.
The EGTT feature must be turned on before the is41smscgttsn parameter can be specified.
Notes
The mosmstcapseg parameter is turned off automatically if the Portability Check for MO SMS feature is turned off or the temporary FAK for the feature expires, and the MO-based GSM SMS NP feature is not enabled.
Output
chg-gsmsmsopts:is41smscgttsn=set1:defis41smsc=1234:igmsmsrelay=yes
tekelecstp 09-06-08 18:52:54 EST EAGLE 41.1.0
CHG-GSMSMSOPTS: MASP A - COMPLTD
;
Related Topics
chg-gta
Use this command to change the global title address information (GTA) for applicable global title selectors required to specify a global title entry.
This command changes the routing objects for messages requiring global title translations. The specified point code, subsystem number, MRN set ID, and routing indicator overwrite the existing data values.
When the Intermediate GTT Load Sharing feature and the Flexible GTT Load Sharing feature are both on, multiple relationships can be defined among a set of destination point codes in the existing MRN table. The relationship used in a particular translation is based on the GTA digits used for translation. The MRN Set ID and the post-translation PC create a key that is used to perform a lookup in the MRN table. This lookup results in a set of alternate PCs from which a PC is selected, based on relative cost, to route the MSU in most cost-effective way.
Note:
If the EGTT feature is turned on, then the GTT Selector (ent/chg/dlt/rtrvgttsel), GTT Set
(ent/dlt/rtrv-gttset), and GTA
(ent/chg/dlt/rtrvgta) commands replace the Translation Type
(ent/dlt/rtrv-tt) and Global Title Translation
(ent/chg/dlt/rtrv-gtt) commands. It is not recommended to
run
ent/dlt/rtrv-tt & ent/chg/dlt/rtrv-gtt commands
as it may cause the advance GTA fields of GTT entry to be reset to the default
values.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- gttsn (mandatory)
- GTT set name. A GTT set is an entity to which global title addresses and selectors are assigned.
- cggtmod (optional)
- Calling party GT modification indicator. This parameter specifies whether calling party global title modification is required.
- cgpc (optional)
- ANSI CgPA point code with subfields
network
indicator-network cluster-network cluster member (ni-nc-ncm).
- Range:
- 0-255, *
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
The asterisk (*) value is not valid for the ni subfield.
When
chg-sid:pctype=ansiis specified, ni=000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni=001–005.When
chg-sid:pctype=ansiis specified, nc=000 is valid if ni=006–255.When
chg-sid:pctype=ansiis specified, ni-*-* is valid if ni =006–255.The point code 000-000-000 is not a valid point code.
- cgpcaction (optional)
-
This parameter is used to provide the required abilities, indicating what any particular translation needs to do with CgPA PC.
- cgpci (optional)
- ITU international CgPA point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- cgpcn (optional)
- ITU national CgPA point code in the format of a
5-digit number (nnnnn);
or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by
the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- cgpcn16 (optional)
- 16-bit ITU national CgPA point code with subfields unit number-sub number area-main number area (un-sna-mna).
- cgpcn24 (optional)
- 24-bit ITU national CgPA point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- defmapvr (optional)
- Default MAP version for a MAP message. This parameter is used to provide the default MAP version for a MAP message if ACN (Application Context Name) is not present in an incoming MAP message.
- dpc (optional)
- ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- dpci (optional)
- ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- dpcn (optional)
- ITU destination point code in the format of a
5-digit number (nnnnn);
or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by
the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- dpcn16 (optional)
- 16-bit ITU national destination point code with subfields unit number-sub number area-main number area (un-sna-mna).
- dpcn24 (optional)
- 24-bit ITU national destination point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- eaddr (optional)
- End Address (Similar to EGTA). This parameter
specifies the end of a range of MAP digits
(IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).
- Range:
- 1--21 digits
If the Hex Digit Support for GTT feature is not enabled, the range is 1 - 21 decimal digits; valid digits are 0-9.
If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.
- Default
- Same as the specified SADDR value
- egta (optional)
- End global title address. The end of a range of
global title digits.
- Range:
- 1 - 21 digits
If the Hex Digit Support for GTT feature is not enabled, the range is 1-21 decimal digits; valid digits are 0-9.
If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.
- Default:
- Same as the specified gta value
- fallback (optional)
- Fallback option. The action that is taken if the last translation doesn't match when performing GTT using a FLOBR-specific GTT mode.
- opc (optional)
- ANSI originating point code with subfields
network
indicator-network cluster-network cluster member (ni-nc-ncm).
- Range:
- 0-255, *
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
The asterisk (*) value is not valid for the ni subfield.
When
chg-sid:pctype=ansiis specified, ni=000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni=001–005.When
chg-sid:pctype=ansiis specified, nc=000 is valid if ni=006–255.When
chg-sid:pctype=ansiis specified, ni-*-* is valid if ni =006–255.The point code 000-000-000 is not a valid point code.
- opci (optional)
- ITU international originating point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- opcn (optional)
- ITU national originating point code in the format
of a 5-digit number (nnnnn); or 2, 3, or 4
numbers (members) separated by dashes (m1-m2-m3-m4) as defined by
the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- opcn16 (optional)
- 16-bit ITU national originating point code with subfields unit number-sub number area-main number area (un-sna-mna).
- opcn24 (optional)
- 24-bit ITU national originating point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- pc (optional)
- ANSI point code with subfields
network
indicator-network cluster-network cluster member (ni-nc-ncm). The
prefix
subfield indicates a private point code (prefix-ni-nc-ncm).
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- pci (optional)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- pcn (optional)
- ITU national destination point code in the format
of a 5-digit number (nnnnn); or 2, 3, or 4
numbers (members) separated by dashes (m1-m2-m3-m4) as defined by
the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pcn16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). The prefix subfield indicates a private point code (prefix- un-sna-mna).
- pcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).
- pkgtype (optional)
- The ANSI and ITU TCAP package type.
- Range:
-
- ansiuni
- ANSI unidirectional
- ansiabort
- ANSI abort
- any
- Wildcard value
- bgn
- Begin
- cnt
- Continue
- cwp
- Conversation with Permission
- cwop
- Conversation without Permission
- end
- End
- ituabort
- ITU abort
- ituuni
- ITU unidirectional
- resp
- Response
- qwp
- Query with Permission
- qwop
- Query without Permission
- ANSI TCAP Package Types
- ansiuni, qwp, qwop, resp, cwp, cwop, ansiabort, any
- ITU TCAP Package Types
- bgn, ituabort, ituuni, any, end, cnt
- ppmeasreqd (optional)
- Per Path Measurement required. This parameter specifies whether to perform per path measurements.
- saddr (optional)
- Start Address (Similar to GTA). The beginning of a
range of MAP digits (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).
- Range:
- 1--21 digits
If the Hex Digit Support for GTT feature is not enabled, the range is 1 - 21 decimal digits; valid digits are 0-9.
If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.
- Default
- Same as the specified SADDR value
- testmode (optional)
- This parameter invokes a Test Tool that is used to
debug the FLOBR/TOBR rules.
Caution:
If the testmode=on parameter is specified, then the rule is used only by test messages and is ignored by live traffic. If the testmode=off parameter is specified, then both test and live messages use the rule. Changing from testmode=off to testmode=on is equivalent to deleting the rule for live traffic.
Example
chg-gta:gttsn=lidb:gta=9195554321:xlat=dpcssn:ri=ssn:pc=001-255-252:ssn=254
chg-gta:gttsn=test:gta=100000:egta=199999:pca=1-1-1:xlat=dpcngt:ri=gt:gtmodid=set1
chg-gta:gttsn=setnat003:gta=987658321198765432102:pcn=s-129
chg-gta:gttsn=itui1:gta=987658321198765432112:pci=s-1-210-1
chg-gta:gttsn=setnat003:gta=987658321198765432122:pcn=s-128-aa
chg-gta:gttsn=setmap:gta=2345678911:egta=3456789022:ri=ssn:pc=2-2-2:ssn=221:mapset=dflt
chg-gta:gttsn=setopcode:pci=3-3-2:opcode=*:pkgtype=bgn:acn=*:prio=1024
In this example, the database contains a GTA range [5556000-5558000], but no part of the GTA range [5558001-5559000] exists. The command deletes the GTA range [5556000-5558000] from the database and adds two new GTA ranges [5556000-5556799] and [5556800-5559000].chg-gta:gttsn=tst1:gta=5556800:egta=5559000:split=yes
This example deletes the GTA range [5556000-5556799] from the database and adds a new GTA range [5556200-5556500] to the database. All the parameters for the GTA range [5556200-5556500] have the same values as that of the deleted [5556000-5556799] GTA range, except the pc parameter that is has a value of 1.
chg-gta:gttsn=tst1:gta=5556200:egta=5556500:pc=1-1-2:split=no
This example deletes the GTA range [5556200-5556500] from the database and adds two new GTA ranges [5556200-5556400] and [5556401-5556500] to the database.
chg-gta:gttsn=tst1:gta=5556401:egta=5556500
This example specifies the default MRN set.chg-gta:gttsn=setmrn:gta=1234567880:pc=1-1-2:mrnset=dflt
This example removes the MRN set ID.chg-gta:gttsn=setmrn:gta=1234567890:egta=2234567890:pc=1-1-2:mrnset=none
chg-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901: optsn=cggta1:opcsn=opc1
chg-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901: cgselid=1024:opcsn=opc1
chg-gta:gttsn=setcdgta:gta=123456789012345678901:egta=223456789012345678901: optsn=none
chg-gta:gttsn=setopc:opca=002-001-001:xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20:optsn=setcgssn
chg-gta:gttsn=setcgpc:cgpca=001-001-001:xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20:optsn=setcgssn
chg-gta:gttsn=setcgssn:cgssn=100:ecgssn=200:xlat=dpcssn:ri=ssn: pca=001-001-001:ssn=20
chg-gta:gttsn=set1:gta=2543:egta=2943:actsn=actdisc1:ppmeasreqd=yes
chg-gta:gttsn=set2:cgpc=1-2-*:actsn=actudts1
chg-gta:gttsn=set3:opcn=2543:actsn=actudts1
chg-gta:gttsn=set4:cgssn=25:ecgssn=29:actsn=actdup1:xlat=dpc:ri=gt:pc=1-1-1
This example specifies hexadecimal digits for the gta and egta parameters.chg-gta:gttsn=set1:gta=abcd:egta=abce
chg-gta:gttsn=setmap:gta=2345678901:egta=3456789012:ri=ssn:pc=1-1-3:ssn=225:mapset=2:loopset=raleigh1
This example specifies that calling party GT modification is required.chg-gta:gttsn=setans004:cggtmod=yes:gta=981234
This example changes the GTA translations when the FLOBR feature is turned on.chg-gta:gttsn=setcdgta:gta=1234567890:egta=2234567890: xlat=dpcssn:ri=ssn:pca=001-001-001:ssn=100:fallback=no:testmode=on
This example changes the GTA translations when the OBSR feature is enabled and the FLOBR feature is turned on.chg-gta:gttsn=setcdgta:gta=1234567890:egta=2234567890: xlat=dpcssn:ri=ssn:pc=2-2-2:ssn=100:fallback=yes:optsn=setcggta:testmode=on
This example changes the GTA translations when the FLOBR feature is turned on.chg-gta:gttsn=setcdssn:cdssn=15:ecdssn=29:xlat=dpc:pc=1-1-1:ri=gt
This example changes the GTA translations when the TOBR and OBSR features are turned on.chg-gta:gttsn=setopcode:pkgtype=qwop:opcode=none:family=*:xlat=dpc:ri=gt: pc=2-2-2:opcsn=setopc:optsn=setcdgta
chg-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:acn=1-22-123-43-54-65-76: xlat=dpc:ri=gt:pc=2-2-2:opcsn=setopc:optsn=setcdgta
chg-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:family=*:xlat=dpc:ri=gt: pc=2-2-2:optsn=imsi1:defmapvr=v3
chg-gta:saddr=1234567890:eaddr=2234567890:gttsn=setmsisdn
This example changes the GTA translation for a DPC GTT set when the FLOBR feature is turned on.chg-gta:gttsn=setdpc:dpc=1-1-1:optsn=setc1
chg-gta:gttsn=setcdgta:gta=78901234:xlat=dpc:gtmodid=none
chg-gta:gttsn=setcdgta:gta=123456789012345678901:xlat=none:gtmodid=gttsn1
chg-gta:gttsn=setopcode:pkgtype=bgn:opcode=none:acn=1-2-3-4-5-6-7:xlat=none:mapset=1
chg-gta:gttsn=setcdgta:gta=123456:xlat=none:mapset=1:mrnset=2
Example for 16 bit PC and CGPCACTION param.
chg-gta:gttsn=gtt1:xlat=dpc:ri=ssn:pcn16=1-14-0:cgpcn16=45-1-0:mapset=dflt:
cgpcaction=remove
chg-gta:gttsn=imei1:saddr=98765432112:xlat=dpc:ri=gt:pci=1-210-1:transmeasrqd=yes
Dependencies
The EGTT feature must be turned on before this command can be entered.
The ANSI/ITU SCCP Conversion feature must be enabled before a translated point code that is of a different domain than the GTT set specified by the gttsn parameter can be specified.
At least one optional parameter must be specified.
The gttsn=none parameter cannot be specified.
The point code specified for the pc parameter must be a full point code.
The values of the gta/saddr and egta/eaddr parameters must be the same length.
If the specified or previously provisioned translated
point code is of type ANSI, then the
ngti value of the referred GT
Modification Identifier (see the
ent-gtmod command) must be 2.
The length of the specified gta/saddr parameter must match the number of digits provisioned for the specified GTT set when the VGTT feature is turned off. If the VGTT feature is turned on, then up to 10 GTA/SADDR lengths can exist per GTT set. If the Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA/SADDR lengths can exist per GTT set.
The specified gta/egta or saddr/eaddr range must exist for the specified GTT set in the STP active database. While an exact match is not required, an overlap with another range cannot be specified. If the range overlaps, an error is generated that displays a list of overlapped global title addresses. An example follows that shows what happens when the user attempts to enter a range (such as 8005550000 to 8005559999) that overlaps an existing range. The overlapping links must match. If they do not, error message E2401 is generated displaying the list of overlapped global title addresses:
The following GTA ranges overlap the input GTA range START GTA END GTA 8005550000 8005551999 8005552000 8005553999 8005554000 8005555999 CHG-GTA: MASP A - Command AbortedIf a new or existing xlat=dpcngt parameter is specified, a new or existing ri=gt parameter must be specified.
If the ssn parameter is specified, a new or existing xlat=dpcssn parameter must be specified.
If the xlat=dpcssn parameter is specified, the ssn parameter must be specified.
If the pc/pca/pci /pcn/pcn24/pcn16 parameter is specified, and the point code is the STP true point code, then the value of the new or existing xlat parameter must be dpcssn, and the new or existing value of the ri parameter must be ssn.If the pc/pca/pci/pcn/pcn24/pcn16 parameter, ssn parameter, or both, are specified, and the point code is the STP true point code, the ssn value must exist in the SS-APPL table.
If the pc/pca/pci/pcn/pcn24/pcn16 parameter is specified, then it must exist as a destination in the Route table or reside in a cluster that exists as a destination in the Route table (for global routing) unless the point code is the STP’s true point code.
If new or existing ri=ssn and xlat=dpc parameters are specified, and the pc/pca/pci/pcn/pcn24/pcn16 parameter is not specified, then the existing PC must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.
If new or existing ri=ssn, xlat=dpc, and pc/pca/pci/pcn/pcn24/pcn16 parameters are specified, the new point code must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.
If a new or existing ccgt=yes parameter is specified, a new or existing ri=ssn parameter must be specified.
If the new or existing pc/pca/pci/pcn/pcn24/pcn16 parameter is an the STP point code or capability point code, then the ccgt=no parameter must be specified.
If new or existing ri=ssn and xlat=dpcssn parameters are specified, a new or existing xlat=dpcssn parameter must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.
The GTT table cannot be full.
If the ri=gt parameter is specified, the mrnset parameter must be specified. If the ri=gt parameter is not specified, the mrnset parameter cannot be specified
If the Flexible GTT Load Sharing feature is enabled, the specified PC must already exist in the specified MRN set.
The specified MRN set must already exist in the MRN table.
If the Flexible GTT Load Sharing feature is enabled, the specified PC must exist in the MRN set.
The Flexible GTT Load Sharing feature must be enabled before the mrnset parameter can be specified.
If the ri=gt parameter is specified, the mrnset parameter must be specified. If the ri=ssn parameter is specified, the mrnset parameter cannot be specified.
The SEAS command can operate only on the default MRN set or the default MAP set.
The MRN table is corrupt or cannot be found.
If the ri=ssn parameter is specified, the mapset parameter must be specified. If the ri=gt parameter is specified, the mapset parameter cannot be specified.
Note: The mapset parameter can only be specified if the Flexible GTT Load Sharing feature is enabled.
The Flexible GTT Load Sharing feature must be enabled before the mapset parameter can be specified.
The specified MAP set must exist in the database.
The specified or previously provisioned PC/SSN must exist in the specified or previously provisioned MAP set.
The SEAS command cannot operate on any MAP set other than the default MAP set.
If the xlat=dpc parameter is specified, and the value of the force parameter is not yes, then the point code and MAP set must exist in the MAP table.
The MAP table is corrupt or cannot be found.
The specified GTA/SADDR must occur within an existing GTA range in the specified GTT Set.
The gta, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, cgssn/cdssn, opcode/acn/pkgtype, opcode/family/pkgtype, dpc/dpca/dpci/dpcn/dpcn24/dpcn16, or saddr parameter must be specified.
The FLOBR feature must be turned on before the cgssn, opcsn, optsn, and cgselid parameters can be specified in the same command.
The pc/pca/pci/pcn/pcn24/pcn16, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, and dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameters must have values within the valid range for each subfield.
The value specified for the ecgssn/ecdssn parameter must be greater than the value specified for the cgssn/cdssn parameter.
The specified GTT set must have a set type of
opcode (see the
ent-gttset command) before the
opcode/acn/pkgtype or
opcode/family/pkgtype
parameters can be specified. The specified GTT set must
have a set type of
cdssn, cgssn, cdgta/cgta, opc, or
cgpc before the
cdssn, cgssn, gta, opc, or
cgpc parameter, respectively, can be
specified.
The OBSR feature must be enabled before the opcsn, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, or (e)cgssn parameters can be specified.
If the GTT set specified by the
gttsn parameter (GTTSN set) has a
set type of
cdgta (see the
ent-gttset command), then the
optsn parameter cannot specify a GTT
set (OPTSN set) with a set type of cgssn.
The OPTSN set must have a set type of
cggta or
cgpc.
The FLOBR feature must be turned on before a GTTSN set with a set type of cgpc, cggta, or opc can be specified with an OPTSN with a set type other than cgssn.
If the FLOBR feature is turned on, and the GTTSN set has a set type of cdgta or cdssn, then the OPTSN set cannot have a set type of opc.
If the TOBR feature is turned on, and the GTTSN set has a set type of opcode, then the OPTSN set cannot have a set type of opc.
If the GTTSN set has a set type of MBR (imei/imsi/vlrnb/msisdn/smrpda/smrpoa), then the OPTSN set type cannot have the same set type as GTTSN.
If the OPTSN set has a set type of MBR (imei/imsi/vlrnb/msisdn/smrpda/smrpoa), then the GTTSET must have a set type of MBR (imei/imsi/vlrnb/msisdn/smrpda/smrpoa) or opcode.
The
cdselid, cgselid, and
optsn parameters cannot be specified
together in the command. If the GTTSN has a set type of
cdgta,
cdssn, or
opcode (see the
ent-gttset command) then the
opcsn parameter can be specified if
one of the other exclusive parameters is specified.
The gta parameter must be specified if the GTTSN set type has a value of cdgta or cggta. The gta parameter cannot be specified for other set types.
The cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameter must be specified if the GTTSN set type has a value of cgpc. The cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameter cannot be specified for other set types.
The opc/opca/opci/opcn/opcn24/opcn16 parameter must be specified if the GTTSN set type has a value of opc. The opc/opca/opci/opcn/opcn24/opcn16 cannot be specified for other set types.
The cgssn parameter must be specified if the GTTSN set type is cgssn. The cgssn parameter cannot be specified for other set types.
The range specified by the cgssn/ecgssn and cdssn/ecdssn parameters cannot overlap a currently existing range for the specified GTT set.
The GTT set specified by the
opcsn
parameter must have a set type of
opc
(see the
ent-gttset
command).
If the specified GTT set is an ANSI set, the cgpc/cgpca, opc/opca, and dpc/dpca parameters must be valid ANSI point codes. If the specified GTT set is an ITU set, the cgpci/cgpcn/cgpcn24/cgpcn16, opci/opcn/opcn24/opcn16, and dpci/dpcn/dpcn24/dpcn16 parameters must be valid ITU point codes.
The set domain of the opcsn parameter must be the same as the set domain of the gttsn parameter. For example, if the set domain of the gttsn parameter is ANSI, then the set domain of the opcsn parameter must be ANSI. If the set domain of the gttsn parameter is ITU, then the set domain of the opcsn parameter must be ITU.
The range specified by the cgssn/ecgssn and cdssn/ecdssn parameters must exist for the specified GTT set in the STP active data base. An exact match is not required.
The translation entry associated with the specified point code (dpc/dpca/dpci/dpcn/dpcn24/dpcn16, pc/pca/pci/pcn/pcn24/pcn16, or opc/opca/opci/opcn/opcn24/opcn16) or opcode must already exist.
The cgpc, cgssn, gta, opc, cdssn, opcode and saddr parameters cannot be specified in the same command.
If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing.
The Hex Digit Support for GTT feature must be turned on before hexadecimal digits can be specified for the gta/saddr or egta/eaddr parameters.
The SCCP Loop Detection feature must be enabled before the loopset parameter can be specified.
The value of the loopset parameter must already exist in the database.
The Loopset table is corrupt or cannot be found.
The value specified for the egta/eaddr parameter must be greater than value specified for the gta/saddr parameter.
The value specified for the pc parameter cannot be associated with a proxy point code.
The AMGTT feature or the AMGTT CgPA Upgrade feature must be turned on before the cggtmod parameter can be specified.
The FLOBR feature must be turned on before the fallback, cdselid, (e)cdssn, or dpc parameter can be specified.
The FLOBR feature must be turned on before the
gttsn
parameter can specify a GTT set with a set type other
than cdgta (see the
ent-gttset command) in the same
command with the
cgselid parameter.
The OBSR feature must be enabled or the FLOBR feature must be turned on before the cgselid parameter can be specified.
The same value cannot be specified for the gttsn and optsn parameters.
The ANSI/ITU SCCP Conversion feature must be enabled before the GTT set specified by the optsn parameter can have a different domain than the GTT set specified by the gttsn parameter.
A TOBR quantity feature must be turned on before the opcode, pkgtype, acn, family, saddr, eaddr or defmapvr parameter can be specified.
The opcode, pkgtype, and family parameters must be specified together for ANSI TCAP translations. The opcode, pkgtype, and acn parameters must be specified together for ITU TCAP translations.
If the GTT set specified by the
gttsn parameter has a set type of
opcode (see the
ent-gttset command), then the
opcode/acn/pkgtype
or
opcode/family/pkgtype parameters
must be specified. These parameters cannot be specified if the GTT set has of
any other set type.
If the GTT set specified by the
gttsn parameter has a set type of
cdssn (see the
ent-gttset command), then the
cdssn parameter must be specified.
This parameter cannot be specified if the GTT set has any other set type.
The
opcsn parameter can be specified
only if the GTT set specified by the
gttsn parameter has a set type of
cdgta, opcode, or
cdssn (see the
ent-gttset command).
The value specified for the gttsn parameter must match the name of an existing GTT Set.
A value of none must be specified for the optsn, cgselid, or cdselid parameter before the parameter can be changed to another value.
The ANSI/ITU SCCP Conversion feature must be enabled and the FLOBR feature must be turned on before the cgcnvsn parameter can be specified.
The GTT set specified by the
gttsn parameter must have a set type
of
cdgta or
cggta (see the
ent-gttset command), before the
cgcnvsn parameter can be specified.
The value specified for the gttsn parameter cannot be the same as the value specified for the cgcnvsn parameter.
If the family parameter is specified, then the pkgtype parameter must have a value of ansiuni, qwp, qwop, resp, cwp, cwop, ansiabort, or any.
If the acn parameter is specified, then the pkgtype parameter must have a value of bgn, ituabort, ituuni, any, end, or cnt.
The gttsn parameter must be specified and must match an existing GTT set.
The GTT set name specified in the optsn, opcsn, or cgcnvsn parameters must match an existing GTT set name.
If the pkgtype=ituabort parameter is specified, then a value of none must be specified for the acn and opcode parameters.
If the pkgtype=ansiabort parameter is specified then a value of none must be specified for the family and opcode parameters.
The OBSR feature must be enabled or the FLOBR feature must be turned on before the optsn parameter can be specified.
The GTT Action Set specified by the actsn parameter must already exist in the database.
If the GTT set specified by the
gttsn parameter has a set type of
dpc (see the
ent-gttset command), then
the dpc/dpca/dpci/dpcn/dpcn24/dpcn16
parameter must be specified. If the GTT set has a set type
other than
dpc, then the
dpc/dpca/dpci/dpcn/dpcn24/dpcn16
parameter cannot be specified.
The value specified for the
gtmodid parameter must already exist
in the GTMOD table (see the
ent-gtmod command).
The GTMOD table is corrupt or cannot be found.
The values specified for the
gta and
egta parameters must be an exact
match to the GTA values referred in GTT Action Path table (see the
ent-gttapath command).
If the FGTTLS feature is enabled, and the xlat=none parameter is specified, then the mrnset or mapset parameter must be specified.
If the xlat=none parameter is specified, then the ri, pc/pca/pci/pcn/pcn24/pcn16, force, ssn, and ccgt parameters cannot be specified.
The acn and family parameters cannot be specified together in the command.
If the cgssn parameter is specified, then the (e)cdssn parameter cannot be specified. If the cdssn parameter is specified, then the (e)cgssn parameter cannot be specified.
If the opc or dpc parameter is specified, then the (e)gta, (e)cgssn, (e)cdssn, and opcode parameters cannot be specified.
The J7 Support feature must be enabled before the cgpcn16/opcn16/dpcn16 parameters can be specified.
The J7 Support feature must not be enabled before the cgpcn24/opcn24/dpcn24/cgpca/opca/dpca parameters can be specified.
The SADDR parameter must be specified if the GTT set specified by the gttsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).
If the GTT set specified by the optsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) in the GTA command for an ITU opcode entry, then the package type specified via the pkgtype parameter must be ITU BGN/CNT/END.
The defmapvr parameter can be specified in the GTA command for an ITU opcode entry if the GTT set specified by the optsn parameter is of MBR type (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA).
PRIO parameter can be specified with OPCODE GTT set types only.
PRIO value should lie between 1-1024 (both inclusive)
If the saddr parameter is specified, then the ecgssn/ecdssn parameters cannot be specified.
Notes
The maximum length of the resulting GTA string must not exceed 21 digits when translation is complete.
If a GTT is being deleted or changed and the point code (DPC or RTE) is not found in the route table (unless the point code is the STP’s true point code), then the following message is displayed in the terminal scroll area:
NOTICE: No DPC and/or RTE found for GTT being deleted or changed.
The above situation may occur if the reference count rules were not enforced and a DPC and/or RTE were deleted while being referenced by a GTT entry. This indicates a software error; contact My Oracle Support (MOS).
In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-) and the private and spare point code subtype prefix (ps-). All of the point code types support the private (internal) point code subtype prefix (p-).
When the Flexible GTT Load Sharing feature and the Intermediate GTT Load Sharing feature are on, multiple relationships can be defined among a set of destination point codes in the existing MRN table. The relationship used in a particular translation is based on the GTA digits used for translation. The mrnset parameter and the post-translation PC create a key that is used to perform a lookup in the MRN table. This lookup results in a set of alternate PCs, from which a PC is selected, based on relative cost, to route the MSU in most cost-effective way.
When the Flexible GTT Load Sharing feature is turned on, multiple relationships can be defined among a set of PC/SSN pairs in the existing MAP table. The relationship used in a particular translation is based on the GTA digits used for translation.
When the Origin-based SCCP Routing feature is enabled, the CdPA GTA entry can be provisioned in addition to the CgPA GTA, CgPA PC, CgPA SSN, and OPC entries. When provisioning, the Advanced CdPA GTA entry can associate with the CgPA GTA set or the CgPA PC set, the SELID and/or OPC set; the CgPA GTA, CgPA PC, or OPC can associate with the CgPA SSN set; the CgPA SSN cannot associate with any other GTT set. The Advanced CdPA GTA entry may contain the selector ID along with CgPA information present in the MSU to search the Selector table again for the CgPA GTA or CgPA PC Set.
A loopset consists of a set of point codes that form a routing loop in the network. If the SCCP Loop Detection feature is enabled, then the loopset can be associated with or disassociated from specified translation entries. Loopsets that are associated with translation entries are checked during intermediate and final GTT traffic routing. If a loop exists, then the system can be notified with or without discarding the associated traffic.
If the range specified by the gta and egta parameters does not exactly match the existing range, then the existing range is split. All addresses in the existing range that are outside the range specified by the gta/egta parameters retain the original xlat, ri, pc and ssn parameters. A new range is created that is bounded by the gta/egta parameters. The new range contains new values for the xlat, ri, pc and ssn parameters that are present in the command, while retaining parameter values from the previous range that do not have corresponding new values in the command.
If the FLOBR GTT hierarchy is provisioned on a linkset, then translations do not have to be searched in a predetermined manner. If a translation points to another GTTSET/SELID, then database searches continue. The number of searches is limited by the following conditions:
- The same GTT set name cannot be referred more than once.
- Up to 7 database searches can be performed.
- For MBR, the same GTT settype (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) cannot be referred more than once.
If the FLOBR feature is turned on, then any translation can point to any GTTSETs other than that specified by the GTTSN. The CdPA GTA and CdPA SSN translations can also point to an OPCSN. For CdPA GTA and CdPA SSN translations, if an OPTSN GTTSET/SELID is provisioned apart from an OPCSN, then the OPTSN GTTSET/SELID takes precedence over the OPCSN.
The MBR GTT set types translation entries (IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA) can be configured only when the TOBR feature is turned ON. The GTTSets of the types mentioned above are allowed to be provisioned ONLY in GTA entries from a GTTSet of the type OPCODE or one of the other GTT Set types supported by this feature (SS7 Firewall).
Translations associated with the TOBR feature:
- ANSI Opcode—ANSI opcode specifier, ANSI TCAP Package type, and Family
- ITU Opcode—ITU opcode, ITU TCAP Package Type, and ACN
Translations associated with the FLOBR feature:
- CdPA SSN Translations—Can be configured with routing and flexible routing data. The provisioning rules for CdPA SSN translations are the same as CgPA SSN translations in OBSR.
- DPC Translations—The provisioning rules for DPC translations are the same as OPC translations except that OPCSN parameter cannot be configured for DPC translations.
Output
chg-gta:gttsn=set2:xlat=dpcssn:ri=ssn:pc=3-3-3:ssn=10:cgpc=1-2-*:actsn=actudts1:ppmeasreqd=yes
tekelecstp 10-02-15 17:29:06 EST EAGLE 42.0.0
CHG-GTA: MASP A - COMPLTD
;
chg-gta:gttsn=imsi1:xlat=dpc:ri=gt:pc=1-1-1:saddr=1234567890:eaddr=2234567890
tekelecstp 15-05-24 12:09:18 EST EAGLE 46.3.0
ENT-GTA: MASP A - COMPLTD
;
chg-gta:gttsn=setopcode:pci=3-3-2:opcode=*:pkgtype=bgn:acn=*:
prio=1024
tekelecstp 16-11-07 14:13:13 MST EAGLE 46.5.0.0.0-70.5.0
CHG-GTA: MASP A - COMPLTD
;
chg-gta:gttsn=imei1:saddr=98765432112:xlat=dpc:ri=gt:pci=1-210-1:transmeasrqd=yes
tekelecstp 17-05-11 15:20:06 EST EAGLE 46.6.0
CHG-GTA: MASP A - COMPLTD
;
chg-gtcnv
Use this command to change entries in the Default Global Title Conversion table. A table entry is identified by the direction and the tta or tti parameter, or the tti/np/nai parameter combination. The Notes section for this command describes rules for changing entry information.
Parameters
- nai (optional)
- Nature of address indicator. This parameter is mandatory when gtixlat=24 is specified, and cannot be specified when gtixlat=22 is specified.
- np (optional)
- Numbering plan. This parameter is mandatory when gtixlat=24 is specified, and cannot be specified when gtixlat=22 is specified.
- npdd (optional)
- New prefix digits to be deleted. The number of new prefix digits to be deleted. These digits will be replaced with the new prefix digits string (npds).
- npds (optional)
- New prefix digits string. The new prefix digits string that will replace the received prefix digits.
- Range:
- 1 - 21 digits
If the Hex Digit Support for GTT feature is not enabled and on, the range is 1 - 21 decimal digits; valid digits are 0-9.
If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.
- Default:
- No change to current value
- nsdd (optional)
- New suffix digits to be deleted. The number of new suffix digits to be deleted. These digits will be replaced with the new suffix digits string (nsds).
- nsds (optional)
- New suffix digits string. The new suffix digits string that will replace the received suffix digits.
- Range:
- 1 - 21 digits
If the Hex Digit Support for GTT feature is not enabled and on, the range is 1 - 21 decimal digits; valid digits are 0-9.
If the Hex Digit Support for GTT feature is enabled and on, the range is 1 - 21 hexadecimal digits; valid digits are 0-9, a-f, A-F.
- Default:
- No change to current value
Example
This example changes a dir=atoi entry’s current tti value to 5:
chg-gtcnv:dir=atoi:tta=10:tti=5This example changes a dir=atoi entry’s current tti, nai, and np values to 7, 8, and 6 respectively, and changes or adds NSDD and NSDS values:
chg-gtcnv:dir=atoi:tta=11:tti=7:nai=8:np=6:nsdd=3:nsds=123
This example changes a dir=itoa entry’s current TTA value to 11, and changes or adds NPDD and NPDS values:
chg-gtcnv:dir=itoa:tta=11:tti=7:npdd=3:npds=123This example changes a dir=itoa entry’s TTA value to 12, and changes or adds NSDD and NSDS values:
chg-gtcnv:dir=itoa:tta=12:tti=7:nai=8:np=6:nsdd=5:nsds=45667This example adds or changes a dir=both entry’s NSDD and NSDS values:
chg-gtcnv:dir=both:tta=12:tti=33:nsdd=3:nsds=456This example changes a default dir=atoi entry’s current TTI value to 9, and changes or adds NSDD and NSDS values:
chg-gtcnv:dir=atoi:tta=*:tti=9:nsdd=1:nsds=9This example changes a default dir=atoi entry’s current TTI, NAI, and NP value to 4, 6, and 5 respectively:
chg-gtcnv:dir=atoi:tta=*:tti=4:nai=6:np=5This example changes a default dir=itoa entry’s current TTI value to 17, and changes or adds NPDD and NPDS values:
chg-gtcnv:dir=itoa:tta=17:tti=*:nai=*:np=*:npdd=3:npds=123This example resets existing NPDD/NPDS or NSDD/NSDS values to "no digit modification":
chg-gtcnv:dir=both:tta=12:tti=11:rdmod=yesThis example specifies hexadecimal digits for NSDS:
chg-gtcnv:dir=atoi:tta=*:tti=4:npdd=3:npds=abc1234fedDependencies
The ANSI/ITU SCCP Conversion feature must be enabled before this command can be entered.
If the dir=atoi parameter is specified, then the tta parameter must be specified.
If the dir=both parameter is specified, then the tta and tti parameters must be specified.
If the dir=both parameter is specified, then a wildcard value (*) cannot be specified for any of the other parameters.
If the dir=atoi parameter is specified, then a value of * can be specified only for the tta parameter.
If the dir=itoa parameter is specified, then a value of * must be specified for the tti, np, and nai parameters.
If the dir=itoa and gtixlat=22 parameters are specified, then a value of * cannot be specified.
The specified dir, tta, tti, np, and nai parameter combination cannot already exist in the database.
The nsdd/nsds and the npdd/npds parameters cannot be specified together in the command.
The Hex Digit Support for GTT feature must be enabled and on before hexadecimal digits can be specified for the npds and nsds parameters.
Notes
The use of asterisks (wildcards) is allowed only once for each direction of ANSI to ITU and ITU to ANSI. This provides a configurable default.
In the conversion direction of ANSI to ITU, an asterisk can be specified only for the ANSI tta parameter.
In the conversion direction of ITU to ANSI, the asterisk value must be specified for the itu, tti, np, and nai parameters.
Asterisks are not allowed when conversion is in both directions (dir=both).
The suffix digit manipulation parameters nsdd and nsds cannot be specified in the same command with the prefix digit manipulation parameters (npdd and npds). The npdd and nsdd parameters specify how many digits to delete, if any, from the beginning or end respectively of the Global Title address digits. The npds and nsds parameters specify what digits, if any, to append to the beginning or end respectively of the Global Title address digits.
The gtixlat parameter is expressed in the form of the ANSI GTI and the ITU GTI. The gtixlat parameter is used to indicate the conversion of the Global Title Indicator between the ANSI and ITU standards. For example: A gtixlat value of 24 converts an incoming ANSI GTI2 to an outgoing ITU GTI 4 or an incoming ITU GTI 4 to an outgoing ANSI GTI2.
Output
chg-gtcnv:dir=atoi:gtixlat=22:tta=10:tti=5
rlghncxa03w 03-11-07 11:43:07 EST EAGLE 31.3.0
CHG-GTCNV: MASP A - COMPLTD
;
Related Topics
chg-gtmod
Use this command to change GT Modification (GTMOD) entry data. The GTMOD entry consists of a GTMOD ID and GTMOD specific data.
Parameters
Note:
Definitions for the feature options specified by the on and off parameters are located in the Notes section.- cgpassn (optional)
- Calling party subsystem number. This parameter specifies the calling party subsystem address that receives the message.
- ngti (optional)
- New Global Title Indicator. This parameter specifies whether a new GTI translation format is type 2 or type 4.
- nnai (optional)
- New nature of address indicator. This parameter specifies the value that is used to replace the received NNAI.
- npdd (optional)
- Number of prefix digits to be deleted. The number of digits to be deleted from the prefix of the received GT address.
- nsdd (optional)
- Number of suffix digits to be deleted. The number of digits to be deleted from the suffix of the received GT address.
- off (optional)
-
Turns off the specified feature options. A comma-separated list of feature options that are requested to be turned off. Up to 8 feature options can be specified in the list.
Example
chg-gtmod:gtmodid=set2:ngti=4:nnp=4:nnai=2:off=gt0fill:npds=2:precd=sfx:nsds=1
chg-gtmod:gtmodid=set3:on=gt0fill:nnp=7:nnai=100:nsdd=2:ntt=none
Dependencies
If the ngti=4 parameter is specified, then the nnp and nnai parameters must be specified.
If the ngti=2 parameter is specified, then the nnp and nnai parameters cannot be specified.
The ANSI/ITU SCCP Conversion feature must be enabled before the ngti parameter can be specified.
The Hex Digit Support for GTT feature must be turned on before hexadecimal digits can be specified for the npds or nsds parameter.
The GTMOD table is corrupt or cannot be found.
At least one optional parameter must be specified.
The AMGTT, AMGTT CdPA Only, or AMGTT CgPA Upgrade feature must be turned on before any parameter except the ntt parameter can be specified.
The value specified for the gtmodid parameter must already exist in the GTMOD table.
If the npdd/npds and nsdd/nsds parameters are specified or were previously provisioned, then the precd parameter must be specified.
The combined digit length of the values for the specified or previously provisioned npds and nsds parameters cannot be greater than 21.
The (n)gtmodid=none parameter cannot be specified.
If the ngti=4 parameter is specified, then the referred translated point code cannot be ANSI. For ANSI point codes, the ngti value must be 2.
If the ngti=4 parameter is specified or was previously provisioned, then a value of none cannot be specified for the nnp and nnai parameters.
If the ngti=none parameter is specified, then the on=gt0fill parameter cannot be specified.
If the on=gt0fill parameter is specified, then the ngti parameter must be specified.
The value specified for the ngtmodid parameter cannot already exist in the database.
The same value cannot be specified for the on and off parameters.
Notes
on/off options
- gt0fill —GT zero fill. Specifies whether the last 0 of the GTA is a treated as a valid digit (OFF) or as filler (ON) during GT Modification for the gti(x)=2 to gti(x)=4 scenario.
Output
chg-gtmod:gtmodid=gtmodid2:ngti=4:nnp=4:nnai=2:off=gt0fill
tekelecstp 10-03-18 14:43:31 EST EAGLE 42.0.0
Command entered at terminal #4
GTMOD table is (2 of 50000) 1% full
CHG-GTMOD: MASP A - COMPLTD
;
Related Topics
chg-gtt
Use this command to change the routing objects for messages requiring global title translation. The global title addresses remain unchanged.
Note:
If the EGTT feature is turned on, then the GTT Selector (ent/chg/dlt/rtrvgttsel), GTT Set
(ent/dlt/rtrv-gttset), and GTA
(ent/chg/dlt/rtrvgta) commands replace the Translation Type
(ent/dlt/rtrv-tt) and Global Title Translation
(ent/chg/dlt/rtrv-gtt) commands. It is not recommended to
run
ent/dlt/rtrv-tt & ent/chg/dlt/rtrv-gtt commands
as it may cause the advance GTA fields of GTT entry to be reset to the default
values.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- cggtmod (optional)
- Calling party GT modification indicator. This parameter specifies whether calling party global title modification is required.
- pc (optional)
- ANSI point code with subfields
network
indicator-network cluster-network cluster member (ni-nc-ncm). The
prefix
subfield indicates a private point code (prefix-ni-nc-ncm).
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- pci (optional)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- pcn (optional)
- ITU national point code in the format of a 5-digit
number (nnnnn); or 2, 3,
or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by
the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc ,prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).
- ri (optional)
- Routing Indicator. This parameter provides routing instructions to the receiving signaling point. In gateway screening, messages may be screened based on the value of the routing indicator.
- type/typea/typei/typen/typen24/typeis/typens (optional)
- Translation type. The translation type and network
type. This parameter is the decimal representation of the 1-byte field used in
SS7.
The type and typea parameters specify an ANSI network.
The typei parameter specifies an ITU-international network.
The typen parameter specifies an ITU-national network.
The typen24 parameter specifies a 24-bit ITU-national network.
The typeis parameter specifies an ITU-international spare network.
The typens parameter specifies an ITU-national spare network.
A translation type numeric value may be entered as an ANSI type (type or typea) and as an ITU type (typei/typen/typen24/typeis/typens). However, they are separate entities.
The point code domain translation types for GTT are handled by the EAGLE protocol processing as either ANSI or ITU; therefore, ITU applies to ITU-I, ITU-I spare, ITU-N, ITU-N spare, and ITU-N24.
Example
chg-gtt:type=5:gta=9195551212:egta=9195551999:xlat=dpcssn:ri=ssn: pc=255-002-001 :ssn=255
chg-gtt:ttn=lidb2:gta=9197771212:egta=9197771999:xlat=dpcngt:ri=gt: pc=255-002-001
chg-gtt:ttn=lidb6:gta=910777:pc=255-002-002
chg-gtt: type=10:gta=8005553232:egta=8005554000:gtmodid=sn1
chg-gtt:type=11:gta=8005553232:egta=8005554000:gtmodid=none
chg-gtt:gta=123456:pci=s-1-129-7:typei=41
chg-gtt:gta=223456:pcn=s-128-aa:typen=3
chg-gtt:ttn=setmrn:gta=1234567890:egta=2234567890:pc=1-1-2:mrnset=none
chg-gtt:ttn=setmrn:gta=2234567891:egta=2234567892:pc=1-1-2:mrnset=dflt
chg-gtt:ttn=setmrn:gta=2345678901:egta=3456789012:pc=1-1-3:mrnset=2
chg-gtt:ttn=setmap:gta=2345678911:egta=3456789022:ri=ssn:pc=2-2-2:ssn=6: mapset=dflt
The database contains a GTA range [5556000-5558000], but no part of the GTA range [5558001-5559000] exists. This example deletes the GTA range [5556000-5558000] from the database and adds a new GTA range [5556800-5559000] to the database.chg-gtt:ttn=tst1:gta=5556800:egta=5559000:split=no
This example deletes the GTA range [5556800-5559000] from the database and adds three new GTA ranges [5556800-5556899], [5556900-5557000] and [5557001-5559000] to the database.chg-gtt:ttn=tst1:gta=5556900:egta=5557000
This example specifies hexadecimal digits for the gta, egta, and nsds parameters.chg-gtt:type=1:xlat=dpcssn:ri=ssn:ssn=10:pc=1-1-1:gta=df3456789012345678906: egta=df345678901234567890a
chg-gtt:ttn=setmap:gta=2345678901:egta=3456789012:ri=ssn:pc=1-1-3:ssn=10:mapset=2: loopset=none:gtmodid=set6
This example specifies that calling party GT modification is required.chg-gtt:gta=981234:type=4:cggtmod=yes
chg-gtt:typeis=5:gta=123456:egta=129999:xlat=dpc:ri=gt:pci=s-1-1-4
chg-gtt:typens=5:gta=123456:egta=129999:xlat=dpc:ri=gt:pcn=s-111
Dependencies
If the
pcn parameter is specified, its
format must match the format that was assigned with
chg-stpopts:npcfmti.
The value specified for the tt parameter must correspond to the value specified for the type/typea/typei/typen/typen24/typeis/typens parameter.
The value of the tt parameter must exist in the Translation Type table.
The ANSI/ITU SCCP Conversion feature must be enabled before a translated point code and a translation type in different network types can be specified.
If the xlat=dpc, ri=ssn, and pc/pca/pci/pcn parameters are specified, then the point code must exist in the MAP table.
If the new or existing xlat parameter value is dpc, the new or existing ri parameter value is ssn, and the pc/pca/pci/pcn parameter is not specified, a point code must exist in the Remote Point Code/MAP table.
If the xlat parameter value is changed from dpcssn to dpc or dpcngt, a new ssn parameter value cannot be specified, and the current ssn parameter value must be removed.
If the new xlat parameter value is dpcssn, and the current ssn parameter value has been removed, a new ssn parameter value must be specified.
The start GTA length must equal the number of digits
specified by the translation type. If the VGTT (variable length GTT) feature is
turned on, then up to 10 GTA lengths per translation type are allowed. When the
ent-gtt command is entered to create
entries, the software keeps track of the lengths and allows only ten different
lengths. The global title address specified for the translation type must then
have the same number of digits as an existing GTA.
If the specified or previously provisioned translated
point code is of type ANSI, then the
ngti value of the referred GT
Modification Identifier (see the
ent-gtmod command) must be 2.
If the egta parameter is specified, the length must equal the length of the start GTA.
If the egta parameter is specified, the value must be greater than the value specified for the gta parameter.
The range of global title addresses to be changed, as specified by the start and end global title addresses, must match exactly or be contained within an existing range in the global title translation data for the specified translation type.
The new gta - egta range cannot include the GTA or EGTA of an existing range. However, the new GTA range can completely fall within an existing GTA range. If the range overlaps, an error is generated that displays a list of overlapped GTAs. An example follows that shows what happens when the user attempts to enter a global title address range (such as 8005550000 to 8005559999) that overlaps an existing range. The overlapping links must match. If they do not, the error message displays the list of overlapped global title addresses:
The following GTA ranges overlap the input GTA range
START GTA END GTA 8005550000 8005551999 8005552000 8005553999 8005554000 8005555999
CHG-GTT: MASP A - Command Aborted The tt parameter cannot be specified with a value that has been defined as an alias for another translation type.
Either the type or the ttn parameter must be specified.
Point code entries must be full point codes. Partial point codes are not allowed.
Table 4-7 Valid Parameter Combinations for chg-gtt Routing Parameters
| New or Existing XLAT Value | New or Existing RI Value | Routing Action | SSN Value |
|---|---|---|---|
|
DPC |
GT |
Translate DPC only and route on GT |
Cannot be specified. The current database entry is removed. |
|
DPC |
SSN |
Translate DPC only and route on SSN |
Cannot be specified. The current database entry is removed. |
|
DPCSSN |
GT |
Translate DPC and SSN and route on GT |
Must be specified |
|
DPCSSN |
SSN |
Translate DPC and SSN and route on SSN |
Must be specified |
|
DPCNGT |
GT |
Translate DPC only and route on GT |
Cannot be specified. The current database entry is removed. |
To enter this command, the Remote Point Code table cannot be full.
To enter this command, the subsystem table for primary remote point codes cannot be full.
If the ri=ssn parameter is specified, the mrnset parameter cannot be specified.
If the Flexible GTT Load Sharing feature is enabled, the point code must already exist in the specified MRN set.
The specified MRN set must already exist in the MRN table.
The Flexible GTT Load-Sharing feature must be enabled before the mrnset parameter can be specified.
The SEAS command is not allowed to operate on any other MRN set except the default MRN set.
The MRN table is corrupt or cannot be found.
The mapset parameter can only be specified if the Flexible GTT Load Sharing feature is enabled, and the ri=ssn parameter is specified. If the ri=ssn parameter is specified, the mapset parameter must be specified. If the ri=gt parameter is specified, the mapset parameter cannot be specified.
If the Flexible GTT Load Sharing feature is not enabled, the mapset parameter cannot be specified.
At least one entry must be provisioned in the specified MAP set in the MAP table.
The MAP table is corrupt or cannot be found.
The specified or previously provisioned point code and subsystem number must exist in the specified or previously provisioned MAP set.
The SEAS command cannot operate on any MAP set other than the default MAP set.
The specified GTA must lie within an existing GTA range in the specified GTT Set.
The specified GTA range must not overlap with any other existing GTA range in the specified GTT Set.
If the Flexible GTT Load Sharing feature is enabled, then the specified PC must exist in the MRN set.
If the ri=gt parameter is specified, the mapset parameter cannot be specified.
The Hex Digit Support for GTT feature must be turned on before hexadecimal digits can be specified for the gta or egta parameter.
The Loopset table is corrupt or cannot be found.
The SCCP Loop Detection feature must be enabled before the loopset parameter can be specified.
The value of the loopset parameter must exist in the Loopset table.
The site identification table is corrupt or cannot be found.
The Route table is corrupt or cannot be found.
The database is corrupt or cannot be found. Severe database failure.
The Loopset table is corrupt or cannot be found.
If the ri=gt parameter is specified, the mrnset parameter must be specified.
The GTT table cannot be full.
If the value of the pc/pca/pci/pcn/pcn24 parameter is the True Point Code, then the xlat=dpcssn parameter and the ri=ssn parameter must be specified.
If the ssn parameter is specified, and if the value of the pc/pca/pci/pcn/pcn24 parameter is the True Point Code, then the value of the ssn parameter must exist in the SS-APPL table.
The value of the pc/pca/pci/pcn/pcn24 parameter must exist as a destination in the ordered route entity set or must reside in a cluster (ANSI only) that exists as a destination in the ordered route entity set.
If the xlat=dpcssn and ri=gt parameters are specified, then the ssn parameter must be specified.
The xlat=dpcssn parameter must be specified before the ssn parameter can be specified.
If the xlat=dpcngt parameter is specified, then the ri=gt parameter must be specified.
The gta length is not defined for the specified translation type entity.
If the tt parameter is not specified, then the value of the ttn parameter must match the value of a tt parameter in the STP database.
The value of the pc/pca/pci/pcn/pcn24 parameter cannot be out of range.
At least one optional parameter must be specified.
The value specified for the pc parameter cannot be associated with a proxy point code.
The AMGTT feature or the AMGTT CgPA Upgrade feature must be turned on before the cggtmod parameter can be specified.
The GTT set associated with the translation type
specified by the ttn parameter must have a
set type of
cdgta (see the
ent-gttset command).
The value specified by the
gtmodid parameter must already exist
in the GTMOD table (see the
ent-gtmod command).
The GTMOD table is corrupt or cannot be found.
The ttn=none parameter cannot be specified.
The network domain of the translation type specified by
the
ttn parameter cannot be CROSS (see
the
ent-gttset command).
The xlat=none parameter cannot be specified.
The values specified for the
gta and
egta parameters must match the GTA
values referred in the GTT Action Path table (see the
ent-gttapath command).
Notes
The specified DPC, SSN, relative cost, and routing indicator will overwrite the existing data values in the table.
When the Intermediate GTT Load Sharing feature and the Flexible GTT Load Sharing feature are on, multiple relationships can be defined among a set of destination point codes in the existing MRN table. The relationship used in a particular translation is based on the GTA digits used for translation. The MRN Set and the post-translation PC formulate a key used as a lookup in the MRN table. The MRN table lookup results in a set of alternate PCs, one of which is selected (based on relative cost) to route the MSU in the most cost effective way.
When the Flexible GTT Load Sharing feature is turned on, multiple relationships among a set of PCs and SSNs in the existing MAP table are supported. The relationship used in a particular translation is based on the GTA digits used for translation. The MAP set ID and PC/SSN formulate a key that is used to perform lookup tasks in the MAP table. The lookup results in a set of mate PC/SSNs, one of which is selected to route the MSU in the most cost effective way.
If the AMGTT feature is turned off, then the Default GT Conversion table is used for conversion.
AMGTT feature: The digit manipulation parameters NSDD, NSDS are enabled with the AMGTT feature. NSDD and NSDS (suffix digit manipulation parameters) are mutually exclusive of the NPDD and NPDS (prefix digit manipulations parameters).
Spare Point Code feature (53120): The point code parameters PCI and PCN supports the Spare Point Code subtype prefix (s-). The Point Code domain translation types for GTT are handled by the system protocol processing as ANSI or ITU. ITU applies to ITU-I, ITU-I Spare, ITU-N, and ITU-N Spare. ITU-I includes ITU-I Spare, and ITU-N includes ITU-N Spare.
Flexible GTT Load Sharing feature (74382): The Flexible GTT Load Sharing feature allows a PC or PC/SSN combination to be provisioned in multiple load-sharing relationships for post-GTT load sharing of intermediate and final GTT traffic.
Load sharing for intermediate GTT traffic requires the Intermediate GTT Load Sharing feature, which can be run in conjunction with the Flexible GTT Load Sharing feature. Intermediate GTT load sharing is performed through the MRN table, and the GTT destination is a PC. If both the Intermediate and Flexible GTT Load Sharing features are on, different load-sharing relationships can be defined between the same set of PCs, and different sets of destinations can contain the same PCs.
Load sharing for final GTT traffic is performed through the MAP table, and the GTT destination is a PC/SSN combination. If the Flexible GTT Load Sharing feature is on, different load-sharing relationships can be defined between the same set of PC/SSNs, and different sets of destinations can contain the same PC/SSN combinations.
A loopset consists of a set of point codes that form a routing loop in the network. If the SCCP Loop Detection feature is enabled, then the loopset can be associated with or disassociated from specified translation entries. Loopsets that are associated with translation entries are checked during intermediate and final GTT traffic routing. If a loop exists, then the system can be notified with or without discarding the associated traffic.
The maximum length of the resulting GTA string must not exceed 21 digits when translation is complete.
If the range specified by the gta and egta parameters does not exactly match the existing range, then the existing range is split. All addresses in the existing range that are outside the range specified by the gta and egta parameters retain the original xlat, ri, pc, and ssn parameters.
A new range is created that is bounded by the gta and egta parameters. The new range contains new values for the xlat, ri, pc, and ssn parameters that are present in the command, while retaining parameter values from the previous range that do not have corresponding new values in the command.
If the EGTT feature is turned on, then the following
occurs for the
chg-gtt command:
- For ANSI, if a GTT selector is deleted using the
dlt-gttselcommand, then the corresponding GTT entry cannot be updated. - For ITU, if a true GTT selector entry (GTI=2 or
GTI=4) is deleted using the
dlt-gttselcommand, or if the GTT set name of an entry is changed using thechg-gttselcommand, then the corresponding GTT entry cannot be updated.
Output
chg-gtt:gta=981234:type=4:cggtmod=yes:gtmodid=set3
tekelecstp 10-03-09 17:29:06 EST EAGLE 42.0.0
CHG-GTT: MASP A - COMPLTD
;
chg-gttact
Use this command to change a Global Title Translation (GTT) Action entry. A GTT Action entry consists of an Action ID, an action, and action specific data. The action specified in the entry determines the process that is performed on the MSU during translation.
Parameters
Note:
Definitions for the feature options specified by the on and off parameters are located in the Notes section.- act (optional)
- Action. The GTT Action that is applied to the
message.
- Range:
-
- disc
- discard message with no return error
- dup
- route a copy of the message to a specified duplicate node
- fwd
- route the original message to a specified forward node instead of the destination indicated by the GTT/ DB data
- scpval
- perform the SCCP MAP validation on MO/MT-FSM messages
- sflog
- send a copy of original message to SFLOG card
- sfthrot
- discard message if threshold is exceeded
- srvc
- apply service (GPORT/GFLEX/SMSMR) on the message
- tcaperr
- discard message that has a specified TCAP error
- udts
- discard message and send UDTS/XUDTS
- atcaperr (optional)
-
ANSI TCAP error cause. The reason for discarding a message that contains the ANSI TCAP portion associated with the tcaperr GTT Action.
- atirescgmodid (optional)
-
Calling party global title modification identifier for ATI. The GTMOD ID to be associated with the calling party of a SFAPP GTT Action entry.
- bursts (optional)
- The number of previous 30 second windows from where the unused capacity can be carried over to the current window.
- cgpc (optional)
- ANSI CgPA point code with subfields
network
indicator-network cluster-network cluster member (ni-nc-ncm). The
prefix
subfield indicates a private point code
(prefix-ni-nc-ncm).
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- cgpci (optional)
- ITU international CgPA point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- cgpcn (optional)
-
ITU national CgPA point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- cgpcn16 (optional)
- 16-bit ITU national CgPA point code with subfields unit number-sub number area-main number area (un-sna-mna). The prefix subfield indicates a private point code (prefix-un-sna-mna).
- cgpcn24 (optional)
- 24-bit ITU national CgPA point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).
- cgpcogmsg (optional)
- The data used as the Calling Party Point Code in the outgoing message.
- defactid (optional)
- Default Action ID. The default action that
is performed when the
fwd GTT Action fails to route the
MSU or when
sfthrot or
scpval GTT Action fails.
- Range:
- ayyyyyyyy
1 leading alphabetic character followed by 8 alphanumeric characters
The defactid parameter can take one of the following values:
- GTT Action ID with a GTT Action of disc, udts, or tcaperr (see the act parameter). This value must already be defined in the GTT Action table.
- fallback —The MSU is routed using routing data in the translated MSU when action is fwd. When action is set to scpval/sfthrot, the MSU is discarded.
- itcaperr (optional)
-
ITU TCAP error cause. The reason for discarding the message that contains the ITU TCAP portion associated with the tcaperr GTT Action.
- ndgt (optional)
- Number of digits to be matched. This parameter is used to specify the number of digits that needs to be matched between the SCCP and MAP parameters.
- off (optional)
-
Disables or turns off the specified feature options. A comma-separated list of feature options that are requested to be turned off. Up to 8 feature options can be specified in the list.
- on (optional)
-
Enables or turns on the specified feature options. A comma-separated list of feature options that are requested to be turned on. Up to 8 feature options can be specified in the list.
- pc (optional)
- ANSI point code with subfields
network
indicator-network cluster-network cluster member (ni-nc-ncm). The
prefix
subfield indicates a private point code
(prefix-ni-nc-ncm).
- Synonym:
- pca
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- pci (optional)
-
ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- pcn (optional)
-
ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pcn24 (optional)
-
24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix subfield indicates a private point code (prefix-msa-ssa-sp).
- pcn16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). The prefix subfield indicates a private point code (prefix-un-sna-mna).
- psirescgmodid (optional)
-
Calling party global title modification identifier for PSI. The GTMOD ID to be associated with the calling party of a SFAPP GTT Action entry.
- ri (optional)
- Routing indicator. The routing indicator in the SCCP called party address of the MSU being processed.
- sprm (optional)
-
SCCP Parameter. This parameter is used to decide whether the SCCP GTA, NP and NAI (if GTI=4 and NP/NAI is present) will be picked up from CDPA or CGPA and used for comparison.
- ssn (optional)
-
Subsystem number. The value used for the SSN in the SCCP called party address of the MSU.
- threshold (optional)
- Throttling threshold. The MSU is discarded if the number of MSUs serviced by the SFTHROT action exceeds this value in a 30 second period.
Example
chg-gttact:actid=dup1:act=dup:ssn=40
Changing the Action Id of the already provisioned GTT Action entry:chg-gttact:actid=dup1:act=dup:nactid=dup2
chg-gttact:actid=disc1:act=tcaperr:atcaperr=10
chg-gttact:actid=actfwd1:act=fwd:pc=2-2-2:ri=gt:defactid=none
chg-gttact:act=dup:actid=dup2:cdgtmodid=set1:cggtmodid=none
chg-gttact:act=dup:actid=dup5:cggtmodid=set4
chg-gttact:actid=actfwd2:act=fwd:pc=2-2-2:ri=gt:defactid=fallback:on=useicmsg
chg-gttact:actid=actfwd3:act=fwd:pc=2-2-2:ri=gt:cgpcogmsg=opcicmsg
chg-gttact:actid=actdup3:act=dup:pc=2-2-2:ri=gt:cgpc=1-1-1:cgpcogmsg=provcgpc
chg-gttact:act=fwd:actid=actfwd5:pcn16=1-14-0:ri=gt:mrnset=dflt:cgpcogmsg=remove
chg-gttact:actid=gflex1:act=GPORT
chg-gttact:actid=actsrvc1:snp=e164:snai=rnndn:srvcerr=gtt
chg-gttact:actid=actsfthrot:threshold=2000:bursts=1
chg-gttact:actid=sflog1:nactid=sflogid1
chg-gttact:actid=scpval1:act=scpval:sprm=cgpa:ndgt=20
chg-gttact:actid=sfapp8:failactid=fallback
chg-gttact:actid=sfapp8:hlraddr=tcapparm:tt=26
chg-gttact:actid=sfapp9:hlraddr=usecdpa
chg-gttact:actid=sfapp10:act=sfapp:atirescgmodid=set1
chg-gttact:actid=sfapp10:psirescgmodid=set5
chg-gttact:actid=sfapp10:on=handlresp
Dependencies
A value of dup or fwd must be specified for the act parameter before the pc/pca/pci/pcn/pcn24/pcn16, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, cgpcogmsg, cdgtmodid, cggtmodid, ssn, ri, mrnset, mapset, or loopset parameter can be specified and before a value of useicmsg can be specified for the on or off parameter.
The act=tcaperr parameter must be specified before the atcaperr and itcaperr parameters can be specified.
The act=udts parameter must be specified before the udtserr parameter can be specified.
The act=fwd/sfthrot/scpval parameter must be specified before the defactid parameter can be specified.
The Service Numbering Plan (snp), Service Nature of Address Indicator (snai), Service Name (srvcname) and Service Error Cause (srvcerr) parameters can only be specified when act is set to srvc.
The srvc/sflog/sfthrot/scpval GTT Action cannot be changed to any other GTT Action (Duplicate/forward/TCAP Error/Discard/UDTS Error) and vice versa.
The parameters threshold and bursts can only be specified when action is set to sfthrot.
The sfthrot GTT Action cannot be changed to any other GTT Action (Duplicate/Forward/TCAP Error/Discard/UDTS Error/SRVC/SCPVAL) and vice versa.
The scpval GTT Action cannot be changed to any other GTT Action (Duplicate/Forward/TCAP Error/Discard/UDTS Error/SRVC/SFTHROT) and vice versa.
The sflog GTT Action cannot be changed to any other GTT Action (Duplicate/Forward/TCAP Error/Discard/UDTS Error/SRVC/SFTHROT/SCPVAL) and vice versa.
The SCCP Parameter (sprm), TCAP Parameter (tprm) can only be specified when act is set to scpval and valtype is set to sccptotcap.
The Number of digits to match (ndgt) parameters can only be specified when act is set to scpval.
A value of disc, udts, tcaperr or scpval must be specified for the act parameter before a value of uimreqd can be specified for the on or off parameter.
The GTT Action table is corrupt or cannot be found.
The GTT Action entry specified by the actid parameter must already exist in the database.
The value specified for the nactid parameter cannot already exist in the database.
A value of none or fallback cannot be specified for the actid or nactid parameter.
If a value of dup or fwd is specified for the act parameter then the pc/pca/pci/pcn/pcn24/pcn16 parameter must be specified.
If the cgpcogmsg=provcgpc parameter is specified, then the cgpc/cgpca/cgpci/cgpcn/cgpcn24/pcn16 parameter must be specified.
The GTT Action - DISCARD feature must be enabled before a value of disc, udts, or tcaperr can be specified for the act parameter.
The GTT Action - DUPLICATE feature must be enabled before the act=dup parameter can be specified.
The specified PC/SSN must already exist in the specified MAP set.
If the ri=ssn parameter is specified, then the mrnset parameter cannot be specified.
The Flexible GTT Load Sharing feature must be enabled before the mrnset parameter can be specified.
If the ri=gt parameter is specified, then the mapset parameter cannot be specified.
The Flexible GTT Load Sharing feature must be enabled before the mapset parameter can be specified.
The specified MAP set must already exist in the database.
The specified MRN set must already exist in the MRN table.
If the Flexible GTT Load Sharing feature is enabled, then the specified PC must already exist in the specified MRN set.
The point code specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter must be a full point code.
The value specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter must already exist as a destination in the Route table.
If the value specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter is the STP true point code, then the value specified for the ssn parameter must already exist in the SS-APPL table.
The value specified for the pc parameter cannot be associated with a proxy point code.
The MAP table is corrupt or cannot be found.
If the pc/pca/pci/pcn/pcn24/pcn16, ri=ssn and ssn parameters are specified, then the PC/SSN must be populated in the Remote Point Code and MAP tables.
The point code specified for the pc/pca/pci/pcn/pcn24/pcn16 and cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameters must be within the range specified by the parameter definition.
A value of disc, utds, or tcaperr must be specified for the defactid parameter.
The Route table is corrupt or cannot be found.
The STP Self-identity table is corrupt or cannot be found.
The SS-APPL table is corrupt or cannot be found.
The MRN table is corrupt or cannot be found.
The ri=ssn and the ssn=none parameters cannot be specified together in the command.
The SCCP Loop Detection feature must be enabled before the loopset parameter can be specified.
The value specified for the loopset parameter must already exist in the database.
The Loopset table is corrupt or cannot be found.
Failure while reading the GTT Action Set Table.
The GTT Action - FORWARD feature must be enabled before the act=fwd parameter can be specified.
The GTMOD table is corrupt or cannot be found.
The point code specified by the pc/pca/pci/pcn/pcn24/pcn16 parameter must be associated with a valid route.
If the value specified for the pc/pca/pci/pcn/pcn24/pcn16 parameter is the STP true point code, then the ri=ssn parameter must be specified.
The values specified for the cdgtmodid and cggtmodid parameters must already exist in the GTMOD table.
The AMGTT or AMGTT CgPA Upgrade feature must be turned on before the cggtmodid parameter can be specified.
The GTT Action ID specified by the defactid parameter must already exist.
The pc/pca/pci/pcn/pcn24/pcn16 and cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameters must have the same domain.
One of the optional parameters must be specified.
The value specified by the act parameter cannot be changed until the associated Action ID is referenced by an Action Set or by any forward/scpval/sfthrot/sflog action. The value can only be changed from disc/udts/tcaperr to disc/udts/tcaperr.
The defactid=none parameter cannot be specified.
The same value(s) cannot be specified for the on and off parameters.
The GFLEX feature must be activated if the GFLEX service is entered with the SRVCNAME parameter.
The GPORT feature must be activated if the GPORT service is entered with the SRVCNAME parameter.
The Portability Check for Mobile Originated SMS feature/PPSMS feature must be turned ON, or the MO SMS ASD/MO SMS B-Party Routing/MO SMS GRN/MO SMS IS41-to-GSM Migration/MO-based GSM SMS NP/MO-based IS41 SMS NP feature must be ENABLED before the SMSMR Service is entered with SRVCNAME parameter.
If the value specified for the SRVCNAME parameter is GFLEX, then the snai=sub, natl or intl parameter must be specified.
If the value specified for the SRVCNAME parameter is GPORT/SMSMR, then the snai= rnidn, rnndn, rnsdn or ccrndn parameter must be specified.
If the value specified for the SRVCNAME parameter is GPORT/SMSMR, then the snp=e164 parameter must be specified.
If the value specified for the SRVCNAME parameter is GFLEX, then the snp=e164, e212 or e214 parameter must be specified.
The GTT destination must exist in the DSTN table.
A value of fwd, dup or scpval must be specified for the act parameter before a value of useicmsg can be specified for the on or off parameter.
The value specified for the atirescgmodid and psirescgmodid parameters must already exist in the GTMOD table.
AMGTT feature must be enabled, if atirescgmodid or psirescgmodid is specified.
Notes
on/off options
- uimreqd —UIM required. Specifies whether a UIM should be generated.
- useicmsg —Use Incoming Message. Specifies whether to apply GTT Action data to the message as the message was received (OFF) or after any EPAP or GTT translation/modification data has been applied (ON).
- handlresp — Handle response message. Specifies whether to apply GTT Action data to the message as the message is a response message to an Eagle-generated ATI or PSI.
GTT Actions srvc, scpval, sflog and sfthrot cannot be changed to any other GTT Action (Duplicate/Forward/TCAP Error/Discard/UDTS Error/srvc/scpval/sflog/sfthrot) and vice versa. A srvc GTT Action representing one service can be changed to another service.
GTI, TT and NPDS must be provisioned in GTMOD table to associate gtmodid with ATIRESCGMODID or PSIRESCGMODID.
Output
chg-gttact:actid=dup1:ssn=40
tekelecstp 10-02-04 18:29:41 EST EAGLE 42.0.0
chg-gttact:actid=dup1:ssn=40
Command entered at terminal #4
GTT Action table is (2 of 2000) 1% full
CHG-GTTACT: MASP A - COMPLTD
;
chg-gttact:actid=gflex1:act=GPORT
tekelecstp 13-12-07 13:41:11 EST EAGLE 46.0.0
chg-gttact:actid=gflex1:act=GPORT
Command entered at terminal #1
GTT Action table is (5 of 2000) 1% full
CHG-GTTACT: MASP A - COMPLTD
;
chg-gttact:actid=sfthrot1:threshold=2000:bursts=1
tekelecstp 15-05-27 15:43:59 EST Eagle 46.3.0
chg-gttact:actid=sfthrot1:threshold=2000:bursts=1
Command entered at terminal #1
GTT Action table is (5 of 2000) 1% full
CHG-GTTACT: MASP A - COMPLTD
;
chg-gttact:actid=scpval1:act=scpval:sprm=cgpa:ndgt=20
tekelecstp 15-05-28 10:27:42 EST EAGLE 46.3.0
chg-gttact:actid=scpval1:act=scpval:sprm=cgpa:ndgt=20
Command entered at terminal #1
GTT Action table is (20 of 2000) 1% full
CHG-GTTACT: MASP A - COMPLTD
;
chg-gttact:actid=sfapp3:act=sfapp:atirescgmodid=set5
tekelecstp 18-05-07 10:13:26 EST EAGLE 46.7.0.0.0-74.5.0
chg-gttact:actid=sfapp3:act=sfapp:atirescgmodid=set5
Command entered at terminal #4.
GTT-ACT table is (3 of 2000) 1% full.
CHG-GTTACT: MASP A - COMPLTD
;
Related Topics
chg-gttapath
Use this command to change a GTT Action path entry. A GTT Action path consists of pairs of "setname + value" for Opcode/CgGTA/CdGTA. Each "setname + value" pair must already be defined in the GTT translation table.
Parameters
Example
chg-gttapath:gttpn=path1:opgttsn=opsn2:acn=1-1-1-1-1-1-1:opcode=123:pkgtype=ituuni
chg-gttapath:gttpn=path1:cggttsn=cgsn2:cggta=45673
chg-gttapath:gttpn=path1:ngttpn=path2
Dependencies
If the family parameter is specified, then a value of ansiuni, qwp, qwop, resp, cwp, cwop, ansiabort, or any must be specified for the pkgtype parameter.
If the acn parameter is specified, then a value of bgn, ituabort, ituuni, any, end, or cnt must be specified for the pkgtype parameter.
If the pkgtype=ituabort parameter is specified, then a value of none must be specified for the acn and opcode parameters.
If the pkgtype=ansiabort parameter is specified then a value of none must be specified for the family and opcode parameters.
The opcode, pkgtype, and family parameters must be specified together for ANSI TCAP translations. The opcode, pkgtype, and acn parameters must be specified together for ITU TCAP translations.
If the family and opcode parameters are specified, then either both parameters must have a value of none or neither parameter can have a value of none.
The GTA table is corrupt or cannot be found.
The GTT DBMM table is corrupt or cannot be found.
A value of none cannot be specified for the opgttsn, cggttsn, and cdgttsn parameter(s).
The GTT Action Path table is corrupt or cannot be found.
The specified path cannot already exist in the GTT Action Path table.
The acn and family parameters cannot be specified together in the command.
The GTT Action - DISCARD, GTT Action - FORWARD, or GTT Action - DUPLICATE feature must be enabled before this command can be entered.
A translation entry corresponding to the specified (opgttsn + opcode + pkgtype + acn/family)/(cgttsn + cggta)/(cdgttsn + cdgta) parameters must exist.
At least one GTT set-value combination must be specified.
The GTT set name specified by the opgttsn, cggttsn, or cdgttsn parameter must match an existing GTT set name.
The GTT set name specified by the opgttsn, cggttsn, and cdgttsn parameters must have set types of opcode, cggta, and cdgta, respectively.
The GTT Set table must be accessible.
The GTA value specified by the cggta or cdgta parameter must be the start GTA in the translation entry.
The GTT path name specified by the gttpn parameter must already exist in the database.
A GTT set-value combination(s) cannot be associated with a GTT path that is already associated to another combination. The value specified for the path name must be different from the existing path name.
The GTT path name specified by the ngttpn parameter cannot already exist in the database.
The value specified for the gttpn and ngttpn parameters cannot be a reserved word.
At least one optional parameter must be specified.
Output
chg-gttapath:gttpn=path2:cggttsn=cgsn2:cggta=45673
tekelecstp 10-02-04 18:29:41 EST EAGLE 42.0.0
chg-gttapath:gttpn=path2:cggttsn=cgsn2:cggta=45673
Command entered at terminal #4.
GTT Action Path table is (1 of 10000) 1% full
CHG-GTTAPATH: MASP A - COMPLTD
;
Related Topics
chg-gttaset
Use this command to change Global Title Translation (GTT) Action Set data. A GTT Action Set consists of an Action Set name and a set of Action IDs. The specified Action IDs determine the actions that are applied to the MSU during translation. Action IDs are configured using the ent/chg/dlt-gttact commands.
Parameters
Note:
Definitions for the feature options specified by the on and off parameters are located in the Notes section.Example
Changing the GTT Action Set name:chg-gttaset:actsn=asetdisc1:nactsn=asetdisc2
Removing Action ID1 and ID3 from an Action Set and changing ID2 to another ID in the GTT Action Set table:chg-gttaset:actsn=asetdup1:actid1=none:actid2=disc1:actid3=none:off=testmode
chg-gttaset:actsn=asetfwd1:actid1=actfwd1:actid2=actdup1:on=testmode
chg-gttaset:actsn=asetsrvc1:actid1=actdup2:actid2=actsrvc2
Dependencies
The GTT Action table is corrupt or cannot be found.
The GTT Action Set table is corrupt or cannot be found.
The Action ID specified by the actid(X) parameter(s) must already exist in the GTT Action table.
The value specified for the nactsn parameter cannot already exist in the database.
The GTT Action Set name specified by the actsn parameter must already exist in the GTT Action Set table.
A value of none cannot be specified for the (n)actsn parameter.
At least one Action ID in the Action Set must be associated with an action other than none or fallback.
Only one Action ID in an Action Set can be associated with an action of type disc, udts, tcaperr or srvc.
If an Action ID with an action of fwd is specified, then no other Action ID in the Action Set can be associated with an act of disc, udts, tcaperr, srvc, or fwd.
If an Action ID with an action of srvc is specified, then no other Action ID in the same Action Set can be associated with an act of fwd, disc, udts, tcaperr, or srvc.
If the Action Set contains five Action IDs with an action of dup then the remaining Action ID cannot have an action of dup.
Action IDs associated with an action of disc, udts, tcaperr, srvc, or fwd must be the last actions in an Action Set.
Action IDs associated with an action of sfthrot must be the first action in an Action Set.
If the Action Set contains two Action IDs associated with an action of scpval, then the remaining action ID cannot be associated with an action of scpval.
One of the optional parameters must be specified.
The actid1/actid2/actid3/actid4/actid5/actid6 parameters must each specify a unique Action ID in the command.
The EGTT feature must be turned on before this command can be entered.
The same option(s) cannot be specified for the on and off parameters.
A maximum of two SCPVAL GTT actions are allowed in an action set. Both action sets should have a different combination of SPRM and TPRM.
Notes
on/off options
- testmode—invokes a field-safe Test Tool used to debug the GTT Action Set rules
Output
chg-gttaset:actsn=asetdup1:actid1=dup2:on=testmode
tekelecstp 10-02-04 18:29:41 EST EAGLE 42.0.0
chg-gttaset:actsn=asetdup1:actid1=dup2:on=testmode
Command entered at terminal #4.
GTT Action Set table is (2 of 20000) 1% full
CHG-GTTASET: MASP A - COMPLTD
;
Related Topics
chg-gttsel
Note:
If the EGTT feature is turned on, then the GTT Selector (ent/chg/dlt/rtrvgttsel), GTT Set
(ent/dlt/rtrv-gttset), and GTA
(ent/chg/dlt/rtrvgta) commands replace the Translation Type
(ent/dlt/rtrv-tt) and Global Title Translation
(ent/chg/dlt/rtrv-gtt) commands. It is not recommended to
run
ent/dlt/rtrv-tt & ent/chg/dlt/rtrv-gtt commands
as it may cause the advance GTA fields of GTT entry to be reset to the default
values.
Parameters
Note:
The nature of address indicator parameters (naiv or nai) and the numbering plan parameters (npv or np) can be specified using either a mnemonic or an explicit value. Both values cannot be specified at the same time for the same parameter. NAIV/NAI Mapping shows the mapping between the naiv and nai values. NPV/NP Mapping shows the mapping between the npv and np values.- gti/gtia/gtii/gtin/gtin24/gtiis/gtins /gtin16 (mandatory)
- Global title indicator.
For all EGTT selector commands, the domain is defined as GTI and GTIA (ANSI), GTII (ITU international), GTIN (ITU national), GTIN24 (24-bit ITU national), GTIIS (ITU international spare), GTINS (ITU national spare) and GTIN16 (16-bit ITU National).
For the selector commands, GTI and GTIA are equivalent. GTT selectors can be provisioned for the same translation type (TT) with different ITU domains. GTT selectors are provisioned independently for each domain.
- eaglegen (optional)
- This parameter specifies whether the selector is used by system-generated messages.
- gttsn (optional)
- GTT set name. A GTT set is an entity to which global title addresses and selectors are assigned.
Example
chg-gttsel:gtii=2:tt=40:cdgtasn=setcggta:cgpcsn=none:cgssn=10:selid=12
chg-gttsel:gtia=2:tt=253:gttsn=newansi
chg-gttsel:gtin=4:tt=0:np=dflt:nai=dflt:gttsn=setint000
This example changes the selectors linked with GTTSN ANSI1 so that the selectors are linked with ANSI2 (if ANSI2 is an existing GTT set in the database):
chg-gttsel:gtii=4:tt=5:npv=1:naiv=2:gttsn=ansi2
chg-gttsel:gtin=4:tt=60:npv=5:naiv=5:cgpcsn=setcgpc:selid=100:cgssn=10
chg-gttsel:gtia=2:tt=21:cggttsn=setcgpc:cdgttsn=setcdgta:cgssn=20:selid=1:lsn=ls10
chg-gttsel:gtia=2:tt=2:cdgttsn=setcdgta:lsn=ls1010
chg-gttsel:gtia=2:tt=2:cdgttsn=setcdgta:eaglegen=yes
chg-gttsel:gtins=4:cdgttsn=setitu004:tt=4:np=e164:nai=intl
chg-gttsel:gti=0:cdgttsn=setansi0
chg-gttsel:gtin16=2:tt=10:cgpcsn=abc
chg-gttsel:gtii=2:tt=17:msgtype=u:cdgttsn=cdset1
chg-gttsel:gtii=2:tt=17:msgtype=x,xs:cdgttsn=cdset3
Dependencies
The EGTT feature must be turned on before this command can be entered.
The np and npv parameters cannot be specified together in the same command.
The nai and naiv parameters cannot be specified together in the same command.
The gti/gtia=4, gti(x)=, and gti(x)=3 parameters cannot be specified.
If the gti/gtia/gtii/gtin/gtin24/gtiis/gtins/gtin16=2 parameter is specified, then the np/npv and nai/naiv parameter combinations cannot be specified.
If the gtii/gtin/gtin24/gtiis/gtins/gtin16=4 parameter is specified, an np(v)/nai(v) parameter combination must be specified. These parameters can be specified in any combination.
The network domain (ANSI or ITU) must match that of the GTT Set entry specified by the cdgttsn, cdgtasn, or gttsn parameter.
The GTT set specified by the cdgtasn, cdgttsn, or gttsn parameter must already exist in the GTT Set table.
A value of none cannot be specified for the gttsn, cdgtasn, cdgttsn, cggttsn, cggtasn, or cgpcsn parameter.
The OBSR feature must be enabled before the cdgtasn, cggtasn, cgpcsn, or cgssn parameter can be specified.
The GTT set specified by the cgttsn, cggtasn, or cgpcsn parameter must already exist in the GTT Set table.
The network domain of the CgPA GTT Set specified by the cggttsn, cggtasn, or cgpcsn parameter must match the domain indicated by the gti(x) parameter.
The set type specified by the cggtasn or cgpcsn parameter must match the set type of the corresponding entry in the GTT set table. For example, the cggtasn parameter should have a set type of cggta, and the cgpcsn parameter should have a set type of cgpc.
The SSNSELID table must be accessible.
A value of none cannot be specified for the cdgtasn parameter if the gttsn parameter specifies the only GTTSET associated with that selector.
If the FLOBR feature is turned on, then the cdgtasn, cggtasn, and cgpcsn parameters cannot be specified.
An entry must already exist that matches the msgtype, gti(x), tt, and np(v)/nai(v) combination of parameters.
If the OBSR feature is enabled or the FLOBR feature is turned on, then the gttsn parameter cannot be specified.
The np and nai parameters must both have a value of dflt or neither can have a value of dflt.
The FLOBR feature must be turned on before the l sn, eaglegen, cdgttsn, and cggttsn parameters can be specified.
At least one GTT set name parameter must be specified. These parameters include:
- cdgtasn, cggtasn, or cgpcsn if the OBSR feature is enabled
- cdgttsn or cggttsn if the FLOBR feature is turned on
- gttsn if the OBSR feature is not enabled and the FLOBR feature is not turned on
The GTT Set specified by the
cdgtasn or
gttsn parameter must have a set type
of
cdgta (see the
ent-gttset
command).
The GTT Set table is corrupt or cannot be found.
The GTT Selector table is corrupt or cannot be found.
The GTTDBMM table is corrupt or cannot be found.
The linkset specified by the lsn parameter must already exist in the Linkset table.
A database error occurred while trying to access the SSNSELID table.
The SSNSELID Table cannot contain more than 100,000 entries.
The GTTDBMM Table cannot contain more than 42,502 entries.
The Linkset table is corrupt or cannot be found.
If the lsn parameter is specified, then the cdgttsn or cggttsn parameter must be specified.
The cggtasn, cgpcsn, and cggttsn parameters cannot be specified together in the command.
The gttsn, cdgtasn, and cdgttsn parameters cannot be specified together in the command.
If the gttsn, cdgttsn, or cdgtasn parameter is specified, then the cgssn parameter cannot be specified. If the cggtasn, cgpcsn, or cggttsn parameter is specified, then the cgssn parameter must be specified.
If the eaglegen=yes parameter is specified, then the msgtype, lsn, selid, gttsn, cdgtasn, cgssn, cggttsn, cggtasn, and cgpcsn parameters cannot be specified.
If the np=dflt or nai=dflt parameter is specified, then the cggtasn, cggttsn, cgpcsn, cgssn, eaglegen, lsn, and selid parameters cannot be specified.
If the gti(x)=0 parameter is specified, then the eaglegen, tt, np/npv, and nai/naiv parameters cannot be specified.
If a value of 2 or 4 is specified for the gti(x) parameter, then the tt parameter must be specified.
The MBR - supported GTT set types (IMEI/IMSI/MSISDN/VLRNB/SMRPDA/SMRPOA) cannot be referenced by GTT selectors.
Notes
The entry that matches the specified parameter combination is assigned to the specified gttsn.
When the Origin-based SCCP Routing feature is enabled, two GTT sets, either the cdgtasn/cggtasn or the cdgtasn/cgpcsn, can be assigned to a GTT selector. The cggtasn and cgpcsn GTT sets are mutually exclusive and cannot be assigned to the same GTT selector.
When the value of the cggtasn/cgpcsn GTT set is specified as none, that combination (domain, tt, gti, np/npi, na/nai, cgssn, and selid) are deleted from the database. At any point of time, each provisioned selector must have at least one GTT set.
There is no J7 FAK dependency on the GTIA/GTIN16/GTIN24 parameters. The command can be entered successfully whether the J7 FAK is enabled or not enabled.
GTT Selector entries configured using GTIN24/GTIN16 parameters shall be treated as ITU-N24 entries if the J7 FAK is disabled and shall be treated as ITU-N16 entries if the J7 FAK is enabled.
chg-gttsel:gtii=2:tt=17:msgtype=u,us:cdgttsn=cdset1
- chg-gttsel:gtii=2:tt=32:msgtype=all:cdgttsn=cdset1
Output
chg-gttsel:gti=0:cdgttsn=setansi0
tekelecstp 10-04-28 13:02:49 EST Eagle 42.0.0
chg-gttsel:gti=0:cdgttsn=setansi0
Command entered at terminal #4.
CHG-GTTSEL: MASP A - COMPLTD
;
chg-gttsel:gttsn=cd1:msgtype=u:gtii=0
tekelecstp 17-07-14 15:22:49 EST Eagle 46.6
chg-gttsel:gttsn=cd1:msgtype=u:gtii=0
Command entered at terminal #4.
CHG-GTTSEL: MASP A - COMPLTD
;
chg-gttsel:gttsn=u,us,xs:msgtype=u:gtii=0
tekelecstp 17-07-14 15:22:49 EST Eagle 46.6
chg-gttsel:gttsn=cd1:msgtype= u,us,xs:gtii=0
Command entered at terminal #4.
CHG-GTTSEL: MASP A - COMPLTD
;
Related Topics
chg-gttset
Use this command to specify the attributes to change for an existing set of global title translations.
Parameters
- gttsn (mandatory)
- GTT set name. A GTT set is an entity to which global title addresses and selectors are assigned.
- checkmulcomp (optional)
- This option indicates whether or not to find translation for multiple components (up to 3 components, if present) of a TCAP message.
- gttsetmeasrqd (optional)
- GTTSET Measurement required. This parameter specifies whether to perform per GTTSET measurements.
- ndgt (optional)
- Number of digits. The number of digits required for GTAs associated with this GTT set.
- netdom (optional)
- Network domain. This command does not distinguish
between ITU national or ITU international because the Enhanced Global Title
Translation (EGTT) feature does not discriminate between the ITU-I and ITU-N
translations.
Note:
The netdom parameter refers to the incoming message network domain.
Example
chg-gttset:gttsn=lidb:netdom=cross
chg-gttset:gttsn=setxyz:netdom=cross:ndgt=10
chg-gttset:gttsn=acdgta:ngttsn=acdgta1
chg-gttset:gttsn=imsi1:npsn=imsi
chg-gttset:gttsn=setopcode:checkmulcomp=on
chg-gttset:gttsn=setabc:gttsetmeasrqd=pertrans
chg-gttset:gttsn=opcode1:sxudt=no
Dependencies
The (n)gttsn=none parameter cannot be specified.
The specified netdom parameter value must be cross. This command cannot be used to change the netdom setting from cross to ansi or itu.
If the settype parameter has a value of cdssn, cgpc, cgssn, opc, opcode, or dpc, then the ndgt parameter cannot be specified.
The EGTT feature must be turned on prior to using this command.
The value specified for the gttsn parameter must match the name of an existing GTT Set.
If the VGTT feature is turned on, the ndgt parameter cannot be specified.
The ANSI/ITU SCCP Conversion feature must be enabled before the netdom parameter can be specified.
If GTAs are assigned to the GTT set, the ndgt parameter cannot be specified.
The netdom=cross parameter can be specified if the settype=cdgta/imei/imsi/msisdn/vlrnb/smrpoa/smrpda parameter is specified.
The GTTSET table must be accessible.
The GTT DBMM table must be accessible.
The NPSN parameter will be specified with IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA GTT set types.
The NPSN parameter can be of MBR set type only.
The value specified for the npsn parameter must match the name of an existing GTT Set of IMEI/IMSI/MSISDN/VLRNB/SMRPOA/SMRPDA types.
The GTT set type of GTT set entry referred by the NPSN parameter should be different from the GTT set type referred by the GTTSN parameter.
The GTT set specified by the gttsn parameter must not be associated with the GTT set referred by the NPSN parameter.
The GTTSET domain and the associated NPSN set domain must match, when the SCCP conversion feature is not ON.
CHECKMULCOMP parameter can be specified with OPCODE GTT set types only.
The SXUDT parameter must be specified with the OPCODE GTT set type only.
Output
chg-gttset:gttsn=acdgta:ngttsn=acdgta1
tekelecstp 10-04-28 17:58:38 EST Eagle 42.0.0
GTT-SET table is (1 of 2000) 1% full.
CHG-GTTSET: MASP A - COMPLTD
;
chg-gttset:gttsn=msisdn:npsn=smrpoa1
tekelecstp 15-05-28 17:58:38 EST Eagle 46.3.0
GTT-SET table is (1 of 2000) 1% full.
CHG-GTTSET: MASP A - COMPLTD
;
chg-gttset:gttsn=setopcode:checkmulcomp=on
tekelecstp 16-10-10 13:54:11 MST EAGLE 46.5.0.0.0-70.5.0
CHG-GTTSET: MASP A - COMPLTD
;
chg-gttset:gttsn=imei12:gttsetmeasrqd=yes
tekelecstp 17-05-11 15:30:38 EST Eagle 46.6.0
GTT-SET table is (1 of 10000) 1% full.
CHG-GTTSET: MASP A - COMPLTD
;
chg-gttset:gttsn=opcode1:sxudt=yes
tekelecstp 17-07-15 14:28:38 EST Eagle 46.6.0
GTT-SET table is (3 of 10000) 1% full.
CHG-GTTSET: MASP A - COMPLTD
;
Related Topics
chg-gtw-stp
Use this command to modify the level 3 ANSI transfer control status (TFCSTAT) when converted from ITU to ANSI.
Parameters
Example
chg-gtw-stp:tfcstat=1
Dependencies
None
Notes
None
Output
chg-gtw-stp:tfcstat=1
rlghncxa03w 04-01-11 11:34:04 EST EAGLE 31.3.0
CHG-GTW-STP: MASP A - COMPLTD
;
Related Topics
chg-gws-actset
Table 4-8 Gateway Screening Stop Action Definitions
| Gateway Screening Stop Action ID | Gateway Screening Stop Action Set Name | Stop Action 1 | Stop Action 2 | Action Performed by the system |
|---|---|---|---|---|
|
1 |
copy |
copy |
— |
Copy the MSU for the STP LAN feature. |
|
2 |
rdct |
rdct |
— |
Redirect the MSU for the DTA feature. |
|
3 |
cr |
copy |
rdct |
Copy the MSU for the STP LAN feature and redirect the MSU for the DTA feature. |
Caution:
Even though gateway screening is in the screen test mode, as defined by the gwsa=off and gwsm=on parameters in thechg-ls command, the GWS action in the stop action set will be performed at the end of the screening process.
Parameters
Note:
The TIF, TIF2, and TIF3 stop actions each represent a specific TIF service. The services are provisioned using thechg-npp-serv command.
Note:
Definitions of the values for the act1 - act10 parameters are located in the Notes section.Note:
GWS Stop Actions DUP and STRIP can be provisioned only in the GWS Action Set.Example
chg-gws-actset:actid=4:actname=cncf:act1=cncf
chg-gws-actset:actid=5:actname=dup:act1=dup
Dependencies
At least one optional parameter must be specified.
If the all=none parameter is specified, then no other optional parameters can be specified.
The actname=none parameter cannot be specified.
The force=yes parameter must be specified to change an existing stop action.
The Calling Name Conversion Feature must be turned on before the CNCF stop action can be specified.
The TLNP feature must be turned on or the ISUP NP with EPAP feature must be enabled before the TLNP stop action can be specified.
The TLNP feature must be turned on before the TLNP stop action can be specified.
A specific stop action can be specified for one and only one stop action parameter for each stop action set.
The value specified for the actname parameter cannot already exist in the database.
A value of copy can be specified for only the act1 parameter.
If the RDCT stop action is specified with other stop actions, then it must be specified with the last stop action parameter specified for the command.
The TLNP stop action cannot be specified in the same action set with the CNCF stop action.
The TINP gateway screening stop action cannot be specified in the same action set with the CNCF gateway screening stop action.
The TINP feature must have been enabled before upgrading to Release 39.2 or later before the TINP stop action can be specified.
At least one TIF feature must be enabled before the TIF, TIF2, or TIF3 stop action can be specified.
Only one of the TIF, TIF2, TIF3, TLNP, TINP, RDCT, and SCCP stop actions can be specified in the command.
If specified, the TIF, TIF2, TIF3, TLNP, TINP, RDCT, or SCCP stop action must be the last stop action in the command.
The SCCP stop action cannot be specified in the same Action Set with the CNCF stop action.
The MTP Routed GWS Stop Action feature must be enabled before the SCCP stop action can be specified.
The GWS STRIP stop action cannot be specified with other stop actions in the same Action Set.
The GWS DUP point code (GDPC) must be configured in the STPOPTS table before the GWS DUP stop action can be specified.
Notes
The GWS stop action 1 (act1) is the first stop action to be performed, and GWS stop action 10 (act10) is the last stop action to be performed on the MSU. These parameters can have the following values:
- cncf—Convert the PIP parameter with the GN parameter or the GN parameter with the PIP parameter in the ISUP IAM message for the Calling Name Conversion Facility feature
- copy—Copy the MSU for the STP LAN feature
- dup---- MSUs that pass gateway screening are duplicated towards a point code configured in STPOPTS:GDPC.
- none—No action is performed on the MSU
- rdct—Redirect the MSU for the DTA feature
- sccp—SCCP messages that pass gateway screening are forwarded to the SCCP card for service processing. This GWS stop action applies only to MTP routed UDT/UDTS and XUDT/XUDTS messages.
- strip--- De-encapsulate the MSUs encapsulated by GWS REDIRECT stop action and then send to MTP3 layer for further processing.
- tif—Apply TIF processing to MSU
- tif2—Apply TIF processing to MSU
- tif3—Apply TIF processing to MSU
- tinp—ISUP IAMs that pass gateway screening are intercepted by the Triggerless ISUP NP equipped EAGLE and converted to include the RN if the call is to a ported number. This GWS stop action applies only to the Triggerless ISUP NP feature.
- tlnp—ISUP IAMs that pass gateway screening are intercepted by the Triggerless LNP equipped EAGLE and converted to include the LRN if the call is to a ported number. This GWS stop action applies only to the Triggerless LNP feature.
Output
chg-gws-actset:actid=4:actname=cncf:act1=cncf
rlghncxa03w 04-01-10 11:43:04 EST EAGLE 31.3.0
CAUTION: GWS action set may be referenced by one or more GWS rules
CHG-GWS-ACTSET: MASP A - COMPLTD
;
chg-gws-actset:actid=5:actname=dup:act1=dup
tklcstp 13-10-10 11:43:04 EST EAGLE 46.0
CAUTION: GWS action set may be referenced by one or more GWS rules
CHG-GWS-ACTSET: MASP A - COMPLTD
;
Related Topics
chg-gws-redirect
Use this command to change the provisioning data for the redirect function. The values that are specified for this command are stored in the Redirect table, and they are used to set the variable fields of the MSUs being redirected. For example, if the ri=gt parameter is specified, the value gt is set for the routing indicator in the called party address (CDPA) of the MSU being redirected.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- dpc (optional)
- Specifies the value used to set the ANSI destination point code field in the routing label of the MSU that is being redirected. The point code has subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- dpca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- Default:
- Current value.
- dpci (optional)
- Specifies the value used to set the ITU international destination point code field in the routing label of the MSU that is being redirected. The point code has subfields zone-area-id.
- dpcn (optional)
- Specifies the value used to set the ITU national destination point code field in the routing label of the MSU that is being redirected. The point code is in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) when the
chg-stpopts:npcfmtiflexible point code option is on. A group code (gc) must be specified when the ITUDUPPC feature is on (nnnnn-gc, m1-m2-m3-m4-gc).
- dpcn24 (optional)
- Specifies the value used to set the 24-bit ITU national destination point code field in the routing label of the MSU that is being redirected. The point code has subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- dpcn16 (optional)
- Specifies the value used to set the 16-bit ITU national destination point code field in the routing label of the MSU that is being redirected. The point code has subfields unit number-sub number area-main number area (un-sna-mna).
- enabled (optional)
- This parameter specifies whether MSUs that have passed gateway screening are redirected or routed as normal.
- gta (optional)
- The value used to set the global title address (dialed digits) in the SCCP called party address of the MSU being redirected.
- ri (optional)
- The value used to set the routing indicator in the SCCP called party address of the MSU being redirected.
Example
chg-gws-redirect:dpc=111-222-111:ri=gt:ssn=10:tt=1:gta=180833:enabled=on
chg-gws-redirect:enabled=off
chg-gws-redirect:dpcn16=1-14-0:ri=gt:ssn=10:tt=10:gta=1:enabled=off
Dependencies
At least one optional parameter must be specified.
The dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter must be defined in the Destination table or defined as the STP site point code.
If the dpc/dpca/dpci/dpcn/dpcn24/dpcn16 parameter is defined as a destination, at least one route must be defined.
The redirect function data must exist in the database before it can be changed with this command.
Notes
None
Output
chg-gws-redirect:dpc=111-222-111:ri=gt:ssn=10:tt=1:gta=180833:enabled=on
rlghncxa03w 04-07-10 11:43:04 EST EAGLE 31.6.0
CHG-GWS-REDIRECT: MASP A - COMPLTD
;
Related Topics
chg-inpopts
Use this command to provision INP-specific data. This command updates the INPOPTS table.
Parameters
Note:
The options in the on and off parameters are described in the Notes section.- defrn (optional)
- Default routing number. A default routing number that is used for own-network subscribers.
- dra (optional)
- Destination routing address. This parameter specifies the routing address format supported in INP "Connect" response messages.
- Range:
-
- rndn
- RN + [CDPNPFX] + DN
- rn
- Routing Number
- ccrndn
- [CDPNPFX] + CC + RN + DN
- rnnecdn
- RN+ [CDPNPFX]+ NEC+ DN
- homerndn
- Home Routing Number
- rnasd
- RN + ASD
- asdrn
- ASD + RN
- rnasddn
- Supports RN +ASD+ [CDPNPFX] + DN in the INP "CONNECT" response messages.
- asdrndn
- Supports ASD+ RN + [CDPNPFX] + DN in the INP "CONNECT" response messages.
- ccrnasddn
- Supports [CDPNPFX] +CC + RN + ASD+DN in the INP "CONNECT" response messages.
- asdrnccdn
- Supports ASD+ RN+ [CDPNPFX]+ CC+ DN in the INP "CONNECT" response messages.
- ccasdrndn
- Supports [CDPNPFX] +CC + ASD + RN+DN in the INP "CONNECT" response messages.
- rnasdccdn
- Supports RN + ASD + [CDPNPFX] +CC + DN in the INP "CONNECT" response messages.
- rnasdnecdn
- RN + ASD + [CDPNPFX] + NEC + DN
- asdrnnecdn
- ASD + RN+ [CDPNPFX]+ NEC+ DN
- rngrn
- RN + GRN
- grnrn
- GRN + RN
- rngrndn
- RN + GRN + [CDPNPFX] + DN
- grnrndn
- GRN + RN + [CDPNPFX] + DN
- ccrngrndn
- [CDPNPFX] + CC + RN + GRN + DN
- ccgrnrndn
- [CDPNPFX] + CC + GRN + RN + DN
- grnrnccdn
- GRN + RN + [CDPNPFX] + CC + DN
- rngrnccdn
- RN + GRN + [CDPNPFX] + CC + DN
- rngrnnecdn
- RN + GRN + [CDPNPFX] + NEC + DN
- grnrnnecdn
- GRN + RN + [CDPNPFX] + NEC + DN
- grn
- GRN
- grndn
- GRN + [CDPNPFX] + DN
- ccgrndn
- [CDPNPFX] + CC + GRN + DN
- Default:
- No change to the current value
- System Default:
- rndn
- off (optional)
- This parameter turns off the specified options. Up to 8 comma-separated unique options can be specified.
- on (optional)
- This parameter turns on the specified options. Up to 8 comma-separated unique options can be specified.
- relcause (optional)
- Release cause. The reason for releasing the call when an INP Circular Route is detected.
- sporttype (optional)
- Service Portability type. This parameter specifies whether Service Portability is performed for the associated feature.
Note:
The S-Port feature must be turned on before any change to the parameter will impact the associated feature.Note:
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’entity id ) is applied.
Example
chg-inpopts:dra=rn:dranp=e164:dranai=intl
chg-inpopts:dranp=f69:dranai=sub:dra=rndn
chg-inpopts:dra=rn:dranp=e164:dranai=intl:cdpnpfx=fac:dltpfx=yes
chg-inpopts:dranp=f69:dranai=sub:dra=rndn:cdpnpfx=200
chg-inpopts:dranp=f69:dranai=sub:dra=rndn:cdpnpfx=200:ncdpnpfx=3abcdef:dltpfx=yes
chg-inpopts:dranp=f69:dranai=sub:dra=rndn:cdpnpfx=3abcdef:ncdpnpfx=none
chg-inpopts:dranp=f69:dranai=sub:dra=rndn:cdpnpfx=fed123:dltpfx=no
chg-inpopts:dra=rn:dranp=e164:dranai=intl:cdpnpfx=fac:dltpfx=no:cdpnnai=1 :snai=none
chg-inpopts:sprestype=connect
chg-inpopts:dra=rnnecdn:nec=abcd1
chg-inpopts:dra=asdrnccdn:dranp=e164:dranai=intl:cdpnpfx=fac:dltpfx=yes
chg-inpopts:relcause=30
chg-inpopts:dra=grnrndn:dranp=e164:dranai=intl
chg-inpopts:dranp=e164:dranaiv=10:dra=rn
chg-inpopts:dranai=sub:dranpv=3
chg-inpopts:dranpv=4:dranaiv=20
chg-inpopts:cdpnpfx=2a3b4c5d6e7f
chg-inpopts:cdpnnai=1:snai=sub
chg-inpopts:on=cutnpaste
chg-inpopts:dra=ccgrndn:dranp=e164:dranai=intl
Dependencies
At least one optional parameter must be specified.
The dranp and dranpv parameters cannot be specified together in the command.
The dranai and dranaiv parameters cannot be specified together in the command.
If the ncdpnpfx or dltpfx parameter is specified, the cdpnpfx parameter must be specified.
A value of none cannot be specified for the cdpnpfx parameter.
If the ncdpnpfx=none parameter is specified, then the dltpfx parameter cannot be specified.
The value specified for the cdpnpfx parameter must already exist in the INPOPTS table.
The value specified for the ncdpnpfx parameter cannot already exist in the INPOPTS table.
A maximum of 5 Called Party Number Nature of Address values is allowed.
The cdpnnai and snai parameters must be specified together in the command.
If this command is entered to delete a CdPN Nature of Address value from the INPOPTS table, then the value specified for the cdpnnai parameter must already exist in the INPOPTS table.
A valid value must be specified for the nec parameter.
A maximum of 40 Called Party Number Prefix values can be provisioned.
If the nec=none parameter is specified, then values of asdrnnecdn, rnasdnecdn, rnnecdn, rngrnnecdn, and grnrnnecdn cannot be specified for the dra parameter.
The INP CRP feature must be enabled before the relcause parameter can be specified.
The S-Port feature must be enabled before the sporttype parameter can be specified.
The INP feature must be enabled before this command can be entered.
The same option cannot be specified for the on and off parameters.
Notes
on/off options
- cutnpaste —Specifies whether the CutAndPaste parameter is included in an INP CONNECT response message. The value for the CutAndPaste parameter is the length of the incoming DN in the IDP query. If the cutnpaste option is provisioned, then this value is cut from the CdPN. The remaining digits are pasted to the end of the DRA digits sent by the STP in the CONNECT response to form the new routing digits. This option has a default of OFF.
Output
chg-inpopts:dra=rngrn:nec=0
tekelecstp 09-05-05 12:20:32 EST EAGLE 41.1.0
CHG-INPOPTS: MASP A - COMPLTD
;
Related Topics
chg-ip-card
Use this command to provision IP networking parameters for a given card.
Parameters
- loc (mandatory)
- Card location. The unique identifier of a specific
application subsystem located in the STP.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118, 1113, 1115
- bpipaddr (optional)
- Bonded Port IPv4 address. This parameter specifies an IPv4 address for the card in the specified location.
- bpsubmask (optional)
- Bonded Port IPv4 submask.
- Range:
- The value must be valid for the class of the entered IP address.
- Valid for Class A Networks
-
- 255.0.0
- 255.192.0
- 255.224.0
- 255.240.0
- 255.248.0
- 255.252.0
- 255.254.0
- 255.255.128.0
- Valid for Class A or B Networks
-
- 255.255.0.0
- 255.255.192.0
- 255.255.224.0
- 255.255.240.0
- 255.255.248.0
- 255.255.252.0
- 255.255.254.0
- 255.255.255.128
- Valid for Class A, B, or C Networks
-
- 255.255.255.0
- 255.255.255.192
- 255.255.255.224
- 255.255.255.240
- 255.255.255.248
- 255.255.255.252
- defrouter (optional)
- Default router IP address. This is a TCP/IP address expressed in standard dot notation. IP addresses consist of the system’s network number and the machine’s unique host number. An example IP address is 192.126.100.5, where 192.126.100 is the network number and 5 is the machine’s host number.
- dnsa (optional)
- IP address for Domain Name Server A. TCP/IP address expressed in standard dot notation. IP addresses consist of the system’s network number and the machine’s unique host number. An example IP address is 192.126.100.5, where 192.126.100 is the network number and 5 is the machine’s host number.
- dnsa6 (optional)
- The IPv6 address for Domain Name Server A.
dsna6 address should be enclosed in double quotes (" ").
- dnsb (optional)
- IP address for Domain Name Server B. TCP/IP address expressed in standard dot notation. IP addresses consist of the system’s network number and the machine’s unique host number. An example IP address is 192.126.100.5, where 192.126.100 is the network number and 5 is the machine’s host number.
- domain (optional)
- Domain name of the Domain server.
- dscp (optional)
- This parameter specifies the dscp value that shall be set for outbound messages for SIGTRAN cards.
- rstdomain (optional)
- Reset Domain Name. This parameter is used to reset the Domain Name to a NULL value.
- sctpcsum (optional)
-
SCTP checksum algorithm. This parameter specifies the configured SCTP checksum algorithm for a specific card.
The system-wide setting for the SCTP checksum algorithm type (see the
chg-sg-optscommand) takes precedence over the setting for an individual card. Thechg-sg-opts:sctpcsum=percardcommand must be entered before thechg-ip-card:sctpsum=command can be entered.
Example
chg-ip-card:loc=1211:dnsa=150.1.1.1:domain=nc.tekelec.com:defrouter=150.1.1.105
chg-ip-card:loc=1107:sctpcsum=adler32
chg-ip-card:dscp=4
Dependencies
At least one optional parameter must be specified.
The value specified for the loc parameter must correspond to the location of a card that can run an IP application (other than the eroute application, which is not supported by this command). For a list of the cards and their associated applications, see Table A-7.
The card in the location specified by the loc parameter must be inhibited before this command can be entered.
If the domain parameter is specified, the rstdomain parameter cannot be specified.
The default router IP address cannot be an existing IP link address.
The default router IP address must be local to one of the card's Ethernet network(s).
If the card in the location specified by the loc parameter is not an E5-SM4G or E5-SM8G-B card then the bpipaddr and bpsubmask parameters cannot be specified.
The IP address specified by the bpipaddr and bpsubmask parameters must be unique.
The bpipaddr parameter must be specified before the bpsubmask parameter can be specified.
A valid value must be specified for the bpsubmask parameter.
If the bpipaddr parameter is specified, then the bpsubmask parameter must be specified.
The
chg-sg-opts:sctpsum=percard command
must be entered before the
sctpsum parameter can be specified
in the
chg-ip-card command.
A valid value must be specified for the domain parameter. If the value contains a hyphen, then the host name must be enclosed within quotation marks.
Notes
The Domain Name has a 120 character limitation.
Table 4-9 Standard DSCP Values
| DSCP Class | DSCP (bin) | DSCP (hex) | DSCP (dec) |
|---|---|---|---|
| NONE | 000000 | 0×00 | 0 |
| CS1 | 001000 | 0×08 | 8 |
| AF11 | 001010 | 0×0A | 10 |
| AF12 | 001100 | 0×0C | 12 |
| AF13 | 001110 | 0×0E | 14 |
| CS2 | 010000 | 0×10 | 16 |
| AF21 | 010010 | 0×12 | 18 |
| AF22 | 010100 | 0×14 | 20 |
| AF23 | 010110 | 0×16 | 22 |
| CS3 | 011000 | 0×18 | 24 |
| AF31 | 011010 | 0×1A | 26 |
| AF32 | 011100 | 0×1C | 28 |
| AF33 | 011110 | 0×1E | 30 |
| CS4 | 100000 | 0×20 | 32 |
| AF41 | 100010 | 0×22 | 34 |
| AF42 | 100100 | 0×34 | 36 |
| AF43 | 100110 | 0×26 | 38 |
| CS5 | 101000 | 0×28 | 40 |
| EF | 101110 | 0×2E | 46 |
| CS6 | 110000 | 0×30 | 48 |
| CS7 | 111000 | 0×38 | 56 |
Output
chg-ip-card:loc=1211:dnsa=150.1.1.1:domain=nc.tekelec.com:defrouter=150.1.1.105:
sctpcsum=adler32
rlghncxa03w 08-02-22 15:35:05 EST EAGLE 38.0.0
CHG-IP-CARD: MASP A - COMPLTD
;
chg-ip-card:dscp=10
rlghncxa03w 13-09-24 16:56:31 EST EAGLE 46.0.0
CHG-IP-CARD: MASP A - COMPLTD
;
Related Topics
chg-ip-conn
Use this command to enable or disable a particular SIP/ENUM/SCCP/SFAPP/IPS with SFLOG connection to receive SIP/ENUM/SCCP/SFAPP/IPS with SFLOG traffic respectively. The IPCONN table supports the provisioning information related to the SIP/ENUM/SCCP/SFAPP/IPS with SFLOG connections.
Parameters
Example
chg-ip-conn:cname=conn1101a:open=yes
chg-ip-conn:cname=conn1101a:open=no
Dependencies
SIPNP Feature must be enabled before enabling or disabling any SIP connection.
At least one ENUM card must be provisioned before entering any ENUM connection information.
At least one IPS card with SFLOG=yes must be provisioned before entering any TCP connection information on IPS
At least one SCCP/SFAPP card must be provisioned before entering any Visualization connection information
IPCONN table should be accessible.
The value specified for the CNAME parameter must already exist in the IPCONN table.
Notes
None
Output
chg-ip-conn:cname=conn1101a:open=yes
tekelecstp 12-06-25 15:44:10 EST EAGLE 45.0.0
chg-ip-conn:cname=conn1101a:open=yes
Command entered at terminal #4.
CHG-IP-CONN: MASP A - COMPLTD
;chg-ip-lnk
Use this command to provision the IP link table.
Parameters
- loc (mandatory)
- Card location. The unique identifier of a specific
application subsystem located in the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118, 1113, 1115
- auto (optional)
- Tells hardware whether to automatically determine
duplex and speed.
Note:
Always specify "auto=yes" for ports that connected to an ELAP. The corresponding ports on ExAP LAN switches should be configured accordingly to achieve the operational speed and duplex of 1Gbps and Full Duplex.
- ipaddr (optional)
- The IP address for the specified port. This is a TCP/IP address expressed in standard dot notation. IP addresses consist of the system’s network number and the machine’s unique host number. An example IP address is 192.126.100.5, where 192.126.100 is the network number and 5 is the machine’s host number.
- mcast (optional)
- Multicast Control. This parameter enables or disables multicast support for the interface. This parameter is necessary for INP, G-Port, and G-Flex to establish the connection from the Service Module card to the MPS system.
- submask (optional)
- The subnet mask of the IP interface in the form of
an IP address with a restricted range of values.
This parameter is mandatory when the ipaddr parameter is specified.
- Range:
- The value must be valid for the class of the entered IP address.
- Valid for Class A Networks
-
- 255.0.0
- 255.192.0
- 255.224.0
- 255.240.0
- 255.248.0
- 255.252.0
- 255.254.0
- 255.255.128.0
- Valid for Class A or B Networks
-
- 255.255.0.0
- 255.255.192.0
- 255.255.224.0
- 255.255.240.0
- 255.255.248.0
- 255.255.252.0
- 255.255.254.0
- 255.255.255.128
- Valid for Class A, B, or C Networks
-
- 255.255.255.0
- 255.255.255.192
- 255.255.255.224
- 255.255.255.240
- 255.255.255.248
- 255.255.255.252
- Default:
- If the
ipaddr parameter is not
specified, there is no change to the parameter value. If a host's IP address is
known, the default subnet mask should be chosen according to
Default
Subnet Mask Values.
Table 4-10 Default Subnet Mask Values
Network Class IP Network Address Range Default Subnet Mask A
1.0.0.0 to 127.0.0.0
255.0.0.0
B
128.0.0.0 to 191.255.0.0
255.255.0.0
C
192.0.0.0 to 223.255.255.0
255.255.255.0
- System Default:
- 0.0.0.0
Example
chg-ip-lnk:loc=1102:port=a:auto=yes
Dependencies
The value specified for the ipaddr parameter must already exist in the Host table.
The IP addresses for interface A, B, C, and D must be unique (a card cannot have two interfaces on the same network).
At least one optional parameter must be specified.
If auto=yes is specified, then the duplex and speed parameters cannot be specified.
The value specified for the loc parameter must correspond to the location of a card that can run an IP application (other than the EROUTE application, which is not supported by this command). For a list of the cards and their associated applications, see Table A-7.
The card in the location (other than OAM locations) specified by the loc parameter must be inhibited before this command can be entered.
If the location specified by the loc parameter is an OAM card location, then the command can be entered while the card is in IN-SR status (as DB modifications are not allowed while the OAM is inhibited). However, the card needs to be re-initialized after the command in order for the changes to take effect.
Sockets cannot be assigned to the B interface for all cards except for those configured as IPSG.
The local
ipaddr and
submask values of either the A or B
network cannot be changed to an address that represents a different network if
a default router and/or other gateway routers are is assigned to the current
local network (display with
rtrv-ip-card and
rtrv-ip-rte).
The local IP address cannot be changed if the current
or new local host has open sockets or associations (the
open parameter set to
yes with the
ent/chg-assoc command).
The IP address of an existing IP link entry in the IP Link table cannot be changed if it exists in the IP Host table.
An IP link entry must be provisioned in the IP Link table before an IP host entry can be provisioned with a corresponding IP address in the IP Host table.
The IP host entry must be deleted from the IP Host table before an IP link entry can be deleted from the IP Link table.
An existing IP link entry in the IP Link table cannot be deleted (ipaddr=0.0.0.0) if it exists in the IP Host table.
The IP network address specified by the
ipaddr and
submask parameters must be different
from the PVN and fast copy network addresses specified by the
pvn/pvnmask, fcna/fcnamask, and
fcnb/fcnbmask parameters (see the
chg-netopts command).
The card in the location specified by the loc parameter must support the port specified by the port parameter.
The ipaddr and submask parameters must be specified together in the command.
The local IP address cannot be changed if the local
host associated with a diameter connection has open connections (the open
parameter set to
yes with the
chg-assoc command and that association
is associated with a diameter connection in the DCONN table).
An IP address cannot be configured for the card if the card is provisioned as a GTT card.
Each IP address in the IP link table must be unique.
Speed = 1000 (1 Gbps link) can be specified only for ExAP port on the card.
Each IP address entered into the IP Link table must be unique.
If the submask parameter is specified, the value given must be a valid subnet mask.
Notes
Interface A/D is used for ExAP connectivity and interface B/C is used for the signaling network on the SLIC card running the DEIR/EIR/SIP application.
When the
chg-ip-lnk command is executed for an
OAM card location, the following message is displayed:
CAUTION: MCAP IP INFO HAS BEEN CHANGED, MANUAL RE-INITIALIZATION IS NEEDEDOutput
chg-ip-lnk:loc=1102:port=a:auto=yes
chg-ip-lnk:loc=1102:port=a:auto=yes
Command entered at terminal #3.
;
tekelecstp 14-06-05 11:17:48 MST EAGLE5 46.0.0-65.20.0
CHG-IP-LINK: MASP B - COMPLTD
;
chg-ip-lnk:loc=1103:port=c:ipaddr=10.248.13.59:submask=255.255.255.0:auto=yes
chg-ip-lnk:loc=1103:port=c:ipaddr=10.248.13.59:submask=255.255.255.0:auto=yes
Command entered at terminal #18.
;
tekelecstp 16-05-25 11:51:03 MST EAGLE 46.4.0.0.0-69.1.0
CHG-IP-LINK: MASP B - COMPLTD
;
Related Topics
chg-is41-msg
Use this command to provision IS41 test messages. These messages are used by the MO SMS NPP Test Tool to test MO-based IS41 SMS message processing by the NPP.
Parameters
- active (optional)
- This parameter specifies whether the IS41 MOSMS message can be sent to the network card for processing.
- cdpagti (optional)
- Called party address global title indicator. The SCCP CdPA GT for the IS41 test message.
- cdpagtnai (optional)
- Called party address global title nature of address indicator. The SCCP CdPA GT NAI for the IS41 test message.
- cdpndgts (optional)
- Called party number digits. The TCAP CdPN (SMS_DA / SMS_ODA) digits for the IS41 test message.
- cdpnes (optional)
- Called party number encoding scheme. The TCAP CdPN (SMS_DA / SMS_ODA) encoding scheme for the IS41 test message
- cdpnnai (optional)
- Called party number nature of address indicator. The TCAP CdPN (SMS_DA / SMS_ODA) NAI for the IS41 test message.
- cdpnnp (optional)
- Called party numbering plan. The TCAP CdPN (SMS_DA / SMS_ODA) NP for the IS41 test message.
- cgpagti (optional)
-
Calling party address global title indicator. The SCCP CgPA GT for the IS41 test message.
- cgpagtnai (optional)
- Calling party address global title nature of address indicator. The SCCP CgPA GT NAI for the IS41 test message.
- cgpndgts (optional)
- Calling party number digits. The TCAP CgPN (SMS_OOA) digits for the IS41 test message.
- cgpnes (optional)
- Calling party number encoding scheme. The TCAP CgPN (SMS_OOA) encoding scheme for the IS41 test message
- cgpnnai (optional)
- Calling party number nature of address indicator. The TCAP CgPN (SMS_OOA) NAI for the IS41 test message.
Example
chg-is41-msg:msgn=1:cdpnnai=1:cdpadgts=12457896abcd:cgpnnai=1
chg-is41-msg:msgn=1:cdpnnai=1:cdpndgts=981123456
Dependencies
The TSTMSG table is corrupt or cannot be found.
If the reset parameter is specified, then no other parameters can be specified.
At least one optional parameter must be specified.
Output
chg-is41-msg:msgn=1:cdpnnai=1:cdpndgts=987654321:cgpnnai=1
tekelecstp 09-03-02 10:46:51 EST EAGLE 40.1.0
CHG-IS41-MSG: MASP A - COMPLTD
;
Related Topics
chg-is41opts
Use this command to change the values of one or more of the IS41 option indicators maintained in the IS41 Options (IS41OPTS) table.
Parameters
Note:
The options for the on and off parameters are described in the Notes section.- dfltrn (optional)
- Default routing number. The routing digits if Service Portability is not applicable.
- esnmfg (optional)
- ESN manufacturer code. The value that will be encoded in the manufacturer code section of the esn parameter for a LOCREQ response message.
- esnsn (optional)
- ESN serial number. The value that will be encoded in the serial number section of the esn parameter for a LOCREQ response message.
- iec (optional)
- International escape code. The international escape code that a received LOCREQ message can contain and have lookup performed.
- locreqdn (optional)
- This parameter specifies whether to obtain the Called Party, used for database lookup, from the SCCP or TCAP layer of a received LOCREQ message.
- locreqrmhrn (optional)
- LOCREQ remove HomeRN. This parameter specifies whether to remove the HomeRN from the TCAP Outgoing Called Party for a relayed LOCREQ message.
- mscmktid (optional)
- MSCID market ID. The value that will be encoded in the Market ID section of the mscid parameter for a response LOCREQ message.
- mscswitch (optional)
- MSCID market ID switch. The value that will be encoded in the Market ID Switch section of the mscid parameter for a response LOCREQ message.
- mtplocreqlen (optional)
- The number of terminating called party digits to extract from the LOCREQ message.
- mtplocreqnai (optional)
- MTP-routed LOCREQ nature of address indicator. This parameter specifies how the Called Party from the TCAP layer of a received MTP-routed LOCREQ message will be interpreted.
- Range:
-
- ccrndn
- Country code, routing number, and national directory number
- frmsg
- Incoming message value.
- intl
- International number
- natl
- National number
- rnidn
- Routing number prefix and international dialed/directory number
- rnndn
- Routing number prefix and national dialed/directory number
- rnsdn
- Routing number prefix and subscriber dialed/directory number
- sub
- Subscriber number
- locreqlen
- Number of terminating called party digits specified by the locreqlen parameter
- Default:
- frmsg
- nec (optional)
- National escape code. The national escape code that a received LOCREQ message can contain and have lookup performed.
- off (optional)
- This parameter turns off the specified options. Up to 8 comma-separated options can be specified.
- on (optional)
-
This parameter turns on the specified options. Up to 8 comma-separated options can be specified.
- rspcdpapcp (optional)
- Response called party point code present. The point code present bit that will encode the SCCP CdPA GTA of a LOCREQ response message.
- Range:
-
- off
- The response will not contain a point code present bit.
- on
- The point code in the SCCP CgPA of the received LOCREQ message will be used. If no point code is present, the originating point code in the MTP Routing Label will be used.
- frmsg
- The point code present bit from the received message will be used. Override does not occur.
- Default:
- off
- rspcdpari (optional)
- Response called party routing indicator. The value of the routing indicator bit that will encode the SCCP CdPA GTA of a LOCREQ response message.
- Range:
-
- frmsg
- The received message routing indicator bit will be used. Override does not occur.
- gt
- The GTA digits in the SCCP CgPA GTA of the received message will be used. If no GTA digits are present in the SCCP CgPA GTA, override will occur according to the cdpari=ssn parameter.
- ssn
- The SCCP CgPA of the received message will be used.
- Default:
- frmsg
- rspcgpanai (optional)
- Response calling party nature of address indicator. The nature of address (NAI) that will encode the SCCP CgPA GTA of a LOCREQ response message.
- rspcgpanp (optional)
- Response calling party numbering plan. The numbering plan (NP) that will encode the SCCP CgPA GTA of a LOCREQ response message.
- rspcgpapcp (optional)
- Response calling party point code present. This parameter specifies the point code present bit that will encode the SCCP CgPA GTA of a LOCREQ response message.
- Range:
-
- frmsg
- The point code present bit from the received message will be used.
- on
- The point code in the SCCP CdPA of the incoming LOCREQ message will be used. If no point code is present, the destination point code in the MTP Routing Label will be used.
- off
- The response message will not contain a point code present bit.
- Default:
- frmsg
- rspcgpari (optional)
- Response calling party routing indicator. The routing indicator bit that will encode the SCCP CgPA GTA of a LOCREQ response message.
- rspcgpatt (optional)
- Response calling party translation type. The translation type (TT) that will encode the SCCP CgPA GTA of a LOCREQ response message.
- rspdig (optional)
- Routing number. The digit encoding format of the TCAP Outgoing Called Pary parameter for a LOCREQ response message.
The routing number will be used as is or concatenated with the Called Party Number. The routing number format will be used on a per EAGLE node basis.
- rspdigtype (optional)
- Response digit type. The value that will encode the Digit Type field in the TCAP Outgoing Called Party parameter of a LOCREQ response message.
- rspmin (optional)
- Response LOCREQ MIN parameter encoding. This parameter specifies how the min parameter of a LOCREQ response message will be encoded.
- Range:
-
- homern
- The exact number of digits, with home RN prefix, as encoded in the Called Party of the received LOCREQ message.
- nothomern
- The exact number of digits, without home RN prefix, as encoded in the Called Party of the received LOCREQ message.
- tendelhomern
- The leading 10 digits of the Called Party of the received LOCREQ message after deleting the home RN prefix, if it exists.
- tenhomern
- The leading 10 digits the Called Party of the received LOCREQ message without deletion of the home RN prefix.
- tenzero
- 10 digits filled with 0.
- Default:
- homern
- rspnon (optional)
- MSRN nature of number. The nature of number value that will encode the TCAP Outgoing Called Party parameter of a LOCREQ response message.
- rspnp (optional)
- MSRN numbering plan. This parameter specifies the numbering plan that will encode the TCAP Outgoing Called Party parameter of the LOCREQ response message.
- rspparm (optional)
- Response parameter. The TCAP parameter that will encode the RN and/or DN information for a LOCREQ response message.
This value encodes the DigitType field of the TerminationList, RoutingDigits, or Digits[Destination] on a per EAGLE node basis.
- smsreqbypass (optional)
- This parameter specifies whether a received SMSREQ message that passes the MNP Service Selector ( serv=mnp parameter in the
chg-sccp-servcommand) will undergo A-Port message processing.
- sporttype (optional)
- Service Portability Type. The application of Service Portability that is applied to the associated feature.
The S-Port feature must be enabled before this parameter can be specified. The S-Port feature must be turned on before any change to the parameter will impact the associated feature.
Note:
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’entity id ) is applied.
- tcapsnai (optional)
- This parameter specifies how the Called Party from the TCAP layer of a received LOCREQ message will be interpreted.
- Range:
-
- ccrndn
- Country code, routing number, and national directory number
- frmsg
- Incoming message value
- intl
- International number
- natl
- National number
- rnidn
- Routing number prefix and international dialed/directory number
- rnndn
- Routing number prefix and national dialed/directory number
- rnsdn
- Routing number prefix and subscriber dialed/directory number
- sub
- Subscriber number
- Default:
- frmsg
Example
chg-is41opts:iec=12345:nec=12345:rspcgpari=gt:rspcdpari=gt
chg-is41opts:rspnon=1:tcapsnai=sub:mscmktid=78
chg-is41opts:locreqdn=tcap:rspcgpapcp=frmsg:rspnp=14:rspmin=tendelhomern
chg-is41opts:smsreqbypass=yes:rspcdpapcp=off
chg-is41opts:rspcgpanai=120:rspcgpanp=5:rspcgpatt=25
chg-is41opts:mtplocreqnai=intl:rspparm=tlist:rspdig=rn
chg-is41opts:rspnon=25:mscmktid=535:mscswitch=55
chg-is41opts:esnmfg=159:esnsn=7215:rspdigtype=67:locreqrmhrn=yes
chg-is41opts:sporttype=gsm:dfltrn=48607:on=smsreqbypass,locreqrspnd
Dependencies
The A-Port or IS41 GSM Migration (IGM) feature must be enabled before this command can be entered.
The EGLEOPTS table is corrupt or cannot be found.
The Service Portability and LOCREQ Query Response features must be enabled before the sporttype parameter can be specified.
The smsreqbypass and locreqrmhrn parameters and the on or off parameter cannot be specified in the same command.
The LOCREQ Query Response feature must be enabled before the dfltrn parameter can be specified.
The LOCREQ Query Response feature must be turned on before the locreqrspnd option can be specified for the on or off parameter.
The same option cannot be specified for the on and off parameters.
Notes
on/off options
- smsreqbypass —Specifies whether a received SMSREQ message that passes the MNP Service Selector (see the
chg-sccp-servcommand) undergoes A-Port message processing. This option has a default of OFF. - locreqrmhrn —LOCREQ remove HomeRN. Specifies whether to remove the HomeRN from the TCAP Outgoing Called Party for a relayed LOCREQ message. This option has a default of OFF.
- locreqrspnd —Specifies whether the system should always respond to a LOCREQ query. This option has a default of OFF.
Output
chg-is41opts:smsreqbypass=yes
tekelecstp 06-09-11 15:13:20 EST EAGLE 36.0.0
Command entered at terminal #4.
CHG-IS41OPTS: MASP A - COMPLTD
;
Related Topics
chg-is41smsopts
Use this command to enter IS41 SMS system options in the database. This command updates the IS41SMSOPTS table.
Parameters
- bpartygttsn (optional)
- MO SMS B-Party Routing GTT Set name. The GTT set where Global Title Translation lookup on B-Party digits is performed.
- defrn (optional)
- Default routing number. A default routing number that is used for own-network subscribers.
- modaparam (optional)
-
This parameter specifies whether the SMS_DestinationAddress or SMS_OriginalDestinationAddress parameter from the IS41 SMDPP message is used for conditioning, lookup, and modification for the MO-based IS41 SMS NP and MO SMS IS41-to-GSM Migration features.
- moigmpfx (optional)
- MO SMS IS41-to-GSM migration prefix. This parameter specifies whether the MO SMS IS41-to-GSM Migration feature uses digits from the RTDB network entity (NE) associated with the B number or the is412gsm parameter (see the
chg-gsmoptscommand) as a prefix to modify the destination address in the outgoing SMDPP.
- mosmsaclen (optional)
-
The number of the digits that are taken from the MO SMS CgPA and used as the Area Code in the MO SMS CdPA.
- mosmsdigmat (optional)
-
This parameter specifies that the “HomeSMSC Match with Digits” search option can be used with the MO-based IS41 SMS NP and MO SMS IS41-to-GSM Migration features.
- mosmsgttdig (optional)
- MO SMS B-Party Routing GTT digit. The digits that are used for Global Title Translation.
- mosmsnai (optional)
- MO-based SMS Nature Address Indicator. The number conditioning that is performed on the SMS_DestinationAddress digits in the SMDPP message before lookup in the number portability database is performed.
- Range:
-
- intl
- Number is treated as INTL (1) for number conditioning.
- nai
- The NAI from the SMS_DestinationAddress parameter in the SMDPP message is used to perform number conditioning
- nat
- Number is treated as NATL (0) for number conditioning.
- unknown
- Number is treated as UNKNOWN (2) for number conditioning.
A value of nai must be specified before the intl, natl, nai1, nai2, nai3, and unkn parameters in the
chg-npp-servcommand can be changed to non-default values for the MOSMSICDPN service. - Default:
- No change to the current value
- System Default:
- intl
- mosmstype (optional)
- MO-based SMS type. The value of the entity type that indicates that a successful lookup occurred in the number portability database.
- mtsmsackn (optional)
- MT-Based SMS acknowledgement. The message generated in response to a successful number portability database lookup for an SMSREQ message from a Home SMSC.
- mtsmschksrc (optional)
- MT-Based SMS check source. This parameter specifies whether the SCCP CgPA GTA of a SMSREQ message is validated to determine whether the source of the message is a Home SMSC.
- Range:
-
- yes
- The SCCP CgPA GTA of an SMSREQ message is validated.
- no
- The SCCP CgPA GTA of an SMSREQ message is not validated.
If the mtsmschksrc=yes parameter is specified, and if the incoming SMSREQ message has SCCP CgPA GTA, then the SCCP CgPA GTA must be found in the Home SMSC list for the source of the message to be considered a Home SMSC. If the message is not found in the Home SMSC list, then the MT-Based IS41 SMS NP feature does not process the message.
If the mtsmschksrc=no parameter is specified, or if SCCP CgPA GTA does not exist in the incoming message, then the source of the message is considered to be a Home SMSC, and the MT-Based IS41 SMS NP feature considers the message for processing.
- Default:
- No change to current value
- System Default:
- no
- mtsmsdigtype (optional)
- MT-Based SMS digit type. The value that is used to encode the "Type of digits" field in the SMS_Address parameter of an SMSREQ ACK message.
- mtsmsdltr (optional)
- MT-Based SMS delimiter. This parameter specifies whether to insert a delimiter string before or after the routing number (RN) when the RN is used in the mtsmsdnfmt digits.
Note:
The delimiter string that is inserted is determined by the mtsmsdltrv parameter.
- mtsmsdltrv (optional)
- MT-Based SMS delimiter value. The delimiter digit string inserted before or after the RN when the RN is used in the mtsmsdnfmt digits.
- mtsmsdnfmt (optional)
- MT-Based SMS DN format. The required format of digits to be encoded in the “SMS_Address” parameter of the SMSREQ response.
- mtsmsesn (optional)
- MT-Based SMS electronic serial number. This parameter specifies whether to encode the ESN parameter while generating the SMSREQ response message.
- mtsmsnakerr (optional)
- MT-Based SMS negative acknowledgement error. The TCAP access denied reason to be included in the NACK response message that is generated for SMSREQ messages.
- mtsmsparm (optional)
- MT-Based SMS parameter. The format used to encode the “SMS_Address” parameter of an SMSREQ response message.
- mtsmsssn (optional)
- MT-Based SMS subsystem number. The SSN that is encoded in "SMS_Address" field, if the mtsmsparm=pcssn parameter is specified, and the SSN entry is not found in the entity.
- mtsmstype (optional)
- MT-Based SMS type. The entity type that indicates a successful lookup occurred in the number portability database.
- spfill (optional)
- This parameter specifies whether the Numbering Plan Processor (NPP) can populate SP and RN entities for own network subscribers at the same time.
- sporttype (optional)
- Service Portability type. This parameter specifies whether Service Portability is performed for the associated feature.
Note:
If Service Portability is performed, then the Service Portability prefix (RTDB GRN entity id) is applied.
Example
This example sets the IS41 SMS options when MO SMS ASD or MO SMS GRN feature is enabled:chg-is41smsopts:modaparam=da:mosmsnai=intl:mosmsaclen=3
This example sets the IS41 SMS options when the MT-based IS41 SMS NP feature is enabled:chg-is41smsopts:mtsmsdltr=no:mtsmsparm=digit
chg-is41smsopts:mtsmsdltrv=9854:mtsmsackn=nack:mtsmsesn=no
chg-is41smsopts:mtsmsssn=2:mtsmsnakerr=55:mtsmsdigtype=25
chg-is41smsopts:mtsmschksrc=no
This example sets the IS41 SMS options when the MO SMS B-Party Routing feature is enabled:chg-is41smsopts:bpartygttsn=setint001:mosmsgttdig=mapbparty
chg-is41smsopts:mtsmsdnfmt=dn:mtsmstype=sp
This example sets the IS41 SMS options when the MO-based IS41 SMS NP feature is enabled:
chg-is41smsopts:mosmstype=sp:mosmsnai=intl:mosmsdigmat=exact: modaparam=da:mosmsaclen=3
This example sets the IS41 SMS options when the MO SMS IS41-to-GSM Migration feature is enabled.
chg-is41smsopts:mosmsdigmat=exact:moigmpfx=is412gsm:modaparam=da: mosmsnai=intl:mosmsaclen=3
This example sets the Area Code Length, when MO-based IS41 SMS NP, MO SMS IS41-to-GSM Migr, MO SMS ASD or MO SMS GRN feature is enabled:chg-is41smsopts:mosmsaclen=5
Dependencies
At least one parameter must be specified.
The mtsmsdltrv parameter must be specified before a value of prern or postrn can be specified for the mtsmsdltr parameter.
The value specified for the bpartygttsn parameter must match the name of an existing GTT Set.
The mosmsgttdig=sccpcdpa parameter must be specified before the bpartygttsn=none parameter can be specified.
The GTT set specified for the bpartygttsn parameter must have settype=cdgta (see the ent-gttset command).
If the bpartygttsn=none parameter is specified, then the mosmsgttdig=mapbparty parameter cannot be specified.
The GTT Set table is corrupt or cannot be found.
The EGLEOPTS table is corrupt or cannot be found.
The MT-Based IS41 SMS NP feature must be enabled before the mtsmsdnfmt, mtsmstype, mtsmsparm, mtsmsdltr, mtsmsdltrv, mtsmsackn, mtsmsesn, mtsmsssn, mtsmsnakerr, mtsmsdigtype, or mtsmschksrc parameters can be specified.
The MO SMS IS41-to-GSM Migration feature must be enabled before the moigmpfx parameter can be specified.
The MO SMS B-Party Routing feature must be enabled before the bpartygttsn or mosmsgttdig parameter can be specified.
The MO-based IS41 SMS NP or MO SMS IS41-to-GSM Migration feature must be enabled before the mosmsdigmat parameter can be specified.
The MO-based IS41 SMS NP feature must be enabled before the mosmstype, defrn, and spfill parameters can be specified.
The MO-based IS41 SMS NP, MO SMS IS41-to-GSM Migration, MO SMS ASD, or MO SMS GRN feature must be enabled before the modaparam, mosmsnai, or mosmsaclen parameter can be specified. The modaparam parameter can also be specified if the MO SMS B-Party Routing feature is enabled.
The S-Port feature must be enabled before the sporttype parameter can be specified.
Output
chg-is41smsopts:mtsmsackn=ack
tekelecstp 08-05-11 13:11:27 EST EAGLE 39.0.0
CHG-IS41SMSOPTS: MASP A - COMPLTD
;
Related Topics
chg-isup-msg
Use this command to enter or change specific parameters of an ISUP test message in the TESTMSG table. The TIF Test Tool processes ISUP test messages to verify the TIF and NPP provisioned configuration in the system.
Parameters
- msgn (mandatory)
- Test message number. The ISUP test message number for which parameters are being changed in the TESTMSG table.
- cdpndgts (optional)
- Called Party Number digits. The value for the CdPN digits in the specified ISUP test message.
- cdpnnai (optional)
- Called Party Number Nature of Address Indicator. The value for the CdPN NAI in the specified ISUP test message.
- cgpncat (optional)
- Calling Party Number Category. The value of the CgPN Category in the specified ISUP test message.
- cgpndgts (optional)
- Calling Party Number digits. The value for the CgPN digits in the specified ISUP test message.
- cgpnnai (optional)
- Calling Party Number Nature of Address Indicator. The value of the CgPN NAI in the specified ISUP test message.
Example
chg-isup-msg:msgn=1:active=yes:nmbits=1:cgpndgts=987654321:cdpndgts=923487:cdpnnai=125
chg-isup-msg:msgn=6:cgpncat=200:cdpnnai=23
Dependencies
At least one of the optional parameters must be specified.
At least one TIF feature must be enabled before this command can be entered.
The TSTMSG table is corrupt or cannot be found.
Output
chg-isup-msg:msgn=10:active=yes:nmbits=1
tekelecstp 08-07-24 10:37:20 EST EAGLE 39.2.0
CHG-ISUP-MSG: MASP A - COMPLTD
;
Related Topics
chg-j1
Use this command to change an interface for a J1 card in the system. J1 interface can be provisioned on E5-E1T1-B.
Parameters
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
chg-j1:loc=1101:j1port=1:encode=ami:j1tsel=external
chg-j1:loc=1102:j1port=2:encode=b8zs:ll=250
Dependencies
At least one optional parameter must be specified.
The card location specified by the loc parameter must be equipped.
The J1 table must be accessible.
The Card (IMT) table must be accessible.
The card specified by the loc parameter must be a LIMT1 card type and application must be CCS7ITU.
The port specified by the j1port parameter must have already been configured with a J1 interface on the specified J1 card with application as CCS7ITU.
All signaling links that are serviced by the specified J1 card with application as CCS7ITU must be deactivated before the values for the encode, j1tsel, and ll parameters can be changed.
Card locations 1113 - 1118 (OAM, TDM, MDAL cards) cannot be specified as values for the loc parameter.
j1port must be in range from 1 to 8.
Notes
External timing is derived from the EAGLE High-Speed Master Clock (1.544 MHz for T1 or 2.048 MHz for E1): therefore, the Master Timing feature is required. Line timing is derived from its received data stream, if present.
Output
chg-j1:loc=1101:j1port=1:encode=ami
tekelecstp 13-12-20 12:33:39 EST 46.0.0-65.3.0
chg-j1:loc=1101:j1port=1:encode=ami
Command entered at terminal #4.
CHG-J1: MASP A - COMPLTD
;
chg-l2t
Use this command to change the values of the SS7 MTP
level 2 timers. The timers are organized in 40 timer sets of which sets 1-35
have 9 timer values and sets 36-40 have 10 timer values. The timer sets are
grouped and system default values are initialized by specification (ANSI, ITU,
High Speed for China, High Speed for Q.703 Annex A, JT Q703, and High Speed for
Unchannelized T1). Each timer set is administered individually by this command.
The
ent-slk command is used to assign an
SS7 signaling link to any of the timer sets. Each assigned link is associated
with a timer set.
Parameters
- l2tset (mandatory)
- Level 2 timer set. This parameter specifies the Level 2 timer set identifier or timer set number. Up to 40 different timer sets can be defined. A signaling link can be assigned to any of the timer sets.
- nodata (optional)
- This parameter specifies a value for the NODATA
timer.
Note:
The NODATA timer measures the amount of time, in milliseconds, that must pass with no transmissions on a link before the EAGLE interprets the condition as a link failure or terminal equipment failure and initiates changeover procedures.The NODATA timer is not applicable for HSLs. It is valid for low speed links only.
The NODATA timer is configurable only for low speed SS7 links running BASIC Error Correction Method (ECM).
The NODATA timer is not configurable for low speed SS7 links running PCR ECM. The NODATA timer value is calculated as T2 (L2 timer 2 value)/3 for low speed SS7 links running PCR ECM.
- t1 (optional)
- Timer 1—Aligned/ready
- Range:
-
5000 - 350000 (milliseconds)
ANSI timer sets 1–10—5000–20000
ITU timer sets 11–20—40000–50000
China timer sets 21–25—25000–350000
Q.703 Annex A timer sets 26–30—25000–350000
Unchannelized T1 timer sets 31–35—16000–151000
Japan timer sets 36--40--- 15000
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—13000
ITU timer sets 11–20—40000
China timer sets 21–25—150000
Q.703 Annex A timer sets 26–30—300000
Unchannelized T1 timer sets 31–35—151000
Japan timer sets 36--40--- 15000
- t2 (optional)
- Timer 2—Not aligned
- Range:
-
5000 - 480000
(milliseconds)
ANSI timer sets 1–10—5000–30000
ITU timer sets 11–20—5000–150000
China timer sets 21–25—5000–150000
Q.703 Annex A timer sets 26–30—5000–150000
Unchannelized T1 timer sets 31–35—5000–14000
Japan timer sets 36--40----5000--480000
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—11500
ITU timer sets 11–20—30000
China timer sets 21–25—130000
Q.703 Annex A timer sets 26–30—130000
Unchannelized T1 timer sets 31–35—14000
Japan timer sets 36--40--5000
- t3 (optional)
- Timer 3—Aligned
- Range:
-
1000 - 20000
(milliseconds)
ANSI timer sets 1–10—5000–20000
ITU timer sets 11–20—1000–2000
Q.703 Annex A timer sets 26–30—1000–2000
China timer sets 21–25—1000–2000
Unchannelized T1 timer sets 31–35—5000–14000
Japan timer sets 36--40---3000
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—11500
ITU timer sets 11–20—2000
China timer sets 21–25—1000
Q.703 Annex A timer sets 26–30—1000
Unchannelized T1 timer sets 31–35—14000
Japan ITU low speed links 36--40---3000
- t4epp (optional)
- Timer 4—Proving period Emergency
- Range:
-
200 - 10000
(milliseconds)
ANSI timer sets 1–10—200–1000
ITU timer sets 11–20— 400–600
China timer sets 21–25—400–600
Q.703 Annex A timer sets 26–30—400–600
Unchannelized T1 timer sets 31–35—3000–10000
Japan timer sets 36--40--3000
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—600
ITU timer sets 11–20—500
China timer sets 21–25—500
Q.703 Annex A timer sets 26–30—500
Unchannelized T1 timer sets 31–35—3000
Japan timer sets 36--40--3000
- t4npp (optional)
- Timer 4— Proving period normal
- Range:
-
500 - 70000
(milliseconds)
ANSI timer sets 1–10—500–5000
ITU timer sets 11–20—7500–9500
China timer sets 21–25—3000–70000
Q.703 Annex A timer sets 26–30—3000–70000
Unchannelized T1 timer sets 31–35—3000–30000
Japan timer sets 36--40-- Not applicable
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—2300
ITU timer sets 11–20—8200
China timer sets 21–25—30000
Q.703 Annex A timer sets 26–30—30000
Unchannelized T1 timer sets 31–35—30000
- t5 (optional)
- Timer 5—Sending SIB
- Range:
- 40 - 500
(milliseconds)
ANSI timer sets 1–10—40–500
ITU timer sets 11–20—80–120
China timer sets 21–25—80–120
Q.703 Annex A timer sets 26–30—80–120
Unchannelized T1 timer sets 31–35—80–120
Japan timer sets 36--40--200
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—100
ITU timer sets 11–20—100
China timer sets 21–25—100
Q.703 Annex A timer sets 26–30—100
Unchannelized T1 timer sets 31–35—80
Japan timer sets 36--40--200
- t6 (optional)
- Timer 6—Remote congestion
- Range:
- 1000 - 10000
(milliseconds)
ANSI timer sets 1–10—1000 - 10000
ITU timer sets 11–20—3000 - 6000
China timer sets 21–24—3000 - 6000
Q.703 timer sets 26–30—3000 - 6000
Unchannelized T1 sets 31–35—3000 - 6000
Japan timer sets 36--40--5000
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—4000
ITU timer sets 11–20—4000
China timer sets 21–25—5000
Q.703 Annex A timer sets 26–30—5000
Unchannelized T1 timer sets 31–35—5000
Japan timer sets 36--40--5000
- t7 (optional)
- Timer 7—Excessive delay of acknowledgment
- Range:
- 200 - 3000
(milliseconds)
For ANSI timer sets 1–10—200–3000
ITU timer sets 11–20—500–2000
China timer sets 21–25—500–2000
Q.703 Annex A timer sets 26–30—500–2000
Unchannelized T1 timer sets 31–35—500–2000
Japan ITU low speed links 36--40---2000--3000
- Default:
- No change to the current value
- System Default:
-
ANSI timer sets 1–10—1500
For ITU timer sets 11–20—1500
For China timer sets 21–25—800
For Q.703 Annex A timer sets 26–30—800
For Unchannelized T1 timer sets 31–35—500
Japan ITU low speed links 36--40--2000
Example
chg-l2t:l2tset=1:t1=5400
chg-l2t:l2tset=21:t4epp=600:t5=90:t6=3500:t7=1900
chg-l2t:l2tset=1:nodata=200
chg-l2t:l2tset=36:t2=6000
Dependencies
At least one optional parameter must be specified.
Failed reading level 2 timer set table.
The value specified for the timer must be within the range for that domain.
The value specified for the timer must be in the allowed range.
For l2tset greater than 35, timers t1, t3, t4epp, t5, and t6 are not allowed to change.
Notes
ANSI timer defaults are within the Telcordia recommended ranges.
ITU timer defaults are within ITU Q.703 white book recommended ranges.
J1 timer defaults are within JT Q.703 white book recommended ranges.
If the value specified for the nodata parameter is greater than 200 milliseconds, then the following message appears:
Caution:
WARNING: If NODATA timer value is greater than 200ms, links could go into congestion before link failure is declaredOutput
chg-l2t:l2tset=21:t4epp=600:t5=90:t6=3500:t7=1900
rlghncxa03w 05-02-07 11:11:28 EST EAGLE5 34.0.0
CHG-L2T: MASP A - COMPLTD
;
chg-l2t:l2tset=1:nodata=200
tekelecstp 08-05-02 16:36:09 EST EAGLE 39.0.0
CHG-L2T: MASP A - COMPLTD
chg-l3t
Use this command to change the SS7 MTP level 3 timers. The SS7 MTP level 3 timers are organized in a timer set of 21 values each. Only one timer set is administered by this command. Each linkset is associated with the SS7 MTP level 3 Timer set. The linkset and timer set association is assigned with the link administration commands.
Parameters
Note:
All timer values are entered in milliseconds. Thertrv-l3t command displays output in seconds.
Note:
All it(X) parameters can be specified for ITU networks only. All t(x) parameters can be specified for ANSI or ITU networks. Tc parameter can be specified for J7 (Japan ITU-N) networks only.- l3tset (mandatory)
- Timer set table. Only one timer set table exists. All SS7 signaling links use the SS7 MTP level 3 timer set table.
- it18 (optional)
-
Timer 18—Timer within a signaling point whose MTP restarts to supervise the receipt of routing information and the activation of the link and link set.
- it19 (optional)
-
Timer 19—Supervision timer during MTP restart to avoid ping-pong of TFP, TFR1, and TRA messages.
- it21 (optional)
-
Timer 21—Overall MTP restart timer at a signaling point adjacent to one whose MTP restarts.
- t22 (optional)
-
Timer 22—Timer at restarting STP, waiting for signaling links to become available; in milliseconds.
- t23 (optional)
-
Timer 23—Timer at restarting STP, started after T22, waiting to receive all TRA messages; in milliseconds.
- t24 (optional)
-
Timer 24—Timer at restarting STP with transfer function, started after T23, waiting to broadcast all TRA messages.
- t25 (optional)
-
Timer 25—Timer at adjacent STP and restarting STP, waiting for TRA message; may be started at level 2.
- t29 (optional)
-
Timer 29—Timer started when a TRA is sent in response to an unexpected TRA or TRW; also, started when traffic resumed without receipt of TRA.
- t30 (optional)
-
Timer 30—Timer to limit sending of TFPs/TFRs in response to an unexpected TRA or TRW.
Example
chg-l3t:l3tset=1:t1=800
chg-l3t:l3tset=1:t5=800:t6=800:t32=70000
Dependencies
The minimum parameter requirement is the table number and at least one timer specified.
Do not specify T20 and IT22 pairs of timers together because one value overrides the other.
Do not specify T21 and IT23 pairs of timers together because one value overrides the other.
The Level 3 timer table must be accessible.
The STP options table must be accessible.
Notes
The command line allows 157 characters. Some SS7 MTP level 3 timer changes may exceed this limit. Multiple entries of this command may be required in such cases.
Timer 9 is not currently supported in the SS7 protocol, and has been omitted from this manual. The command will support this timer when it has been defined in the protocol.
The default values are within the Telcordia recommended ranges.
tc timer is only supported in J7 network.
Output
chg-l3t:l3tset=1:t1=800
rlghncxa03w 04-01-07 08:40:50 EST EAGLE 31.3.0
CHG-L3T: MASP A - COMPLTD
;
chg-lbp
Use this command to change a far-end loopback point’s attribute values maintained in the link fault sectionalization table.
Parameters
- lbp (mandatory)
- Loopback point ID. This parameter identifies a far-end loopback point that lies along an SS7 signaling link path between the STP and the target device (up to and including the target device).
- link (mandatory)
- SS7 signaling links. The SS7 signaling link to be tested.
- Synonym:
- port
- Range:
- a, b, a1 - a31, b1 - b31
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling links.
- loc (mandatory)
- Card location. The unique identifier of a specific application subsystem located in the STP.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
- clli (optional)
- Common Language Location Identifier (CLLI) code. This parameter specifies the CLLI or other mnemonic identifier used to refer to the given loopback point.
- lfst (optional)
- Link fault sectionalization test. The type of link fault sectionalization loopback test to be performed.
- rep (optional)
- Repetition count. The number of link elements of the same type (not including the target device) that lie between the STP and the link element to be tested.
- Range:
- 0 - 31
- Default:
- No change unless:
0—The link element to be looped back for testing is NEI (rle=nei is specified)
0—The type of link fault sectionalization test is NLT (lfst=nlt is specified)
0—The new remote link element is the first loopback point of the link to be tested
1–30—Next sequential number for subsequent loopback points of the link to be tested
Example
chg-lbp:loc=1101:link=a:lbp=1:rle=ds0:lfst=llt
Dependencies
The Link Fault Sectionalization (LFS) feature must be on before using this command.
At least one optional parameter must be specified.
The card location specified in the loc parameter cannot be reserved by the system.
The card location (loc parameter) must identify a provisioned E5-E1T1-B card, provisioned with the LIMT1 card type, configured with either the SS7ANSI or CCS7ITU application.
The CLLI cannot be a reserved word.
The rep parameter value that is specified for this loopback point (LBP) must be greater than the rep parameter value of any previously defined LBP and less than the rep parameter value of any subsequently defined LBP.
The rep parameter must be specified if the default value is a duplicate of the rep parameter value of any previously defined loopback point.
The LBP must have been previously defined.
The rep parameter can be specified only if the lfst=llt parameter is specified.
If the rle=nei parameter is specified, the rep=0 parameter must be specified.
The rle=ds0 or the rle=nei parameter cannot be specified if the lfst=nlt parameter is specified. The DS0 and Network Element Interface (NEI) link elements do not support non-latching loopbacks.
For each SS7 signaling link, you can define only one loopback point with rle=nei specified; and that loopback point must be the terminating SS7 signaling link component.
For each SS7 signaling link, the loopback point with rle=nei specified must be the terminating SS7 signaling link component.
The card location specified in the loc parameter must be equipped.
The Link Fault Sectionalization database Loopback Point (LBP) table is not accessible.
Notes
None
Output
chg-lbp:loc=1101:port=a:lbp=1:rle=ds0:lfst=llt
rlghncxa03w 05-01-17 15:35:05 EST EAGLE5 33.0.0
CHG-LBP: MASP A - COMPLTD
;
chg-lg-card
Use this command to change the group of an LG card.
The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.Parameters
- loc (mandatory)
- The card location as stenciled on the shelf of the system.
- Range:
- 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118
Example
chg-lg-card:loc=1304:grp=lggroup1
Dependencies
The specified grp parameter value must exist in the database.
The card location must not be 1113-1118, or xy09 and xy10 where x is the frame and y is the shelf.
The LG Card table is corrupt or cannot be found.
The card location specified in the loc parameter must be of a provisioned LG card.
The LG Group table is corrupt or cannot be found.
The loc and grp parameters are mandatory
Changing the group of an LG card to which it is already a part of has no effect.
Output
Related Topics
chg-lg-engine
Use this command to modify an LG engine. The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.
Parameters
- port (optional)
- The signaling link on the card specified in the loc parameter.
- Synonym:
- link
- Range:
- a, b, a1 - a31, b1 - b31
Not all card types support all link parameter values.
See Table A-1 for valid link parameter range values for each type of card that can have a location specified in the loc parameter.
Example
chg-lg-engine:engine=txengine1:txrate=100
chg-lg-engine:engine=txengine1:port=b
Dependencies
The engine name specified must pre-exist in the LG Engine table.
The LG Engine table is corrupt or cannot be found.
The number of events associated with a engine should not exceed the max limit.
The txrate parameter cannot be specified with the event parameter of Rx type.
The action=pbk parameter can only be assigned to Tx event direction.
The action parameter of type snk, ret, retl2, cong, or cap can only be assigned to RX event direction.
The port specified in the command must be provisioned.
The rxengine parameter can only be specified with the action=pbk parameter.
The LG Card and Event specified in the command must belong to same network
SIF Size > 272 not supported on ss7hc
The Rx Event can not be associated to more than one Engine on the same LG card
Event dir and Action cannot be changed if engine is of Rx type and associated with the Tx engine.
The LG Event name specified in the command must exist in the table
The specified Rx engine parameter value must be associated with the card.
The port parameter cannot be specified with the event parameter of Rx type.
Engine specified in RxEngine parameter must of Rx Type.
The Rxengine specified must pre-exist in the LG Engine table.
Output
Related Topics
chg-lg-event
Use this command to change an LG event’s characteristics. The command class is TKLC_INTERNAL inheriting properties of DEBUG class. The Load Generator is supported on IPSG, IPLHC, IPGHC and SS7HC GPLs.
Parameters
- cpc (optional)
- ANSI capability point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- cpca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- cpc/cpca/cpci/cpcn/cpcn24 (optional)
- Capability point code. The code used by the SS7 protocol to identify a group of functionally related STPs in the signaling network to which the STP belongs.
- cpcn (optional)
- ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc,m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- cpcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- dpc (optional)
- ANSI destination point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- dpca
- Range:
- p-, 000-255, *
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
The asterisk value (*) is not valid for the ni subfield.
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- dpci (optional)
- ITU international destination point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- dpcn (optional)
- ITU national destination point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- dpcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix indicates a private point code (prefix-msa-ssa-sp).
- opc (optional)
- ANSI originating point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Range:
- p-, 000-255, *
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
The asterisk value (*) is not valid for the ni subfield.
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- opci (optional)
- ITU international originating point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- opcn (optional)
- ITU national originating point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicatesa spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- opcn24 (optional)
- 24-bit ITU national originating point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- sgta (optional)
- Start of global title address. This parameter specifies the beginning of a range of global title digits.
Example
chg-lg-event:event=txisup1:dpc=3-3-3
chg-lg-event:event=txisup1:dpc=2-2-2:opc=1-1-1
chg-lg-event:event=rxisup1:dpc=4-4-4
Dependencies
If the h0h1/cnglvl/cause/usrid/cpc parameter is specified, then the si parameter must have a value of 0 (snm).
If the mincic/maxcic parameter is specified, then the si must have a value of 4 (tup), 5 (isup), or 13 (bicc)
If the tt/ssn/sgta/egta parameter is specified, the si must be 3 (sccp)
Failed to read LG Event table.
The LG Event name specified in the command must exist in the table
The event parameter is mandatory
The value specified for the mincic parameter must be less than the value specified for the maxcic parameter.
The minsize specified must be less than maxsize.
The value specified for the minsls parameter must be less than the value specified for the maxsls parameter.
ITU SLS must be less than 15
The OPC/DPC network type must match the provisioned OPC/DPC network type.
The value specified for the SIF size must be valid for the SI type.
The same DPC cannot be assigned to more than one Event of Rx type.
The value specified for the event name cannot be an EAGLE reserved name.
At least one optional parameter must be specified
SI-specific parameters cannot be specified together in the command.
Optional parameters except dpc cannot be specified with Rx event
The lengths of the values specified for the sgta and egta parameters must match
The sgta and egta parameters must be specified together in the command.
The value specified for the egta parameter must be greater than or equal to the value specified for the sgta parameter.
If the ri=gt parameter is specified, then the sgta/egta parameters must be specified.
If the lengths of the values specified for the sgta/egta parameters do not match the provisioned length of the sgta parameter, then the minsize parameter must be specified.
Output
Related Topics
chg-lnp-serv
Use this command to change an existing LNP service.
Parameters
Note:
All alias translation types must be removed before the service can be moved to another translation type.- ndfltact (optional)
- New default action associated with an LNP TT Service entry.
- Range:
- ayyyyyyyy
1 leading alphabetic character followed by up to 8 alphanumeric characters
The ndfltact parameter must have one of the following values:
- a GTT Action ID that already exists in the GTT Action table with an associated action of disc/udts/tcaperr
- fallback —Fallback to the relay data for MSUs relayed by LNP using relay data from the LNP database provided by the LNP Message Relay service. For an LNP Query message, the MSU is sent to the LNP local subsystem.
- falltogtt —Fallback to GTT. The GTT selector search is performed again, using gttselid=none.
- Default:
- No change to the current value
- nrqdtblnop (optional)
- The action performed with a message that arrives at an SCCP card that does not have the necessary LNP table, and the current message routing is subsystem.
- off (optional)
- Disables or turns off the specified feature options. This parameter specifies a comma-separated list of feature options that are requested to be turned off. Up to 10 feature options can be specified in the list.
- on (optional)
- Enables or turns on the specified feature options. This parameter specifies a comma-separated list of feature options that are requested to be turned on. Up to 10 feature options can be specified in the list.
Example
chg-lnp-serv:tt=10:ndfltact=fallback:on=gttrqd:ngttselid=none
chg-lnp-serv:serv=lidb:ntt=22:ndv=tcap:nttn=mrlidb
chg-lnp-serv:tt=239:nserv=lrnqt
Dependencies
The same value cannot be specified for the on and off parameters.
The ndfltact=none parameter cannot be specified.
The EGTT feature must be turned on before the ngttselid, ndfltact, or on/off=gttrqd parameter can be specified.
If a GTT Action ID is specified as the value for the ndfltact parameter, then the Action ID must already exist in the GTT Action table.
If a GTT Action ID is specified as a value for the ndfltact parameter, then the GTT Action ID must have an associated action of disc, udts, or tcaperr.
The LNP feature must be turned on before this command can be entered.
The LNP SMS feature must be turned on before the nserv=wsmsc parameter can be specified.
The PCS 1900 LNP (PLNP) feature must be turned on before the nserv=pcs parameter can be specified.
The WNP feature must be turned on before the nserv=wnp parameter can be specified.
The value of the ntt parameter cannot already exist in the LNP database.
The value of the nttn parameter cannot already exist in the LNP database.
The value of the serv parameter must already exist in the LNP database.
The serv or tt parameter and one other optional parameter must be specified.
The same value cannot be specified for the ndv and dv parameters.
An LNP alias cannot be specified as the value for the ntt parameter.
All LNP aliases for the existing service must be removed from the LNP database before the nserv or ntt parameter can be specified.
A reserved service type name can be specified as a value for the nttn parameter only if the name matches the existing service (the value specified for the serv parameter).
The LNP TT SERV table is corrupt or cannot be found.
If a value of wsmsc, udf1, udf2, udf3, or udf4 is specified for the serv parameter, then the ndv=sccp parameter must be specified.
If a value of lnpqs, ain, in, pcs, wnp, or lrnqt is specified for the serv parameter, then the ndv=tcap parameter must be specified.
The LRNQT feature must be turned on before the (n)serv=lrnqt parameter can be specified.
The GTT Action table is corrupt or cannot be found.
The value specified for the nserv parameter cannot already exist in the LNP database.
If the value specified for the tt parameter is an alias, then the ntt, nserv, nttn, and ndv parameters cannot be specified.
If the value specified for the (n)serv parameter is already associated with the class, lidb, cnam, isvm, wsmsc, udf1, udf2, udf3, or udf4 service, then a value of lnpqs, lrnqt, ain, in, wnp, or pcs cannot be specified for the (n)serv parameter.
The ndfltact, ngttselid, and on/off=gttrqd parameters cannot be specified with the udf1, udf2, udf3, and udf4 LNP Services.
The nrqdtblnop parameter requires that the Dual ExAP Config feature be enabled.
Notes
on/off options
gttrqd—GTT required. Specifies whether GTT is performed after the successful completion of an LNP Message Relay service and before initiation of an LNP Query service. This option has a default of OFF.
Output
chg-lnp-serv:tt=3:on=gttrqd:ngttselid=10:ndfltact=falltogtt
rlghncxa03w 10-11-08 08:50:12 EST EAGLE 43.0.0
CHG-LNP-SERV: MASP A - COMPLTD
;
Related Topics
chg-lnpopts
Use this command to enter LNP-specific system options in the database. This command updates the LNPOPTS table.
Parameters
Note:
As of Release 43.0, the dra, lrndgts, naiv, and tndgts parameters are obsolete for this command.- admhipri (optional)
- Give LNP database administration the highest administrative priority in the system.
- ccp (optional)
- Copy charge parameters. When this parameter has a value of yes, the system copies the Charge Number and Charge Party Station type from an LNP AIN query (if present) to the LNP AIN Response message.
- jipprv (optional)
- Determines whether a Jurisdictional Information Parameter value is to be added to the IAM.
- servport (optional)
- Service portability.
- Range:
-
- yes
- allows splitting services between TN and LRN override records. This setting allows the LNP user to update LRN overrides for message relay services that are to be supported in the network. The TN gateway point code (NPAC subscription data) is used for message relay services the CLEC wants to provide.
- no
- If no LRN override services are provisioned, then the TN’s gateway point codes (NPAC subscription data) are used to route queries out of the network. If one or more LRN override services are provisioned, the TN is considered to be ported into the network. In this case, if an LRN override service is requested and the LRN has other services administered, but the requested service is not provisioned, then a UDTS response for the service is provided.
- Default:
- No change to the current value
- tndgts (optional)
- SCCP GTA digit length indicator for 10 or 11 digits.
- Range:
-
- yes
- The system verifies that either 10 or 11 digits are present in the CDPA GTA. If 11 digits are present, the first digit is stripped to derive 10 digits for LNP SMS translation. If 10 digits are present, all 10 digits are used for LNP SMS translation.
- no
- The system verifies that 11 digits (plus a padded 0 digit) are present in the CDPA GTA. If 11 digits are present, the system strips the first digit and considers only 10 digits for LNP SMS translation.
- Default:
- No change to the current value
Example
chg-lnpopts:amaslpid=123456789
chg-lnpopts:amactype=003
chg-lnpopts:amafeatid=010
chg-lnpopts:incslp=yes
chg-lnpopts:cic=1369
chg-lnpopts:sp=1234
chg-lnpopts:jipdigits=919460
chg-lnpopts:jipprv=yes
chg-lnpopts:frcsmplx=yes
chg-lnpopts:admhipri=yes
chg-lnpopts:gtwystp=yes
chg-lnpopts:ccp=yes
chg-lnpopts:servport=yes
chg-lnpopts:wqredrct=off
chg-lnpopts:wsmsc10dig=yes
Dependencies
At least one optional parameter must be specified.
The LNP and Triggerless LNP (TLNP) features must be turned on before this command can be entered.
The LNP database must be accessible.
The Triggerless LNP feature must be turned on before the jipprv and jipdigits parameters can be specified.
The LNP SMS feature must be turned on before the wsmsc10dig parameter can be specified.
The LNP options table must be accessible.
The LNP feature or AINPQ feature must be turned on before this command can be entered.
The WNP or PCS feature must be turned on before the wqredrct parameter can be specified.
Notes
If the admhipri=yes parameter is specified, LNP database administration can starve out normal STP updates during LNP administration of 2 TNs per second. If the parameter is set to no, then STP and LNP updates receive the same priority. Depending on the system activity level, the performance of LNP updates may be reduced.
If the gtwystp=yes parameter is specified, the LNP system is also configured as a gateway STP. The NPAC sends down capability point codes without routes. In this configuration, the system does not output a warning (UIM 1176) about capability point codes or true point codes without routes.
MTT rule E3524 has been deleted in Release 43.0 under PR 168138.
AINPQ feature dependency is required to get AIN queries processed by INPQ subsystem.
Output
chg-lnpopts:amaslpid=123456789
rlghncxa03w 04-01-07 00:57:31 EST EAGLE 31.3.0
CHG-LNPOPTS: MASP A - COMPLTD
;
Related Topics
chg-loopset
Use this command to change the loopset data in the database. This command updates the Loopset Table. A single instance of this command can be used to append up to 6 point codes to the loopset (a loopset can contain a total of 12 point codes), replace all data in the loopset, or change one or two point codes in the loopset.
Parameters
- name (mandatory)
- Loopset name. Sn entry in the Loopset table.
The name=none parameter cannot be specified.
- apcl (optional)
- ANSI appending point code list with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm). This parameter allows up to 6 comma-delimited entries in the point code list.
- Synonym:
- apcla
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- apcli (optional)
- ITU international appending point code list with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id). This parameter allows up to 6 comma delimited entries in the point code list.
- apcln (optional)
- ITU national appending point code list in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc). This parameter allows up to 6 comma-delimited entries in the point code list.
- apcln24 (optional)
- 24-bit ITU national appending point code list with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). This parameter allows up to 6 comma-delimited entries in the point code list.
- apc1n16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). This parameter allows up to 6 comma-delimited entries in the point code list.
- mode (optional)
- Mode of operation. This parameter specifies whether the message is discarded when an SCCP loop is detected.
- npc1 (optional)
- ANSI new point code 1 with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- npc1a
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- npc1i (optional)
- ITU international new point code 1 with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- npc1n (optional)
- ITU national new point code 1 in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the chg-stpopts:npcfmti flexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc).The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- npc1n24 (optional)
- 24-bit ITU national new point code 1 with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- npc1n16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). This parameter allows up to 6 comma-delimited entries in the point code list.
- npc2 (optional)
- ANSI new point code 2 with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- npc2a
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- npc2i (optional)
- ITU international new point code 2 with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- npc2n (optional)
- ITU national new point code 2 in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- npc2n24 (optional)
- 24-bit ITU national new point code 2 with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- npc2n16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). This parameter allows up to 6 comma-delimited entries in the point code list.
- pc1 (optional)
- ANSI point code 1 with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- pc1a
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- pc1i (optional)
- ITU international point code 1 with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- pc1n (optional)
- ITU national point code 1 in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pc1n24 (optional)
- 24-bit ITU national point code 1 with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- pc1n16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). This parameter allows up to 6 comma-delimited entries in the point code list.
- pc2 (optional)
- ANSI point code 2 with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- pc2a
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- pc2i (optional)
- ITU international point code 2 with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- pc2n (optional)
- ITU national point code 2 in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pc2n24 (optional)
- 24-bit ITU national point code 2 with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- pc2n16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). This parameter allows up to 6 comma-delimited entries in the point code list.
- rpcl (optional)
- ANSI replacing point code list with subfields network indicator-network cluster-network cluster member (ni-nc-ncm). The prefix subfield indicates a private point code (prefix-ni-nc-ncm). This parameter allows up to 6 comma-delimited entries in the point code list.
- Synonym:
- rpcla
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- rpcli (optional)
- ITU international replacing point code list with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id). This parameter allows up to 6 comma-delimited entries in the point code list.
- rpcln (optional)
- ITU national replacing point code list in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc). This parameter allows up to 6 comma-delimited entries in the point code list.
Example
This example sets the mode to discard and appends the listed point codes to the loopset RTP1 if the set is not being used by GTT.chg-loopset:name=rtp1:mode=discard:apcl=3-7-3,5-7-5,7-4-7,5-4-5
This example replaces the point codes in the set with the listed point codes for the loopset RTP1 if the set is not being used by GTT.chg-loopset:name=rtp2:rpcl=3-2-3,5-7-8,7-8-7,3-5-3
This example sets the mode to DISCARD in the loopset RTP2 if the set is not being used by GTT.chg-loopset:name=rtp2:mode=discard
This example replaces PC1 with NPC1 in the loopset RTP1 if the set is not being used by GTT.chg-loopset:name=rtp1:pc1=3-3-3:npc1=3-3-9
This example replaces PC1 and PC2 with NPC1 and NPC2 in the loopset RTP2 if the set is not being used by GTT.chg-loopset:name=rtp2:pc1=3-2-3:npc1=3-3-9:pc2=7-8-7:npc2=7-7-9
This example sets the mode to NOTIFY in the loopset RTP2 even if the set is being used by GTT.chg-loopset:name=rtp2:mode=notify:force=yes
chg-loopset:name=rtpn16:pc1n16=3-2-3:npc1n16=3-3-9:pc2n16=7-8-7:npc2n16=7-7-9
Dependencies
If the loopset is being used by GTT, and the rpcl, pc1/pc2/npc1/npc2, or mode parameter is specified, then the force=yes parameter must be specified.
If the pc2 parameter is specified, then the pc1 parameter must be specified.
If the npc1 or npc2 parameter is specified, then the corresponding pc1 or pc2 parameter must be specified.
The command requires at least one optional parameter.
The rpcl and apcl parameters cannot be specified together in the command.
If the pc1 or pc2 parameter is specified, then the apcl and rpcl parameters cannot be specified.
The value of the name parameter must already exist in the database.
The SCCP Loop Detection feature must be enabled before this command can be entered.
The GTT feature must be turned on before this command can be entered.
A maximum of 6 point codes can be added using this command with the apcl parameter. The Loopset entry can contain a maximum of 12 point codes.
The Loopset table can hold a maximum of 1,000 loopset entries, with each entry containing up to 12 point codes. Additional loopset entries and point codes cannot be added when the table is full.
The Loopset table must be accessible.
The values for the apcl and rpcl parameters cannot consist of any invalid point codes. The valid point codes must be consecutively specified and separated by commas.
The name=none parameter cannot be specified.
At least one valid point code must be specified as a value for the apcl and rpcl parameters.
The values specified for the apcl and rpcl parameters must be unique.
If the npc1/pc1 or npc2/pc2 parameters are specified together, then the value of the npc parameter cannot equal the value of the pc parameter.
A valid point code must be specified for the pc1, pc2, npc1 or npc2 parameter.
Equal values cannot be specified for the pc1 and pc2 parameters.
Equal values cannot be specified for the npc1 and npc2 parameters.
The GTT table must be accessible.
When adding point codes using the apcl parameter, or changing point codes using the pc1/npc1 or pc2/npc2 parameters, the new point code type must match the point code type of the loopset where the point codes are being added or changed.
The value of the apcl parameter cannot already exist in the loopset.
The value of the pc1 or pc2 parameter must already exist in the loopset.
Notes
There is no J7 FAK dependency on the apcln16/rpcln16/pc1n16/npc1n16/pc2n16/npc2n16 parameters. The command can be entered successfully when the J7 FAK is not enabled.
There is no J7 FAK dependency on the apcln24/rpcln24/pc1n24/npc1n24/pc2n24/npc2n24 parameters. The command can be entered successfully when the J7 FAK is enabled.
There is no J7 FAK dependency on the apcl/apcla/rpcla/pc1a/npc1a/pc2a/npc2a parameters. The command can be entered successfully when the J7 FAK is enabled.
Output
This example replaces the existing point codes with new point codes in loopset RTP2 when that set is not being used by GTT:
chg-loopset:name=rtp2:pc1=3-2-3:npc1=3-3-9:pc2=7-8-7:npc2=7-7-9
rlghncxa03w 07-02-10 08:41:17 EST EAGLE Rel 35.6.0
LOOPSET table is (12 of 1000) 1% full
CHG-LOOPSET: MASP A – COMPLTD
;
Related Topics
chg-ls
Use this command to change the attributes for a specified linkset in the system database. The new values overwrite the existing values. All parameters required for MTP distribution will be used whether they are explicitly specified or obtain from existing provisioning.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.- action (optional)
- This parameter adds or deletes the SAPC, mate IPGWx linkset name, or the value specified for the rcontext parameter.
- apc (optional)
- ANSI point code with subfields network indicator-network
cluster-network cluster member (ni-nc-ncm). The prefix subfield
indicates a private point code (prefix-ni-nc-ncm).
- Synonym:
- apca
- Range:
- p-, 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.The point code 000-000-000 is not a valid point code.
- apci (optional)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- apcn (optional)
- ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4
numbers (members) separated by dashes (m1-m2-m3-m4) as
defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- apcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix indicates a private point code (prefix-msa-ssa-sp).
- apcn16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna). The prefix indicates a private point code (prefix-un-sna-mna).
- apcntype (optional)
- ITU-N Adjacent Point Code Type. The format used for changeover and changeover acknowledgement messages.
- asl8 (optional)
- Adjacent SLS 8-bit indicator. This parameter specifies whether the adjacent node is sending MSUs with 8-bit SLSs.
- asnotif (optional)
- AS notification. This parameter specifies whether AS notifications are sent for an IPSG linkset.
- bei (optional)
- Broadcast exception indicator. This parameter specifies whether TFP (transfer prohibited) messages are allowed to be broadcast on the linkset.
- cggtmod (optional)
- Calling party GT modification indicator. This parameter specifies whether calling party global title modification is required for the specified linkset.
- chgmtp3opc (optional)
- Change MTP3 OPC. This parameter specifies whether to change MTP3 OPC with SPC or not.
- clli (optional)
- Far-end Common Language Location Identifier (CLLI). The CLLI assigned to the linkset.
- gsmscrn (optional)
- GSM MAP screening. This parameter specifies whether GSM MAP screening is allowed.
- gttmode (optional)
- Global Title Translation Mode. This parameter specifies a GTT
Mode hierarchy for each link set.
- Range:
-
- cd
- CdPA GTT only
- cg
- CgPA GTT only
- acdcd
- Advanced CdPA GTT, CdPA GTT
- acdcgcd
- Advanced CdPA GTT, CgPA GTT, CdPA GTT
- acdcdcg
- Advanced CdPA GTT, CdPA GTT, CgPA GTT
- cgacdcd
- CgPA GTT, Advanced CdPA GTT, CdPA GTT
- cgcd
- CgPA GTT, CdPA GTT
- cdcg
- CdPA GTT, CgPA GTT
- fcd
- FLOBR CdPA only
- fcg
- FLOBR CgPA only
- fcgfcd
- FLOBR CgPA, FLOBR CdPA
- fcdfcg
- FLOBR CdPA, FLOBR CgPA
- sysdflt
- System wide default value
- Default:
- No change to current value.
- gwsa (optional)
- Gateway screening action. This parameter specifies whether gateway screening (GWS) is on or off for the specified linkset.
- gwsd (optional)
- Gateway screening MSU discard. This parameter specifies whether the discarding of MSUs that bypass the gateway screening function due to load-shedding is on or off. This parameter is also used with the redirect function; MSUs that cannot be screened are discarded if gwsd=on is specified.
- gwsm (optional)
- Gateway screening messaging. This parameter specifies whether messages are generated for each message screened by gateway screening.
- ipsg (optional)
- IP signaling gateway adjacent point code. This parameter specifies whether a linkset is entered for an IPSG card. The specified adjacent point code is an IP gateway adjacent point code.
- islsrsb (optional)
-
Incoming rotated signaling link selection (SLS) bit. The bit (1-4) for ITU and (1–8) for ANSI link sets to rotate as the new SLS LSB (Least Significant Bit) of the incoming linkset. The SLS is not modified in the outgoing message.
Table 4-32 shows how the rotation affects the four bits of the ITU SLS during linkset selection.
Table 4-33 shows how the rotation affects the four bits of the ANSI SLS during linkset selection.
This parameter is used for ITU or ANSI messages on a per-linkset basis.
- itutfr (optional)
- ITU TFR (Transfer Restricted) procedure indicator. This parameter specifies whether the TFR procedure is on or off on a per-linkset basis. This parameter is valid for ITU national linksets only.
- lst (optional)
- Linkset type of the specified linkset. This parameter specifies whether the specified link is an access link, bridge link, cross link, diagonal link, or extended link, as defined in Telcordia GR-246-CORE, T1.111.5.
- lsusealm (optional)
- IPTPS linkset alarm threshold percent. The percent of the linkset TPS (iptps) at which an alarm is generated to indicate that the actual linkset TPS is approaching the configured iptps value for the linkset.
- maxslktps (optional)
-
Maximum per signaling link TPS. The maximum capacity a link is permitted when sufficient unused capacity is present on the host card.
Note:
This parameter cannot be specified for links in non-IPSG linksets.If the HIPR2 High Rate Mode feature is turned off, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 500,000. If the HIPR2 High Rate Mode feature is turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 750,000. If the HIPR2 High Rate Mode and 1M System TPS features are turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 1,000,000.
- Range:
- 25 - 12,000
Note:
The maximum value that can be specified for this parameter depends on the type of IPSG card that is used:- E5-ENET-B card when the E5-ENET-B IPSG High Throughput feature is turned off-6500 TPS
- E5-ENET-B card when the E5-ENET-B IPSG High Throughput feature is turned on-9500 TPS
- SLIC card - 12,000 TPS
- Default:
- No change to the current value
- System Default:
- 6500
- mtprse (optional)
- ANSI or ITU MTP Restart equipped. This parameter specifies whether the node adjacent to the linkset is equipped with MTP Restart.
- multgc (optional)
- Multiple group codes. The parameter specifies whether multiple group codes can be specified.
- nis (optional)
- Network Indicator Spare. This parameter specifies whether the Network Indicator Spare option is on or off for the specified linkset. When this option is enabled, the Network Spare value for network indicator for both ANSI and ITU-National (ITU-N) links is supported by the system.
- randsls (optional)
- Random SLS (signaling link selection). This parameter is used
to apply random SLS generation on a per linkset basis.
Specifying this parameter enables random SLS generation on a per linkset basis only if the randsls=perls parameter has been specified in the
chg-stpoptscommand. For more details, refer to Database Administration - SS7 User's Guide, Per-Linkset Random SLS.
- sapci (optional)
- ITU international secondary adjacent point code with subfields zone-area-id. The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-zone-area-id).
- sapcn (optional)
- ITU national secondary adjacent point code in the format of a
5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as
defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code, private point code, or private and spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- sapcn24 (optional)
- 24-bit ITU national secondary adjacent point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp). The prefix indicates a private point code (prefix-msa-ssa-sp).
- scrn (optional)
- Gateway screening screen set. The gateway screening screen
set assigned to this linkset.
When using this parameter to change Gateway Screening from an old screenset name with Gateway Screening Allowed Mode gwsa=off to a new screenset name with gwsa=on, the command must first be entered to assign the screenset name to NONE (scrn=none). This assignment prevents any rules from the old screenset from being applied during the interim period that it takes for the new screenset to load.
- slktps (optional)
-
Reserved per signaling link TPS for IPSG Linkset. The capacity guaranteed for each link in the linkset.
Note:
This parameter is required for each link in an IPSG linkset and cannot be specified for links in non-IPSG linksets.Note:
The sum of guaranteed capacities for the links hosted by an IPSG card cannot exceed the IPSG card capacity.Note:
If the HIPR2 High Rate Mode feature is turned off, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 500,000. If the HIPR2 High Rate Mode feature is turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 750,000. If the HIPR2 High Rate Mode and 1M System TPS features are turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 1,000,000.- Synonym:
- rsvdslktps
- Range:
- 0 - 12,000
Note:
The maximum value that can be specified for this parameter depends on the type of IPSG card that is used:- E5-ENET-B card when the E5-ENET-B IPSG High Throughput feature is turned off-6500 TPS
- E5-ENET-B card when the E5-ENET-B IPSG High Throughput feature is turned on-9500 TPS
- SLIC card - 12,000 TPS
- Default:
- No change to the current value
- slkusealm (optional)
- IPTPS signaling link alarm threshold percent. The percent of the link TPS at which an alarm is generated to indicate that the actual link TPS is approaching the alarmed IPTPS (slktps/rsvdslktps or maxslktps) configured for the link.
- slsci (optional)
- 5-bit to 8-bit SLS conversion indicator. This parameter specifies whether the 5-bit to 8-bit SLS conversion feature is used to select links for outgoing messages direct to the given linkset. When enabled, the system replaces any 5-bit SLS values contained in received messages, with a random 8-bit value before the 5-bit SLS values are used by the STP to select the outgoing link in that linkset.
- slsocbit (optional)
- Other CIC (Circuit Identification Code) Bit. If the SLSOCB
feature is turned on, this parameter specifies whether the Other CIC Bit
option is to be used during link selection. If the option is to be used,
specify which bit (5– 16) of the CIC is to be used as the other CIC bit.
During link selection, the specified bit acts as the most significant bit of
the new SLS and bits 2 through 4 of the received CIC become the least
significant bits of the new SLS. This parameter is used for ITU-ISUP
messages. The SLS is not modified in the outgoing message. Table 4-11 shows a received
CIC where bit 9 is the other CIC bit (slsocbit=9). The new SLS is 0100:
Table 4-11 slsocbit example (chg-ls)
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0 0 0 1 0 0 0 1 0 0 1 1 0 0 1 New SLS 0 1 0 0
- slsrsb (optional)
-
Rotated SLS (Signaling Link Selection) Bit. The bit (1–4) to rotate as the new SLS LSB (Least Significant Bit). The SLS is not modified in the outgoing message.
Table 4-35 shows how the rotation affects the SLS during linkset selection.
This parameter is used for ITU messages on a per-linkset basis.
- spc (optional)
- ANSI secondary point code with subfields network indicator-network
cluster-network cluster member (ni-nc-ncm).
- Synonym:
- spca
- Range:
-
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
p-, 000-255, none
prefix—p-
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid for ni = 001-005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006-255.Enter none to delete the point code.
The point code 000-000-000 is not a valid point code.
- spci (optional)
- ITU international secondary point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- spcn (optional)
- ITU national secondary point code in the format of a 5-digit
number (nnnnn); or 2,
3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as
defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- spcn24 (optional)
- 24-bit ITU national secondary point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- spcn16 (optional)
- 16-bit ITU national point code with subfields unit number sub number area main number area (un-sna-mna).
- tfatcabmlq (optional)
- TFA/TCA broadcast minimum link quantity. The minimum number
of links in the given linkset, or in the combined linkset in which the
linkset resides, that must be available to user-part messages traffic. This
parameter value is used by the STP to consider the first-choice ordered
routes using that linkset as Allowed rather than Restricted.
If this parameter's provisioned or default value is 0, then the TFA/TCA broadcast minimum link quantity is calculated by the system to be either 1 for linksets containing 2 or fewer links, or half (rounded-up) of the number of links configured in the linkset for linksets containing more than 2 links.
If this parameter value is set to a specific value greater than 0, then the system does not calculate a TFA/TCA broadcast minimum link quantity. The specified value is used.
Example
Changes linkset WY644368 to use APC 144-202-5:
chg-ls:lsn=wy644368:apc=144-202-005
Changes link set WY644368 to Link Set Type A:
chg-ls:lsn=wy644368:lst=a
Adds an SAPC to a linkset:
chg-ls:lsn=linkset:sapcn=1234-fr:action=add
chg-ls:lsn=c002:gwsm=on: nis=on
chg-ls:lsn=nc003:sltm=reg:lst=b
Adds a 24-bit ITU-N SAPC to a linkset:
chg-ls:lsn=ls1:sapcn24=5-5-5
Deletes a 24-bit ITU-N SAPC from a linkset:
chg-ls:lsn=ls1:sapcn24=5-5-5:action=delete
Assigns a mate linkset to a linkset:
chg-ls:lsn=linkset:matelsn=matelinkset
Changes an ITUN24 linkset to an APCNTYPE for China:
chg-ls:lsn=ls2:apcntype=itunchina
chg-ls:lsn=nc003:slsci=yes:tfatcabmlq=2
chg-ls:lsn=lsitu1:gsmscrn=off
chg-ls:apca=p-011-2-3:lsn=lsa1:lst=a
chg-ls:lsn=ls1:randsls=all
Indicates that calling party GT modification is required:chg-ls:lsn=ls1:apc=1-1-1:cggtmod=yes
Changes the linkset's SPC value:chg-ls:lsn=lsl:spc=100-23-48
Changes the adapter of a specified IPSG linkset:chg-ls:lsn=ls2:adapter=m2pa
Changes the AS notification status and routing context value for an IPSG-M3UA linkset:chg-ls:lsn=m3ua33:rcontext=9999:action=add
Converts the linkset to IPSG:chg-ls:lsn=m2pa33:ipsg=yes
This command changes the Incoming SLS Bit Rotation value to 6 for ANSI link sets:chg-ls:lsn=ls1:islsrsb=6
Changes the GTTMODE value to FLOBR CdPA when the FLOBR feature is turned on:chg-ls:lsn=ls3:gttmode=fcd
Converts the linkset to SLT reflect mode:chg-ls:lsn=ls1:sltset=0
Change adapter type of a 16-bit ITU national linkset type:
chg-ls:lsn=ls1:apcn16=121-5-15:adapter=m3ua
Change linkset chgmtp3opc parameter:
chg-ls:lsn=ls112:chgmtp3opc=off
Change linkset gnameset parameter:
chg-ls:lsn=ls112:gnameset=setb
Change linkset cgpnblset parameter:
chg-ls:lsn=ls112:cgpnblset=3
Dependencies
A valid screenset name must be associated with the linkset, or the scrn parameter must be specified with a valid screenset name before the gwsa, gwsm, and gwsd parameters can be specified.
The gwsa=on parameter must be specified before the gwsd=on parameter can be specified.
At least one optional parameter must be specified.
If the
lsrestrict=off parameter is
specified (see the
chg-ss7opts command), the
tfatcabmlq database value for
C linksets cannot be changed from the system default of 0. If the
lsrestrict=on parameter is
specified, the
tfatcabmlq value for C linksets
(lst=c) can be set to 1 - 16. If the
tfatcabmlq value for one or more
C linksets in the system is changed, the
lsrestrict parameter cannot be
changed from
on to
off until all of the changed C linkset
tfatcabmlq values are set back to 0.
C linksets are never the primary route (except to reach the STP’s mate).
The tfatcabmlq parameter value cannot exceed the total number of assigned links in the linkset.
The linkset name must be in the database.
The screen set name specified by the scrn parameter must be valid and must be in the database.
Adjacent point codes must be full point codes.
The adjacent point code must be defined as a destination point code.
The adjacent point code cannot match the site point code.
The domain of the new adjacent point code must be the same as the previous adjacent point code unless there are no links in the linkset.
Only one linkset can be defined for an adjacent point code.
An SAPC cannot be deleted when routes exist for its SS7 domain.
If the gwsa=off and gwsm=off parameters are specified, all MSUs are passed. If the gwsa=off and gwsm=off parameters are specified for all linksets, gateway screening and the GWS redirect function for the DTA feature are disabled.
If the gwsa=on and gwsm=off parameters are specified, MSUs are screened but messages are not generated.
Caution:
Even though gateway screening is in the screen test mode, as defined by the parameters gwsa=off and gwsm=on, the gateway screening action in the stop action set specified by the actname parameter of the screen set is performed at the end of the screening process. The
mtprse parameter can be specified
only if the MTP restart feature, MTPRS (for ANSI), or ITUMTPRS (for ITU), is
turned on. The
rtrv-feat command can be used to
verify whether the feature is turned on (MTPRS=YES or ITUMTPRS=YES in the
output).
If the ipgwapc=yes or ipsg=yes parameter is specified, then the mtprse=yes parameter cannot be specified.
The clli and apc/apca/apci/apcn/apcn24/apcn16 parameters must be specified together in the command.
The value of the clli parameter must match the clli of the current site.
The asl8=yes parameter can be assigned only to an SS7 linkset (a linkset containing an adjacent point code in the SS7 domain).
The
apcn parameter format must match the
format assigned with the
chg-stpopts:npcfmti parameter.
An SAPC parameter can be specified only for ITU-N and ITU-N24 linksets.
The slsocbit parameter is valid only for ITU linksets.
The slsrsb parameter is valid only for ITU linksets.
The GSM Map Screening feature must be turned on before the gsmscrn parameter can be specified.
The Enhanced GSM Map Screening feature must be turned on before the gsmscrn=on parameter can be specified for an ANSI linkset.
The itutfr parameter is valid only for ITU national linksets.
The group code of DPC(s) must match the group code of the APC/SAPC when the multgc=no parameter is specified.
If the adjacent point code’s group code is changed, the multgc=yes parameter must be specified, or there must be no routes using the linkset.
The multgc parameter value can be changed to no only if there are no routes with group codes different from the adjacent point code’s group code.
Only one ITU-N APC/SAPC is allowed with the multgc=no parameter.
Only one ITU-I or 24-bit ITU-N APC/SAPC is allowed per linkset.
The apcntype parameter can be specified only for ITU-N and ITU-N24 linksets.
A linkset cannot have both a 14-bit ITU-N and a 24-bit ITU-N APC/SAPC unless it contains only IPGWI links. These links support 14-bit ITU-N and 24-bit ITU-N traffic simultaneously.
A linkset with the ipgwapc=no parameter cannot have both a 14-bit ITU-N and a 24-bit ITU-N APC/SAPC if no links are provisioned.
The SAPC cannot be a 24-bit ITU-N point code if the linkset contains E1 ATM links, which do not support 24-bit ITU-N traffic.
The ipgwapc=yes or ipsg=yes parameter must be specified before the lsusealm parameter can be specified.
The ipgwapc=yes or ipsg=yes parameter must be specified before the slkusealm parameter can be specified.
The same value cannot be specified for the lsn and matelsn parameters.
If the action=add parameter is specified, the specified mate linkset cannot already be assigned as the mate of the specified linkset.
When the action=add parameter is specified, the specified mate linkset cannot already be the mate of another linkset.
The specified mate linkset must be an existing linkset in the database.
A mated linkset can have only one assigned link.
Mated linksets can contain only SS7IPGW or IPGWI links.
Mated linksets must have APCs of the same network type.
The card that has the link assigned to the specified linkset must be inhibited before the action=add parameter can be specified to assign the specified mate linkset to the specified linkset.
The card that has a link in the mate linkset must be inhibited before the action=delete parameter can be specified to delete the mate linkset assignment.
If the action=delete parameter is specified to delete a mate linkset assignment, the specified mate linkset must be the mate of the specified linkset in the database.
If the action=delete parameter is specified, then the sapc, matelsn, or rconext parameter must be specified. The parameters cannot be specified together in the command.
The
mtprse parameter can be specified
only if the MTP restart feature ITUMTPRS (for ITU) is turned on. The
rtrv-feat command can be used to
verify whether the feature is turned on (ITUMTPRS=YES in the output).
The slsocbit parameter is valid only if the SLSOCB feature is turned on.
The adjacent point code cannot match the capability point code.
The STP Site ID table is corrupt or cannot be found.
The Linkset table is corrupt or cannot be found.
The Route table is corrupt or cannot be found.
An APC cannot be changed to a point code that has exception routes provisioned.
The Route Exception table is corrupt or cannot be found.
The Origin-based SCCP Routing feature must be turned on before the gttmode parameter can have a value of acdcd, cgacdcd, acdcgcd, acdcdcg, cgcd, cdcg, or cg.
All links assigned to the linkset must be removed before changing the apcntype parameter value from apcn to apcn24 or from apcn24 to apcn.
If one or more of the links in the specified linkset are in service, then the apc/apca/apci/apcn/apcn24/apcn16 parameter cannot be specified.
If
apcn is specified for the Adjacent
Point Code then the format of
apcn must match the format dictated
by the
npcfmti parameter via the
chg-stpopts command.
Gateway linksets must be configured from a SEAS terminal.
If the system is configured for ANSI formatted point code, the network indicator value of the foreign point code parameter must be 6 or greater when the cluster value is 0.
The value of the apc/apca/apci/apcn/apcn24/apcn16 or sapc/sapca/sapci/sapcn/sapcn24 parameter cannot be assigned to more than one linkset.
The new apc/apca/apci/apcn/apcn24/apcn16 parameter must have the same point code type as the apc/apca/apci/apcn/apcn24/apcn16 parameter currently specified for the linkset.
The value of the apc/apca/apci/apcn/apcn24/apcn16 parameter must exist in the Point Code table.
The lst parameter must have a value of b, c, or d if a network or cluster route is configured through the linkset.
If the multgc=yes parameter is specified, then an IPGWI or IPLIMI link must be specified.
If the ITUDUPPC feature is off, then the multgc=yes parameter cannot be specified.
If the multgc=yes parameter is specified, then the apci, apcn, apcn16, or apcn24 parameter must be specified.
The value of the sapc/sapca/sapci/sapcn/sapcn24 parameter must exist in the Destination Point Code table.
The apc/apca/apci/apcn/apcn24 or sapc/sapca/sapci/sapcn/sapcn24 parameter can be defined only once per linkset.
The maximum number of sapc/sapca/sapci/sapcn/sapcn24 entries is 1000.
The value of the specified lsn parameter cannot already exist in the database.
The specified matelsn parameter must already be equipped in the linkset database.
If the linkset is not mated to the linkset specified by the matelsn parameter, then the action=delete parameter cannot be specified.
The value specified for the spc parameter must be a valid full point code.
The values specified for the spc and apc parameters must have the same network type.
If the sapc, matelsn, rcontext, or action parameter is specified, then those four parameters are the only optional parameters that can be specified. If the action parameter is specified, then the sapc or rcontext or matelsn parameter must be specified. If the ipsg parameter is specified, then no other optional parameters can be specified.
The Multiple Linksets to Single Adjacent PC (MLS) feature must be turned on before the spc parameter can be specified.
The value specified for the spc parameter must already exist in the SPC table.
The SPC table must be accessible.
The point code type of the value specified for the spc parameter must be the same as the point code type of the value of the existing spc parameter.
The value specified for the spc parameter cannot already be specified as a secondary point code for an adjacent destination point code.
The value specified for the apc parameter must differ from the adjacent point code of the linkset specified by the lsn parameter.
The value specified for the spc parameter must differ from the secondary point code of the linkset specified by the lsn parameter.
If a proxy linkset is used, then the apc, sapc, action, and lst parameters cannot be specified.
The specified combination of the apc and spc parameters must be unique for each linkset.
The specified combination of the apc and sapc parameters must be unique for each linkset.
The AMGTT feature or the AMGTT CgPA Upgrade feature must be turned on before the cggtmod parameter can be specified.
The ipsg=yes parameter must be specified before the adapter parameter can be specified.
The ipsg=yes and adapter=m3ua parameters must be specified before the asnotif parameter can be specified.
The ipsg=yes and adapter=m3ua parameters must be specified before the rcontext parameter can be specified.
If the IPSG linkset contains links, then the adapter parameter cannot be specified.
The ipsg=yes parameter must be specified before the slktps/rsvdslktps or maxslktps parameter can be specified.
If the ipsg=yes and adapter=m3ua parameters are specified, then the lst=a parameter must be specified.
A maximum of 1 IPGW linkset or a maximum of 6 of any other linksets are allowed between any APC and the EAGLE.
If the HIPR2 High Rate Mode feature is turned off, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 500,000. If the HIPR2 High Rate Mode feature is turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 750,000. If the HIPR2 High Rate Mode and 1M System TPS features are turned on, then the sum of the TPS values assigned to all linksets in the system must be less than or equal to 1,000,000.
The value specified for the slktps/rsvdslktps parameter cannot cause the card to exceed the total maximum capacity of the card.
If the ipsg=yes and adapter=m3ua parameters are specified, then the multgc=yes parameter cannot be specified.
If the ipsg=yes and adapter=m3ua parameters are specified, then the tfatcabmlq parameter cannot be specified.
If the action=delete parameter is specified to delete the routing context, then the value specified for the rcontext parameter must be the value used by the specified linkset in the database.
The link must be equipped.
The Link table is corrupt or cannot be found.
If the linkset already contains IPSG links, then the ipsg=no parameter cannot be specified.
If the ipsg=yes and adapter=m3ua parameters are specified, then a secondary adjacent point code cannot be specified for the linkset.
If one or more links in a specified linkset are in service, then the rcontext parameter cannot be specified.
Multiple signaling links in a single linkset cannot share the same association.
If multiple linksets share an association, then the rcontext parameter cannot be specified for only one linkset.
The value specified for the rcontext parameter must already exist in the database.
If a linkset shares an association with another linkset, then a unique value for the rcontext parameter must be specified for each linkset.
If the ipsg=yes parameter is specified, then the slktps/rsvdslktps parameter must be specified.
If the multgc=yes parameter is specified, then all links assigned to the linkset must be of the same type.
If any of the links are not in the OOS state, then the rcontext parameter cannot be specified.
The ISLSBR feature must be enabled before the islsrsb parameter can be specified.
The FLOBR feature must be turned on before the gttmode parameter can have a value of fcd, fcg, fcgfcd, or fcdfcg.
The SAPC table is corrupt or cannot be found.
The
rsls8=yes parameter (see the
chg-lsopts
command) must be specified for an ANSI linkset before a
value greater than 5 can be specified for the
islsrsb parameter.
If an ITU linkset is used, then a value of 1 – 4 must be specified for the islsrsb parameter.
The value specified for the slktps/rsvdslktps parameter must be less than or equal to the value specified for the maxslktps parameter.
The sltset=0 parameter can be specified only for a type A linkset (lst=a).
The value specified for the slktps/rsvdslktps and maxslktps parameters must be within the allowed range.
The ITUTFR (command
ent/chg-ls) cannot be specified for a
linkset to be configured for APCN16.
The NIS (command
ent/chg-ls) cannot be specified for a
linkset to be configured for APCN16.
The PPC specified must not be a private point code.
The MTP Restart Equipped (MTPRSE) parameter is only valid for adjacent ANSI nodes in the SS7 domain.
The adapter type specified must be either m3ua or m2pa.
The GTT destination must exist in the DSTN table.
Notes
Any optional parameter that is not specified is not changed.
The links that directly connect the system with a distant node are grouped into one or more linksets. A linkset can contain up to 8 (international standards) or 16 (national standard) signaling links, depending on how the system attributes were defined when the network was created.
Signaling link test acknowledgments (SLTA) are the same type of maintenance message as the SLTMs received on the link.
MTP restart provides an orderly process for bringing signaling links back into service after the system has been isolated and restarted. A greater preference is given to restoring the STP to network service in an orderly fashion than to the speed of recovery. The time required is system dependent as shown:
- up to 64 LIMs—62 seconds (Link Alignment Delay)
- 64 - 127 LIMs—97 seconds
- 128 - 191 LIMs—132 seconds
- more than 191 LIMs—167 seconds
When two linksets are used as a combined linkset, each linkset should have the same slsci and asl8 values and the same slsocbit and islsrsb/slsrsb values.
Caution:
This is not enforced in the system and there is no warning mechanism if the values of these parameters are not the same for each linkset.The slsrsb parameter alone does not provide an even distribution of ITU-ISUP messages across all links within a linkset. The system uses all four bits of the SLS to determine the actual link to route messages. Because the static bit is simply rotated within the SLS, all possible values of the SLS field will still not be realized. The slsocbit parameter must also be used to provide an even distribution across all links within the linkset. If both parameters are used for a given linkset, the SLS field is processed in the following order:
- The SLS is modified using the Other CIC Bit option.
- The modified SLS is modified again using the Rotated SLS Bit option.
- The modified SLS is used by the existing linkset and link selection algorithms to select a link.
- The ISUP message is sent out of the link containing the original, unmodified SLS field.
To modify a secondary adjacent point code, sapc has to be first deleted, then added again.
A 24-bit ITU-N point code can be provisioned as an SAPC only if the APC is not already a 24-bit ITU-N point code.
Only one 24-bit ITU-N point code is allowed to be provisioned as an SAPC.
For a linkset containing either low speed CCS7ITU links if the APC is a 14-bit ITU-N point code, then a 24-bit ITU-N point code cannot be provisioned as an SAPC.
For a linkset containing either low speed CCS7ITU links, if the APC is a 24-bit ITU-N point code, then a 14-bit ITU-N point code cannot be provisioned as a SAPC.
For a linkset containing either low speed CCS7ITU links, if the APC is an ITU-I point code, then either a 24-bit ITU-N point code or a 14-bit ITU-N point code can be provisioned as an SAPC, but not both.
In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-) and the private and spare point code subtype prefix (ps-). All of the point code types support the private (internal) point code subtype prefix (p-).
The ITU National and ITU National China Adjacent Point Code types indicate the format that is used for changeover and changeover acknowledgement messages. China specifies a 16-bit field for data in changeover messages. The FSN occupies the first 12 bits. The trailing 4 bits are spare and are coded as 0. ITU uses a 24-bit field for data in the extended changeover/changeover acknowledgement messages. The FSN is encoded in the first 12 bits. The last 12 bits of the field are spare and are coded as zero.
The
randsls parameter value applies to
SCCP ITU-T messages and Class0 and ISUP ANSI messages when random SLS
generation is set to occur on a per linkset basis (the
randsls=perls parameter is specified
in the
chg-stpopts command).
If the randsls=perls parameter is specified, it is recommended that the linksets in a combined linkset be provisioned with the same randsls value to avoid undesired SLS distribution.
The tfatcabmlq=0 parameter specifies that the system broadcasts TFAs or TCAs only when half the links in the given linkset, or in the combined linkset in which it resides, become available.
A gateway linkset can be configured only from a SEAS terminal and not from a system terminal.
If the gwsa=off and gwsm=on parameters are specified, then all MSUs pass. Error messages are generated if an MSU matches a screening condition.
If the gwsa=on and gwsm=off parameters are specified, then MSUs are screened but messages are not generated.
If the gwsa=off and gwsm=on parameters are specified, then gateway screening is defined to be in the screen test mode. The gateway screening action in the stop action set specified by the actname parameter of the screen set is performed at the end of the screening process.
If the asl8=yes and the lst=a (a linkset containing access signaling links) parameters are specified, then the originator of the MSUs is generating 8-bit SLSs. For other linkset types, the asl8=yes parameter indicates that the adjacent STP is converting 5-bit SLSs to 8-bit SLSs. The SLS in MSUs received by the system on a linkset that has the asl8=yes parameter assigned is not converted. These MSUs are assumed to contain 8-bit SLSs.
If the gwsa=on, gwsm=on, and gwsd=off parameters are specified, then MSUs are screened, and error messages are generated if an MSU is passed when it should have been screened.
The chgmtp3opc parameter is applied on the outgoing linkset.
The chgmtp3opc parameter will be nullified if the sccpopts:mtprgtt option is set to fullgtt.
Incoming SLS Bit Rotation
If the ISLSBR feature is turned on, and Incoming SLS Bit Rotation is applied to an MSU, then the outgoing SLS bit rotation is not applied for that MSU. If the ISLSBR feature is turned off, or Incoming SLS Bit Rotation is not applied to an MSU, then the outgoing SLS bit rotation is applied for that MSU.
The valid ISLSRSB values are 1 – 4 for ITU linksets and 1 – 8 for ANSI linksets.
The randsls parameter is applied on incoming linksets for ANSI messages and on outgoing linksets for ITU messages.
Output
This example shows the output when the secondary point code is changed:
chg-ls:lsn=lsl:spc=100-23-48
rlghncxa03w 07-07-18 08:16:14 EST EAGLE 37.5.0
CAUTION: Linkset SPC has changed - verify remote node’s route.
Link set table is (114 of 1024) 1% full
CHG-LS: MASP A - COMPLTD
This example shows the output when GTT mode is changed to FLOBR CdPA:
chg-ls:lsn=ls3:gttmode=fcd
tekelecstp 09-04-12 13:34:33 EST EAGLE 41.0.0
Link set table is (5 of 1024) 1% full.
CHG-LS: MASP A - COMPLTD
;
Related Topics
chg-lsopts
Use this command to administer the thresholds for IPSG-M3UA linksets and to set SLS bit rotation for ANSI linksets.
Parameters
- lsn (mandatory)
- Linkset name. The name of the linkset. Each linkset name must be unique in the system.
- icnimap (optional)
- Incoming NI Map. The NI mapping for incoming MSUs on a linkset. The NI value in the incoming MSU is changed to the value specified by this parameter before processing the message.
- numslkalw (optional)
- Number of signaling links allowed. The IS-NR link count threshold required for an IPSG-M3UA linkset to transition from the Restricted or Prohibited state to the Allowed state.
Note:
When the number of IS-NR links in an IPSG-M3UA linkset transitions from a value less than numslkalw to a value equal to or greater than numslkalw, the linkset transitions to the allowed state.
- numslkproh (optional)
- Number of signaling links required to prohibit a linkset. The IS-NR link count threshold required for an IPSG-M3UA linkset to transition from the Restricted or Allowed state to the Prohibited state.
Note:
When the number of IS-NR links in an IPSG-M3UA linkset transitions from a value equal to or greater than numslkproh to a value less than numslkproh, the linkset transitions to the Prohibited state.
- numslkrstr (optional)
-
Number of signaling links required to restrict a linkset. The IS-NR link count threshold required for an IPSG-M3UA linkset to transition from the Allowed state to the Restricted state.
When the number of IS-NR links in an IPSG-M3UA linkset transitions from a value equal to or greater than numslkrstr to a value less than numslkrstr and greater than numslkproh, the linkset transitions from the Allowed state to the Restricted state. Transition from the Prohibited state to the Restricted state is not supported.
- ognimap (optional)
- Outgoing NI Map. The NI mapping for outgoing MSUs on a linkset. The NI value in the processed MSU is changed to the value specified by the ognimap parameter for that linkset before routing the message to the intended destination.
- pct (optional)
- Point Code and CIC Translation. This option specifies whether to apply PCT to the specified linkset.
Example
The following example changes the threshold value of the numslkproh parameter to 3 for an IPSG-M3UA linkset.chg-lsopts:lsn=lsm3ual:numslkproh=3
The following example sets the incoming and outgoing NI Mapping for a linkset.chg-lsopts:lsn=lsnimap1:icnimap=itun2ituns:ognimap=ituns2itun
The following example sets 8 bit incoming bit rotation for an ANSI link setchg-lsopts:lsn=lsl:rsls8=yes
chg-lsopts:lsn=ls111:pct=on
Dependencies
The value specified for the numslkproh parameter cannot be greater than the value specified for the numslkrstr parameter.
The value specified for the numslkrstr parameter cannot be greater than the value specified for the numslkalw parameter.
The value specified for the lsn parameter must indicate an IPSG-M3UA linkset before the numslkalw, numslkproh, and numslkrstr parameters can be specified.
The value specified for the numslkalw, numslkproh, or numslkrstr parameter cannot be greater than the number of links configured in the IPSG-M3UA linkset.
The ITU National and International Spare Point Code Support feature must be enabled before the icnimap and ognimap parameters can be specified.
The icnimap and ognimap parameters must be specified together in the command.
The NI mapping for incoming messages in a linkset must be compatible with the NI mapping for the outgoing messages.
Values for the icnimap and ognimap parameters other than none can be specified only for ITU-I and ITU-N APCs of the linkset.
An ANSI linkset must be specified by the lsn parameter before the rsls8=yes parameter can be specified.
The ISLSBR feature must be enabled before the rsls8 parameter can be specified.
A PCT quantity feature must be enabled before the pct parameter can be specified.
Notes
NI Mapping Parameter Compliance Rules
The values specified for the icnimap and ognimap parameters for a linkset must be compatible. Table 4-12 shows the relationship between the parameters for a linkset.
Table 4-12 NI Mapping Rules
| ICNIMAP | OGNIMAP |
|---|---|
|
ITUI2ITUIS |
ITUIS2ITUI |
|
ITUIS2ITUI |
ITUI2ITUIS |
|
ITUN2ITUNS |
ITUNS2ITUN |
|
ITUNS2ITUN |
ITUN2ITUNS |
|
NONE |
NONE |
If the rsls8=yes parameter is specified, then 8 bits of the Incoming ANSI SLS are used for the ISLSBR feature. If the rsls8=no parameter is specified, then 5 bits are used.
Table 4-13 summarizes the cases in which rotation is done on the Incoming ANSI SLS bits:
Table 4-13 Incoming SLS Bit Rotation for ANSI Linksets
| Number of Incoming SLS Bits | RSLS8 | Valid range of values of ISLSRSB | SLSCNV/SLSCI | If Incoming SLS bits are rotated or not |
|---|---|---|---|---|
|
5 |
No |
1-5 |
No |
Yes |
|
5 |
No |
1-5 |
Yes |
Yes ( Lower 5 bits) |
|
5 |
Yes |
1-8 |
No |
No |
|
5 |
Yes |
1-8 |
Yes |
Yes |
|
8 |
No |
1-5 |
Yes/No |
Yes (Lower 5 bits) |
|
8 |
Yes |
1-8 |
Yes/No |
Yes |
Output
chg-lsopts:lsn=ls1:rsls8=yes
tekelecstp 09-03-03 10:52:55 EST EAGLE 41.0.0
Command entered at terminal #4.
Link set table is (7 of 1024) 1% full.
CHG-LSOPTS: MASP A - COMPLTD
chg-m2pa-tset
Use this command to change M2PA timers in an M2PA timer set. The srcset and tset parameters can be used to copy from one timer set to another.
Note:
The M2PA RFC feature introduces 20 new timer sets. M2PA timer sets created prior to this feature become M2PA Draft 6 timer sets, which are used by the M2PA Draft 6 associations. M2PA RFC associations use the RFC timer sets.Parameters
Note:
All values specified for the timer parameters (t(X)) are in milliseconds.- srctset (optional)
-
The timer set to be copied into the timer set specified by the tset parameter. If this parameter is specified, no other timer values can be specified.
- t1 (optional)
- T1 timer. Alignment timer. The amount of time M2PA waits to receive a Link Status Alignment message from the peer.
- t3 (optional)
- T3 timer. Ready timer. The amount of time after proving that M2PA waits to receive a Link Status Ready message from the peer.
- t4e (optional)
- T4E timer. Emergency proving timer. The amount of time M2PA generates Link Status Proving messages during emergency proving.
- t4n (optional)
- T4N timer. Normal proving timer. The amount of time M2PA generates Link Status Proving messages during normal proving.
- t5 (optional)
- T5 timer. Busy rate timer. The amount of time between sending Link Status Busy messages while the link is in service.
- t6 (optional)
- T6 timer. Remote congestion timer. The amount of time that a congested link will remain in service.
- t7 (optional)
- T7 timer. Excessive acknowledgement delay timer. The maximum amount of time that can pass between transmission of a user data message and receipt of an acknowledgement for that message from the peer. If this timer expires, the link is taken out of service.
- t16 (optional)
- T16 timer. Proving rate timer. The amount of time between sending Link Status Proving messages while T2N or T2E is running.
Note:
The T16 value is given in microseconds.
- t17 (optional)
- T17 timer. Ready rate timer. The amount of time between sending Link Status Ready messages while T3 is running.
Example
chg-m2pa-tset:tset=1:t1=20000
chg-m2pa-tset:tset=1:t1=20000:ver=d6
chg-m2pa-tset:srctset=1:tset=2:ver=rfc
Dependencies
At least one optional parameter must be specified.
The srctset parameter and the tset parameter cannot specify the same timer set name.
The specified timer must be supported for the Draft 6 version of M2PA.
Either a timer value or the srctset parameter must be specified.
Timer value parameters and the SRCTSET parameter cannot be specified together.
Notes
None
Output
chg-m2pa-tset:tset=1:t1=20000:ver=d6
rlghncxa03w 06-01-18 08:16:14 EST EAGLE 34.3.0
CHG-M2PA-TSET: MASP A - COMPLTD
;
Related Topics
chg-map
Use this command to add or modify an entry in the Mated Application Part (MAP) table. A MAP table entry consists of a mate PC/SSN, its attributes, and an Alternate Routing Indicator Mate MRN Set and MRN point code.
Note:
A mate point code defines an adjacent signaling point, which is considered the mated signal transfer point (STP) to the system. See the Notes section for additional information on multiplicity modes.Note:
The GTT Load Sharing with Alternate Routing Indicator (GTT LS ARI) feature must be enabled before an Alternate RI Mate for a MAP Set can be provisioned.Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.Note:
The mrnset and mrnpc parameters indicate whether an Alternate RI Mate search is performed in the MRN table if all of the point code/subsystem number combinations provisioned in a given MAP Set are unavailable or congested.- pc (mandatory)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- pca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- pci (mandatory)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- pcn (mandatory)
- ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pcn24 (mandatory)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- pcn16 (mandatory)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
- eswt (optional)
- Entity set weight. The weight assigned to each PC/SSN in a weighted entity set.
Note:
This parameter cannot be specified when adding PC/SSNs to a weighted entity set or when modifying RC or weight values for an individual PC/SSN.
- force (optional)
- This parameter must be specified to modify the rc parameter and the srm, mrc, or wt parameter in the same command.
Modification of the srm, mrc, or wt parameter depends on the parameter's current multiplicity state, which depends on the RC value. Changing the rc parameter value can change the multiplicity state, which can cause the srm, mrc, or wt parameter value to become invalid.
- grp (optional)
- The concerned point code broadcast list (CSPC) group name. The CSPC is a group of point codes that should be notified of the subsystem status. A different CSPC group can be assigned to each mated PC/SSN. For ANSI, the EAGLE broadcasts SSP or SSA to the mate subsystem only if the mate’s point code is provisioned as part of the CSPC group to receive an SSP or SSA.
- grpwt (optional)
- Group weight. The weight assigned to each PC/SSN in a weighted RC group.
Note:
This parameter cannot be specified when adding PC/SSNs to a weighted entity set or when modifying RC or weight values for an individual PC/SSN.
- materc (optional)
- Mate relative cost. The RC assigned to the mate PC/SSN that is being added to the entity set. The system determines the multiplicity mode based on the RC values (rc and materc parameters) of the subsystem.
- mpc (optional)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- mpca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- Default:
- 000
- mpci (optional)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- mpcn (optional)
- ITU national point code in the format of a 5-digit ITU number (nnnnn). The prefix subfield indicates a spare point code (prefix-nnnnn).
- mpcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- mpcn16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
- mrc (optional)
- Message routing under congestion. This parameter specifies whether Class 0 messages to the specified PC/SSN are routed to the next preferred mode/subsystem when that PC/SSN is congested.
- mrnpc (optional)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- mrnpci (optional)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- mrnpcn (optional)
- ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- mrnpcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- mrnpcn16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
- mrnset (optional)
- Alternate RI Mate MRN Set ID. The MRN Set where the Alternate RI Mate search is performed.
- mwt (optional)
- Mate point code weight. The weight assigned to the PC/SSN that is being added to a weighted entity set.
- rc (optional)
- Relative cost. The RC assigned to a specified PC/SSN. The EAGLE determines the multiplicity mode based on the relative costs (the rc and materc parameters) of the subsystem.
- srm (optional)
- Subsystem routing messages. This parameter specifies whether subsystem routing messages (SBR, SNR) are transmitted between the mated applications.
This value can be provisioned in any of the multiplicity modes, but its value only affects traffic if the multiplicity mode is DOM or COM. See the Notes section for more information on multiplicity modes.
- sso (optional)
- Subsystem status option. This parameter specifies whether the PC/SSN initiates a subsystem test when a RESUME is received for the PC.
- thr (optional)
- Threshold. The in-service threshold assigned to each PC/SSN in a weighted entity set or RC group.
This parameter cannot be specified when adding PC/SSNs to a weighted entity set or RC group or when modifying RC or weight values for an individual PC/SSN.
If this parameter is not specified, a value of 1% is assigned to each weighted PC/SSN.
Example
This example enters 1 into the MAP table and adds it to the same group as 1. Because 1 already exists in the MAP table, the rc parameter is not used.
chg-map:pc=1-1-0:ssn=10:mpc=1-1-3:mssn=10:materc=40
This example enters 1 into the MAP table, and adds it to the same group as 1. Because 1 has a lower relative cost than 1, it is placed into the group in relative cost order.
chg-map:pc=1-1-0:ssn=10:mpc=1-1-2:mssn=10:materc=30
This example changes the relative cost for the specified PC/SSN pair:
chg-map:pc=1-1-0:ssn=10:rc=20
This example changes the concerned PC broadcast list group name for the specified PC/SSN pair:
chg-map:pc=1-1-0:ssn=10:grp=abc
This example changes the ITU-I spare point code entry s-1-12-2 and adds the spare mate point code entry s-2-23-3 in the map table:chg-map:pci=s-1-12-2:ssn=10:rc=10:mpci=s-2-23-3:mssn=20:materc=10
This example turns ON the SSO option for PC 1-1-0 and SSN 10.
chg-map:pc=1-1-0:ssn=10:sso=on
This example turns OFF the SSO option for PC 1-1-0 and SSN 10.
chg-map:pc=1-1-0:ssn=10:sso=off
This example does not change the current value of the SSO option for the primary or the mate.
chg-map:pc=1-1-0:ssn=10:rc=10
This example turns ON the SSO option for primary and mate.
chg-map:pc=1-1-0:ssn=10:mpc=3-3-3:mssn=2:sso=on
This example turns OFF the sso option for primary and mate.
chg-map:pc=1-1-0:ssn=10:mpc=4-4-4:mssn=2:sso=off
This example does not change the current value for the SSO option for the primary. The SSO option is turned OFF for the mate, because the mate is specified but the sso parameter is not specified (the default is OFF for the mate when the mate is specified).
chg-map:pc=1-1-0:ssn=10:mpc=5-5-5:mssn=2
This example changes the ITU-I spare s-1-12-2 entry and adds the spare mate point code s-2-23-3 entry in the map table.
chg-map:pci=s-1-12-2:ssn=10:rc=10:mpci=s-2-23-3:mssn=20:materc=10
This example adds a new PC/SSN 1 in the existing MAP set 362.chg-map:pc=1-1-1:ssn=10:mpc=1-1-3:mssn=10:materc=40:mapset=362
This example adds a new PC/SSN 1-1-3/15 to the same load-sharing group in the default MAP set to which 1-1-1/15 belongs.chg-map:pc=1-1-1:ssn=15:mpc=1-1-3:mssn=15:materc=40:mapset=dflt
This example changes the RC of 1-1-1/10 in existing MAP set 362 to 20.chg-map:pc=1-1-1:ssn=10:rc=20:mapset=362
This example changes a non-weighted shared or non-weighted combined entity set to a weighted shared or weighted combined entity set.chg-map:pc=1-1-1:ssn=10:eswt=30
This example changes a non-weighted shared or non-weighted combined entity set to a weighted shared or weighted combined entity set. The example also sets a threshold value and changes the weights of all of the PC/SSNs in the entity set.chg-map:pc=1-1-1:ssn=10:eswt=30:thr=50
This example changes a weighted shared or weighted combined entity set to a non-weighted shared or non-weighted combined entity set.chg-map:pc=1-1-1:ssn=10:eswt=none
This example assigns a weight value to each PC/SSN in an RC group within a weighted entity set.chg-map:pc=1-1-1:ssn=10:grpwt=20
This example assigns a threshold value to each PC/SSN in an RC group within a weighted entity set.chg-map:pc=1-1-1:ssn=10:thr=70
This example assigns weight and threshold values to each PC/SSN in an RC group within a weighted entity set.chg-map:pc=1-1-1:ssn=10:grpwt=20:thr=70
This example changes the weight of an existing PC/SSN in a weighted entity set.chg-map:pc=1-1-1:ssn=10:wt=20
This example changes the weight of PC/SSN 1 and adds PC/SSN 1-2-1/10 to an existing weighted entity set.chg-map:pc=1-1-1:ssn=10:wt=50:mpc=1-2-1:mssn=10:materc=20:mwt=30
This example adds PC/SSN 1-3-2/10 to an existing non-weighted entity set.chg-map:pc=1-1-1:ssn=10:mpc=1-3-2:mssn=10:materc=20:mwt=10
This example changes the RC value and turns on MRC of an existing PC/SSN in a weighted entity set.chg-map:pc=1-1-1:ssn=10:rc=30:mrc=yes:force=yes
This example changes the RC value and turns on SRM of an existing PC/SSN in a weighted entity set.chg-map:pc=1-1-1:ssn=10:rc=30:srm=yes:force=yes
This example changes the RC value and the weight of an existing PC/SSN in a weighted entity set.chg-map:pc=1-1-1:ssn=10:rc=30:wt=20:force=yes
This example changes the Alternate RI Mate (MRNSET and MRNPC) in an existing MAP set.
chg-map:mapset=362:pc=1-1-1:ssn=10:mrnset=1:mrnpc=1-1-2
Example for 16 bit PC:
chg-map:pcn16=1-1-1:ssn=10:rc=20:wt=30:mpcn16=1-2-3:mssn=10:materc=20:mwt=20:thr=40
Dependencies
At least one optional parameter must be specified.
The specified remote PC must exist in the MAP table.
The Spare Point Code Support feature must be enabled before an ITU-I or ITU-N spare point code can be specified.
The specified SSN must exist for the specified remote PC.
If a subsystem is configured for a subsystem number (SSN) value in the SS-APPL table, then the specified MAP table entry for that subsystem must be a valid point code type for that subsystem. The following point code types are not valid for the indicated subsystems:
- For the INP subsystem, the True Point code cannot be an ITU-I point code.
- For the AIQ, ATINPQ, VFLEX, and EIR subsystems, the True Point code cannot be an ITU-N24 point code.
The mate PC/SSN cannot be the same as the primary PC/SSN.
If the PC value is an ITU type (pci/pcn/pcn24/pcn16), the srm=yes parameter cannot be specified.
The apca and pcn24/pcn16 parameters cannot be specified for the same MAP set. The pci and pcn parameters cannot be specified for the same MAP set if the MAP set contains a true point code.
The ANSI/ITU SCCP Conversion feature must be enabled before the network type of the CPC broadcast group can be different from the network type of the point code.
The mated PC/SSN must not already exist in the MAP table.
The DPCs of the primary subsystem and the mate subsystem must be full PCs.
The Route table must be accessible.
The format of the pcn or mpcn parameter must match the format assigned with the npcfmti parameter of the chg-stpopts command.
If the mpc parameter is specified, the mssn and materc parameters must be specified.
A maximum of 128 mated applications is allowed per MAP set.
The sso parameter cannot be specified with a PC that is the system true PC.
A true PC can have only one mate.
A true PC cannot be routed to itself.
The RPC3 table must be accessible.
The Site Identification table must be accessible.
If the mssn or materc parameter is specified, the mpc parameter must be specified.
The PC must already exist in the CPC group.
The specified CSPC broadcast list group name must already exist.
If the mpc parameter is specified, then the mssn parameter must be specified.
The number of MPC Subsystem entries must not exceed the table capacity.
A maximum of 1024 unique remote point codes are allowed.
If a remote MPC is specified, then the remote MPC must exist in the Routing table.
If the Flexible GTT Load Sharing feature is not enabled, then the mapset parameter must not be specified. If the Flexible GTT Load Sharing feature is enabled, then the mapset parameter must be specified.
The specified MAP set must exist in the database.
The specified PC/SSN/MAP set must already be provisioned in the MAP table.
The EAGLE true PC can be provisioned only in the default MAP set.
The MAP table must be accessible.
The Weighted GTT Loadsharing feature must be turned on before the wt, mwt, eswt, grpwt, or thr parameters can be specified.
If the eswt, grpwt, or thr parameter is specified, the mpc parameter cannot be specified.
If the eswt, grpwt, and thr parameters are specified, the rc, wt, mrc, srm, sso, and grp parameters cannot be specified.
The eswt and grpwt parameters cannot be specified together in the command.
If the eswt=none parameter is specified, the thr parameter cannot be specified.
If the mwt parameter is specified, the mpc parameter must be specified.
The mpc parameter value must be a full point code.
If the mpc parameter is specified for a weighted entity set, the mwt parameter must be specified.
If the mpc parameter is specified for a non-weighted entity set, the mwt parameter cannot be specified.
The eswt=none parameter cannot be specified for a non-weighted entity set.
The grpwt and thr parameters cannot be specified for a non-weighted entity set.
If the chg-sid:pctype=ansi command is entered, a value of ni=000 cannot be specified.
If the chg-sid:pctype=ansi command is entered, and a value of ni=001 – 005 is specified, a value of nc=000 cannot be specified.
The mate point code in the command cannot exceed the maximum number of entries in the MAP table.
The MAP table contains the maximum number of possible entries for the specified True Point Code. Maximum entries for the ANSI, ITU-I, and ITU-N point codes are:
- ANSI—2 (ANS41 AIQ and LNP), 4 (ANSI41 AIQ, ATINPQ, INP, and V-FLEX)
- ITU-I—4 (ANSI41 AIQ, ATINPQ, EIR, and V-FLEX)
- ITU-N—5 (ANSI41 AIQ, ATINPQ, EIR, INP, and V-FLEX)
Note:
LNP is mutually exclusive with ATINPQ and V-FLEX, unless the Dual ExAP Config feature is enabled.The true point code in the entity set must be the primary PC/SSN for that entity set. The rc parameter value for the specified point code cannot be changed, and a new point code cannot be added that causes the true point code to no longer be the primary PC/SSN.
If the pc parameter value is a true point code, the subsystem must have a lower RC than all other mated subsystems in the RC group.
If the mpc parameter value is a true point code, the subsystem must have a lower RC than all other mated subsystems in the RC group.
The eswt, grpwt, and thr parameters cannot be specified for solitary or dominant entity sets.
The AINPQ, EIR, INP, or V-Flex feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpcn parameter can be a true point code.
The force=yes parameter must be specified before the rc parameter can be specified in the same command with the srm, mrc, or wt parameter.
The force parameter can be used only to specify the rc parameter and the srm, mrc, or wt parameter in the same command.
If the pcn or mpcn parameter is specified, then the format of the parameter must match the format dictated by the chg-stpopts:npcfmti command.
The values specified for the pc and mpc parameters cannot be associated with proxy point codes.
The EIR or V-Flex feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpci parameter can be a true point code.
The LNP, V-Flex, EIR, or INP feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpca parameter can be a true point code.The GTT LS ARI feature must be enabled before the mrnset and mrnpc parameters can be specified.
The value specified for the mrnpc parameter must be a full point code.
The value specified for the mrnset parameter must already exist in the MRN table.
The MRN table is corrupt or cannot be found.
The point codes and alternate RI Mate point codes must have compatible network types as shown:
- ITUI, ITU-N, ITU-I spare, ITU-N-spare—ITUI, ITU-N, ITU-I spare, ITU-N-spare
- ANSI—ANSI
- ITUN-24—ITUN-24
- ITUN-16---ITUN-16
The value specified for the mrnpc parameter must already exist in the specified MRN Set.
If the mrnset parameter is specified, then the mrnpc/mrnpca/mrnpci/mrnpcn/mrnpcn24/mrnpcn16 parameter must be specified.
If the eswt, grpwt, or thr parameter is specified, then the mrnpc parameter cannot be specified.
The mrnset parameter cannot be specified if the MAP Set specified by the mapset parameter contains a True Point Code.
The chg-map command will reject provisioning of local subsystem for ITUN16 SID, so that ITUN16 MSUs will not be forwarded to Local Subsystems.
Notes
When the ANSI/ITU SCCP Conversion feature is enabled, the Concerned Point Code (CSPC) Group’s network type can be of a different network than the mated application’s network type. For example, the mated application’s network type could be ANSI and the CSPC Group could be ITU or mixed with ANSI, ITU, and ITUN concerned point codes.
Multiplicity Modes
For the -map commands, an entity set consists of a group of PC/SSNs that are used for traffic distribution, and an RC group consists of PC/SSNs within an entity set that have the same RC. In loadsharing mode, an entity set contains 1 RC group. In combined loadsharing/dominant mode, an entity set can contain multiple loadsharing groups.
Note:
For dominant and combined loadsharing/dominant modes, the PC/SSN in the MAP table where traffic distribution initializes is determined by the result of GTT translation and is referred to as the preferred PC/SSN. The preferred PC/SSN may not be the lowest cost entry.The EAGLE supports the following multiplicity modes for nodes/subsystems:
- When a PC/SSN pair is not replicated, the pair is in solitary (SOL) mode. The subsystem acts as the only application, with no backup. If this subsystem fails, messages routed to it are discarded and SCCP management returns “Subsystem Unavailable” messages to the originator.
- A group of replicated PC/SSN pairs are in dominant (DOM) mode if each PC/SSN pair in the group has a unique RC. The preferred PC/SSN acts as the primary subsystem while the higher cost systems act as backups.
- A group of replicated PC/SSN pairs are in load sharing (SHR) mode if each PC/SSN pair in the group has the same RC. All messages are evenly distributed at the SCCP level to all nodes/subsystems in the group. If failure occurs, the non-affected subsystem assumes the load of its failed mate.
- The combined load sharing/dominant (COM) mode supports a combination of load sharing and dominant mode. A group of PC/SSN pairs are in COM mode when at least two of the PC/SSN pairs have the same RC and another node subsystem in the group has a different RC.
The sso parameter changes the initialization of the subsystem status (“prohibited” or “allowed”) for PC/SSN MAP entries. The system previously marked the subsystem status “allowed” (OFF) for each PC/SSN entry. The sso option marks the subsystem status “prohibited” for each entry that has sso=on. This causes the EAGLE to generate an SST to the remote PC when an MTP-RESUME is received. Upon reception of an SSA, the subsystem status is marked “allowed”.
In this command, only ITU-international and ITU national point codes support the spare point code subtype prefix (s-).
When the Flexible GTT Load Sharing feature is turned on, MAP Load-Sharing Sets are supported. Each MAP set is identified by a new mapset parameter.
When the Weighted GTT Loadsharing feature is turned on, weighted entity sets and RC groups are supported, and threshold values can be assigned to each PC/SSN in a weighted entity set.
Output
chg-map:pc=1-1-0:ssn=10:mpc=1-1-3:mssn=10:materc=40:mapset=362
tekelecstp 11-03-22 12:29:22 EST EAGLE 44.0.0
chg-map:pc=1-1-0:ssn=10:mpc=1-1-3:mssn=10:materc=40:mapset=362
Command entered at terminal #4.
CHG-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
CHG-MAP: MASP A – COMPLTD
;
chg-map:pc=1-1-1:ssn=100:mrc=no:srm=no
tekelecstp 11-03-22 12:29:22 EST EAGLE 44.0.0
chg-map:pc=1-1-1:ssn=100:mrc=no:srm=no
Command entered at terminal #4.
CHG-MAP: MASP A - MESSAGE: EXTENDED PROCESSING REQUIRED
CAUTION: THE VALUE OF SRM IS EFFECTIVE WHEN MULT IS COM OR DOM AND
THE VALUE OF MRC IS EFFECTIVE WHEN MULT IS DOM.
CHG-MAP: MASP A - COMPLTD
;
chg-mate-stp
Use this command to enter mate or self PC (point code) into the database.
Note:
This command is used to populate the mate STP table, and is used to route responses to queries generated by the EAGLE for SFAPP UC #3/4 back to the originating EAGLE if a member of a set of EAGLEs is forming a gateway. For messages to be routed properly, the table in each of the members of the set must have the same entries.Parameters
- pc (mandatory)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- pc/pca/pci/pcn/pcn24/pcn16 (mandatory)
- Point code.
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.
- pci (mandatory)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)
- pcn (mandatory)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id)
Example
This example adds a point code:
chg-mate-stp:pc=10-20-30
This example adds a 24-bit ITU-N secondary point code:
chg-mate-stp:pcn24=99-99-99
This example adds a spare ITU-N secondary point code:
chg-mate-stp:pcn=s-12345
This example adds a 16-bit ITU-N secondary point code:
chg-mate-stp:pcn16=121-5-10
Dependencies
Mate STP point code must be present in either destination table or SID table.
Point code already exist in mate STP table.
Point code entered must be in same network as other existing point codes.
Mate stp table is full.
Notes
- The command is rejected when the point code is in invalid format.
- The command is rejected when point code is of a different network than the existing point codes/code's network.
- The command is rejected when the stp_table is full, as in, there are 16 point codes in the table already.
- The command is rejected when the point code specified already exists in the table.
- The command is rejected when no DPC (destination point code) exists for the specified point code. To add a new point code in the STP table, either it should be in the SID table or it should exist in the destination point code table.
Output
chg-mate-stp:pci=3-3-1
Searching destination table on disk - please wait...
Searching route table on disk - please wait...
Command Accepted - Processing
tekelecstp 18-05-28 17:24:37 MST EAGLE 46.6.2.0.0-73.19.0
chg-mate-stp:pci=3-3-1
Command entered at terminal #2.
;
tekelecstp 18-05-28 17:24:38 MST EAGLE 46.6.2.0.0-73.19.0
CHG-MATE-STP: MASP B - COMPLTD
chg-meas
Use this command to change both the report and collecting status of the OAM based measurement subsystem.
Note:
After the Measurements Platform collection function has been enabled, the collect=on/off parameter controls only the output of reports to the UI. The parameter has no effect on enabling and disabling collection and report generation for the Measurements Platform. Report generation for the Measurements Platform is controlled by therept-ftp-meas and
chg-measopts commands.
Parameters
- collect (optional)
- Activates or deactivates the reporting of scheduled measurements to the UI when the E5-OAM Integrated Measurements feature is on. This parameter does not affect measurements collection and generation for the Measurements Platform. It only activates or deactivates the reporting of scheduled measurements to the UI for the Measurements Platform.
- gtwylnkset (optional)
- Activates or deactivates the scheduled GTWY measurement report for the linkset.
- gtwylsfltr (optional)
- Filters the linksets included in the GTWY report.
- Range:
-
- both
- Only gateway linksets are included in the report to the terminal and SEAS.
- stp
- Only gateway linksets are included in the report to the terminal. All defined linksets are included in the report to SEAS.
- seas
- All defined linksets are included in the report to the terminal. Only gateway linksets are included in the report to SEAS.
- none
- All defined linksets are included in the report to the terminal and SEAS
Example
chg-meas:collect=on
chg-meas:complink=on:complnkset=on:systottt=off:systotstp=off:collect=on
chg-meas:gtwylsfltr=both
Dependencies
At least one optional parameter must be specified.
If the 15 Minute Measurements and Measurements Platform
collection functions are provisioned (see the
chg-measopts command), then the
collect=on parameter cannot be
specified.
At least one SLK or SIP/DEIR connection must be configured before the collect=on parameter is specified.
If the Integrated Measurements feature is turned on and the link count exceeds 700 links, then the systotstp=on, systottt=on, complnkset=on, complink=on, gtwystp=on, or gtwylnkset=on parameter cannot be specified.
Beginning with Release 46.3, basic OAM measurements are not supported. To turn collect=on, either MCPM or integrated measurements should be enabled.
Notes
Activated scheduled reports print at serial ports
configured for traffic-related unsolicited messages (the
traf=yes parameter of the
chg-trm command).
When the Measurements Platform is not enabled, the daily maintenance scheduled reports are always allowed and cannot be inhibited.
Maintenance Guide provides detailed information on measurements and measurement reports.
Output
chg-meas:complink=on:complnkset=on:systottt=off:systotstp=off:collect=on
rlghncxa03w 04-01-18 17:02:57 EST EAGLE 31.3.0
CHG-MEAS: MASP A - COMPLTD
;
Related Topics
chg-measopts
Use this command to:
- turn on the collection function for Integrated Measurements and Measurements Platform,
- turn the collection function for 15 Minute Measurements on or off
- turn on and off the unchannelized link label for high-speed MTP2 links
- turn the CLLI-based file name option for measurements reports files on or off
- activate or de-activate automatic generation and FTP transfer of scheduled measurements reports to the FTP server
Note:
After the Measurements Platform or Integrated Measurements collection function has been enabled, it cannot be disabled with this command.Caution:
Do not execute thechg-measopts:platformenable=on or
chg-measopts:oamhcmeas=on command near
a collection starting boundary. The best times for executing these commands are
xx07, xx17, xx37 and xx47, where
xx is any hour,
from 00-23.
Parameters
Note:
As of Release 45.0, the all, avldlink, avllink, avlstplan, cllibasedname, collect15min, complink, complnkset, compsctpasoc, compsctpcard, compua, gtwylnkset, gtwylsdestni, gtwylsonismt, gtwylsorigni, gtwyorigni, gtwyorigninc, gtwystp, nmlink, nmlnkset, nmstp, systotstp, systotstplan, systottt, systotsip and systotsfthrot parameters can be set using the individual parameters or as options for the on and off parameters.Note:
The options for the on and off parameters are described in the Notes section.- all (optional)
- Activates or deactivates the automatic generation
and FTP transfer of all scheduled measurements reports.
Note:
The all parameter does not change the setting of the platformenable, cllibasedname, collect15min, unchlinklabel, and oamhcmeas parameters.
- avldlink (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled daily availability measurement report for links.
- avllink (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled hourly availability measurement report for links.
- complink (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled component measurement report for links.
- complnkset (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled component measurement report for linksets.
- compsctpasoc (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled component measurement report for per association SCTP data.
- compsctpcard (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled component measurement report for per card SCTP data.
- compua (optional)
- Activates or deactivates the automatic generation and FTP transfer of the scheduled component measurement report for M3UA and SUA application server/association pairs.
- gtwylnkset (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY measurement report for linksets.
- gtwylsdestni (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY link set measurement report for destination NI
- gtwylsonismt (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY linkset measurement report for ISUP message type per linkset per originating NI
- gtwylsorigni (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY link set measurement report for originating NI
- gtwyorigni (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY link measurement report for originating NI.
- gtwyorigninc (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY link measurement report for originating NI and NC.
- gtwystp (optional)
- Activates or deactivates the automatic generation and FTP transfer of scheduled GTWY measurement report for STP.
- nmlink (optional)
- Activates or deactivates automatic generation and FTP transfer of the scheduled network management measurement report for links.
- nmlnkset (optional)
- Activates or deactivates automatic generation and FTP transfer of the scheduled network management measurement report for link sets.
- nmstp (optional)
- Activates or deactivates automatic generation and FTP transfer of scheduled network management measurement report for STP.
- oamhcmeas (optional)
- Turns on the Integrated Measurements collection
function on the E5-OAM card.
This function cannot be turned off after it has been turned on.
- off (optional)
- This parameter turns off the specified options. Up to 8 comma-separated unique options can be specified.
- on (optional)
- This parameter turns on the specified options. Up
to 8 comma-separated unique options can be specified.
- Range:
-
- all
- avldlink
- avllink
- avlstplan
- cllibasedname
- collect15min
- complink
- complnkset
- compsctpasoc
- compsctpcard
- compua
- gtwylnkset
- gtwylsdestni
- gtwylsonismt
- gtwylsorigni
- gtwyorigni
- gtwyorigninc
- gtwystp
- nmlink
- nmlnkset
- nmstp
- oamhcmeas
- platformenable
- systotidpr
- systotsfthrot
- systotsip
- systotstp
- systotstplan
- systottt
- unchlinklabel
- platformenable (optional)
- Turns on the Measurements Platform collection
function.
This parameter cannot be turned off after it has been turned on.
- systotsfthrot (optional)
- Activates or deactivates automatic generation and FTP transfer of scheduled measurement report for GTT SFTHROT Action.
- systotsip (optional)
- Activates or deactivates automatic generation and FTP transfer of scheduled measurement report for SIP system totals.
- systotstp (optional)
- Activates or deactivates automatic generation and FTP transfer of scheduled measurement report for STP system totals.
Example
chg-measopts:platformenable=on
chg-measopts:platformenable=on:complink=on: complnkset=on:systottt=off:systotstp=off
chg-measopts:on=complink,complnkset,systottt,systotidpr: off=gtwylsonismt,compua,nmlink,nmstp
chg-measopts:systotsip=on
chg-measopts:systotsfthrot=on
Dependencies
The Measurements Platform feature must be turned on before the platformenable=on parameter can be specified.
An MCPM card must be in the IS-ANR Restrict state before the Measurements Platform collection option can be enabled.
The 15 Minute Measurements feature must enabled and turned on before the 15 Minute Measurements collection option can be turned on.
The platformenable=on or oamhcmeas=on parameter must be specified before the cllibasedname=on parameter can be specified.
This command is not allowed while in upgrade mode.
Half-hour collection and report processing cannot be in progress when collect15min=on is specified.
Quarter-hour collection and report processing cannot be in progress when collect15min=off is specified.
At least one SLK or SIP/DEIR connection must be configured, before the platformenable=on or oamhcmeas=on parameter is specified.
The oamhcmeas or platformenable parameter cannot be specified if an OAM/OAMHC to MCP or MCP to OAMHC transition is in progress.
The Integrated Measurements feature must be turned on before the oamhcmeas=on parameter can be specified.
The Integrated Measurements or Measurements Platform feature must be turned on before this command can be entered.
The platformenable and oamhcmeas parameters cannot be specified together in the command.
The same option cannot be specified for the on and off parameters in the same command.
Parameters cannot be specified individually and as options for the on or off parameter in the same command.
At least one GTT Action - SFTHROT must be provisioned before the systotsfthrot=on parameter is specified.
Notes
Activated scheduled reports are generated and transferred to the customer’s FTP server.
The
rept-ftp-meas command can be used to
manually generate and transfer one report at a time as needed.
The primary application of the
set-time command is for Daylight
Savings Time changes, setting the time forward or backward 1 hour. To reduce
effects of
set-time changes on measurements, the
time change should be done within the first 15 minutes of any hour.
The Maintenance Guide provides detailed information on measurements and measurement reports.
CLLI-Based Measurements Report File Name
When the CLLI-based file name option (cllibasedname) is turned on, the CLLI is added to the measurements report file name, and the year is removed from the file name to ensure that the file name is equal to or fewer than 39 characters.
15 Minute Measurements
When the SEAS feature is turned on and 15 Minute Measurements collection is turned from off to on with the collect15min=on parameter, the message "Disabling SEAS Measurements..." is displayed at the UI.
When the SEAS feature is turned on and 15 Minute Measurements collection is running (collect15min=on), EAGLE measurements output to the SEAS interface is disabled.
When the SEAS feature is turned on and 15 Minute Measurements collection is turned from on to off with the collect15min=off parameter, EAGLE measurements output to the SEAS interface is enabled again.
Note:
If SEAS reporting is turned on, for the 24 hours after the 15 Minute Measurements option is turned from on to off, 30-minute demand SEAS reports for time periods prior to the option status change will contain only 15 minutes of data, and SEAS will not support reporting at the xx15 and xx45 times.Some quarter-hour measurements data might not be available for 24 hours after turning 15 Minute Measurements collection on. This condition exists for quarter-hour intervals for which 15 Minute Measurements collection has not yet occurred. Data that was collected on a 30-minute basis is available for reporting for up to 24 hours after it is collected. After the 15 Minute Measurements collection option is turned on, this data remains available on a half-hour basis (xx00 and xx30) but is not available on a quarter-hour basis (xx15 and xx45) because no data was collected on the quarter hours. After the 15 Minute Measurements collection option has been turned on for 24 hours, all 15-minute measurements data is available on a quarter-hour basis (xx00, xx15, xx30, and xx45).
In addition, full 30-minute data coverage will not be available until 24 hours after turning off the 15 Minute Measurements collection option. Reports for specific periods will always contain the amount of data collected for that period.
The action of turning 15-minute measurements feature
control status on using the
chg-ctrl-feat command also has an
impact on the generation of measurements reports for
period=active. Specifically, if the
feature control status of 15-minute measurements is turned on and a report is
requested for the active interval prior to the next scheduled measurements
collection (based on the current 15-minute measurements status), the starting
time for the period shown in the report will be incorrect. As soon as the next
scheduled collection occurs, active reports will show the correct starting
time. For example, if 15-minute feature control status is turned on with the
chg-ctrl-feat command at 13:03, and
the 15-minute measurements collection option is turned on using the
chg-measopts command at 13:05, and a
comp-link report for
period=active is requested at 13:10,
that report will contain an incorrect interval start time. If the same report
is requested at 13:20, the start time shown in the report will be correct,
because a collection occurred at 13:15.
A similar limitation exists for period=last. If the feature control status of 15-minute measurements is turned on and a report is requested for the last interval prior to the next scheduled measurements collection (based on the current 15-minute measurements status), the start and end times for the period shown in the report will be incorrect. The data presented in the report will correspond to the start and end times. As soon as the next scheduled collection occurs, then period=last reports will show the correct start and end times and the corresponding data for that interval. To generate measurements from the last collected interval before the first collection with feature control status on, a period=specific report will need to be entered. In the example given in the previous paragraph, the first report requested at 13:10 would not give the last interval, but the data given would correspond to the interval shown in the report. The second report requested at 13:20 would show correct start and end times and the data would correspond to the interval.
If the 15 Minute Measurements collection option is turned from on to off in the first 15 minutes of a half-hour (xx00-xx15 or xx30-xx45) and a demand report is requested in the second 15 minutes of a half-hour (xx15-xx30 or xx45-xx60) for period=last or period not specified, the report that is displayed will be the last 15-minute interval (xx00-xx15 or xx30-xx45), not the last collected 15-minute interval (xx45-xx00 or xx15-xx30). Collection did not occur during this 15-minute period, and the message “Measurements data not current” will be displayed. To report the last collected 15-minute interval, period=specific must be specified in the command with the correct qh/hh value.
The time interval in each measurements report shows which collection option was on when the measurements were collected. (This might not be the option that is currently on if the option was changed in the last 24 hours).
- xx00-xx15—None. 15 minutes of data will be collected for the quarter-hour xx15.
- xx15-xx30—The xx15 interval will contain no data. The xx30 interval will contain 30 minutes of data.
- xx30-xx45—None. 15 minutes of data will be collected for the quarter-hour xx15.
- xx45-xx00—The xx45 interval will contain no data. The xx00 interval will contain 30 minutes of data.
on/off options
- all —Allows automatic generation and FTP transfer of all scheduled measurements reports. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This parameter does not change the setting of the platformenable, cllibasedname, collect15min, unchlinklabel, and oamhcmeas parameters. This option has a default of OFF
- avldlink —Allows automatic generation and FTP transfer of the scheduled daily availability measurement report for links. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- avllink —Allows automatic generation and FTP transfer of the scheduled hourly availability measurement report for links. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- avlstplan —Allows automatic generation and FTP transfer of the scheduled hourly availability measurement report for STPLAN. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- cllibasedname —CLLI-based measurements report file name option. This option has a default of OFF.
- collect15min —15 Minute Measurements collection function. This option has a default of OFF.
- complink —Allows automatic generation and FTP transfer of the scheduled component measurement report for links. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- complnkset —Allows automatic generation and FTP transfer of the scheduled component measurement report for linksets. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- compsctpasoc —Allows automatic generation and FTP transfer of the scheduled component measurement report for per association SCTP data. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- compsctpcard —Allows automatic generation and FTP transfer of the scheduled component measurement report for per card SCTP data. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- compua —Allows automatic generation and FTP transfer of the scheduled component measurement report for M3UA and SUA application server/association pairs. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwylnkset —Allows automatic generation and FTP transfer of scheduled GTWY measurement report for linksets. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwylsdestni —Allows automatic generation and FTP transfer of scheduled GTWY link set measurement report for destination NI. If the 15 Minute Measurements feature is turned on and the, collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwylsonismt —Allows automatic generation and FTP transfer of scheduled GTWY linkset measurement report for ISUP message type per linkset per originating NI. If the 15 Minute Measurements feature is turned on and the, collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwylsorigni —Allows automatic generation and FTP transfer of scheduled GTWY link set measurement report for originating NI. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwyorigni —Allows automatic generation and FTP transfer of scheduled GTWY link measurement report for originating NI. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwyorigninc —Allows automatic generation and FTP transfer of scheduled GTWY link measurement report for originating NI and NC. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- gtwystp —Allows automatic generation and FTP transfer of scheduled GTWY measurement report for STP. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- nmlink —Allows automatic generation and FTP transfer of the scheduled network management measurement report for links. This option has a default of OFF.
- nmlnkset —Allows automatic generation and FTP transfer of the scheduled network management measurement report for link sets. This option has a default of OFF.
- nmstp —Allows automatic generation and FTP transfer of scheduled network management measurement report for STP. This option has a default of OFF.
- oamhcmeas —Turns ON the Integrated Measurements collection function on the E5-OAM card. This option cannot be turned OFF.
- platformenable —Turns ON the Measurements Platform collection function. This option cannot be turned OFF.
- systotidpr —Allows scheduled reports for IDPR Measurement Pegs on FTP to be generated every 30 minutes. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- systotsfthrot — Allows automatic generation and FTP transfer of scheduled measurement report for GTT SFTHROT actions system totals. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- systotsip — Allows automatic generation and FTP transfer of scheduled measurement report for SIP system totals. If the 15 Minute Measurements feature is turned on and the collect 15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- systotstp —Allows automatic generation and FTP transfer of scheduled measurement report for STP system totals. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- systotstplan —Allows automatic generation and FTP transfer of the scheduled measurement report for the STPLAN feature system totals. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- systottt —Allows automatic generation and FTP transfer of scheduled measurement report for translation type system totals. If the 15 Minute Measurements feature is turned on and the collect15min parameter is specified, then scheduled reports on FTP can be generated every 15 minutes. This option has a default of OFF.
- unchlinklabel —Turns ON/OFF a link label that identifies unchannelized (high-speed) MTP2 links. This option has a default of OFF.
Output
chg-measopts:platformenable=on:complink=on:complnkset=on:systottt=off:systotstp=off
tekelecstp 08-06-01 14:31:25 EST EAGLE 44.0.0
CHG-MEASOPTS: MASP A - COMPLTD
;
chg-measopts:on=systotidpr,systottt,complnkset,complink:off=avldlink,avllink,avlstplan
tekelecstp 10-12-01 12:15:25 EST EAGLE 44.0.0
CHG-MEASOPTS: MASP A – COMPLTD
;
chg-measopts:systotsip=on
tekelecstp 12-07-26 14:41:09 EST EAGLE 45.0.0
chg-measopts:systotsip=on
Command entered at terminal #4.
CHG-MEASOPTS: MASP A - COMPLTD
; chg-measopts:systotsfthrot=on
tekelecstp 15-08-26 14:41:09 EST EAGLE 46.3.0
chg-measopts:systotsfthrot=on
Command entered at terminal #4.
CHG-MEASOPTS: MASP A - COMPLTD
;
chg-mrn
Use this command to add new point codes, modify existing point codes and relative costs, and add or modify Alternate RI Mate data in the Mated Relay Node (MRN) table. The Intermediate GTT Load-Sharing (IGTTLS) feature must be on to enter this command. The GTT Load Sharing with Alternate Routing Indicator Feature (GTT LS ARI) must be enabled to provision an Alternate RI Mate.
If the IGTTLS feature is on, and the Flexible GTT Load Sharing feature (FGTTLS) is enabled, then entries are added to or changed in existing MRN sets in the MRN table.
If the IGTTLS feature is on, and the FGTTLS feature is not enabled, then the MRN table can contain a maximum of 3000 entries. If both the IGTTLS and FGTTLS features are on, then the MRN table can contain a maximum of 6000 entries.
Caution:
If any entries are provisioned in the SCCP-SERV table, the maximum number of entries that the MRN table can contain is reduced by that amount. Enter thertrv-sccp-serv command to see if entries exist in the SCCP-SERV table. See the Notes section for additional information on multiplicity modes.
Parameters
Note:
See Point Code Formats and Conversion for a detailed description of point code formats, rules for specification, and examples.Note:
The mapset, mappc, and mapssn parameters indicate whether an Alternate RI Mate search is performed in the MAP table if all PCs provisioned in a given MRN Set are unavailable or congested.- pc (mandatory)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- pca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- pci (mandatory)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- pcn (mandatory)
- ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- pcn24 (mandatory)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- pcn16 (mandatory)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
- eswt (optional)
- Entity set weight. The weight assigned to each PC in a weighted entity set.
Note:
This parameter cannot be specified when adding PCs to a weighted entity set or when modifying RC or weight values for an individual PC.
- force (optional)
- This parameter must be specified to modify the rc, rc1, rc2, rc3, or rc4 parameter and the wt, wt1, wt2, wt3, or wt4 parameter in the same command.
Modification of the wt, wt1, wt2, wt3, or wt4 parameters depends on the parameter's current multiplicity state, which depends on the RC value. Changing the rc parameter value can change the multiplicity state, which can then cause any of the weight parameter values to become invalid.
- grpwt (optional)
- Group weight. The weight assigned to each PC in a weighted RC group.
Note:
This parameter cannot be specified when adding PCs to a weighted entity set or when modifying RC or weight values for an individual PC.
- mappc (optional)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- mappca
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.
- Default:
- 000
- mappci (optional)
- ITU international point code with subfields zone-area-id. The prefix subfield indicates a spare point code (prefix-zone-area-id).
- mappcn (optional)
- ITU national point code in the format of a 5-digit number (nnnnn); or 2, 3, or 4 numbers (members) separated by dashes (m1-m2-m3-m4) as defined by the
chg-stpopts:npcfmtiflexible point code option. A group code must be specified when the ITUDUPPC feature is turned on (nnnnn-gc, m1-m2-m3-m4-gc). The prefix subfield indicates a spare point code (prefix-nnnnn, prefix-nnnnn-gc, prefix-m1-m2-m3-m4, prefix-m1-m2-m3-m4-gc).
- mappcn24 (optional)
- 24-bit ITU national point code with subfields main signaling area-sub signaling area-signaling point (msa-ssa-sp).
- mappcn16 (optional)
- 16-bit ITU national point code with subfields unit number-sub number area-main number area (un-sna-mna).
- mapset (optional)
- Alternate RI Mate MAP Set ID. The MAP set where Alternate Routing Indicator searches are performed.
- mapssn (optional)
- Alternate RI Mate Subsystem Number. The subsystem number used for the Alternate Routing Indicator search.
- pc1 (optional)
- ANSI point code with subfields network indicator-network cluster-network cluster member (ni-nc-ncm).
- Synonym:
- pca1
- Range:
- 000-255
Specify a valid value for each subfield of the point code, and separate the subfields with a dash (-).
When
chg-sid:pctype=ansiis specified, ni = 000 is not valid.When
chg-sid:pctype=ansiis specified, nc = 000 is not valid if ni = 001–005.When
chg-sid:pctype=ansiis specified, nc = 000 is valid if ni = 006–255.The point code 000-000-000 is not a valid point code.