Avaya Partition Route Tables Simplified
The 5 steps to help you troubleshooting outbound routing issues
In this post, “Avaya Partition Route Tables Simplified,” learn how utilizing these tables help you segregate resources based on location, helping you organize your system configuration and secure different aspects of your voip solution.
As troubleshooters, we find ourselves dealing with the inevitable. Always trying to find ways to be efficient and make our customers happy. I wrote this post to share some of my techniques and help those refresh or show them which steps worked for me when troubleshooting these type of problems.
The dialing troubleshooting steps are=
- 1.- Show confidence
- 2.- Where should you start?
- 3.- ARS and TGs
- 4.- Partition Route Tables
- 5.- Contact those with more experience or familiarity
1.- Show Confidence
This is one of the most important steps. The initial conversation with your customer is crucial. You are looking to cultivate a great relationship by letting the customer express their concerns. The first conversation is the first impression with your customer, because we are helping them solve their concerns. It is important to take this into consideration.
- Some things you can try to demonstrate confidence
- Research the technology
- Read through previous work orders
- Testing procedures
- Contact those with more experience or familiarity
2.- Where should you start?
When troubleshooting, you should start by inspecting the user having the problem. As you review the station form, you are looking for the Class Of Restriction or COR number, TN (Tenant Number) and Class of Service.
Class Of Restrictions (COR) – Besides the calling, called party restrictions, and FRL, the Time Of Day Table (Chart) is what you need to document if you are routing calls based on locations in conjunction with PGNs (Partition Group Numbers).
3.- ARS and TGs
For those system routing calls through independently you might need to just adjust the ARS Analysis entries. For more on this, head over to my ARS Simplified post.
4.- Partition Route Tables
As your system grows, so does everything else. When adding new trunk groups, and remote locations to the Core system it is a good idea to implement Partition Tables as a multi-routing strategy. The first step is checking that you have Tenant Partitioning, and Time-Of-Day Routing enabled under the “System Parameters Customer Options”.
Here are some of the benefits of Partition-tables=
- Up to 8 partition groups (PGNs) with the capacity of adding as many Route-Indexes as you might need.
- Automatic Route Selection based on locations. It helps segregate the routing, load-balance call traffic, and allocate resources.
Other characteristics of the Partition Routing Tables are the Class Of Service assigned to each user and the numbering convention associated with each table.
CORs – are used to direct the caller to use different types of Partition Groups by assigning a specific number to the TN field. This value corresponds to the PGN number associated with the partition routing tables.
Numbering – To keep consistency, try to keep the route index IDs the same as the Route Pattens.
Testing procedures – Now that you have a better understanding of the system configuration, it is time for you to look at the past customer history, and see if this issue has happened, and what steps were taken to resolve it. This also helps you understand and better communicate your ideas to the customer.
List Trace Tool – It is always a good idea to capture a bad and good call. This is possible by having the customer duplicate the incident while running a “list trace” command.
Multi-site ARS Analysis Routing – When troubleshooting dialing out problems, see which routes are associated with the specific location.
Display Locations, and Display ARS ANA XXX location X, are the two immediate commands that defines how calls are been routed.
Multiple Trunk Groups – If possible, try routing calls through a different trunk-group and see if the problem persists. This very well can be related to a routing problem with the service provider.
5.- Contact those with more experience or familiarity
One last option that you might need to take is to contact those teammates who know the system better or are familiar with this particular customer. It is important to have them walk you through as they help you fix the problem. You don’t want to pass the buck and not be accountable for your work.
Please note: I reserve the right to delete comments that are offensive or off-topic.