Provisioning Guide, Release 6.0.x - Features [Cisco BTS 10200 Softswitch]

Table Of Contents

Features

Introduction

Vertical Service Codes

NANP Dial Plan VSC Provisioning

Non-NANP Dial Plan VSC Provisioning for Subscriber and Centrex

Subscriber Defaults

Provisioning Optional Token Defaults

Checking Default Values

Provisioning Defaults using Command Alias

Viewing Factory Defaults

Restoring Factory Defaults

Feature Provisioning

8XX (Toll-Free Calling)

Office Provisioning

Add 8XX to the Office Service IDs

Provisioning Resources

Provisioning Notes/Caveats

911 Emergency

Office Provisioning

Provisioning Resources

Media Gateway Setup

Centrex Provisioning

Emergency Callback

Hostage Negotiation LEA

Viewing Active Calls

CLI Provisioning

CLI examples

Alerting Notification to Third Party Feature Server

Precedence for Provisioned Values

Anonymous Call Rejection and A/D

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Alternate Activation and Deactivation Method

Automatic Callback

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Automatic Recall

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Two-Level AR Activation

Busy Line Verification

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Provisioning Notes/Caveats

Call Block—Reject Caller

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Provisioning Notes/Caveats

Block All Inbound Calls

Call Forward Busy

Office Provisioning—Call Forwarding for Unreachable Condition

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

Call Forwarding Combination

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Provisioning Notes/Caveats

Alternate Way to Activate and Deactivate CFC

Call Forward No Answer

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

Call Forward Redirection

Call Forwarding Unconditional

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

Call Forwarding Variable for Basic Business Groups

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

Call Hold

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Call Park, Call Park Retrieve

Office Provisioning

Subscriber Provisioning

Provisioning Notes/Caveats

Call Transfer

Office Provisioning

Subscriber Provisioning

Call Waiting

Office Provisioning

Subscriber Provisioning

Alternate Activation and Deactivation Method

Call Waiting Deluxe

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Alternate Activation and Deactivation Method

Caller ID with Call Waiting

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

Caller Name Blocking

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Calling Line Identity Presentation, Restriction

Calling Name Delivery

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Calling Number Delivery

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Calling Number Delivery Blocking

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Caller Identity Delivery Suppression-Delivery

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Caller Identity Delivery Suppression-Suppression

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Cancel Call Waiting

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Class of Service Screening

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Provisioning for IVR Collection of Account/Authorization Codes

Subscriber Provisioning

Centrex Provisioning

Codec Negotiation

Codec Selection

Custom Dial Plan

Office Provisioning

Centrex Provisioning

MLHG Provisioning

Provisioning Notes/Caveats

Customer Originated Trace

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Direct Call Pickup Without Barge-In

Office Provisioning

Centrex Provisioning

MLHG Provisioning

Direct Call Pickup With Barge-In (DPU)

Office Provisioning

Centrex Provisioning

MLHG Provisioning

Distinctive Alerting/Call Waiting Indication

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Do Not Disturb

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Alternate Activation and Deactivation Method

Group Speed Call: 1-Digit and 2-Digit

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Alternate Provisioning Method

Hotline

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

Hotline—Variable

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

Alternate Activation and Deactivation Method

Incoming Simulated Facility Group

Office Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

IP Transfer Point Non-Stop Operation

NSO Configuration: D-Link for ISUP with ASP Load Sharing

NSO Configuration: D-link for TCAP with ASP Load Sharing

Limited Call Duration

Local Number Portability for ANSI/North America

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Provisioning Notes/Caveats

Local Number Portability for ITU Local BTS Database Query

Office Provisioning

Subscriber Provisioning

NOA Routing and Dial Plan Provisioning

Allow ACQ or QoR Query on Incoming Trunk Calls

Destination and Call Type ACQ Control

Outgoing Carrier Call LNP ACQ Query Control

Provisioning Notes/Caveats

Multiline Variety Package

Multi-Line Hunt Group

Multi-Lingual Support for Interactive Voice Response and Announcements

Office Provisioning

Provisioning Resources

Announcement Provisioning

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Multiple Directory Number

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

No Solicitation Announcement

Office Provisioning

Provisioning Resources

Announcement Provisioning

Provisioning Feature Control Options for the IVR Interactions

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Provisioning Notes/Caveats

On-Net Routing and Local Number Portability for Inter-PacketCable Cable Management Server Routing

Provisioning LNP Queries

Provisioning an LNP Query on a Carrier Call

Provisioning Carrier Bypass (On-Net Route)—No LNP Queries

Provisioning Carrier Bypass (On-Net Route)—LNP Queries

Provisioning Carrier Bypass (On-Net Route)—Multi-BTSes

Provisioning Inter-CMS—Subscriber Origination (if no NRS), or Trunk Origination on MGC or Terminating CMS (ALL-CALLS + LNP Query)

Provisioning Inter-CMS with NRS—Same BTS Acting as CMS and MGC

Selectively Provisioning LNP Queries (Allow or Disallow) for a Particular Call Type

Outgoing Call Barring

Office Provisioning

Subscriber Provisioning

Alternate Activation and Deactivation Method

Provisioning Notes and Caveats

Outgoing Call Barring—Activation, Deactivation, and Interrogation

Office Provisioning

Subscriber Provisioning

Centrex Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

Outgoing Simulated Facility Group

Office Provisioning

Centrex Provisioning

Own Calling Number Announcement

Office Provisioning

Provisioning From a VSC

Centrex Provisioning

Privacy Screening

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

REFER

Office Provisioning

Provisioning Notes/Caveats

Remote Activation of Call Forwarding and PIN_Change

Office Provisioning

Resource Provisioning (IVR)

Feature Provisioning

Provisioning Notes/Caveats

Subscriber Provisioning

Auth Code Provisioning

Remote Call Forwarding

Office Provisioning

Subscriber Provisioning

Replace

Office Provisioning

Provisioning Notes/Caveats

Screen List Editing: SCF, SCR, SCA, and DRCW

Office Provisioning

Resource Provisioning (IVR)

Feature Provisioning

Subscriber Provisioning

Provisioning Notes/Caveats

Alternate Activation and Deactivation Method

SIP Triggers

Office Provisioning

Subscriber Provisioning

Provisioning Resources

Centrex Provisioning

MLHG Provisioning

Speed Call (1-Digit and 2-Digit) and Activation

Office Provisioning

Subscriber Provisioning

Alternate Provisioning Method

Split Numbering Plan Area

T.38 Fax Relay

Temporary Disconnect

Subscriber Provisioning

Centrex Provisioning

MLHG Provisioning

Three-Way Calling

Office Provisioning

Subscriber Provisioning

Three-Way Calling Deluxe

Office Provisioning

Subscriber Provisioning

Usage Sensitive Three-Way Calling

Office Provisioning

Subscriber Provisioning

Voice Mail, Voice Mail Always, and Voice Mail Access

Office Provisioning Voice Mail Activation (VM_ACT), Deactivation (VM_DEACT), and Access (VM_ACCESS)

Office Provisioning Voice Mail Always

Provisioning Resources

Subscriber Provisioning

Centrex Provisioning

Alternate Way of Activating and Deactivating VM and VMA

Warmline

Office Provisioning

Provisioning Resources

Subscriber Provisioning

Time and Weather Number

Office Service ID for a POP

Configurable FIM/XML

Generating the New FIM/XML File

FIM/XML File and Shared iFC File

Restrictions and Limitations

10/11-Digit Screening

Restricting NODs

Seasonal Suspend Provisioning

Office Provisioning

Subscriber Provisioning

Provisioning Options for Inbound Call Treatment

Provisioning Options for Outbound Call Treatment

Turning Off (Deactivating) Seasonal Suspend

Features

Revised: May 21, 2009, OL-15999-13

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:

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.

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.

Vertical Service Codes

VSC 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

•Non-NANP Dial Plan VSC Provisioning for Subscriber and Centrex

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.
add/change digit-map; id=digit-map-1; DIGIT_PATTERN=[regular digit 
pattern]|*xx|11xx|[regular 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:
add/change digit-map; id=digit-map-ctx; DIGIT_PATTERN=[regular Centrex digit 
pattern]|*xx|11xx|[regular Centrex digit pattern];
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:
add/change sub-profile id=plano1; digit-map-id=digit-map=1;
add/change sub-profile id=plano1; digit-map-id=digit-map-ctx;
Step 4 Associate the digman entry to the dial plan profile and update the NANP_DIAL_PLAN field in the dial-plan-profile table to Y:
add/change dial-plan-profile ID=dpp1; DESCRIPTION=dialing plan profile ID2; 
NANP_DIAL_PLAN=Y;
Step 5 Provision the VSC/CDP table with the VSC code. Here is an example for CFUA for POTS and Centrex subscribers:
add/change vsc digit-string=*72;fname=CFUA;
add/change cdp digit-string=*72; fname=CFUA; cdp-id=cdp1; cat-string=11111111111; nod=VSC;
Non-NANP Dial Plan VSC Provisioning for Subscriber and Centrex

Step 1 Provision the digit map with the digit pattern. This CLI example of the digit map highlights only the pattern for the VSC codes to be reported:
add/change digit-map id=digit-map-1; DIGIT_PATTERN=[regular digit 
pattern]|[*,#]xx{*,#]|[regular digit pattern];
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:
add/change digit-map id=digit-map-ctx; DIGIT_PATTERN=[regular Centrex digit 
pattern]|[*,#]xx[*,#]|*#xx[*,#]|[regular Centrex digit pattern];
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:
add/change sub-profile id=plano1; digit-map-id=digit-map-1;
add/change sub-profile id=plano1; digit-map-id=digit-map-ctx;
Step 4 Add or change entries in the Digman table:
add/change digman id=pretrans; RULE=1; MATCH_STRING=^*; REPLACE_STRING=&;MATCH_NOA=ANY; 
REPLACE_NOA=VSC;
add/change digman ID=pretrans; RULE=2; MATCH_STRING=^#; REPLACE_STRING=&; MATCH_NOA=ANY; 
REPLACE_NOA=VSC;
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:
add/change vsc digit-string=*57*; fname=CFUA;
add/change cdp digit-string=*57*; fname=CFUA; cdp-id=cdp1; cat-string=11111111111; 
nod=VSC;
Subscriber Defaults

You 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 Defaults

The 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.
add var_default noun=aggr; var_name=es_supp; def_vals=Y;
Step 3 Verify that the default value for the es_supp token is provisioned.
show var_default noun=aggr; var_name=es_supp;
NOUN=aggr
VAR_NAME=es_supp
DEF_VALS=Y
Reply:Success:Entry 1 of 1 returned.
Checking Default Values

The 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 Alias

You 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.
add var_default noun=sub; var_name=term_type; def_vals=SIP;
Reply:Success:CLI add succesfully
Step 2 Verify that the default value is configured as expected.
show var_default noun=sub; var_name=term_type;
NOUN=subscriber
VAR_NAME=term_type
DEF_VALS=SIP
Reply:Success:Entry 1 of 1 returned.
Viewing Factory Defaults

This 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=subscriber
VAR_NAME=term_type
BTS_DEFAULT=TERM
DEF_VALS=TG
Reply:Success:Entry 1 of 1 returned.
Restoring Factory Defaults

BTS 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.
delete var_default noun=subscriber; var_name=term_type;
Reply:Success:CLI delete successfully.
Feature Provisioning

This 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

8XX (Toll-Free Calling)

Office Provisioning

Step 1 Create the 8XX feature:
add feature fname=8XX; tdp1=COLLECTED_INFORMATION; tid1=SPECIFIC_DIGIT_STRING; ttype1=R; 
description=toll-free; feature_server_id=FSAIN205;
Step 2 Add destination 800.
add destination dest-id=dest800; call-type=TOLL_FREE; route-type=SUB;
Step 3 Add the dial plan profile.
add dial-plan-profile ID=dp1;
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.
add dial-plan ID=dp1; digit-string=800; dest-id=dest800;
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.
add dn2cust-grp digit-string=8005550001; translated-dn=4695558724;
Add 8XX to the Office Service IDs

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.

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;
Step 4 Provision the SCTP association profile:
add sctp-assoc-profile id=sctp_prof; bundle_timeout=500; max_assoc_retrans=5; 
max_path_retrans=5; max_rto=6000; min_rto=301; sack_timeout=101; hb_timeout=1000;
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 5 Provision the SCTP association:
add sctp-assoc id=sctp_assoc1; sgp-id=itp_7507_1; sctp-assoc-profile-id=sctp_prof; 
remote_port=14001; remote_tsap_addr1=10.89.232.9; remote_tsap_addr2=10.89.233.41; 
local_rcvwin=64000; max_init_retrans=5; max_init_rto=1000; platform_id=FSAIN205;
Step 6 Add the DPC:
add dpc id=stp1; point-code=1-101-0; description=STP1 MGTS STP;
Step 7 Add the SCCP network:
add/change sccp-nw id=1; net-ind=NATIONAL; sub-svc=NATIONAL; hop-count=10;
Step 8 Add the subsystem group:
add subsystem-grp id=SSN_TF; platform-id=FSAIN205; tcap-version=ANS92;
Step 9 Add the subsystem:
add subsystem id=SSN_TF; opc_id=opc; local-ssn=254; remote-ssn=254; sccp-nw-id=1; 
sccp-version=ANS92; application-version=AIN01; (if Toll-Free is an IN1 service, 
application-version=IN1);
Step 10 Add the routing key:
add routing-key id=rk_tf; opc-id=opc; sg-grp-id=sg_grp; si=SCCP; rc=201; 
platform-id=FSAIN205; ssn-id=SSN_TF;
Step 11 Add the SCCP route:
add sccp-route opc_id=opc; dpc_id=stp1; subsystem_grp_id=SSN_TF;
Step 12 Add the SLHR profile:
add slhr-profile id=slhr_tf;
Step 13 Add the service logic host route:
add slhr id=slhr_tf; opc_id=opc; dpc_id=stp1; subsystem_grp_id=SSN_TF; gtt-req=Y; tt=254; 
gtt-addr-type=CDPN; gtt-addr=3;
Step 14 Add the ca-config type DEFAULT-TOLL-FREE-SLHR-ID:
add ca-config type=DEFAULT-TOLL-FREE-SLHR-ID; datatype=string; value=slhr_tf;
Step 15 Place the SCTP association in service:
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.

911 Emergency

Office Provisioning

Step 1 Create the 911 feature:
add/change feature; fname=911; tdp1=COLLECTED_INFORMATION; tid1=911_TRIGGER; ttype1=R; 
description=Emergency Service; feature_server_id=FSPTC235;
Step 2 (Optional) Change the CA-config table entry for the default-office-service-id only if it is required to be different from ca-config-base:
change ca-config type=DEFAULT-OFFICE-SERVICE-ID; datatype=string; value=469;
Step 3 (Optional) Change the CA-config table entry for the called-party-hold-control as required by your network:
change ca-config type=E911-CALLED-PARTY-HOLD; datatype=boolean; value=Y; 
Step 4 Add the destination:
add destination dest-id=dest911; CALL_TYPE=EMG; ROUTE_TYPE=ROUTE; 
ROUTE_GUIDE_ID=opr911;zero-plus=y; CLDPTY_CTRL_REL_ALWD=Y; 
Step 5 Add the service:
add service id=469; FNAME1=911; 
Provisioning Resources

Step 1 Add the media server:
add mgw_profile id=cas_911;    packet-type=ip; aal1=n; aal2=n; aal5=n; pvc=n; svc=n; 
spvc=n; ec_supp=n; sdp-origfield-supp=n; sdp-sessname-supp=n; sdp-email-supp=n; 
sdp-phone-supp=n; sdp-bandwidth-supp=n; sdp-info-supp=n; sdp-time-supp=n; 
sdp-attrib-supp=n; mgcp-erqnt-supp=n; mgcp-hairpin-supp=n; mgcp-qloop-supp=n; 
mgcp-3way-hshake-supp=n; mgcp-conn-id-at-gw-supp=n; termination-prefix=NULL; port-start=1; 
vendor=CISCO;  rbk-on-conn-supp=y; mgcp_max1_retries=3; mgcp-t-tran=1000;  
MGCP_EP_SPECIFIC_CAP_SUPP=y;
Step 2 Add the media gateway:
add mgw id=224.14:2434; tsap-addr=10.89.233.74:2434; call-agent-id=CA146; 
mgw_profile_id=cas_911; call-agent-control-port=2427; type=tgw;
Step 3 Add the CAS trunk group profile:
add cas_tg_profile id=cas_911; sig-type=MF-OSS;  mf-oss-type=MO-10II; oss-sig=n; 
test_line=n; e911=y;
Step 4 Add the trunk group:
add trunk_grp id=911; tg_type=CAS; dial_plan_id=dpcas; sel-policy=LRU; direction=BOTH; 
GLARE=SLAVE; tg_profile_id=cas_911; call-agent-id=CA146; mgcp-pkg-type=MO;
Step 5 Add the termination:
add termination prefix=cas/911/; mgw-id=224.14:2434; type=TRUNK; port-start=1; 
port-end=24; 
Step 6 Add a trunk:
add trunk cic-start=1; cic-end=4; tgn-id=911; termination-prefix=cas/911/; 
mgw-id=224.14:2434; termination-port-start=1; termination-port-end=4; 
Step 7 Add the route:
add route id=ops911; tgn1-id=911; 
Step 8 Add the route guide:
add route-guide id=ops911; policy-type=route; policy-id=ops911; 
Step 9 Add the destination:
add destination dest-id=ops911; call-type=EMG; route-type=ROUTE; route-guide-id=ops911; 
zero-plus=y; CLDPTY_CTRL_REL_ALWD=Y;
Step 10 Add the dial plan:
add dial-plan id=dpcas; digit-string=911; dest-id=ops911odr; min-digits=3; max-digits=3; 
Media Gateway Setup

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;
After the above commands are executed, the status should show:
REPLY=CONFIGURATION COMMAND EXECUTED -> 224.14:2434
ADMIN STATUS -> ADMIN_INS
OPER STATUS -> MGW_STATUS_UP
Step 2 Bring the CAS trunk group into service
CLI> control trunk_grp id=911; target_state=ins; mode=forced; 
CLI> status trunk_grp id=911;
After the above commands are executed, the status should show:
REPLY=CONFIGURATION COMMAND EXECUTED CAS_TRUNK_GROUP -> 911
ADMIN STATUS -> ADMIN_INS
OPER STATUS -> TG_INS
Step 3 Bring CAS trunk terminations into service:
CLI> control trunk-termination tgn-id=911; cic=all; mode=forced; target-state=ins;
CLI> status trunk-termination tgn-id=4005; cic=all;
After the commands are executed, the status should show:
CONFIGURATION COMMAND EXECUTED CAS_TRUNK_GROUP -> 911 -> CIC -> 1
TERM ADMIN STATUS -> ADMIN_INS
TERM OPER STATUS -> TERM_STATE_EQUIP
CIC STATIC STATE -> ACTV
CIC DYNAMIC STATE -> IDLE
CONFIGURATION COMMAND EXECUTED CAS_TRUNK_GROUP -> 911 -> CIC -> 2
TERM ADMIN STATUS -> ADMIN_INS
TERM OPER STATUS -> TERM_STATE_EQUIP
CIC STATIC STATE -> ACTV
CIC DYNAMIC STATE -> IDLE
...
CONFIGURATION COMMAND EXECUTED CAS_TRUNK_GROUP -> 911 -> CIC -> 24
TERM ADMIN STATUS -> ADMIN_INS
TERM OPER STATUS -> TERM_STATE_EQUIP
CIC STATIC STATE -> ACTV
CIC DYNAMIC STATE -> IDLE
This status should apply to all the corresponding circuits in the CAS trunk group (for example, 1 to 24).

At this point, the CAS trunk group circuits are ready to originate and receive calls.

Centrex Provisioning

The following two steps are mandatory for Centrex provisioning:

Step 1 Ensure that POTS access for the Centrex group is provisioned.

Step 2 Ensure that Call Agent provisioning of the digit-map has a digit-map for the emergency number (for example 911 for NANP).

MLHG provisioning is similar to subscriber provisioning as described above.

Emergency Callback

Use the following procedure to provision the Emergency Callback (ECB) feature.

Step 1 Add ECB to the feature table.
add feature fname=ECB; tdp1=TERMINATION_ATTEMPT_AUTHORIZED; tid1=ECB_TRIGGER; ttype1=R; 
description=Emergency Callback; feature_server_id=FSPTC235;
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.
add service id=499;fname9=ECB
Step 3 Provision the PSAP emergency list by specifying the PSAP line DN.
add emergency_number_list digit_string=2145551212
Hostage Negotiation LEA

You cannot provision a ported-out subscriber as a hostage subscriber on the BTS, although you can provision HN_OUTBOUND_DN and HN_FWD_DN as ported out numbers.

The Hostage Negotiation LEA feature is the highest-priority feature in the BTS unless you give an external feature in the FIM/XML file a higher priority. If you do that, the hostage negotiation feature will no longer work and the subscriber may be able to make regular outgoing calls and receive incoming calls.

Step 1 Add the hostage negotiation feature.
CLI> add feature fname=HN; tdp1=TERMINATION_ATTEMPT; tid1=HN_TRIGGER; ttype1=R; 
tdp2=COLLECTED_INFORMATION; tid2=HN_TRIGGER; ttype2=R; FEATURE_SERVER_ID=FSPTC235; 
GRP_FEATURE=N;
Step 2 Add the hostage negotiation feature service.
CLI> add service id=HN; fname1=HN;
Step 3 Add the hostage subscriber.
CLI> add subscriber-service-profile sub id=hostage; service-id=HN;
Step 4 Add hostage information.
CLI> add hostage-info sub-id=hostage; HN-OUTBOUND-DN=outbound_dn; HN-FWD-DN=Forwar_dn;     
HN-SCA-DN1=allowed_dn1....; HN-SCA-DN5=allowed_dn5;
In the sample script above, HN-SCA-DN1... represents an entry in the HN-SCA list.

Viewing Active Calls

This 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:
QUERY CALL-TRACE [MODE=<VERBOSE | BRIEF>] 
DN=<dn>
MLHG-ID=<mlhg-id> TERMINAL=<terminal>
CTXG-ID=<ctxg-id> EXT=<ext>
TGN-ID=<tgn-id> TRUNK-ID=<trunk-id>
SIP-CALL-ID=<sip-call-id>
H323-CALL-ID=<h323-call-id>
TERM=<term>
MGW=<mgw>
CLI examples

In the following example, the VERBOSE option is not shown (which defaults to BRIEF):
QUERY CALL-TRACE DN=4692551234 (for POTS/H323/SIP subscriber)
QUERY CALL_TRACE MHLG-ID=mlhg1 TERMINAL=23 (for POTS MLHG terminal)
QUERY CALL-TRACE CTXG-ID=ctxg1 EXT=1234 (for POTS centrex subscribers)
QUERY CALL-TRACE TGN-ID=123 TRUNK-ID=456 (for SS7 and ISDN trunks)
QUERY CALL-TRACE SIP-CALL-ID=<sip-call-id> (for SIP trunks) 
QUERY CALL-TRACE H323-CALL-ID=<h323-call-id> (for H323 trunks)
QUERY CALL-TRACE TERM=aaln/2@x1-6-00-00-ca-30-88-79.CTlab.cisco.com (termination with 
FQDN)
QUERY CALL-TRACE TERM=aaln/2@64.101.140.231 (termination with TSAP-ADDR)
QUERY CALL-TRACE MGW=x1-6-00-00-ca-30-88-79.CTlab.cisco.com (mgw FQDN)
QUERY CALL-TRACE MGW=64.101.140.231 (mgw TSAP-ADDRESS)
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.
ADD FEATURE-SERVER ID=3PTYFS24; TSAP-ADDR=192.168.100.103:11024; TYPE=3PTY;
EXTERNAL-FEATURE-SERVER=Y;
ADD FEATURE-SERVER ID=3PTYFS23; TSAP-ADDR=SPECIALFS.cisco.com; TYPE=3PTY;
EXTERNAL-FEATURE-SERVER=Y;
ADD FEATURE-SERVER ID=3PTYFS22; TSAP-ADDR=INTERNALFS.cisco.com; TYPE=3PTY;
EXTERNAL-FEATURE-SERVER=N;
Note The following rules apply:

•If the 3PTYFS is deployed in the private management network of the Cisco BTS 10200 Softswitch, you must set EXTERNAL-FEATURE-SERVER to N.

•If the 3PTYFS is deployed in a public network, you must set EXTERNAL-FEATURE-SERVER to Y.

•To set EXTERNAL-FEATURE-SERVER to Y, you must also set TYPE to 3PTY.

Step 2 Add Alerting Notification and the associated TDP and trigger ID:
ADD FEATURE FNAME=ALERT_NOTIFY; TDP1=CALL_ACCEPTED; TID1=CALL_ACCEPTED_NOTIFY; TTYPE1=N; 
FEATURE-SERVER-ID=3PTYFS24;
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;
Step 5 The commands in this step assign Alerting Notification to a specific subscriber.
ADD/CHANGE SERVICE ID=silverservice; FNAME1=CFU; FNAME2=CFB; FNAME3=CFNA; FNAME4=CW; 
FNAME5=ALERT_NOTIFY;
ADD SUBSCRIBER-SERVICE-PROFILE SUB-ID=Subscriber77; SERVICE-ID=silverservice;
Anonymous Call Rejection and A/D

Office Provisioning

Step 1 Create a feature for ACR_Activation:
add feature FNAME=ACR_ACT; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=ACR Activation; GRP_FEATURE=N;
Step 2 Create a feature for ACR_Deactivation:
add feature FNAME=ACR_DEACT; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=ACR Deactivation; GRP_FEATURE=N;
Step 3 Create a feature for ACR:
add feature FNAME=ACR; TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED; TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; 
DESCRIPTION=Anonymous Call Rejection; GRP_FEATURE=N;
Step 4 Create VSC codes in the VSC table:
add vsc DIGIT_STRING=*77; FNAME=ACR_ACT 
add vsc; DIGIT_STRING=*87; FNAME=ACR_DEACT;
Subscriber Provisioning

Step 1 Create a service with these features:
add service id=1; fname1=ACR; fname2=ACR_ACT; fname3=ACR_DEACT;
Step 2 Assign the service to the subscriber:
add subscriber-service-profile; sub-id=sub1; service-id=1; 
Centrex Provisioning

Step 1 Create an entry in the CDP table:
add cdp; id=cdp1; DIGIT_STRING=*77; NOD=VSC; FNAME=ACR_ACT; CAT_STRING=1111111111111111;
add cdp; id=cdp1; DIGIT_STRING=*87; NOD=VSC; FNAME=ACR_DEACT; CAT_STRING=1111111111111111;
MLHG provisioning is similar to subscriber provisioning, which is described above.

Alternate Activation and Deactivation Method

ACR 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 ACR:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=ACR;
Use a CLI command similar to the following to deactivate ACR:
add subscriber-feature-data sub-id=sub_1; active=N; fname=ACR;
Automatic Callback

Office Provisioning

Step 1 Create a feature for AC activation:
add feature fname=AC_ACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE; 
ttype1=R; description=AC activation; feature_server_id=FSPTC235;
Step 2 Create a feature for AC deactivation:
add feature fname=AC_DEACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE; 
ttype1=R; description=AC deactivation; feature_server_id=FSPTC235;
Step 3 Associate AC_ACT and AC_DEACT features with the AC feature:
add feature fname=AC; fname1=AC_ACT; fname2=AC_DEACT; feature_server_id=FSPTC235;
Step 4 Create VSC codes in the VSC table:
add vsc; DIGIT_STRING=*66; FNAME=AC_ACT;
add vsc; DIGIT_STRING=*86; FNAME=AC_DEACT;
Step 5 Create AC service with only the AC feature:
add service id=1; fname1=AC; 
Step 6 Ensure the Call-Agent table has a TSAP_ADDR populated:
change call-agent ID=CA416; STATUS=FORCED_STANDBY_ACTIVE; 
TSAP_ADDR_SIDEA=sim-SYS02CA.ipclab.cisco.com:9416; MGW_MONITORING_ENABLED=Y; 
CLLI=HERNVADTDS1;
Step 7 Ensure office-code has call-agent id provisioned:
change office-code DIGIT_STRING=703432; OFFICE_CODE_INDEX=14; DID=N; CALL_AGENT_ID=CA416; 
DIALABLE=Y; NDC=703; EC=432; DN_GROUP=xxxx;
Step 8 Verify if related ca-config parameters provide the desired configuration. If not, change parameters as required:
show ca-config TYPE=AC-ACTIVATION-LEVEL; DATATYPE=STRING; DEFAULT_VALUE=ONE;
show ca-config TYPE=ACAR-SLHR-ID; DATATYPE=STRING;
The ca-config values for the AR feature are common to the AC feature. Refer to the ca-config values for the AR feature.

Step 9 Add the feature to the default office service-id if it needs to be provided on an office basis.
change ca-config default-office-service-id=999;
Step 10 Assign the feature to the default office service id:
change service id=999; fname1=AC_ACT;
Provisioning Resources

Step 1 Provision the signaling gateway:
add/change sg id=sg_1; description=signaling gateway 1; 
Step 2 Provision the signaling gateway group:
add/change sg-grp id=sg_grp1; sg1-id=sg_1; description=signaling gateway group 1; 
Step 3 Provision the signaling gateway process:
add/change sgp id=itp_7507_1; sg-id=sg_1; description=ITP 7507 for sg_1; 
Step 4 Provision the SCTP association profile:
add sctp-assoc-profile id=sctp_prof; bundle_timeout=500; max_assoc_retrans=5; 
max_path_retrans=5; max_rto=6000; min_rto=301; sack_timeout=101; hb_timeout=1000; 
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 5 Provision the SCTP association:
add sctp-assoc id=sctp_assoc1; sgp-id=itp_7507_1; sctp-assoc-profile-id=sctp_prof; 
remote_port=14001; remote_tsap_addr1=10.89.232.9; remote_tsap_addr2=10.89.233.41; 
local_rcvwin=64000; max_init_retrans=5; max_init_rto=1000; platform_id=FSPTC235; 
Step 6 Add the DPC:
add dpc id=itp1; point-code=7-101-0; description=STP1, MGTS STP;
Step 7 Add the SCCP network:
add/change sccp-nw id=1; net-ind=NATIONAL; SUB_SVC=NATIONAL; HOP-Count=10;
Step 8 Add the subsystem profile:
add subsystem-profile id=SSN_ACAR; PLATFORM_ID=FSPTC235;
Step 9 Add the subsystem:
add subsystem id=SSN_ACAR; opc_id=opc; local-ssn=251; remote-ssn=251; sccp-nw-id=1; 
SCCP_VERSION=ANS92; TCAP_VERSION=ANS92; APPLICATION_VERSION=IN1; 
Step 10 Add the routing key:
add routing-key id=rk_acar; opc-id=opc; sg-grp-id=sg_grp; si=SCCP; rc=205; 
PLATFORM_ID=FSPTC235; ssn-id=SSN_ACAR;
Step 11 Add the SCCP route:
add sccp-route opc_id=opc; dpc_id=itp1; subsystem_grp_id=SSN_ACAR;
Step 12 Add the SLHR profile:
add slhr-profile id=slhr_acar;
Step 13 Add the Service Logic Host Route:
add slhr id=slhr_acar; opc_id=opc; dpc_id=itp1; subsystem_grp_id=SSN_ACAR; gtt-req=Y; 
tt=251; GTT_ADDR_TYPE=CDPN; GTT_ADDR=3;
Step 14 Add the ca-config type ACAR-SLHR-ID:
Add ca-config type=ACAR-SLHR-ID; datatype=string; value=slhr_acar;
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
Step 2 Customize the feature denied flag for the subscriber according to individual requirements:
change subscriber-feature-data sub-id=subscriber_1; fname=AC_ACT; type1=DENIED; value1=Y;
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:
add cdp id=cdp1; DIGIT_STRING=*66; NOD=VSC; FNAME=AC_ACT; CAT_STRING=1111111111111111;
add cdp id=cdp1; DIGIT_STRING=*86; NOD=VSC; FNAME=AC_DEACT; CAT_STRING=1111111111111111;
Provisioning Notes/Caveats

•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.

Automatic Recall

Office Provisioning

Step 1 Create a feature for AR Activation:
add feature fname=AR_ACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE; 
ttype1=R; description=AR activation; feature_server_id=FSPTC235;
Step 2 Create a feature for AR Deactivation:
add feature fname=AR_DEACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE; 
ttype1=R; description=AR deactivation; feature_server_id=FSPTC235;
Step 3 Create VSC codes in the VSC table:
add vsc DIGIT_STRING=*69; FNAME=AR_ACT
add vsc DIGIT_STRING=*89; FNAME=AR_DEACT
Step 4 Create a service with these features:
add service id=1; fname1=AR_ACT; fname2=AR_DEACT;
Step 5 Verify that AR related CA-Config table information is as desired. If not, change required parameters as desired:
show ca-config type=AR%
Reply : Success:  Entries 1-24 of 24 returned.
TYPE=AR-ACTIVATION-LEVEL
DATATYPE=STRING
VALUE=ONE
TYPE=ARAC-ACTIVATION-TO-COIN
DATATYPE=BOOLEAN
VALUE=N
TYPE=ARAC-ACTIVATION-TO-ANONYMOUS-DN
DATATYPE=BOOLEAN
VALUE=N
TYPE=ARAC-ACTIVATION-TO-MLHG
DATATYPE=BOOLEAN
VALUE=Y
TYPE=ARAC-ACTIVATION-TO-NON-UNIQUE-DN
DATATYPE=BOOLEAN
VALUE=N
TYPE=ARAC-INITIAL-QUERY-RESPONSE-TIMER-T5
DATATYPE=INTEGER
VALUE=3
TYPE=ARAC-INTER-BUSY-IDLE-QUERY-DURATION-TIMER-T11
DATATYPE=INTEGER
VALUE=95
TYPE=ARAC-MAX-6SEC-RINGING-CYCLES
DATATYPE=INTEGER
FROM_VALUE=2
TO_VALUE=5
VALUE=4
TYPE=ARAC-MAX-CONCURRENT-ATTEMPTS
DATATYPE=INTEGER
VALUE=30
TYPE=ARAC-MAX-QUEUE-SIZE
DATATYPE=INTEGER
FROM_VALUE=10
TO_VALUE=20
VALUE=15
TYPE=ARAC-MAX-UNANSWERED-RING-APPLICATIONS
DATATYPE=INTEGER
FROM_VALUE=1
TO_VALUE=12
VALUE=2
TYPE=ARAC-MONITORING-TIMER-T6
DATATYPE=INTEGER
VALUE=30
TYPE=ARAC-ORIGINATING-SCAN-RATE
DATATYPE=INTEGER
VALUE=60
TYPE=ARAC-OSPCS-OVERALL-MONITOR-TIMER-T10
DATATYPE=INTEGER
VALUE=3
TYPE=ARAC-OUTSTANDING-NOTIFICATION-TIMER-T8
DATATYPE=INTEGER
VALUE=35
TYPE=ARAC-PERIODIC-SCAN-RATE
DATATYPE=INTEGER
FROM_VALUE=5
TO_VALUE=30
VALUE=30
TYPE=ARAC-QUEUING-SUPPORTED
DATATYPE=BOOLEAN
VALUE=Y
TYPE=ARAC-RESUME-SCANNING-THRESHOLD-TIME
DATATYPE=INTEGER
VALUE=5
TYPE=ARAC-RESUME-SCANNING-TIMER-T2
DATATYPE=INTEGER
VALUE=5
TYPE=ARAC-SUB-QUERY-RESPONSE-TIMER-T9
DATATYPE=INTEGER
VALUE=3
TYPE=ARAC-TERMINATING-SCANNING-MONITOR-TIMER-T7
DATATYPE=INTEGER
VALUE=30
TYPE=ARAC-TERMINATING-SPCS-SCAN-ALLOW
DATATYPE=BOOLEAN
VALUE=Y
TYPE=ARAC-TSPCS-OVERALL-MONITOR-TIMER-T10
DATATYPE=INTEGER
VALUE=3
TYPE=ARAC-TTYPE
DATATYPE=INTEGER
FROM_VALUE=1
TO_VALUE=255
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; 
Step 4 Provision the SCTP association profile:
add sctp-assoc-profile id=sctp_prof; bundle_timeout=500; max_assoc_retrans=5; 
max_path_retrans=5; max_rto=6000; min_rto=301; sack_timeout=101; hb_timeout=1000; 
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 5 Provision the SCTP association:
add sctp-assoc id=sctp_assoc1; sgp-id=itp_7507_1; sctp-assoc-profile-id=sctp_prof; 
remote_port=14001; remote_tsap_addr1=10.89.232.9; remote_tsap_addr2=10.89.233.41; 
local_rcvwin=64000; max_init_retrans=5; max_init_rto=1000; platform_id=FSPTC235; 
Step 6 Add the DPC:
add dpc id=itp1; point-code=7-101-0; description=STP1, MGTS STP;
Step 7 Add the SCCP Network:
add sccp-nw id=1; net-ind=NATIONAL; SUB_SVC=NATIONAL; HOP-Count=10;
Step 8 Add the subsystem profile:
add subsystem-profile id=SSN_ACAR; PLATFORM_ID=FSPTC235; 
Step 9 Add the subsystem:
add subsystem id=SSN_ACAR; opc_id=opc; local-ssn=251; remote-ssn=251 sccp-nw-id=1; 
SCCP_VERSION=ANS92; TCAP_VERSION=ANS92; APPLICATION_VERSION=IN1; 
Step 10 Add the routing key:
add routing-key id=rk_acar; opc-id=opc; sg-grp-id=sg_grp; si=SCCP; rc=205; 
PLATFORM_ID=FSPTC235; ssn-id=SSN_ACAR; 
Step 11 Add the SCCP route:
add sccp-route opc_id=opc; dpc_id=itp1; subsystem_grp_id=SSN_ACAR;
Step 12 Add the SLHR profile:
add slhr-profile id=slhr_acar;
Step 13 Add the Service Logic Host Route:
add slhr id=slhr_acar; opc_id=opc; dpc_id=itp1;subsystem_grp_id=SSN_ACAR; gtt-req=Y; 
tt=251; GTT_ADDR_TYPE=CDPN; GTT_ADDR=3; 
Step 14 Add the ca-config type ACAR-SLHR-ID if not added before:
add ca-config type=ACAR-SLHR-ID; datatype=string; value=slhr_acar;
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
Step 2 Customize the feature denied flag for the subscriber as per the individual requirement:
change subscriber-feature-data sub-id=subscriber_1; fname=AR_ACT; type1=DENIED; value1=Y;
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:
add cdp; id=cdp1; DIGIT_STRING=*69; NOD=VSC; FNAME=AC_ACT; CAT_STRING=1111111111111111;
add cdp; id=cdp1; DIGIT_STRING=*89; NOD=VSC; FNAME=AC_DEACT; CAT_STRING=1111111111111111;
Provisioning Notes/Caveats

•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, :
add ca-config type=AR-ACTIVATION-LEVEL; datatype=string; value=TWO;
To apply at the POP basis:
add pop id=pop1; ar-activation-level=TWO; 
Step 2 Specify the AR two-level activation default Route-Guide to the IVR device.
add ca-config type=DEFAULT-IVR-ROUTE-GUIDE-ID; datatype=string; value=def_ivr_rg; 
Step 3 Add the AR two-level activation IVR-Script-Profile table:
add ivr-script-profile fname=AR_ACT; ivr-access-mode=IVR; ivr-route-guide-id=ar_ivr_rg; 
ivr-script-pkg-type=BAU;
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_ti
me,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_ba
ck_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_act_seq; language-id=def; seq=ar_activation_prompt; description=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_var_dn; type=variable; var-type=dig; var-subtype=ndn;
add audio-segment id=ar_voice_back_date; type=physical; url=file://ar_voice_back_date.wav; 
description=This call was received on
add audio-segment id=ar_var_date; type=variable; var-type=dat; var-subtype=mdy;
add audio-segment id=ar_voice_back_time; type=physical; url=file://ar_voice_back_time.wav; 
description=at
add audio-segment id=ar_var_time; type=variable; var-type=tme; var-subtype=t12;
add audio-segment id=ar_activation_prompt; type=physical; 
url=file://ar_activation_prompt.wav; description=To activate Automatic Recall, dial 1  
otherwise, hang up.
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:
change service id=999; fname1=BLV;
Step 3 Provision the feature in the office:
add feature fname=blv; tdp1=TERMINATION_ATTEMPT; tid1=BLV; ttype1=R; 
feature_server_id=fsptc235; description=Busy-line verification; grp_feature=N;
Provisioning Resources

Step 1 Set the BLV CAS trunk group profile as "no-test" type:
add cas-tg-profile id=cas_blv; no-test-trunk=y;
Step 2 Set the MGCP package type associated with the CAS trunk termination to "MT" type:
add termination id=S0/DS1-1/1; mgw-id=c2421.1001; mgcp-package-type=MT;
Note For normal MGCP 1.0 CAS trunks, mgcp-package-type=MS should be used.

Step 3 Set the Quality of Service parameter of the trunk group:
add trunk-grp id=152; qos-id=pcm;
Note For the BLV barge-in feature to work, the CAS trunk quality of service (QoS) and subscriber QoS (next step, below) should match.

Subscriber Provisioning

Step 1 Set the Quality of Service parameter for a specific subscriber in the subscriber's profile:
add subscriber-profile id=plano-sub-prof; qos-id=pcm;
Step 2 Set access permissions for line verification on a subscriber line:
add subscriber-feature-data sub-id=plano_sub1; fname=BLV; type1=DENIED; value1=N;
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.

•add feature-config fname=BLV; type=ALLOW-EMERGENCY-BARGE-IN; value=N;

•add feature-config fname=BLV; type=ALLOW-CCW-BARGE-IN; value=N;

•change feature-config fname=BLV; type=ALLOW-EMERGENCY-BARGE-IN;value=Y;

•change feature-config fname=BLV; type=ALLOW-CCW-BARGE-IN;value=Y;

•delete feature-config fname=BLV; type=ALLOW-EMERGENCY-BARGE-IN;

•delete feature-config fname=BLV; type=ALLOW-CCW-BARGE-IN;

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.

Call Block—Reject Caller

Office Provisioning

Step 1 Create a feature for CBLK:
add feature FNAME=CBLK; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Block - Reject Caller; GRP_FEATURE=N;
Step 2 Create VSC codes in the VSC table:
add vsc; DIGIT_STRING=*97; FNAME=CBLK; 
Subscriber Provisioning

Step 1 Create a service with this feature:
add service id=1; fname1=CBLK;
Step 2 Assign the service to the subscriber:
add/change subscriber-service-profile; sub-id=sub1; service-id=1; 
Centrex Provisioning

Step 1 Create an entry in the CDP table:
add/change cdp; id=cdp1; DIGIT_STRING=*97; NOD=VSC; FNAME=CBLK; 
CAT_STRING=1111111111111111;
MLHG Provisioning

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, for directions for provisioning SCR.

Block All Inbound Calls

If 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.
add subscriber id=sub_1; sub-profile-id=subprof_1; BILLING_DN=4692550260;
Step 2 Add dn2subscriber entry for the billing DN assigned to the subscriber, but point it to an announcement ID.
add dn2subscriber FDN=4692550260; status=ANNC; ANNC_ID=998;
Call Forward Busy

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.

Fresh Installation

Step 1 Create a feature for CFB-Activation:
add feature FNAME=CFBVA; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFB V Activation; GRP_FEATURE=N;
Step 2 Create a feature for CFB-Deactivation:
add feature FNAME=CFBVD; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC32; DESCRIPTION=CFB V Deactivation; GRP_FEATURE=N;
Step 3 Create a feature for CFB-Interrogation:
add feature FNAME=CFBI; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFB Interrogation; GRP_FEATURE=N;
Step 4 Create a feature for CFB (note that the T_NOT_REACHABLE trigger is added):
add feature fname=CFB; TDP1=T_BUSY; TID1=T_BUSY; TTYPE1=R; TDP2=T_EXCEPTION; 
TID2=T_NOT_REACHABLE; TTYPE2=R; FNAME1=CFBVA; FNAME2=CFBVD; FNAME3=CFBI; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Forwarding Busy; GRP_FEATURE=N;
Step 5 Add a VSC code for CFB-A:
add/change vsc fname=CFBVA; digit-string=*40;
Step 6 Add a VSC code for CFB-D:
add vsc fname=CFBVD; digit-string=#40#;
Step 7 Add a VSC code for CFB-I:
add vsc fname=CFBI; digit-string=*#40;
Step 8 Add a service with these features:
add service id=1; FNAME1=CFB; FNAME2=CFBVA; FNAME3=CFBVD; FNAME4=CFBI;
Step 9 Customize the multiple call forwarding capability as required:
change feature fname=CFB; TYPE1=MCF; VALUE1=Y;
Step 10 Customize for International Call Forwarding as required. This should be applied to CFB and CFBVA:
change feature fname=CFB; TYPE1=INTL; VALUE1=Y;
change feature fname=CFBVA; TYPE1=INTL; VALUE1=Y;
Step 11 Customize for the second stage dial-tone (O):
change feature fname=CFBVA/CFBI; TYPE2=SDT; VALUE2=STUTTER-DIAL-TONE;
Step 12 Customize for the courtesy call. Accepted values: ANS, NOANS, N (O):
change feature fname=CFBVA; TYPE3=CC; VALUE3=ANS;
Step 13 Customize for the final-stage dial-tone:
change feature fname=CFBVA/CFBVD/CFBI; TYPE4=FDT; VALUE4=DIAL-TONE;
Step 14 Add the applicable NODs to be restricted for the CFB feature:
add nod-restrict-list fname=CFB; nod=EMG;
add nod-restrict-list fname=CFB; nod=FIRE;
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:
add mgw-profile id=MTA_00777 keepalive-method=NONE;
Step 16 Add a MGW and reference the applicable mgw-profile:
add mgw id=mta12345; call-agent-id=CA146; mgw-profile-id=MTA_00777; 
tsap-addr=mta12345.cisco.com:1819; type=rgw;
Upgrade or Changes to Database

Step 1 Change the CFB feature to add the T_NOT_REACHABLE trigger:
change feature TDP1=T_BUSY; TID1=T_BUSY; TTYPE1=R; TDP2=T_EXCEPTION; TID2=T_NOT_REACHABLE; 
TTYPE2=R; FNAME1=CFBVA; FNAME2=CFBVD; FNAME3=CFBI; FEATURE_SERVER_ID=FSPTC235; 
DESCRIPTION=Call Forwarding Busy; GRP_FEATURE=N;
Step 2 Use the change service command to refresh the service that contains the CFB feature:
change service id=1; FNAME1=CFB; FNAME2=CFBVA; FNAME3=CFBVD; FNAME4=CFBI;
Step 3 If you have decided to turn off MGW monitoring for a particular MGW, enter the following command:
change mgw-profile id=MTA_00777 keepalive-method=NONE;
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
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 steps are required.

Step 1 Add a feature into the custom-dial-plan table for the Centrex group:
add/change custom-dial-plan ID=cdp1; DIGIT-STRING=*40; NOD=VSC; FNAME=CFBVA; 
CAT-STRING=1111111111111111;
add custom-dial-plan ID=cdp1; DIGIT-STRING=#40#; NOD=VSC; FNAME=CFBVD; 
CAT-STRING=1111111111111111;
add custom-dial-plan ID=cdp1; DIGIT-STRING=*#40; NOD=VSC; FNAME=CFBI; 
CAT-STRING=1111111111111111;
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. 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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CFB; type1=FDN1;
value1=4692551001;
Note The value should be the forwarding-to DN.

Use a CLI command similar to the following to deactivate CFB:
add subscriber-feature-data sub-id=sub_1; active=N; fname=CFB;
Call Forwarding Combination

Office Provisioning

Step 1 Create a feature for CFC_ACT:
add/change feature FNAME=CFC_ACT; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC325;
Step 2 Create a feature for CFC_DEACT:
add/change feature FNAME=CFC_DEACT; TDP1=COLLECTED_INFORMATION; 
TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; FEATURE_SERVER_ID=FSPTC325;
Step 3 Create a feature for CFC_DN_CHG_ACT:
add/change feature FNAME=CFC_DN_CHG_ACT; TDP1=COLLECTED_INFORMATION; 
TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; FEATURE_SERVER_ID=FSPTC325;
Step 4 Create a feature for CFCI_NO_DN_VRFY:
add/change feature FNAME=CFCI_NO_DN_VRFY; TDP1=COLLECTED_INFORMATION; 
TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; FEATURE_SERVER_ID=FSPTC325;
Step 5 Create a feature for CFCI:
add/change feature FNAME=CFCI; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC325;
Step 6 Create a feature for CFC:
add/change feature FNAME=CFC; TDP1=T_BUSY; TID1=T_BUSY; TTYPE1=R; TDP2=CALL_ACCEPTED; 
TID2=CALL_ACCEPTED; TTYPE2=R; FEATURE_SERVER_ID=FSPTC325;TYPE1=TO; VALUE1=30; TYPE2=MCF; 
VALUE2=Y;
Step 7 Define VSC codes for these features:
add/change vsc; fname=CFC_ACT; DIGIT_STRING=*68;
add/change vsc; fname=CFC_DEACT; DIGIT_STRING=*88;
add/change vsc; fname=CFC_DN_CHG_ACT; DIGIT_STRING=*201;
add/change vsc; fname=CFCI_NO_DN_VRFY; DIGIT_STRING=*202
add/change vsc; fname=CFCI; DIGIT_STRING=*203
Step 8 Customize the FDT and SDT flags for these features, if necessary:
change feature; fname=CFC_ACT; TYPE1=FDT; VALUE1=STUTTER_DIAL_TONE;
change feature; fname=CFC_DEACT; TYPE1=FDT; VALUE1=STUTTER_DIAL_TONE;
change feature; fname=CFC_DN_CHG_ACT; TYPE1=FDT; VALUE1=DIAL_TONE; 
TYPE2=FDT;VALUE2=STUTTER_DIAL_TONE;
Step 9 Combine the features defined above into a service:
add/change service id=cfc_dn_chg; FNAME1=CFC_DN_CHG_ACT; FNAME2=CFC_DEACT; FNAME3=CFC; 
FNAME4=CFCI_NO_DN_VRFY; FNAME5=CFCI; add/change service id=cfc; FNAME1=CFC_ ACT; 
FNAME2=CFC_DEACT; FNAME3=CFC; FNAME4=CFCI_NO_DN_VRFY;
Provisioning Resources

None.

Subscriber Provisioning

Step 1 Assign the service a subscriber:
add/change sub-service-profile; sub-id=[sub]; service-id=cfc_dn_chg;
add/change sub-service-profile; sub-id=[sub]; service-id=cfc;
Step 2 Set the FDN, if required:
add/change sub-feature-data; sub-id=sub1; fname=CFC; TYPE1=FDN1; VALUE1=<fdn>;
Centrex Provisioning

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:
add/change cdp; fname=CFC_ACT; DIGIT_STRING=*68; nod=VSC; CAT_STRING=1111111111111111;
add/change cdp; fname=CFC_DEACT; DIGIT_STRING=*88; nod=VSC; CAT_STRING=1111111111111111;
add/change cdp; fname=CFC_DN_CHG_ACT; DIGIT_STRING=*201; nod=VSC; 
CAT_STRING=1111111111111111; 
add/change cdp; fname=CFCI_NO_DN_VRFY; DIGIT_STRING=*202; nod=VSC; 
CAT_STRING=1111111111111111;
add/change cdp; fname=CFCI; DIGIT_STRING=*203; nod=VSC; CAT_STRING=1111111111111111;
MLHG Provisioning

MLHG provisioning is similar to subscriber provisioning.

Provisioning Notes/Caveats

While provisioning CFC, 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=CFC; TYPE1=TO; VALUE1=N;

•The following can be used to activate the feature or change the forwarding-dn for subscriber sub_1 via CLI -

add/change sub-feature-data; sub-id=sub_1; ACTIVE=Y; FNAME=CFC; TYPE1=FDN1; VALUE1=DN

•See effect of changing SDT above for SIP phones

•See effect of changing FDT above for SIP phones

Alternate Way to Activate and Deactivate CFC

Step 1 Activate CFC for a subscriber and modify the forwarding number:
add/change sub-feature-data; sub-id=sub1; fname=CFC; ACTIVE=Y; TYPE1=FDN1; VALUE1=<fdn>;
Step 2 Activate CFC for a subscriber and do not modify the forwarding number:
add/change sub-feature-data; sub-id=sub1; fname=CFC; ACTIVE=Y;
Step 3 Deactivate CFC for a subscriber:
add/change sub-feature-data; sub-id=sub1; fname=CFC; ACTIVE=N;
Call Forward No Answer

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.

Office Provisioning

Step 1 Create a feature for CFNA-Activation:
add feature FNAME=CFNAVA; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFNA Activation; GRP_FEATURE=N;
Step 2 Create a feature for CFNA-Deactivation:
add feature FNAME=CFNAVD; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFNA Deactivation; GRP_FEATURE=N;
Step 3 Create a feature for CFNA-Interrogation:
add feature FNAME=CFNAI; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFNA Interrogation; GRP_FEATURE=N;
Step 4 Create a feature for CFNA:
add feature FNAME=CFNA; TDP1=CALL_ACCEPTED; TID1=CALL_ACCEPTED; TTYPE1=R; FNAME1=CFNAVA; 
FNAME2=CFNAVD; FNAME3=CFNAI; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Forwarding No 
Answer; GRP_FEATURE=N;
Step 5 Add/change the VSC code for CFNA-A:
add/change vsc fname=CFNAVA; digit-string=*72;
Step 6 Add/change the VSC code for CFNA-D:
add/change vsc fname=CFNAVD; digit-string=#72#;
Step 7 Add/change the VSC code for CFNA-I:
add/change vsc fname=CFNAI; digit-string=*#72;
Step 8 Add the service with these features:
add service id=1; FNAME1=CFNA; 
Step 9 If required, change the default no-answer timeout value:
change feature fname=CFNA; TYPE1=TO; VALUE1=45;
Step 10 Customize for International Call Forwarding as required. It should be applied to CFNA and CFNAVA:
change feature fname=CFNA; TYPE1=INTL; VALUE1=Y;
change feature fname=CFNAVA; TYPE1=INTL; VALUE1=Y;
Step 11 Customize for the second stage dial-tone:
change feature fname=CFNAVA/CFNAI; TYPE2=SDT; VALUE2=STUTTER-DIAL-TONE;
Step 12 Customize for the final-stage dial-tone:
change feature fname=CFNAVA/CFNAVD/CFNAI; TYPE4=FDT; VALUE4=DIAL-TONE;
Step 13 Customize the multiple call forwarding capability as required:
change feature fname=CFNVA; TYPE1=MCF; VALUE1=Y;
Step 14 Customize for courtesy call. Possible values: ANS, NOANS, N:
change feature fname=CFNAVA; TYPE3=CC; VALUE3=N;
Step 15 Add the applicable NODs to be restricted for the CFNA feature:
add nod-restrict-list fname=CFNA; nod=EMG;
add nod-restrict-list fname=CFNA; nod=FIRE;
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.

Subscriber Provisioning

Step 1 Assign the service to the subscriber(M):
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
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 steps are required.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
add/change  custom-dial-plan ID=cdp1;DIGIT-STRING=*72; NOD=VSC;FNAME=CFNAVA; 
CAT-STRING=1111111111111111;
add/change  custom-dial-plan ID=cdp1;DIGIT-STRING=*73; NOD=VSC;FNAME=CFNAVD; 
CAT-STRING=1111111111111111;
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:
add/change sub-feature-data sub-id=sub_1; ACTIVE=Y; FNAME=CFNA; TYPE1=FDN1; VALUE1=DN;
•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. 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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CFNA; type1=FDN1;
value1=4692551001;
Note The value should be the forwarding-to DN.

Use a CLI command similar to the following to deactivate CFNA:
add subscriber-feature-data sub-id=sub_1; active=N; fname=CFNA;
Call Forward Redirection

Step 1 Add CFR.
add/change feature_name fname=CFR; description=call forward redirection;
add/change feature FNAME=CFR; TDP1= T_EXCEPTION; TID1= CFR_TRIGGER; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC325; DESCRIPTION=call forward redirection; GRP_FEATURE=N
Step 2 Assign CFR to service and trunk groups:
add service; id=cfr; fname1=CFR; 
change trunk-grp-service-profile; tgn-id=<SIP trunk group id>; service-id=cfr;
Step 3 Allow CFR routing on SIP trunks:
change softsw-tg-profile id=10; protocol-type=SIP; redirect_supported= VALID_DOMAINS_ONLY;
Step 4 Update call forwarding features to allow 302:
change feature_config FNAME=CFNA; TYPE= SIP_302_SUPP; DATATYPE =STRING; VALUE=Y; 
change feature_config FNAME=CFC; TYPE= SIP_302_SUPP; DATATYPE =STRING; VALUE=NOANSWER
change feature_config FNAME=VM; TYPE= SIP_302_SUPP; DATATYPE =STRING; VALUE=NOANSWER
Step 5 Update outgoing SIP trunks to allow 302:
change softsw_tg_profile ID=tb11_sip_1; send-302-on-cf=Y
Call Forwarding Unconditional

Office Provisioning

Step 1 Create a feature for CFU-Activation:
add feature FNAME=CFUA; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFU Activation; GRP_FEATURE=N;
Step 2 Create a feature for CFU-Deactivation:
add feature FNAME=CFUD; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFU Deactivation; GRP_FEATURE=N;
Step 3 Create a feature for CFU-Interrogation:
add feature FNAME=CFUI; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFU Interrogation; GRP_FEATURE=N;
Step 4 Create a feature for CFU:
add feature FNAME=CFU; TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED; TTYPE1=R; FNAME1=CFUA; FNAME2=CFUD; FNAME3=CFUI; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFU; MCF=multiple call forwarding allowed; 
GRP_FEATURE=N;
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:
change feature fname=CFU; TYPE1=INTL; VALUE1=Y;
change feature fname=CFUA; TYPE1=INTL; VALUE1=Y;
Step 12 Customize the second stage dial-tone:
change feature fname=[CFUA|CFUI]; TYPE2=SDT; VALUE2=STUTTER-DIAL-TONE;
Step 13 Customize the courtesy call. Possible values: ANS, NOANS, N:
change feature fname=CFUA; TYPE3=CC; VALUE3=ANS;
Step 14 Customize the final-stage dial-tone:
change feature fname=[CFUA|CFUD|CFUI]; TYPE4=FDT; VALUE4=DIAL-TONE;
Step 15 Add the applicable NODs to be restricted for the CFU feature:
add nod-restrict-list fname=CFU; nod=EMG;
add nod-restrict-list fname=CFU; nod=FIRE;
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.

Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
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 is required.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
add/change  custom-dial-plan ID=cdp1;DIGIT-STRING=*72; NOD=VSC;FNAME=CFUA; 
CAT-STRING=1111111111111111;
add/change  custom-dial-plan ID=cdp1;DIGIT-STRING=#72#; NOD=VSC;FNAME=CFUD; 
CAT-STRING=1111111111111111;
add/change  custom-dial-plan ID=cdp1;DIGIT-STRING=*#72; NOD=VSC;FNAME=CFUI; 
CAT-STRING=1111111111111111;
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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CFU; type1=FDN1;
value1=4692551001;
Note The value should be the forwarding-to DN.

Use a CLI command similar to the following to deactivate CFU:
add subscriber-feature-data sub-id=sub_1; active=N; fname=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.

Office Provisioning

Step 1 Create a feature for CFVABBG-Activation:
add feature FNAME=CFVABBG; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFVBBG - activation; 
GRP_FEATURE=N;
Step 2 Create a feature for CFVBBG:
add feature FNAME=CFVBBG; FNAME1=CFVABBG; FNAME2=CFUD; FNAME3=CFUI; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CFV BBG; GRP_FEATURE=N;
Step 3 Add a service with these features:
add service id=1; FNAME1=CFVBBG;
Step 4 (Optional) Customize the reminder ring capability as required:
change feature fname=CFVBBG; type1=RR; value1=N;
Step 5 (Optional) Customize the multiple call forwarding capability as required:
change feature fname=CFVBBG; TYPE1=MCF; VALUE1=Y; 
Step 6 (Optional) Customize for International Call Forwarding as required.
This should be applied to CFU and CFUA:
change feature fname=CFVBBG; TYPE1=INTL; VALUE1=Y;
change feature fname=CFVABBG; TYPE1=INTL; VALUE1=Y;
Step 7 (Optional) Customize for the second stage dial-tone:
change feature fname=CFVABBG; TYPE2=SDT; VALUE2=STUTTER-DIAL-TONE;
Step 8 (Optional) Customize for the courtesy call:
change feature fname=CFVABBG; TYPE3=CC; VALUE3=N;
Step 9 (Optional) Customize for the final-stage dial-tone:
change feature fname=CFVABBG; TYPE4=FDT; VALUE4=DIAL-TONE;
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
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 is required.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
add/change custom-dial-plan ID=cdp1; DIGIT-STRING=*99; NOD=VSC; FNAME=CFVABBG; 
CAT-STRING=1111111111111111;
Note This is a randomly chosen digit-string.

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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CFU; type1=FDN1;
value1=4692551001;
Note The value should be the forwarding-to DN.

Use a CLI command similar to the following to deactivate CFVBBG:
add subscriber-feature-data sub-id=sub_1; active=N; fname=CFU;
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.

Office Provisioning

Step 1 Create a feature for CHD:
add feature fname=CHD; tdp1=O_MID_CALL; tdp2=T_MID_CALL;  
tid1=O_SWITCH_HOOK_FLASH_IMMEDIATE; tid2=T_SWITCH_HOOK_FLASH_IMMEDIATE; ttype1=R; 
ttype2=R; description=Call Hold; feature_server_id=FSPTC235;
Step 2 Add a service with these features:
add service id=1; fname1=CHD; description=For some Centrex subscribers;
Subscriber Provisioning

The CHD feature is applicable only to a Centrex group.

Centrex Provisioning

For the CHD feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires the following steps:

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1;
Step 2 Add the feature into the custom-dial-plan table for the Centrex group:
add custom-dial-plan ID=cdp1; DIGIT-STRING=*52; NOD=VSC; FNAME=CHD; 
CAT-STRING=1111111111111111;
MLHG provisioning is similar to Centrex provisioning as described above.

Call Park, Call Park Retrieve

Office Provisioning

Step 1 Create a feature for CPRK:
add feature FNAME=CPRK; TDP1=O_MID_CALL; TID1=O_SWITCH_HOOK_FLASH_IMMEDIATE; TTYPE1=R; 
TDP2=T_MID_CALL; TID2=T_SWITCH_HOOK_FLASH_IMMEDIATE; TTYPE2=R; FEATURE_SERVER_ID=FSPTC235; 
DESCRIPTION=Call Park; GRP_FEATURE=N;
Step 2 Create a feature for CPRK_RET:
add feature FNAME=CPRK_RET; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Park Retrieve; 
GRP_FEATURE=N;
Step 3 Add a VSC code in the CDP table:
add cdp id=cdp1; DIGIT_STRING=*58; NOD=VSC; FNAME=CPRK; CAT_STRING=1111111111111111;
Step 4 Add a VSC code in the CDP table:
add cdp id=cdp1; DIGIT_STRING=*59; NOD=VSC; FNAME=CPRK_RET; CAT_STRING=1111111111111111;
Step 5 Create the CPSG table:
add cpsg ID=cpsg1; TCPRK=30; CTXG_ID=ctxg1; CPRK_FDN=414;
Note cpsg1 is the Call Park Subscriber Group id
TCPRK is the Timed Recall (Re-offer) Timer
CPRK_FDN is the Forward-To DN, in case all the re-offers are exhausted

Step 6 Add entries to the Ca-config table:
add ca-config TYPE=CPRK_ANN; DATATYPE=INTEGER; VALUE=901;
add ca-config TYPE=CPRK_CLEAR; DATATYPE=INTEGER; VALUE=902; 
Step 7 Configure Ca-config defaults as required:
add ca-config; TYPE=CPRK-TIMER; DATATYPE=INTEGER; VALUE=60;
add ca-config; TYPE=CPRK-HC-T1; DATATYPE=INTEGER; VALUE=24;
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:
add annc ID=901; TYPE=SYSTEM; SEND_ANSWER=N; NUM_REPEAT=1; DURATION=20; 
ANNOUNCEMENT_FILE=ann_id_901.au; ROUTE_GUIDE_ID=annc1; ANNOUNCEMENT_NUMBER=323;
add annc ID=902; TYPE=SYSTEM; SEND_ANSWER=N; NUM_REPEAT=1; DURATION=20; 
ANNOUNCEMENT_FILE=ann_id_902.au; ROUTE_DE_ID=annc1; ANNOUNCEMENT_NUMBER=323;
Subscriber Provisioning

Step 1 Create a service with these features:
add service id=1; fname1=CPRK; fname2=CPRK_RET;
Step 2 Assign the service to the subscriber:
add/change subscriber-service-profile sub-id=sub1; service-id=1; 
Step 3 Associate the subscriber to a CPSG:
change ext2subscriber CTXG_ID=CTXgroup1; EXT=412; SUB_ID=sub1; CPSG_ID=cpsg1;
The feature is only available for a Centrex group. Refer to above provisioning.

Provisioning Notes/Caveats

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 Transfer

Office Provisioning

Step 1 Provision the feature table:
add/change feature FNAME=CT; TDP1=O_MID_CALL; TID1=O_SWITCH_HOOK_FLASH_IMMEDIATE; 
TTYPE1=R; TDP2=T_MID_CALL; TID2=T_SWITCH_HOOK_FLASH_IMMEDIATE; TTYPE2=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Transfer Feature;
Step 2 Provision the service table:
add service id=2; FNAME1=CT;
Subscriber Provisioning

Step 1 Provision the subscriber-service-profile:
add subscriber-service-profile sub_id=sub-1; service-id=2;
Centrex and MLHG provisioning is similar to subscriber provisioning.

Call Waiting

Office Provisioning

Step 1 Create a feature for CW-Activation:
add feature fname=CW; tdp1=T_BUSY; tid1=T_BUSY; ttype1=R; description=Call Waiting;  
feature_server_id=FSPTC235;
add feature FNAME=CWDA; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Waiting Activation Feature;
add/change feature FNAME=CWDD; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Call Waiting-Deactivation Feature;
Step 2 Add a service with these features:
add service id=1; FNAME1=CW; 
Subscriber Provisioning

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.

For the CW feature, in addition to basic Centrex office provisioning, the Centrex subscriber requires similar provisioning as a POTS subscriber.

The CW feature is not applicable for subscriber category MLHG.

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1;
Alternate Activation and Deactivation Method

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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CW;
Use a CLI command similar to the following to deactivate CW:
add subscriber-feature-data sub-id=sub_1; active=N; fname=CW;
Call Waiting Deluxe

Office Provisioning

Step 1 Provision the Feature table:
add/change feature FNAME=CWD; TDP1=T_BUSY; TID1=T_BUSY; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=China Residential Call Waiting Deluxe Feature;
add/change feature FNAME=CWDA; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=China Residential Call Waiting Deluxe 
Activation Feature;
add/change feature FNAME=CWDD; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=China Residential Call Waiting Deluxe 
Deactivation Feature;
add/change feature FNAME=CWDI; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=China Residential Call Waiting Deluxe 
Interrogation Feature;
Step 2 Provision the Service table:
add service id=1; FNAME1=CWD; FNAME2=CWDA; FNAME3=CWDD; FNAME4=CWDI;
Step 3 Provision the VSC table:
add vsc FNAME=CWDI; DIGIT-STRING=*56;
add vsc FNAME=CWDA; DIGIT-STRING=*58;
add vsc FNAME=CWDD; DIGIT-STRING=*59;
Step 4 (Optional) Customize the call-waiting indication timeout period (in seconds):
change feature fname=CWD; type1=TO; value1=25;
Step 5 (Optional) Customize the RECONNECT-TMR used to time when controlling party goes on-hook but there is at least one party on hold:
change ca-config type=RECONNECT-TMR; datatype=INTEGER; value=20;
Step 6 (Optional) Customize the FEATURE-RECONNECT-TMR when invalid/timeout user-interaction:
change ca-config type=FEATURE-RECONNECT-TMR; datatype=INTEGER; value=20;
Subscriber Provisioning

Step 1 Provision the subscriber-service-profile:
add subscriber-service-profile sub_id=sub_1; service-id=1;
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 performed.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
add custom-dial-plan ID=cdp1; DIGIT-STRING=*58*; NOD=VSC; FNAME=CWDA; 
CAT-STRING=1111111111111111;
add custom-dial-plan ID=cdp1; DIGIT-STRING=#58#; NOD=VSC; FNAME=CWDD; 
CAT-STRING=1111111111111111;
add custom-dial-plan ID=cdp1; DIGIT-STRING=*#58*; NOD=VSC; FNAME=CWDI; 
CAT-STRING=1111111111111111;
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. 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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CWD;
Use a CLI command similar to the following to deactivate CWD:
add subscriber-feature-data sub-id=sub_1; active=N; fname=CWD;
Caller ID with Call Waiting

Office Provisioning

Step 1 Create a feature for CW-Activation:
add feature fname=CIDCW; tdp1=T_BUSY; tid1=T_BUSY; ttype1=R; description=Caller Id with 
Call Waiting; feature_server_id=FSPTC235;
Step 2 Add a service with these features:
add service id=1; FNAME1=CIDCW;
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
Centrex Provisioning

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.

Use a CLI command similar to the following to activate CIDCW:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=CIDCW;
Use a CLI command similar to the following to deactivate CIDCW:
add subscriber-feature-data sub-id=sub_1; active=N; fname=CIDCW;
Caller Name Blocking

The following subsections identify necessary steps for the Caller Name Blocking (CNAB) feature to be offered.

Note The CNAB feature is not supported over SIP trunks.

Office Provisioning

Step 1 Create a feature for CNAB:
add/change feature FNAME=CNAB; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CNAB;
Step 2 Add a VSC code for CNAB:
add vsc fname=CNAB; digit-string=*95;
Step 3 Add a service with the feature:
add service id=1; FNAME1=CNAB; 
Step 4 Enable (or set as required) the LIDB query flag for Softswitch POPs.
change pop id=1; cnam_option=LOCAL_OR_LIDB;
Subscriber Provisioning

Step 1 Assign the service to the subscriber
add subscriber-service-profile sub_id=subscriber_1; service-id=1;
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 is required.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
add custom-dial-plan ID=cdp1; DIGIT-STRING=*95; NOD=VSC; FNAME=CNAB; 
CAT-STRING=1111111111111111;
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.

Calling Name Delivery

Office Provisioning

Step 1 Create a feature for CNAM:
add/change feature FNAME=CNAM; TDP1=FACILITY_SELECTED_AND_AVAILABLE; 
TD1=TERMINATION_RESOURCE_AVAILABLE; TTYPE1=R; FEATURE_SERVER_ID=FSPTC325; 
DESCRIPTION=CNAM;
Step 2 Add service:
add service service-id=1; FNAME1=CNAM;
Provisioning Resources

Step 1 Provision a signaling gateway:
add/change sg id=sg_1; description=signaling gateway 1;
Step 2 Provision a signaling gateway group:
add/change sg/grp id=sg_grp1; sg1-id=sg_1; description=signaling gateway group 1;
Step 3 Provision the signaling gateway process:
add/change sgp id=itp_7507_1; sg-id=sg_1; description=ITP 7507 for sg_1;
Step 4 Provision the SCTP association profile:
add/change sctp-assoc-profile id=sctp_prof; bundle_timeout=500;
max_assoc_retrans=5
max_path_retrans=5
max_rto=6000; min_rto=301;
sack_timeout=101;
hb_timeout=1000;
Step 5 Provision the SCTP associations:
add change sctp-assoc id=sctp_assoc1;
sgp-id=itp_7507_1;
sctp-assoc-profile-id=sctp_prof;
remote_port=14001;
remote_tsap_addr1=10.89.232.9;
remote_tsap_addr2=10.89.233.41;
local_revwin=64000;
max_init_retrans=5;
max_init_rto=1000;
platform_id=FSPTC235;
Step 6 Add DPC
add dpc id=stp1;
point-code=1-101-0;
description=STP1, MGTS STP;
Step 7 Add SCCP network:
add/change sccp-nw id=1; net=ind=NATIONAL; SUB_SVC=NATIONAL; HOP-Count=10;
Step 8 Add subsystem group:
add subsystem-grp id=SSN_CNAM; PLATFORM_ID=FSPTC235; TCAP_VERSION=ANS92;
Step 9 Add subsystem:
add subsystem id=SSN_CNAM; opc_id=opc; local-ssn=232; remote-ssn=232; sccp-nw-id=1; 
SCCP_VERSION=ANS92; APPLICATION_VERSION=IN1;
Step 10 Add routing key:
add routing-key id=rk_cnam; opc-id-opc; sg-grp-id=sg_grp; si=SCCP; rc=204; 
PLATFORM_ID=FSPTC235; ssn-id=SSN_CNAM;
Step 11 Add SCCP route:
add sccp-route opc_id=opc; dpc_id=stp1; subsystem_grp_id=SSN_CNAM; 
Step 12 Add service logic host route (SLHR) profile:
add slhr-profile id=slhr_cnam;
Step 13 Add SLHR:
add slhr id=slhr_cnam; opc_id=opc; dpc_id=stp1; subsystem_grp_id=232; gtt-req=1; tt=5; 
GTT_ADDR_TYPE=CLGN; GTT_ADDR=3;
Step 14 Add ca-config type:
Add ca-config type=DEFAULT-LIDB-SLHR-ID; type=string; value=slhr_cnam;
Step 15 Place SCTP association in-service (INS):
control sctp-assoc id=sctp_assoc1; mode=FORCED; target-state=INS;
Step 16 Place the subsystem group INS:
control subsystem-grp id=SSN_CNAM; mode=FORCED; target-state=INS;
Subscriber Provisioning

Step 1 Assign the CNAM service to the subscriber:
add subscriber-service-profile sub_id-subscriber_1; service-id=1
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:
change ISDN-dchan-profile id=rudp_dchan; FACIL_IE_SUPP=Y;
Centrex Provisioning

Centrex provisioning for the CNAM feature is similar to a POTS subscriber.

MLHG Provisioning

MLHG provisioning for the CNAM feature is similar to subscriber provisioning.

Calling Number Delivery

Office Provisioning

Step 1 Create a feature for CND:
add feature FNAME=CND; TDP1=FACILITY_SELECTED_AND_AVAILABLE; 
TID1=TERMINATION_RESOURCE_AVAILABLE; TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; 
DESCRIPTION=CND; 
Step 2 Add a service with the feature:
add service id=1; FNAME1=CND; 
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
Centrex Provisioning

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.

Calling Number Delivery Blocking

Office Provisioning

Step 1 Create a feature for CNDB:
add feature FNAME=CNDB; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CNDB; 
Step 2 Add a VSC code for CNDB:
add vsc fname=CNDB; digit-string=*67;
Step 3 Add a service with the feature:
add service id=1; FNAME1=CNDB; 
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
Centrex Provisioning

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:

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
Add custom-dial-plan ID=cdp1; DIGIT-STRING=*67; NOD=VSC; FNAME=CNDB; 
CAT-STRING=1111111111111111;
MLHG provisioning is similar to subscriber provisioning as described above.

Caller Identity Delivery Suppression-Delivery

Office Provisioning

Step 1 Create a feature for CIDSD:
add feature FNAME=CIDSD; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE;  
TTYPE1=R;  FEATURE_SERVER_ID=FSPTC235;  DESCRIPTION=CIDSD;
Step 2 Add a VSC code for CIDSD:
add vsc fname=CIDSD; digit-string=*82;
Step 3 Add a service with the feature:
add service id=1; FNAME1=CIDSD; 
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
Centrex Provisioning

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:
Add custom-dial-plan  ID=cdp1; DIGIT-STRING=*82; NOD=VSC; FNAME=CIDSD;  
CAT-STRING=1111111111111111;
MLHG provisioning is similar to subscriber provisioning as described above.

Caller Identity Delivery Suppression-Suppression

Office Provisioning

Step 1 Create a feature for CIDSS:
add feature FNAME=CIDSS; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE;  
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CIDSS;
Step 2 Add a VSC code for CIDSS:
add vsc fname=CIDSS; digit-string=*96;
Step 3 Add a service with the feature:
add service id=1; FNAME1=CIDSS; 
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
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 performed.

Step 1 Add the feature into the Custom-dial-plan table for the Centrex group:
Add custom-dial-plan ID=cdp1; DIGIT-STRING=*96;  NOD=VSC; FNAME=CIDSS;  
CAT-STRING=1111111111111111;
MLHG provisioning is similar to subscriber provisioning as described above.

Cancel Call Waiting

Office Provisioning

Step 1 Create the feature:
add feature FNAME=CCW; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; TTYPE1=R; 
TDP2=O_MID_CALL; TID2=O_SWITCH_HOOK_FLASH_IMMEDIATE; TTYPE2=R; TDP3=T_MID_CALL; 
TID3=T_SWITCH_HOOK_FLASH_IMMEDIATE; TTYPE3=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=CCW;
Step 2 Add a VSC code:
add vsc fname=CCW;  digit-string=*70;
Step 3 Add the service with the feature:
add service id=1; FNAME1=CCW; 
Subscriber Provisioning

Step 1 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1; 
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 performed.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
Add custom-dial-plan ID=cdp1; DIGIT-STRING=*70; NOD=VSC; FNAME=CCW; 
CAT-STRING=1111111111111111;
MLHG provisioning is similar to subscriber provisioning as described above.

Class of Service Screening

Office Provisioning

Step 1 Register the feature in the Office:
Add feature FNAME=COS; tdp1=COLLECTED-INFORMATION; tid1=COS-TRIGGER; ttype1=R; 
feature_server_id=FSPTC235; description=Class Of Service; grp_feature=N;
Step 2 Provision the feature into a service package:
Add service id=special-srv; fname1=COS;
Note This feature can be assigned to any of fnameN tokens

Step 3 (Optional) Provision a Class of Service restriction class:
Add/change cos-restrict id=basic-restrict; casual-restrict-type=<applicable-values>; 
national-restrict-type=<applicable-values>; national-wb-list=<applicable-values>; 
intl-restrict-type=<applicable-values>; ii-restrict=<applicable-values>; 
nod-wb-list=<applicable-values>; acct-code-allow=<applicable-values>; 
acct-code-length=<applicable-values>; auth-code-allow=<applicable-values>; 
auth-code-length=<applicable-values>; auth-code-grp-id=<applicable-values>;
Step 4 (Optional) Provision cos-restrict related tables based on a given cos-restrict provisioning:
Auth-code-grp, Auth-code, Casual-wb-list, Intl-wb-list, Lata, Lata-map, National-wb-list;
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.
change ca-config type=ACCT-CODE-PROMPT-DELAY; datatype=integer; value=200;
change ca-config type=AUTH-CODE-PROMPT-DELAY; datatype=integer; value=250;
Note Account codes and auth codes are not supported on ISDN trunks prior to R4.5 release

Provisioning Resources

Step 1 (Optional) Provision COS on a given trunk group (if required):
Add trunk-grp-feature-data tgn-id=isdn-1; tg=isdn-trunk-1; casual-call=Y/N; 
cos-restrict-id=new-age-restriction;
Subscriber Provisioning

Step 1 Add the service to the subscriber's service profile:
add subscriber-service-profile sub-id=sub1_plano.com; service-id=special-srv;
Step 2 (Optional) Add cos-restrict-id to the subscriber table:
add subscriber sub-id=sub1_plano.com; cos-restrict-id=new-age-restriction;
Centrex and MLHG provisioning is similar to subscriber provisioning as described above.

Provisioning for IVR Collection of Account/Authorization Codes

Step 1 Verify ca-config-base entry for default IVR route guide:

Note The value for DEFAULT-IVR-ROUTE-GUIDE-ID must correspond to the entry in the ROUTE-GUIDE table that routes to the default IVR.
SHOW CA-CONFIG-BASE TYPE=DEFAULT-IVR-ROUTE-GUIDE-ID; DATATYPE=STRING; VALUE=def_ivr_rg;
Step 2 Define the IVR script profile for the COS feature:
add ivr-script-profile fname=COS; ivr-access-mode=IVR;  ivr-route-guide-id=cos_ivr_rg; 
ivr-script-pkg-type=BAU; multiple-language-supp=N; 
Step 3 Specify the COS default voice back language in the LANGUAGE table:
add language id=def;
Step 4 Add an audio segment for the Authorization code prompt:
add audio-segment; id=AUTH-PROMPT; type=PHYSICAL; url=http://cos/auth.au;
Step 5 Add an audio segment for the Account code prompt:
add audio-segment; id=ACCT-PROMPT; type=PHYSICAL; url=http://cos/acct.au;
Step 6 Add an audio sequence for the Authorization code prompt:
add audio-seq id=cos_auth_prm_seq; language_id=def; seq=AUTH-PROMPT;
Step 7 Add an audio sequence for the Account code prompt:
add audio-seq id=cos_acct_prm_seq; language_id=def; seq=ACCT-PROMPT;
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:
add feature-config fname=COS; type=FDT_TIMER; datatype=INTEGER; value=100;
add feature-config fname=COS; type=IDT_TIMER; datatype=INTEGER; value=40;
Subscriber Provisioning

Step 1 Set prompt method as IVR based for the subscriber/group's COS restriction:
change COS-RESTRICT id=test; PROMPT-METHOD=IVR;
Step 2 Set the ALLOW-CALLS-ON-IVR-FAILURE parameter in the subscriber's effective cos-restrict:
change cos-restrict id=test; ALLOW-CALLS-ON-IVR-FAILURE=Y;
Centrex Provisioning

Provisioning is similar to subscriber provisioning and basic Centrex provisioning.

Codec Negotiation

Codec selection and negotiation work together.

Codec Selection

Codec 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.

Office Provisioning

Step 1 Provision the Feature table:
add feature FNAME=CDP; TDP1=COLLECTED_INFORMATION; TID1=CUSTOMIZE_DIALING_PLAN; TTYPE1=R; 
FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Custom Dial Plan Feature;
Step 2 Provision the Service table:
add service id=2; FNAME1=CDP;
Centrex Provisioning

Step 1 Provision the subscriber-service-profile:
add subscriber-service-profile sub_id=sub_1; service-id=2;
MLHG Provisioning

MLHG provisioning is only applicable for MLHG-CTX and is similar to Centrex provisioning.

Provisioning Notes/Caveats

The CDP feature should be assigned to every Centrex category user.

Customer Originated Trace

Office Provisioning

Step 1 Create the feature:
add feature fname=COT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE; ttype1=R; 
description=Customer Originated Trace; feature_server_id=FSPTC235;
Step 2 Add the VSC code:
add vsc fname=COT;  digit_string=*57;
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:
change ca-config type=DEFAULT-OFFICE-SERVICE-ID; datatype=string; value=467;
Step 4 (Optional) For Usage-Sensitive COT, add the COT feature to the default office service id:
Add service id=467; FNAME1=COT; 
Subscriber Provisioning

Step 1 Add the COT feature to a service set:
Add service id=special-srv; fname=COT;
Step 2 Add the service to the subscriber's service profile:
add subscriber-service-profile sub-id=sub1_plano.com; service-id=special-srv; 
Step 3 (Optional) The operator may optionally deny originating a COT service on a subscribers line:
add subscriber-feature-data sub-id=sub1_plano.com; type1=DENIED; value1=Y;
Step 4 (Optional) Change the subscriber's Usage Sensitivity feature applicability flag (if required):
change subscriber id=sub1_plano.com; USAGE-SENS=Y;
Centrex Provisioning

Step 1 Add an entry in the CDP table:
add cdp id=cdp1; DIGIT_STRING=*57; NOD=VSC; FNAME=COT;
MLHG provisioning is similar to subscriber provisioning as described above.

Direct Call Pickup Without Barge-In

Office Provisioning

Step 1 Provision the feature table:
add feature FNAME=DPN; FEATURE_SERVER_ID=FSPTC235; GRP_FEATURE=N; DESCRIPTION=Direct Call 
Pickup Without Barge-In Feature;
Step 2 Provision the service table:
add service ID=2; FNAME1=DPN;
Centrex Provisioning

Step 1 Provision the subscriber-service profile:
add subscriber-service-profile SUB_ID=SUB_1; SERVICE-ID=2;
Step 2 Add the feature into the custom-dial-plan table for the Centrex group:
add custom-dial-plan ID=cdp1; DIGIT-STRING=*23; NOD-VSC; FNAME=DPN; 
CAT-STRING=1111111111111111;
MLHG Provisioning

Applicable for MLHG_CTX only; provisioning is similar to Centrex provisioning.

Direct Call Pickup With Barge-In (DPU)

The following subsections identify necessary steps to provision Direct Call Pickup with barge-in:

Office Provisioning

Step 1 Provision the feature table:
add feature FNAME=DPU; FEATURE_SERVER_ID=FSPTC235; GRP_FEATURE=N; DESCRIPTION=Direct Call 
Pickup With Barge-In Feature;
Step 2 Provision the Service table:
add service ID=2; FNAME1=DPU;
Centrex Provisioning

Step 1 Provision the subscriber-service-profile:
add subscriber-service-profile SUB_ID=SUB_1; SERVICE-ID=2;
Step 2 Add the feature into the custom-dial-plan table for the Centrex group:
add custom-dial-plan ID-cdp1; DIGIT-STRING=*24; NOD-VSC; FNAME-DPU; 
CAT-STRING=1111111111111111;
MLHG Provisioning

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.

Office Provisioning

Step 1 Provision the Feature table:
add feature  FNAME=DACWI;  TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED;  TTYPE1=R;  FEATURE_SERVER_ID=FSPTC235;  
GRP_FEATURE=N; DESCRIPTION=Distinctive Alerting / Call Waiting Indication Feature;
Step 2 Provision the Service table:
add service id=2; FNAME1=DACWI;
Subscriber Provisioning

The DA/CWI feature applies only to a Centrex group.

Centrex Provisioning

Step 1 Provision the subscriber-service-profile:
add subscriber-service-profile  sub_id=sub-1;  service-id=2;
MLHG Provisioning

This feature is only applicable to MLHG-CTX. MLHG provisioning is similar to Centrex provisioning.

Do Not Disturb

Office Provisioning

Step 1 Create a feature for DND-Activation:
add feature FNAME=DND_ACT; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
FEATURE_SERVER_ID=FSPTC235; TTYPE1=R; DESCRIPTION=DND Activation; GRP_FEATURE=N;
Step 2 Create a feature for DND-Deactivation:
add feature FNAME=DND_DEACT; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=DND Deactivation; GRP_FEATURE=N;
Step 3 Create a feature for DND:
add feature FNAME=DND; TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED; TTYPE1=R; FEATURE_SERVER_ID=FSPTC235; DESCRIPTION=Do 
not disturb; GRP_FEATURE=N;
Step 4 Create the VSC codes in the VSC table:
add vsc DIGIT_STRING=*78; FNAME=DND_ACT  
add vsc DIGIT_STRING=*79; FNAME=DND_DEACT;
Step 5 Create the reminder ring feature:
add/change subscriber_feature_data fname=DND; sub_id=<sub id>; type1=RR; value1=Y;
Note Reminder ring is not supported for SIP subscribers.

Subscriber Provisioning

Step 1 Create the service with these features:
add service id=1; fname1=DND;  fname2=DNDA;  fname3=DNDD;
Step 2 Assign the service to the subscriber:
add/change subscriber-service-profile; sub-id=<sub id>; service-id=1; 
Centrex Provisioning

Step 1 Create an entry in the CDP table:
add/change cdp;  id=cdp1;  DIGIT_STRING=*78;  NOD=VSC; FNAME=DND_ACT; 
CAT_STRING=1111111111111111  
add/change cdp;  id=cdp1;  DIGIT_STRING=*79;  NOD=VSC;  FNAME=DND_DEACT; 
CAT_STRING=1111111111111111;
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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=DND;
Use a CLI command similar to the following to deactivate DND:
add subscriber-feature-data sub-id=sub_1; active=N; fname=DND;
Group Speed Call: 1-Digit and 2-Digit

Office Provisioning

Step 1 Add the Group 1 digit speed call feature:
add feature fname=GSC1D; tdp1=COLLECTED_INFORMATION; tid1=SC1D_TRIGGER; ttype1=R; 
description=Group One Digit Speed Call Activation; feature_server_id=FSPTC235;
Step 2 Add the Group 2 digit speed call feature:
add feature fname=GSC2D;     tdp1=COLLECTED_INFORMATION;     tid1=SC2D_TRIGGER;     
ttype1=R; description=Group Two Digit Speed Call Activation;     
feature_server_id=FSPTC235;
Step 3 Create a service with all the Group speed call features:
Add service id=499; fname1=GSC1D; fname2=GSC2D;
Subscriber Provisioning

Step 1 Provision the Subscriber-service-profile table Add the service to the subscriber:
add sub-service-profile sub-id=sub_1_4; service-id=499; 
Centrex Provisioning

In addition to subscriber provisioning, provision the Custom Dial Plan (CDP) Table:

Step 1 Provision the Custom-dial-plan table:
add  custom-dial-plan     ID=cdp1;     DIGIT-STRING=2;     NOD=SPEED-CALL;     FNAME=SC1D;     
CAT-STRING=1111111111111111; 
add  custom-dial-plan     ID=cdp1;     DIGIT-STRING=3;     NOD=SPEED-CALL;     FNAME=SC1D;     
CAT-STRING=1111111111111111;
add  custom-dial-plan      ID=cdp1;     DIGIT-STRING=4;     NOD=SPEED-CALL;     
FNAME=SC1D;     CAT-STRING=1111111111111111;
add  custom-dial-plan      ID=cdp1;     DIGIT-STRING=5;     NOD=SPEED-CALL;     
FNAME=SC1D;     CAT-STRING=1111111111111111;
add  custom-dial-plan      ID=cdp1;     DIGIT-STRING=6;     NOD=SPEED-CALL;     
FNAME=SC1D;     CAT-STRING=1111111111111111;
add  custom-dial-plan      ID=cdp1;     DIGIT-STRING=7;     NOD=SPEED-CALL;     
FNAME=SC1D;     CAT-STRING=1111111111111111;
add  custom-dial-plan     ID=cdp1;     DIGIT-STRING=2x;     NOD=SPEED-CALL;     
FNAME=SC2D;     CAT-STRING=1111111111111111;
add  custom-dial-plan      ID=cdp1;     DIGIT-STRING=3x;     NOD=SPEED-CALL;     
FNAME=SC2D;     CAT-STRING=1111111111111111;
add  custom-dial-plan      ID=cdp1;     DIGIT-STRING=4x;     NOD=SPEED-CALL;     
FNAME=SC2D;     CAT-STRING=1111111111111111; 
MLHG provisioning is similar to subscriber provisioning as described above.

Alternate Provisioning Method

GSC1D can alternately be provisioned or removed by creating an entry in the SC1D table.

Use a CLI command similar to the following to provision the GSC1D code:

add sc1d sub-id=sub_1; dnx=4692551001;

Use a CLI command similar to the following to remove provisioning for the GSC1D code:

add sc1d sub-id=sub_1; dnx=NULL;

Note dnx can be one of {dn1, dn2, dn3, ..., dn9}. For a Centrex subscriber, it can only be one of {dn2, dn3, ..., dn7}

Note For a Centrex user, the sub-id should be the main subscriber id defined in the Centrex-grp table.

GSC2D can alternately be provisioned or removed by creating an entry in the SC2D table.

Use a CLI command similar to the following to provision the GSC2D code:

add sc2d sub-id=sub_1; dnx=4692551001;

Use a CLI command similar to the following to remove provisioning for the GSC2D code:

add sc2d sub-id=sub_1; dnx=NULL;

Note dnx can be one of {dn20, dn21, ..., dn49}.

Note For a Centrex user, the sub-id should be the main subscriber id defined in the Centrex-Grp table.

Hotline

Office Provisioning

Step 1 Register the feature in the Office:
Add feature FNAME=HOTLINE; tdp1=O_ATTEMPT_AUTHORIZED; tid1=O_ATTEMPT_AUTHD; ttype1=R; 
feature_server_id=FSPTC235; description=Hotline; grp_feature=N;
Step 2 Provision the feature into a service package:
Add service id=special-srv; fname1=HOTLINE;
Note This feature may be assigned to any of fnameN tokens

Provisioning Resources

Step 1 The mgw-profile of the media gateway to which subscriber line is associated must have its MGCP version set as "non-0.1":
add/change mgw-profile id=plano-iad; mgcp-version=MGCP_1_0;
Note MGCP 0.1 version does not support TO signal completion report.

Step 2 Set the Dial-Tone timeout as a supported feature by the MGW:
add/change mgw-profile id=plano-iad; mgcp-to-supp=Y;
Subscriber Provisioning

Step 1 Add the service to the subscriber's service profile:
add subscriber-service-profile sub-id=sub1_plano.com; service-id=special-srv;
Step 2 Add the Hotline target DN to the subscriber's feature data:
add subscriber-feature-data sub-id=sub1_plano.com; fname=HOTLINE; type1=FDN1; 
value1=9726712355;
Centrex Provisioning

Centrex and MLHG provisioning is similar to subscriber provisioning as described above.

Hotline—Variable

Provisioning the HOTV (invocation) feature is exactly the same as the Warmline feature except for the feature name.

Office Provisioning

Step 1 Register the features in the Office:
Add feature FNAME=HOTVx; tdp1=COLLECTED-INFORMATION; tid1=VERTICAL-SERVICE-CODE; ttype1=R; 
feature_server_id=FSPTC235; description=Hotline-Variable Act / Deact; grp_feature=N; 
Note HOTVx is interchangeably referred to here for HOTVA, HOTVD, and HOTVI features.

Step 2 Add the VSC code for HOTVA:
add vsc fname=HOTVA;  digit-string=*52*;
Step 3 Add the VSC code for HOTVD:
add vsc fname=HOTVD;  digit-string=#52#;
Step 4 Add the VSC code for HOTVI:
add vsc fname=HOTVI; digit-string=*#52*;
Step 5 Add a service with these features:
add service id=special-srv;  FNAME1=HOTV;  FNAME2=HOTVA;  FNAME3=HOTVD;  FNAME4=HOTVI;
Step 6 (Optional) Provision an exception call-type list for the Hotline service. Multiple call types can be entered:
Add nod-restrict-list fname1=HOTV; call-type=EMG;
Note HOTVx is interchangeably referred to here for HOTVA, HOTVD, and HOTVI features.

Step 7 (Optional) Change the HOTV dial-tone timeout parameter (if need to customize):
Add/change feature FNAME=HOTV; type1=TO; value1=6;
Note The internal default is 4 seconds.

Provisioning Resources

Step 1 The mgw-profile of the media gateway to which the subscriber line is associated must have its MGCP version set as "non-0.1":
add/change mgw-profile id=plano-iad; mgcp-version=MGCP_1_0;
Note MGCP 0.1 version does not support TO signal completion report.

Step 2 Set the Dial-Tone timeout as a supported feature by the MGW:
add/change mgw-profile id=plano-iad; mgcp-to-supp=Y;
Subscriber Provisioning

Step 1 Add the service to the subscriber's service profile:
add subscriber-service-profile sub-id=sub1_plano.com; service-id=special-srv;
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 steps must be performed.

Step 1 Add the feature into the custom-dial-plan table for the Centrex group:
Add/change  custom-dial-plan  ID=cdp1;DIGIT-STRING=*52*; NOD=VSC;FNAME=HOTVA; 
CAT-STRING=1111111111111111;
add/change  custom-dial-plan  ID=cdp1;DIGIT-STRING=#52#; NOD=VSC;FNAME=HOTVD; 
CAT-STRING=1111111111111111;
add/change  custom-dial-plan ID=cdp1; DIGIT-STRING=*#52*;  NOD=VSC; FNAME=HOTVI;  
CAT-STRING=1111111111111111;
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:
add subscriber-feature-data sub-id=sub_1; active=Y; fname=HOTV; type1=FDN1;
value1=4692551001;
Note The value should be the Hotline DN.

Use a CLI command similar to the following to deactivate HOTV:
add subscriber-feature-data sub-id=sub_1; active=N; fname=HOTV;
Incoming Simulated Facility Group

The following subsections identify necessary steps for the Incoming Simulated Facility Group (ISFG) feature to be offered.

Office Provisioning

Step 1 Provision the Feature table:
add feature  FNAME=ISFG;  TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED;  TTYPE1=R;  FEATURE_SERVER_ID=FSPTC235;  
GRP_FEATURE=N; DESCRIPTION=Incoming Simulated Facility Group Feature;
Step 2 Provision the Service table:
add service id=2; FNAME1=ISFG;
Centrex Provisioning

Step 1 Provision the subscriber-service-profile:
add subscriber-service-profile  sub_id=sub_1; service-id=2;
Step 2 Provision CTXG:
Change ctxg ID=ctxg1; SFG_CONTROL=Y; IN_SFG_COUNT=3; OUT_SFG_COUNT=3; BOTH_SFG_COUNT=4;
This feature is only applicable to MLHG-CTX. MLHG provisioning is similar to Centrex provisioning as described above.

Provisioning Notes/Caveats

SFG controls will be effective only if the subscriber(s) are assigned SFG features and the Centrex-grp table has the SFG-Control flag set to Y.

IP Transfer Point Non-Stop Operation

NSO Configuration: D-Link for ISUP with ASP Load Sharing

Perform the following steps to provision an NSO D-Link configuration for ISUP with ASP load sharing.

Step 1 Add the Signaling Gateways with internal redundancy mode set to SSO-NSO.
add sg id=sgw100; internal_redundancy_mode=SSO-NSO;description=SS7 Signaling Gateway ANSI 
testing;priority=1; 
add sg id=sgw110; internal_redundancy_mode=SSO-NSO;description=SS7 Signaling Gateway ANSI 
testing;priority=1; 
Step 2 Add the Signaling Gateway Group for STP (Mated STP) mode.
add sg-grp id=sg-grp100; sg1-id=sgw100;sg2-id=sgw110; sg-grp-mode=Mated_STP;description=SG 
Group for ANSI testing;
Step 3 Add 2 Signaling Gateway Process (SGP) for each Signaling Gateway
add sgp id=sgw100-sgp1; sg-id=sgw100; description=SGP on ITP va-7507-3;
add sgp id=sgw100-sgp2; sg-id=sgw100; description=SGP on ITP va-7507-3;
add sgp id=sgw110-sgp1; sg-id=sgw110; description=SGP on ITP va-7507-6;
add sgp id=sgw110-sgp2; sg-id=sgw110; description=SGP on ITP va-7507-6;
Step 4 Add the OPC and ISUP DPCs.
add opc id=opc1; point-code=250-250-3; point-code-type=ANSI_CHINA;description= Network 
Point Code 1;
add dpc id=hollyville; point-code=250-248-4; point-code-type=ANSI_CHINA; description=ANSI 
SS7 network DPC;
add dpc id=havenville; point-code=250-248-6; point-code-type=ANSI_CHINA; description=ANSI 
SS7 network DPC;
Step 5 Add the SCTP association profile.
add sctp-assoc-profile id=sctp_pf100;
Step 6 Add the SCTP associations to each Signaling Gateway.
add sctp-assoc id=CA-assoc1; sgp-id=sgw100-sgp1;sctp_assoc-profile-id=sctp_pf100; 
platform-id=CA146; remote-port=2905; REMOTE_TSAP_ADDR1=10.0.1.230;
add sctp-assoc id=CA-assoc2; sgp-id=sgw100-sgp2;sctp_assoc-profile-id=sctp_pf100; 
platform-id=CA146; remote-port=2907; REMOTE_TSAP_ADDR1=10.128.7.8;
add sctp-assoc id=CA-assoc3; sgp-id=sgw110-sgp1;sctp_assoc-profile-id=sctp_pf100; 
platform-id=CA146; remote-port=2905; remote-tsap-addr1=10.0.5.216;
add sctp-assoc id=CA-assoc4; sgp-id=sgw110-sgp2;sctp_assoc-profile-id=sctp_pf100; 
platform-id=CA146; remote-port=2907; remote-tsap-addr1=10.128.2.7;
Step 7 Add the ISUP routing key.
add routing-key id=NewMatedSG-rk; opc-id=opc1; sg-grp-id=sg-grp100; si=ISUP; 
platform-id=CA146; rc=60; description=Dual processor Signaling Gateway;
Step 8 Add call control routes for each ISUP DPC.
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 sg id=sgw100; internal_redundancy_mode=SSO-NSO;description=SS7 Signaling Gateway ANSI 
testing;priority=1; 
add sg id=sgw110; internal_redundancy_mode=SSO-NSO;description=SS7 Signaling Gateway ANSI 
testing;priority=1; 
Step 2 Add the Signaling Gateway Group for STP (Mated STP) mode
add sg-grp id=sg-grp100; sg1-id=sgw100;sg2-id=sgw110; sg-grp-mode=Mated_STP;description=SG 
Group for ANSI testing;
Step 3 Add 2 Signaling Gateway Process (SGPs) for each Signaling Gateway
add sgp id=sgw100-sgp1; sg-id=sgw100; description=SGP on ITP va-7507-3;
add sgp id=sgw100-sgp2; sg-id=sgw100; description=SGP on ITP va-7507-3;
add sgp id=sgw110-sgp1; sg-id=sgw110; description=SGP on ITP va-7507-6;
add sgp id=sgw110-sgp2; sg-id=sgw110; description=SGP on ITP va-7507-6;
Step 4 ADD OPC & TCAP DPC's
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 sctp-assoc id=FSAIN-assoc1; sgp-id=sgw100-sgp1; 
sctp_assoc-profile-id=sctp_pf100;platform-id=FSAIN205; 
remote-port=14001;REMOTE_TSAP_ADDR1=10.0.1.230;
add sctp-assoc id=FSAIN-assoc2; sgp-id=sgw100-sgp2; sctp_assoc-profile-id=sctp_pf100; 
platform-id=FSAIN205; remote-port=14002; REMOTE_TSAP_ADDR1=10.128.7.8;
add sctp-assoc id=FSAIN-assoc3; sgp-id=sgw100-sgp1; 
sctp_assoc-profile-id=sctp_pf100;platform-id=FSPTC235; 
remote-port=14001;REMOTE_TSAP_ADDR1=10.0.1.230;
add sctp-assoc id=FSAIN-assoc4; sgp-id=sgw100-sgp2; sctp_assoc-profile-id=sctp_pf100; 
platform-id=FSPTC235; remote-port=14002; REMOTE_TSAP_ADDR1=10.128.7.8;
add sctp-assoc id=FSPTC-assoc1; sgp-id=sgw110-sgp1; sctp_assoc-profile-id=sctp_pf100; 
platform-id=FSAIN205; remote-port=14001;REMOTE_TSAP_ADDR1=10.0.5.216;
add sctp-assoc id=FSPTC-assoc2; sgp-id=sgw110-sgp2; sctp_assoc-profile-id=sctp_pf100; 
platform-id=FSAIN205;remote-port=14002;REMOTE_TSAP_ADDR1=10.128.2.7;
add sctp-assoc id=FSPTC-assoc3; sgp-id=sgw110-sgp1; 
sctp_assoc-profile-id=sctp_pf100;platform-id=FSPTC235; 
remote-port=14001;REMOTE_TSAP_ADDR1=10.0.5.216;
add sctp-assoc id=FSPTC-assoc4; sgp-id=sgw110-sgp2; sctp_assoc-profile-id=sctp_pf100; 
platform-id=FSPTC235; remote-port=14002; REMOTE_TSAP_ADDR1=10.128.2.7;
Step 6 Add the LNP, CNAM & 800 features
add feature fname=LNP; feature-server-id=FSAIN205; description=Local number portability; 
tdp1=COLLECTED_INFORMATION; tid1=LNP_TRIGGER; ttype1=R;
add feature fname=8XX; tdp1=COLLECTED_INFORMATION; tid1=SPECIFIC_DIGIT_STRING; ttype1=R; 
description=Toll Free Number; feature_server_id=FSAIN205;
add feature fname=CNAM;tdp1=FACILITY_SELECTED_AND_AVAILABLE; 
tid1=TERMINATION_RESOURCE_AVAILABLE; ttype1=R; description=Calling Name; 
feature_server_id=FSPTC235;
add feature fname=AC; fname1=AC_ACT; fname2=AC_DEACT; feature_server_id=FSPTC235;
add feature fname=AR; fname1=AR_ACT; fname2=AR_DEACT; feature_server_id=FSPTC235;
Step 7 Add SCCP Network for TCAP services
add sccp-nw id=6;net-ind=NATIONAL;sub-svc=NATIONAL;hop-count=3;
Step 8 Add SSN profile
add subsystem-grp id=SSN_LNP1;platform_id=FSAIN205;tcap-version=ANS92; description=SS grp 
profile for LNP svc;
add subsystem-grp id=SSN_AIN_800_1; platform-id=FSAIN205;tcap-version=ANS92; 
description=SSN grp profile for 800 svc;
add subsystem-grp id=SSN_CNAM1; platform-id=FSPTC235;tcap-version=ANS92; description=SSN 
grp profile for CNAM svc;
add subsystem-grp id=SSN_ACAR1; platform-id=FSPTC235;tcap-version=ANS92; description=SSN 
grp profile for AC/AR svc;
Step 9 Add Subsystem
add subsystem id=SSN_LNP1; opc-id=opc1; local-ssn=247;remote-ssn=247; 
sccp-nw-id=6;sccp-version=ANS92; application-version=AIN01;
add subsystem id=SSN_AIN_800_1; opc-id=opc1; local-ssn=248;remote-ssn=248; 
sccp-nw-id=6;sccp-version=ANS92; application-version=AIN01;
add subsystem id=SSN_CNAM1; opc-id=opc1; local-ssn=232;remote-ssn=232; sccp-nw-id=6; 
sccp-version=ANS92; application-version=IN1;
add subsystem id=SSN_ACAR1; opc-id=opc1; 
local-ssn=251;remote-ssn=251;sccp-nw-id=6;sccp-version=ANS92;APPLICATION_VERSION=IN1;
Step 10 Add routing Key for FSPTC & FSAIN
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;descriptio
n=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.
add trigger-nod-escape-list tid=LCD_TRIGGER; nod=REPAIR;
Step 2 Add a RADIUS profile with the appropriate TSAP address and server type (prepaid).

Note Two examples are shown—one using a domain name and one using an IP address.
add radius-profile id=rad-profile-prepd015; tsap-addr=central777.cisco.com:1819; 
server-type=prepaid;
add radius-profile id=rad-profile-prepd777; tsap-addr=172.16.5.5:1819; 
server-type=prepaid;
Step 3 Add an AAA server group that links to the appropriate RADIUS profile.
add aaa-server-grp id=aaa-server-grp1; radius-profile-id=rad-profile-prepd015;
Step 4 Provision the POP table to link to the appropriate AAA server group.
change pop id=londonpop3; aaa-server-grp-id=aaa-server-grp1;
Step 5 Create the LCD feature.
add feature fname=LCD; tdp1=COLLECTED_INFORMATION; tid1=LCD_TRIGGER; ttype1=R; 
description=Limited Call Duration Feature; feature-server=FSPTC235; grp-feature=N;
Step 6 Add the LCD feature to a service.
add service id=5; fname1=LCD; description=Prepaid Service;
Step 7 Assign the service to a subscriber.
add sub-service-profile sub-id=nyc-sub1; service-id=5;
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.
add ca-config type=RELEASE-CALL-ON-LCD-TRIGGER-FAILURE; datatype=BOOLEAN; value=N;
Local Number Portability for ANSI/North America

Office Provisioning

Step 1 Create a feature for LNP DB lookup:
add 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 the 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 the ported-office-code:
add ported-office-code digits-string=NPA-NXX; in-call-agent=N;
Step 4 Add My-LRN and JIP in the POP table:
change pop id=1; my-lrn=NPA-NXX-XXXX; JIP=NPA;
Step 5 Verify the following table fields for appropriate values:
dn2subscriber.LNP_TRIGGER
dn2subscriber.status
trunk-grp.signal-ported-number
trunk-grp.remote-switch-lrn
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; 
Step 4 Provision the SCTP association profile:
add sctp-assoc-profile id=sctp_prof; bundle_timeout=500; max_assoc_retrans=5; 
max_path_retrans=5;  max_rto=6000; min_rto=301; sack_timeout=101;  hb_timeout=1000; 
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 5 Provision the SCTP association:
add sctp-assoc  id=sctp_assoc1;  sgp-id=itp_7507_1;  sctp-assoc-profile-id=sctp_prof; 
remote_port=14001; remote_tsap_addr1=10.89.232.9; remote_tsap_addr2=10.89.233.41; 
local_rcvwin=64000; max_init_retrans=5; max_init_rto=1000; platform_id=FSAIN205; 
Step 6 Add the DPC:
add dpc id=stp1; point-code=1-101-0;  description=STP1, MGTS STP;
Step 7 Add the SCCP network:
add sccp-nw id=1; net-ind=NATIONAL; SUB_SVC=NATIONAL;  HOP-Count=10;
Step 8 Add the subsystem group:
add subsystem-grp id=SSN_LNP; PLATFORM_ID=FSAIN205; TCAP_VERSION=ANS92; 
Step 9 Add the subsystem:
add subsystem id=SSN_LNP; opc_id=opc; local-ssn=247; remote-ssn=247; sccp-nw-id=1; 
SCCP_VERSION=ANS92; APPLICATION_VERSION=AIN01;
Step 10 Add the routing key:
add routing-key id=rk_lnp;  opc-id=opc;  sg-grp-id=sg_grp;  si=SCCP;  rc=202; 
PLATFORM_ID=FSAIN205; ssn-id=SSN_LNP;
Step 11 Add an SCCP route:
add sccp-route opc_id=opc; dpc_id=stp1; subsystem_grp_id=SSN_LNP;
Step 12 Add the SLHR profile:
add slhr-profile id=slhr_lnp;
Step 13 Add the service logic host route:
add slhr id=slhr_lnp; opc_id=opc; dpc_id=stp1; ssn-id=SSN_LNP;  gtt-req=Y; tt=11; 
GTT_ADDR_TYPE=CDPN; GTT_ADDR=3;
Step 14 Add the ca-config type DEFAULT-LNP-SLHR-ID:
Add ca-config type=DEFAULT-LNP-SLHR-ID; datatype=string; value=slhr_lnp;
Step 15 Add the ca-config type SCP-RESPONSE-TIMER:
Add ca-config type=SCP-RESPONSE-TIMER; datatype=integer; value=3;
Step 16 Place SCTP Association In Service:
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):
change dn2subscriber dn=1522; office-code-index=15; lnp-trigger=Y;
Step 2 Mark subscriber ported-out (ported-out of this donor switch to the recipient switch):
change dn2subscriber dn=1522; office-code-index=15; status=ported-out;
Provisioning Notes/Caveats

•When the ported office code is served by the switch, then, in the provisioning command add ported -office-code, the value for in-call-agent should be Y. During the transition period, the Dn2subscriber table should be modified to status = PORTED-OUT if the subscriber is porting out. If the subscriber is porting in, the LNP-trigger should be changed to N once porting is complete.

•If the IN-CALL-AGENT field in the ported-office-table is set to Y, the BTS will check the Dn2subscriber table to see if the called number is in the BTS. If the IN_CALL_AGENT flag is set to N, the BTS omits the Dn2subscriber table check and performs a LNP query.

•If the LNP-TRIGGER field in the Dn2subscriber table is set to Y , then a query will be performed by the BTS even if the IN-CALL-AGENT field in the ported office code table is set to N.

•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):
add lnp-profile id=lnp_rn_acq; all-call-query=Y; external-lnp-db=n; internal-lnp-db=Y; 
lnp-db-type=RN; rn-signaling-method=prefix-method;
b. Add switch-based LNP Profile for Query on Release (QoR):
add lnp-profile id=lnp_rn_qor; query-on-release=Y; external-lnp-db=n; internal-lnp-db=Y; 
lnp-db-type=RN; rn-signaling-method=prefix-method; release-cause=14;
c. Add a switch-based LNP Profile for Combination of QoR and ACQ:
add lnp-profile id=lnp_rn_acq_qor; all-call-query=Y; query-on-release=Y; 
external-lnp-db=n; internal-lnp-db=Y; np-db-type=RN; rn-signaling-method=prefix-method; 
release cause=14;
d. Add a switch-based LNP Profile for Onward Call Routing (OCR) (also known as Onward Donor Based Routing (ODBR)):
add lnp-profile id=lnp_rn_odbr; onward-call-routing=Y; external-lnp-db=n; 
internal-lnp-db=Y; lnp-db-type=RN; rn-signaling-method=prefix-method;
Step 4 Assign an LNP Profile to be used for the office. In this example, the QoR LNP Profile is used:
add/change ca-config type=DEFAULT-LNP-PROFILE-ID;DATATYPE=STRING; value=lnp_rn_acq_qor;
Subscriber Provisioning

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.
change dn2subscriber dn=1522; office-code-index=15; status=ported-out;
NOA Routing and Dial Plan Provisioning

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):

subscriber/trunk dial-plan "dp_sub_itu" -> noa-route "noa_rt" -> destination "dummy_rn_itu" -> RN dial-plan "dp_rn_itu" -> destination "dest_rn_sub_itu"

Example commands are included in the table below:

Step 1 Provision Digman-profile for RN dial-plan-profile to match RN of this BTS and ported NOA, strip RN, and replace NoA:
add digman-profile id=dm_dpp_rn; description=digman for RN dial-plan-profile after NOA 
Routing (ITU);
Step 2 For a call terminating to a DN ported in to this switch, strip the RN prefix (of this switch, 4001), and replace the NoA:
add digman id=dm_dpp_rn; rule=1; match-string=^4001; match-noa=PORTED_NUMBER_WITH_RN; 
replace-string=none; replace-noa=UNKNOWN; 
Step 3 RN dial-plan-profile does not use NOA routing because this dial-plan-profile is only reached after NOA routing:
add dial-plan-profile id=dp_rn_itu; description=RN dial plan (ITU); nanp-dial-plan=N;
noa-based-routing=N;
Note For a non-North American dial plan, make sure nanp-dial-plan=N.

Step 4 If this digman was not added earlier, then add it now, if desired:
change dial-plan-profile id=dp_rn_itu; dnis-digman-id=dm_dpp_rn;
Step 5 Provision the Destination table. This destination, from the regular subscriber dial-plan, allows an LNP query:
add destination dest-id=dest_sub_itu; call-type=LOCAL; route-type=SUB; 
ani-digman-id=dm_dest_sub_ani; dnis-digman-id=dm_dest_rn; acq-lnp-query=PERFORM-LNP-QUERY; 
description=ITU Sub dest: Allow LNP query;
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:
add dial-plan id=dp_rn_itu; digit-string=1150; noa=UNKNOWN; min-digits=8; max-digits=8; 
dest-id=dest_sub_rn_itu; 
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 dial-plan id=dp_rn_itu; digit-string=17023001; noa=UNKNOWN; min-digits=8; 
max-digits=8; dest-id=dest_sub_rn_itu;
Step 10 Setup the ndc for DN 1-150-1xxx:
add ndc digit-string=1;
Step 11 Setup the exchange-code for DN 1-150-1xxx:
add exchange-code ec=150; ndc=1; max-dn-length=8; min-dn-length=8; office-code-index=15;
Step 12 Setup the dn-group for DN 1-150-1xxx:
add office-code call-agent-id=CA146; ndc=1; ec=150; dn-group=1xxx;
Step 13 Setup the exchange-code for ported-in DN 1-702-3001:
add exchange-code ec=702; ndc=1; max-dn-length=8; min-dn-length=8; office-code-index=5;
Step 14 Setup the office-code for ported-in DN 1-702-3xxx:
add office-code call-agent-id=CA146; ndc=1; ec=702; dn-group=3xxx;
Step 15 Add the regular subscriber dial-plan profile, with NOA routing:
add dial-plan-profile id=dp_sub_itu; ani-digman-id=dm_dpp_ani_itu; 
dnis-digman-id=dm_dpp_sub_dnis; nanp-dial-plan=N; description=Subscriber Local dial-plan 
(ITU);
Step 16 Add normal routing for non-ported DN terminating to local subscriber, e.g., 1-150-1511:
add dial-plan id=dp_sub_itu; digit-string=1150; min-digits=8; max-digits=8; noa=UNKNOWN; 
dest-id=dest_sub_itu;
Step 17 Add the NOA route profile, if desired:
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:
add noa-route id=noa_rt; noa=PORTED_NUMBER_WITH_RN; dest-id=dummy_rn_itu;
Step 19 Add NOA routing, if desired, if not done above:
change dial-plan-profile id=dp_sub_itu; noa-based-routing=Y; noa-route-profile-id=noa_rt;
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.
change dn2subscriber dn=1522; office-code-index=15; status=ported-out;
Allow ACQ or QoR Query on Incoming Trunk Calls

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.:
change destination dest-id=dest_sub_itu; ACQ-LNP-QUERY=NA;
•Destination explicitly allows ACQ:
change destination dest-id=dest_sub_itu; ACQ-LNP-QUERY=PERFORM-LNP-QUERY;
•Destination explicitly disallows ACQ:
change destination dest-id=dest_sub_itu; ACQ-LNP-QUERY=NO-LNP-QUERY;
In the following example, the destination defers to the call type entry for the LNP ACQ decision:

Step 1 Destination indicates that the call-type entry (or omission of call-type entry) determines whether ACQ occurs:
change destination dest-id=dest_sub_itu; call-type=PREMIUM; 
ACQ-LNP-QUERY=ACQ-BASED-ON-CALL-TYPE;
•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:
add call-type-profile call-type=PREMIUM; lnp-query=N;
•Call type allows ACQ on this call:
add/change call-type-profile call-type=PREMIUM; lnp-query=Y;
Outgoing Carrier Call LNP ACQ Query Control

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.

Multiline Variety Package

This 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.
add cdp id=MVPcdp; digit_string=xxxxxxx; nod=MVP_POTS_ACCESS;
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.
add cdp id=MVPcdp; digit_string=2; nod=SPEED_CALL; fname=SC1D; 
CAT_STRING=1111111111111111
add cdp id=MVPcdp; digit_string=2x; nod=SPEED_CALL; fname=SC2D; 
CAT_STRING=1111111111111111
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.
add cdp id=MVPcdp; digit_string=*72; nod=VSC; fname=CFUA; CAT_STRING=1111111111111111
add cdp id=MVPcdp; digit_string=*73; nod=VSC; fname=CFUD; CAT_STRING=1111111111111111
e. Define the access code (#) and extension that enables calls to a member of the internal MVP Centrex group.
add cdp id=MVPcdp; digit_string=#; nod=MVP_EXTENSION; CAT_STRING=1111111111111111
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.
add digit-map id=digit-map; 
digit-pattern=0T|00|[2-9]11|[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|0[2-9]xx[2-9]xxxxxx|011
xxxxxx.T|101xxxx|#x.T|*[4-9]x|*[2-3]xx|11xx|[2-9]#|[2-4]x#|[2-9]T|[2-4]xT|01[2-9]xxxxx.T
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.
add subscriber_profile id=SubProfile; digit_map_id=digit-map;
dial_plan_id=PSTN DIAL-PLAN;
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.
add subscriber id=MainSubMVPgrp1; sub-profile-id=SubProfile;
add centrex_grp id=MVPgrp1; cdp_id=MVPcdp; call_agent_id=CA146 main_sub_id=MainSubMVPgrp1;
add cpsg id=MVPgrp1; ctxg_id=MVPgrp1; CPRK-FDN=12345
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.
change subscriber id=SubA; sub_profile_id=SubProfile category=CTXG_INDIVIDUAL; 
ctxg_id=MVPgrp1;
change subscriber id=SubB; sub_profile_id=SubProfile category=CTXG_INDIVIDUAL; 
ctxg_id=MVPgrp1;
change subscriber id=SubC; sub_profile_id=SubProfile category=CTXG_INDIVIDUAL; 
ctxg_id=MVPgrp1;
b. Create Extensions for the SubA, SubB, and SubC to enable extension dialing between the MVP group members.
add ext2subscriber ext=4001; sub_id=SubA; ctxg_id=MVPgrp1; cpsg_id=MVPgrp1;
add ext2subscriber; ext=4002; sub_id=SubB; ctxg_id=MVPgrp1; cpsg_id=MVPgrp1;
add ext2subscriber ext=4003; sub_id=SubC; ctxg_id=MVPgrp1; cpsg_id=MVPgrp1;
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 Centrex, MLHG, and Voicemail Provisioning, page 8-1, for directions for provisioning a MLHG.

Multi-Lingual Support for Interactive Voice Response and Announcements

The 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.

Office Provisioning

Step 1 Create the MLS feature:
add feature fname=MLS; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE; ttype=R; 
feature_server_id=FSPTC325
Step 2 Add service to the MLS feature:
add service id=mls; fname1=MLS;
Step 3 Add * code for MLS feature:
add vsc digit-string=*56; fname=MLS;
Provisioning Resources

Step 1 Add media server:
add mgw-profile id=ms_profile; vendor=Cisco; silent-supress-supp=N; rbk-on-conn-supp=N; 
packet-type=IP; AAL1=N; AAL2=N; AAL5=N; PVC=N; SVC=N; SPVC=N; EC=N; SDP-ORIGFIELD-SUPP=N; 
SDP-SESSNAME-SUPP=N; SDP-EMAIL-SUPP=N; SDP-PHONE-SUPP=N; SDP-URI-SUPP=N; 
SDP-BANDWIDTH-SUPP=N; SDP-INFO-SUPP=N; SDP-TIME-SUPP=N; SDP-ATTRIB-SUPP=N; 
MGCP-ERQNT-SUPP=N; MGCP-HAIRPIN-SUPP=N; MGCP-3WAY-HSHAKE-SUPP=Y; 
MGCP-CONN-ID-AT-GW-SUPP=Y; MGCP-CMD-SEQ-SUPP=N; MGCP-VMWI-SUPP=N; TERMINATION-PREFIX=ann/; 
PORT-START=0; MGCP-VERSION=MGCP_1_0; MGCP-RSVP-SUPP=N;
Step 2 Add media gateway:
add mgw id=ipunity_ms; tsap-addr=<ip addr of MS MGCP>; call-agent-id=CA166; 
mgw-profile-id=ms_profile; rgw=n; tgw=y; call-agent-control-port=0; ans=n; ivr=y; nas=n; 
pbx=n;
Step 3 Add IVR trunks:
add/change annc-tg-profile; id=annc_tg_p; annc=N; ivr=Y; auto_answer=Y;
Step 4 Addtermination:
add termination prefix=annc/; port-start=0; port-end=30; type=trunk; mgw-id=ipunity_ms;
Step 5 Add trunk group:
add trunk-grp id=1; call-agent-id=CA146; tg_typeannc; mgw-id=ipunity_ms; 
tg-profile-id=annc_tg_p; mgcp-pkg-type=AUDIO;
Step 6 Add trunk:
add trunk cic-start=1; ; cic-end=30; tgn-id=1; termination-prefix=ann/; 
termination-port-start=0; termination-port-end=29; mgw-id=ipunity_ms;
Step 7 Add route:
add route id=rt_annc; tgn1-id=1; tg-selection=LCR;
Step 8 Add route guide:
add route-guide id=rg_annc; policy-type=ROUTE; policy-id=rt annc;
Step 9 Add an IVR script profile for MLS:
add ivr-script-profile fname=MLS; ivr-access-mode=ivr; ivr-route-guide-id=ivr_rg; 
ivr-script-pkg-type=BAU;
Announcement Provisioning

Step 1 Add the default language identification:
add language id=def;
Step 2 Add the languages to the language table:
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>.
Step 5 Add MLS configuration parameters:
add feature-config; fname=MLS; type=RESTART-KEY; datatype=string; value=*;
add feature-config; fname=MLS; type=RETURN-KEY; datatype=string; value=#;
add feature-config; fname=MLS; type=FDT-TIMER; datatype=integer; value=50;
add feature-config; fname=MLS; type=NUM-ATTEMPTS; datatype=integer; value=3; 
description=number of attempts;
Subscriber Provisioning

The following steps detail how to add a subscriber for the MLS feature.

Step 1 Add a subscriber:
add subscriber id=sub_1; sub-profile-id=subprof_1; DN1=4692550260; language-id=spa;
Step 2 Assign the MLS service to the subscriber:
add subscriber-service-profile sub_id=sub_1; service-id=mls;
Centrex Provisioning

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.

Office Provisioning

Step 1 Create a feature for MDN:
add feature  FNAME=MDN; TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED; TTYPE1=R;  FEATURE_SERVER_ID=FSPTC235;  
DESCRIPTION=MDN; 
Step 2 Add a service with the feature:
add service id=1; FNAME1=MDN; 
Subscriber Provisioning

Step 1 Add the subscriber:
add subscriber id=sub_1; sub-profile-id=subprof_1; DN1=4692553008;
Step 2 Assign the service to the subscriber:
add subscriber-service-profile sub_id=subscriber_1; service-id=1;  
Step 3 Add a secondary DN to the subscriber:
add dn2subscriber sub_id=subscriber_1; fdn=469-255-3009; cwt_type=WT2; ring_type=R2; 
Step 4 Add a unique call waiting tone for each DN:
add dn2subscriber sub_id=subscriber_1; fdn=469-255-3010; cwt_type=WT3; ring_type=R3;
Step 5 Add a unique ringing pattern for each DN:
add dn2subscriber sub_id=subscriber_1; fdn=469-255-3011; cwt_type=WT4; ring_type=R4;
Centrex Provisioning

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 feature fname=NSA_ACT; TDP1=COLLECTED_INFORMATION; TID1=VERTICAL_SERVICE_CODE; 
TTYPE1=R; FEATURE_SERVER_ID=FSPTC325;
Step 2 Create the NSA feature, and include NSA_ACT as a subfeature:
add feature fname=NSA; TDP1=TERMINATION_ATTEMPT_AUTHORIZED; 
TID1=TERMINATION_ATTEMPT_AUTHORIZED; TTYPE1=R; FEATURE_SERVER_ID=FSPTC325; FNAME1=NSA_ACT;
Step 3 Add a VSC for NSA_ACT:
add vsc fname=NSA_ACT; DIGIT_STRING=*94;
Step 4 Add a custom dial plan (CDP) if the feature is used for a Centrex group:
add cdp id=cdp1; fname=NSA_ACT; DIGIT_STRING=*94; nod=VSC; CAT_STRING=1111111111111111;
Step 5 Create or modify the Screen List Editing (SLE) feature:
add feature fname=SLE;
Step 6 Add the NSA feature to a service:
add service id=nsa; fname1=NSA;
Step 7 (Optional) Reset the limit of DNs that the subscriber can place on the NSA bypass list. The default value is 31.
add ca-config type=SLE-LIST-SIZE; datatype=INTEGER; value=25;
Provisioning Resources

This section explains how to provision the interface to the IVR server, the IVR announcement trunks, and route to the IVR server for the NSA feature.

Step 1 Add a media server:
add mgw-profile ID=ms_profile; VENDOR=Cisco; SILENT-SUPPRESS-SUPP=N; RBK-ON-CONN-SUPP=N; 
PACKET-TYPE=IP; AAL1=N; AAL2=N; AAL5=N; PVC=N; SVC=N; SPVC=N; EC=N; SDP-ORIGFIELD-SUPP=N; 
SDP-SESSNAME-SUPP=N; SDP-EMAIL-SUPP=N; SDP-PHONE-SUPP=N; SDP-URI-SUPP=N; 
SDP-BANDWIDTH-SUPP=N; SDP-INFO-SUPP=N; SDP-TIME-SUPP=N; SDP-ATTRIB-SUPP=N; 
MGCP-ERQNT-SUPP=N; MGCP-HAIRPIN-SUPP=N; MGCP-QLOOP-SUPP=N; MGCP-3WAY-HSHAKE-SUPP=Y; 
MGCP-CONN-ID-AT-GW-SUPP=Y; MGCP-CMD-SEQ-SUPP=N; MGCP-VMWI-SUPP=N; TERMINATION-PREFIX=ann/; 
PORT-START=0; MGCP-VERSION=MGCP_1_0; MGCP-RSVP-SUPP=N;
Note Not all fields in the mgw-profile table are noted in this section. However, fields pertaining to the feature are noted.
Step 2 Add a media gateway:
add mgw id=ipunity_ms; tsap-addr=<ip addr of  MS MGCP>; call-agent-id=CA166; 
mgw-profile-id=ms_profile; rgw=n; tgw=y; call-agent-control-port=0; ans=n; ivr=y; nas=n; 
pbx=n;
Step 3 Add IVR trunks:
add annc-tg-profile id=annc_tg_p; annc=N; ivr=Y; auto_answer=Y;
Step 4 Add a termination:
add termination prefix=ann/; port-start=0; port-end=30; type=trunk; mgw-id=ipunity_ms;
Step 5 Add a trunk group:
add trunk-grp id=1; call-agent-id=CA146; tg_type=annc; mgw-id=ipunity_ms; 
tg-profile-id=annc_tg_p; mgcp-pkg-type=AUDIO;
Step 6 Add a trunk:
add trunk cic-start=1; cic-end=30; tgn-id=1; termination-prefix=ann/; 
termination-port-start=0; termination-port-end=29; mgw-id=ipunity_ms;
Step 7 Add a route:
add route id=rt_annc; tgn1-id=1; tg-selection=LCR;
Step 8 Add a route guide:
add route id=rt_annc; tgn1-id=1; tg-selection=LCR;
Step 9 Add an IVR script profile for the NSA and NSA_ACT features:
add ivr-script-profile FNAME=NSA; IVR_ACCESS_MODE=IVR; IVR_ROUTE_GUIDE_ID=ivr_rg; 
IVR_SCRIPT_PKG_TYPE=BAU;
add ivr-script-profile FNAME=NSA_ACT; IVR_ACCESS_MODE=IVR; IVR_ROUTE_GUIDE_ID=ivr_rg; 
IVR_SCRIPT_PKG_TYPE=BAU;
Step 10 Place the trunks and other resources out of service (OOS):
control trunk-termination tgn-id=20; cic=all; mode=forced; target-state=OOS;
unequip trunk-termination tgn-id=20; cic=all;
control trunk-grp id=20; mode=forced; target-state=OOS;
control mgw id=ipunity_ms; mode=forced; target-state=OOS;
Step 11 Place the trunks and other resources in service (INS):
control mgw id=ipunity_ms; mode=forced; target-state=INS;
control trunk-grp id=20; mode=forced; target-state=INS;
equip trunk-termination tgn-id=20; cic=all;
control trunk-termination tgn-id=20; cic=all; mode=forced; target-state=INS;
Step 12 Verify the status of the resources:
status mgw id=ipunity_ms;
status trunk-grp id=20;
status tt tgn-id=20; cic=all;
Announcement Provisioning

This section explains how to specify the audio segments and audio sequences played by the IVR server.

Step 1 If not available, add the default language ID:
add language id=def;
Step 2 Add common audio segments:
add audio-segment; id=NSA; type=PHYSICAL; url=file://nsa.wav; description=No Solicitation;
add audio-segment; id=AGAIN; type=PHYSICAL; url=file://again.wav; description=again
add audio-segment; id=ANONYMOUS;type=PHYSICAL; url=file://anonymous.wav; 
description=anonymous;
add audio-segment; id=ARE; type=PHYSICAL; url=file://are.wav; description=are;
add audio-segment; id=DIAL; type=PHYSICAL; url=file://dial.wav; description=dial;
add audio-segment; id=ENTRIES; type=PHYSICAL; url=file://entries.wav; description=entries;
add audio-segment; id=ENTRY; type=PHYSICAL; url=file://entry.wav; description=entry;
add audio-segment; id=EXTENSION; type=PHYSICAL; url=file://extension.wav; 
description=extension;
add audio-segment; id=FROM; type=PHYSICAL; url=file://from.wav; description=from;
add audio-segment; id=INCLUDING; type=PHYSICAL; url=file://including.wav; 
description=including;
add audio-segment; id=IS; type=PHYSICAL; url=file://is.wav; description=is;
add audio-segment; id=NEXT; type=PHYSICAL; url=file://next.wav; description=next;
add audio-segment; id=NO; type=PHYSICAL; url=file://no.wav; description=no;
add audio-segment; id=OFF; type=PHYSICAL; url=file://off.wav; description=off;
add audio-segment; id=ON; type=PHYSICAL; url=file://on.wav; description=on;
add audio-segment; id=REPEATING; type=PHYSICAL; url=file://repeating.wav; 
description=repeating;
add audio-segment; id=THERE; type=PHYSICAL; url=file://there.wav; description=there;
add audio-segment; id=TO; type=PHYSICAL; url=file://to.wav; description=to;
add audio-segment; id=WILDCARD; type=PHYSICAL; url=file://wildcard.wav; 
description=wildcard;
add audio-segment; id=YOUR; type=PHYSICAL; url=file://your.wav; description=Your;
Step 3 Add NSA audio segments:
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;
Step 4 Add NSA_ACT authentication audio segment:
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_3_5; type=PHYSICAL; url=file://sle_3_5.wav; description=To hear 
these instructions repeated, dial 
add audio-segment; id=SLE_3_6; type=PHYSICAL; url=file://sle_3_6.wav; description=Please 
dial now.
add audio-segment; id=SLE_7; type=PHYSICAL; url=file://sle_7.wav; description=We are 
sorry, the digits dialed are not a valid command;
add audio-segment; id=SLE_8; type=PHYSICAL; url=file://sle_8.wav; description=We are 
sorry. The number you have dialed is incorrect;
add audio-segment; id=SLE_11_1; type=PHYSICAL; url=file://sle_11_1.wav; 
description=service is now;
add audio-segment; id=SLE_11_2; type=PHYSICAL; url=file://sle_11_2.wav; description=Please 
continue, dial;
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 