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!

 

[trvlr1]

In my system, if 2222 had been used and then deleted, it would automatically route to the operator. In the case of 3333, if it has not been used, it will give a busy as you are seeing.

 

[trvlr1]

If you look in to your RDB there are all kinds of entries that refer to routing various types of calls, specifically in INT_DATA.
PRT
INT_DATA

Calls To Vacant Number
CTVN if set to OVF OVF OVF ATN should send calls to the operator for unassigned numbers, but I still have the scenario above where numbers that have never been assigned get recordings saying the number is unassigned. One of these days I will figure out why that happens.

 

[mikep1230]

Okay, I think I follow what you're getting at. The problem is that when I do a ld 21/prt/int_data I see:
CTVN OVF OVF OVF OVF

If I'm interpreting the info in another thread (

http://www.tek-tips.com/viewthread.cfm?qid=1561241&page=250)

correctly, that means calls to a vacant number are set to be rejected (and not transferred to the operator).

 

[trvlr1]

I would agree with your assessment, looks like we need to have someone with more experience than either of us chime in on this one .... OVF should give you a telco intercept message.

 

[trvlr1]

One other thing to look at, in LD 23, check see if those numbers are CDN's

 

[mikep1230]

No dice; we've got a single CDN, and it's not any of the above.

I do appreciate your continued efforts on this!

 

[RickyPone]

Print 222 in ld20. Or print 22.

 

[mikep1230]

Sorry, what type(s) would I specify there? I've tried type 'dnb' in ld 20 and found no hits.

 

[RickyPone]

If you have tried 22 or 222 already then don't bother. In ld20 prt the type ludn. If it is unused it will be there.

 

[mikep1230]

I did a ld 20/prt/ludn... I found 333 (partial match), but nothing for 1111 or 2222.

 

[trvlr1]

If you dial each of those numbers slowly, do you get the message/operator prior to getting all 4 digits in? ie if you dial 1 or 11 do you get a result, or do you have to dial 111 or 1111 to get the result? As I think Rickypone is alluding to, you may have a really short dial string set up for something that may not be used any more.

 

[RickyPone]

Could be in a database as an fdn or hunt

 

[RickyPone]

Forget the last post. You said you were actually dialing the dn.

 

[mikep1230]

Okay, interesting. I just tried dialing from a phone directly connected to the PBX, and got:

1111 - fast busy
2222 - operator
3333 - fast busy

In all cases, the result came immediately after the 4th digit was entered.

Previously I'd only been looking at inbound calls from the PSTN; I hadn't tried dialing from inside the office.

RickyPone -- How would I check for those?

Thanks!

 

[RickyPone]

You have to print the tnb. Then look at every one. I wouldn't do that if I were you. What is your spre code? Ld21 prt ftr_data

 

[GHTROUT]

If you found 333 in LUDN, then 3333 does not exist in your PBX, anywhere.

1111 is the CDP number you already found.

2222 I suspect you missed...so do this:

LD 20
REQ PRT
TYPE DNB
DN 2



--
Nortel Resources at GHTROUT.com
--

 

[mikep1230]

Wow... somehow you're totally right GHTROUT, I missed 2222 in the ld 20/prt/dnb. I have no idea how; I'd followed the same process from previously-found forum posts, and didn't find it in the output for reasons I can't explain right now. The type is LDN (Listed Directory Number?). I found a ld 21/prt/ldn_data which spit out an LDN0 entry that's 2222. The LDN2 entry there syncs with what I expect the the primary reception/operator number to be. If I'm interpreting things correctly again, this is basically a set of buttons on the receptionist's phone?

Okay, so let me see if I can run this all down again:
1111 = pointed at a down trunk, which means it goes to the attendant
2222 = on the receptionist's phone
3333 = defined nowhere, hence fast busy

Again, many thanks for the assistance!

 

[nessman]

If you say you haven't touched a PBX ever until 3 days ago, I would strongly suggest you let your vendor tackle this one for you.

I don't mind helping customers out with little things they can safely do on their own - so long as it doesn't impact our revenue stream and I find a little bit of knowledge on their part makes them less daring. But customers under maintenance who don't know what they're doing can cost us vendors a lot of money in labor for fixing things they broke because their (usually bored) IT guy was trying on the phone guy hat. Don't be that guy!

With that... do you have incoming DID's? Are your DID blocks encompassing 1111 and 3333? If so - and you have no DN 1111 or 3333 - it's not going to connect unless you do some incoming digit conversion to route calls in those blocks to an attendant or a recording saying that # isn't in service. On a Meridian, extensions starting with 1 tend to be rare as you're in SPRE territory there. You have no DN 3333 in your system because when you did a LUDN, you only got a 333 - meaning there's no DN's in the system from 3330 to 3339.

Again, because you're new at this (and we all were at some point) work with your vendor!! Cut your teeth on some basic stuff first (phone moves/adds/changes) before you start getting into the nuts and bolts of the PBX. If your company depends on the phone system to generate revenue and support customers - and your tinkering brings those calls to a halt... well, it's a bad job market for unemployed IT folks (as a former IT manager I would fire you on the spot).

 

[GHTROUT]

He is working with his vendor - you're just doing it for free again nessman

Actually, I can't think of anyone who has come so far and done so well in 3 days. He's beyond most vendor techs already. Bravo.

--
Nortel Resources at GHTROUT.com
--