|
|
The CMA agent provides support for management and control of call and media resources. It manages connections (accept and drop). It provides player/recorder services such as play, record, and delete. It also provides DTMF detection and generation.
It is unique in that its primary purpose is to manage and control call and media resources within the DAP architecture. In order to accomplish this task, the CMA must communicate via H.323. This section describes the configuration of the following:
 |
Note To change the circuit switched line (T1 or E1) parameters, see the Cisco AS5300 Universal Access Server manual. |
The CMA (TNT) requires only SERVICE entries that specify AMM (ACB) hosts to which to route startapp requests. The token used by the CMA (TNT) to search the Domain Services Routing table for an Application object is the DNIS or RDNIS (depending on setting of lookup by CMA (TNT) parameter) associated with an incoming call to one of the CMA agent's ports.
Step 2 Edit $PARMLIB/parms/TNT/Route.<hostname>. Add a line:
SERVICE APP <hostname> *
|
Note uOne requires the CMA (TNT) and the ACB to be on the same gateserver. Therefore, the <hostname> should be the same as that of the CMA (TNT) agent. |
This is required only if SMSI (aka SMDI) is used to set and clear MWI (or stutter dialtone).
The CMA (TNT) can communicate SMSI information over an SMSI link on RS-232 serial port 1 of the computer on which it is running. The SMSI communication with the switch or adjunct occurs through the CMA (TNT) SMSI resource module.
|
Note Only outbound SMSI (MWI) is supported. |
The SMSI link (from Switch or adjunct) must have a dedicated RS-232 asynchronous connection to the gateserver. It must be transmitting and receiving information according to Bellcore (Telcordia) specification TR-NWT-000283 (Simplified Message Desk Interface, Generic Performance Requirements and Generic Requirements).
The serial port device is usually the /dev/ttyb under Solaris. The port (B) should have no services (e.g., ttymon) running on it. See the applicable UNIX manual for more information about setting up services (e.g., with saf and port monitors like ttymon).
Step 2 Edit the $TNTHOME/parms/SMSI.ini
| Parameter Name | Description | Valid Values and Defaults |
Names of devices to be managed by the resource module are identified by their device descriptor name and listed in the [SMSI] section. | Valid Values: Default: N/A | |
The baud rate to be used on a given device for transmission and reception of SMDI messages. (See Xon, Xoff, and ModemControl). | Valid Values: 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400 Default = 9600 | |
A range of stations for which a specific device services MWI requests. Two stations, start and stop, are to be identified with a white space separator. The numbers may be any sequence of numbers (up to 33 digits) made up of the signals (digits) - 0123456789. The number of digits in the start and stop stations must be identical. | Valid Values: <= 33 digits Default: N/A | |
Used to enable/disable hardware flow control on the SMSI interface. Should be considered if the switch does not support software flow control (Xon, Xoff). | Valid Values: On, Off If this value is set to On, special care should be given to hardware interface characteristics. Software flow control requires only a three-wire RS-232 interface (transmit, receive, and ground), whereas hardware flow control (modem control) interfaces require as many as 25 (request to send, clear to send, data terminal ready, etc.). The RS-232 interface exists in a number of vendor-proprietary formats regarding pinouts for 9 versus 25 pin connectors, and this normally results in required onsite troubleshooting. Default = Off | |
The character size in bits for both transmission and reception on the SMSI interface. | Valid Values: 5, 6, 7, 8 Default = 8 | |
Parity setting used for transmission and reception of SMDI messages on a given device. | Valid Values: None, Odd, Even Default = None | |
Number of stop bits used for transmission and reception on the SMSI interface. | 1, 2 Default = 1 | |
Used to enable/disable start/stop output control on the SMSI interface. This will suspend output (MWI messages) when the switch sends a STOP character. Any input character received will resume transmission of MWI traffic to the switch. | Valid Values: On, Off If On, a received STOP character (0x13) suspends output and a received START character (0x11) restarts output. The STOP and START characters will not be read, but will merely perform flow control functions. Default = On | |
Used to enable/disable start/stop output control on the SMSI interface. This parameter may be useful in high SMSI message volume deployments. | Valid Values: On, Off If On, the SMSI interface transmits a STOP character when its input queue is nearly full, and a START character when enough input has been read so that the input queue is nearly empty again. Default = OFF | |
Used to enable a prefix for all transmitted MWI messages on a given device. The available prefix is a carriage-return line-feed sequence, necessary for the Selsius Call Manager interface. | Valid Values: None, CR_LF Default = None |
The following is a sample SMSI.ini file
[SMSI] Device1=/dev/ttyb [Device1] BaudRate=9600 Stations=0000000000 9999999999 ModemControl=Off DataBits=8 StopBits=1 Xon=On Xoff=On MWIMapping=Off
There are many SMSI Adjuncts on the market. The following are instructions on administering the Technologies Group VoiceBridge II Switch Integration Unit. Follow the instructions provided by the vendor for Installing and Configuring the VoiceBridge II Switch Integration Unit.
These instructions assume use of 4-digit extensions and a PBX. The following are settings that require changes from the defaults.
Step 2 From SETUP, select PARMS.
Step 3 Go back to SETUP and select PORTS.
Step 4 Go back to SETUP and select ADVANCED.
Step 5 Go back to the Main Menu. Select UTILS.
Step 6 From UTILS, select SERIAL.
Step 7 From SERIAL select CENTREX.
|
Note By convention, use the serial port settings shown below. They must match the settings used by the CMA to which the SMSI link is connected. |
Step 8 Go back to the UTILS menu. Select DATE/TIME.
Step 9 Set the current date and time.
The following table provides information about the parameters that affect the CMA agent. Descriptions, default values, and ranges of valid values are listed for each parameter.
| Section | Parameter Name | Description | Valid Values and Defaults |
[DBG] | |||
| INFO
| Informational (I-) - indicates data relating to normal operation. | Valid Values: Default = N/A |
| WARN
| Warning (W-) - generated when an inconsistency in processing occurs which will not have a negative effect on processing. | |
| ERROR | Includes both types of debugging indicated above, plus error (E-) messages. These are normally generated when DAP processing fails. | |
[TRACE] | |||
| STATE | When enabled, allows you to step through the code by easily matching sections that belong together. | Valid Values: ON, OFF Default: N/A |
| MODULES | Designates which modules have been identified for tracing. | Same as [DBG] |
[ROUTING] | |||
| PRIMARYSERVER | Not currently used. | N/A |
| SECONDARYSERVER | Not currently used. | N/A |
| DEFAULTAPPSERVICEID | Points to which to send a phone call. Application registers an ASI (Application Service ID). | Valid Values: TAPDance, UM Default: TAPDance |
| LOOKUPBY | Informs TNT which number will be used as a service id. | ANI, DNIS Default = DNIS |
[RESOURCE] | |||
| LOADCONFIG |
| PktBus, H323, TTSP |
[SESSION] | |||
| RESPONSEFORMAT |
| Valid Values: SP, TNT Default: SP |
| LOGGINGFORMAT |
| Valid Values: SP, TNT Default: SP |
[SD] |
|
|
|
| DurationTimeout |
| Default: 30 (seconds) |
[CONTAINER] | |||
| LOCALBASEPATH | A URL that refers to a container object located under the path specified by the container path. The value of LOCALBASEPATH is configurable and will be set at startup time. This form will be supported for all schemes. | Valid URL in the format of |
| CTTEMPBASEPATH | A URL that refers to a container object located under CTTEMP. The value of CTTEMP is configurable and will be set at startup time. This form will be supported only for the file scheme. | Valid URL in the format of
|
| DRIVERBASEPATH | The location of the available dynamic libraries that will handle different schemes (e.g., file, IMAP, etc.) |
|
| DYNAMICCACHESIZE | Number of phrases that can be cached. |
|
| SYSTEMCACHESIZE | Number of system prompts that can be cached. |
|
| RECORDFORMAT |
| Must be set to G729 for either G729 or G729a codec. |
[MEDIA] | |||
| DEFAULTFMT |
| Default = .wav |
| DEFAULTLENGTH |
| Valid Values: Default = 180 seconds |
[MEDIAFILEEXTENSION] | |||
| WAV |
| Default = .wav |
| 24kADPCM |
| 24kadpcm |
| 32kADPCM |
| 32kadpcm |
| 48kMuLawPCM |
| 48kmulawpcm |
| 64kMuLawPCM |
| 64kmulawpcm |
| 48kALawPCM |
| 48kalawpcm |
| 64kALawPCM |
| 64kalawpcm |
[MEDIAENCODING] | |||
| WAV |
| <valid values listed below> |
| 24kADPCM |
| ADPCM 6000 |
| 32kADPCM |
| ADPCM 8000 |
| 48kMuLawPCM |
| MULAW 6000 |
| 64kMuLawPCM |
| MULAW 8000 |
| 48kALaw |
| PCM 6000 |
| 64kALawPCM |
| PCM 8000 |
| G729 |
| G729 1000 |
[MEDIARATE] | |||
| WAV |
| <valid values listed below> |
| 24kADPCM |
| 6000 |
| 32kADPCM |
| 8000 |
| 48kMuLawPCM |
| 6000 |
| 64kMuLawPCM |
| 8000 |
| 48kALaw |
| 6000 |
| 64kALawPCM |
| 8000 |
| G729 | Please see sample G729 dial peer configuration in Appendix A"Case Studies - Gateway and Gatekeeper". | 1000 |
[MONITOR] | |||
| SESSIONENTRIES |
| Default = 250 |
| GROUPENTRIES |
| Default = 250 |
[SCR] | |||
| DestroyGroup |
| Default = OnIdle |
The following is a sample TNT.ini file
*/ [DBG] INFO=SCR RES GRP WARN=ALL ERROR=ALL [TRACE] STATE=ON MODULES=SCR SES [ROUTING] PRIMARYSERVER=mikey.amteva.com #ECONDARYSERVER=mikey.amteva.com DEFAULTAPPSERVICEID=TAPDance LOOKUPBY=DNIS [RESOURCE] LOADCONFIG=PktBus H323 [SESSION] RESPONSEFORMAT=SP LOGGINGFORMAT=SP [SD] DurationTimeout=30 [CONTAINER] LOCALBASEPATH=containers CTTEMPBASEPATH=temp DRIVERBASEPATH=lib/Container DYNAMICCACHESIZE=25 SYSTEMCACHESIZE=25 RECORDFORMAT=MULAW [MEDIA] DEFAULTFMT=WAV DEFAULTLENGTH=180 [MEDIAFILEEXTENSION] WAV=wav 24kADPCM=24kadpcm 32kADPCM=32kadpcm 48kMuLawPCM=48kmulawpcm 64kMuLawPCM=64kmulawpcm 48kALawPCM=48kalawpcm 64kALawPCM=64kalawpcm [MEDIAENCODING] WAV=G729 1000 24kADPCM=ADPCM 6000 32kADPCM=ADPCM 8000 48kMuLawPCM=MULAW 6000 64kMuLawPCM=MULAW 8000 48kALawPCM=PCM 6000 64kALawPCM=PCM 8000 G729=G729 1000 [MEDIARATE] WAV=1000 24kADPCM=6000 32kADPCM=8000 48kMuLawPCM=6000 64kMuLawPCM=8000 48kALawPCM=6000 64kALawPCM=8000 G729=1000 [MONITOR] SESSIONENTRIES=250 GROUPENTRIES=250 [SCR] DestroyGroup=OnIdle
The uOne and amisain applications and the SMSI interface use the Addressing and Dialing Rules for address expansion and manipulation and for dialing constraints. The DialMap.ini file defines the Addressing Rules and is discussed in detail in the next chapter.
| Parameter Name | Description | Valid Values and Defaults | ||||
The number of ports (DS0s) for inbound calls to be supported by the resource module.
| Valid range: 1-120 Default: None
| |||||
The vendor configuration file used for stack initialization. These files are located in $TNTHOME/parms/vendor. Valid vendor files are: Config_GK Config_GK_DTMF Config_GK_DTMF_729 Config_GK_RtpDTMF Config_NoGK Config_NoGK_DTMF Config_NoGK_DTMF_729 Config_NoGK_RtpDTMF | Valid vendor configuration file Default: None
| |||||
Identifies the name of the state machine script used for signaling control of the H.323 interface. These files are located in $TNTHOME/parms/state. | Valid state machine script Default: None | |||||
The starting port number used for establishing RTP connections. | Valid Range: 1000 - 9999 Default: None | |||||
Interval at which RTP transmissions occur (msec) for silence compressed encodings (SilenceCompression=On). Note that the VendorConfig file, as well as the gateway, will need to be configured accordingly. | Valid Range: 20 - 200 Default: 20
| |||||
Interval at which gatekeeper registration occurs (seconds). | Valid Range: None, 1 - 1000 Default: None | |||||
Amount of time to trim off the end of recorded phrases terminated by DTMF (voice hangup or end of data). Intended to squelch DTMF energy which may pass in the audio stream before the tone is detected. | Valid Range: 0 -5000 (msec) Default: 0 | |||||
URL for the container to be used for 'beep' functionality in record operations.
| Valid .wav file Default: N/A
| |||||
Identifies whether silence compression will be used in processing RTP data. This setting needs to be coordinated with the codec setting on the gateways in which the server will be deployed. | Valid Range: On, Off Default: None
| |||||
Identifies the method used to detect the DTMF digits. This setting needs to be coordinated with the dial-peer setting on the gateways in which the server will be deployed. | Valid Values: FFT, RTP, H245, DEFAULT
Default: None | |||||
Identifies RTP header data marker bit implementation. This value needs to correspond to the gateway(s) behind which the resource is to be deployed. | Valid Values: CiscoVCWare, H225 Default: CiscoVCWare | |||||
Enables remapping of the H225 SETUP CalledParty/CallingParty fields via regexp/DialMap functionality. Note that the DialMap.ini configuration file should contain H225CALLEDPARTY / H225CALLINGPARTY / H225REDIRECTEDPARTY / H225CALLTYPE configuration sections to use this feature. | Valid Values: None, CalledParty, CallingParty, CallType, Redirected Number Default: None | |||||
Dictates the location for RDNIS and CallType in the H225 setup message | Valid Values: NonStandardData, NonStandardControl Default: NonStandardControl
| |||||
Specifies the DNIS to be used in absence of network information which might be received as channel associated signaling (CAS) or common channel signaling (CCS). This number is presented as the LocalNumber parameter to an application instance. It is also used for routing, as well as the 'From' number in evaluating a ports' ability to dial a specific phone number via the DialMap utility. | Valid DNIS Default: N/A | |||||
Indicates whether to use gateway or gatekeeper routing for outbound calls. | Valid Values: GKRouted, DirectRouted Default: GKRouted | |||||
IP address of the gateway used for outbound calls. | Valid IP address Default: 0.0.0.0 | |||||
RTPBridgeType | Where the RTP/voice streams are bridged when doing a Hairpin Bridge. | Valid Values: GateServer, GateWay Default: GateServer | ||||
FastStartOutbound | Allows CMA to use fast start (H.323 fast connect) procedure for outbound calls. | Valid Values: On/Off Default: Off
|
The following is a sample H323.ini file
[H323] MaxPorts=2 VendorConfig=Config_NoGK_DTMF StateDef=H323.Radvision.ini RtpStartPort=7000 GKRegistrationInterval=None RecordTrim=100 RecordBeepContainer=file:///system/440beep.wav SilenceCompression=On DTMFDetect=DEFAULT H225SetupMapping=CallingParty CalledParty DNISToken=8045551212 OutboundCallType=DirectRouted OutboundRouterIP=172.24.160.75
RADIUS accounting information is useful for billing, especially for outbound calls.
Step 2 There are two components to configure to enable RADIUS billing on a gateway—
For information on gateway configuration to enable RADIUS billing for outbound calls, see Appendix A Case Studies: Gateway and Gatekeeper.
|
Note The TTS software provided by Lernout & Hauspie (L&H) must be procured through your systems integrator (SI), or directly from L&H. If you need more information on procuring software, please talk to your SI or account representative. |
The following steps are necessary for implementing the TTS feature.
Step 2 These must be placed in the $TNTHOME/vendor/lhttsh/lib directory.
Step 3 Configure $PARMLIB/TNT/parms/TTSP.ini
| Parameter Name | Description | Valid Values and Defaults | ||
The maximum number of TTS calls to be supported by the resource module. | Valid range: 1-96 Default: 5 | |||
Signal to send to application if tear down occurs with the TTSP resource allocated.
| Valid range: 0-9 Default: 0 |
Step 4 Configure the $PARMLIB/TNT/parms/TNT.ini with the TTS Player (TTSP) resource module entry:
Posted: Mon Sep 25 20:20:09 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.