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

T1 Multiplexing 1

Status
Not open for further replies.

alycera

Technical User
Jan 28, 2003
39
US
Hi Folks,

Looking to establish toll bypass to a third site. We have a Modular ICS with a PRI feeding the main office. Second slot has a T1 card (16 channels provisioned) headed to plant #1. We also have a full T1 (data only) to plant #2 that we can strip some channels for voice. Trouble is, no more T1 ports available at the main office.

Is it possible to get something from Adtran (or whoever) that will terminate both T1s, send data to two V.35s and (here's the catch) 12 channels of plant #1 voice and 12 channels of plant #2 voice over a single DSX1 and into the existing T1 card?

I assume if I can get the multiplex issue handled, the other issue is whether I can divide channels 1-12 and 13-24 into separate line pools to allow destination codes, routing, etc. to work properly.

If this is all impossible, any suggestions on other trunking methods (E&M or whatever) that would allow hitting an expansion slot other than the T1 slots?

Thanks in advance,

John
 
I got a spec from Adtran for a device (Atlas 550) that'll take both T's, send data channels to their own V.35s and then bundle the remaining channels over a single T1 interface for the Norstar. Since I'm likely going to split the incoming T1s in half, I'll end up with a T1 for the Modular ICS that has channels 1-12 from Site 1 and channels 13-24 from Site 2. I assume I can just assign them to separate line pools and run with it. Sound plausible?
 
Yep -- this one is a straight T1. The PRI is on the other card.

This is going to work WAY BETTER and chew up less channels than Plan B (I was considering adding a T1 card to the open slot in the Site #1 MICS and then daisy chaining to Site #3).

Thanks for your responses!
 
Hi alycera, when the straight T1 was broken down to data and voice/pri. Did you use dedicated maps on the Adtran Atlas 500 on both ends or were dial plans?

If possible, please post your configuration for the Atlas 550 as well as the MICS. I'm having trouble with getting the MCDN with PRI to work across two sites. Thanks!
 
Hi filo,

Just making things clear that the two T1s that were broken down were interoffice data and tie-line voice. The PRI is the other card on the main office MICS and is used to hit the PSTN for outside lines. We don't have a BCM. We used the Atlas as an outboard way to regroup the T1s (to avoid upgrading the MICS software and buying yet another T1 card). That being said, here's how it went down . . . (careful, this turned out to be pretty lengthy)

I used dedicated maps on the Atlas and it worked great. The Atlas has the integrated Network (T1) port plus a dual V.35 card and a dual T1/PRI card. I plugged the Norstar into the network port. I plugged each of the T1s from the remote sites into the dual T1/PRI card. The map sends the data channels from the remote sites to the V.35 ports and into a Cisco 1720 with a dual V.35 module. It also sends the voice channels from the remote sites to the network port and on to the Norstar.

Both remote locations use Adtran TSU 120s (with DSX1 ports). I used 12 channels from each remote location for data. This left 12 channels from each location for voice -- together they make a full T1 tie line. Perfect since I only had one T1 port available on the Norstar!

On the main office Norstar, I took tie lines 1-12 and put them in line pool C and tie lines 13-24 into line pool D. Then I used routing and destination codes to grab the extension number and send it out over the correct line pool.

I did struggle with a Norstar issue this past week though. Any help you can offer would be appreciated. We're doing voice fine from the office to the remote sites and back. However, when trying to dial from one remote site to the other (through the main MICS), I get a fast busy. I'm assuming the destination code and route thing needs a tel set at the next hop. Do you know a way to hop across an MICS in order to get to a third site? I'm attempting to dial the other remote site with a destination code that is actually a destination code on the main system. Again, either the main system can't pass it onto the other remote site or I missed something in the setup. Any ideas?

If you'd like the Atlas config, hit my email at jmeggers@alycera.com and I'll drop you a copy. I don't have a copy of the Norstar config though.

Also, if you're having troubles splitting a PRI, most of the troubles I've heard of deal with breaking out channels and not getting the associated signaling data broken out from channel 24. Don't know your situation, but there's a little food for thought!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top