Table Of Contents
Configuring Network Specific Facility Codes
About NSF Codes
About the NSF Code Type
About the NSF Code Value
About the Optional Carrier Identification Code
About the Optional Modifying Parameter
About Configuring NSF Codes
Configuring Network Specific Facility Codes
You may need to configure Network Specific Facility (NSF) codes for your Cisco Unified MeetingPlace system when making outdials directly to the PSTN (without an intervening PBX) on trunks using the ISDN protocol. This chapter explains how to configure your Cisco Unified MeetingPlace system with the correct NSF codes when necessary and includes the following sections:
•About NSF Codes
•About the NSF Code Type
•About the NSF Code Value
•About the Optional Carrier Identification Code
•About the Optional Modifying Parameter
•About Configuring NSF Codes
Note Usually NSF codes are used only in the U.S. and Canada.
About NSF Codes
To determine if your Cisco Unified MeetingPlace system requires NSF codes, ask your phone service provider. You determine this before installing your Cisco Unified MeetingPlace system.
If you do not set up the NSF codes properly, or if you do not configure them at all, you can encounter the following problems:
•Failed outdials—Outdials directly to the PSTN are rejected. However, outdials via an intervening PBX can work.
•Higher phone service costs—Outdials can work directly to the PSTN, but the standard or premium rates of the carrier may be applied, rather than discounted rates. As part of provisioning a service, a carrier can require that customers use specific NSF code information. This information must be sent out on every call to get a specific discounted service rate for the call.
The ISDN protocol allows phone service providers to add their own custom protocol extensions. These custom protocol extensions allow carriers to provide various localized services that are not defined in the general ISDN specifications. These custom protocol extensions are contained in the NSF Information Element (IE). They are generally called NSF codes for short. The NSF code is also called the Binary Facility Coding Value (BFCV).
NSF codes consist of the following:
•NSF code type (service or feature). See the "About the NSF Code Type" section.
•NSF code value (which service or feature is desired). See the "About the NSF Code Value" section.
•Optional Carrier Identification Code (CIC) that identifies which carrier is providing a service or feature. See the "About the Optional Carrier Identification Code" section.
•Optional modifying parameter. See the "About the Optional Modifying Parameter" section.
About the NSF Code Type
The NSF code type determines if the NSF is a service or feature. There are four NSF code types, as listed in Table 3-1.
Table 3-1 NSF Code Types
NSF Code Type
|
Example
|
Service
|
Software Defined Network (SDN) by AT&T
|
Feature
|
Billing Number preferred for ANI by AT&T
|
Service plus modifying parameter
|
Outwats and Tie Line by Bell Canada
|
Feature plus modifying parameter
|
Vari-A-Bill (Flexible Billing) by AT&T
|
About the NSF Code Value
The NSF code value indicates the specific ID of the service or feature. This value ranges from 0 to 31. Table 3-2 gives some common NSF code types and their corresponding NSF code value.
Table 3-2 Examples of NSF Code Values for Specific NSF Code Types
NSF Code Type
|
NSF Code Value (BFCV)
|
Software Defined Network (SDN) by AT&T
|
1
|
Billing Number preferred for ANI by AT&T
|
4
|
Outwats by Bell Canada
|
3
|
Vari-A-Bill by AT&T
|
9
|
Note The NSF code value is also called the Binary Facility Coded Value (BFCV).
About the Optional Carrier Identification Code
The Carrier Identification Code (CIC) is a four-digit code established by the FCC in the U.S. to identify each phone company. For example, the CIC for AT&T is 1288. If a subscriber has a variety of services available from various carriers, the CIC is used to select a carrier.
The CIC is not always included in an NSF code. The carrier that provides the connection from Cisco Unified MeetingPlace to the central office determines if the CIC is included in the NSF.
Note Some carriers abbreviate their CIC to three digits, dropping the most significant digit. When you request CIC information, you must determine if the carrier uses three or four digits.
About the Optional Modifying Parameter
The modifying parameter, if used, is a value from 0 to 255. For example, Bell Canada uses the modifying parameter as a Service IDentifier (SID). For their Outwats service, the NSF code is not complete unless it has a BFCV of 3 and an SID of 2. Another example is Vari-A-Bill by AT&T which has a BFCV of 9 and an SID of 6.
About Configuring NSF Codes
Do the following procedures to configure your NSF codes:
•To Create a New Protocol Table
•To Modify the New Protocol Table
•To Assign Port Groups to Use the New Protocol Table
•To Restart the Cisco Unified MeetingPlace System
•To Test the NSF Codes
To Create a New Protocol Table
Step 1 Access the CLI. If you do not already have terminal logging turned on, turn it on. For information on logging, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server.
Step 2 At the tech$ prompt, enter protparm. The following menu appears:
meetingplace:tech$ protparm
***** P R O T P A R M C O N F I G M E N U *****
1) View protocol parameter table(s)
2) Modify protocol parameter table
4) Delete protocol table(s)
Enter protocol table to copy from [0..99] : 3
Enter protocol table(s) to copy to [50-99] : 50
Copied to protocol table(s) 50.
Step 3 Copy a protocol table by entering 3.
Step 4 Enter the number of the protocol table from which you want to copy. In this example, it is protocol table number 3, so enter 3. See Table 3-3 for assistance with choosing which table to copy from.
Note If this is part of a software upgrade from a Cisco Unified MeetingPlace system before Release 5.1, the default protocol tables 3 and 4 are not correct. To resolve this, use the protparm command to delete tables 3 and 4. This restores them to the defaults as listed in Table 3-3.
Table 3-3 Protocol Table Defaults
T1 PRI Protocol Type
|
Protocol Table Number to Copy From
|
AT&T
|
2
|
Nortel
|
3
|
Bell
|
4
|
Step 5 Enter the number of the protocol table to which you want to copy. In this example, it is protocol table number 50, so enter 50.
Note The number for the new protocol table must be a number not already used by an existing protocol table. All Cisco Unified MeetingPlace systems have protocol tables 0 to 49 already configured, so when you create a new protocol table, use protocol table number 50 or higher.
Step 6 Exit the protparm command by entering x.
To Modify the New Protocol Table
Note The following procedure assumes that the information copied into the new protocol table in the "To Create a New Protocol Table" procedure is correct, with the exception of the NSF code information.
Step 1 Access the CLI. If you do not already have terminal logging turned on, turn it on. For information on logging, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server.
Step 2 At the tech$ prompt, enter protparm. The protparm command menu appears.
Step 3 Modify the protocol parameter table by entering 2.
Step 4 Enter the number of the new protocol table you created in the "To Create a New Protocol Table" procedure. In this example, it is table 50, so enter 50. See the following example:
Enter protocol table number [50..99] : 50
***** M O D I F Y M E N U *****
2) Modify general information
3) Modify incoming called party number processing (DDI)
4) Modify incoming calling party number processing (CLI)
5) Modify outgoing calling party information
6) Modify outgoing called party type of number (TON)
7) Modify outgoing called party numbering plan (NPI)
8) Modify outgoing private number definition
9) Modify outgoing local number definition
a) Modify outgoing long distance number definition
b) Modify outgoing international number definition
c) Modify outgoing Network Specific Facilities (NSF) codes
d) Modify outgoing NSF Carrier Identification Code (CIC)
Enter list command [table 50]: c
Step 5 Modify the outgoing NSF codes by entering c. Each time you press Enter, you move to the next line. See the following example:
Enter modify command [table 50]: c
---------------- PROTOCOL TABLE 50 ------------------
------- To skip over a field, just press <cr> -------
Outgoing Network Specific Facilities (NSF) Codes
------------------------------------------------
NSF code 1 type [ not used] :
BFCV 1 value [not used] :
Extra 1 param [not used] :
NSF code 2 type [ not used] :
BFCV 2 value [not used] :
Extra 2 param [not used] :
Enter modify command [table 50]:
Step 6 Enter the NSF code type. Depending on your Cisco Unified MeetingPlace configuration, it will be "service," "feature," "parm service," or "parm feature." See the "About the NSF Code Type" section.
Step 7 Enter the NSF code value (BFCV). See the "About the NSF Code Value" section.
Step 8 Enter the modified parameter, if there is one.
Step 9 (Optional) If your Cisco Unified MeetingPlace configuration uses a second NSF code, enter the appropriate information. If your Cisco Unified MeetingPlace configuration does not use a second NSF code, press Enter until you reach the modify command prompt.
Step 10 Modify the outgoing NSF CIC by entering d. See the following example:
Enter modify command [table 50]: d
---------------- PROTOCOL TABLE 50 ------------------
------- To skip over a field, just press <cr> -------
Outgoing NSF Carrier Identification Code (CIC)
------------------------------------------------
NSF code 1 type [ natl] :
Enter modify command [table 50]:
Step 11 Enter the CIC code type. Depending on your Cisco Unified MeetingPlace configuration, it will be "user," "natl," "intl," "user4," "natl4," or "intl4." See the "About the Optional Carrier Identification Code" section.
Step 12 Enter the CIC code.
Step 13 Go to the main protparm command menu by entering x.
Step 14 Exit the protparm command by entering x.
To Assign Port Groups to Use the New Protocol Table
Assign all port groups with ports using NSF codes to use the new protocol table.
Note Your Cisco Unified MeetingPlace system may have spans going to different carriers and each carrier may require a different NSF code. To resolve this, assign the ports from one carrier to one port group and the ports from a different carrier to a different port group. Configure the port groups to use different protocol tables. Configure the protocol table for each port group with the NSF code required by the carrier for that port group.
Step 1 Access the CLI. If you do not already have terminal logging turned on, turn it on. For information on logging, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server.
Step 2 At the tech$ prompt, enter port. The following menu appears:
***** P O R T / G R O U P C O N F I G M E N U *****
Step 3 Modify the port group record by entering 5. The second line in the following example appears:
Enter port group record number [0..31] : 0
------------ GROUP 0 ---------------
--- To skip over a field, just press <cr> ---
Activate the group? [y] :
Signaling [loop start] : protocol table
Number of DID digits [ 0] :
Step 4 Enter the number of the appropriate port group record. In this example, it is port group record 0, so enter 0. The rest of the preceding example appears.
Step 5 Continue pressing Enter until you reach Signaling.
Step 6 Select Signaling by entering protocol table.
Step 7 At Protocol table, enter the number of the appropriate protocol table. In this example, it is protocol table 50, so enter 50. Continue pressing Enter until you get back to the Enter command prompt.
Step 8 (Optional) Repeat this procedure if more than one port group uses NSF codes.
Step 9 Exit the port command by entering x.
To Restart the Cisco Unified MeetingPlace System
Step 1 Access the CLI.
Step 2 At the tech$ prompt, enter restart.
Step 3 Wait for the Cisco Unified MeetingPlace system to come back up.
To Test the NSF Codes
Note The trace utility called acsetrace can also be used to troubleshoot outdial problems.
Step 1 Access the CLI. If you do not already have terminal logging turned on, turn it on. For information on logging, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server.
Step 2 At the tech$ prompt, enter activity. The following menu appears:
meetingplace:tech$ activity
VUI Configuration: 1152 Sessions, 1200 Confs
*** VUI INTERNAL STATUS UTILITY ***
1) Quick Status of all Ports 4) Make Test Call
2) Verbose Status of Port Range 5) Show All Confs
3) Display complete Port Information 0) Quit
Enter the Command (0 -- 100): 4
Enter destination for your call:
Note The preceding example is for a Cisco Unified MeetingPlace 8112. For a Cisco Unified MeetingPlace 8106, there are 576 sessions and 576 conferences. See the highlighted values on line 2.
Step 3 To make a test call, enter 4. The Cisco Unified MeetingPlace system prompts you for a destination telephone number.
Step 4 Enter a nearby telephone number. The Cisco Unified MeetingPlace system prompt asks if you want specific ports.
Step 5 Enter t. The Cisco Unified MeetingPlace system prompt asks if you want to specify a range of ports.
Step 6 Enter f. The Cisco Unified MeetingPlace system prompt asks you for the port number.
Step 7 Enter a port number that is configured to use NSF codes. The Cisco Unified MeetingPlace system places the call.
If the call goes through, the NSF codes are correct.
If the call does not go through, retrace the steps in this chapter and verify that everything was done correctly. If it still does not work, contact Cisco TAC.
Step 8 Exit the activity command by entering 0.