Nortel to Cisco T1s

[rachelle]

Here is a lot of stuff, from my Nortel CS1000 side. They want all inbound to the Cisco to come from Nortel Loops 104, 105, 124. They want all outbound from Cisco to use Nortel Loops 56, 100, 125. The Cisco guys are seeing inbound calls on 56, 100, 125... they don't want that.

I don't know what more I can do. The route is LIN. The member order has been set as follows. Please advise what you would do at this point. I don't know what more to do for them.

Router located in 60A:
0/0/0 Loop 56 DCH 12
0/0/1 Loop 100 DCH 18
0/1/0 Loop 125 DCH 20

Router located in 63C:
0/0/1 Loop 104 DCH 16
0/1/0 Loop 105 DCH 17
0/1/1 Loop 124 DCH 19



TYPE RDB
CUST 00
ROUT 104
DES VOIP
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC D100
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD xxxxxx
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 0
NDNO 0 *
DEXT NO
DNAM NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3


PAGE 002

NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
RACD 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
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR YES
ASID 17
SFNB
USFB
CALB 7 8


per our call:
104, 105, and 124 are in 63C
56, 100, and 125 are in 60A


All trunk members are built like the following:
DES VOIP
TN 104 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 3
RTMB 104 1
B-CHANNEL SIGNALING
TGAR 1
AST NO
IAPG 0
CLS CTD DTN WTA LPR APN THFD HKD
P10 VNL
TKID
FCAR NO
AACR NO


All Trunk members, in order:
ROUT 104

TYPE TLST
TKTP TIE
ROUT 104
DES VOIP
TN 104 01 MBER 1 VOIP
TN 104 02 MBER 2 VOIP
TN 104 03 MBER 3 VOIP
TN 104 04 MBER 4 VOIP
TN 104 05 MBER 5 VOIP
TN 104 06 MBER 6 VOIP
TN 104 07 MBER 7 VOIP
TN 104 08 MBER 8 VOIP
TN 104 09 MBER 9 VOIP
TN 104 10 MBER 10 VOIP
TN 104 11 MBER 11 VOIP
TN 104 12 MBER 12 VOIP
TN 104 13 MBER 13 VOIP
TN 104 14 MBER 14 VOIP
TN 104 15 MBER 15 VOIP
TN 104 16 MBER 16 VOIP
TN 104 17 MBER 17 VOIP
TN 104 18 MBER 18 VOIP
TN 104 19 MBER 19 VOIP
TN 104 20 MBER 20 VOIP
TN 104 21 MBER 21 VOIP
TN 104 22 MBER 22 VOIP
TN 104 23 MBER 23 VOIP
TN 105 01 MBER 24 VOIP
TN 105 02 MBER 25 VOIP
TN 105 03 MBER 26 VOIP
TN 105 04 MBER 27 VOIP
TN 105 05 MBER 28 VOIP
TN 105 06 MBER 29 VOIP
TN 105 07 MBER 30 VOIP
TN 105 08 MBER 31 VOIP
TN 105 09 MBER 32 VOIP
TN 105 10 MBER 33 VOIP
TN 105 11 MBER 34 VOIP
TN 105 12 MBER 35 VOIP
TN 105 13 MBER 36 VOIP
TN 105 14 MBER 37 VOIP
TN 105 15 MBER 38 VOIP
TN 105 16 MBER 39 VOIP
TN 105 17 MBER 40 VOIP
TN 105 18 MBER 41 VOIP
TN 105 19 MBER 42 VOIP
TN 105 20 MBER 43 VOIP
TN 105 21 MBER 44 VOIP
TN 105 22 MBER 45 VOIP
TN 105 23 MBER 46 VOIP
TN 124 01 MBER 47 IP124
TN 124 02 MBER 48 IP124
TN 124 03 MBER 49 IP124
TN 124 04 MBER 50 IP124
TN 124 05 MBER 51 IP124
TN 124 06 MBER 52 IP124
TN 124 07 MBER 53 IP124
TN 124 08 MBER 54 IP124
TN 124 09 MBER 55 IP124
TN 124 10 MBER 56 IP124
TN 124 11 MBER 57 IP124
TN 124 12 MBER 58 IP124
TN 124 13 MBER 59 IP124


PAGE 002

TN 124 14 MBER 60 IP124
TN 124 15 MBER 61 IP124
TN 124 16 MBER 62 IP124
TN 124 17 MBER 63 IP124
TN 124 18 MBER 64 IP124
TN 124 19 MBER 65 IP124
TN 124 20 MBER 66 IP124
TN 124 21 MBER 67 IP124
TN 124 22 MBER 68 IP124
TN 124 23 MBER 69 IP124
TN 056 01 MBER 70 VP56
TN 056 02 MBER 71 VP56
TN 056 03 MBER 72 VP56
TN 056 04 MBER 73 VP56
TN 056 05 MBER 74 VP56
TN 056 06 MBER 75 VP56
TN 056 07 MBER 76 VP56
TN 056 08 MBER 77 VP56
TN 056 09 MBER 78 VP56
TN 056 10 MBER 79 VP56
TN 056 11 MBER 80 VP56
TN 056 12 MBER 81 VP56
TN 056 13 MBER 82 VP56
TN 056 14 MBER 83 VP56
TN 056 15 MBER 84 VP56
TN 056 16 MBER 85 VP56
TN 056 17 MBER 86 VP56
TN 056 18 MBER 87 VP56
TN 056 19 MBER 88 VP56
TN 056 20 MBER 89 VP56
TN 056 21 MBER 90 VP56
TN 056 22 MBER 91 VP56
TN 056 23 MBER 92 VP56
TN 100 01 MBER 93 VP100
TN 100 02 MBER 94 VP100
TN 100 03 MBER 95 VP100
TN 100 04 MBER 96 VP100
TN 100 05 MBER 97 VP100
TN 100 06 MBER 98 VP100
TN 100 07 MBER 99 VP100
TN 100 08 MBER 100 VP100
TN 100 09 MBER 101 VP100
TN 100 10 MBER 102 VP100
TN 100 11 MBER 103 VP100
TN 100 12 MBER 104 VP100
TN 100 13 MBER 105 VP100
TN 100 14 MBER 106 VP100
TN 100 15 MBER 107 VP100
TN 100 16 MBER 108 VP100
TN 100 17 MBER 109 VP100
TN 100 18 MBER 110 VP100
TN 100 19 MBER 111 VP100
TN 100 20 MBER 112 VP100
TN 100 21 MBER 113 VP100
TN 100 22 MBER 114 VP100
TN 100 23 MBER 115 VP100
TN 125 01 MBER 123 VP125
TN 125 02 MBER 124 VP125
TN 125 03 MBER 125 VP125
TN 125 04 MBER 126 VP125
TN 125 05 MBER 127 VP125
TN 125 06 MBER 128 VP125


PAGE 003

TN 125 07 MBER 129 VP125
TN 125 08 MBER 130 VP125
TN 125 09 MBER 131 VP125
TN 125 10 MBER 132 VP125
TN 125 11 MBER 133 VP125
TN 125 12 MBER 134 VP125
TN 125 13 MBER 135 VP125
TN 125 14 MBER 136 VP125
TN 125 15 MBER 137 VP125
TN 125 16 MBER 138 VP125
TN 125 17 MBER 139 VP125
TN 125 18 MBER 140 VP125
TN 125 19 MBER 141 VP125
TN 125 20 MBER 142 VP125
TN 125 21 MBER 143 VP125
TN 125 22 MBER 144 VP125
TN 125 23 MBER 145 VP125

no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[bhassell2000]

look at the RLIs in LD 86 and see what calls are routed to the routes that you dont' want calls to go over from the Nortel switch

Thanks,

Buddy

 

[rachelle]

Route 104 connects the two systems. There are 6 Loops assigned to this route. See my member ordering, why would a call hit loop 56 and not loop 104, when 104 is totally available?

The RLIs send calls to the telco (local and long distance). This route is only used for calls between the two platforms.


rlc

no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[Tman45]

The way I see it is that you should change your route 104 to be labeled inbound VoIP and create a new route to be your outbound VoIP if your Cisco nuts desire it to be setup that way. So basically what is happening now is that you only have 1 route (104) that can hold calls so they will see both inbound and outbound on them ... not sure how to specify inbound to use the new route only - someone else that is better versed in inbound/outbound routing can clarify.

 

[rachelle]

Please confirm:

If outbound from Nortel to cisco, calls will start on Loop 104, channel 23. Yes?
If inbound from cisco to Nortel, call will start on Loop 104, channel 1. Yes?

If the above two assumptions are correct then, how can I change the Loop orders? Do I not control that from the member ordering?

Why would Loop 56 and 125 be filling from channel 23 down, before loop 104?

I think that we have an ordering issue but, I don't know how to fix it.

CALLING ALL ROUTING GURUs!!!!!!




rlc


no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[bhassell2000]

the order for outbound calls is in the ordering in the RLI entry 0 then entry 1 thren entry 2 an so on. Id 104 is the first choice it will always go there first.

Thanks,

Buddy

 

[rachelle]

Route 104 is the only route used by this RLI. How do you control what channel or loop is used within the Route? Is that the route member order? If not, how does it pick a channel?


rlc

no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[Tman45]

Exactly my point - you should create a new route to split your inbound outbound calls otherwise ALL your calls are going to go to ROUTE 104 which means you will have ALL outbound and ALL inbound - there is NO OTHER route to choose from - so leave your outbound setup the way it is and create a new inbound VoIP route - it would probably be less confusing if you didn't have a Loop 104 and a Route 104

 

[rachelle]

Not sure what you mean. How do I communicate this to the cisco side? What do I need to do on my side?


rlc

no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[Reusser]

Linear hunt in the route would indicate that outbound calls from Nortel would 1st hit trunk 145 - loop 125 channel 23 - last member in the route working towards the 1st member

TN 125 22 MBER 144 VP125
TN 125 23 MBER 145 VP125

you need to do one of 2 things:

1 do as TMAN45 suggest and create a new route with Member from loops 56, 100, and 125

or
2 move loops 104, 105, 124 to the last members in the route

 

[rachelle]

For option 1, the building of a new route. I know how to do that easy enough.

I would leave route members 104, 105, and 124 in Route 104, accessed by RLI 104. I would create a new RDB with 56, 100, and 125 members. What is the access for this route? I have always had in and out on my routes. How do you set them as only inbound or only outbound?

I think option 2 is looking better and better.


rlc

no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[Reusser]

set it up same as the other route but do not add a pointer in a RLI to it. Unless someone dials ACOD it is an inbound only route.

 

[johnpoole]

add a new route.(105). you can set iao to inbound only instead of iao.. then ld 14 out 23, remove all 23 port of say 56.. new 23 and on rtmb 105 1.. moves then to inbound route.. as long as 105 in not in your rlb, it's not going to take outbound calls..

to seperate calls by direction, you need two rdb's, with only one as an entry in ld rlb

john poole
bellsouth business
columbia,sc

 

[rachelle]

Okay, to recap:

If no RLI access a route, that route is inbound only. Yes?

In the RDB I will set to what pneumonic for inbound only or outbound only?

Route 104 has a ton of RLIs pointing to it so, that would be my outbound. Yes?
New Route XXX will have no RLIs so, that is inbound. Yes?

I think that I am starting to see the whole picture. I hope, that is.

rlc

no matter where you go, there you are.
"This participation is persona and does not represent the United States Census Bureau." They make me say this.

 

[StanleySteamer]

The ONLY way to prevent calls from from going out to the Cisco on loops 56,100,125 is to put them in a separate route. Changing the order of trunk members won't help.

Even with SRCH LIN on the route a phone that is in network group 1 (loops 32 to 63) will use trunks in loop 56 as a first choice. The switch tries to keep the outbound calls in the same network group.

 

[Reusser]

you are correct - if you want to tag route as incoming only, prompt is ICOG set to ICT

 

[PareshTC]

Always try and use only 1 Loop within a route and keep route and loop numbers identical for tracking. This way I can control via RLB's what routes are used for incoming and what for outgoing. Dunno if that would work for all setups though, but i found it helps simplify call routing.

 

[johnpoole]

it's great when you can do that.. i've always perfered it.. for instance, my loop 49 is a pri going to a remote (parkridge).. the rdb is 49, the rlb is 49 the dgt is 49 as well as dch 49.. if i could have, i would have sent the 49xx numbers to that site.

if i have a trouble at parkridge, i don't spend much time tracking a call through the box

john poole
bellsouth business
columbia,sc