Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have:

  • a patch panel with 24 ports.
  • Windows server
  • voip connection (voice over ip)

How do I make the connection from the patch panel to the router?

Do I need a router? If yes does it need to have certain features?

What exactly do I have to install on the windows server to make voip work?

What do I need to install on the clients to make everything work (something open source)?

Any other advice would be most appreciated. I am a newbie with this, please help.


They didn't give me any specifications of what software or hardware to use, I have to figure it out by myself, this is why I'm asking for help.

I am presuming my provider handles sip. Internal users are going to use soft phones. My telephone system will just need to be calling in/out.

It's really stupid that my question got closed. I just needed advice on how and what should I do from people with experience not from frustrated people who have nothing to do with the subject.


locked by Chopper3 Jul 28 '11 at 15:59

closed as not a real question by Iain, pauska, ThatGraemeGuy, Maxwell, user48838 Jul 28 '11 at 12:40

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Sorry, this is WAY overbroad for a single question. You need to call someone to help you with this. – pauska Jul 28 '11 at 12:13
You're not qualified to undertake this kind of project without one of the following things happening. 1) Early death. 2) Being murdered by the client. 3) getting a completely useless and unmaintainable end result. Quick answer. Don't Do It. Find a contractor who can do it all for you, and pay them to do it. – Tom O'Connor Jul 28 '11 at 12:14
How exactly did you get this project? Are you an employee of the company or are you a contractor? – joeqwerty Jul 28 '11 at 12:32
@joeqwerty - My guess is, Lowest Bidder. – Tom O'Connor Jul 28 '11 at 12:38
Some friend of a friend wanted to open a call center and I offered to look into the problem and help, this was my starting place. – Andrei Cristian Prodan Jul 28 '11 at 13:05
up vote 0 down vote accepted

You need to commute packets so you need a switch, you need to handle voip so your switch will need to handle Qos, you also need to acess the outside so you need a router. If you need to implement a IPBX then asterix may be your weapon of choice. You're question is too broad to answer correctly. Maybe you 'll better bet on contacting a contractor for that.

"commute packets"? -- What about "Switch" packets. – Tom O'Connor Jul 28 '11 at 13:01
Ooops! maybe my french to english translation was not that good after all. – Maxwell Jul 28 '11 at 15:38
  • let others do it.
  • if you want to get a reasonable answer i suggest you add [much] more details - eg:
    • what voip protocol does your service provider handle [probably sip, but it's worth checking]
    • are your internal users going to use soft or hard-phones
    • what features should the telephone system offer - just calling in/out? call groups? auditing/recording? ivr?

open source voip for windows sounds experimental - you might consider using linux and asterisk or freeswitch under it. there are few commercial voip platforms for windows - 3cx is one of them.

As far as hardware ... if you're connecting a network, your patch panel needs to be connected to a switch. If you're going send/receive calls outside your network, you'll need a router. As far as the rest ... this is a big question. What have you researched so far? I agree with pQd ... to my knowledge asterisk is one of the most common PBX systems in the world, it might be worth looking into. At the same time, a live business server is probably not the place to be learning linux if you don't know it. – Daniel B. Jul 28 '11 at 12:17
This has to be done on a windows server. Also thanks plenty, this really helped! – Andrei Cristian Prodan Jul 28 '11 at 13:03
Yes, I second this. As the systems administrator for a VoIP provider, I can definitely tell you that without the knowledge you'd need to answer the easy networking questions, you'll be hopelessly lost when tackling Asterisk. Give up now and find someone who has past experience doing this. – Ernie Jul 28 '11 at 15:47

Not the answer you're looking for? Browse other questions tagged or ask your own question.