DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-947ISDN-SGR (ISDN-PRI Signaling Group)
9
3890 A request to use a network
service (e.g., SDN) has
been denied.
Administration somewhere
on the network has
indicated that the
requested service has not
been subscrib ed to or
purchased for this trunk.
This could be a local administration problem only, or a
mismatch between the local administration and that of the
network provider.
1. From the circuit pack and port number (in the Aux Data
field), determine the trunk group against which the error
was reported.
2. Display the trunk group form: If the trunk group is
Call-by-Call (Service Type is ‘‘cb c’’), check all routing
pattern forms containing this trunk group to see if the
Service/Feature fields contain th e correct network
services purchased for this trunk. If the trunk group is
not Call-by-Call, chec k that the Service Type field
contains the single network service purchased for this
trunk.
3. If local administration appears correct, c onsult with the
customer and/or the network provider to determine the
services that the customer has subscribed to for this
trunk group.
3892 Protocol detail; may offe r a
clue if customer is having
ISDN calls denied with an
unexpected intercept tone.
If customer is complaining of unexpected intercep t tones
when accessing ISDN trunks or PRI endpoints and no other
cause can be foun d, escalate the prob lem and provide th e
next tier with this Error Log information.
3894 Protocol detail; may offe r a
clue if customer is having
ISDN calls denied with an
unexpected intercept tone.
First, eliminate any transitory state mismatch problems by
issuing the test port UUCSSpp command for the trunk port
shown in the aux data field. Test #256 (Service State Audit)
is the important test in the sequence. If this passes
satisfactorily, yet the customer continues to complain of
unexpected intercept tones when accessing ISDN trunks or
PRI endpoints and no other cause can be found, escalate
the problem and p rovide the next tier with this Error Log
information.
3905 Protocol detail; may offe r a
clue if customer is having
ISDN calls denied with an
unexpected intercept tone.
If customer is complaining of unexpected intercep t tones
when accessing ISDN trunks or PRI endpoints and no other
cause can be foun d, escalate the prob lem and provide th e
next tier with this Error Log information.
3906 Protocol detail; may offe r a
clue if customer is having
ISDN calls denied with an
unexpected intercept tone.
If customer is complaining of unexpected intercep t tones
when accessing ISDN trunks or PRI endpoints and no other
cause can be found, escalate to the problem and p rovide
the next tier with this Error Log information.
Table 9-362. Descriptions and Recommendations for Error Types 3840-3928 — Continued
Error
Code Description Recommendation
Continued on next page