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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linking 2 ICSs via PRI 1

Status
Not open for further replies.

VEASEL

Vendor
Jan 28, 2002
15
0
0
US
We have a situation where 2 sights are connected via
a T1 now. We want to change to PRI so we get more
info to the remote sight. We activated PRI enabler
code at each sight and tried switching but they
didn't seem to connect. whenever you try calling
across it says "no Free lines".
In programming on the main side it says 24 lines
on the remote sight it says 1 loop. We didn't
make any progress so for the shortterm we went back
to T1. Am I missing something?
Thanks,
Randy
 
What Rls of Software has each site got? While I have not ever done what you are trying to do, precisely, it is my understanding that Rls 5.0 includes a new feature to make your kind of situation easier to impliment.
 
you need 2ea DTI cards in the host in order to complete this. One for the point to point connection and the other for the PRI. Jeter@LasVegas.com
Fisher CCNA
Sprint-Data
 
We did a site to site setup when I took the ICS class and I kept my notes on it. Here is a step by step on a PRI System to system setup (1: is first site and 2: is second site)
A Headings - software keys, Maint and Hardware
1 enter software keys
2. disaable module
3. change card to pri
4 look at card (pri card, lines 1-23)
5 select protocol - SL1
6 select type (1:slave 2:master)
7 select b chan sequence (1: ascending 2:descending)
8. select CO fail - TIA547A
9. Select IF Levels - ISDN
(the following may have some changes per your T-1 paramaters of your circuit)
10. Select Framing - ESF
11. Select internal CSU (on/off)
12. select CSU Build out (0)
13. Select Line Coding _ B8zs
14. Select Clocking source - (1:timing master 2:primary)
NOTE: if you select protocol as slave you must select Clocking source as primary
Note: If you select Protocol as Master you must select clocking source as timing master
B. Headingfs - Services, Routing services, Routes
1. Route - select 001
2. dial out number - select none
3. use - select PRI - A
4. DN Type - select private
C. Headings - Services, Routing services, dest codes
1. None defined add dest codes for remote sites (1, 2, 3, etc.)
2. Normal - seleclt route 001
3. absorb length - select 0
D. Headings - Terminals and sets
1. Line pool access - select line pool PRI-A
2. Line access - assign target line to set
E. Headings - Terminals and sets. Line access, OLI
1. Enter set DN #
F. Headings - lines
1. Trunk line data - line type - select public
2. Rec'd # - select DN # (if assigning target line to DN 221 this would then be 221)
3. If busy - select to prime
4. Prime set - select 1st dn on system (receptionist)
5. CLID Set - select DN # (set 221 in above ref)
G. Headings - system programming, Bus name
1. Enter business name
2. Release reasons - select text: detailed
NOTE after looking this over it seems that you should endable the module since you disabled it way back in step 2

Jerry Reeve

Ps: forgive the typo's
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top