The list trace tool – The tool that makes us supernatural

In this post ‘The list trace tool – ‘The tool that makes us supernatural’ – you will learn how this diagnostic command or tool, can help us troubleshoot from the most common issues to the most complex problems. When finding common day to day enduser problems such as: ‘I can’t dial long distance’, ‘I can’t access voicemail’, or troubleshoot inbound call traffic to see if the caller is reaching the correct destination. 

Through out the years Avaya has incorporated more features to this tool, making it more robust.If you ask me which tool or SAT command do you normally utilize the most? – My response hands down is the ‘list trace’ command. For this reason I have created this list which describes each list trace action.

• 1.- Station / End-user dialing issues
• 2.- Trunk related issues
• 3.- VDN and Vectors

 

1.-Station / End-user dialing issues

‘list trace station x’ – When you run this command it starts capturing data as soon as the station goes off-hook providing a CID number, call treatment, route selection, trunk group, trunk group features, and finally setup digits.

CID Number or Call Identifier Number – This number is associated with a new call or event. It is useful when associating a particular call or event to a trace.

Call Treatment – This portion of the trace gathers the Call- Type and Dialed Number.

Route Selection – This section of the trace collects the Route Patterns and Preference option. Keep in mind that you can have multiple trunk groups associated to a Route Pattern.

Trunk Group – Here the trace informs you which TG is being in-use and which channel has been selected.

Trunk Group Features – Depending on your TG settings, here you might be able to see Calling Number, Name, etc.

Setup Digits – These are numbers sent to your Service Provider

Note – For H.323 or SIP Calls, the codec type will be shown in the trace, as well as the IP Network Region, Gatekeeper or Call Servers IPs, Jitter, and Packet Loss.

• Oofo – Out of order packets
• Jitter – self explanatory
• Buff – Buffer size

 

• WC – Worst case packet loss or jitter
• Avg – Average jitter or packet loss

 

2.- Trunk Group related issues

‘list trace tac x’ traces a specific trunk group. It is very similar to the station trace, providing the same attributes already discussed. One of the main benefits of this trace it’s to learn if the end-user is accessing the correct TG.

For SIP Trunk Trunk Groups, a Call-ID 17 digit number is provided with each call or event.

CID is also provided in the SIP Trace allowing you to tag each event to an value or ID.

INVITE, ACK, BYE, and OK are the SIP Methods or messages interchanged between servers or SIP sessions. Providing which transport protocol has been selected or configured (TLS or TCP).

3.- VDN and Vectors

‘list trace vdn x’ – This trace details the call entering the respective vdn, displaying vector information including BSR (Best Services Routing), Variables, and each step taken by the caller from vector to vector until the call gets delivered to its destination or disconnects.

‘list trace vector x’ Similar to the vdn trace, but it only traces one vector per argument.

Other list trace arguments are=

• ewt (expected wait time) based on Avaya’s algorithm for Call Center.
• ras – H.323 registration events
• data-module – self explanatory
• attendant – self explanatory
• advocate – this is related to Call Center View

List trace ras ip-stations x

As listed here the Gatekeeper Request (RGQ)sent to the Call Server from the phone. The Call Server or Gatekeeper will send a GCF (Gatekeeper Confirm) packet back to the ip phone. Once the phone gets the GCF it will then send a request RRQ  (Registration Request) back to the Call Server, and finally the RCF goes out to the phone allowing it to register. (RCF= Registration Confirm).

List trace ras ip address xx.xx.xx.xx outputs the same as the ras ip-station trace.

Action Step

When running the list trace command, which denial events do you normally get? and how do you get it fixed?

 

Get my fresh content

 

Resources

Avaya Maintenance Command Reference Guide – Page 253