2-24
Cisco BTS 10200 Softswitch SIP Feature and Provisioning Guide, Release 5.0
OL-12397-13
Chapter2 SIP Subscribers
Cisco BTS 10200 Softswitch-Based Features
Planning VSCs In Networks with SIP Subscribers.
Some features require SIP subscriber to enter a series of numbers and characters on the SIP client or
handset. Typically, the subscriber dials VSC digits followed by additional dialing keys representing the
parameters for the feature call. For MGCP subscribers, the BTS 10200 sends a response tone or
announcement between the VSC code and the additional digits. However, for SIP endpoints, all the digits
are dialed at a stretch without waiting for an intervening response tone from the BTS10200. The
following paragraph explains how certain combinations of VSC can cause mismatches between the
feature the subscriber is attempting to manage versus the response of the BTS 10200, and how to plan
VSCs to avoid these mismatches.
You should not deploy certain combinations of VSCs on networks with SIP endpoints. If you deploy a
VSC longer than 2 digits, make sure that the longer VSC does not begin with the same sequence of
characters as one of the shorter VSCs. In some cases, the system might match the shorter string even if
the subscriber dialed the longer string. Consider the following example, for which the subscriber is
expected to dial a VSC followed by a DN.
A SIP subscriber is provisioned with *93 for Feature1 and *938 for Feature2, and dials
*938+2135551801 to invoke Feature2. The BTS 10200 receives *9382135551801 in the INVITE
message. By default, it takes the first six characters, in this case *93821, and uses this string to look up
the feature in the VSC table. There is no match for *93821, therefore the BTS 10200 proceeds as follows.
First, it uses *9 to look for a match in the VSC table and it cannot be found. Then it uses *93, finds a
match, and delivers Feature1. This is incorrect. The user's intention was to invoke Feature2 and not
Feature1. The solution is for the service provider to change one of the two VSCs (either *93 or *938) in
the VSC table.
Supported VSC-Enabled Features for SIP Endpoints
The following BTS 10200 Vertical Service Code (VSC) features are supported on SIP endpoints:
•Calling identity delivery and suppression, suppression part (CIDSS)
•Calling identity delivery and suppression, delivery part (CIDSD)
•Calling name delivery blocking (CNAB)
•Outgoing call bearing activation (OCBA), outgoing call bearing deactivation (OCBD), outgoing call
bearing interrogation (OCBI)
•Call forwarding unconditional activation (CFUA), call forwarding unconditional deactivation
(CFUD), call forwarding unconditional interrogation (CFUI)
Reminder ringback cannot be enabled for SIP subscribers. If you are turning on the Call Forward
Unconditional (CFU) feature for a SIP subscriber, make sure that reminder ring capability is turned
off. This should be done at a subscriber level.
Here is the command format at the feature level:
add feature fname=CFU; tdp1=TERMINATION_ATTEMPT_AUTHORIZED;
tid1=TERMINATION_ATTEMPT_AUTHORIZED; feature_server_id=FSPTC235; ttype1=R;
fname1=CFUA; fname2=CFUD; type1=MCF; value1=Y; type2=RR; value2=N;
description=CFU MCF multiple call forwarding allowed, RR ring reminder not
allowed;
And at the subscriber feature level:
add subscriber-feature-data sub_id=sip_sub2; FNAME=CFU; type2=RR; VALUE2=N;