Static Routing Cmdlets

 

Topic Last Modified: 2012-10-17

With static routes, administrators can predetermine the network routes taken by SIP messages. When a message is received by a server, the server checks the message address and then forwards the message to the next hop server preconfigured by an administrator. If configured correctly, static routes help ensure timely, and accurate, delivery of messages, and with minimal overheard placed on servers.

Static Routing Cmdlets

Unless otherwise instructed by Microsoft support personnel, static routes configured for Microsoft Lync Server 2010 should be created using the New-CsStaticRoute cmdlet. After a route has been created, you can then use the CsStaticRoutingConfiguration cmdlets to add that route to a static routing collection.

Static Routing

• 
  Get-CsSipResponseCodeTranslationRule

• 
  New-CsSipResponseCodeTranslationRule

• 
  Remove-CsSipResponseCodeTranslationRule

• 
  Set-CsSipResponseCodeTranslationRule

• 
  New-CsStaticRoute

• 
  Get-CsStaticRoutingConfiguration

• 
  New-CsStaticRoutingConfiguration

• 
  Remove-CsStaticRoutingConfiguration

• 
  Set-CsStaticRoutingConfiguration

• 
  New-CsSipProxyCustom

• 
  New-CsSipProxyRealm

• 
  New-CsSipProxyTCP

• 
  New-CsSipProxyTLS

• 
  New-CsSipProxyTransport

• 
  New-CsSipProxyUseDefault

• 
  New-CsSipProxyUseDefaultCert

• 
  New-CsIssuedCertId

For details about Lync Server Management Shell cmdlets, see the Lync Server Windows PowerShell blog at https://go.microsoft.com/fwlink/p/?LinkId=203150.