Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco BTS 10200 Softswitch

Single Number Reach

Downloads

Table Of Contents

Cisco BTS 10200 Softswitch Single Number Reach Feature Module

Understanding the Single Number Reach Feature

Single Number Reach Feature Description

Follow-me

Find-me

SNR_ACT Feature

Feature Interactions

Prerequisites

Provisioning

Office Provisioning

Resource Provisioning

Announcement Provisioning

Feature Control Options for Provisioning IVR Interactions

Subscriber Provisioning

SNR_ACT IVR Virtual Subscriber Provisioning

Operations

Operator CLI Interface

Single Number Reach Feature-Config and Feature-Config-Base Table

SNR_ACT Feature-Config and Feature-Config-Base Table

Subscriber Feature Data Table

SNR Table

Single Number Reach XML Schema

Subscriber Web-Based Interface

Subscriber IVR-Based Interface

Accessing the Single Number Reach IVR Menu

IVR Authentication

Single Number Reach Main Menu

Single Number Reach (Forwarding Per Schedule) Activation

CFU Activation

VMA Activation

Single Number Reach Deactivation

Single Number Reach IVR Prompts

Billing

Measurements


Cisco BTS 10200 Softswitch Single Number Reach Feature Module

Revised: July 31, 2008

This document describes the Single Number Reach feature for Release 6.0 MR1 of the Cisco BTS 10200 Softswitch and explains how to use it. It includes the following topics:

•Understanding the Single Number Reach Feature

•Provisioning

•Operations

•Billing

•Measurements

Understanding the Single Number Reach Feature

Single Number Reach allows the subscriber to unify subscriber services and features by using one master routing number to reach a subscriber. Subscribers can be reached at one or multiple user endpoints (UEs), even if those UEs belong to a different service provider. You can assign Single Number Reach to subscribers with physical UEs, or virtual subscribers without physical UEs. Use Single Number Reach to allow the following:

•Multiple UEs to be reached via the same number

•Individual UEs with multiple access mechanisms to have the same number

Single Number Reach does the following:

•Incoming calls are sent to voice mail.

•Incoming calls are sent to a single destination number.

•Incoming calls are routed to UE(s) based on forwarding schedules in the order provisioned by the subscriber. See Find-me.

Single Number Reach Feature Description

The Single Number Reach feature enhances Follow-me while adding Find-me.

Follow-me

Single Number Reach works with follow-me which uses the Call Forwarding Unconditional (CFU) and Voice Mail Always (VMA) features. When the Follow-me feature is active and the forwarding number is present, the Follow-me feature forwards the incoming call to the forwarding number unconditionally. See Cisco BTS 10200 Softswitch Network and Subscriber Feature Descriptions, Release 6.0.x. for more on CFU and VMA.

Follow-me can only be associated with a subscriber's master number. As long as the master number is not assigned to a virtual subscriber, subscribers can enter vertical service codes (VSCs) to change CFU and VMA configuration from the UE associated with their master number.

Subscribers provision CFU and VMA using the interactive voice response (IVR) interface or web-based interface. See "SNR_ACT Feature" section and "Subscriber Web-Based Interface" section.

Figure 1 provides an illustration of the follow-me feature for both virtual and nonvirtual numbers.

Figure 1 Single Number Reach - Follow-me Feature

Find-me

The Find-me feature is a search feature that is set depending on one's holiday, time of day (TOD), or end of day (EOD) schedules. Find-me is a multi CFU that branches a call depending on the assigned schedule that the user predefines. The system rings each idle line as defined in the schedule. When a call is answered on one device, all other dialed calls are terminated or cancelled.

Using Single Number Reach's address book of 10 UEs, the subscriber chooses combinations of UEs to ring at different times of day and holidays or vacations. When find-me is active, each UE in the group begins ringing. If the call is answered, all UEs stop ringing. If unanswered, when the ring maximum is reached, the call goes to voice mail. Callers hear an announcement saying we are trying to reach the desired party. After the announcement, they hear the ringback tone.

UEs in the find-me group schedules have subscriber-provisionable ring delays. Subscribers can set the following parameters:

•Delay until ringing starts—0-15 seconds, where 0 means ring immediately.

•Number of rings—0-15, where

–15 means continue ringing indefinitely until a system or device timeout is reached.

–0 means do not ring this UE. Use 0 to temporarily prevent calling a UE without removing the UE from the schedule.

•Ring Type—0-7

Find-me can be associated only with a subscriber's master number. One master number can be associated with the following schedules:

•Six time of day (TOD) schedules that allow up to 7 UEs from the subscriber's address book.

•One holiday schedule that allows up to 7 DNs or AORs and up to 18 holiday entries.

Each schedule has a priority. When schedules overlap, the one with higher priority takes precedence.

If a subscriber has answered a find-me call and subsequent calls are made to the master number, these later calls are controlled using the ALLOW-MULTIPLE-INVOCATIONS feature_config and snr_profile flags. See "Single Number Reach Feature-Config and Feature-Config-Base Table" section.

Find-me is mainly provisioned using the web-based interface. The IVR interface just provides activation or deactivation of the feature. See the "SNR_ACT Feature" section and to the "Subscriber Web-Based Interface" section.

Figure 2 shows the illustration of the find-me feature for both virtual and non-virtual numbers.

Figure 2 Single Number Reach - Find-me Feature

SNR_ACT Feature

The SNR activation (SNR_ACT) enables the SNR. It activates the Follow-me, Find-me, and VMA features. The SNR_ACT uses the IVR server. If the IVR server is not working and accessible, SNR_ACT does not work. Using the Single Number Reach IVR interface, SNR_ACT allows subscribers to do the following:

•Activate and deactivate Single Number Reach

•Activate and deactivate VMA

•Activate and deactivate CFU

•Configure the CFU forwarding number

CFU, VMA, and Single Number Reach are mutually exclusive when a subscriber provisions them using the IVR; activating one of them deactivates the others. When a subscriber activates the CFU, VMA or Single Number Reach through the IVR, a check ensures that the feature to be activated is assigned to the subscriber.

Virtual subscribers cannot simultaneously deactivate all three Single Number Reach modes using the IVR. (Virtual subscribers have a termination type (term-type)=none. For example, the subscriber associated with the master number has term-type=none.) The system requires that at least VMA be active; otherwise calls to the master number fail.

To access the IVR interface, a subscriber needs a user ID (master number) and a personal identification number (PIN). Most phones support entering digits (letters or characters) into an IVR system; therefore, the master number is always a DN and not an AOR.

The PIN is not used to access the web-based interface, however the subscriber can reset their PIN via the web-based interface. See "Subscriber Web-Based Interface" section.

Feature Interactions

Table 1 describes feature interaction between Single Number Reach and existing features.

Table 1 Single Number Reach (Find-me) Feature Interaction Matrix 

Feature
Interaction on Master Number
Interaction
on the
Forked Calls
Impacted
Module(s)

911

Not applicable.

No impact

—

Anonymous Call Rejection (ACR)

No impact. ACR occurs before Single Number Reach.

No impact.

—

Automatic Callback (AC)

When subscriber activates AC toward the Single Number Reach master number, then the following conditions are true:

If Single Number Reach number is a virtual, destination switch that cannot monitor a virtual subscriber, Then treat as nonunique.

If the Single Number Reach number is physical, the destination switch performs normal processing if the number is local. Otherwise, it is off-net or pstn; then it is not applicable.

When a subscriber activates AC and he or she is:

Virtual - Not applicable.

Physical - originating switch performs normal processing.

Single Number Reach feature does not get invoke for the AC ringback call.

No impact.

Plain old telephone service (POTS), Basic Call module (BCM)

Automatic Recall (AR)

When a subscriber activates the AR toward the Single Number Reach master number then the following conditions are true:

If the Single Number Reach master number is a virtual number, then the destination switch cannot monitor the virtual subscriber. Treat as non-unique.

The Single Number Reach master number is physical, the destination switch performs the normal processing if the number is local. Otherwise, it is off-net or pstn; then it is not applicable.

When the subscriber activates AR and he or she is:

Virtual number- Not applicable.

Physical - originating switch performs normal processing.

Single Number Reach feature does not get invoke for the AR ringback call.

No impact.

POTS, BCM

Busy Line Verification (BLV)

Single Number Reach is inhibited when BLV is invoked on the master number.

Not applicable.

POTS

Call Block (CBLK)

Not applicable. CBLK originating with starcode.

Invocation is the same as SCR.

No impact.

—

Call Forwarding Busy (CFB)

Single Number Reach has precedence over CFB.

When Single Number Reach is invoked, CFB is inhibited.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

POTS

Call Forwarding Combination (CFC)

Single Number Reach has precedence over CFC.

When Single Number Reach is invoked, CFC is inhibited.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

POTS

Call Forwarding No Answer (CFNA)

Single Number Reach has precedence over CFNA.

When Single Number Reach is invoked, CFNA is inhibited.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

POTS

Call Forwarding Not Reachable (CFNR)

Single Number Reach has precedence over CFNR.

When Single Number Reach is invoked, CFNR is inhibited.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

POTS

Call Forwarding Redirection (CFR)

CFR is not applicable. CFR happens at the trunk level. 302 will be dropped in this case.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

POTS

Call Forwarding Unconditional (CFU)

CFU is equivalent to the Follow-me feature.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

POTS

Call Forwarding Variable (CFV)

Same as CFU at invocation time.

Same as CFU at invocation time.

—

Call Hold (CHD)

No impact.

No impact.

—

Call Park (CPRK)

Not applicable.

No impact.

—

Call Park Retrieve (CPRK_RET)

Not applicable.

No impact.

—

Call Transfer (CT)

Not applicable.

Not applicable.

—

Call Waiting (CW)

Single Number Reach has higher precedence.

When Single Number Reach is invoked, CW is inhibited.

No impact.

POTS

Call Waiting Deluxe (CWD)

Single Number Reach has higher precedence.

When Single Number Reach is invoked, CWD is inhibited.

No impact.

—

Caller ID with Call Waiting (CIDCW)

Single Number Reach has higher precedence.

When Single Number Reach is invoked, CIDCW is inhibited.

No impact.

—

Calling Identity Delivery and Suppression Delivery (CIDSD)

Not applicable.

Not applicable.

—

Calling Identity Delivery and Suppression-Suppression (CIDSS)

Not applicable.

Not applicable.

—

Calling Identity Delivery Blocking (CIDB)

Not applicable.

Not applicable.

—

Calling Line Identity Presentation (CLIP)

No impact.

Normal terminating feature invocation on each forked call.

Subject to incoming calling information availability in the setup message.

—

Calling Line Identity Restriction (CLIR)

Not applicable.

Normal originating feature invocation on each forked call.

Subject to calling party permanent presentation status or per-call presentation status at the time of call origination.

—

Calling Name Blocking (CNAB)

Not applicable.

Not applicable.

—

Calling Name Delivery (CNAM)

No impact.

Normal terminating feature invocation on each forked call.

—

Calling Number Delivery (CND)

No impact.

Normal terminating feature invocation on each forked call.

—

Calling Number Delivery Blocking (CNDB)

Not applicable.

Not applicable.

—

Cancel Call Waiting (CCW)

Not applicable.

Not applicable.

—

CENTREX

Single Number Reach feature can be assigned to CENTREX subscriber.

Single Number Reach feature can be assigned to CENTREX subscriber.

—

Centrex Group and Custom Dial Plan (CDP)

Not applicable.

No impact.

—

Class of Service (CoS) Screening

Not applicable.

Normal originating feature invocation on each forked call.

Screening includes go through the NOD-Restrict list.

—

Customer Originated Trace (COT)

Not applicable.

No impact.

—

Directed Call Pickup with Barge-In (DPU)

DPU is inhibited when Single Number Reach is invoked.

No impact.

—

Directed Call Pickup without Barge-In (DPN)

DPN is inhibited when Single Number Reach is invoked.

No impact.

—

Distinctive Alerting Call Waiting Indication (DACWI)

Single Number Reach has higher precedence.

When Single Number Reach is invoked, DACWI is inhibited.

No impact.

—

Distinctive Ringing Call Waiting (DRCW)

Single Number Reach has higher precedence.

When Single Number Reach is invoked, DRCW is inhibited.

No impact.

—

Do Not Disturb (DND)

No impact. DND occurs before Single Number Reach.

No impact.

—

Emergency Callback (ECB)

ECB takes precedence over Single Number Reach.

Single Number Reach is inhibited when ECB is invoked.

Not applicable.

POTS

Group Speed Call: 1- Digit (GSC1D)

Not applicable.

Normal originating feature invocation on each forked call.

—

Group Speed Call: 2- Digit (GSC2D)

Not applicable.

Normal originating feature invocation on each forked call.

—

Hostage Negotiation (HN)

When HN is invoked, Single Number Reach is inhibited.

Not applicable.

—

HOTLINE

Not applicable.

—

POTS

Hotline Variable (HOTV)

Not applicable.

—

POTS

Incoming Simulated Facility Group (ISFG)

No impact.

Not applicable.

—

Interactive Voice Response (IVR)

Apply at Single Number Reach programming time. During IVR session, CW and midcall hook flash are inhibited.

Not applicable.

—

Local Number Portability (LNP)

Not applicable.

No impact. Normal originating feature invocation on each forked call.

—

Message Waiting Indicator (MWI)

Not applicable.

Not applicable.

—

MIDCALL

Not applicable.

Not applicable.

—

Multi Lingual Support (MLS)

Apply at Single Number Reach programming time. IVR prompts base on language preference.

Not applicable.

—

Multiline Hunt Group (MLHG)

Single Number Reach feature can be assigned to MLHG subscriber. If Single Number Reach is assigned to the main subscriber, the hunting does not take place. If Single Number Reach is assigned to the individual sub, the Single Number Reach is invoked if the sub is dialed directly. If the terminal associated with the Single Number Reach is hunted as part of MLHG, then the Single Number Reach is invoked as well.

Single Number Reach feature can be assign to MLHG subscriber. If Single Number Reach is assigned to the main sub, the hunting does not take place. If Single Number Reach is assigned to the individual sub, the Single Number Reach is invoked if the subscriber is dialed directly. If the terminal associated with the Single Number Reach is hunted as part of MLHG, then the Single Number Reach is invoked as well.

—

Multiline Variety Package (MVP)

Not applicable.

No impact.

—

Multiple Directory Numbers (MDN)

Only one DN in the MDN list can be assigned the Single Number Reach feature and it is supported on the main DN where the Single Number Reach is invoked.

No impact.

—

No Solicitation Announcement (NSA)

No impact. Single Number Reach is invoked after NSA feature is finished.

No impact.

POTS

Off Hook Delayed (OHD)/Off Hook Immediate (OHI) or any external originating feature

Not applicable.

Normal originating feature invocation on each forked call.

—

ONA

Not applicable.

Not applicable.

—

Outgoing Call Barring (OCB)

Not applicable.

Each forked call is subjected to OCB screening by CoS. If an instance of a forked call is blocked, then this particular forked call is released.

—

Outgoing Simulated Facility Group (OSFG)

Not applicable.

Centrex originating feature that limits the number of outing origination calls. The number of forked calls is subject to this limit.

—

POST-PAID Limited Call Duration (LCD)

No impact.

No impact.

—

PRE-PAID (LCD)

No impact.

No impact.

—

Privacy Screening (PS)

PS has higher precedence. PS is invoked first.

PS places the first call to AppSvr.

When a second call comes from the AppSvr, Single Number Reach is invoked.

No impact

—

REFER

Not applicable.

Not applicable.

—

Remote Activation of Call Forwarding (RACF)

Not applicable. RACF originates with starcode.

Same as CFU on invocation.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

—

Remote Call Forwarding (RCF)

Same as CFU at invocation time.

Same as CFU at invocation time.

—

REPLACE

Not applicable.

Not applicable.

—

Screening List Editing (SLE)

Not applicable.

Not applicable.

—

Seasonal Suspend (SEAS)

When SEAS is invoked, Single Number Reach is inhibited.

Not applicable.

POTS

Selective Call Acceptance (SCA)

No impact. SCA occurs before SNR.

If the number is on the list, Single Number Reach is invoked; otherwise, the call is rejected.

No impact.

—

Selective Call Forwarding (SCF)

No impact.

SCF occurs prior to the Single Number Reach. Therefore if the caller is on the subscriber's selective call forwarding list, then the call is forwarded. Otherwise all other calls invokes the Single Number Reach.

No impact.

—

Selective Call Rejection (SCR)

No impact. SCR occurs before Single Number Reach.

Single Number Reach is not hit if the number is on the list.

No impact.

—

Single Number Reach

By default, Single Number Reach is inhibited when one Single Number Reach service instance is already invoked on the master number. To control whether multiple invocations of Single Number Reach are allowed or not, use the feature-config or Single Number Reach profile.

If there is a forked call and the destination subscriber has Single Number Reach active, Single Number Reach is not invoked.

—

Speed Call: 1-Digit (SC1D)

Not applicable.

The normal originating feature invocation on each forked call.

—

Speed Call: 1-Digit (SC2D)

Not applicable.

The normal originating feature invocation on each forked call.

—

TAT_1 (or any external feature has higher precedence than Single Number Reach)

When a call is made to a Single Number Reach subscriber that has TAT_1 feature then the TAT_1 feature is invoked prior to Single Number Reach. The first leg of the call is routed to the Application Server and then the second leg is sent back from the Application Server where Single Number Reach is invoked. Then the call runs through the Single Number Reach list until the subscriber answers the call or it is forwarded to voice mail.

No impact.

—

TAT_2 or any external feature has lower precedence than Single Number Reach

Single Number Reach has higher precedence. TAT_2 is invoked on each of the forked calls.

When Single Number Reach is active, TAT_2 is not invoked. Then the call runs through the Single Number Reach list until the subscriber answers the call or it is forwarded to voice mail.

No impact.

—

Temporary Disconnect (TDISC)

When TDISC is invoked, Single Number Reach is inhibited.

Not applicable.

POTS

Three Way Calling (TWC)

Not applicable.

Not applicable.

—

Three Way Calling Deluxe (TWCD)

Not applicable.

Not applicable.

—

Time of Day (TOD)

Apply at Single Number Reach invocation time.

Not applicable.

—

Toll-Free (8XX)

Not applicable.

No impact. Normal originating feature invocation on each forked call.

—

Usage-Sensitive Three-Way Calling (USTWC)

Not applicable.

Not applicable.

—

VM_BUSY

Single Number Reach has precedence over VM_BUSY.

When Single Number Reach is invoked, VM_BUSY is inhibited.

If there is a forked call, the subsequent call is not forwarded if the terminating party is on the BTS. The maximum hop count prevents the call from any further diversion.

—

VM_NO_ANSWER

Single Number Reach has precedence over VM_NO_ANSWER.

When Single Number Reach is invoked, VM_NO_ANSWER is inhibited.

For the forked call, the subsequent call is not forwarded if the terminating party is on BTS. The maximum hop count prevents the call from any further diversion.

—

Voice Mail Always (VMA)

VMA is equivalent to follow-me feature.

Not applicable.

—

WARMLINE

Not applicable.

—

POTS


Prerequisites

Single Number Reach requires an IVR and voice mail server.

Provisioning

This section explains how to do the following:

•Office Provisioning

•Resource Provisioning

•Announcement Provisioning

•Feature Control Options for Provisioning IVR Interactions

•Subscriber Provisioning

•SNR_ACT IVR Virtual Subscriber Provisioning

Note For complete CLI information, see the Cisco BTS 10200 Softswitch CLI Database.

Office Provisioning

This section lists the provisioning steps required to complete office provisioning for the Single Number Reach feature. The CFU and VMA features should be provisioned before the subscriber completes the Single Number Reach office provisioning procedure. For details on provisioning the CFU and VMA features, see the Cisco BTS 10200 Softswitch Provisioning Guide, Release 6.0.x.

Step 1 Create the Single Number Reach activation (SNR_ACT) feature. 

add feature fname=SNR_ACT; feature_server_id=FSPTC235; grp_feature=N;

Step 2 Create the Single Number Reach feature and include CFU and VMA as subfeatures. 

add feature fname=SNR; tdp1=TERMINATION_ATTEMPT_AUTHORIZED; 
tid1=TERMINATION_ATTEMPT_AUTHORIZED; ttype1=R; feature_server_id=FSPTC235; fname1=CFU; 
fname2=VMA; grp_feature=N;

Step 3 Add the Single Number Reach feature service. 

add service id=snr; fname1=SNR;

Resource Provisioning

This section lists the provisioning steps required to complete the resource provisioning for the Single Number Reach feature.

Note Only MGW_PROFILE table fields used by Single Number Reach are discussed below. For complete MGW_PROFILE table details, refer to the Cisco BTS 10200 Softswitch CLI Database.

Step 1 Add a media server. 

add mgw_profile id=ivr_ipunity; vendor=Cisco; packet_type=IP; aal1=N; aal2=N; aal5=N; 
pvc=N; svc=N; spvc=N; mgcp_version=MGCP_1_0; termination_prefix=ivr/;

Step 2 Add a media gateway. 

add mgw id=ipunity-227-103; tsap_addr=ms-ipunity.ipclab.cisco.com; call_agent_id=CA146; 
mgw_profile_id=ivr_ipunity; type=TGW;

Step 3 Add the IVR trunk group profile. 

add annc_tg_profile id=ivr-ipunity; annc=N; ivr=Y; auto_answer=Y; local_trunk_selection=N; 
description=IVR server using IPUnity;

Step 4 Add a trunk group. 

add trunk_grp id=80031; call_agent-id=CA146; tg_profile_id=ivr-ipunity; tg_type=annc; 
mgcp_pkg_type=ANNC_CABLE_LABS; pop_id=1; cost=1;


Step 5 Add a termination. 

add termination prefix=ivr/; port_start=1; port_end=30; type=trunk; mgw_id=ipunity_ms;

Step 6 Add a trunk. 

add trunk cic_start=1; cic_end=30; tgn_id=80031; mgw_id=ipunity_ms; 
termination_prefix=ivr/; termination_port_start=1; termination_port_end=30;

Step 7 Add a route. 

add route id=rt_ivr; tgn1-id=80031; tg-selection=LCR;

Step 8 Add a route guide. 

add route_guide id=rg_ivr; policy_type=ROUTE; policy_id=rt_ivr;

Step 9 Add an IVR script profile for the Single Number Reach and SNR_ACT features. 

add ivr_script_profile fname=SNR; ivr_access_mode=IVR; IVR_ROUTE_GUIDE_ID=rg_ivr; 
IVR_SCRIPT_PKG_TYPE=BAU;


add ivr_script_profile fname=SNR_ACT; ivr_access_mode=IVR; IVR_ROUTE_GUIDE_ID=rg_ivr; 
IVR_SCRIPT_PKG_TYPE=BAU;

Step 10 Place the trunk group and other resources in service (INS). 

control mgw id=ipunity_ms; mode=forced; target_state=INS;


control trunk_grp id=80031; mode=FORCED; target_state=INS;


equip trunk_termination tgn_id=80031; cic=all;


control trunk_termination tgn_id=80031; cic=all; mode=FORCED; target_state=INS;

Step 11 Verify resource status. 

status mgw id=ipunity_ms;


status trunk_grp id=80031;


status tt tgn_id=80031; cic=all;

Announcement Provisioning

This section lists steps required to complete announcement provisioning for Single Number Reach and SNR_ACT.

Step 1 If you have not already done so, add the default language ID. 

add language id=def;

Step 2 Add the audio segments that are common or shared among multiple menus or features. 

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;


add audio_segment id=SNR_TO_CONFIRM_PRESS; type=PHYSICAL; url=file://to_confirm_press.wav; 
description=To confirm, press


add audio_segment id=SNR_SORRY_NUM_INVALID; type=PHYSICAL; 
url=file://SorryNumberInvalid.wav; description=We are sorry. The number you have entered 
is incorrect.


add audio_segment id=SNR_SORRY_CMD_INVALID; type=PHYSICAL; 
url=file://SorryCommandInvalid.wav; description=We are sorry. The digits entered are not a 
valid command.


add audio_segment id=SNR_FORWARDING_TO_NUM; type=PHYSICAL; 
url=file://your_calls_currently_fwd_to.wav; description=Your calls are currently being 
forwarded to


add audio_segment id=SNR_PLEASE_ENTER_FWD_NUM; type=PHYSICAL; 
url=file://PleaseEnterFwdDn.wav; description=Please enter the number to which you want 
your calls forwarded, followed by the number sign key.


add audio_segment id=SNR_TO_REPEAT_INSTRUCTIONS; type=PHYSICAL; 
url=file://to_hear_instructions_repeated.wav; description=To hear these instructions 
repeated, press

Step 3 Add the Single Number Reach audio segments. 

add audio_segment id=SNR_TRYING_TO_REACH_PARTY; type=PHYSICAL; 
url=file://trying_to_reach_party.wav; description=We are trying to reach your party. 
Please stay on the line.


add audio-segment id=SNR_RING_BACK_TONE; type=PHYSICAL; url=file://ring_back_tone.wav; 
description=2 seconds of ringback tone.

Step 4 Add the SNR_ACT authentication audio segments. 

add audio_segment id=SNR_WELCOME; type=PHYSICAL; url=file://snr_welcome.wav; 
description=Welcome to the Single Number Reach System.


add audio_segment id=SNR_ENTER_NUM; type=PHYSICAL; url=file://snr_enter_number.wav; 
description=Please enter your SNR number, followed by the number sign key.


add audio_segment id=SNR_ADMIN_NUM; type=PHYSICAL; url=file://snr_admin_number.wav; 
description=You are about to administer SNR for


add audio_segment id=SNR_ADMIN_DIFF_NUM; type=PHYSICAL; 
url=file://snr_admin_diff_number.wav; description=To administer a different SNR number, 
press


add audio_segment id=SNR_INVALID_USER_ID_ABORT; type=PHYSICAL; url=file://hang_up_now.wav; 
description=Please hang up now, consult your written instructions, and try again later.


add audio_segment id=SNR_ENTER_PIN; type=PHYSICAL; url=file://please_enter_your_pin.wav; 
description=Please enter your pin, followed by the number sign key.


add audio_segment id=SNR_REENTER_PIN; type=PHYSICAL; 
url=file://please_reenter_your_pin.wav; description=Please re-enter your pin, followed by 
the number sign key.


add audio_segment id=SNR_INCORRECT_PIN; type=PHYSICAL; url=file://snr_incorrect_pin.wav; 
description=We are sorry. The pin entered does not match the current PIN for SNR number


add audio_segment id=SNR_PIN_ATTEMPTS; type=PHYSICAL; url=file://snr_pin_attempts.wav; 
description=If this is not the desired SNR number, please hang up and retry. The number of 
consecutive invalid pin attempts for this account is currently


add audio_segment id=SNR_FOR_YOUR_PROTECTION; type=PHYSICAL; 
url=file://for_your_protection.wav; description=For you protection, if this count reaches


add audio_segment id=SNR_ACCESS_WILL_BE_DISABLED; type=PHYSICAL; 
url=file://phone_access_will_be_disabled.wav; description=account access via phone will be 
disabled.


add audio_segment id=SNR_PHONE_ACCESS_IS_DISABLED; type=PHYSICAL; 
url=file://phone_access_is_disabled.wav; description=Phone access for this account is 
disabled. To re-enable phone access, please reset your pin via the internet.

Step 5 Add the SNR_ACT Main Menu audio segments. 

add audio_segment id=SNR_FORWARDING_PER_SCHED; type=PHYSICAL; 
url=file://your_calls_fwd_per_sched.wav; description=Your calls are currently being 
forwarded based upon your forwarding schedule.


add audio_segment id=SNR_FORWARDING_TO_VOICEMAIL; type=PHYSICAL; 
url=file://your_calls_fwd_to_voicemail.wav; description=Your calls are currently being 
forwarded straight to your voicemail.


add audio_segment id=SNR_NO_FORWARDING_ACTIVE; type=PHYSICAL; 
url=file://snr_no_forwarding_active.wav; description=You currently do not have any of your 
SNR Call Forwarding Features active.


add audio_segment id=SNR_TO_ACTIVATE_CONFIG_CFU; type=PHYSICAL; 
url=file://to_activate_config_fwd_num.wav; description=To activate or configure forwarding 
to a single number, press


add audio_segment id=SNR_TO_CONFIG_CFU; type=PHYSICAL; url=file://to_config_fwd_num.wav; 
description=To configure forwarding to a single number, press


add audio_segment id=SNR_TO_ACTIVATE_FWD_SCHED; type=PHYSICAL; 
url=file://to_activate_fwd_sched.wav; description=To activate Forwarding per your 
schedule, press


add audio_segment id=SNR_TO_ACTIVATE_VMA; type=PHYSICAL; 
url=file://to_activate_fwd_voicemail.wav; description=To activate Forwarding straight to 
Voicemail, press


add audio_segment id=SNR_TO_DEACTIVATE_ALL_SNR; type=PHYSICAL; 
url=file://to_deactivate_all_snr_fwd.wav; description=To deactivate all SNR Forwarding 
Features, press


add audio_segment id=SNR_TO_EXIT_TO_VMS; type=PHYSICAL; 
url=file://to_exit_snr_to_voicemail.wav; description=To exit this SNR system and connect 
to your voicemail, press


add audio_segment id=SNR_TO_EXIT; type=PHYSICAL; url=file://to_exit_snr.wav; 
description=To exit this SNR system, hang up or press


add audio_segment id=SNR_EXIT_SYSTEM; type=PHYSICAL; url=file://exit_snr_system.wav; 
description=You are now exiting the SNR configuration system. Goodbye.




Step 6 Add the SNR_ACT Forwarding per Schedule audio segments. 

add audio_segment id=SNR_FWD_PER_SCHED_NOT_CONFIG; type=PHYSICAL; 
url=file://fwd_per_sched_not_config.wav; description=Forwarding per schedule is not 
configured properly. Please contact customer service.


add audio_segment id=SNR_NO_SCHED_ACTIVE; type=PHYSICAL; 
url=file://fwd_sched_needs_config.wav; description=Your forwarding schedule needs to be 
configured via the internet before it can be activated.

Step 7 Add the SNR_ACT Forwarding to Single Number audio segments. 

add audio_segment id=SNR_CFU_NOT_CONFIG; type=PHYSICAL; 
url=file://fwd_to_single_num_not_config.wav; description=Forwarding to a single number is 
not configured properly. Please contact customer service.


add audio_segment id=SNR_CFU_NUM_INVALID; type=PHYSICAL; 
url=file://fwd_to_num_invalid.wav; description=Your forward-to-number is not set to a 
valid number.


add audio_segment id=SNR_CFU_FWD_TO_NUM_IS; type=PHYSICAL; url=file://fwd_to_num_is.wav; 
description=Your forward-to number is


add audio_segment id=SNR_TO_FWD_TO_THIS_NUM; type=PHYSICAL; 
url=file://to_fwd_to_this_num.wav; description=To forward all calls to this number, press


add audio_segment id=SNR_TO_CHANGE_FWD_TO_NUM; type=PHYSICAL; 
url=file://to_change_fwd_to_num.wav; description=To change your forward-to number, press


add audio_segment id=SNR_FWD_TO_NUM_IS_GOING_TO_BE; type=PHYSICAL; 
url=file://fwd_num_is_going_to_be.wav; description=Your forward-to number is going to be 
changed to


add audio_segment id=SNR_TO_CHANGE_FWD_DIFF_NUM; type=PHYSICAL; 
url=file://to_change_fwd_to_diff_num.wav; description=To change your forward-to number to 
a different number, press


add audio_segment id=SNR_TO_RETURN_TO_PREV_MENU; type=PHYSICAL; 
url=file://to_return_to_previous_menu.wav; description=To return to the previous menu, 
press


add audio_segment id=SNR_TO_RETURN_WITHOUT_UPDATE_FWD; type=PHYSICAL; 
url=file://to_return_without_update_fwd.wav; description=To return to the previous menu 
without updating your forward-to number, press

Step 8 Add the SNR_ACT Forwarding to Voicemail audio segments. 

add audio_segment id=SNR_VMA_NOT_CONFIGURED; type=PHYSICAL; 
url=file://fwd_to_voicemail_not_config.wav; description=Forwarding to a voicemail is not 
configured properly. Please contact customer service.


add audio_segment id=SNR_EXIT_TO_VOICEMAIL; type=PHYSICAL; 
url=file://exit_snr_to_voicemail.wav; description=You are now exiting the SNR 
configuration system and connecting to voicemail.

Step 9 Add the SNR_ACT common audio sequences. 

add audio_seq id=SNR_NUM_INVALID; language_id=def; seq=SNR_SORRY_NUM_INVALID; 
description=We are sorry. The number you have entered is incorrect.


add audio_seq id=SNR_CMD_INVALID; language_id=def; seq=SNR_SORRY_CMD_INVALID; 
description=We are sorry. The digits entered are not a valid command.



Step 10 Add the Single Number Reach announcement audio sequence. 

add audio_seq id=SNR_ANNC_SEQ; language_id=def; seq=SNR_TRYING_TO_REACH_PARTY; 
description=We are trying to reach your party. Please stay on the line.


add audio-seq id=SNR_RINGBK_SEQ; LANGUAGE_ID=def; SEQ=SNR_RING_BACK_TONE;

Step 11 Add the SNR_ACT authentication audio sequences. 

add audio_seq id=SNR_AUTH_WELCOME; language_id=def; seq=SNR_WELCOME; description=Welcome 
to the Single Number Reach System.


add audio_seq id=SNR_AUTH_USER_ID; language_id=def; seq=SNR_ENTER_NUM; description=Please 
enter your SNR number, followed by the number sign key.


add audio_seq id=SNR_CONFIRM_NUM; language_id=def; 
seq=SNR_ADMIN_NUM,var_digits,SNR_TO_CONFIRM_PRESS,var_digits,SNR_ADMIN_DIFF_NUM,var_digits
; description=You are about to administer SNR for <ds>. To confirm, press 
<AUTH-USERID-CONFIRM-OP>. To administer a different SNR number, press 
<AUTH-USERID-CHANGE-OP>.


add audio_seq id=SNR_INVALID_USER; language_id=def; seq=SNR_SORRY_NUM_INVALID; 
description=We are sorry. The number you have entered is incorrect.


add audio_seq id=SNR_INVALID_ABRT; language_id=def; seq=SNR_INVALID_USER_ID_ABORT; 
description=Please hang up now, consult your written instructions, and try again later.


add audio_seq id=SNR_ENTER_PIN; language_id=def; seq=var_audio; 
description=<SNR_ENTER_PIN/SNR_REENTER_PIN> Please (re)enter your pin, followed by the 
number sign key.


add audio_seq id=SNR_INVALID_PIN; language_id=def; seq=SNR_INCORRECT_PIN,var_digits; 
description=We are sorry. The pin entered does not match the current PIN for SNR number 
<ds>.


add audio_seq id=SNR_PIN_ATTEMPTS; language_id=def; 
seq=SNR_PIN_ATTEMPTS,var_number,SNR_FOR_YOUR_PROTECTION,var_number,SNR_ACCESS_WILL_BE_DISA
BLED; description=If this is not the desired SNR number, please hang-up and retry. The 
number of consecutive invalid pin attempts for this account is currently <d>. For you 
protection, if this count reaches <d>, account access via phone will be disabled.


add audio_seq id=SNR_AUTH_LOCKOUT; language_id=def; seq=SNR_PHONE_ACCESS_IS_DISABLED; 
description=Phone access for this account is disabled. To re-enable phone access, please 
reset your pin via the internet.

Step 12 Add the SNR_ACT Main Menu audio sequences. 

add audio_seq id=SNR_MAIN_MENU; language_id=def; 
seq=var_audio,var_digits,var_audio,var_digits,var_audio,var_digits,var_audio,var_digits,va
r_audio,var_digits,var_audio,var_digits,var_audio,var_digits,SNR_TO_REPEAT_INSTRUCTIONS,va
r_digits; 
description=<SNR_FORWARDING_TO_NUM/SNR_FORWARDING_PER_SCHED/SNR_FORWARDING_TO_VOICEMAIL/SN
R_NO_FORWARDING_ACTIVE>,<ds/NULL>,<SNR_TO_CONFIG_CFU/SNR_TO_ACTIVATE_CONFIG_CFU>,<MAIN-ACT
IVATE-CFU-OP>,<SNR_TO_ACTIVATE_FWD_SCHED/NULL>, 
<MAIN-ACTIVATE-FWD-SCHED-OP/NULL>,<SNR_TO_ACTIVATE_VMA/NULL>,<MAIN-ACTIVATE-FWD-VMA-OP/NUL
L>,<SNR_TO_DEACTIVATE_ALL_SNR/NULL>,<MAIN-DEACTIVATE-ALL-FWD-OP/NULL>,<SNR_TO_EXIT_TO_VMS>
,<MAIN-EXIT-TO-VMS-OP/NULL>,<SNR_TO_EXIT>,<MAIN-EXIT-OP/NULL>. To repeat instructions, 
press <REPEAT-INSTRUCTION>.


add audio_seq id=SNR_EXITING_SYST; language_id=def; seq=SNR_EXIT_SYSTEM; description=You 
are now exiting the SNR configuration system. Goodbye.



Step 13 Add the SNR_ACT Forwarding per Schedule audio sequences. 

add audio_seq id=SNR_SNR_NOT_CFG; language_id=def; seq=SNR_FWD_PER_SCHED_NOT_CONFIG; 
description=Forwarding per schedule is not configured properly. Please contact customer 
service.


add audio_seq id=SNR_NO_SCHED_ACT; language_id=def; seq=SNR_NO_SCHED_ACTIVE; 
description=Your forwarding schedule needs to be configured via the internet before it can 
be activated.

Step 14 Add the SNR_ACT Forwarding to Single Number audio sequences. 

add audio_seq id=SNR_CFU_NOT_CFG; language_id=def; seq=SNR_CFU_NOT_CONFIG; 
description=Forwarding to a single number is not configured properly. Please contact 
customer service.


add audio_seq id=SNR_CFU_MENU; language_id=def; 
seq=var_audio,var_digits,var_audio,var_digits,SNR_TO_CHANGE_FWD_TO_NUM,var_digits,SNR_TO_R
ETURN_TO_PREV_MENU,var_digits,SNR_TO_REPEAT_INSTRUCTIONS,var_digits; 
description=<SNR_CFU_NUM_INVALID/SNR_CFU_FWD_TO_NUM_IS/SNR_FORWARDING_TO_NUM>,<NULL/ds/ds>
,<NULL/SNR_TO_FWD_TO_THIS_NUM/NULL>,<NULL/CFU-ENABLE-CFU-OP/NULL>,To change your 
forward-to number, press <CFU-CHANGE-FWD-TO_NUM-OP>. To return to the previous menu, press 
<CFU-RTN-TO-PREV-MENU-OP>. To hear these instructions repeated, press 
<REPEAT-INSTRUCTION>.


add audio_seq id=SNR_ENTR_FWD_NUM; language_id=def; seq=SNR_PLEASE_ENTER_FWD_NUM; 
description=Please enter the number to which you want your calls forwarded, followed by 
the number sign key.


add audio_seq id=SNR_CFU_NUM_CNFM; language_id=def; 
seq=SNR_FWD_TO_NUM_IS_GOING_TO_BE,var_digits,SNR_TO_CONFIRM_PRESS,var_digits,SNR_TO_CHANGE
_FWD_DIFF_NUM,var_digits,SNR_TO_RETURN_WITHOUT_UPDATE_FWD,var_digits,SNR_TO_REPEAT_INSTRUC
TIONS,var_digits; description=Your forward-to number is going to be changed to <ds>. To 
confirm, press <CFU-CONFIRM-CFU-NUM-OP>. To change your forward-to number to a different 
number, press <CFU-CHANGE-FWD-TO-DIFF-NUM-OP>. To return to the previous menu without 
updating your forward-to number, press <CFU-RTN-WITHOUT-UPDATE-OP>. To hear these 
instructions repeated, press <REPEAT-INSTRUCTION>.

Step 15 Add the SNR_ACT Voicemail audio sequences. 

add audio_seq id=SNR_VMA_NOT_CFG; language_id=def; seq=SNR_VMA_NOT_CONFIGURED; 
description=Forwarding to a voicemail is not configured properly. Please contact customer 
service.


add audio_seq id=SNR_EXITNG_TO_VM; language_id=def; seq=SNR_EXIT_TO_VOICEMAIL; 
description=You are now exiting the SNR configuration system and connecting to voicemail.

Feature Control Options for Provisioning IVR Interactions

This section lists the steps required to complete the provisioning for feature control options for the IVR interactions.

Step 1 Add the feature configurations for SNR_ACT. 

add feature_config fname=SNR_ACT; type=RESTART-KEY; datatype=string; value=*; 
description=Key to dial to restart entering the number.


add feature_config fname=SNR_ACT; type=RETURN-KEY; datatype=string; value=#; 
description=Key to dial to complete the entry of the number.


add feature_config fname=SNR_ACT; type=REPEAT-INSTRUCTION; value=0; description=Digit to 
dial to hear instructions repeated.


add feature_config fname=SNR_ACT; type=T-SESSION; datatype=integer; value=6000; 
description=Session timer in 0.1 sec increments.


add feature_config fname=SNR_ACT; type=FDT-TIMER; datatype=integer; value=150; 
description=Time to wait for first digit to be dialed, in 0.1 sec increments


add feature_config fname=SNR_ACT; type=IDT-TIMER; datatype=integer; value=70; 
description=Time to wait between digits, in 0.1 sec increments.

Step 2 Add the feature configurations for SNR_ACT authentication. 

add feature_config fname=SNR_ACT; type=AUTH-CHECK-FOR-MST-NUM; datatype=boolean; value=Y; 
description=Whether to check if call originated from SNR Master Number.


add feature_config fname=SNR_ACT; type=AUTH-PIN-ATTEMPTS-TO-LOCK; datatype=integer; 
value=5; description=Number of consecutive invalid pin attempts to lock out IVR user.


add feature_config fname=SNR_ACT; type=AUTH-PIN-ATTEMPTS-TO-WARN; datatype=integer; 
value=2; description=Number of pin attempts to start warning they will be locked out.


add feature_config fname=SNR_ACT; type=AUTH-USERID-ATTEMPTS-TO-EXIT; datatype=integer; 
value=3; description=Num of consecutive UserID attempts to cause user exit from IVR.


add feature_config fname=SNR_ACT; type=AUTH-USERID-CONFIRM-OP; value=1; description=Digit 
to dial to confirm proper SNR number is to be configured.


add feature_config fname=SNR_ACT; type=AUTH-USERID-CHANGE-OP; value=2; description=Digit 
to dial to change the SNR number that is to be configured.

Step 3 Add the feature configurations for the SNR_ACT Main Menu. 

add feature_config fname=SNR_ACT; type=MAIN-ACTIVATE-CFU-OP; value=1; description=Digit to 
dial from main menu to activate CFU.


add feature_config fname=SNR_ACT; type=MAIN-ACTIVATE-FWD-SCHED-OP; value=2; 
description=Digit to dial from main menu to activate fowarding per schedule.


add feature_config fname=SNR_ACT; type=MAIN-ACTIVATE-FWD-VMA-OP; value=3; 
description=Digit to dial on main menu to activate forwarding to voicemail.


add feature_config fname=SNR_ACT; type=MAIN-DEACTIVATE-ALL-FWD-OP; value=4; 
description=Digit to dial from main menu to deactivate all SNR forwarding.


add feature_config fname=SNR_ACT; type=MAIN-EXIT-TO-VMS-OP; value=5; description=Digit to 
dial from main menu to exit to VoiceMail System.


add feature_config fname=SNR_ACT; type=MAIN-EXIT-OP; value=9; description=Digit to dial to 
exit IVR.

Step 4 Add the feature configurations for the SNR_ACT Forwarding to Single Number menu. 

add feature_config fname=SNR_ACT; type=CFU-ENABLE-CFU-OP; value=1; description=Digit to 
dial from CFU menu to activate CFU.


add feature_config fname=SNR_ACT; type=CFU-CHANGE-FWD-TO-NUM-OP; value=2; 
description=Digit to dial from CFU menu to change CFU forward-to number.


add feature_config fname=SNR_ACT; type=CFU-RTN-TO-PREV-MENU-OP; value=9; description=Digit 
to dial from CFU menu to return to previous menu.


add feature_config fname=SNR_ACT; type=CFU-CONFIRM-CFU-NUM; datatype=boolean; value=N; 
description=Whether user given extra prompt to confirm new CFU fwd number.


add feature_config fname=SNR_ACT; type=CFU-CONFIRM-CFU-NUM-OP; value=1; description=Digit 
to dial from CFU Confirm menu to confirm new CFU number.


add feature_config fname=SNR_ACT; type=CFU-CHANGE-FWD-TO-DIFF-NUM-OP; value=2; 
description=Digit to dial from CFU Confirm menu to change CFU fwd-to number.


add feature_config fname=SNR_ACT; type=CFU-RTN-WITHOUT-UPDATE-OP; value=9; 
description=Digit to dial from CFU Confirm menu to return without updating.

Subscriber Provisioning

This section lists steps required for provisioning subscribers, assigning the Single Number Reach service to the subscriber, and performing the initial setup of the subscriber PIN.

Step 1 If a subscriber entry for the subscriber does not exist, add a subscriber entry for subscriber. For a virtual subscriber, set term_type=none. 

add subscriber id=222-789-3510; sub_profile_id=subprof_1; DN1=222-789-3510; 
voice_mail_id=vm_as

Step 2 Assign the Single Number Reach service to the subscriber. 

add subscriber_service_profile sub_id=222-789-3510; service_id=snr;

Step 3 Add the subscriber_feature_data for the initial setup of the SNR_ACT PIN. 

add subscriber_feature_data sub_id=222-789-3510; fname=SNR_ACT; type1=PINTYPE; 
value1=NEWPIN; type2=PIN; value2=3510; type3=PINATTS; value3=0;

Step 4 Add the initial subscriber Single Number Reacted schedule. The reacted schedule can be provisioned to make the subscriber handle the call during the Single Number Reach process, for example handling or allowing the calls to ring simultaneously or sequentially, TOD of scheduling the call. The subscriber sets up and configures the Single Number Reacted schedule setup through the XML file. 

add snr sub_id=222-789-3510; file=/snr.xml;


SNR_ACT IVR Virtual Subscriber Provisioning

This section lists the steps required for provisioning SNR_ACT virtual subscribers.

Step 1 Add the SNR_ACT virtual subscriber. All Single Number Reach subscribers will call 2227891000 for IVR access to their SNR_ACT features: