Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Avaya Aura & Unified Communications (http://support.avaya.com/forums/forumdisplay.php?f=2)
-   -   How to change an 11 or 10 digit call to a 4-digit extension call (http://support.avaya.com/forums/showthread.php?t=14317)

koch112 08-04-2020 07:41 AM

How to change an 11 or 10 digit call to a 4-digit extension call
I entered this a 2nd time to get a better title.

We want to translate a 10 or 11 digit call to an internal 4-digit call.

We have an internal conference bridge, extension 1234.

It is also accessible externally via 732-555-1234 or 1-732-555-1234.

(phone numbers are for example only).

Our internal users insist on dialing the external number to access the bridge instead of using the internal extension. Obviously, using the external number ties up trunks and also consumes our monthly allotment of minutes with our carrier.

I know we could create an entry in our ARS ANALISYS table and simply block the external number where they would get a re-order tone.

I'd like to instead strip either 1732555 or 732555 from the dialed number and make it an internal PBX call to extension 1234.

Is there a way to accomplish this? Is there documentation your could refer me to?

koch112 08-06-2020 09:39 AM

Answering my own questions...
I seem to be answering my own questions in these forums.

How did I solve this?

Well, I added a route pattern which had the trunk group for our voice bridge server.

I then added the phone number with both 1732 and 732 to my ars analysis screen.

I then routed those calls to my new route pattern which went to the trunk group where the bridge server is attached.

So, a simple solution which took me a bit to figure out. I've been away from doing this for a few years, so I had to dredge up the solution from my long term memory.

mlombardi1 08-10-2020 07:42 AM

Another option is ARS digit conversion. This intercepts the call for modification before ARS routing is determined.

koch112 08-10-2020 08:33 AM

Good idea

I was unaware of the ars digit conversion table. Ours is completely empty. Good info for the future!

koch112 08-14-2020 08:30 AM

AAR digit-conversion
OK, I found AAR digit-conversion.

In my other cases, those phone numbers were going directly to devices which are attached via trunks groups. So the ARS ANALISYS method worked for those numbers.

In analyzing the Call Detail Report from my PRI carrier, I discovered that people are dialing the outside phone number for extensions which are in our system. So, we're paying to call ourselves. We're also tying up 2 trunks since the call goes out 1 trunk and "hairpins" back to one of our incoming trunks.

The AAR digit-conversion table will allow me to solve this problem.

Everyone should program their system such that any phone number which is an incoming trunk must be in the AAR digit-conversion table. This is so the call is transparently changed to an internal extension call.

koch112 08-14-2020 12:22 PM

ARS digit-conversion not AAR digit-conversion
Doing a list trace on my extension, my numbers were not be transformed. I needed to use the ARS digit-conversion to correct the numbers.

All times are GMT -7. The time now is 03:32 PM.