Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

S8300/G700's: Re-route outgoing calls from an LSP(branch ofice) thru Core(Main office) system's PRI? 1

Status
Not open for further replies.

pichels

Technical User
Aug 1, 2005
313
US
Hi-

Hopefully explaining this properly - we need help this weekend(next few days) - started a move of our office to a new building.
We have our Avaya Definity up and running but the new PRI is damaged and under water.

We already have our Telco routing our “incoming” - 800/Local numbers for this branch office(LSP - S8300/G700's) routed thru our main office - core(also S8300/G700's) system - that is working.
However - we'd like to re-route our "outgoing" calls from this LSP or branch office system thru our main/core system across our MPLS thru our Madison office.

1.
Here is the trunk that needs to be re-routed..

display trunk-group 20 Page 1 of 21
TRUNK GROUP

Group Number: 20 Group Type: isdn CDR Reports: y
Group Name: Branch office PRI(LSP) COR: 73 TN: 1 TAC: 720
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4

GROUP MEMBER ASSIGNMENTS Total Administered Members: 23

Port Code Sfx Name Night Sig Grp
1: 004V101 MM710 20
2: 004V102 MM710 20

2.
To this trunk here...

display trunk-group 11 Page 1 of 21
TRUNK GROUP

Group Number: 11 Group Type: isdn CDR Reports: y
Group Name: Primary-PRI(Core) COR: 1 TN: 1 TAC: 711
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4

Can anyone help us re-route traffic from one S8300 to another S8300?
Please let us know if you need further details.
Thx.

-SP



 
Appears I may have to change route-pattern and check ars anal XXX for other route patterns we missed?
 
list route" will show you anything using TG20 as a 1st choice. Do a screen shot, then update the route patterns to use TG11 as a 1st choice. Bigger picture......you may want to just add TG11 as a 2nd choice on this branch office routes so all of this happens automatically for you in the future. Both for outages and for "all trunks busy" conditions. No need to dive into the ARS tables for this.

-CL
 
Hi-

Thx - I tried changing route patterns earlier to no avail yet - must be missing something.

Here we have all sorts of routes for the Core system at our main site.
Don't we want to match or get the branch(LSP) site to use these routes - right?

1.
Main(Core - working PRI that branch/LSP needs to use)

list route-pattern Page 1
ROUTE PATTERNS
Route Name/Trk FRL Hop IXC BCC TSC CA-TSC ITC Service/Feature
Pat Pref Grp Lmt 0 1 2 3 4 W Request
1 Core Local
1 11 3 user y y y y y n n none both
2 1 3 user y y y y y n n none both
2 Core LD
1 11 4 user y y y y y n n none rest
2 1 4 user y y y y y n n none rest
3 Core Intl
1 11 5 user y y y y y n n none rest
4 Core Tollfre
1 11 3 user y y y y y n n none rest
2 1 3 user y y y y y n n none rest
5 Core 911
1 11 0 user y y y y y n n none rest
2 1 0 user y y y y y n n none rest

ARS:

Dialed Total Route Call Node
String Min Max Pattern Type Number
16 11 11 p2 fnpa
1608270 11 11 p2 hnpa
1608271 11 11 p2 hnpa
1608273 11 11 p2 hnpa
1608277 11 11 p2 hnpa
1608279 11 11 p2 hnpa
1608576 11 11 p2 hnpa


2.
Branch(LSP - needs to use Main/core PRI/routes for outgoing calls - the AC is 319)

NOTE:
Change to TG 11 - same as Main/Core site above - still not working according to our tests so far...need to make sure they are dialing correctly - worry about ARS - since we'd had to add many entries for cell phones and diff area codes forced by our Telco setup on PRI!


21 Branch Local
1 11 3 user y y y y y n n none rest
22 Branch Long Distanc
1 11 4 user y y y y y n n none rest
23 Branch Intl
1 11 5 user y y y y y n n none rest
24 Branch Toll Free
1 11 3 user y y y y y n n none rest
25 Branch 911
1 11 0 user y y y y y n n none rest
26 Branch
1 11 3 user y y y y y n n none rest

100 Branch 1319
1 11 4 user y y y y y n n none rest
200 Branch 530
1 11 4 user y y y y y n n none rest
201 Branch 551
1 11 3 user y y y y y n n none both
251 Core - For Branch AC 551
1 11 3 user y y y y y n n none rest


ARS:
Location: all Percent Full: 3

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
3 7 7 p1 hnpa n
13 11 11 p2 fnpa n
1319 11 11 100 fnpa n
1319310 11 11 26 fnpa n
1319369 11 11 26 fnpa n
1319398 11 11 26 fnpa n
1319432 11 11 26 fnpa n
1319530 11 11 100 fnpa n
1319533 11 11 26 fnpa n
1319538 11 11 26 fnpa n
1319551 11 11 251 fnpa n


We can try adding as 2nd choice - but would rather get 1st choice working first - since we have no experience with setting up that way.
Will test changes to route patterns above again - but any further feedback is appreciated.

-SP

 
Thanks - was ARS that fixed it in the end. We have some Local area numbers that don't work if insert digits is not fixed - ex. add 1 or 1319.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top