12-10-2014 09:12 AM - edited 03-18-2019 11:26 AM
CUCM 7.1.3 MGCP Gatways. All calls coming into campus from PSTN first touch the CUCM. If the extension caller is trying to reach is not on the CUCM, but on the old Rolm 9751, call is routed over another MGCP PRI to the Rolm System. PSTN > CUCM PRI > ROLM. Although the originator's CLI is something to the affect 5184431234, it appears as 7168881234 on the Rolm The 716888 is the college area code + exchange. I assumed the PRI between the CUCM and ROLM is doing a called party transformation, but I don't see on the PRI configuration. On a CDR dump, the CLI of the originating call is correct, however the dialed number is now the 7168881234. The significant digits for the call from the PSTN to the CUCM is 4. Significant digits from the CUCM to the ROLM is 4 also.
Where do look to see where the college prefix is replacing the CLI area code/exchange?
Solved! Go to Solution.
12-10-2014 01:13 PM
First, do a "debug isdn q931" on the PRI to the ROLM to confirm that CUCM is sending out the translated CLI and that it's not the ROLM doing something clever.
If it definitely is CUCM doing the digit manipulation, follow the chain of Route Pattern -> Gateway/Route List -> Route List Details to see if you can see where the Calling Party is being altered.
GTG
12-10-2014 01:13 PM
First, do a "debug isdn q931" on the PRI to the ROLM to confirm that CUCM is sending out the translated CLI and that it's not the ROLM doing something clever.
If it definitely is CUCM doing the digit manipulation, follow the chain of Route Pattern -> Gateway/Route List -> Route List Details to see if you can see where the Calling Party is being altered.
GTG
12-15-2014 09:43 AM
Gordon -
I did have a 716888XXXX prefix on the PRI that handled the original incoming call and outcalled to the 2ndary Rolm Switch. Part of my confusion was tracking the detail of the call via CDR. When the 716888XXXX mask was in effect the calls in CDR listed outbound calling number as the 7168881234 (ie). When I removed the prefix, the CDR outbound listed it as NULL so I thought the CLI was not going through when in fact it was.
Thank you for your help with.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide