Table Of Contents
Numbering Plans and Dialing Procedures
E.164 Dialing Plan Implementation
Dial 1 Options for Local, Toll, and InterLATA Calls
Directory Services (411, 555-1212, 0+ Listing Services)
Information Service Calls (900 and 976)
n11 support (211, 311, 411, 511, 611, 711, 811)
Community Information and Referral Services (211)
Traffic and Transportation Information (511)
Telecommunications Relay Services (711)
NRUF Reporting for NANPA Audit Support
Important Provisioning Requirements
Emergency 911 Trunk Connection Loss Alarm
Numbers Used to Access Operator Services
Busy Line Verification (BLV) and Operator Interrupt (OI) Services
Active Call Information Display
Alerting Notification to Third-Party Feature Server
Calling Party Number Options for Outbound SETUP Messages
Option to Send Billing DN as CPN for Outbound Calls
Option to Send Billing DN as CPN for Emergency Calls
Option to Send Redirecting Number as CPN for Redirected Calls
Dialing Parity (IntraLATA Toll Presubscription)
Local Number Portability (LNP)
RFC 2833 DTMF Relay—Call Agent Controlled Mode
Availability of Legacy Behavior
Conditions for Sending LCO for RFC 2833 Telephone-Events
Technical Description of SIP Triggers
Terminology Used in This Section
Off-Hook Trigger (Delayed and Immediate)
Termination Attempt Triggers (TAT_1 and TAT_2)
Feature Interactions for OHD Trigger
Feature Interactions for TAT_1 and TAT_2 Triggers
T.38 Fax Relay, Modem, and TDD Handling
Understanding the Fax, Modem, and TDD Handling Feature
MGCP/NCS Interface—Fax Modes Supported
SDP Attributes Support for T.38 Fax Relay
MTA DQOS Support for T.38 Fax Relay
Fallback to Audio Media on T.38 Negotiation Failure
Audio Restore After Successful T.38 Fax Transmission
SDP Attributes Encoding Formats
CMTS Discovery Using the Static Subnet Table
Operational Recommendations for Porting Procedures
Near End Test Origination Test Calls
Testing Capability for 911 FGD-OS Trunks
Network Loopback Test for NCS/MGCP Subscriber Endpoints
Network Loopback Test for ISDN PRI Trunks
Network Features
Revised: July 21, 2008, OL-12606-18 (Release 5.0)The Cisco BTS 10200 Softswitch supports network features as described in the following sections:
•
Numbering Plans and Dialing Procedures—This section includes information on digit manipulation, E.164 dialing plan, casual dialing (dial around), dial 1 options, directory services, easily recognizable codes, Information service calls (900 and 976), n11 support (211, 311, 411, 511, 611, 711, 811). and NRUF reporting.
•
•
In general, BTS 10200 features delivered via gateway clients behave identically to their public switched telephone network (PSTN) counterparts.
Note
see Chapter 4, "Class of Service Restrictions and Outgoing Call Barring Features."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. The VSC values used throughout this chapter are for illustration purposes. For convenience, some VSC values are preprovisioned in the BTS 10200. The valid formats for VSC ASCII strings are listed in the Vertical Service Code commands in the Cisco BTS 10200 Softswitch CLI Database. To view the current VSC values provisioned on your system, use the show vsc CLI command. To provision VSCs, see the VSC provisioning procedure in the Cisco BTS 10200 Softswitch Provisioning Guide.
Typically, the system responds to user handset actions by providing an appropriate announcement. However, if an announcement is not provisioned or cannot be played, an alternate tone (for example, reorder tone) is played. Announcements are listed in the Cisco BTS 10200 Softswitch Provisioning Guide, and tones are listed in the Cisco BTS 10200 Softswitch Operations and Maintenance Guide.
Interoperability
The BTS 10200 interworks with a wide range of network elements (NEs), but there are certain limitations. Cisco recommends that you keep the following caution in mind as you prepare to purchase and use NEs for your network.
Caution
Numbering Plans and Dialing Procedures
The BTS 10200 supports the numbering plans and dialing procedures listed in Table 1-1. These features are described in the sections that follow.
Note
Table 1-1 Support for Numbering Plans and Dialing Procedures
ITU-T Recommendation E.164
GR-532-CORE
FSD-30-17-0000GR-2892-CORE
SR-2275, Sec. 3.3GR-532-CORE
FSD-30-16-0000
Digit Manipulation
The Digit Manipulation (DIGMAN) feature provides the ability to modify both calling number and called number for both incoming and outgoing calls within the BTS 10200.
The calling party number is also known as ANI (automatic number identification). The called party number is also known as DNIS (dialed number identification service).
In addition to modifying the calling number and the called number, the digit manipulation tables can be used to modify the nature of address (NOA) of ANI and/or DNIS numbers. This feature provides the following benefits in the service provider network:
•
•
•
For additional standards information, see the following industry sources:
•
•
The BTS 10200 performs digit manipulation by matching and replacing digits in the digit string that is being processed.
E.164 Dialing Plan Implementation
The BTS 10200 implements a dialing plan based on ITU-T Recommendation E.164, The International Public Telecommunication Numbering Plan, a standard for numbering and routing. This dialing plan uses a generic numbering scheme for number evaluation. The BTS 10200 performs digit manipulation on ANI data of the calling party, and on DNIS data of the called party.
National Number
In the E.164 numbering scheme, there are three parts to any national number (number that terminates within the country):
•
•
•
The combination [EC + DN] is called the subscriber number (SN).
The combination [NDC + EC + DN], or [NDC + SN], is called the national number (NN).[NDC + EC + DN] is interpreted as [NPA + NXX + XXXX] in NANP, where NPA (numbering plan area) = 200 to 999, NXX (office code) = 200 to 999, and XXXX = 0000 to 9999. The BTS 10200 applies the NANP interpretation if the NANP-DIAL-PLAN flag is set to Y (yes) in the DIAL-PLAN-PROFILE table.
A user originates a call by dialing as follows:
•
•
•
Examples of national prefixes include:
–
–
–
–
For countries that do not use NDCs, it is not necessary to provision any value for the NDC parameter in the BTS 10200.
International Number
The international number is the number dialed from one country to another to reach a subscriber. Each country is assigned a country code (CC). The international number is the combination [CC + NN], or [CC + NCD + EC + DN]. Table 1-2 lists several examples.
To place a call to a phone in another country, the caller must dial an international prefix and then the international number. Thus, the complete digit string to dial is [international prefix + CC + NN]. The international prefix varies from country to country. Examples of international prefixes include:
•
Example of a call from China to Montreal: 00-1-514-870-xxxx
•
Example of a call from the United States to Bruxelles: 011-32-02-123-xxxx
In some countries, two or more international prefixes may be used
•
•
Casual Dialing (Dial Around)
Casual dialing, also known as dial around, specifies whether the carrier supports 101XXXX calls. The digit map CLI command tokens provide the digit pattern. The digit pattern specifies all possible acceptable patterns. An example of a casual digit pattern is 1010321 or 1010220. The digit map table tells the media gateway (MGW) how to collect and report dialed digits to the Call Agent (CA). Subscribers can prefix their toll, interLATA, or international calls with 101XXXX. Casual dialing supports the following casual calls:
•
•
•
Dial 1 Options for Local, Toll, and InterLATA Calls
The service provider can provision the system to control the use of prefix 1 for specific types of calls and for specific subscribers. Local, toll, and interLATA call types can each be independently provisioned in the subscriber-profile table as follows:
•
•
•
For service access code (SAC) calls such as 500, 700, 800, and 900, the user must dial the prefix 1. The flags LOCAL-PFX1-OPT, INTERLATA-PFX1-OPT, and TOLL-PFX1-OPT in the Subscriber table do not affect these types of calls.
For a list of the specific provisioning parameters, see the Subscriber Profile table in the Cisco BTS 10200 Softswitch CLI Guide. For a complete list of release cause codes, see the Appendix of the Cisco BTS 10200 Softswitch Provisioning Guide.
Directory Services (411, 555-1212, 0+ Listing Services)
The BTS 10200 supports the directory services access feature as specified in Telcordia document GR-352-CORE, LSSGR: Interface To Directory Assistance Systems (FSD 30-17-0000).
Directory services allows a subscriber to obtain the listed telephone number for a given name and address. The caller dials a specific service number to reach directory services, also referred to as directory assistance (DA). When a subscriber dials one of the following digit patterns, the BTS 10200 routes the call to the applicable directory services in the PSTN:
•
•
•
•
•
The service to the caller can be provided manually by a live operator, automated via a voice or dual tone multifrequency (DTMF) recognition system, or by a combination of these. The volume level from an automated voice-response unit, however, should be comparable to that of a live operator. Different network operators can employ different systems in providing directory services.
A typical directory services request requires that the caller first give the name of the town and city. The caller then provides the name of the person or business that the caller wants to call, including the spelling of unusual names. Finally, the caller states if the request is for residence or business. Additional services include handling multiple requests made during the same call and automatic connection to the person (or business) the caller wants to call.
Easily Recognizable Codes
The BTS 10200 supports selected easily recognizable codes (ERCs) as described in document SR-2275, Telcordia Notes On the Network, Section 3.3. The supported ERCs are
•
•
•
•
Other Telcordia reference documents include:
•
•
Information Service Calls (900 and 976)
Information service calls (ISCs) provide a variety of announcement-related services on a national or local basis. There are two general categories of this service:
•
•
National calls are dialed as 1-900-xxx-xxxx and local calls are dialed as NPA-976-xxxx.
n11 support (211, 311, 411, 511, 611, 711, 811)
Note
This section describes BTS 10200 support for n11 services. The typical relationship between the n11 codes and the nature of dial (NOD) values is as follows.
For a complete list of NOD values, see the Nature of Dial command in the Cisco BTS 10200 Softswitch CLI Database. To view the current NOD values provisioned on your system, use the show nod CLI command.
For additional information on n11 calling, see the following industry documents:
•
•
Community Information and Referral Services (211)
The 211 service provides access to information from government service agencies and certain public charity groups.
Nonemergency Services (311)
Some city governments offer 311 service to provide nonemergency information to the community. The caller dials 311 and the Call Agent translates this to the closest nonemergency access office.
The BTS 10200 supports nonemergency services (311) for routing calls to a specified route type and identification. Routes for all nonemergencies (311) are allocated through the destination table by defining the call type (call-type=NON-EMG) and the routing information for the dialed digits.
Directory Assistance (411)
The 411 service provides directory assistance. See the "Directory Services (411, 555-1212, 0+ Listing Services)" section.
Traffic and Transportation Information (511)
The 511 service provides access to information about local traffic conditions.
Repair Service (611)
The 611 service connects to the local telephone repair service (if the service provider offers this service).
Telecommunications Relay Services (711)
The 711 service provides access to telecommunications relay services (TRS).
Local Billing Services (811)
The 811 service connects to the local telephone billing office.
NRUF Reporting for NANPA Audit Support
Numbering Resource Utilization and Forecast (NRUF) reporting provides NANPA audit data based on provisioned values in the dn2subscriber table. For FCC-required NANPA audit compliance, the report input is NPANXX. In markets outside of NANPA, the input can be based on either the combination of the NDC and the EC, or just the EC.
The data for NRUF reporting is generated based on either the NDC or the EC. The service provider can use the report dn-summary command to generate the following reports:
•
•
For additional details of this feature, see the NRUF chapter of the Command Line Interface Reference Guide.
Emergency Services (911)
The BTS 10200 supports emergency services (911) as specified in Telcordia document GR-529-CORE, LSSGR: Basic 911 Emergency Service (FSD 15-01-0000).
Other Telcordia reference documents include
•
•
This section covers the following topics:
•
•
•
•
•
Description
The digit string 911 is typically used in the U.S. Other digit strings are used elsewhere in the world.
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. The 3-digit 911 number is assigned for public use in many areas of the United States and Canada for reporting an emergency and requesting emergency assistance. Depending on municipal requirements and procedures, an ESB attendant can transfer the call to the proper agency, collect and relay emergency information to the agency, or dispatch emergency aid directly for one or more participating agencies.
911 calls are location dependent and must be selectively routed to the appropriate PSAP depending on where the call originates. The routing process is part of the Enhanced 911 (E911) feature set and works as follows:
1.
2.
Once the caller is connected to the PSAP attendant, the PSAP system typically displays the caller's directory number to the PSAP attendant. Additional data (such as the subscriber's name, address and closest emergency response units) may also be retrieved from the local carrier automatic location identification (ALI) database and displayed to the PSAP attendant.
The service provider can provision a flag for each subscriber to specify which number to send with emergency calls—the subscriber directory number or the subscriber billing number.
Special emergency functions can be provided via a channel-associated signaling (CAS) trunking gateway (TGW) that supports ESB trunks or emergency service line (ESL) trunks with MF signaling. Examples of special emergency functions include:
•
•
•
Important Provisioning Requirements
For service providers in the U.S., it is typical to provision the Destination table with call-type=EMG for the digit string 911, and call-subtype=NONE (default), because 911 is a central dispatch point for all emergency, ambulance, fire, and police calls.
Caution
Depending on the region of the world, the provisionable timers may require different values, or may not be needed, and they can be turned off. The called-party control feature, typically used in the United States, can also be turned off. All other functions of the emergency number are the same as for the 911 feature.
The emergency service feature can be made available to all subscriber lines connected to a BTS 10200 using the default office service ID, or to all subscribers in a specific POP using the office service ID. See the "Office Service ID and Default Office Service ID" section on page 3-134 for a general description of this provisionable service.
911 Overflow Announcement
The system plays an announcement when all circuits to the emergency center are busy and the emergency call cannot be completed to the emergency center. An example of an announcement for this feature is, "We are experiencing 911 difficulties. Please hang up and dial 0 to reach an operator for emergency assistance." The announcement is applied when the announcement resource is available and applicable. For the specific cause code and announcement ID, see "Appendix A, Cause Code to Announcement ID Mappings" in the Cisco BTS 10200 Softswitch Provisioning Guide.
Emergency 911 Trunk Connection Loss Alarm
The BTS 10200 is capable of generating a critical alarm of when an emergency trunk resource becomes remotely or locally blocked. This alarm will be raised when any of the following events occurs:
•
•
•
This feature is applicable only to emergency trunks of type CAS, SS7 and ISDN. The EMERGENCY-TRUNK-GROUP token in the applicable trunk group table must be provisioned to support this feature. For CAS trunk groups, the E911 / EMERGENCY-TRUNK token must also be provisioned.
Feature Interactions
The following feature interactions apply to emergency calls (call-type=EMG):
•
•
–
–
–
Feature Provisioning Commands
To provision this feature, see the 911 provisioning procedure in the Cisco BTS 10200 Softswitch Provisioning Guide.
Operator Services
The BTS 10200 supports operator services as specified in Telcordia Requirement FR-271, Operator Services Systems Generic Requirements (OSSGR).
Operator services is a call-processing function whereby callers can access either a live operator or an automated function to complete calls or gain access to information. The service provider can provide this feature or outsource it to a third-party vendor. Some additional functions accomplished by operator services include automatic call distribution, billing detail recording, and information retrieval.
This section includes the following additional topics:
•
•
Numbers Used to Access Operator Services
The following numbers are commonly used to access operator services:
•
•
•
•
•
•
Types of Services
Operator services provided to callers typically include:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Busy Line Verification (BLV) and Operator Interrupt (OI) Services
This section describes busy line verification (BLV) and operator interrupt (OI) services. OI is also referred to as emergency interrupt (EI). BLV and OI services are based on GR-1176 (FSD 80-01-0300), Busy Line Verification, part of Telcordia OSSGR requirements (FR-271).
Description and Operation
BLV service permits the user to obtain operator assistance to determine if a called line is in use. The user dials 0, waits for the operator to pick up the line, and requests BLV service. OI service permits the operator to speak directly with the busy party. The service provider can deny BLV service to any subscriber by setting type=denied for fname=BLV in the subscriber-feature-data table (see the BLV provisioning link listed below). Note that denying BLV also denies OI.
BLV and OI services work as follows:
1.
2.
3.
4.
5.
Note
The BLV feature can be made available to all subscribers lines connected to a BTS 10200 using the default office service ID, or to all subscribers in a specific POP using the office service ID. See the "Office Service ID and Default Office Service ID" section on page 3-134 for a general description of this provisionable service.
Feature Interactions
The following feature interactions are applicable to the BLV and OI services:
•
•
Feature Provisioning Commands
To provision this feature, see the BLV provisioning procedure in the Cisco BTS 10200 Softswitch Provisioning Guide.
Network Services
The BTS 10200 supports the network services listed in Table 1-3.
8XX (Toll-Free Calling)
The purpose of the toll-free feature is to have the called party, rather than the calling party, charged for the call. These calls are prefixed with the 1+8XX service access codes. The seven digits following the 8XX codes are used for routing the call. For an inbound/outbound 8XX call, the BTS 10200 checks the local toll-free database first. If the corresponding DN is not found in the local toll-free database, the system sends a query to the service control point (SCP) to request the corresponding DN.
All aspects of toll-free calling are transparent to the caller. A caller expects to dial 1-8XX-NXX-XXXX to reach the desired destination. The company that translates the number to a specific DN, and the company that routes the call, must appear transparent to callers. Most callers are not aware that their dialed 8XX number is changed into a specific DN. What matters to the callers is that they reach what they perceive to be the called number, and they are not billed for the call.
Note
8XX Call Processing
The system processes outbound 8XX calls as follows:
1.
2.
3.
Note
4.
Note
Figure 1-1 shows the processing of an outbound 8XX call placed by a subscriber.
Figure 1-1 Processing of an Outbound 8XX Call
Notes for Figure 1-11.
2.
3.
4.
Figure 1-2 shows the processing of an 8XX call received from the network with a network-specific NOA.
Figure 1-2 Processing of an 8XX Call with a Network-Specific NOA
Notes for Figure 1-21.
2.
3.
Local Toll-Free Database
This section explains how the system uses information from the local toll-free database.
The BTS 10200 provides the ability to translate inbound/outbound 8XX numbers at the Feature Server (FS) using a local 8XX database. The 8XX service supports the following features:
•
•
•
•
•
The BTS 10200 also supports optional DNIS service. In an 8XX DNIS service, when a call is terminated to a PBX (call center), 4 digits are outpulsed to the PBX to identify the originally dialed 8XX number. In case of custom DNIS, up to 22 digits can be outpulsed with additional information such as:
•
•
•
When a translated number (for an original 8XX call) is received, the Analyzed Info DP triggers the FS. The BTS 10200 looks up the DNIS and TG information for the call. The DNIS information is then outpulsed to the PBX. If an overflow condition is encountered, the call is routed to the overflow trunk. The overflow trunk can be a PSTN trunk.
See SR-2275, Telcordia Notes on the Network, Section 14.6 for additional information on toll-free database services.
SCP-Based Toll-Free Services
This section explains how the system uses information from the external toll-free database.
The BTS 10200 communicates with an SCP-based database called the toll-free database service, which contains information for routing the call. The database service provides information about the network service provider selected to complete the call, and information for translating the toll-free number to a specific 10-digit directory number (DN). The routing of the call can vary depending on the arrangements made between the toll-free subscriber and the network service provider. These arrangements can include selective routing based on the time of day, day of week, and location from which the call originates.
Provisioning Commands
To provision this feature, see the 8XX (Toll-Free Calling) provisioning procedure in the Cisco BTS 10200 Softswitch Provisioning Guide.
Active Call Information Display
The BTS 10200 allows the service provider to display information about an active (in-progress) call (originating or terminating). The implementation is based on Telcordia document GR-529-CORE, Call Tracing (FSD 15-03-000). The display is performed using a CLI query command.
The input parameter can be any subscriber-specific or trunk-specific information including:
•
–
–
–
–
–
•
–
–
–
The system output (display) includes available information about the calling and called parties (for example, calling number, called number, call state, trunk type, call ID, charge number, and redirected number). The system supports both brief and verbose display modes.
For additional information about required inputs and available outputs, see the "Viewing Active Calls" information in the Cisco BTS 10200 Softswitch Operations and Maintenance Guide.
Alerting Notification to Third-Party Feature Server
The BTS 10200 can be provisioned to deliver alerting notification (notification of power ringing or call-waiting tone on the subscriber line) and call data to a third-party feature server (3PTYFS). This feature is available for both off-net-to-on-net calls and on-net-to-on-net calls. It can be assigned globally (for all subscribers on the switch), on a per-POP basis, or for individual subscribers. The feature supports advertising of an externally addressable FQDN to an external third-party feature server when necessary. 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.
Note
This document does not describe the messaging interface specs or call-data fields provided by the BTS 10200. Developers of applications for the 3PTYFS who are interested in the interface specifications should contact their Cisco account team.
Call Flow
The call flow works as follows:
1.
2.
3.
Alerting Notification has no impact on the setup or progress of the call. The BTS 10200 continues with normal call processing regardless of any response from the 3PTYFS.
Prerequisites
The BTS 10200 locates the 3PTYFS via a TSAP address that is provisioned in the BTS 10200 database. If the TSAP address is a domain name, the domain name must also be configured in the service provider domain name system (DNS) server.
The BTS 10200 advertises its own TSAP address to the 3PTYFS. There are specific requirements for entering this information during initial software installation. For details, see the "Installation Considerations" section.
The 3PTYFS should be provisioned to support this feature in accordance with the applicable product documentation. The BTS 10200 does not send any provisioning or status/control commands to the 3PTYFS.
Caution
Restrictions and Limitations
CALL_ACCEPTED_NOTIFY Trigger Sent for Incoming Calls to Subscribers OnlyThe system sends the CALL_ACCEPTED_NOTIFY trigger to the 3PTYFS only if the called party is a subscriber on the BTS 10200. This is true even if the feature is provisioned globally (at the office level) on the BTS 10200.
Limitations when Calling Party Is Using Certain SIP and H.323 DevicesSome calling-party devices (certain SIP- and H.323-based endpoints) may not send an explicit alerting indication (180 Ringing for SIP and Alerting for H.323). In these cases, the Call Agent does not report the CALL_ACCEPTED_NOTIFY trigger to the 3PTYFS.
Subsequent TriggersThe BTS 10200 does not send updated information to the 3PTYFS based on subsequent triggers in the call (following the CALL_ACCEPTED TDP). For example, if a user hangs up while another call is on hold (in call-waiting mode) and the phone is rung again, the BTS 10200 does not report a trigger and does not send any data.
NAPTER and SRV Record Lookup Not SupportedThis feature does not support the use of the Naming Authority Pointer (NAPTR) or DNS services (SRV) records for lookup of the 3PTYFS domain name. The DNS server must be populated with the address (A) record for the fully qualified domain name (FQDN) specified in the TSAP address of the 3PTYFS.
Status and Control CommandsThe status feature-server command reports the status of feature server components internal to the BTS 10200. However, the BTS 10200 does not send any status or control commands to the 3PTYFS.
Installation Considerations
For Alerting Notification to function correctly, specific data must be entered into the opticall.cfg file at the time of initial BTS 10200 software installation. The choice of data depends on whether the 3PTYFS will be deployed in the same private (internal) management network as the BTS 10200, or in a public network.
•
•
This installation data also affects the provisioning requirements for the 3PTYFS in the Feature Server table:
•
•
Note
Feature Provisioning Commands
For provisioning steps, see the Alerting Notification provisioning procedure in the Cisco_BTS 10200 Softswitch Provisioning Guide.
Calling Party Number Options for Outbound SETUP Messages
The BTS 10200 provides options for controlling the calling party number (CPN) data sent in the outbound SETUP message on calls outbound or redirected from the BTS 10200 to the PSTN.
Option to Send Billing DN as CPN for Outbound Calls
The system has a provisionable option for sending a subscriber billing DN (or main DN of a PBX subscriber) as the CPN in outbound SETUP messages on outgoing nonemergency calls. This is provisionable using the SEND-BDN-AS-CPN token in the Subscriber table.
•
•
The sending of the subscriber name and number is subject to the provisioning of the PRIVACY token in the Subscriber table.
Option to Send Billing DN as CPN for Emergency Calls
The system has a provisionable option for sending a subscriber billing DN (or main DN of a PBX subscriber) as the CPN in outbound SETUP messages on outgoing emergency calls. This is provisionable using the SEND-BDN-FOR-EMG token in the Subscriber table.
Note
•
•
The system sends the main subscriber number, if it is provisioned, according to the following rules:
•
•
Option to Send Redirecting Number as CPN for Redirected Calls
This feature allows the service provider to control the CPN data sent in the outbound SETUP message on redirected calls outbound from the BTS 10200 to the PSTN.
The CPN option is provisionable (via CLI commands) using the SEND-RDN-AS-CPN token in the TRUNK-GRP table:
•
•
N is the default value.This feature is applicable to the following scenarios:
•
•
Redirection by a Subscriber Phone
Figure 1-3 shows an example of the networks and phones involved in redirection by a subscriber phone. Table 1-4 explains how to provision the SEND-RDN-AS-CPN token for various call-redirection scenarios and results.
Figure 1-3 General Network View for Redirection by a Subscriber Phone
Table 1-4 Provisioning SEND-RDN-AS-CPN in TRUNK-GRP Table for Redirection by Subscriber Phone
CPN and RDN
Data
(Example)
Provisioned for SEND-RDN-
AS-CPN
Outbound
SETUP
MessageOn-net to off-net call (either of the following):
A -> B -> fwd -> C -> fwd -> off-net
A -> C -> fwd -> off-net
CPN=
972-555-1111RDN=
972-555-3333Y
Overwrite CPN
with RDNCPN=
972-555-3333RDN=
972-555-3333N
Do not change CPN
CPN=
972-555-1111RDN=
972-555-3333Off-net to on-net to off-net call:
Inbound off-net call -> B -> fwd -> off-net
Note
(from the incoming SETUP message)
is 817-555-8888.
The new RDN is the DN of the forwarding phone, Subscriber B—972-555-2222.CPN=
214-555-7777RDN=
817-555-8888(from incoming SETUP message)
Y
Overwrite CPN
with RDNCPN=
972-555-2222RDN=
972-555-2222N
Do not change CPN
CPN=
214-555-7777RDN=
972-555-2222
Redirection of a Basic or Tandem Call
Figure 1-4 illustrates the redirection of a basic or Tandem call.
Figure 1-4 Example of Redirection of Basic or Tandem Call
Notes for Figure 1-4•
•
•
•
•
Table 1-5 Provisioning SEND-RDN-AS-CPN in TRUNK-GRP Table for Redirection of Basic/Tandem Call
Provisioned for SEND-RDN-
AS-CPN(Default = N)
Outbound
SETUP
Message
