Version
Chapter 2
Configuring NMS CAS
2.1 Introduction
2.2 Configuring Using the oamsys Utility
2.3 Sample Configuration Files
2.3.1 AG 2000 Board: Loop Start Protocol
2.3.2 AG Quad T1 Board: WNK Protocol
2.3.3 AG 4000 E1 Board: MFC-R2 Protocol
2.3.4 CG 6000C Board: MFC-R2 Protocol
2.4 Configuring Using the agmon Utility
2.5 Sample AG Configuration Files
2.5.1 AG 2000 Board: Loop Start Protocol
2.5.2 AG-E1 Board: MFC-R2 Protocol
2.5.3 AG Quad T1 Board: WNK Protocol
2.5.4 AG 4000 Board: MFC-R2 Protocol
2.1 Introduction
A configuration file is a text file that lists the type, location, and role of each board on a PC chassis. It also specifies what software modules are loaded to each board's memory. With Natural Access 4.0 or later, use the
oamsys
utility with system configuration files and board keyword files to set up your boards for NMS CAS. See the
NMS OAM System User's Manual
for more details about using NMS OAM and its utilities and the OAM service API. Using Natural Access 3.0 or earlier, the
agmon
utility is used to load and monitor AG boards according to AG configuration files.
agmon
reads the AG configuration file and configures the AG boards accordingly.
One or more sample configuration files are installed with each protocol software package. These sample configuration files are country- and protocol-specific, and include statements that make the protocol run appropriately for a particular country.
This chapter describes how to configure boards to use NMS CAS. Whether you use the
oamsys
utility or use
agmon
depends on which version of Natural Access you are using:
For Natural Access 4.0 or later, this chapter describes how to edit NMS OAM configuration files or set keywords so that the
oamsys
utility configures and monitors the boards properly for the protocol software you are using.
For Natural Access 3.0 or earlier, this chapter describes how to edit configuration files so that
agmon
configures boards properly for the protocol software you are using.
This chapter provides sample configuration files for various boards and protocols.
For more information about configuration files, refer to the
appropriate board installation and developer's manual. For Natural Access 4.0 or later, also refer to the
NMS OAM System Users Manual
. For Natural Access 3.0 or earlier, refer to the
AG Runtime Configuration and Developer's Manual
.
2.2 Configuring Using the oamsys Utility
For systems using Natural Access 4.0 or later, specify configuration information for all boards in the system in an NMS OAM system configuration file and in board keyword files. These files reference managed components that specify whether a board performs MVIP switching, which board is the MVIP clock master, which software modules to transfer to the board's memory on startup (including which TCPs to load), and other settings. To learn how to use NMS OAM to modify your configuration and set up the CAS software, see the board-specific installation manual and the
NMS OAM System User's Manual
.
To configure the boards based on the information in the NMS OAM configuration file, run
oamsys
.
oamsys
transfers all software modules specified in the file to each board, and performs any other configuration activities needed. You should also start
oammon
, which monitors the boards for errors and other events.
Use
oamcfg
to change system information or board parameters after the system is running.
oamsys
,
oamcfg
, and
oammon
are installed with Natural Access. They require Natural Access 4.0 or later to run in Server mode or Multi mode.
oamsys.cfg
is the system configuration file that contains information about all the boards in the system and specifies which configuration files to load. For more information, see the
NMS OAM System User's Manual
.
2.3 Sample Configuration Files
The following sections show sample configuration files for CAS protocol applications on various hardware configurations using Natural Access 4.0 or later. See the board-specific installation and developer's manual for more details about configuring the boards.
2.3.1 AG 2000 Board: Loop Start Protocol
The following sample NMS OAM configuration file describes an AG 2000 board using a Loop Start protocol in the USA (with eight ports with 600 Ohm network line impedance). The board is configured to run as a stand alone unit.
CAS protocol-specific items are shaded.
TCPFiles[0] = nocc.tcp
TCPFiles[1] = lps0.tcp
Indicate which TCP to load to the board. This setting is protocol-specific.
The first statement loads the no call control protocol. The second statement loads the loop start protocol.
XLaw = mu-LAW
Defines voice signaling bit patterns sent to the network when the TCP is not active. This is country-specific.
Note: Mu-law is a companding algorithm used for digital trunks. AG 2000 boards need to know the originating companding law in order to generate an analog voice signal.
DLMFiles[0] = gtp.leo
DLMFiles[1] = voice.leo
DLMFiles[2] = svc.leo
Specify optional runtime components to be transferred to the coprocessor on the board (leo files are Loadable Executable Objects).
The first statement loads the trunk protocol engine. The second one loads the play and record manager. The third one loads the DSP function manager.
NetworkInterface.Analog[0..7].ConfigFile = a2usals6.slc
Specifies the AG 2000 board with loop start signaling type and 600 Ohm line impedance. Country-specific settings.
Clocking.HBus.ClockSource = OSC
Specifies the source from which this board derives its timing. Setting OSC defines the board as a clock master.
Clocking.HBus.ClockMode = STANDALONE
Specifies the CT bus clock that the board drives. Set a board in standalone mode so the board references its own clocking information.
DSP.C5x.DSPFiles[0] = signal DSP.C5x.DSPFiles[1] = tone DSP.C5x.DSPFiles[2] = dtmf
DSP.C5x.DSPFiles[3] = mf
DSP.C5x.DSPFiles[4] = callp
DSP.C5x.DSPFiles[5] = ptf DSP.C5x.DSPFiles[6] = echo.m54
DSP.C5x.DSPFiles[7] = oki.m54
DSP.C5x.DSPFiles[8] = rvoice.m54
DSP.C5x.DSPFiles[9] = voice.m54
DSP.C5x.DSPFiles[10] = wave.m54
Install DSP program files. For this configuration, you will need at least the statements shown.
The following DSP functionality is defined by this configuration:
· Out-of-band channel associated signaling
· Beep, tone generation, dial
· DTMF and silence/energy detectors
· MF detection
· Call Progress detection
· Pure tone filters
· Echo cancellation
· OKI-style play, record
· Raw voice
· NMS ADPCM play and record
· Wave-style play, record
2.3.2 AG Quad T1 Board: WNK Protocol
The following sample NMS OAM configuration file describes one AG Quad T1 board set up using a Wink Start TCP for the USA.
CAS protocol-specific items are shaded.
TCPFiles[0] = wnk0.tcp
Indicate the TCP to load to the board. The setting here is protocol-specific.
The statement loads the wink start protocol.
Xlaw = MU-LAW
Defines the switch idle codes.
RunFile = sysqn.run
Specify runtime components to be loaded to the board. This is board and protocol specific.
CCMode = NONE
Specifies the level of call control DSP resources allocated for Channel Associated Signaling (CAS) protocols running on the board. The statement specifies that call control resource management is not required.
Clocking.HBus.ClockSource = NETWORK
Specifies the source from which this board derives its timing.
Specifies a digital trunk as the board's clock source.
Note: If you select
NETWORK
, you must complete
Clocking.HBus.ClockSourceNetwork
.
Clocking.HBus.ClockSourceNetwork = 1
Specifies the number of a trunk that the board uses as an external network clocking source for its internal clock.
Clocking.HBus.ClockMode = STANDALONE
Specifies the CT bus clock that the board drives.
Set a board in standalone mode so the board references its own clocking information.
NetworkInterface.T1E1[0..3].FrameType = D4
NetworkInterface.T1E1[0..3].LineCode = AMI_ZCS
Set up trunk information for the board to match the connected equipment.
DSP.C5x.DSPFiles[0] = tone.dsp
DSP.C5x.DSPFiles[1] = callp.dsp
DSP.C5x.DSPFiles[2] = dtmf.dsp
DSP.C5x.DSPFiles[3] = voice.dsp
DSP.C5x.DSPFiles[4] = mf.dsp
# DSP.C5x.DSPFiles[X] = rvoice.dsp
# DSP.C5x.DSPFiles[X] = okiply.dsp
# DSP.C5x.DSPFiles[X] = okirec.dsp
# DSP.C5x.DSPFiles[X] = wavply.dsp
# DSP.C5x.DSPFiles[X] = wavrec.dsp
These statements install DSP program files. For this configuration, you will need at least the statements shown. The following DSP functionality is defined by this configuration:
· Beep, tone generation, dial
· Call Progress detection
· DTMF and silence/energy detectors
· NMS ADPCM play and record
· MF detection, compelled sequences
# Uncomment and put in the correct counter:
· Raw voice
· OKI-style play
· OKI-style record
· Wave-style play
· Wave-style record
2.3.3 AG 4000 E1 Board: MFC-R2 Protocol
The following sample NMS OAM configuration file describes one AG 4000 E1 board set up using a MFC-R2 TCP.
CAS protocol-specific items are shaded.
TCPFiles[0] = mfc0.tcp
Indicate the TCP to load to the board. The setting here is protocol-specific.
The statement loads the MFC-R2 TCP.
VoiceIdleCode = 0xd5
SignalIdleCode = 0x9
Defines voice signaling bit pattern sent to the network when the TCP is not active. This is country-specific.
Specifies the A-Law silence, idle bit pattern.
LoadFile = ag4000.lod
RunFile = ag4000.cor
Specify runtime components to be loaded to the board. This is board and protocol specific.
DLMFiles[0] = gtp.leo
DLMFiles[1] = voice.leo
DLMFiles[2] = svc.leo
Specify optional runtime components to be transferred to the coprocessor on the board (leo files are Loadable Executable objects).
The first statement loads the trunk protocol engine. The second one loads the voice manager. The third one loads the DSP function manager.
Clocking.HBus.ClockSource = NETWORK
Specifies the source from which this board derives its timing.
Specifies a digital trunk as the board's clock source.
Note: If you select
NETWORK
, you must complete
Clocking.HBus.ClockSourceNetwork
.
Clocking.HBus.ClockSourceNetwork = 1
Specifies the number of a trunk that the board uses as an external network clocking source for its internal clock.
Clocking.HBus.ClockMode = STANDALONE
Specifies the CT bus clock that the board drives.
Set a board in standalone mode so the board references its own clocking information or a digital network source.
NetworkInterface.T1E1[0..3].FrameType = CEPT
NetworkInterface.T1E1[0..3].LineCode = HDB3
Set up trunk information for the board to match the connected equipment.
DSP.C5x.DSPFiles[0] = tone.m54
DSP.C5x.DSPFiles[1] = callp.m54
DSP.C5x.DSPFiles[2] = dtmf.m54
DSP.C5x.DSPFiles[3] = voice.m54
DSP.C5x.DSPFiles[4] = mf.m54
DSP.C5x.DSPFiles[5] = ptf.m54
DSP.C5x.DSPFiles[6] = signal.m54
# DSP.C5x.DSPFiles[X] = echo.m54
# DSP.C5x.DSPFiles[X] = rvoice. m54
# DSP.C5x.DSPFiles[X] = oki.m54
# DSP.C5x.DSPFiles[X] = wave.m54
Install DSP program files. For this configuration, you will need at least the statements shown.
The following DSP functionality is defined by this configuration:
· Beep, tone generation, dial
· Call Progress detection
· DTMF and silence/energy detectors
· NMS ADPCM play and record
· MF detection, compelled sequences
· Pure tone filters
· Out-of-band channel associated signaling
# Uncomment and put in the correct counter:
· Echo cancellation
· Raw voice
· OKI-style play, record
· Wave-style play, record
2.3.4 CG 6000C Board: MFC-R2 Protocol
The following sample configuration file describes a CG 6000C board using an MFC-R2 protocol. For more information about board-specific entries, refer to the
CG 6000C Installation and Developer's Manual
.
CAS protocol-specific items are shaded.
Clocking.HBus.ClockSource = OSC
Clocking.HBus.ClockSourceNetwork = 1
Specifies the source from which this board derives its timing. Settings OSC define the board as a clock master.
Clocking.HBus.ClockMode = STANDALONE
Specifies the CT bus clock that the board drives.
Set a board in standalone mode so the board references its own clocking information.
TCPFiles = mfc0.tcp
Indicate the TCP to load to the board. The setting here is protocol-specific.
The statement loads the MFC-R2 TCP.
DSPStream.VoiceIdleCode[0..3] = 0xd5
DSPStream.SignalIdleCode[0..3] = 0x9
Defines the voice signaling bit pattern sent to the network when the TCP is not active. This is country-specific. Specifies the A-Law silence, idle code pattern.
Set up trunk information for the board:
NetworkInterface.T1E1[0..3].Type = E1
Specifies the trunk type for each trunk on the board.
NetworkInterface.T1E1[0..3].Impedance = G703_120_OHM
Specifies the type of cable connecting to the telephone network.
NetworkInterface.T1E1[0..3].SingalingType = CAS
Determines how voice and signaling information is routed to and from the E1 or T1 trunk and DSP resources.
NetworkInterface.T1E1[0..3].FrameType = CEPT
Defines the framing format for the current board or trunk.
NetworkInterface.T1E1[0..3].LineCode = HDB3
Specifies the ones density maintenance method used on the trunk line to maintain a clear channel transmission.
DLMFiles[0] = cg6krun
Specifies an optional runtime component (modular extension to the core file) to be transferred to the board by the configuration file.
DSP.C5x[0..31].Libs[0] = cg6kliba
Specifies the DSP library file name.
DSP.C5x[0..31].XLaw = A_LAW
Determines the DSP hardware companding mode.
Note: All DSPs must have the same value.
DSP.C5x[0].Files = qtsignal callp tone dtmf ptf mf echo
DSP.C5x[1..31].Files = voice tone dtmf echo rvoice callp ptf wave oki ima \
gsm_ms g726 mf
Specifies digital signal processor function modules (DPFs) loaded to CG 6000C board DSPs for applications to use on a per-call/channel basis.
Resource[0].Definitions = ( dtmf.det_all & echo.ln20_apt25 & ptf.det_2f & \
tone.gen & \callp.gnc & ptf.det_4f & \
( (rvoice.rec_mulaw & rvoice.play_mulaw) | \
(rvoice.rec_alaw & rvoice.play_alaw) | \
(rvoice.rec_lin & rvoice.play_lin) | \
(voice.rec_16 & (voice.play_16_100 | voice.play_16_150 | voice.play_16_200)) | \
(voice.rec_24 & (voice.play_24_100 | voice.play_24_150 | voice.play_24_200)) | \
(voice.rec_32 & (voice.play_32_100 | voice.play_32_150 | voice.play_32_200)) | \
(voice.rec_64 & (voice.play_64_100 | voice.play_64_150 | voice.play_64_200)) | \
(wave.rec_11_16b & wave.play_11_16b) | \
(wave.rec_11_8b & wave.play_11_8b) | \
(oki.rec_24 & (oki.play_24_100 | oki.play_24_150 | oki.play_24_200)) | \
(oki.rec_32 & (oki.play_32_100 | oki.play_32_150 | oki.play_32_200)) | \
(ima.rec_24 & ima.play_24) | \
(ima.rec_32 & ima.play_32) | \
(gsm_ms.frgsm_rec & gsm_ms.frgsm_play) | \
g726.rec_32 | g726.play_32) )
DebugMask = 0x0
Specifies the type and level of tracing that the board performs.
2.4 Configuring Using the agmon Utility
For systems using Natural Access 3.x or earlier, create an AG configuration file for your setup by using a text editor to modify or combine the contents of the example files installed on your system. Include any necessary entries from the sample configuration files included with the protocol software. Save the file with the file name
ag.cfg
(by default
agmon
looks for a file with this name).
agmon
uses the following algorithm to search for the AG configuration file:
Windows NT and Windows 2000:
agmon
searches in the current working directory, and then in the directories specified in the
AGLOAD
environment variable.
UNIX:
agmon
searches in the current working directory, and then in the directory
/opt/nms/ag/cfg
.
Note:
Several other sample configuration files also reside in the same directory as
ag.cfg
. These files are installed with various NMS software packages to accommodate different types of board configurations. For board specific settings, refer to the appropriate hardware installation and developer's manual.
2.5 Sample AG Configuration Files
The following sections show sample AG configuration files for CAS protocol applications on various hardware configurations using Natural Access 3.x.
Note:
Certain statements (for example
Idlecode
) may be included in either the
COMMON
section or the
BOARDS
section of the AG configuration file. Statements in the
COMMON
section apply to
all
boards in the system. Statements in the
BOARDS
sections apply to specific boards in the system.
2.5.1 AG 2000 Board: Loop Start Protocol
The following sample AG configuration file describes an AG 2000 board using a loop start protocol in the USA (with four ports with 900 ohm network line impedance and four ports with 600 ohm network line impedance). The board is configured to run as a stand alone unit, without MVIP connectivity.
Shaded statements are country-specific settings for the LPS0 TCP. For more information about board-specific entries, refer to the
AG 2000 Installation and Developer's Manual
.
[AGBOARD]
The AG configuration file must begin with this statement.
#--- COMMON section ---
Any statements in this section of the file will apply to all boards listed in the BOARDS sections below.
TCP = nocc.tcp
TCP = lps0.tcp
Indicate the TCP to load to the board. The setting here is protocol-specific.
The first statement loads the no call control protocol. The second statement loads the loop start protocol.
AG2DspFile = voice.m54
AG2DspFile = tone.m54
AG2DspFile = signal.m54
AG2DspFile = callp.m54
AG2DspFile = ptf.m54
AG2DspFile = dtmf.m54
Install DSP program files. They are installed on all boards listed in this file, since they appear in the
COMMON
section of this file. For this configuration, you will need at least the statements shown.
The following DSP functionality is defined by this configuration:
· NMS ADPCM play and record
· Beep, tone generation, dial
· Out-of-band channel associated signaling
· Call Progress detection
· Cleardown and precise tone detection
· DTMF and silence/energy detectors
RunModule = gtp.leo
RunModule = svc.leo
RunModule = voice.leo
Specify optional runtime components to be transferred to the coprocessor on the board. (
leo
files are Loadable Executable Objects).
#--- BOARDS section ---
Board 0
Indicates the beginning of a description of a particular board. The number appearing here will be used to refer to the board in software.
PCIBUS = 0
Defines the PCI bus location of the board.
PCISLOT = 19
Defines the slot location of the board on the PCI bus.
ClockRef = OSC
Configures the telephony bus clock. Setting
OSC
defines the board as a clock master.
EnableMvip = No
Determines whether MVIP switching is enabled for the board. Set to
Yes
to enable switching.
Note: Certain default switch connections are made on AG boards when
EnableMVIP=No
that are not made when
EnableMVIP=Yes
. For more information, see your AG board documentation.
IdleCode = MU-LAW
Defines voice signaling bit patterns sent to the network when the TCP is not active. This is country-specific.
Note: Mu-law is a companding algorithm used for digital trunks. AG 2000 boards need to know the originating companding law in order to generate an analog voice signal.
QSLAC 0..3 = a2usals9.slc
QSLAC 4..7 = a2usals6.slc
This statement defines SLAC files to program QSLAC devices. In this case, these statement define US loop start signaling 900 ohm lines on 0,1,2,3 and US loop start signaling 600 ohm lines on ports 4,5,6,7.
End Board
Indicates the end of the description for board 0.
2.5.2 AG-E1 Board: MFC-R2 Protocol
The following sample AG configuration file describes an AG-E1 board (at I/O address 2C0, IRQ 12) running an MFC-R2 TCP specific to the People's Republic of China.
Shaded statements are settings specific to the MFC-R2 TCP. For more information about board-specific entries, refer to the appropriate installation and developer's manual.
[AGBOARD]
The AG configuration file must begin with this statement.
#-- COMMON section --
Any statements in this section of the file will apply to all boards listed in the
Board
sections below.
Interrupt = 12
Specifies the interrupt to be used by all ISA AG boards in your system.
DspFile = voice_a.dsp
DspFile = signal_a.dsp
DspFile = dtmf_a.dsp
DspFile = callp_a.dsp
DspFile = tone_a.dsp
DspFile = mf_a.dsp
Install DSP program files. They are installed on all boards listed in this file, since they appear in the
COMMON
section of this file. For this configuration, you will need at least the statements shown. You can add others.
The
_a
following each file name indicates that these files are for A-law encoding. If your setup calls for mu-law encoding, remove the
_a
from each file name.
RunFile = systn.run
Defines the coprocessor software to be used. It is board and protocol-specific. For AG-T1 and AG-E1 boards with digital CAS protocol software, use
systn.run
.
#-- BOARDS section --
Board 0
Indicates the beginning of a description of a particular board. The number appearing here will be used to refer to the board in software.
Address = 2C0
This is the board's I/O address. Each board must have a unique address. The address is set here and on the board's face using switches. The
Address
statement is not necessary for PCI-based boards, but is necessary for ISA boards.
TCP = mfc0.tcp
Indicates the TCP to load to the board. The setting here is protocol-specific. For MFC-R2 under Natural Access, specify
mfc0.tcp
.
IdleCode = 0xD5,0xB
Defines voice signaling bit patterns sent to the network when the TCP is not active. This is country-specific.
The setting shown here is specific to the People's Republic of China. The first hexadecimal number represents the digital pattern to be output on the voice channels of the E1 trunk.
0xD5
is the silence pattern for A-law companding. The second number is the value of the signaling bit associated with each voice channel.
0xB
(ABCD = 1011) is the MFC-R2 idle signaling code in the PRC.
ClockRef = NET1
Configures the clock.
NET1
causes the board to derive the local clock using the clock extracted from the E1 line.
EnableMVIP = No
Determines whether MVIP switching is enabled for the board. Set to
Yes
to enable switching.
Note: Certain default switch connections are made on AG boards when
EnableMVIP=No
, that are not made when
EnableMVIP=Yes
. For more information, see your AG board documentation.
LineCode = HDB3
Defines the trunk line coding algorithm. The setting made here is
high-density bipolar 3
, which is the default setting for the AG-E1.
End Board
Indicates the end of the description for board 0.
2.5.3 AG Quad T1 Board: WNK Protocol
The following sample AG configuration file describes one AG Quad board set up using the Wink Start TCP for Hong Kong.
Shaded statements are settings specific to the Wink Start TCP. For more information about board-specific entries, refer to the appropriate installation and developer's manual.
[AGBOARD]
#---COMMON section---
Any statements in this section of the file will apply to all boards.
DspFile = dtmf.dsp
DspFile = voice.dsp
DspFile = callp.dsp
DspFile = tone.dsp
These statements install the DSP files. They are installed on all boards, since they appear in the
COMMON
section.
TCP = wnk0.tcp
Indicates the TCP to load to the board. The setting here is protocol-specific. For Wink Start under Natural Access, specify
wnk0.tcp
.
IdleCode = MU-LAW
#IdleCode = 0x7f, 0xa
Default for Hong Kong.
Change to this setting if the protocol uses a pulse-on-idle signaling polarity (see
Chapter 17
for details on the WNK protocol implementation in Hong Kong).
RunFile = sysqn.run
Defines the runfile software to be loaded to the board.
#-- BOARDS section --
Board 0
The beginning of the configuration for a specific board.
PCIbus = 0
PCIslot = 1
CCMode = HIGH
EnableMVIP = NO
DigitalMode=CAS
Applies to all trunks, since it is outside of the
Trunk
section (run the
blocate
utility to find the correct PCI bus and slot).
Trunk 0
Beginning of description for Trunk 0.
FrameType = D4
LineCode = AMI
End Trunk
Trunk 1..3
Beginning of description for Trunks 1, 2, and 3.
LineCode = AMI_ZCS
End Trunk
End Board
End of configuration for Board 0.
2.5.4 AG 4000 Board: MFC-R2 Protocol
The following sample AG configuration file describes one AG 4000 board set up using the MFC-R2 protocols, for CCITT Blue Book implementation (CR2).
Shaded statements are settings specific to the MFC-R2 TCP. For more information about board-specific entries, refer to the appropriate installation and developer's manual.
[AGBOARD]
Any statements in this section will apply to all boards.
#--- COMMON section ---
LoadFile = ag4000.lod
Define the runfile software to be loaded to the board.
RunFile = ag4000.cor
This is board-specific.
RunModule = gtp.leo
RunModule = voice.leo RunModule = svc.leo
Specify optional runtime components to be transferred to the coprocessor on the board (leo files are Loadable Executable objects).
The first statement loads the trunk protocol engine. The second one loads the voice manager. The third one loads the DSP function manager.
#--- BOARDS section ---
Board 0
The beginning of the configuration for a specific board.
DSP.C5x.DSPFiles[0] = tone.m54
DSP.C5x.DSPFiles[1] = callp.m54
DSP.C5x.DSPFiles[2] = dtmf.m54
DSP.C5x.DSPFiles[3] = voice.m54
DSP.C5x.DSPFiles[4] = mf.m54
DSP.C5x.DSPFiles[5] = ptf.m54
DSP.C5x.DSPFiles[6] = signal.m54
# DSP.C5x.DSPFiles[X] = echo.m54
# DSP.C5x.DSPFiles[X] = rvoice.m54
# DSP.C5x.DSPFiles[X] = oki.m54
# DSP.C5x.DSPFiles[X] = wave.m54
Install DSP program files. For this configuration, you need at least the statements shown.
The following DSP functionality is defined by this configuration:
· Beep, tone generation, dial
· Call Progress detection
· DTMF and silence/energy detectors
· NMS ADPCM play and record
· MF detection, compelled sequences
· Pure tone filters
· Out-of-band channel associated signaling
# Uncomment and put the correct counter:
· Echo cancellation
· Raw voice
· OKI-style play, record
· Wave-style play, record
PCIBUS = 1
PCISLOT = 4
Use blocate utility to find the correct PCI bus and slot.
TCP = mfc0.tcp
Indicates the TCP to load to the board. The setting here is protocol-specific.
This statement loads the MFC-R2 TCP.
IdleCode = 0xd5,0x9
Defines voice signaling bit patterns sent to the network when the TCP is not active. This is country-specific.
This statements specifies A-Law silence, idle signaling bit code.
ENABLEMVIP = NO
This line determines whether MVIP switching is enabled for the board. Set to Yes
to enable switching.
LINECODE = HDB3
The LineCode statement defines the trunk line coding algorithm.
End Board
End of configuration for Board 0.
Version
Want to send us feedback on our documentation? Email:
Tech_Pubs@nmss.com
Copyright © 2001, Natural MicroSystems, Inc. All rights reserved.