Not accepting 4 digits over isdn tie line 1

[chancal]

Hello everyone,
I have a a Nortel Option 11 on one end of a 23-channel tie line and an i3 switch on the other end used for building to building extension dialing.

we just recently changed our corporate DID block to a new contiguous block for our 2 buildings so i've had to change the dial plans to accomdate the new extensions to go over the tie.

Nortel building uses 8400 to 8499 block, i3 building uses 8000 to 8199 block.

I have set up my i3 side fine, i am able to dial 4 digit Nortel extensions from i3 no problem.

I cant do the same from Nortel to i3.

As a test, i have created 1 test number as follows on my Option 11:
CUST 0
FEAT cdp
TYPE dsc
DSC 8080
DSC 8080
FLEN 0
DSP LSC
RLI 9
NPA
NXX
The RLI 9 points it to go over the ROUT of where my tie line is (note that this hasnt changed, this is the same even before my contiguous DID migration)

My RLI 9 looks like this:
CUST 0
FEAT rlb
RLI 9

RLI 9
ENTR 0
LTER NO
ROUT 13
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ YES

ISET 1
NALT 5
MFRL 0

and my ROUT 13 looks like this:
>ld 21
PT1000

REQ: ltm
CUST 0
ROUT 13

TYPE TLST
TKTP TIE
ROUT 13
DES I3_TIES
TN 006 01 MBER 1 I3TIE
TN 006 02 MBER 2 I3TIE
TN 006 03 MBER 3 I3TIE
TN 006 04 MBER 4 I3TIE
TN 006 05 MBER 5 I3TIE
TN 006 06 MBER 6 I3TIE
TN 006 07 MBER 7 I3TIE
TN 006 08 MBER 8 I3TIE
TN 006 09 MBER 9 I3TIE
TN 006 10 MBER 10 I3TIE
TN 006 11 MBER 11 I3TIE
TN 006 12 MBER 12 I3TIE
TN 006 13 MBER 13 I3TIE
TN 006 14 MBER 14 I3TIE
TN 006 15 MBER 15 I3TIE
TN 006 16 MBER 16 I3TIE
TN 006 17 MBER 17 I3TIE
TN 006 18 MBER 18 I3TIE
TN 006 19 MBER 19 I3TIE
TN 006 20 MBER 20 I3TIE
TN 006 21 MBER 21 I3TIE
TN 006 22 MBER 22 I3TIE
TN 006 23 MBER 23 I3TIE

Before the DID contiguous block migration, we were using 3-digit extension dialing for inter and intra office dialing. All this programming is still intact.
Is there still a 3 digit cap somewhere on the option 11 that was programmed before my time?

please help. thank you

 

[GHTROUT]

I would be testing by using the Route Access code, to determine if it is a BARS/CDP issue or a route issue. You have not printed the route out, only the list of trunks.

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too

 

[chancal]

Sorry im not following that part? what should i do to test with Route Access Code?

 

[GHTROUT]

Dial the Route Access code of the Route that links you to the distant system, then dial an extension in the distant system.

The test you are performing right now is dialing a CDP Steering Code, so you are adding BARS/CDP into the test. You want to make sure the Trunk Route and the distant system are working as expected.. THEN build and start using CDP.

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too

 

[PERRYPJ]

He is saying to dial the ACOD and then the 4 digit number and see if it works

OLD ROLMEN WORKING ON NORTELS AND AVAYA

 

[Reusser]

Also - turn on DCH messaging - this will give you clues to what side is rejecting and why.

 

[chancal]

okay so when i try dialing with the acod (7913), i get a fast busy as i enter the 3. What does that mean?

 

[GHTROUT]

That might mean your own phone is restricted.

As the telecom person, you need:

-- an NCOS that equals FRL 7
-- TGAR 0
-- CLS UNR

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too

 

[chancal]

GHTrout you are right.
I made the NCOS and TGAR change and can dial it now.
So by pressing 7913 and 8080 i can get to the other side.
This is what d-channel messages are saying:
DCH 13 OMSG SETUP REF 00000017 CH 6 23 TOD 15:04:28
CALLING #XXX-XXX-XXXX NUM PLAN: E163
CALLED #:8080 NUM PLAN: E163

DCH 13 IMSG CALLPROC REF 00000017 CH 6 23 TOD 15:04:28

DCH 13 IMSG ALERT REF 00000017 CH 6 23 TOD 15:04:28
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 13 IMSG CONNECT REF 00000017 CH 6 23 TOD 15:04:28

DCH 13 OMSG CONN ACK REF 00000017 CH 6 23 TOD 15:04:28

DCH 13 OMSG DISC REF 00000017 CH 6 23 TOD 15:04:44
CAUSE :NORMAL CALL CLEARING

DCH 13 IMSG RELEASE REF 00000017 CH 6 23 TOD 15:04:44

DCH 13 OMSG REL COMP REF 00000017 CH 6 23 TOD 15:04:44

So where does that leave me? Why can't i just dial 8080 by itself?

By the way, when i 8080 it just eventually goes to a fast busy and there are no d-channel messages from it.

 

[GHTROUT]

In the case of 7913+8080 working, and the BARS apparently correct, what I would do is create a new LD86 Route List that looks just like RLI 9. This will eliminate Route List corruption.

If nothing changes, then I would LD87 OUT DSC 8080 and build it back as "TSC" 8080

If that does not solve it, then I would build a DMI table that did nothing (does not inst or del anything) and add it to the Route List.

If that does not solve it, I would look at your LD21 LDN_DATA and make sure that LDN0 is a four digit number.

If that did not solve it, I would EDD and Reload.

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too

 

[chancal]

GHTROUT,
you are the man!
I tried the RLI thing with a new RLI 11 and repointed DSC 8080 to it. Didnt make a difference.
I then outed DSC 8080 and recreated it as TSC 8080. it works with both my original RLI 9 and the new RLI 11 so it's not route list corruption.

what is TSC? what does it do?
thanks again