Use of voice & Data on T1

Tags:
DataCenter
Routers
T-1/T-3 Services
I have a business with two sites geographically seperated but have just installed a T1 line and now need equipment to get everything to talk. I want to split the T1 to offer voice and Data. I have 8 computers on either side and plan on having a microsoft exchange server in one site. I use quickbooks that i need to access from wherever and also want to share other data like presentations. the quickbooks is on a laptop not server at present. I have a Comdial digital in one place & Toshiba in another. I want the phones to work as extensions-even though they have different codes. I have a limited budget since its a small business. whats the best way to go about this. Thanks folks...
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

I have a question,are both switches/key systems equipped to interface a T-1 circuit. Right off the bat you will need DSU/CSU or a router with a DSU/CSU blade to split the signal, allocating bandwidth for both voice and data. So initially you will need additional equipment. Also the two switches/key systems will need to exchange call processing information or appear as a node or opx (off prem extension) to one another in order to “talk” to one another. A protocol commonly used in this type of application is Q sig. There are workarounds but more information on the telephone systems is needed.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Engineer300
    I assume that the voice PBX's do not support Voip? I think that the cheapest way to do this would be to get a couple of routers that can emulate a T1 link over IP. The T1 link between the sites is then treated as an IP link, over which you can run both your data traffic as well as the emulated T1 traffic. The Voip technology in the routers only uses as much bandwidth as you need to support active voice calls. The routers will need 2 interfaces, a straight T1 interface for the data traffic, and a special channelised voice T1 for connecting to the local PBX. I suspect this will work better, and be less expensive than using T1 muxes. However it takes a bit of expertise to set this up. I guess another option would be to upgrade the PBX's to support Voip.
    0 pointsBadges:
    report
  • Mrhbear
    Depending on the level of integration you want with the key systems and the requirements on how you want this to work, even QSIG may not help. Both of the other comments have good points - Make sure you have detailed information on both systems and it may be easier to upgrade to a VoIP system that is better suited for handling multiple locations. We specialize in VoIP and even when you know what you're doing this can be tricky. Just make sure that even if the vendor of your phone systems say it can work, test it - they usually have a broad range of what's considered acceaptable as working.
    0 pointsBadges:
    report
  • Bmanzwfb
    It might be more difficult to get two different key switches to talk over a channellized T-1 than to standardize on a VoIP system for both your locations and use the T-1 for voice and data combined. We have delayed implementation of this very thing till we get the money to standardize on VoIP system at our remote locations.
    0 pointsBadges:
    report
  • Dkdoyle
    I know everyone is suggesting voip but that is expensive. You can split the T1 channels for some for voice and the others for data using the CSU/DSu's. You probably already know that. That will get your data up quickly. For the voice I would go to manufactures web page or better yet call them. As mentioned you may be able to use QSIG to get them to work but you may have to modify one or both systems. Best of luck.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: