Downloads |
Table Of Contents
Cisco BTS 10200 Softswitch Single Number Reach Feature Module
Understanding the Single Number Reach Feature
Single Number Reach Feature Description
Feature Control Options for Provisioning IVR Interactions
SNR_ACT IVR Virtual Subscriber Provisioning
Single Number Reach Feature-Config and Feature-Config-Base Table
SNR_ACT Feature-Config and Feature-Config-Base Table
Single Number Reach XML Schema
Subscriber Web-Based Interface
Subscriber IVR-Based Interface
Accessing the Single Number Reach IVR Menu
Single Number Reach (Forwarding Per Schedule) Activation
Single Number Reach Deactivation
Single Number Reach IVR Prompts
Cisco BTS 10200 Softswitch Single Number Reach Feature Module
Revised: July 31, 2008This 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
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:
•
•
Single Number Reach does the following:
•
•
•
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:
•
•
–
–
•
Find-me can be associated only with a subscriber's master number. One master number can be associated with the following schedules:
•
•
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:
•
•
•
•
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.
Prerequisites
Single Number Reach requires an IVR and voice mail server.
Provisioning
This section explains how to do the following:
•
•
Note
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
add feature fname=SNR_ACT; feature_server_id=FSPTC235; grp_feature=N;Step 2
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 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
Step 1
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 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 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 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 termination prefix=ivr/; port_start=1; port_end=30; type=trunk; mgw_id=ipunity_ms;Step 6
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 route id=rt_ivr; tgn1-id=80031; tg-selection=LCR;Step 8
add route_guide id=rg_ivr; policy_type=ROUTE; policy_id=rt_ivr;Step 9
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
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
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
add language id=def;Step 2
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, pressadd 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 toadd 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, pressStep 3
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 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 foradd audio_segment id=SNR_ADMIN_DIFF_NUM; type=PHYSICAL; url=file://snr_admin_diff_number.wav; description=To administer a different SNR number, pressadd 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 numberadd 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 currentlyadd audio_segment id=SNR_FOR_YOUR_PROTECTION; type=PHYSICAL; url=file://for_your_protection.wav; description=For you protection, if this count reachesadd 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 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, pressadd audio_segment id=SNR_TO_CONFIG_CFU; type=PHYSICAL; url=file://to_config_fwd_num.wav; description=To configure forwarding to a single number, pressadd audio_segment id=SNR_TO_ACTIVATE_FWD_SCHED; type=PHYSICAL; url=file://to_activate_fwd_sched.wav; description=To activate Forwarding per your schedule, pressadd audio_segment id=SNR_TO_ACTIVATE_VMA; type=PHYSICAL; url=file://to_activate_fwd_voicemail.wav; description=To activate Forwarding straight to Voicemail, pressadd 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, pressadd 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, pressadd audio_segment id=SNR_TO_EXIT; type=PHYSICAL; url=file://to_exit_snr.wav; description=To exit this SNR system, hang up or pressadd 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 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 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 isadd 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, pressadd 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, pressadd 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 toadd 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, pressadd 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, pressadd 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, pressStep 8
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 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 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 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 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 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 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 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 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 incrementsadd 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 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 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 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
add subscriber id=222-789-3510; sub_profile_id=subprof_1; DN1=222-789-3510; voice_mail_id=vm_asStep 2
add subscriber_service_profile sub_id=222-789-3510; service_id=snr;Step 3
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 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 subscriber ID=snr_act_ivr_annc_sub; CATEGORY=IVR; NAME=tb22 snr-act-annc-sub; STATUS=ACTIVE; dn1=222-789-1000; PRIVACY=NONE; RING-TYPE-DN1=R1; USAGE-SENS=N; SUB-PROFILE-ID=dp222;TERM-TYPE=ROUTE; POLICY-ID=rt_ivr;Step 2
add feature fname=IVR; tdp1=T_ANSWER; tid1=T_ANSWER; ttype1=R; description=Internal IVR feature; feature_server_id=FSPTC235;Step 3
add service id=SNR_ACT_IVR_SVC; fname1=IVR; fname2=SNR_ACT;Step 4
add sub-service-profile sub-id=snr_act_ivr_annc_sub; service-id=SNR_ACT_IVR_SVC;# <!-- Limit the .xml instance to the size Noted in the .xsd schema. -->Sample Single Number Reach XML content.
<?xml version="1.0" encoding="UTF-8"?><SNR xmlns="urn:ietf:params:xml:ns:cisco:bts:feature:snr"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="urn:ietf:params:xml:ns:cisco:bts:feature:snr snr.xsd"><VER>06.00.01.V00</VER><MI>1</MI><ABK><AE><DS>Office Phone</DS><UI>1</UI><UE><DN>4692550901</DN></UE></AE><AE><DS>Soft Client</DS><UI>2</UI><UE><AR>sip:kdong@cisco.com</AR></UE></AE><AE><DS>Mobile Phone</DS><UI>3</UI><UE><DN>2143928649</DN></UE></AE><AE><DS>UseDescriptionWith32CharsMaximum</DS><UI>4</UI><UE><AR>123456789@12345678901234567890123456789012345678901234567890.com</AR></UE></AE></ABK><FND><TOD><DS>Normal WeekDay TOD Schedule</DS><ST>1</ST><BT>08:00:00</BT><ET>17:30:00</ET><SC><WD>12345</WD></SC><PA><UI>1</UI><RT>1</RT><RD>0</RD></PA><PA><UI>2</UI><RT>7</RT><RD>3</RD></PA><PA><UI>4</UI><NR>1</NR><RT>1</RT><RD>3</RD></PA><PR>1</PR></TOD><TOD><DS>WeekEnd TOD Schedule</DS><ST>1</ST><BT>07:30:00</BT><ET>23:59:59</ET><SC><WD>06</WD></SC><PA><UI>2</UI><NR>15</NR><RT>1</RT><RD>0</RD></PA><PA><UI>3</UI><NR>3</NR><RT>1</RT><RD>4</RD></PA><PR>6</PR></TOD><TOD><DS>Team Training: Send To Voicemail</DS><ST>1</ST><BT>08:00:00</BT><ET>11:59:59</ET><SC><PD><BD>2007-12-17</BD><ED>2007-12-19</ED></PD></SC><PR>5</PR></TOD><HOL><ST>1</ST><PD><BD>2007-07-03</BD><ED>2007-07-04</ED></PD><PD><BD>2007-12-25</BD><ED>2008-01-02</ED></PD><PA><UI>1</UI><NR>5</NR><RT>1</RT><RD>0</RD></PA><PA><UI>3</UI><NR>3</NR><RT>1</RT><RD>0</RD></PA><PR>7</PR></HOL></FND></SNR>
Operations
This section describes the operational interfaces for the Single Number Reach feature. The following interfaces are described:
•
•
Operator CLI Interface
To support Single Number Reach, the Single Number Reach and SNR_ACT tokens have been added to the CLI interface. A Single Number Reach table has been added to the CLI interface. For complete CLI information, refer to the Cisco BTS 10200 Softswitch CLI Database.
Single Number Reach Feature-Config and Feature-Config-Base Table
The type-value pairs listed in Table 2 are added to the feature-config-base.
SNR_ACT Feature-Config and Feature-Config-Base Table
The type-value pairs listed in Table 3 are added to the feature-config-base.
Subscriber Feature Data Table
The subscriber-feature-data table stores feature status, failed PIN attempts, PIN status (NEWPIN, LOCKEDPIN, PIN) and access PIN. The subscriber can unlock the PIN if the PIN is locked after repeated failed PIN attempts. The subscriber-feature-data table displays the number of PIN attempts as well. The PIN status for the feature SNR_ACT is saved in the subscriber-feature-data table as a type-value pair. Besides the current values (NEWPIN, PIN) for PIN-TYPE, a new type LOCKEDPIN is needed. A new type-value pair PINATTS (number of consecutive failed pin attempts) is added for SNR_ACT feature.
Table 4 lists type-value pairs added or updated in the subscriber-feature-data table.
Table 4 Subscriber Feature Data
SNR_ACT
PINTYPE
NEWPIN, PIN, LOCKEDPIN
LOCKEDPIN
SNR_ACT
PINATTS
Integer
0
SNR Table
The SNR table (Table 5) defines the functionality associated with the BTS 10200 Call Agent.
Table Name: SNR
Table Containment Area: Feature Server
Table Contents:
1.
2.
3.
The Command Line Actions are: Show, add, change, delete, audit, sync, and help
•
•
•
•
•
•
•
•
•
Primary Key Token(s): sub-id
Add Rules: Either the snr_profile or the file field is specified.
Change Rules: Either the snr_profile or the file field is specified.
Delete Rules:
When only the ID is specified, all other entries with the same ID are removed.
Single Number Reach XML Schema
The SNR table stores SNR profile data, as shown in Figure 3. When provisioning a subscriber using CLI, the subscriber ID and the corresponding XML file populate the SNR table. When provisioning a subscriber from a third party system, the subscriber ID and the XML content populate the SNR table.
Note
Figure 3 Single Number Reach - XML Data Schema
The schema below defines the Single Number Reach profile XML format. The XML format is provided here for raw XML file modification, and has the definitions of different XML segments.
<?xml version="1.0" encoding="UTF-8" ?><xs:schematargetNamespace="urn:ietf:params:xml:ns:cisco:bts:feature:snr"xmlns:xs="http://www.w3.org/2001/XMLSchema"xmlns:snr="urn:ietf:params:xml:ns:cisco:bts:feature:snr"elementFormDefault="qualified" attributeFormDefault="unqualified"><xs:annotation><xs:documentation>Copyright (c) 2007-2008 Cisco Systems, Inc. All RightsReserved. BTS10200 Single Number Reach Profile Schema.Version: 06.00.01.V00</xs:documentation><xs:documentation>Note: The corresponding .xml instances should be stripped ofextra white spacing and tab indentations, to ensure they donot exceed the maximum size of 8K (8192) bytes. They shouldalso not contain any semicolons or single-quotes anywhere,including in the header of the file.</xs:documentation></xs:annotation><xs:simpleType name="tStatus" final="list restriction"><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="0" /><xs:maxInclusive value="1" /><xs:enumeration value="0"><xs:annotation><xs:documentation>Inactive</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>Active</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType><xs:simpleType name="tMultipleInvocation"final="list restriction"><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="0" /><xs:maxInclusive value="1" /><xs:enumeration value="0"><xs:annotation><xs:documentation>Multiple SNR Invocation disallowed forsubscriber. While SNR already invoked for thissubscriber, subsequent calls to this subscriberwill be sent to voicemail.</xs:documentation></xs:annotation></xs:enumeration><xs:enumeration value="1"><xs:annotation><xs:documentation>Allow Multiple SNR Invocation for thissubscriber, if the FeatureConfigAllow-Multiple-Invocation=Y. Even if SNR isalready invoked for this subscriber, subsequentcalls will also try to invoke SNR.</xs:documentation></xs:annotation></xs:enumeration></xs:restriction></xs:simpleType><xs:simpleType name="tDate" final="list restriction"><xs:annotation><xs:documentation>Date range limited to 2000-01-01 -> 2127-12-31, with notime zone offset extension.</xs:documentation></xs:annotation><xs:restriction base="xs:date"><xs:pattern value="2[0-1][0-9]{2}-[0-1][0-9]-[0-3][0-9]"></xs:pattern></xs:restriction></xs:simpleType><xs:simpleType name="tTime" final="list restriction"><xs:annotation><xs:documentation>Time range limited to 00:00:00 -> 23:59:59, with no timezone offset extension.</xs:documentation></xs:annotation><xs:restriction base="xs:time"><xs:pattern value="[0-2][0-9]:[0-5][0-9]:[0-5][0-9]"></xs:pattern></xs:restriction></xs:simpleType><xs:complexType name="tPeriod"><xs:sequence><xs:element name="BD" type="snr:tDate" /><xs:element name="ED" type="snr:tDate" /><xs:any namespace="##any" processContents="skip"minOccurs="0" maxOccurs="unbounded"></xs:any></xs:sequence></xs:complexType><xs:simpleType name="tWeekDay" final="list restriction"><xs:annotation><xs:documentation>List of day numbers, where SUN=0, MON=1, TUE=2, WED=3,THU=4, FRI=5, SAT=6. Example: MON,WED,FRI = 135</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:pattern value="[0-6]{1,7}" /><xs:minLength value="1" /><xs:maxLength value="7" /></xs:restriction></xs:simpleType><xs:complexType name="tSchedule"><xs:choice><xs:element name="WD" type="snr:tWeekDay" /><xs:element name="PD" type="snr:tPeriod" /></xs:choice></xs:complexType><xs:simpleType name="tVersion" final="list restriction"><xs:restriction base="xs:string"><xs:patternvalue="[0-9]{2}\.[0-9]{2}\.[0-9]{2}\.[A-Za-z][0-9]{2}" /><xs:minLength value="12" /><xs:maxLength value="12" /></xs:restriction></xs:simpleType><xs:simpleType name="tPriority" final="list restriction"><xs:annotation><xs:documentation>The larger value means higher priority.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="1" /><xs:maxInclusive value="7" /></xs:restriction></xs:simpleType><xs:simpleType name="tNumberOfRings" final="list restriction"><xs:annotation><xs:documentation>A value of 15 means continue ringing indefinitely until asystem or device timeout is reached.A value of 0 means do not ring this UE at all - this canbe used to temporarily prevent calling this UE, withoutneeding to completely remove the UE from the schedule.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="0" /><xs:maxInclusive value="15" /></xs:restriction></xs:simpleType><xs:simpleType name="tRingDelay" final="list restriction"><xs:annotation><xs:documentation>The time (in units of number of rings) to wait beforestarting to ring this UE. Since each ring correlates toabout 6 seconds, a value of 5 means wait about 30seconds before start ringing this UE.</xs:documentation></xs:annotation><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="0" /><xs:maxInclusive value="15" /></xs:restriction></xs:simpleType><xs:simpleType name="tRingType" final="list restriction"><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="0" /><xs:maxInclusive value="7" /></xs:restriction></xs:simpleType><xs:simpleType name="tAOR" final="list restriction"><xs:restriction base="xs:anyURI"><xs:minLength value="1"></xs:minLength><xs:maxLength value="64"></xs:maxLength></xs:restriction></xs:simpleType><xs:simpleType name="tDN" final="list restriction"><xs:restriction base="xs:string"><xs:pattern value="[0-9]+" /><xs:minLength value="1" /><xs:maxLength value="26" /></xs:restriction></xs:simpleType><xs:simpleType name="tDescription" final="list restriction"><xs:annotation><xs:documentation>SingleQuotes and Semicolons not allowed in the XML.</xs:documentation></xs:annotation><xs:restriction base="xs:string"><xs:minLength value="0" /><xs:maxLength value="32" /><xs:pattern value="[^';]*"></xs:pattern></xs:restriction></xs:simpleType><xs:simpleType name="tUeIdx" final="list restriction"><xs:restriction base="xs:unsignedByte"><xs:minInclusive value="1" /><xs:maxInclusive value="10" /></xs:restriction></xs:simpleType><xs:complexType name="tUE"><xs:choice><xs:element name="DN" type="snr:tDN" /><xs:element name="AR" type="snr:tAOR" /></xs:choice></xs:complexType><xs:complexType name="tParticipant"><xs:sequence><xs:element name="UI" type="snr:tUeIdx" /><xs:element name="NR" type="snr:tNumberOfRings"minOccurs="0" default="3" /><xs:element name="RT" type="snr:tRingType" minOccurs="0"default="1" /><xs:element name="RD" type="snr:tRingDelay" /><xs:any namespace="##any" processContents="skip"minOccurs="0" maxOccurs="unbounded" /></xs:sequence></xs:complexType><xs:complexType name="tAddressEntry"><xs:sequence><xs:element name="DS" type="snr:tDescription" minOccurs="0"default="Description Not Entered" /><xs:element name="UI" type="snr:tUeIdx" /><xs:element name="UE" type="snr:tUE" /><xs:any namespace="##any" processContents="skip"minOccurs="0" maxOccurs="unbounded" /></xs:sequence></xs:complexType><xs:complexType name="tAddressBook"><xs:sequence><xs:element name="AE" type="snr:tAddressEntry"minOccurs="0" maxOccurs="10" /></xs:sequence></xs:complexType><xs:complexType name="tTOD"><xs:sequence><xs:element name="DS" type="snr:tDescription" minOccurs="0"default="Description Not Entered" /><xs:element name="ST" type="snr:tStatus" /><xs:element name="BT" type="snr:tTime" /><xs:element name="ET" type="snr:tTime" /><xs:element name="SC" type="snr:tSchedule" /><xs:element name="PA" type="snr:tParticipant" minOccurs="0"maxOccurs="7" /><xs:element name="PR" type="snr:tPriority" /><xs:any namespace="##any" processContents="skip"minOccurs="0" maxOccurs="unbounded" /></xs:sequence></xs:complexType><xs:complexType name="tHoliday"><xs:sequence><xs:element name="ST" type="snr:tStatus" /><xs:element name="PD" type="snr:tPeriod" minOccurs="0"maxOccurs="18" /><xs:element name="PA" type="snr:tParticipant" minOccurs="0"maxOccurs="7" /><xs:element name="PR" type="snr:tPriority" /><xs:any namespace="##any" processContents="skip"minOccurs="0" maxOccurs="unbounded" /></xs:sequence></xs:complexType><xs:complexType name="tFindMe"><xs:sequence><xs:element name="TOD" type="snr:tTOD" minOccurs="0"maxOccurs="6" /><xs:element name="HOL" type="snr:tHoliday" /><xs:any namespace="##any" processContents="skip"minOccurs="0" maxOccurs="unbounded" /></xs:sequence></xs:complexType><xs:complexType name="tSingleNumberReach"><xs:sequence><xs:element name="VER" type="snr:tVersion" /><xs:element name="MI" type="snr:tMultipleInvocation"minOccurs="0" default="1" /><xs:element name="ABK" type="snr:tAddressBook" /><xs:element name="FND" type="snr:tFindMe" /><xs:any processContents="skip" minOccurs="0"maxOccurs="unbounded" /></xs:sequence></xs:complexType><xs:element name="SNR" type="snr:tSingleNumberReach"><xs:unique name="uniqueTodHolPriority"><xs:annotation><xs:documentation>The priorities for all of the TOD and HOL schedulesneed to be unique. This ensures that when there isan overlap of more than one schedule beingapplicable at a particular time, the desired higherpriority schedule will be chosen.</xs:documentation></xs:annotation><xs:selector xpath="snr:FND/snr:TOD | snr:FND/snr:HOL" /><xs:field xpath="snr:PR" /><xs:field xpath="snr:ST" /></xs:unique><xs:key name="keyUI"><xs:selector xpath="snr:ABK/snr:AE" /><xs:field xpath="snr:UI" /></xs:key><xs:keyref name="keyTodParUIRef" refer="snr:keyUI"><xs:annotation><xs:documentation>Ensure that the specified TOD UIs exist in theaddress book.</xs:documentation></xs:annotation><xs:selector xpath="snr:FND/snr:TOD/snr:PA" /><xs:field xpath="snr:UI" /></xs:keyref><xs:keyref name="keyHolParUIRef" refer="snr:keyUI"><xs:annotation><xs:documentation>Ensure that the specified HOL UIs exist in theaddress book.</xs:documentation></xs:annotation><xs:selector xpath="snr:FND/snr:HOL/snr:PA" /><xs:field xpath="snr:UI" /></xs:keyref></xs:element></xs:schema>Subscriber Web-Based Interface
The subscriber web-based interface is not provided by Cisco, but by the service provider. The interface can invoke CLI commands to allow the subscriber to configure Single Number Reach options. Subscriber user IDs and passwords, used to control access, are not stored on the BTS 10200, but maintained by the service provider elsewhere.
Subscriber IVR-Based Interface
This section describes the subscriber IVR-based interfaces. It includes the following:
•
•
•
•
•
Accessing the Single Number Reach IVR Menu
A Single Number Reach subscriber can set options using an IVR-based interface accessible from any UE. The subscriber calls a known DN (like a toll-free number) and enters the user ID and PIN to hear a configuration menu. Because this interface uses the master number as the user ID, the master number must be a DN and not an AOR.
IVR Authentication
Figure 4 shows user ID authentication for Single Number Reach.
Figure 5 shows the PIN authentication for the Single Number Reach feature. The detailed IVR prompts are listed in Table 6.
Figure 4 User ID Authentication
Figure 5 PIN Authentication
Single Number Reach Main Menu
After the user ID and PIN are authenticated, the subscriber hears a list of options available on the main menu (based on current Single Number Reach status):
1. Activate or configure forwarding to a single number2. Activate forwarding per your schedule3. Activate forwarding straight to voicemail4. Deactivate all SNR forwarding features9. Exit this SNR system0. To hear these instructions repeatedFigure 6 details the Single Number Reach main menu options and play Single Number Reach status. Detailed IVR prompts are listed in Table 6.
Figure 6 Play Single Number Reach Status and Main Menu Options
Single Number Reach (Forwarding Per Schedule) Activation
Figure 7 shows the Single Number Reach (find-me) activation. Detailed IVR Prompts are listed in Table 6.
Figure 7 Single Number Reach (Forwarding Per Schedule) Activation
CFU Activation
After the subscriber chooses 1 to activate CFU, he or she hears the current forward-to number is and submenu choices:
1. Forward all calls to this number2. Change Forward-To number9. Return to previous menu0. Repeat this menuA check verifies the CFU number against the dial plan. Speed dial codes are not valid CFU numbers.
VMA Activation
After the subscriber chooses 3 to activate VMA, a check verifies the subscriber has VMA then the feature is activated.
Single Number Reach Deactivation
After the subscriber chooses 4 to deactivate features, Single Number Reach, CFU, and VMA are deactivated.
Single Number Reach IVR Prompts
Table 6 gives details about the prompts used in the Single Number Reach IVR menus. The IVR prompts display how to traverse the Single Number Reach IVR tree. The IVR prompts provide important information on how to modify the different parts of Single Number Reach through the IVR system. Some prompts are split into multiple messages or combined into single messages when played. In the IVR prompts, a PIN is used instead of a password. This lets the subscriber know the prompts are for the Single Number Reach IVR PIN instead of the Single Number Reach web interface password and prevents reuse of existing similar password prompts.
Billing
A new Single Number Reach feature ID has been added to the billing interface for the Single Number Reach and SNR_ACT features. Table 7 lists the billing interface updates for the Single Number Reach feature.
For answered calls, two full-call CDRs are generated; one for the original call terminating on the master number and one for the call picked up by the final terminating party. All other forked calls have one CDR per call.
If a call goes to voice mail after SNR_ACT, two billing records are created; one for SNR_ACT and one for VM_Access.
Because Single Number Reach (follow-me) uses CFU and VM service logic, the invocation of follow-me shows in CFU and VM billing records.
Measurements
Table 8 lists Single Number Reach counters. These counters are kept on a BTS 10200 system-wide basis rather than for each subscriber.
Use the report measurement-pots-local-summary command to generate a report of the counters.
Because Single Number Reach (follow-me) uses CFU and VM service logic, the invocation of follow-me shows in CFU and VM counters.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R))Copyright © 2008 Cisco Systems, Inc. All rights reserved.
