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

Creates an object reference to the default certificate used by Microsoft Communications Server “14”. This object reference can then be used configure a static route to use TLS (Transport Layer Security) as its transport protocol.




Parameter Required Type Description



Switch Parameter

Reports detailed activity to the screen as the cmdlet runs.

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. If you elect to use TLS (the recommended transport) you must also specify the Communications Server certificate to be used for authentication purposes. You can either obtain a certificate specifically for use on your static route, or you can configure TLS to use your default Communications Server certificate . If you decide to use the default certificate, you can create an object reference to that certificate by running New-CsSipProxyUseDefaultCert. In turn, that certificate object reference can be used by the New-CsSipProxyTLS cmdlet to configure TLS as the transport protocol.

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

Return Types

New-CsSipProxyUseDefaultCert creates new instances of the Microsoft.Rtc.Management.WriteableConfig.Settings.SipProxy.UseDefaultCert 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.