Cisco Unified MeetingPlace Release 6.1 -- About NSF Codes
m (1 revision)
Latest revision as of 21:11, 28 March 2011
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.
- NSF code value (which service or feature is desired).
- See the About the NSF Code Value.
- Optional Carrier Identification Code (CIC) that identifies which carrier is providing a service or feature.
- Optional modifying parameter.