1 Reply Latest reply on Dec 5, 2012 7:27 AM by patrick

    550 Err on user PRI plus some other questions

    jimtgs New Member

      I have a 550 with a PRI from the Telco going to a PRI on a PBX. Both are NI2 and have no issue for years. I recently noticed my USER PRI going to the PBX is flashing ERR every 5 seconds so under modules I have hundreds of Error Seconds over a 15 min period


      My main timing source is the telco and backup is INTERNAL. The other day we lost our PRI for abour 24 hours.


      I would like to know that my USER PRI is synced up good to the PBX. There are no errors on the PBX admin / maintenance screen.


      The other funny thing is under System NAME, I had our company name. All of sudden the name changed to CARRIER? Is this a sympton of some pending problem. No-one has access to the Atlas but me.


      I also have another telco PRI connected to Slot 1. I have this PRI setup as Secondary with $ in the accept column. So I want my calls to route outbound over this PRI when my main PRI is down. It was intermittent the other day. Could that be when my clocking source was out it caused outgoing to fail some of the time?


      Thank you!!!!

        • Re: 550 Err on user PRI plus some other questions
          patrick Employee

          You can verify the timing source in the ATLAS by looking under SYSTEM STATUS at the "System Timing Source." It should show either "PRIMARY : Locked" or "BACKUP : Locked." If this is toggling between PRIMARY and BACKUP then you should set both PRIMARY and BACKUP to INTERNAL and see if the ATLAS can lock on to the internal clock. If it cannot then the ATLAS needs to be sent in for repair. If the timing source shows "BACKUP : Locked" then the ATLAS is not receiving a stable clock from the primary source.


          Is the ATLAS PRI interface showing Controlled Slip Seconds (CSS) as well as Errored Seconds? If it is then those are clock slips, which means the data the ATLAS is receiving on that PRI is using a different clock then the clock the ATLAS is using. If it is only showing Errored Seconds then these are CRC errors and could be a bad cable. You can use a T1 Loopback Plug to loop the port on the ATLAS as well as the port on the PBX to see if both run clean to a loopback. If either runs errors to a loopback then that T1/PRI port is bad.


          In order for the system name to change, someone would have to have typed in the new name. The default system name is "ATLAS 550" so it was not defaulted, and the word "CARRIER" does not appear anywhere in the ATLAS menus.


          If your "secondary" PRI shows errors and clock-slips then that can cause calls to fail. If both PRIs are from the same telco then you should be able to set your PRIMARY clock to your "main" PRI and the BACKUP clock to the "secondary" PRI and they should both be using the same clock from the central office.


          Hope this helps,