Table of Contents
Advertisement
8.2-20 Integration Volume
7. DISPLAY TEST
This test verifies that the ROLMphone 400 shows the correct call information for those units
configured for call processing.
a.
Connect the ROLMphone 400 to the jack position of the modular adapter associated with Unit 1,
Link 1 on the RIC board. (The link programmed for call processing on the RIC board.)
b. From phone C, call the pilot number for VMLINK (the pilot number for the Octel 200/300).
Does the ROLMphone 400 look like this?
CCCC
Phone C Name =
VVVV
VMLINK
NO
YES
c.
Hang up phone C.
BUSY FORWARD TEST
d. Cause phone C to be busy by taking it off-hook. Phone C should be programmed to forward on
Busy or RNA to the pilot number for the Octel 200/300 (VMLINK).
e.
From phone A, call the extension number for phone C.
f.
Does the ROLMphone 400 display look like this?
CCCC
Phone C Name =
AAAA
BFWD
YES
NO
RING NO ANSWER (RNA) FORWARD TEST
g. Put phone C back on-hook. From phone A, call phone C. Wait until the call forwards from phone
C to the VMLINK hunt group (RNA).
Octel 200/300
S.4.1
CCCC (Phone C Name)
=
Phone C extension number (the calling extension number).
The name programmed for phone C.
=
Pilot number for VMLINK phantom hunt group.
=
The name for CPI Links (required name).
Determine the cause and correct the problem before continuing.
'
Continue tests for each CPI Link configured.
'
CCCC Phone C Name
AAAA Phone A Name
=
Phone C extension number (the calling extension number).
The name programmed for phone C.
=
The extension (mailbox) number for the call forwarded to the Octel
200/300.
=
Busy forwarded.
Continue tests for each CPI Link configured.
'
Determine the cause and correct the problem before continuing.
'
VVVV VMLINK
BFWD
PB60019-01
Advertisement
Chapters
Table of Contents
