So unfortunately we have a local PRI from Verizon at one of our locations. This site has been a nightmare with multiple issues. Each time as usual Verizon has blamed everything on our equipment and it ended up being their issue. Any ways so the latest issue is this:
- PRI circuit has lots of errors but "show isdn status" is showing it up (Layer 1, 2)
Layer 1 Status:
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
- I do see these messages when running a debug here and there:
- Any inbound calling does not work. I have tried calling the DID's from Cell, Landline and we get either a fastbusy tone, or Non working number message and running a "debug isdn q921 and q931" doesn't even show the call hitting our router.
- And as expected first thing Verizon said it is our equipment and our equipment is not accepting the call
After talking to the manager of this tech he said that they inbound calling is not working because there are lot of errors on the T1. I told him regardless I should still atleast see the calls hitting the router because the PRI is showing up. And he insisted that there is an issue with either our equipment and the demarc extension. Any thoughts, notions, suggestions on why the inbound calling not working?
Also these messages were showing up in the logs but its been 20 mins so far haven't seen them again:
Jan 3 09:28:55.557: %CONTROLLER-5-UPDOWN: Controller T1 0/3/1, changed state to up
Jan 3 09:28:55.565: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
Jan 3 09:29:06.557: %CONTROLLER-5-UPDOWN: Controller T1 0/3/1, changed state to down (LOF detected)
Jan 3 09:29:06.557: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
Jan 3 09:29:07.557: %CONTROLLER-5-UPDOWN: Controller T1 0/3/1, changed state to up
There is very little that could be done if the call does not even reach the gateway. In these kind of scenarios it is a good idea to open a TAC case and have the TAC engineer get on a conference call with you and the service provider to sort things out. Any other suggestions are welcome.
Thank you good post, however my router already has the IOS with the fix. Still seeing errors on it. This still does not explain why the inbound calls aren't working though. Verizon is seriously a worst provider of any services period and so is their tech support.
Symptoms: After unplugging and reconnecting a T1 cable, the T1 controller remains down or report continuous errors. After a router reload, the T1 controller remains up until the cable is disconnected again.Conditions: This symptom affects only the following cards: HWIC-xCE1T1-PRI, NM-8CE1T1-PRI, VWIC3-xMFT-T1/E1, and GRWIC-xCE1T1-PRI. Also, the T1 signal must be somewhat out-of-specification according to T1.403 standards.Workaround 1: Reload the router with the T1 cable plugged in.Workaround 2: Step 1) Upgrade to a fixed-in Cisco IOS version. Step 2) Issue the following commands (hidden, so tab complete will not work):enable config t controller ! ( example: controller t1 0/0/0 ) hwic_t1e1 equalizeStep 3) Shut/no shut the T1 controller, or reload the router to allow the CLI to take effect.
Like I mentioned that the router has the IOS in which this bug was fixed. Verizon called me and while I was on the phone with them we were doing some testing. They told me that the calls are just sitting there and our equipment is not accepting them. Any ways after I got done talking to them I decided to reset our gateway and controller again.
As soon as I did that everything started working. Going to keep an eye on it. So far there is no root cause of why this happened. I did end up adding this command as well by the way just in case hwic_t1e1 equalize. I am thinking if this might be the reason but we'll see.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...