3842

Cause Value 2. A request has been made to use a transit network or common carrier that cannot be accessed. The equipment sending this cause event does not recognize the transit network.

3843

Cause Value 3. No route to destination. Request received to route call through a transit network that is recognized but not allowed to carry the call or not able to serve the destination. The service provider cannot route the call to the indicated destination. Communication Manager does not originate Cause Value 3.

The repair steps are based on Tier 4 recommendations:

1. Check the numbers sent for any missing prefixes or service values that were needed to access the network.
2. Check the Cause Information Element Location Code.
3. Check Communication Manager administration:

   1. Dial plan/Location: The home NPA is administered incorrectly, causing incorrect code conversion.
   2. IXC: The IXC matching pattern is administered incorrectly or not at all on the dial plan, causing incorrect IXC manipulation.
   3. AAR/ARS digit conversion: The wrong digit string substitution is being made. The call is being routed into the wrong network and over the wrong route pattern. Further conversion is needed but the dial string is restricted from further conversion.
   4. AAR/ARS digit analysis: Call type is incorrect for the call being made specifying the wrong type of number and/or number plan information, or it is preventing code conversion from taking place. Call is being routed to the incorrect route pattern where the incorrect digit manipulation and/or code conversion is taking place.
   5. ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion at the route pattern.
   6. Route pattern: Incorrect code conversion due to wrong entries in NPA, prefix mark, and toll list/prefix mark fields. Deleting the wrong number of digits or inserting the wrong digits. Failing to strip IXC or international code digits, stripping a user-dialed IXC code, or IXC forcing the call to the wrong inter-exchange carrier. Number format changed to a format incorrect for the call type. The incorrect service or feature is specified for the call being made on a CBC trunk group preference.

3846

Cause Value 6. The far-end switch has indicated that the B-channel (trunk) is not acceptable for use in the call for which it was requested.

This could indicate an administration problem. For example, the local switch and the far-end switch have different B-channels administered. It could also reflect the occurrence of a normal race condition. For example, the local switch has requested use of a B-channel that the far-end switch had just reserved for use on another call.

3858

Cause Value 18. The switch sent a message to the far-end switch or terminal adapter that did not respond in the time allowed. The remote device/endpoint did not respond with an ALERTING/PROGRESS/CONNect indication within the time administered in the T303 or T310 timers Q.931 specification. Cause Value 18 indicates high traffic conditions in the serving network or noisy conditions on the span carrying the D-channel messaging. The noise is causing the loss of messages being sent to the remote device. The remote device might also be unable to respond to the incoming SETUP message. This Cause Value has end-to-end significance and should always be passed back through the network to the user.

3878

Cause Value 38. The far-end switch has indicated that the network is not functioning correctly and that the condition may last a relatively long period of time. For example, immediately re-attempting the call may not be successful. The network is out of order.

3890

Cause Value 50. A request to use a network service has been denied. Administration somewhere on the network has indicated that the requested service has not been subscribed 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.

3892

Cause Value 52. Protocol detail; may offer a clue if customer is having calls denied with an unexpected intercept tone. If the customer is complaining of unexpected intercept tones and no other cause can be found, escalate the problem and provide the next tier with this Error Log information.

3894

Cause Value 54. Protocol detail; may offer a clue if customer is having calls denied with an unexpected intercept tone. First, eliminate any transitory state mismatch problems by entering test port location for the trunk port shown in the Aux Data field. Service State Audit Test (#256) is the important test in the sequence. If this passes satisfactorily, yet the customer continues to complain of unexpected intercept tones and no other cause can be found, escalate the problem and provide the next tier with this Error Log information.

3902

FRANCE ONLY: Cause Value 62. Service not authorized.

Call rejected. This Cause Value has end-to-end significance and should always be passed back through the network to the user.

Cause Value 62 (VN4) indicates that the call could not be completed because the user has not subscribed to the service, feature, or supplementary service requested in the SETUP message. If the user is supposed to have access to this service, feature, or supplementary service, complete the required ordering process with the service provider.

Cause Value 62 (1TR6) indicates that the remote endpoint does not accept this call, although it could have accepted the call because the equipment is neither busy nor incompatible. The diagnostic information in the Cause information element might contain the user-supplied condition for why the call was rejected.

3903

Cause Value 63. Service or option not available, unspecified. This cause value is used to report a “service or option not available” event only when no other cause in the “service or option not available” class applies. This Cause Value shall either be passed to the user or mapped to Cause Value 41 (temporary failure) when it is received at a CO as part of SS7 call handling. Communication Manager does not originate Cause Value 63.

3905

Cause Value 65. Protocol detail; may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone. If the customer is complaining of unexpected intercept tones and no other cause can be found, escalate the problem and provide the next tier with this Error Log information.

3906

Cause Value 66. Protocol detail; may offer a clue if customer is having ISDN calls denied with an unexpected intercept tone. If the customer is complaining of unexpected intercept tones and no other cause can be found, escalate to the problem and provide the next tier with this Error Log information.

3909

Cause Value 69. A request to use a network service has been made, but the network has rejected the request because the requested service is not implemented. Follow the recommendation for Error Type 3890, Cause Value 50.

3910

Cause Value 70. Only restricted digital bearer capability available. The call could not be completed because the equipment sending this Cause Value only supports the restricted version of the requested bearer capability, and in the SETUP message, bearer capability was unrestricted. Communication Manager does not originate Cause Value 70.

The repair steps are based on recommendations from Tier 4 ISDN experience:

1. Check Communication Manager administration (network generated the Cause Value):

   1. Route pattern: An incorrect ITC and/or BCIE specified. These fields affect how the bearer capability is encoded in the SETUP message.
   2. The ITC administered on the originating endpoint might be incorrect for this call and/or the speed options in the device itself might be incorrect for calls over these ISDN facilities.
   3. Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint tandeming through Communication Manager to create a SETUP message with the wrong bearer capability.
   4. A call tandeming through Communication Manager ISDN trunk group to ISDN trunk group might have a bearer capability that is not supported by the outgoing ISDN facilities or network.
   5. A call tandeming through Communication Manager on a non-ISDN trunk group inter-working to an ISDN trunk group might have an incorrect bearer capability assigned on the incoming trunk group. The BC and ITC fields on the incoming trunk group may be set wrong.

3919

Cause Value 79. Service or option not implemented or unspecified. The call could not be completed because the equipment sending this Cause Value has not implemented a service, feature, or supplementary service requested by the user, and none of the other Cause Values in the Service or Option Not Implemented class apply. As an implementation option, this Cause Value might be mapped to Cause Value 41 (temporary failure) when it is received at a CO as part of SS7 call handling. Communication Manager does not originate Cause Value 79.

3928

Cause Value 88. A call was denied because a basic incompatibility existed between the type of call and either the facilities selected by the routing pattern or the called user. This error may offer a clue if the customer complains of receiving unexpected intercept tone.

3942

Cause Value 102. Recovery on timer expiry. No answer to CALL PROCEEDING.

The equipment sending this Cause Value sent or received a Layer 3 Q.931 message. Sending or receiving this message has initiated a Layer 3 timer that has expired. This Cause Value is being generated in conjunction with Q.931 protocol error handling procedures. The ISDN network between the user and the equipment generating the Cause Value might:

• Send no cause indication through the network.
• Send a more generic Cause Value through the network.

The repair steps are based on recommendations from Tier 4 ISDN experience:

1. Check the diagnostic information for the timer number that has expired.
2. Check that the protocols at each end of the interface match. For example, both sides are NI-2.
   If the ends of the interface are running different protocols, they might be running with different values for their Layer 3 timers. If the protocols at each end of the interface match, the Communication Manager timer might have expired because:

   1. The far-end never saw the message because the message was corrupted in transmission by noise on the D-channel. Check for any type of T1/E1 facility errors.
   2. The far-end is experiencing a high traffic condition and did not have the processing time to parse the sent message before the timer expired.
   3. Even though the message was seen to be generated in an internal Communication Manager trace, the message was never transmitted out onto the D-channel. Perform an external protocol capture on the D-Channel to confirm the transmission of the suspect message.

3942 (cont’d)

3942 (cont’d)