Nortel Routing Change 1

[AnthonyHardy]

CS1000 involved: We're changing our ld lines to another switch (already connected to the cs1000 via pri, functional).

Currently, we dial 4 to access ld lines (8 tie trunks on the cs1000). I need to re-route that to the other switch across the PRI.

I've been doing a lot of searching, trying to figure out exactly what I will need to change and here's what I have found so far:


>ld 20

REQ: prt
TYPE: dn
TYPE DNB
CUST 0
DN 4
DATE
PAGE
DES

DN 4
TYPE RDB
ROUT 3

So, it looks like dn of 4 uses ROUT 3. I need it to use ROUT 11, but I'm not sure how to change that.

Here's RDB 3:


>ld 21
PT1000

REQ: prt
TYPE: rdb
CUST 0
ROUT 3

TYPE RDB
CUST 00
DMOD
ROUT 3
DES ATTNET
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK NO
ISDN NO
PTYP ATT
AUTO NO
DNIS NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 4
TARG 03
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP SDAT
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3

IENB 5
TFD 0
VSS 0
VGD 6
SST 5 0
NEDC ETH
FEDC ETH
CPDC NO
DLTN YES
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
VRAT NO
MUS YES
MRT 8


PAGE 002

MANO NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO


You can see the ACOD of 4 there, so I'm guessing that's how the route to the tie trunks is made (doing an LTM confirms that the current ld trunks are associated with ROUT 3 and that ROUT 11 is the other switch).

Currently, I have a DSC that routes 79xxxx to ROUT 11, so I thought I could perhaps just remove the RDB 3 and create a DSC (4) that would point to ROUT 11 as well, but I'm nervous about doing that as I don't know if I could simply add the RDB back and go back to the way we currently handling ld calls. I also thought that perhaps I could change RDB 3 and make the ACOD 49 or something else (does it have to be an available dn?), but I can't change the ACOD to 49 or even another available dn (101 is available).

Ignorance sucks . . Any ideas?

 

[Firebird Scrambler]

My guess is that you need to be in LD 16 and change the RDB route 4 to a different ACOD number. Then change the ACOD of route 11 to have a "4". It might also be wise to print off the ESN data and view it via the Excel program to get an overall view of all numbers dialled out.

http://www.ghtrout.com/ghtrout/files/ConversionUtility(BARS-TNB-More)_by_DB.zip

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[AnthonyHardy]

Haven't had a chance to try the excel sheet, but will first thing in the morning. Tried changing the ACOD or ROUT 3 to something else (was able to) and then changing the ACOD of ROUT 11 to 4, just got a fast busy.

I thought perhaps I could do a DSC, but it doesn't allow full 10 digit plus code dialing (that I can figure out). When someone dials 4NPA-NXX-XXXX, it needs to go over ROUT 11 and the PRI. It can send the 4 or not, I can handle the translation on the other end.

I'll take a look at the excel sheet tomorrow and see if it can help me figure it out. Thanks!

 

[AnthonyHardy]

Well, no luck. The spreadsheet has issues (won't parse my files), so that doesn't help.

Any other hints? I obviously don't know how 4 is working. I change the ACOD of ROUT 3 (normally 4, change it to something else, 8911 for example), and dialing 4 gets a fast busy (makes sense).

I then create a DSC of 4, using the same RLI that my other DSC that goes to the same system is using.

Should I perhaps setup some sort of digit manipulation? I can handle the remote end (figure out how to route what ever comes my way), but I need to get the nortel to send it there.

Any assistance is GREATLY appreciated.

 

[AnthonyHardy]

OK, figured out something, finally, at least partially. Changed ACOD on ROUT 3 away from 4. Changed ACOD on ROUT 11 (to system where new ld lines are) to 4. Added a DSC of 4 and now I can dial 4 and get to the new system where I can wait on the full number and do what is needed.

Now, to get my remote Nortel (uses ip tie trunks back to my main Nortel) to be able to do the same thing. They dial 51<area code><number> to get to the old ld trunks. Here we go again!

 

[AnthonyHardy]

ugh. having a time trying to figure this remote site out.

They dial 51<area code><number>. There is a DGT that removes the 4 and inserts a 4. Using dch messages, I can see the main site is getting 4<area code><number>.

What I want to do is just have the remote site dial 5, come to the main site, translate that to ext 4, which moves to my ld trunks and then let's them dial the ten digit number.

How can I find out where that 5 is being handled at the remote site? Here's what I'm dug up so far:

In the ESN 5 was AC2 (no idea if that means anything). Still trying to track it down. Any help is greatly appreciated.

 

[AnthonyHardy]

OK, got that the remote site had an ACOD of 5 on it's ROUT coming back to the main switch (missed that earlier). Setup remote switch so it will send 5 alone to the main CS1000.

Somewhere in the main switch there is something preventing me from creating an acd, a dsc or anything with 5. Trying to track it down, no luck so far.

 

[bhassell2000]

Prt
dnb
dn 5

in main switch and see if its used for something

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/pub/buddy-hassell/7/5a5/b8b

 

[AnthonyHardy]

Ah . nm. Changed the remote switch to send 51 to the main switch and then I could setup a DSC for 51 to be pushed to the system handling long distance.

THanks for taking the time to post assistance, firebirdscrambler. I do appreciate it. ALso, thanks to this whole forum, as most of my digging and hints to my final solution came from the years of knowledge accumulated here.