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

PRI and Patch issues BCM450 - Urgent 4

Status
Not open for further replies.

curlycord

Programmer
Sep 22, 2002
14,225
Toronto, Canada
I have strange problem.

We have a BCM450 installed a week and half ago, worked fine untill Friday.
Intermmitent inbound (fast busy) on DID's, and calls drop upon transfer.

Tech went to site yesterday, found his settings had changed...
PRI's Clocking were programmed as 1 Primary and other 2 secondary at install, yesterday he states they are now at 1 secondary and 2 are internal, somthing like that....switched it back and all ok and left site.
Today again this programming switched back and inbound issues.
We sent him a SU patch release March 19, upon loading it said newer files already existed therefore could not patch.
The previous patch was March 10th we had installed.

Anyone have similair issues or know anything?

Thanks
cc


=----(((((((((()----=
curlycord
 
Yes i have had the same problem,,I set these at install.

1st card set to primary
2nd card secondary
3rd card secondary.

When i check these later i found the 2nd card changed to internal,
I changed it back to secondary and the 3rd card changed to internal.

My tech support helpdesk says this is correct,
the cards will change.

so
card 1 is primary
card 2 is secondary
card 3 is internal
card 4 haven't put one in yet i but guess its internal
 
Still an issue with the Clocking..
Mod 40 is primary
Mod 30 is secondary
Mod 20 is internal

it just again switched but this time to:
Mod 40 is internal
Mod 30 is secondary
Mod 20 is primary

Call is into Nortel but this is nuts.



=----(((((((((()----=
curlycord
 
I have never seen programming change on its own.

Nortel still has not called back yet it's marked as critical.

Anyone know of any tricks or new things when adding 3 PRIs on this new beast??.


=----(((((((((()----=
curlycord
 
Since I haven't touched a 450, all I would reccomend is swapping the DTMs and see if the problem follows/persists?

Maybe hardware mismatch is the root of the problem?

"Adversity is Opportunity
 
I think Nortel has a problem with PRIs and the BCM450. We had a similar issue on a new install. Nortel is getting some heat about this as well.


--DB
 
Notel wants copies and screen shots of the data base.

Strange that it did work for week and today it changed settings 4 times. Unfortunatly this is a 64 person call center for a very well known company in N.A.

Thanks for that note D



=----(((((((((()----=
curlycord
 
I forgot to add that all though they may have a fix for the PRI issues as noted in the March 18th patch the problem as noted in my first post is we cannot patch it now because the new patch thinks we have newer patches already so it wont continue.

Here is just the mentions of PRI:
BCM450.R100.SU.SYSTEM-004_BCM450_R1

- System intermittently performs "cold start"
When making an outgoing PRI call coretel may occasionally
crash.
Q01949895

- PRI doesn't come back into service after remote alarm clears
When there is a short interruption of the PRI service that results in a remote
alarm (AIS, RAI), the DTM Module in the BCM shows a remote alarm
(yellow led in the upper left corner is lit) as expected. However, when the PRI
service is re-established, the DTM Module still shows a remote alarm and no
incoming or outgoing calls are possible (Not expected)
Remote alarm condition should be cleared on the DTM Module.
Q01822428-02

- PRI calls cutting off intermittently
Intermittently, an incoming PRI calls may be disconnected
if there are 8-9 simultaneous PRI calls. Only one call at
a time gets disconnected and the problem happens only on
incoming calls.
Q01923297-01




=----(((((((((()----=
curlycord
 
I know my system changed the clocking source as i have described in my post but the customer has 75 lines and a large call centre 40 agents.

The lines are working fine.

The only problem i am experencing is "intermittent" agents unable to log out. can take 5 mins for logout to complete

I have all patches applied as in your post above.

I have a CEC card fitted.
I wonder is this the common factor.
 
Update

Still an open ticket with Nortel

This came out Monday:

Analysis:
ISSUE: B-channels locking up on PRI
RELEASE: BCM 450 R1
CR: Q02003707
SYMPTOMS: Customers are reporting an intermittent problem with random channels locking up on PRI. The problem
appears to be triggered by incoming calls because it usually happens on the first few channels. Customers rarely report
issues making outgoing calls.
WORKAROUND: None
STATUS: This Condition is currently under investigation by BCM Sustaining designers. A designer patch has been
created and is being tested. Please contact Nortel Technical Support and open a case if you believe you have a system
with any of the symptoms above.

Nortel has dialed in and applied a beta patch.

We are monitoring.

=----(((((((((()----=
curlycord
 
As I understand it from a case I had early this week ...
Nortel currently has a "designer core-tel" load that they can install via access to the OS.
An actual BETA patch is due soon.
Nortel reports that the designer load has resolved the issue at 100% of the sites where it has been installed.


-SD-
 
Designer patch failed on one of our BCM450's today.. Just an FYI, it's not a fix-all..


--DB
 
Our B-Channels would start bouncing on incoming calls. It appeared to be like the D channel saying "Hey, I got this trunk available so let's use it" then rejecting the call.. It would just sit there and flicker on the BCM Monitor tool and it would take about 72 hours for it to rear it's ugly head.. A media bay module reset would take care of the issue until the next 72 hours. Nortel is claiming our programming has caused overrun errors in the DTI and it basically stops accepting calls.. But then why would I call in and get the problem and at the same time use another set to call in and the call get answered? It's messed up..

Nortel has some 'splaining to do.. I know they're trying, but it seems they are using us as their guinea pigs.


My two cents..


--DB
 
is there a cure for this problem? I am having the same problem and I have all the patches up to 4/22/09.
 
It's explained above.
Call Nortel to put a ticket in and to have them install a special designer core-tel patch....there is no patch avialable for us yet for this issue.



=----(((((((((()----=
curlycord
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top