Can't find any routing information for DNs 1

[mikep1230]

I have a Nortel 81c PBX. I'm trying to track down how it handles 3 different inbound calls:
DNIS 1111 = Seems to ring operator during the day, auto attendant at night
DNIS 2222 = Seems to work the same way as 1111
DNIS 3333 = 'No such number'/fast busy

The problem is I've never touched a PBX until 3 days ago. This forum has been incredibly helpful, starting with "how to log in" and going from there.

With that information, I've found:
- There's a Distant Steering Code (DSC) of 1111 configured in the Coordinated Dial Plan (CDP) -- load 87. This points to Route List Indicator (RLI) 29.
- RLI 29 (in load 86) points to route 8.
- Route 8 (in load 21) contains a reference to "TIE" and "FAXSEV".
I'm interpreting this as: 1111 dials the fax server, which has been shut down for a year now. Maybe it fails back to the operator when that tie line is down?

I've found no reference at all to 2222 or 3333 though; I tried a prt in ld's 49 (type icd), 23 (type acd), 95, and 20 (type dnb).

The guys we contract for this stuff are apparently claiming that unknown DNs always end up at the operator... but then why does 3333 get rejected? I operate the device that actually feeds the "PSTN" connection to the PBX, and I literally see the ISDN messages where my end sends a "SETUP" and the PBX clears the call with "number unassigned." Why would 2222 and 3333 behave differently if neither is assigned?

Thanks in advance for any help that can be offered!

 

[nessman]

I dunno... I hear "I have an 81c and I never touched a PBX before" and I get nervous.

Sounds as though he didn't like the answer he got from his vendor (valid concern) and decided to take a stab at it himself. Not sure how big his vendor is - but they should have an escalation path if he's not happy with what the field tech told him. If not - maybe it's time he shopped for a better vendor.

If this was a single cabinet 11c at a small 'who cares?' non-profit, hey - have fun learning (and yes, he has come a long way which is commendable)... but a system that big for someone that green - IMHO it's too much risk.

With that - make sure you go into LD 43 and do an EDD before you start playing around just in case you need to go back.

 

[mikep1230]

I do appreciate the concern, guys -- talk about going above and beyond!

You may be relieved to know that I'm aware of my limitations: I'm perfectly happy to look at it, but I have no intention of making changes to a system that I don't understand. My original goal was to gather enough information that I could intelligently contradict the field tech who gave us the initial answer and force them to look deeper. Between some usage data I already had and what you guys helped me figure out though, I can actually accomplish what I need to without ever touching the PBX, which works out even better. Were we not replacing this thing in 6 months anyway (with a system that we can better support and which is more appropriately sized to the 100-user site), I might care more about the competency of our contracted techs. ;-)