Alternative Endpoint administration considerations and impacts

Last Updated : Jul 05, 2018 |
Prolog information
Metadata
Keywords:
The current method for administering non-SIP endpoints is to use either of the following:
  • System Manager to create a non-SIP endpoint without a SIP profile.
  • The Communication Manager SAT.
You must configure Session Manager to route calls to the correct Communication Manager.

Alternative method for administering endpoints

An alternative method for administering non-SIP, such as H.323 and analog, is to use System Manager to create a SIP profile for an non-SIP endpoint. URE routing will automatically route calls to the correct Communication Manager.
The alternative method:
  • Simplifies Session Manager routing configuration.
  • Allows non-SIP endpoints to have multiple SIP handles.
  • Provides Dual Registration (H.323 and SIP endpoints on the same extension) with no further System Manager configuration.
  • Provides an easy migration to a SIP endpoint by changing the endpoint type.

Use Case

A customer has H.323 endpoints with DID numbers scattered randomly among different Communication Manager servers. This arrangement makes it cumbersome to configure Session Manager routing to send calls for H.323 endpoints to correct Communication Manager.
The Customer uses the new technique to take advantage of URE routing in place of manually administering Session Manager routing policies.

Impact on capacities

Important:
This method assigns a SIP profile to an H.323 endpoint. Using this method reduces the total SIP endpoint capacity by the number of H.323 endpoints assigned a SIP profile.
For example, if you configure 200 H.323 stations using the alternative method, you reduce the maximum number of SIP devices by 200.