Call to translation pattern took longer to reach the translated DN

[Mohd Marzuki]

I translated 0 > 9000 which is pilot number for CUACE, noticed when press 0 to dial using particular CSS it's taking a few seconds before the call translated to 9000 and hear the ringing tone.

Which part to check on this?

Thanks

[Jaime Valencia]

Your whole dial plan for anything that might be matching 0, once you've found, note the partitions and check the CSS.

[Marco Rojas Abarca]

What you are experiencing is expected, this is what is called Inter-digit time out. What is happening is that within your dial plan there is another pattern (could be another Translation Pattern, DN or Route Pattern) starting with "0".

The following Cisco document explains this behavior:

http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/6171-interdigit-timeout.html

Now going back to your concern and moving forward with the explanation, the Unified Communications Manager Platform is designed to route calls based on the closest match. When you dial "0" since there is another pattern starting also with 0 in your dial plan then, CUCM will wait for more digits. It is not until the T302 timer (that the document above mentions)  expires that CUCM routes the call based on the order of the partitions set or configure on the routing device (in your scenario it is going to be the CSS of the Translation Pattern)

You will be able to check there is an over-lapping pattern within your system by going (in the Administration page for Call Manager) to Call Routing > Route Plan Report and:

1) Type 0 on the search bar and hit search and all the results starting with 0 should display.

Or

2) Exporting your dial plan to a .csv file, open it with excel and apply filters to find the overlapping problem.

You can also reduce the T302 timer from the Call Manager service parameters from the default value (15 seconds) to a minimum of 3 seconds.

Hope this information helps