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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM200 4.0 getting 52005 **ERROR** Reset by Network Manager

Status
Not open for further replies.

jrath

Vendor
Oct 28, 2002
5
US
thread1361-1586247

Just wondering if anyone had come up with a solution to this. I have had two seperate BCM200s running 4.0 do this now in the last 6 months. Oddly enough they are both owned by the same customer, and so far I haven't seen any of our other customers BCMs do this. The 52005s are usually followed by multiple 51103 "Call rejected, due to all 8 keycoded trunks being in-use on the DS30 interface" which I assume is a result of the 52005. Rebooting seems to temporarily correct the issue, but usually only for a day or two. Installed SU29 on the latest BCM to experience this, (was at SU28 when the issue started), it had no impact on the issue.
 
Are the VoIP trunks SIP or H323?
Does the customer use Centralized VM?
Have you used the BCM Monitor IP Devices tab to see if the IP Trunks are getting locked into an "Active" state?

-SD-
 
The VoIP trunks are H.323 and yes they do use a centralized VM on a BCM400 at their main location. I have looked at BCM monitor and seen some of the trunks appearing to be locked in an "Active" state but not all of them at once. Usually some show idle even though the alarm message says all 8 are in use. Yesterday for example, only one showed active (but it did appear to be locked up), the rest were showing idle.
 
Found this in the Avaya Knowledge base:
Description (Problem Clarification)

If voice mail is hosted on the BCM 4.0 and a message waiting indicator is sent to a voice mail client system over SIP, it is possible that Alarms 52005 and 11204 will be generated on the voice mail host BCM. Some services may go down or restart.


Resolution Plan

Patch BCM.R400.034 ,which deploys components IPTelProviderAgent: 41.130.1.43 and FEPS: 41.500.0.33, contains corrective content for this issue. Apply this patch to any site(s) exhibiting this symptom.

Close match. Perhaps they need a patch for H323?


-SD-
 
Close and you may be right about needing an H.323 patch. The big difference here is it isn't the 400 that is hosting the VM that the messages are showing up on, it is actually the branch 200s.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top