19 Operation on an ISDN Access
ARGUS 152
231
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 check
should extend outside of the local exchange, it is possible to perform the Service check 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:
If the outgoing call is not successful, it is not possible to make a statement about an
incoming call. Therefore, you will never see “- +” or “- *” on the display.
+
-
*
=
=
=
suppl. service supported
suppl. service not supported
No definite assessment can be
made so an error code is displayed.
In such case, it is recommended that
you have someone place a call to
the access under test using this
service.
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.
-
An outgoing call with this service is not possible.
+ *
The call was sent successfully, the call to the remote end failed (e.g. remote
end busy thus no B channel was available for the call back).
*
Wrong number, no B channel available or other error.
Test results:
