This is a 6202 on firmware 188.8.131.52. It was working perfectly during the first half of the day.
Vitelity (the carrier) is starting to refuse outbound calls through an inbound server. This is just background. Unfortunately in the beginning I learned (w/ their advice) to set both inbound and outbound calls to go through the inbound server assigned to the client. They stop allowing this for a specific client and suddenly outbound calls aren’t going through. So I have to build an outbound trunk, point it at the outbound server, and then set all the outbound rules to use that trunk instead.
I did that for a client this afternoon. Outbound calling is working now.
However, inbound calls are being rejected by the UCM. See attached. Any ideas why that would start happening suddenly? Inbound routes have not changed. I see on the initial invite that the correct DID (inbound) is displaying. So the inbound rule should see that and route the call accordingly.