Export (0) Print
Expand All

SIP Trunking Drilldown: Supported Topologies

Communications Server 2007 R2

Topic Last Modified: 2009-07-14

The interface for connecting Office Communications Server environment to the Session Initiation Protocol (SIP) trunk of the service provider is made on the external side of a Mediation Server. The following list contains the supported topologies that you can use to enable this connection to your service provider’s SIP trunk:

  • Private connection. In this configuration, the mediation server connects to the SIP trunk using a private network connection to the service provider. For instance, this could be a dedicated MPLS T1 connection installed for the purpose of SIP trunking.
    Ee323446.5eae2ed4-5d5b-4be7-b8ff-7debc2b02c23(en-us,office.13).gif

  • VPN connection. In this configuration, the mediation server connects to the SIP trunk using a virtual private network (VPN) connection to the service provider. This could run over a general Internet connection or an existing MPLS wide area network (WAN) connection. Unlike the private connection option, these multi-purpose connections are usually shared and used for multiple scenarios. The purpose for the VPN connection is to create an isolated, secure channel on which the SIP trunked calls are carried.
    Ee323446.89777c13-a528-4bfa-a28d-8091d05d4852(en-us,office.13).gif

  • Public Connection. In this configuration, the Mediation Server connects to the SIP trunk by using a direct Internet connection. Unlike the private and VPN options, this topology does not leverage an isolated link to the SIP trunk.
    Ee323446.42383f9c-2c0d-414a-b972-5931b31df7fc(en-us,office.13).gif

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft