For some reason have a location whose route will not go out. So if the destination code to the route is 42 and should dial another BCM over IP turnks. The result would be to ring extension say for example 4221. The route is built, the destination code is built, the remote IP is there. As soon as we dial 42 we get invalid number. There are no other uses for a leading 4 in this BCM. I did find hunt groups with a leading 4 but I changed all of them. Still we get invalid number when we dial 42. Other outbound IP trunk routes work fine.
Monitor is running and doesn't show any activity on the IP trunks.
Monitor is running and doesn't show any activity on the IP trunks.