Incoming call route

[rogerssa]

We have did numbers from XXX-9100 - XXX-9199.

Just recently all incoming calls to these numbers fail to work.

XXX-9110
XXX-9111

XXX-9112

XXX-9113

to

XXX-9119

Those ten numbers are all that don't work.  I'm not sure why or what changed that caused this to start to fail.  We have had the system running pretty much as is for years.  

I did pull some logs from the provider to show what is happening they are saying the PBX is returning it back.

I have checked this issue and noticed that calls to these numbers are routing back to ADTRAN with last 4 digit as dialed number that is the reason calls are failing.

ADTRAN IP: 12.xx.xxx.241
PBX IP: 12.xx.xxx.242

-- INVITE from ADTRAN to your PBX (I am sharing only the header of the trace instead of complete logs)

14:38:24.795 SIP.STACK MSG Tx: UDP src=12.xx.xxx.241:5060 dst=12.xx.xxx.242:5060
14:38:24.795 SIP.STACK MSG INVITE sip:7xx7xx9110@12.xx.xxx.242:5060 SIP/2.0
14:38:24.795 SIP.STACK MSG From: "AIRESPRINGHPBX" <8189221872>< strong="">@12.xx.xxx.242:5060;transport=UDP>;tag=4fc7d878-7f000001-13c4-3f6e59-9ff1bbe3-3f6e59
14:38:24.796 SIP.STACK MSG To: <7xx7xx9110>< strong="">@12.xx.xxx.242:5060>
14:38:24.796 SIP.STACK MSG Call-ID: 4fca9798-7f000001-13c4-3f6e59-8ebf0823-3f6e59@12.xx.xxx.242
14:38:24.796 SIP.STACK MSG CSeq: 1 INVITE
14:38:24.796 SIP.STACK MSG Via: SIP/2.0/UDP 12.xx.xxx.241:5060;branch=z9hG4bK-3f6e59-f7c70caf-195e19d9

-- Received 100 trying from your PBX

14:38:24.805 SIP.STACK MSG Rx: UDP src=12.xx.xxx.242:50823 dst=12.xx.xxx.241:5060
14:38:24.805 SIP.STACK MSG SIP/2.0 100 Trying
14:38:24.805 SIP.STACK MSG Via: SIP/2.0/UDP 12.xx.xxx.241:5060;branch=z9hG4bK-3f6e59-f7c70caf-195e19d9
14:38:24.806 SIP.STACK MSG From: "AIRESPRINGHPBX" <8189221872@12.xx.xxx.242 udp="UDP">;tag=4fc7d878-7f000001-13c4-3f6e59-9ff1bbe3-3f6e59
14:38:24.806 SIP.STACK MSG To: <7xx7xx9110@12.xx.xxx.242>
14:38:24.806 SIP.STACK MSG Date: Tue, 18 Jan 2022 14:38:24 GMT
14:38:24.806 SIP.STACK MSG Call-ID: 4fca9798-7f000001-13c4-3f6e59-8ebf0823-3f6e59@12.xx.xxx.242
14:38:24.806 SIP.STACK MSG CSeq: 1 INVITE

-- Immediately after this ADTRAN received the INVITE from your PBX with last 4 digits of the calling number and with different contact header (number)

14:38:24.809 SIP.STACK MSG Rx: UDP src=12.xx.xxx.24250823 dst=12.xx.xxx.241:5060
14:38:24.809 SIP.STACK MSG INVITE sip:9110@12.xx.xxx.241 SIP/2.0
14:38:24.809 SIP.STACK MSG Via: SIP/2.0/UDP 12.xx.xxx.242:5060;branch=z9hG4bK4FE746E
14:38:24.809 SIP.STACK MSG Remote-Party-ID: "AIRESPRINGHPBX" <7657629091@12.xx.xxx.242>;party=calling;screen=no;privacy=off
14:38:24.810 SIP.STACK MSG From: "AIRESPRINGHPBX" <7657629091@12.xx.xxx.242>;tag=DB15DB58-91
14:38:24.810 SIP.STACK MSG To: <9110@12.xx.xxx.241></9110@12.xx.xxx.241>
14:38:24.810 SIP.STACK MSG Date: Tue, 18 Jan 2022 14:38:24 GMT
<span style="font-fam ...

So is this a route pattern failing on Call Manager?

[Jaime Valencia]

You need to look at your call routing configuration, in your GW/CUBE and / or CUCM depending on the protocol to figure this out, only you who has access to all that information and the ability to review everything can tell where the problem is, and then determine based on your call routing configuration how to fix it without introduction any further issues.

[rogerssa]

Thanks, but still not sure where to find the problem the route list look correct.  I'm not doing anything different to not allow the pattern to move through CMCU to the device.

[Jaime Valencia]

That's why you need to look at all your call routing configuration to determine the exact call path, and then review everything that is involved, if you have verified your GW/CUBE configuration and you're absolutely sure the issue is not there, then you can use DNA to try to figure out the call routing.

[rogerssa]

I figured out the problem.  System failed over to backup cube during a power outage.  I have restored the cube and will get the correct config onto backup as it was the issue.