Assistance reading call log

[mumbles202]

Working on a CUCM w/ a MGCP gateway that has a pri attached and trying to understand call flow.  This is a snippet of a q931 from taken using RTMT:

Inbound Q931 SETUP message from 192.168.10.5 at timestamp 09/03/2021 09:17:06.759

SETUP, pd = 8, callref = 0x1488, Message Size = 68 bytes

Bearer Capability i = 0x8090A2, ITU-T standard, Speech, Circuit mode, 64k, µ-law
Channel ID i = 0xA98382 - PRI interface, Exclusive channel 2
Display i = 'WIRELESS CALLER'
Calling Party Number i = '1112223333' - Plan: ISDN, Type: National, Presentation Allowed, User-provided, verified and passed
Called Party Number i = '5020' - Plan: Unknown, Type: Unknown
Redirecting Number i = 0x008F, '2222222245' - Plan: Unknown, Type: Unknown

I can see 5020 defined as a CTI route point in CUCM and it forwards to a UCCX.  What I'm not seeing in CUCM is either a DN  or translation pattern that has 2245 (or anything w/ a similar mask) that is forwarding to the 5020 number.  Is there anywhere else I should be looking?  The call comes in and routes successfully but I want to update it to go to a Call Pickup Group instead of the UCCX now.

[Elliot Dierksen]

Is that gateway facing the PSTN? Regardless, that means that something on the other side of this PRI forwarded the call to 5020.

[Roger Kallberg]

If you want to get calls destined to 5020 to go somewhere else than CCX just make the changes needed to get it to whatever you want it to get to. What I mean is remove the CTI RP that sends the calls destined to 5020 to CCX and create the needed configuration for getting it to the call pickup group.

[Maren Mahoney]

If this is from a CUCM trace file, then this is an MGCP gateway. If that is the case, I'm curious to know what mechanism is modifying the incoming PSTN dialed number and truncating it to 5020.

As for locating a number containing 2245, have you use the Dial Plan Report for "All Patterns and URIs" "contains" "2245"? It may very well be something other than a DN or TP...

Maren

[mumbles202]

Yes, this is MGCP.  I believe I checked the dial plan report but I can certainly check this again Monday.  

As for just re-pointing the number to a new DN (I had contemplated that) my concern is if carrier X is doing a forward at the switch and they change carriers then that breaks.  Not the end of the world but I'd rather tackle it now then down the road.

[Elliot Dierksen]

The forwarding/redirecting number only matters if the call went to something that looks at that like Unity voicemail. There should be a check box on the gateway config page for accept/include redirecting information. If that check box is cleared, then that information is ignored.

[Roger Kallberg]

Cannot see that someone as suggested to re-point the number, so not sure where you got this from.

Based on the information shared it looks like something, not necessarily on-prem, is forwarding calls destined for 2222222245 to 5020 and this (5020) directory number is setup as a CTI RP that is defined as a trigger in CCX.

As you said you would want to get calls to 5020 to stop going to CCX then you’ll need to remove the CTI RP, aka the trigger, and create the needed configuration to achieve the outcome you want.