Version





The nms303tool prompts you to enter a global program trace mask variable that specifies the amount of on-screen HDLC information the program displays while it runs.

NMS_GR303Initialize: Result=NMSGR303_SUCCESS
InterfaceId=0:
NMS: boardNb=0 trunkNb=0 timeslotNb=24
NMS: boardNb=0 trunkNb=0 timeslotNb=12
NMS: boardNb=0 trunkNb=1 timeslotNb=24
NMS: boardNb=0 trunkNb=1 timeslotNb=12

nms303tool initializes the Access303 or Exchange303 library. Access303 starts internal tasks including the AimTaskAr303 which makes it possible for nms303tool to communicate with the Aztek aim303 utility. aim303 is a part of the Aztek software and should be used in conjunction with nms303tool integration tests.
nms303tool displays the following message:
AR303AimTask: waiting for AIM Socket Connection on port 4200
Note: nms303tool calls NMS_GR303PhDataRequest internally when the Access303 or Exchange303 library calls Ar303PhDataRequest. All HDLC data received from the IDT or RDT side, as well as any HDLC transmit or receive errors, are passed to the Access303 or Exchange303 stack through the Ar303PhDataIndication function.
where hostname is the host name of the machine where nms303tool is running.
nms303tool displays the following message:
AR303AimTask: Menu Socket Connected on port 4200
Enter options at the aim303tool menu (for controlling Access303 or Exchange303 stack).

where hostname specifies the system where the NMS GR303 library is running.
NMS_GR303Initialize: Result=NMSGR303_SUCCESS
nms303tool displays a Result=NMSGR303_SUCCESS message when the interface is provisioned.
InterfaceId=0:
NMS: boardNb=24 trunkNb=0 timeslotNb=24
NMS: boardNb=12 trunkNb=0 timeslotNb=12
NMS: boardNb=24 trunkNb=1 timeslotNb=24
NMS: boardNb=12 trunkNb=1 timeslotNb=12

The nmsv5tool prompts you to enter a global program trace mask variable that specifies the amount of on-screen HDLC information the program displays while it runs. Available trace masks include:
Note: Options 17 and 18 (calling NMS_V5PhSendData and NMS_V5SendSA7Bit) are only available in standalone mode. When the NMS V5 library is integrated with the AV5 library, nmv5demo calls NMS_V5PhSendData and NMS_V5SendSA7Bit internally as requested by the AV5 library V5PhDataRequest, V5SetSA7ToOne and V5SetSA7ToZero functions.

NMS_V5Initialize: Result=NMSV5_SUCCESS
NMS: boardNb=0 trunkNb=0
17:30:43E1Status Function InterfaceId=0 Status: LOS=0 LOF=0 AIS=0 RAI=0 CRCErr=0 FEBE=0 N_SA7_0=0 N_SA7_1=1
NMS: boardNb=0 trunkNb=1
NMS_V5StartInterface: Result=NMSV5_SUCCESS

nmsv5tool initializes the AV5 library. The AV5 library starts internal tasks including the AIM task, which makes it possible for the aimv5 utility to communicate with the Aztek AV5 stack.
nmsv5tool displays the following message:
Aztek_waitconnect: waiting for Menu Socket Connection on port 5200
Note: nms303tool calls NMS_GR303PhDataRequest and NMS_GR303SendSA7Bit and the AV5 stack calls V5PhDataRequest, V5SetSA7ToOne, and V5SetSA7ToZero. nmsv5tool passes all HDLC data received from the IDT side, as well as any HDLC transmit and receive errors, to the AV5 stack by using the AV5PhDataIndication function. nmsv5tool also sends E1 status reports to the AV5 library by calling the AV5 library function V5E1Status.
where hostname is the host name of the machine where nmsv5tool is running.
nmsv5tool displays the following message:
Aztek_waitconnect: AIM socket connected on port 5200, file descriptor 648
Enter options at the aim303 menu for controlling Access303 stack.

|
Aztek AV5 Library Parameters
|
NMS V5 Library Parameters
|
|---|---|
|
E1=0 CChannel=16
|
boardNb=0, trunkNb=0, trunkNb=16
|
|
E1=1 CChannel=16
|
boardNb=0, trunkNb=1, trunkNb=16
|
NMS_V5Initialize: Result=NMSV5_SUCCESS
nmsv5tool displays a Result=NMSGRV5_SUCCESS message when the interface is provisioned.
19:31:46E1Status Function InterfaceId=0 Status: LOS=0 LOF=0 AIS=0 RAI=0 CRCErr=0 FEBE=0 N_SA7_0=0 N_SA7_1=1
NMS: boardNb=0 trunkNb=0
V5PhDataIndication AztecReturn=0x30
19:31:46E1Status Function InterfaceId=0 Status: LOS=0 LOF=0 AIS=0 RAI=0 CRCErr=0 FEBE=0 N_SA7_0=0 N_SA7_1=1
NMS: boardNb=0 trunkNb=1
V5PhDataIndication AztecReturn=0x30
Then, nmsv5tool displays a Result=NMSV5_SUCCESS message.
Version