Required procedures before administering a Session Manager profile

Last Updated : Mar 04, 2021 |

About this task

Perform the following steps before administering a Session Manager profile.

Procedure

  1. To administer the primary Session Manager, add a SIP entity of type Session Manager with listen ports.
  2. Optional To administer the secondary, third, and fourth Session Manager for redundancy purposes, add a SIP entity of type Session Manager with listen ports.
  3. If you enable the Policy-based Assignment of Users to Session Managers feature, based on the policy type you want to administer, do one of the following:

    Policy type

    Requirements

    Fixed-region

    Create a region and assign Session Managers to the region on the Session Manager Groups page. See Adding a region.

    Location-region

  4. Add SIP domains.
  5. Administer Communication Manager as a Feature Server SIP entity.
  6. Administer the Communication Manager Feature Server as an application instance.
  7. Add the Communication Manager Feature Server as an application available for SIP Entities.
  8. Administer and add applications available for SIP Entities. Repeat as needed for each application:
    1. Create the SIP entity.
    2. Create a new element for the application.
    3. Add the application to the list of applications available for SIP Entities.
  9. Create an Application Sequence from the existing applications to specify the Origination Application Sequence and Termination Application Sequence. See Creating an Application Sequence.
  10. If you have conference products that support the Conference Factory feature, add Conference Factory Sets.
  11. To use a Branch Session Manager server as a Survivability Server, add SIP entities of type Session Manager and Branch Session Manager with listen ports.
  12. To modify the Home Location, configure values that are similar to Locations. To add a new value, add a Location.

    See Creating Locations.

    Note:

    Specify the Home Location to support user mobility. Session Manager profiles must be defined only for SIP endpoints. Assign SIP handles to all endpoints registered with Communication Manager.

  13. Synchronize Communication Manager station data and messaging data with System Manager:
    1. Administer each Communication Manager and Messaging application as an application instance.
    2. Synchronize Communication Manager and messaging data with the System Manager.