Confirming Data From LIST TRACE TAC 1

[kulabird]

Greetings:

My CM 8.1 has changed carriers and we setup new ISDN PRI trunks to a Cisco CUCM acting as my central office switch. I have test number 477-7777 which is reachable from the outside world to my internal station 77777. But using 'list trace tac' the dial number shows as 847-7777. What is causing this?

NOTES:
CUCM sends me 7 digits.
My internal station numbering is 5 digits.
No digit manipulation on trunk group page 2. No change in routing if I try to strip the first 2 incoming digits and replace with 47.
Incoming call handling treatment only looks for 477 numbers and strips 2 digits.
No change if I look for 847 numbers and route to other working numbers.

ADDITIONAL COMMENTS
I do not remember if the old trunks did the same. The old TRUNK GROUP and INCOMING CALL HANDLING do not have any odd digit manipulation - I did not catch this until we fully changed carriers.
Am I not interpreting list trace correctly?
Is there another digit manipulation which alters digits I am missing?

 

[kulabird]

Need to modify this after completing much testing.

Something is transforming digits on incoming calls but I don't know where to look. I have contacted Avaya and we'll delve deeper once a Tier 3(?) tech is available.

Whatever is doing this is not in trunk group page 2 or incoming call handling. It's been quite a time determining work arounds for di numbers pointed to AAR just as a bandaid. My system is inserting 8 on dialed numbers but I have no extensions (stations, hunt groups, VDNs, etc) which begin with 8. I can't change

 

[kulabird]

Part 2
I can't change dialplan analysis (above erased comment was uniform dialplan) number 8 which is a FAC as some entry is still using 8. Absolutely nothing with 8 in FAC.

 

[Shaun E]

CUCM itself is a virtualised/software platform and doesn't have ISDN as such so the Cisco side of the PRI is likely terminating on a Cisco ISR or similar device.

Are you able to run an ISDN trace on this device? It's entirely possible that there are number translations occurring there especially if the port was used for another connection in the past. Running an ISDN trace on the Cisco gateway will at least allow you to see what digits it's sending to CM.

I myself have CM 8.1 trunked to my CUCM environment via a QSIG E1 PRI (G650 on the Avaya side, Cisco 2921 ISR on the CUCM side) so if you need more pointers let me know.

 

[kulabird]

Ah! Thanks. I may take you up on that.

My connection from Avaya to Cisco is an ISDN PRI via NI2. Why not QSIG? My system and 2 other systems changed carriers at the same time due to an end of contract on the old carrier. The new carrier chose to standardize for three systems and they chose NI2 as all of us could support it.

After cutting over carriers, I happened to notice the setup digits from the CUCM showed up in 'list trace tac' as malformed or manipulated. We had various persons over a Teams call sharing their screens and the carrier showed their outbound logs displaying the send digits as '477-xxxx' while I would see a 3 digit setup number such as 843 or a 7 digit setup number as 84x-xxxx. I didn't know where to get the raw CDR before Avaya manipulates the digits which placed me in a corner. 'List trace tac' shows the digits after manipulation and does not indicate what settings/features caused this.

For example:
My internal station number: 77777 (my system mainly uses 5 digit extensions beginning with 7)
The commercial number to reach me is 4777777
Incoming call handling treatment for the trunk group is to search 7 digit LENs using 477 and strip 2.
On the old carrier, the incoming call of 4777777 would strip 2 digits to 77777 which matches my extension/station.
Tracing on the old carrier's circuits? No can do. When we cutover it was all or nothing. There is no more incoming traffic on that trunk.*
On the new carrier's call treatment, I did the same as the old carrier - search for 7 digit LENs using 477 and strip 2.
When outside callers call my number, 4777777, it reaches my desk but the dialed number is 'list trace tac' shows as 8477777.
Attempts to use incoming call handling treatment on 847 numbers are unsuccessful.
But...calling 8477777 on another phone on my system does ring my internal station of 77777.
'8477777' seems to be a feature code + the extension/station number.
8 is a FAC for me but I can't find any 8 in feature access codes.
And why is list trace tac showing a FAC? Ran this by a business partner and they were scratching their head. Waiting on Avaya to provide some idea of what happened.

*I might be able to find another Avaya system still on the old carrier and can ask for their 'list trace' info.

 

[Bill P]

depending on the version of your CM there is now a calltype analysis table that can manipulate digits.

Here is how the numbers flow through the Avaya system.