1012 Command Line Interface
1012 Command Line Interface
www.taqua.com
Taqua
740 East Campbell Road, Suite 200 Richardson, TX 75081 Main Phone: (972) 692-1800 TAC Support: 1-866-792-0198 For software licensing information, e-mail Taqua Marketing at simplify@taqua.com. 2006, 2007, 2008, 2009 Taqua All rights reserved. T7000, dryIse, ISE, ISEHouse, OpenManager, and OM Server are trademarks of Taqua. All products, names and services are trademarks and registered trademarks of their respective companies.
Disclaimer of Taqua: Material contained in this document is subject to change without notice. The material herein is solely for information purposes and does not represent a commitment by Taqua, or its representatives. Taqua has prepared the information contained in this document solely for use by its employees, agents, and customers. Dissemination of this information and/or concepts to other parties is prohibited without the prior written consent of Taqua. In no event will Taqua be liable for any incidental or consequential damage in connection with the furnishing, performance or use of this material. Taqua reserves the right to revise this publication in accordance with formal change control procedures defined by Taqua.
990-1012-001
Table of Contents
Using CLI
CLI Commands Modified in Release 6.0.1 ...............................................1 CLI Commands Retired in Release 6.0.1 ..................................................2 Using CLI through the OM .........................................................................5 Using Generic CLI Commands ..................................................................6
CLI Examples ..................................................................................................... 13
Command Syntax ..................................................................................... 26 Using CLI Security .................................................................................... 27 Using CLI Remote Card Access ..............................................................28 Application Entities .................................................................................. 29
Application Domain Object .................................................................................. 29 OID ...................................................................................................................... 30
Alarms
Acknowledging Alarms ............................................................................51 Provisioning Alarms ................................................................................. 53 Querying Alarms ....................................................................................... 54
Events
Managing Events ...................................................................................... 57 Logging Events ......................................................................................... 58 Querying Events ....................................................................................... 60
Table of Contents
Queries
Generic CLI Queries ................................................................................. 63 General Switch Queries ........................................................................... 65 Database Queries ..................................................................................... 83 CDRs .......................................................................................................... 89 Substitution ............................................................................................... 92 Central Office ............................................................................................ 94 Protocols ................................................................................................... 96
MGCP.................................................................................................................. 96 SIP....................................................................................................................... 98 SS7.................................................................................................................... 105 GR-303/PRI ....................................................................................................... 113
FTRS ........................................................................................................ 120 Routing .................................................................................................... 122 In-Service Upgrades ............................................................................... 124 CALEA ..................................................................................................... 127
Provisioning
911 ............................................................................................................ 136 AIN ........................................................................................................... 138
Before Provisioning AIN .................................................................................... 138 Provisioning AIN ................................................................................................ 139
Carriers .................................................................................................... 196 Change Number Announcement ........................................................... 211 Equipment Provisioning ........................................................................ 213 FTRS ........................................................................................................ 223 Trunk Groups .......................................................................................... 233
ii
Table of Contents
CAS Trunk Groups ............................................................................................ 235 Clear Channel Trunk Groups ............................................................................ 252 Interface Groups................................................................................................ 258 Hunt Groups ...................................................................................................... 273 PRI Trunk Groups ............................................................................................. 286 IP Trunk Groups ................................................................................................ 307 SS7 Trunk Groups............................................................................................. 324
Rate Centers ........................................................................................... 410 Screen Lists ............................................................................................ 415 SIP ............................................................................................................ 418
Setting up an IP Network Interface.................................................................... 419 Setting up a Subscriber Access SIP Endpoint .................................................. 420 Setting up a Network Gateway SIP Endpoint .................................................... 421 Resolving Fully Qualified Domain Names ......................................................... 465
Tandem ANI Subscribers ....................................................................... 511 Route Lists .............................................................................................. 514 Subscribers ............................................................................................. 530
RcfInfo ............................................................................................................... 570
Table of Contents
iii
Maintenance
General Maintenance ............................................................................. 597 Call Processing Maintenance ................................................................ 610 Substitution Maintenance ...................................................................... 626 Trunk Group Maintenance ..................................................................... 627 Device Maintenance ............................................................................... 628 SS7 Maintenance .................................................................................... 638 ISUP Maintenance .................................................................................. 643 GR-303 Maintenance .............................................................................. 649 AIN Maintenance ..................................................................................... 654 Test Panel Maintenance ......................................................................... 656 In Service Upgrades ............................................................................... 658 Test Tone Maintenance ..........................................................................663 Automatic Number Announcement ...................................................... 665 SIP/MGCP/VoIP Maintenance ................................................................ 666
Performance Monitoring
Active Call Measurements ..................................................................... 669
DS1 Monitoring.................................................................................................. 671 Performance Monitoring Maintenance .............................................................. 672
Clock Cards
CC2 .......................................................................................................... 721
iv
Table of Contents
Appendix B: Protocols
Trunk Protocols ................................................................................................. 745 Other Protocols ................................................................................................. 748
HyperTerminal ........................................................................................768
Local Access ..................................................................................................... 768
Table of Contents
vi
Table of Contents
Using CLI
Tip
Print out pages in this chapter to use as cheat sheets/ memory aids.
You can use the commands in this guide by connecting to a T7000 using Telnet through the OM or ProComm. See Appendix C: Accessing the Switch on page 749, and Appendix D: Using Hyper-Terminal on page 815.
WARNING
Before running an existing script on a switch running a 6.0.1 load, the script should be inspected for the presence of these CLI commands and/or objects. If a modified command and/or object is found, be sure to edit the script and test any changes made.
NOTE: If you are upgrading from Release 5.0 or earlier, the CardConfiguration object must be the 1st object created in your script. See CardConfiguration on page 165 for details.
create MediaGateway now requires a bearerGrpKey parameter, see MediaGateway on page 371. SipEsgwEndpoint now requires a bearerGrpKey parameter, see SIP Emergency Services Gateway Endpoint on page 449. SipNgwEndpoint now requires a bearerGrpKey parameter, see SIP Network Gateway Endpoint on page 459. RcfInfo now requires a remoteDN parameter, see RcfInfo on page 570.
Using CLI
WARNING
Before running an existing 6.0 script on a 6.0.1 switch, the script should be inspected for the presence of the following CLI commands. Please delete any command found in the following list and replace it with its Release 6.0.1 equivalent before running the script.
Deleted CLI Commands in Release 6.0.1 If you used this command in 6.0
addRDTSpan addScreenList addToScreenList changeAuditList createCodecProfileList createProfile createRDT createSCCPNode createSCCPSubsys createTCAPService deleteProfile deleteCodecProfileList deleteRDT deleteSCCPNode deleteSCCPSubsys deleteTCAPService disableAudits dispSCCPNode dispSCCPSubsys dispTCAPService enableAudits insertCodecProfileToList
Using CLI
Deleted CLI Commands in Release 6.0.1 If you used this command in 6.0
insertInto MediaGateway modifyProfile nailUp queryCfbInfo queryCfdInfo queryCffInfo queryCfvInfo queryDbMgrs queryIGMiscOptions queryIGs queryOfcMiscOptions queryProfile queryRDTObject querySCFInfo queryScreenList querySdInfo queryShelfInfo querySCCPNode querySCCPSubsys queryTrkGrpMiscOptions
remAllFromScreenList remFromScreenList removeCodecProfileFromList removeRDTSpan setAuditPeriod setCommFailureShelfIds setCmtsMiscOption setEOCFlowThru setIGHdlcOption setIGMiscOption setInterfaceGroupTimer setNetRef setNextRDTSpan setOfcMiscOption setTCAPServiceTimer
deleteFrom Screen List deleteFrom Screen List deleteFrom CodecProfileList deleteFrom InterfaceGroup modify Shelf no replacement setMisc PacketCableCmts modify InterfaceGroup modify InterfaceGroup setMisc InterfaceGroup modify InterfaceGroup modify Shelf netref1OID modify Shelf netref2OID setNextRDTRoute setMisc OfficeParms modify TCAPServiceGTT modify TCAPServicePCSSN
Using CLI
Deleted CLI Commands in Release 6.0.1 If you used this command in 6.0
setTdmSpeed setTrunkGroupMiscOptions
unnail
destroy NailedUpCircuit
Using CLI
Action From the Network View of the OM click Network View. Right-click a T7000 graphic to which you want to connect. A pop-up menu appears.
Select Telnet. The Telnet client program appears. Telnet defaults to the last card with which it had a session. To connect to a new card: Select Connect > Remote System. In the Host Name field, enter the IP address of the new card to which to connect or select it from the drop-list.
Click Connect.
For other ways of establishing a remote CLI connection, see Appendix C: Accessing the Switch on page 749, and Appendix D: Using Hyper-Terminal on page 815.
Using CLI
a list of the Generic CLI commands, enter helpCLI a list of the database objects that a Generic CLI command operates on, as well as the general syntax for that command, enter the command name a commands parameters, enter the command and the dbObject help on a specific parameter, enter a question mark (?)in place of that parameter
command
action
usage
create <dbObject> <key> <required parms> [optional parms] destroy <dbObject> <key>
modifies an attribute of modify <dbObject> <key> <attrName> <value> an object modify <dbObject> <key> <attrName> <bitName> <value> sets a miscellaneous setMisc <objectType> <key> <miscOptionAttr> option for an object. <value> Use this command to set options added by In Service Upgrades (ISUs) displays an object query <dbObject> <key> [attribute]
setMisc
query
insertInto inserts an object into insertInto <dbObject> <key> <attrName> another objects nested <subKey> <subVal> collection insertInto <dbObject> <key> <attrName> <subKey> <subObjType> <requiredParms>
Tip
Use a subkey of 1 to insert an object at the start of a collection. Use a subkey of -1 to insert an object at the end of a collection.
deleteFrom deletes an object from deleteFrom <dbObject> <key> <attribute> another objects nested <subKey> collection
Using CLI
command
action
usage
lock
Tip
Lock a Trunk Group before destroying it, and lock a Trunk Group facility before deleting it from a Trunk Group.
unlock
places an object unlock <dbObject> <key> (device) in an in-service administrative state places an object (device) in an administrative state where it does not accept new service requests, but keeps performing current activities until done shutdown <dbObject> <key>
shutdown
status
Using CLI
However, when a string consists of two or more words, you must enclose the words in double quotes:
create Carrier "Sprint Canada" 6677 <done>
There are also times when you do not want to assign a string to an attribute. This is different from assigning an empty string (e.g., ) to the attribute. To show that you do not want a string assigned to the attribute, enter a period ., as the following example demonstrates:
create Subscriber You did not provide enough parameters to complete the command Usage: create Subscriber <key> <lastName> <firstName> [restrict] [subscribedServices] [interLATACarrier] [intraLATACarrier] [rateCenter] [facility] facility: [TDMFacility] [facilityOID] [GR303Facility] [RDTName] [crv] [MGCPFacility] [MGTermination] [SIPFacility] [IPTrunkGroup] [username] [password] create Subscriber 8176809148 Rufus Leaking 0 0 . . rc1 TDMFacility line-23 <done>
In the previous example, we did not assign an interLATACarrier or an intraLATACarrier to the subscriber.
Using CLI
Optional Parameters
Starting in Release 6.0, the create command supports optional parameters. If, after entering the last required parameter for an object, the remaining parameters are all optional, you can simply press the Enter key to complete the command. You may also enter one or more optional parameters, then press the Enter key to skip the remaining optional parameters. You can not, however, skip over one or more optional parameters. You can quickly identify the optional parameters of any object by entering
create object
where object is the name of the object to be created. The required parameters are enclosed in angle brackets, e.g., <requiredParameter>, and the optional parameters are enclosed in square brackets, e.g., [optionalParameter]. For example, to see which parameters are optional in the Subscriber object, enter the following command:
create Subscriber You did not provide enough parameters to complete the command Usage: create Subscriber <key> <lastName> <firstName> [restrict] [subscribedServices] [interLATACarrier] [intraLATACarrier] [rateCenter] [facility] facility: [TDMFacility] [facilityOID] [GR303Facility] [RDTName] [crv] [MGCPFacility] [MGTermination] [SIPFacility] [IPTrunkGroup] [username] [password]
Note that restrict, subscribedServices, interLATACarrier, intraLATACarrier, rateCenter and facility are all optional parameters. The following command creates a new Subscriber, and does not enter any of the optional parameters:
Using CLI
Limitiations
Generic CLI is unable to modify nested bitfields. A bitfield is an attribute where each binary digit (bit) is a separate attribute in its own right. A nested bitfield is a bitfield contained in one object that is itself contained in another object. The following examples illustrates the problem, but may make more sense after reading the Modify Example on page 14. The Carrier Object (seeCarriers on page 196) has a restrictions attribute that is a bitfield. The restrictions attribute is not nested, so it can be manipulated directly by Generic CLI. The following example:
queries the restrictions attribute. The NO_DA bit is set modifies the restrictions attribute, turning the NO_DA bit off modifies the restrictions attribute, turning the NO_PRE_SUB bit on query the restrictions attribute. The NO_PRE_SUB bit is set.
query Carrier WorldComm restrictions <52e4a34> restrictions........(BITFIELD) -> 40 .NO_DA modify Carrier WorldComm restrictions NO_DA 0 modify Carrier WorldComm restrictions NO_PRE_SUB 1 query Carrier WorldComm restrictions <52e4a34> restrictions........(BITFIELD) -> 8 .NO_PRE_SUB
Note that in the foregoing example, the modify command was able to refer to the attribute in the bitfield directly by name. Now consider the IP Trunk Group object (see IP Trunk Groups on page 307). The IP Trunk Group object contains an options attribute, which itself is a SipNgwEndpointOptions object. The options object contains a supportEarlyCutThrough attribute, which is a bitfield.
query IPTrunkGroup IPTG1 options <52e57cc> options....................<52d3180> <52d3180> SIPOptions plusOnePrepend....................FALSE doCallingNameDip..................FALSE screenDNChoice....................SCREEN_DN routeAdvance......................FALSE supportEarlyCutThrough............(BITFIELD) -> 0 sendCPN...........................CPN_DEFAULTDN sendUserForNoANI..................SEND_ANONYMOUS sendCarrierId.....................OFF routeOnRcvdCarrier................OUTBCRRIER_INBCARRIER callingPartyPresentationDisplay...SEND_ANONYMOUS revertToPrimaryFE.................TRUE bypassVmNotifyDeliveryCheck.......OFF
10
Using CLI
Because the supportEarlyCutThrough bitfield is contained in the options object, which is contained in the IP Trunk Group object, it is a nested bitfield. Generic CLI is unable to modify nested bitfield attributes by name, as the following example shows. First we use the modify command to tell us the names of the bitfield attributes:
modify IPTrunkGroup IPTG1 options supportEarlyCutThrough You did not provide enough parameters to complete the command <supportEarlyCutThrough> : Type is Bitfield. These options can be turned on or off Possible values: 1(1) = SIPtoSS7_EarlyCutThru 2(2) = SIPtoTDM_EarlyCutThru
We can not refer to the attribute by name, as the previous example just demonstrated. We can, however, refer to it by value: From the 1st modify example, the value of SIPtoSS7_EarlyCutThru is 1 Generic CLI will accept that value, as the following two commands demonstrates:
modify IPTrunkGroup IPTG1 options supportEarlyCutThrough 1 query IPTrunkGroup IPTG1 options <52e57cc> options....................<52d3180> <52d3180> SIPOptions plusOnePrepend....................FALSE doCallingNameDip..................FALSE screenDNChoice....................SCREEN_DN routeAdvance......................FALSE supportEarlyCutThrough............(BITFIELD) -> 1 .SIPtoSS7_EarlyCutThru sendCPN...........................CPN_DEFAULTDN sendUserForNoANI..................SEND_ANONYMOUS sendCarrierId.....................OFF routeOnRcvdCarrier................OUTBCRRIER_INBCARRIER callingPartyPresentationDisplay...SEND_ANONYMOUS revertToPrimaryFE.................TRUE bypassVmNotifyDeliveryCheck.......OFF
Note, however, when we modify a bitfield in this manner, we update the value of all of the bitfield attributes. The following example sets the SIPtoTDM_EarlyCutThru bit, but it also clears the SIPtoSS7_EarlyCutThru bit
Using CLI
11
modify IPTrunkGroup IPTG1 options supportEarlyCutThrough 2 query IPTrunkGroup IPTG1 options <52e57cc> options....................<52d3180> <52d3180> SIPOptions plusOnePrepend....................FALSE doCallingNameDip..................FALSE screenDNChoice....................SCREEN_DN routeAdvance......................FALSE supportEarlyCutThrough............(BITFIELD) -> 2 .SIPtoTDM_EarlyCutThru sendCPN...........................CPN_DEFAULTDN sendUserForNoANI..................SEND_ANONYMOUS sendCarrierId.....................OFF routeOnRcvdCarrier................OUTBCRRIER_INBCARRIER callingPartyPresentationDisplay...SEND_ANONYMOUS revertToPrimaryFE.................TRUE bypassVmNotifyDeliveryCheck.......OFF
In order to set both bits, we have to add the values (1 + 2) together, and set the result:
modify IPTrunkGroup IPTG1 options supportEarlyCutThrough 3 query IPTrunkGroup IPTG1 options <52e57cc> options....................<52d3180> <52d3180> SIPOptions plusOnePrepend....................FALSE doCallingNameDip..................FALSE screenDNChoice....................SCREEN_DN routeAdvance......................FALSE supportEarlyCutThrough............(BITFIELD) -> 3 .SIPtoSS7_EarlyCutThru .SIPtoTDM_EarlyCutThru sendCPN...........................CPN_DEFAULTDN sendUserForNoANI..................SEND_ANONYMOUS sendCarrierId.....................OFF routeOnRcvdCarrier................OUTBCRRIER_INBCARRIER callingPartyPresentationDisplay...SEND_ANONYMOUS revertToPrimaryFE.................TRUE bypassVmNotifyDeliveryCheck.......OFF
12
Using CLI
CLI Examples
Most of the CLI commands are self-explanatory, but the syntax for some of them can be a little complicated. Lets take a look at a few example commands to see how they work:
Create Example
Suppose we want to add a MediaGateway object. The first thing we can do is query the system to see what other MediaGateway objects already exist.
835> create MediaGateway Existing keys: mg1 mg2
If we continue the current naming convention, we will create mg3. We do not know at this point what the required parameters are, but Generic CLI knows, and will prompt us as we go along. Lets get started:
836> create MediaGateway mg3 You did not provide enough parameters to complete the command Usage: create MediaGateway <key> <profileName> <domain> <nearEndNiOid> <profileName> : Available keys in tMGCPProfileDbMgr: mgp
Lets try the command again, this time adding the key (mg3) and the profileName. Note that Generic CLI helpfully provided us with a list of all existing profileName keys:
839> create MediaGateway mg3 mgp You did not provide enough parameters to complete the command Usage: create MediaGateway <key> <profileName> <domain> <nearEndNiOid> <domain> : Type is String with length 1 to 64
Assume, for this example, that we know the domain (which will be dm5), but dont know the format of the nearEndOid parameter. Adding a question mark after the domain provides additional information about this variable:
842> create MediaGateway mg3 mgp dm5 ? Usage: create MediaGateway <key> <profileName> <domain> <nearEndNiOid> <nearEndNiOid> : Type is Valid OID
Now that we know the type of the newEndNiOid parameter, we can finish the command:
843> create MediaGateway mg3 mgp dm5 fe-0 <done>
Using CLI
13
Modify Example
For this example, we want to modify one of our MediaGatewayProfiles. We start by querying the system to see which profiles have already been created:
160> query MediaGatewayProfile ? <key> Existing keys: ac mgp
We see the mgp profile key from the create example, so lets work with that one.
161> modify MediaGatewayProfile mgp You did not provide enough parameters to complete the command Usage: modify <dbObject> <key> <attrName> <value> Usage: modify <dbObject> <key> <attrName> <bitName> <value> <attrName> : Available parameters: terminationPrefix requestedInfo quarantineHandling supportedPackages signalSupport DLCXOptions encodeDigitMap THIST retransmitTime keepAliveTime MAX1 MAX2 TMAX minRTOThresh maxRTOThresh responseAckParam enablePiggyback piggybackTime transLowWaterMark transHighWaterMark provRespTime responseRetransEnabled
Generic CLI returns a list of modifiable attributes. Lets assume we want to modify the DLCXOptions attribute. First, we would like to see the current value:
163> query MediaGatewayProfile mgp <2d2f488> MediaGatewayProfile key......................"mgp" terminationPrefix........"BWgw" requestedInfo............(BITFIELD) -> 400 .EVENT_STATES quarantineHandling.......LOOP supportedPackages........(BITFIELD) -> 7 .LINE .GENERIC .DTMF signalSupport............(BITFIELD) -> 0 DLCXOptions..............PREFIX_TERM_ID encodeDigitMap...........LOWERCASE THIST....................7530 (30000) retransmitTime...........c8 (200) keepAliveTime............ea60 (60000)
14
Using CLI
MAX1.....................7 (7) MAX2.....................b (11) TMAX.....................4e20 (20000) minRTOThresh.............3e8 (1000) 164> maxRTOThresh.............fa0 (4000) responseAckParam.........INCLUDE responseAckNum...........a (10) enablePiggyback..........DISABLE piggybackTime............c8 (200) transLowWaterMark........19 (25) transHighWaterMark.......32 (50) provRespTime.............c8 (200) responseRetransEnabled...YES
Generic CLI can tell us what other values the DLCXOption attribute can assume:
166> modify MediaGatewayProfile mgp DLCXOptions 167> Usage: modify <dbObject> <key> <attrName> <value> <DLCXOptions> : Type is Integer Possible values: 0 = NO_DLCX 1 = PREFIX_TERM_ID 2 = PREFIX_STAR 3 = STAR_ONLY
We can change an Integer attribute by either value or by name. First, modify the attribute by value:
167> modify MediaGatewayProfile mgp DLCXOptions 2 <done>
Note that, as in the next command, we can query a particular attribute directly:
168> query MediaGatewayProfile mgp DLCXOPtions <2d2f488> MediaGatewayProfile key......................"mgp" DLCXOptions..............PREFIX_STAR
Using CLI
15
Generic CLI knows the permissible values for each attribute, and will not allow an invalid value to be entered, as the following examples illustrate:
171> modify MediaGatewayProfile mgp DLCXOptions 5 *******************ERROR****************************** ****************************************************** ClassName+AttrName: MediaGatewayProfileDLCXOptions Value 5 Attribute not in value list. ******************************************************* ******************************************************* 172> modify MediaGatewayProfile mgp DLCXOptions STAR_ONE Usage: modify <dbObject> <key> <attrName> <value> <DLCXOptions> : Type is Integer Possible values: 0 = NO_DLCX 1 = PREFIX_TERM_ID 2 = PREFIX_STAR 3 = STAR_ONLY
The preceding commands worked with integer attributes, but not all attributes are integers. Some attributes are bitfields. A bitfield is a collection of up to 32 flags. Since a flag is either on or off, a bitfield is a way to store a lot of information in the switch without taking up a lot of memory. You can set or reset the value of one flag in a bitfield without disturbing the values of the other flags. Lets see how that works with our MediaGatewayProfile object. Recall that the requestedInfo attribute of the MediaGatewayProfile object is a bitfield:
63> query MediaGatewayProfile mgp <2d2f488> MediaGatewayProfile key......................"mgp" terminationPrefix........"BWgw" requestedInfo............(BITFIELD) -> 400 .EVENT_STATES
The current status of the requestedInfo bitfield is that one flag (the EVENT_STATUS flag) is on. The other flags in the bitfield are off.
16
Using CLI
Lets see what the other flags in the requestedInfo attribute are:
175> modify MediaGatewayProfile mgp requestedInfo Usage: modify <dbObject> <key> <attrName> <bitName> <value> <requestedInfo> : Type is Bitfield. These options can be turned on or off Possible values: 1 = REQUESTED_EVENTS 2 = DIGIT_MAP 4 = SIGNAL_REQUESTS 8 = REQUEST_IDENTIFIER 16 = NOTIFIED_ENTITY 32 = CONNECTION_IDENTIFIER 64 = DETECT_EVENTS 128 = OBSERVED_EVENTS 256 = VERSION_SUPPORTED 512 = REASON_CODE 1024 = EVENT_STATES 2048 = MAX_MGCP_DATAGRAM 4096 = CAPABILITIES
Since at this point we dont know the valid values to turn a bitmap attribute on or off, we can ask Generic CLI:
186> modify MediaGatewayProfile mgp requestedInfo DIGIT_MAP 4096 Valid values for bitfield specifiers are 0 and 1 Usage: modify <dbObject> <key> <attrName> <bitName> <value>
189> query MediaGatewayProfile mgp <2d2f488> MediaGatewayProfile key......................"mgp" terminationPrefix........"BWgw" requestedInfo............(BITFIELD) -> 402 .DIGIT_MAP .EVENT_STATES quarantineHandling.......LOOP
Using CLI
17
insertInto Example
The insertInto command is used to add an object or a value into a collection (such as a list object) that is part of another object. Consider the OfficeParms object. When it is created, it contains an list of countryCodes, as the following command shows:
query OfficeParms 123 countryCodes <69cd7fc> countryCodes..................<69d8e98> <69d8e98> CountryCodeList (3661836 items) -> 1 (1): 1 (1) 2 (2): 7 (7) 3 (3): 14 (20) 4 (4): 1b (27) 5 (5): 1e (30) 6 (6): 1f (31) 7 (7): 20 (32) 8 (8): 21 (33) 9 (9): 22 (34) a (10): 24 (36) b (11): 27 (39) [output snipped to conserve space] 51 (81): fa (250) 52 (82): fb (251) 53 (83): fc (252) 54 (84): fd (253) 55 (85): fe (254) 56 (86): ff (255) 57 (87): 101 (257) 58 (88): 102 (258) 59 (89): 103 (259) 5a (90): 104 (260) 5b (91): 105 (261) [rest of output snipped to conserve space]
18
Using CLI
Suppose we want to add the country code for Uganda (256) to the countryCodes list, but we are unsure how to go about it. Generic CLI knows the parameters, and will prompt us if we ask:
insertInto OfficeParms You did not provide enough parameters to complete the command Usage: insertInto <dbObject> <key> <attrName> <subKey> <subVal> Usage: insertInto <dbObject> <key> <attrName> <subKey> <subObjType> <requiredPams> Existing keys: 123
There is only one OfficeParms object in our switch, and its name is 123, so lets add that to our command:
insertInto OfficeParms 123 Usage: insertInto <dbObject> <key> <attrName> <subKey> <subVal> Usage: insertInto <dbObject> <key> <attrName> <subKey> <subObjType> <requiredPams> <attrName> : Available parameters: OSSInfoDigits countryCodes
OfficeParms has two collections, but we are dealing with countryCodes, so lets add that to our command:
insertInto OfficeParms 123 countryCodes Usage: insertInto <dbObject> <key> <attrName> <subK Usage: insertInto <dbObject> <key> <attrName> <subKey> <ms> <subKey> : Type is Integer <69d8e98> CountryCodeList (3661836 items) -> 1 (1): 1 (1) 2 (2): 7 (7) 3 (3): 14 (20) 4 (4): 1b (27) 5 (5): 1e (30) 6 (6): 1f (31) 7 (7): 20 (32) 8 (8): 21 (33) 9 (9): 22 (34) a (10): 24 (36) b (11): 27 (39) [output snipped to conserve space] 51 (81): fa (250) 52 (82): fb (251) 53 (83): fc (252) 54 (84): fd (253) 55 (85): fe (254) 56 (86): ff (255) 57 (87): 101 (257) 58 (88): 102 (258) 59 (89): 103 (259) 5a (90): 104 (260) 5b (91): 105 (261) [rest of output snipped to conserve space]
Using CLI
19
We need two additional parameters, subKey and subObjType. The first required parameter is subKey, and it is an integer. A list is keyed by the index of the item that is being added. We can add our item to the start of the list with a subKey of 1, or to the end of the list with a subkey of -1, or anywhere in the middle of the list with the appropriate value1. In this case, the countryCodes are already sorted, so maintenance will be easier if we insert the country code for Uganda (256) with a subkey of 87.
query OfficeParms 123 countryCodes <69cd7fc> countryCodes..................<69d8e98> <69d8e98> CountryCodeList (3661836 items) -> 1 (1): 1 (1) 2 (2): 7 (7) 3 (3): 14 (20) 4 (4): 1b (27) 5 (5): 1e (30) 6 (6): 1f (31) 7 (7): 20 (32) 8 (8): 21 (33) 9 (9): 22 (34) a (10): 24 (36) b (11): 27 (39) [output snipped to conserve space] 51 (81): fa (250) 52 (82): fb (251) 53 (83): fc (252) 54 (84): fd (253) 55 (85): fe (254) 56 (86): ff (255) 57 (87): 100 (256) 58 (88): 101 (257) 59 (89): 102 (258) 5a (90): 103 (259) 5b (91): 104 (260) [rest of output snipped to conserve space]
Note that the CountryCodeList now has a new entry at index 87, which corresponds to country code for Uganda that we added.
1.The subKey for a list is the index where you want to add the subValue. If you add a subValue to the middle of a list, the existing subValue at that index is not replaced, but simply moved back one position in the list.
20
Using CLI
deleteFrom example
This example continues from the previous example. Lets say want to delete country code 259:
query OfficeParms 123 countryCodes <69cd7fc> countryCodes..................<69d8e98> <69d8e98> CountryCodeList (3661836 items) -> 1 (1): 1 (1) 2 (2): 7 (7) 3 (3): 14 (20) 4 (4): 1b (27) 5 (5): 1e (30) 6 (6): 1f (31) 7 (7): 20 (32) 8 (8): 21 (33) 9 (9): 22 (34) a (10): 24 (36) b (11): 27 (39) [output snipped to conserve space] 51 (81): fa (250) 52 (82): fb (251) 53 (83): fc (252) 54 (84): fd (253) 55 (85): fe (254) 56 (86): ff (255) 57 (87): 100 (256) 58 (88): 101 (257) 59 (89): 102 (258) 5a (90): 103 (259) 5b (91): 104 (260) [rest of output snipped to conserve space]
Lets start with the basic command:
deleteFrom OfficeParms 123 Usage: deleteFrom <dbObject> <key> <attrName> <subKey> <attrName> : Available parameters: OSSInfoDigits countryCodes
It should come as no surprise that we will be deleting from the countryCodes list, so lets add that to our command:
Using CLI
21
deleteFrom OfficeParms 123 countryCodes Usage: deleteFrom <dbObject> <key> <attrName> <subKey> <subKey> : Type is Integer <69d8e98> CountryCodeList (3661836 items) -> 1 (1): 1 (1) 2 (2): 7 (7) 3 (3): 14 (20) 4 (4): 1b (27) 5 (5): 1e (30) 6 (6): 1f (31) 7 (7): 20 (32) 8 (8): 21 (33) 9 (9): 22 (34) a (10): 24 (36) b (11): 27 (39) [output snipped to conserve space] 51 (81): fa (250) 52 (82): fb (251) 53 (83): fc (252) 54 (84): fd (253) 55 (85): fe (254) 56 (86): ff (255) 57 (87): 100 (256) 58 (88): 101 (257) 59 (89): 102 (258) 5a (90): 103 (259) 5b (91): 104 (260) [rest of output snipped to conserve space]
Note that Generic CLI shows us the entries in the countryCodes list. Since we are dealing with a list, the subKey is the index of the item to be deleted. We want to delete country code 259, which is at index position 90 in the list, so the subKey is 90.
query OfficeParms 123 countryCodes <69cd7fc> countryCodes..................<69d8e98> <69d8e98> CountryCodeList (3661836 items) -> 1 (1): 1 (1)
22
Using CLI
2 (2): 7 (7) 3 (3): 14 (20) 4 (4): 1b (27) 5 (5): 1e (30) 6 (6): 1f (31) 7 (7): 20 (32) 8 (8): 21 (33) 9 (9): 22 (34) a (10): 24 (36) b (11): 27 (39) [output snipped to conserve space] 51 (81): fa (250) 52 (82): fb (251) 53 (83): fc (252) 54 (84): fd (253) 55 (85): fe (254) 56 (86): ff (255) 57 (87): 100 (256) 58 (88): 101 (257) 59 (89): 102 (258) 5a (90): 104 (260) 5b (91): 105 (261) [rest of output snipped to conserve space]
Note that deleting the item at index 90 in the list resulted in the remaining entries in the list moving up one position.
Using CLI
23
query example
This example illustrates how to query a particular attribute of an object. This can be useful when you are only interested in viewing a small part of a large object. Consider, for example, the OfficeParms object. Because it has a large CountryCodeList, a simple query will result in hundreds of lines of information. But if you were only interested in the ServiceCodes attribute, you could instruct Generic CLI to display only that portion of the of the OfficeParms object:
query OfficeParms taquaTexas serviceCodes <4fc7808> serviceCodes..................<4fc8c00> <4fc8c00> ServiceCodes Cfwd_On............."*72" Cfwd_Off............"*73" CfBusy_On..........."*90" CfBusy_Off.........."*91" CfNoAns_On.........."*92" CfNoAns_Off........."*93" Creject_On.........."*77" Creject_Off........."*87" Cblock_On..........."*60" Cblock_Off.........."*80" Caccept_On.........."*64" Caccept_Off........."*84" Ctrace.............."*57" CidBlock............"*67" CancelCw............"*70" CidUnBlock.........."*82" Creturn_On.........."*69" MsgRetrieve........."*83" Cffixed_On.........."*94" Cffixed_Off........."*95" PriorityCall_On....."*61" PriorityCall_Off...."*81" SpeedDial8.........."*74" SpeedDial30........."*75" SpeedDial8Review...."*78" SpeedDial30Review..."*79" SCFwd_On............"*63" SCFwd_Off..........."*85" Cback_On............"*66" Creturn_Off........."*89" Cback_Off..........."*86"
24
Using CLI
setMisc example
Previous to Release 6.0.1, different objects had individual commands to perform this function. However, all objects that support miscellaneous parameters have been enhanced to use this CLI command. Invoke this command without any parameters to get a usage string and a list of object that support the command:
setMisc Usage: setmisc <dbObject> <key> <miscOption> <value> This action can be performed on the following: CASTrunkGroup CLRTrunkGroup InterfaceGroup IPTrunkGroup MGCPTrunkGroup OfficeParms PacketCableCmts PCMMCmts PRITrunkGroup SS7TrunkGroup
The following example shows how to use the setMisc command for the OfficeParms object to discover what miscOption(s) can be set, and the permissible values for the option.
setMisc OfficeParms You did not provide enough parameters to complete the command Usage: setmisc <dbObject> <key> <miscOption> <value> Existing keys: taquaTexas setMisc OfficeParms taquaTexas You did not provide enough parameters to complete the command Usage: setmisc <dbObject> <key> <miscOption> <value> Available miscOptions: TestAttribute setMisc OfficeParms taquaTexas TestAttribute Usage: setmisc <dbObject> <key> <miscOption> <value> <TestAttribute> : Type is Integer Possible values: 0 = NO 1 = YES setMisc OfficeParms taquaTexas TestAttribute YES <done>
Using CLI
25
Command Syntax
Command Syntax
Syntax
Commands are case-sensitive. Do not use symbols. For example, do not enter AT&T as a carrier name. Instead, enter ATT.
Description required parameter, must be entered at the command line optional parameter, may be entered at the command line text string parameters that include spaces. For example, to enter a trunk group that is named Trunk Group 1, enter Trunk Group 1 in the command line comments made by the script writer. The T7000 does not process any text following # Typically, each command creates, runs, and terminates as a separate process. When %c appears at the end of a command, the command is called as a function in the same process as the shell.
< > [ ]
# %c
NOTE: %c is not recommended for Generic CLI commands. See Using Generic CLI Commands on page 6.
prompt
prompting text printed by the system when you need to enter additional information to complete a command
26
Using CLI
Login Process
Switch files have the permissions level of the user that created them. To modify a file you must have the same or higher permission level as the files creator.
Step
1 2 3 4 5
Action Modify the super user password. See passwd on page 47. Create level 1 administrator(s). See adduser on page 48. Create level 2 user(s). See adduser on page 48. Log off from the super user account. See <Ctrl> + D on page 46. Log in again as an Administrator. See _login on page 46.
Using CLI
27
NOTE: a second <Ctrl> + <D> will log you out of the session on the local card!
A Telnet session in ThinISE automatically reconnects if the card is reset. The session does not re-establish if power is removed from the card. To start a remote card access session:
Step
1 2
Action Connect to the T7000 host card. At the T7000 CLI prompt, type rsh <cardID> (cardID needs to be in hexadecimal format) to connect to the target card. Complete any diagnostics. Enter <Ctrl> + <D> to exit remote card access.
3 4
28
Using CLI
Application Entities
Application Entities
The T7000 application software makes heavy use of Application Domain Objects and Object Identifiers, both of which are explained in the following sections.
Line subscriber line interface circuit (SLIC), only available on LTCs Span T1 terminated to a Dallas Semiconductor DS2152 framer Trunk individual DS0 timeslot (1 of 24) on a T1 span DSP Digital Signal Processor Card T7000 front card TDM Time Division Multiplexed switch HDLC High-level Data Link Control, the OM186 communications controller or transwitch DS3 28 T1s, only available on BICs
Each ADO type has configurable attributes that are unique to that particular device type. If no prior configuration has taken place when a card is initially powered up, an ADO is created with a set of reasonable default values for each configurable device. Once modifications have been made to the default values, the new values reside in flash memory and subsequent power-up cycles do not require reconfiguration.
Using CLI
29
Application Entities
OID
An object identifier (OID) is an encoded 32-bit value that uniquely identifies each ADO in a T7000 network.
Tip
View the actual value of an OID using dispOID.
The CLI uses readable forms of the OID, specified by the dash-separated string "Device-Instance-Card-Shelf" where:
Device Card, Line, Trunk, Span, DSP, TDM, HDLC, DS3, FE Instance 0-based instance number of the device. For trunks instance is the timeslot. Card card number on which the device resides. Card numbers are 1based (1-20). Shelf T7000 number (1-255)
If you leave out OID fields, the T7000 uses a local default. If you do not enter a card OID, the default is the local card; unless the command is a card OID, the default is the instance value and the shelf defaults to local.
card LTC device line trunk span TIC TIC2 BIC PIC PIC2 trunk span trunk span DS3 FE FE values 0-31 0-47 0-1 0-383 0-15 0-479 0-19 0-2 0-1 0-2 example/explanation Line-2-1-22 is the 3rd line on card 1 shelf 22 24 timeslots x 2 DS1s, Trunk-33-2-1 is the 33rd trunk on the 2nd card in shelf 1 Span-0-1-4 is the 1st span on card 1 shelf 4 24 timeslots x 16 DS1s Span-2-1-8 is the 3rd span on card 1 shelf 8 24 timeslots x 20 DS1s Span-19-6-1 is the 20th span on card 6 shelf 1 ds3-0-15-12 is the first DS3 on card 15 shelf 12 fe-1-7-9 is the second Fast Ethernet Interface (FE) on card 7 shelf 9 fe-2-7-9 is the third Fast Ethernet Interface (FE) on card 7 shelf 9
30
Using CLI
Using Scripts
Using Scripts
Scripts are groups of related commands, put in order according to command dependencies.
CAUTION
To minimize provisioning and configuration errors Taqua recommends the following: 1.Use provisioning scripts instead of entering individual provisioning commands. 2. Test scripts using dryISE. dryISE simulates the operations of a real T7000, so you can test your scripts without affecting the call traffic on a T7000. 3. Test scripts using a non-production T7000 with the same software image, and preferably the same configuration.
Viewing Scripts
To view scripts in the software release, from Windows Explorer select the applicable hard drive, then Program Files > Taqua > OpenManager x.x.x > ocxapp > scripts (where x.x.x is the version of the OM). To view a scripts full text, double-click it.
Loading Scripts
To load a script from its location on the hard drive of the OM, enter its name from dryISE.
Using CLI
31
Using Scripts
a text file a list of commands executed at the command prompt when run by a shell process used to provision a switch
Complete the following steps for the DB Master card to run a configuration script on the switch.
Step
1
Action Enter queryDbMaster to determine which card on the switch is assigned the role of Database Master. Do the following on the DB Master card: Enter tftp to start tftp on the DB Master card. Enter device 6 to assign the local ramdisk device (6) for download storage. Enter get <filename> where <filename> is the script in the current working directory of the card used by ISEhouse. Enter quit to exit tftp. Enter ls 6 to display the contents of the ramdisk device and verify the script downloaded. Enter sh -e < 6/<filename> where <filename> is the name of the script to execute.
If the switch is not in an in-service state after executing the script, restore each card with restore card-<number> where <number> is the cards slot number. After each card has been restored, enter dbFlash ALL This saves the current switch configuration to a database file in flash memory.
32
Using CLI
Using dryISE
Using dryISE
dryISE (Imbedded System Engine) simulates operational switch situations and lets you to test your scripts before using them on a real T7000. The basis for dryISE is the T7000 operating system, ISE. dryISE provides the core functionality for process control (creating ISE tasks).
NOTE: The T7000 supports a subset of commands for its dryISE switch simulator.
Memory management Flash memory management IPC message services Timer services Object services Circular buffer services Global Map Command line shell
x-commands program symbols use $ command modifiers use % environment variables If the command interpreter cannot find a matching xcommand, it looks for a script in the working directory. The default file extension for scripts is .ocx.
Tip
If the script file uses .ocx, omit .ocx when specifying.
up and down arrow keys recall commands commands can be edited once recalled F1 re-displays the current line ESC clears the current line rrun on page 44 executes script files or shell commands on other cards
Using CLI
33
Using dryISE
dryISEs CLI %Rx executes script files or shell commands on other cards, use on any shell command line (x = another cards number).
ISEs CLI
34
Using CLI
Using dryISE
dryISE Commands
The following are simulation commands specific to dryISE:
<hexAddr>
auditTimers Current Time 91088763 Timer expiration time 91088903 (in 140 mSec) <2894a70> executeMemoryAudit (smrouting)0: 40000 1: 2945d48 2: 9dfeb0 3: 1388 Timer expiration time 91089091 (in 141 mSec) <2d82d90> executeUtime (smrouting)0: 40000 1: 2945d4c 2: 9dfeb0 3: 3e8 Timer expiration time 91089341 (in 391 mSec) <2d76570> updateLEDStatus (smrouting)0: 50000 (dispLEDStatus)1: 0 (broadcast)2: 0 3: 0 4: 7d0 3 Timer(s) active
Using CLI
35
Using dryISE
<fileName>
(where x.x.x is the version of the OM) > ocxapp > scripts.
CALL LTC1.ocx
NOTE: This command can only be executed from within a script.
NOTE: Do not confuse this command with the call command. The call command works on both dryISE and the switch, and should only be used by Taqua support.
cmdfileEchoOff cmdfileEchoOff
This command turns off command line echo of script files.
cmdfileEchoOn cmdfileEchoOn
This command turns on command line echo of script files.
36
Using CLI
Using dryISE
<objptrOrReal>
ConvertAddr 441d2e8 Real 441d2e8 is objPtr 80883a5d ConvertAddr 80883a5d ObjPtr 80883a5d is real 441d2e8 cs_config cs_config <line> [ORIG|TERM] [digits]
This command configures a line for call simulation as originator or terminator. The digits are required only for origination.
Syntax Description Object Identifier unique identifier that the T7000 uses to address each object or circuit. See OID on page 30. ORIG call originator TERM call terminator dialed digits, required only if you enter ORIG
Using CLI
37
Using dryISE
[line]
[line|ORIG|TERM]
[line|ORIG|TERM]
cs_reset Line-1-1-1
38
Using CLI
Using dryISE
<TimerId>
<msec> [line]
value (in millieseconds) to assign the timer Object Identifier unique identifier that the T7000 uses to address each object or circuit. See OID on page 30. Skip this parameter to set the value for all lines on the card.
[line|ORIG|TERM]
[digits]
Using CLI
39
Using dryISE
[line]
<line>
<digits>
OID
40
Using CLI
Using dryISE
<OID>
dumpTDM Line - 0x200 connections: Line - 0x201, Line - 0x201 connections: Line - 0x200, env
Tip
env should be the 1st command in any dryISE session.
<cardnum> [shelfnum]
[cardtype]
Using CLI
41
Using dryISE
Syntax
Description The port number of the channel of the IP address (16-bit number from 0-65535). The default port number is 3333. Also called the primaryPort.
[hostdport]
The following command sets up a TIC on card 1, shelf 10, with a port number 3333:
<line/trunk>
hu Line-1-1-1
NOTE: See oh on page 43, and also see pcall on page 43.
<span>
<farCard> <farSpan>
42
Using CLI
Using dryISE
querySpans
This command is a debug tool for use in dryISE. It identifies which spans (if any) have been configured on the local card, and shows the remote cards and spans to which they connect.
querySpans Configured spans: Span 0 is configured for remote card 2, span 0 Span 1 is configured for remote card 2, span 1
oh oh <lineOID>
This command signals off-hook on a line or trunk.
Syntax Description Object Identifier unique identifier that the T7000 uses to address each object or circuit. See OID on page 30.
<lineOID> oh Line-1-1-1
NOTE: Also See oh on page 43, and also see pcall on page 43.
<lineOID>
<digits>
Using CLI
43
Using dryISE
<span>
<fileName>
(where x.x.x is the version of the OM) > ocxapp > scripts.
<fileName>
(where x.x.x is the version of the OM) > ocxapp > scripts.
run LTC1.ocx
44
Using CLI
Using dryISE
sleep
Tip
This command is useful in scripts, to insure a delay between commands.
sleep <msec>
This command temporarily suspends execution.
Syntax Description
tdmd tdmd
This command starts the TDM controller.
release921
release921 <inst>
This command releases GR-303 EOC or TMC link connections on links using Link Access Protocol-D (LAPD).
Syntax inst Description the instance of the link. Range: 1 - maximum number. The maximum number varies by card type: BIC 338 ETIC 32 LTC 32 TIC 32 PIC 0
release921 1
To reconnect the link connections, see resync921 on page 651.
Using CLI
45
Using ISE
Using ISE
The T7000 Operating System is called ISE (Imbedded System Engine). ISE has a command shell, similar to UNIX, that processes system level commands. If the command shell does not recognize a command, it passes it on to the applications system.
ISE Commands
The following are simulation commands specific to dryISE:
Syntax
<name>
46
Using CLI
Using ISE
passwd passwd
This command changes the password of the active user. Type the old password, press <Enter>, and the new password prompt appears. Type the new password, press <Enter>, and the repeat password prompt appears. Re-type the new password, and press <Enter> to change the password.
NOTE: The password is only changed on the local card. Be sure to repeat this command on each card of the shelf!
Syntax
Description Type the current password of the user and press <Enter>. Type the new password for the user and press <Enter>. Type the new password a second time and press <Enter> to confirm the change.
passwd Enter old password: ***** Enter password: ***** Enter it again: *****
Using CLI
47
Using ISE
Syntax
<name>
[passwd] [shell]
whoami admin
48
Using CLI
Using ISE
users users
This command shows a list of users on the T7000. To use this command, you must be logged in as a level 1 or level 0 user. Enter users and press <Enter>. The data returned is the user name and permission level of all users defined on the T7000.
perm 0 1 2
Syntax
<name>
rmuser kdugas
dl dl <address> <count>
This command displays T7000 memory, one 32 bit word at a time The left most number is the starting address in memory. The next four sets of numbers are four 32 bit words of memory. To the right, enclosed in curly braces, is the ASCII representation of memory.
Syntax Description starting address to display. the number of bytes to display.
<address> <count>
dl 8b0320 20 008b0320: 29232840 632f3a76 6c2f7376 662f6374 008b0330: 662f6d73 682e6d73 3120762c 3220362e (9110336)<8b0340>
Using CLI
49
Using ISE
db db <address> <count>
This command displays T7000 memory, one 8 bit byte at a time. The left most number is the starting address in memory. The next sixteen sets of numbers are sixteen 8 bit bytes of memory. To the right is the ASCII representation of memory.
Syntax Description starting address to display. the number of bytes to display.
<address> <count>
now now
This command displays the current system date and time.
50
Using CLI
Alarms
2
Alarms tell you if there is a software or hardware problem on the T7000. Alarm definitions apply to all of the cards on the shelf. Each alarm trigger is a subset of all the T7000 events that can occur on the switch. For a full list of events, see the T7000 Maintenance and Troubleshooting Guide. The following commands do not resolve the problem causing the alarm, but do acknowledge the alarm. For information on how to resolve alarms, see the T7000 Maintenance and Troubleshooting Guide.
Acknowledging Alarms
ackAlarm
ackAlarm <Alarm Type> <CauseObjectID> <login> (card)
This command acknowledges an alarm. The command turns off the sound of audible alarms. Acknowledge an alarm to indicate that you know the alarm exists.
Syntax <Alarm Type> <CauseObjectID> Description The name of the activated alarm. See the T7000 Maintenance and Troubleshooting Guide. The object ID of the equipment causing the alarm. Object Identifierunique identifier that the T7000 uses to address each object or circuit. See OID on page 30. The user name to be associated with acknowledging the alarm. optional The card number that has the alarm condition.
<login> (card)
Alarms
51
Acknowledging Alarms
decommission
decommission <card>
This command indicates the card is out of service in the slot it is currently in and will not become active again unless rebooted or replaced. This command removes all outstanding alarms with an OID specifying that slot and removes the cardStatus alarm from the db master who is maintaining the list of system alarms.
Syntax <card> Description card number (1-20)
decommission 3
manualClear
manualClear <alarmType> <OID>
This command clears the specified alarm on the specified object. Syntax <alarmType> Description The type of alarm to clear The Object ID that currently has the alarm.
<OID>
52
Alarms
Provisioning Alarms
Provisioning Alarms
changeAlarmDefAttr
changeAlarmDefAttr <TriggeringEvent> <attrIndex> <newValue>
This command modifies alarms on the T7000.
Syntax <TriggeringEvent> <attrIndex> Description The alarm category or type. See the T7000 Maintenance and Troubleshooting Guide. The attribute value that you want to change, including: 2Alarm text 3Severity 4LED 5Audible Alarm <newValue> Use the corresponding value for the attrIndex selected, including: For attrIndex 2 use any text string that describes the alarm For attrIndex 3 use: INFORMATIONAL_ALARM, MINOR_ALARM, MAJOR_ALARM, or CRITICAL_ALARM) For attrIndex 4 use: LED_OFF, LED_RED, LED_YELLOW, LED_GREEN) For attrIndex 4 use: 0 for No audible alarm or 1 for Yes audible alarm
Alarms
53
Querying Alarms
Querying Alarms
alarmHistory
alarmHistory [[-v] <size> (card)]
If the OM is disconnected from the T7000, this command shows the alarms in the alarm history list on the T7000. When the OM is connected to the T7000, this list is empty because the alarm history is sent directly to the OM.
Syntax [-v] <size> (card)
alarmHistory
Description optional verbose flag, displays detailed alarm information if present number of alarm records to show optional card to query
C S l y Alarm Type r s ------------------------------------------------------------------------04.15-10:17:43 Card-7-7-24 - AuditCorrection 04.15-10:14:36 Span-19-7-24 - SpanAIS 04.15-10:14:36 Span-18-7-24 - SpanAIS 04.15-10:14:36 Span-17-7-24 - SpanAIS 04.15-10:14:36 Span-16-7-24 - SpanAIS 04.15-10:14:36 Span-15-7-24 - SpanAIS Timestamp ObjectID
54
Alarms
Querying Alarms
queryAlarmDef
queryAlarmDef <TriggeringEvent/ALL>
This command shows information pertaining to the specified alarm or all of the alarms.
Syntax <TriggeringEvent/ALL> Description
The name of any alarm trigger or ALL to show all of the alarm definitions. See the T7000
******* Alarm Definition ******* TriggeringEvent = CardStatus Alarm Text = Card is offline Severity = MAJOR_ALARM LED = CARD_LED Turns on audible alarm This is a system-wide alarm
Alarms
55
Querying Alarms
queryAlarms
queryAlarms [[-v] [QueryType] [QueryItem] [card]]
This command queries current alarm status. If you only enter queryAlarms the T7000 shows all currently active alarms for the card that originated the CLI command.
Syntax [-v] [QueryType] Description optional verbose flag, displays detailed alarm information if present optional parameter, only processed if -v flag is entered ALARM SEVERITY [QueryItem] optional parameter, only processed if -v flag is entered If the first parameter is ALARM, this parameter is any valid alarm or alarm category name. See the T7000 Maintenance and Troubleshooting Guide. If the first parameter is SEVERITY, this parameter is INFORMATIONAL_ALARM, MINOR_ALARM, MAJOR_ALARM, or CRITICAL_ALARM. [card] optional parameter, only processed if -v flag is entered Indicates the card number (1-20) on which the alarm resides.
queryAlarms SEVERITY MINOR_ALARM 19 S A A S Timestamp ObjectID e u c y Alarm Type v d k s --------------------------------------------------------03.30-11:18:28 ClkCard-0-0-1 CR * - * TDM_No_Valid_Ref 03.30-11:18:28 ClkCard-0-0-1 MJ * - * PowerA_Undervolt 03.30-11:26:40 SS7Link-0-2-1 MJ * - * SS7LinkStatus 03.30-11:27:02 SS7Link-1-3-1 MJ * - * SS7LinkStatus 04.04-12:08:11 Shelf-0-0-1 MJ * - * OMDiskThreshold 04.04-13:25:02 Card-17-17-1 MJ * - * CardStatus 04.05-09:56:10 Card-2-2-1 MN * - * AuditsManuallyDisabled 04.13-10:22:25 FE-1-11-1 IN * - * FEIfPaused
NOTE: Sev is the severity (MN=minor, MJ=major, CT=critical, IN=informational) Aud is whether or not the alarms is audible alarm (*=yes, -=no) Ack is whether or not the alarm been acknowledged (*=yes, -=no) Sys is whether or not this is a system-wide alarm (*=yes, -=no) Clr is whether or not the alarm been cleared (M=manually cleared, A=automatically cleared, -=not cleared)
56
Alarms
Events
3
As actions take place on the T7000 they produce events. For a complete list of events, see the T7000 Maintenance and Troubleshooting Guide.
Managing Events
enableEvent
enableEvent <eventType>
This command allows disabled events to be processed by the system. By default, all events are enabled and processed
NOTE: The event is only enabled on the card where the enableEvent command was entered.
Syntax
<eventType>
enableEvent AdoAttributeChanged ****** Event Notification ****** (eventName): EventEnabled (senderID): <718d120> (objectID): 0 (timestamp): 3b3a4 5bf (enabledEVID): 20606f
getMaxEventTransmit
getMaxEventTransmit [card]
This command displays the maximum number of events that are sent to a host by a
card. If card is omitted, the number of events sent by all cards is displayed.
Syntax Description Card number to get value from. Range is 1 20. Default is all cards
[card]
Events
57
Logging Events
Logging Events
eventLogSize
eventLogSize <size>
NOTE: The initial size of the event log is 100.
This command limits the number of events buffered in the event log to size.
Syntax Description number of events to record
<size>
eventLogSize 150
postEvent
postEvent <eventType> <oid> <parm1 <parm2 <...>>> cardNumber
This command generates an event on a specific oid on a specific card.
Syntax Description name of any valid event type Object Identifier unique identifier that the T7000 uses to address each object or circuit. See OID on page 30. Note: oid may be zero. the text that describes the event (If there are spaces, use double quotes.) number of card (1-20)
<eventType> <oid>
purgeEventLog
purgeEventLog
This command cleans the Event Log of all event records.
58
Events
Logging Events
stopEventLog
stopEventLog <eventName> [<shelf, card, pid, cat, inst>]
This command stops the logging of a specific event or of all events.
Syntax Description optional--skip this parameter to log all events name of specific event to log
Events
59
Querying Events
Querying Events
queryEventLog
queryEventLog <numEvents>
This command queries the most recent events
Syntax Description The number of events to display from the event log
<numEvents>
queryEventLog 2
**************************** ******** Event report ********* ******************************* Event #(1) ****** Event Notification ****** (eventName): Warning (senderID): <1431890> (objectID): "ohDelay" (timestamp): 8695 (refdate): 7d710c (reftime): 111208 (rawreftime): 82e2 (reserved): 0 (text): "Local SCCP PC/SSN does not exist. Cannot configure TCAP Service"
Event #(2) ****** Event Notification ****** (eventName): Warning (senderID): <1120b30> (objectID): "ohDelay" (timestamp): 8756 (refdate): 7d710c (reftime): 111208 (rawreftime): 82e2 (reserved): 0 (text): "Local SCCP PC/SSN does not exist. Cannot configure TCAP Service"
60
Events
Querying Events
queryEventRegs
queryEventRegs <eventName> or <eventNumber> or <shelf=x>
This command returns a list of processes that have registered to be notified upon the occurrence of the specified event. Syntax Description The name of the event that one or more processes have registered for. All events registered on shelf x. Note: shelf= must be typed in exactly as it appears.
queryEventRegs Fuse_Failure
EventRegistration #(0x1) This registration is for: Fuse_Failure Destination ID = shelf (0x5) card (0xa), pid (0x35), category (0x0), instance (0x0) Sender #0 = shelf (0x5) card (0xa), pid (0x7fffffff), category (0x7fffffff), instance (0x7fffffff) Stop FLag Set = FALSE
Events
61
Querying Events
62
Events
Queries
Generic CLI Queries
4
Use the query command to query a Generic CLI object. When entered without a dbObject, the query command returns a list of Generic CLI objects that can be queried.
query To query facilities, use 'queryFacility' Usage: query <dbObject> <key> [attribute] This action can be performed on the following: AccountCodeProfile AcctCodePatternProfile AniSubscriber BearerGroup CalltypeProfile CardConfiguration CardProperties Carrier CarrierRouteList CASTrunkGroup CFBInfo CFDInfo CFFInfo CFVInfo CLRTrunkGroup CodecProfile CodecProfileList DigitMap DS3Properties EscapeCodePatternProfile FEIProperties FTRSProfile HostIPAddrPair HuntGroup InterfaceGroup IPTrunkGroup LineProperties LNPRouteList MediaGateway MediaGatewayProfile OffHookDelayProfile OffHookImmediateProfile OfficeParms OutPulseProfile PacketCableCmts PCMMCmts PFCPatternProfile Prefix PRITrunkGroup PublicFeatureCodeProfile RateCenter RcfInfo SCCPNode SCFInfo ScreenList SdInfo SDSPatternProfile ServiceProfile Shelf SipAgwEndpoint SipAgwEndpointProfile SipEsgwEndpoint SipEsgwEndpointProfile SipNgwEndpoint SipNgwEndpointProfile sipVMS SMDIParms SpanProperties SpecificDigitStrProfile SS7TrunkGroup Subscriber
Queries
63
Some Generic CLI object queries have been documented in this manual, see:
query AniSubscriber on page 513 query Card on page 167 query Carrier on page 208 query CFVInfo on page 553 query SCFInfo on page 553 query CFBInfo on page 554 query CFDInfo on page 554 query CFFInfo on page 555 query OfficeParms on page 388 query Prefix on page 407 Querying a RateCenter on page 414 query SdInfo on page 556 query SCCPNode on page 486 query sipVMS on page 594 query SMDIParms on page 590 query Subscriber on page 552 TcapMwiParms on page 497
Any object not explicitly documented follows the Generic CLI Create Example on page 13.
64
Queries
View a snapshot of all active calls on an switch at a point in time. Log calls for a specific period. View the call log.
You can determine the interval in seconds to log calls on the switch. View active calls or a recorded call log on the following:
A card A trunk group A span All of the cards in a switch All of the spans in a switch All of the trunk groups on a switch
Queries
65
queryActiveCalls queryActiveCalls <spanOID | feifOID | cardOID | TrunkGroupName> queryActiveCalls <perSpan | perFeif | perTrunkGroup> queryActiveCalls <perCard [lines | trunks]>
This command displays a current active call snapshot.
Syntax <spanOID | feifOID | cardOID | TrunkGroupName> Description spanOID display for a single span feifOID display for a single Fast Ethernet Interface (FEIF), valid for PICs only cardOID display for a single card TrunkGroupName display for a single trunk group <perSpan | perFeif | perTrunkGroup> perSpan display for all spans perFeif display for all FEIFs perTrunkGroup display for all trunk groups
perCard display for all cards, both lines and trunks perCard lines display for all cards, lines only perCard trunks display for all cards, spans only
Active Channels per span: Span-0-2-11: 3 Span-1-2-11: 2 Span-2-2-11: 18 Span-3-2-11: 0 Span-4-2-11: 12 Span-5-2-11: 16 Span-6-2-11: 2 Span-7-2-11: 3 Span-8-2-11: 20 Span-9-2-11: 19
66
Queries
queryCallHist queryCallHist <spanOID | feifOID | cardOID | TrunkGroupName> queryCallHist <perSpan | perFeif | perTrunkGroup> queryCallHist <perCard [lines | trunks]>
This command displays the history of active call log.s
Syntax <spanOID | feifOID | cardOID | TrunkGroupName> Description spanOID display for a single span feifOID display for a single Fast Ethernet Interface (FEIF), valid for PICs only cardOID display for a single card TrunkGroupName display for a single trunk group <perSpan | perFeif | perTrunkGroup> perSpan display for all spans perFeif display for all FEIFs perTrunkGroup display for all trunk groups
perCard display for all cards, both lines and trunks perCard lines display for all cards, lines only perCard trunks display for all cards, spans only
Active Channels per span: Span-0-2-11: 304 Span-1-2-11: 225 Span-2-2-11: 180 Span-3-2-11: 10 Span-4-2-11: 128 Span-5-2-11: 169 Span-6-2-11: 208 Span-7-2-11: 388 Span-8-2-11: 203 Span-9-2-11: 197
Queries
67
assigned to a trunk group assigned to a GR-303 interface group acting as an SS7 link acting as a nailed up circuit assigned to a subscriber (for lines)
NOTE: This command does not return information for PIC facilities. PIC facilities are dynamically assigned.)
Description Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30. returns span-specific facilities
68
Queries
Syntax <oid>
Description Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30.
queryFacility Line-0 (OID: 4a18000) <3f409a0> Line key.........................<> objectID....................Line-0-1-10 dependentOIDs...............<> containerOID................Card-1-1-10 operationalState............BUSY administrativeState.........UNLOCKED masterOperationalState......ACTIVE masterAdministrativeState...UNLOCKED currentActivityCount........1 (1) maximumActivityCount........1 (1) inTest......................NO cpState.....................ACTIVE sReservedKey................<> protocol....................FXO signalingType...............LOOPSTART_A suspended...................NOT_SUSPENDED timers......................<3f41350> <3f41350> SubscriberFacilityTimers GuardTime...................4b0 (1200) ChargeDelay.................0 (0) TimedDisconnectTime.........1388 (5000) ForwardDisconnectTime.......c8 (200) RingCadenceOnTime...........7d0 (2000) RingCadenceOffTime..........fa0 (4000) MinFlashHookTime............12c (300) FlashInterval...............384 (900) MinWinkDuration.............64 (100) MaxWinkDuration.............15e (350) WinkDuration................c8 (200) DebounceTime................1e (30) FlashDuration...............384 (900) OffHookDigMax...............46 (70) OffHookDigMin...............0 (0) OnHookDigMax................46 (70) OnHookDigMin................0 (0) TerminatorDisconnectDelay...7d0 (2000) LCFO_Duration...............2bc (700) DialtoneDelay...............96 (150) channel.....................30 (48) activeService...............0 (0) subscriberKey..............."9724800000" conferenceInfo..............0 (0)
Queries
69
origChannelList.............0 (0) restrictedDigitPattern......0 (0) ropDigits...................0 - No Attribute Definition ropResultInfo...............0 - No Attribute Definition ropResultFlag...............0 - No Attribute Definition ringingType.................0 (0) activeCCBKey................"00a1600H4y0jq02" passiveCCBKey...............0 - No Attribute Definition activeCCBlock...............<3f40a78> <3f40a78> CCBlock key.................................0 objectID............................0 dependentOIDs.......................0 - No Attribute Definition origOID.............................Line-0-1-10 contextKey.........................."00a1600H4y0jq02" role................................ORIGINATOR ani................................."9724800000" destinationAddress.................."9724800001" termOID.............................Line-1-1-10 patternMatched......................3 (3) callingPartyNumPres.................1 (1) callingPartyName...................."Crutcher Mark" callingPartyNamePres................1 (1) callingPartyNameAvail...............0 (0) portedToLRN.........................0 (0) translatedIndicator.................0 (0) useLnpRoute.........................0 (0) carrier.............................0 (0) carrierSelectionInfo................0 (0) facilityInfoElem....................0 (0) infoDigits..........................0 (0) chargeNumber........................"" callType............................0 (0) originalAddress.....................0 (0) serviceIndicator....................0 (0) hopCounter..........................7f (127) redirectionCount....................0 (0) redirectionReason...................0 (0) redirectingNumber...................0 (0) networkServices.....................0 (0) msgType.............................1 (1) backwardProgressDescription.........1 (1) causeCode...........................10 (16) lata................................"123" dialToneType........................0 (0) forwardProgressDescription..........3 (3) changeBackwardProgressDescription...1 (1) changeForwardProgressDescription....0 (0) transferCapability..................0 (0) callingPartySubaddress..............0 (0) calledPartySubaddress...............0 (0) tandemRoutingCode...................0 (0) jurisdictionInfo...................."972480" routeFailedReason...................0 (0) restrictInfoAnalTrigger.............0 (0) restrictInfoCollTrigger.............0 (0) circuitCode.........................0 (0) uniqueNatureOfAddress...............1 (1) termChannelList.....................0 (0) dialedDigits........................"9724800001" genericInfoForEmergency.............<> locationIDNumber....................<> redirectSession.....................0 (0) redirectSessionType.................0 (0) currentSession......................0 (0) carrierUsed.........................0 (0) disposition.........................64 (100) dispositionTime....................."20071018001929000" offHkTime..........................."20071018001926000" onHkTime............................0 (0) termTrunkGroup......................""
70
Queries
carrierConnectTime.................."" carrierDisconnectTime..............."" tcapReqd............................0 (0) origRateCenter......................"rc1" termRateCenter......................"rc1" billingFlag.........................1 (1) partialCdrHandle....................0 (0) longDurationCdrHandle...............<419aa78> <419aa78> cmSendLongDurationCdr smrouting...10030 - No Attribute Definition key........."00a1600H4y0jq02" replacementDigits..................."" replacementMode.....................0 - No Attribute Definition PCAC................................"" prefixMatchedLen....................6 - No Attribute Definition SCPDipForAINDone....................0 - No Attribute Definition replacementAni......................"" replacementInfoDigits...............0 - No Attribute Definition remoteOperations....................0 (0) ainResourceType.....................0 - No Attribute Definition strParamBlock.......................0 - No Attribute Definition matchedPtnStr.......................0 - No Attribute Definition destName............................0 - No Attribute Definition accessCode..........................0 - No Attribute Definition countryCode.........................0 - No Attribute Definition InterOperAssiCode...................0 - No Attribute Definition tandemRouteDigit....................0 - No Attribute Definition featureInteraction..................0 - No Attribute Definition ftrsUseLnp..........................0 - No Attribute Definition ftrsPCAC............................0 - No Attribute Definition ftrsFwdingProfile...................0 - No Attribute Definition origDialedDigits...................."" origOutBoundCarrier................."" incCarrierId........................0 - No Attribute Definition replacementCSI......................100 - No Attribute Definition session.............................2 (2) NXCode..............................0 - No Attribute Definition regionCode..........................7fffffff - No Attribute Definition billingCalledParty..................0 (0) abridgedCDR.........................0 (0) origDestDigits......................"9724800001" origBearerOID.......................Line-0-1-10 termBearerOID.......................Line-1-1-10 originalAddressNOA..................fe (254) redirectingNumberNOA................fe (254) callingPartyNOA.....................0 (0) tandemBciInterworking...............0 (0) answerInd...........................0 (0) userNetworkInteraction..............0 (0) authStatus..........................0 (0) tandemFciInterworking...............0 (0) billingOrigOID......................Line-0-1-10 billingTermOID......................0 origInfoDigits......................0 (0) origChargeNumber....................0 (0) ccbspare1...........................0 (0) ccbspare2...........................0 (0) ccbspare3...........................0 (0) cfNumberFromLocalSipPhone...........0 (0) serviceActivationParm...............0 (0) escapeFtrsProfile...................0 (0) cadenceProfile......................0 (0) calledPtyStaType....................0 (0) voiceMailIndicator..................0 - No Attribute Definition callingPartyCategory................7fffffff - No Attribute Definition infoCollectedPattern................13 - No Attribute Definition ccbBitField.........................0 (0) origNumberPres......................3 (3) redNumberPres.......................3 (3) routeAttempts.......................0 (0)
Queries
71
callContextBlocks...........Dictionary (0 items) -> cblock......................<3f41158> <3f41158> CommonCCBlock key.....................<> objectID................Line-0-1-10 dependentOIDs...........<> trunkGroupName..........<> crv.....................0 (0) serviceFlag.............0 (0) onDemandServices........(BITFIELD) -> 0 serviceInProgress.......0 (0) reservedCodecTypeList...<> IPTrunkReserved.........0 (0) mediaGateway............<>
72
Queries
queryGrp
queryGrp [name] [<attributeName> [LOCAL] [TRACE]]
This command shows information about any trunk or hunt group. To convert hexadecimal output from this query command to decimal, see Using Hexadecimal on page 741.
Syntax [name] <attributeName> [LOCAL] Description name of group. Omit for a list of all Trunk or Hunt Groups. to return only a single attribute from the query optional requests that data is retrieved from the card where the command is entered, instead of from the dBMaster [TRACE] optional data is displayed in as an object trace.
queryGrp AmerC1 ******* Facility Group Trace ******* CASTrunkGroup key........................"AmerC1" facilities.................<1d8c670> FacilityList (1 items) -> 1 (1): TGFacility facility...Span-6-8-18 cic........0 (0) timers.....................<25aabc0> CasTimers GuardTime...................4b0 (1200) ChargeDelay.................0 (0) TimedDisconnectTime.........1388 (5000) ForwardDisconnectTime.......c8 (200) RingCadenceOnTime...........7d0 (2000) RingCadenceOffTime..........fa0 (4000) MinFlashHookTime............12c (300) FlashInterval...............384 (900) MinWinkDuration.............64 (100) MaxWinkDuration.............15e (350) WinkDuration................c8 (200)
Queries
73
DebounceTime................1e (30) FlashDuration...............384 (900) OffHookDigMax...............46 (70) OffHookDigMin...............0 (0) OnHookDigMax................46 (70) OnHookDigMin................0 (0) TerminatorDisconnectDelay...7d0 (2000) LCFO_Duration...............2bc (700) options....................<25aa180> CASOptions glareControl......................ODD outpulseAsDialed..................FALSE numOfDIDDigits....................a (10) networkServices...................NONE skipMinDigitsRestriction..........FALSE fgc911MakeFirstSecond.............OFF useANIDNIS........................NO routeOnRcvdCarrier................OUTBCRRIER_INBCARRIER diddtmfProvideDialtoneAfterWink...OFF selectionMethod............ROUND_ROBIN sendOAssistCalls...........FALSE sendDAssistCalls...........FALSE tandemRoutingType..........NO_ROUTING defaultDN..................0 restrictions...............(BITFIELD) -> 0 defaultNPA.................0 replaceDestinationDigits...FALSE replaceCarrier.............FALSE replaceAniDigits...........FALSE replaceInfoDigits..........FALSE ftrsProfile................0 replaceCSI.................FALSE localTermination...........ALLOWED tandemDefaultRoutingType...USE_CARRIER_NANP miscOptions................Dictionary (0 items) -> denyAniList................0 direction..................BI_DIRECTIONAL tandemCustomReplacement....NO trunkProtocol..............FXO signalingType..............LOOPSTART_D receivingProtocol..........NO_SUB_PROTOCOL outpulsingProtocol.........NO_SUB_PROTOCOL numDestDigits..............DEFAULT numAniDigits...............DEFAULT numInfoDigits..............DEFAULT outPulseProfileKey.........0 E911DefaultANI.............0
74
Queries
querySysMgr querySysMgr
If you perform this command on the card that is not the System Manager (SM), it returns the following:
Information about the cards role, for example, if this card is the Primary Management Interface (PMI) or Alternate Management Interface (AMI) Address of ISEhouse, if present Pointer to the active SM in the switch
querySysMgr System Manager status ===================== Current role is AMI SM Server (ISEhouse) shelf address is 210000. SM Server (ISEhouse) IP address is 172.19.161.20 The currently active SM is shelf 23/card 21 (0x17/0x15).
If you perform this command on the card that is the SM, it returns
Information about the cards role, showing it is the active SM Address of ISEhouse, if present States of all cards in the switch Outstanding timers against cards in the switch
querySysMgr System Manager status ===================== Current role is PMI SM Server (ISEhouse) shelf address is 210000. SM Server (ISEhouse) IP address is 172.19.161.20 Shelf numbers in this OCX system: 23 The currently active SM is this card, shelf 23/card 21 (0x17/0x15). S H E L F 23 =================================== Chassis = READY Slot 01 = READY Slot 02 = READY Slot 03 = READY Slot 04 = NULL Slot 05 = DISABLED Slot 06 = READY Slot 07 = READY Slot 08 = READY Slot 09 = NULL Slot 10 = READY Slot 11 = NULL Slot 12 = READY Slot 13 = NULL Slot 14 = NULL Slot 15 = READY Slot 16 = NULL Slot 17 = READY Slot 18 = NULL Slot 19 = READY Slot 20 = NULL Clk A = READY Clk B = NULL
Queries
75
queryConnections queryConnections
This command sends a HOSTD query event to all cards. It collects and reports the responses. It shows each network connection, and the connected shelf number in hexadecimal, the IP address, and the amount of time that the shelf has been connected to the switch. To convert hexadecimal output from this query command to decimal, see Using Hexadecimal on page 741. Also, see queryHostdProxyDb on page 81
queryConnections Card 17: Shelf:0xfd Card 21: Shelf:0x21 2 connections to shelf IP:172.19.168.5 Uptime:0 days 06:33:44 IP:172.19.161.20 Uptime:3 days 07:06:00
This command sets the wait time before performing a query command.
Syntax <waitTime> Description number of milliseconds
setQueryWait 1200
76
Queries
queryCardStatus queryCardStatus
This command shows card status for all of the cards in a switch, including the type of card and if it is in service or not.
queryCardStatus ************************************** ********* System Card Status ********* ************************************** SLOT ( 1):TICSUB Mgr SLOT ( 2):TIC SLOT ( 3):TIC SLOT ( 4):OUT-OF-SERVICE SLOT ( 5):OUT-OF-SERVICE SLOT ( 6):LTC SLOT ( 7):OUT-OF-SERVICE SLOT ( 8):PIC SLOT ( 9): SLOT (10):PICSUB Mgr SLOT (11): SLOT (12):PIC SLOT (13): SLOT (14):OUT-OF-SERVICE SLOT (15):BIC SLOT (16): SLOT (17):BICSUB Mgr SLOT (18): SLOT (19):BIC SLOT (20): CLCK (01):CLK CLCK (02):OUT-OF-SERVICE
Queries
77
queryShelfLEDs queryShelfLEDs
This command shows shelf light emitting diodes (LEDS) on all the cards in a switch and their severity.
queryShelfLEDs Slot: 1 2 3 Crit: - - Majr: - - Minr: - - Adbl: - - 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 - - - - - - - - - - - - - - - - - - - - - - A - - - - - - - - - - - - - A - A A - - - - - - - - - A A - A A
shelf_inv
shelf_inv
This command shows which slots have in-service cards logged onto inventory (marked by asterisks) and which cards currently have Ethernet connections (marked by brackets around asterisks).
shelf_inv
S C L l O 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 k T 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 A ==============================================================< - - - [*] - - - - - * * * - - - - - * * - C l k B *
78
Queries
dispOID
dispOID <OID>
Queries
79
status
status <oid> | (<object>) <key>)
This is the Generic CLI status command. For details, see status on page 7. It can also show command the Operational State, Master Operational State, Administrative State, Master Administrative State, Resource Status, and Resource Available status for an OID. However, this usage is being phased out. Use statusFacility instead.
Syntax [oid] Description Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30.
status span-0 ***** Status for Span-0-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: UNLOCKED Master Administrative State: UNLOCKED Resource Status: ISV Resource Available?: YES
statusFacility
statusFacility <oid> This command shows the Operational State, Master Operational State, Administrative State, Master Administrative State, Resource Status, and Resource Available status for an OID.
Syntax <oid> Description Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30.
934> statusFacility span-0 935> ***** Status for Span-0-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: UNLOCKED Master Administrative State: UNLOCKED Resource Status: ISV Resource Available?: YES
80
Queries
spanStatus
spanStatus
This command show the Operational State, Master Operational State, Administrative State, Master Administrative State, Resource Status, and Resource Available for all spans on the local card.
spanStatus Mastr Mastr Oper Oper Admin Admin Resrc Resrc OID State State State State Status Avail --------------------------------------------------------Span-0-6-23 ena ena unlk unlk isv yes Span-1-6-23 dis ena unlk unlk oos no
querySchedule querySchedule
This command shows the current task schedule. See addTask on page 597.
Tip
Although tasks can control alternate routing, they can also be used to automatically schedule any task that the switch should run periodically, such as backing up (flashing) the switch databases. querySchedule Current Time: 2004.09.05-10:34:39. Current Schedule: Task Name Start Time Card Period Command -------------------------------------------------------------------taskName yyyy.mo.dd-hh:mm:ss ## xxxxxxx x-command backup 2004.09.05-23:55:00 0 daily sh<6/backup
queryHostdProxyDb queryHostdProxyDb
This command lists all HOSTD connections to the switch. It shows OM, ISEhouse, and TOPI shelf connections in hexadecimal, and which card in the shelf terminates the connection. To convert hexadecimal output from this query command to decimal, see Using Hexadecimal on page 741. Also, see queryConnections on page
76.
Queries
81
now
now
This command returns the system time.
82
Queries
Database Queries
Database Queries
queryDbMaster queryDbMaster
This command shows the card number of the database master card. The dB master contains the provisioning database. All cards in the system know which card is the dB master. If the card running the dB master fails, another running card automatically becomes the dB master.
queryDbMaster DbMaster: 1
queryDb
queryDb [dbManagerID [key [attribute]]]
Tip
If you do not enter a dbManagerID, all database managers are returned
This command shows the list of databases and can also show the database being managed by a certain database manager. If you enter a key, only the database item referring to the key appears.
Description
the name of the db manager key optional the specific name (key) of the object that you want to query, for example the name of a rate center or the DN of a subscriber attribute optional
the attribute in the object of the database that you want to query queryDb tNailDbMgr Current Database... * * * * *
Queries
83
Database Queries
queryMemAudit queryMemAudit
This command displays memory audit information, including information about db Flash.
Related Commands
See setDbFlashPadSize on page 600. See setServiceSaveInterval on page 601.
queryMemAudit ******* Memory Audit Information ******* ShelfNumber = 10 Low memory threshold: 15% of 190.734MB (28.609MB) Memory Test Sample Period = 5000 millisecs Memory Test Sample Threshold = 3 times Required memory pad for dbFlash = 500000 Service database autosave interval = 180000000 millisecs Sufficient memory condition for 32 audit cycles
84
Queries
Database Queries
queryAttrDefs IPAddrPair ***** Attribute Definition For Class (IPAddrPair), Attribute (sIPAddr) ***** INDEX: 0 ACCESS: ReadWrite REQUIRED: NO DISPLAYED ON GUI: YES PERSISTENT: YES DATA TYPE: tString DEFAULT VALUE: 0 VALID VALUES: Any String between 7 and 15 characters MIN/MAX: 7 15 ***** Attribute Definition For Class (IPAddrPair), Attribute (Port) ***** INDEX: 1 ACCESS: ReadWrite REQUIRED: NO DISPLAYED ON GUI: YES PERSISTENT: YES DATA TYPE: Integer DEFAULT VALUE: 1 VALID VALUES: Any Integer between 1 and 65535 MIN/MAX: 1 65535
Queries
85
Database Queries
queryAttrDef Ds3Line operationalState ***** Attribute Definition For Class (Ds3Line), Attribute (operationalState) ***** INDEX : 4 ACCESS : ReadOnly REQUIRED : NO DISPLAYED ON GUI : YES PERSISTENT : NO DATA TYPE : Integer DEFAULT VALUE : 1 INPUT TYPE : String or Integer VALID VALUES : (DISABLED or 0), (ENABLED or 1), (ACTIVE or 2), (BUSY or 3),
86
Queries
Database Queries
queryModifiedAttrs queryModifiedAttrs
This command lists the object attributes that have been modified. This is usually the result of applying a patch to a trunk group.
xqueryModifiedAttrs IPTrunkGroup:sendCPN-OCX5.0.0-0042 HuntGroup:sendPilotDNasANI-OCX5.0.0-0078 InterfaceGroup:discardSETUP-OCX5.0.0-0087 OfficeParms:pingPeriod-OCX5.0.0-0096 SS7TrunkGroup:passFacilityMessage-OCX5.0.0-0099 PRITrunkGroup:errIntervalInMils-OCX5.0.0-0123 PRITrunkGroup:lowWaterPerSec-OCX5.0.0-0123 PRITrunkGroup:highWaterPerSec-OCX5.0.0-0123 InterfaceGroup:lowWaterPerSec-OCX5.0.0-0123
queryIG
queryIG <RDTName>
Tip
An asterisk next to the Trunk OID shows which card is running the call control logic. When the path is Active, the asterisk will be on that trunk. When the path is Forwarding, the asterisk will be on the mates trunk.
This command shows the trunks that are assigned to the primary and secondary EOCs and TMCs for an RDT interface group, as well as their corresponding spans.
NOTE: A status of Forwarding is the same as Active.
Syntax RDTName
queryIG
EOC Primary Path Status : Active Trunk-83-11-9* EOC Secondary Path Status : Standby Trunk-107-11-9 TMC Primary Path Status : Standby Trunk-95-11-9 TMC Secondary Path Status : Active Trunk-119-11-9* Spans: 1 Span-3-11-9 2 Span-4-11-9 Primary Secondary
Queries
87
Database Queries
<dbMgrCatName> <key>
In this example, rate center rc1 is referenced by several subscribers. Until these subscribers are deleted, or their rate center changed, rate center rc1 cannot be deleted.
whoDependsOn tRateCenterDbMgr rc1 Dependencies on this database entry... Dependencies in database tSubscriberDbMgr... Key: 9724800020 Key: 9724800021 Key: 9724800022 Key: 9724800023 Key: 9724800024 Key: 9724800025 Key: 9724800026 Key: 9724800027 Key: 9724800028 Key: 9724800029
88
Queries
CDRs
CDRs
queryCdrStatus
queryCdrStatus
This command displays Call Detail Record (CDR) counters and whether or not a billing collection host (for example, the OM) is connected.
Syntax maTotalTransmittedCdrCount maTotalRecordCdrCount maBufferedCdrCount Description The total number of CDRs transmitted from the card. The total number of CDRs created on this card since last boot. The total number of CDRs buffered on the card. If this value exceeds the maMaxCdrBuffer amount the system deletes the oldest CDRs to protect the cards memory. maTotalLostCdrCount maMaxCdrBuffer The total number of CDRs that were lost due to the CDR buffer being full. The maximum number of CDRs that can be stored on the card when the billing collector is not connected. The number of CDRs (default 30) sent to the billing collection system for every CDR transmission. The number of milliseconds between CDR transfers. The transfer rate for CDRs can be determined by using the following formula:
maMaxCdrPerTransmit
maCdrTransmitInterval
Queries
89
CDRs
Syntax maHostID
Description The destination id of the registered billing collection system. This value is only valid when the isHostConnected variable shows Yes connected. Indicates if CDRs are being held on the card (Yes), or being collected off the card, (No)
isCardBuffering
queryCdrStatus ******************************************** **************** CDR Status **************** ******************************************** maTotalTransmittedCdrCount.............8 maTotalRecordCdrCount..................8 maBufferedCdrCount.....................0 maMaxCdrBuffer.........................5000 maMaxCdrPerTransmit....................104 maCdrTransmitInterval..................1400 maSessionNumber........................8 maSequenceNumber.......................8
90
Queries
CDRs
showCDR
showCDR <maxRecords> [maPrintCdrDetail]
This command displays uncollected CDR records from the card.
NOTE: When CDR collection is running properly, there will be no (or very few) CDRs to display on the card.
Description the maximum number of CDR records to display. optional specifies that besides the raw CDR data, a formatted trace of the CDR show also be printed. 0f -- detailed print of primary CDRs f0 -- detailed print of secondary (service) CDRs ff -- detailed print of primary and secondary CDRs 0 -- (default) do not print detailed information for any type of CDRs
showCDR 3 [BEGIN]--------------OCX Message Accounting------------------[00001] 1;11;01;01;0000001;000001;;cardInit;20061221191644001;;;;;;;;;; [00002] 0;11;01;01;0000;0;0000002;000002;9724800000;;20061222222028000;200612222 22112000;104;20061222222112000;0;;;;;;;;0000;9724800000;15;00;;;;;;;;;;00 00;;;0; 0;;;00;;;16;;;0 [00003] 0;11;01;01;0001;0;0000003;000003;9724800001;;20061222222031000;200612222 22113000;104;20061222222113000;0;;;;;;;;0000;9724800001;15;00;;;;;;;;;;00 00;;;0; 0;;;00;;;16;;;0
[END
Queries
91
Substitution
Substitution
querySubstitution querySubstitution
This command shows the substitution manager, group members, and status of substitution for the specific card.
****** Substitution Status Check ****** Substitution Manager Card: 10 Substitution Group Member Cards: (8) (9) Substitution is active for NONE Substitution Manager Card: 14 Substitution Group Member Cards: (12) Substitution is active for NONE Substitution Manager Card: 20 Substitution Group Member Cards: (17) (18) (19) Substitution is active for NONE
querySubBus querySubBus
This platform command validates the substitution bus configuration in the rear of the midplane.
querySubBus Reads and displays *current* sub bus configuration Warning: Lack of rear cards on ends of group appear as breaks Warning: With 2 rear sub cards on same bus, data is unreliable querySubBus: (myslot=15) is not currently setup as a subCard querySubBus: can only be run on a SubCard I2C: Rear card config: I/O I2C: Sub Bus Config: ON Sub BusF
92
Queries
Substitution
displaySubBusGrps displaySubBusGrps
This platform command displays the saved substitution bus configuration from each substitution manager card.
displaySubBusGrps Displays *saved* sub bus configuration from each subCard Saved data is updated on power up and s/w subCard config* Warning: Lack of rear cards on ends of group appear as breaks Warning: With 2 rear sub cards on same bus, data is unreliable 1 2 S 3 X 4 x 5 x 6 X 7 8 9 10 11 12 13 14 15 16 17 18 19 20 - - - - - - - - - - - -
Queries
93
Central Office
Central Office
queryCAC
queryCAC <code>
This command shows the Carrier Access code and carrier attributes.
Syntax <code> Description 4-digit carrier access code
queryCAC 0333 Carrier: WorldComm, Code: 0333, Carrier Attributes: InterLata OS Capable DA Capable International
queryAudio
queryAudio [<name> | <ALL>]
Tip
Use this command to see which recorded announcements are provisioned on the switch: queryDbKeys tAudioDbMgr
This command shows a list of the recorded announcements on the switch. For a complete list of announcements on the T7000, see the T7000 Product Description Manual.
Syntax [name] [ALL] Description announcement name Keyword that acts as the key for all announcements.
queryAudio offHook Announcement: offHook Bytes: 54084 queryAudio ALL Current Announcement list --Announcement: --Announcement: --Announcement: --Announcement: --ScrNumToDel Announcement18 DelEntry Bytes: 149130 Bytes: 12364
Announcement19
94
Queries
Central Office
Bytes: 46799
SCRAnnouncement
Queries
95
Protocols
Protocols
Commands in this section are grouped by protocol, such as MGCP, VoIP, SS7, etc. For most MGCP commands, use the Generic CLI query command.
MGCP
queryGWY
queryGWY <associationId | all> [debug]
This command returns the Local and Remote addressing information for the requested Association ID(s). It queries the MGCP Stack Interface to get the association table information and dumps it for debugging purposes. An association can be thought of as a pairing between one FE's IP/port (either fe0 or fe-1 for the PIC) and the Gateway's IP/port (or the Gateway's Domain Name, if the IP is not yet known).
Syntax <associationId | all> [debug] Description Association ID, or the keyword all to query all Association IDs Optional keyword that provides additional information, mostly of interest to Taqua TAC personnel.
queryGWY all
172.19.160.111/2727 172.19.160.111/2727 172.19.160.111/2727 172.19.160.111/2727 172.19.160.111/2727 169.254.175.7/2427/hxt2.taqua.com hNXT2 169.254.175.6/2427/hxt1.taqua.com hNXT 172.19.177.240/2427/arris.taqua.com Aris 172.19.160.138/2427acgw.taqua.com gw3 172.19.160.128/2427/atagw2.taqua.com gw1
In the above example, the local IP Address of the 1st Association ID is 172.19.160.111, and the local Port number is 2727. The remote IP address of the same Association ID is 169.254.175.7, the Port Number is 2427, the Domain Name is hxt2.taqua.com,and the Gateway Instance is hNXT2.
queryGWY all debuug Assoc. Table entry size = 608 bytes. Id Prev NxtF Local IP/Port Remote IP/Port/Name Gateway Instance 1 8197 4 172.19.160.111/2727 0.0.0.0/0/[1] No Gateway Instance. 3 4 7 172.19.160.111/2727 169.254.175.7/2427/hxt2.taqua.com hNXT2 4 1 3 172.19.160.111/2727 169.254.175.6/2427/hxt1.taqua.com hNXT1 5 6 8197 172.19.160.111/2727 172.19.177.240/2427/arris.taqua.com Aris 6 7 5 172.19.160.111/2727 172.19.160.138/2427/acgw.taqua.com gw3 7 3 6 172.19.160.111/2727 172.19.160.128/2427/atagw2.taqua.com gw1 6 Gateway Associations are defined.
96
Queries
Protocols
queryGWYCounts
Tip
Use this command to ensure your Gateways are provisioned in a "balanced" manner among the available PIC or PIC2 card.
queryGWYCounts
This command searches the Media Gateway database and prints how many Gateways are provisioned on each PIC or PIC2 card. It also provides a count of the number of Gateways that were locked at the time the command ran. The 1st example shows 2 Gateways provisioned on a single PIC:
queryGWYCountsqueryGWYCounts Card: PIC 6 PIC 8 PIC 9 PIC13 PIC17 Gwy Count: 3000 1 3000 2000 2000
Queries
97
Protocols
SIP
status
status <oid>
This is the Generic CLI command, used to show information about a PIC cards Fast Ethernet (FE) interfaces.
Syntax <oid> Description Object Identifier of the Fast Ethernet Interface Facility (FEIF).
Object Identifier unique identifier that the T7000 uses to address each object or circuit of the near end network interface OID provisioned on the T7000. See OID on page 30.
status fe-0 ***** Status for FE-0-7-9 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: UNLOCKED Master Administrative State: UNLOCKED Resource Status: ISV Resource Available?: YES Bearer Activity?: 0 Bearer Resource Available?: YES IP Dialogue Activity? : 0 IP Dialogue Resource Available? : YES
98
Queries
Protocols
Tip
Use this command to see which codec profiles have been provisioned: query CodecProfile
This command shows the codec list or lists to which the codec profile belongs.
Syntax <codecProfileName> Description name of the codec profile to query
queryListByCodecProfile prf10 CodecProfileName:prf10 Key(codecProfileLstName): prflist3A Member in CodecProfileLst: codecProfile...: prf10 codecProfile...: prf30 codecProfile...: prf20 Key(codecProfileLstName): prflist3B Member in CodecProfileLst: codecProfile...: prf10 codecProfile...: prf20 codecProfile...: prf30
Queries
99
Protocols
Description name of SIP endpoint Keyword that acts as the key for all SIP endpoints with a name.
querySipEndpointByName SIP Endpoint Name ============================== querySipEndpointByName ALL 0 item(s) found using 'ALL' ) SIP Endpoint DN ===============
100
Queries
Protocols
querySipEndpoint
querySipEndpoint [[ALL] | [SipEndpointDN]]
Without a parameter, this command returns a list of all SIP endpoint keys. With a parameter of a SIP endpoint key, this command returns the entry in the Sip Endpoint Database that corresponds to that key. With a parameter of ALL, this command returns all entries in the Sip Endpoint Database.
Syntax [sipEndpointKey] [ALL] Description 10-digit directory number that acts as a key for SIP endpoint Keyword that acts as the key for all SIP endpoints.
<60c6bd0> SipAgwEndpoint key......................."9724691000" endpointName..............<> profileName..............."agwP1" bearerGrpKey.............."bg_agw" priHostIPAddrPair.........0 (0) altHostIPAddrPairs........0 (0) actHostIndex..............PRIMARY_HOST_ACTIVE transportType.............UDP signalingType.............SIP cmtsName..................<> FQDN......................<> outboundProxyIPAddrPair...0 (0)
Queries
101
Protocols
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods for example: 10.2.86.195
querySipEndpointByAddr Key=IP Address Pair SIP Endpoint DN ===================== ========================= 10.1.130.251:5060 9726921979 10.1.164.191:5060 9726921847 10.1.164.34:6200 9723847905 172.19.160.104:6060 9723847705 querySipEndpointByAddr 10.1.130.251:5060 1 item(s) found using '10.1.130.251:5060' <3907860> SipNgwEndpoint key......................."9726921979" endpointName..............<> priHostIPAddrPair.........<3907920> <3907920> IPAddrPair sIPAddr..."10.1.130.251" Port......13c4 (5060) lSecHostIPAddrPair........<> actHostIndex..............PRIMARY_HOST_ACTIVE bearerCards...............<39079c0> <39079c0> BearerCardList keyType......Integer
102
Queries
Protocols
valType......Integer collection...List (1 items) -> (1) IntegerValue: 8 (8) transportType.............UDP signalingType.............SIP profileName..............."ngwProfile1" cmtsName..................<> outboundProxyIPAddrPair...0 (0) * * * * *
Queries
103
Protocols
104
Queries
Protocols
SS7
The following commands query the status of SS7 objects
SS7RouteStatus R1_MIN SS7Route: R1_MIN Object ID: SS7Route-0-0-23 DPC: 229-123-100 Priority: 1 Congestion: 0 Status: Available LinkSet LinkSet1 is Available routeLB1 Object ID: 0x92c000 DPC: 200-200-200 Priority: 1 Congestion: 0, Status: Available LinkSet LinkSetLB1 is Available
Queries
105
Protocols
getSLSMap
getSLSMap [linksetName]
This command shows the Signaling Link Selection (SLS) mapping for the SS7 links in the specified lank set. If no link set is specified, the SLS maps for all link sets are showed.
Syntax Description name of the link set to display
linksetName
LinkSet: LinkSetLB1 (PC: 200-200-200) : Active, In Service Members: LinkLB1, Available ==================== SLSMAP for linkset 'LinkSetLB1' ==================== SLS Current Link Defined Link Alternate Link flag Link Set ___ ____________ ____________ ______________ ____ ________ 0 LinkLB1 LinkLB1 0 1 LinkLB1 LinkLB1 0 2 LinkLB1 LinkLB1 0 3 LinkLB1 LinkLB1 0 4 LinkLB1 LinkLB1 0 5 LinkLB1 LinkLB1 0 6 LinkLB1 LinkLB1 0 7 LinkLB1 LinkLB1 0 8 LinkLB1 LinkLB1 0 9 LinkLB1 LinkLB1 0 10 LinkLB1 LinkLB1 0 11 LinkLB1 LinkLB1 0 12 LinkLB1 LinkLB1 0 13 LinkLB1 LinkLB1 0 14 LinkLB1 LinkLB1 0 15 LinkLB1 LinkLB1 0 16 LinkLB1 LinkLB1 0 17 LinkLB1 LinkLB1 0 18 LinkLB1 LinkLB1 0 19 LinkLB1 LinkLB1 0 20 LinkLB1 LinkLB1 0 21 LinkLB1 LinkLB1 0 22 LinkLB1 LinkLB1 0 23 LinkLB1 LinkLB1 0 24 LinkLB1 LinkLB1 0 25 LinkLB1 LinkLB1 0 26 LinkLB1 LinkLB1 0 27 LinkLB1 LinkLB1 0 28 LinkLB1 LinkLB1 0 29 LinkLB1 LinkLB1 0 30 LinkLB1 LinkLB1 0 31 LinkLB1 LinkLB1 0 ...... route on link: LinkLB1 total: 128 percent: 100
106
Queries
Protocols
linkSetStatus LinkSetLB1 LinkSet Error Correction Method: Basic Error Correction Method Type: F LinkSet Object ID: 0x928000 PC: 200-200-200 Status: Active In Service Members: LinkLB1
linkStatus
linkStatus [linkName]
This command shows the status of a SS7 link within a link set. If no link is specified, the command shows the status for all links
Syntax [linkName] link name Description
linkStatus Linkset: LinkSetLB1, Error Correction Method: Basic Error Correction Method Link: LinkLB1 Error Correction Method: Basic Error Correction Method Type: F Link Object ID: 0x4c924000, Channel: Trunk-23-19-9 SLC: 00, PC: 200-200-200, Instance: 0 Status: Available
Queries
107
Protocols
nodeStatus
nodeStatus [nodeName]
This command reports the status of SS7 nodes. If no node is specified, the command shows the status for all nodes
Syntax [nodeName] node name Description
nodeStatus CXautoNode Object ID: 0x930000 PC: 100-100-100 Local, No Transfer Capability, ( Local) Not Restarting LBautoNode Object ID: 0x930001 PC: 200-200-200 Remote, No Transfer Capability, Adjacent Node Not Restarting, Accessible
SS7NetworkStatus ss7LBnet Object ID: 0x934000, Not BCC Network, Local Network. Not Restarting Members: OCXautoNode LBautoNode
108
Queries
Protocols
queryCIC
queryCIC pointCode
This command shows all CICs for a specified point code.
CAUTION
This command could return a very large number of CICs.
Syntax pointCode
queryCIC 2-2-2 ******* CIC Trace for 2-2-2 ******* CIC = 15, OID=Trunk-14-2-5 CIC = 1, OID=Trunk-0-2-5 CIC = 16, OID=Trunk-15-2-5 CIC = 2, OID=Trunk-1-2-5 CIC = 17, OID=Trunk-16-2-5 CIC = 3, OID=Trunk-2-2-5 CIC = 18, OID=Trunk-17-2-5 CIC = 4, OID=Trunk-3-2-5 CIC = 19, OID=Trunk-18-2-5 CIC = 5, OID=Trunk-4-2-5 CIC = 20, OID=Trunk-19-2-5 CIC = 6, OID=Trunk-5-2-5 CIC = 21, OID=Trunk-20-2-5 CIC = 7, OID=Trunk-6-2-5 CIC = 22, OID=Trunk-21-2-5 CIC = 8, OID=Trunk-7-2-5 CIC = 23, OID=Trunk-22-2-5 CIC = 9, OID=Trunk-8-2-5 CIC = 10, OID=Trunk-9-2-5 CIC = 11, OID=Trunk-10-2-5 CIC = 12, OID=Trunk-11-2-5 CIC = 13, OID=Trunk-12-2-5 CIC = 14, OID=Trunk-13-2-5
Queries
109
Protocols
dispPCMap
dispPCMap [nodeName]
This command displays the PC (Point Code) map for a given Alias node. The PC map routes ISUP messages by CIC to the Alias node.
Syntax [nodeName] Description Optional SS7 node name.Omit to display the PC map for all Alias nodes.
dispPCMap Garland AliasPCName Garland AliasPC 229-100-102 DestinationPC CICrange 230-100-011 0044-0056
110
Queries
Protocols
SLTC T1: 10000 SLTC T2: 30000 TXCongestionAbatementL1:30 TXCongestionOnsetL1:40 TXCongestionDiscardL1:60 TXCongestionAbatementL2:50 TXCongestionOnsetL2:70 TXCongestionDiscardL2:90 TXCongestionAbatementL3:80 TXCongestionOnsetL3:100 TXCongestionDiscardL3:110 TXCongestionTimer:30
queryNodeTimers Houston Houston Object ID: SS7Node-2-0-20 L3T25: 30000 L3T28: 3000 L3T29: 60000
queryNWTimers ss7LBnet Object ID: 0x934000 L3T22: 8000 L3T23: 16000 L3T24: 15000 L3T26: 12000 L3T27: 3000
Queries
111
Protocols
queryRouteTimers toHou toHou Object ID: SS7Route-0-0-20 L3T6: 800 L3T8: 1000 L3T10: 30000 L3T15: 2000 L3T16: 1400
112
Queries
Protocols
GR-303/PRI
queryDS1s
queryDS1s <rdtName>
This command shows the status of DS1s that connect the switch to an RDT.
Syntax rdtName Description name of Interface Group
NOTE: This command only returns information about the card to which it is directly connected. For the status of all d-channels on the switch, see queryDchStatus on page 114.
query921Status Inst 1 2 3 4 5 6 7 8 9 LAPD State TEI_Assigned TEI_Assigned TEI_Assigned TEI_Assigned Multiple_frame_established Multiple_frame_established Multiple_frame_established Multiple_frame_established Multiple_frame_established DLCI 104 904 104 100 100 104 904 104 100 OID Trunk-299 Trunk-299 Trunk-311 Trunk-311 Trunk-335 Trunk-299 Trunk-299 Trunk-311 Trunk-311 (012b) (012b) (0137) (0137) (014f) (012b) (012b) (0137) (0137) Port 1 1 2 2 3 1 1 2 2
Queries
113
Protocols
Syntax <TrkGrpName>
queryDchStatus toHoustonPRI PRI/NFAS Group: toHoustonPRI D-ch Primary (Trunk-263-10-20) Path Status : FailedLapd: Out_of_service Primary Trunk-263-10-20 Signaling Status: ISDND: lapdActive Channel: Failed Path: Failed Path Protection Status: PPS: waitingPathAvai Primary: Failed
114
Queries
Protocols
queryRDTClasses queryRDTClasses
This command shows all the long and short names of the RDT classes.
queryRDTClasses *******RDT CLASS NAMES FOR COMMAND-LINE INTERFACE******* Long Name: (NetworkElement) --- Abbreviated Name: (ne) -- Integer Value: (6) Long Name: (Equipment) --- Abbreviated Name: (eq) --Integer Value: (7) Long Name: (Memory) --- Abbreviated Name: (mem) --- Integer Value: (8) Long Name: (IdlcCPProfile) --- Abbreviated Name: (icpp) -- Integer Value: (25) Long Name: (IdlcDLProfile) --- Abbreviated Name: (idlp) -- Integer Value: (26) Long Name: (AnalogLineTerm) --- Abbreviated Name: (alt) -- Integer Value: (10) Long Name: (DS1LineTerm) --- Abbreviated Name: (ds1) --Integer Value: (17) Long Name: (ProtectionGroupUnit) --- Abbreviated Name: (pgu) --- Integer Value: (5) Long Name: (AlarmCountList) --- Abbreviated Name: (acl) -- Integer Value: (9)
Queries
115
Protocols
queryRDTLines Etres 1 2 3 4 5 6 InServ InServ InServ InServ InServ InServ Provisioned Provisioned Provisioned Provisioned Provisioned Provisioned NotRemoved NotRemoved NotRemoved NotRemoved NotRemoved NotRemoved {} {} {} {} {} {}
116
Queries
Protocols
queryRDTObject Etres mem 1 ******** RDT Object ObjectClass ObjectId PrimarySrvcState SecondarySrvcState Trace ******** - Memory - 1 - InServ - {}
Queries
117
Protocols
for GR-303 subscribers the subscriber DNs on an RDT and the unique call reference value (CRV) assigned to each subscriber DN for MGCP subscribers the subscriber DNs on an MGCP gateway and the unique termination ID assigned to each subscriber DN
Syntax <RDT/GW> Description name of the GR-303 RDT/name of the MGCP GW
querySubCRVs Etres Subscribers for IG Etres: CRV/MgTermID: 1Subscriber: 9724800001 CRV/MgTermID: 2Subscriber: 9724800002 CRV/MgTermID: 3Subscriber: 9724800003
queryCRVs
queryCRVs <RDTName|PRIGroupName> [p|r]
This command shows which CRVs are reserved or assigned to trunks for that RDT or PRI interface group.
Syntax RDTName| PRIGroupName [p|r] Description name of the GR-303 RDT name of the PRI interface group p permanent signal, returns only CRVs in which the phone has been off-hook for over 2.5 minutes r reserved, returns only CRVs reserved (unavailable while the switch allocates a trunk for the call).
queryCRVs AFC_NW_TARRANT
118
Queries
Protocols
Queries
119
FTRS
FTRS
queryPretranslation queryPretranslation <PreTransKey> | <ALL>
This command shows all patterns of a pretranslation table.
Prerequisites
Create an FTRS profile, see FTRSProfile on page 231 Create an FTRS pretranslation table, see createPretranslation on page 223 Add an FTRS pretranslation, see addPretranslation on page 224
Syntax <PreTransKey <ALL> Description the name of the pretranslation table a keyword that acts as the key for all pretranslation tables
queryPretranslation E911_Service_T Pre-Translation Table : 'E911_Service_T' ----------------------------------------------------------1: 911T /REM 1,3 /INS 1,2124800005 =CARRIER /CAC 0999 /REM 1,10 /INS 1,911 /CT 10 ===========================================================
120
Queries
FTRS
Prerequisites
Create an FTRS profile, see FTRSProfile on page 231 Create an FTRS pretranslation table, see createPretranslation on page 223 Add an FTRS pretranslation, see addPretranslation on page 224
Syntax <PreTransKey> <digitPtnStr> Description the name of the pretranslation table A digit pattern string in the pretranslation table. A pattern is the called number, dialed by the subscriber or received on a trunk group.
9*4600000
queryPretransByDigitPtn pretrantest
Queries
121
Routing
Routing
queryRouting queryRouting <NANP | LNP | CARR | TANDEMCARR | TANDEMANI>
Tip
Use query TandemTGRouteLis t to query Tandem Trunk Group routing.
This command returns the auxiliary routing tree for all route lists of the specified type, along with their minimum and maximum digits.
Syntax NANP
Description NANP North American Numbering Plan, routes calls when the destination is in the same carrier's network as the switch. LNP Local Number Portability, routes to telephone numbers that are moved between or within Local Exchange Carriers (LECs). CARR Carrier routes a four-digit number that identifies any company that provides circuit communications. TANDEMCARR Tandem Carrier routes from a subtending switch to an AT or ICX using the carrier code or a combination of the carrier code and the route code. TANDEMANI Tandem Automatic Number Identification, routes from a subtending switch to a AT or IXC using the ANI of the call.
LNP
CARR
TANDEMCARR
TANDEMANI]
122
Queries
Routing
queryRouting NANP ***** 1-DIGIT ROUTE LISTS ***** ROUTE LIST NAMED: RappServ MIN_DIGITS: (0) MAX_DIGITS: (0) ROUTE #0: ipngwaz1 ***** 3-DIGIT ROUTE LISTS ***** ROUTE LIST NAMED: ANA_T6000 MIN_DIGITS: (685) MAX_DIGITS: (685) ROUTE #0: ipngwVDngw ROUTE LIST NAMED: PSAP1 MIN_DIGITS: (911) MAX_DIGITS: (911) ***** 10-DIGIT ROUTE LISTS ***** ROUTE LIST NAMED: IAD1_MGCP MIN_DIGITS: (2124605000) MAX_DIGITS: (2124605000) ROUTE #0: ipngwVDngw ROUTE LIST NAMED: 2124605002 MIN_DIGITS: (2124605002) MAX_DIGITS: (2124605002) ROUTE #0: ipngwVDngw ROUTE LIST NAMED: skinney ROUTE #0: ipngwaz1
Queries
123
In-Service Upgrades
In-Service Upgrades
Taqua Technical Assistance Center (TAC) uses in-service upgrades (ISUs) to modify T7000 software while the switch is carrying call traffic. ISUs can either be applied to one card or all cards on a T7000. An ISU can be applied individually or as part of a Service Pack. Service Packs bundle ISUs in groups. This bundling reduces ISU dependencies and improves ISU interaction testing. ISUs in Service Packages are built, tested, and released together on the last General Availability (GA) software release and all previously-released Service Packages. Once an ISU is applied, it installs and re-applies itself automatically on every successive reboot of the cards. If an ISU is unapplied, but not unloaded, it reapplies itself on successive reboots.
WARNING
ISUs should always be applied on a T7000-wide basis, unless directed by Taqua. ISUs applied to a single-card should only be performed by qualified personnel under appropriate circumstances. If misused, single-card ISUs can cause the T7000 state to get out of sync and negatively affect call processing.
124
Queries
In-Service Upgrades
queryPatch
queryPatch [-v] [-s] <patchID | applied | catalyst | functional | all>
This command shows the ISU number, patch status, active status, and timestamp for one or more ISUs on a particular card.
Syntax [-v] [-s] <patchID applied catalyst Description The verbose parameter displays all ISU information. The default is to display brief ISU information. The sort parameter displays ISUs in numerical order. The default is to display ISUs in the order which they were applied. patchID Returns information for a particular ISU. applied Returns information on all applied (i.e. active) ISUs. catalyst Returns information on ISUs classified as catalysts. A catalyst ISUs does nothing when applied, but its presence or absence causes other ISUs to behave differently. functional Returns information on ISUs classified as functional. Functional ISUs take action when applied. all Returns information on all ISUs.
functional all>
queryPatch all Patch ID ======== OCX5.0.0-0004 OCX5.0.0-0007 OCX5.0.0-0015 OCX5.0.0-0014 OCX5.0.0-0017 OCX5.0.0-0018 OCX5.0.0-0010 OCX5.0.0-0001 OCX5.0.0-0006 OCX5.0.0-0011 OCX5.0.0-0012 OCX5.0.0-0013
Status ====== Applied Applied Applied Applied Applied Applied Applied Applied Applied Applied Applied Applied
Act. ==== Yes Yes Yes Yes Yes Yes Yes No/C No/C Yes Yes Yes
Flags ===== 00000015 00000005 00000015 00000015 00000015 00000015 00000015 00000005 00000015 00000015 00000015 00000015
Timestamp ========= 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006 11/13/2006
11:07:38 11:20:40 11:07:38 11:07:39 11:07:39 11:07:39 11:07:40 11:20:43 11:07:41 11:07:41 11:07:41 11:07:4
Queries
125
In-Service Upgrades
functional all>
sysQueryPatch -g OCX5.0.0-0004 *************** ** Shelf: 20 ** *************** C C l l 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 k k PatchID 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 A B ------------------------------------------------------------OCX5.0.0-0004 A A A A Aa a A: applied,active U: unapplied,active blank: not loaded a: applied,inert u: unapplied,inert dash: not loaded on mother/daughter
126
Queries
CALEA
CALEA
queryPenCommands queryPenCommands <admPW>
This shows all of the Pengroup commands.
Prerequisites
Create a pen group, createPenGrp on page 176 Change the Pen group password, see changePenPW on page 179
Syntax <admPW> Description administrator password.
queryPenCommands pw System Level Commands: createPenGrp, deletePenGrp, queryPenGrp, startPenMonitor, stopPenMonitor, setPenAttr, changePenPW, queryPenTarget, queryPenData, queryPenCommands, setPenGroupTimer Lea Level Commands: addLea, removeLea, queryLeas, queryLea, addLeaSpan, removeLeaSpan, startLeaMonitor,stopLeaMonitor, setLeaAttr Case Level Commands: addLeaCase, removeLeaCase, queryLeaCase, startCaseMonitor, stopCaseMonit or, addVoiceChnl, removeVoiceChnl, setCaseAttr Other Commands: queryPenLog, resizePenLog, purgePenLog
Queries
127
CALEA
Prerequisites
Create a pen group, createPenGrp on page 176 Change the Pen group password, see changePenPW on page 179
Syntax <admPW> Description administrator password
queryPenGrp pw ******* PenGroup Trace ******* <<2bc6c68>> PenGroup (key)0: <2b3ee68> (leaDict)1: <2b3da88> (targetDict)2: <2b3d098> (defaultPW)3: <2deff60> (adminPW)4: <1a98028> (ocxSystemID)5: <29e99a8> (ocxCardOID)6: 4a00001 (ocxMonitoringState)7: 1 (callDataCount)8: 0 (callContentCount)9: 0 (penClient_T1_period)a: 4b (penClient_T2_period)b: ea60 (penClient_T3_p eriod)c: a (dialedDigitExtraction)d: 1 <2b3ee68> tString {pengrp} <2b3da88> Dictionary (numItems)0: 0 (dataItems)1: <2b3e478> <2b3e478> tArray 0: 0 1: 0 2: 0 <2b3d098> Dictionary (numItems)0: 0 (dataItems)1: <2de6240> <2de6240> tArray 0: 0 1: 0 2: 0 3: 0 4: 0 <2deff60> tArray 0: 51 1: d0 2: f0 3: 59 4: 10 <1a98028> tArray 0: 4e 1: b3 <29e99a8> tString {PlanoT7000}
128
Queries
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179 Add a case, see addLeaCase on page 187
Syntax <targetDirn> <admPW> Description subject's directory number administrator password
queryPenTarget 9724800031 pw Target Dirn: 9724800031 LeaName: NTTA CaseID: TollRunner1001 Case Monitoring State: DISABLED Lea Monitoring State: ENABLED InterceptType: Call Data Start Date: Stop Date:
Queries
129
CALEA
Prerequisites
Change the Pen group password, see setPenGroupTimer on page 180 Create the Pen group database, see createPenGrp on page 176
Syntax <admPW> Description administrator password
queryPenData pw PenGroup Data: ocxSystemID = testT7000 ocxCardOID = Card-1-1-10 penClientT1 = 75 penClientT2 = 60000 penClientT3 = 10 dialedDigitExtraction = ENABLED ocxMonitoringState = ENABLED
130
Queries
CALEA
queryLea
queryLea <leaName> <admPW>
This command shows a LEA's attributes, its optionally assigned T1 spans, and a list of its cases. View individual cases using queryLeaCase, see queryLeaCase on page 132.
Prerequisites
Change the Pen group password, see changePenPW on page 179 Add a LEA, see addLea on page 181
Syntax <leaName> <admPW> Description Law Enforcement Agency name administrator password
queryLea NTTA pw LeaName: NTTA LEA ipAddr: 10.1.2.3 LEA Port: 5060 LEA Client Instance: 1 LEA Monitoring State: ENABLED LEA leaTrunkProtocol: NO_PROTOCOL Spans: logicalSpan - spanOID ---------------------------------Cases: 291> CaseIDs - TargetDirns ---------------------------------TollRunner1001 - 9724800031
Queries
131
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179
Syntax <leaName> <caseID> <admPW> Description Law Enforcement Agency name name assigned to the case administrator password
queryLeaCase NTTA TollRunner1001 pw Target Dirn: 9724800031 LeaName: NTTA CaseID: TollRunner1001 Case Monitoring State: DISABLED Lea Monitoring State: ENABLED InterceptType: Call Data Start Date: Stop Date:
132
Queries
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179
Syntax <admPW> [numRecords] Description administrator password optional the number of records you would like returned
queryPenLog pw 15 ---------------------OCX Pen-Link (Calea) Event Log------------------[01/25/07-16:24:48]: (Unknown) Informational - ADM password changed. [01/25/07-16:31:30]: (NTTA) Informational - LEA NTTA was added. [01/25/07-16:32:53]: (NTTA) Informational - Case was added.
Queries
133
CALEA
134
Queries
Provisioning
Use the commands in this chapter to set up the switch.
5
WARNING
The procedures in this guide are recommended by Taqua. Taqua does not assume responsibility for loss of data and in no event will Taqua be liable for any incidental or consequential damage in connection with the furnishing, performance or use of this material. The CLI provides low-level system access to users. This access has the potential to cause disruption of service, rendering the switch unusable and requiring intervention from Taquas field service personnel. To minimize provisioning and configuration errors Taqua recommends the following: 1. Use provisioning scripts instead of entering individual provisioning commands. Scripts are a group of dependent or related commands. 2. Test scripts using dryISE. dryISE simulates the operations of a real switch and provides a place to test scripts without affecting the call traffic on a switch. 3. Test scripts using a non-production switch with the same software image, and preferably the same configuration.
Provisioning
135
911
911
911 over CAS
CAS trunks using the FGC protocol route 911 calls. For information on Basic 911 and E911, see the T7000 Provisioning Guide.
Action Provision a CAS trunk group with FGC protocol (7-digit ANI) or FGCOS protocol (10-digit ANI) connecting the switch to the 911 tandem. For Basic 911, set the following trunk group timers (see CAS Trunk Group Timers on page 244): MinFlashHookTime 70 ms FlashInterval 60 ms FlashDuration 100 ms
Provision the prefixes (NPANXXs) on the switch.See Prefixes on page 403. Provision a 9-digit route list with the format 911NPANXX for each prefix with associated subscribers on the switch. See NANP Route List on page 519. Add the CAS trunk group that connects to the 911 tandem to each 9digit route list. See CAS Trunk Groups on page 235.
Action Provision the SS7 network. Provision the dedicated SS7 trunk group connecting the switch to the E911 tandem and a shared SS7 trunk group to take over if the dedicated SS7 trunk group fails. See SS7 Trunk Groups on page 324. Provision the prefixes (NPANXXs) on the switch. See Prefixes on page 403. Provision a 9-digit route list with the format 911NPANXX for each prefix with associated subscribers for each prefix on a switch. See NANP Route List on page 519.
136
Provisioning
911
Step
5
Action Associate the SS7 trunk groups connecting to the E911 tandem with each 9-digit route list. See Adding Facilities to a SS7 Trunk Group on page 344.
Provisioning
137
AIN
AIN
Advanced Intelligent Network (AIN) triggers are events that specify when the switch suspends call processing and queries the AIN database on a Service Control Part (SCP). The SCP, rather than the switch, stores calling services logic, leaving more storage room on the switch.
Step
1 2
Action Add an SCCP node to the local node, if one does not already exist. Add an SCCP Subsystem to the SCCP node of the local node, with the SSNs of the TCAP service. The SS7 service provider gives you the SSN value. Add an SCCP node to the Remote SCP or STP Alias node, if one does not already exist. Add an SCCP Subsystem to the Remote SCCP node of the SCP or STP Alias node. Use the same SSN for the remote Subsystem as was used for the local Subsystem in step 2. Add a generic AIN TCAP service with the applicable attributes including: svcType AINSVC remotePC point code of the remote node with the AIN database used by this service. See Point Codes on page 470.
138
Provisioning
AIN
Provisioning AIN
The following figure shows the order of provisioning for AIN:
Step
1
Action Create service pattern profile(s) for each of the following AIN trigger profile types: N11 Public Feature Code Specific Digit String Service pattern profiles contain services patterns
Add AIN service pattern(s) to each of the service pattern profiles created in step 1, The service pattern associates a digit pattern or code pattern with a TCAP service. Create AIN trigger profile(s) for each AIN trigger type. An AIN trigger profile
contains an AIN trigger type, which is either a digit pattern or a feature code. An AIN trigger profile tells the switch which SCP to route to or when to use escape codes and digit patterns.
4
Create a Service Profile for each set of AIN trigger profiles. A Service Profile contains AIN trigger profiles. Add a Service Profile to a subscriber or the Central Office.
Provisioning
139
AIN
Creating AIN Service Pattern Profiles create N11PatternProfile <key> create PFCPatternProfile <key> create SDSPatternProfile <key>
Use the Generic CLI create command to create the following types of AINservice pattern profiles:
description An N11 pattern profile stores N11 service patterns. The switch sends a query to the SCP when a subscriber dials an N11 number (where N=2-9). Use N11 service pattern profiles to assign numbers such as 711 or 511 to provide services to subscribers.
WARNING
Do not use the N11 Pattern Profile to assign 911 service. PFCPatternProfile A Public Feature Code pattern profile stores PFC patterns. The switch sends a query to the SCP when a subscriber dials a Public Feature Code *XX (where X=0-9). Use Public Feature Code service pattern profiles to assign codes such as *09 to provide services to subscribers. SDSPatternProfile A Specific Digit String pattern profiles stores SDS patterns. The switch sends a query to the SCP when a subscriber dials a Specific Digit String NXXXXXXXXX (where N=2-9 and X=0-9). Use Specific Digit String service pattern profiles to assign lists of digits (such as DNs) to provide services to subscribers.
Syntax <key>
140
Provisioning
AIN
Related Commands destroy N11PatternProfile <key> destroy PFCPatternProfile <key> destroy SDSPatternProfile <key query N11PatternProfile <key> query PFCPatternProfile <key> query SDSPatternProfile <key
Provisioning
141
AIN
Adding Service Patterns to a Service Pattern Profile insertInto <dbObject> <key> patterns <subKey> <subValue>
Tip
The same service pattern profile can have multiple service patterns.
Use the Generic CLI insertInto command to add a service pattern to a service pattern profiles patterns list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <dbObject>
Description name of the database object. One of: N11PatternProfile PFCPatternProfile SDSPatternProfile
name of a service pattern profile previously created the digits comprising the pattern to be added the TCAP service previously defined that will be invoked when this pattern is recognized
insertInto N11PatternProfile N11Pat patterns 311 HOST3 insertInto N11PatternProfile N11Pat patterns 411 HOST4 insertInto N11PatternProfile N11Pat patterns 511 HOST5
See Using Generic CLI Commands on page 6
Prerequisites
Create each service pattern profile before adding a service pattern to it (see Creating AIN Service Pattern Profiles on page 140). Create a TCAP service before adding a service pattern that invokes it. See TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492.
Related Commands query N11PatternProfile <key> query PFCPatternProfile <key> query SDSPatternProfile <key
142
Provisioning
AIN
Removing Service Patterns from Service Pattern Profiles deleteFrom <dbObject> <key> patterns <subKey>
Use the Generic deleteFrom CLI command to remove service patterns from a service pattern profiles patterns list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <dbObject> Description name of the database object. One of: N11PatternProfile PFCPatternProfile SDSPatternProfile <key> <subKey> name of a service pattern profile previously created the digits comprising the pattern to be removed.
deleteFrom N11PatternProfile N11Pat patterns 311 deleteFrom N11PatternProfile N11Pat patterns 411 deleteFrom N11PatternProfile N11Pat patterns 511
See Using Generic CLI Commands on page 6
Prerequisites
Create each service pattern profile before adding a service pattern to it (see Creating AIN Service Pattern Profiles on page 140). Create a TCAP service before adding a service pattern that invokes it. See TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492.
Related Commands query N11PatternProfile <key> query PFCPatternProfile <key> query SDSPatternProfile <key>
Provisioning
143
AIN
Related Commands query EscapeCodePatternProfile <key> Deleting Escape Code Pattern Profiles destroy EscapeCodePatternProfile <key>
Remove an escape code patterns profile from all Off Hook Delay Trigger, Public Feature Code, or a Specific Digit String Trigger profiles before attempting to delete it.
Syntax <key> Description name of the escape code pattern profile previously created
144
Provisioning
AIN
Adding Escape Code Patterns to an EscapeCodePatternProfile insertInto EscapeCodePatternProfile <key> escapeCodes <index> <value>
Use this command to add an escape code to an escape code profiles escapeCodes list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax EscapeCodePattern Profile <key> <index> Description keyword which specifies the EscapeCode object class name of the escape code pattern profile previously created the position in the list where <value> is to be inserted
Tip
Use a index of 1 to insert an escape code at the start of the escape code profile. Use a index of -1 to insert an escape code at the end of the escape code profile.
<value>
a string of digits
Prerequisites
Create an Escape Code Pattern before adding an escape code pattern to it (see Creating Escape Code Pattern Profiles on page 144).
Provisioning
145
AIN
Removing Escape Code Patterns from an EscapeCodePatternProfile deleteFrom EscapeCodePatternProfile <key> escapeCodes <index>
Use this command to remove an escape code from an escape code profile from an EscapeCodePatternProfiles escapeCodes list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax Description
EscapeCodePattern keyword which specifies the EscapeCode object class Profile <key> <index> name of the escape code pattern profile previously created the index number of the digit string to be removed from the escape code pattern profile
deleteFrom
EscapeCodePatternProfile
Prerequisites
Create an Escape Code Pattern Profile and add an Escape Code to it before deleting an Escape Code Pattern from it (see Adding Escape Code Patterns to an EscapeCodePatternProfile on page 145).
146
Provisioning
AIN
Use the Generic CLI create command to create the following types of AIN Trigger Profiles. Required parameters are underlined.
name N11Profile description N11 (where N=2-9) This AIN trigger sends a query to the SCP when a subscriber dials an assigned N11 number. Use service pattern profiles to assign numbers like 711 or 511 to provide services to subscribers. parameters key name of trigger profile serviceName name of service this trigger profile provides servicePatternKey name of previouslycreated service pattern profile associated with this trigger profile
Tip
Taqua recommends assigning this profile to the office service profile, not a subscriber service profile OffHookDelayProfile
This AIN trigger sends a query to the SCP when a subscriber dials digits not in the escape code profile.
key name of trigger profile serviceName name of service this trigger profile provides serviceRouteID the TCAP service previously defined that contains the routing to the SCP escapeProfileKey name of escape code pattern profile
Tip
Taqua recommends assigning this profile to a subscriber service profile, not the office service profile.
OffHookImmediateProfile
This AIN trigger sends a query to the SCP key name of trigger profile when it receives an off-hook indication from a serviceName name of service this trigger non-ISDN subscriber or a SETUP message profile provides from an ISDN interface. serviceRouteID the TCAP service previously defined that contains the routing to the SCP
Tip
Taqua recommends assigning this profile to a subscriber service profile, not the office service profile.
Provisioning
147
AIN
name
description
parameters key name of trigger profile allowRetries the number of times a subscriber can attempt to enter a valid account code Range: 0 - 2 Default: 0 acctCodePrompt determines the type of prompt used: PlayAnnAndDialTone (default) Play announcement and provide dial tone PlayAnnAndStutterTone Play announcement and provide stutter dial tone DialToneOnlyDial Tone only StutterToneOnly Stutter Tone only PlayAnnOnly Play announcement only servicesCalltypeProfileKey name of a previously created Call Type profile for the following call types: Call Forwarding Variable Call Forwarding Fixed Call Forwarding Do Not Answer Call Forwarding Busy Selective Call Forwarding Calls to a remote call forwarding subscriber Automatic callback Speed dial Automatic Call Return Warmline Revertive Call LDCalltypeProfileKey name of a previously created Call Type profile for toll call types 2, 4, 6. calltypeProfileKeyAssignment name of a previously created Call Type profile for call types 0 - 15
AccountCode- The Account Code Profile determines which Profile call types require account code digits, and how account code digits are collected. An Account Code Profile can be assigned to multiple Service Profiles. NOTE: If OffHookImmediateProfile and AccountCodeProfile are both assigned to the same subscriber, OffHookImmediateProfile takes precedence over AccountCodeProfile.
PubicFeatureCodeProile
Public Feature Code XX (where X=0-9) This AIN trigger sends a query to the SCP when a subscriber dials the assigned service code (e.g., *XX). Use service pattern profiles to assign codes like *09 to provide services to subscribers.
key name of trigger profile serviceName name of service this trigger profile provides servicePatternKey name of previously created service pattern profile associated with this trigger profile
Tip
Taqua recommends assigning this profile to a subscriber service profile, not the office service profile.
148
Provisioning
AIN
name SpecificDigitStrProfile
description Specific Digit String NXXXXXXXXX (N=2-9 and X=0-9) This AIN trigger sends a query to the SCP when a subscriber dials a series of assigned digits. Use service pattern profiles to assign a list of digits (such as a DN) to provide services to subscribers.
parameters key name of trigger profile serviceName name of service this trigger profile provides servicePatternKey name of previously created service pattern profile associated with this trigger profile
Tip
Taqua recommends assigning this profile to the office service profile, not a subscriber service profile
TermAttemptProfile
This AIN trigger sends a query to the SCP when the call directed to the Directory Number (DN) reaches the Termination Attempt Trigger Detection Point (TDP). This occurs when the call terminates to a subscriber on the T7000 (with or without facility).
key name of trigger profile serviceName name of service this trigger profile provides serviceRouteID the TCAP service previously defined that contains the routing to the SCP
Tip
Taqua recommends assigning this profile to a subscriber service profile, not the office service profile.
create one or more service pattern profiles (see Creating AIN Service Pattern Profiles on page 140). add one or more service patterns to each service pattern profile (see Adding Service Patterns to a Service Pattern Profile on page 142).
Create a TCAP service before adding a service pattern that invokes it. See TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492. Create an escape code pattern profile (see Creating Escape Code Pattern Profiles on page 144).
NOTE: Escape code pattern profiles are optional for Specific Digit String profiles.
Provisioning
149
AIN
For Off Hook Delay, Off Hook Immediate and Termination Attempt trigger profiles
Create a TCAP service before adding a service pattern that invokes it. See TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492.
For AcountCodeProfile
Related Commands query N11Profile <key> query OffHookDelayProfile <key> query OffHookImmediateProfile <key> query PublicFeaureCodeProile <key> query SpecificDigitStrProile <key> query TermAttemptProfile <key>
150
Provisioning
AIN
Deleting AIN Trigger Profiles destroy N11Profile <key> destroy OffHookDelayProfile <key> destroy OffHookImmediateProfile <key> destroy PublicFeatureCodeProfile <key> destroy SpecificDigitStrProfile <key> destroy TermAttemptProfile <key>
Use this command to remove an AIN trigger profile.
Syntax Description keyword which specifies the N11 Profile object class keyword which specifies the Off Hook Delay Profile object class
N11Profile OffHook-DelayProfile
OffHookImmediate- keyword which specifies the Off Hook Immediate Profile object class Profile PublicFeatureCode keyword which specifies the Public Feature Code Profile Profile object class SpecificDigitStrProfile TermAttemptProfile
<key> keyword which specifies the Specific Digit String Profile object class
keyword which specifies the Termination Attempt Profile object class name of the AIN Trigger Profile previously created
Prerequisites
Before deleting an AIN trigger profile:
Remove the AIN trigger profile from the Service Profile to which it is assigned.
Related Commands query N11Profile <key> query OffHookDelayProfile <key> query OffHookImmediateProfile <key> query PublicFeatureCodeProile <key> query SpecificDigitStrProfile <key> query TermAttemptProfile <key>
Provisioning
151
AIN
Service Profile
A Service Profile contains one or more AIN trigger profiles. The Service Profile can have many AIN trigger profiles, as long as each is of a different trigger type. An AIN trigger profile specifies calls that require AIN processing. Assign a Service Profile to:
individual subscribers all subscribers on the switch both individual subscribers and all subscribers
NOTE: Taqua recommends assigning these Trigger Profiles only to subscribers: Off Hook Delay, Off Hook Immediate, Public Feature Code, Termination Attempt. NOTE: Taqua recommends assigning these Trigger Profiles only to the Office: N11, Specific Digit String
AIN triggers are first checked against an individual subscribers Service Profile. If there is no match, the trigger is then checked against the officeService Profile. A Service Profile has the following attributes. Each AIN Trigger Profile key is the name of an AIN Trigger Profile. See Creating AIN Trigger Profiles on page 147.
Attribute key OffHookImmediateProfileKey OffHookDelayProfileKey PublicFeatureCodeProfileKey SpecificDigitStringProfileKey N11ProfileKey AccountCodeProfileKey Service Profile name Off Hook Immediate AIN Trigger Profile key Off Hook Delay AIN Trigger Profile key Public Feature Code AIN Trigger Profile key Specific Digit String AIN Trigger Profile key N11 AIN Trigger Profile key Account Code AIN Trigger Profile key Description
152
Provisioning
AIN
The the Generic CLI is used for all Service Profile commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
NOTE: A newly created Service Profile does not have any AIN Trigger Profiles associated with it. Use the Generic CLI modify command to add one or more AIN Trigger Profiles to a Service Profile.
create ServiceProfile SP1 modify ServiceProfile SP1 N11ProfileKey N11Prof1 Deleting Service Profiles
Use the destroy command to delete a Service Profile. You can delete a Service Profile without first deleting its contents. The AIN trigger profiles assigned to that Service Profile will remain available to other Service Profile. However, before removing a Service Profile, remove it from the office and/or subscribers to which it is assigned.
Provisioning
153
Account Codes
Account Codes
The Account Codes feature, first introduced in Release 6.0, shares many of the same concepts as AIN Triggers (See AIN on page 138.)
Tip
Other vendors may refer to non-verified account codes as account codes or "project codes", and to verified account codes as authorization codes.
The switch may verify the account code digits against a provisioned digit length. Taqua calls this case a non-verified account code. Or, the switch may verify the account code digits against a list of allowed digit strings. Taqua calls this case a verified account code. The collected digits appear in the CDR record for Taqua customer billing purposes.
154
Provisioning
Account Codes
Step
1
Action (Optional) Create an Escape Code Pattern Profile. An Escape Code Pattern Profile contains numbers that can be called without an Account Code. See Creating Escape Code Pattern Profiles on page 144. (Optional) Create an Account Code Pattern Profile. An Account Code Pattern Profile contains a list of Account Codes that a subscriber dials to complete a call. See AcctCodePatternProfile on page 157. NOTE: An Account Code Pattern Profile is not required if you are provisioning non-verified account codes. In this case, the subscriber may enter any combination of digits that matches the digitsLength attribute in the Call Type Profile. See CalltypeProfile on page 160.
Create a Call Type Profile. A Call Type Profile determines the length of the Account Code. It also determines whether or not an Escape Code Pattern Profile, or an Account Code Pattern Profile, or both, are used. See CalltypeProfile on page 160.
Provisioning
155
Account Codes
Step
4
Action Create an Account Code Profile. An Account Code Profile specifies which call types require Account Code digits and the account code collection requirements. These collection requirements determine the user prompt when an Account Code is required, and the number of retries allowed when an invalid Account Code is entered. An Account Code Profile also specifies which call types require Account Code digits. See AccountCodeProfile on page 161.
Create a Service Profile. The Service Profile associates the Account Code Profile with the Subscriber to which the account code requirements apply. See Service Profile on page 152. NOTE: You may also assign the Account Code Profile to an existing Service Profile. Such a Service Profile will also contain AIN trigger profiles, which allow AIN-based features for the subscriber.
156
Provisioning
Account Codes
AcctCodePatternProfile
An Account Code Pattern Profile contains a list of Account Codes that a subscriber dials to complete a call. An AcctCodePatternProfile has the following attributes:
Attribute key patterns Description name of the Account Code Pattern Profile a list of Account Codes.
The Generic CLI is used for all Account Code Pattern Profile commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
patterns
See Adding Account Codes to an AccountCodePatternProfile on page 158 and Removing Account Codes from an AccountCodePatternProfile on page 159
Provisioning
157
Account Codes
Adding Account Codes to an AccountCodePatternProfile insertInto AcctCodePatternProfile <key> patterns <index> <value>
Use this command to add an Account Code to an AccountCodePatternProfiles patterns list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax AcctCodePattern Profile <key> <index> Description keyword which specifies the Account Code Pattern Profile object class name of a previously created Account Code Pattern Profile the position in the list where <value> is to be inserted
Tip
Use a index of 1 to insert an escape code at the start of the Account Code Patter Profile. Use a index of -1 to insert an escape code at the end of the Account Code Patter Profile.
<value>
Prerequisites
Create an Account Code Pattern Profile before adding an Account Code pattern to it (see AcctCodePatternProfile on page 157).
158
Provisioning
Account Codes
Removing Account Codes from an AccountCodePatternProfile deleteFrom AcctCodePatternProfile <key> patterns <index>
Use this command to remove an Account Code from an AccountCodePatternProfiles patterns list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax Description
AcctCodePattern keyword which specifies the Account Code Pattern Profile object Profile class <key> <index> name of the Account Code Pattern Profile previously created the index number of the digit string to be removed from the Account Code Pattern Profile
Prerequisites
Create an Account Code Pattern Profile and add an Account Code to it before deleting an Account Code from it (see Adding Account Codes to an AccountCodePatternProfile on page 158).
Provisioning
159
Account Codes
CalltypeProfile
Tip
Different Call Type Profiles with different values in the digitsLength field can use the same Account Code Pattern Profile. Each Call Type Profile will only match on the number of Account Code digits specified in the digitsLength field.
A Call Type Profile determines the length of the Account Code. It also determines whether or not an Escape Code Pattern Profile, or an Account Code Pattern Profile, or both, are used. A Call Type Profile has the following attributes: Attribute key digitsLength Description name of the Call Type Profile the number of Account Code digits in the Account Code Pattern Profile to verify
acctCodePattern optional name of the Account Code Pattern Profile associated with ProfileKey this Call Type Profile. Do no data fill this attribute if you are provisioning non-verified account codes. escCodePatternP optional name of the Escape Code Pattern Profile associated with rofileKey this Call Type Profile. Do no data fill this attribute if you are provisioning non-verified account codes.
The Generic CLI is used for all Call Type Profile commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key digitsLength
acctCodePatternProfileKey escCodePatternProfileKey
160
Provisioning
Account Codes
AccountCodeProfile
An Account Code Profile specifies which call types require Account Code digits and the account code collection requirements. These collection requirements determine the user prompt when an Account Code is required, and the number of retries allowed when an invalid Account Code is entered. An Account Code Profile has the following attributes:
Attribute key allowRetries Description name of the Call Type Profile the number of times a subscriber may reenter an Account Code. Range: 0 - 2. Default: 0 acctCodePrompt the type of prompt the switch will provide when a call is attempted that requires an Account Code. Values are: PlayAnnAndDialTone (default) Prompt announcement followed by dial tone. PlayAnnAndStutterTone Prompt announcement followed by stutter tone. DialToneOnly Dial tone only. StutterToneOnly Stutter tone only. PlayAnnOnly Prompt announcement only. servicesCalltype the name of a previously provisioned Call Type Profile to be used ProfileKey for the following types of services calls: Call Forwarding Variable Call Forwarding Fixed Call Forwarding Do Not Answer Call Forwarding Busy Selective Call Forwarding Calls to a remote call forwarding subscriber Automatic callback Speed dial Automatic Call Return Warmline Revertive Call If a Call Type Profile is not assigned to this attribute, account codes are not required for these services.
Provisioning
161
Account Codes
Attribute LDCalltypeProfileKey
Description the name of a previously provisioned Call Type Profile to be used for intralata, interlata and international calls. These are the typical call types for which the user requests account code service (toll restriction with PIN). If a Call Type Profile is not assigned to this attribute, account codes are not required for these types of calls. NOTE: You may alternately provision one or more specific call types in the calltypeProfileKeyAssignment list.
calltypeProfile- a list of call types, each with an associated Call Type Profile. KeyAssignment NOTE: If you provision an LDCallTypeProfile key, and also provision a CallType Profile for Call Types 2, 4 or 6, the CallType Profiles provisioned here take priority over the LDCallTypeProfile.
The Generic CLI is used for all Account Code Profile commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
create AccountCodeProfile LD_3_digit_verified modify AccountCodeProfile LD_3_digit_verified calltypeProfileKeyAssig nment OAInterlata_3 threeDigitVerified
162
Provisioning
BearerGroup
BearerGroup
A BearerGroup is a set of one or more Fast Ethernet Interfaces (FEIs). A BearerGroup object simplifies bearer management for IP Endpoints. Prior to Release 6.0.1, each MediaGateway and SIP Endpoint had its own separate list of Fast Ethernet Interfaces to be used as bearer resources for IP calls. Frequently, these lists were identical. With a BearerGroup, the list of Fast Ethernet Interfaces is centralized. This simplifies maintenance: whenever the list of Fast Ethernet Interfaces needs to be changed, instead of updating several IP Endpoints, only a single BearerGroup need be updated. A BearerGroup object has the following attributes:
Attribute key bearerFEs Description Name of the BearerGroup object A list containing Fast Ethernet Interface OIDs.
The Generic CLI is used for all BearerGroup commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
bearerFEs
See Adding a Fast Ethernet Interface to a BearerGroup on page 164 and Removing a Fast Ethernet Interface From a BearerGroup on page 164.
create BearerGroup bg1 query BearerGroup bg1 destroy BearerGroup bg1 Dependent Commands
After creating a BearerGroup, assign it to one or more IP Endpoints. See MediaGateway on page 371, Setting up a Subscriber Access SIP Endpoint on page
420, and Setting up a Network Gateway SIP Endpoint on page 421.
Provisioning
163
BearerGroup
Adding a Fast Ethernet Interface to a BearerGroup insertInto BearerGroup <key> bearerFEs <subkey> <subvalue>
Use the Generic CLI insertInto command to add a Fast Ethernet Interface to a BearerGroups bearerFE list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> BearerGroup name This is the index in the bearerFE list where you want to enter the Fast Ethernet Interface OID. Description
<subkey>
Tip
Use a index of 1 to insert the Fast Ethernet Interface OID at the start of a BearerGroups bearerFEs list. Use a index of -1 to insert Fast Ethernet Interface OID at the end of a BearerGroups bearerFEs list.
<subvalue>
This attribute specifies the Fast Ethernet Interface Object ID. See OID on page 30.
The following command adds Fast Ethernet Interface 1 to the start of the bearerFE list for BearerGroup bg1:
insertInto BearerGroup bg1 bearerFEs 1 fe-1 Removing a Fast Ethernet Interface From a BearerGroup deleteFrom BearerGroup <key> bearerFEs <subkey>
Use the Generic CLI deleteFrom command to remove a Fast Ethernet Interface from a BearerGroups bearerFE list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> carrier name The index in the bearerFE list of the Fast Ethernet interface that is being removed. Note that the FE to be removed is specified by its position in the bearerFE List, not by its instance! Description
<subkey>
The following command removes the Fast Ethernet Interface at the start of the bearerFE list for BearerGroup bg1
164
Provisioning
CardConfiguration
CardConfiguration
Tip
You must create a CardConfiguration object before any provisioning can be done to the card. This is a major change from previous releases, one that is sure to break every existing script!
New in Release 6.0 is the CardConfiguration object. CardConfiguration lets you define a card on the shelf before the card is physically booted. This enables you to pre-provision a card before it is installed on the shelf, and protects the integrity of the provisioning database when a card type other than what has been provisioned is inserted into the shelf. Whenever a card boots, its card type is checked against the corresponding entry in the CardConfiguration object. If the card types do not match, there is a mismatch between what is provisioned in the database and what is present on the shelf. In such a case, the switch will not unlock the card, and the card can not be used for processing calls. When faced with such a mismatch, you must either replace the front card to agree with the database, or modify the CardConfiguration object to change its card type. You may change the card type as long as the new card type has more facilities than the old type. Only the following changes are allowed, all other combinations will fail:
TIC to TIC2_16SPAN TIC to a TIC2 TIC2_16SPAN to a TIC2 PIC to a PIC2_2 PIC2 to a PIC2_3
If you can not change the CardConfiguration card type, you must first destroy the old CardConfiguration object for that slot and then create a new CardConfiguration object.
NOTE: The old card will have to be deprovisioned before Generic CLI will let you destroy its corresponding CardConfiguration object.
Provisioning
165
CardConfiguration
The Generic CLI is used for all CardConfiguration commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
166
Provisioning
CardConfiguration
query Card
query Card
This command displays information about card objects. Since the output from this command is both long and varies by card type, this section is organized a little differently than the rest of the document. For whatever type of card the command is run on, the following information is displayed:
query card (OID: 5b00001) <48e6400> LTCard key.........................<> objectID....................Card-1-1-27 dependentOIDs...............Array (7 items, zero items suppressed) ->
Attribute <oid>
Description Object Identifier of the Card, in hex. Object Identifier unique identifier that the T7000 uses to address each object or circuit of the near end network interface OID provisioned on the T7000. See OID on page 30.
cardType
The type of card being queried. Values are: LTCard Line Termination Card TICard T1 Interface Card ETICard TI Interface Card 2 DS3Card Broadband Interface Car VPCard Packet Interface Card PIC2Card Packet Interface Card 2
objectID dependentOIDs
Object Identifier of the Card, in the form of Card-SlotSlot-Shelf A list of the Lines (LTC), T-1 Spans (LTC, TIC, TIC2), DS-3s (BIC), or Fast Ethernet Interfaces (PIC, PIC2) that the card contains.
Provisioning
167
CardConfiguration
Description Object Identifier of the shelf containing the card, in the form of Shelf-<shelfNumber>-0-<shelfNumber> Status of the card for processing call traffic. For more detail, see The T7000 Maintenance and Troubleshooting Guide Status of the controlling device for processing call traffic. For more detail, see The T7000 Maintenance and Troubleshooting Guide
masterOperationalState
168
Provisioning
CardConfiguration
Attribute administrativeState
Description Status of the card for making changes. For more detail, see The T7000 Maintenance and Troubleshooting Guide Status of the controlling device for processing call traffic. For more detail, see The T7000 Maintenance and Troubleshooting Guide LTC, PIC and PIC2: Total number of active calls on this card in hex (decimal) LTC, PIC and PIC2: Maximum possible number of active calls on this card in hex (decimal). The DS-3/span/trunk/line is currently in Test mode (i.e., diagnostics are being run. Number of T-1 Spans on this card in hex (decimal) Internal value. Number of Lines on this card in hex (decimal) Number of Digital Signal Processors on this card in hex (decimal). Number of DS-3s on this card in hex (decimal). Number of Fast Ethernet Interfaces on this card in hex (decimal). Internal Value. Controls the local Fault Manager. For details, consult The T70000Maintenance and Troubleshooting Guide. Internal, read-only value. When flow control is disabled on an ingress port (i.e. FE0, FE1, FE2) frames are subject to Weighted Random Early Drop (WRED) whenever the average rate for that port has been exceeded. During this time frames are differentiated based upon their drop precedence. During Level 1 dropping only rateControlHighDrop percent of High-Drop frames will be dropped. If Level 1 dropping is insufficient to reduce the incoming rate, then Level 2 dropping will become active. When this occurs all High-Drop frames are dropped and rateControlLowDrop percent of LowDrop frames are also dropped.
masterAdministrativeSta te currentActivityCount maximumActivityCount inTest spansPerCard spanType linesPerCard dspsPerCard ds3sPerCard feifsPerCard operatingMode systemMode
rateControlHighDrop
rateControlLowDrop
Provisioning
169
CardConfiguration
Attribute qosFixedPriority_CPU
Description Internal, read-only value. The fixed values for the FE ports use a value of 0 for low priority and 1 for high priority.
qosFixedPriority_GigE
Internal, read-only value. The fixed values for the FE ports use a value of 0 for low priority and 1, 2, or 3 for higher priority.
qosVlanTransmitPriority
Internal, read-only value. Sets the transmit priority level based upon the vlan tag priority bits. qosVlanTransmitPriority, qosFixedPriority_CPU and qosFixedPriority_GigE controls are mutually exclusive (i.e., only one them should be set).
qosVlanDropPriority
Internal, read-only value. When ports are configured to use VLAN Tag based Transmit priority one should also setup the VLAN Drop Priority. This control is used when congestion occurs to map the vlan tag priority bits to a drop level, and to decide which packets to drop first. The High Drop Priority packets are dropped first. A value of 0 = Low drop priority, 1 = High Drop Priority
qosBufferReservations
Internal, read-only value. This value adjusts the size of the ZL50410 internal buffers, which are used to store ingress packets.
qosBufferThresholds
Internal, read-only value. This value adjusts the ZL50410 internal buffer pool thresholds. When buffer usage in a pool exceeds its threshold the ZL50410 may either flow control or drop the incoming packet.
ipFlowControlThresholds
170
Provisioning
CardConfiguration
Attribute incomingCallQueueMode
Description Low-level software incoming rate limiting. This value changes how the switch arrives at a time interval to wait between handling MGCP:RsIP, SIP:REGISTER, and SIP:INVITE messages. Values are: Fixed. Uses incomingCallQueueIntervals Dynamic. The software will do its best to arrive at a good interval value based on processor usage.
CAUTION
Contact Taqua TAC Support before changing this value! incomingCallQueueIntervals Millisecond interval for low-level software incoming rate limiting. There is one interval for each supported protocol.
CAUTION
Contact Taqua TAC Support before changing any of these values! outgoingCallQueueIntervals Millisecond interval for low-level software outgoing rate limiting. There is one interval for each supported protocol.
CAUTION
Contact Taqua TAC Support before changing any of these values!
PIC 2 Cards show the following additional information. These are internal objects used by the system software.
Provisioning
171
CardConfiguration
PIC and PIC 2 Cards show the following additional information. This is an internal object used by the system software.
ipFlowControlThreshold
PIC and PIC 2 Cards show the information about their codecs. Sample output is displayed below:
codecList...................List (3 items) -> (1) <48aed10> Codec key..............Codec-0-1-1 codecType........G711 codecWeight......64 (100) maximumSession...32 (50) activeSessions...0 (0) (2) <48aecb0> Codec key..............Codec-0-1-1 codecType........G726 codecWeight......c8 (200) maximumSession...2e (46) activeSessions...0 (0)
172
Provisioning
CardConfiguration
(3) <48aec50> Codec key..............Codec-0-1-1 codecType........G729 codecWeight......c8 (200) maximumSession...30 (48) activeSessions...0 (0)
Attribute Description Default name for a codec Type of codec. A measure of the processing load placed on a DSP when using this codec Maximum number of sessions this codec can handle Count of the number of sessions this codec is currently handling.
Provisioning
173
CALEA
CALEA
CALEA is an acronym for Communications Assistance for Law Enforcement Act of 1994. CALEA requires that the switch support legal surveillance by remote Law Enforcement Agencies (LEAs) of subscribers in real time. The surveillance includes call-detail information and may also include call-content (voice) information for a surveillance. The following table describes the types of surveillances.
Table 1: CALEA Surveillance Surveillance Call Data (CD) Surveillance Connection TCP/IP Description Contains the following: Start Time, Stop Time, Calling Party, and Called Party of each call. Call Data Channels (CDCs) deliver this data. This is also called a Pen-Register, or Trap-andTrace surveillance. Call Content (CC) TCP/IP and trunks Contains the following: Surveillance in a T1 The voice content of the telephone call and the Call Content Channels (CCCs) for the call The CD surveillance data This is also called a Title III surveillance.
WARNING
Information about Law Enforcement A surveillance activities is confidential. If non-authorized personnel access this information, they could alert the subjects of the surveillance and interfere with lawful investigations. To maintain confidentiality, all CALEA commands (except the createPenGrp command) require a password (.
174
Provisioning
CALEA
Order of Provisioning
Order of provisioning for CALEA: l
Step
1 2
Action Create the Pen group database, see createPenGrp on page 176 Change the administrator password, see changePenPW on page 179 Add a LEA, see addLea on page 181 Add a subject: If the case requires Call Content, add T1 span(s) to the LEA, see addLeaSpan on page 183 Add a case, see addLeaCase on page 187 If the case requires Call Content, add voice channels to the case, see addVoiceChnl on page 189 Enable surveillance on the case, see startCaseMonitor on page 192 Monitor Control Description system level allows all monitoring on the switch does not disable LEA monitoring default value is enabled
3 4
LEA level allows the monitoring of cases on the LEA disables the monitoring of all cases for a LEA default value is enabled
case level controls monitoring for individual cases default value is disabled
By default, the Pen level and LEA level monitoring are enabled, but individual cases default to disabled. This allows the carrier to provision surveillance in advance of the surveillance start date. When the court order takes effect, all that need be done is to manually enable the cases individually.
CAUTION
Do not use the switch scheduler software to activate or deactivate cases automatically. The scheduler does not currently have password protection, which is required to ensure the confidentiality.
Provisioning
175
CALEA
<ocxSystemID> The Intercept Access Point (IAP) system identification text string. The LEA uses the IAP to distinguish messages sent to it from various switches.
Dependent Commands
After creating the Pen Group, change the Pen group password, see changePenPW
on page 179
All other CALEA commands. Run this command before any other CALEA commands.
176
Provisioning
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179 Remove all related cases and LEAs. Remove case data, see removeLeaCase on page 188 Remove LEA data, see removeLea on page 182
Syntax <admPW> Description The administrator password.
deletePenGrp pw
Provisioning
177
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179 Create the Pen group database, see createPenGrp on page 176 Stop Pen group database monitoring, see stopPenMonitor on page 191
178
Provisioning
CALEA
Default password - initially set by Taqua Administrator password - set by you and used with all CALEA commands
When you provision the Pen group database, both passwords are set to the same value oldpw. At that time, you can reset the default password to another value, which causes the administrator password to be set to the same value. After you change the administrator password, you cannot change the default password. You can change the administrator password at any time, but not back to the default value.
Syntax <oldPW> <newPW> [ADM:DEF] Description The current password (case sensitive). The new password (case sensitive). This specifies which password to change. If pwType is omitted, it is assumed to be ADM. If specified, pwType must be one of the following (case sensitive): DEF - default ADM - administrator
Prerequisites
Change the Pen group password, see changePenPW on page 179.
See createPenGrp on page 176.
Provisioning
179
CALEA
CL_T1 The timer that sets the interval between messages sent to the connecting LEA server in milliseconds. Range is from 10 to 1000. CL_T2 The timer for the card with the TCP/IP connection that determines the period, in milliseconds, between attempts to open a closed socket. Range is from 15000 to 3200000. CL_T3 The timer that sets the interval between connection test messages sent to the LEA. This time ranges between 60,000 and 3200000 minutes. If set to 0, the switch does not send connection test messages. <value> <admPW> The new integer value of the specified timer (measured in milliseconds). The administrator password.
Prerequisites
Change the Pen group password, see changePenPW on page 179.
See createPenGrp on page 176.
180
Provisioning
CALEA
addLea
Tip
If a single LEA has multiple data collection systems, each system will have its own IP Address and port. In this case, create a separate LEA for each data collection system.
<leaIPAddr>
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195 <leaPort> [FXO] <admPW> The IP port the LEA is using. Internal value The administrator password.
Prerequisites
Change the Pen group password, see changePenPW on page 179. Create the Pen group database, see createPenGrp on page 176. Change the Pen group password, see changePenPW on page 179.
Dependent Commands
After defining a LEA, you may add one or more T1 spans to deliver call-content information to the LEA's data collection device. In this situation, assign logical span numbers to the T1 spans to be dedicated to the LEA. Later, when the you add voice channels to the LEA's cases, the appropriate logical span number is used along with the T1 channels assigned for call-content delivery.
See addLeaSpan on page 183. See addLeaCase on page 187. See addVoiceChnl on page 189.
Provisioning
181
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Remove all cases in the LEA, see removeLeaCase on page 188. Stop LEA monitoring, see stopLeaMonitor on page 185.
removeLea fbi pw
182
Provisioning
CALEA
<admPW>
Prerequisites
Change the Pen group password, see changePenPW on page 179. Add the LEA, see addLea on page 181.
Dependent Commands
See addLeaCase on page 187. See addVoiceChnl on page 189. See startCaseMonitor on page 192.
Provisioning
183
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Add the LEA span, see addLeaSpan on page 183. Remove the voice channels, see removeVoiceChnl on page 190.
Dependent Commands
See removeVoiceChnl on page 190.
removeLeaSpan fbi 1 pw
184
Provisioning
CALEA
Description The name of the Law Enforcement Agency. The administrator password.
Prerequisites
Change the Pen group password, see changePenPW on page 179. Define the LEA, see addLea on page 181. Add case data, addLeaCase on page 187.
Tip
Disabling LEA-level monitoring disables all of the LEAs cases. When reenabling LEA-level monitoring, the cases remain disabled. You must manually re-enable the cases
Prerequisites
Change the Pen group password, see changePenPW on page 179. Start the LEA monitoring, see startLeaMonitor on page 185.
stopLeaMonitor fbi pw
Provisioning
185
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Define the LEA, see addLea on page 181. Stop LEA monitoring, see stopLeaMonitor on page 185.
Syntax <leaName> <attrType> Description The Law Enforcement Agency name. The name of the attribute to set. AttrName is one of the following (case sensitive): LEAIPADDR The IP address for the data collection device of the connecting LEA LEAPORT The port number for the data collection device of the connecting LEA <value> <admPW> The new value of the attribute. The administrator password.
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195
186
Provisioning
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Define the LEA, see addLea on page 181.
Syntax <leaName> <lealeaCaseID> <targetDirn> <interceptType> Description The Law Enforcement Agency name. The name assigned to the case. This value is usually provided by the LEA. The subjects directory number. The type of surveillance authorized for this subject. One of the following (case sensitive): CD Call Data CC Call Content + Call Data
NOTE: The switch allows a subject to be added to all provisioned LEAs, but only a maximum of 5 LEAs can monitor a subject at the same time (J-STD-25 requirement/limitation) <admPW> The administrator password.
Dependent Commands
If Call Content is authorized, assign logical spans and trunks for the call content surveillance. See addVoiceChnl on page 189.
See startCaseMonitor on page 192.
Provisioning
187
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Stop the case monitoring, see stopCaseMonitor on page 193. Remove voice channels, see removeVoiceChnl on page 190.
Dependent Commands
See stopCaseMonitor on page 193. See removeVoiceChnl on page 190.
188
Provisioning
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Define the LEA, see addLea on page 181. Add T1 span(s) to the LEA, see addLeaSpan on page 183. Add a case, addLeaCase on page 187.
Dependent Commands
See startCaseMonitor on page 192.
Provisioning
189
CALEA
Prerequisites
Add a voice channel, see addVoiceChnl on page 189.
Syntax <leaName> <lealeaCaseID > <logicalSpan> <chan> <admPW> Description The Law Enforcement Agency name. The name assigned to the case. The logical span number of the T1 span that corresponds with the voice channel The voice channel (1 - 24) for one leg of the subject's call. The administrator password.
190
Provisioning
CALEA
Dependent Commands
See createPenGrp on page 176.
Syntax <admPW>
Prerequisites
Change the Pen group password, see changePenPW on page 179.
See startPenMonitor on page 191.
stopPenMonitor pw
Provisioning
191
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. If a case's surveillance type requires call-content delivery, you cannot enable monitoring until the voice channels are provisioned. See addVoiceChnl on page 189. Define the LEA, see addLea on page 181. Add T1 span(s) to the LEA if required, see addLeaSpan on page 183. Add case data, addLeaCase on page 187. Add voice channels to the case, if required, addVoiceChnl on page 189.
192
Provisioning
CALEA
Prerequisites
Change the Pen group password, see changePenPW on page 179. Start case monitoring, see startCaseMonitor on page 192.
Syntax <leaName> <leaCaseID> <admPW> Description The Law Enforcement Agency name. The name assigned to the case. The administrator password.
Provisioning
193
CALEA
COURTORDER The alphanumeric characters that represent the court order. This field is for reference only. INTERCEPTTYPE The type of surveillance the case requires: - 1 for call-content surveillances (includes call-data) - 0 for call-data only surveillances STARTDATE date/time string (for reference only) STOPDATE date/time string (for reference only) <value> <admPW> The new value of the attribute. The administrator password.
Prerequisites
Change the Pen group password, see changePenPW on page 179. Add case data, see addLeaCase on page 187. Stop case level monitoring, see stopCaseMonitor on page 193. To change intercept type from CC to CD, see removeVoiceChnl on page 190. To change intercept type from CD to CC, see addVoiceChnl on page 189.
NOTE: The STARTDATE and STOPDATE attributes do not control the enabling and disabling of a case. Changing the INTERCEPTTYPE from call-content to call-detail does note remove the voice channels assigned to the case. You need to remove these voice channels, see removeVoiceChnl on page 190. Add voice channels before changing INTERCEPTTYPE from call-detail only to call-detail plus voice.
194
Provisioning
CALEA
<admPW>
Prerequisites
Change the Pen group password, see changePenPW on page 179.
See createPenGrp on page 176.
Prerequisites
Change the Pen group password, see changePenPW on page 179.
See createPenGrp on page 176.
purgePenLog pw
Provisioning
195
Carriers
Carriers
A carrier is a company that provides communication circuits. Each carrier attached to the switch has a Carrier Access Code (CAC), a list of capabilities, and routing information. Carriers assigned to a subscriber are chosen automatically, or the subscriber can over ride the carrier assignments by dialing 101 followed by the CAC. A Carrier has the following attributes:
attribute key code intraLata value name of carrier, for example ATT 4-digit carrier access code, for example 4321 for AT&T This attribute specifies the toll services that originate and terminate in the same Local Access and Transport Area (LATA). Possible values: NO The carrier does not offer toll services that originate and terminate in the same LATA, calls route to treatment. CarrierRoute If this carrier offers toll services that terminate in the same LATA, using a Carrier Route List route. NanpRoute The carrier offers toll services that terminate in the same LATA using the following routes in order of priority: Subscriber route NANP Route List route Carrier Route List route AniRoute The carrier offers toll services that terminate in the LATA using the following routes in order of priority: ANI Route List route Carrier Route List route Nonlocal_CarrierRoute The carrier offers toll services that terminate in the same LATA using the following routes in order of priority: Subscriber route Carrier Route List route Nonlocal_AniRoute The carrier offers toll services that terminate in another LATA using the following routes in priority order: Subscriber route ANI Route List route Carrier Route List route
196
Provisioning
Carriers
attribute interLata
value This attribute specifies the services that terminate in another LATA Possible values: NO The carrier does not offer toll services that originate and terminate in another LATA, calls route to treatment. CarrierRoute If this carrier offers toll services that terminate in another LATA, using a Carrier Route List route. NanpRoute The carrier offers toll services that terminate in another LATA using the following routes in order of priority: Subscriber route NANP Route List route Carrier Route List route AniRoute The carrier offers toll services that terminate in another LATA using the following routes in order of priority: ANI Route List route Carrier Route List route Nonlocal_CarrierRoute The carrier offers toll services that terminate in another LATA using the following routes in order of priority: Subscriber route Carrier Route List route Nonlocal_AniRoute The carrier offers toll services that terminate in another LATA using the following routes in priority order: Subscriber route ANI Route List route Carrier Route List route
Provisioning
197
Carriers
attribute international
value This attribute specifies the toll services that terminate in a different country. Possible values: NO The carrier does not offer international call service that originate and terminate in another LATA, calls route to treatment. CarrierRoute If this carrier offers international call service that terminate in another LATA, using a Carrier Route List route. NanpRoute The carrier offers international call service that terminate in another LATA using the following routes in order of priority: Subscriber route NANP Route List route Carrier Route List route AniRoute The carrier offers international call service that terminate in another LATA using the following routes in order of priority: ANI Route List route Carrier Route List route Nonlocal_CarrierRoute The carrier offers international call service that terminate in another LATA using the following routes in order of priority: Subscriber route Carrier Route List route Nonlocal_AniRoute The carrier offers international call service that terminate in another LATA using the following routes in priority order: Subscriber route ANI Route List route Carrier Route List route
198
Provisioning
Carriers
attribute worldZone1
value This attribute specifies the services to countries identified by the single-digit country code of 1 (Canada, and most Caribbean countries), not the U.S. Possible values: NO The carrier does not offer worldzone1 call service that originate and terminate in another LATA, calls route to treatment. CarrierRoute If this carrier offers worldzone1 call service that terminate in another LATA, using a Carrier Route List route. NanpRoute The carrier offers worldzone1 call service that terminate in another LATA using the following routes in order of priority: Subscriber route NANP Route List route Carrier Route List route AniRoute The carrier offers worldzone1 call service that terminate in another LATA using the following routes in order of priority: ANI Route List route Carrier Route List route Nonlocal_CarrierRoute The carrier offers worldzone1 call service that terminate in another LATA using the following routes in order of priority: Subscriber route Carrier Route List route Nonlocal_AniRoute The carrier offers worldzone1 call service that terminate in another LATA using the following routes in priority order: Subscriber route ANI Route List route Carrier Route List route
Provisioning
199
Carriers
attribute OSCapable
value This attribute specifies Operator Services. Possible values: NO The carrier does not offer operator services call service that originate and terminate in another LATA, calls route to default OS provider. CarrierRoute If this carrier offers operator services call service that terminate in another LATA, using a Carrier Route List route. NanpRoute The carrier offers operator services call service that terminate in another LATA using the following routes in order of priority: Subscriber route NANP Route List route Carrier Route List route AniRoute The carrier offers operator services call service that terminate in another LATA using the following routes in order of priority: ANI Route List route Carrier Route List route Nonlocal_CarrierRoute The carrier offers operator services call service that terminate in another LATA using the following routes in order of priority: Subscriber route Carrier Route List route Nonlocal_AniRoute The carrier offers operator services call service that terminate in another LATA using the following routes in priority order: Subscriber route ANI Route List route Carrier Route List route
200
Provisioning
Carriers
attribute DACapable
value This attribute specifies Directory Assistance services. Possible values: 0 NO The carrier does not offer directory assistance call service that originate and terminate in another LATA, calls route to default DA provider. CarrierRoute If this carrier offers directory assistance call service that terminate in another LATA, using a Carrier Route List route. NanpRoute The carrier offers directory assistance call service that terminate in another LATA using the following routes in order of priority: Subscriber route NANP Route List route Carrier Route List route AniRoute The carrier offers directory assistance call service that terminate in another LATA using the following routes in order of priority: ANI Route List route Carrier Route List route Nonlocal_CarrierRoute The carrier offers directory assistance call service that terminate in another LATA using the following routes in order of priority: Subscriber route Carrier Route List route Nonlocal_AniRoute The carrier offers directory assistance call service that terminate in another LATA using the following routes in priority order: Subscriber route ANI Route List route Carrier Route List route
OS01NXCode OS011NXCode
The 1NX code that is sent to this carrier for 01+ operatorassisted calls. The default value is 158. The 1NX code that is sent to this carrier for 011+ operatorassisted calls originating from pay stations (for example, pay telephones, hotels). The default value is 138.
Provisioning
201
Carriers
attribute routeCodesMap
value NOTE: routeCodesMap is an object with its own attributes. See the examples at the end of this command for usage. The 2-digit route code for each type of call that the switch sends when routing to this carrier over FGD. This is also called an OZZ code and the switch sends a 0 before the code. These codes need to match the code that the connecting switch is expecting. The connecting switch only uses this code if it routes calls using the carrier access code and the route code. As a default, the switch sends 00 for the route code. Attributes: local extendedArea calls to an extended area interLATA OAInterLATA Operator Assisted InterLATA calls intraLATA OAIntraLATA Operator Assisted IntraLATA calls international OAInternational Operator Assisted international calls worldZone1 OAWorldZone1 Operator Assisted World Zone 1 calls e911 Enhanced 911 calls DAIntraLATA Directory Assisted IntraLATA calls DAInterLATA Directory Assisted InterLATA calls OAZeroMinus Operator Assisted calls to 0 SAC Special Access Code (SAC) calls, typically 800 toll free numbers. A SAC query supplies one of the following: Telephone number where the call can be routed Carrier name that handles calls for that toll free number Range: 0 - 99
deniedInfoDigits NOTE: deniedInfoDigits is a list object. See the examples at the end of this command for usage. This attribute specifies which information digits that you want to block from an IC or OSS and send the default 00 digits instead. By default none of the digits are denied from routing to an OSS.
202
Provisioning
Carriers
attribute ANIKPType
value This attribute specifies the outpulsed tones on trunks using the FGCOS protocol to none so the KP tone (start of pulsing signal) is sent. Possible values: NONE KP tone (start of pulsing signal) is sent SIGNALING KP is sent if DTMF is used PRE_SUB KP is sent if the subscriber is presubscribed (CAC not dialed), KP is sent if the subscriber is not pre-subscribed (CAC dialed). BOTH KP is sent if DTMF is used and the subscriber is presubscribed (CAC not dialed), KP is sent if DTMF is used and the subscriber is not pre-subscribed (CAC dialed).
restrictions
This attribute specifies the restrictions assigned Type is Bitfield. These options are individually turned on or off by name. See example. Possible values: DA_ONLY Allow directory assistance calls only NO_CAC Do not allow CAC calls (101XXXX) NO_DA Do not allow directory assistance calls NO_OSDIALED Do not allow operator services (0+, 00, 0) calls NO_OSSTATION Do not allow operator service station (hotel, motel, etc.) calls NO_PRE_SUB Do not allow calls without a presubscribed carrier OS_ONLY Allow operator services calls only PRE_SUB_ONLY Allow calls with a pre-subscribed carrier only
Provisioning
203
Carriers
attribute circuitCodeForTNS
Transit Network Selection (TNS) parameter that includes the associated CAC or PCAC. The TNS is sent when using SS7 trunks. This circuit code is sent to the AT and the AT uses it to determine the call type and where to send the call.
Attributes: local extendedArea interLATA OAInterLATA intraLATA OAIntraLATA international OAInternational worldZone1 OAWorldZone1 e911 DAIntraLATA DAInterLATA OAZeroMinus SAC Follow the call type attribute with the circuit code sent in the optional Transit Network Selection (TNS) parameter, which includes the associated CAC or PCAC. The TNS is sent when using SS7 trunks. This circuit code is sent to the AT and the AT uses it to determine the call type and where to send the call. Range: 0 - 15
204
Provisioning
Carriers
attribute PCAC
value This attribute specifies the 4-digit PCAC of the carrier that is sent in the outgoing call setup signal. In standard call processing, the CAC in the outgoing signaling message is the same as the CAC used for routing. Use this field to send a different CAC in the signaling message than the switch uses to route the call.
NOTE: The switch uses the PCAC of the carrier if there is not a PCAC assigned to the associated prefix.
If the switch uses PRI signaling, it sends the PCAC in the SETUP message.
Provisioning
205
Carriers
The Generic CLI is used for all Carrier commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key code
code intraLata interLata international worldZone1 OSCapable DACapable OS01NXCode OS011NXCode routeCodesMap ANIKPType restrictions circuitCodeForTNS
PCAC
deniedInfoDigits
See Adding deniedInfoDigits to a Carrier on page 210 and Removing deniedInfoDigits from a Carrier on page 210.
create Carrier MCI 1234 modify modify modify modify Carrier Carrier Carrier Carrier MCI MCI ATT ATT restrictions OS_ONLY 0 circuitCodeForTNS extendedArea 1 routeCodesMap interLATA 23 PCAC 1212
206
Provisioning
Carriers
Dependent Commands
After creating a carrier modify its attributes, see modify on page 6. After creating a carrier assign it to:
NOTE: A tandem carrier route list uses the route codes assigned to a carrier, see Tandem Carrier RouteList on page 523.
A subscriber, see Subscribers on page 530. The directory assistance and operator services fields of the Office Parameter, see OS Provider on page 382 and DA Provider on page 382.
NOTE: A carrier must be OS or DA capable to be assigned as the default carrier in the office parameter, see OfficeParams on page 382.
A route list, see Carrier Route List on page 515. A subscriber, see Subscribers on page 530. The directory assistance and operator services fields of the Office Parameter, see OfficeParams on page 382.
CAUTION
Deleting a carrier may negatively affect operations.
Provisioning
207
Carriers
query Carrier
Tip
Use this command without a key to see which carriers have been provisioned on the switch.
query Carrier MCI <52c6120> Carrier key................."MCI" code................"1234" intraLata...........NO interLata...........NO international.......NO worldZone1..........NO OSCapable...........NO DACapable...........NO OS01NXCode..........9e (158) OS011NXCode.........8a (138) routeCodesMap.......<52c7840> <52c7840> CarrierRouteCodes local.............0 (0) extendedArea......0 (0) interLATA.........0 (0) OAInterLATA.......0 (0) intraLATA.........0 (0) OAIntraLATA.......0 (0) international.....0 (0) OAInternational...0 (0) worldZone1........0 (0) OAWorldZone1......0 (0) e911..............0 (0) DAIntraLATA.......0 (0) DAInterLATA.......0 (0) OAZeroMinus.......0 (0) SAC...............0 (0) deniedInfoDigits....<52c76c0> <52c76c0> InfoDigitsList valType......Integer collection...List (0 items) ->
208
Provisioning
Carriers
ANIKPType...........NONE restrictions........(BITFIELD) -> 0 circuitCodeForTNS...<52c7910> <52c7910> CircuitCode local.............0 (0) extendedArea......0 (0) interLATA.........0 (0) OAInterLATA.......0 (0) intraLATA.........0 (0) OAIntraLATA.......0 (0) international.....0 (0) OAInternational...0 (0) worldZone1........0 (0) OAWorldZone1......0 (0) e911..............0 (0) DAIntraLATA.......0 (0) DAInterLATA.......0 (0) OAZeroMinus.......0 (0) SAC...............0 (0) PCAC................<>
Provisioning
209
Carriers
<subkey>
Tip
Use a index of 1 to insert deniedInforDigits at the start of a carriers deniedInfoDigits list. Use a index of -1 to insert deniedInforDigits at the end of a carriers deniedInfoDigits list.
<subvalue>
This attribute specifies which information digits that you want to block from an IC or OSS and send the default 00 digits instead. By default none of the digits are denied from routing to an OSS.
The following command adds info digits "11" to the start of the deniedInfoDigits list for carrier ATT:
insertInto Carrier ATT deniedInfoDigits 1 11 Removing deniedInfoDigits from a Carrier deleteFrom Carrier <key> deniedInfoDigits <subkey>
Use the Generic CLI deleteFrom command to remove a value to a Carriers deniedInforDigits list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> subkey carrier name This attribute specifies which information digits you want to remove from the deniedInfoDigits list Description
The following command removes the info digits at the start of the deniedInfoDigits list for carrier ATT:
210
Provisioning
Action Create a NANP route list for the number that will trigger the Change Number Announcement (see NANP Route List on page 519 for more information about route lists). The following example creates a route list for subscriber 9724800013. We will call this Change Number Announcement route list CNA_9724800013, to help us remember which subscriber the announcement is for. In this example, we are going to pre-provision the CNA route list, so we want it to be intially inactive. create NANPRouteList CNA_9724800013 9724800013 9724800013 NO
Add the service to the route list (see Route Lists on page 514, and Adding a Route to a Route List on page 527 for more information). insertInto NANPRouteList CNA_9724800013 routes 1 CNASvc:2145301945 Note that the type of route list and the name of the route list were determined in step 1, and that routes is a keyword that must be used when inserting route into a route list. "1" is the positiion in the route list where we want to enter the service. Also, note that CNASvc: is a keyword that identifies the Change Number Announcement service, and "2145301945" is the changed number for the subscriber.
NOTE: If you omit the final ":" in "CNASvc" the announcement will omit the 1st digit of the new number!
3
At some later time, we will want to activate the Change Number Announcement for the subscriber. This is done with the Generic CLI modify command:
modify NANPRouteList CNA_9724800013 active YES
Provisioning
211
Tip
Use CNA with a range of directory numbers to provision NPA overlays.
Action Create a NANP route list for the range of directory numbers that will trigger the Change Number Announcement (see NANP Route List on page 519 for more information about route lists). The following example creates a route list for the range of directory numbers 9724800000 to 9724809999. We will call this Change Number Announcement route list CNA_97248, to help us remember the range of directory numbers in this route list. In this example, we are not going to pre-provision the CNA route list, because we want the changes to take place immediately. create NANPRouteList CNA_972480 9724800000 9724809999
Add the service to the route list (see Route Lists on page 514, and Adding a Route to a Route List on page 527 for more information). insertInto NANPRouteList CNA_972480 routes 1 CNASvc:214575XXXX See step 2 in the previous example for a discussion about the type and name of the route list. In this step, we want to concentrate on the format of the CNA number. In this example, "214575" replaces "972480". Each "X" in the string "XXXX" is a wildcard that allows the corresponding digit in the original dialed number to be used in the Changed Number Announcement. To illustrate: if a caller dials "9724800021", the announcement would be, The number you are calling, 9724800021, has been changed. Please make a note of the new number, 2145750021
212
Provisioning
Equipment Provisioning
Equipment Provisioning
lockFacility lockFacility <facilityOID>
This command places a facility (device) in an out-of-service administrative state. Syntax <facilityOID> Description facilityOID the Object Identifier of a trunk, line, span, fe, or ds3. See OID on page 30.
statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: UNLOCKED Master Administrative State: UNLOCKED Resource Status: ISV Resource Available?: YES lock line-1 statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: LOCKED Master Administrative State: UNLOCKED Resource Status: OOS Resource Available?: NO
Provisioning
213
Equipment Provisioning
statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: LOCKED Master Administrative State: UNLOCKED Resource Status: OOS Resource Available?: NO unlockFacility line-1 statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: UNLOCKED Master Administrative State: UNLOCKED Resource Status: ISV Resource Available?: YES
214
Provisioning
Equipment Provisioning
Tip
Once a facility has been shut down, use unlockFacility on page 214 to return it to service.
This command places a facility (device) in an administrative state where it does not accept new service requests, but keeps performing current activities until done.
Syntax <facilityOID>
Description facilityOID the Object Identifier of a trunk, line, span, fe, or ds3. See OID on page 30.
statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: UNLOCKED Master Administrative State: UNLOCKED Resource Status: ISV Resource Available?: YES shutdownFacility line-1 statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: LOCKED Master Administrative State: UNLOCKED Resource Status: OOS Resource Available?: NO
Provisioning
215
Equipment Provisioning
statusFacility line-1 ***** Status for Line-1-1-10 ***** Operational State: ENABLED Master Operational State: ENABLED Administrative State: LOCKED Master Administrative State: UNLOCKED Resource Status: OOS Resource Available?: NO
216
Provisioning
Equipment Provisioning
Tip
Tip: use queryAttrDefs on page 85 to see the list of facility attributes and their valid values, and queryFacility on page 69 to see the current attribute values of a specific facility.
Syntax <facilityOID>
Description facilityOID the Object Identifier of a trunk, line, span, fe, or ds3. See OID on page 30.
queryFacility line-1 (OID: 4a18001) <3f25020> Line key.........................<> objectID....................Line-1-1-10 dependentOIDs...............<> containerOID................Card-1-1-10 ringingType.................0 (0) modifyFacility line-1 ringingType 1 <done> queryFacility line-1 (OID: 4a18001) <3f25020> Line key.........................<> objectID....................Line-1-1-10 dependentOIDs...............<> containerOID................Card-1-1-10 ringingType.................1 (1)
Provisioning
217
Equipment Provisioning
The following example provisions a Primary and Secondary DNS on a Fast Ethernet Interface.
query fe-0 (OID: 4544000) <2a0dba0> FEIf key.........................<> objectID....................FE-0-1-5 dependentOIDs...............Array (25 items, zero items suppressed) -> [0] IntegerValue: IPTrunk-0-1-5 output trimmed to conserve space [24] IntegerValue: IPTrunk-24-1-5 primaryDns..................<> secondaryDns................<> inimumDnsTTL...............5 (5) modifyFacility fe-0 primaryDns 172.19.160.110 modifyFacility fe-0 secondaryDns 172.19.160.210 query fe-0 (OID: 4544000) <2a0dba0> FEIf key.........................<> objectID....................FE-0-1-5 dependentOIDs...............Array (25 items, zero items suppressed) -> [0] IntegerValue: IPTrunk-0-1-5 output trimmed to conserve space [24] IntegerValue: IPTrunk-24-1-5 primaryDns.................."172.19.160.110" secondaryDns................"172.19.160.210" minimumDnsTTL...............5 (5)
218
Provisioning
Equipment Provisioning
Provisioning
219
Equipment Provisioning
NailedUpCircuit
A NailedUpCircuit creates a nailed-up path between two trunks or spans and initiates a TDM connection between them. Nailed-up trunks/spans allow the switch to have a dedicated, non-switched path from an input DS0 port on a T1 to an output DS0 port on a T1. The nailed-up path through the switch does the following:
Guarantees transmission Prevents information on the path from being subject to call processing Provides a clear-channel (no signaling data) 64 Kbps connection between two trunks Provides a DS0 cross-connect function within the switch, eliminating external equipment for separating switched and non-switched circuits
circuit_B
The Generic CLI is used for all NailedUpCircuit commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
create NailedUpCircuit nailup-1 Trunk-4 query NailedUpCircuit nailup-1 <5ee11f0> NailedUpCircuit key........."nailup-1" circuit_A...Trunk-4-1-27 circuit_B...Trunk-8-1-27 destroy NailedUpCircuit nailup-1
Trunk-8
220
Provisioning
Equipment Provisioning
CAUTION
Use caution when setting timers on an RDTs facilities.
Prerequisites
Tip
Use this command to see a complete list of line timer names and attributes: queryAttrDefs SubscriberFacil ityTimers
Provisioning
221
Equipment Provisioning
222
Provisioning
FTRS
FTRS
The Flexible Translation, Routing and Signaling (FTRS) option alters the switchs call processing and customize digits. For more information on FTRS, see the T7000 Provisioning Guide. Provision FTRS by adding pretranslation tables, patterns and route, then adding the profile:
Step
1
Action Create the pretranslation table (see createPretranslation on page 223.) Add a pretranslation to the pretranslation table. (see addPretranslation on page 224.) Create a profile and associate a pretranslation table and/or a common route table with the profile (see FTRSProfile on page 231.). Assign the profile to a subscriber, trunk group, or the office parameters. (see Subscribers on page 530, Trunk Groups on page 233 or OfficeParams on page 382).
Provisioning
223
FTRS
A set of incoming digits that trigger FTRS. When the switch matches a pattern to the incoming digits, it applies FTRS. Inbound actions: Inbound actions change the digits, CAC, ANI II information digits, or ANI. This is done after digit collection is complete, but before screening and routing. Outbound digits: Outbound digits change to the outpulsed digits, CAC, ANI II information digits, or ANI, after the route is defined. Optional common routes. A common route changes the following outbound actions after screening:
Route type specifies the route that the call uses including: Carrier route, Route List or Subscriber. Outbound digits change to the outpulsed digits, CAC, ANI II information digits, or ANI, after the route is defined
Description The name of the pretranslation table This field defines the string you attach to the pretranslations table. Strings include a pattern, an inbound action and an outbound action. Enclose the string in quotation marks.
224
Provisioning
FTRS
Syntax pattern
Description Pattern Use a pattern to set incoming digits that the switch matches, then applies FTRS inbound actions. Digits from Subscribers 1 to 30 digits including, * and #. Digits from Trunks 0, 1, 2, 3, 4, 5, 6, 7, 8, 9. For CAS trunks, specify KP (Key Pulse signal) and ST (STart signal) values as follows: K KP B KP' (KP prime) C KP' '(KP double prime) A KP'' (KP triple prime) [ Any of the KP values (KP, KP, KP, or KP). S ST B ST' (ST prime) C ST'' (ST double prime) A ST''' (ST triple prime) ] Any of the ST values (ST, ST, ST, or ST). T Perform critical timing on a digit collection for a digit pattern. See CriticalDigitTimeout on page 391. After the critical timer expires, the switch declares the collected set of digits is complete and processes the call. T(n) The number of milliseconds the switch waits before indicating the collected set of digits is complete and processes the call, where n=0-30. Use T(n) after a specific digit string to lengthen or shorten the critical timer. For example, 0111504T2 shortens the critical timer to 2 seconds after collecting the specified digits. The default critical timer setting is 4 seconds, see OfficeParms Timers on page 391
Tip
When entering digit sequences, X matches any digit 0 - 9, and N matches any digit 2 - 9. To match a range of digits enter the first values of the range followed by a series of Xs. For example, to include all numbers from 9724800000 to 9724809999, type 972480XXXX.
Provisioning
225
FTRS
Syntax InboundActions
Description Inbound Actions change the digits, CAC, ANI II information digits, or ANI, after digit collection is complete but before screening and routing. /REM n, n removes from position n, n number of digits. For example, /REM 1, 3, removes 3 digits from position 1 (the first digit). /INS n, "digit string" inserts a digit string (parameter n, n position, digit string). For example, /INS 1,972480 inserts 972480 before the digit string. /VAR n collects one or more digits from the end of the pattern. Used for international numbers after the 7th digit. For example, / VAR 3, collects up to 3 more digits. /ANI n stores n digits from position 1 as the Automatic Number Identifier. For example, /ANI 10, store the next 10 digits as the ANI. /CAC n stores n digits from position 1 as the Carrier Access Code. For example, /CAC 4, stores the first four digits as the CAC. x/ESC profile name when the digit x is received FTRS escapes to another profile. This is used for IAD subscribers in a business group that press a number to get an outside line. /CLGDB X specifies a list of ANIs to match in addition to the called number before actions are applied. The ANIs themselves are in pretranslation table X.
226
Provisioning
FTRS
Syntax OutboundActions
Description Outbound Actions (these actions are triggered by the =) = CARRIER to modify the routing of a call by PIC or CAC and modify the outbound digits of the call. This is for calls that are routed by carrier. = routeListname to modify the outbound digits by the route list name, using the following route list type: NANP, LNP, Carrier, Tandem Carrier, Tandem Trunk Group, Tandem ANI using the route list name. If the exact name is not found, the switch searches for a matching pattern in the order of the route lists above. = SUBSCRIBER to send the call to the subscriber, you use the REM or INS option with this type of routing. /CAC for the CARRIER option, uses the Carrier Access Code to route the call. For example = CARRIER /CAC, routes the call to the CAC. /CAC XXXX for the CARRIER option, reroutes the call using the CAC that you enter. For example: = CARRIER /CAC 0333, reroutes the call using the 0333 CAC. /PIC 1 or /PIC 2 for the CARRIER option, uses the subscribers PIC1 (interLATA) or PIC2 (intraLATA) to reroute the call. /REM n, n(performed before a route is selected) removes from position n, n number of digits. For example, /REM 1, 3, removes 3 digits from position 1 (the first digit). /INS n, "digit string (performed before a route is selected) inserts a digit string (parameter n, n - position, digit string). For example, /INS 1,972480 inserts 972480 at position 1. /ANI XXXXXXXXXX outpulses digits as the ANI.
NOTE: Effective with Release 6.0, the /ANI outbound action has been enhanced. See examples.
/II XX outpulses specified digits as Information Digits /PCAC XXXX outpulse a Pseudo Carrier Access Code instead of the CAC. /DEST name sends the call to a common route table using the name you enter. /LNP overrides an FTRS outbound route action if an LNP route exists /CT alters the call type for a given digit pattern prior to outpulsing, resulting in modification of the outpulsed called number, ST digit, and digit sequences dependent on the outgoing trunk group protocol (0-17) see the T7000 Provisioning Guide for more information.
Provisioning
227
FTRS
Prerequisites
Create an FTRS profile, see FTRSProfile on page 231. Add an FTRS pretranslation table, see createPretranslation on page 223 Use the following models with the addPretranslation command:
addPretranslation <preTransKey> "pattern, inbound actions, = routeList routeListName, outbound actions" addPretranslation < preTransKey > "pattern, inbound actions, = CARRIER (/CAC, /CAC XXXX or /PIC) addPretranslation < preTransKey > "pattern, inbound actions, = SUBSCRIBER (/REM or /INS) addPretranslation < preTransKey > "pattern, inbound actions, /DEST destinationName
addPretranslation pretran972 "972480XXXX =SUBSCRIBER /REM 1,3" addPretranslation pretran972 "469480XXXX /REM 1, 3 /INS 1, 214 /DEST Local" addPretranslation pretran972 "972999XXXX /REM 4,3" addPretranslation pretran972 "972T /INS 4, 4801002" addPretranslation pretran972 "2144801031 /DEST Route1_214" addPretranslation pretran972 "8174801032 /REM 1,10 /INS 1, 2144801002 = CARRIER /CAC 0333" addPretranslation pretran972 "1002 /INS 1,214480 /DEST TenDigitIntraLata" addPretranslation pretran972 "469467X0XX = CARRIER /CAC 0333 /ANI 9724801001 /REM 1,6 /INS 1, 214480" addPretranslation pretran972 "469467000X = R2144801001 /REM 1, 10 /INS 1,2144801001" addPretranslation pretran972 "569480XXXX /REM 1, 3 /INS 1 214 = R2144801001"
The following examples demonstrate the new outbound ANI feature as of Release 6.0:
addPretranslation "972XXXXXXX = SUBSCRIBER /ANI 8174800000" # outpulse fixed ANI 8174800000 addPretranslation "XXXXXXXXXX = SUBSCRIBER /ANI 972XXXXXXX" # outpulse variable ANI 972XXXXXXX, only replace NPA
If Subscriber A (2144800000) calls 8174800000, the outpulse ANI will be 9724800000 using FTRS if Subscriber B (2144800001) calls 8174800000, the outpulse ANI will be 9724800001 using FTRS if Subscriber A or B calls 9724800000, the outpulse ANI will be 8174800000.
228
Provisioning
FTRS
Prerequisites
Create an FTRS profile, see FTRSProfile on page 231. Add an FTRS pretranslation table, see createPretranslation on page 223. Add a pretranslation to the pretranslation table, see addPretranslation on page 224.
Prerequisites
Create an FTRS profile, see FTRSProfile on page 231. Add an FTRS pretranslation table, see createPretranslation on page 223. Add an FTRS pretranslation, see addPretranslation on page 224.
removePretranslation PreTrans972 1
Provisioning
229
FTRS
Prerequisites
Create an FTRS profile, see FTRSProfile on page 231. Create an FTRS pretranslation table, see addPretranslation on page 224. deletePretranslation PreTrans972
230
Provisioning
FTRS
FTRSProfile
An FTRSProfile is a container for a rule pattern that applies to a specific subscriber, originating trunk group, or the entire office. A rule pattern is a pretranslation table and an optional common route table. After you build a profile, assign it to a subscriber, trunk group, or the office parameters. An FTRSProfile object has the following attributes:
Attribute key PretransKey RouteKey Description The name of the FTRS profile Optional name of the pretranslation table associated with the profile. Optional name of route table associated with the profile. Note: This is the name defined by using the /DEST syntax for the pretranslation. See createPretranslation on page 223.
The Generic CLI is used for all FTRSProfile commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
PretransKey RouteKey
Prerequisites
PretransKey RouteKey
NOTE: If a route list is provisioned for the modified FTRS digit string, a common route is not needed.
Provisioning
231
FTRS
Dependent Commands
Add the profile to a subscriber, trunk group or the office parameters, see Subscribers on page 530,Trunk Groups on page 233 and OfficeParams on page 382.
232
Provisioning
Trunk Groups
Trunk Groups
Tip
The trunk group name is used during CDR conversion. The AMA/EMI record is populated with the last four characters. Taqua recommends the trunk group names have 4 digit trunk group numbers. For example: CAS Trunk Groups start from 0000 PRI Trunk Groups start from 1000 ISUP Trunk Groups start from 2000 Hunt Groups start from 3000 IP Trunk Groups start from 4000 MGCP Trunk Groups start from 5000.
A trunk is a communication line between two switches. For example, a trunk could connect the T7000 to a Private Branch Exchange (PBX), or to another T7000.Trunk groups bundle one or more trunks that perform a similar function. The function is defined by the trunk group. Customer demand or call traffic determines when and where trunk groups are deployed. The switch supports the following types of trunk groups:
CAS, see CAS Trunk Groups on page 235 Clear Channel, see Clear Channel Trunk Groups on page 252 Interface Groups, Interface Groups on page 258 IP, see IP Trunk Groups on page 307 MGCP, see MGCP Trunk Group on page 359 Multi-Line Hunt Group, see Hunt Groups on page 273 PRI, see PRI Trunk Groups on page 286 SS7, see SS7 Trunk Groups on page 324
233
Trunk Groups
End Office (EO) routes calls to an Access Tandem (AT) with special routing information, for example: a Carrier Identification code and a route code. Access Tandem (AT) routes calls to Inter-exchange Carriers (ICs) using the incoming Carrier Identification code/route code, the incoming trunk group, or ANI from the EO.
NOTE: The software does not currently support Tandem Screening (SCP dips for N00 routing, 8xx service, LNP, and AIN triggers). The T7000 performs LNP screening and routing if the tandem routing type is set to NO_ROUTING and an LRN is received. T7000 performs an SCP dip and routing (as if the call were a subscriber origination) if an LRN is not received, but the prefix is set to ported. For all other tandem routing types, the T7000 routes based on called number.
Attribute <tandemRoutingType>
Values Tandem Routing Type attribute NONE Uses routing based on the dialed number, the subscribers carrier, or the LNP code CARRIER Forces the calls received on this trunk group to use incoming Tandem Carrier route lists TRUNKGROUP Forces the calls received on this trunk group to use incoming Tandem Trunk Group route lists ANI Forces the calls received on this trunk group to use incoming Tandem ANI route lists
Dependent Commands
If you selected the CARRIER tandem routing type, provision the Carrier Identification code and route codes for each carrier, see Carriers on page 196. If you selecting the TRUNKGROUP or AIN routing type, ensure the trunk protocol matches the protocol on the other end, see modifyProtocol on page 222. Provision tandem route lists and add routes, see Route Lists on page 514.
234
Trunk Groups
NOTE: The trunk group name cannot contain a semi-colon (;), nor can it consist of either the word ALL or the word all facilities A list of the facilities (trunks) in the trunk group. See Adding Facilities to a CAS Trunk Group on page 251, and Removing Facilities from a CAS Trunk Group on page 251. The timers for this trunk group. See CAS Trunk Group Timers on page 244. The options for this trunk group. See CAS Trunk Group Options on page 247. FIRST_AVAILABLE always select the first trunk available ROUND_ROBIN (default) sequentially rotate the use of trunks sendOAssistCalls sendDAssistCalls TRUE allow operator assisted calls FALSE (default) do not allow operator assisted calls TRUE allow directory assisted calls FALSE (default) do not allow directory assisted calls
235
Trunk Groups
Attribute tandemRoutingType
Description Sets the type of routing for calls received on the trunk group. For a discussion of this attribute, see The tandemRoutingType Trunk Group attribute on page 234. NO_ROUTING Uses routing based on the dialed number, the subscribers carrier, or the LNP code. Note: when custom tandem TG outpulsing is required, choose this option for the inbound tandem TG, and set the tandemCustomReplacement attribute to YES. CARRIER_ROUTING (default) Forces the calls received on this trunk group to use incoming Tandem Carrier route lists TRUNKGROUP_ROUTING Forces the calls received on this trunk group to use incoming Tandem Trunk Group route lists ANI_ROUTING Forces the calls received on this trunk group to use incoming Tandem ANI route lists
defaultDN
The default directory number when the trunk group connects to a PBX that needs to have default Primary IntraLATA or InterLATA Carrier (PIC). Also, add a default subscriber with this number to set the specific IntraLATA or InterLATA Carrier to bill the number correctly. see Subscribers on page 530 Length: 10
CAUTION
Only use a defaultDN for CAS trunk groups with a DIDMF or a DIDDTMF protocol.
NOTE: If assigned, the defaultDN becomes the default ANI for 911 calls made without a 10 digit ANI. See E911DefaultANI on page 242 restrictions The restrictions on this trunk group. See CAS Trunk Group Restrictions on page 250.
236
Trunk Groups
Attribute defaultNPA
Description The NPA to be added when 7-digits are received on an incoming trunk group. The switch adds the defaultNPA to the 7-digits and then routes on 10-digits. This defaultNPA must be a provisioned prefix, see Prefixes on page 403. Length: 3
NOTE: For DIDMF or DIDDTMF CAS trunks, the homeNPA of the defaultDN is added to the 7-digits, if available. If a defaultDN is not available, then the defaultNPA is used. For CAS trunks using FXO protocol, the homeNPA of the subscriber is added on the 7-digits replaceDestinationDigits TRUE allow the use of replacement destination digits (called number) on the trunk group. The switch replaces part or all of the destination digits depending on how the prefix is provisioned, see Subscribers on page 530, Destination Digit Replacement on page 346, and replacementMode on page 405. FALSE do not replace Destination Digits and send the dialed digits. REPLACE_IfNotPorted do not replace Destination Digits in the outgoing signaling messages if the called DN has a non-T7000 LRN associated with it replaceCarrier This attribute controls the use of a PCAC on the trunk
group.
TRUE allow the use of PCAC on the trunk group. The switch replaces the CAC depending on how the prefix or carrier is provisioned. See Prefixes on page 403, replacementMode on page 405, and Carriers on page 196. FALSE do not use a PCAC on the trunk group and send the CAC. REPLACE_IfNotPorted do not use a PCAC if the called number has an non-T7000 LRN associated with it and send the CAC.
237
Trunk Groups
Attribute replaceAniDigits
Description This attribute controls the use of a PANI II digits on the trunk group. TRUE allow the use of a Pseudo ANI (PANI) on the trunk group. The switch replaces the ANI (calling number) depending on how the prefix is provisioned, see Subscribers on page 530. FALSE do not use a PANI on the trunk group and send the ANI. REPLACE_IfNotPorted do not use a PANI if the called number has an non-T7000 LRN associated with it and send the ANI.
replaceInfoDigits
TRUE allow the use of a PANI II digits on the trunk group. The switch replaces the ANI II digits depending on how the prefix is provisioned,See Subscribers on page 530. FALSE do not use PANI II digits on the trunk group and send the ANI II digits on the facility. REPLACE_IfNotPorted do not use PANI II digits if the called number has an non-T7000 LRN associated with it and send the ANI II digits on the facility
ftrsProfile
The profile assigned to the incoming trunk group. This profile determines how the switch manipulates digits and routing. See FTRS on page 223.
NOTE: A subscriber profile takes precedence over an incoming trunk group profile. For example, if a subscriber has a profile assigned and is in a FXO trunk group with a profile, the switch uses the subscriber profile. For more information, consult the T7000 Provisioning Guide. replaceCSI
This controls the use of the Carrier Selection Information parameter in outgoing messages on the trunk group.
TRUE allow the use of a PCSI on the trunk group. The switch replaces the outpulse of the CSI parameter depending on how the prefix is provisioned, See Subscribers on page 530 FALSE do not send a PCSI on the trunk group and send the CSI. REPLACE_IfNotPorted do not use PCSI if the called number has an non- T7000 LRN associated with it and send the CSI.
238
Trunk Groups
Attribute localTermination
Description
The localTermination attribute controls if incoming trunk group allows for local terminations or not. If it does not allow for local terminations then use the trunk group in a tandem routing application. If you allow local terminations in a tandem routing trunk group, then if the DN terminates on the switch the calls for that DN will not be tandemed out of the switch.
ALLOW (default) allow incoming calls on the trunk group to terminate on the switch. NOT_ALLOWED only allow incoming calls to tandem through the switch.
tandemDefaultRoutingType
The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment.
miscOptions
The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs). An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415 and Prefixes on page 403.
denyAniList
239
Trunk Groups
Attribute direction
Description ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions.
NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch.
BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call tandemCustomReplacement Used to outpulse 7 digits for tandem calls. NO (default) no special outpulsing is performed. YES outpulse 7 digits for non-ported subscribers. See 7 Digit Tandem Call Outpulsing on page 409
240
Trunk Groups
Description
DIDMF See DIDMF on page 747. DIDDTMF See DIDDTMF on page 747. FGC See FGC on page 745. FGCB2 See FGCB2 on page 745. FGCOF See FGCOF on page 745. FGCOS See FGCOS on page 745. FGDAT See FGDAT on page 746. FGDATOS See FGDATOS on page 746. FGCVZOS See FGCVZOS on page 745. FGD (default) See FGD on page 745. FGDEOIC See FGDEOIC on page 746. FGDICEO See FGDICEO on page 746. FGDEOAT See FGDEOAT on page 746. FGDATEO See FGDATEO on page 746. DIDMF See DIDMF on page 747. DIDDTMF See DIDDTMF on page 747. WSMF2WAY See WSMF2WAY on page 747. FGDINC See FGDINC on page 746. FXO See FXO on page 746. WSMF2WAY See WSMF2WAY on page 747. signalingType This parameter is optional for all protocols except FXO and FXS. For these protocols, the signaling type must be either LOOPSTART or GROUNDSTART. For all other protocols, the signalingType defaults to EM numDestDigits the number of digits outpulsed. DEFAULT sets the number of destination digits to be outpulsed to ten 7 sets the number of destination digits to be outpulsed to seven 10 sets the number of destination digits to be outpulsed to ten numAniDigits the number of ANI digits outpulsed. DEFAULT sets the number of ANI digits to be outpulsed to ten 7 sets the number of ANI digits to be outpulsed to seven 10 sets the number of ANI digits to be outpulsed to ten
241
Trunk Groups
Attribute numInfoDigits
Description the number of informational digits OUTPULSED. DEFAULT sets the number of Information digits to be outpulsed to two 1 sets the number of Information digits to be outpulsed to one 2 sets the number of Information digits to be outpulsed to two
outPulseProfileKey E911DefaultANI
Used with the FGCOF protocol to customize outpulsing sequences. See See OutPulseProfile on page 397 This attribute is used to specify a 10 digit ANI when a 911 call is made and a 10 digit ANI is not received, and a defaultDN is not assigned to the Trunk Group.
The Generic CLI is used for CAS Trunk Group commands, see Using Generic CLI
Commands on page 6.
key
trunkProtolcol signalingType
242
timers options selectionMethod sendOAssistCalls sendDAssistCalls tandemRoutingType defaultDN restrictions defaultNPA replaceDestinationDigits replaceCarrier replaceAniDigits replaceInfoDigits ftrsProfile replaceCSI localTermination
Trunk Groups
facilities
See Adding Facilities to a CAS Trunk Group on page 251, and Removing Facilities from a CAS Trunk Group on page 251.
create CASTrunkGroup SWBELL-Plano modify CASTrunkGroup SWBELL-Plano sendOAssistCalls FALSE query CASTrunkGroup SWBELL-Plano destroy CASTrunkGroup SWBELL-Plano
243
Trunk Groups
244
Trunk Groups
Timer
Description
NOTE: A wink is used to signal acknowledge of a facility seizure and readiness to accept digits MinWinkDuration MinWinkDuration: the minimum duration which will qualify a brief incoming off hook signal as a wink. Default: 100 ms MaxWinkDuration MaxWinkDuration: the maximum duration which will be allowed when attempting to qualify an incoming off hook signal as a wink. If this duration is exceeded, the off hook will be declared as a sustained off hook. This may be interpreted by an E&M protocol as either an origination or an answer signal. Default: 350 ms WinkDuration WinkDuration is the duration of a wink signal that the T7000 will transmit outbound for E&M protocols. Default: 100 ms FlashDuration Limit for the duration that the switch sends a flash signal. Set this time for 100 ms in a Basic 911 configuration. See 911 over CAS on page 136. Default: 900 ms
CAUTION
Changing any of OffHook or OnHook T1 driver timers could adversely effect subscribers with dial pulse, see options on page 543 OffHookDigMax The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Default: 70 ms OffHookDigMin The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Default: 0 ms OnHookDigMax The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Default: 70 ms OnHookDigMin The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Default: 0 ms TerminatorDisconnectDelay The time for the terminating telephone to receive dial tone after the originating telephone hangs up. Range: 1,500 - 10,000 ms Default: 2,000
245
Trunk Groups
Timer LCFO_Duration
Description This is the duration of the Loop Current Feed Open (LCFO) signal. This forward disconnect signaling is required by some answering machines and voice mail systems to be longer than normal. 150 - 7,500 ms Default: 700
246
Trunk Groups
Outpulse as Dialed allows a switch acting as a local End Office (EO) to provide long distance service without having an InterLATA carrier provisioned. The local EO outpulses the dialed digits to the local tandem office. Then, the local tandem office, not the local EO, performs screening and translation on the dialed digits. For more information, see The T7000 Provisioning Guide. TRUE routes by and outpulses the exact digits the subscriber dials FALSE the switch translates the digits, chooses a call type and routes based on the call type (local, extended, intraLATA, interLATA, worldZone1, International, etc.). numOfDIDDigits Sets the number of direct inward dialing digits allowed (0-10) for trunk groups with DIDMF or DIDDTMF protocols. Range: 1 - 30 Default: 10
247
Trunk Groups
Attribute networkServices
Description Set BLV/BLI only on trunk groups coming from an operator station. You need one trunk group for each service. Allow for one of the following operator services: NONE (Default) Neither BLV or BLI. BLV Busy Line Verification allows an external operator to verify if a subscriber line is busy. An operator calling over a BLV trunk receives a busy signal if the line is busy or a ringback if the line is idle. BLI Busy Line Interrupt allows an external operator to interrupt a busy line. An operator calling over a BLI trunk interrupts the busy subscriber who can either drop the existing conversation and accept the operator call or continue with the existing conversation.
skipMinDigitsRestriction
TRUE If a subscriber enters less than the minimum number of digits required by a protocol, the switch collects the digits entered and tries to process the call. Use TRUE if the trunk group has an FTRS profile, which adds digits to meet the requirements. FALSE If a subscriber enters less than the minimum number of digits required by the protocol, the call does not complete.
fgc911MakeFirstSecond
ON changes the FGCVZOS protocol for 911 calls, outpulsing the second stage for the first stage and nothing for the second stage OFF no change to the outpulsing For DIDDTMF and DIDMF trunk groups: USE_ANI If ANI is received T7000 outpulses *ANI** If ANI not received and home NPA is stored with trunk group T7000 outpulses *HNPA** If ANI is not received and home NPA is not stored with trunk group T7000 outpulses *** USE_DNIS T7000 outpulses **DNIS* USE_BOTH If ANI is received and home NPA is stored with trunk group T7000 outpulses *ANI*DNIS* If ANI not received and home NPA is stored with trunk group T7000 outpulses *HNPA*DNIS* If ANI not received and home NPA is not stored with trunk group T7000 outpulses **DNIS* NO (default)
useANIDNIS
248
Trunk Groups
Attribute routeOnRcvdCarrier
Description InbCarrier_OutbCarrier route on the Incoming Carrier if available, otherwise, route on the Outbound Carrier. InbCarrier_only route on the Incoming Carrier only. OutbCarrier_InbCarrier (default) route on the Outbound Carrier, if available, otherwise, route on the Incoming Carrier. OutbCarrier_only route on the Outbound Carrier only.
NOTE: The incoming carrier is the outpulsed carrier value received on CAS trunk groups diddtmfProvideDialtoneAf Enables the T7000 to provide dial tone directly after sending a terWink wink. Two situations where this could be useful: 1. When the T7000 is connected to a PBX: here, a PBX subscriber could dial 9 for an outside line. After the PBX seizes an E&M circuit and the T7000 acks the seizure with the standard wink supervision, the T7000 would then provide dial tone and collect digits. From the point of view of the PBX subscriber, it would seem as though he were connected directly to the T7000. 2. When the T7000 is connected to an IVR system, the IVR can redirect calls back out to the network. Contact Taqua Technical support for configuration details. The feature is only for DTMF E&M, not MF E&M. Most users do not have an MF capable phone. ON The switch provides dial tone after a wink. OFF (default) The switch does nothing special after a wink.
modify CASTrunkGroup SWBELL-Plano options skipMinDigitsRestriction TRUE modify CASTrunkGroup SWBELL-Plano options glareControl ODD
249
Trunk Groups
NO_INBOUND_WITHOUT_ Does not allow calls that do not include the ANI. ANI
The CAS Trunk Group restrictions attribute is a bit field, so individual values are:
modify modify
250
Trunk Groups
Adding Facilities to a CAS Trunk Group insertInto CASTrunkGroup <key> facilities <subkey> <subvalue>
Use the Generic CLI insertInto command to add a trunk to a CAS Trunk Groups facilities list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
Tip
Use a index of 1 to insert a facility at the start of the facilities list. Use a index of -1 to insert a facility at the end of the facilities list.
<subvalue>
This attribute specifies which trunk you want to add to the Trunk Group.
The following command adds trunk 0 on the local card to CAS Trunk Group SWBELL-Plano:
insertInto CASTrunkGroup SWBELL-Plano facilities 1 TGFacility trunk-0
Removing Facilities from a CAS Trunk Group deleteFrom CASTrunkGroup <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a trunk to a CAS Trunk Groups facilities list. See the deleteFrom example on page 21 for a detailed explanation of this command.
NOTE: You must first lock the Trunk before you can remove it from the Trunk Group.
Syntax <key>
Description
<subkey>
The following example locks trunk 0 on the local card and then removes it from CAS Trunk Group SWBELL-Plano:
SWBELL-Plano facilities 1
251
Trunk Groups
error-checking to ensure the trunks added are not in another trunk group different modes of route selection (first available, round robin) automatic deletion of routes upon trunk group deletion
NOTE: The trunk group name cannot contain a semi-colon (;), nor can it consist of either the word ALL or the word all facilities A list of the facilities (trunks) in the trunk group. See Adding Facilities to a Clear ChannelTrunk Group on page 257, and Removing Facilities from a Clear ChannelTrunk Group on page 257. FIRST_AVAILABLE always select the first trunk available ROUND_ROBIN (default) sequentially rotate the use of trunks defaultNPA The NPA to be added when 7-digits are received on an incoming trunk group. The switch adds the defaultNPA to the 7digits and then routes on 10-digits. This defaultNPA must be a provisioned prefix, see Prefixes on page 403. Length: 3 replaceDestinationDigit TRUE allow the use of replacement destination digits s (called number) on the trunk group. The switch replaces part or all of the destination digits depending on how the prefix is provisioned, See Subscribers on page 530, Destination Digit Replacement on page 346, and replacementMode on page 405. FALSE do not replace Destination Digits and send the dialed digits. REPLACE_IfNotPorted do not replace Destination Digits in the outgoing signaling messages if the called DN has a nonT7000 LRN associated with it
selectionMethod
252
Trunk Groups
Attribute replaceCarrier
group.
TRUE allow the use of PCAC on the trunk group. The switch replaces the CAC depending on how the prefix or carrier is provisioned. See Prefixes on page 403, replacementMode on page 405, and Carriers on page 196. FALSE do not use a PCAC on the trunk group and send the CAC. REPLACE_IfNotPorted do not use a PCAC if the called number has an non-T7000 LRN associated with it and send the CAC. replaceAniDigits
This attribute controls the use of a PANI II digits on the trunk group.
TRUE allow the use of a Pseudo ANI (PANI) on the trunk group. The switch replaces the ANI (calling number) depending on how the prefix is provisioned, see Subscribers on page 530. FALSE do not use a PANI on the trunk group and send the ANI. REPLACE_IfNotPorted do not use a PANI if the called number has an non-T7000 LRN associated with it and send the ANI.
replaceInfoDigits
TRUE allow the use of a PANI II digits on the trunk group. The switch replaces the ANI II digits depending on how the prefix is provisioned,See Subscribers on page 530. FALSE do not use PANI II digits on the trunk group and send the ANI II digits on the facility. REPLACE_IfNotPorted do not use PANI II digits if the called number has an non-T7000 LRN associated with it and send the ANI II digits on the facility
ftrsProfile
The profile assigned to the incoming trunk group. This profile determines how the switch manipulates digits and routing. See FTRS on page 223.
NOTE: A subscriber profile takes precedence over an incoming trunk group profile. For example, if a subscriber has a profile assigned and is in a FXO trunk group with a profile, the switch uses the subscriber profile. For more information, consult the T7000 Provisioning Guide.
253
Trunk Groups
Attribute replaceCSI
Description
This controls the use of the Carrier Selection Information parameter in outgoing messages on the trunk group.
TRUE allow the use of a PCSI on the trunk group. The switch replaces the outpulse of the CSI parameter depending on how the prefix is provisioned, see Subscribers on page 530 FALSE do not send a PCSI on the trunk group and send the CSI. REPLACE_IfNotPorted do not use PCSI if the called number has an non- T7000 LRN associated with it and send the CSI.
localTermination
The localTermination attribute controls if incoming trunk group allows for local terminations or not. If it does not allow for local terminations then use the trunk group in a tandem routing application. If you allow local terminations in a tandem routing trunk group, then if the DN terminates on the switch the calls for that DN will not be tandemed out of the switch.
ALLOW (default) allow incoming calls on the trunk group to terminate on the switch. NOT_ALLOWED only allow incoming calls to tandem through the switch.
tandemDefaultRouting Type
The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment.
miscOptions
The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs). An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415 and Prefixes on page 403.
denyAniList
254
Trunk Groups
Attribute direction
Description ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions.
NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch.
BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call
All Clear Channel Trunk Group commands use the Generic CLI, see Using Generic
CLI Commands on page 6.
key
There are no optional parameters for the create command. The modify command applies to the following attributes:
selectionMethod defaultNPA replaceDestinationDigits replaceCarrier replaceAniDigits replaceInfoDigits ftrsProfile replaceCSI localTermination tandemDefaultRoutingType denyAniList direction
255
Trunk Groups
facilities
See Adding Facilities to a Clear ChannelTrunk Group on page 257, and Removing Facilities from a Clear ChannelTrunk Group on page 257.
create CLRTrunkGroup SWB2 modify CLRTrunkGroup SWB2 direction ONE_WAY_IN query CLRTrunkGroup SWB2 destroy CLRTrunkGroup SWB2
256
Trunk Groups
Adding Facilities to a Clear ChannelTrunk Group insertInto CLRTrunkGroup <key> facilities <subkey> TGFacility <subvalue>
Use the Generic CLI insertInto command to add a trunk to a Clear Channel Trunk Groups facilities list. See theinsertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
Tip
Use a index of 1 to insert a facility at the start of the facilities list. Use a index of -1 to insert a facility at the end of the facilities list.
<subvalue>
This attribute specifies which trunk you want to add to the Trunk Group.
The following command adds trunk 0 on the local card to Clear Channel Trunk Group SWB2:
insertInto CLRTrunkGroup SWB2 facilities 1 TGFacility trunk-0
Removing Facilities from a Clear ChannelTrunk Group deleteFrom CLRTrunkGroup <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a trunk to a Clear Channel Trunk Groups facilities list. See thedeleteFrom example on page 21 for a detailed explanation of this command.
NOTE: You must first lock the Trunk before you can remove it from the Trunk Group.
Syntax <key>
Description
<subkey>
The following example locks trunk 0 on the local card and then removes it from Clear Channel Trunk Group SWB2:
SWB2 facilities 1
257
Trunk Groups
Use an Interface Group to connect the switch to an RDT using GR-303. An Interface Group consists of at least two, and as many as 28 T1 spans. These spans connect the T7000 to an RDT. The primary T1 span carries the primary Embedded Operations Channel (EOC) and the Timeslot Management Channel (TMC). The secondary T1 span contains carries the secondary EOC and TMC, which provide redundancy when the primary EOC and TMC are unusable. The remaining trunks in the spans are used to carry voice traffic between the switch and the RDT. Additional spans may be added to the Interface Group to provide even more capacity. A Interface Group has the following attributes.
Attribute key Description trunk group name. See the suggested naming convention for Trunk Groups on page 233.
NOTE: The trunk group name cannot contain a semicolon (;), nor can it consist of either the word ALL or the word all facilities A list of the facilities (trunks) in the trunk group. See Adding Facilities to an Interface Group on page 272, and Removing Facilities from an Interface Group on page 272. The timers for this trunk group. See Interface Group Timers on page 263. The options for this trunk group. See Interface Group Options on page 269. FIRST_AVAILABLE always select the first trunk available ROUND_ROBIN (default) sequentially rotate the use of trunks sendOAssistCalls sendDAssistCalls TRUE allow operator assisted calls FALSE (default) do not allow operator assisted calls TRUE allow directory assisted calls FALSE (default) do not allow directory assisted calls
258
Trunk Groups
Attribute tandemRoutingType
Description Sets the type of routing for calls received on the trunk group. For a discussion of this attribute, see The tandemRoutingType Trunk Group attribute on page 234. NO_ROUTING (default) Uses routing based on the dialed number, the subscribers carrier, or the LNP code CARRIER_ROUTING Forces the calls received on this trunk group to use incoming Tandem Carrier route lists TRUNKGROUP_ROUTING Forces the calls received on this trunk group to use incoming Tandem Trunk Group route lists ANI_ROUTING Forces the calls received on this trunk group to use incoming Tandem ANI route lists
restrictions defaultNPA
The restrictions on this trunk group. See Interface Group Restrictions on page 271. The NPA to be added when 7-digits are received on an incoming trunk group. The switch adds the defaultNPA to the 7-digits and then routes on 10-digits. This defaultNPA must be a provisioned prefix, see Prefixes on page 403. Length: 3 ALLOW (default) allow incoming calls on the trunk group to terminate on the switch. NOT_ALLOWED only allow incoming calls to tandem through the switch.
localTermination
tandemDefaultRoutingType
The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment.
miscOptions
The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs).
259
Trunk Groups
Attribute denyAniList
Description An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415, and Prefixes on page 403. ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions. NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch. BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call
direction
vendor
the company that manufactured the RDT connected to this trunk group. Values are: If you are connecting to a Nortel RDT, you must enter "nortel" (without the quotes") If you are connecting to a Tollbridge RDT, you must enter "tollbridge" (without the quotes")
location primarySpanOID
the location of the RDT. This is an informational field, and does not affect the operation of the switch Object ID of the Primary T1 Span for this Interface Group. This span is used for the Primary Embedded Operations Channel (EOC), EOC Path Protection Switch (PPS), Timeslot Management Channel (TMC), and the TMC PPS. See OID on page 30. NOTE: The switch automatically assigns the 12th timeslot (trunk 11) to the EOC and the 24th timeslot to the TMC (trunk
primarySpanLogicalID
Logical value the Primary T1 Span for this Interface Group. Range: 1 - 28.
260
Trunk Groups
Attribute secondarySpanOID
Description Object identifier of the span the EOC backup and TMC backup use after PPS has occurred. See OID on page 30. The switch automatically assigns the 12th timeslot (trunk11) to the EOC and the 24th timeslot to the TMC (trunk23).
Logical value the Secondary T1 Span for this Interface Group. Range: 1 - 28. Shows the OID, service state and path status of the Primary EOC. Shows the OID, service state and path status of the Secondary EOC. Shows the OID, service state and path status of the Primary TMC. Shows the OID, service state and path status of the Secondary TMC. This debug attribute controls how the switch shows ISDN Call Establishment, Call Clearing, Maintenance and Miscellaneous messages. The messages are displayed when running a CLI session on the card that has the active TMC. Values are: MSG_TRACE_NONE (default) The message trace for this trunk group is off. MSG_ONLY Shows the ISDN messages MSG_WITH_INBOUND_DUMP Shows ISDN messages and a dump of inbound IEs. MSG_WITH_OUTBOUND_DUMP Shows ISDN messages and a dump of outbound IEs. MSG_WITH_BOTH_DUMP Shows ISDN messages and a dump of both inbound and outbound IEs.
CAUTION
Contact Taqua TAC Support before using this option. flowThroughProvisioning NO_EOC the RDT does not support messaging over the EOC interface NO the RDT supports messaging over the EOC interface, but does not allow flow-through provisioning YES the RDT allows for flow-through provisioning using the OM GUI or T7000 CLI
261
Trunk Groups
The Generic CLI is used for all Interface Group commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
flowThroughProvisioning
timers options selectionMethod sendOAssistCalls sendDAssistCalls tandemRoutingType restrictions defaultNPA localTermination tandemDefaultRoutingType denyAniList direction isdnMsgTrace flowThroughProvisioning
facilities
See Adding Facilities to an Interface Group on page 272, and See Removing Facilities from an Interface Group on page 272.
create InterfaceGroup AFCUMC1 Richardson AFC span-0-2 1 span-1-3 2 1 modify InterfaceGroup AFCUMC1 sendOAssistCalls FALSE query InterfaceGroup AFCUMC1 timers destroy InterfaceGroup AFCUMC1
262
Trunk Groups
263
Trunk Groups
Timer MaxWinkDuration
Description MaxWinkDuration is the maximum duration which will be allowed when attempting to qualify an incoming off hook signal as a wink. If this duration is exceeded, the off hook will be declared as a sustained off hook. This may be interpreted by an E&M protocol as either an origination or an answer signal.
NOTE: A wink is used to signal acknowledgment of a facility seizure and readiness Default: 350 ms to accept digits. WinkDuration
WinkDuration is the duration of a wink signal that the T7000 will transmit outbound for E&M protocols Default: 200 ms Limit for the duration that the switch sends a flash signal. Default: 900 ms The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Changing this T1 driver timer could adversely effect subscribers with dial pulse, see options on page 543. Default: 70 ms The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Changing this T1 driver timer could adversely effect subscribers with dial pulse, see options on page 543. Default: 0 ms. The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Changing this T1 driver timer could adversely effect subscribers with dial pulse, see options on page 543. Default: 70 ms The timer that allows the T1 driver to detect dial pulse, for rotary dialing. Changing this T1 driver timer could adversely effect subscribers with dial pulse, see options on page 543. Default: 0 ms. The time for the terminating telephone to receive dial tone after the originating telephone hangs up. Range: 1,500 - 10,000 ms Default: 2,000 ms
FlashDuration OffHookDigMax
OffHookDigMin
OnHookDigMax
OnHookDigMin
TerminatorDisconnectDelay
LCFO_Duration
This is the duration of the Loop Current Feed Open (LCFO) signal. This forward disconnect signaling is required by some answering machines and voice mail systems to be longer than normal. Range: 150 - 7,500 ms Default: 700 ms
264
Trunk Groups
Timer T301
Description The time between receiving an ALERT message and receiving a CONNECT message. Clears the call when the timer expires, not used with a network supervision call control. Network side timer. Default: 180,000 ms The time between sending SETUP and receiving a CONNECT from the IDT. Sends a SETUP message when the timer expires. Network side timer. Default: 4,000 ms
T303
T305
The time between sending a disconnect without progress indicator and receiving the same or a REL (release) message. The network sends a REL message when the timer expires. Clears the call when a REL COMPLETE message is received. Network side timer. Default: 30,000 ms
T306
Started instead of T305 when the toneOption is set in the PRI group (see toneOption on page 296). In this case, the switch will to play the tone or announcement (whatever is appropriate) instead of the device handling that itself. Network side timer. Default: 30,000 ms The time between sending a SUSPEND ACK message and sending a RES (resume) ACK message. Clears the network connection when the timer expires. Network side timer. Default: 180,000 ms The time between sending and receiving a REL message. Resends a REL message and resets when the timer expires. Network side timer. Default: 4,000 ms
T307
T308
T309
The time between data link disconnection and data link reconnection. The network channel clears and the B channel releases when the timer expires. Network side timer. Default: 90,000 ms
265
Trunk Groups
Timer T310
Description The time between receipt of Call Proceeding and the next message (Alert, Connect, or Disconnect) is received. Network side timer. Default: 10,000 ms NOTE: The switch supports this timer, but IDTs do not send Call Proceeding.
T313
The time between sending a RESUME request and receiving a RESUME ACK message. Sends a DISC (disconnect) messages when the timer expires. User side timer. Default: 4,000 ms
T316
The time between sending a RESTART message and receiving a RESTART ACK message. RESTART message may be sent several times after the timer expires. Network and user side timer. Default: 30,000 ms The time between receiving a RESTART message and the internal clearing of call reference. The switch sends a maintenance notification when the timer expires. Set at less than the value of T316. Network and user side timer. Default 20,000 ms The time between sending a RESUME request and receiving a RESUME ACK or RESUME REJ (reject) message. The switch sends a release message when the timer expires. User side timer. Default: 4,000 ms The time between sending a SUSPEND message and receiving a SUSPEND ACK or SUSP (suspend) REJ message. The device enters an active state when the timer expires. User side timer. Default: 4,000 m The time between a D-channel failure and receiving a response to a layer 3 message. The switch sends a DLESTABLISHMENT message request on both channels when the timer expires. Network and user side timer. Default: 40,000 ms The time between sending a STATUS ENQ message and receiving a STATUS DISC, REL, or REL COMPLETE message. Sends STATUS ENQ when the timer expires. Network and user side timer. Default: 4,000 ms
T317
T318
T319
T321
T322
266
Trunk Groups
Timer RotaryDialingGuardTimer
Description Allows for pulse dialing by ignoring all messages until the timer times out. This rejects messages from RDTs that send immediate off-hook and keeps the switch from interpreting the off-hook as a digit. Default 400 ms The amount of delay between messages sent over the EOC. Do not set this timer to less than 500 ms. Any value less could lead to system instability. Default: 500 ms The delay between the time the switch receives "Connect Ack" and the time it checks for offhook or onhook on the signaling bits on the trunk. The delay is needed to account for timing sensitivities in the driver. Range: 500 - 2,000 ms Default: 700 ms
EOCMessageDelay
SignalBitAuditDelay
CRVReserveTime
The amount of time between reserving a CRV and assigning a trunk to that CRV. If this timer expires before the CRV has a trunk assigned, the CRV is removed from the reserved state and made available. Range: 1,000 - 20,000 ms Default: 10,000 ms
hdlcErrorInterval
Tip
The flexibility of being able to set both the interval and the water marks let you react to either error spikes (a burst of errors in a short period of time) or a "trickle" of errors over a longer period of time.
The Error Interval is used with the "high" and "low" water marks to determine how tolerant the switch will be with respect to detected errors. See hdlcErrorLowWaterMark on page 302 and hdlcErrorHighWaterMark on page 303. The switch counts errors on the link for the duration of the hdlcErrorInterval. If the low water mark is "10", and 10 errors occur during the 10 second interval, the switch issues a warning. If the high water mark is reached during the interval, the switch takes the link down. After the interval expires, the timer and the error counts are reset and the switch starts counting again from zero. Range: 1,000 60,000 ms Default: 10,000 ms
267
Trunk Groups
Timer sendResponseTime
Description The number of milliseconds the bearer circuit waits after sending a circuit status update for an acknowledgement from the signaling circuit. If no acknowledgement is received, the timer expires and the status is retransmitted. Range: 1,000 60,000 ms Default: 5,000 ms
CAUTION
Contact Taqua TAC Support before changing this timer.
modify InterfaceGroup AFCUMC1 timers hdlcErrorInterval 30000
268
Trunk Groups
269
Trunk Groups
hdlcErrorHighWaterMark
The number of errors that can occur on the link during the hdlc Error Interval before the switch takes the link out of service. Once the errors reach the high water mark, the link is immediately removed from service. It will not come back into service until someone acknowledges (clears) the alarm which requires manual intervention. If the value is zero, the switch will never take the link out of service, no matter how many errors occur on the link. See hdlcErrorInterval on page 295. Default: 0 NOTE: For backward compatibility, the default value (zero) disables this feature. Values greater than zero enable the feature. Also note, the switch does not mind if the High Water Mark is actually lower than the Low Water Mark (in this case, the warning is never issued, but the alarm is issued and the link is taken out of service when the number of errors exceeds the High Water Mark).
reoriginateWithoutRelease ON when the terminator leaves the phone off hook (after the originator hangs up), the line will remain connected to the original trunk as it proceeds with call reorigination (playing dial tone, etc). If no digits are entered, and the phone is left off hook long enough, the line will enter the Permanent Signal state, and the T7000 sends a Disconnect with Cause Code = 27. OFF send Disconnect with Normal Clearing after the timer expires.
modify InterfaceGroup AFCUMC1 options reoriginateWithoutRelease ON
270
Trunk Groups
The Interface Group restrictions attribute is a bit field, so individual values are:
modify modify
271
Trunk Groups
Adding Facilities to an Interface Group insertInto InterfaceGroup <key> facilities <subkey> RdtLogicalSpan <oid> <cic>
Use the Generic CLI insertInto command to add a span to a Interface Groups facilities list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> <subkey> Interface Group name This is the index in the facilities list where you want to enter the facility. Range: 1 - 28 Description
Tip
Use a index of 1 to insert a facility at the start of the facilities list. Use a index of -1 to insert a facility at the end of the facilities list.
<oid>
This attribute specifies which span you want to add to the Interface Group.
<logicalSpan This attribute specifies the Logical Span Number of the inserted Span. Number>
The following command adds Span 1 in Card 2 as Logical Span number 3 to Interface Group AFCUMC1:
insertInto InterfaceGroup AFCUMC1 facilities 3 RdtLogicalSpan Span-1-2-27 3
Removing Facilities from an Interface Group deleteFrom InterfaceGroup <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a span from an Interface Groups facilities list. See the deleteFrom example on page 21 for a detailed explanation of this command.
NOTE: You must first lock the Span before you can remove it from the Interface Group.
Description This is the index in the facilities list where you want to remove the facility.
The following example locks Span 1 on the local card and then removes it from PRI Trunk Group SWB1:
AFCUMC1
facilities 3
272
Trunk Groups
Hunt Groups
The following types of hunts are associated with a multi-line hunt group: 1. Regular hunting this type of hunt begins with the terminal dialed and ends with the last terminal in the hunt group 2. Uniform Call Distribution (UCD) this is the default type of hunt group 3. Circular hunting this type of hunt beings with the terminal following the most-recently-used terminal and ends with the terminal immediately preceding the starting terminal. Any start hunt information is ignored, since it chooses the start hunt point based on the last terminal dialed.
NOTE: Use the Generic CLI modify command to change the type of hunt used, see selectionMethod on page 274.
Action Create or select a subscriber for the pilotLDN. see Subscribers on page 530 Make sure the subscriber has a facility. The subscriber chosen for the PilotLDN cannot have any of the following services: Call Waiting Caller ID Hot Line Revertive Call Warm Line In addition, the pilotLDN subscriber can not be an Enhanced Voice Services subscriber.
Create the Hunt Group using the subscriber from step 1 as the pilotLDN. You may also specify an optional overflowDN at this time. This is usually the DN of a Voice Mail System. Note that the subscriber chosen for the overflowDN can not have the Revertive Call service, or be an Enhanced Voice Services subscriber. See Creating a Hunt Group on page 279.
Add the pilotLDN facility to the Hunt Group. See Adding Facilities to a Hunt Group on page 281.This subscribers facility is Terminal 0, or the first terminal. Add additional facilities to the Hunt Group. See Adding Facilities to a Hunt Group on page 281.
273
Trunk Groups
NOTE: The trunk group name cannot contain a semicolon (;), nor can it consist of either the word ALL or the word all. facilities A list of the facilities (trunks) in the Hunt Group. See Adding Facilities to a Hunt Group on page 281, and Removing Facilities from a Hunt Group on page 283. The timers for this Hunt Group. Hunt Groups use CAS Trunk Group Timers, see CAS Trunk Group Timers on page 244. The options for this trunk group. Hunt Groups use CAS Trunk Group options. See CAS Trunk Group Options on page 247. REGULAR_HUNT This type of hunt begins with the terminal dialed and ends with the last terminal in the hunt group. CIRCULAR_HUNT This type of hunt begins with the terminal dialed and ends with the terminal immediately preceding the starting terminal. UNIFORM_CALL_DISTRIBUTION_HUNT This type of hunt beings with the terminal following the most recentlyused terminal and ends with the terminal immediately preceding the starting terminal. Any start hunt information is ignored, since it chooses the start hunt point based on the last terminal dialed. sendOAssistCalls sendDAssistCalls TRUE allow operator assisted calls FALSE (default) do not allow operator assisted calls TRUE allow directory assisted calls FALSE (default) do not allow directory assisted calls
timers
options
selectionMethod
274
Trunk Groups
attribute tandemRoutingType
value Sets the type of routing for calls received on the trunk group. For a discussion of this attribute, see The tandemRoutingType Trunk Group attribute on page 234. NO_ROUTING Uses routing based on the dialed number, the subscribers carrier, or the LNP code CARRIER_ROUTING (default) Forces the calls received on this trunk group to use incoming Tandem Carrier route lists TRUNKGROUP_ROUTING Forces the calls received on this trunk group to use incoming Tandem Trunk Group route lists ANI_ROUTING Forces the calls received on this trunk group to use incoming Tandem ANI route lists
restrictions localTermination
The restrictions on this Hunt Group. See Hunt Group Restrictions on page 280. This attribute is not meaningful for Hunt Groups. Please ignore it.
tandemDefaultRoutingType The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment. miscOptions The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs). An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415, and Prefixes on page 403. The Hunt Group direction attribute is inherited from Trunk Groups, where it is used to set up pairs of incoming an outgoing trunk groups. For a Hunt Group, however, direction should always be set to BI_DIRECTIONAL.
denyAniList
direction
275
Trunk Groups
attribute pilotLDN
value A pilot listed directory number (LDN) is a number assigned to the first line of a group of lines that forms the multi-line hunt group. The pilotLDN is the number dialed to reach the group. There must be at least one pilotLDN per hunt group, but there can be multiple pilotLDNs per multi-line group for nested sets. Note: this field is read-only. Optional, the number to which the call routes if all terminals in a hunt group are busy. If no number is specified, then all terminals busy results in the busy tone. The overflow DN of one hunt group can be the pilotLDN of another hunt group. Used to associate an optional start hunt number with a terminal in the Hunt Group. One or more additional start hunt numbers may be added to a hunt group. Once
overflowDN
associatedDNs
additional start hunt numbers are added to the hunt group, either a start hunt number or the pilotLDN can be dialed to start the hunt.
Used only for regular or circular hunt type Hunt Groups. Hunt groups using the UCD hunt type do not require start hunt points.
NOTE: After adding a Start Hunt number, the switch adds a route list using the associatedDN and adds the hunt group as the route. trunkProtocol trunkSignalingType One of the following: FXO See FXO on page 746. LOOPSTART A supervisory signal from a telephone or PBX that completes the signaling loop path GROUNDSTART A method of analog signaling from a terminal or subscriber loop to a switch, where one side of a cable pair is temporarily grounded memberOrigination The memberOrigination allows a terminal without a subscriber associated with it to originate calls. Values are TRUE to allow terminals without a subscriber associated to them to originate calls. The terminal uses the pilotLDN as the ANI. FALSE to restrict terminals without a subscriber associated to them from making calls. This attribute has a complex relationship with the gr303UsePilotND and sendPilotDNasANI attributes. See ANI Sent and Services Used on page 278.
276
Trunk Groups
attribute gr303UsePilotDN
value This attribute allows GR-303 members to originate calls using the Pilot DN instead of their own. This does not apply to any kind of transfer, forward, etc. This attribute has a complex relationship with the memberOrigination ad sendPilotDNasANI attributes. See ANI Sent and Services Used on page 278. TRUE to allow GR-303 members to originate using the pilot ANI instead of their own if member origination is enabled. This does not apply to any kind of transfer, forward, etc. FALSE (default) to restrict GR-303 members from using the pilot ANI
sendPilotDNasANI
This attribute sends the Pilot DN as the ANI when a member of a Hunt Group makes a call. This attribute has a complex relationship with the memberOrigination and gr303UsePilotDN attributes. See ANI Sent and Services Used on page 278. TRUE members send the Pilot DN as ANI. FALSE (default) members do not send the Pilot DN as ANI.
277
Trunk Groups
gr303Use memberANI Sent Services ANI Sent Services PilotDN Origination FALSE FALSE TRUE FALSE TRUE FALSE member member member GR303: pilot, others: member pilot pilot member member member GR303: pilot, pilot others: member member member GR303: pilot, can not make calls pilot pilot pilot can not make calls pilot pilot can not make calls
FALSE
TRUE
TRUE
TRUE TRUE
FALSE FALSE
FALSE TRUE
TRUE
TRUE
FALSE
TRUE
TRUE
TRUE
pilot
pilot
278
Trunk Groups
key pilotLDN
modify modify
timers options selectionMethod sendOAssistCalls sendDAssistCalls restrictions localTermination tandemDefaultRoutingType denyAniList direction overflowDN trunkProtocol trunkSignalingType memberOrigination gr303UsePilotDN sendPilotDNasANI
facilities associatedDNs
See Adding Facilities to a Hunt Group on page 281, Removing Facilities from a Hunt Group on page 283, Adding associatedDNs to a Hunt Group on page 284, and
Removing associatedDNs from a Hunt Group on page 285
279
Trunk Groups
The Hunt Group restrictions attribute is a bit field, so individual values are:
modify modify
280
Trunk Groups
Adding Facilities to a Hunt Group insertInto HuntGroup <key> facilities <subkey> <facilityType> <subvalue>
Use the Generic CLI insertInto command to add a facility to a Hunt Groups facilities list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
Tip
You can add a facility to the front of the list by entering a "1" here, but only do so when entering the Pilot DN. Use a -1 to add a facility to the end of the list.
<facilityType>
Valid values are: TDMFacility GR303Facility MGCPFacility SIPFacility. NOTE: Hunt Groups do not support SIP Access Subscribers.
<subvalue>
This attribute specifies which facility you want to add to the Trunk Group.
Add the pilotLDN's facility to the Hunt Group as the first facility in the Hunt Group. This subscribers facility is Terminal 0, or the first terminal. See insertInto on page 6. The following command adds a pilot DN facility to a Hunt Group:
insertInto HuntGroup WeekdayOffice facilities 1 TDMFacility Line-0-1-27
The following example adds additional facilities to a Hunt Group. The query command verifies the ordering of the facilities in the Hunt Group.
NOTE: When adding additional facilities into the Hunt Group, make sure the subkey is greater than 1, as the Pilot DN must be the 1st facility in the Hunt Group!
insertInto HuntGroup WeekdayOffice facilities 2 TDMFacility Line-2-1-27 insertInto HuntGroup WeekdayOffice facilities 3 TDMFacility Line-3-1-27
281
Trunk Groups
query HuntGroup WeekdayOffice facilities <48fe374> facilities.................<48f9890> <48f9890> HGFacilityList collection...List (3 items) -> (1) <4906d40> TDMFacility facilityOID...Line-0-1-27 (2) <4907f60> TDMFacility facilityOID...Line-2-1-27 (3) <4903030> TDMFacility facilityOID...Line-3-1-27
282
Trunk Groups
Removing Facilities from a Hunt Group deleteFrom HuntGroup <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a facility from a Hunt Groups facilities list. See the deleteFrom example on page 21 for a detailed explanation of this command.
NOTE: You must first lock the facility before you can remove it from the Hunt Group.
Syntax <key>
Description
<subkey>
This example builds on the configuration set up in Adding Facilities to a Hunt Group. The following example locks Line-3-1-27 on the local card and then removes it from Hunt Group WeekdayOffice. The query command verifies that the desired facility was removed from the Hunt Group.
lock Line-3-1-27 deleteFrom HuntGroup WeekdayOffice facilities 3 query HuntGroup WeekdayOffice facilities <48fe374> facilities.................<48f9890> <48f9890> HGFacilityList collection...List (2 items) -> (1) <4906d40> TDMFacility facilityOID...Line-0-1-27 (2) <4907f60> TDMFacility facilityOID...Line-2-1-27
283
Trunk Groups
Adding associatedDNs to a Hunt Group insertInto HuntGroup <key> associatedDNs <subkey> <subvalue>
Use the Generic CLI insertInto command to add an associated DN to a Hunt Groups associatedDNs dictionary. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey> <subvalue>
NOTE: After adding a Start Hunt number, the switch adds a route list using the associated DN and adds the hunt group as the route.
The following command adds a new associated DN to a Hunt Group, and associates it with terminal 2. The query command verifies the ordering of the associated DNs in the Hunt Group. Note that the switch automatically created a new route to the associated DN.
insertInto HuntGroup WeekdayOffice associatedDNs 9724801000 2 ****** Event Notification ****** (eventName): Configuration (senderID): <49035d0> (objectID): "Src S:0 C:0 Pid:3f " (timestamp): 47e1a4dd (refdate): 7d8313 (reftime): f341a (rawreftime): 47e1992 a (reserved): 0 (text): "MGR: tNANPRoutingDbMgr CREATED: WeekdayOffice_startHunt _2_9724801000" query HuntGroup WeekdayOffice associatedDNs <490db90> associatedDNs...............<490f7d0> <490f7d0> StartHuntDict collection...Dictionary (2 items) -> StringKey: 9724800000 IntegerValue: 1 (1) StringKey: 9724801000 IntegerValue: 2 (2)
284
Trunk Groups
Removing associatedDNs from a Hunt Group deleteFrom HuntGroup <key> associatedDNs <subkey>
Use the Generic CLI deleteFrom command to remove an associated DN from a Hunt Groups facilities dictionary. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
NOTE: After deleting a Start Hunt number, the switch removes the route list using the associated DN.
This example builds on the configuration set up in Adding associatedDNs to a Hunt Group. The following command removes associated DN 9724801000 from Hunt Group WeekdayOffice. The query command verifies that the desired associated DN was removed from the Hunt Group.
deleteFrom HuntGroup WeekdayOffice associatedDNs 9724801000 ****** Event Notification ****** (eventName): Configuration (senderID): <490e100> (objectID): "Src S:0 C:0 Pid:3f " (timestamp): 47e19f0a (refdate): 7d8313 (reftime): f341a (rawreftime): 47e1992 a (reserved): 0 (text): "MGR: tNANPRoutingDbMgr DELETED: WeekdayOffice_startHunt _2_9724801000" query HuntGroup WeekdayOffice associatedDNs <490db90> associatedDNs...............<490f7d0> <490f7d0> StartHuntDict collection...Dictionary (1 items) -> StringKey: 9724800000 IntegerValue: 1 (1)
285
Trunk Groups
ISDN Primary Rate Interface (PRI) can transmit up to 1.544 megabytes per second of data or up to 24 telephone calls at one time. ISDN PRI 23B+D consists of:
23 Bearer (B) channels available to transfer information, at 64 kilobytes per second each. One Data (D) channel used for signaling to control the status of a connection, at 64 kilobytes per second.
NOTE: The trunk group name cannot contain a semicolon (;), nor can it consist of either the word ALL or the word all facilities A list of the facilities (trunks) in the trunk group. See Adding Facilities to a PRI Trunk Group on page 306, and Removing Facilities from a PRI Trunk Group on page 306. The timers for this trunk group. See PRI Trunk Group Timers on page 293. The options for this trunk group. See PRI Trunk Group Options on page 296. FIRST_AVAILABLE always select the first trunk available ROUND_ROBIN (default) sequentially rotate the use of trunks sendOAssistCalls sendDAssistCalls TRUE allow operator assisted calls FALSE (default) do not allow operator assisted calls TRUE allow directory assisted calls FALSE (default) do not allow directory assisted calls
286
Trunk Groups
Attribute tandemRoutingType
Description Leave this attribute set to the default value of NO_ROUTING. ISDN PRI routes calls based on either the calling number or default DN subscriber record. Refer to screenDN on page 300 to determine which subscriber record is used. optional default directory number. Used when the trunk group connects to a PBX that needs to have default Primary IntraLATA or InterLATA Carrier (PIC). Make sure you add a default subscriber with this number to set the specific IntraLATA or InterLATA Carrier to bill the number correctly, as well as to allow for allowed/ denied lists and an NANP route list for the range of DNs that the PBX handles.
defaultDN
NOTE: If assigned, the defaultDN becomes the default ANI for 911 calls made without a 10 digit ANI. See E911DefaultANI on page 314 restrictions defaultNPA The restrictions on this trunk group. See PRI Trunk Group Restrictions on page 305. The NPA to be added when 7-digits are received on an incoming trunk group. The switch adds the defaultNPA to the 7-digits and then routes on 10-digits. This defaultNPA must be a provisioned prefix, see Prefixes on page 403. Length: 3 replaceDestinationDigits TRUE allow the use of replacement destination digits (called number) on the trunk group. The switch replaces part or all of the destination digits depending on how the prefix is provisioned, See Subscribers on page 530, Destination Digit Replacement on page 346, and replacementMode on page 405 FALSE do not replace Destination Digits and send the dialed digits. REPLACE_IfNotPorted do not replace Destination Digits in the outgoing signaling messages if the called DN has a non-T7000 LRN associated with it
287
Trunk Groups
Attribute replaceCarrier
group.
TRUE allow the use of PCAC on the trunk group. The switch replaces the CAC depending on how the prefix or carrier is provisioned. See Prefixes on page 403, replacementMode on page 405, and Carriers on page 196. FALSE do not use a PCAC on the trunk group and send the CAC. REPLACE_IfNotPorted do not use a PCAC if the called number has an non-T7000 LRN associated with it and send the CAC. replaceAniDigits
This attribute controls the use of a PANI II digits on the trunk group.
TRUE allow the use of a Pseudo ANI (PANI) on the trunk group. The switch replaces the ANI (calling number) depending on how the prefix is provisioned, See Subscribers on page 530. FALSE do not use a PANI on the trunk group and send the ANI. REPLACE_IfNotPorted do not use a PANI if the called number has an non-T7000 LRN associated with it and send the ANI.
replaceInfoDigits
TRUE allow the use of a PANI II digits on the trunk group. The switch replaces the ANI II digits depending on how the prefix is provisioned,See Subscribers on page 530. FALSE do not use PANI II digits on the trunk group and send the ANI II digits on the facility. REPLACE_IfNotPorted do not use PANI II digits if the called number has an non-T7000 LRN associated with it and send the ANI II digits on the facility
ftrsProfile
The profile assigned to the incoming trunk group. This profile determines how the switch manipulates digits and routing. See FTRS on page 223.
NOTE: A subscriber profile takes precedence over an incoming trunk group profile. For example, if a subscriber has a profile assigned and is in a FXO trunk group with a profile, the switch uses the subscriber profile. For more information, consult the T7000 Provisioning Guide.
288
Trunk Groups
Attribute replaceCSI
Description
This controls the use of the Carrier Selection Information parameter in outgoing messages on the trunk group.
TRUE allow the use of a PCSI on the trunk group. The switch replaces the outpulse of the CSI parameter depending on how the prefix is provisioned, See Subscribers on page 530 FALSE do not send a PCSI on the trunk group and send the CSI. REPLACE_IfNotPorted do not use PCSI if the called number has an non- T7000 LRN associated with it and send the CSI.
localTermination
ALLOW (default) allow incoming calls on the trunk group to terminate on the switch. NOT_ALLOWED only allow incoming calls to tandem through the switch.
tandemDefaultRoutingType
The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment.
miscOptions
The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs). An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked. See Prefixes on page 403, and Prefixes on page 403
denyAniList
289
Trunk Groups
Attribute direction
Description ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions.
NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch.
BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call tandemCustomReplacement Used to outpulse 7 digits for tandem calls. NO (default) no special outpulsing is performed. YES outpulse 7 digits for non-ported subscribers. See 7 Digit Tandem Call Outpulsing on page 409. dChannelOIDprimary side object identifier of the OOS trunk acting as the data channel for the PRI trunk group switch role: USER If the PRI interface is a PBX or other configuration that receives PRI service. NET If the switch is positioned in the network as a Class 5 End Office or other configuration that provides PRI service. primaryLogicalSpan dChannelOIDSecondary secondaryLogicalSpan optional logical identifier of the D-channel; for example, 1 optional object identifier of the trunk acting as the data channel backup for the PRI trunk group optional logical identifier of the D-channel backup; for example, 2
290
Trunk Groups
Attribute isdnMsgTrace
Description This debug attribute controls how the switch shows ISDN Call Establishment, Call Clearing, Maintenance and Miscellaneous messages. The messages are displayed when running a CLI session on the card that has the PRI span. Values are: MSG_TRACE_NONE (default) The message trace for this trunk group is off. MSG_ONLY Shows the ISDN messages MSG_WITH_INBOUND_DUMP Shows ISDN messages and a dump of inbound IEs. MSG_WITH_OUTBOUND_DUMP Shows ISDN messages and a dump of outbound IEs. MSG_WITH_BOTH_DUMP Shows ISDN messages and a dump of both inbound and outbound IEs.
CAUTION
Contact Taqua TAC Support before using this option. terminalEndpointID E911DefaultANI optional Terminal Endpoint Identifier. Range: 0 - 63, default: 0 This attribute is used to specify a 10 digit ANI when a 911 call is made and ANI does not contain a 10 digit number, and a defaultDN is not assigned to the Trunk Group.
The Generic CLI is used for all PRI Trunk Group commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key dChannelOIDPrimary
291
Trunk Groups
timers options selectionMethod sendOAssistCalls sendDAssistCalls tandemRoutingType defaultDN restrictions defaultNPA replaceDestinationDigits replaceCarrier replaceAniDigits replaceInfoDigits ftrsProfile replaceCSI localTermination tandemDefaultRoutingType denyAniList direction isdnMsgTrace terminalEndpointId
facilities
See Adding Facilities to a PRI Trunk Group on page 306, and Removing Facilities from a PRI Trunk Group on page 306.
create PRITrunkGroup SWB1 Trunk-23-1-27 modify PRITrunkGroup SWB1 sendOAssistCalls FALSE query PRITrunkGroup SWB1 timers destroy PRITrunkGroup SWB1
292
Trunk Groups
293
Trunk Groups
Timer T308
Description The time between sending and receiving a REL message. Resends a REL message and resets when the timer expires. Network side timer. Default: 4,000 ms
T309
The time between data link disconnection and data link reconnection. The network channel clears and the B channel releases when the timer expires. Network side timer. Default: 90,000 ms
T310
The time between data link disconnection and data link reconnection. The call clears when the timer expires. Network side timer. Default: 10,000 ms
T313
The time between sending a RESUME request and receiving a RESUME ACK message. Sends a DISC (disconnect) messages when the timer expires. User side timer. Default: 4,000 ms
T316
The time between sending a RESTART message and receiving a RESTART ACK message. RESTART message may be sent several times after the timer expires. Network and user side timer. Default: 30,000 ms
T317
The time between receiving a RESTART message and the internal clearing of call reference. Sends a maintenance notification when the timer expires. Set at less than the value of T316. Network and user side timer. Default: 20,000 ms
T318
The time between sending a RESUME request and receiving a RESUME ACK or RESUME REJ (reject) message. Sends a release message when the timer expires. User side timer. Default: 4,000 ms
T319
The time between sending a SUSPEND message and receiving a SUSPEND ACK or SUSP (suspend) REJ message. The device enters an active state when the timer expires. User side timer. Default: 4,000 ms
294
Trunk Groups
Timer T321
Description The time between a D-channel failure and receiving a response to a layer 3 message. Sends a DL-ESTABLISHMENT message request on both channels when the timer expires. Network and user side timer. Default: 40,000 ms
T322
The time between sending a STATUS ENQ message and receiving a STATUS DISC, REL, or REL COMPLETE message. Sends STATUS ENQ when the timer expires. Network and user side timer. Default: 4,000 ms
T3M1
The time between sending a SERVICE message and receiving a SERVICE ACKNOWLEDGE message. The SERVICE status of the B-Channels should be unchanged as a result of a temporary D-Channel failure. The CPE should use a SERVICE message to notify the Network of the state change once the DChannel comes back into service. For AT&T B-Channel availability procedure only. Default: 120,000 ms
hdlcErrorInterval
Tip
The flexibility of being able to set both the interval and the water marks let you react to either error spikes (a burst of errors in a short period of time) or a "trickle" of errors over a longer period of time.
The Error Interval is used with the "high" and "low" water marks to determine how tolerant the switch will be with respect to detected errors. See hdlcErrorLowWaterMark on page 302 and hdlcErrorHighWaterMark on page 303. The switch counts errors on the link for the duration of the hdlcErrorInterval. If the low water mark is "10", and 10 errors occur during the 10 second interval, the switch issues a warning. If the high water mark is reached during the interval, the switch takes the link down. After the interval expires, the timer and the error counts are reset and the switch starts counting again from zero. Range: 10,000 - 60,000 milliseconds Default: 10,000
295
Trunk Groups
296
Trunk Groups
autoRestartOnBoot
Automatically sends a RESTART message after booting the D-channel. A restart message drops all calls on the Bchannels. Values are: Off On
autoRestartOnLinkBounce
Automatically sends a RESTART message when a link bounces. A restart message drops all calls on the Bchannels. Values are: Off On
allowNX64
Allows the trunk group to originate NX64 calls, a multirate call that uses multiple B channels. Currently the switch supports 2X64. Values are: Off On
contiguousNX6
networkServices
Set BLV/BLI only on trunk groups coming from an operator station. You need one trunk group for each service. Allow for one of the following operator services: Values are: BLV Busy Line Verification allows an external operator to verify if a subscriber line is busy. An operator calling over a BLV trunk receives a busy signal if the line is busy or a ring-back if the line is idle. BLI Busy Line Interrupt allows an external operator to interrupt a busy line. An operator calling over a BLI trunk interrupts the busy subscriber who can either drop the existing conversation and accept the operator call or continue with the existing conversation.
sendCarrierId
Sends the CAC in the call set up messaging. This option allows the switch to send the CAC to another switch in the network and only works when the trunk group is set to USER_SIDE. The CAC is sent in the optional Translation Network Selection information element. Values are: NO YES includes all call types SOME_CALL_TYPES includes: INTER_LATA, OA_INTER_LATA, INTRA_LATA, OA_INTRA_LATA, INTERNATIONAL, OA_INTERNATIONAL, WORLDZONE1, OA_WORLDZONE1, DA_INTRA_LATA, DA_INTER_LATA, OA_ZERO_MINUS, and TANDEM_CALL
297
Trunk Groups
sendCalledNumberAsPBX
Sends the called number as dialed to the terminator, including: 7-digit dialing, 0-, 0+, 1+ and carrier dialing (101XXXX+1+NPANXXXXXX). This allows the switch to play the role of a PBX between subscribers and an end office. The switch also sends the CAC for IntraLATA and InterLATA calls. This attribute only applies to USER role. Values are: NO YES
NOTE: If set, this attribute overrides both outPulseAsDialed on page 298 and numOfDIDDigits on page 299 attributes. bChannelAvailabilityProcedure NO the switch only responds to SERVICE messages. ATT indicates the status change on a B-channel for Call Processing. Use this when connecting to PBXs that use the ATT procedure. The switch sends and responds to SERVICE messages NOTE: This attributre is ignored in USER mode if sendCalledNumberAsPBX on page 298 is set.
outPulseAsDialed
For calls terminating to the PRI group, this attribute allows the switch to act as a local End Office (EO), providing long distance service without having an InterLATA carrier provisioned. The switch, acting as a local EO, outpulses the dialed digits to the local tandem office. Then, the local tandem office, not the local EO, performs screening and translation on the dialed digits. Values are: False the switch translates the digits, chooses a call type and routes based on the call type (local, extended, intraLATA, interLATA, worldZone1, International, etc.). True routes by and outpulses the exact digits the subscriber dials and does not send the CAC for the call.
NOTE: If set, this attribute overrides numOfDIDDigits on page 299 in either USER or NETWORK mode.
298
Trunk Groups
numOfDIDDigits NOTE: This attributre is ignored in USER mode if sendCalledNumberAsPBX on page 298 is set. This attributre is ignored in USER or NETWORK mode if outPulseAsDialed on page 298 is set.
Set the number of direct inward dialing digits allowed from two to ten. Values are: ALL the switch sends (outpulses) all of the digits that it receives. 1-10 the switch only sends (outpulses) the last number of digits that you select. redirectingNumberOption Redirecting a calling number is used when connecting to a voice mail system using PRI. In a scenario where A calls B and B forwards to voice mail, C is the redirecting number. This setting determines which Information Element (IE) is used to send the redirecting DN. Values are: NO does not send the redirecting number, even if it is present, to a voice mail system. REDIRECTING_NUMBER_IE inserts the redirecting DN (B) in the setup message as the redirecting number IE. Use for Lucent PBXs. ORIGINAL_CALLED_NUMBER_IE sends the redirecting DN (B) as the original called number IE, in the setup message. Use for a Nortel PBX. CALLING_NUMBER_IE sends the redirecting DN (B) as the calling number IE in the setup message. Use for Taqua Courier voice mail. CALLED_NUMBER_IE sends the redirecting DN (B) as the called number IE in the setup message. Use for TNS voice mail systems Zeus. implicitChannelId This setting is for PRI FAS groups (only 1 span in the group): Values are: Off sends the Channel Id formatted in the explicit or long form. Onsends the Channel Id (sent with the Service or Service Ack message) formatted in the implicit or short form that some vendors require. Note: the implicit or short formatting is rarely required. useImplicitChannelIdForPPS This setting is for PRI NFAS groups. Values are: Off sends the Channel Id formatted in the explicit or long form. On sends the Channel Id (sent with the Service or Service Ack message) formatted in the implicit or short form that some vendors require. The implicit or short formatting is rarely required
299
Trunk Groups
releaseCompleteAtSetup
screenDN
This setting is for PRI calls that originate on the T7000. Values are: DEFAULTDN if a default DN exists and has a subscriber, it becomes the subscriber key in the facility CPN if a calling party number is known and the subscriber is on the T7000, the calling party number replaces the subscriber key in the facility. DEFAULTDN_CPN DEFAULTDN is performed, if there is no default DN or no subscriber for that DN, CPN is performed. CPN_DEFAULTDN CPN is performed, if the calling party number is unknown or the subscriber is not on the T7000, DEFAULTDN is rarely required.
sendCPN
This setting works with screenDN. It sets which digits are sent for calling party number. Values are: CPN_DEFAULTDN if no CPN, use default DN DEFAULTDN use default DN as the calling party number CPN use CPN as the calling party number DEFAULTDN_CPN use default DN, if there is no default DN, use CPN. NONE the T7000 does not provide calling party
sendChargeNumber
Values are: DEFAULTDN (default) The default DN will be sent in the charge number. CPN If the calling party Number is received then CPN will be sent in the charge number. If calling party number is not received and there is a default DN for the trunk group then default DN will be sent in the charge number. BILLING_NUM If the Billing number is present for the subscriber used for screening it will be sent in charge number, otherwise the screened DN number will be sent in the charge number. Note: The screen DN option affects the choice of screenDN and therefore this option.
blockCPN
This setting prevents the Calling Party Number from being sent unless the CPN presentation is Allowed. It is useful when connecting to a PBX that is does not honor a restricted CPN presentation. Values are: Off Send CPN according to CPN presentation. On No not send CPN unless CPN presentation is allowed.
300
Trunk Groups
backwardProgressIndication
This setting is for PRI trunks connecting to a PBX that terminates to subscribers using CAS trunks. Values are: USE_NOT_END_TO_END_ISDN ISDN ensures the switch connecting to the T7000 does not use inband USE_INBAND_AVAILABLE ensures the switch connecting to the T7000 uses inband
mplicitInterfaceIdi
This setting is for PRI trunk groups with one d-channel. It controls the formatting of the "channel Id Interface Element" field. Values are: FALSE the switch does not send a message TRUE the switch sends a message saying the bearer channel is in the same span as the d-channel
sendLocalCallasSubscriber
This setting allows the switch to take an incoming PRI call and use the Remote Call Forwarding service to send the call over an outgoing PRI trunk group yet treat the call as local: FALSE adds a 1 to the called party number TRUE If a call is LOCAL or EXTENDED_AREA the switch flags every called party number as an ISDN subscriber number
releaseTreatment
Values are: RELEASE_CALL the access equipment provides treatment PROVIDE_TREATMENT the switch plays an announcement when there is a problem with the digits received
originalNumberOption
This option is used to populate various elements of the PRI Setup message. It can be useful when dealing with the interactions between multiple call forwardings and a persnickety voice mail system. Values are: NO No special processing is done (default) REDIRECTING_NUMBER_IE The Original Called Number parameter populates the Redirecting Number parameter. ORIGINAL_CALLED_NUMBER_IE The Original Called Number parameter populates the Redirecting Number parameter. CALLING_NUMBER_IE The Original Called Number parameter populates the Calling Number Information Element parameter. CALLED_NUMBER_IE The Original Called Number parameter populates the Called Number Information Element parameter.
301
Trunk Groups
networkSendDisconnectOnBusy
This option is used when dealing with equipment that cannot handle a Release message when a call is placed to a busy subscriber. Values are: SEND_RELEASE_ON_BUSY the switch sends Release when a subscriber on the PBX places a call to the switch for a busy subscriber (default) SEND_DISCONNECT_ON_BUSY the switch sends Disconnect when a subscriber on the PBX places a call to the switch for a busy subscriber
passExtCharForCallingName This option controls how the Calling Name is presented. The Calling Name is conveyed using ASCII characters. Normally, only the lower half of the 256 ASCII character set are sent. However, sometimes characters from the upper half are sent as well. Although the upper half of the ASCII character set contains mostly graphics characters, it also contains some characters used in European languages, such as , , and . Unfortunately, some switches will interpret a character from the upper half of the ASCII character set as being the end of the Calling Name (technically, this is called the Extension Bit, and it indicates the last octet in the field). In such a case, you will need to set this attribute to TRUE to prevent the T7000 from confusing the switch at the other end. Values are: FALSE (default) limits the value of characters in the Calling Name to the lower half of the ASCII character set. TRUE does not limit the values of characters in the Calling Name. hdlcErrorLowWaterMark The number of errors that can occur on the link during the hdlc Error Interval before the switch issues an hdlcWarning event. This is for informational purposes only. No action is taken by the system, although a tech should probably investigate the cause of the alarm If the value is zero, the switch will never issue a warning, no matter how many errors occur on the link. See hdlcErrorInterval on page 295. Default: 5
302
Trunk Groups
hdlcErrorHighWaterMark
The number of errors that can occur on the link during the hdlc Error Interval before the switch takes the link out of service. Once the errors reach the high water mark, the link is immediately removed from service. It will not come back into service until someone acknowledges (clears) the alarm - which requires manual intervention. If the value is zero, the switch will never take the link out of service, no matter how many errors occur on the link. See hdlcErrorInterval on page 295. Default: 0
sendUnknownCalledPtyForNumOfDIDDigits
This setting controls how the switch builds a SETUP message when outPulseAsDialed (see page 298) is set to FALSE and the called party number is less than 7 digits long. Values are: FALSE (default) set the numberingPlanId field in the SETUP message to ISDN_NUMBERING_PLAN and the typeOfNumber field in the SETUP message to ISDN_SUBSCRIBER_NUMBER. TRUE set the numberingPlanId field in the SETUP message to UNKNOWN_NUMBERING_PLAN, and the typeOfNumber field in the SETUP message to ISDN_UNKNOWN_NUMBER,
routeOnRcvdCarrier
InbCarrier_OutbCarrier route on the Incoming Carrier if available, otherwise, route on the Outbound Carrier. InbCarrier_only route on the Incoming Carrier only. OutbCarrier_InbCarrier (default) route on the Outbound Carrier, if available, otherwise, route on the Incoming Carrier. OutbCarrier_only route on the Outbound Carrier only.
NOTE: The outbound carrier ID is the carrier value received in the TNS parameter for PRI trunk groups playBusyToneOnNetworkSid This setting allows the switch to play a busy tone on the e Network side of a PRI Trunk when the Far End indicates a busy condition after requesting cut-through. Values are: FALSE (default) switch does not play busy tone (PBX supplies busy tone). TRUE switch plays busy tone.
303
Trunk Groups
defaultCnameDelivery
This setting controls the default behavior for calling name delivery when no calling name is available on the incoming trunk. Values are: All_Subscribers (default) Uses the name associated with the DefaultDN of the trunk group for all calls. Local_Subscribers_Only Uses the name associated with the DefaultDN of the trunk group only for local terminations. No_Delivery No delivery of the name associated with the DefaultDN.
delaySIPInviteForCallingPartyName
This setting affects PRI to SIP calls. It instructs the switch to wait for a ISDN PRI FACILITY message (which contains the Calling Party Name) before sending out the INVITE to the terminating endpoint. A value of 0 means no delay. Range: 0 - 1000 ms
304
Trunk Groups
NO_OS_INTERNATIONAL Restrict OS international calls. NO_INBOUND_WITHOUT Does not allow calls that do not include the ANI. _ANI
The PRI Trunk Group restrictions attribute is a bit field, so individual values are:
modify modify
305
Trunk Groups
Adding Facilities to a PRI Trunk Group insertInto PRITrunkGroup <key> facilities <subkey> PRIFacility <oid> <cic>
Use the Generic CLI insertInto command to add a trunk to a PRI Trunk Groups facilities list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> <subkey> Description
Tip
Use a index of 1 to insert a facility at the start of the facilities list. Use a index of -1 to insert a facility at the end of the facilities list.
<oid> <cic>
This attribute specifies which trunk you want to add to the Trunk Group. This attribute specifies the Circuit Identification Code of the inserted Trunk.
The following command adds trunk 26 on the local card to PRI Trunk Group SWB1:
insertInto PRITrunkGroup SWB1 facilities -1 PRIFacility Trunk-26-1-27 1
Removing Facilities from a PRI Trunk Group deleteFrom PRITrunkGroup <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a trunk to a PRI Trunk Groups facilities list. See the deleteFrom example on page 21 for a detailed explanation of this command.
NOTE: You must first lock the Trunk before you can remove it from the Trunk Group.
Description
The following example locks trunk 26 on the local card and then removes it from PRI Trunk Group SWB1:
306
Trunk Groups
IP Trunk Groups
An IP trunk group connects a SIP endpoint to a PIC cards Fast Ethernet Interface. More than one IP trunk group can be assigned to a SIP endpoint, as long as the directory number (DN) ranges assigned to each trunk group are different. Trunk Group has the following attributes:
Attribute key Description trunk group name. See the suggested naming convention for Trunk Groups on page 233.
NOTE: The trunk group name cannot contain a semi-colon (;), nor can it consist of either the word ALL or the word all options selectionMethod sendOAssistCalls sendDAssistCalls tandemRoutingType The options for this trunk group. See IP Trunk Group Options on page 317. Note: this field is read-only. ROUND_ROBIN sequentially rotate the use of trunks TRUE allow operator assisted calls FALSE (default) do not allow operator assisted calls TRUE allow directory assisted calls FALSE (default) do not allow directory assisted calls Sets the type of routing for calls received on the trunk group.
NO_ROUTING (default) Uses routing based on the dialed number, the subscribers carrier, or the LNP code. CARRIER_ROUTING Forces the calls received on this trunk group to use incoming Tandem Carrier route lists TRUNKGROUP_ROUTING Forces the calls received on this trunk group to use incoming Tandem Trunk Group route lists ANI_ROUTING Forces the calls received on this trunk group to use incoming Tandem ANI route lists
307
Trunk Groups
Attribute defaultDN
Description Optional field for NetworkGateway endpoints. This is the pseudo subscriber DN for a Network Gateway. The default directory number (DN) is used for screening incoming IP calls on this trunk group. If provisioned, add a default subscriber with this number. see Subscribers on page 530
NOTE: If assigned, the defaultDN becomes the default ANI for 911 calls made without a 10 digit ANI. See E911DefaultANI on page 314 restrictions defaultNPA The restrictions on this trunk group. See IP Trunk Group Restrictions on page 322. The NPA to be added when 7-digits are received on an incoming trunk group. The switch adds the defaultNPA to the 7-digits and then routes on 10-digits. This defaultNPA must be a provisioned prefix, see Prefixes on page 403. Length: 3 replaceDestinationDigits TRUE allow the use of replacement destination digits (called number) on the trunk group. The switch replaces part or all of the destination digits depending on how the prefix is provisioned, see Subscribers on page 530, Destination Digit Replacement on page 346, and replacementMode on page 405. FALSE do not replace Destination Digits and send the dialed digits. REPLACE_IfNotPorted do not replace Destination Digits in the outgoing signaling messages if the called DN has a non-T7000 LRN associated with it replaceCarrier This attribute controls the use of a PCAC on the trunk
group.
TRUE allow the use of PCAC on the trunk group. The switch replaces the CAC depending on how the prefix or carrier is provisioned. See Prefixes on page 403, replacementMode on page 405, and Carriers on page 196. FALSE do not use a PCAC on the trunk group and send the CAC. REPLACE_IfNotPorted do not use a PCAC if the called number has an non-T7000 LRN associated with it and send the CAC.
308
Trunk Groups
Attribute replaceAniDigits
Description
This attribute controls the use of a PANI II digits on the trunk group.
TRUE allow the use of a Pseudo ANI (PANI) on the trunk group. The switch replaces the ANI (calling number) depending on how the prefix is provisioned, See Subscribers on page 530. FALSE do not use a PANI on the trunk group and send the ANI. REPLACE_IfNotPorted do not use a PANI if the called number has an non-T7000 LRN associated with it and send the ANI.
replaceInfoDigits
TRUE allow the use of a PANI II digits on the trunk group. The switch replaces the ANI II digits depending on how the prefix is provisioned,See Subscribers on page 530. FALSE do not use PANI II digits on the trunk group and send the ANI II digits on the facility. REPLACE_IfNotPorted do not use PANI II digits if the called number has an non-T7000 LRN associated with it and send the ANI II digits on the facility
ftrsProfile
The profile assigned to the incoming trunk group. This profile determines how the switch manipulates digits and routing. See FTRS on page 223.
NOTE: A subscriber profile takes precedence over an incoming trunk group profile. For example, if a subscriber has a profile assigned and is in a FXO trunk group with a profile, the switch uses the subscriber profile. For more information, consult the T7000 Provisioning Guide. replaceCSI
This controls the use of the Carrier Selection Information parameter in outgoing messages on the trunk group.
TRUE allow the use of a PCSI on the trunk group. The switch replaces the outpulse of the CSI parameter depending on how the prefix is provisioned, See Subscribers on page 530 FALSE do not send a PCSI on the trunk group and send the CSI. REPLACE_IfNotPorted do not use PCSI if the called number has an non- T7000 LRN associated with it and send the CSI.
309
Trunk Groups
Attribute localTermination
Description
The localTermination attribute controls if incoming trunk group allows for local terminations or not. If it does not allow for local terminations then use the trunk group in a tandem routing application. If you allow local terminations in a tandem routing trunk group, then if the DN terminates on the switch the calls for that DN will not be tandemed out of the switch.
ALLOW (default) allow incoming calls on the trunk group to terminate on the switch. NOT_ALLOWED only allow incoming calls to tandem through the switch.
tandemDefaultRoutingType The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment. miscOptions The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs). An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415,and Prefixes on page 403.
denyAniList
310
Trunk Groups
Attribute direction
Description ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions.
NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch.
BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call tandemCustomReplacement Used to outpulse 7 digits for tandem calls. NO (default) no special outpulsing is performed. YES outpulse 7 digits for non-ported subscribers. See 7 Digit Tandem Call Outpulsing on page 409. codecListName The name of the codec list for this trunk group. A codec list is a container for codec profiles that are associated with one or more IP or MGCP trunk groups. See CodecProfileList on page 425. The name of the media stream parameter for this trunk group. Media stream parameters control the characteristics of the bearer or RTP portion of a VoIP call. See MediaParam on page 431
mediaParamName
311
Trunk Groups
Attribute maximumCalls
Description The number of maximum calls (sessions) based on the number of cards in the system or protection group and codec types used from 0-5376. The number of calls is based on the use of virtual IP trunks from the pool of 1,344 possible trunks per PIC. Since an IP trunk group has no physical facilities, there would otherwise be no limit to the number of calls that a subscriber or a group of subscribers could originate or terminate. This is where the IP Trunk Group concentration ratio is defined. For example, if you had 800 subscribers using a trunk group you could assign 200 as the maximum calls for a 4:1 ratio. Also, you could over assign the maximum calls per group, since the trunks get assigned as they are requested from the pool. 24=default 0-5376=range
priNearEndNiOid
Object Identifier of the Fast Ethernet Interface Facility (FEIF). This is the interface and associated IP address used for signalling. See OID on page 30. The secondary Fast Ethernet (FE) interface and associated IP address the PIC uses to provide redundancy.
secNearEndNiOid
NOTE: If you do not provision a secNearEndNiOid (secondary near end network interface object identifier) FE, the primary is always active and you do not have redundancy. If you do provision a secondary FE, the first FE to come into service is active. actNearEndNiOid activeCalls Note: This field is read-only. This field shows which FEIF is active. Note: This field is read-only. This dynamic field shows the number of calls the trunk group is currently carrying. operationalState Note: This field is read-only. UNREACHABLE Network problems are preventing the switch from communicating with the IP endpoint at the other end of the IP Trunk Group. REACHABLE the switch can communicate with the IP endpoint at the other end of the IP Trunk Group
312
Trunk Groups
Attribute administrativeState
Description Note: This field is read-only. LOCKED The IP Trunk Group is administratively prohibited from providing services. See lock on page 7. UNLOCKED The IP Trunk Group is administratively allowed to provide services. See unlock on page 7.. SHUTTING_DOWN The IP Trunk Group is currently providing services, but no new services are allowed to start. As soon as the last service completes, the administrativeState will automatically transition to LOCKED. See shutdown on page 7.
bearerAuditTimer1
The time, in milliseconds, after the IP call is established to initiate a check for received RTP packets. The default is 3600000 milliseconds (3600 seconds, or one hour). See auditBearerResources in this section. The time, in milliseconds, after bearerAuditTimer1 has expired to check for received RTP packets. The default is 600000 milliseconds (600 seconds, or ten minutes). See auditBearerResources in this section. This flag enables or disables bearer audits. Bearer audits timers prevent a hung IP call from using bandwidth. Bearer resource audits prevent a hung IP call from using bandwidth. The switch compares RTP packet counts from bearerAuditTimer1 and bearerAuditTimer2. If the count is the same, indicating no RTP packets have been exchanged, the switch tears down the call. If the count is different, indicating RTP packets have been exchanged, auditing restarts. TRUE the switch compares RTP packet counts from bearerAuditTimer1 and bearerAuditTimer2. If the count is the same, indicating that no RTP packets have been exchanged, the switch tears down the call. If the count is different, indicating RTP packets have been exchanged, auditing restarts (default). FALSE no bearer audit is performed.
bearerAuditTimer2
auditBearerResources
Future feature. Note: This field is read-only. Future feature. Note: This field is read-only. a optional DN on which to screen calls. See screenDNChoice on page 317.
313
Trunk Groups
Attribute useINFOMethod
Description TaquaWorks: Use of this option causes all routing and call control to be done by the BroadWorks platform NOTE: BroadWorks uses a propitiatory extension to the INFO method. This INFO method should only be sent to a BroadWorks application server. If set, the T7000 uses the INFO method to send hook flash events to BroadWorks, and receives Call Waiting Caller ID infromation from BroadWorks. FALSE (default) do not use the BroadWorks proprietary extension to the INFO method True use the BroadWorks proprietary extension to the INFO method.
sigFQDN
Fully Qualified Domain Name of the signaling Network Interface. If populated, this string can be used in place of the IP address and port number of the FEIF. See useSigFQDN on page 314. This attribute controls if the sigFQDN is used instead of the IP Address and Port Number of the Fast Ethernet Interface associated with this IP Trunk Group. Note that sigFQDN must be provisioned, or this field has no effect. Values are: FQDN_FOR_FROM_HDR use the sigFQDN to construct the FROM header. FQDN_FOR_CONTACT_HDR use the sigFQDN to construct the CONTACT header. FQDN_FOR_RPARTY_ID use the sigFQDN to construct the REMOTE PARTY ID header. FQDN_FOR_DIVERSION use the sigFQDN to construct the DIVERSION header.
useSigFQDN
bearerFreeGrpKey E911DefaultANI
future feature This attribute is used to specify a 10 digit ANI when a 911 call is made and the From: header does not contain a 10 digit number and a defaultDN is not assigned to the Trunk Group.
314
Trunk Groups
The Generic CLI is used for all IP Trunk Group commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key priNearEndNiOid
defaultDN
315
Trunk Groups
options sendOAssistCalls sendDAssistCalls tandemRoutingType defaultDN restrictions defaultNPA replaceDestinationDigits replaceCarrier replaceAniDigits replaceInfoDigits ftrsProfile replaceCSI localTermination tandemDefaultRoutingType denyAniList direction codecListName mediaParamName maximumCalls priNearEndNiOid secNearEndNiOid bearerAuditTimer1 bearerAuditTimer2 auditBearerResources screenDN useINFOMethod sigFQDN useSigFQDN create IPTrunkGroup agwTrkGrp fe-0-10 modify IPTrunkGroup agwTrkGrp options sendCPN CPN modify IPTrunkGroup agwTrkGrp useINFOMethod TRUE lock IPTrunkGroup agwTrkGrp destroy IPTrunkGroup agwTrkGrp
316
Trunk Groups
317
Trunk Groups
Values CALLING_DN use this option for residential EVS subscribers or businesses. Provision a pseudo-subscriber on the T7000 for the calling DN.
1. Calling Party DN 2. IP Trunk Group Screen DN IP Trunk Group Default DN
DEFAULT_DN use this option for businesses and for IP Trunk Groups. Provision a defaultDN for the IP Trunk Group and a pseudo-subscriber for the defaultDN.
IP Trunk Group Default DN
DIVERSION_THEN_SCREEN use this option when the Network Gateway supplies a Diversion Header to indicate call forwarding and when multiple IP Trunk Groups provisioned off the same Network Gateway require different screening treatments. Provision a pseudo-subscriber for the diversion (redirecting) party on the T7000. Provision a screenDN in the IP Trunk Group and a pseudo-subscriber for the screenDN.
1. Diversion Header party 2. IP Trunk Group Screen DN IP Trunk Group Default DN
DIVERSION_THEN_CALLING use this option when the Network Gateway supplies a Diversion Header to indicate call forwarding. Provision a pseudo-subscriber for the diversion (redirecting) party on the T7000.
1. Diversion header party 2. Calling Party DN 3. IP Trunk Group Screen DN IP Trunk Group Default DN
DIVERSION_THEN_DEFAULT use this option when the Network Gateway supplies a Diversion Header to indicate call forwarding.. Provision a pseudo-subscriber for the diversion (redirecting) party on the T7000.
1. Diversion header party IP Trunk Group Default DN
routeAdvance
CALLING_DN use this option for residential EVS subscribers or businesses. Provision a pseudo-subscriber on the T7000 for the calling DN.
1. Calling Party DN 2. IP Trunk Group Screen DN 3. IP Trunk Group Default DN
318
Trunk Groups
Option Name
Values
supportEarlyCutThrough for devices (typically IVRs) that need to cut through the twoway SIP voice path before the call is answered. Do not set these values for devices that support cutting through the twoway SIP voice path after the call is answered Type is Bitfield. These options are individually turned on or off by name. See example. SIPtoSS7_EarlyCutThru Support early cut through for SIP to SS7 and SIP to PRI calls. SIPtoTDM_EarlyCutThru Support early cut through for SIP to TDM calls. sendCPN This option affects how the switch determines the Calling Party Number for SIP originations from a Network Gateway endpoint.
NOTE: The Preferred Privacy Option and the Privacy information received in incoming RPID or Privacy Header still continue to determine the Name and Number presentation.
Values are: CPN_DEFAULTDN (default) the T7000 sends the User Portion of the From Header as the Calling Party Number. If the From header does not have a User Portion then the DefaultDN from the Network gateway IP Trunk Group will be sent. DEFAULTDN The T7000 sends the defaultDN of the IPTrunkGroup as the Calling Party Number. DEFAULTDN_CPN The T7000 sends the defaultDN of the IPTrunkGroup as the Calling Party Number if it is provisioned on the IP Trunk group and datafilled in the Subscriber database. If no default DN is provisioned, the T7000 sends the User Portion of the From Header as the Calling Party Number (since DefaultDN is mandatory for a Network gateway IP Trunk Group, this option is the same as DEFAULTDN). NONE The T7000 does not send the Calling Party Number. CPN The T7000 sends the User Portion of the From Header as the Calling Party Number. sendUserForNoANI This option controls what to display on a SIP phone when a call originating from a CAS trunk has no ANI. SEND_UNAVAILABLE "Unavailable" SEND_ANONYMOUS "Anonymous" SEND_PRIVATE "Private" SEND_OUT_OF_AREA "Out-Of-Area"
319
Trunk Groups
Values This option controls which carrier ID to send. Values are: Off (default) Do not send a carrier ID. InbCarrier_OutbCarrier Send the inbound carrier ID, if it is present, otherwise, send the outbound carrier ID, if it is present. InbCarrier_only send the Inbound carrier ID, if it is present. OutbCarrier_InbCarrier Send the outbound carrier ID, if it is present, otherwise, send the inbound carrier ID, if it is present. OutbCarrier_only send the outbound carrier ID if it is present.
routeOnRcvdCarrier
InbCarrier_OutbCarrier route on the Incoming Carrier if available, otherwise, route on the Outbound Carrier. InbCarrier_only route on the Incoming Carrier only. OutbCarrier_InbCarrier (default) route on the Outbound Carrier, if available, otherwise, route on the Incoming Carrier. OutbCarrier_only route on the Outbound Carrier only.
callingPartyPresentationDisplay
This option affects how the switch builds the From header of an INVITE request when the endpoints preferredPrivacyMethod option is set to NO_PRIVACY_METHOD and the calling name or number is restricted. SEND_UNAVAILABLE "Unavailable" SEND_ANONYMOUS (default) "Anonymous" SEND_PRIVATE "Private" SEND_OUT_OF_AREA Out-Of-Area" See: preferredPrivacyMethod on page 437 (SIP Access Gateway Options) preferredPrivacyMethod on page 445 (SIP Emergency Services Gateway Options) preferredPrivacyMethod on page 455 (SIP Network Gateway Options)
revertToPrimaryFE
This option controls how the switch behaves after a failed primary FE recovers. Values are: FALSE (default) the switch continues to use the secondary FE. TRUE the switch reverts to using the primary FE.
320
Trunk Groups
Values This option allows a subscriber who is not assigned to a Voice Mail Service to use call forwarding to forward a call to an M6 VMS. Values are: FALSE (default) the switch checks that a subscriber has voice mail service assigned before processing an incoming NOTIFY message. TRUE the switch processes the incoming NOTIFY message from the voice mail system without checking to see if the subscriber has voice mail service assigned.
chargeNumberChoice
This option selects the Charge Number for the call from one of the following choices: SCREEN_DN set the Charge Number to the screen DN if it exists, otherwise use the default DN of the Trunk Group CALLING_DN set the Charge Number to Calling Party Number if it exists, otherwise use the default DN of the Trunk Group DEFAULT_DN set the Charge Number to the default DN of the Trunk Group DIVERSION_THEN_SCREEN set the Charge Number to the diversion header number if it exists, otherwise use the screen DN if it exists, otherwise use the original address if it exists, otherwise use the Default DN of the Trunk Group. DIVERSION_THEN_CALLING set the Charge Number to the diversion header number if it exists, otherwise use the then original address if it exists, otherwise se the Calling Party number if it exists, otherwise use the Default DN of the Trunk Group DIVERSION_THEN_DEFAULT set Charge Number to the diversion header number if it exists, otherwise use the original address if it exists, otherwise use the Default DN SCREEN_CHOICE (default) set the charge number to the subscriber key
modify IPTrunkGroup IPTG1 options screenDNChoice DEFAULT_DN modify IPTrunkGroup IPTG1 options supportEarlyCutThrough 1
NOTE: The supportEarlyCutThrough attribute is a nested bitfield, and must be handled differently from a normal bitfield. See Limitiations on page 10.
321
Trunk Groups
322
Trunk Groups
The IP Trunk Group restrictions attribute is a bit field, so individual values are:
modify modify
323
Trunk Groups
Service Switching Point (SSP) a switch that recognizes Intelligent Network (IN) calls and can route and connect those calls Access Tandem (AT) a Local Exchange Carrier (LEC) switching system that provides access between a local exchange network and the interexchange networks Interexchange Carrier (IC) a long distance carrier that includes all facilities-based interLATA
NOTE: The trunk group name cannot contain a semi-colon (;), nor can it consist of either the word ALL or the word all facilities A list of the facilities (trunks) in the trunk group. See Adding Facilities to a SS7 Trunk Group on page 344, and See Removing Facilities from a SS7 Trunk Group on page 344. The timers for this trunk group. See SS7 Trunk Group Timers on page 332. The options for this trunk group. See SS7 Trunk Group Options on page 336. FIRST_AVAILABLE always select the first trunk available ROUND_ROBIN (default) sequentially rotate the use of trunks sendOAssistCalls sendDAssistCalls TRUE allow operator assisted calls FALSE (default) do not allow operator assisted calls TRUE allow directory assisted calls FALSE (default) do not allow directory assisted calls
324
Trunk Groups
Attribute tandemRoutingType
Description Sets the type of routing for calls received on the trunk group. For a discussion of this attribute, see The tandemRoutingType Trunk Group attribute on page 234. NO_ROUTING (default) Uses routing based on the dialed number, the subscribers carrier, or the LNP code. CARRIER_ROUTING (default) Forces the calls received on this trunk group to use incoming Tandem Carrier route lists TRUNKGROUP_ROUTING Forces the calls received on this trunk group to use incoming Tandem Trunk Group route lists ANI_ROUTING Forces the calls received on this trunk group to use incoming Tandem ANI route lists
restrictions defaultNPA
The restrictions on this trunk group. See CAS Trunk Group Restrictions on page 250. The NPA to be added when 7-digits are received on an incoming trunk group. The switch adds the defaultNPA to the 7-digits and then routes on 10-digits. This defaultNPA must be a provisioned prefix, see Prefixes on page 403. Length: 3
NOTE: For DIDMF or DIDDTMF CAS trunks, the homeNPA of the defaultDN is added to the 7-digits, if available. If a defaultDN is not available, then the defaultNPA is used. For CAS trunks using FXO protocol, the homeNPA of the subscriber is added on the 7-digits replaceDestinationDigits TRUE allow the use of replacement destination digits (called number) on the trunk group. The switch replaces part or all of the destination digits depending on how the prefix is provisioned, See Subscribers on page 530, Destination Digit Replacement on page 346, and replacementMode on page 405. FALSE do not replace Destination Digits and send the dialed digits. REPLACE_IfNotPorted do not replace Destination Digits in the outgoing signaling messages if the called DN has a non-T7000 LRN associated with it
325
Trunk Groups
Attribute replaceCarrier
group.
TRUE allow the use of PCAC on the trunk group. The switch replaces the CAC depending on how the prefix or carrier is provisioned. See Prefixes on page 403, replacementMode on page 405, and Carriers on page 196. FALSE do not use a PCAC on the trunk group and send the CAC. REPLACE_IfNotPorted do not use a PCAC if the called number has an non-T7000 LRN associated with it and send the CAC. replaceAniDigits
This attribute controls the use of a PANI II digits on the trunk group.
TRUE allow the use of a Pseudo ANI (PANI) on the trunk group. The switch replaces the ANI (calling number) depending on how the prefix is provisioned, see Subscribers on page 530. FALSE do not use a PANI on the trunk group and send the ANI. REPLACE_IfNotPorted do not use a PANI if the called number has an non-T7000 LRN associated with it and send the ANI.
replaceInfoDigits
TRUE allow the use of a PANI II digits on the trunk group. The switch replaces the ANI II digits depending on how the prefix is provisioned,see Subscribers on page 530. FALSE do not use PANI II digits on the trunk group and send the ANI II digits on the facility. REPLACE_IfNotPorted do not use PANI II digits if the called number has an non-T7000 LRN associated with it and send the ANI II digits on the facility
ftrsProfile
The profile assigned to the incoming trunk group. This profile determines how the switch manipulates digits and routing. See FTRS on page 223.
NOTE: A subscriber profile takes precedence over an incoming trunk group profile. For example, if a subscriber has a profile assigned and is in a FXO trunk group with a profile, the switch uses the subscriber profile. For more information, consult the T7000 Provisioning Guide.
326
Trunk Groups
Attribute replaceCSI
Description
This controls the use of the Carrier Selection Information parameter in outgoing messages on the trunk group.
TRUE allow the use of a PCSI on the trunk group. The switch replaces the outpulse of the CSI parameter depending on how the prefix is provisioned, see Subscribers on page 530 FALSE do not send a PCSI on the trunk group and send the CSI. REPLACE_IfNotPorted do not use PCSI if the called number has an non- T7000 LRN associated with it and send the CSI.
localTermination
The localTermination attribute controls if incoming trunk group allows for local terminations or not. If it does not allow for local terminations then use the trunk group in a tandem routing application. If you allow local terminations in a tandem routing trunk group, then if the DN terminates on the switch the calls for that DN will not be tandemed out of the switch.
ALLOW (default) allow incoming calls on the trunk group to terminate on the switch. NOT_ALLOWED only allow incoming calls to tandem through the switch.
tandemDefaultRoutingType The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP(default) Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list. USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list. USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment. miscOptions The miscellaneous options to add to the trunk group. Miscellaneous options are added using In Service Upgrades (ISUs). An ANI deny list name from the screen list database. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked.See Screen Lists on page 415, and Prefixes on page 403.
denyAniList
327
Trunk Groups
Attribute direction
Description ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions.
NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch.
BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call tandemCustomReplacement Used to outpulse 7 digits for tandem calls. NO (default) no special outpulsing is performed. YES outpulse 7 digits for non-ported subscribers. See 7 Digit Tandem Call Outpulsing on page 409. pointCode type point code of non-adjacent node to which trunk group connects. See Point Codes on page 470. The signaling type that matches the connection at the other end: ANSI for American National Standards Institute signaling type primarily used in North America ITU Internal value, not available in current release
328
Trunk Groups
Attribute isdnMsgTrace
Description This debug attribute controls how the switch shows ISDN Call Establishment, Call Clearing, Maintenance and Miscellaneous messages. The messages are displayed when running a CLI session on the card that has the SS7 Trunk Group. MSG_TRACE_NONE The message trace for this trunk group is off. MSG_ONLY Shows ISDN Call Establishment, Call Clearing, Maintenance, and Miscellaneous messages in a Procomm window that connects to the card that contains the span. MSG_WITH_INBOUND_DUMP Shows ISDN messages and a dump of inbound IEs. MSG_WITH_OUTBOUND_DUMP Shows ISDN messages and a dump of outbound IEs. MSG_WITH_BOTH_DUMP Shows ISDN messages and a dump of inbound and outbound IEs.
CAUTION
Contact Taqua TAC Support before using this option. defaultJIP This optional attribute is used to specify a default Jurisdiction Information Parameter (JIP) when the JIP is not included in an incoming IAM message. JIP is an optional parameter in the IAM message, but it should always be included when feasible. If an IAM message is received without a JIP, the defaultJIP will be used to determine the Rate Center and recorded in the CDR. If the call is forwarded through the switch, the defaultJIP will be sent if the incoming IAM did not include a JIP. The defaultJIP should reflect the LATA or MSC of the originating switch, and be in the form of NPA-NXX. E911DefaultANI This attribute is used to specify a 10 digit ANI when a 911 call is made and neither the Calling Number nor the Charge Number contains a 10 digit ANI.
329
Trunk Groups
The Generic CLI is used for all SS7 Trunk Group commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key pointCode
type
timers options selectionMethod sendOAssistCalls sendDAssistCalls tandemRoutingType restrictions defaultNPA replaceDestinationDigits replaceCarrier replaceAniDigits replaceInfoDigits ftrsProfile replaceCSI localTermination tandemDefaultRoutingType denyAniList direction type isupMsgTrace
330
Trunk Groups
facilities
See Adding Facilities to a SS7 Trunk Group on page 344, and Removing Facilities from a SS7 Trunk Group on page 344.
Prerequisites
Provision the SS7 network before provisioning SS7 trunk groups, see createSS7Network on page 475. Provision a non-adjacent SS7 node with the same point code as the SS7 trunk group before provisioning an SS7 trunk group, see createNode on page 476.
createSS7Network net y n createNode remote 229-101-000 net Y n n create SS7TrunkGroup SSP1 229-101-000 ANSI modify SS7TrunkGroup SSP1 sendOAssistCalls FALSE query SS7TrunkGroup SSP1 options destroy SS7TrunkGroup SSP1
331
Trunk Groups
332
Trunk Groups
Timer T12
Description The time between the Blocking message and the Blocking Acknowledge message. Resends a Blocking message and restarts T12 when the timer expires. Default: 10,000 ms The time between the initial Blocking message and the Blocking Acknowledge message. Resends a Blocking message, starts T13 timer, and stops the T12 timer when the timer expires. Default: 60,000 ms The time between the initial Blocking message and the Blocking Acknowledge message. Resends Unblocking message and restarts T14 when the timer expires. Default: 10,000 ms The time between the initial Unblocking message and the Unblocking Acknowledge message. Resends Unblocking message, starts T15 timer, and stops T14 when the timer expires. Default: 60,000 ms The time between the sending of a Reset Circuit message not due to a T5 timer ending and the receipt of Release Complete message. Resends Reset Circuit message and restarts T16 when the timer expires. Default: 10,000 ms The time between sending an initial Reset Circuit message not due to the expiration of T5 and receiving a Release Complete message. Resends the Reset Circuit message, restarts T17, and stops T16 when the timer expires. Default: 60,000 ms The time between a Circuit Group Blocking message and the receipt of Circuit Group Blocking acknowledgement. Resends the Circuit Group Blocking message and restarts T18 when the timer expires. Default: 10,000 ms The time between the initial Circuit Group Blocking message and the receipt of Circuit Group Blocking acknowledgement. Resends the Circuit Group Blocking message, restarts T19, and stops T18 when the timer expires. Default: 60,000 ms
T13
T14
T15
T16
T17
T18
T19
333
Trunk Groups
Timer T20
Description The time between the initial Circuit Group Unblocking message and the receipt of Circuit Group Unblocking acknowledgement. Resends Circuit Group Unblocking message and restarts T20 when the timer expires. Default: 10,000 ms The time between the initial Circuit Group Unblocking message and the receipt of Circuit Group Unblocking acknowledgement. Resends Circuit Group Unblocking message, restarts T21, and stops T20 when the timer expires. Default: 60,000 ms The time between the Circuit Group Reset message and the receipt of an acknowledgement. Resends Circuit Group Reset message and restarts T22 when the timer expires. Default; 10,000 ms The time between the initial Circuit Group Reset message and the receipt of an acknowledgement. Resends Circuit Group Reset message, restarts T23, and stops T22 when the timer expires. Default: 60,000 ms The time between sending a check tone and the receipt of the backward check tone. Sends Continuity message indicating failure and starts T25 when the timer expires. Default: 1,900 ms The time between the first Continuity Check failure and when continuity is detected. Sends a Continuity Check Request message and repeats Continuity Check when the timer expires. Default: 5,000 ms The time between a second Continuity Check failure and continuity is detected. Sends a Continuity Check Request message, restarts T26, and checks continuity when the timer expires. Default: 60,000 ms The time between the receipt of a Continuity message indicating failure of repeat continuity check and the receipt of Continuity Check Request message. Sends Reset Circuit message, starts T16, and stops T17 when the timer expires. 180,000 ms The time between a Circuit Query message and the receipt of Circuit Query Response message. 10,000 ms
T21
T22
T23
T24
T25
T26
T27
T28
334
Trunk Groups
Timer T34
Description The time between sending a Loop-Back Acknowledge message in response to the receipt of Continuity Check Request message and a Continuity or Release message. Releases all equipment, sends a Reset Circuit message, starts T16, and stops T17 when the timer expires. Default: 10,000 ms The time between a Circuit Reservation Acknowledge message and the receipt of Initial Address message or Release message. Initiates the release procedure when the timer expires. Default: 20,000 ms The time between a Circuit Validation Test message and the receipt of Circuit Validation Response message. Resends the Circuit Validation Test message and restarts TCVT when the timer expires. Default: 10,000 ms The time between a Continuity Check Request message and the receipt of Loop-Back Acknowledgement message. Sends a Reset Circuit message, starts T16, and starts T17 when the timer expires. Default: 20,000 ms The Hardware Carrier Group Alarm is the time between carrier loss and carrier restore. Default: 120,000 ms The time between receiving an ACC indicator and expiration of the alarm. Removes the ACC controls in the exchange when the timer expires. Default: 5,000 ms The time between a Circuit Group Blocking message and the receipt of Circuit Group Blocking or Circuit Group Unblocking message. Accepts the subsequent Circuit Blocking message as a new message when the timer expires. Default: 5,000 ms The time between a Circuit Group Reset Message and the receipt of Circuit Group Reset Message. Accepts the subsequent Circuit Group Reset Message as a new message when the timer expires. Default: 5,000 ms
TCRA
TCVT
TCCR
THGA
TACC
TCGB
TGRS
335
Trunk Groups
336
Trunk Groups
Values Determines how the calling name, if available, will be sent in the Initial Address Messages. 0=FALSE do not send calling name 1=sendGenericName include calling name in the generic name parameter 2=sendPartyInfo include calling name in party info parameter if the calling name is not restricted 3=sendPartyInfoThenGn include the calling name in party info parameter if the calling name is not restricted, otherwise include calling name in the generic name parameter
sendCallingNumber
Indicates if the number of the calling party is included in signaling for the trunk group. 0=False 1=True
sendCarrierId
Indicates if the carrier identification of the service provider is included in signaling for the trunk group. 0=False 1=True
sendJurisdictionInformation
Indicates if the information about the geographic boundary of the service provider is included in signaling for the trunk group. This is the LRN value assigned to the originating rate center of the calling party. 0=False 1=True
sendChargeNumber
The charge number is one of the following: Billing number for subscribers located on the switch, the ANI for calls received on CAS trunk groups, or the charge number received on PRI and SS7 trunk groups. If a charge number is not received, the switch uses the Calling Party Number. The options for charge number are: 0=IF_NOT_CALLING sends the Charge Number parameter only when the value is different from the Calling Party Number parameter value for the call 1=ALWAYS_CPN_CHARGE_NUM always sends the Calling Number as the Charge Number. 2=NEVER never sends a Charge Number parameter 3=ALWAYS_CHARGE_NUM always sends the Charge Number parameter\.
337
Trunk Groups
Values Indicates if the status of the telephone line (including: ringing, busy ring, voicemail answering, intercept) is included in signaling for the trunk group. 0=False 1=True
terminationType
Indicates the type of SS7 termination switch: 0=SSP Switch Signaling Point for terminations to another End Office 1=AT Access Tandem for terminations to a Class 4 switch 2=IXC Inter Exchange Carrier for terminations to a carrier switch
continuityProcedure
Indicates the type of wire, either 2 wire (2w) if the terminating switch is analog or 4 wire (4w) if it is digital. 2=2wsends COT at 1780Hz and receives COT at 1780Hz 4=4wsends COT at 2010Hz and receives COT at 2010Hz
sendHopCounter
Sends the hop parameter (the number of nodes between a source and a destination) in the Initial Address message. 0=False 1=True
OLIRequired
Allows the switch to accept an inbound call without the Originating Line Information (OLI) parameter in an Initial Address Message (IAM). 0allow the switch to accept these calls 1not allow the switch to accept these calls.
sendGenericDigits
Allows the switch to send digits in the outgoing IAM message that identify supplementary service, for example the Calling Name Delivery is allowed or restricted 0=False 1=True
338
Trunk Groups
Values Set BLV/BLI only on trunk groups coming from an operator station. One trunk group is required for each service. 0=NONE 1=BLVBusy Line Verification allows an external operator to verify if a subscriber line is busy. An operator calling over a BLV trunk receives a busy signal if the line is busy or a ring-back if the line is idle. 2=BLIBusy Line Interrupt allows an external operator to interrupt a busy line. An operator calling over a BLI trunk interrupts the busy subscriber who can either drop the existing conversation and accept the operator call or continue with the existing conversation.
sendTNS
Options for sending the Transit Network Selection (TNS) parameter in the IAM for non-SAC calls (for AT and IXC terminationType trunk groups): 0=STANDARDsends the TNS according to the definitions in GR-394-CORE: For a terminationType of AT, the switch always sends the TNS if the carrier is not 0110 For a terminationType of IXC, the switch only sends the TNS for international calls 1=ALWAYSalways send TNS regardless of terminationType or carrier 2=NEVERnever send TNS regardless of terminationType or carrier 3=CARRIER_NOT_0110send TNS only if the carrier value for the call is not 0110, for AT terminationType trunk groups only (Note: 0110 is the CAC for SAC calls.) 4=CARRIER_0110send TNS only if the carrier value for the call is 0110, for AT terminationType trunk groups only
NOTE: The sendTNS field does not apply to trunk groups with an SSP terminationType, the switch never sends the TNS for this type.
339
Trunk Groups
Values Options for sending the Transit Network Selection (TNS) parameter in the IAM for SAC calls (for AT terminationType trunk groups): 0=STANDARDif switch does not perform the SCP dip for the SAC number, the switch always sends a TNS parameter with carrier value 0110 1=SAC_CARRIER_0110the switch sends the TNS parameter only if the carrier value for the call is 0110 2=NEVERthe switch never sends the TNS parameter
releaseOption
RELEASE_CALL sends a release with cause (rejects the call) to the far end when a call cannot be completed, use in tandem applications RELEASE_TREATMENT releases the call and send it to treatment
send00asOLI
In the Initial Address Message (IAM), the T7000 includes the Originating Line Identifier (OLI) parameter. OLI is populated using the provisioned originatingLineType for subscriber originations, and the received OLI/facility information digits value for trunk group originations. 1=TRUEIf an OLI parameter is sent in the outgoing IAM, the T7000 sets the OLI value to 00 for all calls routed on the SS7 trunk group. 0=FALSEIf an OLI parameter is sent in the outgoing IAM, the T7000 sends the originating OLI/Information digit value in the outgoing IAM.
keepIncoming7dNOA
When the NPA is added, this option checks the nature of address (NOA) for the called number included in the outbound IAM: 0=TRANSLATE_NOANOA changes from SUBSCRIBER_NUMBER to NATIONAL_NUMBER 1=KEEP_NOANOA stays the same
routeAdvance
1=TRUEif a specific cause value is returned, attempt to route the call on the next trunk group in the route list. 0=FALSEif a specific cause value is returned, the call routes to treatment
340
Trunk Groups
Values This option controls how the Calling Name is presented. The Calling Name is conveyed using ASCII characters. Normally, the Calling Name is composed of characters from the lower half of the 256 ASCII character set. However, sometimes characters from the upper half are sent as well. Although the upper half of the ASCII character set contains mostly graphics characters, it also contains some characters used in European languages, such as , , and . Unfortunately, some switches will interpret a character from the upper half of the ASCII character set as being the end of the Calling Name (technically, this is called the Extension Bit, and it indicates the last octet in the field). In such a case, you will need to set this attribute to FALSE to prevent the T7000 from confusing the switch at the other end. Values are: FALSE (default) limits the value of characters in the Calling Name to the lower half of the ASCII character set. TRUE does not limit the values of characters in the Calling Name.
sendCPCategoryAsEmergency ForESGW
Overrides the call type of calls sent from an Emergency Services Gateway. Such calls are translated by the gateway into a 10 digit DN, which may be recognized by the PSAP as a 911 call. TRUE forces the ESGW call type to be e911 FALSE (default) sends the default call type for the call.
doNotUseJipForCallingNumber
Determines if the call type is determined by JIP (the Jurisdiction information parameter, which is optionally sent by the originating exchange in the IAM message). Only affects calls which have the JIP available. TRUE do not use the jurisdiction Info number to determine the call type. FALSE (default) use the jurisdiction Info number to determine the call type.
341
Trunk Groups
Values This option determines the handling of Carrier Code information in the CDR of a call that was routed using carrier routing. TRUE populate the CDR with the outbound Carrier Code, regardless of how the call is routed. FALSE (default) only populate the CDR with the outbound Carrier Code when the call is routed using Carrier Routing.
passFacilityMessage
Determines if the switch passes any received ISUP FACILITY message from an inbound SS7 trunk to the outbound SS7 Trunk Group. TRUE pass any received ISUP FACILITY message on to the outgoing SS7 trunk group. FALSE (default) do not pass the received ISUP FACILITY message on to the outgoing trunk group.
routeOnRcvdCarrier
InbCarrier_OutbCarrier route on the Incoming Carrier if available, otherwise, route on the Outbound Carrier. InbCarrier_only route on the Incoming Carrier only. OutbCarrier_InbCarrier (default) route on the Outbound Carrier, if available, otherwise, route on the Incoming Carrier. OutbCarrier_only route on the Outbound Carrier only.
NOTE: The incoming carrier is the CARRIER ID parameter received on SS7 trunk groups. The outbound carrier ID is the carrier value received in the TNS parameter for SS7 trunk groups sendToneOnE911TrunkAtOnHook Determines if the switch sends a tone to the PSAP if an E911 caller goes on hook TRUE switch sends dial tone to the PSAP if an E911 caller goes on hook. FALSE (default) no tone is sent ignore1stFacilityMessage This option determines the handling of the ISUP Facility message. It was added for Canadian 911 service. TRUE ignore the Facility message. FALSE (default) do not ignore the Facility message.
modify SS7TrunkGroup SSP1 options sendCPCategoryAsEmergencyForESGW TRUE modify SS7TrunkGroup SSP1 options sendSACTNS SAC_CARRIER_0110
342
Trunk Groups
NO_INBOUND_PAYSTATIO Does not allow a non-subscriber-initiated call if the N information digit/OLI is 7, 29 or 70. NO_INBOUND_WITHOUT_ ANI Does not allow calls that do not include the ANI.
The SS7 Trunk Group restrictions attribute is a bit field, so individual values are:
modify modify
343
Trunk Groups
Adding Facilities to a SS7 Trunk Group insertInto SS7TrunkGroup <key> facilities <subkey> TGFacility <subvalue>
Use the Generic CLI insertInto command to add a trunk to an SS7 Trunk Groups facilities list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
Tip
Use a index of 1 to insert a facility at the start of the facilities list. Use a index of -1 to insert a facility at the end of the facilities list.
<subvalue>
This attribute specifies which trunk you want to add to the Trunk Group.
The following command adds trunk 0 on the local card to SS7 Trunk Group SSP1:
insertInto SS7TrunkGroup SSP1 facilities 1 SS7Facility Trunk-0-1-27 1
Removing Facilities from a SS7 Trunk Group deleteFrom SS7TrunkGroup <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a trunk to an SS7 Trunk Groups facilities list. See the deleteFrom example on page 21 for a detailed explanation of this command.
NOTE: You must first lock the Trunk before you can remove it from the Trunk Group.
Syntax <key>
Description
<subkey>
The following example locks trunk 0 on the local card and then removes it from SS7 Trunk Group SSP1:
344
CAC Substitution uses a Pseudo Carrier Access Code (PCAC) that replaces the original pre-subscribed or dialed CAC in the signaling message.See CAC Substitution on page 346.
Destination Digit Replacement uses a replacement string of digits that replace or overlay digits in an original destination number. The new number is sent as the called number in the signaling message.See Destination Digit Replacement on page 346. ANI Replacement uses Pseudo ANI (PANI) digits that replace the original ANI (calling number). The PANI is sent out in the outgoing signaling message.See ANI Replacement on page 347. ANI II Digit Replacement uses PANI II digits that replace the original ANI II digits. The PANI II digits are sent out in the outgoing signaling message. See ANI II Digit Replacement on page 347. CSI Replacement uses a Pseudo Carrier Selection Information (PCSI)
value that defines if a subscriber is presubscribed to a carrier or not. CSI replacement applies only to calls originating on the switch. See CSI Replacement on page 348.
NOTE: The Flexible Translation, Routing, and Signaling (FTRS, see FTRS on page 223) feature also customizes outgoing signaling information for in-band and outof-band signaling. If FTRS and Outgoing Signal Customization are provisioned on a switch, FTRS takes priority over Outgoing Signal Customization.
Outgoing Signal Customization only applies to calls originating on the switch, as well as to calls tandemed through the switch on CAS, PRI, IP and SS7 Trunk Groups. This feature applies to all subscriber originations on the switch, including: analog lines, GR-303, a PBX with a default DN, and hunt groups. However, outgoing Signal Customization does not affect:
CDR
E911 calls
The callType of the CDR is the call type of the call before outgoing signaling customization occurs. Each of the pseudo replacements have their own unique CDR field.
345
CAC Substitution
CAC Substitution provisions a PCAC that is sent in the outgoing call setup signal. In standard call processing, the CAC in the outgoing signaling message is the same as the CAC used for routing. When the leading digits of an Original Destination Number match a terminating prefix with a PCAC, this feature sends a different CAC (the PCAC) in the signaling message in place of the one the switch uses to route the call.
For CAS signaling the switch sends the PCAC in the outgoing signaling message. For SS7 signaling the switch sends the PCAC in the optional Transit Network Selection (TNS) and Carrier Identification Parameter (CIP) parameters of the Initial Address Message (IAM). To set the TNS, use the Generic CLI modify command on the Carrier to set the circuit code. See
Carriers on page 196.
For PRI signaling, if the TNS Information Element (IE) is sent in the SETUP, the switch sends the PCAC in the TNS IE.
The following objects determine the CAC the switch uses to route the call:
The pre-subscribed carrier for the subscriber (PIC1/PIC2) The carrier from the 101XXXX CAC dialed by the subscriber The switchs default OS and DA carriers The switchs default PIC2 carrier
For CAS signaling the switch sends the modified destination digits in the outgoing signaling message. For SS7 signaling the switch sends the modified destination digits in the Called Party parameter of the IAM. For PRI signaling the switch sends the modified destination digits in the Called Party Number of the SETUP message.
346
ANI Replacement
ANI (calling number) Replacement provisions a Pseudo ANI (PANI) sent in outgoing call setup messages. In standard call processing, the ANI sent in the outgoing signaling message is the same as the ANI of the subscriber. This feature sends a different ANI (the PANI) in the signaling message in place of the subscriber's ANI. When leading digits of an Original Destination Number match a terminating prefix with a PANI assigned:
For CAS signaling the switch sends the replacement ANI in the outgoing signaling message. (Except for FGC.) For SS7 signaling the switch sends the replacement ANI in the Calling Party parameter in the IAM. For PRI signaling the switch sends the replacement ANI in the Calling Party Number of the SETUP message.
For CAS signaling the switch sends the PANI II digits in the outgoing signaling message. For SS7 signaling the switch sends the PANI II digits in the IAM.
347
CSI Replacement
Replaces the Carrier Selection Information (PCSI) value, which defines if a subscriber is presubscribed to a carrier or not. CSI replacement applies only to calls originating on the switch. The CSI is an optional parameter in the SS7 Initial Addressing Message (IAM). For CAS, the CSI is the KP digit in the ANI sequence. The CSI value overrides the ANI KP type in the CAS protocol.Outgoing Signal
CSI Value SS7 Selected CAC presubscribed and not input by calling party 0000 0001 Selected CAC presubscribed and input by calling party Selected CAC presubscribed, no indication of whether input by calling party CAS Selected CAC presubscribed and not input by calling party FGCOS DP=KP DTMF=KP' FGDAT/OS DP=KP DTMF=KP Selected CAC presubscribed and input by calling party FGCOS DP=KP DTMF=KP FGDAT/OS DP=KP DTMF=KP Selected CAC presubscribed, no indication of whether input by calling party FGCOS DP=KP DTMF=KP FGDAT/OS DP=KP DTMF=KP Selected CAC not presubscribed and input by calling party FGCOS DP=KP DTMF=KP FGDAT/OS DP=KP DTMF=KP 0000 0010 0000 0011 Outpulse
Selected CAC not presubscribed and input by calling party 0000 0100
348
Replacement Mode
Controls what is or is not replaced on a Prefix, i.e., sets the replacement mode for a prefix on the switch. For details, see Prefixes on page 403, and replacementMode on page 405. The following table contains examples of digit replacement.
Original No. Replace Prefix 972 692 1909 972 692 1909 972 692 1909 972 692 1909 972 692 1909 972 692 1909 972 692 1909 972 692 1909 972 692 1909 972 692 1909 555 1212 972 692 972 692 972 692 972 692 972 692 972 692 972 692 972 692 972 692 972 692 1909 972 555 1212 817 540 540 817 540 4 817 540 817 817 540 4 817540 817 817 5 404 817 540 5575 004 555 1212 005 555 1212 817 540 1909 540 1909 817 540 4 1909 817 540 1909 817 692 1909 817 540 4909 817540 817 817 5 404 817 540 5575 004 555 1212 005 555 1212 Same length replacement of the prefix Shorter replacement of the prefix Longer replacement of the prefix Same length overlay of digits Shorter overlay of digits Longer overlay of digits Same length replacement of digits Shorter replacement of digits Longer replacement of digits Same length replacement of digits 972 is the home NPA of the caller 214 is the home NPA of the caller Prefix Replacement Digits Digits in Outgoing Signal Description
349
Use the Generic CLI modify command on the Prefix object (see Prefixes on page 403) replacementDigits attribute to set replacement destination digits (called number) for the original destination number in the outgoing call setup message. Use the Generic CLI modify command on the Prefix object (see Prefixes on page 403) and the replacementMode attribute (see replacementMode on page 405) to set the replacement mode for a prefix. Use the Generic CLI modify command on the Prefix object (see Prefixes on page 403) replacementCSI attribute to set the replacement CSI for subscriber. Use the Generic CLI modify command on the Prefix object (see Prefixes on page 403) replacementAniDigits attribute to set the replacement digits for the ANI (calling number) of a call. Use the Generic CLI modify command on the Prefix object (see Prefixes on page 403) replacementInfoDigits attribute to set Pseudo ANI II (PANI II) digits sent in outgoing call setup messages.
2. Use the Generic CLI modify command to set the PCAC for a carrier object that is sent in the outgoing call setup signal. See Carriers on page 196. 3. Use the Generic CLI modify command on the Carrier to set the circuit code in the optional Transit Network Selection (TNS) parameter sent with the associated CAC or PCAC, when using SS7 trunks. See Carriers on page 196. 4. Use the Generic CLI modify command to control the use of digit, PCAC, ANI, and ANI II digit replacement on a trunk group. This enables the outgoing signal customization feature on the applicable trunk groups. See Trunk Groups on
page 233.
350
GR-303
GR-303
General Requirements (GR)-303 is a group of specifications. The switch uses GR303 to be part of an Integrated Digital Loop Carrier (IDLC) system. The GR-303 option configures and connects the switch to a Remote Digital Terminal (RDT). The RDT, in turn, connects to subscribers telephones.
createRDT
This command was replaced in Release 6.0.1 with the Generic CLI create command. See Interface Groups on page 258
replaceRDT
replaceRDT <name> <location> <vendor> <primarySpanOID> <primarySpanLogicalID> <secondarySpanOID> <secondarySpanLogicalID> [flow-thru provisioning]
This command changes the attributes of an existing RDT. See createRDT on page 351 for information on each attribute.
CAUTION
Replacing an RDT may negatively affect operations.
replaceeRDT RDT1
Dependent Commands
Add analog lines and spans:
351
GR-303
Prerequisites
RDT, see createRDT on page 351
Syntax rdtName RDT name Description
reprovisionRDT RDT1
Dependent Commands
After reprovisioning the RDT, you can:
352
GR-303
provisionRDTLine provisionRDTLine <rdtName> <startTermId> [endTermId] [loop | ground] [2wire | 4wire] [setOOS]
This command provisions one or more RDT analog lines connecting the RDT to subscribers.
Prerequisites
RDT, see createRDT on page 351.
Syntax <rdtName> [endTermId] [loop ground] name of RDT number of the last analog line on the RDT to add. If adding only one analog line, do not enter this value. loopstart if the RDT provides battery on the ring and ground on the tip groundstart if the RDT provides battery on the ring and open (0 VDC) on the tip. Description
<startTermId> the number of the first analog line on the RDT to add (1-2048)
NOTE: The RDT must have a line card that can recognize groundstart [2wire 4wire] [setOOS] 2wire terminating switch is analog 4wire terminating switch is digital sets the line(s) out of service
NOTE: To put the line in the in-service state, ensure the physical connection has been made and skip this parameter.
Dependent Commands
After you add analog lines you can:
add GR-303 subscribers, see Subscribers on page 530. bring the line into service, restoreRDTLine on page 355.
353
GR-303
Prerequisites
RDT lines, see provisionRDTLine on page 353.
Syntax <rdtName> <termId> [endTermId] name of RDT number of the first analog line on the RDT you want to deprovision (12048) number of the last analog line on the RDT to deprovision if deprovisioning only one analog line, do not enter this parameter Description
354
GR-303
Prerequisites
RDT lines, see provisionRDTLine on page 353. RDT lines, see removeRDTLine on page 355.
Syntax <rdtName> <termld> name of RDT number of the RDT analog line on the RDT to restore (1-2048) Description
Prerequisites
RDT lines, see provisionRDTLine on page 353.
Syntax <rdtName> <termld> [normal forced] name of RDT number of the RDT analog line on the RDT to remove (1-2048) normal removes the RDT analog line from service after all calls currently in progress have been completed forced removes the RDT analog line from service regardless of whether or not calls are in progress. Calls in progress on that line are dropped Description
355
GR-303
syncDS1Line RDT1 1 28
Prerequisites.
RDT lines, see provisionRDTLine on page 353.
Syntax <rdtName> [endTermId] name of RDT last RDT analog line on the RDT to sync (1-2048) Description
356
GR-303
Prerequisites
RDT with EOC or TMC, see createRDT on page 351..
Syntax <rdtName> name of RDT Description
syncRDTClock RDT1
Prerequisites
RDT with EOC or TMC, see createRDT on page 351..
Syntax <rdtName> <on off> name of RDT on turns EOC audits on off turns EOC audits off Description
357
MGCP
MGCP
Order of Provisioning
For information on the commands included in the above provisioning flow, refer to the following topics in the VoIP section:
The Generic CLI is used for all MGCP commands, see Using Generic CLI
Commands on page 6.
358
MGCP
tandemDefaultRoutingType The order route lists are used if the T7000 has a tandem trunk group route list provisioned, but this route list does not have trunks assigned: USE_CARRIER_NANP Calls default to a carrier route list. If a carrier is not assigned, calls default to a NANP route list USE_NANP_CARRIER Calls default to a NANP route list. If a NANP route list is not assigned, calls default to a carrier route list USE_CARRIER_ONLY Calls default to a carrier route list. If the carrier is assigned, but the carrier route list is does not have trunks assigned to it, route to treatment. USE_NANP_ONLY Calls default to a NANP route list. If the a NANP route list is assigned, but the NANP route list does not have trunks assigned to it, route to treatment. miscOptions denyAniList Miscellaneous options are added using ISUs. These appear at the trunk group level. The name of a previously created screening list. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415.
359
MGCP
attribute direction
value ONE_WAY_IN One-way incoming trunk groups allow incoming calls, but not outgoing calls. The facilities are dedicated to receiving calls. When the connection is made, however, data or voice can travel in both directions. ONE_WAY_OUT One-way outgoing trunk groups allow outgoing calls, but not incoming calls. The facilities are dedicated to sending calls. When the connection is made, however, data or voice can travel in both directions. NOTE: ONE_WAY_IN and ONE_WAY_OUT trunk groups work together to allow two-way communication. A ONE_WAY_OUT trunk group from one switch connects to a ONE_WAY_IN trunk group at another switch. BI_DIRECTIONAL Bi-directional trunk groups allow both incoming and outgoing calls. In a bi-directional trunk group, a trunk can be an incoming trunk on one call and an outgoing trunk on the next call
tandemCustomReplaceme nt
Used to outpulse 7 digits for tandem calls. NO (default) no special outpulsing is performed. YES outpulse 7 digits for non-ported subscribers. See 7 Digit Tandem Call Outpulsing on page 409
codecListName
The name of the codec list for this trunk group. A codec list is a container for codec profiles that are associated with one or more IP or MGCP trunk groups. See CodecProfileList on page 425. The name of the media stream parameter for this trunk group. Media stream parameters control the characteristics of the bearer or RTP portion of a VoIP call. See MediaParam on page 431. The maximum number of active calls this trunk group can handle. Since an MGCP trunk group has no physical facilities, there would otherwise be no limit to the number of calls that a subscriber or a group of subscribers could originate or terminate. Note: This field is read-only. This dynamic field shows the number of calls the trunk group is currently carrying.
mediaParamName
maximumCalls
activeCalls
operationalState
Note: This field is read-only. UNREACHABLE Network problems are preventing the switch from communicating with the IP endpoint at the other end of the MGCP Trunk Group. REACHABLE the switch can communicate with the IP endpoint at the other end of the MGCP Trunk Group
360
MGCP
value
LOCKED The MGCP Trunk Group is administratively prohibited from providing services. See lock on page 7. UNLOCKED The MGCP Trunk Group is administratively allowed to provide services. See unlock on page 7. SHUTTING_DOWN The MGCP Trunk Group is currently providing services, but no new services are allowed to start. As soon as the last service completes, the administrativeState will automatically transition to LOCKED. See shutdown on page 7. bearerAuditTimer1 The time, in milliseconds, after the IP call is established to initiate a check for received RTP packets. The default is 3600000 milliseconds (3600 seconds, or one hour). The time, in milliseconds, after bearerAuditTimer1 has expired to check for received RTP packets. The default. is 600000 milliseconds (600 seconds, or ten minutes) auditBearerResources This flag enables or disables bearer audits. Bearer audits timers prevent a hung IP call from using bandwidth. When bearer audits are enabled, the switch compares RTP packet counts from bearerAuditTimer1 and bearerAuditTimer2. If the count is the same, indicating that no RTP packets have been exchanged, the switch tears down the call. If the count is different, indicating RTP packets have been exchanged, auditing restarts. The default is TRUE. Assigned key string for customized Digit Map. See Digit Maps on page 378.
bearerAuditTimer2
digitMapKey
361
MGCP
key
defaultDN
options defaultDN tandemDefaultRoutingType denyAniList direction codecListName mediaParamName maximumCalls bearerAuditTimer1 bearerAuditTimer2 auditBearerResources digitMapKey create CardConfiguration pic1 PIC 10 create MGCPTrunkGroup ipgrp1 modify MGCPTrunkGroup ipgrp1 maximumCalls 250 lock MGCPTrunkGroup ipgrp1 destroy MGCPTrunkGroup ipgrp1
362
MGCP
supportEarlyCutThrough For devices (typically IVRs) that need to cut through the twoway voice path before the call is answered. Do not set this option for devices that support cutting through the two-way voice path after the call is answered. Values are: ON support early cut through of the two-way voice path before the call is answered. OFF (default) do not support early cut through of the twoway voice path before the call is answered.
modify MGCPTrunkGroup ipgrp1 options supportEarlyCutThrough ON
363
MGCP
MediaGatewayProfile
A MediaGatewayProfile defines different types of media gateways. Associate one or more MediaGateways with a media MediaGatewayProfile. A MediaGatewayProfile has the following attributes:
attribute key terminationPrefix values name of MediaGatewyaProfile the prefix portion of the analog access line local termination names: aaln/# analog access lines, for example: aaln/1, aaln/2 phone phones, for example: phone1, phone2 requestedInfo a bitfield of information the T7000 can audit. These options are individually turned on or off by name. REQUESTED_EVENTS DIGIT_MAP SIGNAL_REQUESTS REQUEST_IDENTIFIER NOTIFIED_ENTITY CONNECTION_IDENTIFIER DETECT_EVENTS OBSERVED_EVENTS VERSION_SUPPORTED REASON_CODE EVENT_STATES (default) MAX_MGCP_DATAGRAM CAPABILITIES quarantineHandling NONE If the MediaGateway cannot process the MGCP command CRCXs Q parameter, set this to NONE STEP one notification per NotificationRequest is allowed LOOP (default) multiple notifications per NotificationRequest are allowed supportedPackages a bitfield of packages supported by the T7000. These options are individually turned on or off by name. LINE (default) GENERIC (default) DTMF (default) MEDIA_FORMAT
364
MGCP
attribute signalSupport
values a bitfield that describes the behavior of a signal sent to the MediaGateway. These options are individually turned on or off by name. See example. NOTE: Gateways from different vendors require different sets of attributes. Before setting these attributes, Read Your Friendly Manual to see which attributes your Gateway requires! CRCXorRQNTwithTO when sending a CRCX or RQNT, include a "t" with the digit map parameter. Some MTAs won't work without the "t" CRCXwoSDP send offering CRCX without SDP. Send MDCX with SDP after call been established DetectEvt4EmbedRQNT send Detect Events in embedded RQNT IgnoreOffOnHookEvts when the PostEmbeddedRQNT option is selected, the NOTIFY received may contain OffHook and OnHook events without any digits. This option allows the switch to ignore the OffHook/OnHook event and not send a CRCX/DLCX... when Media Terminations is in the idle (OnHook) state LCFOSupport select if the MTA/CM supports the ability to send the Loop Current Feed Open (LCFO) signal when the termination disconnects, required by some terminations (default is on) MDCXonConnect if enabled the T7000 sends MDCX when the call has been answered (default is off) MDCXonTransient after the subscriber has dialed all of their digits, some MTAs require the Call Agent to send a MDCX indicating a media direction of "sendRecevie". Otherwise, when the called party answers, they get a one way voice path PostEmbeddedRQNT send an embedded RQNT when the MGCP phone goes onhook. This RQNT contains a digitMap (D: field). The next time the MGCP phone goes offhook, it plays dial tone and collects digits, based on the digitMap. When the phone matches a dialing pattern from the digitmap, or detects an inter-digit timeout, it sends a NOTIFY containing both the offhook event and collected digits.
Tip
If the MGCP phone supports an embedded RQNT, Taqua recommends using this option, since it results in significantly fewer messages passed between the phone and the switch.
365
MGCP
values ROHToggle if S:ot(-) is sent to MTA/CM to turn off ROH at ROH timeout (default is off) RQNTonHookEvent if enabled the T7000 sends RQNT when it receives NOTIFY hook event (off hook, on hook or flash hook). Set this flag to support Motorola and Scientific Atlanta EMTA's, and other devices that require an RQNT after a hook event RQNTorCRCXwSpecialDfield if enabled the T7000 sends a RQNT with a special string in the D: field. This option can be used to customize communication with certain gateways. See specialDfieldStr on page 369 SendAUEPatTO with this attribute set and upon receiving a timeout response from an AUEP or RQNT, the Call Agent will send an AUEP. Without that setting, the switch will assume the phone is idle and on hook. Leaving this attribute unset can keep the switch from flooding the ethernet with messages (on large scale failures). bracketType controls the type of bracketing added by the T7000 if the bracketedIP attribute is enabled. Has no effect if the bracketedIP attribue is disabled. disabled - [ip]:port enabled - [ip:port] bracketedIP if enabled, the T7000 adds brackets to the notified entity field of MGCP messages that are sent from the PIC. The type of brackets is controlled by the bracketType attribute cidCWaitSupport if MTA/CM supports S:rg,ci() signal for caller id call waiting (default is on) digitMapForMidCall use the digit map specified for this gateway when collecting digits in the middle of a call (for example, after hook flash). This attribue is not set by default, which means that the call agent will request the MTA to send one digit at a time. keepAlive if enabled, the T7000 sends an AUEP every <keepAliveTime> interval to keep firewall hole open for signaling path between T7000 and MTA/CM mwiToggle if turning off MWI stutter dial tone is indicated as S:L/mwi(-) or S:L/dl on the next call after voice mail indicator transition from YES to NO (default is off) reorderForROH certain gateways do not accept the ROH signal S:L/ot. If enabled S:L/ro is sent instead of ROH resendAUEP resend AUEP if bit set using 'auditInterval' in MGTerminationProfile
366
MGCP
attribute DLCXOptions
values mechanism to delete a residual connection on the media gateway when it administratively transitions from locked to unlocked NO_DLCX(default) no DLCX is sent PREFIX_TERM_ID one DLCX is sent for every termination on the gateway (default) PREFIX_STAR one DLCX (with the terminationPrefix *) is sent to the gateway STAR_ONLY one DLCX (with the *) as the endpoint to the gateway
encodeDigitMap THIST
UPPERCASE where D: x is uppercase LOWERCASE where D: x is lowercase (default) the time, in milliseconds, that the T7000 waits before resending to the media gateway the last MGCP command the media gateway sent range 10,000-60,000 30,000 (default)
retransmitTime
initial timer value, in milliseconds, for the T7000 to retransmit the MGCP command it sent, if a response is not received by the T7000 range 100-2,000 200 (default)
keepAliveTime
If mgKeepAliveToggle is set to ON (in the signalSupport parameter), then this is the value of the interval range 1,000-180,000 60,000 (default)
MAX1
number of retransmits before trying another IP address of a media gateway, must be less than MAX2 range 5-25 7 (default)
MAX2
number of retransmits before disconnecting the association with a media gateway, must be greater than MAX1 range 5-25 11 (default)
TMAX
maximum time to continue retransmitting commands to the media gateway range 0-20000 20000 (default)
minRTOThresh
lower threshold for which the retransmission timer starts 200-2,000 1,000 (default)
367
MGCP
attribute maxRTOThresh
values upper threshold for which the retransmission timer starts 2,000-10,000 4,000 (default)
responseAckParam
whether or not to send the transaction IDs included in the K line of the MGCP command (ResponseAck manages the facility with a list of confirmed transaction-id ranges), this adds previously unacknowledged transaction IDs to a new transaction (see responseAckNum to set the number of transaction IDs added) INCLUDE (default) NOT_INCLUDE
responseAckNum
Tip
You cannot modify this attribute after setting it. To change the value, delete and re-create the MediaGatewayProfile.
number of transaction IDs included in the K line of the MGCP command (see responseAckParam) 1-50 10 (default)
enablePiggyback
Internal value allows the T7000 to send several MGCP messages at the same time to one or more terminations on a media gateway and vice versa For example, after getting NOTIFY from a termination operating in lockstep mode, the T7000 sends the response and a new NotificationRequest command together to ensure message delivery fate-sharing of the two. ENABLE DISABLE (default)
piggybackTime
time to wait before sending a list of commands together using piggyback 0-200 200 (default)
transLowWaterMark
maximum pending transactions before the T7000 stops sending 101 Provisional Responses 0-100 25 (default)
transHighWaterMark
minimum pending transactions from the media gateway when the T7000 starts to send 101 Provisional Responses 0-100 50 (default)
368
MGCP
attribute provRespTime
values time to wait for a media gateway retransmission, after which the T7000 sends a Provisional Response 100-1,000 200 (default)
responseRetransEnabled
enables retransmission of a response when the media gateway sends a Provisional Response YES (default) NO
keepIPAddrFromSTATICto YES (default) if the address Mode changes from RSIP STATIC, do not reset the IP address. NO reset the IP address when the address Mode changes from STATIC specialDfieldStr A custom digit map sent when RQNTorCRCXwSpecialDfield is set in signalSupport on page 365.
Tip
Support for Occum ([0-9#*]) is build into the switch software, and is automatically sent when
RQNTorCRCXwSpecialDfield is set. Populate this field only for equipment requiring a different custom digit map.
369
MGCP
The Generic CLI is used for All MediaGatewayProfile command, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key terminationPrefix
terminationPrefix requestedInfo quarantineHandling supportedPackages signalSupport DLCXOptions encodeDigitMap THIST retransmitTime keepAliveTime MAX1 MAX2 TMAX minRTOThresh maxRTOThresh responseAckParam enablePiggyback piggybackTime transLowWaterMark transHighWaterMark provRespTime responseRetransEnabled keepIPAddrFromSTATICtoRSIP spedialDfieldStr
create MediaGatewayProfile p "aaln/" modify MediaGatewayProfile p requestedInfo DIGIT_MAP 1 modify MediaGatewayProfile p signalSupport CRCXorRQNTwithTimeout 1
370
MGCP
MediaGateway
A MediaGateway has the following attributes:
attribute key endpointName profileName value name of the MTA/CM a more descriptive or intuitive name for the MTA/CM name of MediaGatewayProfile associated with this
371
MGCP
attribute addressMode
value how the T7000 initiates communication with the media gateway STATIC The T7000 specifies the IP address. If the MTA/CM tries to communicate with a different address the T7000 rejects it. RSIP (default) the MTA/CM dynamically specifies the IP address
nearEndNiOid
Object Identifier of the Fast Ethernet Interface Facility (FEIF). See OID on page 30. This is the interface and associated IP address on the T7000 used to communicate with the MTA/CM.
terminations
372
MGCP
The Generic CLI is used for all MediaGateway commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
create MediaGateway gw1 p bg_mg1 "gw1.taqua.com" fe-0 lock MediaGateway gw1 modify MediaGateway gw1 priHostIPAddrPair $IP_ADDR:2400 modify MediaGateway gw1 addressMode STATIC
373
MGCP
MGTerminationProfile
A MGTerminationProfile defines different types of MediaGateway terminations. Associate MediaGateway terminations with these profiles. A MGTerminationProfile has the following attributes:
attribute key auditInterval value name of MGTerminationProfile rate, in milliseconds, at which AuditEndpoint (AUEP) messages are sent to the termination to synchronize it with the T7000. AUEP messages determines the status of a termination and aids in debugging. Also used by NCS. 60,000-1800000 60,000 (default) timedDisconnectTime for terminating calls, the time to wait (in milliseconds) after the called party has gone on hook before initiating disconnect procedures 2,000-10,000 5,000 (default) reoriginateTime time to wait (in milliseconds) after call completes before reorigination is started 1,000-10,000 2,000 (default) LCFODuration the duration (in milliseconds) of the Loop Current Feed Open (LCFO) signal. This signaling is required by some terminations. 0-7500 If set to 0, then no LCFO is signaled to the termination. 700 (default) sendLCFO priorityCallRingPattern ENABLE send LCFO to the termination (default) DISABLE do not send LCFO to the termination ring pattern to send for priority call rg mgcpRingDefault r0 mgcpRing0 r1 mgcpRing1 r2 mgcpRing2 r3 mgcpRing3 r4 mgcpRing4 r5 mgcpRing5 (default)
374
MGCP
attribute acarRingPattern
value ring pattern to send for automatic callback/automatic call return alerting rg mgcpRingDefault r0 mgcpRing0 r1 mgcpRing1 r2 mgcpRing2 r3 mgcpRing3 (default) r4 mgcpRing4 r5 mgcpRing5
revertiveRingPattern
ring pattern to send for revertive ringing rg mgcpRingDefault r0 mgcpRing0 r1 mgcpRing1 (default) r2 mgcpRing2 r3 mgcpRing3 r4 mgcpRing4 r5 mgcpRing5
The Generic CLI is used for all MG Termination Profile commands, see Using
Generic CLI Commands on page 6.
key
375
MGCP
MGTermination
A MGTrmination (MediaGateway) has some of the characteristics of lines or trunks. But MGTerminations are like GR-303 CRVs in that they must always belong to an MGCP trunk group. You cannot remove an MGTermination from an MGCP trunk group, but you can move it from one MGCP trunk group to another.
NOTE: Lock MG terminations to move them from one MGCP trunk group to another. See lock on page 7
mgcpTrunkGroupName administrativeState
376
MGCP
The Generic CLI is used for all MG Termination commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
profileName mgcpTrunkGroupName
NOTE: Use the lock and lock commands before modifying a MediaGateway.
377
MGCP
Digit Maps
A Digit Map specifies one or more Digit Map patterns. A Digit Map is used to streamline call processing between the switch and an MGCP endpoint. Once a Digit Map is sent to an MGCP endpoint, the MTA uses the Digit Map patterns to collect the digits in a call, which it sends to the switch in one NTFY message. This is much more efficient than sending one digit at a time in a series of NTFY messages - all of which have to be acknowledged with a 200 OK reply. Consider the dialing plan in use at the CO when building up a Digit Map. In some cases, a single generic Digit Map pattern will suffice. In others cases, you may need to define several specific Digit Map patterns. Use the following characters to construct a Digit Map pattern.
Character 0, 1, 2, 3...9 X [] [-] * # T Any digit 0 through 9 Specifies a grouping of digits. Any one digit from the group satisfies the digitpattern. Specifies a range of digits. Any one digit from the range satisfies the digit pattern. Specifies the star key Specifies the pound key Specifies a timeout. Used to terminate a pattern. Description Digits 0 through 9, specified explicitly
A Digit Map pattern can be short and simple, or it can be a long, complex string of characters. Here are some example Digit Map patterns, ranging from simple to complex:
Digit Map "00" "*XX" "[2-9]11" Dial 0, 0 Dial any two digits, 0 through 9 Dial any single digit, 2 through 9, then 1, 1. The resultant patterns are: 211, 311, 411 911 "[01][2-9]11" Dial either 0 or 1, then any single digit, 2 through 9, then 1, 1 The resultant patterns are: 0211, 0311, 0411 0911, and 1211, 1311, 1411 1911 "0[T#]" Dial 0, then either the pound key or a timeout specifies the end of the dialing pattern. Meaning
378
MGCP
Meaning then any 4 digits from 0 through 9, then any single digit 2 through 9, then any six digits 0 through 9 then either the pound key or a timeout specifies the end of the dialing pattern. (The resultant patterns are too numerous to list!)
The Generic CLI is used for all Digit Map commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
patterns
See Adding a Pattern to a Digit Map on page 380, and Removing a Pattern from a Digit Map on page 381.
379
MGCP
Adding a Pattern to a Digit Map insertInto DigitMap <key> patterns <subkey> DigitMapPattern <subvalue>
Use the Generic CLI insertInto command to add a Digit Map pattern into a Digit Maps patterns list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
Tip
Use a index of 1 to insert a DigitMap pattern at the start of the patterns list. Use a index of -1 to insert a DigitMap pattern at the end of the patterns list.
<subvalue>
query DigitMap n11 <490a140> DigitMap key........"n11" patterns...<490af60> <490af60> DigitMapList collection...List (1 items) -> (1) <490cc50> DigitMapPattern pattern..."[2-9]11"
380
MGCP
Removing a Pattern from a Digit Map deleteFrom DigitMap <key> patterns <subkey>
Use the Generic CLI deleteFrom command to remove a Digit Map pattern from a Digit Maps patterns list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description
subkey
deleteFrom DigitMap n11 patterns 1 query DigitMap n11 <490a140> DigitMap key........"n11" patterns...<490af60> <490af60> DigitMapList collection...List (0 items) ->
381
OfficeParams
OfficeParams
The OfficeParms object contains parameters that affect the entire switch An OfficeParms object has the following attributes:
Attribute key CLLICode Lata options OS Provider DA Provider name of the switch signed CLLI (Common Language Location ID) code three digit Local access and transport area identifier The options for this Officeparms object. See OfficeParms Options on page 389. name of the office-default carrier providing Operator Services (OS) If present, restrict must also be present name of the office-default carrier providing Directory Assistance (DA) If present, restrict and OS Provider must also be present rateCenter name of the local rate center If present, restrict, OS Provider and DA Provider must also be present timers OSSInfoDigits The timers for this Officeparms object. See OfficeParms Timers on page 391. The information digits (ANI digits) that force calls to route to an Operator Service System (OSS) instead of normal routing. By default, calls with information digits of 6, 7, and 29 are routed to an OSS The Service Profile to associate with this Central Office See Service Profile on page 152. Vertical Service Codes that specify the dialing patterns for Description
serviceProfile serviceCodes
Tip
To find a specific country code, go to http://www.the-acr.com/codes/cntrycd.htm
transFlag
Yes outpulses the translated number for local digit translation routing on the switch. No (default) does not outpulse the translated number for local digit translation routing.
382
OfficeParams
Attribute LLControl
Description Line load control level. When a line load class is suspended, subscribers with that line load class cannot make calls. Line load control relieves congestion by cutting off classes of subscriber lines to the switch. This provides better service to the remaining subscribers and reduces the chance of CO failure. Line load control divides subscribers into three separate groups: A the highest priority group, and requires communications during emergencies. Subscribers in this group include: law enforcement, fire, and rescue personnel. B secondary priority, typically businesses and some individuals C tertiary priority, typically individuals Typically, group A contains 10% of the subscribers with the B and C groups containing the remaining 90%. During an emergency, use line load control on C or on B and C to reduce congestion and allow subscribers in group A to communicate. This attribute is a bitfield. The line load classes are individually turned on or off by name. See example CLASS_A CLASS_B CLASS_C
Tip
To see the Line Load class of a particular subscriber, see query Subscriber on page 552.
vmwiTimerA
The number of hours that the switch attempts to send an Visual Message Waiting Indicator (VMWI) message to a subscriber line that is off-hook. If the timer expires, then the switch stops trying to send the Indicator message. This timer is only used when a subscriber is off-hook and receives a new voice mail message. Values are: 2hr 2.5hr 3hr 3.5hr 4hr Default: 2.5hr
vmwiTimerB
The interval that the switch sends a refresh message to subscribers with voicemail service. The refresh message updates the subscribers CPEs with VMWI. This ensures the correct status of a CPE, if the VMWI is lost for any reason. The switch does not send a refresh message if the setting is 0 minutes. Values are: none 15min 30min 45min 60min Default: 30min
redirectingNumberAs CallerID
No (default)) to send the calling partys DN as the caller ID when a call is forwarded from a base station Yes to send the DN of the base station as the caller ID (instead of that of the original caller) when a call is forwarded.
NOTE: The default value for this field is No, and should not be changed unless you want to change the Caller ID DN that is forwarded for all calls on the switch
383
OfficeParams
Attribute callingNameDisplayOption
Description LastNameFirst (default) to display the last name of the subscriber first on a subscribers caller ID device. For example Lisenby, Jeremy. FirstNameFirst to display the last name of the subscriber first on a subscribers caller ID device. For example Jeremy Lisenby.
useVMWIOSITimer
This field controls which timer is used when sending MWI to a subscribers phone: TRUE the switch uses the VMWIOSITimeout timer, see useVMWIOSITimer on page 384. FALSE (default) the switch uses the LCFO_Duration timer, see LCFO_Duration on page 246.
ftrsProfile
The FTRS profile assigned to all originations on the switch. The T7000 checks subscriber or trunk group FTRS profiles first; if the dialed pattern does not match a pattern in that FTRS profile the switch checks this profile. The name of a previously created screening list. The screen list contains one or more prefixes or DNs. Any call originating from a prefix or DN in the denyAniList will be blocked, see Screen Lists on page 415. FALSE (default) Media Gateway IP addresses can not dynamically change. TRUE Media Gateway IP addresses can dynamically change automatically (i.e., without human intervention), as with a DNS, for example.
denyAniList
mgcpDynamicIPUpdates
sipUserAgentName
This is the string sent in the User-Agent Header of SIP request messages. As per RFC 3261, the sting is configurable, and can be changed if required.
ANA_announcement- The delay between first and second Automatic Number Pause Announcement. See Automatic Number Announcement on page 665. Values are in seconds Range: 1 - 10 Default: 5 NOTE: This timer also controls the delay between the first and second Changed Number Announcement. sendRespForREGSatOverFlow Determines the switch's response to a SIP REGISTER request when the maxREGScps threshold is exceeded. ResponseNone Do not send any response. Response403 (default) Send a 403 Forbidden response. Response503 Send a 503 Service unavailable response.
384
OfficeParams
Description Determines the switch's response when the maxRSIPScps threshold is exceeded ResponseNone Do not send any response. Response200 Send a 200 OK responseS
tmsDigit
Specifies the digit a caller needs to enter to interrupt the announcement and terminate the call when the Telemarketer Screening announcement is played. Type is Bitfield. These options are individually turned on or off by name. See example. DISCONNECT_WITHOUT_DIGIT it the tmsDelay timer expires without the caller entering a digit. If this option is selected, the switch disconnects the call. If this option is not selected (default), the switch terminates the call normally TRIGGER_ON_RESTRICTED triggered for callers with a presentation of restricted, private or anonymous. If this option is selected, the Telemarketer Screening service is triggered for these call types. If this option is not selected (default), the Telemarketer Screening service is not triggered for these call types. NOTE: The Telemarketer Screening service is always triggered for callers with a presentation of Unavailable, Unknown or Out of Area. DISC_ON_RESOURCE_FAIL Determines if the caller should be disconnected due to insufficient resources to play the Telemarketer Screening announcement. If this option is selected, the switch disconnects the call. If this option is not selected (default), the switch terminates the call normally.
tmsOptions
sipAllowToUseTopVia Determines if the switch looks in the top VIA header to determine the originating endpoint of an INVITE request when the address is not found in the bottom VIA header. Normally the switch only uses the bottom VIA header. However, some SIP Devices send INVITEs with a private IP address in the bottom VIA. Such calls fail because the switch can not find the devices public IP address in the message. Select: TRUE Look in the bottom VIA, and, if necessary, the Top VIA, to determine the senders IP address. FALSE (default) Look only in the bottom VIA to determine the senders IP address.
385
OfficeParams
The Generic CLI is used for all OfficeParms commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
CLLICode Lata options OSProvider DAProvider rateCenter timers serviceProfile serviceCodes transFlag LLControl vmwiTimerA vmwiTimerB redirectingNumberAsCallerID callingNameDisplayOption useVMWIOSITimer ftrsProfile denyAniList mgcpDynamicIPUpdates sipUserAgentName ANA_announcementPause
386
OfficeParams
The insertInto and the deleteFrom commands apply to the following parameters:
See:
OSSInfoDigits countryCodes Adding a Country Code to OfficeParms on page 396 Removing a Country Code from Office Parms on page 396 Adding OSS Information Digits to OfficeParms on page 393 Removing OSS Information Digits from Office Parms on page 395
OfficeParms OfficeParms OfficeParms OfficeParms OfficeParms OfficeParms taquaTexas taquaTexas taquaTexas taquaTexas taquaTexas taquaTexas RICHTXCODS0 serviceCodes Cfwd_On "*55" LLControl CLASS_C 0 vmwiTimerA 3.5hr tmsOptions DISCONNECT_WITHOUT_DIGIT 1 tmsOptions DISC_ON_RESOURCE_FAIL 0
create modify modify modify modify modify
Prerequisites
Carriers, see Carriers on page 196 Rate Centers, see Rate Centers on page 410
Dependent Commands
After setting the Office Parameters, you can set the following:
387
OfficeParams
query OfficeParms 123 timers timers........................<2beef98> <2beef98> OfficeTimers ExcessiveAlerting........3a98 (15000) ExceptionRecoveryTime....ea60 (60000) ROHToneDuration..........ea60 (60000) FirstDigitTimeout........4e20 (20000) InterDigitTimeout........2710 (10000) CriticalDigitTimeout.....fa0 (4000) PartialCdrTimeout........ea60 (60000) SpeedDialTimeout.........fa0 (4000) TermScanningDuration.....1b7740 (1800000) LongDurationCdrTimeout...24_HRS VMWIOSITimeout...........1388 (5000) pingPeriod...............bb8 (3000)f
388
OfficeParams
OfficeParms Options
The Officeparms options are a bitfield, individually turned on or off by name. See example. Name PIC2_REQUIRED_FOR_ INTRALATA INTRALATA_RESTRICTIONS_ APPLY_TO_CAC INTERLATA_RESTRICTIONS_ APPLY_TO_CAC INTERNATIONAL_RESTRICTIONS_APPLY_TO_CAC ROUTE_ZERO_MINUS_TO_ PIC2 PREFIX_RATE_CENTER_OVERRIDES_SUBSCRIBER_RATE_ CENTER FAIL_UNKNOWN_DIGIT_ PATTERN ENABLE_877_SAC ENABLE_866_SAC ENABLE_866_SAC ENABLE_855_SAC ENABLE_844_SAC ENABLE_833_SAC ENABLE_822_SAC CALLING_NAME_QUERY_ REQUIRED Description Routes non-CAC calls for subscribers with no intraLATA carrier presubscribed to an announcement. Applies intraLATA toll subscriber restrictions to a dialed CAC and presubscribed PIC2. Applies interLATA toll subscriber restrictions to a dialed CAC and presubscribed PIC1. Applies international subscriber restrictions to a dialed CAC (for example, 1010288) and presubscribed PIC1. Operator services calls are routed to PIC2. Uses the rate center associated with the prefix instead of the rate center associated with the subscriber. Routes call to announcement if dialing pattern is not recognized. Enables 877 calls for toll free database lookup. Enables 866 calls for toll free database lookup Enables 866 calls for toll free database lookup. Enables 855 calls for toll free database lookup. Enables 844 calls for toll free database lookup. Enables 833 calls for toll free database lookup. Enables 822 calls for toll free database lookup Requires the switch to send a calling name query for local calls on the switch. By default the switch uses the subscriber database for local calling name. This option requires a query for all calls Rejects incoming calls with no calling number. Enables custom replacement of the carrier, ani, etc. even if calls use AIN to route. On intraLATA calls, the switch selects the PCAC from the Prefix database. If set, when the prefix is not defined in the Prefix database, the switch selects the PCAC from the Carrier On intraLATA calls, the switch selects the PCAC from the Prefix database. If set, when the prefix is not defined in the Prefix database, the switch selects the PCAC from the Carrier.
CAC_FROM_CARRIER
389
OfficeParams
Name USE_AIN_CALLING_NAME
Description If set, use the Name Presentation and Name from the AIN Termination Attempt response and not preform the Calling Name TCAP dip for Intraswitch calls, even if the CALLING_NAME_QUERY_REQUIRED option is turned on
query OfficeParms taquaTexas options <2b89cec> options.......................(BITFIELD) -> 1c .INTRALATA_RESTRICTIONS_APPLY_TO_CAC .INTERLATA_RESTRICTIONS_APPLY_TO_CAC .INTERNATIONAL_RESTRICTIONS_APPLY_TO_CAC modify OfficeParms taquaTexas options PCAC_FROM_CARRIER 1 modify OfficeParms taquaTexas options INTERNATIONAL_RESTRICTIONS_APPLY_TO_CAC 0 query OfficeParms taquaTexas options <2b89cec> options.......................(BITFIELD) -> 2000c .INTRALATA_RESTRICTIONS_APPLY_TO_CAC .INTERLATA_RESTRICTIONS_APPLY_TO_CAC .PCAC_FROM_CARRIER
390
OfficeParams
OfficeParms Timers
The Officeparms timers are a nested object of timers. All numerical timer values are in milliseconds, except for LongDurationCdrTimeout, which is in hours.
CAUTION
Setting office timers to values other than their defaults could negatively affect operations.
Description
ExceptionRecovery The number of milliseconds the switch sends the reorder tone after Time an announcement that follows a failure on the switch. ROHToneDuration FirstDigitTimeout The number of milliseconds the switch waits in an off-hook state before playing a receiver off-hook tone (howler tone). The number of milliseconds the switch waits for the caller to dial the first digit after going off-hook. Sends a loud tone that alerts the calling party when the timer expires. The number of milliseconds between digits dialed when placing a call when the collected set of digits are not subject to critical timing. Sends a message or tone to the caller when the timer expires.
InterDigitTimeout
CriticalDigitTimeout The number of milliseconds the switch waits before indicating the collected set of digits has matched a collection pattern. This is used when a matched pattern is a subset of a longer pattern and for 7digit dialing. PartialCdrTimeout The number of milliseconds before a partial CDR is created. The timer starts when a call is made on a SIP, SS7 or PRI Trunk, after the terminating circuit is seizing and alerting has begun, and the call is not completed. The timer is canceled if the originator hangs up. This is recordType 2 in the CDR. The number of milliseconds (configurable between 3 and 5 seconds) before a speed dial entry is triggered. Internal Value-This timer determines the length of time that the terminating switch will do terminating scanning for an Automatic Callback attempt. It is initialized when the terminating switch receives a terminating scanning request query message The number of hours between printing long duration CDRs. The range is 0-24hrs, with 24hrs being the default. For example, if this timer is 2hrs, a long duration CDR prints every two hours from when the call begins until it ends. The number of milliseconds (500-7500) the switch waits to turn on the Message Waiting Indication lamp at the CPE. The default is 5,000.
SpeedDialTimeout TermScanningDuration
LongDurationCdrTimeout
VMWIOSITimeout
391
OfficeParams
Description This versatile timer is used to ping the default gateway, as well as failed Network Gateways (NGWs) and Emergency Service Gateways (ESGWs). If the timer is non-zero, the switch pings the default gateways to detect failures. If the timer is zero, default gateways are not pinged. For ESGs and NSGWs, this timer works in conjugation with the Emergency Stand Alone feature. If enabled, the switch pings failed NGWs and ESGWs to detect when the gateway is once again reachable. If the timer is zero, failed NGWs and ESGWs are pinged at a default value. if the timer is non-zero, the interval that the switch pings the failed NGW or ESGW at default gateway is 10 times the provisioned value. The response time-out to the ping is determined by the pingRespTimerValue (see pingRespTimerValue on page 447). A response to the ping causes the switch to stop sending the ping to the failed NGW or ESGW. See ESAOption on page 464 Range: 0 - 600000 (600 seconds, or 10 minutes). The default is 3,000 ms.
tmsDelay
Telemarketer Screening timer. Works with the tmsOptions DISCONNECT_WITHOUT_DIGIT option. Range: 1000 - 30000 ms. The default is 10000 ms
392
OfficeParams
Adding OSS Information Digits to OfficeParms insertInto OfficeParms <key> OSSInfoDigits <subKey> <val>
The Generic CLI insertInto command adds Information Digits to the OfficeParmss OSSInfoDigits list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax Description the name of the switch, which was created with the create OfficeParms command the index of the list where you want to add the new Info Digits.
<key> <subKey>
Tip
Use a index of 1 to insert Information Digits at the start of the OSSInforDigits list. Use a index of -1 to insert Information Digits at the end of the OSSInforDigits list.
<val>
This example stores info digits 06 to the OSSInfoDigits list at position 6. If there are fewer than 6 entries in the list, the digits are added to the end of the list.
393
OfficeParams
07 20 00
07 00
SAC translated call with previously determined 23 information digits of 00 or 02 (only applicable if no information digits are received on SAC response)
Any station except A non-pay station with toll free SAC translated call 24 27, 29, 70 and ANI II digits are not 23 (only applicable if information digits are not received on SAC response) 27,29,70 Pay station with toll free SAC call (only applicable 25 if information digits are not received on SAC response) Pay station with network provided coin signaling (non SAC calls only) 27
Normal
Normal
27 29 30-32 34 40-49 52 60
Call from inmate/detention type stations (non SAC 29 calls only) Intercept callnot currently available Telco OSS Unrestricted use that is locally determined by the carrier OUTWATTS calls not currently available A call delivered to a transport carrier from Traffic Routing Administration (TRA) provider, which originated from an unrestricted line A call from cellular/wireless carrier that is forwarded to an IXC over type 1or 2 trunks Pay Station call that does not use network provided coin signaling (no SAC calls) Reserved for future expansion A call originating from Virtual Private Network (VPN) Unassigned 00 00 40-49 00 60
394
OfficeParams
Removing OSS Information Digits from Office Parms deleteFrom OfficeParms <key> OSSInfoDigits <subKey>
The Generic CLI deleteFrom command removes Information Digits from the OfficeParmss OSSInfoDigits list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> <subKey> Description the name of the switch, which was created with the create OfficeParms command The index in the OSSInfoDigits list of the Info Digits that are being removed.
This example deletes the 3rd entry from the OSSInfoDigits list (Info Digits 29)
query OfficeParms taquaTexas OSSInfoDigits <2b89a20> OSSInfoDigits.................<29a5168> <29a5168> InfoDigitsList valType......Integer collection...List (3 items) -> (1) IntegerValue: 6 (6) (2) IntegerValue: 7 (7) (3) IntegerValue: 1d (29) deleteFrom OfficeParms taquaTexas OSSInfoDigits 3 query OfficeParms taquaTexas OSSInfoDigits <2b89a20> OSSInfoDigits.................<29a5168> <29a5168> InfoDigitsList valType......Integer collection...List (2 items) -> (1) IntegerValue: 6 (6) (2) IntegerValue: 7 (7)
395
OfficeParams
Adding a Country Code to OfficeParms insertInto OfficeParms <key> countryCodes <pos> <val>
The Generic CLI insertInto command adds an international country code for countries subscribers can call to an OfficeParmss countryCode list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax Description the name of the switch, which was created with the create OfficeParms command the index of the list where you want to add the new country code value. An item added to the middle of the list will not delete any existing entry, but simply increase the length of the list.
<key> <pos>
Tip
Use a index of 1 to insert a Country Code at the start of the countryCodes list. Use a index of -1 to insert a Country Code at the end of the countryCodes list.
<val>
This example stores Country Code 217 at position 222 in the country codes list.
CAUTION
Deleting a country code may negatively affect operations.
This example deletes the Country Code at position 222 in the country codes list.
396
OfficeParams
OutPulseProfile
An OutPulseProfile defines a set of outpulsing sequences for an FGCOF Trunk Group. Both Stage 1 and Stage 2 out pulsing can be independently modified by call type. The custom out pulsing overrides the default out pulsing for each call type and is stored in the OutPulseProfile patterns dictionary. See "FGCOF Outpulsing" in
The T7000 Provisioning Manual.
The Generic CLI is used for all OutPulseProfile commands, see Using Generic CLI
Commands on page 6.
key
patterns
See Adding a Pattern to an OutPulseProfile on page 398, and Removing a Pattern from an OutPulseProfile on page 401.
Dependent Commands
An FGCOF Trunk Group, see CAS Trunk Groups on page 235 Associate the outPulseProfileKey with the FGCOF Trunk Group. See outPulseProfileKey on page 242. For example, to associate OutPulseProfile OPP1 with FGCOS Trunk Group TG1:
397
OfficeParams
Adding a Pattern to an OutPulseProfile insertInto OutPulseProfile <key> patterns <subkey> FGCOPPattern <Stage1St1> <Stage1St2> <Stage2St1> <Stage2St2>
Use the Generic CLI insertInto command to add a FGCOP pattern into an OutPulsePatterns patterns dictionary. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
OutPulsePattern name
This is the key to the patterns dictionary. The dictionary is keyed by call type. Values are: 0 = LOCAL 1 = EXTENDED_AREA 2 = INTER_LATA 3 = OA_INTER_LATA 4 = INTRA_LATA 5 = OA_INTRA_LATA 6 = INTERNATIONAL 7 = OA_INTERNATIONAL 8 = WORLDZONE1 9 = OA_WORLDZONE1 10 = E911 11 = DA_INTRA_LATA 12 = DA_INTER_LATA 13 = OA_ZERO_MINUS 14 = SAC 15 = UNKNOWN_CALL_TYPE 16 = TERMINATING_CALL 17 = TANDEM_CALL 18 = TERMINATING_LOCAL 19 = TERMINATING_EXTENDED 20 = TERMINATING_INTRATOLL 21 = SIP_IAD 22 = INTER_LATA_COIN 23 = INTRA_LATA_COIN
<subkey>
Tip
Either the decimal value or the call type string can be entered for the subkey, (e.g., instead of entering "OA_WORLDZONE1", you could simply enter "9".
398
OfficeParams
Syntax
Description 50 = TANDEM_INTRALATA 51 = TANDEM_E911 52 = TANDEM_DA 53 = TANDEM_INTERLATA 54 = TANDEM_WORLDZONE1 55 = TANDEM_SAC 56 = TANDEM_INTERNATIONAL 61 = TANDEM_OA_INTRALATA 62 = TANDEM_OA_INTERLATA 63 = TANDEM_OA_WORLDZONE1 64 = TANDEM_OA_INTERNATIONAL 65 = TANDEM_ZEROMINUS
<subkey>, continued
<Stage1St1>
FGCOF can send one or two ST tones per stage. This is the value for the first ST in Stage 1. Values are: None Do not send a signal ST Send an ST signal STP Send an ST Prime signal ST2P Send an ST Double Prime signal ST3P Send an ST Triple Prime signal
<Stage1St2>
FGCOF can send one or two ST tones per stage. This is the value for the second ST in Stage 1. Values are: None Do not send a signal ST Send an ST signal STP Send an ST Prime signal ST2P Send an ST Double Prime signal ST3P Send an ST Triple Prime signal
<Stage2St1>
FGCOF can send one or two ST tones per stage. This is the value for the first ST in Stage 2. Values are: None Do not send a signal ST Send an ST signal STP Send an ST Prime signal ST2P Send an ST Double Prime signal ST3P Send an ST Triple Prime signal
<Stage2St2>
FGCOF can send one or two ST tones per stage. This is the value for the second ST in Stage 2. Values are: None Do not send a signal ST Send an ST signal STP Send an ST Prime signal ST2P Send an ST Double Prime signal ST3P Send an ST Triple Prime signal
399
OfficeParams
insertInto OutPulseProfile OPP1 patterns OA_INTRA_LATA FGCOPPattern STP STP ST ST3P insertInto OutPulseProfile OPP1 patterns 3 FGCOPPattern ST2P None ST ST query OutPulseProfile OPP1 <5f1c760> OutPulseProfile key........"OPP1" patterns...<5f1c970> <5f1c970> OutPulsePatternDict (2 items) -> OA_INTRA_LATA: <5f2dfd8> FGCOPPattern Stage1ST1...STP Stage1ST2...STP Stage2ST1...ST Stage2ST2...ST3P OA_INTER_LATA: <6055b18> FGCOPPattern Stage1ST1...ST2P Stage1ST2...None Stage2ST1...ST Stage2ST2...ST
400
OfficeParams
OutPulsePattern name
This is the key to the patterns dictionary. The dictionary is keyed by call type. Values are: LOCAL EXTENDED_AREA INTER_LATA OA_INTER_LATA INTRA_LATA OA_INTRA_LATA INTERNATIONAL OA_INTERNATIONAL WORLDZONE1 OA_WORLDZONE1 E911 DA_INTRA_LATA DA_INTER_LATA OA_ZERO_MINUS SAC UNKNOWN_CALL_TYPE TERMINATING_CALL TANDEM_CALL TERMINATING_LOCAL TERMINATING_EXTENDED TERMINATING_INTRATOLL SIP_IAD INTER_LATA_COIN INTRA_LATA_COIN
<subkey>
401
OfficeParams
deleteFrom OutPulseProfile OPP1 patterns OA_INTER_LATA query OutPulseProfile OPP1 <5f1c760> OutPulseProfile key........"OPP1" patterns...<5f1c970> <5f1c970> OutPulsePatternDict (1 items) -> OA_INTRA_LATA: <5f2dfd8> FGCOPPattern Stage1ST1...STP Stage1ST2...STP Stage2ST1...ST Stage2ST2...ST3P
402
Prefixes
Prefixes
A prefixes specifies 3-digits (NPA), 6-digits (NPA-Nxx), or 7-10 digit numbers. Prefixes provides information used to determine the call type For subscriber originations, a prefix identifies the Rate Center for the called number. It also denotes 7 digit dialing for local calls originated from the prefix. For incoming trunk groups, a prefix determines the Rate Center for the calling and called number.
Tip
Since a prefix can be 10 digits long, adding the DNs of subscriber who have been ported off the switch can avoid LNP DIPs on the entire prefix
A prefix can be marked as ported (that is, at least one number from the prefix has moved to another switch). When a prefix is ported, the switch must query an SCP to determine the ported location of all numbers in the prefix.
NOTE: By default, all prefixes that are not defined map to InterLATA toll call type.
403
Prefixes
attribute ported
value Used only used for intraLATA prefixes: YES the prefix is a portable prefix, that is at least one number from the prefix moved to another switch, and a switch must query an SCP for the ported location of that number NO the prefix is not a portable prefix
allowedDialing
A bitfield of prefix dialing options. These options are individually turned on or off by name. See example SEVEN_DIGIT_LD to allow 7-digit long distance dialing (0+7D, 1+7D). SEVEN_DIGIT_LOCAL to allow 7-digit local dialing. If the first digit is not 1 or 0 then local calling is assumed and local calls route immediately after seven digits are dialed and the 4 second CriticalDigitTimeout expires.
locallyAmbiguous
Controls how the switch behaves if 7-digit dialing is active and there are prefixes with NPAs that match prefixes with office codes (NXXs) on the switch: YES after dialing 7 digits the switch inserts a critical digit timeout (default 4 seconds) allowing the subscriber to continue dialing a 10-digit number NO after dialing 7 digits the call connects not allowing the subscriber to dial a 10-digit number
internationalCode
Valid only for WORLDZONE1 prefixes. For interLATA and intraLATA prefixes leave this field at its default setting. The code required to make calls to worldZone 1 areas (Canada and the Caribbean). The code should be 01 plus the region code of the worldZone 1 area. For example, 013 for calls the worldZone 1 area 450, or 011 for calls to counties except Canada and most countries in the Caribbean.
Npa
The NPA of an NXX prefix provisioned to support 7-digit dialing across NPA boundaries. See 7-Digit Dialing Across NPA Boundaries on page 408. The digits that you want to replace the destination digits (called number) for the original destination number in the outgoing call setup message. The switch replaces digits for numbers associated with a specific terminating prefix, See Outgoing Signaling Customization on page 345.. The PCAC is the 4-digit Pseudo CAC (PCAC) that is sent in the outgoing call setup signal. In standard call processing, the CAC in the outgoing signaling message is the same as the CAC used for routing. This field sends a different CAC in the signaling message than the switch uses to route the call, see Outgoing Signaling Customization on page 345..
replacementDigits
PCAC
404
Prefixes
attribute replacementMode
value Sets the replacement mode for the prefix: NO_REPLACEMENT (default) Sends the original destination prefix or digits REPLACE_PREFIX Replaces the prefix digits regardless of the number of digits. For example, 3 digits could replace a 6-digit prefix. OVERLAY_ORIG_DEST Replaces the exact number of digits of the original destination number. REPLACE_ORIG_DEST Replaces the original destination digits with a different digit set. For examples, see Destination Digit Replacement on page 346.
replacementAniDigits
The Pseudo ANI (PANI) to replace the ANI (calling number) of a call that uses this prefix,. see Outgoing Signaling Customization on page 345. The PANI II Information digits to replace the digits sent in outgoing call setup messages. Use this field to send different ANI II digits (the Pseudo ANI II digits) in the signaling message in place of the ANI II digits associated with a facility, see Outgoing Signaling Customization on page 345. The Carrier Selection Information (CSI) type that defines if a subscriber is presubscribed to a carrier or not. CSI replacement applies only to calls originating on the switch. The CSI is an optional parameter in the SS7 IAM and for CAS the CSI is the KP digit in the ANI sequence. The CSI value overrides the ANI KP type in the CAS protocol. See Outgoing Signaling Customization on page 345. CSI_UNKNOWN Outpulses the CSI value that the switch determines. CARRIER_NOIND Outpulses 0 in the CSI parameter in SS7 or the default KP type in CAS. CARRIER_PRESUB Selected Carrier Access Code (CAC) presubscribed and not input by calling party. See CSI Replacement on page 348. CARRIER_PRESUB_INPUT Selected CAC presubscribed and input by calling party. See CSI Replacement on page 348. CARRIER_PRESUB_NOINDINPUT Selected CAC presubscribed, no indication of whether input by calling party. See CSI Replacement on page 348.. CARRIER_NOTPRESUB_INPUT Selected CAC not presubscribed and input by calling party. See CSI Replacement on page 348.
replacementInfoDigits
replacementCSI
405
Prefixes
The Generic CLI is used for all Prefix commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
Prerequisites
nature rateCenter ported allowedDialing locallyAmbiguous internationalCode Npa replacementDigits PCAC replacementMode replacementAniDigits replacementInfoDigits replacementCSI
Dependent Commands
By adding a prefix, you are making this prefix available to associate with a:
NANP route list, see NANP Route List on page 519 LNP route list, see LNP Route List on page 517 Subscriber, see Subscribers on page 530
Prefix 214777 INTRALATA rc1 Prefix 808 WORLDZONE1 Prefix 214777 allowedDialing SEVEN_DIGIT_LD 1
406
Prefixes
query Prefix
query Prefix <prefix>
Tip
Use this command without a key to see which prefixes are provisioned on the switch.
This Generic CLI command shows information about a 3-, 6-, or 7-digit NANP prefix.
Syntax <prefix> Description A 3-, 6-, or 7-digit prefix of subscribers that connect to the switch.
query Prefix 817 <2bee040> Prefix key....................."817" nature..................INTRALATA rateCenter..............<> ported..................NO allowedDialing..........(BITFIELD) -> 0 locallyAmbiguous........NO internationalCode.......b (11) Npa.....................<> replacementDigits.......<> PCAC....................<> replacementMode.........NO_REPLACEMENT replacementAniDigits....<> replacementInfoDigits...<> replacementCSI..........CSI_UNKNOWN
407
Prefixes
Action Provision an IntraLATA 6-digit prefix (NPA-NXX) for each office. For example, provision 214480 and 972455. See Prefixes on page 403. Set the prefixes to allow 7-digit local dialing. See allowedDialing on page 404. Provision a separate prefix for each 6-digit prefix using the three digits of the NXX. For example, provision a 480 and 455 prefix. See Prefixes on page 403.
2 3
NOTE: 7-digit dialing across NPA boundaries does not support provisioning identical NXXs. For example, the switch does not support local 7-digit dialing between 214480 and 972480.
4
Set the NPA value as the NPA of each NXX provisioned in step 1 on page 408. For example, provision 214 for the NPA of the 480 prefix and 972 for the NPA field of the 455 prefix. See Npa on page 404. Set the rate center relationships between the 6-digit prefixes as either local or extended area. See Adding a RateCenter on page 412.
408
Prefixes
Action Set the inbound tandem Trunk Group tandemRoutingType to NO_ROUTING. Set the outbound tandem Trunk Group tandemCustomReplacement to YES. Set the outbound tandem Trunk Group replaceDestination to REPLACE_IfNotPorted Provision a 6-digit Prefix in the form of NPA-NXX for each 7 digit pattern. For example, to outpulse 7 digits for calls to 972-480-XXXX provision a 972480 prefix. Set the 6-digit Prefix replacementDigits to NXX. For example, in the 972480 prefix, set the replacementDigits to 480. Set the 6-digit Prefix replacementMode to REPLACE_PREFIX.
409
Rate Centers
Rate Centers
A rate center is a designated geographic area within a Local Access and Transport Area (LATA). A switch must have at least one rate center. All calls made within the rate center are considered local (or non-toll). All calls made to another rate center may be local, extended area, or intraLATA toll.
NOTE: An intraLATA call for which both an original and remote rate center cannot be determined is considered local.
The Generic CLI is used for all rate center commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
LRN restrictions
LRN restrictions
relationships
410
Rate Centers
See Adding a RateCenter on page 412, and See Removing a RateCenter on page 414.
NOTE: Deleting a rate center may negatively affect operations.
Dependent Commands
After creating a rate center, create a relationship between it and:
An extended area rate center, see Adding a RateCenter on page 412 An intratoll rate center, see Adding a RateCenter on page 412
Prerequisites
A carrier, see Carriers on page 196 A prefix, see Prefixes on page 403 The Office Parameter, if it is the local rate center, see OfficeParams on
page 382
Rate center, see Adding a RateCenter on page 412 To delete a rate center, you must remove or modify the following items that relate to the rate center:
Carriers, see Carriers on page 196 The rate center attribute in Office Parameters, see OfficeParams on page
382
Prefixes, see Prefixes on page 403 Subscribers, see Subscribers on page 530
411
Rate Centers
See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
<subkey> <subvalue>
412
Rate Centers
This example creates a 2nd and a 3rd ratecenter. The 2nd rate center has an extended relationship with the 1st rate center, and the 3rd rate center has an intra toll relationship with the 1st rate center.
create RateCenter rc2 972530 create RateCenter rc3 214289 insertInto RateCenter rc1 relationships rc2 EXTENDED insertInto RateCenter rc1 relationships rc3 INTRATOLL query RateCenter rc1 <1a01720> RateCenter key............."rc1" LRN............."972480" restrictions....(BITFIELD) -> 0 relationships...<2bfc758> <2bfc758> RelationshipDict keyType......Unknown valType......Integer collection...Dictionary (2 items) -> StringKey: rc2 IntegerValue: 1 (1) StringKey: rc3 IntegerValue: 2 (2)
413
Rate Centers
<subkey>
deleteFrom RateCenter rc1 relationships rc3 query RateCenter rc1 <1a01720> RateCenter key............."rc1" LRN............."972480" restrictions....(BITFIELD) -> 0 relationships...<2bfc758> <2bfc758> RelationshipDict keyType......Unknown valType......Integer collection...Dictionary (1 items) -> StringKey: rc2 IntegerValue: 1 (1)
query RateCenter rc1 Rate Center rc1Restrictions: 0 Extended Area Rate Centers rc2 IntraLata Toll Rate Centers rc3
414
Screen Lists
Screen Lists
Screen lists are lists of prefixes or DNs for call screening. A screen list can apply to the entire Central Office or to a Trunk Group. See:
Central Office denyAniList on page 384 CAS Trunk Groups denyAniList on page 239 Clear Channel Trunk Groups denyAniList on page 254 Hunt Groups denyAniList on page 275 Interface Groups denyAniList on page 260 IP Trunk Groups denyAniList on page 310 MGCP Trunk Groups denyAniList on page 359 PRI Trunk Groups denyAniList on page 289 SS7 Trunk Groups denyAniList on page 327
Allowed list a subscriber can complete calls only to the prefixes in the screening list. See allowedList on page 537. Denied list a subscriber can complete calls to all prefixes except those in the screening list. See deniedList on page 537.
A screen list is also used for the following subscriber calling services:
Selective Call Acceptance a subscriber only receives calls from a list of DNs Selective Call Rejection a subscriber rejects calls from a list of DNs Selective Call Forwarding a subscriber forwards calls from a list of DNs Priority Call a subscriber receives calls with a distinctive ringing tone from callers on a list of DNs
A calling service screen list is automatically created when the service is provisioned, and automatically destroyed when the service is de-provisioned. See
setSubCOS on page 576.
415
Screen Lists
The Generic CLI is used for Screen List commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
name
There are no optional parameters for the create command. The insertInto and deleteFrom commands apply to the following parameters:
facilities
See Adding a Prefix or DN to a Screen List on page 417, and Removing a Prefix or DN from a Screen List on page 417
416
Screen Lists
Adding a Prefix or DN to a Screen List insertInto ScreenList <key> prefixes <subkey> [subvalue]
Use the Generic CLI insertInto command to add a prefix or a DN to a screen lists prefixes list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
Screen list name. See name on page 416 for important information about subscriber screen list naming conventions
The prefixes list in a screen list is a sorted list. The key to this list is the DN you want to add to the screen list. The DN you want to add to this screen list. In the case of a ScreenList, the subvalue can be omitted, since it is the same as the subkey.
<subkey> [subvalue]
Either of the following commands adds the DN 9724801234 to the Priority Call Screen List for the subscriber at DN 9724800000:
insertInto ScreenList 9724800000PRI prefixes 9724801234 insertInto ScreenList 9724800000PRI prefixes 9724801234 9724801234
Either of the following command adds the prefix 408 to the badANI Screen List:
insertInto ScreenList badANI prefixes 408 insertInto ScreenList badANI prefixes 408 408
Removing a Prefix or DN from a Screen List deleteFrom ScreenList <key> facilities <subkey>
Use the Generic CLI deleteFrom command to remove a prefix or a DN from a screen lists prefixes list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description
Screen list name. See name on page 416 for important information about subscriber screen list naming conventions
The prefixes list in a screen list is a sorted list. The key to this list is the DN that you want to remove.
<subkey>
The following example removes the 408 prefix from the badANI screen list:
417
SIP
SIP
See
Setting up an IP Network Interface on page 419 Setting up a Subscriber Access SIP Endpoint on page 420 Setting up a Network Gateway SIP Endpoint on page 421
418
SIP
Step
1
Action Provision an IP network interface: Remove the Fast Ethernet Interface (FEI) from service, see remove on page 628. Set the FEI attributes, see setFeifIPAddr on page 422. Set the FEI options, see setFeifOptions on page 424. (optional) Set the range of Real Time Protocol (RTP) port addresses to FEI, see setRtpPortBase on page 423. (optional) Restore the FEI to service, see restore on page 628.
Create codec lists: Create a Codec Profile List, see CodecProfileList on page 425. Create Codec Profiles, see CodecProfile on page 427. Modify Codec Profile attributes, see CodecProfile on page 427. Insert Codec Profiles into Codec Profile List, see Adding CodecProfiles to a CodecProfileList on page 426.
Create a host name and IP address table entry, see Host IP Addr Pair on page 429. (optional) Create media stream parameters, see MediaParam on page 431.
419
SIP
Step
1
Action If necessary, configure a BearerGroup of Fast Ethernet Interfaces, see BearerGroup on page 163. Create a SIP endpoint profile: Create a SubscriberAccess SIP endpoint profile, see SIP Access Gateway Profile on page 436. Use the modify command to change the SIP endpoint profiles options, see SIP Access Gateway Options on page 437 and SIP Timers on page 434.
Create a SubscriberAccess SIP endpoint, see Subscriber Access Gateway Endpoint on page 441. Add the IP trunk group that associates the FEI on the T7000 to the SIP endpoint, see IP Trunk Groups on page 307. Add a SIP subscriber whose 10-digit DN is the same the SIP endpoints, see Subscribers on page 530. Add the subscriber key (DN) and password.
420
SIP
Step
1
Action If necessary, configure a BearerGroup of Fast Ethernet Interfaces, see BearerGroup on page 163. Create a SIP endpoint profile: Create a Network Gateway SIP endpoint profile, see SIP Network Gateway Profile on page 454. Use the modify command to change the SIP endpoint profiles options, see SIP Network Gateway Options on page 455 and SIP Timers on page 434.
Create a Network Gateway SIP endpoint: Create a Network Gateway SIP endpoint, see SIP Network Gateway Endpoint on page 459. Add the primary IP address and port. (optional) Assign an alternate IP address and port, see Adding IP Addr Pairs to a SIP Network Gateway Endpoint on page 462..
Add the IP trunk group that associates the FEI on the T7000 to the SIP endpoint, see Trunk Groups on page 233. Add a pseudo-SIP subscriber whose 10-digit DN is the same the SIP endpoints, see Subscribers on page 530. Add an NANP Route List with the range of DNs on the Network Gateway (SIP AP), see NANP Route List on page 519 Add the IP trunk group to the route list, see Adding a Route to a Route List on page 527.
421
SIP
setFeifIPAddr
Tip
Use modifyFacility on page 217 to set the primary and secondary DNS for an FE.
Prerequisites
Remove the FEI oid from service, see remove on page 628. IP host, see Host IP Addr Pair on page 429.
Syntax <feifoid> <sigIPaddr> <rtpIPaddr> Description Object Identifier of the Fast Ethernet Interface Facility (FEIF). See OID on page 30. IP address of the FE used to receive signaling packets. IP address of the FEI used to receive RTP packets. PIC: same value as sigIPaddr. PIC2: different IP address than the sigIPaddr. The sigIPaddr and the rtpIPaddr must be on the same subnet. <netmask> IP network mask. <defaultgateway> IP address of the default gateway or router to the network.
NOTE: The sigIPaddr and the rtpIPaddr must be in a separate IP network than the
Dependent Commands
Restore the FEI oid to service, see restore on page 628. Set the FEI options, see setFeifOptions on page 424.
422
SIP
Prerequisites
FEI connection, see setFeifIPAddr on page 422.
Syntax <feifoid> <RtpPortBase> Description Object Identifier of the Fast Ethernet Interface facility. See OID on page 30. The lowest UDP port number used to receive RTP (2-65534, even numbers only). Ports are assigned dynamically at run-time. 49152 is the default. The total number of UDP ports available on the FEI to receive RTP (49152-65535, even numbers only).
<RtpPortNum>
In the following example the lowest RTP port value is 49152. The total number of ports available is 2070. This means the RTP port selected at run-time will be between 49152 and 51222 (49152+2070).
423
SIP
setFeifOptions
Tip
Use modifyFacility on page 217 to set the primary and secondary DNS for an FE.
Prerequisites
FEI connection, see setFeifIPAddr on page 422.
Syntax <feifoid> <sipPort> <mgcpPort> <vlantag> Description Object Identifier of the Fast Ethernet Interface Facility (FEIF). See OID on page 30. SIP receive port number from 1-7000. 5060 is the default and this value is almost always used. Media Gateway Control Protocol receiving port number, 2727 is the default A virtual LAN allows hosts in the same physical switched infrastructure but in separate virtual broadcast domains to be addressed from the same subnet and share a common default gateway address. 0=DISABLED (default) If vlantagging is disabled, you cannot set the priority of packets sent from the PIC. 1=ENABLED If vlantagging is enabled, you can set the priority of packets sent from the PIC by adding an 802.1Q tag header to each packet. <vlanid> If vlantag is DISABLED, enter 0. If vlantag isENABLED, enter a virtual LAN ID from 1-4095. 1 is the default. <sig8021pri> If vlantagis ENABLED, an 802.1Q tag header is added to each packet the PIC transmits. This header shows the priority of the packets sent by the PIC. range 0 is the lowest priority, 7 is the highest priority (3=signaling default) <sigDSCP> sigDSCP (signaling DSCP) controls the priority at which signaling packets are sent through the network. Background: Diffserv Codepoint (DSCP) controls the priority at which signaling packets are sent through the network. It is a coarse-grained, class-based mechanism for traffic management, defined in RFC 2474. DSCP aware routers implement Per-Hop Behaviors (PHBs), based on DSCP. These PHBs define the packet forwarding properties associated with a given class of traffic. The Expedited Forwarding PHB, defined in RFC 2598, provides a low-loss, low-latency, assured bandwidth service for VoIP applications. The value of this PHB is 184 (hex 0xB8), and is the default value for this attribute. 0-252 (default 184)
424
SIP
CodecProfileList
A CodecProfileList is:
a container for Codec Profiles. For more information, see CodecProfile on page 427. associated with one or more IP trunk groups, setting the Codec Profiles used on those groups. For more information, see IP Trunk Groups on page 307.
To properly configure Codec Profiles and the Codec Profile Lists, know the following capabilities of the SIP endpoint with which the T7000 will communicate:
the codec types it supports the different configurations of each codec it supports
NOTE: If the T7000 and SIP endpoint do not agree on a Codec Profile, the T7000 refuses the call during call setup.
The Generic CLI is used for All CodecProfileList commands, see Using Generic CLI
Commands on page 6. NOTE: As a safety precaution, a CodecProfileList must be removed from all IP Trunk Groups that are using it before it can be deleted. The switch will issue a warning message, specifying the name of the IP Trunk Group that is using the codec list.
key
The modify command does not apply to CodecProfileLists. The insertInto and the deleteFrom commands apply to the following parameters:
codecProfiles
See Adding CodecProfiles to a CodecProfileList on page 426 and Removing CodecProfiles from a CodecProfileList on page 426
425
SIP
Tip
The same Codec Profile may be added to different Codec Profile Lists.
<subkey>
Tip
Use a index of 1 to insert a codecProfile the start of the codecProfile list. Use a index of -1 to insert a codecProfile at the end of the codecProfile list.
<CodecProfile>
This attribute specifies which CodecProfile you want to add to the CodecProfileList.
<subkey>
The following example removes the 1st CodecProfile from CodecProfileList prflist1
426
SIP
CodecProfile
Use CodecProfiles to create variations of standard codecs. Insert Codec Profiles into a CodecProfileList in the order you want the T7000 to attempt to use them. A CodecProfile has the following attributes:
Attribute key codecTypeAndSize Description name of the CodecProfile Codec type and sample size. See the T7000 Provisioning Guide for a chart detailing sample size and required bandwidth. Values are: G711_5MS G.711 codec, 5 ms sample size. G711_10MS G.711 codec, 10 ms sample size. G711_20MS (default) G.711 codec, 20 ms sample size. G726_5MS G.726 codec, 5 ms sample size. G726_10MS G.726 codec, 10 ms sample size. G726_20MS G.726 codec, 20ms sample size. G729_10MS G.7296 codec, 10 ms sample size. G729_20MS G.7296 codec, 20ms sample size. G729_30MS G.7296 codec, 30ms sample size. vadFlag Voice Activity Detection (VAD) silence suppression flag. Values are: OFF turns Voice Activity Detection silence suppression off. If your SIP phone or ATA does not support VAD, set this parameter to OFF ON turns Voice Activity Detection silence suppression. This allows the switch to send one silence packet (representing multiple packets), which decreases messaging between the endpoints. dtmfToneMode How Dual Tone Multi Frequency Tones (DTMF) are transmitted during a call. INBAND tones are sent as regular packetized voice; tones are sent in the same packets as the voice OUTBAND tones are sent in the same RTP stream, but in separate packets from the voice (see RFC 2833)
427
SIP
The Generic CLI is used for All CodecProfile commands, see Using Generic CLI Commands on page 6.
NOTE: As a safety precaution, a CodecProfile that is in use can not be deleted! The switch will issue a warning message, specifying the name of the CodecProfileList that is using the Codec Profile. The CodecProfile must be removed from all CodecProfileLists that are using it before it can be deleted.
key
To properly configure CodecProfiles and the CodecProfileLists, know the following capabilities of the SIP endpoint with which the T7000 will communicate:
the codec types supported the different configurations of each codec supported
NOTE: If the T7000 and SIP endpoint cannot agree on a Codec Profile, the T7000 refuses the call during call setup.
create CodecProfile cp1 modify CodecProfile cp1 vadFlag ON modify CodecProfile cp1 codecTypeAndSize G711_20ms modify CodecProfile cp1 codecTypeAndSize G711_20MS query CodecProfile cp1 <2bfc720> CodecProfile key................"cp1" codecTypeAndSize...G711_20MS vadFlag............ON dtmfToneMode.......OUTBAND
Dependent Commands
Add this CodecProfile to a CodeProfileList, see CodecProfileList on page 425.
428
SIP
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195 secIPAddrPair Optional Secondary IP address and Port number of the IP host
The Generic CLI is used for all Host IP Addr Pair commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
sIPAddr Port
priIPAddrPair
secIPAddrPair
429
SIP
create HostIPAddrPair Host1@taqua.com 10.1.134.243 6030 modify HostIPAddrPair Host1@taqua.com secIPAddrPair 10.1.134.244 6031 query HostIPAddrPair Host1@taqua.com <2bfc1f0> HostIPAddrPair key............."Host1@taqua.com" priIPAddrPair...<2bfcce0> <2bfcce0> IPAddrPair sIPAddr..."10.1.134.243" Port......178e (6030) secIPAddrPair...<2bfc308> <2bfc308> IPAddrPair sIPAddr..."10.1.134.244" Port......178f (6031)
430
SIP
MediaParam
A MediaParam is a media stream parameter. Media stream parameters are configurable parameters for the bearer or RTP portion of a VoIP call. Media stream parameters apply to an entire trunk group. A MediaParam has the following attributes:
Attributes key adaptiveVadFlag Description name of the media stream parameter Adaptive Voice Activity Detection (VAD) silence suppression MANUAL Manual Silence Threshold DYNAMIC (default) Dynamic Threshold Detection vadThreshold The decibel threshold where adaptiveVadFlag detection occurs from -20 to -50. -30 is the default.
NOTE: set this only if Manual Silence Threshold is enabled modemFaxHandlingCodec Modem and fax data transport is encoded using G711 upspeed G711 upspeed off G711 upspeed ON (default) jitterBufferMode The jitter buffer conceals variations in RTP packet arrival times FIXED buffer size is fixed ADAPTIVE (default) buffer size changes to deal with varying levels of jitter jitterBufferMaxSize The maximum time data is held in the buffer to conceal jitter. Range 10-100. 100 is the default.
NOTE: This value can be set for either FIXED or ADAPTIVE jitterBufferMode jitterBufferInitialSize The initial size of the jitter buffer from 0-100. 20 is the default.
431
SIP
Attributes echoCancelFlag
Description Controls the Echo Cancellers. Echo cancellation is often required because the process of packetizing voice samples can introduce delay and generate echo. ECHO_CANCEL_OFF disables the echo canceller ECHO_CANCEL_ON (Default) enables the echo canceller
echoTailSize
Sets the maximum amount of echo tail (in milliseconds) that the echo canceller works on. 32 64 (default) 128
rtpDSCPtos
RTP DSCP, controls the priority at which RTP packets are sent through the network. Difserv Codepoint (DSCP) is a coarse-grained, classbased mechanism for traffic management. Diffserv selects the per-hop behavior (PHB) for each signaling packet forwarded through the network.a Expedited Forwarding PHB provides a low-loss, lowlatency, assured bandwidth service for VoIP applications. The DSCP value for this PHB (which is recommend) is 184 (hex 0xB8).
signaling802_1_priority
To set this parameter, ensure vlantag is ENABLED, see setFeifOptions on page 424. When vlantagging is ENABLED, the 802.1Q tag header is added to each bearer packet the PIC transmits. The information set in this parameter controls the priority of packets. range (0 is the lowest priority, 7 is the highest priority) bearer default: 5
payloadType2833
used by the MGCP or SIP protocol to identify the RFC 2833 SDP Payload Type. Default is 101. The range is 96 - 999 used by the MGCP and SIP protocols. If the value is set to ON, the switch will use the values in rxGainControl and txGainControl when it sets up an RTP stream. used by MGCP to set the amount of gain in a remote device (MTA) stream. The same amount of gain is set for both the transmit and receive direction. This happens regardless of the value of enableGainControl. Default is 0 (i.e., no gain). The range is -14 dB to +14 dB the amount of transmit gain to set in the MGCP or SIP media stream. Default is 0 (i.e., no gain). The range is -14 dB to +14 dB
enableGainControl
gainControlDb
rxGainControl
432
SIP
Attributes txGainControl
Description the amount of receive gain to set in the MGCP or SIP media stream. Default is 0 (i.e., no gain). The range is -14 dB to +14 dB
The Generic CLI is used for all MediaParam commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
create modify
adaptiveVadFlag vadThreshold modemFaxHandlingCodec jitterBufferMode jitterBufferMaxSize jitterBufferInitialSize echoTailSize rtpDSCPtos signaling802_1_priority payloadType2833 enableGainControl gainControlDb rxGainControl txGainControl
Dependent Commands
Apply a media stream parameter to a trunk group, see Trunk Groups on page 233.
433
SIP
SIP Timers
Each Sip Endpoint Profile contains a SIP timer object. The timers in the SIP timer object control how the endpoint behaves in a SIP network. A SIP Endpoint has the following attributes.
Attribute Timer1 Description The timers A, E, and G; INVITE request retransmit interval (UDP only), non-INVITE request retransmit interval (UDP only), and INVITE response retransmit interval. Range: 100 - 1,000 ms Default: 500 ms Timer2 The maximum retransmit interval for non-INVITE requests and INVITE responses. Range: 800 - 8,000 ms Default: 4,000 ms TimerB The INVITE transaction timeout. Far-end failover occurs when this timer expires. Range: 2,000 - 64,000 ms Default: (64 * timer1) TimerD The wait time for response 0s for TCP/SCTP retransmits. Range: 32,000 - 64,000 ms Default: 32,000 ms TimerF The non-INVITE transaction timeout. Range: 6,400 - 64,000 ms Default: (64 * timer1) TimerH The wait time for ACK receipt. Range: 6,400 - 64,000 ms Default: (64 * timer1) TimerI The wait time for 0s for TCP/SCTP ACK retransmits. Default: 1,000 - 10,000 ms Range: 5,000 ms TimerJ The wait time for 0s for TCP/SCTP non-INVITE request retransmits. Range: 6,400 - 64,000 ms Default: (64 * timer1) TimerK The wait time for 0s for TCP/SCTP response retransmits. Range: 1,000 - 10,000 ms Default: 5,000 ms
434
SIP
Attribute TimerFO
Description Failover timer: the wait time for a response to an INVITE before sending the INVITE to the secondary IP address Range: 800 - 8,000 ms Default: 4,000 ms
435
SIP
The Generic CLI is used for all SIP Access Gateway Profile commands, see Using
Generic CLI Commands on page 6
key
There are no optional parameters for the create command. The modify command applies to the following attributes:
options timers
436
SIP
NOTE: The T7000 is not a proxy. allowHeaderValue This is a bitfield of the types of headers sent in the ALLOW method. By default, all values are set. Values are: INVITE (set by default) Allow INVITE requests REGISTER (set by default) Allow REGISTER requests BYE (set by default) Allow BYE requests CANCEL (set by default) Allow CANCEL requests ACK (set by default) Allow ACK requests NOTIFY Allow NOTIFY requests SUBSCRIBE Allow SUBSCRIBE requests OPTIONS Allow OPTIONS requests UPDATE Allow UPDATE requests INFO (set by default) Allow INFO requests preferredPrivacyMethod NO_PRIVACY_METHOD send calling party name and number in the FROM header. If the calling party presentation is restricted or unavailable, the switch will send From: "Anonymous" <sip:Anonymous@IP_ADDRESS:Port> REMOTE_PARTY_ID (default) send or do not send calling party name and number, depending on what is set in the Remote Party ID header of the SIP message PRIVACY_HEADER send or do not send calling party name and number, depending on what is set in the Privacy header of the SIP message
437
SIP
Attribute expiresHeaderValue
Description contents of the EXPIRES header, how long the current message should be honored from Range: 1,000 to 360,000 milliseconds. 180,000 is the default.
NOTE: If the timer expires before the call is set up, the call is cancelled. dnsLookup Specifies how the switch resolves a Fully Qualified Domain Name (FQDN) into an IP Address and Port number when a lookup in the Host Names table fails. Note that the switch always first checks the Host Names table to resolve an FQDN, regardless of the setting of the dnsLookup attribute. The choices are: DNS_LOOKUP_DISABLED the switch makes no further attempts to resolve the FQDN. DNS_LOOKUP_ENABLED the switch issues a DNS A query to resolve the FQDN into an IP Address (for details, consult RFC 1034). DNS_SRV_LOOKUP_ENABLED the switch issues a DNS SRV query to resolve the FQDN into an IP Address and a Port number (for details, consult RFC 2782). If the DNS SRV query fails, the switch issues a DNS A query to resolve the FQDN into an IP Address. For details, see Resolving Fully Qualified Domain Names on page 465. dnsRespTimerValue How long the switch will wait for a DNS query before giving up. Range: 500 - 10,000 ms Default: 3,000 ms responseToOPTIONS This attribute controls how the switch responds to an OPTIONs request. Since the switch does not support the OPTIONS method, the normal response should be 405, Method not allowed. However, some endpoints (such as the Audio Codes Session Border Controller), cannot process this response. To accommodate such endpoints, the switch can send 200 OK instead. The choices are: Response200ToOptions Send a 200 OK response. Response405ToOptions (default) Send a 405 Method not allowed response.
438
SIP
Attribute sipCallRefMapOption
Description This attribute controls how the switch identifies messages in a SIP dialog. RFC 3261 defines a dialog as the combination of the To tag, the From tag, and the Call-ID. However, some endpoints change the To tag or the From tag after an INVITE message is sent or received. To accommodate such endpoints, the switch can identify messages in a dialog by Call-ID only. The choices are: CALLID_FROM_TO_HDR (default) Use Call-ID, To tag, and From tag to identify messages in a dialog, per RFC 3261. CALLID_ONLY Use only Call-ID to identify messages in a dialog.
secondaryDNReqURI
For SIP subscribers with a secondary DN whose alertInfoHdr attribute is INCLUDE_WITH_SPACES or INCLUDE_WITHOUT_SPACES PRIMARY always set the Req URI address of the INVITE Request to the primary DN, regardless of which DN was dialed (default) SECONDARY always set the Req URI address of the INVITE Request to the secondary DN, regardless of which DN was dialed
alertInfoHdr
NOT_INCLUDE do not include an Alert Info Header in the INVITE Request (default) INCLUDE_WITH_SPACES an Alert-Info header is included in the INVITE Request, consisting of the alertInfoStringPrefix assigned to the Subscriber Access Gatewayendpoint profile, followed by the numeric value received in the Alert-Info Header Alert-String received from the home Application Server, with one space before and one space after the string text INCLUDE_WITHOUT_SPACES an Alert-Info header is included in INVITE Request, consisting of the alertInfoStringPrefix assigned to the Subscriber Access Gateway endpoint profile, followed by the numeric value received in the Alert-Info Header received from the home Application Server.
alertInfoStringPrefix
This is a string used by the SIP phone or ATA to deliver a distinctive ring tone. If the value of the alertInfoHdr attribute is INCLUDE_WITH_SPACES or INCLUDE_WITHOUT_SPACES, this string will be delivered, along with the numeric value received in the Alert-Info Header from the home Application Server.
439
SIP
Attribute regsWithoutChallenge
Description Determines if the Subscriber Access Endpoint can Register without being issued a Challenge. Values are: NO (default) the endpoint cannot Register without answering a Challenge. YES the endpoint can Register without answering a Challenge. NOTE: This attribute was added in Release 6.0.1 to allow interworking with some wireless phones. In most cases however, the default value should be used.
RealmString
Tip
If you are upgrading from Release 5.0, and SIP Registration is failing, try changing this attribute to Tekelec7000.
This is the realm parameter issued in a challenge during the SIP Registration process. You may have to change this value from the default if an Access Gateway requires a custom realm string. Or, you may need to change the realm from the default for security purposes. Otherwise, accept the default value. Default: Taqua-T7000
modify SipAgwEndpointProfile agwProfile1 options maxForwards 4 modify SipAgwEndpointProfile agwProfile1 options responseToOPTIONS 200
Dependent Commands
Associate a SIP Access Gateway endpoint with a SIP Access Gateway Endpoint profile, see Subscriber Access Gateway Endpoint on page 441.
440
SIP
EndpointName
Optional name of IP End Point used to label the IP End Point. Length: 1 - 48 characters.
The SIP Access Gateway Endpoint Profile associated with this endpoint. The BearerGroup associated with this endpoint. See BearerGroup on page 163. The Primary IP address and Port number of the SIP endpoint. Normally this information is supplied by the SIP phone as part of the SIP Register process. A list of alternate IP addresses and Port numbers of the SIP endpoint. This attribute is normally 0 for a Subscriber Access Gateway. HOST_NOT_USED OUTBOUND_PROXY_ACTIVE PRIMARY_ACTIVE SECONDARY_ACTIVE
AltHostIPAddrPairs
actHostIndex
bearerFEs transportType
The Fast Ethernet Interface(s) that handle (RTP). Each PIC card has two FEs. Use multiple FEs for load sharing. This field is read-only. UDP SIP messages are conveyed to this endpoint using User Datagram Protocol
signalingType cmtsName
This field is read-only. SIP This endpoint is served by the SIP protocol. cmtsName - Used to implement the optional DQoS Dynamic Quality of Service) feature. When a CMTS is assigned to an endpoint, a connection is established with the CMTS using the COPS (Common Open Policy Service) protocol. Every call that is made from/ to that endpoint will trigger the DQoS feature to allocate gate's with the CMTS before sending any call processing messages.
441
SIP
Attribute FQDN
Description Fully Qualified Domain Name (FQDN). Normally, a Subscriber Access endpoint does not have an FQDN. If used, a Domain Name System (DNS) will be required to translate the FQDN to an IP address. The outbound proxy IP Address Pair is the address of a firewall. When provisioned, this attribute is used for sending outbound SIP messages to the Subscriber Access Gateway endpoint. If there is a firewall between the switch and the Subscriber Access Gateway endpoint, enter the IP address and port of the firewall.
outboundProxyIPAddrPair
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195
The Generic CLI is used for all SIP Access Gateway Endpoint commands, see
Using Generic CLI Commands on page 6
key
profileName
sIPAddr Port
create SipAgwEndpointProfile agwp1 create SipAgwEndpoint 6924800000 agwp1 bg_agw modify SipAgwEndpoint 6924800000 priHostIPAddrPair 202.158.201.38 5060 destroy SipAgwEndpoint 6924800000
442
SIP
Prerequisites
SIP endpoint profile, see SIP Access Gateway Profile on page 436. Codec Profile List, see CodecProfileList on page 425, and Codec Profile, see CodecProfile on page 427, and Adding CodecProfiles to a CodecProfileList on page 426. Media stream parameter, see MediaParam on page 431
Dependent Commands
Create an IP trunk group and modify its attributes, see see IP Trunk Groups on page 307. Add prefixes, see Prefixes on page 403. Create a route list, see with a route over the IP trunk group, see NANP Route List
on page 519.
443
SIP
The Generic CLI is used for all SIP Emergency Services Gateway Profile commands, see Using Generic CLI Commands on page 6 The required parameters for the create command are:
key
There are no optional parameters for the create command. The modify command applies to the following attributes:
options timers
444
SIP
NOTE: The T7000 is not a proxy. allowHeaderValue This is a bitfield of the types of headers sent in the ALLOW method. By default, all values are set. Values are: INVITE (set by default) Allow INVITE requests REGISTER Allow REGISTER requests BYE (set by default) Allow BYE requests CANCEL (set by default) Allow CANCEL requests ACK (set by default) Allow ACK requests NOTIFY Allow NOTIFY requests SUBSCRIBE Allow SUBSCRIBE requests OPTIONS Allow OPTIONS requests UPDATE Allow UPDATE requests INFO Allow INFO requests preferredPrivacyMethod NO_PRIVACY_METHOD send calling party name and number in the FROM header. If the calling party presentation is restricted or unavailable, the switch will send From: "Anonymous" <sip:Anonymous@IP_ADDRESS:Port> REMOTE_PARTY_ID (default) send or do not send calling party name and number, depending on what is set in the Remote Party ID header of the SIP message PRIVACY_HEADER send or do not send calling party name and number, depending on what is set in the Privacy header of the SIP message
445
SIP
Attribute expiresHeaderValue
Description contents of the EXPIRES header, how long the current message should be honored from Range: 1,000 to 360,000 milliseconds. 180,000 is the default.
NOTE: If the timer expires before the call is set up, the call is cancelled. dnsLookup Specifies how the switch resolves a Fully Qualified Domain Name (FQDN) into an IP Address and Port number when a lookup in the Host Names table fails. Note that the switch always first checks the Host Names table to resolve an FQDN, regardless of the setting of the dnsLookup attribute. The choices are: DNS_LOOKUP_DISABLED the switch makes no further attempts to resolve the FQDN. DNS_LOOKUP_ENABLED the switch issues a DNS A query to resolve the FQDN into an IP Address (for details, consult RFC 1034). DNS_SRV_LOOKUP_ENABLED the switch issues a DNS SRV query to resolve the FQDN into an IP Address and a Port number (for details, consult RFC 2782). If the DNS SRV query fails, the switch issues a DNS A query to resolve the FQDN into an IP Address. For details, see Resolving Fully Qualified Domain Names on page 465. dnsRespTimerValue How long the switch will wait for a DNS query before giving up. Range: 500 - 10,000 ms Default: 3,000 ms responseToOPTIONS This attribute controls how the switch responds to an OPTIONS request. Since the switch does not support the OPTIONS method, the normal response should be 405, Method not allowed. However, some endpoints (such as the Audio Codes Session Border Controller), cannot process this response. To accommodate such endpoints, the switch can send 200 OK instead. Response200 Send a 200 OK response. Response405 (default Send a 405 Method not allowed response.
446
SIP
Attribute sipCallRefMapOption
Description This attribute controls how the switch identifies messages in a SIP dialog. RFC 3261 defines a dialog as the combination of the To tag, the From tag, and the Call-ID. However, some endpoints change the To tag or the From tag after an INVITE message is sent or received. To accommodate such endpoints, the switch can identify messages in a dialog by Call-ID only. The choices are: CALLID_FROM_TO_HDR (default) Use Call-ID, To tag, and From tag to identify messages in a dialog, per RFC 3261. CALLID_ONLY Use only Call-ID to identify messages in a dialog.
diversionRequired
YES populates the redirectingNumber field in the diversion header of a SIP call NO (default) no redirectingNumber is added See ESAOption on page 464. Specifies how the switch determines the incoming route. CALLING_THEN_BOTTOM_VIA (default) when the switch receives an INVITE request, it first determines the originating Endpoint by inspecting the FROM header. It uses NANP routing to determine the incoming IP trunk group. If it can not find an IP trunk group from the FROM header, it then inspects the bottom VIA, as described in the BOTTOM_VIA_HEADER only option. BOTTOM_VIA_ONLY when the switch receives an INVITE request, it determines the incoming route by looking up the Network Endpoint associated with the IP address in the bottom VIA. It uses the default IP Trunk Group of the SIP Ngw End Point for the incoming IP Trunk Group.
ESAOption incomingRoute
NOTE: The required option for Emergency Services Gateways is BOTTOM_VIA_ONLY. pingRespTimerValue Used with ESAOption ESAforPingRespTimeOut. Specifies how long the switch will wait for a response to a ping. When the timer expires, the switch sends another ping to the unreachable endpoint Range: 500 3,000 milliseconds (default = 1,000)
447
SIP
Attribute farEndFailoverControl
Description For use with, but not limited to, TaquaWorks. Values are: PreferActiveHost (default) Always sends the 1st INVITE for a call to the active IP address(see actNearEndNiOid on page 312). PreferPrimary Always send the1st INVITE for a call to the primary IP address. If no response is returned, continue sending INVITE requests for the call to the primary IP address, until either a response is received or the failover timer fires (see TimerFO on page 435). After the failover timer expires, send all subsequent INVITE requests to the secondary IP address until either a response is received or timer B fires (see TimerB on page 434). Repeat this process for the next call, regardless of what happened to the current call. NOTE: Set farEndFailoverControl to PreferPrimary for BroadWorks Applications Servers.
send3xxForINVITE
For use with TaquaWorks systems without a Network Server. This attribute controls how the switch responds to an INVITE from a member of one business group on BroadWorks Application Server to a member of a different business group, also on the BroadWorks Application Server. NOTE: If you are not using TaquaWorks, or if your TaquaWorks system has a Network Server, leave this attributes value at the default. Values are: OFF (default) the switch sends an INVITE to the BroadWorks Application Server. 302 the switch sends a 302 Redirect to the BroadWorks Application Server. This 302 allows BroadWorks to properly handle the call without a Network Server.
Dependent Commands
Associate a SIP Emergency Services Gateway endpoint with a SIP Emergency Services Gateway Endpoint profile, see SIP Emergency Services Gateway Endpoint on page 449
448
SIP
endpointName
actHostIndex
449
SIP
Attribute outboundProxyIPAddrPair
Description The outboundProxyIPAddrPair is the IP address of a Session Border Controller (SBC). When provisioned, this attribute is used for sending outbound SIP messages to the Emergency Services Gateway endpoint. If there is a SBC or proxy firewall between the switch and the Emergency Services Gateway endpoint, enter the IP address and port of the firewall.
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195
The Generic CLI is used for all SIP Emergency Services Gateway commands, see
Using Generic CLI Commands on page 6
There are no optional parameters for the create command. The modify command applies to the following attributes:
The insertInto and the deleteFrom commands apply to the following parameters:
See:
altHostIPAddrPairs
Adding IP Addr Pairs to a SIP Emergency Services Gateway Endpoint on page 452 Removing IP Addr Pairs from a SIP Emergency Services Gateway on page 453
450
SIP
create SipEsgwEndpoint 9724809911 esgwProfile1 bg_esgw 202.158.201.38 5060 query SipEsgwEndpoint 6924801000 destroy SipEsgwEndpoint 6924801000
Prerequisites
SIP endpoint profile, see SIP Emergency Services Gateway Profile on page 444. Codec Profile, see CodecProfile on page 427, and Codec Profile List, see CodecProfileList on page 425. Media stream parameter, see MediaParam on page 431
Dependent Commands
Create an IP trunk group and modify its attributes, see IP Trunk Groups on page 307. Add prefixes, see Prefixes on page 403. Create a route list with a route over the IP trunk group, see LNP Route List on page
517.
451
SIP
Adding IP Addr Pairs to a SIP Emergency Services Gateway Endpoint insertInto SipEsgwEndpoint <key> altHostIPAddrPairs <subkey> <IPAddrPair>
Use the Generic CLI insertInto command to add an IP Address to a SIP Network Gateway Endpoints altHostIPAddrPairs list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> <subkey> Description
Tip
Use a index of 1 to insert an alternate IP Address Pair at the start of the altHostIPAddrPair list. Use a index of -1 to insert an alternate IP Address Pair at the end of the altHostIPAddrPair list.
<IPAddPair>
This attribute specifies which Fast Ethernet you want to add to the SIP Emergency Services Gateway Endpoint.
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195
The following command adds IP Address 202.158.201.39, Port 506 to SIP Emergency Services Gateway 6924001000s altHostIPAddrPairs list:
452
SIP
Removing IP Addr Pairs from a SIP Emergency Services Gateway deleteFrom SipEsgwEndpoint <key> altHostIPAddrPairs <subkey>
Use the Generic CLI deleteFrom command to remove an IP Address from a SIP Emergency Services Gateway Endpoints altHostIPAddrPairs list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
The following example removes the 1st IP Address from SIP Emergency Services Gateway 6924801000s altHostIPAddrPairs list:
453
SIP
The Generic CLI is used for all SIP Network Gateway Profile commands, see Using
Generic CLI Commands on page 6
key
There are no optional parameters for the create command. The modify command applies to the following attributes:
options timers
454
SIP
NOTE: The T7000 is not a proxy. allowHeaderValue This is a bitfield of the types of headers sent in the ALLOW method. By default, all values are set. Values are: INVITE (set by default) Allow INVITE requests REGISTER Allow REGISTER requests BYE (set by default) Allow BYE requests CANCEL (set by default) Allow CANCEL requests ACK (set by default) Allow ACK requests NOTIFY Allow NOTIFY requests SUBSCRIBE Allow SUBSCRIBE requests OPTIONS Allow OPTIONS requests UPDATE Allow UPDATE requests INFO Allow INFO requests preferredPrivacyMethod NO_PRIVACY_METHOD send calling party name and number in the FROM header. If the calling party presentation is restricted or unavailable, the switch will send From: "Anonymous" <sip:Anonymous@IP_ADDRESS:Port> REMOTE_PARTY_ID (default) send or do not send calling party name and number, depending on what is set in the Remote Party ID header of the SIP message PRIVACY_HEADER send or do not send calling party name and number, depending on what is set in the Privacy header of the SIP message
455
SIP
Attribute expiresHeaderValue
Description contents of the EXPIRES header, how long the current message should be honored from Range: 1,000 to 360,000 milliseconds. 180,000 is the default.
NOTE: If the timer expires before the call is set up, the call is cancelled. dnsLookup Specifies how the switch resolves a Fully Qualified Domain Name (FQDN) into an IP Address and Port number when a lookup in the Host Names table fails. Note that the switch always first checks the Host Names table to resolve an FQDN, regardless of the setting of the dnsLookup attribute. The choices are: DNS_LOOKUP_DISABLED the switch makes no further attempts to resolve the FQDN. DNS_LOOKUP_ENABLED the switch issues a DNS A query to resolve the FQDN into an IP Address (for details, consult RFC 1034). DNS_SRV_LOOKUP_ENABLED the switch issues a DNS SRV query to resolve the FQDN into an IP Address and a Port number (for details, consult RFC 2782). If the DNS SRV query fails, the switch issues a DNS A query to resolve the FQDN into an IP Address. For details, see Resolving Fully Qualified Domain Names on page 465. dnsRespTimerValue How long the switch will wait for a DNS query before giving up. Range: 500 - 10,000 ms Default: 3,000 ms responseToOPTIONS This attribute controls how the switch responds to an OPTIONs request. Since the switch does not support the OPTIONS method, the normal response should be 405, Method not allowed. However, some endpoints (such as the Audio Codes Session Border Controller), cannot process this response. To accommodate such endpoints, the switch can send 200 OK instead. Response200ToOptions Send a 200 OK response. Response405ToOptions (default Send a 405 Method not allowed response.
456
SIP
Attribute sipCallRefMapOption
Description This attribute controls how the switch identifies messages in a SIP dialog. RFC 3261 defines a dialog as the combination of the To tag, the From tag, and the Call-ID. However, some endpoints change the To tag or the From tag after an INVITE message is sent or received. To accommodate such endpoints, the switch can identify messages in a dialog by Call-ID only. The choices are: CALLID_FROM_TO_HDR (default) Use Call-ID, To tag, and From tag to identify messages in a dialog, per RFC 3261. CALLID_ONLY Use only Call-ID to identify messages in a dialog.
diversionRequired
YES populates the redirectingNumber field in the diversion header of a SIP call NO (default) no redirectingNumber is added See ESAOption on page 464. Specifies how the switch determines the incoming route. BOTTOM_VIA_THEN_CALLING (default) when the switch receives an INVITE request, it first determines the originating Endpoint by inspecting the FROM header. It uses NANP routing to determine the incoming IP trunk group. If it can not find an IP trunk group from the FROM header, it then inspects the bottom VIA, as described in the BOTTOM_VIA_HEADER only option. BOTTOM_VIA_ONLY when the switch receives an INVITE request, it determines the incoming route by looking up the Network Endpoint associated with the IP address in the bottom VIA. It uses the default IP Trunk Group of the SIP Ngw End Point for the incoming IP Trunk Group.
ESAOption incomingRoute
pingRespTimerValue
Used with ESAOption ESAforPingRespTimeOut. Specifies how long the switch will wait for a response to a ping. When the timer expires, the switch sends another ping to the unreachable endpoint Range: 500 3,000 milliseconds (default = 1,000)
457
SIP
Attribute farEndFailoverControl
Description For use with, but not limited to, TaquaWorks. Values are: PreferActiveHost (default) Always sends the 1st INVITE for a call to the active IP address(see actNearEndNiOid on page 312). PreferPrimary Always send the1st INVITE for a call to the primary IP address. If no response is returned, continue sending INVITE requests for the call to the primary IP address, until either a response is received or the failover timer files (see TimerFO on page 435). After the failover timer expires, send all subsequent INVITE requests to the secondary IP address until either a response is received or timer B fires (see TimerB on page 434). Repeat this process for the next call, regardless of what happened to the current call
Dependent Commands
Associate a SIP Network Gateway endpoint with a SIP Network Gateway Endpoint profile, see SIP Network Gateway Endpoint on page 459
458
SIP
endpointName
Optional name of IP End Point used to label the IP End Point. Length: 1 - 48 characters.
The SIP Network Gateway Endpoint Profile associated with this endpoint. The BearerGroup associated with this endpoint. See BearerGroup on page 163. The Primary IP address and Port number of the SIP endpoint. A list of back-up IP addresses and ports of the connecting softswitch, to be used when a connection cannot be made to the PriHostIPAddrPair. HOST_NOT_USED OUTBOUND_PROXY_ACTIVE PRIMARY_ACTIVE SECONDARY_ACTIVE
actHostIndex
transportType
This field is read-only. UDP SIP messages are conveyed to this endpoint using User Datagram Protocol
signalingType FQDN
This field is read-only. SIP This endpoint is served by the SIP protocol. Optional Fully Qualified Domain Name (FQDN). The T7000 usually forms SIP messages using the IP address of the Network Gateway endpoint. If the Network Gateway requires a Fully Qualified Domain Name (FQDN) instead of an IP address in outbound requests, double-click FQDN and enter the FQDN of the Network Gateway.
NOTE: FQDN may be used to implement a DNS based NGW redundancy scheme.
459
SIP
Attribute outboundProxyIPAddrPair
Description The outboundProxyIPAddrPair is the IP address of a Session Border Controller (SBC). When provisioned, this attribute is used for sending outbound SIP messages to the Network Gateway endpoint. If there is a SBC or proxy firewall between the switch and the Network Gateway endpoint, enter the IP address and port of the firewall.
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195
The Generic CLI is used for all SIP Network Gateway commands, see Using
Generic CLI Commands on page 6
key
profileName BearerGrpKey
sIPAddr Port
There are no optional parameters for the create command. The modify command applies to the following attributes:
The insertInto and the deleteFrom commands apply to the following parameters:
altHostIPAddrPairs bearerFEs
See Adding IP Addr Pairs to a SIP Network Gateway Endpoint on page 462, and Removing Bearer FEs from a SIP Network Gateway on page 463.
create SipNgwEndpoint 6924801000 ngw_p1 bg_ngw1 query SipNgwEndpoint 6924801000 destroy SipAgwEndpoint 6924801000 202.158.201.38 5060
460
SIP
Prerequisites
SIP endpoint profile, see SIP Network Gateway Profile on page 454. Codec Profile List, see CodecProfileList on page 425, and Codec Profile, see CodecProfile on page 427, and Adding CodecProfiles to a CodecProfileList on page 426. Media stream parameter, see MediaParam on page 431
Dependent Commands
Create an IP trunk group and modify its attributes, see IP Trunk Groups on page 307. Add prefixes, see Prefixes on page 403. Create a route list, see with a route over the IP trunk group, see Tandem ANI Route List on page 521.
461
SIP
Adding IP Addr Pairs to a SIP Network Gateway Endpoint insertInto SipNgwEndpoint <key> altHostIPAddrPairs <subkey> <IPAddrPair>
Use the Generic CLI insertInto command to add an IP Address to a SIP Network Gateway Endpoints altHostIPAddrPairs list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> <subkey> Description
Tip
Use a index of 1 to insert an alternate IP Address Pair at the start of the altHostIPAddrPair list. Use a index of -1 to insert an alternate IP Address Pair at the end of the altHostIPAddrPair list.
<IPAddPair>
This attribute specifies which Fast Ethernet you want to add to the SIP Network Gateway Endpoint.
NOTE: The IP address must be entered in the dotted decimal format of four octets in decimal (0-255) separated by periods; for example: 10.2.86.195
The following command adds IP Address 202.158.201.39, Port 506 to SIP Network Gateway 6924001000s altHostIPAddrPairs list:
462
SIP
Removing Bearer FEs from a SIP Network Gateway deleteFrom SipNgwEndpoint <key> altHostIPAddrPairs <subkey>
Use the Generic CLI deleteFrom command to remove an IP Address from a SIP Network Gateway Endpoints altHostIPAddrPairs list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description
<subkey>
The following example removes the 1st IP Address from SIP Network Gateway 6924801000s altHostIPAddrPairs list:
463
SIP
ESAOption
Both the SIP Emergency Services Gateway Options and the SIP Network Gateway Options use the ESAOption. If the switch does not receive a response to an INVITE request from the Network Gateway, Timer B expires, and the feature is invoked.
Tip
See The T7000 Provisioning Guide for a discussion of Emergency Stand Alone and Enhanced Voice Services subscribers.
Emergency Stand Alone (ESA) protection for Enhanced Voice Services (EVS) Subscribers automatic IP trunk group management for all types of SIP calls
The following table shows how different values of the ESAOption affect its behavior.
Value DISABLED (default) ESAonBFired Effect on IP trunk group management None. None. Effect on Enhanced Voice Subscribers None. ESA for the EVS subscriber making the call. ESA for the EVS subscriber making the call. Subsequent calls by EVS subscribers using the same IP Trunk group automatically invoke ESA, until the IP trunk group is back in service.
ESAonBFiredAndPingSep The IP trunk group is automatically taken out of service by marking it unreachable. The IP trunk group is not used for any type of SIP call (not just EVS calls, but regular SIP traffic as well). The switch starts pinging the Network Gateway. When the Network Gateway responds to the switchs ping, the IP trunk group is automatically put back into service by marking it reachable, and the switch reverts to normal routing.
NOTE: The Ping time-out is determined by the pingRespTimerValue. The Ping interval is determined by the pingPeriod.
464
SIP
FQDN on page 442 (Access Gateways) FQDN on page 449 (Emergency Services Gateways) FQDN on page 459 (Network Gateways.
In such cases:
The switch constructs outgoing INVITE requests to the endpoint using the provisioned FQDN in the Request URI and the To header. However, before sending the INVITE, the switch must resolve the FQDN into an IP Address and Port Number. When the switch receives incoming INVITE requests from the endpoint, it must resolve the FQDN in the Contact header so it knows where to send responses.
Prior to release 6.0, the switch resolved FQDNs via the Host Names table. The Host Names table is a static lookup table indexed by FQDN. New in Release 6.0, the switch can resolve an FQDN by sending a query to a Domain Name System (DNS) Server. A DNS Server is a computer in the network which handles FQDN queries from multiple clients. When the IP Address or Port Number associated with an FQDN changes, there is minimal provisioning impact on the network, because only one computer (the DNS Server) needs to be updated with the new information. When the switch has to resolve an FQDN, it always checks the Host Names table first. If the lookup succeeds, the switch uses the IP Address and Port Number from the Host Names table. However, if the FQDN is not found in the Host Names table, the switch checks the value of the endpoints dnsLookup attribute. The value of this attribute determines how the switch resolves the endpoints FQDN. For details, see:
dnsLookup on page 438 (Access Gateways) dnsLookup on page 446 (Emergency Services Gateways) dnsLookup on page 456 (Network Gateways.
465
SIP
If no DNS query is made, or if the DNS query fails, the switch uses the last used IPaddr pair for the endpoint. This is the active IPaddr pair for the endpoint, either:
the last address used by the host the last result returned by the DNS server the provisioned the primary / secondary IP Address)
NOTE: To speed processing, the switch caches DNS Server responses. These responses are not kept forever, but are discarded when they have exceeded their Time To Live. This behavior is controlled by the minimumDnsTTL attribute in the Fast Ethernet Interface that made the DNS query.
For more information, see Host IP Addr Pair on page 429 and Provisioning a DNS Server in the T7000 Provisioning Guide.
466
Shelf
Shelf
A Shelf object contains information about the switch. It has the following attributes:
Attribute Description Note: this field is read-only. The number of the shelf. Range: 1 - 31 netref1OID Network Reference 1 Object ID. Defines the first of two network references from which the shelf may take clock reference. If used, the value is a T1 span OID. See OID on page 30, and tdmConfig (iii) on page 730. netref2OID Network Reference 2Ojbect ID. Defines the second of two network references from which the shelf m may take clock reference. If used, the value is a T1 span OID. See OID on page 30, and tdmConfig (iii) on page 730. tdmSpeed Note: this field is read-only. The speed of the TDM bus. This number varies, depending on the types of card in the shelf. Values are: 8Mhz 10Mhz 12Mhz 14Mhz 16Mhz auditsEnabled Displays the status of the replicated database manager audit function. Values are: ENABLED audits are enabled. This is the normal value for this attribute. All cards will be periodically audited by the Database Manager, which ensures that all cards data is equivalent across the shelf. Any inconsistencies will automatically re-synchronize with the Database Masters copy of the data. DISABLED audits are manually disabled.
key
CAUTION
Database audits should not be disabled during normal operations! AUTO_DISABLED Internal value. PAUSED_FOR_SWACT Internal value.
467
Shelf
Attribute auditPeriod
Description This timer controls how often the Database Manager conducts a database audit. Minimum audit period: 900,000 milliseconds (every15 minutes) Default audit period: 1,800,000 milliseconds (every 30 minutes)
auxAuditsEnabled This field lets you tune the replicated database audits. If enabled, a regular replicated database audit will be followed with an audit of auxiliary data. For example, when an auxAudit is initiated, extra audits are run on the Substitution and Trunk Group databases. Values are: NO Disable auxiliary audits YES (default) Enable auxiliary audits auditExclusions primaryDNS secondaryDNS keyring A dictionary containing a set of databases to be excluded from the next database audit. The IP address of the primary Domain Name Server for Taqua Mail. The IP address of the secondary Domain Name Server for Taqua Mail. A set of software license keys that allow you to run features such as Telemarketer Screening on your switch. Software license keys are only valid on the switch for which they were issued. For software licensing information, e-mail Taqua Marketing at simplify@taqua.com.
The Generic CLI is used for all Shelf commands, see Using Generic CLI Commands on page 6.
NOTE: A Shelf object is automatically created by the system. There is no create command.
auditExclusions keyring
468
Shelf
query Shelf 27 <5368290> Shelf key...................1b (27) netref1OID............0 netref2OID............0 tdmSpeed..............8Mhz auditsEnabled.........ENABLED auditPeriod...........1b7740 (1800000) auxAuditsEnabled......YES auditExclusions.......<5368b98> <5368b98> RepDbMgrDict (0 items) -> primaryDns............0 secondaryDns..........0 minimumDnsTTL.........5a0 (1440) keyring...............0 (0)
469
SS7
SS7
SS7 is a protocol suite that communicates and controls network elements for call setup, tear down, and database lookup. In the PSTN, SS7 uses out-of band signaling on a separate signaling network, to find a path for each call and to set up and manage calls. The switch connects to the SS7 network using signaling links.
Point Codes
All nodes in the SS7 network are identified by a Point Code. A Point Code is a unique number are assigned by Telcordia Point codes are in the following format: ###.###.### (where ### is a number between 1-254).
The first set of digits (network) represent the carrier, for example 244 is WorldComm, 254 is AT&T. The second set of digits (cluster) represent the subsystem/region. The third set of digits (member) represent the node in its CO.
SCCP
The Signaling Connection Control Part (SCCP) provides two functions that MTP does not. SCCP can address applications within a signaling point. MTP can only receive and deliver messages from a node; it does not deal with software applications within a node. SCCP allows the use of other messages using separate applications (referred to as subsystems) within a node. Examples of subsystems are 800 call processing, Advanced Intelligent Network (AIN), and Custom Local-Area Signaling Service (CLASS) services (for example, call back, call return, and calling name).SCCP allows the addressing of applications (referred to as subsystems) within a node to receive messages. SCCP provides support for TCAP.
470
SS7
When the originating signaling point knows the location of the node providing the service, it uses a direct routing capability based on point code plus subsystem number (PC + SSN). When the originating signaling point does not know the location of the node providing the service, it uses an incremental routing capability called Global Title Translation (GTT). GTT frees an originating signaling point from needing to know every potential point code to which it might have to route a message.
SCCP Subsystems
An SCCP subsystem is an application within a Service Switching Point (SSP) switch that recognizes Intelligent Network (IN) calls and can route and connect those calls. Examples are:
800 number translation. Local Number Portability (LNP) Call Back and Call Return.
AIN
The AIN (Advanced Intelligent Network) is a network architecture developed by Telcordia. AIN triggers in the switch software work in conjunction with service logic in an AIN SCP. This design allows the switch to support new services with existing switch software. The Application Peripheral (AP) system from Innovative Systems is an example of an AIN SCP. The AP box (as it is known), can augment the existing T7000 feature set with AIN services as such as Telemarketer Call Screening, Budget Toll, Account Code Plus, and Calling Card/Prepay.
471
SS7
SS7 Services
SS7 provides many services, including: Setting up the connection for a call (ISUP)
Managing the connection for a call (ISUP) Tearing down the connection when a call completes (ISUP) Querying calling party name (TCAP/SCCP) Directing 8XX toll-free and 900 toll calls (TCAP/SCCP) Performing Local Number Portability (LNP) queries (TCAP/SCCP)
When the switch is connected to multiple networks, it enables the switch to have a unique point code in each network. It is used in cap and grow applications.
When the switch is connected to multiple networks, different networks may know the switch by different point codes. The MOPC feature allows the switch to have a unique point code in each network.
NOTE: Do not provision MOPC if the second network recognizes the switch by the same point code.
When the switch is used in a cap and grow application, MOPC can be used to minimize the total amount of reprovisioning needed in the network. Provision MOPC on the link sets connected to the STPs with the Point Code of the legacy switch.
472
SS7
Start SS7 provisioning by creating the local network where the switch resides, and the remote network where the STPs, SSPs, and SCPs reside. (see createSS7Network on page 475).
Create the local node that represents the switch in the local network. Create the STPs, SCPs, and SSPs in the remote network. Create an STP Alias for SCCP Global Title Translation routing (see createNode on page
476).
Create a link set for each adjacent node (see createLinkSet on page 478). Add one or more links to each link set (see createLink on page 480). For each node with transfer capability, create a route over the link set to that node (see createSS7Route on page 482). Create an SCCP node to the local node, and an SCCP node for each SCP addressed by PC + SSN routing (see SCCPNode on page 484.). Create an SCCP subsystem in the local node, and an SCCP subsystem for each SCP addressed by PC + SSN routing (see Adding SCCP Subsystems to an SCCPNode on page 485). Create a TCAP for each service provided by an SCP (see TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492).
473
SS7
Create a node that represents the adjacent switch in the local network (see createNode on page 476). Create a link set to the adjacent node (see createLinkSet on page 478). Add one or more links to the link set to the adjacent node (see createLink on page 480). Create a route over the link set to the adjacent node. If the node is connected to the STP pair, create additional routes over the link sets to the STP pair (see createSS7Route on page 482). If the adjacent node is an SCP (such as the Innovative Systems AP) addressed by PC + SSN routing):
create an SCCP node in the adjacent node (see SCCPNode on page 484.) create an SCCP subsystem in the adjacent node for each SCP addressed by PC + SSN routing (see Adding SCCP Subsystems to an
SCCPNode on page 485
create a TCAP for each service provided by an SCP (see TCAP Service, see TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492).
474
SS7
<networkName>
<localFlag>
createSS7Network LocalNetwork Y Y
Dependent Commands
By creating an SS7 network, you are creating a container for one or more SS7 nodes, and their associated SS7 elements.
<networkName>
Prerequisites
SS7 network, see createSS7Network on page 475 Delete SS7 node, see deleteNode on page 477
Dependent Commands
Before deleting an SS7 network you must first delete its associated SS7 elements which include:
475
SS7
createNode
createNode <nodeName> <DPC> <networkName> <adjacentFlag> <nodeType> <xferFlag>
This command creates an SS7 node in an SS7 network.
Syntax <nodeName> <DPC> <networkName> <adjacentFlag> <nodeType> Description name of the SS7 node Destination Point Code of the SS7 node. See Point Codes on page 470. Name of the SS7 network created via createSS7Network. Y if the node is adjacent to the local node N if the node is not adjacent to the local node Local the local T7000 Remote a node in the SS7 network with a known point code. Alias a node in the SS7 network with a hidden, private point code. See setPCMap on page 500. <xferFlag> .Y if the node has transfer capability. This includes STPs, T7000s and Legacy Switches that can route messages to other nodes in the SS7 network. N if the node does not have transfer capability.
Prerequisites
SS7 network, see createSS7Network on page 475
createNode Local 229-100-000 Local_net N Local N createNode STP1 229-100-101 Remote_net Y Remote Y
476
SS7
deleteNode
deleteNode <nodeName>
This command deletes an SS7 node from an SS7 network.
Syntax Description name of the SS7 node
<nodeName>
Prerequisites
SS7 node, see createNode on page 476.
deleteNode STP1
Dependent Commands
Before deleting an SS7 node you must first delete its associated SS7 elements which include:
the SCCP node, SS7 Trunk groups using that node, all routes to the node. link sets to the node (and the links within the link set)
477
SS7
Prerequisites
SS7 node, see createNode on page 476
Syntax Description name of the SS7 link set point code of the SS7 node that terminates the link set. See Point Codes on page 470. type of link set: A (A-link sets) connects to STPs and provides signaling to the SS7 network
Tip
See Appendix D of the T7000 Provisioning Guide for examples using Alias link sets.
F (F-link sets) connect to another SSP and provides signaling between the switches but not with the SS7 network L (Alias link sets) The link set connects the local switch to a subtending switch that shares a common connection to the SS7 network through the local switchs A-links. Alias link sets are primarily used for cap-and-grow deployments. kind of link set error correction: T basic error correction used for link sets not using satellite (default) S Preventive cyclic retransmission (PCR) is the error correction method used for link sets using satellite.
<kind>
WARNING
The Preventive cyclic retransmission feature not currently implemented. Do not specify this parameter!
NOTE: All links in a link set must have the same error correction method. Even if only one link is configured via satellite, assign PCR to the entire link set.
478
SS7
Dependent Commands
Add links to the link set, see createLink on page 480 Activate the link set, see activateLinkSet on page 639.
Prerequisites
SS7 link set, createLinkSet on page 478 Delete SS7 links, see deleteLink on page 481
deleteLinkSet Linkset1
Dependent Commands
Before deleting an SS7 link set you must first delete its associated SS7 elements which include:
479
SS7
createLink
createLink <linkName> <trunkOID> <linkSetName> <SLC> <type>
This command creates an SS7 link and associates it with an existing SS7 link set. Each link set can hold up to 16 links. A switch supports a total of 40 links.
Syntax Description name of link to create Trunk Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30. name of a link set previously created. Signaling Link Code a unique number within a link set that identifies the link. Range: 0-15.
<linkName> <trunkOID>
<linkSetName> <SLC>
Tip
Coordinate SLC assignments with the adjacent node. SLC assignments typically start with 0 for the first link in a link set
<Type>
Type of link: a A link. Can be placed only in A link sets f F link. Can be placed only in F-link sets and Alias-link sets.
Prerequisites
SS7 link set, see createLinkSet on page 478
Dependent Commands
Before the link can carry traffic, it must unblocked, see unblockLink on page 640.
480
SS7
deleteLink
deleteLink <linkName>
This command deletes an SS7 link from an SS7 link set.
Syntax Description name of link to delete
<linkName>
Prerequisites
SS7 link, see createLink on page 480 Block the SS7 link, see blockLink on page 640
deleteLink Link_1_1
Dependent Commands
Before the link can be deleted, it must blocked, see blockLink on page 640
481
SS7
Tip
A route to an adjacent node over a link set that terminates at that node should always be provisioned as a primary route. Any other routes to that node should be provisioned as secondary routes.All routes to non-adjacent nodes should always be provisioned as primary routes
Tip
To specify a combined link set, set the same priority for both routes to a node.
Prerequisites
SS7 link set, see createLinkSet on page 478. SS7 node, see createNode on page 476.
482
SS7
Prerequisites
SS7 route, see createSS7Route on page 482
deleteSS7Route route_stp
CAUTION
Deleting an SS7 route may negatively affect operations!
483
SS7
SCCPNode
A Signaling Connection Control Part (SCCP) node has the following attributes:
Attribute Description Point code of the new SCCP node. See Point Codes on page 470. A dictionary containing the SCCP Subsystems within this SCCP Node. Note: this field is read-only. The Accessibility state of SCCP Node. Values are: NOT_ACCESSIBLE ACCESSIBLE
key
subsystems accessible
The Generic CLI is used for all SCCPNode commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
See:
subsystems
Prerequisites
Adding SCCP Subsystems to an SCCPNode on page 485 Removing SCCP Subsystems from an SCCPNode on page 485
SS7 node, see createNode on page 476 SCCP subsystem(s), see Adding SCCP Subsystems to an SCCPNode on page 485
484
SS7
Adding SCCP Subsystems to an SCCPNode insertInto SCCPNode <key> subsystems <subkey> SCCPSubsys <ssn>
Use the Generic CLI insertInto command to add an SCCP Subsystem to a SCCPNodes subsystems dictionary. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> <subkey> SCCPNode point code. This is the subsystem number of the SCCP application on the remote switch. It is used as the key to the SCCPNodes subsystems dictionary. Range: 2 - 254. <ssn> This is the subsystem number of the SCCP application on the remote switch. It must be the same as the subkey. Range: 2 - 254. Description
The following command adds an entry for SCCP subsystem 253 to the SCCPNode with a point code of 229-101-0.
insertInto SCCPNode 229-101-0 subsystems 253 SCCPSubsys 253
Removing SCCP Subsystems from an SCCPNode deleteFrom SCCPNode <key> subsystems <subkey>
Use the Generic CLI deleteFrom command to remove a SCCP Subsystem from a SCCPNodes subsystems dictionary. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> <subkey> SCCPNode point code. This is the subsystem number of the SCCP application on the remote switch. Description
The following example removes the subsystem 253 from the SCCPNode with a point code of 229-101-0.
Dependent Commands
Delete the TCAP Service using the SCCP subsystems.
485
SS7
query SCCPNode 229-101-0 <5b1c030> SCCPNode key..........229-101-0 subsystems...<5b1c4b8> <5b1c4b8> SCCPSubsystemDict (3661851 items) -> f0 (240): <5b41500> SCCPSubsys pc................229-101-0 ssn...............f0 (240) accessible........NOT_ACCESSIBLE fc (252): <5b2efa8> SCCPSubsys pc................229-101-0 ssn...............fc (252) accessible........NOT_ACCESSIBLE fe (254): <5b34380> SCCPSubsys pc................229-101-0 ssn...............fe (254) accessible........NOT_ACCESSIBLE accessible...ACCESSIBLE
486
SS7
<pointCode>
Prerequisites
SCCPNode, see SCCPNode on page 484.
Dependent Commands
Remove all SCCP Subsystems from to the SCCP node, see Removing SCCP
Subsystems from an SCCPNode on page 485
487
SS7
TCAPServiceGTT
There are two types of TCAP Service objects: one for Global Title Translation routing, the other for Point Code + Subsystem Number routing. Use the TCAPServiceGTT object for Global Title Translation routing. A TCAPServiceGTT object has the following attributes:
Attribute Description the unique name of the TCAP service Type of TCAP service: CNAMESVC calling party name service SACAINSVC Service Access Code (SAC) Advanced Intelligent Network (AIN) based service SACIN800SVC Service Access Code (SAC) Advanced Intelligent Network (AIN) based 800 service LNPAINSVC Local Number Portability AIN service AINSVC services allows the switch to communicate with an SCP for AIN information. See AIN on page 471. CBACKSVC call back service, a/k/a CLASS feature Automatic Callback CRETURNSVC call return service TCAPMWISVC TCAP Message Waiting Indicator service
key svcType
routeType
The type of routing that the SCCP will use for this TCAP service. GTT (default) Global Title Translation: directs TCAP queries to the STP for GTT.
local SCCP subsystem number for this TCAP service Range: 2 - 254 point code of the remote node for GTT routing GTT routing Global Title Translation Type NOTE: Translation Types are supplied by the provider of the TCAP service.
t1Timer
Time value to wait for response to TCAP query (msec) Range: 1000-3000 Default: 3000
488
SS7
Attribute
Description Resume Scanning Timer. The time in milliseconds that the originating switch waits to resume scanning after the calling party does not answer special ringing. This timer begins when the application of special ringing has timed out. This timer stops if the Call Back/Call Return attempt is deactivated. Range:180000 - 720000 Default: 3000 Initial Query Response Timer. The time in milliseconds that the originating switch waits for a response to the initial query. Range:1000 - 5000 Default: 3000 Monitoring Timer. The time in milliseconds that the called party of a Call Back/Call Return request is monitored for an idle notification. Range:150000 - 2100000 Default: 1800000 Terminating Scanning Monitoring Timer. The time in milliseconds the originating switch will wait for a response from the terminating switch to any query other than the initial query. Range: 0 - 1800000 Default: 0 Outstanding Notification Timer. The time the terminating switch should wait after sending an Idle status to the originating switch, before rechecking the called lines busy/idle status. Range: 0 - 2100000 Default: 0 Subsequent Query Response Timer. The time in milliseconds the originating switch will wait for a response from the terminating switch to any other query other than the initial query. Range: 1000 5000 Default: 3000 Originating/Terminating Switch Overall Monitoring Timer. The maximum continuous time in milliseconds the particular request can be in effect for a given customer. This limits the number of times a customer may reactivate a Call Back/Call Return request. Range: 7200000 - 14400000 Default: 10800000
t2Timer
t5Timer
t6Timer
t7Timer
t8Timer
t9Timer
t10Timer
489
SS7
Attribute t11Timer
Description Inter - Busy/Idle Query Duration Timer. The time in milliseconds for the Inter-Busy/Idle Query Duration Timer. The terminating switch uses this timer to control the status of a queued entry with originating scanning. If the amount of time between queries exceeds this timer, the corresponding queue entry is flagged inactive. T11 is the terminating switch maximum allowed value for the originating scan rate, plus 5 seconds. This timer is initialized when a busy/idle query for a queued Call Return/Call Back request, which does not have outstanding notification, is received by the terminating switch. This timer stops when the Automatic Callback request is marked as having outstanding notification, the Automatic Callback request is completed or the Automatic Callback request is deactivated. Range: 0 - 5700000 Default: 0 Originating Scan Rate. The time in milliseconds to control the active/inactive status of a queued entry with orig scanning. Range: 30000 -600000 Default: 60000
origScanRate
490
SS7
The Generic CLI is used for all TCAPServiceGTT commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
Prerequisites
t1Timer t2Timer t5Timer t6Timer t7Timer t8Timer t9Timer t10Timer t11Timer origScanRate
SCCP Nodes, see SCCPNode on page 484. SCCP SSNs on the local node, the STP Alias (GTT routing) or SCP (PCSSN routing), see Adding SCCP Subsystems to an SCCPNode on page 485
create TCAPServiceGTT sacin800 SACIN800SVC PCSSN 252 229-101-000 4
491
SS7
TCAPServicePCSSN
There are two types of TCAP Service objects: one for Global Title Translation routing, the other for Point Code + Subsystem Number routing. Use the TCAPServicePCSSN object for Point Code + Subsystem Number routing. A TCAPServicePCSSN object has the following attributes:
Attribute Description the unique name of the TCAP service Type of TCAP service: CNAMESVC calling party name service SACAINSVC Service Access Code (SAC) Advanced Intelligent Network (AIN) based service SACIN800SVC Service Access Code (SAC) Advanced Intelligent Network (AIN) based 800 service LNPAINSVC Local Number Portability AIN service AINSVC services allows the switch to communicate with an SCP for AIN information. See AIN on page 471. CBACKSVC call back service, a/k/a CLASS feature Automatic Callback CRETURNSVC call return service TCAPMWISVC TCAP Message Waiting Indicator service
key svcType
routeType
The type of routing that the SCCP will use for this TCAP service. PCSSN (default) Point Code/Subsystem Number: directs TCAP queries directly to the Service Logic Host on a specific SCP or applications server.
local SCCP subsystem number for this TCAP service Range: 2 - 254 point code of the remote node for PCSSN or GTT routing PCSSN routing remote subsystem number NOTE: Remote Subsystem Numbers are supplied by the provider of the TCAP service.
t1Timer
Time value to wait for response to TCAP query (msec) Range: 1000-3000 Default: 3000
492
SS7
Attribute
Description Resume Scanning Timer. The time in milliseconds that the originating switch waits to resume scanning after the calling party does not answer special ringing. This timer begins when the application of special ringing has timed out. This timer stops if the Call Back/Call Return attempt is deactivated. Range:180000 - 720000 Default: 3000 Initial Query Response Timer. The time in milliseconds that the originating switch waits for a response to the initial query. Range:1000 - 5000 Default: 3000 Monitoring Timer. The time in milliseconds that the called party of a Call Back/Call Return request is monitored for an idle notification. Range:150000 - 2100000 Default: 1800000 Terminating Scanning Monitoring Timer. The time in milliseconds the originating switch will wait for a response from the terminating switch to any query other than the initial query. Range: 0 - 1800000 Default: 0 Outstanding Notification Timer. The time the terminating switch should wait after sending an Idle status to the originating switch, before rechecking the called lines busy/idle status. Range: 0 - 2100000 Default: 0 Subsequent Query Response Timer. The time in milliseconds the originating switch will wait for a response from the terminating switch to any other query other than the initial query. Range: 1000 5000 Default: 3000 Originating/Terminating Switch Overall Monitoring Timer. The maximum continuous time in milliseconds the particular request can be in effect for a given customer. This limits the number of times a customer may reactivate a Call Back/Call Return request. Range: 7200000 - 14400000 Default: 10800000
t2Timer
t5Timer
t6Timer
t7Timer
t8Timer
t9Timer
t10Timer
493
SS7
Attribute t11Timer
Description Inter - Busy/Idle Query Duration Timer. The time in milliseconds for the Inter-Busy/Idle Query Duration Timer. The terminating switch uses this timer to control the status of a queued entry with originating scanning. If the amount of time between queries exceeds this timer, the corresponding queue entry is flagged inactive. T11 is the terminating switch maximum allowed value for the originating scan rate, plus 5 seconds. This timer is initialized when a busy/idle query for a queued Call Return/Call Back request, which does not have outstanding notification, is received by the terminating switch. This timer stops when the Automatic Callback request is marked as having outstanding notification, the Automatic Callback request is completed or the Automatic Callback request is deactivated. Range: 0 - 5700000 Default: 0 Originating Scan Rate. The time in milliseconds to control the active/inactive status of a queued entry with orig scanning. Range: 30000 -600000 Default: 60000
origScanRate
494
SS7
The Generic CLI is used for all TCAPServicePCSSN commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
Prerequisites
t1Timer t2Timer t5Timer t6Timer t7Timer t8Timer t9Timer t10Timer t11Timer origScanRate
SCCP Nodes, see SCCPNode on page 484. SCCP SSNs on the local node, the STP Alias (GTT routing) or SCP (PCSSN routing), see Adding SCCP Subsystems to an SCCPNode on page 485
create TCAPServicePCSSN sacin800 SACIN800SVC 252 229-101-000 252
495
SS7
<key>
Prerequisites
SCCP Node, see SCCPNode on page 484. SCCP SSN on the local node, the STP Alias (GTT routing) or SCP (PCSSN routing), see Adding SCCP Subsystems to an SCCPNode on page 485 TCAP Service, see TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492
496
SS7
TcapMwiParms
TcapMwiParms enable the switch and an SS7 voice mail system (VMS) to communicate MWI status to one another. The switch connects to a VMS using an SS7 F-link. The subscriber, either directly connected to the switch or connected to a subtending node of the switch, receives a Message Waiting Indicator (MWI) notification when there are one or more new voice mail messages at the VMS. A TcapMwiParms object has the following attributes:
Attribute key mSRID Description voice mail subscribers DN TCAP Message Storage and Retrieval Identifier (MSRID). Uniquely identifies each VMS providing TCAP MWI. Must be 10 digits long. Range: 0000000001-9999999999. callingDN mwiType This field is read only. DN of Voice Mail System. This read only field is for internal use. Values are: ACTIVE1 ACTIVE2 ACTIVE3 callingPartyNumber callType This field is read only. DN of the voice mail originator This field is read only. Bearer capability. Values are: ISDN ISDN PRI ANLG Analog timeStamp numberOfMessages This field is read only. Timestamp sent by the Message Storage and Retrieval system This field is read only. Number of voice message in the voice mail box
497
SS7
The Generic CLI is used for all TcapMwiParms commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
mSRID
query TcapMwiParms 8174801022 <33c1be0> TcapMwiParms key.................."8174801022" mSRID................"1234560001" callingDN............<> mwiType..............0 callingPartyNumber...<> callType.............ISDN timestamp............<> displayText..........<> numberOfMessages.....0 (0)
Prerequisites
VMS, see Voice Mail on page 586 F-link connecting to the VMS, see SS7 on page 470
498
SS7
setMOPC
setMOPC <LinkSetName> <pointCode>
This command assigns an Multiple Originating Point Code to an SS7 link set. See Multiple Originating Point Code on page 472..
Syntax LinkSetName the link set name the alternate originating point code to be used for messages sent over this link set. Description
<pointCode>
Prerequisites
At least two SS7 Networks. See createSS7Network on page 475 Or, an Alias node. See createNode on page 476
NOTE: Only use multiple point codes to connect to two different SS7 networks that have each assigned a different point code to the switch. Do not use this feature if both SS7 networks recognize the same point code
setL3MOPC
setL3MOPC <LinkSetName> <pointCode>
Prerequisites
A link set.
Syntax LinkSetName the link set name L3 Multiple Originating Point Code is the point code that identifies the local node with an alternate point code for MTP Level 3 messages. See Level 3 Multiple Originating Point Code on page 472 Description
<pointCode>
499
SS7
setPCMap
setPCMap <aliasNodeName> <destPointCode> <CIC> <range>
This command configures ISDN routes to a subtending node. An alias Point Code (PC) map directs ISUP messages from a remote switch through the local switch to an alias switch. This mapping allows an alias switch to connect to a distant node using voice trunks.t.
Syntax <aliasNodeName> <destPointCode> name of subtending node Distant end node's point code. The point code that the switch provides signaling to, for example, an Access Tandem's point code. See Point Codes on page 470. The circuit identification code of the first SS7 trunk connecting to the subtending node. The number of CICs mapped by the switch to the subtending node. Description
<CIC> <range>
Prerequisites
An subtending switch is provisioned for an alias point (see createNode on page
476).
500
SS7
CAUTION
Deleting routing may negatively affect operations.
Prerequisites
A Point Code Map, see setPCMap on page 500
Syntax <aliasNodeName> <destPointCode> subtending node name Distant end node's point code. This is the point code that the switch will provide signaling to: an Access Tandem's point code, for example The lowest numbered circuit identification code in the SS7 trunk group that connects the alias and destination nodes. Description
<lowCIC>
501
SS7
Prerequisites
SS7 link, see createLink on page 480
Prerequisites
SS7 link, see createLink on page 480
Syntax Description new timer value in milliseconds Range: 10,000 to 30,000 0 to disable sending SLTM messages linkName link name skip this parameter to apply this the value to all SS7 links
<new_period>
502
SS7
CAUTION
Use caution when setting SS7 link timers.
The following commands set the values for MTP Level 2 and MTP Level 3 SS7 timers
Syntax new_period linkName all_pcr all_basic Description new timer value see the limits in the table below for specific values Link name set the timer value for a specific link all_basic basic error correction used for link sets not using satellite (default) all_pcr Preventive cyclic retransmission (PCR) is the error correction method used for link sets using satellite. This feature not currently implemented.
The following table contains the names of all of the commands and their limits.
Command L2Tie_period L2Tin_period L2T1_period L2T2_period L2T3_period L2T4e_period L2T4n_period L2T5_period L2T6_period L2T7_period L3T1_period L3T2_period Description MTP Level 2 timer value for emergency alignment error rate monitor threshold Limits 1 - 10 ms
MTP Level 2 timer value for normal alignment error rate monitor 1 - 10 ms threshold MTP Level 2 timer value for aligned/ready MTP Level 2 timer value for not aligned MTP Level 2 timer value for aligned MTP Level 2 timer 4 emergency value, for the emergency proving period when the link set only contains 1 link 12,900 - 16,000 ms 5,000 - 14,000 ms 5,000 - 14,000 ms 593 ms
MTP Level 2 timer 4 normal value for when the link set contains 2,300 ms more than one link MTP Level 2 timer value for sending Status Indication Busy (SIB) MTP Level 2 timer value for remote congestion MTP Level 2 timer value for excessive delay of acknowledgement MTP Level 3 timer value delay to avoid message missequencing on changeover MTP Level 3 timer value waiting for changeover acknowledgment 80 - 120 ms 1,000 - 6,000 ms 500 - 2,000 ms 500 - 1,200 ms 700 - 2,000 ms
503
SS7
Command L3T3_period L3T4_period L3T5_period L3T6_period L3T7_period L3T8_period L3T10_period L3T12_period L3T13_period L3T14_period L3T15_period L3T16_period L3T17_period L3T19_period L3T20_period L3T21_period L3T22_period L3T23_period
Description MTP Level 3 timer value delay to avoid mis-sequencing on changeback MTP Level 3 timer value waiting for changeback acknowledgment (first attempt) MTP Level 3 timer value waiting for changeback acknowledgment (second attempt) MTP Level 3 timer value delay to avoid message missequencing on controlled rerouting MTP Level 3 timer value waiting for signaling data link connection acknowledgment MTP Level 3 timer value transfer-prohibited inhibited timer (transient solution) MTP Level 3 timer value waiting to repeat signaling route set test message MTP Level 3 timer value waiting for uninhibit acknowledgment MTP Level 3 timer value waiting for force uninhibit MTP Level 3 timer value waiting for inhibition acknowledgment MTP Level 3 timer value waiting to repeat signaling route set congestion test
Limits 500 - 1,200 ms 500 - 1,200 ms 500 - 1,200 ms 500 - 1,200 ms 1,000 - 2,000 ms 800 - 1,200 ms 30,000 - 60,000 ms 800 - 1,500 ms 800 - 1,500 ms 2,000 - 3,000 ms 2,000 - 3,000 ms
MTP Level 3 timer value waiting for route set congestion status 1,400 - 2,000 ms update MTP Level 3 timer value delay to avoid oscillation of initial alignment failure and link restart MTP Level 3 failed link craft referral timer value MTP Level 3 timer value waiting to repeat local inhibit test 800 - 1,500 ms 480,000 - 600,000 ms 90,000 - 120,000 ms
MTP Level 3 timer value waiting to repeat remote inhibit test 90,000 - 120,000 ms MTP Level 3 value timer at restarting SP waiting for signaling links to become available MTP Level 3 timer value at restarting SP, started after T22, waiting to receive all Traffic Restart Allowed (TRA) messages (network-dependent) MTP Level 3 timer value at restarting SP with transfer function, started after T23, waiting to broadcast all TRA messages (network-dependent) 0 - 60,000 ms 0 - 60,000 ms
L3T24_period
15,000 ms
MTP Level 3 timer value at the SP adjacent to the restarting SP, 30,000 - 35,000 ms waiting for Traffic Restart Allowed (TRA) message MTP Level 3 timer value at restarting SP waiting to repeat Traffic Restart Waiting (TRW) MTP Level 3 timer value of the minimum duration of unavailability for full restart 12,000 - 15,000 ms 2,000 5,000 ms
504
SS7
Description
Limits
MTP Level 3 timer value at SP adjacent to restarting SP, waiting 3,000 - 35,000 ms for Traffic Restart Waiting (TRW) message MTP Level 3 timer value started when TRA message is sent in response to unexpected TRA or TRW message MTP Level 3 false link congestion detection timer value MTP Level 3 probation timer value for link oscillation Procedure B MTP Level 3 suspension timer value for link oscillation Procedure B 60,000 - 65,000 ms 10,000 - 120,000 ms 60,000 - 600,000 ms 5,000 - 120,000 ms
Prerequisites
SS7 link, see createLink on page 480
505
SS7
L2TX_onset
L2TX_onset <level> <new_threshold> [linkName]
This command sets the transmission congestion onset limit for levels 1 to 3.
Syntax <level> <new_threshold> Description 1 - 3, onset is the second threshold for detecting the start of congestion (levels 1, 2, and 3) The number of messages before the onset of congestion: 31-49 Level 1 61-79 Level 2 91-109 Level 3 [linkName] Link name skip this parameter to set this value for all SS7 links
CAUTION
Use caution when setting SS7 congestion levels.
Prerequisites
SS7 link, see createLink on page 480
L2TX_onset 1 38 Link_1
506
SS7
CAUTION
Use caution when setting SS7 congestion levels.
NOTE: Each congestion abatement must be lower than the corresponding congestion onset level. See L2TX_onset on page 506.
Prerequisites
SS7 link, see createLink on page 480
L2TX_abatement 2 45 Link_1
507
SS7
CAUTION
Use caution when setting SS7 congestion levels.
NOTE: Each congestion discard must be lower than the corresponding congestion onset level. See L2TX_onset on page 506.
Prerequisites
SS7 link, see createLink on page 480
L2TX_discard 1 58 Link_1
508
SS7
CAUTION
Use caution when setting SS7 congestion levels.
Prerequisites
SS7 link, see createLink on page 480
L2RX_congestion 80
CAUTION
Use caution when setting SS7 congestion levels.
Prerequisites
SS7 link, see createLink on page 480
L2RX_abatement 45
509
SS7
CAUTION
Use caution when setting SS7 congestion levels.
Prerequisites
SS7 link, see createLink on page 480
Syntax <new_level> Description The threshold for monitoring the reduction of congestion, from 61 messages and above.
L2RX_discard 101
510
511
attribute fraudIndicator
value 0 does not trace calls from the subscriber 1 creates a secondary CDR for each call from the subscriber
All ANI Subscriber provisioning is carried out with the Generic CLI, see Using
Generic CLI Commands on page 6.
Prerequisites
restrictions
SS7 trunk groups incoming to the switch that tandem to the PSTN. see Route Lists
on page 514
create AniSubscriber 9724812222 Liao David modify AniSubscriber 9724812222 deniedList deny modify AniSubscriber 9724812222 restrict NO_INTRALATA 1 modify AniSubscriber 9724812222 restrict NO_INTERLATA 1 query AniSubscriber 9724812222 <4909030> AniSubscriber key.............."9724812222" lastName........."Liao" firstName........"David" restrict.........(BITFIELD) -> 3 .NO_INTRALATA .NO_INTERLATA allowedList......<> deniedList......."deny" suspension.......OFF fraudIndicator...OFF destroy AniSubscriber 9724812222
512
query AniSubscriber 9724901234 <4909830> AniSubscriber key.............."9724901234" lastName........."Black" firstName........"Andrew" restrict.........(BITFIELD) -> 10 .NO_OA_INTERNATIONAL allowedList......<> deniedList.......<> suspension.......OFF fraudIndicator...OFF
513
Route Lists
Route Lists
A route list defines the circuit path for specific numbers. Use a route list to add and remove routes from specific paths. You can create the following types of route lists:
Carrier, see Carrier Route List on page 515 LNP, see LNP Route List on page 517 NANP, see NANP Route List on page 519 Tandem ANI, see Tandem ANI Route List on page 521 Tandem Carrier, see Tandem Carrier RouteList on page 523 Tandem Trunk Group, see Tandem TG Route List on page 525
514
Route Lists
Tip
Use this attribute to implement time-of-day alternate routing. To do this, provision two routes. At any time, mark one route active, and mark the other route inactive.
Tip
Use this attribute when pre-provisioning a new set of routes. Mark the new set of routes inactive. You can then effect an immediate cutover to the new route list by deactivating the in-use route list and activating the pre-provisioned route list. An immediate cutover eliminates any downtime for call attempts while the operator is dragging and dropping trunk groups over to the route list. Also, the new routelist can be pre-provisioned during the day, and cutover can take place during off-hours.
selectionMethod
FIRST_AVAILABLE (default) always select the first available route ROUND_ROBIN use the available routes sequentially
515
Route Lists
The the Generic CLI is used for all carrier route list commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key min
active selectionMethod
routes
See Adding a Route to a Route List on page 527, and Removing a Route from a Route
List on page 529.
Prerequisites
Carrier, see Carriers on page 196
516
Route Lists
Tip
Flag prefixes as ported. See
If a called DN is not a local subscriber and the called prefix is flagged as ported, the switch queries an LNP database to determine the LRN (Local Routing Number) of the ported DN. When the LNP database responds to the query from the switch, it returns either the original dialed number or the LRN. If the database returns the original dialed number, the call routes normally. If, however, the database returns an LRN, the switch uses the LRN and the LNP Route Lists to route the call to the ported subscribers switch.
NOTE: The LNP route list should contain routes for all LRNs in the switchs LATA.
For example, a call is made to 806-689-1234. The switch determines that the prefix 806689 is ported. The switch queries the LNP database, which returns the LRN 806-689-9999. The switch routes the call using the 806-689-9999 LNP route list. An LNP Route List has the following attributes:
Attribute key min max routes active Description unique name of LNP route list the lowest LRN in the remote switch Length: 6 - 10 digits the highest LRN in the remote switch Length: 6 - 10 digits a list of routes to the remote switch this flag controls if the route list is usable. Values are: NO do not use this route list (useful when adding or removing routes to the route list). Yes (default) use this route list. This is normal state for a route list. selectionMethod FIRST_AVAILABLE (default) always select the first available route ROUND_ROBIN use the available routes sequentially
517
Route Lists
The the Generic CLI is used for all LNP route list commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key min
routes
See Adding a Route to a Route List on page 527, and Removing a Route from a Route
List on page 529.
Prerequisites
Ported prefix, see Prefixes on page 403. LRN, see Rate Centers on page 410.
518
Route Lists
519
Route Lists
The the Generic CLI is used for all NANP route list commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key min
routes
See Adding a Route to a Route List on page 527, and Removing a Route from a Route
List on page 529.
Prerequisites
Prefix, see Prefixes on page 403.
520
Route Lists
The the Generic CLI is used for all tandem ANI route list commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key min
routes
521
Route Lists
See Adding a Route to a Route List on page 527, and Removing a Route from a Route
List on page 529.
Prerequisites
Trunk groups with matching protocols on the End Office (EO) and the AT, see Route Lists on page 514 and the following table:
Trunk Protocol Feature Group D (FGD) Feature Group C (FGC) SS7 FGD-Access Tandem (FGDAT) None Carrier Identification code Carrier Identification code/route code Special Routing Information to the AT
Dependent Commands
Add outgoing trunk groups for the connecting IXCs, see Route Lists on page 514. Add the outgoing trunk groups to the tandem ANI route list, see Adding a Route to
a Route List on page 527.
Add Tandem ANI Subscribers to screen calls based on the ANI, see query AniSubscriber on page 513
522
Route Lists
The the Generic CLI is used for all tandem carrier route list commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key min
active selectionMethod
routes
See Adding a Route to a Route List on page 527, and Removing a Route from a Route
List on page 529.
523
Route Lists
Prerequisites
Carrier, see Carriers on page 196. Trunk groups with matching protocols on the End Office (EO) and the AT, see Route Lists on page 514 and the following table:
Trunk Protocol FGD FGC SS7 Allowed Routing by the AT Incoming ANI Incoming trunk group Incoming trunk group Incoming ANI Incoming trunk group Incoming Carrier Identification code FGDAT Incoming ANI Incoming trunk group Incoming Carrier Identification code and route code
Dependent Commands
Add outgoing trunk groups for the connecting ICs, see Route Lists on page 514. Add the outgoing trunk groups to the tandem carrier route list, see Adding a Route to a Route List on page 527.
524
Route Lists
The the Generic CLI is used for all tandem trunk group route list commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
active selectionMethod
routes
See Adding a Route to a Route List on page 527, and Removing a Route from a Route
List on page 529.
525
Route Lists
Prerequisites
Trunk groups with matching protocols on the End Office (EO) and the AT, see Route Lists on page 514 and the following table:
Trunk Protocol FGD FGC SS7 Allowed Routing by the AT Incoming ANI Incoming trunk group Incoming trunk group Incoming ANI Incoming trunk group Incoming Carrier Identification code FGDAT Incoming ANI Incoming trunk group Incoming Carrier Identification code and route code
Dependent Commands
Add outgoing trunk groups for the connecting ICs, see Route Lists on page 514. Add the outgoing trunk groups to the tandem carrier route list, see Adding a Route to a Route List on page 527.
526
Route Lists
Tip
When entering ranges for route lists, use X as a wild card. For example, instead of entering two parameters for a new route list (972480000 9724809999), enter 972480XXXX for the same results.
Syntax <key>
Description
<subkey>
This is the index in the routes list where you want to enter the route.
Tip
Use a index of 1 to insert a route at the start of a Route List. Use a index of -1 to insert a facility at the end of a Route List.
<subvalue>
This attribute specifies the route that you are adding to the routes list. You may add: A line OID A trunk OID A span OID A trunk group key Digits a service, such as TestTone100, or TestTone102 (see Test Tone Maintenance on page 663.) Changed Number Announcement ("CNASvc", see Change Number Announcement on page 211.) Automatic Number Announcement ("ANASvc", see Automatic Number Announcement on page 665.
527
Route Lists
CarrierRouteList IXC routes 1 SSP1 LNPRouteList LNP1 routes 1 trunk-0 NANPRouteList Test1 routes 1 9724800031 NANPRouteList TestTone102 routes 1 Test102
528
Route Lists
Removing a Route from a Route List deleteFrom <routeListType> <key> routes <subkey>
Use the Generic CLI deleteFrom command to add a route from a Route List. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> <routeListType> Description
<subkey>
This is the index in the route list of the route you want to remove.
529
Subscribers
Subscribers
A subscriber is a person or a company receiving service from the switch. A subscriber is distinguished by its connecting facility, so we often speak of POTS subscribers, GR-303 subscribers, IP subscribers, and so on. A Subscriber has the following attributes:
attribute key value subscribers DN, a 10-digit DN even if the subscriber has 7-digit dialing
NOTE: To provision a voice mail system (VMS), use the provisioned routing number or the pilotLDN in this field. pin lastName firstName restrict 4-digit personal identification number. Internal value, not available in current release subscribers last name subscribers first name This attribute defines the restrictions on a subscriber. For a single restriction, enter its hexadecimal value (listed below). For multiple restrictions, add the hexadecimal values together and enter the total. See Using Hexadecimal on page 741. Extended Area The subscriber can place calls to nearby exchanges, but these calls are routed using PIC2 (the intraLATA carrier) and billed as intraLATA, hexadecimal value 2 IntraLATA Toll The subscriber cannot place calls to intraLATA exchanges that require a toll, hexadecimal value 4 InterLATA Toll The subscriber cannot place calls to interLATA exchanges that require a toll, hexadecimal value 8 International The subscriber cannot place calls to international exchanges, hexadecimal value 10
530
Subscribers
value NPA 900 The subscriber cannot place 1-900 pay-per-call calls, hexadecimal value 20 NXX 976 The subscriber cannot place 1-976 pay-per-call calls, hexadecimal value 40 NPA 500 The subscriber cannot place 1-500 pay-per-call calls, hexadecimal value 80 NPA 700 The subscriber cannot place 1-700 pay-per-call calls, hexadecimal value 100 NO PIC2 The subscriber must dial the CAC (101XXXX) to place calls to intraLATA exchanges that require a toll, hexadecimal value 200 NO SCREEN The originator screening is bypassed and the call is processed on dialed digits and CAC, hexadecimal value 400 Soft DialTone The subscriber can only dial 911 and 611 calls, hexadecimal value 800 DA TO PIC2 The subscribers DA calls (411 only) go to PIC2, the intraLATA carrier, hexadecimal value. 1000 Collect or Third Party Calls The subscriber cannot make collect or third party calls, hexadecimal value 2000
NOTE: Only one of NO Qos, QoS If COPS Up, or Qos Must can be set for a given subscriber.
QoS Must For IP subscribers (SIP and MGCP) provisioned as Access Subscriber: the subscriber needs successful gate negotiation for their call to proceed, which implies that COPS needs to be up. hexadecimal value 4000 No QoS For IP subscribers (SIP and MGCP) provisioned as Access Subscriber: the subscriber does not need gate negotiation for their call processing. hexadecimal value 10000 QoS If COPS Up For IP subscribers (SIP and MGCP) provisioned as Access Subscriber: gate negotiation will only occur if COPS is up (if gate negotiation fails, the call will not proceed). The call will proceed if COPS is down. hexadecimal value 8000
531
Subscribers
attribute subscribedServices
value This attribute defines the services for a subscriber. For a single service, enter its hexadecimal value (listed below). For multiple services, add the hexadecimal values together and enter the total. See Using Hexadecimal on page 741. NOTE: The following services are inherited by OPX Subscribers from the Primary Subscriber: Call Forwarding Call Forwarding Busy Call Forwarding Do Not Answer Call Forwarding Fixed Caller ID Blocking Caller ID Delivery Caller ID Unblocking Calling Name Delivery Enhanced Call Forwarding Do No Answer MWI Options Remote Call Forwarding Activation Revertive call Selective Call Forwarding NOTE: The following services can not be assigned to a Primary Subscriber with an OPX facility: Call Back Call Block Call Reject Call Return Call Transfer Call Waiting Call Waiting Caller ID Priority Call Secondary DN Selective Call Acceptance Speed Dial Three-Way Warm Line
532
Subscribers
Hex Value 4 2
Definition Displays the telephone number of an incoming call and posts the date and time of the call. Blocks the subscribers number (Caller ID) delivery on outgoing calls. Also allows the subscriber to use Caller ID Unblock.
NOTE: A similar feature can be used on a per-call-basis. CALLER_ID_UNBLOCK CALLING_NAME CALL_BACK 100 200 Allows the subscriber to remove the restriction of CALLER_ID_BLOCK for one call. Displays the name of an incoming caller. Call Back is an outgoing call management feature that allows the subscriber to make a call to the last DN called. To activate Call Back, the subscriber, after reaching a DN, hangs up, and enters feature access code *66. Once Call Back activates, the busy/idle status of the called and calling lines is checked periodically until call setup is attempted or a timeout occurs. When both lines are idle, the calling party hears a special ring. When the caller picks up the set, the called partys line rings. If the called DN is busy, the subscriber does not hear a busy signal, but is notified by a tone, after which automatic processing of the call continues for up to 30 minutes or until the DN is idle. CALL_BLOCK 20000 Call Block allows the subscriber to create a reject list of directory numbers (DNs). Calls from these DNs receive a fast busy signal and the subscribers telephone does not ring. Subscribers are billed for Call Block on a subscription basis; a flat, monthly rate. Allows the subscriber to forward all incoming calls to another number. This feature is also known as CLASS feature Call Forwarding Variable. Allows the subscriber to forward incoming calls when their number is busy.
CALL_FORWARDING
40
CALL_FORWARD_BUSY
400
533
Subscribers
Definition Provisions a fixed call forwarding number for a subscriber. A fixed call forwarding number allows the subscriber to activate and deactivate call forwarding, but does not allow changing number without calling the service provider.
NOTE: Call Forwarding Fixed can not be provisioned with Call Forwarding. CALL_FORWARD_LOCAL 4000 For subscribers provisioned as Subscriber Access endpoints: Allows subscribers to forward calls on a per-call basis, depending on the access devices settings. The T7000 does not store a call forwarding number. CALL_FORWARD_NOANS 800 Allows subscribers to forward incoming calls when they are not available to answer. To set the number of rings before forwarding, see numberOfCFDRings on page 542 Allows subscribers to reject calls from people who have Caller ID Blocking on their telephone. This service is an incoming call management feature that allows the subscriber to place a call to the number of the last call that was received. To turn on Call Return the subscriber presses *69 and the switch plays back the last incoming calls DN. The subscriber presses 1 to complete the call. This feature includes Recall Block to Private, it does not return calls on calling numbers with blocked Caller ID. If the called DN is busy, the subscriber does not hear a busy signal, but is notified by an announcement, after which automatic processing of the call continues for up to 30 minutes or until the DN is idle. CALL_TRANSFER CALL_WAITING 20 1 Allows the subscriber to transfer a call to another number. Alerts the subscriber to a second incoming call and allows the subscriber to switch between the calls. Also, allows the subscriber to use cancel call waiting. Displays the name and number of a second incoming call.
CALL_REJECT CALL_RETURN
80 8000
CALL_WAITING_CALLER_ID
1000
534
Subscribers
Definition Allows the subscriber to set following: the number of rings (2-9) before call forwarding activates the forward-to destination number Enhanced Call Forwarding No Answer and Call Forwarding No Answer are exclusive, only assign one of these services. For instance, if the Enhanced Call Forwarding No Answer Service is enabled, then disable Call Forwarding No Answer.
PRIORITY_CALL
200000
This service allows the subscriber to create and edit a screening list and assign a distinctive ring to the DNs in the list. Incoming calls from calling parties in the screening list are identified to the subscriber by the distinctive ring. Or, if a subscriber is engaged in conversation and a call from one of the designated DNs arrives, a distinctive tone accompanies the incoming call. Calls from all other DNs ring normally. Subscribers who subscribe to any or all of the call forwarding services may add Remote Activation. This feature provides a dedicated DN on the switch that can be used for remote activation. Subscriber directly call to this remote activation DN from any location. Calls to this number are answered with a tone. The subscriber then dials the home DN and a security code from the remActCFSecurityCode field. If the security code matches the provisioned code in the Subscriber window, a confirmation tone is returned. The subscriber proceeds through the call forwarding activation/deactivation procedure as if dialing from home.
REMOTE_CALL_FWD_ACTIVATION
40000
REVERTIVE_CALL
400000 0
This feature allows the subscriber to set up a talk path with other telephones on a single line. The subscriber dials their own DN, listens for a confirmation tone and hangs up to allow all telephones on the line to ring. Multiple telephones can go off hook and talk until all telephones hang up. This feature is also called Barn Service or Home Intercom. This service allows the subscriber to receive incoming calls only from a specified list of up to 10 numbers. An incoming call from a DN that is not on the Selective Call Acceptance (SCA) list routes to an announcement stating that the called party will not receive the call. For example, subscribers who do not want to be interrupted by unwanted calls but want to receive important calls. The SCA subscriber does not receive notification when a call is rejected.
SELECTIVE_CALL_ACCEPTANCE
80000
535
Subscribers
Definition This service allows subscribers to forward calls from telephone numbers identified on their Selective Call Forwarding list (up to 10 DNs) to another DN. When the Selective Call Forwarding feature has been activated, only incoming calls that appear on the Selective Call Forwarding List are forwarded to the remote location. Allows the subscriber to dial frequently-called DNs using a two-digit code (speed dial number). The subscriber has a list of 30 speed dial numbers. The subscriber can have both SPEED_DIAL8 and SPEED_DIAL30 for a total of 38 speed dial numbers.
SPEED_DIAL30
800000
SPEED_DIAL8
400000
Allows the subscriber to dial frequently-called DNs using a one-digit code (speed dial number). The subscriber has a list of 8 speed dial numbers. Routes all calls to the subscriber with a presentation of Unavailable, Unknown or Out of Area to an announcement prior to termination. The Central Office TRIGGER_ON_RESTRICTED option allows the service to be triggered for calls with a presentation of restricted, private or anonymous (see tmsOptions on page 385). After the announcement is played, the caller must dial the digit mentioned in the announcement in order for the call to proceed. Otherwise, the call is terminated after a timer expires. See tmsDigit on page 385 and tmsOptions on page 385.
TELEMARKETER_SCREENING
10
Tip
The Telemarketer Screening feature requires a software license from Taqua. For software licensing information, e-mail Taqua Marketing at simplify@taqua.com.
THREE_WAY WARM_LINE
8 100000 0
Allows a third person to join in a two-party call. The switch dials a pre-determined DN from a subscribers line automatically if the receiver is left off-hook for 0 to 30 seconds. The automatically dialed number can be any telephone number or digits routed by the switch, (911 is allowed, but not recommended). Warm Line becomes Hot Line service when you set the Warm Line timer to 0. You can use Hot Line with a Customer Service DN to have a new resident call your company for telephone service. See warmLineDigitTimeout on page 541 and warmLineForwardDN on page 541.
timezoneOffset
An optional attribute used when the subscriber resides in a different time zone than the switch. The switch applies the value in the timezoneOffset to calculate the local time at the subscribers phone when displaying Caller ID and time. The carrier that handles the subscribers interLATA calls (PIC1) if no interLATA carrier is desired, enter NOPIC.
interLATACarrier
536
Subscribers
The carrier that handles the subscribers intraLATA calls (PIC2), if no intraLATA carrier is desired, enter NOPIC. Home Numbering Plan Area. The subscribers area code. key from screen list: Allowed dialing screening prefixes. key from screen list: Denied dialing screening prefixes. Note: this field is read only. A dynamic bitfield detailing which services are currently being used by the subscriber. If the value of the corresponding bit is set, the service is in use.
CAUTION
Do not modify this attribute unless directed to by Taqua TAC! CALL_WAITING CALLER_ID_BLOCK CALLER_ID THREE_WAY TELEMARKETER_SCREEN CALL_TRANSFER CALL_FORWARDING CALL_REJECT CALLER_ID_UNBLOCK CALLING_NAME CALL_FORWARD_BUSY CALL_FORWARD_NOANS CALL_WAITING_CALLER_ID ENHANCED_CF_NOANS CALL_RETURN SELECTIVE_CALL_FORWARDINGCALL_BLOCK REMOTE_CALL_FWD_ACTIVATION SELECTIVE_CALL_ACCEPTANCE CALL_FORWARD_FIXED PRIORITY_CALL SPEED_DIAL8 SPEED_DIAL30 WARM_LINE CALL_BACK REVERTIVE_CALL OPX_FIRST_OFFHK_DIAL OPX_FIRST_OFFHK_ANS OPX_FIRST_SEC_OFFHK
537
Subscribers
rateCenter
name of the rate center this subscriber belongs to, this shows up as the originating rate center for all subscriber calls in the CDRs. Enter NONE for no rate center. Subscribers porting status. Values are: In the beingPorted field, select the appropriate porting status for this subscriber. For details as to how the switch routes ported subscribers, see Routing to a Ported Subscriber on page 715. NOT_BEING_PORTED for all subscribers that are not being ported to another switch and for all subscribers that not being ported from other switches to the switch. The call is terminated to subscribers facility. BEING_PORTED_IN For all subscribers that are being ported into the T7000 from other switches. Flags the switch that it may have to do an LNP dip to find the new number for the subscriber. Calls to the subscriber continue to terminate on the subscribers old switch until the LRN database is updated with the LRN of the local switch. Use this when adding a ported subscriber to the switch or before removing a ported subscriber off of the old switch. BEING_PORTED_OUT For all subscribers that are being ported to another switch. Flags the switch that it may have to do an LNP dip to find the new Location Routing Number for the subscriber. Calls to the subscriber continue to terminate on the local switch until the LRN database is updated with the LRN of the subscribers new switch. If the new switchs LRN is returned, LRN routing is used to forward the call to the subscribers new switch. Prevents Outgoing Signal Customization, and later changes to the facility OID, RDT Name, CRV, or IPTrunkGroup.
beingPorted
Tip
Verify that the LNP database has been updated before deleting subscribers from the switch. See testLnpQuery on page 642.
voiceMailIndicator
serviceProfile
This is the name of the Service Profile for Subscribed AIN Services and/or Account Codes. See Service Profile on page 152, and AcctCodePatternProfile on page 157. If populated, used as the billing number field in CDRs.
billingNumber
538
Subscribers
secondaryDNs
List of Distinctive Ringing numbers and associated alerting profiles. Distinctive Ringing service, also called teen service, allows up to six DNs to be assigned to the same customers line. The subscriber has one outgoing line and the party identification of six incoming lines. The switch creates a route list for each secondary DN with the same route as the primary DN
NOTE: A secondaryDN can not be a Hunt Group Pilot DN or a Start Hunt number
The alerting tone is the tone the switch sends when the secondaryDN is dialed: ALERTING_DEFAULT The default ringing tone on the switch, this tone is always applied to the primary DN. The tone is 2 seconds on and 4 seconds off. (also the default if the parameter is omitted) ALERTING_1 1second on, 1 second off, 1 second on ALERTING_2 0.5 seconds on, 0.5 seconds off, 0.5 seconds on, 0.5 seconds off, 0.5 seconds on ALERTING_3 0.25 seconds on, 0.5 seconds off, 2.25 seconds on ALERTING_4 0.25 seconds on, 0.5 seconds off, 1.5 seconds on, 0.5 seconds off, 0.25 seconds on ALERTING_5 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.5 seconds on ALERTING_3GR506 0.4 seconds on, 0.2 seconds off, 0.4 seconds on, 0.2 seconds off, 0.8 seconds on, 4.0 seconds off remActCFSecurityCode originatingLineType Security Code to remotely activate Call Forward service. Length: 4 - 9 digits Flex ANI - originatingLineType. See Flex ANI Out-Pulsed Information Digits on page 394.
539
Subscribers
lineLoadClass
Line Load Class of Subscriber. Line load control divides subscribers into three separate groups: A the highest priority B secondary priority C tertiary priority The highest priority A group requires communications in emergencies. Subscribers in this group include law enforcement, fire, and rescue personnel. The B and C groups contain the remaining subscribers (businesses and individuals). Typically, group A contains 10% of the subscribers with B and C containing the remaining 90%. During an emergency, use line load control on the C class, or on B and C classes to reduce congestion and allow group A to communicate. See LLControl on page 383,.
540
Subscribers
mwiOptionsvoiceMailSyste mID
Message Waiting Indicator. Controls how the subscriber is alerted to new voice mail messages. Values are" Stutter Provides a stutter tone on the subscribers telephone when the subscriber has new voice mail messages. Stutter_VMWI Provides a stutter tone and Visual Message Waiting Indicator (VMWI) when the subscriber has new voice mail messages. VMWI is a flashing LED or message on a CPE that has VMWI capability. Stutter_VMWI_Ring Provides a stutter tone, VMWI, and an abbreviated ring on the subscribers telephone when the subscriber has new voice mail messages. An abbreviated ring applies if a subscriber is off-hook and receives a message, after the subscriber goes on-hook, then the switch partially rings the telephone before sending stutter and VMWI. VMWI Provides VMWI when the subscriber has new voice mail messages. VMWI is a flashing LED or message on a CPE that has VMWI capability.
NOTE: VMWI is the only valid MWI option for SIP AGW Subscribers.
VMWI_Ring Provides VMWI and an abbreviated ring on the subscribers telephone when the subscriber has new voice mail messages. An abbreviated ring applies if a subscriber is off-hook and receives a message, after the subscriber goes on-hook, then the switch partially rings the telephone before sending stutter and VMWI. Permanent_Stutter Provides a stutter tone on the subscribers telephone when the subscriber has new voice mail messages. It is different from regular stutter because the dial tone stutters until the subscriber enters a digit, goes onhook, or does not enter a digit and the First Digit Timer expires. Permanent_Stutter_VMWI Permanent Stutter and Stutter and VMWI Permanent_Stutter_VMWI_Ring Permanent Stutter and Stutter and VMWI and Abbreviated Ring warmLineDigitTimeout warmLineForwardDN Range: 0 30000 (0 for Hot Line, 1000 to 30000 for Warm Line). The DN called if the receiver is left off-hook for the length of time specified in the warmLineDigitTimeout field.
Tip
You can use Hot Line with a Customer Service DN to have a new resident automatically call your company for telephone service.
541
Subscribers
ftrsProfile
The FTRS profile associated with this subscriber. The switch applies FTRS if the pattern associated with the profile matches the dialed digits. See FTRS on page 223.
NOTE: A subscriber profile takes precedence over an incoming trunk group profile. For example, if a subscriber has a profile assigned and is in a hunt group, the switch uses the subscriber profile. For more information, consult the T7000 Provisioning Guide. maximumCFVCalls The maximum number of calls that can be simultaneously active for the Call Forwarding Variable service. Default: 1 maximumCFDCalls The maximum number of calls that can be simultaneously active for the Call Forwarding No Answer service. Default: 1 maximumCFBCalls The maximum number of calls that can be simultaneously active for the Call Forwarding Busy service. Default: 1 numberOfCFDRings The number of rings (2-9) to allow before the Call Forwarding No Answer service or Voice Mail service forwards the call. Range: 2 9 Default: 3 appServerTG For Enhanced Voice Services or Hosted SIP Gateway Subscribers, this is the name of the SIP Application Server trunk group The 3- or 10-digit ID of SIP Voice Mail System serving the subscriber.
voiceMailSystemID
542
Subscribers
TaquaMailProvisioned
Note: this field is read only. Status of Voice Mail System provisioning for the subscriber. Values are: NOT_APPLICABLE (default) subscriber is not a member of TaquaMail SIP VMS. NO subscriber is a member of TaquaMail SIP VMS, but the server has not yet confirmed the provisioning. YES subscriber is a member of TaquaMail SIP VMS, and the server has confirmed the provisioning. NOTE: When a subscriber is a member of TaquaMail SIP VMS, provisioning is automatically handled by the T7000. The switch sends a request to the TaquaMail VMS to provision a subscriber. When the TaquaMail server succeeds in fulfilling that request, it updates the subscriber record to reflect that provisioning was successful. If the TaquaMailProvisioned field is still 'NO' when a database audit triggers, the switch resends the request to the TaquaMail VMS to provision the subscriber.
The DN associated with an OPX facility. The phone number a caller dials that rings both the primary and the Off-Premises Extension (OPX) phone Type is Bitfield. These options are individually turned on or off by name. See example. FORCE_CALLWAIT_CALLERID set this option if the subscriber has the Call Waiting Caller ID service, and his CPE device does not respond properly with an acknowledgement. USE_DIAL_PULSE set this option for subscribers with dial pulse telephones (also called rotary telephones). The default is to use DTMF dialing
facility
The facility object holds subscriber facility data. See: TDM Facility on page 547 GR303Facility on page 548 MGCP Facility on page 549 SIP Facility on page 550
543
Subscribers
The Generic CLI is used for all Subscriber commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
TDMFacility
GR303Facility
MGCPFacility SIPFacility
544
Subscribers
allowedList deniedList rateCenter beingPorted voiceMailIndicator serviceProfile billingNumber remActCFSecurityCode originatingLineType lineLoadClass mwiOptions warmLineDigitTimeout warmLineForwardDN ftrsProfile maximumCFVCalls maximumCFDCalls maximumCFBCalls numberOfCFDRings appServerTG voiceMailSystemID TaquaMailProvisioned opxPrimaryDN options
Tip
See TDM Facility on page 547, GR303Facility on page 548, MGCP Facility on page 549, and SIP Facility on page 550 for modify facility examples.
facility
545
Subscribers
secondaryDNs
See Adding Secondary DNs to Subscribers on page 557 and Removing Secondary DNs from Subscribers on page 559. Also, seequery Subscriber on page 552, query CFVInfo on page 553, query SCFInfo on page 553, query CFBInfo on page 554, query CFBInfo on page 554, query CFDInfo on page 554, and query CFFInfo on page 555.
create Subscriber 9724800001 Miller Craig 0 201204 WorldComm LuckyDog rc1 TDMFacility Line-01 create Subscriber 9724800037 James Stephen 0 204 WorldComm LuckyDog rc1 GR303Facility AFCUMC1 4 create Subscriber 8174801011 Anderson Paul 0 0 . . . SIPFacility ipgrp1 8174801011 Pa55W0rd modify Subscriber 9724800001 restrict NXX_976 1 destroy Subscriber 9724800001
Prerequisites
Carrier, see Carriers on page 196. Rate center, see Adding a RateCenter on page 412 For GR-303 subscribers, RDT, see createRDT on page 351 For pseudo IP subscribers, see IP Trunk Groups on page 307 For MGCP subscribers, MGCP termination, see MGTermination on page 376.
546
Subscribers
TDM Facility
The TDMfacility object holds subscriber data for TDM facilities.
attribute facilityOID
value Object Identifier of the Line for this TDM facility. Only applies to LTC. Range: 1 - 32 Example: Line-01
The following example creates a subscriber with a TDM facility on the current (LTC) card.
create Subscriber 9724800001 Miller Craig 0 201204 WorldComm LuckyDog rc1 TDMFacility Line-01
The following example modifies a subscribers TDM facility on the current (LTC) card.
query Subscriber 9724800000 facility <5c5b33c> facility...............<5c68fd8> <5c68fd8> TDMFacility facilityOID...Line-0-2-2 modify Subscriber 9724800000 facility TDMFacility Line-0-2-21
547
Subscribers
GR303Facility
The GR303facility object holds subscriber data for GR-303 facilities.
value Name of a previously defined Remote Data Terminal.See GR-303 on page 351. The number of the physical analog line hanging off of the RDT. Range: 0- 2048.
The following example creates a subscriber with a GR303 facility. The ACFUMC1 RDT was previously defined.
create Subscriber 9724800037 James Stephen 0 204 WorldComm LuckyDog rc1 GR303Facility AFCUMC1 4
548
Subscribers
MGCP Facility
The MGCPFacility object holds subscriber data for MGCP facilities.
attribute MGTermination
The following example creates a subscriber with a MGCP facility. The term-1-2 MGTermination was previously defined.
create Subscriber 8174801012 Leaking Rufus . ffd . . . MGCPFacility term-1-2
549
Subscribers
SIP Facility
The SIPFacility object holds subscriber data for SIP facilities.
value For IP subscribers, the name of the IP trunk group For IP subscribers configured as SubscriberAccess SIP endpoints, the username is the subscribers DN For IP subscribers configured as SubscriberAccess SIP endpoints, the password is 0-16-character password The username and password are combined, encrypted, and shared between the switch and the CPE device; and used in the Registration process between the CPE device and the switch. The only time the password visible is when you enter it in the command line!
The following example creates a subscriber with a SIP facility. The IP trunk group and SIP Access Gateway were previously defined.
create Subscriber 9726921839 Paradise Sal . . . . . SIPFacility gw1_ipgrp 9726921839 OnTheRoad
550
Subscribers
The following example modifies a SIPFacility. Note that switch encrypts the password.
query Subscriber 8174802345 facility <609d234> facility...............<60a2638> <60a2638> SIPFacility IPTrunkGroup..."ipgrp1" username......."8174802345" password......."53036b2aafe896a1f8a59654e0f3094e" modify Subscriber 8174802345 facility SIPFacility Usage: modify Subscriber 8174802345 facility SIPFacility [username] [password] <IPTrunkGroup> : Available keys in tIPTrunkGroupDbMgr: ipgrp1 ipgrp10 ipgrp11 modify Subscriber 8174802345 facility SIPFacility ipgrp11 8174802345 Pa55W0rd query Subscriber 8174802345 facility <609d234> facility...............<60f5010> <60f5010> SIPFacility IPTrunkGroup..."ipgrp11" username......."8174802345" password......."2d63fc8b1d3cd85d272e58ef90ec80d3"
<IPTrunkGroup>
551
Subscribers
query Subscriber 9724800002 <5f51560> Subscriber key...................."9724800002" pin....................0 lastName..............."Pennington" firstName.............."Bill" restrict...............(BITFIELD) -> 0 subscribedServices.....(BITFIELD) -> 204 .CALLER_ID .CALLING_NAME timezoneOffset.........0 (0) interLATACarrier......."WorldComm" intraLATACarrier......."WorldComm" homeNPA................"972" allowedList............0 deniedList.............0 serviceInUse...........(BITFIELD) -> 0 rateCenter............."rc1" beingPorted............NOT_BEING_PORTED voiceMailIndicator.....NO_MAIL serviceProfile.........0 billingNumber..........0 secondaryDNs...........0 (0) remActCFSecurityCode...0 originatingLineType....0 (0) lineLoadClass..........C mwiOptions.............Stutter warmLineDigitTimeout...2710 (10000) warmLineForwardDN......0 ftrsProfile............0 maximumCFVCalls........1 (1) maximumCFDCalls........1 (1) maximumCFBCalls........1 (1) numberOfCFDRings.......3 appServerTG............0 voiceMailSystemID......0 TaquaMailProvisioned...NOT_APPLICABLE opxDN..................0
552
Subscribers
query CFVInfo 9724800002 <6d933c0> CFVInfo key.............."9724800002" remoteDN........."9724800010" maxActiveCalls...2 (2) serviceActive....TRUE fwdToVoiceMail...0 (0)
query SCFInfo 9724800002 <6ef4280> SCFInfo key.............."9724800002" remoteDN........."9724800008" maxActiveCalls...1 (1) serviceActive....FALSE fwdToVoiceMail...0 (0)
553
Subscribers
query CFBInfo 9724800002 <6dc2f50> CFBInfo key.............."9724800002" remoteDN........."9724800011" maxActiveCalls...2 (2) serviceActive....TRUE fwdToVoiceMail...0 (0)
query CFDInfo 9724800002 <6ec3cc0> CFDInfo key.............."9724800002" remoteDN........."8724800014" maxActiveCalls...2 (2) serviceActive....TRUE fwdToVoiceMail...0 (0) numberOfRings....4
554
Subscribers
query CFFInfo 9724800002 <6df0eb0> CFFInfo key.............."9724800002" remoteDN........."9724800012" maxActiveCalls...2 (2) serviceActive....TRUE fwdToVoiceMail...0 (0)
555
Subscribers
Tip
Use this command to see which subscribers have speed dial lists provisioned on the switch: queryDbKeys tSpeedDialDbMgr
This command displays the information for an object in the speed dial database.
Syntax <key> Description subscribers directory number
query SdInfo 9724800007 <5f374c0> SdInfo key.................."9724800007" sharingAllowedFlag...(BITFIELD) -> 0 entryList8...........0 (0) sd8Owner............."9724800003" entryList30..........0 (0) sd30Owner............0 query SdInfo 9724800003 <5b53850> SdInfo key.................."9724800003" sharingAllowedFlag...(BITFIELD) -> 1 .SpeedDial8SharingAllowed entryList8...........<5f0e818> <5f0e818> Sd8Array entry_2..."9724800020" entry_3...0 entry_4..."9724800022" entry_5...0 entry_6...0 entry_7...0 entry_8...0 entry_9...0 sd8Owner.............0 entryList30..........0 (0) sd30Owner............0
556
Subscribers
<subkey> <secondaryDN>
[alertingPattern] Optional Alerting Pattern. Values are: ALERTING_DEFAULT (default) The default ringing tone on the switch, this tone is always applied to the primary DN. The tone is 2 seconds on and 4 seconds off. ALERTING_1 1second on, 1 second off, 1 second on. ALERTING_2 0.5 seconds on, 0.5 seconds off, 0.5 seconds on, 0.5 seconds off, 0.5 seconds on. ALERTING_3 0.25 seconds on, 0.5 seconds off, 2.25 seconds on. ALERTING_4 0.25 seconds on, 0.5 seconds off, 1.5 seconds on, 0.5 seconds off, 0.25 seconds on ALERTING_5 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.25 seconds on, 0.25 seconds off, 0.5 seconds on ALERTING_3GR506 0.4 seconds on, 0.2 seconds off, 0.4 seconds on, 0.2 seconds off, 0.8 seconds on, 4.0 seconds off
557
Subscribers
The following example adds two secondary DNs to the same subscriber. Note that the 1st command does not specify an alerting pattern. After the two secondaryDNs have been added, the subscriber is queried to confirm the changes.
insertInto Subscriber 9724800010 secondaryDNs 9724801010 DirectoryNumberEntry 9724801010 <done> insertInto Subscriber 9724800010 secondaryDNs 9724801011 DirectoryNumberEntry 9724801011 ALERTING_3 <done> query Subscriber 9724800010 secondaryDNs <5bf19e8> secondaryDNs...........<5ec4810> <5ec4810> SecondDNList (2 items) -> <5ec35a0> DirectoryNumberEntry numberString....."9724801010" cadenceProfile...ALERTING_DEFAULT <5ee23f8> DirectoryNumberEntry numberString....."9724801011" cadenceProfile...ALERTING_3
See Using Generic CLI Commands on page 6
558
Subscribers
The following example builds on the example in Adding Secondary DNs to Subscribers, and removes the second entry from the secondaryDNs list. After the secondaryDN has been removed, the subscriber is queried to confirm the changes.
deleteFrom Subscriber 9724800010 secondaryDNs 9724801011 <done> query Subscriber 9724800010 secondaryDNs <5bf19e8> secondaryDNs...........<5ec4810> <5ec4810> SecondDNList (1 items) -> <5ec35a0> DirectoryNumberEntry numberString....."9724801010" cadenceProfile...ALERTING_DEFAULT
See Using Generic CLI Commands on page 6
559
Subscribers
FXO protocol Bi-directional Loopstart signaling type Assigned a pilotLDN (for Hunt Groups only).
The service code (for example *83) that subscribers use to access voice mail from their telephone (see serviceCodes on page 382). Route list to the VMS and add the trunk group to the route list (see Route Lists on page 514). Add a subscriber, identifying the subscriber as the VMS, and use a provisioned routing number or the pilotLDN in the subscriber phone number field (see Subscribers on page 530). Provision the voice mail interface (see SMDIParms on page 587).
560
Subscribers
Prerequisites
Subscriber with voice mail, see Subscribers on page 530
deactivateSubVM 9724800000
561
Subscribers
activateCfv
activateCfv <baseDN> <remoteDN> <maxActiveCalls>
This command activates call forwarding variable. Call forwarding variable redirects calls intended for the subscribers number to another number allows the subscriber to change the number.
NOTE: Call forward variable can not be activated when call forward fixed is active
Description
NOTE: Call forward variable can not be activated on Network Gateway or Access Gateway subscribers. <remoteDN> directory number where call will forward.
NOTE: the switch does not support call forwarding variable to OPX subscribers <maxActiveCalls> maximum number of active calls that can be forwarded at the same time Range: 1 - 99
Prerequisites
Subscriber with call forwarding, see Subscribers on page 530
Prerequisites
Subscriber with call forwarding variable, see activateCfv on page 562
Syntax <baseDN> subscribers DN Description
deactivateCfv 9726785397
562
Subscribers
activateCfb
activateCfb <baseDN> <remoteDN> <maxActiveCalls>
This command activates call forwarding busy. Call forwarding busy allows the subscriber to forward calls to another number when the subscriber is using the telephone.
Syntax <baseDN> subscribers DN Description
NOTE: Call forward busy can not be activated on Network Gateway or Access Gateway subscribers. <remoteDN> directory number where call will forward
NOTE: the switch does not support call forwarding busy to OPX subscribers <maxActiveCalls> maximum number of active calls that can be forwarded at the same time Range: 1 - 99
Prerequisites
Subscriber with call forwarding busy, see Subscribers on page 530
Prerequisites
Subscriber with call forwarding busy, see activateCfb on page 563
deactivateCfb 9726785397
563
Subscribers
activateCfd
activateCfd <baseDN> <remoteDN> <maxActiveCalls> [numberOfRings]
This command activates call forwarding dont answer. Call forward dont answer redirects calls intended for the subscribers number to another number when the telephone rings and is not answered.
Syntax <baseDN> subscribers DN Description
NOTE: Call forward dont answer can not be activated on Network Gateway or Access Gateway subscribers. <remoteDN> directory number where call will forward
NOTE: the switch does not support call forwarding to OPX subscribers <maxActiveCalls> maximum number of active calls that can be forwarded at the same time Range: 1 - 99 [<numberOfRings] Optional maximum number of rings before call is not answered Range: 2 - 9 Default: 3
Prerequisites
Subscriber with call forwarding dont answer, see Subscribers on page 530
Prerequisites
Subscriber with call forwarding dont answer, see activateCfd on page 564
deactivateCfd 9726785397
564
Subscribers
activateCff
activateCff <baseDN> <remoteDN> <maxActiveCalls>
This command activates call forwarding fixed on a subscriber. Call forwarding fixed allows the subscriber to activate and deactivate call forwarding, but does not allow changing number without calling the service provider.
NOTE: Call forward fixed can not be activated when call forward variable is active
Description
NOTE: Call forward fixed can not be activated on Network Gateway or Access Gateway subscribers. <remoteDN> directory DN where call will forward
NOTE: the switch does not support call forwarding to OPX subscribers/ <maxActiveCalls> maximum number of active calls that can be forwarded at the same time Range: 1 - 99
Prerequisites
Subscriber with call forwarding, see Subscribers on page 530
565
Subscribers
Prerequisites
Subscriber with call forwarding, see Subscribers on page 530
566
Subscribers
assignCff
assignCff <baseDN> <remoteDN> <maxActiveCalls>
This command modifies the remote DN and/or maxActuveCalls to a subscriber with call forwarding fixed.
NOTE: This command does not active call forward fixed on a subscriber. See activateCff on page 565.
NOTE: the switch does not support call forwarding to OPX subscribers/ <maxActiveCalls> new maximum number of active calls that can be forwarded at the same time
Prerequisites
Subscriber with call forwarding fixed, see Subscribers on page 530 assignCff 9726785000 9726920900 4
removeCff
removeCff <baseDN>
This command removes call forwarding fixed from a subscriber. If call forward fixed was active, it deactivates the service, and removes the call forward fixed information from the call forward fixed database.
Syntax <baseDN> subscribers DN Description
Prerequisites
Subscriber with call forwarding, see Subscribers on page 530
removeCff 9726785000
567
Subscribers
activateSCF
activateSCF <baseDN> <remoteDN>
This command activates selective call forwarding on a subscriber and sets the state to ON if there is at least one screen list entry; otherwise the state is set to OFF.
See Screen Lists on page 415. Syntax <baseDN> subscribers DN Description
NOTE: OPX subscribers can not activate selective call forwarding. <remoteDN> directory number where call will forward
Prerequisites
Subscriber with selective call forwarding, see Subscribers on page 530, or setSubCOS on page 576 Subscriber with an SCFscreen list, see assignSCF on page 569.
Prerequisites
Subscriber with selective call forwarding, see activateSCF on page 568 Subscriber with a screen list, See Screen Lists on page 415.
deactivateSCF 9723201000
568
Subscribers
assignSCF
assignSCF <baseDN> <remoteDN>
This command assigns selective call forwarding on a subscriber and sets the state to OFF.
Syntax <baseDN> <remoteDN> subscribers DN directory number where call will forward Description
Prerequisites
Subscriber with selective call forwarding, see Subscribers on page 530, or setSubCOS on page 576
removeSCF
removeSCF <baseDN
This command removes selective call forwarding from a subscriber.
Syntax <baseDN> Description subscribers number
Prerequisites
Subscriber with selective call forwarding, see Subscribers on page 530, or setSubCOS on page 576
removeSCF 9723201000
569
Subscribers
RcfInfo
RcfInfo objects are used to provision Remote Call Forwarding. Remote Call Forwarding allows all calls to a subscribers number to be permanently forwarded, through the Direct Distance Dialing network, to a remote number. Remote Call Forwarding is similar to call forwarding variable, but differs in the following ways:
The forwarding is always activated. No physical telephone is associated with the remote call forwarding base DN. The subscriber Base DN provides billing information and routes the forwarded call over the correct carrier. CLASS and custom calling services are not assigned to the subscriber. Simultaneous calls may be active between the base switching office and the remote call forwarding remote DN. The remote DN should be associated with a type of hunting arrangement, if more than one simultaneous call is allowed. The forwarded-to number cannot be changed by the subscriber.
NOTE: Subscriber must be a pseudo-subscriber (i.e., the subscriber can not have a facility associated with it) remoteDN numActiveCalls numAllowedCalls directory number where call will forward Note: this field is read only. The number of currently active calls to this DN number of calls simultaneously active (1-N) in decimal format Range: 1 - 99 Default: 1 rcfActivated Values are: True (default) Remote Call Forwarding Service is active. False Remote Call Forwarding Service is not active.
570
Subscribers
The the Generic CLI is used for all RcfInfo commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
key
remoteDN
numAllowedCalls
NOTE: An RcfInfo object cannot be deleted while calls are still active.
Prerequisites
Carrier, see Carriers on page 196. Subscriber, see Subscribers on page 530
571
Subscribers
setSdEntry
setSdEntry <DN> <entry> [digits]
This command allows adding, replacing, and clearing single entries in a subscribers speed list database. To clear an entry, omit the digits parameter.
Syntax <DN> <entry> subscribers DN speed dial code Range: 2 - 9, or 20 - 49 [digits] the directory number assigned to the speed dial code. Description
Prerequisites
Subscriber, see Subscribers on page 530 Speed dial 8 or speed dial 30 service, see setSubCOS on page 576.
deleteSdInfo
deleteSdInfo DN
This command deletes all information in the speed dial database for the specified DN. This includes both Speed Dial 8 and Speed Dial 30 lists.
Syntax DN Description DN associated with speed dial code
Prerequisites
Subscriber, see Subscribers on page 530 Speed dial 8 or speed dial 30 service, see setSubCOS on page 576. Speed Dial entry, see setSdEntry on page 572.
deleteSdInfo 9724800000
572
Subscribers
clearSdList
clearSdList DN Type
This command deletes all entries from a speed dial list, but not the list itself.
Syntax DN Type subscribers DN 8 or 30, depending on whether the speed dial code is a one(8) or two-digit code (30) Description
Prerequisites
Subscriber, see Subscribers on page 530 Speed dial 8 or speed dial 30 service, see setSubCOS on page 576. Speed Dial entry, see setSdEntry on page 572.
clearSdList 9724800001 30
Prerequisites
Subscriber, see Subscribers on page 530 Speed dial 8 or speed dial 30 service, see setSubCOS on page 576. Speed Dial entry, see setSdEntry on page 572.and see setSdSharingAllowedFlag on
page 573. Syntax DN Type status subscribers DN 8 or 30, depending on whether the speed dial code is a one- (8) or two-digit code (30) ON sharing OFF no sharing Description
setSDSharingAllowedFlag 9724800001 8 ON
573
Subscribers
shareSdList
shareSdList ownerDN readerDN Type
This command enables speed dial list sharing within a subscribers list.
NOTE: A subscriber may only share a speed dial list with one subscriber at a time. If a subscriber is already sharing a list with one person and begins sharing with another, the first sharing partner will be automatically removed from the subscribers sharing list.
Description sharer of the speed dial list who is not the owner 8 or 30, depending on whether the speed dial code is a one- (8) or two-digit code (30)
Prerequisites
Subscriber, see Subscribers on page 530 Speed dial 8 or speed dial 30 service, see setSubCOS on page 576. Speed Dial entry, see setSdEntry on page 572.and see setSdSharingAllowedFlag on
page 573.
574
Subscribers
Prerequisites
Subscriber, see Subscribers on page 530 Speed dial 8 or speed dial 30 service, see setSubCOS on page 576. Speed dial entry, see setSdEntry on page 572. Shared speed dial list, see setSdSharingAllowedFlag on page 573.
Syntax readerDN Type Description sharer of the speed dial list who is not the owner 8 or 30, depending on whether the speed dial code is a one- (8) or two-digit code (30)
removeSdListShare 9724800004 8
575
Subscribers
setSubCOS
setSubCOS <key> <services>
Tip
To view a subscribers current services, use the Generic CLI query command on the Subscriber object.
This command changes a subscribers services. For a single service, enter its hexadecimal value. For multiple services, add the hexadecimal values together and enter the total. See Using Hexadecimal on page 741.
Syntax <key> <service> subscribers DN (number) see subscribedServices on page 532 for a list of services Service
See Subscribers
on page 530.
Prerequisites
Subscriber, see Subscribers on page 530
setSubRestrict
Tip
To view a subscribers current restrictions, use the
Prerequisites
Subscriber, see Subscribers on page 530
setSubRestrict 9724800000 80
576
Substitution
Substitution
A substitution group is a set of the same type of front cards with one substitution manager. A PIC or PIC2 card does not require any special hardware to be a substitution manager. Other types of cards require a rear substitution card: Front Card
LTC TIC TIC TIC TIC2 TIC2 BIC PIC PIC2
Rear Card
LTS TIIS TIIS2 TIIS2-Test TIIS2 TIIS2-Test DIIS
FEI, FEI2a FEIb, FEI2
a. A PIC can only use two of a FEI2s three Fast Ethernet Interfaces. b. Taqua recommends only pairing the PIC2-400 with an FEI. Also, the substitution manager in a PIC2 substitution group cannot have fewer FE Interfaces than any service card in that group.
The LTS is a specialized rear card that can only function as a substitution card. The TIIS, TIIS2, TIIS2-Test and DIIS rear cards are dual purpose cards that can function either as input/output cards, or as substitution cards. Configure these cards by inserting a jumper card into the Dual In-line Memory Module slot on the card. The substitution manager provides redundancy for the substitution group. If a card in a substitution group fails, then the substitution manager substitutes for the failed card. See the T7000 Provisioning Guide for rules regarding substitution.
577
Substitution
All substitution provisioning is carried out with the Generic CLI, see Using Generic
CLI Commands on page 6.
578
Substitution
key
NOTE: Unlike many other objects, in a substitution group, the key is not a name, but the card number of the substituting manager card.
create SubstitutionGroup 5
create SubstitutionGroup 2 query SubstitutionGroup 2 <52d2b40> SubstitutionGroup key............2 (2) serviceCards...<52d2ae0> <52d2ae0> ServiceCardList valType......Unknown collection...List (0 items) -> sparedCard.....0 (0) destroy SubstitutionGroup 2 query SubstitutionGroup 2 Database item not found Existing keys:
579
Substitution
Adding a Card To a Substitution Group insertInto SubstitutionGroup <key> serviceCards <subkey> ServiceCardItem <serviceCard>
The Generic CLI insertInto command adds a card to a SubstitutionGroups serviceCards list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description The name of the substitution group. Remember, unlike other objects, the name of the substitution group is the card number of the substitution manager. <subkey> This is the index in the service card list where you want to enter the new card.
Tip
Use a index of 1 to insert a service card at the start of a serviceCards List. Use a index of -1 to insert a service card at the end of the serviceCards List.
<serviceCard>
The slot number of the card being added to substitution group Range: 1-20
Prerequisites
Substitution group, see Creating a Substitution Group on page 579.
580
Substitution
create
creates a Substitution Group with card 1 as the substitution manager, adds card 2 as the 1st service card in the Substituting Group, checks the status of the substitution group.
SubstitutionGroup 1
insertInto SubstitutionGroup 1 serviceCards 1 ServiceCardItem 2 query SubstitutionGroup 1 <50c9e40> SubstitutionGroup key............1 (1) serviceCards...<50c9b30> <50c9b30> ServiceCardList valType......Unknown collection...List (1 items) -> (1) <50c9c40> ServiceCardItem card.....................2 (2) maxSwitchbackCount.......0 (0) currentSwitchbackCount...0 (0) sparedCard.....0 (0)
581
Substitution
Removing a Card From a Substitution Group deleteFrom SubstitutionGroup <key> serviceCards <SubKey>
The Generic CLI deleteFrom command removes a card from a SubstitutionGroups serviceCards list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description The name of the substation group. Range: 1-20 <subKey> The index in the Service Card List oft the card being removed from the substitution group Range: 1-20
checks the status of the substitution group. There are two service cards in this substitution group: card 2 (the 1st entry in the Service Card List) and card 6 (the 2nd entry in the Service Card List). removes card 2 from the substitution group. Note that the card to be removed is specified by its position in the Service Card List, not by its card number! checks the status of the substitution group to confirm that only card 6 remains in the substitution group. Note that after removing card 2, card 6 has moved up to position 1 in the Service Card List.
582
Substitution
query SubstitutionGroup 1 <32b1fc0> SubstitutionGroup key............1 (1) serviceCards...<32b1f60> <32b1f60> ServiceCardList valType......Unknown collection...List (2 items) -> (1) <51c85a0> ServiceCardItem card.....................2 (2) maxSwitchbackCount.......0 (0) currentSwitchbackCount...0 (0) (2) <51ccc30> ServiceCardItem card.....................6 (6) maxSwitchbackCount.......0 (0) currentSwitchbackCount...0 (0) sparedCard.....0 (0) deleteFrom SubstitutionGroup 1 serviceCards 1 query SubstitutionGroup 1 <32b1fc0> SubstitutionGroup key............1 (1) serviceCards...<32b1f60> <32b1f60> ServiceCardList valType......Unknown collection...List (1 items) -> (1) <51ccc30> ServiceCardItem card.....................6 (6) maxSwitchbackCount.......0 (0) currentSwitchbackCount...0 (0) sparedCard.....0 (0)
Prerequisites
Substitution card in a group, see Adding a Card To a Substitution Group on page 580.
583
Substitution
Tip
Many users prefer to manually switch back cards during the maintenance window. See swact on page 626.
This command enables one revertive switchback of a service card. Revertive switchback occurs when the formerly-failed service card reboots: the substitution manager automatically switches its activity back to the service card
Description
NOTE: Once a card has switched back you must manually reset the switchback count. See disableRevertiveSwact on page 584, or resetSwitchbackCount on page 585
enableRevertiveSwact 3
disableRevertiveSwact 3
584
Substitution
resetSwitchbackCount 3
585
Voice Mail
Voice Mail
The switch communicates with one or more Voice Mail Systems (VMSs) using:
TCAP over an SS7 F-link. Subscribers and callers connect to the VMS over an F-link from the switch to the call answering points on the VMS, TcapMwiParms on page 497 the Simplified Message Desk Interface (SMDI) over an RS-232 serial port. Subscribers and callers connect to the VMS over voice trunks from the switch to the call answering points on the VMS, SMDIParms on page
587
a SIP interface. Subscribers and callers connect to the SIP VMS over a SIP interface from the switch to the SIP VMS, sipVMS on page 593
NOTE: The switch does not support Generic Data Message Transport (GDMT).
586
Voice Mail
SMDIParms
SMDIParms objects are used to connect to a Voice Mail System (VMS) using the Simplified Message Desk Interface (SMDI) protocol over RS-232. Subscribers and callers connect to the VMS over voice trunks from the switch to the call answering points on the VMS. An SMDIParms object has the following attributes:
Attribute key forwardNumberChoice Description Name of the Message Storage and Retrieval (MRS) system FIRST_FORWARDING_NUMBER the original called number is sent over the SMDI link in the call history data LAST_FORWARDING_NUMBER (default) the last forwarding number is sent over the SMDI link in the call history data MessageWaitingIndicator Control Yes (default) the SMDI link controls the Message Waiting Indicator (MWI) to identify that a message is awaiting the subscriber No the SMDI link does not control the MWI and an error message is returned to the VMS tcapMSRID TCAP Message Storage and Retrieval Identifier (MSRID) uniquely identifies each VMS providing TCAP MWI Must be 10 digits long Range: 0000000001-9999999999. callHistoryDelayLimit number of seconds the switch waits before deleting/not sending a call history record Range: 2-6 Default: 4 servingGroups cardNumberOfRS232Port name of the CAS trunk group or hunt group interfacing with the VMS rear card number to which the SMDI connects using the RS232 port Range: 1 - 20
587
Voice Mail
Attribute baudRate
Description The speed of the connection between the voice mail system and the switch. This must match the baud rate set on the VMS itself. NOTE: The switch uses 1 start bit, 7data bits, an even parity bit, and 1 stop bit.
CAUTION
Software flow control tends to cause problems above 9600 baud, so limit communications speed to 9600 baud. 1200 2400 4800 9600 (default) 14400 19200 28800 38400 56000 softwareFlowControl Yes (default) to control the rate of message transmission between the switch and the VMS using XON/XOFF control characters No no software flow control modemDialNumber Optional DN of the VMS. Used to contact the VMS via modem. Length: 7 - 11 digits standard GR283_ISSUE_1 (Default) for a VMS that meets General Requirements (GR)-283, Simplified Message Desk Interface (SMDI), Issue 1 TR283_ISSUE_2 for a VMS that meets Technical Requirements (TR)-283, Simplified Message Desk Interface (SMDI), Generic Performance Requirements, Issue 2 MWIT1Timer The number of seconds that the switch maintains a copy of information in the original request and associate it with the transaction until the MWI control attempt is completed or the mwiT1Timer expires. Range: 2-6 Default: 4
588
Voice Mail
Attribute defaultMailboxNPA
Description Optional NPA added to 7-digit calls or that replaces the existing NPA in 10-digit calls. Length: 3 digits The number of digits used by the switch to complete the call to the VMS. Value: 7 - 10 digits Default: 7
numMailboxDigits
The the Generic CLI is used for all SMDIParms commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
servingGroups
See Adding a Trunk Group to servingGroups on page 592, and Removing a Trunk
Group from servingGroups on page 592.
create SMDIParms VMS01 0000000001 19 create SMDIParms VMS02 0000012345 1 LAST_FORWARDING_NUMBER YES
589
Voice Mail
query SMDIParms Zeus ******* SMDI Parms ******* MSR Name: Zeus forwardingNumberChoice: 1 messageWaitingIndicatorControl: 1 MSRID: 001 tcapMSRID: 1234567001 callHistoryDelayLimit: 4 servingGroup: 0 cardNumberOfRS232Port: 1 baudRate: 9600 softwareFlowControl: 1 modemDialNumber: (null) mwiT1Timer: 4 standard is GR283_ISSUE_1
590
Voice Mail
Set the trunk groups attributes: FXO protocol, bi-directional, loopstart signaling type, assigned a pilotLDN (for Hunt Groups only), see Route Lists on page 514. Service code that subscribers use to access voice mail from their telephone, see
serviceCodes on page 382
Route list to the VMS, see Route Lists on page 514 Trunk group to the route list, see Adding a Route to a Route List on page 527 Subscriber, identifying the subscriber as the VMS, and use a provisioned routing number or the pilotLDN in the subscriber phone number field, see Subscribers on
page 530
Action Provision an SS7 trunk group to connect to the VMS and add trunks to the trunk group, see Route Lists on page 514 Provision the service code, for example *83, that subscribers use to access voice mail from their telephone, see serviceCodes on page 382 Provision a route list to the VMS and add the trunk group to the route list, see Route Lists on page 514 Add the subsystem number to the SCCP on the local node, see Adding SCCP Subsystems to an SCCPNode on page 485 Add a TCAP service with MWI, see TCAPServiceGTT on page 488 and TCAPServicePCSSN on page 492. Assign subscribers voice mail service, see assignSubVM on page 560.
Dependent Commands
By adding VMS, you are making voice mail available to be associated with subscribers, see Subscribers on page 530.
591
Voice Mail
Adding a Trunk Group to servingGroups insertInto SMDIParms <key> servingGroups <subkey> <subvalue>
Use the Generic CLI insertInto command to add a Trunk Group to the servingGroups list. See the insertInto Example on page 18 for a detailed explanation of this command.
Syntax <key> Description
SMDIParms name
This attribute specifies the Trunk Group that you are adding to the servingGroups list. The MSRID for the trunk group in the servingGroups list.
<subkey> <subvalue>
Removing a Trunk Group from servingGroups deleteFrom SMDIParms <key> servingGroups <subkey>
Use the Generic CLI deleteFrom command to add a Trunk Group from the servingGroups list. See the deleteFrom example on page 21 for a detailed explanation of this command.
Syntax <key> Description
SMDIParms name
This is the MSRID of the trunk group in the servingGroups list of the Trunk Group you want to remove.
<subkey>
592
Voice Mail
sipVMS
A sipVMS object connects to the T7000 using IP trunk groups. An sipVMS object has the following attributes:
Attribute key vmsName voiceMailDNOption Description 10-digit DN used to access the SIP VMS name of the SIP voice mail system connected to the switch Choice for RemoteDN or "leave-to number" for calls forwarded to Voice Mail. Values are: SubscriberDN remoteDN servingIpTrkGrp accessDN Name of the serving IP trunk group. DN for retrieving voice messages. Length: 3 - 10 digits. subscriptionOption Option to turn on/off sending SUBSCRIBE to Voice Mail. Values: No (default) Yes subscriptionInterval Refresh interval for sending SUBSCRIBE to Voice Mail. Range: 30 minutes - 4320 minutes (3 days) Default: 60 minutes. subscriptionAudit Run the MWI Subscription Audit on this Voice Mail System. Values are: Disabled Do not run an audit on this subscriber. Enabled Run an audit on this subscriber. Send SUBSCRIB or UNSUBSCRIBE messages as needed. pendingSubscriptionC The number of subscribers checked each audit period. ount Range: 10 - 1000 Default: 100 tcapMSRID TaquaMailAddress MSRID for sending TCAP VM-related messages to subtending nodes. The IP address or name of the TaquaMail server.
TaquaMailPilotProvis Note: this field is read only. ioned Status of provisioning for the voicemail system.
593
Voice Mail
The the Generic CLI is used for all sipVMS commands, see Using Generic CLI Commands on page 6. The required parameters for the create command are:
Dependent Commands
By creating a Voice Mail System, you are making voice mail service available to subscribers.
query sipVMS 9726921910 <2d3c068> sipVMS key........................"9726921910" vmsName...................."sipVMS1" voiceMailDNOption..........SubscriberDN servingIpTrkGrp............"ipgrpVM" accessDN..................."*09" subscriptionOption.........No subscriptionInterval.......3c (60) subscriptionAudit..........Enabled pendingSubscriptionCount...64 (100) tcapMSRID.................."1234567001" TaquaMailAddress...........0
594
Voice Mail
setSubVMI
Tip
The Generic CLU query command shows the status of a subscribers voiceMailIndicator as 0-no mail or 1new mail. See
CAUTION
This command overrides the connecting voice mail systems messaging.
Description the subscribers telephone number ON sets the subscribers CPE to indicate there is new voice mail, including: stutter dial tone, VMWI, and an abbreviated ring. OFF resets the subscribers CPE by removing stutter dial tone and the Voice Mail Waiting Indicator (VMWI).
Prerequisites
VMS attached to the switch, see SMDIParms on page 587 Subscriber with voice mail, see Subscribers on page 530
setSubVMI 9724800001 ON
595
Voice Mail
sendVMWI
sendVMWI <key> <value> [updateFlag]
This command sends a VMWI on or VMWI off message to a subscriber CPE. This command only controls the VMWI and abbreviated ring, and does not affect stutter tone. You can also use it to send a refresh message or immediately send the VMWI message.
Syntax <key> <value> Description the subscribers telephone number ON sends the VMWI on message to the subscribers CPE. OFF sends the VMWI off message to the subscribers CPE. This command does not affect the status of the voiceMailIndicator attribute in the Subscribers object. [updateFlag] R the refresh message updates the subscribers CPEs with the VMWI. This ensures the correct status of a CPE, if the VMWI is lost for any reason. I sends the immediate VMWI on message to the CPE.(default)
Prerequisites
VMS attached to the switch, see SMDIParms on page 587 Subscriber with voice mail, see Subscribers on page 530
sendVMWI 9724800001 ON R
596
Maintenance
Maintenance commands make changes to the T7000 database, its components, or functions of the T7000.
General Maintenance
The following commands are general utility commands:
addTask
Tip
To view all the tasks currently scheduled on the switch, see querySchedule on page 81
Description uniquely identifies a task, may be any string Specify the time a task should start. The start time can be: mo:dd:hh:mm month, day, hour, and minute all specified hh:mm month and day assumed current system month and day, hour and minute are specified. now start time is immediate
<"command param_1...param_n">
Specify the action executed by the scheduler at the start time. This is a CLI command in double quotes. Entered the command as on the command line. Operating system commands, CLI commands, and scripts are valid values.
NOTE: No validation is done for commands. <card number> number of the card on which to perform the task or ALL to perform the task on all cards
Maintenance
597
General Maintenance
Syntax [period]
Description Select period, or default to one time. once The default if no period is entered, task will run once. xxxx User-specified where xxxx is some decimal number of minutes hourly Task runs hourly from the start time. daily Task runs daily from the start time. weekly Task runs weekly from the start time. monthly Task runs monthly from the start time. yearly Task runs yearly from the start time.
598
Maintenance
General Maintenance
removeTask
Tip
To view all of the tasks currently scheduled on the switch, see querySchedule on page 81
removeTask <taskName>
This command removes a task from the scheduler.
Syntax <taskName> Description . The task name of one of the tasks in the scheduler.
Prerequisites
Task, see addTask on page 597
removeTask dbflash
dbFlash
dbFlash [<cardNumber> | <ALL>]
This command saves the provisioned database to flash memory.
Syntax [<cardNumber> | <ALL>] Description without an additional parameter, the command saves the database of the current card to flash memory. cardNumber(1 - 20) Saves the databases of the specified card to flash memory. ALL Saves the databases of all cards to flash memory.
Maintenance
599
General Maintenance
dbFlashSize
dbFlashSize
This command details the flash memory size for each database.
NOTE: The output from the following example has been edited to fit on a single page.
dbFlashSize Flashname: TCAPServices PackedSize: e0 TravSize: 160 NoTravSize: 160 Flashname: SCCPDb PackedSize: e0 TravSize: 160 NoTravSize: 160 Flashname: FTRSPrfileDb PackedSize: e0 TravSize: 160 NoTravSize: 160 Flashname: FTRSPTransDb PackedSize: e0 TravSize: 160 NoTravSize: 160 Flashname: AlarmDefs PackedSize: 2f35 TravSize: 99f0 NoTravSize: 99f0 Flashname: MemoryAuditDb PackedSize: 144 TravSize: 2c0 NoTravSize: 2c0 Total appDb: PackedSize = 7a91 RealSize(references traversed) = 12460 RealSize(references not traversed) = 12460 Flashname: CFVINFO PackedSize: e0 TravSize: 160 NoTravSize: 160 Flashname: CFFINFO PackedSize: e0 TravSize: 160 NoTravSize: 160 Flashname: SPDLINFO PackedSize: e0 TravSize: 160 NoTravSize: 160 Total servDb: PackedSize = 540 RealSize(references traversed) = 840 RealSize(references not traversed) = 840
setDbFlashPadSize 1002000
600
Maintenance
General Maintenance
periodInMilliseconds
Maintenance
601
General Maintenance
utime
Tip
Enter the utime command twice in succession: once to clear the current counts, and again to show the most recent CPU usage.
utime
This command displays a snapshot of the amount of CPU time each process has used since the last time the utime command was executed.
72547873ms (sysclicks=1193) 811819957 [isr] 0 251240871 [maddog] 1 0 initd 2 628062 rpcd 5 0 testd 6 1022369332 memd 7 0 smregd 8 0 xsh 9 0 getty a 12422110 net_datalink b 0 eigwd c 2032648 net_status d 43460 bootp_client e 0 ttyMon f 3340576 telnetd 10 437 environd 11 0 traced 12 0 cat 13 41223 smSubd 14 9008449 Mgmt_Daemon
loadAudio
Tip
Audio files are not replicated databases: be sure to load the audio file on all of the cards in the shelf.
602
Maintenance
General Maintenance
unloadAudio
Tip
Audio files are not replicated databases: be sure to remove the audio file from all of the cards in the shelf.
unloadAudio <name>
This command removes an announcement file from a card on the switch.
CAUTION
Removing announcements may negatively affect operations!
unloadAudio allCircuitsBusy
ls
Tip
Valid devices are 6 (RAM), E (Execute), and F (flash)
ls <dev>
This command lists the contents of the specified device.
Syntax <dev> Description device name, for example: e device e (code versions) f flash 6 device 6
ls f 4420000 4440000 4460000 4480000 4500000
16a 7 0 7 1ea
1 1 1 1 1
1 1 1 1 1
Maintenance
603
General Maintenance
ping
ping <host> [interface]
This command verifies the IP connection to a card or to a computer using the cards or the computers IP address. It sends one ICMP ECHO request packet and waits for a reply.
Syntax <host> Description The IP address of the card or the computer to be verified, in dotted quad form. Optional interface parameter, one of eth0 voip0 voip1 eth0 is valid for all card types, voip0 and voip1 are only valid for a PIC card. Default is eth0.
[interface]
604
Maintenance
General Maintenance
ipconfig
ipconfig
This command shows the IP connections of the switch to other devices and to the OM Server.
IP Configuration Device eth0 BOOTP reply received: True Vendor options = 1 My IP = 10.1.135.250 Host IP = 10.1.135.50 Default Gateway IP = 10.1.135.1 DNS IP = 0.0.0.0 Subnet Mask = 255.255.255.0 Root Path = Lubbock\tic3
ps
This command lists the processes currently running. For each process, the command displays the Process ID (PID), the parent process PID, the process priority, state (numeric), state (symbolic), stack base, stack length, stack margin, timestamp (last time the Pid became RDY), utime (number of ticks the Pid has consumed), and Pid Name).
ps 77:59:57.952 (280797952) <10bca300> 3/70/25% hi(<=3)/lo/sISR (2 hISR) state sbase slen mrgn timstmp utime name 0 0 f 1 Rdy d25ce0 e2c af0 0 39cd05ea [maddog] 1 0 1 d3e818 Rcv d3e7e0 de4 790 184a3a7 1cbed78 initd 2 0 1 d3fc28 Rcv d3fbf0 dcc c04 10bc9215 2242b4 rpcd 5 0 2 da4138 Rcv da4100 d50 c90 a46 19c testd 6 0 e 1 Rdy d509f0 d84 a48 174 58152b4f memd 7 20 0 e69e9c Syn ea4670 b30 ad0 183840b f9 smregd 8 9 3 d27670 Syn 26e97b0 c48 848 b2538dc 7b42 xsh 9 0 2 d6c2c4 Sus d6c290 bb8 7d8 18e4a7b 6f0a getty a 0 0 d8e8f8 Rcv d8e8c0 3de8 39e0 10bca2ff 1d205a4 net_datalink
Maintenance
605
General Maintenance
CAUTION
The forceDbMaster command will briefly disrupt SS7 traffic.
Description cardNumber the number of the card you want to be the dbMaster best uses system criteria to select the best DB Master (non-substitution, fastest, first, lowest card number)
forceDbMaster 2
restoreDb
Tip
Use queryDb on page 83 to list the names of the databases.
606
Maintenance
General Maintenance
<type>
resetHostdProxyDb local hostd proxy db reset for local card only resetHostdProxyDb all hostd proxy db reset for all cards
Maintenance
607
General Maintenance
<UserName> <Password>
<DN>
608
Maintenance
General Maintenance
banner
banner <word> [word...]
Tip
Use banner to denote different phases of a script. See Using Scripts on page 31.
This commands prints messages to the console in large block letters. The command supports word wrap, and it converts alphabetic characters to lower case before printing them. Any character not understood is replaced by a blank
NOTE: The command shell intercept various characters before executing any command. See Command Syntax on page 26.
Syntax
<word>
banner start mtp3 config X X X X XXXX XXXXX XXXX XXXXX X X X X XX X XXX X XXXX XX X X X X X X X X XXXX XXX XXXX X XXX X XXXXX X X XXXXX X X XXXX XXX X X X X X X X X XXX XXXX XXXXX X X
XX XX X X X X X X X X
XXX X XXXX X X X X
Maintenance
609
610
Maintenance
Syntax
traceCalledPty Invalid Number of arguments (0) supplied. Usage: traceCalledPty <CalledParty | off> off Reset the CalledParty Current CalledParty Being traced : None traceCalledPty 9724804001
traceCallingPty 2147658891
Maintenance
611
rover
rover <OriginatingSubscriber> <DialedDigits> [NODIP]
This command implements Taquas Routing Translations Verification (RoVer) feature. RoVer allows a crafts person to place a virtual call between a calling party and a called party and to observe the switch translations used to place the call.
Syntax <OriginatingSubscriber> Description DN of the calling party. RoVer supports any Subscriber DNs assigned to a Line, an FXO trunk group, a SIP Access Gateway trunk group, a G303 RDT and CRV, or an MGCP Termination in the subscriber record. Note that the subscriber DN may or may not be assigned an Application Server trunk group. You can also trace the routing from an incoming Trunk Group. Rover supports subscriber Trunk Groups that use the PRI, DID or FXO protocol. Use the Trunk Group key in place of the Originating Subscriber (see Incoming Trunk Group Call on page 615).
<DialedDigits>
The digits dialed to place the call. Use a comma to separate a service code from the destination digits, or to separate the destination digits from the account code (see Account Code on page 624). RoVer supports seven and ten digit dialing, international dialing, and most services, such as speed dialing (see Speed Dial on page 617), and Account Codes (see Account Code on page 624, Missing Account Code on page 625, and Wrong Account Code on page 625). NOTE, however, Rover is primarily a route verification tool. It does not work with the following originating services: CALEA CID Block Revertive Call
[NODIP]
Optional parameter to handle database dips for 800 calls or Local Number Portability enquiries. Values are: nodip the appropriate database will not be accessed dip (default) the appropriate database will be accessed.
612
Maintenance
RoVer reports the results of the virtual call using the following categories:
Preliminary Information
Collected Digits interDigitTimeout (if applicable) FTRS Translation results (if applicable) See Office Pattern FTRS Translation on page 619 and FTRS Translation, Multiple Routing Attempts on page 620 type of digits collected (if applicable) Origination Address Carrier Destination Address OLI ISUP Originating Line Information Parameter (if applicable) CSI Carrier Selection Information Nature of Address (if applicable) call Type screening results for originator screening results for destination Originating Rate Center (if applicable) routing result (line and trunk or the reason for failure to route)
INFORMATION COLLECTED
SCREENING
ROUTING
NOTE: Rover can not make a virtual call if the subscribers facility is out of service. This applies to physical facilities as well as virtual facilities, such as GR-303, MGCP, or SIP. NOTE: Rover runs until a facility is selected that would normally complete the call. No terminating services (such as Telemarketer Screening, Selective Call Reject or Anonymous Call Reject) are ever triggered by rover.
Maintenance
613
614
Maintenance
Maintenance
615
rover 9724800000 972480001 nodip Route Verification (9724800000 dialing 972480001 - without dip ) Begins: DIGIT COLLECTION... Inter-digit timeout : collected digits-> 972480001 INFORMATION COLLECTED... Origination Address: 9724800000 Carrier: 0333 (WorldComm) Destination Address: 972480001 OLI: 0 CSI: 1 (presubscribed but not input) Nature of Address: 0xfe () SCREENING... Screening for subscriber: (9724800000) Screening on destination: (972480001) Originating Rate Center: rc1 Screening passed: call type: Unknown (15) ROUTING 972480001 ... Routing on digits: (972480001) CM Route Failed, reason: UNABLE_TO_ROUTE (-1), digits: 972480001 Route Verification Complete Route Verification complete for originating facility Line0-1-27
616
Maintenance
Maintenance
617
rover 9724800000 4089731234 nodip Route Verification (9724800000 dialing 4089731234 without dip ) Begins: DIGIT COLLECTION... Digits collected 4089731234, type tenDigitDial INFORMATION COLLECTED... Origination Address: 9724800000 Carrier: 0333 (WorldComm) Destination Address: 4089731234 OLI: 0 CSI: 1 (presubscribed but not input) Nature of Address: 0x3 (National number) SCREENING... Screening for subscriber: (9724800000) Screening on destination: (4089731234) Originating Rate Center: rc1 Screening passed: call type: interLata (2), Carrier: 0333, Screening PCAC from carrier = (null) ROUTING 4089731234 ... Routing on carrier: (0333) CM Route Failed, reason: UNABLE_TO_ROUTE (-1), digits: 4089731234 Route Verification Complete Route Verification complete for originating facility Line0-1-27
618
Maintenance
Maintenance
619
620
Maintenance
Maintenance
621
622
Maintenance
Maintenance
623
624
Maintenance
Maintenance
625
Substitution Maintenance
Substitution Maintenance
swact
swact <fromCard> <toCard>
Swact stands for Switch Activity. This command switches call processing:
from a service card to the substitution manager from the substitution manager back to the service card.
NOTE: Only switch back to the service card after all issues are resolved and the card is restored.
Description the card from which you want to switch the card to which you want to switch
Assume that cards 1 - 3 are in a substitution group and that card 1 is the substitution manager. To manually switch to the substitution manager from card 3 (switchover):
swact 3 1
To manually switch from the substitution manager to 3 (switchback):
swact 1 3
626
Maintenance
restartPRI
restartPRI <TrunkGroupName> <restartClass> [ChannelID]
This command sends a restart command to the trunk(s) in a PRI trunk group.
Syntax <TrunkGroupName> <restartClass> Description name of PRI trunk group "trunk" individual trunk "span" span "all" all trunks in the trunk group [ChannelID] optional trunk/span Object Identifier used when restartClass is either "trunk" or "span". See OID on page 30.
Maintenance
627
Device Maintenance
Device Maintenance
The following commands perform maintenance on cards, spans, trunks, or lines.
remove
remove <oid>
This command causes the facility to be operationally disabled and administratively locked See lock on page 7, and also see disable on page 630.
Syntax <oid> Description Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30.
remove Trunk-23-1-3
restore
restore <oid>
This command causes the facility to be operationally able and administratively unlocked. See unlock on page 7, and also see enable on page 630.
Syntax <oid> Description Object Identifier unique identifier that the switch uses to address each object or circuit. See OID on page 30.
restore Trunk-23-1-3
628
Maintenance
Device Maintenance
busy
busy <oid>
This command causes the facility to be available but not accept additional service requests. Busy is an operational state
CAUTION
This command should only be used by qualified personnel under appropriate circumstances for testing or debugging.
Syntax <oid>
Description The object Identifier of a line, span, or DS-3. See OID on page 30.
Prerequisites
Facility in service.
busy Trunk-23-1-3
unbusy
unbusy oid
This command causes the facility to be available and accept additional service requests. Unbusy is an operational state.
CAUTION
This command should only be used by qualified personnel under appropriate circumstances for testing or debugging.
Syntax <oid>
Description The object Identifier of a line, span, or DS-3. See OID on page 30.
Prerequisites
Facility in busy state, see busy on page 629
unbusy Trunk-23-1-3
Maintenance
629
Device Maintenance
disable
disable oid
This command causes the facility to be unavailable for processing service requests. Disabled is an operational state.
CAUTION
This command should only be used by qualified personnel under appropriate circumstances for testing or debugging.
Prerequisites
Facility in service.
Syntax <oid> Description The object Identifier of a line, span, or DS-3. See OID on page 30.
disable Trunk-23-1-3
enable
enable <oid>
This command causes the facility to be operational and available, but unavailable to process service requests. Enabled is an operational state.
CAUTION
This command should only be used by qualified personnel under appropriate circumstances for testing or debugging.
Syntax <oid>
Description The object Identifier of a line, span, or DS-3. See OID on page 30.
Prerequisites
Facility in service.
enable Trunk-23-1-3
630
Maintenance
Device Maintenance
regMaintConsole regMaintConsole
This command sets the local card as the destination for ISUP circuit maintenance message output. When an ISUP alert is received, the maintenance console prints it.
***** T7000 ISUP Maintenace Alert ***** CIC 1020 -> T18 Expired
deregMaintConsole regMaintConsole
This command disables the local card as the destination for ISUP circuit maintenance command output.
CAUTION
Use caution when resetting line timers.
Syntax <oid>
resetLineTimers Line-1-1-1
Maintenance
631
Device Maintenance
Loss of Signal (LOS) An LOS alarm indicates a loss of T1 signal and transmits what is commonly called a red alarm. Alarm Indication Signal (AIS) An AIS alarm indicates that the near-end T1 framing is lost. This is usually generated by multiplexers or equipment at intermediate cross-connect points on the circuit. An AIS transmits what is commonly called a blue alarm. Remote Alarm Indication (RAI) An RAI is sent by far-end equipment to report that it is not receiving a T1 signal. An RAI transmits what is commonly called a yellow alarm.
The Fault Manager restores the service on the span once the fault condition is remedied.
Syntax [cardNumber] Description Optional card number. If no card number is supplied, the command defaults to the local card.
CAUTION
Disabling Fault Managers automatic response to span alarms can negatively affect operations.
Syntax [cardNumber]
Description Optional card number. If no card number is supplied, the command defaults to the local card.
632
Maintenance
Device Maintenance
test
test <oid>
This command tests an individual span or line. These tests are called DS3 diagnostics, T1 diagnostics or Subscriber Line Interface Card (SLIC) diagnostics, depending on the type of span or line under test.
Test DS3 Diagnostic Description Run the test on a DS-3 span OID. Provides active diagnostic capabilities for the DS3 framerthat determines if the framer chip and associated firmware work properly. Result: [PASSED/FAILED] Report: DS3 Comm Path Test [PASSED/ FAILED] for span X indicates if the communication paths to/from the DS3 framer are open. Run the test on a T-1 span OID. Provides active diagnostic capabilities for the T1 framer that determines if the framer chip and associated firmware work properly. Result: [PASSED/FAILED] Report: T1 Comm Path Test [PASSED/ FAILED] for span X indicates if the communication paths to/from the T1 framer are open. Result: [PASSED/FAILED] Report: T1 Data Path Test [PASSED/ FAILED] for span X (New I/O=False) indicates whether the T1 data path is open. If the external loopback fails, the internal loopback runs to isolate any data path problem. SLIC Diagnostics Run the test on a line OID. The SLIC diagnostic test verifies the proper operation of each of the 32 SLICs by testing each SLIC operating state. Results
Results
T1 Diagnostic
Results
Result: [PASSED/FAILED] Report: SLIC Off-Hook Test [PASSED/ FAILED] for Line X indicates if the SLIC off-hook test passed or failed for the line. Result: [PASSED/FAILED] Report: SLIC Ring and Ring Trip Tests [PASSED/FAILED] for Line X indicates if the SLIC Ring and Ring Trip Tests passed or failed for the line.
Prerequisites
Remove the facility (span or line) from service before running a test, see remove on page 628.
Syntax <oid> Description Line or Span OID. See OID on page 30.
test span-23-1-3
Maintenance
633
Device Maintenance
Tip
See Using Hexadecimal on page 741 to convert decimal to hexadecimal
NOTE: The explanation of this command appears on the next several pages.
Syntax <spanNumber>
Description The zero-based number in hexadecimal of the span to send the signal. The number of spans on a card depends on the card type: Nr. of Spans Card Type LTC TIC ETIC2 BIC PIC 2 16 20 28 0 1 - based decimal 0 - based hexadecimal 2 f 13 1b 0
<timeslot>
The one-based timeslot (trunk) in hexadecimal on the span to send the signal. The number of timeslots on a card depends on the card type: Nr. of Timeslots Card Type LTC TIC ETIC2 BIC PIC 1 - based decimal 48 384 480 672 0 1 - based hexadecimal 30 180 1E0 2A0 0
634
Maintenance
Device Maintenance
Syntax <signalType>
Description The signaling type of the trunk group determines what type of signal to send. The following categorizes the signals within each signaling type. NOTE: The 403 after EANDMS, LST and GST represent the T1-403 specification. E & M signaling (EANDMS) ONHOOK or EANDMS_ONHOOK on-hook signal OFFHOOK or EANDMS_OFFHOOK off-hook signal DIGIT or EANDMS_DIGIT internal value, do not use WINK or EANDMS_WINK wink signal FLASH or EANDMS_FLASH flash signal DS0AIS or EANDMS_DS0AIS DS0 blue alarm, Alarm Indication Signal (AIS) DS0RAI or EANDMS_DS0RAI DSO yellow alarm, remote alarm indicator Loopstart (LST403) LST403_LO loop open signal (on-hook) LST403_LC loop closed signal (off-hook) LST403_DIGIT internal value, do not use LST403_WINK wink signal LST403_FLASH flash signal LST403_LCF loop current feed signal LST403_LCFO loop current feed open signal (forward disconnect) LST403_RING ring signal LST403_DS0AIS DS0 blue alarm, Alarm Indication Signal (AIS) LST403_DS0RAI DSO yellow alarm, remote alarm indicator Groundstart (GST403) GST403_LO loop open signal (on-hook) GST403_LC loop closed signal (off-hook) GST403_DIGIT internal value, do not use GST403_WINK wink signal GST403_FLASH flash signal GST403_LCF loop current feed signal GST403_LCFO loop current feed open signal (forward disconnect) GST403_RING ring signal GST403_RNGND ring ground signal GST403_DS0AIS DS0 blue alarm, Alarm Indication Signal (AIS) GST403_DS0RAI DSO yellow alarm, remote alarm indicator
Maintenance
635
Device Maintenance
Syntax [digit]
Description Optional parameter when type is DIGIT, EANDMS_DIGIT, LST403_DIGIT, or GST403_DIGIT. Range: 0 - 9
Prerequisites
Trunk group, see Trunk Groups on page 233
636
Maintenance
Device Maintenance
queryGain
queryGain <oid>
This command displays the transmit and receive gain on a trunk.
NOTE: queryGain does not work on the trunks of an LTC card.
Syntax <oid>
setGain
setGain <oid> <txGain> <rxGain>
This command changes the transmit and receive gain on a trunk.
NOTE: setGain does not work on the trunks of an LTC card.
Description Trunk Object Identifier. See OID on page 30. Amount of transmit gain in dB. 0 is the initial value. Range: 0 - 7 Amount of receive gain in dB. 0 is the initial value. Range: 0 - 7
queryGain Trunk-28 Gain settings for Trunk-28 Tx Gain -0 db Rx Gain -0 db setGain Trunk-28 2 7 queryGain Trunk-28 Gain settings for Trunk-28 Tx Gain -2 db Rx Gain -7 db
Maintenance
637
SS7 Maintenance
SS7 Maintenance
The following commands are SS7 operations commands.
SS7Restart
SS7Restart [networkName]
This command restarts an SS7 network. This could become necessary when you need to synchronize routing information with the STPs. Since restart is a disruptive procedure, you would typically not use this command. The network is unavailable for the duration of the restart. The restart time depends on the L3T27 timer, see L3T27_period on page 504.
CAUTION
Restarting an SS7 network briefly disrupts SS7 messaging.
Syntax [networkName]
Description Network name. Omit this parameter to force an SS7 restart for all networks
SS7Restart MCI
638
Maintenance
SS7 Maintenance
activateLinkSet
Tip
Use
activateLinkset <linkSetName>
This command activates an inactive link set. When a link set is provisioned, it defaults to an inactive state. Activate a link set after you add the links and are ready for the link set to send and receive signaling messages.
Syntax <linkSetName> Description name of the link set to activate
activateLinkset Linkset1
<linkSetName>
deactivateLinkSet Linkset1
Maintenance
639
SS7 Maintenance
blockLink
blockLink <linkName>
This command takes an SS7 signaling link out of service. The link is marked management blocked
Syntax <linkName> Description
name of the link to block
blockLink Link_1_1
unblockLink
Tip
Before unblocking a link, be sure that the link set is active. See activateLinkSet on page 639.
unblockLink <linkName>
This command allows a formerly blocked link to start carrying signaling information.
Syntax <linkName> Description
name of the link to unblock
unblockLink Link_1_1
640
Maintenance
SS7 Maintenance
inhibitLink
Tip
The last link in a link set can not be inhibited. The switch automatically uninhibits previously inhibited links when the last noninhibited link in a link set fails.
inhibitLink <linkName>
This command inhibits an SS7 signaling link. Inhibiting a signaling link restricts it from send signaling traffic, allowing only test and maintenance traffic. Inhibiting a link does not cause any link status changes at MTP Level 2. The switch on either or both sides of the signaling link can request link inhibition, and either switch can refuse inhibiting if it would impact routing.
Syntax <linkName> Description
name of link to inhibit
inhibitLink SWBT
uninhibitLink
Tip
Use linkStatus on page 107 to find the status of a link.
uninhibitLink <linkName>
This command uninhibits a locally inhibited SS7 signaling link.Since the switch on either side of the signaling link can request link inhibition, locally uninhibiting the link may not return it to a traffic bearing state.
Syntax <linkName> Description
name of link to inhibit
uninhibitLink SWBT
Maintenance
641
SS7 Maintenance
testLnpQuery
Tip
Use this command to validate SS7 routing from the switch to the SCP.
testLnpQuery 3042962645 2145290269 Raw TCAP Component dump: 0xe9 0x13 0xcf 0x02 0x14 0x00 0xd1 0x02 0x65 0x01 0x30 0x09 0x8f 0x07 0x03 0x10 0x49 0x20 0x13 0x99 0x99 Analyze Route response: Calling party address: 9402319999
642
Maintenance
ISUP Maintenance
ISUP Maintenance
Integrated Services User Part (ISUP) defines the protocol for setting-up, managing, and releasing trunk circuits (terminating line exchanges) that carry voice and data between a calling party and a called party.
circuitCCR
circuitCCR <PC> <CIC>
This command performs a continuity check. The circuitCCR command generates a COT (continuity check test) tone and sends it over the voice path to ensure total signaling and voice connectivity with SS7. This test is necessary because SS7 does use the actual voice circuit for messaging.
Syntax <PC> <CIC> Description designates the point code of a circuit designates the circuit identification code of a circuit
Maintenance
643
ISUP Maintenance
644
Maintenance
ISUP Maintenance
circuitGBlock Example
This command features a parameter that only a programmer could love. Suppose we want to reset CICs 101, 102, 110, 113, 115 and 122 for a particular point code. Here is how we would go about calculating the StatusBitMask:
CIC in msg: 101
Once the binary representation is converted to hex (1), it must be manipulated to account for Intel Little Endan memory addressing. 1. 2. 3. In hex representation (2), the upper and lower 2 byte blocks are swapped. In hex representation (3), the upper and lower bytes of each 2 byte block are swapped. In hex representation (4),the least significant byte (which used to be the most significant byte in hex representation (1)) is dropped, since this parameter expects only 24 significant bits.
The final result from hex representation (4) is converted to decimal and entered in the command:
Maintenance
645
ISUP Maintenance
circuitGUnblock
Tip
See circuitGBlock Example on page 645 to see how to calculate the StatusBitMask value.
<Release>
circuitReset
circuitReset <PC> <CIC>
This command sends a reset message.
NOTE: In systems that maintain circuit status in memory, there may be occasions when the memory is damaged. In such a case, reset the circuits to the idle condition in both exchanges to make them available for new traffic. Since the exchange with the damaged memory does not know whether the circuits are idle, busy outgoing, busy incoming, blocked, etc., the Reset Circuit messages and Group Reset Circuit (for a group of circuits) messages are applicable for the affected circuit(s).
Description designates the point code of a circuit designates the circuit identification code of a circuit
646
Maintenance
ISUP Maintenance
circuitQuery
Tip
Use this command when coordinating a circuit turn-up procedure.
Description designates the point code of a circuit designates the circuit identification code of a circuit designate range
Maintenance
647
ISUP Maintenance
circuitTest
circuitTest <PC> <CIC>
This command functions in systems that maintain circuit status in memory. The command sends a message on a routine or demand basis to request circuit translation information from the exchange at the other end of a circuit.
Syntax <PC> <CIC> Description designates the point code of a circuit designates the circuit identification code of a circuit
circuitBlock
circuitBlock <PC> <CIC>
This command permits the switch to remove traffic from the distant terminal of a circuit due to a fault, or to perform testing.
Syntax <PC> <CIC> Description designates the point code of a circuit designates the circuit identification code of a circuit
648
Maintenance
GR-303 Maintenance
GR-303 Maintenance
These commands are GR-303 operations commands.
inhibitPath
inhibitPath <name> <pathType> <pathPriority>
This command inhibits a GR-303 path.
Syntax Description RDT name a GR-303 path, either EOC Embedded Operations Channel TMC Timeslot Management Channel <pathPriority> Path priority, either PRIM primary SEC secondary
<name> <pathType>
<name> <pathType>
Maintenance
649
GR-303 Maintenance
Description
cancelRDTCmd RDT1
<name> <pathType>
NOTE: Although active calls are normally maintained during path protection switch-over, if you specify the FORCED parameter, active calls are dropped.
Dependent Commands
To switch back to the primary spans, repeat the protectionSwitch command.
650
Maintenance
GR-303 Maintenance
resync921
resync921 inst
This command reconnects the GR-303 EOC or TMC link connections on links that use Link Access Protocol-D (LAPD).
Syntax inst Description he instance of the link. Range: 1 - maximum number. The maximum number varies by card type: BIC 338 ETIC 32 LTC 32 TIC 32 PIC 0
resync921 1
Maintenance
651
GR-303 Maintenance
<name>
<state>
The DS1 is working properly. The DS1 is provisioned correctly (settings on the switch and RDT match).
Syntax
Description RDT name terminal ID number of the span on the RDT you want to place in loopback 0 release 1 set
<name>
<ds1TermId> <setInLoopback>
setLoopbackMode RDT1 15 1
CAUTION
When a DS1 is in loopback mode, it cannot carry information between the switch and the RDT.
652
Maintenance
GR-303 Maintenance
<CRV>
resetCRVs RDT1 P
Maintenance
653
AIN Maintenance
AIN Maintenance
These commands are AIN operations commands.
testCNameQuery 8174032222
Telephone number where the call can be routed Carrier name that handles calls for that toll free number
Syntax callingNumber calledNumber [Carrier] Description 10-digit telephone number of the originator 10-digit telephone number dialed 4 digit carrier code
654
Maintenance
AIN Maintenance
Telephone number where the call can be routed Carrier name that handles calls for that toll free number
Syntax ani calledNumber lata noHexDump Description The 10 digit Automatic Number Identification (ANI) of the telephone number of the calling party 10-digit telephone number dialed 3 digit Local Access and Transport Area disables the hexadecimal dump
Maintenance
655
splitFacility
splitFacility <OID | DN> [time]
This command splits the span or the subscribers facility and allows it to be accessed from the test panel.
NOTE: Entering the splitFacility without parameters shows if a facility is currently split. You can only split one facility at a time.
Description Object Identifier of subscribers facility, see OID on page 30. DN is the number of the subscriber. The time (in seconds) to split the facility. Use decimal for this command. Default is 600 seconds = 10 minutes.
[time]
656
Maintenance
Prerequisites
Split the span or subscriber, see splitFacility on page 656
Syntax <OID | DN> Description Object Identifier of subscribers facility, see OID on page 30. DN is the number of the subscriber.
Maintenance
657
In Service Upgrades
In Service Upgrades
Tip
Each card in the switch has a 7/ patchLog file. To troubleshoot, dump this file with 'cat < 7/ patchLog' and save the results.
To modify T7000 software while it is carrying call traffic, TAC uses in-service upgrades (ISUs). ISUs can either be applied to a single card or to all of the cards on a T7000. Once an ISU is applied, it installs and re-applies itself automatically on every successive reboot of the cards. If you unapply the ISU, but do not also unload it, it returns on successive reboots. ISUs should be applied on a T7000-wide basis unless directed by Taqua TAC. ISUs applied to a single-card should only be performed by qualified personnel under appropriate circumstances. If misused, they can cause the T7000 state to get out of sync and negatively affect call processing.
Action Connect to a card on the T7000. Copy the ISU archive file into the directory from which the card is booting or tftping. Load the ISU archive file from the directory to the specified card. Apply the ISU to the card. Verify that the ISU has been applied to the card.
3 4 5
Action Connect to the system manager card on the T7000. Copy the ISU archive file into the directory from which the system manager card is booting or tftping. Load the ISU archive file from the directory to the system manager card. The ISU tftps over and is distributed to all of the cards on the switch. Apply the ISU to all cards on the switch. Verify that the ISU has applied to each card on the T7000.
4 5
658
Maintenance
In Service Upgrades
sysLoadPatchArchive
Each card in the switch has a 7/patchLog file. To troubleshoot, dump this file with 'cat < 7/patchLog' and save the results.
sysLoadPatchArchive <filename>
This command is executed on the active system manager card. The system manager distributes and loads the ISU archive on all cards in a switch.
NOTE: If the file specified does not exist locally, the card attempts to find it in its TFTP home directory on ISEhouse. If it is there, the card TFTPs it over into the local file system (as specified in the filename itself). If the file is not found on the local file system or in the TFTP home directory, the operation fails.
This command does not apply the ISU to the software. To apply the ISU to all the cards on the switch, see sysApplyPatch on page 660. To apply the ISU to a single card, see applyPatch on page 660.
Syntax <filename> Description name of ISU archive file. Only file devices 7 and f may be specified.
sysLoadPatchArchive 7/OCX4.0.0-0002.a
This command does not apply the ISU to the software. To apply the ISU to a single card, see applyPatch on page 660.
Syntax <filename> Description name of file on ISU archive. Only file devices 7 and f may be specified.
loadPatchArchive 7/OCX4.0.0-0002.a
Maintenance
659
In Service Upgrades
Prerequisites
Load the patch on all of the cards, see sysLoadPatchArchive on page 659.
Syntax Description name of file
<patchID>
sysApplyPatch OCX4.0.0-0002
applyPatch
applyPatch <patchID>
This command instructs the card on which it is executed to apply the patch.
Prerequisites
Load the patch on one of the cards, see loadPatchArchive on page 659
Syntax Description name of file
<patchID>
applyPatch OCX4.0.0-0002
660
Maintenance
In Service Upgrades
Prerequisites
Apply the patch on all of the cards, see sysApplyPatch on page 660
Syntax Description name of file
<patchID>
sysUnApplyPatch OCX4.0.0-0002
Prerequisites
Apply the patch on one of the cards, see applyPatch on page 660
Syntax Description name of file
<patchID>
unapplyPatch OCX4.0.0-0002
Maintenance
661
In Service Upgrades
Syntax
<patchID>
sysUnloadPatch OCX1.4.2-0002
unloadPatch
unloadPatch <patchID>
This command instructs the card on which it is executed to unload the patch.
NOTE: Patches are loaded in entire archives. Patches are unloaded individually.
Syntax
<patchID>
unloadPatch OCX1.4.2-0002
662
Maintenance
Subscriber hears noise on the line during a conversation Subscriber is unable to clearly hear the called party Subscriber's data connection is not working properly
The carrier technician can connect a test box close to the subscriber's location, usually at the point where the line enters the subscriber's home or office, to test the line. The test box (usually a SAGE) is capable of dialing up the switch test line, measuring the returned tone, and detecting noise on the line. 100 - Type Test Lines The 100-type line provides the following items:
Returns off-hook (answer) supervision upon seizure of the test line. Provides a quiet interval of 300 ms 10% Provides 1004 Hz at 0dBm0 for 5.5 0.5 seconds. Applies a quiet termination to the caller for 60 minutes or until the caller hangs up. This allows the user to confirm the test line has been connected and measure the level of the circuit. The level can be used to determine signal-to-noise ratio measurements. If the caller does not hang up within 60 minutes, the line produces howler tone.
102-Type Test Lines The 102-type line provides the following items:
Returns off-hook (answer) supervision upon seizure of the test line. Provides a quiet interval of 300-ms -10%. Provides a 1004 Hz at 0 dBm0 tone for 9 seconds 10% followed by 1 second of quiet termination (silence). Continues the 10-second sequence is repeated continuously for 60 minutes or until the caller hangs up. If the caller does not hang up within 60 minutes, the line produces howler tone.
Maintenance
663
Action Add a prefix for the test tone numbers (see Prefixes on page 403 for more information about adding a prefix.) For example, to use prefix 972555 for Test Tone calls create Prefix 972555 Note that the choice of the prefix is completly arbitrary, and will probably be different for your office.
Create a route list that will contain the number to dial for each test (see NANP Route List on page 519 for more information about route lists). The following two examples create a route list for Test Tone 100 and Test Tone 102 calls. We will call the Test Tone 100 route list TestTone100. We have decided it can be accessed by calling 0100 in the 972555 prefix that was set up in step 1. create NANPRouteList TestTone100 9725550100 In a similar fashion, we have decided to call the Test Tone 102 route list TestTone102, and access it by calling 0102 in the 972555 prefix. create NANPRouteList TestTone102 9725550102 Note that once again, the choice of the route list names and the DN were completely arbitrary. However, services such as Test Tone must use NANP routing, so there was no choice about the type of route list to create.
Add the services to the route list (see Route Lists on page 514, and Adding a Route to a Route List on page 527 for more information). insertInto NANPRouteList TestTone100 routes 1 Test100 insertInto NANPRouteList TestTone102 routes 1 Test102 For these steps, there is no choice: The type of route list and the name of the route list were determined in step 2. Futhermore, routes is a keyword that must be used when inserting route into a route list. Finally, Test100 and Test102 are keywords that identify the Test Tone 100 and Test Tone 102 services, respectively.
664
Maintenance
Automatic Number Announcement (ANA) helps a carrier technician identify the phone number of a particular line. One or more special ANA numbers can be provisioned on the switch. When the special ANA number is dialed, the switch speaks the calling number in a customized announcement. After a brief pause, the switch repeats the calling number announcement. If the carrier technician does not hang up after the second announcement, the switch presents howler tone. To provision Automatic Number Announcement:
Step
1
Action (Optional) add a prefix for the ANA numbers (see Prefixes on page 403 for more information about adding a prefix.). Standard industry practice in North America is to use the 958 or 959 exchanges for local and long distance test numbers, but you are free to choose any exchnage for Automatic Number Announcements. For example, to use prefix 972958 for ANA calls create Prefix 972958
Create a route list that will contain the number to dial for the Automatic Number Announcement (see NANP Route List on page 519 for more information about route lists). The following example creates a route list for ANA calls. We will call the Automatic Number Announcement route list ANA_1. We have decided it can be accessed by calling 1234 in the 972958 prefix that was set up in step 1. create NANPRouteList ANA_1 9729581234 Note that once again, the choice of the route list name and the DN were completely arbitrary. However, services such as ANA must use NANP routing, so there was no choice about the type of route list to create.
Add the service to the route list (see Route Lists on page 514, and Adding a Route to a Route List on page 527 for more information). insertInto NANPRouteList ANA_1 routes 1 ANASvc For these steps, there is no choice: The type of route list and the name of the route list were determined in step 2. Futhermore, routes is a keyword that must be used when inserting route into a route list. Finally, ANASvc is a keyword that identifies the Anutomatic Number Announcement service.
Maintenance
665
SIP/MGCP/VoIP Maintenance
SIP/MGCP/VoIP Maintenance
pingVoip
pingVoip <device_num> <ip_addr>
Issue this command on a PIC card to test the communications path to a given IP address over the specified Ethernet port. The switch issues an ICMP ping (sometimes referred to a a Packet Internet Groper command, as per RFC 1739), to determine if the remote host is active and to determine the round-trip communicating delay between the switch and the host.
Syntax Description Number of the device to issue the ping command from. 0 Fast Ethernet Port 0 1 Fast Ethernet Port 1 2 Fast Ethernet Port 2 (PIC 2 only)
<device_num>
<ip_addr>
666
Maintenance
SIP/MGCP/VoIP Maintenance
nslookup
nslookup <FQDN> <Interface> [dnsSRV(0|1)]
Issue this command on a PIC card to debug queries and responses from a DNS (Domain Name System).
Syntax <FQDN> <Interface> Description Fully Qualified Domain Name for the query. The number of the device which will issue the DNS lookup. 0 Fast Ethernet Port 0 1 Fast Ethernet Port 1 2 Fast Ethernet Port 2 (PIC 2 only)
[dnsSRV(0|1)]
Optional parameter which specifies the type of DNS lookup. Values are: 0 DNS_A lookup. Returns an IP Address. 1 DNS_SRV lookup. Returns an IP Address and Port Number.
Prerequisites
DNS server configured on the Fast Ethernet Interface. See modifyFacility on page
217.
Maintenance
667
SIP/MGCP/VoIP Maintenance
nslookup as.taqua.local 1 Header information: ID: 777 Operation Code: QUERY Query/Response Flag: Response Authoritative Answer Flag: true Truncation Flag: false Recursion Desired: true Recursion Available: true Response Code: NO_ERROR Question Count: 1 Answer Record Count: 2 Authority Record Count: 0 Additional Record Count: 0 Question section: Name: as.taqua.local Type: A Class: INTERNET Answer section: 2 Name: as.taqua.local Type: A Class: INTERNET TTL: 0 seconds IP Addr: 172.19.160.193 Name: as.taqua.local Type: A Class: INTERNET TTL: 0 seconds IP Addr: 172.19.160.191 Authority section: 0 Additional section: 0
668
Maintenance
Performance Monitoring
The commands in this chapter relate to T7000 Performance Monitoring. Performance Monitoring on the T7000 measures the following:
Active Call Measurements (ACMs) DS1 Monitoring DS3 Performance Monitoring Peg Counts Usage Intervals
View a snapshot of active facilities on a T7000 at a point in time. Accumulate snapshots of facility activity. View and reset the accumulated data.
You determine the interval in seconds to take snap shots of activity on the T7000. You can view activity or a log of accumulated data on the following:
A card A trunk group A span All of the cards in a T7000 All of the spans in a T7000 All of the trunk groups on a T7000
NOTE: Using ACMs from the command line is independent from ACMs on the OM. They are separate processes and they do not affect each other.
Performance Monitoring
669
logActiveCalls 30
Dependent Commands
The following ACM commands are dependant on logActiveCalls:
stopActiveCallLog stopActiveCallLog
This command stops the active facility snap shots.
NOTE: Use resetCallHist on page 670 to reset the call log statictics.
stopActiveCallLog
resetCallHist resetCallHist
This command resets the active facility snap shot log and stops the logActiveCalls command. All of the ACM counters are set to zero.
Prerequisites
Log the active calls, see logActiveCalls on page 670
670
Performance Monitoring
DS1 Monitoring
DS1 monitoring tracks the status of spans by collecting data from the spans drivers per ANSI T1.231. The T7000 gathers, reports, and thresholds performance data from the spans. A line is a DS1 that connects the T7000 to another network element. A path is a DS1 that passes through at least one other network element and connects the T7000 to another switch. The following types of performance date are collected
Table 1: DS1 Performance Monitoring Counters fc cvl Failure Count, the number of the occurrences of near- and far-end path failure events Code Violation - Line, the number of both bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the period. An EXZ increments the CVL by one regardless of the length of the zero string. For a B8ZS signal, BPVs that are part of the zero substitution code are excluded from the count. This counter is subject to inhibiting. Inhibiting is when there is an overriding condition that prevents events from being counted. Errored Second-Line, the number of one-second intervals with one or more BPVs, EXZs, or LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code are excluded. Severely Errored Second Line, the number of one-second intervals with 1544 or more BPVs plus EXZs, or one or more LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code are excluded Loss Second Line: The number of one-second intervals containing one or more LOS defects. Severely Errored Frame/Alarm Indication Signal (SEF/AIS) Second-Path, the number of one-second intervals containing one or more SEF defects or one or more AIS defects. This counter is subject to inhibiting. Alarm Indicator Signals Second-Path, the number of one-second intervals containing one or more AIS defects. An AIS defect is a signal that indicates serious impairments, such as upstream failure events. This counter is subject to inhibiting.
esl sesl
lossl sasp
aissp
sefsp or Severely Errored Framing Seconds, the number of one-second performance report message (PRM) sefs intervals containing an severely errored frame (SE) = 1. This counter is subject to inhibiting. cvp Code Violation: The number of frame synchronization bit errors in the SF format or the count of cyclic redundancy check (CRC-6) errors in the ESF format occurring during the accumulation period. This counter is subject to inhibiting. Errored Second Type B: this counter only applies to DS1 ESF paths. It is a count of one-second intervals between 2 and 319 CRC-6 errors, no SEF defects, and no AIS defects. This counter is subject to inhibiting Controlled Slip Second-Path: The number of one-second intervals containing one or more controlled slips. Counts of controlled slips are accurately made in the path terminating network element of the DS1 signal, where the controlled slip takes place. A controlled slip indicates a synchronization problem in DS1 paths. A controlled slip does not cause an out-of-frame event. This counter is subject to inhibiting. Unavailable Second: The number of one-second intervals for which the DS1 path is unavailable. The DS1 path becomes unavailable at the onset of 10 contiguous severely errored seconds (SESs). The 10 SESs are included in unavailable time. Once unavailable, the DS1 path becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from unavailable time. Some counts are inhibited during unavailability All of the above counters
esbp
cssp
uasp
all
Performance Monitoring
671
Action Set up the DS1 performance monitoring using the following: setPMTime on page 673 to set the DS1 monitoring time suppressTCA15 on page 674 or unsuppressTCA15 on page 674 to configure the frequency of Threshold Crossing Alerts (TCAs) setTCA15 on page 675 and setTCA24 on page 676 to configure the 15minute and 24-hour threshold levels.
Enable TCA reporting for a span using startTCA15 on page 677 and startTCA24 on page 678. Turn on the DS1 monitoring display using setPMDisplayOn on page 679. Start DS1 performance monitoring on an oid using startPM on page 680. Wait for TCA alarms/events or refer to the status of an oid. getPMStatus on page 681 to view general status getPMCurrent on page 682 to view all intervals getPMInterval on page 683 to view a specific interval
3 4 5
NOTE: The Threshold15Min and Threshold24Hour alarms create a current alarm when a threshold is passed.
To turn off the TCA use stopTCA15 on page 677 and stopTCA24 on page
678.
To turn off the DS1 performance monitoring use stopPM on page 680 and
setPMDisplayOff on page 679
672
Performance Monitoring
setPMTime
setPMTime <oid> <timeval>
This command sets the DS1 performance monitoring line time for a span. Use this command to set the performance monitoring time on a span to a value that matches the T7000s time.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <timeval> The line time in seconds, from 0 to 86,399 (zero-based). This value is the timestamp on the DS1 monitoring output. There are 3,600 seconds for each hour period. For example, 2:00 am is 7200 and 11:00 pm is 82000. Note: Enter the value in parenthesis to use a decimal value.
Performance Monitoring
673
Syntax <oid>
Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span.
[nefe]
Enter one of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). NOTE: If omitted, the default is ne.
suppressTCA15 Span-1
unsuppressTCA15 Span-1
674
Performance Monitoring
setTCA15
setTCA15 <oid> <pmtype> <value> [nefe]
This command sets 15-minute threshold values for a span and DS1 monitoring counter.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <pmtype> <value> See DS1 Performance Monitoring Counters on page 671. Decimal value of the threshold: fc 1 cvl 13340 esl 65 sesl 10 lossl 1 sasp 2 aissp 1 sefsp or sefs 1 cvp 72 esp 65 esap 13296 esbp 1 sesp 10 cssp 1 usap 10 [nefe] Enter one of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). If you do not enter a value for nefe, the T7000 defaults to ne.
Performance Monitoring
675
setTCA24
setTCA24 <oid> <pmtype> <value> [nefe]
This command sets 24-hour threshold values for a span and DS1 monitoring counter.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <pmtype> <value> See DS1 Performance Monitoring Counters on page 671. Decimal value of the threshold: fc 1 cvl 133400 esl 648 sesl 100 lossl 1 sasp 17 aissp 1 sefsp or sefs 1 cvp 691 esp 648 esap 132960 esbp 1 sesp 100 cssp 4 usap 10 [nefe] Enter one of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). If you do not enter a value for nefe, the T7000 defaults to ne.
676
Performance Monitoring
startTCA15
startTCA15 <oid> <pmtype> [nefe]
This command enables the T7000 to send the 15-minute TCAs for a specific span and DS1 monitoring counter.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <pmtype> [nefe] See DS1 Performance Monitoring Counters on page 671. Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
stopTCA15
stopTCA15 <oid> <pmtype> [nefe]
This command disables 15-minute TCAs for a specific span and DS1 monitoring counter.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <pmtype> [nefe] See DS1 Performance Monitoring Counters on page 671. Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
Performance Monitoring
677
startTCA24
startTCA24 <oid> <pmtype> [nefe]
This command enables the T7000 to send the 24-hour TCAs for a specific span and DS1 monitoring counter.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <pmtype> [nefe] See DS1 Performance Monitoring Counters on page 671. Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
stopTCA24
stopTCA24 <oid> <pmtype> [nefe]
This command disables 24-hour TCAs for a specific span and DS1 monitoring counter.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <pmtype> [nefe] See DS1 Performance Monitoring Counters on page 671. Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
678
Performance Monitoring
setPMDisplayOn setPMDisplayOn
This command enables event display for DS1 (and DS3) performance monitoring. Use this command to view DS1 performance monitoring events for all spans. The events include:
Indication that a 15-minute interval completes on an span. A 15-minute TCA is issued. A 24-hour TCA was issued.
setPMDisplayOff setPMDisplayOff
This command disables event display for DS1 (and DS3) performance monitoring.
Performance Monitoring
679
startPM
startPM <oid | allspans>
This command starts DS1 performance monitoring for a span, or for all spans on the card.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span.
allspans
This parameter is used to start Performance Monitoring on all DS1s on all spans on the card.
startPM Span-0
stopPM
stopPM <oid | allspans>
This command stops DS1 performance monitoring for a span, or for all spans on the card.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span.
allspans
This parameter is used to start Performance Monitoring on all DS1s on all spans on the card.
stopPM Span-0
680
Performance Monitoring
LINE the span number on the card INIT the DS1 performance monitoring availability, 1=available 0=not
available
ENAB the state of performance monitoring, 1=enabled 0=disabled INTVLS the number of 15-minute intervals collected, from 0 to 196 or
48 hours of intervals
PMTIME the current line time in seconds SUP15 the status of for TCA suppression, 0=not surpressed,
1=surpressed
getPMStatus getPMStatus: T1.231 Performance Monitor Status: LINE INIT ENAB INTVLS PMTIME SUP15 0 1 0 0 8452 0 1 1 0 0 0 0 2 1 0 0 0 0 3 1 0 0 0 0 4 1 0 0 0 0
Performance Monitoring
681
Prerequisites
Set the DS1 monitoring time, see setPMTime on page 673 Enable TCA reporting for a span using startTCA15 on page 677 and
startTCA24 on page 678.
getPMCurrent Span-1
The following defines the output for this command. Values that are not available show -----:
cur15 current 15-minute interval results lastInt last 15-minute interval results Sum24 summary of the most recent 24-hour period last24 summary of the previous 24-hour period before sum24 Today counts since the 00 time or midnight Yesterday counts from the last period of 24-hours timeSt the time stamp of line time in seconds vsecs valid seconds invData the invalid data flag that identifies any >10 second gap in data, 1 = invaild data and 0 = valid data dsecs same as valid seconds
NOTE: The time for determining today and yesterday is based on line time, not the system time. Line time ranges from 0 to 86,399. To synchronize the line time with the T7000s time see setPMTime on page 673.
682
Performance Monitoring
Prerequisites
Set the DS1 monitoring time, see setPMTime on page 673 Enable TCA reporting for a span using startTCA15 on page 677 and
startTCA24 on page 678.
Turn on the DS1 monitoring display using setPMDisplayOn on page 679. Start DS1 performance monitoring on an oid using startPM on page 680.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. <intervalN> The number of the interval that you want to view. There are 192 intervals in 48 hours, one for every 15-minutes. Interval 0 is the current interval and interval 1 is the last completed interval. Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
[nefe]
The following defines the output for this command. Values that are not available show -----.
cur15 current 15-minute interval results Prev # the previous interval and number of the interval before the
requested interval
Int # the requested interval and its number Next # the next interval after the requested interval timeSt the time stamp of line time in seconds vsecs valid seconds invData the invalid data flag that identifies any >10 second gap in data,
Performance Monitoring
683
T1.231 DS1 Performance Monitor Interval Data Near End: Line 0 Valid Intervals 1 currentLineTime 52721 timeSt vsecs invDat dsec fc esl sesl lossl sasp aissp sefsp cvp esp esap esbp sesp cssp uasp cur15 52200 521 0 521 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Prev 0 52200 521 0 521 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Int 1 52132 68 1 68 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Next ------------------------------------------------------------------------2 sum24 52132 68 3 68 0 0 0 0 0 0 0 0 0 0 0 0 0 0 last24 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Counters
684
Performance Monitoring
getPMTCA
getPMTCA <oid> [<nefe]
This command shows the current intervals, thresholds, and TCAs.
Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. [nefe] Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
The following results show the current TCA count (cur15), the threshold level for 15-minutes (thresh15), the count of TCAs sent (notify15), and the corresponding information for 24-hours.
getPMTCA Span-1 T1.231 DS1 Performance Monitor Interval Data Near End: Line 1 Valid Intervals 0 currentLineTime 0 TCA15 not suppressed cur15 thresh15 notify15 sum24 thresh24 notify24 timeSt ----0 0 ----0 0 vsecs ----0 0 ----0 0 invDat ----0 0 ----0 0 dsec ----0 0 ----0 0 fc -----1 0 -----1 0 cvl -----13340 0 ----- -133400 0 esl -----65 0 -----648 0 sesl -----10 0 -----100 0 lossl -----1 0 -----1 0 sasp -----2 0 -----17 0 aissp -----1 0 -----1 0 sefsp -----1 0 -----1 0 cvp -----72 0 -----691 0 esp -----65 0 -----648 0 esap -----1 0 -----1 0 esbp -----1 0 -----1 0 sesp -----10 0 -----100 0 cssp -----1 0 -----4 0
uasp -----10 0 -----10 0
Counters
NOTE: Threshold values appear as negative values, if TCA is not enable for a counter.
Performance Monitoring
685
setTCADefaults Span-1
686
Performance Monitoring
cur15 current 15-minute interval results lastInt last 15-minute interval results Sum24 summary of the most recent 24-hour period last24 summary of the previous 24-hour period before sum24 Syntax <oid> Description Span Object Identifier see OID on page 30. NOTE: Use capital S when entering oid for Span. [nefe] Enter either of the following: ne near-end to show DS1 status for the T7000 fe far-end to show DS1 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
resetPMIntervals Span-1
Performance Monitoring
687
688
Performance Monitoring
DS3 Monitoring
DS3 Monitoring
DS3 monitoring consists of counters that monitor the condition of in-service DS3s processing call traffic, per ANSI T1.231. DS3 counters determine the local status of DS3 lines and paths by collecting data from the spans driver. A line is a DS3 that connects the T7000 to another network element. A path is a DS3 that passes through at least one other network element and connects the T7000 to another switch. The following types of performance date are collected:
Table 2: DS3 Performance Monitoring Counters fc cvl Failure Count, the number of the occurrences of near- and far-end path failure events. Code Violation-Line, the number of both bipolar violations (BPVs) and excessive zeros (EXZs) occurring over the period. An EXZ increments the CVL by one regardless of the length of the zero string. For a B8ZS signal, BPVs that are part of the zero substitution code are excluded from the count. This counter is subject to inhibiting. Inhibiting is when there is an overriding condition that prevents events from being counted. Errored Second-Line, the number of one-second intervals with one or more BPVs, EXZs, or LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code are excluded. Severely Errored Second Line, the number of one-second intervals with 1544 or more BPVs plus EXZs, or one or more LOS defects. For a B8ZS-coded signal, BPVs that are part of the zero substitution code are excluded Loss Second Line The number of one-second intervals containing one or more LOS defects. Severely Errored Frame/Alarm Indication Signal (SEF/AIS) Second-Path, the number of onesecond intervals containing one or more SEF defects or one or more AIS defects. This counter is subject to inhibiting. Alarm Indicator Signals Second-Path, the number of one-second intervals containing one or more AIS defects. An AIS defect is a signal that indicates serious impairments, such as upstream failure events. This counter is subject to inhibiting. Severely Errored Framing Seconds, the number of one-second performance report message (PRM) intervals containing an severely errored frame (SE) = 1. This counter is subject to inhibiting. Code Violation The number of frame synchronization bit errors in the SF format or the count of cyclic redundancy check (CRC-6) errors in the ESF format occurring during the accumulation period. This counter is subject to inhibiting. All of the above counters
esl sesl
lossl sasp
aissp
sefsp
cvp
all
Performance Monitoring
689
DS3 Monitoring
Table 2: DS3 Performance Monitoring Counters esp Errored Second The number of one-second intervals, for DS3 ESF, containing any of the following: CRC-6 errors CS events SEF defects AIS defects The number of one-second intervals, DS3 SF, containing any of the following: FE errors CS events SEF defects AIS defects This counter is subject to inhibiting esap Errored Second Type A: this counter only applies to DS3 ESF paths. The number of one-second intervals with exactly one Cycle Redundancy Check (CRC)-6 error, and no severely errored frame (SEF) or AIS defects. This counter is subject to inhibiting Errored Second Type B: this counter only applies to DS3 ESF paths. It is a count of one-second intervals between 2 and 319 CRC-6 errors, no SEF defects, and no AIS defects. This counter is subject to inhibiting Severely Errored Second: this counter applies to both SF and ESF frame formats of DS3. ESF the number of one-second intervals with 320 or more CRC-6 errors, or one or more SEF or AIS defects. SF the number of one-second intervals with eight or more FE events, an SEF defect, or AIS defect. This counter is subject to inhibiting cssp Controlled Slip Second-Path: The number of one-second intervals containing one or more controlled slips. Counts of controlled slips are accurately made in the path terminating network element of the DS3 signal, where the controlled slip takes place. A controlled slip indicates a synchronization problem in DS3 paths. A controlled slip does not cause an out-of-frame event. This counter is subject to inhibiting Unavailable Second: The number of one-second intervals for which the DS3 path is unavailable. The DS3 path becomes unavailable at the onset of 10 contiguous severely errored seconds (SESs). The 10 SESs are included in unavailable time. Once unavailable, the DS3 path becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from unavailable time. Some counts are inhibited during unavailability
esbp
sesp
uasp
690
Performance Monitoring
DS3 Monitoring
Action Set up the DS3 performance monitoring using the following: setPMTime on page 692 to set the DS3 monitoring time suppressTCA15 on page 693 or unsuppressTCA15 on page 693 to configure the frequency of Threshold Crossing Alerts (TCAs) setTCA15 on page 694 and setTCA24 on page 695 to configure the 15-minute and 24-hour threshold levels.
Enable TCA reporting for a span using startTCA15 on page 695 and startTCA24 on page 696. Turn on the DS3 monitoring display using setPMDisplayOn on page 697. Start DS3 performance monitoring on an oid using startPM on page 698. Wait for TCA alarms/events or refer to the status of an oid. getPMStatus on page 699 to view general status getPMCurrent on page 700 to view all intervals getPMInterval on page 701 to view a specific interval
NOTE: NOTE: The Threshold15MinDS3 and Threshold24HourDS3 alarms create a alarm when a threshold is passed.
To turn off the stopTCA15 on page 696 and stopTCA24 on page 697. To turn off the DS3 performance monitoring use stopPM on page 698 and
setPMDisplayOff on page 679
Performance Monitoring
691
DS3 Monitoring
setPMTime
setPMTime <oid> <timeval>
This command sets the DS3 performance monitoring line time for a DS3. Use this command to set the performance monitoring time on a DS3 to a value that matches the T7000s time.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <timeval> The line time in seconds, from 0 to 86,399 (zero-based). This value is the timestamp on the DS3 monitoring output. There are 3,600 seconds for each hour period. For example, 2:00 am is 7200 and 11:00 pm is 82000. Note: Enter the value in parenthesis to use a decimal value.
692
Performance Monitoring
DS3 Monitoring
Syntax <oid>
Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line.
[nefe]
Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
suppressTCA15 DS3-1
unsuppressTCA15 DS3Line-1
Performance Monitoring
693
DS3 Monitoring
setTCA15
setTCA15 <oid> <pmtype> <value> [<nefe>]
This command sets 15-minute threshold values for a DS3 monitoring counter.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> <value> See DS3 Performance Monitoring Counters on page 689. Decimal value of the threshold: fc 1 cvl 13340 esl 65 sesl 10 lossl 1 sasp 2 aissp 1 sefs 1 cvp 72 esp 65 esap 13296 esbp 1 sesp 10 cssp 1 usap 10 [<nefe>] Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
694
Performance Monitoring
DS3 Monitoring
setTCA24
setTCA24 <oid> <pmtype> <value> [nefe]
This command sets 24-hour threshold values for a DS3 monitoring counter.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [nefe] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
startTCA15
startTCA15 <oid> <pmtype> [nefe]
This command enables the T7000 to send the 15-minute TCAs for a DS3 monitoring counter.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [nefe] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
Performance Monitoring
695
DS3 Monitoring
stopTCA15
stopTCA15 <oid> <pmtype> [nefe]
This command disables 15-minute TCAs for a DS3 monitoring counter.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [nefe] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
startTCA24
startTCA24 <oid> <pmtype> [nefe]
This command enables the T7000 to send the 24-hour TCAs for a DS3 monitoring counter.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [nefe] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
696
Performance Monitoring
DS3 Monitoring
stopTCA24
stopTCA24 <oid> <pmtype> [nefe]
This command disables 24-hour TCAs for a DS3 monitoring counter.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [<nefe>] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
setPMDisplayOn setPMDisplayOn
This command enables event display for DS3 (and DS1) performance monitoring. Use this command to view DS3 performance monitoring events for all DS3s. The events include:
Indication that a 15-minute interval completes on a DS3. A 15-minute TCA is issued. A 24-hour TCA was issued.
setPMDisplayOff setPMDisplayOff
This command disables event display for DS3 (and DS1) performance monitoring.
Performance Monitoring
697
DS3 Monitoring
startPM
startPM <oid>
This command starts DS3 performance monitoring.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line.
startPM DS3-0
stopPM
stopPM <oid>
This command stops DS3 performance monitoring.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line.
stopPM DS3-0
698
Performance Monitoring
DS3 Monitoring
LINE the DS3 number on the card INIT the DS3 performance monitoring availability, 1=available 0=not
available
ENAB the state of performance monitoring, 1=enabled 0=disabled INTVLS the number of 15-minute intervals collected, from 0 to 196 or
48 hours of intervals
PMTIME the current line time in seconds SUP15 the status of for TCA suppression, 0=not surpressed,
1=surpressed
getPMStatus getPMStatus: T1.231 Performance Monitor Status: LINE INIT ENAB INTVLS PMTIME 0 1 0 0 8452 1 1 0 0 0 2 1 0 0 0 3 1 0 0 0 4 1 0 0 0
SUP15 0 0 0 0 0
Performance Monitoring
699
DS3 Monitoring
Prerequisites
Set the DS3 monitoring time, see setPMTime on page 673 Enable TCA reporting for a DS3 using startTCA15 on page 677 and startTCA24 on page 678. Start DS3 performance monitoring on an oid using startPM on page 680.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. [nefe] Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
getPMCurrent DS3-1
The following defines the output for this command. Values that are not available show -----:
cur15 current 15-minute interval results lastInt last 15-minute interval results Sum24 summary of the most recent 24-hour period last24 summary of the previous 24-hour period before sum24 Today counts since the 00 time or midnight Yesterday counts from the last period of 24-hours timeSt the time stamp of line time in seconds vsecs valid seconds invData the invalid data flag that identifies any >10 second gap in data,
700
Performance Monitoring
DS3 Monitoring
Prerequisites
Set the DS3 monitoring time, see setPMTime on page 673 Enable TCA reporting for a DS3 using startTCA15 on page 677 and
startTCA24 on page 678.
Turn on the DS3 monitoring display using setPMDisplayOn on page 679. Start DS3 performance monitoring on an oid using startPM on page 680.
Syntax <oid> Description DS3 Object Identifier see OID on page 30.
NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <intervalN> The number of the interval that you want to view. There are 192 intervals in 48 hours, one for every 15-minutes. Interval 0 is the current interval and interval 1 is the last completed interval. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
[nefe]
The following defines the output for this command. Values that are not available show -----.
cur15 current 15-minute interval results Prev # the previous interval and number of the interval before the
requested interval
Int # the requested interval and its number Next # the next interval after the requested interval timeSt the time stamp of line time in seconds vsecs valid seconds invData the invalid data flag that identifies any >10 second gap in data,
Performance Monitoring
701
DS3 Monitoring
getPMInterval DS3-0 1 T1.231 DS3 Performance Monitor Interval Data Near End: Line 0 Valid Intervals 1 currentLineTime 52721 timeSt vsecs invDat dsec fc esl sesl lossl sasp aissp sefsp cvp esp esap esbp sesp cssp uasp cur15 52200 521 0 521 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Prev 0 52200 521 0 521 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Int 1 52132 68 1 68 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Next ------------------------------------------------------------------------2 sum24 52132 68 3 68 0 0 0 0 0 0 0 0 0 0 0 0 0 0 last24 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Counters
702
Performance Monitoring
DS3 Monitoring
getPMTCA
getPMTCA <oid> [nefe]
This command shows the current intervals, thresholds, and TCAs.
Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. [nefe] Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
The following results show the current TCA count (cur15), the threshold level for 15-minutes (thresh15), the count of TCAs sent (notify15), and the corresponding information for 24-hours.
getPMTCA DS3-1 T1.231 DS3 Performance Monitor Interval Data Near End: Line 1 Valid Intervals 0 currentLineTime 0 TCA15 not suppressed timeSt vsecs invDat dsec fc cvl esl sesl lossl sasp aissp sefsp cvp esp esap esbp sesp cssp uasp cur15 thresh15 notify15 sum24 thresh24 notify24 ----0 0 ----0 0 ----0 0 ----0 0 ----0 0 ----0 0 ----0 0 ----0 0 -----1 0 -----1 0 -----13340 0 ----- -133400 0 -----65 0 -----648 0 -----10 0 -----100 0 -----1 0 -----1 0 -----2 0 -----17 0 -----1 0 -----1 0 -----1 0 -----1 0 -----72 0 -----691 0 -----65 0 -----648 0 -----1 0 -----1 0 -----1 0 -----1 0 -----10 0 -----100 0 -----1 0 -----4 0 -----10 0 -----10 0
Counters
Performance Monitoring
703
DS3 Monitoring
NOTE: Threshold values appear as negative values, if TCA is not enable for a counter.
setTCADefaults DS3-1
704
Performance Monitoring
DS3 Monitoring
cur15 current 15-minute interval results lastInt last 15-minute interval results Sum24 summary of the most recent 24-hour period last24 summary of the previous 24-hour period before sum24 Syntax <oid> Description DS3 Object Identifier see OID on page 30. NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. [nefe] Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
resetPMIntervals DS3-1
Performance Monitoring
705
DS3 Monitoring
NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [nefe] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
706
Performance Monitoring
DS3 Monitoring
NOTE: Use DS3-x, where x is 0, 1, or 2 depending on the DS3 line. <pmtype> [nefe] See DS3 Performance Monitoring Counters on page 689. Enter either of the following: ne near-end to show DS3 status for the T7000 fe far-end to show DS3 status for the switch to which the T7000 connects (not currently supported). Note: If you do not enter a value for nefe, the T7000 defaults to ne.
Performance Monitoring
707
Peg Counts
Peg counts count facility events relative to the following:
T7000 Call Model Usage of SS7 links or link sets by MTP levels 1 - 3, per SS7 route, per SCCP, or per PC and SSN combination. Message Signal Units (MSUs) received/transmitted
These measurements are a subset of the measurements defined in Section 4 of Telcordias GR-478 that are applicable to an SSP.
Usage Intervals
Usage Intervals track usage of SS7 links or link sets by MTP level 2, level 3, and SCCP TCAP. These measurements are a subset of the SS7 Measurements defined in Section 4 of Telcordias GR-478 that are applicable to an SSP.
Using Counters
Counters manage peg counts or usage intervals.
Enable and disable the counter using enableCounter on page 715 and
disableCounter on page 716
708
Performance Monitoring
The following table lists the MTP Level 1 Peg and Usage Counters.
Table 4: MTP Level 1 Peg and Usage Counters Name Data Transmitted on a link SNMP Description total MSUs MSUOctets LSSUs transmitted on an outgoing link Counter Type Peg
Performance Monitoring
709
The following table lists the MTP Level 2 Peg and Usage Counters.
Table 5: MTP Level 2 Peg and Usage Counters Name Congestion Discard Events by Discard Level Congestion MSUs Discarded by priority Data Received on a link Data Retransmitted on a link Duration of Receipt of SIB Duration of Signaling Link Congestion by congestion level Duration of Transmitting of SIB Signaling Link Congestion Events by congestion level Signaling Link RX Congestion Events RX Congestion Discard Events SNMP Description Total Congestion Discard Events by Discard Level Total Congestion MSUs Discarded by priority Total MSUs MSUOctets or LSSUs received on an incoming link Total MSUs MSUOctets retransmitted on an outgoing link Duration of the Receipt of Busy Link Status Unit Duration of Signaling Link Congestion by congestion level Duration of the Transmitting of Busy Link Status Unit Total Signaling Link Congestion Events by congestion level Total Signaling Link RX Congestion Events Total RX Congestion Discard Events Counter Type Peg Peg Peg Peg Usage Usage
710
Performance Monitoring
The following table lists the MTP Level 3 Peg and Usage Counters.
Table 6: MTP Level 3 Peg and Usage Counters Name MSUs Discarded of invalid DPC MSUs Discarded of invalid SIO MSUs Discarded due to congestion by priority Duration of Linkset Active Duration of Link unAvailable Duration of Link in Service Duration of Remote Processor Outage SRCT MSUs Transmitted per route RSR MSUs Transmitted per route RSP MSUs Transmitted per route TFA MSUs Received per route TFC MSUs Received per route TFP MSUs Received per route TFR MSUs Received per route' SLTM Received on a link SLTA Received on a link UPU MSUs Received SNMP Description total MSUs Discarded of invalid DPC total MSUs Discarded of invalid SIO total MSUs Discard due to congestion by priority 0,1,2 and 3 Duration of Link set Active (at least on link is in operation) Duration of Link unAvailable Duration of Link Service in L2 Duration of Remote Processor Outage total Signalling Route Set Congestion Test MSUs Transmitted per route total Restricted Signalling Route Set test MSUs Transmitted per route total Prohibited Signalling Route Set test MSUs Transmitted per route total Transfer Allowed MSUs Received per route total Transfer Controlled MSUs Received per route total Transfer Prohibited MSUs Received per route total Transfer Restricted MSUs Received per route total SLTM Received on an incoming link total SLTA Received on an incoming link total User Part Unavailable MSUs Received Counter Type Peg Peg Peg Usage Usage Usage Usage Peg Peg Peg Peg Peg Peg Peg Peg Peg Peg
Performance Monitoring
711
The following table lists the SCCP and TCAP Peg and Usage Counters.
Table 7: SCCP/TCAP Peg and Usage Counters Name SSA MSUs Received SSP MSUs Received ST MSUs Received SSA MSUs Transmitted SSP MSUs Transmitted MSUs Rejected with invalid APC/SSN SST MSUs Transmitted SNMP Description total Subsystem Allowed MSUs Received total Subsystem Prohibited MSUs Received total Subsystem Test MSUs Received total Subsystem Allowed MSUs Transmitted total Subsystem Prohibited MSUs Transmitted total invalid affected PC/SSN received total Subsystem Test MSUs Transmitted Counter Type Peg Peg Peg Peg Peg Peg Peg
712
Performance Monitoring
The following table lists the Call Processing Peg and Usage Counters.
Table 8: Call Processing Peg and Usage Counters Name Call Attempts Collect Digits Attempts Call Completion Attempts Terminating Calls Answered Routing Failures Line Busy Originating Calls Abandoned Terminating Calls Ring No Answer Protocol errors not associated with a call SNMP Description Call Attempts Collect Digits Attempts Call Completion Attempts Total Terminating Calls Answered Routing Failures Line Busy Total Originating Calls Abandoned Terminating Calls Ring No Answer Protocol errors not associated with a call Counter Type Peg Peg Peg Peg Peg Peg Peg Peg Peg
Performance Monitoring
713
queryCounterDefs
Tip
To view the PIDs currently running on the T7000, see ps on page 605.
queryCounterDefs <pid>
This command shows the counter definitions for a given PID.
Syntax <pid> Description Process ID. See Peg and Usage Counter PIDs on page 709.
queryCounterDefs 38
NOTE: Output trimmed to conserve space
**** Counter Definition Named (Data Transmitted on a link) ***** Type: (PEG COUNTER) Message: (Mtp1Transmit) Category: (0x1) Default State: (ENABLED) Current State: (ENABLED) Dimension: (3) Threshold (Low): (0) Threshold EventID (Low): (0x0) Threshold (Med): (0) Threshold EventID (Med): (0x0) Threshold (High): (0) Threshold EventID (High): (0x0) Dimensioned Counter Names: (MSUs) (MSUOctets) (LSSUs) Internal Peg Index: (0) Counter ID: (0) Peg Function: (_Mtp1Sm+0x74) FSM definition: (_Mtp1SmDef+0x0) Instance Type: (0x4)
714
Performance Monitoring
Performance Monitoring
715
716
Performance Monitoring
queryCounterDef "SSP MSUs Transmitted" 3e **Counter Definition Named (SSP MSUs Transmitted** Type: (PEG COUNTER) Message: (Subsystem_Prohibited_Transmitted) Category: (0x6) Default State: (ENABLED) Current State: (ENABLED) Dimension: (1) Threshold (Low): (0) Threshold EventID (Low): (0x0) Threshold (Med): (0) Threshold EventID (Med): (0x0) Threshold (High): (0) Threshold EventID (High): (0x0) Internal Peg Index: (4) Counter ID: (4) Peg Function: (_defaultPeg+0x0) FSM definition: (_SCMGSmDef+0x0) Instance Type: (0x2)
Performance Monitoring
717
queryCounters 3f 1 NONZERO Peg: (Originating Calls Abandoned) SM Instance (48). 1 Peg: (Total Registered Categories) SM Instance (0). 44 Peg: (Call Completion Attempts) SM Instance (48). 1 Peg: (Call Completion Attempts) SM Instance (77). 1 Peg: (Call Attempts) SM Instance (48). 1 Peg: (Call Attempts) SM Instance (58). 1 Peg: (Terminating Calls Ring No Answer) SM Instance (77). 1 Peg: (Collect Digits Attempts) SM Instance (48). 1 Peg: (Collect Digits Attempts) SM Instance (58). 1 Peg: (Total SM Instances In PID) SM Instance (0). 2259 Peg: (Terminating Calls Answered) SM Instance (48). 1
718
Performance Monitoring
queryCounter "SSA MSUs Received" 3e No counts for (SSA MSUs Received). Counter disabled or counts = 0.
Performance Monitoring
719
720
Performance Monitoring
Clock Cards
The commands in this chapter relate to T7000 timing.
8
Entering the command without any parameters defaults to a query. For example, the commands timeConfig and timeConfig query are equivalent Entering the command with a parameter of help displays the help string for the command For required parameters, enter the name of the parameter, =, and the value. For example, the date parameter requires a value, enter date=10/10/ 2007.
CC2
Use the commands in this section when directly connected to a CC2. Most CC2 commands follow a common syntax pattern;
If an optional parameter is omitted from a command, CC2 maintains the value currently associated with the parameter. For example, you may change the time without changing the date using the timeConfig command.
Clock Cards
721
CC2
mbusConfig help Usage: mbusConfig [help] [query] [active=<a|b|ab>] [master=<a|b>] [autoadd = <a|b|ab|none>]
NOTE: In the query <*> identifies the master card and [] indicate to which you are connected.
InSv ---Y Y
Auto-add -------Y Y
722
Clock Cards
CC2
mbusConfig (iii) mbusConfig [active=<a | b | ab>] [master=<a | b>] [autoadd = <a | b | ab | none>]
This command controls the functions of the CC2 and message bus.
Syntax [active = <a | b | ab>] Description Controls which CC2s and message buses are in service. The purpose of this command is to prepare to remove or reboot a CC2. Both CC2s can not be out of service at the same time. a activates CC2 A b activates CC2 B ab activates both CC2s [master = <a | b>] Controls which CC2 is the master. Both cards can not be the master at the same time. a makes CC2 A the master. b makes CC2 B the master. [autoadd = <a | b | ab | none>] Configures auto-add state of a message bus. At least one message bus will be in service at all times, even if both are configured not to auto-add. Y the message bus is automatically activated when its CC2 is booted. N the message bus stays out of service when the associated CC2 boots.
mbusConfig active=a master=a autoadd=ab [Removing clock card B] --> shutting down message bus B [Removal complete] Settings updated. mbusConfig active=ab master=a autoadd=ab [Adding clock card B] --> starting up message bus B [Clock card addition complete] Settings updated.
Clock Cards
723
CC2
timeConfig help Usage: timeConfig [help] [query] [time=<hh:mm:ss>] [date=<mm/dd/yyyy>] [tz=<minutes vs. GMT>] [isdst=<y|n>]
timeConfig Current GMT time is 12:59:21 Tuesday, October 09, 2007. Current LOCAL time is 13:59:21 Tuesday, October 09, 2007. Local timezone is 0 minutes relative to GMT. DST is in effect. DST is enabled for the southern hemisphere using an absolute algorithm. Local time is moved back 1 hour at 21:00 on 1 February. Local time is moved ahead 1 hour at 05:00 on 1 July.
724
Clock Cards
CC2
timeConfig (iii) timeConfig [time=<hh:mm:ss>] [date=<mm/dd/yyyy>] [tz=<minutes vs. GMT>] [isdst=<y | n>]
This command sets the time and time zone on the master CC2 on the T7000. Use local time in the 24-hour format, show whether DST is in effect.
Syntax [time=<hh:mm:ss>] Description Enter the time is in a 24 hour clock format with colons between entries: 00-24 hours 00-60 minutes 00-60 seconds [date=<mm/dd/ yyyy>] Enter the date value separated by forward slashes and in North American date format: 01-12 month (mm) 01-31 day (dd) #### year (yyyy) [tz=<minutes vs. GMT>] the difference (-720) to (840) between Greenwich Mean Time and the time zone of the T7000s location, for example -300 Eastern U.S. timezone -360 Central U.S. timezone -420 Mountain U.S. timezone -480 Pacific U.S. timezone NOTE: Use values based on the difference of local standard time versus GMT, do not adjust for DST. [isdst=<y | n>] Use one of the following: n Daylight saving time is not in effect y Daylight saving time is in effect
timeConfig time=17:37:00 date=6/19/2001 tz=-300 isdst=y Time set to 21:37:00 06/19/2001 GMT Settings updated. Current GMT time is 21:37:00 Tuesday, June 19, 2001. Current LOCAL time is 17:37:00 Tuesday, June 19, 2001. Local timezone is -300 minutes relative to GMT. DST is in effect. DST is enabled for the northern hemisphere using a relative algorithm. Local time is moved ahead 1 hour at 02:00 on the first Sunday in April. Local time is moved back 1 hour at 02:00 on the last Sunday in October.
Clock Cards
725
CC2
dstConfig (i)
dstConfig <help>
This command is used to set the rules for and enable daylight saving time (DST).
Syntax <help> Description Shows the usage string for the command.
dstConfig help Usage: dstConfig [help] [query] [enable|disable] [hemisphere=<n|s>] [h1hr=<hour>] [h2hr=<hour>] [h1date=<mm/dd>|<mm,weekno,weekday>] [h2date=<mm/dd>|<mm,weekno,weekday>]
dstConfig Current GMT time is 13:15:09 Tuesday, October 09, 2007. Current LOCAL time is 14:15:09 Tuesday, October 09, 2007. Local timezone is 0 minutes relative to GMT. DST is in effect. DST is enabled for the southern hemisphere using an absolute algorithm. Local time is moved back 1 hour at 21:00 on 1 February. Local time is moved ahead 1 hour at 05:00 on 1 July.
726
Clock Cards
CC2
dstConfig (iii) dstConfig [enable | disable] [hemisphere=<n | s>] [h1hr=<hour>] [h2hr=<hour>] [h1date=<mm/dd> | <mm,weekno,weekday>] [h2date=<mm/dd> | <mm,weekno,weekday>]
This command sets the rules for and enable daylight saving time (DST). You can enabled or disabled DST apart from provisioning the rules or you can do it at once. There are two types of DST:
Absolute DST means you set the specific days and times at which the one-hour jumps forward and backward occur. Relative DST means you set the nth occurrences of weekdays in a month to be the days at which the one-hour forward and backward jumps occur. Absolute DST and relative DST are mutually exclusive and provisioning one will overwrite the other.
Syntax Description enable activates the DST rules disable deactivates the DST rules DST rules are disabled by default until provisioned and enabled. You can use the enable option in the same dstConfig command as the rules.
[enable | disable]
[hemisphere=<n | s>]
n Northern s Southern When northern hemisphere is specified, the first half date (h1date) is the spring forward date, and the second half date (h2date) as a fall back. For the southern hemisphere, these are reversed.
[h1hr=<hour>]
h1hr 0 - 23, the hour that the DST change occurs in first half of the year (January-June). NOTE: For U.S. DST rules this value should be 2, because the changeover occurs at 2:00 AM in the Spring.
[h2hr=<hour>]
h2hr 0 - 23, the hour that the DST change occurs in second half of the year (July-December). NOTE: For U.S. DST rules this value should be 2, because the changeover occurs at 2:00 AM in the Fall.
Clock Cards
727
CC2
Description The dates have two options absolute and relative formats, for the first half of the year h1date and the second h2date. The formats for h1date and h2date must be the same. The absolute format is the absolute date: mm 1-6 for h1date and 7-12 for h2date dd 1-31 The relative format has three comma-separated entries: First entry the number of the month in which the change takes place. Second entry the week number of the month in which the change occurs (1 4 or 0 for the last week). Third entry the day of the week 0 Sunday 1 Monday 2 Tuesday 3 Wednesday 4 Thursday 5 Friday 6 Saturday
Relative for the first Sunday in April and last Sunday in October:
dstConfig enable hemisphere=n h1hr=2 h2hr=2 h1date=4,1,0 h2date=10,0,0 Settings updated. Current GMT time is 13:19:41 Tuesday, October 09, 2007. Current LOCAL time is 13:19:41 Tuesday, October 09, 2007. Local timezone is 0 minutes relative to GMT. DST is not in effect. DST is enabled for the northern hemisphere using a relative algorithm. Local time is moved ahead 1 hour at 02:00 on the first Sunday in April. Local time is moved back 1 hour at 02:00 on the last Sunday in October.
728
Clock Cards
CC2
tdmConfig help Usage: tdmConfig [help] [query] [mode=<sonet|sdh>] [revertive=<y|n>] [src1=<null|net1|net2|bits1|bits2|sync1|sync2|comp1|comp2|10mhz>] [src2=<null|net1|net2|bits1|bits2|sync1|sync2|comp1|comp2|10mhz>] [src3=<null|net1|net2|bits1|bits2|sync1|sync2|comp1|comp2|10mhz>] [src4=<null|net1|net2|bits1|bits2|sync1|sync2|comp1|comp2|10mhz>] [output1=<off|regen|net1|net2>] [output2=<off|regen|net1|net2>] [net1freq=<t1e1|8khz>] [net2freq=<t1e1|8khz>] [freerun=<y|n>]
NOTE: In the query <*> represents the reference currently selected and T identifies that an input is terminating.
tdmConfig query State = LOCKED Mode = SONET Src Selection = REVERTIVE <*> Primary Source Ref = NETREF 1 [GOOD] Secondary Source Ref = COMPOSITE 1 [GOOD] Tertiary Source Ref = BITS 2 [BAD] Network Ref 1 Freq = 1.544/2.048 MHz Network Ref 2 Freq = 1.544/2.048 MHz Clock Output 1: OFF Clock Output 2: OFF Forced Freerun (master only) = N ClkGood Enable = reflects clocks
Clock Cards
729
CC2
tdmConfig (iii) tdmConfig [mode=<sonet | sdh>] [revertive=<y | n>] [src1=<null | net1 | net2 | bits1 | bits2 | sync1 | | comp1 | comp2 | 10mhz>] [src2=<null | net1 | net2 | bits1 | bits2 | sync1 | | comp1 | comp2 | 10mhz>] [src3=<null | net1 | net2 | bits1 | bits2 | sync1 | | comp1 | comp2 | 10mhz>][src4=<null | net1 | net2 | | bits2 | sync1 | sync2 | comp1 | comp2 | 10mhz>] [output1=<off | regen | net1 | net2>] [output2=<off | | net1 | net2>] [bits1term=<none | a | b | ab>] [bits2term=<none | a ab>] [sync1term=<none | a | b | ab>] [sync2term=<none | a ab>] [comp1term=<none | a | b | ab>] [comp2term=<none | a ab>] [net1freq=<t1e1 | 8khz>] [net2freq=<t1e1 | 8khz>] [freerun=<y | n>]
This command sets the CC2 to generate timing from which the other cards on the T7000 synchronize. This timing drives the cards Time Division Multiplexing (TDM) output on T1, DS3, and OC3 (future) trunks and across the midplane voice bus.
Tip
Put network timing references on two separate cards. If one card goes down, timing is derived from the reference on the alternate card.
This command allows for up to four source references for T7000 alignment and the two clock outputs. The source references are the following:
Set the clock reference after the OpenManager is installed and configured.
Syntax [mode=<sonet | sdh>] Description Specifies the timing mode of the T7000: sonet Synchronous Optical Network for North American networks sdh Synchronous Digital Hierarchy for European/international networks The T7000 cannot have a timing mode that is incompatible with any of the selected source references.
730
Clock Cards
CC2
Description 1 yes, causes the CC2 to always prefer the highest priority available timing reference, even if it has to switch away from another valid reference. 2 no or non-revertive mode makes the CC2 stay on a valid reference until it fails, regardless of priority.
[src1=<null | net1 | net2 | bits1 | bits2 | sync1 | sync2 | comp1 | comp2 | 10mhz>] [src2=<null | net1 | net2 | bits1 | bits2 | sync1 | sync2 | comp1 | comp2 | 10mhz>] [src3=<null | net1 | net2 | bits1 | bits2 | sync1 | sync2 | comp1 | comp2 | 10mhz>] [src4=<null | net1 | net2 | bits1 | bits2 | sync1 | sync2 | comp1 | comp2 | 10mhz>]
These are the four timing references (src1 - 4) of the T7000. Provision references in order from primary to quaternary. Provision the sources out of sequence is not allowed, for example if the primary (src1) source is null, the remaining sources can not be provisioned. null disables the source net1 a derived network reference provided to the CC2 by front cards in T7000 (1.544 MHz SONET/ 2.048 MHz SDH / 8 KHz) net2 another derived network reference, see net1 bits1 Building Integrated Timing Supply (BITS) clocks are 1.544 MHz signals and use the timing from North America on T1s. A BITS clock connects to the mini DB9 connector. bits2 another BITs reference, see bits1 sync1 in SDH mode, BITS inputs are disallowed, and E1 sync pulse inputs are available. An E1 sync pulse clock is a 2.048 MHz signal on an E1 trunk. An E1 sync pulse clock connects to the mini DB9 connector. sync2 another E1 sync pulse clock, see sync1 comp1 a composite clock signal that is a bipolar clock signal that runs at 64 KHz. Embedded within the signal is a bipolar violation every 8 clocks or 64+8 KHz. Composite clocks connect to the CC2 though the mini DB9 connector, typically from a Global Positioning System (GPS) unit. comp2 another composite clock signal, see comp1 10mhz the 10 MHz sine wave that connects through the BNC connector
Clock Cards
731
CC2
Syntax [output1 = <off | regen | net1 | net2>] [output2 = <off | regen | net1 | net2>]
Description Configures clock outputs on CLK I/O ports 1 and 2. off disables clock output, this is currently the only supported configuration regen uses DS1 BITS or E1 sync pulse clock when netref1 and netref2 are not available, this configuration is not supported net1 routes network reference 1 to the specified CLK I/O output (clock card 1 or clock card 2), this configuration is not supported net2 routes network reference 2 to the specified CLK I/O output (clock card 1 or clock card 2), this configuration is not supported
Configures termination of the bits input on the CLK I/O port 1 (bits1term) or 2 (bits2term). none neither CC2 should terminate the bits input a terminate the bits input on CC2 A b terminate the bits input on CC2 B ab terminate the bits1 on both CC2s
Configures termination of the sync input on the CLK I/O port 1 (sync1term) or 2 (sync2term). none neither CC2 should terminate the bits input a terminate the bits input on CC2 A b terminate the bits input on CC2 B ab terminate the bits1 on both CC2s
Configures termination of the comp input on the CLK I/O port 1 (comp1term) or 2 (comp2term). none neither CC2 should terminate the bits input a terminate the bits input on CC2 A b terminate the bits input on CC2 B ab terminate the bits1 on both CC2s
[net1freq = <t1e1 | 8khz>] Configures the frequencies of network references 1 (net1freq) and 2 (net2freq). [net2freq = <t1e1 | 8khz>] t1e1 translates to 1.544 MHz in SONET mode and 2.048 MHz in SDH mode. 8khz tells the CC2 to expect network reference timing at a frequency of 8 KHz. Assumes that the front card is converting the rate before providing the reference to the CC2s.
732
Clock Cards
CC2
Description Forces the master CC2 into freerun mode, this puts the T7000 into local timing mode. y puts the T7000 into freerun mode n the T7000 returns to timing from valid source references
tdmConfig freerun=y
Clock Cards
733
CC2
bitsConfig help Usage: bitsConfig [help] [query] [bits1frame=<esf|d4>] [bits1line=<b8zs|ami>] [bits1lbo=<0|133|266|399|533|-7.5|-15|-22.5>] [bits2frame=<esf|d4>] [bits2line=<b8zs|ami>] [bits2lbo=<0|133|266|399|533|-7.5|-15|-22.5>]
bitsConfig query Frame format Line coding Line build out Alarm Status LOS LOF AIS BITS 1 ESF B8ZS 0-133 1 1 0 BITS 2 ESF B8ZS 0-133 1 1 0
734
Clock Cards
CC2
bitsConfig (iii) bitsConfig [bits1frame=<esf | d4>] [bits1line=<b8zs | ami>] [bits1lbo=<0 | 133 | 266 | 399 | 533 | -7.5 | -15 | -22.5>] [bits2frame=<esf | d4>] [bits2line=<b8zs | ami>] [bits2lbo=<0 | 133 | 266 | 399 | 533 | -7.5 | -15 | -22.5>]
This command configures the BITS of the T1 framers that physically connect to the CC2 BITS1 and BITS2 connectors. Provision the BITS configuration when using a bits1 or bits2 as a TDM reference.
NOTE: The BITS configuration applies to the master and slave CC2.
Description Configures the frame format for BITS 1 (bits1frame) or BITS 2 (bits2frame). esf Extended-Superframe format, default setting d4 Superframe format Configures the line coding format for BITS 1 (bits1line) or BITS 2 (bits2line). b8zs Bipolar 8 Zero Substitution, default setting ami Alternate Mark Inversion Configures the line build out for BITS 1 (bits1lbo) or BITS 2 (bits2lbo). 0 0-133 ft. or 0 dB 133 133-266 ft. 266 266-399 ft. 399 399-533 ft. 533 533-655 ft. -7.5 -7.5 dB -15 -15 dB -22.5 -22.5 dB
[bits1lbo=<0 | 133 | 266 | 399 | 533 | -7.5 | -15 | -22.5>] [bits2lbo=<0 | 133 | 266 | 399 | 533 | -7.5 | -15 | -22.5>]
Clock Cards
735
CC2
sysStatus
sysStatus
The command shows the state of all devices monitored by system audits. This command does not have parameters
sysStatus OCX Chassis Data -P/N: 893-0002-001 Rev: B00 S/N: S200150
Fuse status: OK Power board A status: OK Power board B status: OK Local Clock Good: Y Partner Clock Good: Y Current battery voltages: Va = 53.632v Vb = 0.000v Current board temperatures: Ta = 31.5 deg. C. Tb = 23.5 deg. C. Current fan speeds, temps, and states: Fan Speed(RPM) Fault? 1 2533 N 2 2607 N 3 2333 N 4 2440 N Override state: normal Inlet temp : 23.50 deg. C. Outlet temp 1: 27.02 deg. C. Outlet temp 2: 15.21 deg. C. status bit 1: 0 status bit 0: 0 overtemp?: N tray failure?: N
736
Clock Cards
CC2
testLEDs
testLEDs <1 | 0>
This command tests all LEDs and relays in the T7000. The LED test only tests the LEDs on the CC2 running the test and on the T7000 chassis.
Syntax <1 | 0> Description 1 to begin the LED test 0 to end the LED test
testLEDs 1
Clock Cards
737
CC2
738
Clock Cards
A
sp 12/ 13 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 sp 13/ 14 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 sp 14/ 15 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 sp 15/ 16 360 361 362 363 364 365 366 367 369 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 sp 16/ 17 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 sp 17/ 18 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 sp 18/ 19 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 sp 19/ 20 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479
The following table lists which trunks (timeslots) belong to which spans. This table presents the information in decimal format.
sp 0/ 1 trunk 0 trunk 1 trunk 2 trunk 3 trunk 4 trunk 5 trunk 6 trunk 7 trunk 8 trunk 9 0 1 2 3 4 5 6 7 8 9 sp 1/ 2 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 sp 2/ 3 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 sp 3/ 4 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 sp 4/ 5 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 sp 5/ 6 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 sp 6/ 7 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 sp 7/ 8 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 sp 8/ 9 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 sp 9/ 10 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 sp 10/ 11 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 sp 11/ 12 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287
trunk 10 10 trunk 11 11 trunk 12 12 trunk 13 13 trunk 14 14 trunk 15 15 trunk 16 16 trunk 17 17 trunk 18 18 trunk 19 19 trunk 20 20 trunk 21 21 trunk 22 22 trunk 23 23
739
1BA 1D2 1BB 1D3 1BC 1D4 1BD 1D5 1BE 1D6 1BF 1C0 1C1 1D7 1D8 1D9 1DA 1DB 1DC 1DD 1DE 1DF
18C 1A4 18D 1A5 18E 18F 190 191 192 193 194 195 196 197 1A6 1A7 1A8 1A9
1AA 1C2 1AB 1C3 1AC 1C4 1AD 1C5 1AE 1C6 1AF 1C7
740
Using Hexadecimal
Using Hexadecimal
Certain CLI parameters are entered in hexadecimal format. Use the hexadecimal charts or Hexadecimal Calculator on page 744 to convert decimal values to hexadecimal values and vice versa.
0 0 1 2 3 4 5 6 7 8 9 A B C D E F
000 016 032 048 064 080 096 112 128 144 160 176 192 208 224 240
Digits 0-9 with their usual meaning Letters A-F (or a-f) represent hexadecimal digits with values of (decimal) 10 to 15
3
003 019 035 051 067 083 099 115 131 147 163 179 195 211 227 243
1
001 017 033 049 065 081 097 113 129 145 161 177 193 209 225 241
2
002 018 034 050 066 082 098 114 130 146 162 178 194 210 226 242
4
004 020 036 052 068 084 100 116 132 148 164 180 196 212 228 244
5
005 021 037 053 069 085 101 117 133 149 165 181 197 213 229 245
6
006 022 038 054 070 086 102 118 134 150 166 182 198 214 230 246
7
007 023 039 055 071 087 103 119 135 151 167 183 199 215 231 247
8
008 024 040 056 072 088 104 120 136 152 168 184 200 216 232 248
9
009 025 041 057 073 089 105 121 137 153 169 185 201 217 233 249
A
010 026 042 058 074 090 106 122 138 154 170 186 202 218 234 250
B
011 027 043 059 075 091 107 123 139 155 171 187 203 219 235 251
C
012 028 044 060 076 092 108 124 140 156 172 188 204 220 236 252
D
013 029 045 061 077 093 109 125 141 157 173 189 205 221 237 253
E
014 030 046 062 078 094 110 126 142 158 174 190 206 222 238 254
F
015 031 047 063 079 095 111 127 143 159 175 191 207 223 239 255
741
Using Hexadecimal
742
Using Hexadecimal
Hexadecimal Number
743
Using Hexadecimal
Hexadecimal Calculator
Most Windows operating systems come with a calculator application. To use the calculator to determine hexadecimal values:
Step
1
Action From the Start button, select Programs > Accessories > Calculator. The calculator appears.
2 3 4 5
Select View>Scientific. Select Dec. Enter the decimal value to convert. For example, 154. Select Hex. The hexadecimal value appears. For example, 9A.
744
Appendix B: Protocols
This appendix gives a brief overview of various protocols supported by the switch.
Trunk Protocols
For complete details, see Appendix A of the T7000 Provisioning Guide.
FGC
The Feature Group C (FGC) Bell I protocol supports direct-dialed traffic, uses 1 digit for ANI information, 3/10 digits for called party, and 2-stage outpulsing; for example: 911/NPA-Nxx-XXXX and 7 digit ANI.
FGCB2
The Feature Group C Bell II (FGCB2) protocol supports direct-dialed traffic, 2 digits for ANI information and 3/10 digit called number
FGCOS
The Feature Group C Operator Services (FGCOS) protocol supports intraLATA OS calls. This protocol is used for intraLATA toll and assistance calls to a BCC. FGCOS uses the same signaling sequence as FGC.
FGCOF
The Feature Group C Operator Flexible (FGCOF) protocol is based on FGCOS, but has the ability to customize the Stage 1 and Stage 2 outpulsing for any call type.
FGCVZOS
The Feature Group C Verizon Operator Services (FGCVZOS) supports Verizon operator group customization for FGC on top of FGCOS.
FGD
The Feature Group D (FGD) protocol supports 1+ long distance dialing (equal access) and 10 digit ANI.
Appendix B: Protocols
745
FGDAT
The Feature Group D Access Tandem (FGDAT) protocol supports the switch connecting to an AT with 1+ long distance dialing (equal access) and 10 digit ANI on CAS trunks.
FGDATOS
Feature Group D Access Tandem Operator Services (FGDATOS) supports interLATA OS calls. This protocol is used for interLATA operator services and/or directory assistance call types for domestic Interexchange Carriers. FGCOS uses the same singling sequence as FGDAT.
FGDATEO
The Feature Group D Access Tandem to End Office (FGDATEO) protocol supports the switch in the role of an AT and the far end in the role of an EO using FGD.
FGDEOAT
The Feature Group D End Office to Access Tandem (FGDEOAT) protocol supports the switch in the role of an EO and the far end in the role of an AT using FGD.
FGDEOIC
The Feature Group D End Office to Interexchange Carrier (FGDEOIC) protocol supports the switch in the role of an EO and the far end in the role of an IC using FGD.
FGDICEO
The Feature Group D Interexchange Carrier to End Office (FGDICEO) protocol supports the switch in the role of an IC and the far end in the role of an EO using FGD. The FGDICEO protocol is not symmetrical, rather the terminating sequence is FGD.
FGDINC
Feature Group D for International and Carriersupports connecting to a legacy/ tandem switch. This protocol expects: two stage on international (wink-outpulsewink-outpulse), single stage domestic (wink-outpulse-wink).
FXO
Foreign Exchange Officefor trunks that connect to an FXO and provide dial tone to a subscriber or trunks in a multi-line hunt group.
746
Appendix B: Protocols
Trunk Protocols
WSMF2WAY
The Wink Start Multi-Frequency Two Way (WSMF2WAY) protocol supports the following calls on inter-exchange trunks: 1+10D, 101XXX+10D, 0+10D, 0, 011+Country Code (CC)+international number, 01+CC+international number operator assisted.
DS
The Digital Signal (DS) protocol supports PRI connections on the network and user side.
SS7
The SS7 protocol supports signaling for SS7 trunk groups.
FXO
The Foreign Exchange Office (FXO) protocol supports trunks that connect to an FXO and provide dial tone to a subscriber or trunks in a multi-line hunt group.
DIDMF
The Direct Inward Dialing, Multi-Frequency (DIDMF) protocol supports CAS trunks that connect to a PBX.
DIDDTMF
The Direct Inward Dialing, Dual Tone Multi-Frequency (DIDDTMF) protocol supports CAS trunks that connect to a PBX.
Appendix B: Protocols
747
Other Protocols
IDT
The Integrated Digital Terminal (IDT) protocol supports Interface Groups that connect the switch to an RDT and use GR-303 protocol.
MGCP
Media Gateway Control Protocol (MGCP) supports multimedia conferences over IP (Internet Protocol). MGCP is an ASCII-based, application-layer control protocol that establishes, maintains, and ends calls between two or more
terminations. SIP
The Session Initiated Protocol (SIP) supports calls using Voice over Internet Protocol (VoIP).
748
Appendix B: Protocols
You can execute CLI commands locally from your switch room, or you can log on to the switch remotely. Local access requires a PC running a terminal emulation program and a physical connection to the craft port on a T700 card. Remote access requires an Internet connection, and a PC running either a terminal emulation program with a telnet client, or the Open Manager Client. In this chapter:
Determining the IP Address of a Card on the Switch Terra Term Professional Procomm Plus Open Manager Telnet HyperTerminal
749
The BOOTP table shows the IP address of every card that boots from ISEHouse. The cards are listed under the DeviceName column and the IP address of that card is listed under the IP Address column. For example, the first line of the above figure shows that Baltimore CCB (Clock Card B) has an IP address of 179.19.164.25.
750
Action From the Network View of the OM click Network View. Right-click the switch graphic to which you want to connect. A pop-up menu appears.
Select Properties.
The primaryIP attribute contains the IP address of the card that connects to the OM.
751
Terra Term Professional is an open source Windows terminal emulator and telnet client that can be used for local or remote switch access. Taqua distributes Terra Term Professional with new software releases.
Local Access
To use Terra Term Professional for local access, connect a serial cable from the COM port of a PC to the craft port of a BIC, LTC, PIC, PIC II, TIC,TICII or clock card. Next, connect to that card using the Terra Term Professional software.
Terra Term Professional Local Access Prerequisites Either a DB-9 male to DB-9 female serial cable, or a DB-25 male to DB9 female serial cable, depending on the COM port connection on the PC.
Action Connect the male end of the serial cable to an unused COM port on the PC. Connect the female end of the serial cable to a craft port on the card with which you want to communicate.
752
Local Access
Step
3
Action In Windows: Start > Programs > Accessories > Terra Term Pro The New Connection dialog appears.
Click the Serial radio button and select the same COM port you chose in step 1.
Click OK.
753
Step
5
Action Next, configure the serial port settings. Select Setup > Serial port...
From the Port drop-list, select the same COM port you chose in step 1.
7 8 9 10 11 12
From the Baud rate drop-list select 38,400. From the Data drop-list select 8. From the Parity drop-list select None. From the Stop drop-list select 1. From the Flow control drop-list select None. Leave the Transmit delay msec/char and msec/line at 0.
754
Local Access
Step
13
Note that the Com port and the baud rate are now part of the window title.
14
755
Step
15
Click OK
16
Note that the COM port, baud rate, and terminal type are part of the window title.
17
Press the <Enter> key several times to get the login prompt. Enter the login name and password of a previously provisioned user.
756
Remote Access
Remote Access
To use Terra Term Professional for remote access, connect the PC to the Internet. Next, connect to a card on the switch using the Terra Term Professional software.
Terra Term Professional Remote Access Prerequisites A PC running Windows 9x/NT/2000/XP with: a connection to the Internet an installed copy of Terra Term Professional Remote Connection to the Switch
To make a remote connection to the Switch using Terra Term Professional:
Step
1
Action In Windows: Start > Programs > Accessories > Terra Term Pro The New Connection dialog appears.
The TCP/IP radio button is selected by default. In the Host field, enter the IP address of the card you want to connect to. To determine this address, see Determining the IP Address of a Card on the Switch on page 750. In the Service field, select Telnet. Leave the other fields to their default values. Click OK.
757
Step
2
Note that the IP Address is now part of the window title. Before logging on, make sure the terminal type is configured properly
3
758
Remote Access
Step
4
Click OK
5
You may need to press the <Enter> key several times to get the login prompt. Enter the login name and password of a previously provisioned user.
759
Procomm Plus
Procomm Plus
Procomm Plus is a Windows terminal emulator and telnet client that can be used for local or remote switch access. Taqua distributed this program with earlier versions of the switch software.
Local Access
To use Procomm Plus for local access, connect a serial cable from the COM port of a PC to the craft port of a BIC, LTC, PIC, PIC II, TIC, TICII or clock card. Next, connect to that card using the Procomm Plus software
Procomm Plus Local Access Prerequisites Either a DB-9 male to DB-9 female serial cable, or a DB-25 male to DB9 female serial cable, depending on the COM port connection on the PC.
Action Connect the male end of the serial cable to an unused COM port on the PC. Connect the female end of the serial cable to a craft port on the card with which you want to communicate. In Windows: Start > Programs > Procomm Plus > Data Terminal.
760
Local Access
Step
4
Ensure the quick status line has the following settings: Terminal type = VT100 port selection = direct connect-ComX (where X corresponds to the COM port you chose in step 1.) speed = 38400 port settings = N81 If not, click on the appropriate part of the quick status line and change.
5
Follow steps 6 through 9 on page 762 to set up a capture file, otherwise skip to step 10 on page 762 to log in.
761
Procomm Plus
Step
6
Check the box Query for the file name when capture is started. After the change is made the screen Capture File appears.
8 9
To open the capture file go to Data > Capture File. Type a name to specify the Capture file Click OK
10
You may need to press the <Enter> key several times to get the login prompt. Enter the login name and password of a previously provisioned user. The login screen appears.
762
Remote Access
Remote Access
To use Procomm Plus for remote access, connect the PC to the Internet. Next, connect to a card on the switch using the Procomm Plus software.
Procomm Plus Remote Access Prerequisites A PC running Windows 9x/NT/2000/XP with: a connection to the Internet an installed copy of Procomm Plus Remote Connection to the Switch
To make a remote connection to the Switch using Procomm Plus:
Step
1 2
Action In Windows: Start > Programs > Procomm Plus > Telnet. The Procomm Plus telnet window appears.
Ensure the quick status line has the following settings: Terminal type = VT100 port selection = direct connect-Telnet If not, click on the appropriate part of the quick status line and change.
763
Procomm Plus
Step
3
Action Select >Options>Data Options>Setup Files> Setup button for capture. Check the box Query for the file name when capture is started. After the change is made the screen Capture File appears.
Follow steps 6 through 9 on page 765 to set up a capture file, otherwise skip to step 10 on page 765 to log in. Select >Options>Data Options>Setup Files. The Setup dialog appears
764
Remote Access
Step
7
Check the box Query for the file name when capture is started. After the change is made the screen Capture File appears.
8 9
To open the capture file go to Data > Capture File. Type a name to specify the Capture file Click OK
10 11
To Telnet to a T7000 card use the Direct Connect Option. Go to Data > Manual Connect. The manual connect dialog appears.
Enter the IP address of the switch you want to connect to. To determine this address, see Determining the IP Address of a Card on the Switch on page 750.
765
Procomm Plus
Step
12
You may need to press the <Enter> key several times to get the login prompt. Enter the login name and password of a previously provisioned user.
766
Remote Access
Remote Access
Open Manager Telnet Remote Access Prerequisites A PC running Windows 9x/NT/2000/XP with a connection to the Internet an installed copy of the Open Manager Client Remote Connection to the Switch
To make a remote connection to the Switch using Open Manger Telnet:
Step
1 2
Action From the Network View of the OM click Network View. Right-click a switch graphic to which you want to connect. A pop-up menu appears.
NOTE: The method always connects to the same card the OM connects to.
4
After the login prompt appears, enter the login name and password of a previously provisioned user.
767
HyperTerminal
HyperTerminal
HyperTerminal is a Windows terminal emulator that can be used for local switch access. Microsoft bundled HyperTerminal with all versions of Windows from Windows 95 through WIndows XP.
Local Access
To use Hyper-Terminal for local access, connect a serial cable from the COM port of a PC to the craft port of a BIC, LTC, PIC, PIC II, TIC,TICII or clock card. Next, connect to that card using the Hyper-Terminal software.
Hyper-Terminal Local Access Prerequisites Either a DB-9 male to DB-9 female serial cable, or a DB-25 male to DB9 female serial cable, depending on the COM port connection on the PC.
Action Connect the male end of the serial cable to an unused COM port on the PC. Connect the female end of the serial cable to a craft port on the card with which you want to communicate.
768
Local Access
Step
3
Action In Windows: Start > Programs > Accessories > HyperTerminal > HyperTerminal (ensure it is the Hyper-Terminal entry without the .ht extension). The Connection Description dialog appears.
4 5
In the Name field enter OCXdirect or the desired name. Click OK. The Connect To dialog appears.
From the Connect using drop-list, select the same COM port you chose in step 1.
769
HyperTerminal
Step
7
8 9 10 11 12 13
From the Bits per second drop-list select 38,400. From the Data bits drop-list select 8. From the Parity drop-list select None. From the Stop bits drop-list select 1. Set flow control to None. Click OK. A blank Hyper-Terminal window appears.
770
Local Access
Step
14
15 16 17
Click the Settings tab. From the Emulation drop-list, select VT100. Click OK. A blank Hyper-Terminal window appears.
18
Press the <Enter> key several times to get the login prompt. Enter the login name and password of a previously provisioned user.
771
HyperTerminal
772
Index
Numerics
7-Digit Dialing Across NPA Boundaries 408 911 over CAS 136
A
Access Tandem 525 Account Codes 154 activateCfb 563 activateCfd 564 activateCff 565 activateCfv 562 activateLinkSet 639 activating call forwarding busy 563 call forwarding dont answer 564 call forwarding fixed 565 call forwarding variable 562 EOC 357 link set 639 adding codec lists 425 hosts 429 RDTs 351 SCCP node 484 SS7 link set 478 SS7 links 480 SS7 networks 475 SS7 routes 482 tasks 597 Adding Escape Code Pattern Profiles 144, 157 addLea 181 addLeaCase 187 addLeaSpan 183 addPretranslation 224 Address 35 addTask 597 adduser 48 addVoiceChnl 189
Advanced Intelligent Network 138 AIN 138, 144, 157 Adding Service Patterns 142 Creating AIN Service Pattern Profiles 140 Creating AIN Trigger Profiles 147 Deleting AIN Trigger Profiles 151 Deleting Service Profiles 153 Provisioning AIN 139, 155 aissp 686, 704 alarm history querying 54 alarmHistory 54 alarms editing 53 provisioning 53 querying 54, 56 querying definitions 55 Allowed list 415 allowNX64 297 alternate routing schedules querying 81 ANI Replacement 347 announcements querying 94 Application Domain Object 29 applying patch 660 applying patch 660 applyPatch 660 assign call forwarding fixed 567 assignCff 567 assignSubVM 560 AT 525 attributes querying 86 querying all 85 audio loading on the switch 602 unloading from the switch 603 auditTimers 35
Index
773
B
backwardProgressIndication 301 bChannelAvailabilityProcedure 298 BearerGroup 163 Bearergroup bearerGrpKey 371, 441, 449 beingPorted BEING_PORTED 538 BEING_PORTED_OUT 538 NOT_BEING_PORTED 538 bitsConfig 734, 735 BLI 339 blockCPN 300 blocking 640 circuits 648 links 640 blockLink 640 BLV 339 busy 629
C
CAC_FROM_CARRIER 389 CALEA addLea 181 addLeaCase 187 addLeaSpan 183 addVoiceChnl 189 changePenPW 179 createPenGrp 176 deletePenGrp 177 order of provisioning 175 purgePenLog 195 queryLea 131 queryLeaCase 132 queryPenCommands 127 queryPenData 130 queryPenGrp 128 queryPenLog 133 queryPenTarget 129 removeLea 182 removeLeaCase 188 removeLeaSpan 184 removeVoiceChnl 190 resizePenLog 195
setCaseAttr 194 setLeaAttr 186 setPenAttr 178 setPenGroupTimer 180 startCaseMonitor 192 startLeaMonitor 185 startPenMonitor 191 stopCaseMonitor 193 stopLeaMonitor 185 stopPenMonitor 191 CALL 36 Call Content (CC) Surveillance 174 Call Data (CD) Surveillance 174 call forwarding 553 call forwarding block querying 554 call forwarding busy activating 563 deactivating 563 call forwarding dont answer activating 564 deactivating 564 call forwarding fixed activating 565 assigning 567 deactivating 566 querying 555 removing 567 call forwarding variable activating 562 deactivating 562 querying 553 CALL_BACK 533 CALL_FORWARD_BUSY 533 CALL_FORWARD_FIXED 534 CALL_FORWARD_LOCAL 534 CALL_FORWARD_NOANS 534 CALL_FORWARDING 533 CALL_REJECT 534 CALL_RETURN 534 CALL_TRANSFER 534 CALL_WAITING 534 CALL_WAITING_CALLER_ID 534 CALLER_ID 533 CALLER_ID_BLOCK 533 CALLER_ID_UNBLOCK 533 calling name TCAP querying 654 CALLING_NAME 533 CALLING_NAME_QUERY_REQUIRED 389 callingNameDisplay 296 calls
774
Index
logging active 670 querying active 66 querying history 67 resetting simulated calls on a line 38 resetting history 670 simulating 739, 740 starting simulated 39 stopping simulated 40 stopping simulated calls on a line 38 cancelRDTCmd 650 card description 29 card number 41 card type 41 CardConfiguration 163, 165 cards checking connections 604 querying status 77 carrier access codes querying 94 Carriers 196 carriers querying 208 CAS 911 136 E911 136 CAS Options networkServices 248 numOfDIDDigits 247 CAS trunk groups 235 CAS trunks modifying protocols 222 Case Monitoring 175 CDRs querying status 89 viewing amount in buffer 91 changeAlarmDefAttr 53 changePenPW 179 Channel Associated Signaling trunk groups 235 ChargeDelay 244, 332 chargingOffice 336 checking card connections 604 circuit continuity check generating 643 circuitBlock 648 circuitCCR 643 circuitGBlock 644 circuitGReset 644 circuitGUnblock 646 circuitQuery 647
circuitReset 646 circuits blocking 648 querying 647 resetting 646 resetting (group) 644 testing 648 unblocking 648 unblocking (group) 646 circuitTest 648 circuitUnblock 648 Clear Channel trunk groups 252 clearSdList 573 cmdfileEchoOff 36 cmdfileEchoOn 36, 37 codec lists adding 425 creating 425 querying 99 CodecProfile 427 CodecProfileList 425 configuring simulated lines 37 connecting simulated cards 42 simulated spans 42 connections checking card 604 querying 76 contiguousNX6 297 continuityProcedure SS7 Options continuityProcedure 338 continuityTestFrequency 336 Controlled Slip Second 671, 686, 690, 704 COT generating 643 country codes deleting 396 removing 396 craft connections querying 78 create sipVMS 593 createHostIPAddr 429 createLink 480 createLinkSet 478 createPenGrp 176 createPretranslation 223 createProfile 231 createRDT 351 createSS7Network 475 createSS7Route 482
Index
775
creating codec lists 425 hosts 429 RDTs 351 SCCP node 484 SS7 link set 478 SS7 links 480 SS7 networks 475 SS7 routes 482 Creating Escape Code Pattern Profiles 144, 157 CriticalDigitTimeout 391 cs_config 37 cs_dispstats 38 cs_finish 38 cs_reset 38 cs_settimer 39 cs_start 39 cs_stop 40 CSSP 671, 686, 690, 704 cssp 686, 704 Ctrl + D 46 current processes querying 605 CUSTOM_REPLACE_AIN 389 cvl 686, 704 cvp 686, 704
D
DA_ONLY 271, 305, 322, 343 database querying by manager 83 saving 599 database master querying 83 databases removing 599 dbFlash 599 dbFlashSize 600 d-channels querying 113, 114 deactivateCfd 564 deactivateCff 566 deactivateLinkSet 639 deactivateSCF 568 deactivateSubVM 561 deactivating call forwarding busy 563 call forwarding dont answer 564 call forwarding fixed 566 call forwarding variable 562
deactiveCfb 563 deactiveCfv 562 decommission 52 defaultDN 318 delCountryCodes 396 deleteLink 481 deleteLinkset 479 deleteNode 477 deletePCMap 501 deletePenGrp 177 deletePretranslation 230 deleteSdInfo 572 deleteSS7Network 475, 476 deleteSS7Route 483 deleting country codes 396 international codes 395, 396 point code mapping 501 SCCPNode 487 SS7 link set 479 SS7 links 481 SS7 networks 475, 476 SS7 node 477 SS7 routes 483 tasks 599 Deleting Escape Code Pattern Profiles 144 Denied list 415 deprovisioning RDT lines 354 deprovisionRD 354 devices contents 603 dial 40 Digital Signal Processor description 29 disable 630 displaySubBusGrps 93 dispLocTS 40 querying locked lines 631 dispMidTS 41 DS1 setting loopback 652 DS1 lines syncing 356 DS3 29 DSP description 29 dstConfig 726, 727 dumpTDM 41
776
Index
E
E911 over SS7 136 Process 136 EAS 408 echoing starting script 36, 37 stopping script 36 editing alarms 53 enable 630 ENABLE_822_SAC 389 ENABLE_833_SAC 389 ENABLE_844_SAC 389 ENABLE_855_SAC 389 ENABLE_866_SAC 389 ENABLE_877_SAC 389 enableEvent 57 enabling events 57 ENHANCED_CF_NOANS 535 env 41 environment 41 EOC activating 357 EOC and TMC 650 inhibiting 649 querying 113 reconnecting 651 releasing 45 resyncing 651 uninhibiting 649 Equipment 213 esap 686, 704 esbp 686, 704 esl 686, 704 esp 686, 704 event log purging 58 querying 60 setting size 58 stopping 59 eventLogSize 58 events enabling 57 managing 57 posting 58 purging event log 58 querying event log 60 setting log size 58 ExceptionRecoveryTime 391 Extended Area Service 408
F
facility querying 69 FAIL_UNKNOWN_DIGIT_PATTERN 389 fault manager querying 76 setting to automatic 632 setting to manual 632 fc 686, 704 FEI setting IP address 422 FEI options setting 424 fgc911MakeFirstSecond 248 FirstDigitTimeout 391 flash memory size setting 600 FlashDuration 245 FlashInterval 244 forceDbMaster 606 ForwardDisconnectTime 244 FTRS addPretranslation 224 createPretranslation 223 createProfile 231 deletePretranslation 230 queryPretransByDigitPtn 121 queryPretranslation 120 removePretranslation 229
G
generating circuit continuity check 643 COT 643 getMaxEventTransmit 57 getPMCurrent 700 getPMInterval 701 getPMStatus 699 getPMTCA 703 getSLSMap 106 glareControl 247, 336 GR-303 649 GR-303 Interfaces trunk groups 258 GuardTime 244, 332
H
HDLC description 29
Index
777
Hexadecimal lines 743 hexadecimal 741 High-level Data Link Control description 29 hosts adding 429 creating 429 hu 42 Hunt Groups Circular Hunting 273 Regular hunting 273 Uniform Call Distribution 273 Hunt groups 273 hunt groups querying 73 HyperTerminal 768
L2T3_period 503 L2T4e_period 503 L2T4n_period 503 L2T5_period 503 L2T6_period 503 L2T7_period 503 L2Tie_period 503 L2Tin_period 503 L2TX_abatement 507 L2TX_discard 508 L2TX_onset 506 L3T1_period 503 L3T10_period 504 L3T12_period 504 L3T13_period 504 L3T14_period 504 L3T15_period 504 L3T16_period 504 L3T17_period 504 I L3T19_period 504 L3T2_period 503 implicitChannelId 299 L3T20_period 504 INBOUND_ANI_REQUIRED 389 L3T21_period 504 inhibiting L3T22_period 504 EOC and TMC 649 L3T23_period 504 links 641 L3T24_period 504 inhibitlink 641 L3T25_period 504 inhibitPath 649 L3T26_period 504 InterDigitTimeout 391 L3T27_period 504 Interexchange Carrier 525 L3T28_period 505 Interface trunk groups 258 L3T29_period 505 INTERLATA_RESTRICTIONS_APPLY_TO_CAC L3T3_period 504 389 L3T31_period 505 international codes L3T33_period 505 deleting 395, 396 L3T34_period 505 removing 396 INTERNATIONAL_RESTRICTIONS_APPLY_TO_C L3T4_period 504 L3T5_period 504 AC 389 L3T6_period 504 INTRALATA_RESTRICTIONS_APPLY_TO_CAC L3T7_period 504 389 L3T8_period 504 IP trunk groups 307 LCFO_Duration 246 ipConfig 605 LEA Monitoring 175 IXC 525 LEDs querying 78 K line description 29 keepIncoming7dNOA 340 Line Numbering hexadecimal 743 L lines modifying protocols 222 L2T1_period 503 removing from service 628 L2T2_period 503 restoring to service 628
778
Index
link sets activating 639 links 640 inhibiting 641 linkSetStatus 107 linkSpan 42 linkStatus querying SS7 links 107 LNP Route List 517 loadAudio 602 loading scripts 31 loading, patch 659 loadPatchArchive 659 Local Access HyperTerminal 768 Procomm Plus 760 Terra Term Professional 752 locked lines querying 631 locked trunks 631 logActiveCalls 670 logging active calls 670 login 46 LongDurationCdrTimeout 391 loopback setting DS1s 652 lossl 686, 704 ls 603
MOPC setting 499 mplicitInterfaceIdi 301 multiple point codes setting 499
N
NANP Route List 519 Network Gateway Endpoint 459 networkServices 248, 339 PRI Options networkServices 297 SS7 Options sendACTNS 340 TNS 339 Transit Network Selection 339 NO_DA 271, 305, 322, 343 NO_DA_INTERLATA 271, 305, 322, 343 NO_DA_INTRALATA 271, 305, 322, 343 NO_INBOUND_PAYSTATION 343 NO_INBOUND_WITHOUT_ANI 305, 322, 343 NO_INTERLATA 322, 343 NO_INTERNATIONAL 271, 322, 343 NO_INTRALATA 271, 305, 322, 343 NO_OS_INTERLATA 271, 305, 322, 343 NO_OS_INTERNATIONAL 271, 305, 322, 343 NO_OS_INTRALATA 271, 305, 322, 343 NO_OSDIALED 271, 305, 322, 343 NO_OSSTATION 271, 305, 322, 343 nodeStatus 108 numOfDIDDigits 247, 299
M
managing events 57 manualClear 52 MaxWinkDuration 245 mbusConfig 722 media stream parameters 431 MediaParam 431 memberOrigination 276 MGCP 358 MGCP trunk groups 359 MinFlashHookTime 244 MinWinkDuration 245 modifying CAS trunk protocols 222 line protocols 222 modifyPretranslation 229 modifyProtocol 222
O
Object Identifier description 30 off-hook 43 OffHookDigMax 245 OffHookDigMin 245 office parameters querying 388 Office Parms country codes 396 OSS Information Digits 393, 395 oh 43 OID 30 OIDs description 30 OLIRequired 338 on-hook 42
Index
779
OnHookDigMax 245 OnHookDigMin 245 Open Manger Telnet 767 originalNumberOption 301 OS_ONLY 271, 305, 322, 343 Outgoing Signal Customization Provisioning Process 348 Outgoing Signaling Customization 530 outPulseAsDialed 298 outpulseAsDialed 247
contiguousNX6 297 implicitChannelId 299 mplicitInterfaceIdi 301 numOfDIDDigits 299 originalNumberOption 301 outPulseAsDialed 298 redirectingNumberOption 299 rejectOption 296 releaseCompleteAtSetup 300 releaseOption 296 releaseTreatment 301 responseToStatusEnquiry 296 P screenDN 300 sendCalledNumberAsPBX 298 PartialCdrTimeout 391 sendCarrierId 297 passwd 47 sendChargeNumber 300 password 47 sendCPN 300 patch sendLocalCallasSubscriber 301 applying 660 statusEnqOption 269, 296 querying 125, 126 toneOption 296 unapply 661 transferSubadressAllowOption 296 unloading 662 useImplicitChannelIdForPPS 299 patch, loading 659 PRI trunk groups 286 PCAC_FROM_CARRIER 389 Primary Rate Interface trunk groups 286 pcall 43, 739, 740 Priority Call 415 PEED_DIAL8 536 PRIORITY_CALL 535 Peg Counts 708 Process Pen Monitoring 175 911 over CAS 136 PIC2_REQUIRED_FOR_INTRALATA 389 E911 over SS7 136 ping 604 Procomm Plus 760 pingT1 44 protectionSwitch 650 point code mapping provisioning deleting 501 RDT lines 353 removing 501 provisioning alarms 53 setting 500 provisionRDTLine 353 Point Codes 470 ps 605 postEvent 58 Pseudo ANI 345 posting Pseudo Carrier Access Code 345 events 58 PREFIX_RATE_CENTER_OVERRIDES_SUBSCRI Pseudo Carrier Selection Information 345 purgeEventLog 58 BER_RATE_CENTER 389 purgePenLog 195 prefixes querying 407 PreTransKey 224, 230 Q PRI 297 PRI Options query available facility 68 query Carrier 208 allowNX64 297 autoRestartOnBoot 297 query CfvInfo 553 backwardProgressIndication 301 query facility 69 bChannelAvailabilityProcedure 298 query OfficeParms 388 blockCPN 300 query Prefix 407 callingNameDisplay 296 query ScfInfo 553
780
Index
query sipVMS 594 query SMDIParms 590 query921Status 113 queryActiveCalls 66 queryAlarmDef 55 queryAlarms 56 queryAttrDefClass 86 queryAttrDefs 85 queryAudio 94 queryCAC 94 queryCallHist 67 queryCard 167 queryCardStatus 77 queryCdrStatus 89 queryCfbInfo 554 queryCfdInfo 554, 555 queryCIC 109 queryConnections 76 queryCounter 719 queryCounterDef 717 queryCounterDefs 714 queryCounters 718 queryDb 83 queryDbKeys 84 queryDbMaster 83 queryDchStatus 114 queryDS1s 113 queryEventLog 60 queryEventRegs 61 queryFaultStatus 76 queryGrp 73 queryIG 87 querying 553, 631 active calls 66 active simulated timers 35 alarm definitions 55 alarm history 54 alarms 54, 56 all attributes 85 alternate routing schedules 81 announcements 94 attributes 86 available facility 68 call forwarding block 554 call forwarding do not answer querying 554 call forwarding fixed 555 call forwarding variable 553 call history 67 calling name TCAP 654 card status 77 carrier access codes 94
carriers 208 CDR status 89 circuits 647 codec lists 99 connections 76 craft connections 78 current processes 605 database by manager 83 database master 83 d-channels 113, 114 EOC and TMC 113 event log 60 facility 69 fault manager 76 hunt groups 73 LEDs 78 office parameters 388 patch 125, 126 prefixes 407 Rate Centers 414 RDT classes 115 RDT commands 119 RDT DS1s 113 RDT interface group 87 RDT lines 116 RDT objects 117 SAC AIN 654 SAC IN 655 SCCP nodes 486 SCCP subsystem 486 selective call forwarding 553 setting wait time 76 simulated line statistics 38 SIP endpoints 100, 101, 102 SM 75 spans 43 SS7 counters 714, 717, 718, 719 SS7 link sets 107 SS7 link timers 110 SS7 network timers 111 SS7 networks 108 SS7 node 108 SS7 node timers 111 SS7 point codes CICs 109 SS7 route timers 112 SS7 Routes 105 SS7 signaling links 106 status 98 substitution 92 system manager 75 Trunk Groups 73 voice mail connections 590
Index
781
queryIPTrunkReservation 99 queryLea 131 queryLeaCase 132 queryLinkTimers 110 queryListByCodecProfile 99 queryModifiedAttrs 87 queryNodeTimers 111 queryNWTimers 111 queryPatch 125 queryPenCommands 127 queryPenData 130 queryPenGrp 128 queryPenLog 133 queryPenTarget 129 queryPretransByDigitPtn 121 queryPretranslation 120 queryRDTClasses 115 queryRDTLines 116 queryRDTObject 117 queryRouteTimers 112 queryRouting 122 querySchedule 81 queryShelfLEDs 78 querySipEndpoint 101 querySipEndpointByAddr 102 querySipEndpointByName 100 querySpans 43 querySubBus 92 querySubCRVs 118 querySubstitution 92 querySysMgr 75
R
Rate Center 414 Rate Centers 410 RDT classes querying 115 RDT commands querying 119 RDT DS1s querying 113 RDT interface group querying 87 RDT lines deprovisioning 354 provisioning 353 querying 116 removing 355 restoring 355 syncing 356
RDT objects querying 117 RDTs adding 351 creating 351 reprovisioning 352 setting line and trunk timers 221 reconnecting EOC and TMC 651 redirectingNumberOption 299 regMaintConsole 631 rejectOption 296 release921 45 releaseCompleteAtSetup 300 releaseOption 296, 340 releaseTreatment 301 releasing EOC and TMC 45 remActCFSecurityCode 535 Remote Access Open Manger Telnet 767 Procomm Plus 763 Terra Term Professional 757 Remote Call Forwarding Activation 535 REMOTE_CALL_FWD_ACTIVATION 535 remove 628 Remove user 49 removeCff 567 removeLea 182 removeLeaCase 188 removeLeaSpan 184 removePretranslation 229 removeRDTLine 355 removeSCF 569 removeSdListShare 575 removeTask 599 removeVoiceChnl 190 removing call forwarding fixed 567 country codes 396 databases 599 international codes 396 line from service 628 point code mapping 501 RDT lines 355 span from service 628 SS7 link set 479 SS7 links 481 SS7 networks 475, 476 SS7 node 477 SS7 routes 483
782
Index
tasks 599 trunk from service 628 reprovisioning RDTs 352 reprovisionRDT 352 resetCallHist 670 resetCRVs 653 resetPMCurrent 706 resetPMIntervals 705 resetPMSummary 707 resetting circuits 646 circuits (group) 644 simulated calls on a line 38 resizePenLog 195 responseToStatusEnquiry 296 restarting SS7 network 638 restartPRI 627 restore 628 restoreDb 606 restoreRTDLine 355 restoring line to service 628 RDT lines 355 span to service 628 trunk to service 628 resync921 651 resyncing EOC and TMC 651 Revertive switchback 584 REVERTIVE_CALL 535 rmFlash 599, 601 rmuser 49 ROHToneDuration 391 Route Lists LNP 517 NANP 519 Tandem ANI 521 Tandem Carrier 523 tandem TG 525 ROUTE_ZERO_MINUS_TO_PIC2 389 routeAdvance 340 routeOnRcvdCarrier 249 Routing Translations Verification (RoVer) 612 rover 612 rrun 44 RTP port base setting 423 run 44 running scripts 44 scripts remotely 44
S
SAC AIN querying 654 SAC IN querying 655 sasp 686, 704 saving database 599 SCCP node creating 484 SCCP nodes querying 486 SCCP subsystem querying 486 SCCPNode 484, 486, 487 SCCPSubsys 486 scheduling tasks 597, 599 Screen Lists allowed list 415 denied list 415 Priority Call 415 Selective Call Acceptance 415 Selective Call Forwarding 415 Selective Call Rejection 415 screenDN 300 scripts 31 loading 31 running 44 running remotely 44 starting echoing 36, 37 stopping echoing 36 Security adduser 48 login 46 passwd 47 rmuser 49 users 49 whoami 48 Security Code Remote Call Forwarding Activation 535 sefs 686, 704 Selective Call Acceptance 415 Selective Call Forwarding 415 Selective Call Rejection 415 SELECTIVE_CALL_ACCEPTANCE 535 SELECTIVE_CALL_FORWARDING 536 send00asOLI 340 sendACTNS NEVER 340
Index
783
SAC_CARRIER_0110 340 STANDARD 340 sendCalledNumberAsPBX 298 sendCallingName 337 sendCallingNumber 337 sendCallProgress 338 sendCarrierId 297 SS7 Options sendCarrierId 337 sendChargeNumber 300, 337 sendCPN 300 sendGenericDigits 338 sendHopCounter 338 sendImmediateVMWI 596 sendJurisdictionInformation 337 sendLocalCallasSubscriber 301 sendTNS ALWAYS 339 CARRIER_0110 339 CARRIER_NOT_0110 339 NEVER 339 STANDARD 339 Service Profile 152 sesl 686, 704 sesp 686, 704 setAutoMode 632 setCaseAttr 194 setEOCTasks 357 setFeifIPAddr 422 setFeifOptions 424 setL3MOPC 499 setLeaAttr 186 setLineTimer 221 setLoopbackMode 652 setManualMode 632 setMOPC 499 setPCMap 500 setPenAttr 178 setPenGroupTimer 180 setPMDisplayOff 697 setPMDisplayOn 697 setPMTime 692 setQueryWait 76 setRtpPortBase 423 setSubCOS 576 setSubRestrict 576 setSubVoiceMailIndicator 595 setTCA15 694 setTCA24 695 setTCADefaults 704 setting event log size 58
fault manager to automatic 632 fault manager to manual 632 FEI IP address 422 FEI options 424 flash memory size 600 link timers for SLTCT1 502 MOPC 499 multiple point codes 499 point code mapping 500 RTP port base 423 subscriber restrictions 576 subscriber services 576 timers on a RDT trunks 221 timers on RDT lines 221 setting loopback DS1 652 shareSdList 574 shelf number 41 shelf_inv 78 showCDR 91 Signaling System 7 trunk groups 324 simulated cards connecting 42 simulated line statistics querying 38 simulated spans connecting 42 simulating 42, 43 SIP Endpoints Netwowrk Gateway 459 Subscriber Access Gateway 441 SIP endpoints querying 100, 101, 102 sipAllowToUseTopVia 385 sipVMS 594 skipMinDigitsRestriction 248 sleep 45 SLIC driver 45 slicd 45 SLTCT1 setting link timers 502 SLTCT1_period 502 SLTCT2_period 502 SM querying 75 span description 29 transmit signal signal spans
784
Index
querying 43 removing from service 628 spanStatus 81 SPEED_DIAL30 536 SpeedDialTimeout 391 SS7 911 136 E911 136 SS7 counters querying 714, 717, 718, 719 SS7 link set adding 478 creating 478 deleting 479 removing 479 SS7 link sets querying 107 SS7 link timers querying 110 SS7 links adding 480 creating 480 deleting 481 querying 107 removing 481 SS7 network timers querying 111 SS7 networks adding 475 creating 475 deleting 475, 476 querying 108 removing 475, 476 SS7 node 477 deleting 477 querying 108 removing 477 SS7 node timers querying 111 SS7 Options chargingOffice 336 continuityTestFrequency 336 glareControl 336 OLIRequired 338 sendCallingName 337 sendCallingNumber 337 sendCallProgress 338 sendChargeNumber 337 sendGenericDigits 338 sendJurisdictionInformation 337 terminationType 338 SS7 point codes CICs
querying 109 SS7 route timers querying 112 SS7 routes adding 482 creating 482 deleting 483 removing 483 SS7 signaling links querying 106 SS7 Trunk Groups 324 SS7NetworkStatus 108 SS7Restart SS7 network restarting 638 SS7RouteStatus 105 startCaseMonitor 192 starting script echoing 36, 37 simulated calls 39 simulated SLIC driver 45 simulated TDM controller 45 starting simulated 45 startLeaMonitor 185 startPenMonitor 191 startPM 698 startTCA15 695 startTCA24 696 status 80, 98 statusEnqOption 269, 296 statusFacility 80 stopCaseMonitor 193 stopEventLog 59 stopLeaMonitor 185 stopPenMonitor 191 stopping event log 59 script echoing 36 simulated calls 40 simulated calls on a line 38 stopPM 698 stopTCA15 696 stopTCA24 697 Subscriber Access Gateway Endpoint 441 Subscribers 530 subscribers assigning voice mail 560 deactivating voice mail 561 setting restrictions 576 setting services 576 substitution querying 92
Index
785
suppressTCA15 693 Surveillance call content 174 call data 174 swact 626 switchback 626 Switchback, revertive 584 switching EOC and TMC 650 switching between 650 switchover 626 syncDS1Line 356 syncing DS1 lines 356 RDT lines 356 syncRDTLine 356 sysApplyPatch 660 sysLoadPatchArchive 659 sysQueryPatch 126 sysStatus 736 system manager querying 75 sysUnapplyPatch 661 sysUnloadPatch 662
T
T1 332 T12 333 T13 333 T14 333 T15 333 T16 333 T17 333 T18 333 T19 333 T20 334 T21 334 T22 334 T23 334 T24 334 T25 334 T26 334 T27 334 T28 334 T34 335 T5 332 T6 332 T7 332 T8 332 TACC 335
Tandem ANI Route List 521 Tandem Carrier 523 Tandem Carrier Route List 523 Tandem TG Route List 525 tasks adding 597 deleting 599 removing 599 scheduling 597, 599 TCAP Service Global Title Translation routing 488 Point Code + Subsystem routing 492 TCAP service 496 destroying 496 TCAPServiceGTT 488 TCAPServicePCSSN 492 TCCR 335 TCGB 335 TCRA/SS7 Timers 335 TCVT 335 TDM description 29 TDM connections viewing simulated 41 TDM controller starting simulated 45 tdmd 45 TELEMARKETER_SCREENING 536 terminationType 338 TerminatorDisconnectDelay 245 TermScanningDuration 391 Terra Term Professiona 752 test 633 testCNameQuery 654 testing circuits 648 testLEDs 737 testSacAinQuery 654 testSacInQuery 655 TGRS 335 THGA 335 THREE_WAY 536 Threshold15Min 672 Threshold24Hour 672 Time Division Multiplex description 29 timers querying active simulated 35 toneOption 296 traceCalledPty 611 traceCallingPty 611 traceCPStates 610
786
Index
transferSubadressAllowOption 296 Trunk description 29 Trunk Groups querying 73 restartPRI 627 Trunk groups Channel Associated Signaling (CAS) 235 Clear Channel 252 GR-303 258 IP 307 MGCP 359 Primary Rate Interface (PRI) 286 Signaling System 7 (SS7) 324 SS7 324 trunks removing from service 628 restoring to service 628 txSpanSignal transmit signal on span 634
patch 662 unloadPatch 662 unsuppressTCA15 693 Usage Intervals 708 usap 686, 704 USE_AIN_CALLING_NAME 390 useANIDNIS 248 useImplicitChannelIdForPPS 299 User adding 48 User list 49 User name 48 users 49 using 31, 741 Using dryISE 33 Using Hexadecimal 741 utime 602
V
viewing CDRs in buffer 91 current simulated TDM connections 41 viewing 31 viewRDTCmds 119 VMWIOSITimeout 391 voice mail assigning to subscribers 560 querying connections 590 removing from subscribers 561
U
unapply patch 661 unapplyPatch 661 unblocking 640 circuits 648 circuits (group) 646 links 640 unblockLink 640 unbusy 629 uninhibiting EOC and TMC 649 uninhibitPath 649 unloadAudio 603 unloading
W
WARM_LINE 536 whoami 48 WinkDuration 245
Index
787