locked
Lync Server Enterprise Voice: SIP Trunk or PRI RRS feed

  • Question

  • We are considering changing our PBX to Lync Enterprise Voice. Which will give better service: a PRI or a SIP Trunk? We are looking to change ISPs increase our bandwidth to 100MB. How well will a SIP Trunk work with that bandwidth when it comes to QoS? Is it better to put the Voice on a separate circuit?

    Vincent McCaskill MCT, MCITP, MCTS, MCSA

    Thursday, June 7, 2012 4:22 PM

Answers

  • As you can imagine, it's very difficult to provide a single "correct" answer to this question as everyone's situation is different.  SIP trunking can be done over the internet or through private circuits so depending on which method you choose your cost, quality, and reliability could be very different.  Regardless of the connectivity method I like SIP trunks because they are far more flexible - from the numbers you can assign to them to how an outage is handled to the features you can get.  If I were deploying an environment with small to medium call volume needs where telephony service was not a business critical function (i.e. a call center) I'd get a good SLA-backed (in terms of circuit availability) internet connection from a reputable carrier and run the calls over that.  If I had a business with very large call volumes then I'd probably get SIP service from one of the big carriers and run dedicated circuits to them.

    I'm sure others will have additional/different opinions.


    Mike Stacy | http://mikestacy.typepad.com


    • Edited by .Mike Stacy Thursday, June 7, 2012 5:57 PM
    • Proposed as answer by Lisa.zheng Friday, June 8, 2012 7:15 AM
    • Marked as answer by Noya Lau Thursday, June 21, 2012 10:17 AM
    Thursday, June 7, 2012 5:57 PM

All replies

  • As you can imagine, it's very difficult to provide a single "correct" answer to this question as everyone's situation is different.  SIP trunking can be done over the internet or through private circuits so depending on which method you choose your cost, quality, and reliability could be very different.  Regardless of the connectivity method I like SIP trunks because they are far more flexible - from the numbers you can assign to them to how an outage is handled to the features you can get.  If I were deploying an environment with small to medium call volume needs where telephony service was not a business critical function (i.e. a call center) I'd get a good SLA-backed (in terms of circuit availability) internet connection from a reputable carrier and run the calls over that.  If I had a business with very large call volumes then I'd probably get SIP service from one of the big carriers and run dedicated circuits to them.

    I'm sure others will have additional/different opinions.


    Mike Stacy | http://mikestacy.typepad.com


    • Edited by .Mike Stacy Thursday, June 7, 2012 5:57 PM
    • Proposed as answer by Lisa.zheng Friday, June 8, 2012 7:15 AM
    • Marked as answer by Noya Lau Thursday, June 21, 2012 10:17 AM
    Thursday, June 7, 2012 5:57 PM
  • If you read this page carefully, you can find the answer to your question.

    http://www.ozekiphone.com/what-is-sip-trunking-session-initiation-protocol-trunking-314.html

    This system perfectly deal with calls, I did not encounter with problems while I used the service.

    Thursday, October 4, 2012 12:11 PM