Im having some issues where I get calls dropping in our environment.
After looking at the log file on the gateway (MGCP) I noticed a lot of AIS and LOF errors, which is causing the circuit to flap.
sh controller e1, and sh interface serial0/1/0 did not show any increasing errors, and the controller is up (but as mentioned it flaps)
I did clear the counters on the controller and will look again tomorrow to see if I get any errors.
Normally I would just get the telco to come out and sort the issue, which I did do.
They unplugged our equipment and ran a test (trend/trent test...not sure about the spelling) which showed no errors. Only after plugging our equipment in again are they able to see errors on the line.
This has been a working solution for years now and we havent done any changes in our environment, which makes me think the problem is still on the telco side, but they do have a valid point when they ran their tests and showed that errors only appear on the line if the line in plugged into our equipment.
We have two gateways, both with a PRI connecting to the telco, and both PRI's show the AIS and LOF errors, so I highly doubt a cable or card fault on our equipment.
Aug 7 09:43:39.345 BST: %CONTROLLER-5-UPDOWN: Controller E1 0/1/0, changed state to down (AIS detected)
Aug 7 09:43:39.349 BST: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/1/0:15, TEI 0 changed to down
Aug 7 09:43:40.345 BST: %CONTROLLER-5-UPDOWN: Controller E1 0/1/0, changed state to up
Aug 7 09:43:40.409 BST: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/1/0:15, TEI 0 changed to up
Aug 7 09:43:50.346 BST: %CONTROLLER-5-UPDOWN: Controller E1 0/1/0, changed state to down (LOF detected)
Aug 7 09:43:50.346 BST: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/1/0:15, TEI 0 changed to down
Aug 7 09:43:51.218 BST: %LINK-3-UPDOWN: Interface Serial0/1/0:15, changed state to down
Aug 7 09:43:57.346 BST: %CONTROLLER-5-UPDOWN: Controller E1 0/1/0, changed state to up
Aug 7 09:43:57.414 BST: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/1/0:15, TEI 0 changed to up
Aug 7 09:43:59.346 BST: %LINK-3-UPDOWN: Interface Serial0/1/0:15, changed state to up
Any help, or ideas on what could possibly cause these errors on our side would be greatly appreciated.
Thanks for the link Thomas. The AIS and LOF messages stopped for a while after the telco tech came to site for the first time and did his tests.
I think it might have been because he unplugged the PRI from our equipment and then plugged it back in again.
Unfortunately the errors returned a day later, so I reported the problem to the telco again only to hear from them that the fault is not on their side...very frustrating working with a telco. So I escalated the matter as high as I could and only then did I get a call from the account portfolio manager and explained to him that the fault is on their side. The account manager conferenced the NOC team into the call and they confirmed that they can see errors on the line.
A quick reset from their side (which took two seconds) and all the errors stopped.
What really grates me is the fact that I had to go through such lengths to get the telco to admit the problem and do something as simple as a reset on the PRI.
Thanks again for the link, which explains all these errors in detail and how to troubleshoot them.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...