Creating SIP Entities

Last Updated : Aug 11, 2023 |
Prolog information
Metadata
Keywords:
Before you begin
To create SIP entities for the edge Branch Session Manager setup, enable the Enable Edge Topology check box on the Global Settings page.
  1. On the System Manager web console, click ElementsRouting SIP Entities.
  2. Click New.
  3. In the General section, do the following:
    1. In Name, type the name of the SIP entity.
    2. In IP Address Family, click the address types that the SIP entity supports. For more information see IP address family validations.
      ADDITIONAL INFORMATION:
      For administering SIP entities by using IPv6 address, ensure that on the Global Settings page, the Enable IPv6 check box is selected. If IPv6 is not enabled, the IPv6 and Both options are not available.
      Depending on the IP Address Family that you select, the system displays:
      • For IPv4 IP address family: FQDN or IPv4 Address field.
      • For IPv6 IP address family: FQDN or IPv6 Address field.
      • For Both address family: FQDN or IPv4 Address and FQDN or IPv6 Address fields.
        For SIP entities other than Session Manager, if the FQDNs for IPv4 and IPv6 are separate, specify both fields with the corresponding IPv4 and IPv6 FQDNs.
        If one FQDN resolves to IPv4 and IPv6 addresses, fill the FQDN or IPv4 Address field. You can leave the FQDN or IPv6 Address field blank.
        For Session Manager SIP entities, specify only IP addresses.
      Session Manager supports a mixture of FQDN and IPv6 addresses for SIP entities other than Session Manager.
    3. In the FQDN or IP4 Address or FQDN or IP6 Address fields, type the FQDN or IP address of the SIP entity.
    4. In Type, click Session Manager as the type of SIP entity.
    5. In Network Topology, select one of the following:
      ADDITIONAL INFORMATION:
      If Enable Edge Topology is enabled on the Global Settings page and SIP Entity is of type Session Manager, SIP Trunk, Other, or Service Provider, Session Manager displays the Network Topology field.
      If SIP Entity is of type Session Manager, Session Manager displays the following options:
      • Enterprise: Specifies the entity is part of the enterprise or core network. This is the default value.
      • Edge Core: Specifies the entity is part of the enterprise or core network and also has an interface to establish connections with Edge Branch SIP entities using Session Border Controller. When you select Edge Core, Session Manager displays the SBC Public IP Address or FQDN field.
      • Edge Branch: Identifies the entity is part of a branch or private network and also has an interface to establish connections with Edge Core SIP entities using Session Border Controller. When you select Edge Branch, Session Manager displays the SBC Private IP Address or FQDN field.
      If SIP Entity is of type SIP Trunk, Other, or Service Provider, Session Manager displays the following options:
      • Enterprise: Specifies the entity is part of the enterprise or core network. This is the default value.
      • Branch: Specifies the entity is part of a branch or private network. A Branch topology SIP entity can only be directly connected to a Branch Session Manager instance and not to any core Session Manager instance.
    6. In SBC Public IP Address or FQDN, type the public IP address or public FQDN of Session Border Controller.
    7. In SBC Private IP Address or FQDN, type the private IP address or private FQDN of Session Border Controller.
    8. In Notes, type information about the SIP entity.
    9. In Location, select a location.
    10. In Outbound Proxy, select a proxy. For Session Manager, you can specify an Outbound Proxy, if required.
    11. In Time Zone, select the default time zone for the SIP entity.
    12. In Minimum TLS Version, select the required TLS version to configure.
      ADDITIONAL INFORMATION:
      Use this field to set the minimum allowed TLS version to a different setting other than the global setting for this SIP entity.
    13. In Credential name, type a regular expression string.
      For example: To use www.sipentity.domain.com, type the string www\.sipentity\.domain\.com.
  4. For a non-Session Manager SIP Entity type, click the appropriate mode in Loop Detection Mode.
    ADDITIONAL INFORMATION:
    By default, Loop Detection Mode is On.
  5. In SIP Link Monitoring, click one of the following:
    • Use Session Manager Configuration
    • Link Monitoring Enabled
      • In Proactive Monitoring Interval (in seconds), type the time. The range is from 1 through 9000 seconds and the default value is 900.
      • In Reactive Monitoring Interval (in seconds), type the time. The range is from1 through 900 seconds and the default value is 120.
      • In the Number of Tries field, type a number. The range is from 0 through 15 and the default value is 1.
    • Link Monitoring Disabled
  6. To specify the Entity Links:
    1. Click Add.
    2. In Name, type the name.
    3. In SIP Entity 1, click the required Session Manager SIP Entity.
      ADDITIONAL INFORMATION:
      SIP Entity 1 must always be a Session Manager instance.
    4. In IP Address Family, click the address types that the SIP entity supports.
    5. In Protocol, select the appropriate protocol.
    6. In Port, type the required port.
    7. In SIP Entity 2, click the required non-Session Manager SIP Entity.
    8. In Port, type the required port.
      ADDITIONAL INFORMATION:
      This is the port on which you have configured the remote entity to receive requests for the specified transport protocol.
    9. In Connection Policy, click the appropriate policy.
      ADDITIONAL INFORMATION:
      Session Manager does not accept SIP connection requests or SIP packets from untrusted SIP entities.
    10. Click Deny New Service to deny service for the associated entity link.
  7. In Failover, add ports if the SIP entity is a failover group member.
    ADDITIONAL INFORMATION:
    This step is applicable only for Session Manager SIP entity type.
  8. To specify the Port parameters:
    1. Click Add in the Port section.
    2. Enter the necessary port and protocol parameters.
    3. To remove an incorrectly added port, select the respective Port and click Remove.
  9. For OPTIONS requests, in Response Code & Reason Phrase, add or remove a SIP code and phrase to mark the SIP entity as up or down, respectively.
  10. Click Commit.