Demonstrates a Natural Access application that specifies the server type on which a context is created and processed. Applications can specify that context processing occur within the application (inproc), on the local server (localhost), or on a remote server (server name or IP address). Applications using the OAM service must use a context created on a local or remote server.
testdm [options]
Where call control options are:
|
Call control option... |
Use this option to... |
|---|---|
|
-? |
Display the Help screen and terminate testdm. |
|
-@ host_name |
Specify the name or IP address of the host on which to create the context. Default: localhost |
|
-b board_# |
Specify the board number. Default: board 0 |
|
-p protocol |
Specify the name of the TCP. Refer to the NMS CAS for Natural Call Control Developer's Manual for a list of available protocols. |
|
-d digits |
Specify the number to dial. Default: 555 |
|
-m inslot,outslot |
Specify the port (DSP) addresses for incoming and outgoing calls respectively. Default: 0,2 |
Where OAM options are:
|
OAM option... |
Use this option to... |
|---|---|
|
-n name |
Specify the name of the managed object. |
|
-k keyword |
Specify the keyword name. If unspecified, the program displays all keywords. |
|
-f field |
Specify the desired field within keyword name keyword. |
|
-i index |
Specify an array index of keywords. Default: all |
|
-q |
Display the keyword qualifiers. |
|
-s text |
Display all keyword names containing the specified text. |
testdm works with any NMS board that has a processor and DSPs.
Note: Some TCPs supported by testdm do not work with some boards.
To use testdm:
Natural Access, NMS OAM, and a protocol must be installed on your system. Refer to the NMS CAS for Natural Call Control Developer's Manual for a list of available protocols.
Natural Access Server (ctdaemon) must be running either on a local or remote server. Use the -@ option to specify the name or IP address of a remote server. The test program uses the local server as the default.
testdm displays and sets keyword information for NMS OAM managed objects. The program starts threads that act as inbound and outbound parties. The program does the following:
Places a call.
Answers the call.
Plays a voice message.
Hangs up the line.
NMS OAM functions are performed on the local or remote server. Call control functions are performed within the processing space of the application (inproc).
The following procedure assumes you are testing on an AG 2000 board that has two lines connected through a central office simulator.
Complete the following steps to run testdm:
|
Step |
Action |
|
1 |
Navigate to the directory containing testdm. |
|
2 |
Start ctdaemon. |
|
3 |
Start testdm by entering the following command at the prompt: testdm -b n -p lps0 -d 555 -m slot1,slot2 |
|
4 |
If the test is successful, testdm prints Test passed. |