Station Coverage Receiving Busy

[Naperguy1]

We have been receiving multiple reports of users who call another internal user. When the call is not answered, it follows coverage, but instead of getting the voicemail, it returns a busy signal. they hang up. Dial again. It goes through to voicemail.

Systems: Avaya CM 5.2.0.947.3 / Mod Messaging 5.1

VM is QSIG / Trunk group 99

A trace of a station revealed denial event 1195 with the denial report for that specific event pasted below. I'm trying to figure out if the problem lies in CM or MM. I believe it is CM.

EVENTS REPORT

Event Event Event Event First Last Evnt
Type Description Data 1 Data 2 Occur Occur Cnt

1195 Circ/channel unavail 20B F2C 07/22/07:59 07/28/10:34 255
1195 Circ/channel unavail 9E0 F2C 07/22/08:05 07/28/10:35 255
1195 Circ/channel unavail 30D F2C 07/22/08:15 07/28/10:36 255
1195 Circ/channel unavail 92E F2C 07/22/08:29 07/28/10:24 255

 

[LoopbackJack]

Do you have enough voicemail ports? Check your usage, sounds like you are running out of channels or you have some bad channels.

 

[Naperguy1]

69 trunk members / when this occurred, I statused the trunk group and only 3 were active. The rest were idle.

 

[demanding]

I have a very similar issue- but getting dead air instead of the busy. We have CM 5.2.1 with QSIG. We have VM and Modular Messaging 5.2 where it was reported on both and cannot be recreated. No channel issues. This just started a month ago after we upgraded a new location to CM 5.2.1 so I'm in agreement the problem is in CM. Will be escalating to our BP at the next complaint.

 

[LoopbackJack]

Do you have maintenance with Avaya? If so, I would call in a ticket and have them look at it.

 

[AvayaTier3]

C:\avayadoc\Aura CM5_2\CM5_2_avayadoc\CM52DenialEvents.pdf
page 32 of 154

Resource Unavailable Class Cause Values

Cause Value 21
[0x15/0x95] -
Call rejected
The remote endpoint did not accept this call, even though the equipment is
neither busy nor incompatible and it could have accepted the call.
Check the diagnostic information (DIAG) for the user-supplied condition for why
the call was rejected. See Cause Values and their meanings/interpretations on
page 13.

Cause Value 18
[0x12/0x92] -
No user responding/ No response from the remote device
The remote device/endpoint/PBX 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 ISDN network or
noisy conditions on the T1/E1 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 request.
This Cause Value has end-to-end significance and should always be passed back
through the network to the user.

Cause Value 34
[0x22/0xA2] -
No circuit/channel available/
Negative closed user group comparison (1TR6: AT&T ISDN Protocol)
Cause Value 34 indicates that the call cannot be completed because there is no
appropriate circuit/channel available to handle the call request, or congestion
exists within the ISDN network.

Communication Manager generates this Cause Value when a call is tandeming
through Communication Manager and the trunk group to be used for the outgoing
leg is:
- In "all trunks busy" condition
- Otherwise unavailable for service
- Unreachable from the incoming trunk group due to Class of Restriction (COR),
FRL, trunk-to-trunk transfer restrictions, or disconnect supervision
restrictions

Cause Value 34 (1TR6) indicates that the packet mode call was rejected because
the user is not a member of the remote end's Closed User Group (CUG), which is
a feature associated with packet mode calls similar to X.25 connection made over
the ISDN D-channel.

Communication Manager does not support packet mode sessions on D-channels,
therefore this is not applicable to Communication Manager.

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

Cause Value 42
[0x2A/0xAA] -
Switching equipment congestion
The call could not be completed because the switching equipment generating this
Cause Value is experiencing a period of high traffic.
This Cause Value has end-to-end significance and should always be passed back
through the network to the user.
Troubleshooting
Wait and try the call again later.

Cause Value 44
[0x2C/0xAC] -
Requested circuit/channel not available
The call was not completed because the circuit/channel requested for use in the
SETUP message was not available, and the call could not be negotiated to another
channel either because no other channel was available, or negotiation is not
supported or was not wanted for this call.

This Cause Value is generated when a glare condition is occurring and B-Channel
negotiation is not supported.

Communication Manager generates this Cause Value when:
- It is the NETWORK side of the interface and a glare condition is occurring on
the requested B-Channel.
- The B-Channel requested in the incoming SETUP message is not in the correct
maintenance state to handle a call (for example, it is busied out or undergoing
testing).

Troubleshooting
- CO switch default settings turn off channel negotiation support. Make a
specific request to turn on channel negotiation support when ordering CO
service.
- Check Communication Manager administration (network generated the Cause
Value).
- Trunk group form: When the Channel Negotiation field is set to exclusive,
Communication Manager requests B-Channels for calls without support for
negotiation so if at the remote end the requested B-Channel is unavailable for
whatever reason the call cannot be negotiated to a more acceptable B-Channel and
the call will be rejected with Cause Value 44. Set the Channel Negotiation field
to preferred to support channel negotiation.

Cause Value 47
[0x2F/0xAF] -
Resource unavailable, unspecified/
New destination (4ESS/5ESS: 4/5 Electronic Switching System)
Cause Value 47 indicates a resource unavailable event only when no other cause
in the resource unavailable class applies.
Cause Value 47 (4ESS/5ESS) If this Cause Value is returned in a RELEASE_COMPLETE
or DISCONNECT message and the customer is an Alternate Destination Call
Redirection (ADCR) subscriber, it invokes call redirection.
Communication Manager does not originate Cause Value 47.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[AvayaTier3]

If you can duplicate your problem while doing list trace station, it may provide a clue.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[Naperguy1]

We have been able to duplicate it. It appears to only affect certain individuals - unknown as to why. My call goes through. My next door neighbor's call does not. AvayaTier3 - thank you for the post. I have been through the cause values to verify resolution possibilities. Loopback - we do have a mtce contract and a ticket is submitted. I'm waiting to receive an update.

 

[AvayaTier3]

Command: change mst default

turn on call trace, proc errors

you can decode the trace in your web browser

the uid for call trace will be for your trunk-group

example:
trunk-group 99 = uid 830063
hex 63 = decimail 99

change mst                                                      Page   1 of  15
                                MESSAGE SEQUENCE TRACE

     Run Time Limit: 2  hours     Disable On Buffer Full? n  Generic Filters? n
    Store Timestamp? y                     Start Trigger? n
    Message Storage: entire                 Stop Trigger? n
                                              Stop Count:
                                               Retrigger? n

             X.25? n           CCMS? n    CALL TRACE? y            PMS? n
         ISDN-PRI? n         PACKET? n           CDR? n   HW ERROR LOG? n
         ISDN-BRI? n        VECTORS? n  DEBUG BUTTON? n    PROC ERRORS? y
             ASAI? n  VECTOR EVENTS? n         PRECs? n             IP? n
              CMS? n            EWT? n           BSR? n           BASM? n
                        IP Stations? n DENIAL EVENTS? n   FW ERROR LOG? n
X.25 Filter Data
             Processor Channel: 1
              Application Data: none                 Link Control: all
                 Confirmations? n                  Session Timers? y
               Session Control: all            Application Errors? y
     Processor Channel Control: all         Unrecognized Messages? y

change mst                                                      Page   7 of  15
                                MESSAGE SEQUENCE TRACE

Call trace Filter Data:

   call_p? y dump call records for each stimulus? y
   conn_m? y
    grp_m? y
   serv_d? y
  suser_m? y
   msg_sv? y
   stn_sv? y



  Filter Selection: specific

    UIDs: 830063   0        0        0        0
    Mask: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com