|
|
|
|
Joined: Mar 2002
Posts: 3,630
Moderator-Avaya, Nortel
|
|
Moderator-Avaya, Nortel
Joined: Mar 2002
Posts: 3,630 |
working on a PRI with ATT. Can't dial in or out. D channel is up. the only alarm or error I get is Pool Busy or OOS.
does this mean that the legend has went out via the D channel and requested a trunk and gotten back a response from the switch? The ATT tech says they don't even see us on the D channel.
Help ASAP!
|
|
|
|
|
Joined: Aug 2004
Posts: 9,172 Likes: 22
Admin
|
|
Admin
Joined: Aug 2004
Posts: 9,172 Likes: 22 |
Sounds like the B channels are not configured in the trunk group,not released,or I've had a bad DSX cross connect in the CO emulate the same problem. I would have them check and redheck the protocol translations.
|
|
|
|
|
Joined: Aug 2004
Posts: 9,172 Likes: 22
Admin
|
|
Admin
Joined: Aug 2004
Posts: 9,172 Likes: 22 |
typo- make that recheck the protocol translations.
|
|
|
|
|
Joined: Mar 2002
Posts: 3,630
Moderator-Avaya, Nortel
|
|
Moderator-Avaya, Nortel
Joined: Mar 2002
Posts: 3,630 |
well, after banging our heads, seems we had some corrupt program or something in the switch. once we cleaned it out and started over, it all worked fine. We were switching from a standard DS1 to PRI, so there was a need to get rid of some of that programming.
|
|
|
|
|
Joined: Mar 2002
Posts: 117
Member
|
|
Member
Joined: Mar 2002
Posts: 117 |
I had a similar response. I was turning up a fractional PRI with 11 channels. I was told the first 11 and D on 24. I built the circuit a week in advance. On cut day, same results. It turned out that the particular carrier likes to build their fracs from the bottom up. So basically the D was up, but no B channels assigned to the channels the carrier was looking for. **#@@?
|
|
|
|
Forums84
Topics94,528
Posts640,022
Members49,852
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (jab1780),
150
guests, and
47
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
![[Linked Image]](https://sundance-communications.com/forum/images/559.jpg)