I have a bcm 450 that we have been troubleshooting with provider for the last past 10 months. They randomly get dropped calls only when they get busy. The calls were only being dropped originally in the acd. Now it happens all the time. When the call gets dropped it usually says normal clearing. The provider says they see no errors. they have sent out several techs to check the pri extension and they have randomly found issues. no details relayed back to customer. The extension is over 1000' and is in a hospital so it bounces from telco closet to telco closet. The provider said they ran a new cat5e extension. But i don't think it goes all the way back to the verizon fiber. I know when we extend circuits we use t-1 cable that both pair is shielded. The system was up to date with its patches back in march. Provider installed 2 different Adtran units at the pbx and the problem got worse. With the Adtran they said they could monitor it better and found nothing. just wondering if anyone has any advice.
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
bcm450 dropped calls
- Thread starter wstn77
- Start date
curlycord
Programmer
In future BCM forum is here for your favs:
Needle in haystack, could be anything.
BCM 450?
Is the BCM up to date with patches? what are the names of the last patches and dates?
Have you replaced the DTI card or patch cord?
What has been done on BCM side?
What are the alarm codes in the log?
What are all the settings at related to PRI programming?
Have you had different vendors/techs who know their PRI programming?
Have the carrier setup monitoring for 24 hours?
Have you ranted and told the carrier you have replaced the system (Poker Face) and still same issue?
" The extension is over 1000' "
What do you mean the extension?
The patch cable from the Pair Gain box to the KSU?
The Pair Gain (first piece of equipment in the building) should always be requested to be installed at the phone system.
Signal travels further/better from CO to Pair Gain then Pair Gain to KSU.
Cause No. 16: normal call clearing. This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network.
Still needle in haystack though.
Do you have a spare KSU with PRI? The ultimate test to prove carrier.
=----(((((((((()----=
curlycord
Toronto Canada
Needle in haystack, could be anything.
BCM 450?
Is the BCM up to date with patches? what are the names of the last patches and dates?
Have you replaced the DTI card or patch cord?
What has been done on BCM side?
What are the alarm codes in the log?
What are all the settings at related to PRI programming?
Have you had different vendors/techs who know their PRI programming?
Have the carrier setup monitoring for 24 hours?
Have you ranted and told the carrier you have replaced the system (Poker Face) and still same issue?
" The extension is over 1000' "
What do you mean the extension?
The patch cable from the Pair Gain box to the KSU?
The Pair Gain (first piece of equipment in the building) should always be requested to be installed at the phone system.
Signal travels further/better from CO to Pair Gain then Pair Gain to KSU.
Cause No. 16: normal call clearing. This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network.
Still needle in haystack though.
Do you have a spare KSU with PRI? The ultimate test to prove carrier.
=----(((((((((()----=
curlycord
Toronto Canada
- Thread starter
- #3
This patch, then the next one in February or March. Another vendor who helps in situations like this installed the last patch. He looked at all progamming and said it looked fine. When I updated the system to a pri i installed an expansion and put the pri card in the expansion. I originally thought that could have been the problem and moved the card to the main system and replaced the pri card. That was the first thing i did. I don't think i ever replaced the patch chord to the card though. Carrier says they monitored what they could and no problems on their end. however when their circuit extensions techs come out to test the extension. they have found errors 3 out of 4 times and never give any info on the errors. The extension is from verizon fiber in the main pbx of the hospital to the customers telco closet to a biscuit box. The system resides in the same room. Again that feed is over 1000'. So there is alot of room for loss and probably 3 telco closets in between. They did install the adtran at the phone system and the call drop got worse. when they removed it got better. Also there is an ACD with 9 clients. Originally it seemed to only be when calls were in que. i do not have another system to swap out. I have monitored it in bcm monitor and found some errors that were in suspect but i don't fully understand the report and they have several calls at time. I plan to run another report on monday and send it to the carrier.
- Thread starter
- #4
- Thread starter
- #5
This is one error i found from march records
16:02:35 > CC > CRef Origin: CRef 12 DISCONNECT
Cause - Invalid IE content
Location: Private network serving the local user
Coding Standard: CCITT standardized coding as described below
Cause Class: Protocol Error
Cause: Invalid information element contents
05 00 81 00 E4
16:02:35 < CC < CRef Origin: CRef 12 RELEASE_CC
16:02:35 > CC > CRef Origin: CRef 12 RELEASE_COMPLETE
Cause - Invalid IE content
Location: User
Coding Standard: CCITT standardized coding as described below
Cause Class: Protocol Error
Cause: Invalid information element contents
05 00 80 00 E4
16:02:35 > CC > CRef Origin: CRef 12 DISCONNECT
Cause - Invalid IE content
Location: Private network serving the local user
Coding Standard: CCITT standardized coding as described below
Cause Class: Protocol Error
Cause: Invalid information element contents
05 00 81 00 E4
16:02:35 < CC < CRef Origin: CRef 12 RELEASE_CC
16:02:35 > CC > CRef Origin: CRef 12 RELEASE_COMPLETE
Cause - Invalid IE content
Location: User
Coding Standard: CCITT standardized coding as described below
Cause Class: Protocol Error
Cause: Invalid information element contents
05 00 80 00 E4
norstarboy125
Vendor
Make sure yours protocol settings in the BCM match the carriers.
Charm City Communications
Charm City Communications
- Status
Similar threads
- Locked
- Question
- Locked
- Question