Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM 400. Unable to recieve call on T1 1

Status
Not open for further replies.

mevans1974

IS-IT--Management
Jan 18, 2008
77
BS
Hi
I hope someone can help me.
I have a BCM 400 rel.4.0.2.03
I have a issue with a T1, the T1 was working all of a suddent it stop from recieving calls. You can make out going calls but when you try to call into the office the caller will recieve a dialtone.
When i look in the CM monitor i can see the call Active.
so i know the call is hitting the BCM but the question is where i'm i recieving the dialtone from. I work with the CO for 2 days and they said that the problem is not theirs i know it is but hi have to prove it.

Have anyone expereance tis problem
 
Is it a T1 or PRI? If T1 and you have Auto Answer on E&M trunks. Maybe, Answer with DISA got switched on.
 
Its a T1
Auto answer is set to on on E&M Trunks
I check all the trunks answer with DISA is no enable
 
Turn Auto Answer off and hard code line appearance and test. Do you have a prime set programmed, if so, make test on that telephone.
 
I had this problem with 2 of my systems both 4.0.

It is A known problem from Nortel,It is a DSP resource issue. It started happening for me back in September. After going round and round with Nortel for Months they finally released a Core patch (and admitted it was there problem)to fix this issue.

BCM.R400.158_BCM_4.0: BCM.R400.158-CORE, This is the patch that resolves the issue.
 
Deweyhumbolt
I try what you sad and it did not work. I spoke with Nortel and they said it's a central office problem & the CO said it's a PBX Problem so you know ny delamer. I don't know what to do now.
Here is the log that nortel recieve from the PBX maybe someone can make sense of it.

Here is the alarms I pulled up from the logs:

<critical> 2008-01-18T09:39:54.481225 Guardian CORE [2457]: eventID=41; message=Core Telephony - "Loss of Signal" long term alarm threshold has been exceeded on the DTM.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. Get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T09:58:27.461551 Guardian CORE [2457]: eventID=325; message=Core Telephony - "Errored Second"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T09:58:27.461592 Guardian CORE [2457]: eventID=328; message=Core Telephony - "Line Code Violation" short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T09:58:27.461627 Guardian CORE [2457]: eventID=329; message=Core Telephony - "Loss of Signal" short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T09:58:27.461662 Guardian CORE [2457]: eventID=330; message=Core Telephony - "Loss of Frame" short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T09:58:37.430846 Guardian CORE [2457]: eventID=323; message=Core Telephony - "Degraded Minute"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T12:52:27.720990 Guardian CORE [2457]: eventID=325; message=Core Telephony - "Errored Second"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T12:52:27.721034 Guardian CORE [2457]: eventID=330; message=Core Telephony - "Loss of Frame" short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T12:52:37.630920 Guardian CORE [2457]: eventID=323; message=Core Telephony - "Degraded Minute"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T12:58:32.141233 Guardian CORE [2457]: eventID=325; message=Core Telephony - "Errored Second"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T12:58:32.141276 Guardian CORE [2457]: eventID=330; message=Core Telephony - "Loss of Frame" short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
<minor> 2008-01-18T12:59:14.130818 Guardian CORE [2457]: eventID=323; message=Core Telephony - "Degraded Minute"short term alarm threshold has been exceeded on the DTM. The module is in a no-new-calls state.; problemResolution=Check your cabling from any DTM modules to the external network and run loopback tests on the circuit to check for network issues. If long term alarms occur get your network provider to check the circuit during problem conditions.
 
I think Dantheman has the answer. That's why I starred him. All your errors look core related. Get the patch.
 
Hi Guys,
Thank you for your help it is working now.
I had to apply the patch to correct the problem.

Dinner is on me LOL........
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top