Cisco Route Patterns are showing down even though they are up in cucm

[Venkata]

Hello Team,

I came accross an incident where cisco route patterns are showing as degraded.

When I cross checked in call manger I found they are up and associated SIP trunk is also up.

Upon furhter deep analysis I found the same trunk is showing as degraded even though it is up in cucm.

The destination peer of the trunk is stating as down in the Porngosis but everything is up and fine in the call manager.

What might be the issue for this to happen.

Thanks,

Venkata.

[Scott_Clement]

Hi @Venkata,

It could depend on what version of Prognosis you're currently using and whether that system has the latest patch installed. There have been fixes released to address issues with SIP trunk status under CUCM for different versions of Prognosis that you may just be missing.
I'm also aware of a limitation of the CUCM interfaced that provides SIP trunk status and Prognosis is only able to report the status of the first 200 trunks that the CUCM interface returns.

If the information above doesn't help, it would be best to submit a support case so that we can investigate further. If you can include a current irfax, we can check the current patch level to see if you may just be missing a fix that's already available. Otherwise, we can help validate if Prognosis is showing the correct information based on the source data and provide a fix if not.

Regards,
Scott Clement
IR Support

[rfetkovich]

Hey Venkata,

We actually were experiencing the same scenario on 12.1 Patch 1 and 2.  Didn't matter once I updated Prognosis.  Some of our SIP trunks would show degraded to our CUBEs.  

Ended up being that the peers that showed green and registered on the trunk page in Prognosis, were the same listed in a server-group on the CUBE.

I ended up adding all of our CUCM node IPs to the "ip address trusted list" under the "voice services voip" configuration on the CUBEs.  Once that was done, the CUBEs showed fully operational from a Prognosis standpoint.  Not sure if that is a weird CUCM, CUBE or Prognosis bug, but thats what worked for me.

It was weird because it didn't seem to impact all of our CUBEs, just a subset.

Thanks,

RJ