 04-11-2006, 02:38 AM | #1 (permalink) | ||||||||
| Junior Member
Location: Tampa Rep Power: 0  Gender:  Country:  | Telco problem or not? Hello to all! I'm glad I found this forum and look forward to contributing as much as I can. I am mostly self taught but I have few local guru's I bug periodically when I get stumped or stupid. I have a client I moved to new office in Jan. He switched telco vendors (Verizon to USLEC) and upgraded to PRI from T-1. System is MICS-XC 5.? and fiber NAM 4.1. All fiber with ASM mod. I upgraded to PRI software and reconfigured his system for DID's too. We have 4 digit DNIS, NI2, B8ZS, ESF - standard config like I've done dozens of times before. Since move and cutover to PRI we have had a problem with not all calls getting routed thru PRI. Calls will complete to system operator with message "line 1-23 to prime". Some calls will complete as routed thru DNIS on target lines. Problem has been present since cutover and got worse while USLEC did monitoring and call trapping. We (the client) has circumvented the problem on occasion by busying out the suspected problem b-channel. When that is done all calls seem to route OK. I have seen random Alrm 75, Alrm 41-44, EVT 323,330,331,336,327 some CFA's with OOF and LOS alarms. My internal CSU is turned on. The CO is Lucent 5ESS I think - definitely Lucent I have rebooted system numerous times, disabled and enabled card, deprovisioned and provisioned, reseated T1 card, software, and swapped T1 card. In addition I have replaced cable to smart jack and and still get random Alrm 75's. We have verified ground is good back to electrical panel. Nothing I have done has changed the consistency of the problem. Of course Telco (USLEC) says its got to be our hardware or software. They are stating they cannot find anything wrong when they test. Any ideas or comments would be greatly appreciated. I will send you one of my special made company golf hat or visor if your suggestion or remedy helps me resolve this issue. | ||||||||
 |   |
| 04-11-2006, 09:07 AM | #2 (permalink) | ||||||||
| Senior Member   Ramjet is wore ass out from the holidays!
Rep Power: 8 Gender: Country: | We had the same problem on a system with 2 pri's a couple of years back. SBC did various testing etc and continued to blame the problem on the equipment. We connected a T-Berd to the worst circuit and let it run for a while and found we were getting frame slips. We insisted that SBC change the cable pairs on that circuit, and all trouble stopped. I would be willing to bet that you have a marginal cable pair. __________________ Two snips, a snort, a turn, a fly, and a grunt, and it was so simple, like the jitterbug, it plum evaded me! | ||||||||
| | |
| 04-11-2006, 09:48 AM | #3 (permalink) | |||||||||
| Junior Member
Location: Tampa Rep Power: 0 Gender: Country: | Quote:
| |||||||||
| | |
| 04-12-2006, 09:16 AM | #4 (permalink) | ||||||||
| Senior Member Ramjet is wore ass out from the holidays!
Rep Power: 8 Gender: Country: | Yea, they always think they know more than you. In our case, we were the CLEC ourselves, providing the 2 pri's from our Santera 1 CO, so it stands to reason we knew just a little about it. Since the pair change on both pri's, there have been no problems at all. I always check the network log when I go onsite for anything. This is a 7.0 XC, and it is just about full (including ports 13 and 14 on the 2nd 6 port fiber card.  __________________ Two snips, a snort, a turn, a fly, and a grunt, and it was so simple, like the jitterbug, it plum evaded me! | ||||||||
| | |
| 04-27-2006, 10:53 PM | #5 (permalink) | ||||||||
| Junior Member
Location: Tampa Rep Power: 0 Gender: Country: | FYI follow up - we did have crappy Verizon lines, but the main culprit appears to be the internal CSU. The CSU is supposed to be transparent I think. However, I disabled it and re-enabled the PRI and blew about 50 inbound and outbound calls into the system and the event 609 code dissapeared. It was occuring once every 4-5 minutes throughout the day and usually followed up by an Alarm 75. | ||||||||
| | |
| 04-30-2006, 10:00 AM | #7 (permalink) | ||||||||
| Junior Member 
Location: Houghton, NY Rep Power: 7  | I would make them come on site with a T-bird to test your link. They are responsible for testing up to the D-Mark in your facility. I would have them come down and monitor the link. As stated above, they will most likely find a bouncing T-Span causing slips or frame losses. | ||||||||
| | |
| 05-01-2006, 08:16 AM | #8 (permalink) | ||||||||
| Senior Member Ramjet is wore ass out from the holidays!
Rep Power: 8 Gender: Country: | The Tberd is how we proved it was their problem! Gotta love it!!!!!!!!!!!!!! __________________ Two snips, a snort, a turn, a fly, and a grunt, and it was so simple, like the jitterbug, it plum evaded me! | ||||||||
| | |
 |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
 Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Really Strange MICS/AA/Voice Mail problem | lgherb | BCM and Norstar | 5 | 04-06-2006 09:30 AM |
| BayStack 460 PoE problem | dixi | Meridian Systems | 2 | 09-10-2004 04:36 PM |
| Callpilot Apllication Problem | sneexy69 | Meridian Systems | 2 | 11-22-2003 12:23 PM |
| Strangest Problem Ever ? | markj39k | BCM and Norstar | 11 | 01-15-2003 10:11 AM |
Linear Mode
