Ok, here is an odd one. In a second site (in which we have a pretty big language barrier with the local carrier) we've just received additional LS trunks. We've put them on the 6 LS ports on our controller. Now, we've gone over our ARS routes again and again, but once we dump then into a Trunk Group, we end up with failed calls. We put them on a set with a DTS button, and each one of those trunks are able to get out and dial.
We put them in a trunk group, remembering to both remove them from the DTS keys and reassigning them in the Trunk Service Assignment to ensure they are not DTS, check the route (9+7 digits) out to that trunk and it does not work.
Now, one difference is that before this, we had one working LS trunk on the ASU that we had set up the same and it worked fine. The difference now is that we are the Hybrid ONS/LS ports on the controller. It looks like a CO Circuit descriptor issue, but I honestly am not seeing it. Any ideas? Thanks.
We put them in a trunk group, remembering to both remove them from the DTS keys and reassigning them in the Trunk Service Assignment to ensure they are not DTS, check the route (9+7 digits) out to that trunk and it does not work.
Now, one difference is that before this, we had one working LS trunk on the ASU that we had set up the same and it worked fine. The difference now is that we are the Hybrid ONS/LS ports on the controller. It looks like a CO Circuit descriptor issue, but I honestly am not seeing it. Any ideas? Thanks.