CHAPTER 5-1 Cisco BTS 10200 Softswitch Provisioning Guide, Release 7.0 OL-23040-01 5 Features Revised: July 2010, OL-23040-01 Introduction This chapter shows you how to add features to BTS subscribers using CLI commands. Before using the procedures in this chapter complete the following tasks: Each feature has the following sections: • Office Provisioning—Office level requirements are one-time procedures performed during initial BTS configuration. • Provisioning Resources—Network resource (CAs, FSs, MGWs, trunks, terminations) level requirements are performed during initial BTS configuration. • Alternate Activation and Deactivation Method—Ways to activate and deactivate a feature. Table 5-1 Pre-Provisioning Checklist Tasks CAs have basic provisioning. FSs have basic provisioning. MGWs have basic provisioning. Trunks have basic provisioning. Terminations have basic provisioning. Subscribers have basic provisioning, like dial plans. For complete information on dial plans, see the Cisco BTS 10200 Softswitch Dial Plan Guide. You understand the BTS features. For complete information on each feature, see Cisco BTS 10200 Softswitch Network and Subscriber Feature Descriptions. You are using the Cisco BTS 10200 Softswitch CLI Database for complete information on each table and token. CLI examples in this guide are for stand-alone illustrative purposes.
198
Embed
chapter5 7.0 prov€¦ · CHAPTER 5-1 Cisco BTS 10200 Softswitch Provisioning Guide, Release 7.0 OL-23040-01 5 Features Revised: July 2010, OL-23040-01 Introduction This chapter shows
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Cisco BTOL-23040-01
C H A P T E R 5
Features
Revised: July 2010, OL-23040-01
IntroductionThis chapter shows you how to add features to BTS subscribers using CLI commands. Before using the procedures in this chapter complete the following tasks:
Each feature has the following sections:
• Office Provisioning—Office level requirements are one-time procedures performed during initial BTS configuration.
• Provisioning Resources—Network resource (CAs, FSs, MGWs, trunks, terminations) level requirements are performed during initial BTS configuration.
• Alternate Activation and Deactivation Method—Ways to activate and deactivate a feature.
Table 5-1 Pre-Provisioning Checklist
Tasks
CAs have basic provisioning.
FSs have basic provisioning.
MGWs have basic provisioning.
Trunks have basic provisioning.
Terminations have basic provisioning.
Subscribers have basic provisioning, like dial plans. For complete information on dial plans, see the Cisco BTS 10200 Softswitch Dial Plan Guide.You understand the BTS features. For complete information on each feature, see Cisco BTS 10200 Softswitch Network and Subscriber Feature Descriptions.
You are using the Cisco BTS 10200 Softswitch CLI Database for complete information on each table and token. CLI examples in this guide are for stand-alone illustrative purposes.
Vertical Service CodesVSC provisioning is dependent on the type of dial plan in effect, NANP or otherwise. Currently, there are two standard configurations based on the nature of dial plan associated with a subscriber. They are identified by the NANP-DIAL-PLAN token in the dial-plan-profile table and are discussed in the following sections:
• NANP Dial Plan VSC Provisioning, page 5-2
• Non-NANP Dial Plan VSC Provisioning for Subscriber and Centrex, page 5-3
The following restriction applies to networks with SIP endpoints. Certain combinations of VSCs should not be deployed on networks with SIP endpoints. If you deploy a VSC longer than 2 digits, make sure that the longer VSC does not begin with the same sequence of characters as one of the shorter VSCs. In some cases, the system might match the shorter string even if the subscriber dialed the longer string.
Consider the following example, for which the subscriber is expected to dial a VSC followed by a DN. A SIP subscriber is provisioned with *93 for Feature1 and *938 for Feature2, and dials *938+2135551801 to invoke Feature2. The BTS receives *9382135551801 in the INVITE message. By default, it takes the first six characters, in this case *93821, and uses this string to look up the feature in the VSC table. There is no match for *93821, therefore the BTS proceeds as follows. First, it uses *9 to look for a match in the VSC table and it cannot be found. Then it uses *93, finds a match, and delivers Feature1. This is incorrect. The user's intention was to invoke Feature2 and not Feature1. The solution is for the service provider to change one of the two VSCs (either *93 or *938) in the VSC table.
NANP Dial Plan VSC Provisioning
Step 1 Provision the digit map with the digit pattern.
Note The "[regular digit pattern]" referred to is part of the subscriber digit map/digit pattern. The VSC digit patterns are embedded within the subscriber’s digit map/digit pattern.
Step 2 Add the digit pattern to the digit map used for Centrex subscribers:
Note The "[regular Centrex digit pattern]" is part of the Centrex digit map/digit pattern. The VSC digit patterns are embedded within the Centrex digit map/digit pattern.
Step 3 Associate the digit maps in Steps 1 and 2 with the appropriate subscriber profiles:
Note The "regular digit pattern" referred to in this section is part of the subscriber digit map/digit pattern. The VSC digit patterns are to be embedded within the subscriber’s digit map/digit pattern.
Note Only the following VSC signatures are applicable:*XX**XX##XX#*#XX**#XX#
Step 2 Add the digit pattern to the digit map used for Centrex subscribers:
Note The regular Centrex digit pattern referred to in this section is part of the Centrex digit map/digit pattern. The VSC digit patterns are to be embedded within the Centrex digit map/digit pattern.
Step 3 Associate the digit maps in Steps 1 and 2 to the appropriate subscriber profiles:
Step 5 Associate the entries in the Digman table to the dial plan profile and update the NANP_DIAL_PLAN token in the Dial-plan-profile table to N:
add/change dial-plan-profile ID=dpp1; DESCRIPTION=dialing plan profile ID2; NANP_DIAL_PLAN=N; DNIS_DIGMAN_ID=pretrans;
Step 6 After the feature tables are populated, provision the VSC/CDP table with a VSC code for all applicable features. The following is an example for CFUA for POTS and Centrex subscribers:
Subscriber DefaultsYou can create defaults for subscribers, this does the following:
• Allows you to configure default values for optional tokens
• Adds data validation of configured default values
• Allows you to provision default values using a command alias
• Allows you to show the BTS factory default settings
This feature is automatically enabled after BTS installation. After upgrading, the existing configured default values are preserved.
Note After configuring default values, you should exit and start a new CLI session before performing regular provisioning. The configured default values will only take effect in the new CLI session.
Provisioning Optional Token DefaultsThe following example provisions the default value for the es_supp token in the AGGR table.
Step 1 Show the configured default value, if any. In this example, no default value is configured.
show var_default noun=aggr; var_name=es_supp;
Reply:Success: Database is void of entries
Step 2 Provision Y as the default value for the es_supp token.
Step 3 Verify that the default value for the es_supp token is provisioned.
show var_default noun=aggr; var_name=es_supp;
NOUN=aggrVAR_NAME=es_suppDEF_VALS=YReply:Success:Entry 1 of 1 returned.
Checking Default ValuesThe Configurable Default Values for Subscriber Provisioning feature checks the integrity of the configured default value to ensure the default value is consistent with the token value specified in the database. An invalid default value will be rejected when you add or change the default value.
The following example illustrates an attempt to configure the default value of a token with an invalid value.
change var_default noun=aggr; var_name=es_supp; def_vals=BAD_VALUE;Reply:Failure:<BAD_VALUE> is invalid - should be one of [Y,N]
Note A subsequent add operation may still fail even though the default value is an allowable value because the default value might violate further integrity checks and business rules validation at provisioning time.
Provisioning Defaults using Command AliasYou can use a command alias for adding, changing, and viewing a token default value. The following example illustrates using the command alias sub when configuring the default value of the term_type token in the Subscriber table.
Step 1 Configure the default value for the term_type token in the Subscriber table.
Step 2 Verify that the default value is configured as expected.
show var_default noun=sub; var_name=term_type;
NOUN=subscriberVAR_NAME=term_typeDEF_VALS=SIPReply:Success:Entry 1 of 1 returned.
Viewing Factory DefaultsThis feature adds the all token to the show var_default command to provide the ability to show if a token has a factory default value configured and also the currently configured default value. The following example illustrates displaying both the factory default value and the currently configured value for the term_type token in the subscriber table.
show var_default noun=subscriber; var_name=term_type; all=y;
NOUN=subscriberVAR_NAME=term_typeBTS_DEFAULT=TERMDEF_VALS=TGReply:Success:Entry 1 of 1 returned.
Restoring Factory DefaultsBTS factory default values can be replaced by user provisioned defaults. You can restore the factory default value by deleting the provisioned default value. The following example restores the factory default value for the term_type token in the Subscriber table.
Feature ProvisioningThis section describes how to provision features on the BTS.
Note If your network uses an ISUP variant other than ANSI ISUP:--- For call-waiting features, BTS supports CWD, but not CW or CIDCW--- For three-way-calling features, BTS supports TWCD, but not TWC or USTWC
Step 4 Add the digit string to the dial plan for the subscriber/trunk. The dial-plan ID must match the ID of the appropriate dial-plan-profile, and the dest-id must match the ID of the appropriate destination.
Caution For the 8XX feature, do not enter a value for the nature of address (NOA) parameter. You must allow the system to use the NOA default value (NATIONAL). This is true even if you have calls with a network-specific NOA.
Tip Enter this command as add dial-plan (not change dial-plan) even if the dial-plan already exists.
Step 5 Add the Dn2cust group. The system uses these provisioned values for local 8XX calls only, not for external calls or for calls that require an SCP database query.
This section explains how to add the 8XX feature to the default-office-service-id (a switch-wide default service) and to the office-service-id (a POP-wide default service). If you provision an office-service-id for a POP, that office-service-id takes precedence over the default-office-service-id. However, if you do not provision an office-service-id for a POP, the system uses the default-office-service-id.
Step 1 Add this feature to the default office service ID (ABC in this example). This allows the system to provide this feature to all subscribers by default.
a. Enter the following command to display the ID of the default-office-service-id.
show ca-config type=DEFAULT-OFFICE-SERVICE-ID;
The system displays the value of the default-office-service-id. In this example, assume that the system displayed the value as ABC.
b. Use the following command to determine what number (N) should be used for fnameN.
show service id=ABC;
The system displays the features that are in this service table.
c. If 8XX is not already included in this service, add 8XX by entering the following command. Do not use a number for FNAMEn that is already being used for this service.
add/change service id=ABC; fname9=8XX;
Step 2 If you are using POP-specific office service IDs, you can add the 8XX feature. If you add this feature to the office service ID (XYZ in this example), all subscribers in this POP will be given the 8XX feature.
a. Enter the following command to display the ID of the office-service-id.
show pop id=pop1;
The system displays the value of the office-service-id, if it already exists for this POP. In this example, assume that the system displayed the value as XYZ.
Note If the display shows that there is no office-service-id provisioned for this POP, you must first use the change pop command to add an office-service-id.
b. Use the following command to determine what number (N) should be used for fnameN.
show service id=XYZ;
The system displays the features that are in this service table.
c. If 8XX is not already included in this service, add 8XX by entering the following command. Do not use a number for FNAMEn that is already being used for this service.
add/change service id=XYZ; fname9=8XX;
Provisioning Resources
These steps explain how to provision the resources to enable an SCP query.
Note The hb_timeout and max_path_retrans tokens are not configurable via the CLI change command. To configure or change these values, a new SCTP association profile must be added.
control sctp-assoc id=sctp_assoc1; mode=forced; target-state=INS;
Step 16 Place the subsystem group in service:
control subsystem-grp id=SSN_TF; mode=forced; target-state=INS;
Provisioning Notes/Caveats
If the toll free trigger is generated by trunk (SS7, CAS) calls and no calling party is received in the setup indication (IAM), ensure that the JIP field or LRN field in the POP table associated with the trunk group is set to the appropriate value. If not, the SCP query will fail.
The Cisco BTS Softswitch is connected to a MGW supporting MGCP (MS, DT, and MO) through an IP network. Some examples of media gateways are Cisco MC3810 and Cisco C3660. Contact Cisco TAC for additional details on gateways supported for CAS trunk groups.
CAS Trunk Group Control Commands
After the CAS trunk group is provisioned in the BTS and the corresponding MGCP gateway is configured for CAS, the CAS trunk group and the CAS trunk circuits can be brought into service with control commands from the EMS.
At the EMS CLI> prompt, execute the following commands:
Step 1 Bring the MGW into service:
CLI> control mgw 224.14:2434; target_state=ins; mode=forced;CLI> status mgw id=224.14:2434;
Emergency ANIThe Emergency ANI feature allows the service provider to provision a E911 number, which can be different from the subscriber DN or the billing DN. To provision the specific ANI for E911 calls for a subscriber, use the EMERGENCY-ANI table. The emergency ANI specified in this table overrides any subscriber settings made for outbound calling ID on E911 calls.
The EMERGENCY_ANI table contains two tokens—SUB-ID and EMG-ANI.
• The subscriber ID (SUB-ID) token indicates the ID of the subscriber for whom the emergency ANI has to be specified. The EMG-ANI token specifies the value (number) for ANI to be sent for emergency calls for the specified subscriber ID.
• If the subscriber ID exists in the EMERGENCY-ANI table, the EMG-ANI specified in this table is sent as the calling party number (caller ID) for an emergency call.
• If the subscriber ID is not present in this table, and if the SEND_BDN_FOR_EMG token in the Subscriber table is set to Y, the billing DN is sent as the calling party number. Otherwise, DN1 in the Subscriber table is sent as the calling party number for emergency calls.
Note For a complete list of tokens used with the EMERGENCY-ANI table, see the Cisco BTS 10200 Softswitch CLI Database.
Use the following sample steps to add an emergency ANI-specific number to a subscriber. In the steps given below, when a call is made for E911, the BTS 10200 checks to see if the calling subscriber (212-222-2801) is configured in the EMERGENCY-ANI table. The BTS 10200 then replaces the calling number ID with the EMG-ANI number (212-111-1111).
Step 1 Follow the steps to add a subscriber to the BTS 10200. See the Cisco BTS 10200 Softswitch Provisioning Guide and the Cisco BTS 10200 Softswitch CLI Database for complete information on how to add subscribers.
Step 2 Add the EMG-ANI for the subscriber in the EMERGENCY-ANI table.
add sub-id=<sub-id>; EMG-ANI=<number>;
add sub-id=212-222-2801; EMG-ANI=212-111-1111;
In the above example, the subscriber ID (212-222-2801) needs to be configured in the subscriber table before it is specified in the EMERGENCY-ANI table.
Emergency CallbackUse the following procedure to provision the Emergency Callback feature.
Step 2 Add ECB to the list of features available to the subscriber as part of the office-based services. ECB is available to all subscribers associated with the service ID.
Viewing Active CallsThis feature allows the display of of the call information of a currently active call. With this feature, the operator enters the appropriate input, depending on whether it is a subscriber (POTS, H323 or SIP), a Multi-line Hunt Group (MLHG) terminal, a Centrex extension, SS7, an ISDN trunk, a SIP trunk, an H323 trunk, termination, or a media gateway. The input for each type, as well as how to arrive at the call information based on the input is explained in this document. The goal is to first arrive at the Call Segment Association (CSA) index from the input. From the CSA index, all call-related information is retrieved. In some instances, more than one CSA index may be associated with the given subscriber.
CLI Provisioning
The following CLI syntax is used to provision this feature:
Alerting Notification to Third Party Feature Server
Precedence for Provisioned Values
Alerting Notification can be assigned on a switch-wide, per-POP, or per-subscriber level (or all three levels). The system interprets the provisioned values this way:
• Switch—If the office-service-id is not provisioned in the POP table and not provisioned for the individual subscriber, the system uses the default-office-service-id provisioned in the ca-config table. See Step 3.
• POP—If Alerting Notification is included in the office-service-id for the POP, then Alerting Notification applies to all subscribers in the POP, even if the feature is not assigned to an individual subscriber. See Step 4.
• Subscriber—If Alerting Notification is assigned to a specific subscriber, then Alerting Notification applies to the subscriber, regardless of whether Alerting Notification is provisioned in the office-service-id for the POP or in the default-office-service-id in the Call Agent Configuration (ca-config) table. See Step 5.
The following are command examples to provision this feature.
Step 1 Add the 3PTYFS to the database.The TSAP address can be an IP address (with port optional) or a DNS name. If the TSAP address is a domain name, then the domain name must be configured in the service provider DNS.
Note In the procedures included in this document, Alerting Notification is provisioned using the feature identifier FNAME=ALERT_NOTIFY. The feature identifier can be any unique string of up to 16 ASCII characters chosen by the service provider.
Step 3 (Optional) The commands in this step assign Alerting Notification globally (by default) to all subscribers on the switch.
SHOW CA-CONFIG TYPE=DEFAULT-OFFICE-SERVICE-ID;
SHOW SERVICE ID=999;
CHANGE SERVICE ID=999; FNAME8=ALERT_NOTIFY;
Step 4 (Optional) The commands in this step assign Alerting Notification to all subscribers in a specific POP.
SHOW POP ID=CITY007;
SHOW SERVICE ID=NOTIFY;
ADD/CHANGE SERVICE ID=NOTIFY; FNAME1-ALERT_NOTIFY;
Note The hb_timeout and max_path_retrans tokens are not configurable via the CLI change command. To configure or change these values, a new SCTP association profile must be added.
Step 3 Customize the subscriber’s Usage Sensitivity feature applicability flag:
change subscriber id=subscriber_1; USAGE-SENS=Y;
Centrex Provisioning
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step should be completed.
Step 1 Create the following entries in the CDP table:
• The AC and AR features will not work for the subscriber with the category CTXG, MLHG, or CTXG_MLHG because these categories of subscriber do not give a unique DN.
• If the TSAP-Addr in Call-Agent table is incorrect, this feature will not work. It must have a specific UDP port number.
• Office-Code table entries must have the Call-Agent-Id for all the office-codes owned by the Call Agent. If the Call-Agent-Id is not configured in the Office-Code table, this feature will not work.
Step 5 Add the AR two-level activation Audio-Sequence table. These commands must be entered in the order given, and all files specified in the sequence must be installed on the IVR system. If any file specified in the sequence is missing, and the IVR system does not return error, there is a possibility that no files will be played.
show ca-config type=AR%Reply : Success: Entries 1-24 of 24 returned.
CA-Config values for the AC feature are common to the AR feature. Refer to the CA-Config values for the AC feature.
Step 6 (Optional) Add the feature to the default office service-id if it needs to be provided on an office basis. To assign the feature to the default office service id, complete the following steps:
change ca-config type=default-office-service-id; value=999;change service id=999; fname1=AR_ACT;
Provisioning Resources
Step 1 Provision the signaling gateway:
add sg id=sg_1; description=signaling gateway 1;
Step 2 Provision the signaling gateway group:
add sg-grp id=sg_grp1; sg1-id=sg_1; description=signaling gateway group 1;
Step 3 Provision the signaling gateway process:
add sgp id=itp_7507_1; sg-id=sg_1; description=ITP 7507 for sg_1;
Note The hb_timeout and max_path_retrans tokens are not configurable via the CLI change command. To configure or change these values, a new SCTP association profile must be added.
Step 3 Change the subscriber’s Usage Sensitivity feature applicability flag:
change subscriber id=subscriber_1; USAGE-SENS=Y;
Centrex Provisioning
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step must be completed.
Step 1 Create the following entries in the CDP table:
• AC and AR features will not work for the subscriber with the category CTXG, MLHG, or CTXG_MLHG because this category of subscriber does not give a unique DN.
• If the TSAP-Addr in the Call-Agent table is incorrect, this feature will not work. It must have a specific UDP port number.
• Office-Code table entries must have the Call-Agent-Id for all the office-codes owned by the call-agent. If the Call-Agent-Id is not configured in the Office-Code table, this feature will not work.
Two-Level AR Activation
AR activation is also offered as a two-level procedure. When a subscriber dials the activation code, an announcement gives the last incoming calling party number, the date and time when the call was received, and instructions to dial 1 to activate the AR call to that party.
Provisioning two-level AR activation requires the following additional steps:
Step 1 Specify the AR activation level. To apply at the system basis, :
Step 4 Specify the default voice back language in the Language table:
add language id=def;
Step 5 Add the AR two-level activation Audio-Sequence table. These commands must be entered in the order given.
add audio-seq id=ar_vbk_dn_seq; language-id=def; seq=ar_voice_back_dn,ar_var_dn,ar_voice_back_date,ar_var_date,ar_voice_back_time,ar_var_time,ar_activation_prompt; description=The last incoming number was [ dn ]. This call was received on [ date ] at [ time ]. To activate Automatic Recall, dial 1 otherwise, hang up.
add audio-seq id=ar_vbk_anon_seq; language-id=def; seq=ar_voice_back_dn,ar_voice_back_anonymous_dn,ar_voice_back_date,ar_var_date,ar_voice_back_time,ar_var_time,ar_activation_prompt; description=The last incoming number was an anonymous number and cannot be announced. This call was received on [ date ] at [ time ]. To activate Automatic Recall, dial 1 otherwise, hang up.
add audio-seq id=ar_inv_digit_seq; language-id=def; seq=ar_dialing_error,ar_activation_prompt; description=We are sorry. The digits dialed are not a valid command. To activate Automatic Recall, dial 1 otherwise, hang up.
add audio-seq id=ar_con_instr_seq; language-id=def; seq=ar_consult_instruction; description=We are sorry. The digits dialed are not a valid command. To activate Automatic Recall, dial 1 otherwise, hang up.
Step 6 Add the AR two-level activation Audio-Segment table. These commands must be entered in the order given.
add audio-segment id=ar_voice_back_dn; type=physical; url=file://ar_voice_back_dn.wav; description=The last incoming number was
add audio-segment id=ar_voice_back_anonymous_dn; type=physical; url=file://ar_voice_back_anynomous_dn; description=an anonymous number and cannot be announced
add audio-segment id=ar_dialing_error; type=physical; url=file://ar_dialing_error.wav; description=We are sorry. The digits dialed are not a valid command.
add audio-segment id=ar_consult_instruction; type=physical; url=file://ar_consult_instruction.wav; description=We are sorry. Please hang up now, consult your written instructions, and try again later.
Busy Line Verification
Office Provisioning
Step 1 Add the default office service id:
change ca-config default-office-service-id=999;
Step 2 Add the BLV Service to the default-office-service:
Centrex and MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
In general, the BLV feature does not support interaction with features that are invoked by the verified party (terminating subscriber) at the time of verification. If the verified party is engaged in a call and has features invoked, the operator receives a busy tone and cannot perform an interrupt on the call.
You can provision the BLV feature to allow verification if the subscriber has Cancel Call Waiting (CCW) or 911 emergency service invoked at the time of verification. The following optional commands provision the BLV feature to allow or disallow verification when the subscriber has invoked CCW or 911 emergency service.
Note On some voice gateways, ring back tone maybe heard when targeting an idle end-point. If the Voice call send-alert statement is added to the router config file, ring back tone is not transmitted to the verifying party.
MLHG provisioning is similar to Subscriber provisioning.
Provisioning Notes/Caveats
This feature works in conjunction with the SCR feature. Therefore, for the call to be rejected by Call Block, SCR should be assigned to the subscriber and activated. Refer to Screen List Editing: SCF, SCR, SCA, and DRCW, page 5-131, for directions for provisioning SCR.
Billing Enhancement for Business Digital Voice SubscribersThis section explains how to provision the Billing Enhancement for Business Digital Voice Subscriber feature. Perform these tasks in the sequence shown in this section.
Note Ensure that you have added MGW, terminations, and dial-plan before adding subscriber-profile and subscribers. Refer to the Provisioning Guide, Release 6.0.x for more information about adding subscribers.
Note The commands shown in this section are examples; you should provision value that are appropriate for your network and service offerings. CLI syntax allows you to enter commands in uppercase or lowercase. It also allows you to enter hyphens (-) or underscores (_) interchangeably in most cases (exceptions, if any, are noted in the procedures).
A complete list of tokens for each CLI table, as well as the allowed values, default values, and detailed descriptions for each token, is provided in the Cisco BTS 10200 Softswitch CLI database.
The Subscriber Profile (subscriber-profile) table groups shared subscriber properties. Because CAs have several points of presence (POPs), and POPs are a subscriber profile token, you must create POP-specific subscriber profiles.
Block All Inbound CallsIf a subscriber has blocked all the inbound calls, the calling party hears an announcement stating that called party has chosen to deny all inbound calls. For the inbound DN, the DN2SUBSCRIBER entry is provisioned to route the call to ANNC=998, which plays an announcement stating the called party has chosen to deny inbound calls. Use the announcement ID 800 through 899 for custom announcements.
The following steps explain how to provision this feature:
Step 1 Create subscriber without DN1, but with billing DN.
Office Provisioning—Call Forwarding for Unreachable Condition
The CFB feature can forward a call when the called-party line is unreachable or the MGW is down. This is the normal behavior when the keepalive-method token in the mgw-profile table is set to AUEP (this is the default value). If you chose to set the keepalive-method token to NONE, and you want CFB to forward a call when the called-party line is unreachable or down, you must provision an additional trigger for the CFB feature, and you must also refresh the service that contains the CFB feature. Two cases are shown in this section:
• Fresh Installation
• Upgrade or Changes to Database
Caution We recommend that you keep the keepalive-method token set to the default value unless you have some other method of determining MGW connectivity status.
Caution If you want to block call-forwarding to an emergency (EMG) DN, such as 911, you must provision NOD=EMG for the call-forwarding features (CFU, CFB, CFNA, and CFC) in the NOD-RESTRICT-LIST. This is necessary to comply with the rule in Telcordia document GR-580, which says that 911 should not be a permitted "forward to" number.
Step 15 If you have decided to turn off MGW monitoring for a particular MGW, enter the following command:
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following steps are required.
Step 1 Add a feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
• Changing the second stage dial tone (SDT) option will have no effect on the delivery of the second dial tone for SIP subscribers. This option is available through the dial plan in the SIP phone.
• Changing the final stage dial tone (FDT) option will have no effect on the delivery of the final dial tone for SIP subscribers. For SIP phones, an announcement will always be delivered because provisioning to play a dial tone and collect further digits is not available.
This feature is deactivated by default when it is assigned to a subscriber. CFB can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate CFB:
In addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber, In addition, the following steps are required:
Step 1 Define the star codes in the CDP table for Centrex subscribers:
Note If a call originates on a phone connected to Cisco CallManager toward a DN subscribed to the Cisco BTS Softswitch, the Cisco BTS Softswitch cannot forward that call over an H.323 network to a third party using the call forward no answer (CFNA) feature. (The Cisco BTS Softswitch can forward the Cisco CallManager-originated call over a SIP or MGCP-based network to a third party using CFNA.)
There is an interaction when a Centrex subscriber has all three of the following features assigned and active:
• Call hold—CHD
• Call waiting—CW or CIDCW or both
• Call forwarding on no answer—CFNA
In this case, the system does not invoke forwarding for any incoming calls. For the subscriber to have the call waiting features (CW or CIDCW) and CFNA active simultaneously, do not assign the CHD feature to the subscriber.
Caution To block call-forwarding to an emergency (EMG) DN, such as 911, provision NOD=EMG for the call-forwarding features (CFU, CFB, CFNA, and CFC) in the NOD-RESTRICT-LIST. This is necessary to comply with the rule in Telcordia document GR-580, which says that 911 should not be a permitted "forward to" number.
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following steps are required.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
• While provisioning CFNA, TO in the feature table denotes the time-out that should be used for reporting No-Answer. This TO can be changed to ‘N’ seconds by using the following CLI command:
change feature fname=CFNA; TYPE1=TO; VALUE1=N;
• The following can be used to activate the feature or change the forwarding-dn for subscriber sub_1 via CLI:
• Changing the second stage dial tone (SDT) option will have no effect on the delivery of the second dial tone for SIP subscribers. This option is available through the dial plan in the SIP phone.
• Changing the final stage dial tone (FDT) option will have no effect on the delivery of the final dial tone for SIP subscribers. For SIP phones, an announcement will always be delivered because provisioning to play a dial tone and collect further digits is not available.
This feature is deactivated by default when it is assigned to a subscriber. CFNA can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate CFNA:
Caution If you want to block call-forwarding to an emergency (EMG) DN, such as 911, you must provision NOD=EMG for the call-forwarding features (CFU, CFB, CFNA, CFC, and CFNR) in the NOD-RESTRICT-LIST. In this way you comply with the rule in Telcordia document GR-580, which says that 911 should not be a permitted forward-to number.
For the CFNR feature, the Centrex user requires basic Centrex office provisioning and Centrex subscriber provisioning. The latter is similar to the provisioning done for a POTS subscriber. In addition, the following step is required.
Add a feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to the subscriber provisioning as described above.
Provisioning Notes/Caveats
• Changing the second stage dial tone (SDT) option has no effect on the delivery of the second dial tone for SIP subscribers. This option is available through the dial plan in the SIP phone.
• Changing the final stage dial tone (FDT) option has no effect on the delivery of the final dial tone for SIP subscribers. For SIP phones, an announcement is always delivered because because there is no option for the playing of a dial tone and the collecting of further digits.
This feature is deactivated by default when it is assigned to a subscriber. CFNR can alternately be activated and deactivated by the creation of an entry in the subscriber-feature-data table.
Step 1 Use a CLI command similar to the following to activate CFNR to a specific forward-to number:
Note The features assigned to FNAME1, FNAME2, and FNAME3 in this step become sub-features of FNAME and are automatically assigned to a subscriber when FNAME is assigned.
Step 5 Add/change a VSC code for CFU-A:
add/change vsc fname=CFUA; digit-string=*72;
Step 6 Add/change a VSC code for CFU-D:
add/change vsc fname=CFUD; digit-string=#72#;
Step 7 Add/change a VSC code for CFU-I:
add/change vsc fname=CFUI; digit-string=*#72;
Step 8 Add a service with these features:
add service id=1; FNAME1=CFU;
Step 9 Customize the reminder ring capability as required:
change feature fname=CFU; type1=RR; value1=N;
Step 10 Customize the multiple call forwarding capability as required:
change feature fname=CFU; TYPE1=MCF; VALUE1=Y;
Step 11 Customize for International Call Forwarding as required. This should be applied to CFU and CFUA:
Caution If you want to block call-forwarding to an emergency (EMG) DN, such as 911, you must provision NOD=EMG for the call-forwarding features (CFU, CFB, CFNA, and CFC) in the NOD-RESTRICT-LIST. This is necessary to comply with the rule in Telcordia document GR-580, which says that 911 should not be a permitted "forward to" number.
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step is required.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
• Changing the second stage dial tone (SDT) option will have no effect on the delivery of the second dial tone for SIP subscribers. This option is available through the dial plan in the SIP phone.
• Changing the final stage dial tone (FDT) option will have no effect on the delivery of the final dial tone for SIP subscribers. For SIP phones, an announcement will always be delivered because provisioning to play a dial tone and collect further digits is not available.
Alternate Activation and Deactivation Method
This feature is deactivated by default when it is assigned to a subscriber. CFU can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate CFU:
Call Forwarding Variable for Basic Business Groups The following subsections identify necessary steps for provisioning the Call Forwarding Variable for Basic Business Groups (CFVBBG) feature.
Note CFVBBG and CFVABBG are Centrex only (BBG) features.
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step is required.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
• Changing the second stage dial tone (SDT) option will have no effect on the delivery of the second dial tone for SIP subscribers. This option is available through the dial plan in the SIP phone.
• Changing the final stage dial tone (FDT) option will have no effect on the delivery of the final dial tone for SIP subscribers. For SIP phones, an announcement will always be delivered because provisioning to play a dial tone and collect further digits is not available.
• For CFVBBG on SIP phones, the reminder ring will not be played because of limited capability on the SIP phone.
• The value provisioned for the courtesy call option will apply only to internal (within the Centrex group) extensions. If a subscriber wants to activate CFVBBG to an external DN, a courtesy call will always be delivered.
Alternate Activation and Deactivation Method
This feature is deactivated by default when it is assigned to a subscriber. CFVBBG can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate CFVBBG:
Call Forwarding EnhancementThis section explains how to activate CF on a new DN without deactivating on the old DN.
Step 1 On the BTS, enter the following command:cli> add ca_config type=CF-RE-ACTIVATION;value=y;
Note For complete CLI information, see the Cisco BTS 10200 Softswitch Command Line Interface Database.
Provisioning CF Checking Enhancements
This section explains how to let subscribers hear an announcement of their DNs with CF.
Step 1 On the BTS, enter the following command:cli> add ca_config type=CF-INTERROG-WITHOUT-NUM;value=y;
Announcements
These features require the following cause codes, included in the 6.0 MR1 upgrade onwards:
• FS_CAUSE_CF_ACT_DN_PLAY_SUCC
• FS_CAUSE_CF_INT_DN_PLAY_SUCC
Call Hold The Call Hold (CHD) feature allows you to temporarily shut-off an active call, use the telephone for making another call, and then return to the original call. You can alternate between two calls.
There is an interaction when a Centrex subscriber has all three of the following features assigned and active:
• Call hold—CHD
• Call waiting—CW or CIDCW or both
• Call forwarding on no answer—CFNA
In this case, the system does not invoke forwarding for any incoming calls. For the subscriber to have the call waiting features (CW or CIDCW) and CFNA active simultaneously, do not assign the CHD feature to the subscriber.
The following subsections identify necessary steps for the feature to be offered.
Note cpsg1 is the Call Park Subscriber Group idTCPRK is the Timed Recall (Re-offer) TimerCPRK_FDN is the Forward-To DN, in case all the re-offers are exhausted
Note CPRK will get the timer value configured against TCPRK from the CPSG table. If that value is 0, then this value (from the Ca-config table) will be used.
If the configured timer value in the Ca-config and CPSG tables are 0, then this value will be used. If this is also not configured, then a default value of 60 secs will be used.
Step 8 (Optional) If step #6 is performed, add corresponding announcements:
A call can be parked by a Centrex subscriber only against a subscriber in the same CPSG. Similarly, only a member of the same CPSG can retrieve a parked call.
Call Pickup (CPU)This section explains how to provision the Call Pickup (CPU) feature. Perform these tasks in the sequence shown here:
Note The commands shown in this section are examples; you should provision values that are appropriate for your network and service offerings. CLI syntax allows you to enter commands in uppercase or lowercase. It also allows you to enter hyphens (-) or underscores (_) interchangeably in most cases. (Exceptions, if any, are noted in the procedures.)
A complete list of tokens for each CLI table, as well as the permitted range of values, default values, and detailed descriptions for each token, is provided in the Cisco BTS 10200 Softswitch CLI database.
Step 2 add service id=3; fname1=CDP; fname2=CPU; Adds the service table. The Service (service) table defines services and features. A service is a collection of one or more features.
Step 3 add custom-dial-plan-profile id=cdp1; Adds the custom dial plan profile table. This table defines the custom dial plan IDs (CDP IDs) assigned to Centrex groups.
Adds the CPU feature to the custom-dial-plan table for the Centrex group.
Step 5 add vsc DIGIT-STRING=*xx; FNAME=CPU; Translates a vertical service code (VSC), also known as a star code (*XX), to the CPU feature. This table is preprovisioned, based on the Feature table customer records, during installation.
Centrex and MLHG provisioning is similar to subscriber provisioning.
Call Transfer for Business GroupsTo support the Call Transfer for Business Groups feature, following additions to the Cisco BTS 10200 Softswitch CLI Database have been made:
• A new table, CT_PROFILE
• A new token, CT_PROFILE_ID, to the ext2subscriber table
For a full description of the CT_PROFILE table and other CLI database changes, see the Cisco BTS 10200 CLI Database.
This section explains how to perform the following tasks:
• Defining a CT Profile for Individual–Incoming Only–Internal Only
• Defining a CT Profile for Internal Only
• Assigning a CT Profile to a Subscriber
• Adding Subscribers for Various CT Interactions
Defining a CT Profile for Individual, Incoming Only, Internal Only
The following sample command defines a CT profile that enables a CT subscriber to receive an incoming call and transfer it internally only to a business group subscriber.
add ct-profile id = InIncOnlyIntOnly; ADD_ON _RESTRICTIONS= ADD_BG_ONLY; CT_RESTRICTIONS=TRANSFER_TO_BG_ONLY; TWC_RESTRICTIONS=NO_RESTRICTIONS;
Defining a CT Profile for Transferring Calls within a Business Group Only
The following sample command defines a CT profile that enables a CT subscriber inside a business group to receive a call from the public data network and transfer that call to a subscriber inside the business group only.
add ct-profile id = Internal_Only; ADD_ON _RESTRICTIONS= ADD_BG_ONLY; CT_RESTRICTIONS=TRANSFER_TO_BG_ONLY; TWC_RESTRICTIONS=USE_CT_RESTRICTIONS;
Note For complete CLI information, especially including the new CT_PROFILE table, see the Cisco BTS 10200 Softswitch CLI Database.
Assigning a CT Profile to a Subscriber
To support CT for Business Groups, Cisco added a new token to the ext2subscriber table in the Cisco BTS 10200 CLI database. The value specified for the CT_PROFILE_ID token associates a CT profile with the Centrex subscriber. For a detailed description of the CT_PROFILE_ID token in the ext2subscriber table, see the Cisco BTS 10200 Softswitch CLI Database.
The following sample commands assign the CT profiles defined in the preceding two sections to the CT subscribers. The CT profiles are added to the ext2subscriber table.
The sample commands in the following section show how to provision business group subscribers for the various possible CT interactions. For a complete description of the CT_PROFILE table, see the Cisco 10200 Softswitch CLI Database.
Provisioning CT for Individual, All Calls, No Restrictions
The following sample command provisions a subscriber for CT, all calls, no restrictions. All other tokens retain their default values.
add ct-profile-id id=CT-ALL-NR; description= call transfer all calls no restrictions. All other tokens use default values.
Provision CT for All Calls, Internal Only
The following sample command provisions a subscriber for Call Transfer, all calls, internal only:
add ct-profile-id id=CT-ALL-IO; ct-restrictions=INTERNAL-ONLY;description= call transfer all calls internal only.
Provisioning CT for Individual, All Calls, Outside
The following sample command provisions a subscriber for Call Transfer, individual, all calls, outside:
add ct-profile-id id=CT-ALL-OUT; ct-restrictions=OUTSIDE-ONLY;description= call transfer all calls outside only.
Provisioning CT for Individual, Incoming Only, No Restrictions
The following sample command provisions a subscriber for Call Transfer, individual, incoming only, no restrictions:
add ct-profile-id id=CT-IO-NR; ct-restrictions=NO-RESTRICTIONS; description= call transfer incoming only.
Provisioning CT for Incoming Only, Attendant Only
The following sample command provisions a subscriber for Call Transfer, incoming only, attendant only:
add ct-profile-id id=CT-ATTENDANT; ct-restrictions= ATTENDANT-ONLY; description= call transfer - incoming only - attendant only.
Configuring Restrictions
The Cisco BTS 10200 user (for example, a service provider operator) can define how the Call Transfer feature will work for business group subscribers by specifying various combinations of values for the following restriction tokens in the CT_PROFILE table:
• ADD_ON _RESTRICTIONS—The value of this token determines the second-level restriction that is applied when the CT subscriber attempts to add a third party to the call.
• CT_RESTRICTIONS—The value of this token determines the 3rd-level restriction that is applied before a call is transferred.
• TWC_RESTRICTIONS—The value of this token determines the restriction that is applied before the Cisco BTS 10200 permits a call to join a conference.
The following sample command enables a subscriber to establish a conference call with a third party outside the Centrex group. However, call transfer is not permitted because the transfer is restricted to internal only.
add ct-profile-id id=TWC-ALL-NR; twc-restriction=NO-RESTRICTIONS; ct-restrictions=INTERNAL-ONLY;description= No restricions on call conference. Call transfer all calls internal only.
Note Recall Dial Tone (RDT) restrictions are not supported in Release 6.0.1 of the Cisco BTS 10200 Softswitch.
By configuring these tokens, a service provider operator can create several different CT profiles, which the operator can apply to a selected group of subscribers or to all subscribers in the group. The operator can associate a CT profile with a Centrex subscriber by including the ID of the profile in the ext2subscriber table.
For a detailed description of the CT_PROFILE table and its restriction tokens, see the Cisco BTS 10200 Softswitch CLI Database.
Table 5-2 shows how the specification of values for the CT restriction tokens determines the way that CT for a business group is processed.
There is an interaction when a Centrex subscriber has all three of the following features assigned and active:
• Call hold—CHD
• Call waiting—CW or CIDCW or both
• Call forwarding on no answer—CFNA
BTS does not invoke forwarding for incoming calls. For the subscriber to have call waiting features (CW or CIDCW) and CFNA active simultaneously, do not assign CHD to the subscriber.
Do not assign call waiting tone CWT_TYPE to SIP subscribers because their endpoint controls the call waiting tone, not the BTS.
Table 5-2 Call Transfer Restrictions Determine Call Transfer Processing
This feature is activated by default when it is assigned to a subscriber. CW can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate CW:
Interaction between CHD and CW for a Centrex SubscriberWhen a centrex subscriber has both CHD and CW feature, the centrex subscriber can connect to a waiting call using the only the Flash button or hookswitch without having to dial the vertical service code (VSC) for CHD to enable CHD.
To provision this feature, set the type token in the feature-config table to CW-OVER-CHD while configuring the feature_config table for the CW feature. CW-OVER-CHD can take two values—Y and N.
To set the value of the CW-OVER-CHD token to Y, enter the following command:
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step must be performed.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
This feature is deactivated by default when it is assigned to a subscriber. CWD can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate CWD:
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber.
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
The CIDCW feature requires the subscriber to already have the CND or CNAM feature assigned. The CND or CNAM feature enables the subscriber to see the calling party’s information while ringing on a basic call and is a prerequisite before subscribing to the CIDCW feature.
Alternate Activation and Deactivation Method
This feature is activated by default when it is assigned to a subscriber. CIDCW can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step is required.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Calling Line Identity Presentation, Restriction Provisioning for the CLIP and CLIR features is identical to CND and CNDB respectively, except for the change in feature-name. (See provisioning for CND and CNDB).
Note The CLIP feature is associated with and must be provisioned in combination with CND or CNAM, depending on customer requirements.
The trunk-grp-service-profile table associates a trunk group to services. In the above command, the service-id i= 1 corresponds to CNAM service as provisioned.
In addition to assigning the CNAM service to a trunk group, as described above, for the feature to be fully functional for SS7 and ISDN, additional provisioning is required as follows:
• For an outgoing SS7 trunk group, in order for the calling name information to be included in the IAM, the following parameter needs to be set in the ANSI trunk group profile:
change SS7-ansi-tg-profile id=SS7pf1; SEND_GN=Y;
• For ISDN NI2, in order for the calling name information to be included in the outgoing SetUp message, the following parameter needs to be set in the ISDN D-channel profile:
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning to a POTS subscriber. In addition, the following step must be performed:
For the feature, in addition to basic Centrex Office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, perform the following step.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step must be performed.
Step 1 Add the feature into the Custom-dial-plan table for the Centrex group:
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step must be performed.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
Step 5 (Optional) The timer to play the prompt tone for account and authorization codes on the media gateway is configurable via CLI. The delayed request applies only to trunks without a main-subscriber or to trunks with a main-subscriber whose category is PBX.
Note The ID values in the audio-seq table should be cos_auth_prm_seq for authorization code prompt and cos_acct_prm_seq for account code prompt as shown in the above steps; otherwise the announcements are not played.
Step 8 Add/modify configurable timer values for IVR interaction:
Codec SelectionCodec selection allows calls to be established using a variety of encoding and decoding DSP devices (codec) to compress voice for transmission via the RTP. With the proper codec selection for calls, bandwidth can be conserved, allowing more calls to be carried on the same equipment and improving the economics of the VoIP solution.
Custom Dial Plan The following subsections identify necessary steps for provisioning the Custom Dial Plan (CDP) feature.
Step 3 (Optional) For Usage-Sensitive COT behavior in the switch, add the ca-config table if your default office service id needs to be different from factory assigned defaults:
This feature is applicable for MLHG_CTX only. MLHG provisioning is similar to Centrex provisioning.
Distinctive Alerting/Call Waiting Indication
Note For the distinctive call-waiting tones to be played, either the Call Waiting feature or the Call Waiting Deluxe feature must also be assigned and active on the subscriber line.
MLHG provisioning is similar to subscriber provisioning as described above.
Alternate Activation and Deactivation Method
This feature is deactivated by default when it is assigned to a subscriber. DND can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate DND:
For the feature, in addition to basic Centrex Office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following steps must be performed.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Alternate Activation and Deactivation Method
This feature is deactivated by default when it is assigned to a subscriber. HOTV can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate HOTV:
Incoming Simulated Facility Group The following subsections identify necessary steps for the Incoming Simulated Facility Group (ISFG) feature to be offered.
add call-ctrl-route id=holly-ccr; routing-key-id=NewMatedSG-rk; dpc-id=hollyville; user-part-variant-id=ANSISS7_GR317; si=ISUP; description=Call Control Route for ANSI ISUP DPC;
add call-ctrl-route id=haven-ccr; routing-key-id=NewMatedSG-rk; dpc-id=havenville; user-part-variant-id=ANSISS7_GR317; si=ISUP; description=Call Control Route for ANSI ISUP DPC;
Step 9 Add the SS7 trunk group, trunks, routing to the SS7 network destination, dial plan and equip the trunk group terminations according to your network setup, if not already done so.
Step 10 Control CA SCTP-assoc INS
control sctp-assoc id=CA-assoc1;mode=forced;target-state=ins;control sctp-assoc id=CA-assoc2;mode=forced;target-state=ins;
control sctp-assoc id=CA-assoc3;mode=forced;target-state=ins;control sctp-assoc id=CA-assoc4;mode=forced;target-state=ins;
NSO Configuration: D-link for TCAP with ASP Load Sharing
Step 1 Add the Signaling Gateways with internal redundancy mode set to SSO-NSO.
add opc id=opc1; point-code=250-250-3; point-code-type=ANSI_CHINA;description= Network Point Code 1;add dpc id=cap_dpc1;point-code=1-101-0;point-code-type=ANSI_CHINA;description=Capability Point Code for remote STP with GTT;add dpc id=office2; point-code=250-250-3; description= Destination point code for IMT;
Step 5 FSAIN & FSPTC feature server SCTP associations for LNP, 800, CNAM & AC/AR services
add routing-key id=NewMatedSG-rk1; opc-id=opc1; sg-grp-id=sg-grp100;si=sccp;subsystem-grp-id=SSN_LNP1;platform-id=FSAIN205; rc=161; description=Routing Key for SUA User Adaptation layer;add routing-key id=NewMatedSG-rk2; opc-id=opc1; sg-grp-id=sg-grp100; si=sccp;subsystem-grp-id=SSN_AIN_800_1;platform-id=FSAIN205; rc=162; description=Routing Key for SUA User Adaptation layer in FSAIN205;add routing-key id=NewMatedSG-rk3; opc-id=opc1; sg-grp-id=sg-grp100; si=sccp;subsystem-grp-id=SSN_CNAM1;platform-id=FSPTC235; rc=163; description=Routing Key for SUA User Adaptation layer in FSPTC235;add routing-key id=NewMatedSG-rk4; opc-id=opc1; sg-grp-id=sg-grp100;si=sccp;subsystem-grp-id=SSN_ACR1;platform-id=FSPTC235; rc=164;description=Routing Key for SUA User Adaptation layer in FSPTC235;
Step 11 Add SCCP routes for LNP, CNAM, 800 and ACR
add sccp-route opc-id=opc1; dpc-id=cap_dpc1; rk-id=NewMatedSG-rk1; subsystem-grp-id=SSN_LNP1;description=SCCP route for FSAIN LNP service;add sccp-route opc-id=opc1;dpc-id=cap_dpc1;rk-id=NewMatedSG-rk2;subsystem-grp-id=SSN_AIN_800_1;description=SCCP route for 800 service in FSAIN;add sccp-route opc-id=opc1;dpc-id=cap_dpc1;rk-id=NewMatedSG-rk3;subsystem-grp-id=SSN_CNAM1;description= SCCP route for FSPTC CNAM service;add sccp-route opc-id=opc1;dpc-id=office2;rk-id=NewMatedSG-rk4;subsystem-grp-id=SSN_ACAR1;description= SCCP route for FSPTC ACAR service;add call-ctrl-route id=office2-ccr; routing-key-id=NewMatedSG-rk;dpc-id=office2;user-part-variant-id=ANSISS7_GR317; si=ISUP; description=Call Control Route for Office2 destination;
Step 12 Add SS7 trunk group for AC/AR service, the Call Agent configuration for TCAP services, the SLHR profile, the SLHR, and configure the 800 dialing and ported office codes for your network setup.
Step 13 Control FSAIN SCTP association into service.
control sctp-assoc id=FSAIN-assoc1;mode=forced;target-state=ins;control sctp-assoc id=FSAIN-assoc2;mode=forced;target-state=ins;control sctp-assoc id=FSAIN-assoc3;mode=forced;target-state=ins;control sctp-assoc id=FSAIN-assoc4;mode=forced;target-state=ins;
Step 14 Control the FSPTC SCTP association into service.
control sctp-assoc id=FSPTC-assoc1;mode=forced;target-state=ins;control sctp-assoc id=FSPTC-assoc2;mode=forced;target-state=ins;control sctp-assoc id=FSPTC-assoc3;mode=forced;target-state=ins;control sctp-assoc id=FSPTC-assoc4;mode=forced;target-state=ins;
Limited Call Duration
Step 1 Create a NOD escape list for the LCD_TRIGGER so the system will allow certain types of calls (such as repair calls without AAA server authorization.
Step 8 (Optional) When the LCD_TRIGGER is invoked, but for some reason the LCD_TRIGGER fails, this flag is used to determine the action to be taken. If the flag is set to Y, the call is released, else the call is continued. By default, this value is set to Y. If required by your local business office, you can change this value to N.
Note Note If this parameter is set to N and the LCD_TRIGGER fails, the call will be given for free to the caller.
Note The hb_timeout and max_path_retrans tokens are not configurable via the CLI change command. To configure or change these values, a new SCTP association profile must be added.
control sctp-assoc id=sctp_assoc1; mode=FORCED; target-state=INS;
Step 17 Place the Subsystem Group In Service:
control subsystem-grp id=SSN_LNP; mode=FORCED; target-state=INS;
Subscriber Provisioning
Step 1 below shows the LNP-TRIGGER usage during the porting transition. At the start of the porting process, the subscriber status remains assigned, and the LNP-TRIGGER indication will cause an LNP query. If the SCP database query result indicates that the porting has not occurred yet (no LRN is received), then the call is routed locally to the subscriber. Otherwise, if the SCP returns the LRN of another switch, the porting has occurred, and the call is routed onward to the recipient switch using the LRN.
Note The use of LNP-TRIGGER is optional. You may prefer to not use LNP-TRIGGER but instead mark the subscriber status as PORTED-OUT when porting occurs (see Step 2).
Step 2 shows the marking of a subscriber's DN as ported-out of this donor switch. After an LNP query, the call should be routed to the recipient switch using the Location Routing Number (LRN).
Step 1 (optional) Indicate that an LNP query should be performed to determine whether the subscriber has ported-out (or not):
• When the ported office code is served by the switch then during the transition period, the LNP-TRIGGER in the Dn2subscriber table should be set to Y. Once porting is complete, the status should be modified to = PORTED-OUT. If the subscriber is porting in, the LNP-trigger should be changed to N once porting is complete.
• BTS 10200 always checks the Dn2subscriber table to see if the called number is in the BTS before performing LNP query. If the LNP-TRIGGER flag is set to Y, an LNP query is performed by the BTS. If the subscriber is porting in and porting is complete, the LNP Query returns the LRN of BTS and the call is terminated locally. If no LRN is received or if the LRN does not belong to BTS, the call is routed out. If the subscriber is porting out and porting is complete, the LNP Query returns LRN of the recipient switch and the call is routed out. If no LRN is received, the call is terminated locally.
• If the SUBSCRIBER-STATUS field in the Dn2subscriber table is set to PORTED-OUT, then a query will be performed by the BTS even if the LNP-TRIGGER field in the Dn2subscriber table is set to N.
• If the LNP trigger is generated by the trunk (SS7,CAS) calls and no calling party is received in the setup indication (IAM), ensure that the JIP field or LRN field in the POP table associated with the trunk group is set to the appropriate value. If not, the SCP query will fail.
Local Number Portability for ITU Local BTS Database Query In ITU/European markets, the LNP feature performs a query of an internal BTS database. Since an external SS7 TCAP query is not needed, SIGTRAN provisioning is not required. The following subsections identify necessary steps for the LNP feature to be offered in European markets.
Office Provisioning
Step 1 Create a feature for the LNP database lookup.
add/change feature fname=LNP; tdp1=COLLECTED_INFORMATION; tid1=LNP_TRIGGER; ttype1=R; description=local number portability;feature_server_id=FSAIN205;
Step 2 Add this feature to the default office service Id (assuming default office service id=999):
add/change service id=999; fname1=LNP;add ca-config type=DEFAULT-OFFICE-SERVICE-ID; datatype=string; value=999;
Step 3 Add one of the following LNP Profile examples:
a. Add switch-based LNP Profile for All Calls Query (ACQ):
The following sequence shows the marking of a subscriber's DN as ported-out of this donor switch. After an LNP query, the call should be routed to the recipient switch using the Routing Number (RN).
Step 1 Prepare to delete subscriber and mark as ported-out:
control subscriber-termination id=sub1; mode=graceful; target-state=oos;
Step 2 Delete the subscriber (see note for Step 3):
delete subscriber id=sub1;
Step 3 Mark deleted subscriber ported-out (ported-out of this donor switch to the recipient switch).
Note As soon as this command is executed, calls may be mis-routed unless this switch, and others in the network, have the correct RN and associated routing configured to the new recipient switch to which this DN has ported-in. It is expected that the recipient switch also has service subscribed and activated for this DN, which has ported-in to the recipient switch.
Although it is not customary to include basic dial plan and related provisioning in this document, it must be understood to understand the provisioning of Local LNP for ITU/Europe.
The following example shows selected commands for the following scenario:
A subscriber's dial-plan-profile has a noa-route-profile specified, pointing to a destination, which in turn points to an "RN dial-plan", used to route the call using the Routing Number (RN) prefix.
The digit translation flow for a Called Party Number with NoA=8 (ported number with routing number contatenated with directory number) is as follows (note, the objects are added in reverse order in the provisioning example):
Step 6 This destination, from the RN dial-plan, does not allow an LNP query (NO-LNP-QUERY). Since an RN was used for routing to this destination, a second query should not be allowed:
add destination dest-id=dest_sub_rn_itu; call-type=LOCAL; route-type=SUB; ani-digman-id=dm_dest_sub_ani; acq-lnp-query=NO-LNP-QUERY;description=ITU Sub dest after RN routing: do not allow LNP query;
Step 7 NOA Route for ported NOA points to this destination. This destination in turn points to the RN dial-plan:
add destination dest-id=dummy_rn_itu; call-type=LOCAL; route-type=DP; dial-plan-id=dp_rn_itu; description=dummy destination used for NOA Routing to point to RN dial-plan;
Step 8 The RN dial-plan, after stripping the RN (of this switch), routes on the subscriber DN prefix 1150:
Step 9 The RN dial-plan, after stripping RN (of this switch), routes to destination based on full digit string of ported in subscriber with DN 1-702-3001:
add noa-route-profile id=noa_rt; description=NOA Route profile (ITU) to RN dial-plan;
Step 18 Add the NOA route for logical ported number NoA (ITU NoA=8, RN concatenated with DN). The destination identified here will point to the RN dial-plan:
Step 20 Add the dn2rn (Directory Number to Routing Number). All DNs that are ported in to this switch must have a dn2rn entry with the RN value associated with this switch:
add dn2rn dn=17023001; rn=4001;
Step 21 Add dn2rn entries with the RNs associated with all DNs that are ported out of this switch and all RNs needed to route calls to any ported DN in the network/country :
add dn2rn dn=11501522; rn=4101;
Step 22 Prepare to delete the subscriber and mark as ported-out:
control subscriber-termination id=sub1; mode=graceful; target-state=oos;
Step 23 Delete the subscriber (see note for Step 24):
delete subscriber id=sub1;
Step 24 Mark deleted subscriber ported-out.
Note As soon as this command is executed, calls may be mis-routed unless this switch, and others in the network, have the correct RN and associated routing configured to the new recipient switch to which this DN has ported-in (see add dn2rn above). It is expected that the recipient switch also has service subscribed and activated for this DN, which has ported-in to the recipient switch.
Usually, LNP queries for ACQ or QoR occur on the originating switch, in the originating network. However, in some cases the originating switch does not perform LNP queries, for example:
• Originating switch does not have LNP capability
• Originating switch is an International Gateway exchange which does not have access to the country specific LNP database
• At the point of interconnect (POI) between operators of separate networks (e.g., Telco and alternate service operator), a full, routable RN is not available. For example, in Denmark, a ported DN with NoA=112 does not supply the RN, and in Sweden, with NoA=8, the called party number digits may contain a partial RN (the RN indicates the recipient network operator but does not indicate the exact recipient switch ID). In this case, a second LNP query is required to obtain a full routable RN.
The following example shows how to allow queries on incoming calls for a particular trunk group.
Step 1 Allow queries on this trunk group:
change trunk-grp id=1; perform-lnp-query=Y;
Destination and Call Type ACQ Control
If desired, an All Calls Query (ACQ) can be selectively controlled in the destination obtained as a result of digit translation. In some cases, ACQ is desired for 100% of call originations, in which case all destinations may have ACQ-LNP-QUERY=PERFORM-LNP-QUERY, or NA. The NA value, meaning not applicable, indicates that either LNP is not applicable on this destination or that the destination should not be used as criteria on whether to perform an ACQ LNP query. LNP Profile and trunk group values will determine whether a query is performed or not.
For countries where two or more LNP queries are necessary, destinations with ACQ-LNP-QUERY=PERFORM-LNP-QUERY will allow the second query. For example, in Denmark an incoming call with NoA=112 and called party number contain a DN only requires another query, so destinations reached via NOA Routing for NOA=PORTED-NUMBER-WITHOUT-RN should allow have PERFORM-LNP-QUERY value. Likewise, in Sweden, a call with NoA=8 and a partial RN (indicating operator, but not identifying the exact recipient switch), uses a dial-plan entry with the partial RN (of this network) to select a destination with PERFORM-LNP-QUERY to force a second query for a call entering the recipient network.
ACQ-LNP-QUERY=NO-LNP-QUERY will prevent an ACQ query from being performed on this call. This may be used for certain calls for which a query should never be performed (e.g., outgoing calls to a carrier), or after an LNP query has been performed (on this switch, or another), such that NOA Routing and the RN dial-plan select destinations with NO-LNP-QUERY to prevent a second (unnecessary) query.
ACQ-LNP-QUERY=ACQ-BASED-ON-CALL-TYPE will use the call type table entry to determine whether a query will be performed (see examples below).
The destination ACQ criteria in this section only affects All Calls Query (ACQ). These values have no effect on decision criteria for ODBR or QoR queries.
The following examples demonstrate control over ACQ queries using the Destination table:
• Destination not used as LNP ACQ query criteria. LNP-Profile table ALL-CALL-QUERY (and trunk group table PERFORM-LNP-QUERY, for an incoming trunk call) determine whether a query is required.:
• Omission of call-type entry implicitly indicates that no query will be performed. For example, call-type=EMG need not be added to block queries on emergency calls.
• Call type explicitly prevents ACQ for this call type:
Some operators may prefer to NOT perform ACQ LNP queries on subscriber originated outbound calls to a carrier, or alternatively, may desire to allow queries on all, or speficied, carrier calls. Outgoing carrier calls may be dialed explicitly by dialing a digit prefix which translates via the dial plan to a destination with route-type=carrier and a carrier ID specified. Or, for a destination with call-type of intralata or interlata, the default carrier from the calling party's subscriber table entry may be used (PIC1 or PIC2).
Regardless of the method for determining the carrier (and its associated carrier data), for an LNP ACQ query to be performed on a outbound carrier call, the destination arrived at via the dial plan translation must allow a query. If a query is allowed in the destination table (ACQ-LNP-QUERY=PERFORM-LNP-QUERY or NA, or ACQ-BASED-ON-CALL-TYPE with call-type table LNP-QUERY=Y), then the applicable carrier table is used to further determine whether a query is allowed or not.
If the carrier indicates USE-DIAL-PLAN=Y, then the carrier entry is not used as criteria for an LNP query. Otherwise, if USE-DIAL-PLAN=N, then the carrier entry LNP-QUERY=Y/N is used to determine whether or not a query is allowed on the carrier call. Note that , for an ACQ query to be allowed, ACQ must be allowed at all levels, including the LNP Profile table ALL-CALL-QUERY=Y, incoming trunk group PERFORM-LNP-QUERY=Y (if it is an incoming trunk call), destination, and carrier (if applicable, as described above).
Note For a call that uses a pre-subscribed PIC2 carrier, the caller must have a POP assigned (for example, in the Subscriber Profile table), and the associated Pop table entry must have ITP=Y.
Provisioning Notes/Caveats
• Ported-office-code is not currently used for ITU Local LNP.
• Subscriber dial-plan (used for subscriber originations), and associated digit-map normally should not allow a regular subscriber to dial a routing number prefix. The only exception is for countries where there is overlap between the RN and DN prefix (for example, RN may be 4001, and some DNs may start with 4001, such that the Nature of Address, or NoA, must be used to distinguish between the two).
• NOA routing is not required for LNP but is recommended for the following cases:
• If the RN and min/max-digit length combination does not uniquely identify the routing. For example, in Hungary, some DNs start with a prefix that is the same as some NoA, so it is not possible to unambiguously identify the route. Therefore, NOA routing allows the Nature of Address value for ported numbers to be used to select a separate RN dial-plan with routes for RNs. The regular subscriber/trunk dial-plan has routes based on DNs, and for a ported number NoA, NOA routing selects an RN dial-plan with routes for RNs.
• If All Call Query (ACQ) is required for some calls, but not others, then the Destination table (resulting from digit translation) ACQ-LNP-QUERY value controls whether a query is performed or not. The regular subscriber/trunk dial-plan for certain digit-string values routes to destinations that may allow an LNP query. However, for DNs that are ported, for which a database query has returned an RN, then NoA routing is used to select an RN dial-plan, and this dial-plan selects destinations that do not allow a (second) LNP query.
• All Call Query (ACQ) criteria: An ACQ will only result if a query is allowed at all applicable levels. That is, the LNP Profile must indicate ALL-CALL-QUERY-Y, and the destination obtained as a result of digit translation must allow a query (either in the Destination, or Call Type table entry, if applicable). Furthermore, if the call has a trunk origination, then ACQ must also be allowed by the incoming trunk group (PERFORM-LNP-QUERY-Y).
• If LNP criteria for a query is met, but a query to the FSAIN feature server is not requested (Service Switching Function, SSF, does not generate Invite with Notify towards FSAIN), check the ca-config type=DEFAULT-OFFICE-SERVICE-ID and its associated service, ca-config type=DEFAULT-LNP-PROFILE-ID, and LNP Profile values (see above).
• If digit translation fails to find a match in the dial-plan for a digit-string which is configured in the dial-plan, check the dial-plan-profile nanp-dial-plan=N (for non-North America dial-plans), and check that the dial-plan entry has noa=unknown.
• The ISUP hop count may be the only protection from routing loops in some cases. For example, with ODBR or QoR, during the transition period of the "porting window", it is possible that calls will be misrouted due to inconsistencies in the timing of provisioning changes in the donor switch, recipient switch, and central database (if applicable). Normally this situation will be temporary, until the appropriate changes are configured on all the network nodes. However, it is suggested that the ss7_q761_tg_profile hop-count be set to a relatively low value, such as 5 or less, which will minimize the consequences of routing loops.
• If a DN is allowed to port from one operator or exchange to another, and then port again, the dn2subscriber table status token should only be set to PORTED-OUT on the first exchange, that is, the exchange owning the DN number block prefix of the DN being ported. On an exchange for which the DN is porting out, which is not the original donor exchange, the following procedure is
recommended for exchanges that perform ODBR or QoR queries. During the porting transition phase, the subscriber record can be set to status=TEMP_DISCONNECTED, or taken out of service, to prevent routing loops. After the porting window is over, the subscriber and dn2subscriber records can be deleted. Routing loops, although unlikely if proper procedures are used and the timing of changes on various networks nodes are synchronized, may be possible for example if two exchanges both mark the DN as ported-out, and each exchange does a query and retrieves the RN or the other switch.
Long Duration Call CutoffThe LONG-DURATION-CALL-CUTOFF-TMR parameter has been added to the CA-CONFIG table (see Table 5-3).
Note For complete CLI information, see the Cisco BTS 10200 Softswitch CLI Database.
Multiline Variety PackageThis section describes the provisioning steps that you must complete to provision the MVP feature for a group of subscribers. You must provision a custom dial plan (CDP) for a group of subscribers. Thereafter, all MVP groups can share the single custom dial plan (that is, all subscribers who belong to different MVP groups).
Note If you provision a CDP for an MVP Centrex group, the CDP must be mutually exclusive from any regular Centrex group that you provision.
Step 1 Create a custom Dial-Plan-Profile and Dial-Plan entries.
a. Define a custom dial-plan ID.
add custom_dial_plan_profile id=MVPcdp;
b. Define a custom dial-plan to access a plain old telephone service (POTS) line. Specify a new nature of dial (NOD) to indicate POTS access but without any prefix (such as a requirement to dial 9). In the following example, the “xxxxxxx” specified for digit string indicates that the dialed digit string can be any digits (0–9) and that the usual PSTN dial-plan is used to route the call.
INTEGER (0–48) Indicates the timer value for the Long Duration Call Cutoff.
0 indicates that timer is not set and the call is not cut off. Any integer value between 1 and 48 indicates that the call is cut off after the specified number of hours.
Note When you provision a CDP for MVP Centrex, you should not specify a NOD with the values EXTENSION, POTS_ACCESS, or ATTENDANT_ACCESS (which are specified for regular Centrex provisioning).
c. Define the digit string for the speed call feature.
d. Define the VSC codes for features that are used by the MVP subscribers. In the example below, dialed digit *72 is mapped to the call-forward-unconditional-activation feature, *73 is mapped to the call-forward-unconditional-deactivation feature.
Note MVP provisioning is the reverse of regular Centrex provisioning. A subscriber in a MVP Centrex group must dial an access code (#) and then the extension to call another subscriber within the MVP group. There is no need to dial an access code to place an external call.
If you provision # as the access code for internal calls, you must specify * as the access code for VSC provisioning.
Step 2 Define the digit map to define how media gateways collect digits dialed by the subscribers.
Step 3 Create a subscriber profile to be shared by all subscribers in multiple MVP groups. If a subscriber profile exists for the subscribers who are associated with the MVP group, this step can be omitted.
Step 4 Creating the MVP group requires two steps. First you create a main subscriber for each MVP group. Second you create a Centrex group for the main-subscriber that uses the custom dial-plan defined in Step 1. Repeat the commands in this step for each MVP group you create on the Cisco BTS 10200.
Note The last command creates a Call Park Subscriber Group and is required only if CALL-PARK feature is assigned to the MVP group (through the CDP defined in Step 1).
Step 5 Issue the following commands to associate the existing subscribers to the MVP group defined in Step 4.
a. In the following example, three subscribers SubA, SubB, and SubC (existing subscribers) on the BTS 10200 are assigned to the MVP group 1 created in Step 4.
Caution When you specify a value for the EXT (extension) token in the ext2subscriber table, do not include the character * or the character #.
Multi-Line Hunt Group See Announcements, Centrex, MLHG, Voice Mail, and ENUM, for directions for provisioning a MLHG.
Multi-Lingual Support for Interactive Voice Response and AnnouncementsThe Multi-Lingual Support (MLS) for Interactive Voice Response (IVR) and Announcements feature allows subscribers to choose which language (English, French, Spanish) to hear.
The following subsections identify the necessary steps to provision the MLS for IVR and announcements feature.
add language id=eng; announcement-file-prefix=eng_; announcement-number-prefix=1; add language id=fra; announcement-file-prefix=fra_; announcement-number-prefix=2; add language id=spa; announcement-file-prefix=spa_; announcement-number-prefix=3;
Step 3 Add audio segments for MLS * code functionality:
add audio-segment; id=WELCOME; type=PHYSICAL; url=file://welcome.wav; description=Welcome;add-audio-segment; id=YouAreAbout; type=PHYSICAL; url=file://YouAreAbout.wav; description=You are about to change your language of choice; add audio-segment; id=FOR; type=PHYSICAL; url=file://for.wav; description=For; add audio-segment; id=ENGLISH; type=PHYSICAL; url=file://english.wav; description=English;add audio-segment; id=PRESS; type=PHYSICAL; url=file://Press.wav; description=Press;add audio-segment; id=SPANISH; type=PHYSICAL; url=file://spanish.wav; description=Spanish;add audio-segment; id=FRENCH; type=PHYSICAL; url=file://french.wav; description=French;add audio-segment; id=var_audio; type=VARIABLE; var-type=str; description=audio file;add audio-segment; id=YouHaveSelected; type=PHYSICAL; url=file://YouHaveSelected.wav; description=You have selected;add audio-segment; id=AsYourLanguageOfChoice; type=PHYSICAL; url=file://AsYourLanguageOfChoice.wav; description=As your language of choice;add audio-segment; id=ToConfirm; type=PHYSICAL; url=file://ToConfirmYourChoice.wav; description=To confirm your choice;add audio-segment; id=ToExit; type=PHYSICAL; url=file://ToCancelWithoutSaving.wav; description=To cancel without saving;add audio-segment; id=YourLanguageOfChoice; type=PHYSICAL; url=file://yourlanguageofchoiceisnow.wav; description=Your language of choice is now;add audio-segment; id=var_digits; type=VARIABLE; var-type=dig; var-subtype=gen; description=string;add audio-segment; id=var_sign; type=VARIABLE; var-type=str; description=sign(*,#);add audio-segment; id=var_number; type=VARIABLE; var-type=num; var-subtype=crd; description=number;add audio-segment; id=var_time; type=VARIABLE; var-type=tme; var-subtype=t24; description=time;add audio-segment; id=var_day; type=VARIABLE; var-type=wkd; description=weekday;add audio-segment; id=var_audio; type=VARIABLE; var-type=str; description=audio file;
Step 4 Add MLS audio sequences:
add audio_seq id=MLS_WELCOME;language_id=def; seq=WELCOME,YouAreAbout,FOR,ENGLISH,PRESS,var_digits,FOR,SPANISH,PRESS,var_digits,FOR,FRENCH,PRESS,var_digits; description=Welcome. You are about to change your language of choice. For English press <d>. For Spanish press <d>. For French, press <d>.add audio_seq id=MLS_RECONFIRM;language_id=def; seq=YouHaveSelected,var_audio,AsYourLanguageOfChoice,ToConfirm,PRESS,var_digits,ToExit,PRESS,var_digits; description=You have selected <lang> as your language of choice. To confirm your choice, press <d>. To cancel without saving, press <d>.add audio_seq id=MLS_RELEASE;language_id=def; seq=YourLanguageChoice,var_audio; description=Your language of choice is now <lang>.
For this feature, Centrex subscriber provisioning is similar to the provisioning of a POTS subscriber.
MLHG Provisioning
For this feature, MLHG provisioning is similar to subscriber provisioning.
Multiple Directory Number When this feature is enabled for a subscriber, any CALEA provisioning should include both the main number and all virtual numbers to accomplish bi-directional (incoming and outgoing) surveillance.
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber.
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
One of the three FDN values assigned in sub-feature-data must be the subscriber’s primary DN.
If the number of DNs is less than the number of available ring or call waiting tones, be sure the tone for the primary DN is different from the secondary DN tone during configuration.
No Solicitation Announcement
Office Provisioning
Step 1 Create the NSA Activation (NSA_ACT) feature:
add audio-segment; id=NSA_1; type=PHYSICAL; url=file://nsa_1.wav; description=You have reached a number that does not accept solicitations. If you are a solicitor, please add this number to your do-not-call list and hang up now. Otherwise, press;
add audio-segment; id=NSA_2; type=PHYSICAL; url=file://nsa_2.wav; description=or stay on the line;
add audio-segment; id=AUTH_1; type=PHYSICAL; url=file://auth_1.wav; description=Please enter your password now;
add audio-segment; id=AUTH_2; type=PHYSICAL; url=file://auth_2.wav; description=We are sorry, the password you entered is incorrect. Please hang up and try your call later;
add audio-segment; id=AUTH_3; type=PHYSICAL; url=file://auth_3.wav; description=You must now change your password. Please enter a new password now
add audio-segment; id=AUTH_4; type=PHYSICAL; url=file://auth_4.wav; description=Your password has been changed to
add audio-segment; id=AUTH_5; type=PHYSICAL; url=file://auth_5.wav; description=If you are satisfied with this password please press
add audio-segment; id=AUTH_6; type=PHYSICAL; url=file://auth_6.wav; description=now. To reenter the password, please press
add audio-segment; id=AUTH_7; type=PHYSICAL; url=file://auth_7.wav; description=Press <d> to reset your password or dial
Step 5 .Add NSA_ACT SLE audio segment:
add audio-segment; id=SLE_1_1; type=PHYSICAL; url=file://sle_1_1.wav; description=service is currently;
add audio-segment; id=SLE_1_2; type=PHYSICAL; url=file://sle_1_2.wav; description=on your list;
add audio-segment; id=SLE_1_3; type=PHYSICAL; url=file://sle_1_3.wav; description=You may dial during the announcements for faster service. When you have finished, hang up;
add audio-segment; id=SLE_3_1; type=PHYSICAL; url=file://sle_3_1.wav; description=To turn this service;
add audio-segment; id=SLE_3_2; type=PHYSICAL; url=file://sle_3_2.wav; description=To add an entry, press
add audio-segment; id=SLE_3_3; type=PHYSICAL; url=file://sle_3_3.wav; description=To remove one or more entries, press
add audio-segment; id=SLE_3_4; type=PHYSICAL; url=file://sle_3_4.wav; description=To hear the entries on your list, press
add audio-segment; id=SLE_11_3; type=PHYSICAL; url=file://sle_11_3.wav; description=for instructions or hang up;
add audio-segment; id=SLE_13_1; type=PHYSICAL; url=file://sle_13_1.wav; description=To turn on this service, you must add an entry to your list. To add an entry, please press;
add audio-segment; id=SLE_13_2; type=PHYSICAL; url=file://sle_13_2.wav; description=If you wish to hear this announcement repeated, please dial;
add audio-segment; id=SLE_14_1; type=PHYSICAL; url=file://sle_14_1.wav; description=Dial the number to be added, then press;
add audio-segment; id=SLE_14_2; type=PHYSICAL; url=file://sle_14_2.wav; description=To add the last calling party, press;
add audio-segment; id=SLE_14_3; type=PHYSICAL; url=file://sle_14_3.wav; description=then press the
add audio-segment; id=SLE_14_4; type=PHYSICAL; url=file://sle_14_4.wav; description=To add an extension, press
add audio-segment; id=SLE_14_5; type=PHYSICAL; url=file://sle_14_5.wav; description=To add a wildcard, press
add audio-segment; id=SLE_15_1; type=PHYSICAL; url=file://sle_15_1.wav; description=Dial the number to be removed, then press
add audio-segment; id=SLE_15_2; type=PHYSICAL; url=file://sle_15_2.wav; description=To remove all entries, dial
add audio-segment; id=SLE_15_3; type=PHYSICAL; url=file://sle_15_3.wav; description=To remove just the anonymous entries, dial
add audio-segment; id=SLE_15_4; type=PHYSICAL; url=file://sle_15_4.wav; description=To remove an extension, press
add audio-segment; id=SLE_15_5; type=PHYSICAL; url=file://sle_15_5.wav; description=To remove a wildcard, press
add audio-segment; id=SLE_16_1; type=PHYSICAL; url=file://sle_16_1.wav; description=We are sorry. The number of the last calling party is not available;
add audio-segment; id=SLE_16_2; type=PHYSICAL; url=file://sle_16_2.wav; description=Please start again, or dial;
add audio-segment; id=SLE_17; type=PHYSICAL; url=file://sle_17.wav; description=The number you have added is an anonymous entry;
add audio-segment; id=SLE_18; type=PHYSICAL; url=file://sle_18.wav; description=The number you have added is;
add audio-segment; id=SLE_19; type=PHYSICAL; url=file://sle_19_1.wav; description=We are sorry. Your list is full. You must remove an entry before adding another. Please try other options or dial;
add audio-segment; id=SLE_20_1; type=PHYSICAL; url=file://sle_20_1.wav; description=We are sorry. Please try adding the number in a few minutes;
add audio-segment; id=SLE_20_2; type=PHYSICAL; url=file://sle_20_2.wav; description=Please continue or dial;
add audio-segment; id=SLE_21_1; type=PHYSICAL; url=file://sle_21_1.wav; description=We are sorry. The number you have dialed is not a valid number. Please try again later.;
add audio-segment; id=SLE_22; type=PHYSICAL; url=file://sle_22.wav; description=We are sorry. There are no entries on your list. Please try other options or dial
add audio-segment; id=SLE_23; type=PHYSICAL; url=file://sle_23.wav; description=The number you have removed is an anonymous entry;
add audio-segment; id=SLE_24; type=PHYSICAL; url=file://sle_24.wav; description=The number you have removed is;
add audio-segment; id=SLE_25; type=PHYSICAL; url=file://sle_25.wav; description=There are no more entries on your list. Please continue, dial;
add audio-segment; id=SLE_26; type=PHYSICAL; url=file://sle_26.wav; description=There are no more anonymous entries on your list. Please continue, dial;
add audio-segment; id=SLE_27; type=PHYSICAL; url=file://sle_27.wav; description=on your list. Please try other options, or dial;
add audio-segment; id=SLE_28_1; type=PHYSICAL; url=file://sle_28_1.wav; description=To delete an entry, dial
add audio-segment; id=SLE_28_2; type=PHYSICAL; url=file://sle_28_2.wav; description=as soon as you hear it
add audio-segment; id=SLE_29; type=PHYSICAL; url=file://sle_29.wav; description=This is the end of your list;
add audio-segment; id=SLE_30; type=PHYSICAL; url=file://sle_30.wav; description=The first entry on your list is;
add audio-segment; id=SLE_38; type=PHYSICAL; url=file://sle_38.wav; description=The number is already on your list as an anonymous entry;
add audio-segment; id=SLE_39; type=PHYSICAL; url=file://sle_39.wav; description=This number is already on your list;
add audio-segment; id=SLE_40; type=PHYSICAL; url=file://sle_40.wav; description=The number to be removed is not on your list. Please start again, dial
add audio-segment; id=SLE_41; type=PHYSICAL; url=file://sle_41.wav; description=This is the end of your list. Your list is now empty;
Step 6 Add NSA_ACT Time of Day Schedule audio segments:
add audio-segment; id=SLE_TOD; type=PHYSICAL; url=file://sle_tod.wav; description=To schedule this service, press;add audio-segment; id=SLE_TOD_ON; type=PHYSICAL; url=file://sle_tod_on.wav; description=on based on the time-of-day schedule;add audio-segment; id=SLE_TOD_OFF; type=PHYSICAL; url=file://sle_tod_off.wav; description=off based on the time-of-day schedule;add audio-segment; id=TIME_MGMT_01; type=PHYSICAL; url=file://time_mgmt_01.wav; description=Now is;add audio-segment; id=TIME_MGMT_02; type=PHYSICAL; url=file://time_mgmt_02.wav; description=service is scheduled to be on;add audio-segment; id=TIME_MGMT_03; type=PHYSICAL; url=file://time_mgmt_03.wav; description=If you are satisfied with this schedule, please press;add audio-segment; id=TIME_MGMT_04; type=PHYSICAL; url=file://time_mgmt_04.wav; description=now. To set a different time-of-day-schedule, press;add audio-segment; id=TIME_MGMT_05; type=PHYSICAL; url=file://time_mgmt_05.wav; description=Please dial now;
add audio-segment; id=TIME_MGMT_06; type=PHYSICAL; url=file://time_mgmt_06.wav; description=Please enter the start time in 24 hour format;
add audio-segment; id=TIME_MGMT_07; type=PHYSICAL; url=file://time_mgmt_07.wav; description=Please enter the end time in 24 hour format;
add audio-segment; id=TIME_MGMT_08; type=PHYSICAL; url=file://time_mgmt_08.wav; description=Please enter the start weekday, 0 stands for Sunday, 6 stands for Saturday;
add audio-segment; id=TIME_MGMT_09; type=PHYSICAL; url=file://time_mgmt_09.wav; description=Please enter the end weekday, 0 stands for Sunday, 6 stands for Saturday;
add audio-segment; id=TIME_MGMT_10; type=PHYSICAL; url=file://time_mgmt_10.wav; description=That is not a valid time, the time value should be between 0 to 2359, the end time must be later than the start time;
add audio-segment; id=TIME_MGMT_11; type=PHYSICAL; url=file://time_mgmt_11.wav; description=That is not a valid day, the day value should be between 0 to 6;
add audio-segment; id=TIME_MGMT_12; type=PHYSICAL; url=file://time_mgmt_12.wav; description=The new schedule is now applicable;
add audio_seq id=NSA_INVOCATION; language_id=def; seq=NSA_1,var_digits,NSA_2; description=You have reached a number that does not accept solicitations. If you are a solicitor, please add this number to your do-not-call list and hang up now. Otherwise, press <d> or stay on the line;
Step 8 Add NSA_ACT Authentication audio sequence:
add audio_seq id=AUTH_START; language_id=def; seq=AUTH_1; description=Please enter your password now;
add audio_seq id=AUTH_INVALID_PIN; language_id=def; seq=AUTH_2; description=We are sorry, the password you entered is incorrect. Please hang up and try your call later;
add audio_seq id=AUTH_NEW_PIN; language_id=def; seq=AUTH_3; description=You must now change your password. Please enter a new password now;
add audio_seq id=AUTH_REPLAY_PIN; language_id=def; seq=AUTH_4,var_digits,AUTH_5,var_digits,AUTH_6,var_digits; description=Your password has been changed to <ds>. If you are satisfied with this password please press <d> now. To reenter the password, please press <d>;
add audio-seq id=AUTH_END; language_id=def; seq=AUTH_4,var_digits; description=Your password has been changed to <d>;
Step 9 Add NSA_ACT SLE audio sequence:
add audio_seq id=GR220_1_ALL_PUB; language_id=def; seq=YOUR,var_audio,SLE_1_1,var_audio,THERE,var_audio,var_number,var_audio,SLE_1_2,SLE_1_3; description=Your <NSA> service is currently <on/off/tod-on/tod-off>. There <is/are> <no/num> <entry/entries> on your list. You may dial during the announcements for faster service. When you have finished, hang up;
add audio_seq id=GR220_1_ALL_ANM; language_id=def; seq=YOUR,var_audio,SLE_1_1,var_audio,THERE,var_audio,var_number,ANONYMOUS,var_audio,SLE_1_2,SLE_1_3; description=Your <NSA> service is currently <on/off/tod-on/tod-off>. There <is/are> <num> anonymous <entry/entries> on your list. You may dial during the announcements for faster service. When you have finished, hang up;
add audio_seq id=GR220_1_MIXED; language_id=def; seq=YOUR,var_audio,SLE_1_1,var_audio,THERE,var_audio,var_number,var_audio,SLE_1_2,INCLUDING,var_number,ANONYMOUS,var_audio,SLE_1_3; description=Your <NSA> service is currently <on/off/tod-on/tod-off>. There <is/are> <no/num> <entry/entries> on your list, including <num> anonymous <entry/entries>. You may dial during the announcements for faster service. When you have finished, hang up;
add audio_seq id=GR220_3; language_id=def; seq=SLE_3_1,var_audio,DIAL,var_digits,SLE_3_2,var_sign,SLE_3_3,var_sign,SLE_3_4,var_digits,SLE_3_5,var_digits,SLE_3_6; description=To turn this service <on/off>, dial <d>. To add an entry, press <sign>. To remove one or more entries, press <sign>. To hear the entries on your list, press <d>. To hear the instructions repeated, dial <d>. Please dial now;
add audio_seq id=GR220_3_TOD; language_id=def; seq=SLE_3_1,var_audio,DIAL,var_digits,SLE_TOD,var_digits,SLE_3_2,var_sign,SLE_3_3,var_sign,SLE_3_4,var_digits,SLE_3_5,var_digits,SLE_3_6; description=To turn this service <on/off>, dial <d>. To schedule this service, press <d>, To add an entry, press <sign>. To remove one or more entries, press <sign>. To hear the entries on your list, press <d>. To hear the instructions repeated, dial <d>. Please dial now;
add audio_seq id=GR220_7_OTHER; language_id=def; seq=SLE_7,SLE_16_2,var_digits,SLE_16_3; description=We are sorry. The number you have dialed is incorrect. Please start again or dial <d> for instructions.;
add audio_seq id=GR220_7_ACTV; language_id=def; seq=SLE_7; description=We are sorry. The number you have dialed is incorrect;
add audio_seq id=GR220_8; language_id=def; seq=SLE_8; description=We are sorry, the digits dialed are not a valid command;
add audio_seq id=GR220_11; language_id=def; seq=YOUR,var_audio,SLE_11_1,OFF,SLE_11_2,var_digits,SLE_11_3; description=Your <NSA> service is now off. Please continue, dial <d> for instructions or hang up;
add audio_seq id=GR220_12; language_id=def; seq=YOUR,var_audio,SLE_11_1,ON,SLE_11_2,var_digits,SLE_11_3; description=Your <NSA> service is now on. Please continue, dial <d> for instructions or hang up;
add audio_seq id=GR220_13; language_id=def; seq=SLE_13_1,var_sign,SLE_13_2,var_digits; description=To turn on this service, you must add an entry to your list. To add an entry, please press <sign>. If you wish to hear this announcement repeated, please dial <d>;
add audio_seq id=GR220_14; language_id=def; seq=SLE_14_1,var_sign,AGAIN,SLE_14_2,var_digits,SLE_14_3,var_sign,AGAIN,SLE_14_5,var_digits,SLE_14_1,var_sign,AGAIN,SLE_3_6; description=Dial the number to be added, then press <sign> again. To add the last calling party, press <d>, then press the <sign> again. To add a wildcard, press <d>, dial the number to be added, then press <sign> again. Please dial now;
add audio_seq id=GR220_14_EXT; language_id=def; seq=SLE_14_1,var_sign,AGAIN,SLE_14_2,var_digits,SLE_14_3,var_sign,AGAIN,SLE_14_4,var_digits,SLE_14_1,var_sign,AGAIN,SLE_14_5,var_digits,SLE_14_1,var_sign,AGAIN,SLE_3_6; description=Dial the number to be added, then press <sign> again. To add the last calling party, press <d>, then press <sign> again. To add an extension, press <d>, dial the number to be added, then press the <sign> again. To add a wildcard, press <d>, dial the number to be added, then press <sign> again. Please dial now;
add audio_seq id=GR220_15; language_id=def; seq=SLE_15_1,var_sign,SLE_15_2,var_digits,SLE_14_3,var_sign,AGAIN,SLE_15_3,var_digits,SLE_14_3,var_sign,AGAIN,SLE_15_5,var_digits,SLE_14_3,var_sign,AGAIN,SLE_3_5,var_digits,SLE_3_6; description=Dial the number to be removed, then press <sign>. To remove all entries, dial <dd>, then press the <sign> again. To remove just the anonymous entries, dial <dd>, then press the <sign> again. To remove a wildcard, dial <dd>, then press <sign> again. To hear these instructions repeated, dial <d>. Please dial now;
add audio_seq id=GR220_15_EXT; language_id=def; seq=SLE_15_1,var_sign,SLE_15_2,var_digits,SLE_14_3,var_sign,AGAIN,SLE_15_3,var_digits,SLE_14_3,var_sign,AGAIN,SLE_15_4,var_digits,SLE_14_3,var_sign,AGAIN,SLE_15_5,var_digits,SLE_14_3,var_sign,AGAIN,SLE_3_5,var_digits,SLE_3_6; description=Dial the number to be removed, then press <sign>. To remove all entries, dial <dd>, then press the <sign> again. To remove just the anonymous entries, dial <dd>, then press the <sign> again. To remove an extension, dial <dd>, then press <sign> again. To remove a wildcard, dial <dd>, then press <sign> again. To hear these instructions repeated, dial <d>. Please dial now;
add audio_seq id=GR220_16_OTHER; language_id=def; seq=SLE_16_1; description=We are sorry. The number of the last calling party is not available.
add audio_seq id=GR220_16_ACTV; language_id=def; seq=SLE_16_1,SLE_16_2,var_digits,SLE_16_3; description=We are sorry. The number of the last calling party is not available. Please start again or dial <d> for instructions.
Add audio_seq id=GR220_17_OTHER; language_id=def; seq=SLE_17; description=The number you have added is an anonymous entry.
add audio_seq id=GR220_17_ACTV; language_id=def; seq=SLE_17,SLE_11_2,var_digits,SLE_11_3; description=The number you have added is an anonymous entry. Please continue, dial <d> for instruction, or hang up.
add audio_seq id=GR220_18_OTHER; language_id=def; seq=SLE_18,var_audio,var_digits; description=The number you have added is <silence/extension> <d>;
add audio_seq id=GR220_18_ACTV; language_id=def; seq=SLE_18,var_audio,var_digits,SLE_11_2,var_digits,SLE_11_3; description=The number you have added is <silence/extension> <d>. Please continue, dial <d> for instructions, or hang up.;
add audio_seq id=GR220_19; language_id=def; seq=SLE_19,var_digits,SLE_16_3; description=We are sorry. Your list is full. You must remove an entry before adding another. Please try other options or dial <d> for instructions;
add audio_seq id=GR220_20_OTHER; language_id=def; seq=SLE_20_1; description=We are sorry. Please try adding the number in a few minutes;
add audio_seq id=GR220_20_ACTV; language_id=def; seq=SLE_20_1,SLE_20_2,var_digits,SLE_16_3; description=We are sorry. Please try adding the number in a few minutes. Please continue, or dial <d> for instructions;
add audio_seq id=GR220_21_OTHER; language_id=def; seq=SLE_21_1; description=We are sorry. The number you have dialed is not a valid number. Please try again later.;
add audio_seq id=GR220_21_ACTV; language_id=def; seq=SLE_21_1,SLE_20_2,var_digits,SLE_16_3; description=We are sorry. The number you have dialed is not a valid number. Please try again later. Please continue, or dial <d> for instructions;
add audio_seq id=GR220_22; language_id=def; seq=SLE_22,var_digits,SLE_16_3; description=We are sorry. There are no entries on your list. Please try other options or dial <d> for instructions;
add audio_seq id=GR220_23; language_id=def; seq=SLE_23,SLE_11_2,var_digits,SLE_11_3; description=The number you have removed is an anonymous entry. Please continue, dial <d> for instructions, or hang up;
add audio_seq id=GR220_24; language_id=def; seq=SLE_24,var_audio,var_digits; description=The number you have removed is <silence/wildcard/extension> <ds>;
add audio_seq id=GR220_25; language_id=def; seq=SLE_25,var_digits,SLE_11_3; description=There are no more entries on your list. Please continue, dial <d> for instructions, or hang up;
add audio_seq id=GR220_26; language_id=def; seq=SLE_26,var_digits,SLE_11_3; description=There are no more anonymous entries on your list. Please continue, dial <d> for instructions, or hang up;
add audio_seq id=GR220_27; language_id=def; seq=THERE,var_audio,var_number,ANONYMOUS,var_audio,SLE_27,SLE_16_3; description=There <is/are> <one/num> anonymous <entry/entries> on your list. Please try other options, or dial <d> for instructions;
add audio_seq id=GR220_28_PUB; language_id=def; seq=THERE,var_audio,var_number,var_audio,SLE_1_2,SLE_28_1,var_digits,SLE_28_2; description=There <is/are> <one/num> <entry/entries> on your list. To delete an entry, dial <dd> as soon as you hear it;
add audio_seq id=GR220_28_ANM; language_id=def; seq=THERE,var_audio,var_number,var_audio,SLE_1_2,INCLUDING,var_number,ANONYMOUS,var_audio,SLE_28_1,var_digits,SLE_28_2; description=There <is/are> <one/num> <entry/entries> on your list, including <one/num> anonymous <entry/entries>. To delete an entry, dial <dd> as soon as you hear it;
add audio_seq id=GR220_29; language_id=def; seq=SLE_29; description=This is the end of your list;
add audio_seq id=GR220_30; language_id=def; seq=SLE_30,var_audio,var_digits; description=The first entry on your list is <silence/extension> <ds>;
add audio_seq id=GR220_38; language_id=def; seq=SLE_38,SLE_11_2,var_digits,SLE_11_3; description=The number is already on your list as an anonymous entry. Please continue, dial <d> for instructions, or hang up;
add audio_seq id=GR220_39; language_id=def; seq=SLE_39,var_audio,var_digits,SLE_11_2,var_digits,SLE_11_3; description=This number is already on your list. <silence/extension> <ds>. Please continue, dial <d> for instructions, or hang up;
add audio_seq id=GR220_40; language_id=def; seq=SLE_40,var_digits,SLE_11_3; description=The number to be removed is not on your list. Please start again, dial <d> for instructions, or hang up;
add audio_seq id=GR220_41; language_id=def; seq=SLE_41; description=This is the end of your list. Your list is now empty;
Step 10 Add NSA_ACT time of day schedule audio-sequence:
add audio_seq id=TOD_START; language_id=def; seq=TIME_MGMT_01,var_day,var_time,YOUR,var_audio,TIME_MGMT_02,FROM,var_day,var_time,TO,var_day,var_time,TIME_MGMT_03,var_digits,TIME_MGMT_04,var_digits,TIME_MGMT_05; description=Now is <day><time>. Your <fname> service is scheduled to be on from <day> <time> to <day> <time>. If you are satisfied with this schedule, please press <d> now. To set a different time-of-day schedule, press <d>. Please dial now.
add audio_seq id=TOD_START_TIME; language_id=def; seq=TIME_MGMT_06; description=Please enter the start time in 24 hour format;
add audio_seq id=TOD_STOP_TIME; language_id=def; seq=TIME_MGMT_07; description=Please enter the end time in 24 hour format;
add audio_seq id=TOD_START_DAY; language_id=def; seq=TIME_MGMT_08; description=Please enter the start weekday, 0 stands for Sunday, 6 stands for Saturday;
add audio_seq id=TOD_STOP_DAY; language_id=def; seq=TIME_MGMT_09; description=Please enter the end weekday, 0 stands for Sunday, 6 stands for Saturday;
add audio_seq id=TOD_INVALID_TIME; language_id=def; seq=TIME_MGMT_10; description=That is not a valid time, the time value should be between 0 to 2359, the end time must be later than the start time;
add audio_seq id=TOD_INVALID_DAY; language_id=def; seq=TIME_MGMT_11; description=That is not a valid day, the day value should be between 0 to 6;
add feature-config; fname=SLE; type=T1-TIMER; datatype=integer; value=40; description=T1 defines how long the SPCS waits for the customer to confirm an existing remote DN or indicate that the remote DN should be changed. T1 shall be settable between 2 and 10 seconds with an interval of 1 second and a suggested value of 4 seconds;
add feature-config; fname=SLE; type=T2-TIMER; datatype=integer; value=40; description=T2 defines how long the SPCS waits for the customer to specify a new remote DN. T2 defines how long the SPCS waits for the customer to specify a new remote DN;
add feature-config; fname=SLE; type=T3-TIMER; datatype=integer; value=40; description=T3 defines how long the SPCS waits for the customer to specify "#", "12", or "0" when a DN must be added to the list during feature activation. T3 shall be settable between 2 and 10 seconds with an interval of 1 second and a suggested value of 4 seconds;
add feature-config; fname=SLE; type=T4-TIMER; datatype=integer; value=40; description=T4 defines how long the SPCS waits for the customer to specify a DN when adding or deleting an entry. T4 shall be settable between 2 and 10 seconds with an interval of 1 second and a suggested value of 4 seconds;
add feature-config; fname=SLE; type=T5-TIMER; datatype=integer; value=30; description=T5 specifies the time the originating SPCS waits for a response to the initial query sent to the Screened DN.s SPCS. T5 shall be settable between 2 and 4 seconds with an interval of 1 second and a suggested value of 3 seconds.
add feature-config; fname=SLE; type=T6-TIMER; datatype=integer; value=25; description=T6 defines how long the SPCS waits for the customer to specify an option after an entry on the list has been voiced back during list review. For DTMF customers, T6 shall be settable between 2 and 3 seconds with an interval of 0.5 second and a suggested value of 2.5 seconds. For dial pulse customers, it shall be settable between 3 and 4 seconds with an interval of 0.5 second and a suggested value of 3.5 seconds;
add feature-config; fname=SLE; type=IDT-TIMER; datatype=integer; value=40; description=Interdigit timer, the interdigit timing shall be settable between 2 and 9 seconds with an interval of 1 second and a suggested value of 4 seconds;
Caution You must enter the following command after turning on authentication. Otherwise, the customer will be prompted for the PIN, but will always be denied access to the management menu. (Authentication for NSA_ACT is turned on by default and is provisionable using the add/change feature-config command as described in the “Provisioning Feature Control Options for the IVR Interactions” section on page 5-108.)
Step 3 Add subscriber-feature-data for initial setup of the PIN:
In addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber.
MLHG Provisioning
MLHG provisioning is similar to pubscriber provisioning.
Provisioning Notes/Caveats
• One of the three FDN values assigned in sub-feature-data must be the subscriber's primary DN.
On-Net Routing and Local Number Portability for Inter–PacketCable Cable Management Server Routing
The following subsections provide example scenarios for provisioning the On-Net Routing and Local Number Portability (LNP) for Inter–PacketCable Cable Management Server (CMS) Routing feature.
Note See Local Number Portability for ANSI/North America, page 5-81 for detailed information on provisioning LNP.
Provisioning LNP Queries
For all Destinations resulting from dial plan translations for which an LNP query may be allowed, use the Destination NANP-LNP-QUERY default value NA. For all Carrier entries, use LNP-QUERY default value N.
Specify the NANP-LNP-QUERY value either implicitly using add destination without specifying NANP-LNP-QUERY parameter, or explicitly set it.
Specify Carrier LNP-QUERY = N implicitly by omitting the LNP-QUERY parameter, or explicitly.
For example:
change carrier id=0333; lnp-query=N;
Provisioning an LNP Query on a Carrier Call
For all destinations resulting from dial plan translations which could result in Carrier routing (e.g., Destination call-type INTERLATA, TOLL, or CARRIER), the destination NANP-LNP-QUERY should have value PERFORM-LNP-QUERY or NA. If value NA is used, then the appropriate Carrier entry should have either USE-DIAL-PLAN=Y or LNP-QUERY = Y.
add destination dest-id=dest_carrier; call-type=INTERLATA; route-type=ROUTE; route-guide-id=carrier_rg; description=nanp-lnp-query has default value NA!;
add carrier id=0333; inter=Y; intra=Y; intl=Y; use-dial-plan=N; route-guide-id=dpc1-rg; cut-thru=N; status=INS; lnp-query=Y; description=Allow an LNP query on calls to this carrier;
The Cisco BTS 10200 Softswitch will route this call to the carrier unless the called DN is a subscriber assigned on this switch and not in a porting transition state. For this scenario, the operator wants carrier bypass for local subscribers, but does not want to incur the overhead of LNP queries for DNs which are in the process of porting in or porting out (LNP-TRIGGER=Y). The operator might know that either A) there are no transition DNs in this switch (or perhaps all are ported-out), or B) there are very few, and the operator would prefer that the Carrier do the LNP query, and route calls back to our switch for a very few calls.
The destination has call-type INTERLATA for Carrier routing, SUB-ONLY to allow carrier bypass for local subs, and NO-LNP-QUERY to force calls needing a query to go to the carrier.
For example:
add destination dest-id=carrier_or_sub; call-type=INTERLATA; route-type=SUB; bypass-carrier-routing=SUB-ONLY; nanp-lnp-query=NO-LNP-QUERY; description=Carrier route unless SUB assigned (no query);
The Cisco BTS 10200 Softswitch routes this call to the carrier unless the called DN is a subscriber assigned on this switch. This includes DNs which are in the process of either porting in or porting out. For these transition DNs requiring an "unconditional" (ATIS document terminology), which are marked with Dn2subscriber LNP-TRIGGER=Y, will get an LNP query before the routing decision is made. For the transition DNs for which there is an LNP query, the LNP query results determine whether the call is routed to the Carrier or bypasses the carrier if the subscriber is in this switch.
The Destination has call-type INTERLATA for Carrier routing, SUB-ONLY to allow carrier bypass for local subs, and UNCONDITIONAL-LNP-TRIGGER-QUERY to allow a query for DNs during the transition period.
For example:
add destination dest-id=carr_or_sub_lnp; call-type=INTERLATA; route-type=SUB; bypass-carrier-routing=SUB-ONLY; nanp-lnp-query=UNCONDITIONAL-LNP-TRIGGER-QUERY; description=Carrier unless local SUB (query DNs during porting transition);
# Mark DN 703-765-4449 as a 'transition DN" in the process of porting in or porting out
The Destination NANP-LNP-QUERY PERFORM-LNP-QUERY value is used to ensure that an LNP query is done before on-net routing. Of course, this query is still conditional, depending on whether the Ported Office Code entry exists and other related criteria. The destination call-type is either INTERLATA or TOLL, and the BYPASS-CARRIER-ROUTING value is ALL-CALLS. Three routing scenarios are possible:
1. Route to carrier for off-net call.
2. Route using destination for on-net call to another on-net switch.
3. Route on-net to subscriber in the same switch. Ignore carrier and destination routes.
For example:
add destination dest-id=carrier_or_bypass; call-type=INTERLATA; route-type=ROUTE; route-guide-id=on_net_rg; nanp-lnp-query=PERFORM-LNP-QUERY; bypass-carrier-routing=ALL-CALLS; description=LNP query, and route to carrier, or on-net;
Provisioning Inter-CMS—Subscriber Origination (if no NRS), or Trunk Origination on MGC or Terminating CMS (ALL-CALLS + LNP Query)
The provisioning for this scenario is identical to Provisioning Carrier Bypass (On-Net Route)—Multi-BTSes.
Provisioning Inter-CMS with NRS—Same BTS Acting as CMS and MGC
For a subscriber origination, the subscriber dial plan will result in a Destination which does not allow an LNP query and may have an on-net route to the NRS. But for a trunk origination on the same Cisco BTS 10200 Softswitch, the incoming trunk dial plan, for the same DN, has a different destination, which will allow an LNP query, and will not bypass the Carrier for calls to the PSTN.
# Subscriber Destination and Dial Plan; 703-484 is on-net, 301-444 is off-net;
# 703-484 may have DNs ported-out (needs queries).
# 301-444 (off-net) has no ported-in DNs Cisco BTS 10200 Softswitch, and does not need dial-plan entry (always carrier routing)
add destination dest-id=cms_sub_nrs; call-type=INTERLATA; route-type=ROUTE; route-guide-id=nrs_rg; bypass-carrier-routing=ALL-CALLS; nanp-lnp-query=NO-LNP-QUERY; description=Route all sub originations to NRS with no LNP query;
Selectively Provisioning LNP Queries (Allow or Disallow) for a Particular Call Type
A Call Type Profile entry with LNP-QUERY = Y can be added to allow an LNP query for a particular call-type, for example, WEATHER. However, by changing destination LNP criteria, it is possible to allow a query for some weather calls, but not others.
Note For the steps of this procedure, OCB activation (OCBA), OCB deactivation (OCBD), and OCB interrogation (OCBI) are referred to interchangeably as OCBx.
Step 3 Register the COS feature in the office.
Note See the provisioning notes for COS screening. This step is optional and is required only under two circumstances: COS screening functionality is required as a subset of OCB. BW-list screening functionality of OCB needs to be offered to the subscriber even if OCB is
in a deactivated state.
Step 4 Add/change the vsc code for OCBA.
add vsc fname=OCBA; digit-string=*54*;
Step 5 Add/change the vsc code for OCBD.
add vsc fname=OCBD; digitstring=#54*;
Step 6 Add/change the vsc code for OCBI.
add vsc fname=OCBI; digit-string=#54#;
Step 7 Provision the OCB features as a service package.
add service id=ocb; FNAME1=OCB; FNAME2=OCBA; FNAME3=OCBD; FNAME4=OCBI
This feature is deactivated by default when it is assigned to a subscriber. OCB can be activated and deactivated alternately by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate OCB:
• The K-VALUE for the subscriber in the Subscriber-feature-data table will be recorded by the system when the subscriber uses the OCBA feature.
• The COUNT and TIME fields in the Subscriber-feature-data table are used by the operator to manually reset a locked-out subscriber. To unlock a locked-out subscriber, set both fields to '0'.
• The PASSWD provisioned in the Subscriber-feature-data table can be optional if FREE-SELECT-PIN=Y.
Outgoing Call Barring—Activation, Deactivation, and Interrogation The following subsections identify necessary steps for the OCBA, OCBD, and OCBI features to be offered.
Note In this section, OCB activation (OCBA), deactivation (OCBD), and interrogation (OCBI) are interchangeably referred to as OCBx.
For the feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber. In addition, the following step must be performed.
Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
MLHG provisioning is similar to subscriber provisioning as described above.
Provisioning Notes/Caveats
• The K-VALUE for the subscriber in the Subscriber-feature-data table will be recorded by the system when the subscriber uses the OCBA and OCBD feature.
• The COUNT and TIME fields in the Subscriber-feature-data table are system internal and should not be manipulated by the Operator.
Alternate Activation and Deactivation Method
This feature is deactivated by default when it is assigned to a subscriber. OCB can alternately be activated and deactivated by creating an entry in the Subscriber-feature-data table.
Use a CLI command similar to the following to activate OCB:
The default value for the OVERLAP_SENDING_SUPP token is N (no). For a description of the OVERLAP_SENDING_SUPP token, see the information on the DESTINATION table in the Cisco BTS 10200 Softswitch CLI Database.
Provisioning Overlap Dialing in the SOFTSW_TG_PROFILE Table
The token OVERLAP_SUPP is added to the SOFTSW-TG-PROFILE table.
To enable Overlap Dialing for a trunk group on the incoming side, issue the following command:
The default value for the OVERLAP_SUPP token is NONE. For a description of the OVERLAP_SUPP token, see the information on the SOFTSW_TG_PROFILE table in the Cisco BTS 10200 Softswitch CLI Database.
Provisioning Overlap Dialing in the CA_CONFIG_BASE Table
To support Overlap Dialing, you must set the following tokens in the CA_CONFIG_BASE table to the values shown:
• TYPE=OVERLAP-CRITICAL-DIGIT-TIMER
• DATATYPE=INTEGER
• FROM_VALUE=2
• TO_VALUE=20
• CHK_POS_VAL=N
• DEFAULT_VALUE=4
• TYPE=OVERLAP-INTER-DIGIT-TIMER
• DATATYPE=INTEGER
• FROM_VALUE=2
• TO_VALUE=24
• CHK_POS_VAL=N
• DEFAULT_VALUE=16
Provisioning Overlap Dialing in the DIAL_PLAN_PROFILE Table
To support Overlap Dialing, you must set the NANP_DIAL_PLAN token in the DIAL_PLAN_PROFILE table to N (NANP_DIAL_PLAN=N).
Provisioning Overlap Dialing in the DIAL_PLAN Table
To support Overlap Dialing, you must set the NOA token in the DIAL_PLAN table to UNKNOWN (NOA=UNKNOWN).
Provisioning Overlap Dialing for the Sending and Receiving Directions
Use the following provisioning steps to configure Overlap Dialing on the Cisco BTS 10200 for both the sending and receiving directions. If the dialed digits match the prefix string 512378, the Cisco BTS 10200 selects the destination ID of sip1, route ID of siprt1, and trunk group of 11, and sends
out the call in an overlapping mode (the OVERLAP_SENDING_SUPP token is set to Yes in the DESTINATION table). On the trunk group side, calls that come in and go out on a trunk group that is associated with a SOFTSW-TG-PROFILE of sspf1 support overlap-sending and overlap-receiving.
Step 1 Add a softswitch trunk group profile with the token OVERLAP_SUPP set to INCOMING. This step enables the Cisco BTS 10200 to receive overlapped digits through the associated trunk group.
add softsw-tg-profile id=sspf1; protocol-type=SIP; non-src-transport=UDP_ONLY; overlap-supp=BOTH; description=Softswitch TG between PODS;
Step 2 Add a trunk group that is associated with the softswitch trunk group profile. (That is, notice that the value specified for the TG_PROFILE_ID token matches the value specified for the ID token in the SOFTSW_TG_PROFILE table in Step 1.)
add trunk-grp id=11; dial-plan-id=dp11; softsw-tsap-addr=sia-SJ2CA102.trnglab.cisco.com:5060; call-agent-id=CA101; tg-type=softsw; tg-profile-id=sspf1; clli=austtxcsco1; pop-id=1; description=Softswitch Trunk Group to Pod2;
Step 3 Add a route that points to the trunk group.
add route id=siprt1; tgn1-id=11;
Step 4 Add a destination that is associated with the route provisioned in the preceding step. (That is, notice that the value specified for the ROUTE_ID token matches the value specified for the ID token in the ROUTE table in Step 3.) Set the OVERLAP_SENDING_SUPP token to YES to indicate that the Cisco BTS 10200 can send overlapped digits to this destination.
add dial-plan-profile id=dp11; nanp-dial-plan=n; description= non north america local dial plan profile
Note The specification of N for the NANP_DIAL_PLAN token is especially important for the correct operation of Overlap Dialing.
Step 6 Add a dial plan that is associated with destination. (That is, notice that the value specified for the ID token matches the value specified for the ID token in the DIAL_PLAN_PROFILE table in Step 5.)
Note The specification of UNKNOWN for the NOA token is especially important for the correct operation of Overlap Dialing.
Provisioning the Dial Plan
To enable the Overlap Dialing feature, you must provision the digit map in the DIGIT_MAP table and the dial plans to work correctly together. The digit map instructs the media gateway (MGW) how to collect and report dialed digits to the gateway adapter. You must provision dial plans to manage the input digits correctly.
For example, the following four subscribers in remote switches are assigned non-fixed telephone number lengths:
• Subscriber 1 has the number of 469-255 at remote switch A.
• Subscriber 2 has the number of 469-256-4 at remote switch B.
• Subscriber 3 has the number of 469-256-5 at remote switch B.
• Subscriber 4 has the number of 469-256-6789 at remote switch B.
You must complete the following provisioning steps to enable overlap dialing.
Step 1 Create a digit map to instruct the MGW to transmit the first 6 digits, which start with the prefix 469.
add digit-map id=default; digit-pattern=469xxx;
Step 2 Create the softswitch trunk group profiles (softsw-tg-profiles), the trunk groups (trunk-grps), the routes, and destinations for the two remote switches, A and B.
add softsw-tg-profile id=sspfA; protocol-type=SIP; non-src-transport=UDP_ONLY; overlap-supp=NONE; description=Softswitch TG to Switch A with NO Overlap;
add softsw-tg-profile id=sspfB; protocol-type=SIP; non-src-transport=UDP_ONLY; overlap-supp=BOTH; description=Softswitch TG to Switch B with Overlap;
add trunk-grp id=11; dial-plan-id=dp11; noa=unknown; dest-id=xxxx; softsw-tsap-addr=sia-switchA.trnglab.cisco.com:5060; call-agent-id=CA101; tg-type=softsw; tg-profile-id=sspfA; clli=austtxcsco1; pop-id=1; description=Softswitch Trunk Group to Switch A;
add trunk-grp id=12; dial-plan-id=dp11; noa=unknown; dest-id=xxxx; softsw-tsap-addr=sia-switchB.trnglab.cisco.com:5060; call-agent-id=CA101; tg-type=softsw; tg-profile-id=sspfB; clli=austtxcsco2; pop-id=1; description=Softswitch Trunk Group to Switch B;
After you complete the preceding provisioning steps, the Cisco BTS 10200 processes Overlap Dialing according to the following conditions:
• If the user dials 469255, the MGW sends all six digits 469255 to the MGA. The Cisco BTS 10200 routes the digits to DESTINATION_A with no overlap dialing.
• If the user dials 469256-4, the MGW sends 469256 in the first digitmap to the MGA. The Cisco BTS 10200 routes the initial set of digits to DESTINATION_B, and requests more digits from the MGA/MGW if more digits are available. When the MGW transmits the last digit (4), the Cisco BTS 10200 sends it to the same DESTINATION_B.
• If the user dials 469256-6789, the MGW sends the digits 469256 in the first digitmap to the MGA. The Cisco BTS 10200 routes the initial set of digits to DESTINATION_B, and requests more digits from the MGA if more digits are available. When MGW/MGA transmits the remaining digits (6789), the Cisco BTS 10200 sends them one by one to the same DESTINATION_B.
Additional Dial Plan Provisioning
Using the same four subscribers identified in the preceding section, you can create a different digit map and dial plan combination by completing the following steps:
Step 1 Add a digit map that allows the MGW to send either 5 or 6 digits in the initial transmission.
Step 2 Add more dial plans to handle initial 3-, 4-, and 5-digit strings. This ensures that the 3-, 4-, and 5-digit dialed strings are matched with a dial plan and not dropped.
After you create the additional dial plans, the Cisco BTS 10200 processes Overlap Dialing according to the following conditions.
• When the Media Gateway sends 469 only to the Media Gateway Adapter (MGA), the Cisco BTS 10200 finds a dial plan match. However, because the value set for min_digits required in the matched dial plan is not reached, the Cisco BTS 10200 does not do anything and waits for the next digit. Therefore, it does not matter what destination was assigned to the dest-id. When the next digit is available, the Cisco BTS 10200 uses the accumulated digits to try again to match the longest dial plan.
• The Cisco BTS 10200 applies the same procedure to find a matched dial plan when it receives 4692 and 46925.
• When the Cisco BTS 10200 receives 469255, it waits for all the digits and routes the call in ENBLOC mode to DESTINATION_A.
Note In ENBLOC mode, the Cisco BTS 10200 transmits all dialed digits together. Overlap Dialing is not supported in this case. That is, the Cisco BTS 10200 does not send the initial set of digits and then the rest of the digits one by one later.
• When the Cisco BTS 10200 receives 469256, it routes the call in overlapping mode to DESTINATION_B. The Cisco BTS 10200 sends the rest of the digits, one by one, to the same DESTINATION_B.
Provisioning an NCS/MGCP Endpoint
To provision an NCS/MGCP endpoint to support Overlap Dialing, issue the following command to provide a value for the TYPE and VALUE tokens in the CA_CONFIG table:
When enabling Overlap Dialing, you must be careful not to misprovision the feature. For example, if you set the token OVERLAP_SENDING_SUPP in the DESTINATION table to Y (yes) and the token OVERLAP_SUPP in the SOFTSW-TG-PROFILE table to NONE or INCOMING, the feature is not provisioned correctly. When the Cisco BTS 10200 attempts to invoke Overlap Dialing for a call, the feature might not transmit all of the dialed digits.
To avoid misprovisioning Overlap Dialing, enable both the DESTINATION and SOFTSW-TG-PROFILE tables to support sending overlapped digits by setting the token OVERLAP_SENDING_SUPP in the DESTINATION table to Y and the token OVERLAP_SUPP in the SOFTSW-TG-PROFILE table to OUTGOING or BOTH.
Alternatively, you can disallow the sending of overlapped digits by setting the token OVERLAP_SENDING_SUPP in the DESTINATION table to N and the token OVERLAP_SUPP in the SOFTSW-TG-PROFILE table to NONE or INCOMING.
For a description of the DESTINATION table and SOFTSW-TG-PROFILE table, see the Cisco BTS 10200 Softswitch CLI Database.
Own Calling Number AnnouncementThis section explains the steps required to provision the Own Calling Number Announcement (OCNA) feature.
Office Provisioning
Step 1 Provision the Announcement table for the OCNA feature:
Step 4 Do the SIP trunk provisioning, and assign this feature to the subscriber:
add softsw-tg-profile id=10;protocol-type=SIP;
add trunk-grp id=21;softsw-tsap-addr=<ip address of the PS AS IPUnity box>:5060; call-agent-id=CA146;tg-type=softsw; tg-profile-id=10; dial-plan-id=dp1;
add trunk-grp id=22;softsw-tsap-addr=<domain name of the PS AS IPUnity Box>:5060; call-agent-id=CA146;tg-type=softsw; tg-profile-id=10;dial-plan-id=dp1;
Step 7 Specify in the feature-config table whether the calls with privacy as UNKNOWN should be treated as anonymous or not. The default is not anonymous.
Follow the steps in the IVR Provisioning section for Screen List Editing: SCF, SCR, SCA, and DRCW, page 5-131.
Step 2 Add the RACF Virtual Subscriber. All RACF subscribers will call 972-789-1000 for remote access to call forwarding. Subscribers will interact with the IVR subscriber when using the RACF PIN change feature:
Step 4 Add the RACF service for subscribers with a non-unique PIN:
add service id=1; fname1=RACF;
Step 5 Assign the RACF_PIN to the IVR virtual subscriber:
add service id=2; fname1=RACF_PIN;
Step 6 Add the RACF and Pin Change service for subscribers with a unique PIN:
add service id=3; fname1=RACF; fname2=RACF_PIN;
Step 7 Add the service for the subscribers of IVR and RACF categories:
add service id=IVR_SVC; fname1=IVR;
Step 8 Add a VSC for subscribers changing their PIN:
add vsc digit_string=*98; fname=RACF_PIN;
Provisioning Notes/Caveats
• The RACF_PIN feature should only be assigned to those RACF subscribers who have unique PINs.
• A unique PIN is identified in the subscriber feature data entry for RACF as PINTYPE=PIN or PINTYPE=NEWPIN. (The NEWPIN type indicates that the subscriber has not yet changed his PIN from the default one assigned by the service provider. To be able to use the RACF feature, the subscriber must first change his PIN at least once from his home number. Once he does this, the PINTYPE in feature data will be changed to PIN).
• If a subscriber has a non-unique PIN, he is not allowed to change it. It can only be changed through the CLI. For non-unique PIN validation, an authcode should be provisioned, and the PINTYPE should be set to AUTHCODE.
• Non-unique PINs are typically assigned to a group of subscribers sharing the same PIN, that is, in a Centrex environment.
Subscriber Provisioning
Step 1 Assign the RACF feature to the RACF virtual subscriber:
Step 3 The RACF_PIN feature must be assigned to the IVR virtual subscriber. Only this feature and SCA_ACT, SCR_ACT DRCW_ACT, and SCF_ACT features are assigned to this subscriber:
Step 5 This is for regular subscribers with RACF having non-unique PIN so the authcode is used. RACF_PIN change feature is not assigned to this subscriber (sub1):
Step 6 This subscriber (sub2) has a unique PIN. The pintype of "NEWPIN" indicates that he is required to change it from his home/base phone before he can use the RACF feature:
Remote Call Forwarding By default, the multiple call forwarding (MCF) flag is set to Y for both CFU and RCF. For illustration purposes, this flag is included in the CFU and RCF examples below. The flag must be set to Y for both CFU and RCF to allow multiple calls to be forwarded simultaneously by the RCF feature.
Note The subscriber phone number (dn1 in the above command) must be assigned to the subscriber, but it does not need to be associated with a physical telephone.
The Replace feature is only applicable for SIP subscribers.
Screen List Editing: SCF, SCR, SCA, and DRCW The DRCW feature is only for playing a distinctive ringing or distinctive call-waiting tone and does not affect the activation of the call-waiting features (CW, CWD, or CIDCW). A subscriber must have CW, CWD, or CIDCW provisioned and activated in order to receive call-waiting treatment.
Office Provisioning
Step 1 The IVR DN value here must be the same number as the IVR virtual subscriber:
Note The qos-id token must be provisioned to match the qos-id for the trunk in the Quality of Service table. If two MGWs are involved in a call, there are additional QoS requirements applicable for the trunk groups on each MGW. See hptime and lptime token descriptions
Subscribers who are assigned DRCW will need CW, CIDCW, or CWD for the Call-Waiting portion of DRCW to work.
Alternate Activation and Deactivation Method
The following procedure provides an alternative method for activating, deactivating, and provisioning the SCF, SCR, SCA, and DRCW features. The example below activates DRCW:
Step 1 Add a service for the feature, for example, DRCW:
Note You must provision the route-guide-id in the Route Guide table before you configure the sip-trigger-profile.
Note Step 1 applies only if you are provisioning SIP endpoints (SIP subscribers). If you are provisioning SIP endpoints, ignore any OHD-related provisioning in Step 2.
Step 1 Configure the TAT for SIP endpoints (SIP subscribers):
Step 3 To create an IVR prompt/announcement, enter the following commands:
Note The BTS provides a generic prompt that says: “We are sorry. Your premier voice service is unavailable. You may dial a number at anytime or hangup.” This recording is stored as an audio file with the filename 'sip_trigger_barge_in.wav' which is used in the last step of this example.
add audio_segment id=sip_trig_barge_in; TYPE=PHYSICAL; URL=file://sip_trigger_barge_in.wav; description=We are sorry. Your premier voice service is unavailable. You may dial a number at any time or hangup;
Centrex Provisioning
The SIP triggers feature is not supported for Centrex subscribers.
MLHG Provisioning
MLHG provisioning is similar to subscriber provisioning.
Single Number ReachThis section explains how to provision the Single Number Reach (SNR) feature.
Prerequisites
Single Number Reach requires an IVR and voice mail server.
• Feature Control Options for Provisioning IVR Interactions
• Subscriber Provisioning
• SNR_ACT IVR Virtual Subscriber Provisioning
Note For complete CLI information, see the Cisco BTS 10200 Softswitch CLI Database.
Office Provisioning
This section lists the provisioning steps required to complete office provisioning for the Single Number Reach feature. The CFU and VMA features should be provisioned before the subscriber completes the Single Number Reach office provisioning procedure. For details on provisioning the CFU and VMA features, see the Cisco BTS 10200 Softswitch Provisioning Guide.
Step 1 Create the Single Number Reach activation (SNR_ACT) feature.
Step 3 Add the Single Number Reach feature service.
add service id=snr; fname1=SNR;
Resource Provisioning
This section lists the provisioning steps required to complete the resource provisioning for the Single Number Reach feature.
Note Only MGW_PROFILE table fields used by Single Number Reach are discussed below. For complete MGW_PROFILE table details, refer to the Cisco BTS 10200 Softswitch CLI Database.
add audio_segment id=SNR_SORRY_NUM_INVALID; type=PHYSICAL; url=file://SorryNumberInvalid.wav; description=We are sorry. The number you have entered is incorrect.
add audio_segment id=SNR_SORRY_CMD_INVALID; type=PHYSICAL; url=file://SorryCommandInvalid.wav; description=We are sorry. The digits entered are not a valid command.
add audio_segment id=SNR_FORWARDING_TO_NUM; type=PHYSICAL; url=file://your_calls_currently_fwd_to.wav; description=Your calls are currently being forwarded to
add audio_segment id=SNR_PLEASE_ENTER_FWD_NUM; type=PHYSICAL; url=file://PleaseEnterFwdDn.wav; description=Please enter the number to which you want your calls forwarded, followed by the number sign key.
Step 3 Add the Single Number Reach audio segments.
add audio_segment id=SNR_TRYING_TO_REACH_PARTY; type=PHYSICAL; url=file://trying_to_reach_party.wav; description=We are trying to reach your party. Please stay on the line.
add audio-segment id=SNR_RING_BACK_TONE; type=PHYSICAL; url=file://ring_back_tone.wav; description=2 seconds of ringback tone.
Step 4 Add the SNR_ACT authentication audio segments.
add audio_segment id=SNR_WELCOME; type=PHYSICAL; url=file://snr_welcome.wav; description=Welcome to the Single Number Reach System.
add audio_segment id=SNR_ENTER_NUM; type=PHYSICAL; url=file://snr_enter_number.wav; description=Please enter your SNR number, followed by the number sign key.
add audio_segment id=SNR_ADMIN_NUM; type=PHYSICAL; url=file://snr_admin_number.wav; description=You are about to administer SNR for
add audio_segment id=SNR_ADMIN_DIFF_NUM; type=PHYSICAL; url=file://snr_admin_diff_number.wav; description=To administer a different SNR number, press
add audio_segment id=SNR_INVALID_USER_ID_ABORT; type=PHYSICAL; url=file://hang_up_now.wav; description=Please hang up now, consult your written instructions, and try again later.
add audio_segment id=SNR_ENTER_PIN; type=PHYSICAL; url=file://please_enter_your_pin.wav; description=Please enter your pin, followed by the number sign key.
add audio_segment id=SNR_REENTER_PIN; type=PHYSICAL; url=file://please_reenter_your_pin.wav; description=Please re-enter your pin, followed by the number sign key.
add audio_segment id=SNR_INCORRECT_PIN; type=PHYSICAL; url=file://snr_incorrect_pin.wav; description=We are sorry. The pin entered does not match the current PIN for SNR number
add audio_segment id=SNR_PIN_ATTEMPTS; type=PHYSICAL; url=file://snr_pin_attempts.wav; description=If this is not the desired SNR number, please hang up and retry. The number of consecutive invalid pin attempts for this account is currently
add audio_segment id=SNR_FOR_YOUR_PROTECTION; type=PHYSICAL; url=file://for_your_protection.wav; description=For you protection, if this count reaches
add audio_segment id=SNR_ACCESS_WILL_BE_DISABLED; type=PHYSICAL; url=file://phone_access_will_be_disabled.wav; description=account access via phone will be disabled.
add audio_segment id=SNR_PHONE_ACCESS_IS_DISABLED; type=PHYSICAL; url=file://phone_access_is_disabled.wav; description=Phone access for this account is disabled. To re-enable phone access, please reset your pin via the internet.
Step 5 Add the SNR_ACT Main Menu audio segments.
add audio_segment id=SNR_FORWARDING_PER_SCHED; type=PHYSICAL; url=file://your_calls_fwd_per_sched.wav; description=Your calls are currently being forwarded based upon your forwarding schedule.
add audio_segment id=SNR_FORWARDING_TO_VOICEMAIL; type=PHYSICAL; url=file://your_calls_fwd_to_voicemail.wav; description=Your calls are currently being forwarded straight to your voicemail.
add audio_segment id=SNR_NO_FORWARDING_ACTIVE; type=PHYSICAL; url=file://snr_no_forwarding_active.wav; description=You currently do not have any of your SNR Call Forwarding Features active.
add audio_segment id=SNR_TO_ACTIVATE_CONFIG_CFU; type=PHYSICAL; url=file://to_activate_config_fwd_num.wav; description=To activate or configure forwarding to a single number, press
add audio_segment id=SNR_TO_CONFIG_CFU; type=PHYSICAL; url=file://to_config_fwd_num.wav; description=To configure forwarding to a single number, press
add audio_segment id=SNR_TO_ACTIVATE_FWD_SCHED; type=PHYSICAL; url=file://to_activate_fwd_sched.wav; description=To activate Forwarding per your schedule, press
add audio_segment id=SNR_TO_EXIT_TO_VMS; type=PHYSICAL; url=file://to_exit_snr_to_voicemail.wav; description=To exit this SNR system and connect to your voicemail, press
add audio_segment id=SNR_TO_EXIT; type=PHYSICAL; url=file://to_exit_snr.wav; description=To exit this SNR system, hang up or press
add audio_segment id=SNR_EXIT_SYSTEM; type=PHYSICAL; url=file://exit_snr_system.wav; description=You are now exiting the SNR configuration system. Goodbye.
Step 6 Add the SNR_ACT Forwarding per Schedule audio segments.
add audio_segment id=SNR_FWD_PER_SCHED_NOT_CONFIG; type=PHYSICAL; url=file://fwd_per_sched_not_config.wav; description=Forwarding per schedule is not configured properly. Please contact customer service.
add audio_segment id=SNR_NO_SCHED_ACTIVE; type=PHYSICAL; url=file://fwd_sched_needs_config.wav; description=Your forwarding schedule needs to be configured via the internet before it can be activated.
Step 7 Add the SNR_ACT Forwarding to Single Number audio segments.
add audio_segment id=SNR_CFU_NOT_CONFIG; type=PHYSICAL; url=file://fwd_to_single_num_not_config.wav; description=Forwarding to a single number is not configured properly. Please contact customer service.
add audio_segment id=SNR_CFU_NUM_INVALID; type=PHYSICAL; url=file://fwd_to_num_invalid.wav; description=Your forward-to-number is not set to a valid number.
add audio_segment id=SNR_CFU_FWD_TO_NUM_IS; type=PHYSICAL; url=file://fwd_to_num_is.wav; description=Your forward-to number is
add audio_segment id=SNR_TO_FWD_TO_THIS_NUM; type=PHYSICAL; url=file://to_fwd_to_this_num.wav; description=To forward all calls to this number, press
add audio_segment id=SNR_FWD_TO_NUM_IS_GOING_TO_BE; type=PHYSICAL; url=file://fwd_num_is_going_to_be.wav; description=Your forward-to number is going to be changed to
add audio_segment id=SNR_TO_CHANGE_FWD_DIFF_NUM; type=PHYSICAL; url=file://to_change_fwd_to_diff_num.wav; description=To change your forward-to number to a different number, press
add audio_segment id=SNR_TO_RETURN_TO_PREV_MENU; type=PHYSICAL; url=file://to_return_to_previous_menu.wav; description=To return to the previous menu, press
add audio_segment id=SNR_TO_RETURN_WITHOUT_UPDATE_FWD; type=PHYSICAL; url=file://to_return_without_update_fwd.wav; description=To return to the previous menu without updating your forward-to number, press
Step 8 Add the SNR_ACT Forwarding to Voicemail audio segments.
add audio_segment id=SNR_VMA_NOT_CONFIGURED; type=PHYSICAL; url=file://fwd_to_voicemail_not_config.wav; description=Forwarding to a voicemail is not configured properly. Please contact customer service.
add audio_segment id=SNR_EXIT_TO_VOICEMAIL; type=PHYSICAL; url=file://exit_snr_to_voicemail.wav; description=You are now exiting the SNR configuration system and connecting to voicemail.
Step 9 Add the SNR_ACT common audio sequences.
add audio_seq id=SNR_NUM_INVALID; language_id=def; seq=SNR_SORRY_NUM_INVALID; description=We are sorry. The number you have entered is incorrect.
add audio_seq id=SNR_CMD_INVALID; language_id=def; seq=SNR_SORRY_CMD_INVALID; description=We are sorry. The digits entered are not a valid command.
Step 10 Add the Single Number Reach announcement audio sequence.
add audio_seq id=SNR_ANNC_SEQ; language_id=def; seq=SNR_TRYING_TO_REACH_PARTY; description=We are trying to reach your party. Please stay on the line.
Step 11 Add the SNR_ACT authentication audio sequences.
add audio_seq id=SNR_AUTH_WELCOME; language_id=def; seq=SNR_WELCOME; description=Welcome to the Single Number Reach System.
add audio_seq id=SNR_AUTH_USER_ID; language_id=def; seq=SNR_ENTER_NUM; description=Please enter your SNR number, followed by the number sign key.
add audio_seq id=SNR_CONFIRM_NUM; language_id=def; seq=SNR_ADMIN_NUM,var_digits,SNR_TO_CONFIRM_PRESS,var_digits,SNR_ADMIN_DIFF_NUM,var_digits; description=You are about to administer SNR for <ds>. To confirm, press <AUTH-USERID-CONFIRM-OP>. To administer a different SNR number, press <AUTH-USERID-CHANGE-OP>.
add audio_seq id=SNR_INVALID_USER; language_id=def; seq=SNR_SORRY_NUM_INVALID; description=We are sorry. The number you have entered is incorrect.
add audio_seq id=SNR_INVALID_ABRT; language_id=def; seq=SNR_INVALID_USER_ID_ABORT; description=Please hang up now, consult your written instructions, and try again later.
add audio_seq id=SNR_ENTER_PIN; language_id=def; seq=var_audio; description=<SNR_ENTER_PIN/SNR_REENTER_PIN> Please (re)enter your pin, followed by the number sign key.
add audio_seq id=SNR_INVALID_PIN; language_id=def; seq=SNR_INCORRECT_PIN,var_digits; description=We are sorry. The pin entered does not match the current PIN for SNR number <ds>.
add audio_seq id=SNR_PIN_ATTEMPTS; language_id=def; seq=SNR_PIN_ATTEMPTS,var_number,SNR_FOR_YOUR_PROTECTION,var_number,SNR_ACCESS_WILL_BE_DISABLED; description=If this is not the desired SNR number, please hang-up and retry. The number of consecutive invalid pin attempts for this account is currently <d>. For you protection, if this count reaches <d>, account access via phone will be disabled.
add audio_seq id=SNR_AUTH_LOCKOUT; language_id=def; seq=SNR_PHONE_ACCESS_IS_DISABLED; description=Phone access for this account is disabled. To re-enable phone access, please reset your pin via the internet.
Step 12 Add the SNR_ACT Main Menu audio sequences.
IVATE-CFU-OP>,<SNR_TO_ACTIVATE_FWD_SCHED/NULL>, <MAIN-ACTIVATE-FWD-SCHED-OP/NULL>,<SNR_TO_ACTIVATE_VMA/NULL>,<MAIN-ACTIVATE-FWD-VMA-OP/NULL>,<SNR_TO_DEACTIVATE_ALL_SNR/NULL>,<MAIN-DEACTIVATE-ALL-FWD-OP/NULL>,<SNR_TO_EXIT_TO_VMS>,<MAIN-EXIT-TO-VMS-OP/NULL>,<SNR_TO_EXIT>,<MAIN-EXIT-OP/NULL>. To repeat instructions, press <REPEAT-INSTRUCTION>.
add audio_seq id=SNR_EXITING_SYST; language_id=def; seq=SNR_EXIT_SYSTEM; description=You are now exiting the SNR configuration system. Goodbye.
Step 13 Add the SNR_ACT Forwarding per Schedule audio sequences.
add audio_seq id=SNR_SNR_NOT_CFG; language_id=def; seq=SNR_FWD_PER_SCHED_NOT_CONFIG; description=Forwarding per schedule is not configured properly. Please contact customer service.
add audio_seq id=SNR_NO_SCHED_ACT; language_id=def; seq=SNR_NO_SCHED_ACTIVE; description=Your forwarding schedule needs to be configured via the internet before it can be activated.
Step 14 Add the SNR_ACT Forwarding to Single Number audio sequences.
add audio_seq id=SNR_CFU_NOT_CFG; language_id=def; seq=SNR_CFU_NOT_CONFIG; description=Forwarding to a single number is not configured properly. Please contact customer service.
add audio_seq id=SNR_CFU_MENU; language_id=def; seq=var_audio,var_digits,var_audio,var_digits,SNR_TO_CHANGE_FWD_TO_NUM,var_digits,SNR_TO_RETURN_TO_PREV_MENU,var_digits,SNR_TO_REPEAT_INSTRUCTIONS,var_digits; description=<SNR_CFU_NUM_INVALID/SNR_CFU_FWD_TO_NUM_IS/SNR_FORWARDING_TO_NUM>,<NULL/ds/ds>,<NULL/SNR_TO_FWD_TO_THIS_NUM/NULL>,<NULL/CFU-ENABLE-CFU-OP/NULL>,To change your forward-to number, press <CFU-CHANGE-FWD-TO_NUM-OP>. To return to the previous menu, press <CFU-RTN-TO-PREV-MENU-OP>. To hear these instructions repeated, press <REPEAT-INSTRUCTION>.
add audio_seq id=SNR_ENTR_FWD_NUM; language_id=def; seq=SNR_PLEASE_ENTER_FWD_NUM; description=Please enter the number to which you want your calls forwarded, followed by the number sign key.
add audio_seq id=SNR_CFU_NUM_CNFM; language_id=def; seq=SNR_FWD_TO_NUM_IS_GOING_TO_BE,var_digits,SNR_TO_CONFIRM_PRESS,var_digits,SNR_TO_CHANGE_FWD_DIFF_NUM,var_digits,SNR_TO_RETURN_WITHOUT_UPDATE_FWD,var_digits,SNR_TO_REPEAT_INSTRUCTIONS,var_digits; description=Your forward-to number is going to be changed to <ds>. To confirm, press <CFU-CONFIRM-CFU-NUM-OP>. To change your forward-to number to a different number, press <CFU-CHANGE-FWD-TO-DIFF-NUM-OP>. To return to the previous menu without updating your forward-to number, press <CFU-RTN-WITHOUT-UPDATE-OP>. To hear these instructions repeated, press <REPEAT-INSTRUCTION>.
Step 15 Add the SNR_ACT Voicemail audio sequences.
add audio_seq id=SNR_VMA_NOT_CFG; language_id=def; seq=SNR_VMA_NOT_CONFIGURED; description=Forwarding to a voicemail is not configured properly. Please contact customer service.
add audio_seq id=SNR_EXITNG_TO_VM; language_id=def; seq=SNR_EXIT_TO_VOICEMAIL; description=You are now exiting the SNR configuration system and connecting to voicemail.
Feature Control Options for Provisioning IVR Interactions
This section lists the steps required to complete the provisioning for feature control options for the IVR interactions.
add feature_config fname=SNR_ACT; type=FDT-TIMER; datatype=integer; value=150; description=Time to wait for first digit to be dialed, in 0.1 sec increments
add feature_config fname=SNR_ACT; type=IDT-TIMER; datatype=integer; value=70; description=Time to wait between digits, in 0.1 sec increments.
Step 2 Add the feature configurations for SNR_ACT authentication.
add feature_config fname=SNR_ACT; type=AUTH-CHECK-FOR-MST-NUM; datatype=boolean; value=Y; description=Whether to check if call originated from SNR Master Number.
add feature_config fname=SNR_ACT; type=AUTH-PIN-ATTEMPTS-TO-LOCK; datatype=integer; value=5; description=Number of consecutive invalid pin attempts to lock out IVR user.
add feature_config fname=SNR_ACT; type=AUTH-PIN-ATTEMPTS-TO-WARN; datatype=integer; value=2; description=Number of pin attempts to start warning they will be locked out.
add feature_config fname=SNR_ACT; type=AUTH-USERID-ATTEMPTS-TO-EXIT; datatype=integer; value=3; description=Num of consecutive UserID attempts to cause user exit from IVR.
add feature_config fname=SNR_ACT; type=AUTH-USERID-CONFIRM-OP; value=1; description=Digit to dial to confirm proper SNR number is to be configured.
add feature_config fname=SNR_ACT; type=AUTH-USERID-CHANGE-OP; value=2; description=Digit to dial to change the SNR number that is to be configured.
Step 3 Add the feature configurations for the SNR_ACT Main Menu.
add feature_config fname=SNR_ACT; type=MAIN-ACTIVATE-CFU-OP; value=1; description=Digit to dial from main menu to activate CFU.
add feature_config fname=SNR_ACT; type=MAIN-ACTIVATE-FWD-SCHED-OP; value=2; description=Digit to dial from main menu to activate fowarding per schedule.
add feature_config fname=SNR_ACT; type=MAIN-ACTIVATE-FWD-VMA-OP; value=3; description=Digit to dial on main menu to activate forwarding to voicemail.
add feature_config fname=SNR_ACT; type=MAIN-DEACTIVATE-ALL-FWD-OP; value=4; description=Digit to dial from main menu to deactivate all SNR forwarding.
add feature_config fname=SNR_ACT; type=MAIN-EXIT-TO-VMS-OP; value=5; description=Digit to dial from main menu to exit to VoiceMail System.
add feature_config fname=SNR_ACT; type=MAIN-EXIT-OP; value=9; description=Digit to dial to exit IVR.
Step 4 Add the feature configurations for the SNR_ACT Forwarding to Single Number menu.
add feature_config fname=SNR_ACT; type=CFU-ENABLE-CFU-OP; value=1; description=Digit to dial from CFU menu to activate CFU.
add feature_config fname=SNR_ACT; type=CFU-CHANGE-FWD-TO-NUM-OP; value=2; description=Digit to dial from CFU menu to change CFU forward-to number.
add feature_config fname=SNR_ACT; type=CFU-RTN-TO-PREV-MENU-OP; value=9; description=Digit to dial from CFU menu to return to previous menu.
add feature_config fname=SNR_ACT; type=CFU-CONFIRM-CFU-NUM; datatype=boolean; value=N; description=Whether user given extra prompt to confirm new CFU fwd number.
add feature_config fname=SNR_ACT; type=CFU-CONFIRM-CFU-NUM-OP; value=1; description=Digit to dial from CFU Confirm menu to confirm new CFU number.
add feature_config fname=SNR_ACT; type=CFU-CHANGE-FWD-TO-DIFF-NUM-OP; value=2; description=Digit to dial from CFU Confirm menu to change CFU fwd-to number.
add feature_config fname=SNR_ACT; type=CFU-RTN-WITHOUT-UPDATE-OP; value=9; description=Digit to dial from CFU Confirm menu to return without updating.
Subscriber Provisioning
This section lists steps required for provisioning subscribers, assigning the Single Number Reach service to the subscriber, and performing the initial setup of the subscriber PIN.
Step 1 If a subscriber entry for the subscriber does not exist, add a subscriber entry for subscriber. For a virtual subscriber, set term_type=none.
Step 4 Add the initial subscriber Single Number Reacted schedule. The reacted schedule can be provisioned to make the subscriber handle the call during the Single Number Reach process, for example handling or allowing the calls to ring simultaneously or sequentially, TOD of scheduling the call. The subscriber sets up and configures the Single Number Reacted schedule setup through the XML file.
add snr sub_id=222-789-3510; file=/snr.xml;
SNR_ACT IVR Virtual Subscriber Provisioning
This section lists the steps required for provisioning SNR_ACT virtual subscribers.
Step 1 Add the SNR_ACT virtual subscriber. All Single Number Reach subscribers will call 2227891000 for IVR access to their SNR_ACT features:
This section describes the operational interfaces for the Single Number Reach feature. The following interfaces are described:
• Operator CLI Interface
• Subscriber Web-Based Interface
• Subscriber IVR-Based Interface
Operator CLI Interface
To support Single Number Reach, the Single Number Reach and SNR_ACT tokens have been added to the CLI interface. A Single Number Reach table has been added to the CLI interface. For complete CLI information, refer to the Cisco BTS 10200 Softswitch CLI Database.
Single Number Reach Feature-Config and Feature-Config-Base Table
The type-value pairs listed in Table 5-4 are added to the feature-config-base.
SNR_ACT Feature-Config and Feature-Config-Base Table
The type-value pairs listed in Table 5-5 are added to the feature-config-base.
Table 5-4 Single Number Reach Feature-Config and Feature-Config-Base Table
Name Data Type Value Default Description
ALLOW-MULTIPLE-INVOCATION
BOOLEAN Y/N N If ALLOW-MULTIPLE-INVOCATION is set to Y, then multiple invocations is allowed for subscribers which have their Allow-Multiple-Invocation set to 1 in the subscriber’s snr_profile (this flag from the snr_profile defaults to 1, if not specified in the snr_profile). If multiple invocations are not allowed, subsequent calls to a subscriber who already has the Single Number Reach feature invoked, is sent to voice mail.
Table 5-5 SNR_ACT Feature-Config and Feature-Config-Base Table
Name Data Type Value Default Description
RESTART-KEY STRING 0–9,*,# * Key to dial to restart entering the number.
RETURN-KEY STRING 0–9,*,# # Key to dial to complete the entry of the number.
REPEAT-INSTRUCTION DIGITS 0–9 0 Digit to dial to hear instructions repeated.
T-SESSION INTEGER 300–36000 6000 Session timer, in 0.1-second increments.
FDT-TIMER INTEGER 20–600 50 Time to wait for first digit to be dialed, in 0.1 second increments.
IDT-TIMER INTEGER 20-600 50 Time to wait between digits, in 0.1 second increments.
AUTH-CHECK-FOR-MST-NUM
BOOLEAN Y/N Y Checks if the call to IVR system is coming from an Single Number Reach master number (and if it is, verify this is the number the subscriber wants to configure.)
AUTH-PIN-ATTEMPTS-TO-LOCK
INTEGER 1–100 5 Number of consecutive invalid PIN attempts before the Single Number Reach number is locked out from IVR usage.
INTEGER 1–100 2 Number of invalid PIN attempts before warning subscriber that they will be locked from IVR usage.
AUTH-USERID-ATTEMPTS-TO-EXIT
INTEGER 1–100 3 Number of attempts subscriber has to enter a valid Single Number Reach user ID before being booted from the IVR system.
AUTH-USERID-CONFIRM-OP
STRING 0–9 1 Digit to dial to confirm proper Single Number Reach number is to be configured.
AUTH-USERID-CHANGE-OP
STRING 0–9 2 Digit to dial to change the Single Number Reach number that is to be configured.
MAIN-ACTIVATE-CFU-OP STRING 0–9 1 Digit to dial from main menu to activate CFU.
MAIN-ACTIVATE-FWD-SCHED-OP
STRING 0–9 2 Digit to dial from main menu to activate forwarding per schedule.
MAIN-ACTIVATE-FWD-VMA-OP
STRING 0–9 3 Digit to dial on main menu to activate forwarding to voicemail.
MAIN-DEACTIVATE-ALL-FWD-OP
STRING 0–9 4 Digit to dial from main menu to deactivate all Single Number Reach forwarding.
MAIN-EXIT-OP STRING 0–9 9 Digit to dial to exit IVR.
CFU-ENABLE-CFU-OP STRING 0–9 1 Digit to dial from CFU menu to activate CFU.
CFU-CHANGE-FWD-TO-NUM-OP
STRING 0–9 2 Digit to dial from CFU menu to change CFU forward-to number.
CFU-RTN-TO-PREV-MENU-OP
STRING 0–9 9 Digit to dial from CFU menu to return to previous menu.
CFU-CONFIRM-CFU-NUM BOOLEAN Y/N N To give an extra confirmation prompt to the Single Number Reach IVR subscriber when the subscriber is changing the CFU forward-to number.
CFU-CONFIRM-CFU-NUM-OP
STRING 0–9 1 Digit to dial from CFU Confirm menu to confirm new CFU number.
Table 5-5 SNR_ACT Feature-Config and Feature-Config-Base Table (continued)
The subscriber-feature-data table stores feature status, failed PIN attempts, PIN status (NEWPIN, LOCKEDPIN, PIN) and access PIN. The subscriber can unlock the PIN if the PIN is locked after repeated failed PIN attempts. The subscriber-feature-data table displays the number of PIN attempts as well. The PIN status for the feature SNR_ACT is saved in the subscriber-feature-data table as a type-value pair. Besides the current values (NEWPIN, PIN) for PIN-TYPE, a new type LOCKEDPIN is needed. A new type-value pair PINATTS (number of consecutive failed pin attempts) is added for SNR_ACT feature.
Table 5-6 lists type-value pairs added or updated in the subscriber-feature-data table.
SNR Table
The SNR table (Table 5-7) defines the functionality associated with the BTS 10200 Call Agent.
Table Name: SNR
Table Containment Area: Feature Server
Table Contents:
1. SUB-ID
2. Single Number Reach feature profile
3. Token Properties
CFU-CHANGE-FWD-TO-DIFF-NUM-OP
STRING 0–9 2 Digit to dial from CFU Confirm menu to change CFU forward-to number.
CFU-RTN-WITHOUT-UPDATE-OP
STRING 0–9 9 Digit to dial from CFU Confirm menu to return without updating.
Table 5-5 SNR_ACT Feature-Config and Feature-Config-Base Table (continued)
Add Rules: Either the snr_profile or the file field is specified.
Change Rules: Either the snr_profile or the file field is specified.
Delete Rules:
When only the ID is specified, all other entries with the same ID are removed.
Single Number Reach XML Schema
The SNR table stores SNR profile data, as shown in Figure 5-1. When provisioning a subscriber using CLI, the subscriber ID and the corresponding XML file populate the SNR table. When provisioning a subscriber from a third party system, the subscriber ID and the XML content populate the SNR table.
Note The software used to create the XML file must check for valid values and generate the file in proper XML format.
The schema below defines the Single Number Reach profile XML format. The XML format is provided here for raw XML file modification, and has the definitions of different XML segments.
Note: The corresponding .xml instances should be stripped ofextra white spacing and tab indentations, to ensure they donot exceed the maximum size of 8K (8192) bytes. They shouldalso not contain any semicolons or single-quotes anywhere,including in the header of the file.
Multiple SNR Invocation disallowed forsubscriber. While SNR already invoked for thissubscriber, subsequent calls to this subscriberwill be sent to voicemail.
</xs:documentation></xs:annotation>
</xs:enumeration><xs:enumeration value="1">
<xs:annotation><xs:documentation>
Allow Multiple SNR Invocation for thissubscriber, if the FeatureConfigAllow-Multiple-Invocation=Y. Even if SNR isalready invoked for this subscriber, subsequentcalls will also try to invoke SNR.
A value of 0 means do not ring this UE at all - this canbe used to temporarily prevent calling this UE, withoutneeding to completely remove the UE from the schedule.
The time (in units of number of rings) to wait beforestarting to ring this UE. Since each ring correlates toabout 6 seconds, a value of 5 means wait about 30seconds before start ringing this UE.
<xs:documentation>The priorities for all of the TOD and HOL schedulesneed to be unique. This ensures that when there isan overlap of more than one schedule beingapplicable at a particular time, the desired higherpriority schedule will be chosen.
The subscriber web-based interface is not provided by Cisco, but by the service provider. The interface can invoke CLI commands to allow the subscriber to configure Single Number Reach options. Subscriber user IDs and passwords, used to control access, are not stored on the BTS 10200, but maintained by the service provider elsewhere.
Subscriber IVR-Based Interface
This section describes the subscriber IVR-based interfaces. It includes the following:
• Accessing the Single Number Reach IVR Menu
• IVR Authentication
• Single Number Reach Main Menu
• Single Number Reach (Forwarding Per Schedule) Activation
• CFU Activation
• VMA Activation
• Single Number Reach Deactivation
• Single Number Reach IVR Prompts
Accessing the Single Number Reach IVR Menu
A Single Number Reach subscriber can set options using an IVR-based interface accessible from any UE. The subscriber calls a known DN (like a toll-free number) and enters the user ID and PIN to hear a configuration menu. Because this interface uses the master number as the user ID, the master number must be a DN and not an AOR.
IVR Authentication
Figure 5-2 shows user ID authentication for Single Number Reach.
Figure 5-3 shows the PIN authentication for the Single Number Reach feature. The detailed IVR prompts are listed in Table 5-8.
After the user ID and PIN are authenticated, the subscriber hears a list of options available on the main menu (based on current Single Number Reach status):
1. Activate or configure forwarding to a single number2. Activate forwarding per your schedule3. Activate forwarding straight to voicemail4. Deactivate all SNR forwarding features9. Exit this SNR system0. To hear these instructions repeated
Table 5-8 gives details about the prompts used in the Single Number Reach IVR menus. The IVR prompts display how to traverse the Single Number Reach IVR tree. The IVR prompts provide important information on how to modify the different parts of Single Number Reach through the IVR system. Some prompts are split into multiple messages or combined into single messages when played. In the IVR prompts, a PIN is used instead of a password. This lets the subscriber know the prompts are for the Single Number Reach IVR PIN instead of the Single Number Reach web interface password and prevents reuse of existing similar password prompts.
Table 5-8 IVR Prompts
IVR Prompt on Flowchart IVR Prompt Wording
1 SNR_AUTH_WELCOME Welcome to the Single Number Reach system.
2 SNR_AUTH_USER_ID Please enter your SNR number, followed by the number sign key.
3 SNR_CONFIRM_NUM You are about to administer SNR for <xxx-xxx-xxxx>. To confirm, press <1>. To administer a different SNR number, press <2>.
4 SNR_INVALID_USER We’re sorry. The number you have entered is incorrect.
5 SNR_INVALID_ABRT Please hang up now, consult your written instructions, and try again later.
6 SNR_ENTER_PIN Please (re-)enter your pin now, followed by the number sign key.
7 SNR_INVALID_PIN We’re sorry. The pin entered does not match the current PIN for SNR number <xxx-xxx-xxxx>.
8 SNR_PIN_ATTEMPTS If this is not the desired SNR number, please hang-up and retry. The number of consecutive invalid pin attempts for this account is currently <x>. For your protection, if this count reaches <5>, account access via phone will be disabled.
9 SNR_AUTH_LOCKOUT_ABORT Phone access for this account is disabled. To re-enable phone access, please reset your pin via the internet.
10 SNR_FORWARDING_PER_SCHED Your calls are currently being forwarded based upon your forwarding schedule.
11 SNR_FORWARDING_TO_NUM Your calls are currently being forwarded to <xxx-xxx-xxxx>.
12 SNR_FORWARDING_TO_ VOICEMAIL Your calls are currently being forwarded straight to your voicemail.
13 SNR_NO_FORWARDING_ACTIVE You currently do NOT have any of your SNR Call Forwarding Features active.
14 SNR_TO_ACTIVATE_CNFG_CFU To activate or configure Forwarding to a single number, press <1>.
15 SNR_TO_CONFIGURE_CFU To configure Forwarding to a single number, press <1>.
16 SNR_TO_ACTIVATE_FWD_SCHED To activate Forwarding per your schedule, press <2>.
17 SNR_TO_ACTIVATE_VMA To activate Forwarding straight to Voicemail, press <3>.
18 SNR_TO_DEACTIVATE_ALL_SNR To deactivate all SNR Forwarding Features, press <4>.
19 SNR_TO_EXIT_TO_VMS To exit this SNR system and connect to your voicemail, press <5>.
20 SNR_TO_EXIT To exit this SNR system, hang-up or press <9>.
21 SNR_TO_RETURN_TO_PREV_MENU To return to the previous menu, press <9>.
22 SNR_TO_REPEAT_INSTRUCTIONS To hear these instructions repeated, press <0>.
23 SNR_SNR_NOT_CFG Forwarding per schedule is not configured properly. Please contact customer service.
24 SNR_NO_SCHED_ACT Your Forwarding schedule needs to be configured via the Internet before it can be activated.
25 SNR_CFU_NOT_CFG Forwarding to a single number is not configured properly. Please contact customer service.
26 SNR_CFU_NUM_INVALID Your forward-to number is not set to a valid number.
27 SNR_FWD_TO_NUM_IS Your forward-to number is <xxx-xxx-xxxx>.
28 SNR_TO_FWD_TO_THIS_NUM To forward all calls to this number, press <1>.
29 SNR_CFU_NUM_CNFM Your forward-to number is going to be changed to <xxx-xxx-xxxx>. To confirm, press <1>. To change your forward-to number to a different number, press <2>. To return to the previous menu without updating your forward-to number, press <9>. To hear these instructions repeated, press <0>.
30 SNR_TO_CHANGE_FORWARD_TO_ NUM To change your forward-to number, press <2>.
31 SNR_VMA_NOT_CFG Forwarding to voicemail is not configured properly. Please contact customer service.
32 SNR_EXITING_SYST You are now exiting the SNR configuration system. Goodbye.
33 EXITING_TO_VOICEMAIL You are now exiting the SNR configuration system and connecting to your voicemail.
34 SNR_ENTR_FWD_NUM Please enter the number to which you want your calls forwarded, followed by the number sign key.
Step 2 Perform the duplicate_records action on the NPA. Tables that contain records whose digit strings are like the old NPA have an additional record created.
Step 3 After the start date, perform the update-ani action to change duplicate records to reflect the new NPA:
change split-npa old-npa=972-516; update-ani=Y;
Step 4 After the end date, perform the cleanup action to delete records with the old NPA.
change split-npa old-npa=972-516; cleanup=Y;
T.38 Fax Relay
Configuring T.38 Fax Relay
This section describes the steps required to configure T.38 fax relay for different trunk groups, gateways and tables.
Administrator may configure profile information on the Cisco BTS 10200 for each managed MGCP/NCS endpoint to:
• Handle fax using existing audio media (fax pass-through).
• Handle fax using Cisco-proprietary Gateway mode. (Only if supported on the endpoint. Cisco currently does not support this in context of the FXR Package).
• Handle fax using T.38-Loose mode for fax handling, as defined by the MGCP FXR package.
• Allow Cisco BTS 10200 to determine the fax procedure to apply based on the capabilities of the two remote endpoints involved in the fax.
Step 2 For the MGCP / NCS / TGCP Interface T38_ FXR _LOOSE _SUPP:
• ‘Auto’ (default) internally sets ‘Y’ or ‘N’ depending if endpoint supports T.38 fax as indicated by audit endpoint acknowledgement.
• If endpoint supports T.38 FXR package, but does not support advertising this in audit acknowledgement, the Cisco BTS 10200 assumes it is not supported.
• This parameter enables selection of what format to encode the SDP capabilities attributes towards the endpoint when the attributes are received.
Step 2 ‘Cisco’
Step 3 For the MGCP / NCS / TGCP Interface, SDP-CAP-ENCODE-TYPE:
• In MGW Profile table:
– This parameter enables selection of what format to encode the SDP capabilities attributes towards the endpoint when the attributes are received.
• ‘Cisco’
– Cisco proprietary method of encoding SDP capability parameters using “x-” extension prefix.
• ‘STD’
– Encode using the format detailed in RFC-3407.
• ‘Auto’ (default)
– Encode the format that was received from the remote end. Therefore, no changes.
Cisco BTS 10200 SIP interface always encodes using RFC-3407.
For the MGCP / NCS / TGCP Interface, SDP-CAP-ENCODE-TYPE.
Step 4 QOS Table
FAX_T38_ENABLED
Binary flag (Y/N) with default = ‘Y’.
QOS is optional for endpoints and trunks.
If no QOS, or this flag set all ‘Y’ (default), then this flag does not change T.38 Fax feature behavior.
MGCP/TGCP/NCS/H.323 endpoints:
If either endpoint in the call (including SIP) has a QOS entry and this flag set to ‘N’, then BTS will indicate to each MGCP/H.323 endpoint to NOT use T.38 procedures regardless of T.38 loose flag set in MGW profile.
MGCP type endpoints may still perform T.38 fax transmission if the other end is detecting fax and is off-net SIP.
SIP-to-SIP and H.323-to-H.323 calls ignore this flag.
• Cisco proprietary method of encoding SDP capability parameters using “x-” extension prefix.
Step 3 ‘STD’
• Encode using the format detailed in RFC-3407.
Step 4 ‘Auto’ (default)
• Encode the format that was received from the remote end. Therefore, no changes.
• ‘Auto’ (default) internally sets ‘Y’ or ‘N’ depending if endpoint supports T.38 fax as indicated by audit endpoint acknowledgement.
• If endpoint supports T.38 FXR package but does not support advertising this in audit acknowledgement, the Cisco BTS 10200 assumes it is not supported.
Cisco BTS 10200 SIP interface always encodes using RFC-3407.
Provisioning the MGCP / NCS / TGCP Interface SDP-CAP-ENCODE-TYPE
Step 1 In MGW Profile table:
• This parameter enables selection of what format to encode the SDP capabilities attributes towards the endpoint when the attributes are received.
Step 2 ‘Cisco’
• Cisco proprietary method of encoding SDP capability parameters using “x-” extension prefix.
Step 3 ‘STD’
• Encode using the format detailed in RFC-3407.
Step 4 ‘Auto’ (default)
• Encode the format that was received from the remote end. Therefore, no changes.
Cisco BTS 10200 SIP interface always encodes using RFC-3407.
Provisioning the QoS Table
Step 1 FAX_T38_ENABLED
Step 2 Binary flag (Y/N) with default = ‘Y’.
Step 3 QOS is optional for endpoints and trunks.
Step 4 If no QOS, or this flag set all ‘Y’ (default), then this flag does not change T.38 Fax feature behavior.
Step 5 MGCP/TGCP/NCS/H.323 endpoints:
• If either endpoint in the call (including SIP) has a QOS entry and this flag set to ‘N’, then BTS will indicate to each MGCP/H.323 endpoint to NOT use T.38 procedures regardless of T.38 loose flag set in MGW profile.
• MGCP type endpoints may still perform T.38 fax transmission if the other end is detecting fax and is off-net SIP.
Step 6 SIP-to-SIP and H.323-to-H.323 calls ignore this flag.
Step 1 To provision the H.323 Interface, use the REMOTE_FAX_PORT_ RETRIEVAL_MSG Field in H323-TG-Profile and H323-TERM-Profile.
– H.323 gateway can report UDP port for T.38 fax transmission in either H.245 OLC (default) or OLC ACK.
– Indicates which field BTS should look into for this value.
– Cisco IOS H323 GW report in OLC.
Provisioning H.323 Interface: CA-CONFIG Table
Step 1 Cisco BTS 10200 global values are used by H.323 interface to negotiate the T.38 fax connection during voice call establishment when inter-working with a non-H323 endpoint.
Step 2 T38_MAX _BIT_RATE:
Default 14.4
Step 3 T38_MAX _BUFFER_SIZE:
Default 200
Step 4 T38_MAX _DATAGRAM_SIZE:
Default 72
Provisioning CA-CONFIG Table
Step 1 CODEC-T38-PTIME
T.38 codec packetization period.
Default = 20.
Temporary Disconnect
Step 1 Add a cos-restrict table entry and customize restriction behavior as needed:
add/change cos-restrict id=tdisc-restricts;
Step 2 Associate cos-restrict to a POP.
add/change pop id=new; temp-disc-cos-restrict-id=tdisc-restricts;
Step 3 Configure service-denial behavior as needed.
add/change pop id=new; temp-disc-service-allowed=N;
Step 4 Optionally, apply any additional call-types other than as described in R-1070 for which COS feature should not be triggered/invoked.
Step 7 In general for TDISC feature capability at switch level, configure the COS feature as part of default Office service ID.
If "office-service" is the name for the default office-service configured in CA-CONFIG, ensure availability of the COS feature in the default office service.
change service id=office-service; fname1=COS;
Subscriber Provisioning
Step 1 Set subscriber status as necessary. To achieve a TDISC on a subscriber, set the status field as TEMP-DISCONNECTED. To undo the TDISC status, change the TDISC status to another appropriate permissible value.
Step 5 Combine the features defined above into a service:
add/change service id=vm_always; FNAME1=VMA; fname2=VM_ACCESS;
Provisioning Resources
The following table shows how to create the app-server table for a subscriber. The next step shows the multiple ways by which this can be associated to the subscriber. The app-server can be associated to the subscriber through four tables:
• Subscriber table: by populating the VOICE_MAIL_ID with the app-server id
• Subscriber-profile table: by populating the VOICE_MAIL_ID with the app-server id
• Pop table: by populating the VOICE_MAIL_ID with the app-server id
Step 1 Add the service ID by entering a command similar to the following:
add service id=noLNP; fname1-8xx; fname2=911; fname3=USTWC;
Step 2 Add the office service ID to the POP:
change pop id=pop1; office-service-id=noLNP;
Configurable FIM/XMLThe BTS supports an FIM/XML (Feature Interaction Module/Extensible Markup Language) file which defines the interaction between features. However, the current FIM/XML format is time consuming because of the large number of configurable parameters you must define. The Configurable FIM/XML feature introduces a new external configurable FIM/XML file which is more efficient because it defines only the interactions between the IMS Service Control Interface (ISC) and Feature Control Protocol (FCP) features. The BTS10200 Softswitch POTS Feature Server manages the ISC and FCP interactions between ISC and FCP features using the parameters defined in the configurable FIM/XML file.
Using an offline tool created by Cisco BTS, you produce the configurable FIM/XML file using the system’s FIM/XML file and schema data.
The external FIM/XML file allows you to define the behavior of the external features as they interact with the BTS by
• Adding a new external feature name
• Specifying the list of features inhibited by an external feature
• Defining the list of features that inhibit the external feature
• Specifying the external features’ order of precedence order
• Defining error response operations
Generating the New FIM/XML File
Each BTS release includes an original FIM/XML file. The offline FIM/XML tool allows you to define a new external feature or modify existing interactions involving the ISC features.
Tool Requirements
The system must meet the following conditions and requirements for the FIM/XML tool:
• JVM 1.6 or above is installed on the system.
• All three input files are present in the same directory as the tool .jar file.
• The user has writer permission for the directory where the FIM/XML offline tool is located.
• The user has read permission for all the input XML files.
A Shared Initial Filter Criteria (iFC) file specifies all the data you require to provision a new feature in the Element Management System (EMS). The shared iFC file is analogous to provisioning feature data through the CLI. You can provision all the user commands supported through CLI using the shared iFC.
The BTS supports the following commands through shared iFC:
The following conditions apply between the configurable FIM/XML file and the shared iFC file:
• Any property provisionable through FIM/XML cannot be provisioned through the shared iFC file.
• If an external feature name exists in the FIM/XML file but is not defined in EMS, then EMS provisions that external-feature name by reading the FIM/XML file.
For additional information about the shared IFC, refer to BTS XML Support by FTP Adapter Feature Module.
Restrictions and Limitations
You cannot use the FIM/XML to do the following:
• Change the interaction between internal features
• Define feature configuration properties
• Define feature support profile
Each BTS release includes an original FIM/XML file which is installed during system setup and upgrades. Use this file as input, along with the schema, to produce the new FIM/XML file with the offline tool.
Each BTS release includes an original FIM/XML file. The offline FIM/XML tool allows you to define a new external feature or modify existing interactions involving the ISC features.
The system must meet the following conditions and requirements for the FIM/XML tool:
• JVM 1.6 or above is installed on the system.
• All three input files are present in the same directory as the tool .jar file.
• The user has writer permission for the directory where the FIM/XML offline tool is located.
• The user has read permission for all the input XML files.
The following procedure describes how to generate the configureable FIM/XML file using the offline FIM/XML tool.
Step 1 Use any XML editor to create an external FIM/XML file based on the rules from the schema file provided by the BTS during installation. You cannot modify the schema data.
Step 2 Use the XML editor to edit a sample file provided with the tool. This file becomes the offline FIM/XML configuration file used in the next step.
You can edit the FIM/XML file so that emergency features such as 9-1-1, Hostage Negotiation, and Emergency Callback (ECB) cannot be inhibited by the operator after the configurable FIM/XML file is downloaded to the BTS, as shown in the following script:
If you do not specify a schema path, the BTS will use the following default path: /opt/OptiCall/potsctx/bin/FIMXML.xsd
Step 3 Run the following Java application:
java —jar fimxml.jar param1 param2 param3 param4
Where
• param1 = name of the external FIM/XML file described in the first step.
• param2 = the name of the original FIM/XML file produced during the BTS installation. Copy this file from the following path: /opt/OptiCall/etc/fimxml/FSPTC235/FIMXMLRules.xml.
• param3 = name of the configuration file described in the second step.
• param4 = the name of the configurable file to be generated (defaults to merged.xml). This parameter is optional.
If the script runs successfully, the tool returns the following message SUCCESS!! New FIM/XML generated at path <path> and copies or FTPs the successfully generated configurable FIM/XML file to the EMS.
If the script does not complete successfully, the system returns a non-zero value and generates a log file which is copied to the same directory as the FIM/XML tool .jar file.
Note The tool produces log files for both successful and unsuccessful attempts.
The system returns the following message for schema-related errors:
Schema Error: FileName:LineNo:ColumnNo
The system returns the following message for feature name-related errors:
Error:<Feature Name> <error message>
Note You can troubleshoot the errors from the descriptions provided with the error messages.
Step 4 Enter the following command from the EMS:
install fimxml file_name=<absolute_path>
This command does the following:
• Processes the configurable FIM/XML file on the EMS
• Adds external feature names to the EMS
• Copies the new file to the following path: /opt/OptiCall/etc/fimxml/FSPTC235/FIMXMLRules.xml.
Seasonal Suspend ProvisioningThis section explains how to provision the Seasonal Suspend feature.
Note For complete CLI parameter descriptions, see the Cisco BTS 10200 Softswitch CLI Database.
Office Provisioning
You can use the following procedure to create the seasonal suspend and CoS features and to provision a special cos-restriction ID for the Seasonal Suspend feature. You can also set up announcements for the seasonal suspend line.
Step 1 Add the Seasonal Suspend feature (SEAS) to the feature table.
Step 2 To enable SEAS at the switch level, add it to the default office service ID. The system makes all the features in the default office service ID available to all subscribers on the switch.
(In this example, assume that the system displays the default-office-service-id as offc999.)
d. Display the features and feature numbers in the default-office-service-id. (Use the value determined in Substep c for the value of id in the following command.)
show service id=offc999;
e. If <fnameX> is not already present in the list displayed in Substep d., add SEAS to the default-office-service-id. Use an <fnameX> value that is not used yet. (The system allows a maximum of 10 <fnameX> entries in the service table.)
change service id=offc999; fnameX=SEAS;
where fnameX is a previously unused feature-number parameter in this service table.
Caution Use a new <fnameX> (one that is not currently used). If you use an <fnameX> that is already used for another feature, you cause that other feature to be dropped from the default office service ID.
f. Verify that the SEAS feature is included in the default-office-service-id.
show service id=offc999;
Step 3 Add a cos-restrict table entry and customize restriction behavior as needed. Be sure to set the national-wb-list parameter to white. We recommend that you create a special cos-restrict specifically for the Seasonal Suspend feature.
Step 4 Add digit strings to the national-wb-list to allow outbound dialing to desired DNs, such as 611 (or a customer support DN), voice-mail pilot number, and so forth.
Caution If you are provisioning a long-distance number for the digit-string, do not enter a leading digit 1. That could cause the call to be denied. Subscribers will be able to call the long-distance number with or without the 1, depending on the provisioning in the dial-plan table.
Step 5 (Optional) If you want to block toll-free numbers for seasonal suspend subscribers, change the provisioning in the cos-restrict table to set nod-wb-list as black. You can allow subscribers to call specific toll-free numbers (for example a toll-free customer service or repair line or a toll-free voice-mail pilot number) by including the digit string (without the leading digit 1) in the national-wb-list and provisioning the national-wb-list as white.
a. change cos-restrict id=special_cos_1; nod-wb-list=black;
b. add nod-wb-list cos-restrict-id=special_cos_1; nod=toll-free;
c. add national-wb-list cos-restrict-id=special_cos_1; digit-string=800-555-5555;
Caution If you are provisioning a toll-free number for the digit-string, do not enter a leading digit 1. That could cause the call to be denied. Subscribers will be able to call the long-distance number with or without the 1, depending on the provisioning in the dial-plan table.
Step 6 Link the Seasonal Suspend feature to the CoS restriction ID. This step enforces the COS restriction for the Seasonal Suspend feature.
Step 9 Set up announcements for seasonal suspend. Use values for announcement-file that match actual audio files on your announcement server. The .au files must be recorded and uploaded to the announcement server and must be accessible to the BTS 10200.
Step 2 Verify that the system displays the new status for this subscriber.
show subscriber id=sub1;
Provisioning Options for Inbound Call Treatment
This section explains how to provision inbound call treatment options.
Add a Referral DN to Inbound Seasonal Suspend Announcement
You can use this command to add a referral DN to the subscriber-feature-data table. If you do that, the system plays a seasonal suspend announcement that includes the referral DN, entered as value1 in this command. The value for value1 must be a valid DN and must be entered without any dashes (hyphens). If you do not enter this command, the system still plays the generic inbound seasonal suspend message.
Note If status=seasonal-suspend in the subscriber table, the system does not check the active flag in the subscriber-feature-data table.
Route to VMA Instead of Seasonal Suspend
You can provision the system to route all inbound calls to voicemail with the Voice Mail Always (VMA) feature. To enable this feature, you must take the following steps:
• Verify that the VMA feature is activated before you set the subscriber status to seasonal suspend. (VMA can be activated or deactivated only when the subscriber status is active.)
• For specific VMA provisioning commands, see the VMA provisioning procedure in this guide.
Caution If VMA is assigned and active, it takes precedence over the Seasonal Suspend feature for inbound calls, and the system does not provide any seasonal suspend treatment for inbound calls. However, the system can still provide seasonal suspend treatment for outbound calls if provisioned to do so.
Provisioning Options for Outbound Call Treatment
Provision the Seasonal Suspend feature either to provide an announcement on disallowed outbound call attempts or to route disallowed outbound calls to the customer support DN. The parameters for these options are in the feature-config table:
• The default value of route-to-cust-support-dn is N, which means that the call is given to the seasonal suspend announcement and is not routed to the customer support DN. The announcement server (if capable) includes the customer support DN in the announcement if this DN is provisioned as the value for cust-support-dn. However, if the DN is not provisioned, the system provides a generic seasonal suspend announcement.
• If the value of route-to-cust-support-dn is provisioned as Y, the call is routed to the customer support DN if this DN is provisioned as the value for cust-support-dn. However, if route-to-cust-support-dn=Y and the DN is not provisioned, the system plays the generic seasonal suspend announcement.
Note For these commands the cust-support-dn value must be a valid DN entered without any dashes (hyphens). You can provision a local 10-digit number, as shown in the examples below, or a toll or toll-free number.
Note The value for cust-support-dn applies globally to all customers that have the SEAS feature. Therefore, only one DN can be provisioned for this purpose.
This section explains how to perform operational tasks for this feature.
• Moving Subscriber Groups from BTS 10200 to BTS 10200
• Purging Subscribers
• Ensuring Data Match
• Auditing and Synching Subscribers
Moving Subscriber Groups from BTS 10200 to BTS 10200
When moving subscribers from one BTS 10200 to another BTS 10200 in the cluster, divide subscribers into groups. Use one of the following criteria that best meets your needs:
• Geography
• Rate Center
• Administrative grouping
When choosing group size, consider the following:
• Large groups mean fewer groups, but large ones.
– Fewer groups mean less chance of operator error.
– Fewer groups mean a large amounts of subscribers per group. A disaster suddenly increases the load on the BTS 10200.
• Small groups mean many groups, but small ones.
– Many groups mean more chances of operator error.
– Many groups mean smaller amounts of subscribers per group. A disaster results in an even load distribution to multiple BTS 10200s
Step 1 Stop provisioning.
Step 2 On the current BTS 10200, in the table_subscriber_serving_group, change the owner to the future owner BTS 10200.
Step 3 On the future owner BTS 10200, enter the following to pull the data from the HSS:CLI> pull hss-public-id [email protected]
Step 4 On the current BTS 10200, change the DNS Group1 name to point to the future owner BTS 10200:
Step 5 On the future owner BTS 10200, change the owner of Group1 in table subscriber-serving-group to the future owner BTS 10200.
Purging Subscribers
Any BTS 10200 in a cluster can download subscriber data, but one BTS 10200 lacks capacity to store all subscribers in a cluster. When a BTS 10200 reaches maximum capacity it will be unable to pull new subscriber data from the HSS. To avoid this, manually purge all subscribers not owned by this BTS 10200.
Before Moving Subscriber Groups from BTS 10200 to BTS 10200 do the following procedure.
Step 1 On the current BTS 10200, create a list of public-ids in Group1.
Step 2 Copy the list to the future owner BTS 10200.
Step 3 Using the list, the future owner BTS 10200 pulls each subscriber’s data from the HSS.
Auditing and Synching Subscribers
The BTS 10200’s EMS does periodic background audits with the HSS. If the EMS finds an inconsistency, it synchronizes the data. If the BTS 10200 owns the subscriber group, its data overwrites that on the HSS. If the BTS 10200 does not own the subscriber group, the HSS data overwrites that on the BTS.
For each ServingIndication the BTS 10200 sends a User-Data-Request to the HSS. The local subscriber table is compared to the User-Data-Answer and no update is made to HSS-REPOSITORY-DATA table.
If the BTS 10200 owns the subscriber group for this public-id, the BTS 10200 sends a Profile-Update-Request to the HSS for each serving indication.
If the BTS 10200 does not own the subscriber group for this public-id, the BTS 10200 sends a User-Data-Request to the HSS for each subscriber group. If there is a mismatch, the HSS-REPOSITORY-DATA table updates.
To perform a data audit with the HSS, enter the following:
TAS ProvisioningThis section explains how to provision TAS interfaces and subscribers.
Note If the origination information in the incoming S-CSCF SIP message does not match the allowed (provisioned) values in the BTS 10200 database, the BTS 10200 fails the call with a 403 response.
Some of the values shown in this section, such as phone numbers and TSAP addresses, are intended as illustrative examples. You should use values appropriate for your network. In addition, you might need to enter values for some additional optional parameters (not shown here), depending on the requirements of your network. For a complete list and definitions for all parameters, see the Cisco BTS 10200 Softswitch CLI Database.
This procedure assumes that you have provisioned several prerequisite tables, such as call-agent and point of presence (POP), as well as routing and dial-plan tables,
Office Provisioning
Step 1 Add the isc-profile tables for the three types of TAS processing.
Step 4 Add a cause code map profile and a cause code map for the TAS. This map links the standard release code 27 with a 404 release code so that the TAS release code behavior is consistent with RFC 3398.
Step 5 Add the trunk group and link it to the SIP-based trunk group profile.
Be sure to set tg_type=SOFTSW and poi=ISC_TG as shown. Setting poi=isc-tg causes TAS processing to take precedence over all other call-processing features for this trunk group.
You must also add the cause_code_map_id to reference the applicable cause code map (TAS_MAP in this example).
control trunk_grp id=6997; mode=FORCED; target_state=ins;
Step 8 Control the SIP element in service.
control sip_element tsap_addr=sia-SYS16CA146.ipclab.cisco.com:5060; target_state=INS;
Step 9 If you want to use the LNP feature, enter the applicable digit string.
add ported_office_code digit_string=216-555;
Step 10 If you want to use the RACF feature, enter the applicable UAN domain name. The value must match the host part of the public_id parameter in the bts_public_id table for this subscriber (see Step 2 in “Subscriber Provisioning” section on page 5-196).
Terminating White and Black List ProvisioningTo provision the Terminating White and Black List for TDISC subscribers, use the following attribute and table:
• terminating-wb-list attribute in cos-restrict table
• terminating-wb-list table
terminating-wb-list attribute in cos-restrict table
To provision the Terminating White and Black List, configure the terminating-wb-list attribute in the cos-restrict table. The TERMINATING-WB-LIST attribute has the following token name, type, and values:
If the terminating-wb-list token is set to
• NONE—All incoming calls are blocked.
• WHITE—An incoming call is accepted if the calling number is found in the list. All other incoming numbers are blocked.
• BLACK—An incoming call is blocked if the calling number is found in the list. All other incoming numbers are allowed.
terminating-wb-list table
The terminating-wb-list table has the following tokens:
• The COS-RESTRICT-ID token is the ID of the cos-restrict table that contains the terminating-wb-list attribute.
After adding the cos-restrict id, you need to associate the id to a POP. See the Provisioning Steps section for more information.
• The DIGIT-STRING token is the DN (1–14 digits) specified to be blocked or accepted.
Provisioning Steps
This feature can be configured only for TDISC subscribers. To provision TDISC subscribers, see the Temporary Disconnect section in the Cisco BTS 10200 Softswitch Provisioning Guide.
Step 3 Add the cos-restrict id and the Terminating White List to the cos-restrict table.
add cos-restrict id=<cos-res-id>; terminating-wb-list= [NONE | WHITE | BLACK];
• Use the show, add, change, delete commands as given below to verify, add, change, or delete the cos-restrict table. For a complete list of CLI commands used with the cos-restrict table, see the Cisco BTS 10200 Softswitch CLI Database.
show cos-restrict id=<cos-res-id>;terminating-wb-list= [NONE | WHITE | BLACK];add cos-restrict id=<cos-res-id>;terminating-wb-list= [NONE | WHITE | BLACK];change cos-restrict id=<cos-res-id>;terminating-wb-list= [NONE | WHITE | BLACK];