14 Operation on an ISDN Access
266
ARGUS 145
PLUS
There are PBXs that use separate call numbers for incoming and outgoing calls.
In this case, for the Service tests, you can enter a “remote” call number that
does not match the “own” number that is stored in the ARGUS.
If the Service test should extend outside of the local exchange, it is possible to
perform the Service test in an end-to-end mode. In this case, you must enter the remote
call number for a second terminal device. The ARGUS will then automatically check
whether the remote terminal can accept the call under the various services – in other
words, whether it is “compatible” with these services. In the test results, the second part
(, - or *) refers to the answer from the remote exchange.
The ARGUS will display the results of the
test once it is done. The ARGUS makes a
distinction between outgoing calls (the
first +, - or *) and incoming calls (the
, - or *).
Interpreting the test results:
+
-
*
=
=
=
Service supported
Service not supported
A definite statement cannot be
given, see the displayed error code
for the reason (see the table in the
appendix).
In this case, it is recommended that
you have someone place a call to
the access under test using this
service.
to scroll through the results
Close the results display and
open the next higher menu
Display
Explanation
+ +
The self call functions OK or the remote end can take the call for this service
+ -
The call was sent successfully, however, it was rejected at the remote end due
to a lack of authorization.
This is the error class D after a B-channel has been allocated, e.g. using a
SETUP_ACK or CALL_SENT.
Test results:
