[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Creates a new SipProxy.TLS object, which can then be used configure a static route to use TLS (Transport Layer Security) as its transport protocol.


New-CsSipProxyTLS -Certificate <ITLSTLSChoice> -Fqdn <String>


Parameter Required Type Description



X.509 certificate object

Certificate to be used for TLS authentication.




Fully qualified domain name of the next hop server. For example: -Fqdn atl-proxy-001.litwareinc.com.

Detailed Description

When you send a SIP (Session Initiation Protocol) message to someone that message might need to traverse multiple subnets and networks before it is delivered; the path traveled by the message is often referred to as a route. In networking, there are two types of routes: dynamic and static. With dynamic routing, servers use algorithms to determine the next location (the next hop) where a message should be forwarded. With static routing, message paths are predetermined by system administrators. When a message is received by a server, the server checks the message address and then forwards the message to the next hop server that has been preconfigured by an administrator. If configured correctly, static routes help ensure timely, and accurate, delivery of messages, and with minimal overheard placed on servers. The downside to static routes? Messages are not dynamically rerouted in the event of a network failure.

Microsoft Communications Server “14” enables you to set up static routes for proxy servers. These routes are composed of two primary pieces: proxy configuration settings (created using New-CsProxyConfiguration), and SIP proxy routes. In turn, SIP proxy routes have a number of properties; for example, each route must have a Transport, a property that defines the network protocol used for transmitting messages along the route.

Microsoft Communications Server allows you to specify either TCP (Transmission Control Protocol) or TLS (Transport Layer Security) as your transport protocol. If you decide to use TLS as your protocol, you must first create a TLS object using the New-CsSipProxyTLS cmdlet. You can then use that object to specify the protocol for the Transport object created by New-CsSipProxyTransport.

Note that you must also specify a certificate (to be used for authentication purposes) if you choose to use TLS as your transport protocol.

The New-CsSipProxyTLS cmdlet is not required if you use New-CsStaticRoute to create your static route.

Return Types

New-CsSipProxyTLS creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.SipProxy.TLS object.


Add code example

Copy Code
$cert = New-CsSipProxyUseDefaultCert

$tls = New-CsSipProxyTLS -Certificate $cert -Fqdn atl-proxy-001.litwareinc.com

$transport = New-CsSipProxyTransport -TransportChoice $tls -Port 7500

The commands shown in Example 1 create a new SIP proxy transport object that uses TLS as its transport. Because TLS requires a certificate (to be used for authentication purposes), the first command in the example uses New-CsSipProxyUseDefaultCert to configure a new SipProxy.UseDefaultCert. This object, stored in a variable named $cert, instructs Communications Server to use the default certificate for the TLS transport. After the UseDefaultCert object has been created, New-CsSipProxyTLS can be called to create a new SipProxy.TLS object, one that uses the default certificate and that points to atl-proxy-001.litwareinc.com as the fully qualified domain name of the next hop server.

As soon as the TLS object exists that object (and the TLS protocol) can be added to a Transport object, an object created by calling New-CsSipProxyTransport.