-
Provisioning Guide
-
Preface
-
Chapter 1 - Provisioning Overview
-
Chapter 2 - Initial Softswitch Provisioning
-
Chapter 3 - IAD Residential Subscriber Provisioning
-
Chapter 4 - ATA 18x Residential Subscriber Provisioning
-
Chapter 5 - Cable Subscriber Provisioning
-
Chapter 6 - CALEA Provisioning
-
Chapter 7 - Feature Provisioning
-
Chapter 8 - Centrex, MLHG, and Voice Mail Provisioning
-
Chapter 9 - Route Provisioning
-
Chapter 10 - Announcement Server Provisioning
-
Chapter 11 - Provisioning Channel-Associated Signaling
-
Chapter 12 - SS7 Provisioning
-
Chapter 13 - H.323 Provisioning
-
Chapter 14 - SIP Subscriber Provisioning
-
Chapter 15 - ENUM Provisioning
-
Appendix A - Cause Code to Announcement ID Mappings
-
Appendix B - Use Dial Plan Token Routing Impact
-
Appendix C - National Call Type Processing
-
Appendix D - Factory Installed Scripts
-
Appendix E - Defined Cause Codes
-
Appendix F - Admission Reject Cause Code Mapping
-
Appendix G - H323 Trunk Group Cause Code Mapping
-
Appendix H - Session Initiation Protocol Cause Code Mapping
-
Appendix I - Sample Asia Provisioning Script
-
Table Of Contents
Vertical Service Code Provisioning
NANP Dial Plan VSC Provisioning
Non-NANP Dial Plan VSC Provisioning for Subscriber and Centrex
Configurable Default Values for Subscriber Provisioning
Provisioning the Default Value for an Optional Token
Checking the Integrity of the Configured Default Value
Provisioning a Default Value using a Command Alias
Viewing the Factory Default Value
Restoring a Factory Default Value
Add 8XX to the Office Service IDs
Active Call Information Display
Alerting Notification to Third Party Feature Server
Precedence for Provisioned Values
Anonymous Call Rejection and A/D
Alternate Activation and Deactivation Method
Office Provisioning—Call Forwarding for Unreachable Condition
Alternate Activation and Deactivation Method
Alternate Way to Activate and Deactivate CFC
Alternate Activation and Deactivation Method
Alternate Activation and Deactivation Method
Call Forwarding Variable for Basic Business Groups
Alternate Activation and Deactivation Method
Alternate Activation and Deactivation Method
Alternate Activation and Deactivation Method
Alternate Activation and Deactivation Method
Calling Line Identity Presentation, Restriction
Calling Number Delivery Blocking
Caller Identity Delivery Suppression-Delivery
Caller Identity Delivery Suppression-Suppression
Provisioning for IVR Collection of Account/Authorization Codes
Direct Call Pickup Without Barge-In
Direct Call Pickup With Barge-In (DPU)
Distinctive Alerting/Call Waiting Indication
Alternate Activation and Deactivation Method
Group Speed Call: 1-Digit and 2-Digit
Alternate Activation and Deactivation Method
Incoming Simulated Facility Group
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
Local Number Portability for ANSI/North America
Local Number Portability for ITU Local BTS Database Query
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
Multi-Lingual Support for Interactive Voice Response and Announcements
Provisioning Feature Control Options for the IVR Interactions
On-Net Routing and Local Number Portability for Inter-PacketCable Cable Management Server Routing
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-Cisco BTS 10200 Softswitches
Provisioning Inter-CMS with NRS—Same Cisco BTS 10200 Softswitch Acting as CMS and MGC
Selectively Provisioning LNP Queries (Allow or Disallow) for a Particular Call Type
Alternate Activation and Deactivation Method
Provisioning Notes and Caveats
Outgoing Call Barring—Activation, Deactivation, and Interrogation
Alternate Activation and Deactivation Method
Outgoing Simulated Facility Group
Own Calling Number Announcement
Remote Activation of Call Forwarding and PIN_Change
Screen List Editing: SCF, SCR, SCA, and DRCW
Non-IVR Activation and Deactivation of SCA, SCF, SCR, and DRCW
Alternate Activation and Deactivation Method
Seasonal Suspend Provisioning for MR1 and Earlier
Provisioning Options for Inbound Call Treatment
Provisioning Options for Outbound Call Treatment
Turning Off (Deactivating) Seasonal Suspend
Troubleshooting, MR1 and Earlier
Seasonal Suspend Provisioning for MR1.1 and Later
Provisioning Options for Inbound Call Treatment
Provisioning Options for Outbound Call Treatment
Turning Off (Deactivating) Seasonal Suspend
Troubleshooting, MR1.1 and Later
Speed Call (1-Digit and 2-Digit) and Activation
Terminal and Group Make Busy Services
Usage Sensitive Three-Way Calling
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
Alternate Way of Activating and Deactivating VM and VMA
Provision an Office Service ID for a POP
Feature Provisioning
Revised: November 25, 2008, OL-12777-08This chapter describes the CLI provisioning commands necessary for offering supplementary features to a subscriber line and is limited to the Feature Server components of the Cisco BTS 10200 Softswitch. All the necessary steps required to provision the supplementary features offered by the Feature Servers are described in the recommended order; however, only the essential tokens are included in the examples.
The following sections outline the structure of this chapter, the conventions used, and the assumptions that are made. The provisioning procedures are grouped as follows:
•
Feature Provisioning—Provisioning procedures to set up a feature server on the network.
•
•
•
•
•
Note
Tip
The individual procedures for provisioning each supplementary feature are structured as follows:
•
This is a one-time procedure performed during initial softswitch configuration and, under normal circumstances, it is not required at any other point during system operation.
•
Network resources include the Call Agent, Feature Servers, media gateways, trunks, and terminations. Resource provisioning, under normal circumstances, is done one time during the initial softswitch configuration and is not required at other points during system operation.
•
•
If any of these elements do not apply in any individual procedure, they are eliminated. Each provisioning task is presented in a procedural format, with a sequence of provisioning steps.
Conventions
This section outlines additional conventions used only within this chapter. Refer to the Preface for all other conventions.
1.
•
•
•
2.
Assumptions
The following specific assumptions are made in this chapter:
•
•
•
•
–
–
•
Vertical Service Codes
Some features can be accessed and controlled by the subscriber using a handset and vertical service codes (VSCs). VSCs are provisionable by the service provider (any valid unique ASCII string up to five characters long), and the customary values are country specific.
For convenience, some VSC values are preprovisioned in the Cisco BTS 10200 Softswitch. The valid formats for VSC ASCII strings are listed in the VSC table specification in the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide. The preprovisioned VSC values are listed in the Vertical Service Code appendix of the same document.
Note
Vertical Service Code Provisioning
This section supplements the feature provisioning sections for features that can be invoked with a VSC.
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:
•
•
Note
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 10200 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 10200 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
add/change digit-map; id=digit-map-1; DIGIT_PATTERN=[regular digit pattern]|*xx|11xx|[regular digit pattern];
Note
Step 2
add/change digit-map; id=digit-map-ctx; DIGIT_PATTERN=[regular Centrex digit pattern]|*xx|11xx|[regular Centrex digit pattern];
Note
Step 3
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/change dial-plan-profile ID=dpp1; DESCRIPTION=dialing plan profile ID2; NANP_DIAL_PLAN=Y;Step 5
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
add/change digit-map id=digit-map-1; DIGIT_PATTERN=[regular digit pattern]|[*,#]xx{*,#]|[regular digit pattern];
Note
Note
*XX*
*XX#
#XX#
*#XX*
*#XX#Step 2
add/change digit-map id=digit-map-ctx; DIGIT_PATTERN=[regular Centrex digit pattern]|[*,#]xx[*,#]|*#xx[*,#]|[regular Centrex digit pattern];
Note
Step 3
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/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
add/change dial-plan-profile ID=dpp1; DESCRIPTION=dialing plan profile ID2; NANP_DIAL_PLAN=N; DNIS_DIGMAN_ID=pretrans;Step 6
add/change vsc digit-string=*57*; fname=CFUA;add/change cdp digit-string=*57*; fname=CFUA; cdp-id=cdp1; cat-string=11111111111; nod=VSC;
Configurable Default Values for Subscriber Provisioning
The Configurable Default Values for Subscriber Provisioning feature provides the following capabilities:
•
•
•
•
This feature is automatically enabled after Cisco BTS 10200 Softswitch installation. After upgrading, the existing configured default values are preserved.
Note
Provisioning the Default Value for an Optional Token
The following example provisions the default value for the es_supp token in the AGGR table.
Step 1
show var_default noun=aggr; var_name=es_supp;Reply:Success: Database is void of entriesStep 2
add var_default noun=aggr; var_name=es_supp; def_vals=Y;Step 3
show var_default noun=aggr; var_name=es_supp;NOUN=aggrVAR_NAME=es_suppDEF_VALS=YReply:Success:Entry 1 of 1 returned.
Checking the Integrity of the Configured Default Value
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
Provisioning a Default Value using a Command Alias
The Configurable Default Values for Subscriber Provisioning feature enables a command alias to be used 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
add var_default noun=sub; var_name=term_type; def_vals=SIP;Reply:Success:CLI add succesfullyStep 2
show var_default noun=sub; var_name=term_type;NOUN=subscriberVAR_NAME=term_typeDEF_VALS=SIPReply:Success:Entry 1 of 1 returned.
Viewing the Factory Default Value
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=subscriberVAR_NAME=term_typeBTS_DEFAULT=TERMDEF_VALS=TGReply:Success:Entry 1 of 1 returned.Restoring a Factory Default Value
BTS 10200 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 the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
change feature fname=OCB; type1=pin-len; value1=5; type2=to; value2=2-; type3=fail-cnt; value3=4; type4=lock-out; value4=60;
Note
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts4_2/sipdocs/sipadmin/9usrappa.htm
Note
--- For call-waiting features, the system supports CWD, but not CW or CIDCW
--- For three-way-calling features, the system supports TWCD, but not TWC or USTWC
8XX (Toll-Free Calling)
This section explains how to provision outbound toll-free calling for subscribers on the Cisco BTS 10200 Softswitch. Toll-free calling in North America usually involves an 8XX number.
Tip
Office Provisioning
This section explains how to create the 8XX feature and apply it to a dial plan. It also shows how to provision the translation of an 8XX number to a local DN.
Step 1
add feature fname=8XX; tdp1=COLLECTED_INFORMATION; tid1=SPECIFIC_DIGIT_STRING; ttype1=R; description=toll-free; feature_server_id=FSAIN205;Step 2
add destination dest-id=dest800; call-type=TOLL_FREE; route-type=SUB;Step 3
add dial-plan-profile ID=dp1;Step 4
Caution
Tip
add dial-plan ID=dp1; digit-string=800; dest-id=dest800;Step 5
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
a.
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.
show service id=ABC;The system displays the features that are in this service table.
c.
add/change service id=ABC; fname9=8XX;Step 2
a.
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
b.
show service id=XYZ;The system displays the features that are in this service table.
c.
add/change service id=XYZ; fname9=8XX;Provisioning Resources
These steps explain how to provision the resources to enable an SCP query.
Step 1
add sg id=sg_1; description=signaling gateway 1;Step 2
add sg-grp id=sg_grp1; sg1-id=sg_1; description=signaling gateway group 1;Step 3
add sgp id=itp_7507_1; sg-id=sg_1; description=ITP 7507 for sg_1;Step 4
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
Step 5
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; dscp=NONE; ip_tos_precedence=FLASH; local_rcvwin=64000; max_init_retrans=5; max_init_rto=1000; platform_id=FSAIN205;Step 6
add dpc id=stp1; point-code=1-101-0; description=STP1 MGTS STP;Step 7
add/change sccp-nw id=1; net-ind=NATIONAL; sub-svc=NATIONAL; hop-count=10;Step 8
add subsystem-grp id=SSN_TF; platform-id=FSAIN205; tcap-version=ANS92;Step 9
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 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 sccp-route opc_id=opc; dpc_id=stp1; ssn_id=SSN_TF; rk_id=rk_tf;Step 12
add slhr-profile id=slhr_tf;Step 13
add slhr id=slhr_tf; opc_id=opc; dpc_id=stp1; rk_id=rk_tf; ssn_id=SSN_TF; gtt-req=Y; tt=254; gtt-addr-type=CDPN; gtt-addr=3;Step 14
add ca-config type=DEFAULT-TOLL-FREE-SLHR-ID; datatype=string; value=slhr_tf;Step 15
control sctp-assoc id=sctp_assoc1; mode=forced; target-state=INS;Step 16
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
Emergency service is a public safety feature providing emergency call routing to a designated Emergency Service Bureau (ESB), normally called the public safety answering point (PSAP) in the United States.
Tip
The following section identifies the steps necessary to offer 911 Emergency Service.
Office Provisioning
Step 1
add/change feature; fname=911; tdp1=COLLECTED_INFORMATION; tid1=911_TRIGGER; ttype1=R; description=Emergency Service; feature_server_id=FSPTC235;Step 2
change ca-config type=DEFAULT-OFFICE-SERVICE-ID; datatype=string; value=469;Step 3
change ca-config type=E911-CALLED-PARTY-HOLD; datatype=boolean; value=Y;Step 4
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 service id=469; FNAME1=911;
Provisioning Resources
Step 1
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 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 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 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 termination prefix=cas/911/; mgw-id=224.14:2434; type=TRUNK; port-start=1; port-end=24;Step 6
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 route id=ops911; tgn1-id=911;Step 8
add route-guide id=ops911; policy-type=route; policy-id=ops911;Step 9
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 dial-plan id=dpcas; digit-string=911; dest-id=ops911odr; min-digits=3; max-digits=3;
Media Gateway Setup
The Cisco BTS 10200 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 10200 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
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:2434ADMIN STATUS -> ADMIN_INSOPER STATUS -> MGW_STATUS_UPStep 2
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 -> 911ADMIN STATUS -> ADMIN_INSOPER STATUS -> TG_INSStep 3
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 -> 1TERM ADMIN STATUS -> ADMIN_INSTERM OPER STATUS -> TERM_STATE_EQUIPCIC STATIC STATE -> ACTVCIC DYNAMIC STATE -> IDLECONFIGURATION COMMAND EXECUTED CAS_TRUNK_GROUP -> 911 -> CIC -> 2TERM ADMIN STATUS -> ADMIN_INSTERM OPER STATUS -> TERM_STATE_EQUIPCIC STATIC STATE -> ACTVCIC DYNAMIC STATE -> IDLE...CONFIGURATION COMMAND EXECUTED CAS_TRUNK_GROUP -> 911 -> CIC -> 24TERM ADMIN STATUS -> ADMIN_INSTERM OPER STATUS -> TERM_STATE_EQUIPCIC STATIC STATE -> ACTVCIC DYNAMIC STATE -> IDLEThis 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
Step 2
MLHG provisioning is similar to subscriber provisioning as described above.
Active Call Information Display
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
The Cisco BTS 10200 Softswitch delivers alerting notification and call data to a third-party feature server (3PTYFS). The service provider can use appropriately designed and configured feature servers to make use of this notification and data to provide value-added services to subscribers; for example, delivery of caller ID on a subscriber television or computer screen.
For a complete description of this feature, refer to "Alerting Notification to Third Party Feature Servers" in the Network and Subscriber Feature Descriptions.
This document is intended for service provider technicians and engineers who are installing, provisioning, and deploying the Cisco BTS 10200 Softswitch and 3PTYFS in their network.
This section describes the steps required to provision support for Alerting Notification on Cisco BTS 10200 Softswitch. This includes provisioning the Cisco BTS 10200 Softswitch database with the TSAP address of the 3PTYFS, the feature trigger point, and the services with which the feature is offered.
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:
•
