Administering global Session Manager settings

Last Updated : Mar 14, 2025 |

About this task

Use this procedure to administer the global settings of all the configured Session Manager instances.

Procedure

  1. On the System Manager web console, click Elements > Session Manager > Global Settings.
  2. Select the following:

  • Failback Policy to specify manual and scheduled failback support for terminals.

  • Allow Unauthenticated Emergency Calls to allow unauthenticated users to make emergency calls based on the dial pattern.

  • Allow Unsecured PPM Traffic to allow PPM traffic over HTTP to process phone login and download button labels, contact lists, and other services.

  • ELIN SIP Entity to specify the ELIN server for E911 services.

  • Better Matching Dial Pattern or Range in Location ALL Overrides Match in Originator's Location to specify how to route the call based on the Dial Pattern settings.

  • Ignore SDP for Call Admission Control to specify whether Call Admission Control (CAC) uses Session Description Protocol (SDP) in SIP messages to determine the bandwidth used by a call.

  • Disable Call Admission Control Threshold Alarms to disable the alarms generated when the system crosses the alarm thresholds of CAC.

  • Disable Loop Detection Alarms to disable the generation of loop detection alarms.

  1. In the Loop Detection Alarms Threshold (hours) field, type the interval after which an alarm must be generated when the system detects a loop detection error.

    This field is inactive when the Disable Loop Detection Alarms check box is selected.

  2. In the Load Factor Alarm Threshold (80 - 150) field, type the threshold value, after which an alarm must be generated when a Session Manager or Branch Session Manager profile exceeds its defined load factor.

    The default value is 100. The allowed range is between 80 and 150.

  3. Select the Enable Dial Plan Ranges check box to specify dial plan ranges on the Dial Pattern Details page.
    Warning:

    Before you specify a dial plan range, ensure that all Session Manager instances and Branch Session Manager instances are running on software release 6.3.4 or later.

  4. Select the Enable Regular Expression Adaptation check box to enable regular expression adaptations.

    To enable the Regular Expression Adaptation feature, ensure that all Session Manager and Branch Session Manager instances are running on software release 8.0.1 or later.

  5. Select the Enable Device Adaptations check box to enable or disable device adaptations.

    By default, this field is disabled.

    To enable the Device Adaptations feature, ensure that all Session Manager and Branch Session Manager instances are running on software release 8.1.2 or later.

    Note:

    Once enabled, you cannot disable device adaptations until you remove all device mappings and adaptations of the type device.

  6. Select the Enable Flexible Routing check box to enable flexible routing.

    To enable the Flexible Routing feature, ensure that all Session Manager and Branch Session Manager instances are running on software release 8.0.1 or later.

  7. In the Set Precedence for Routing field, select the precedence for routing from the following:

    • Dial Pattern

    • Regular Expressions

    This field displays when the Enable Flexible Routing check box is enabled.

  8. In the Set Dial Patterns Precedence field, set the required precedence order for dial patterns.

    This field displays when the Enable Flexible Routing check box is enabled and the precedence for routing is set to Dial Pattern.

  9. Do the following to enable forward proxy configuration:
    Important:

    From R10.2.1.1 and later, Avaya recommends using the HTTP Proxy Configuration page instead of the Global Settings Page to configure the HTTP proxies. Configuration values from the HTTP Proxy Configuration page override the values of the Global Settings page.

    1. In the HTTPS Proxy Host field, type the proxy host address.
    2. In HTTPS Proxy Port, type the proxy port number.

      • It is mandatory to configure both HTTPS Proxy Host and HTTPS Proxy Port simultaneously.

  10. Select the Enable IPv6 check box to enable IPv6 support.
  11. In the Minimum SIP Entity TLS Version field, click the minimum allowed TLS version for the SIP entity.
  12. In the Minimum Endpoint TLS Version field, click the minimum allowed TLS version for endpoints.
  13. In the TLS Endpoint Certificate Validation field, click the option to validate an endpoint certificate when the connection type is TLS (outbound SIP connection to the endpoint).

    The options are:

    • None: No mutual authentication occurs because there is no certificate validation.

    • Optional: Communication occurs irrespective of whether the endpoint presents a valid certificate.

    • Required: Communication occurs if the endpoint presents a valid certificate trusted by Session Manager.

    This setting applies to all Session Manager and Branch Session Manager instances in the managed network.

  14. Select Enable End to End Secure Call Indication to activate the icon indicating to an end-user that signaling and the media are end-to-end secure.
  15. Do the following to enable the features for military deployments:
    1. Select Enable Military Support.
    2. In MLPP Network Domain(s), type the network domain names for Session Manager to prioritize calls within the domains.

      To enter multiple network domain names, separate the domain names with a comma. For instance, uc, dsn.

  16. Select Enable Application Sequence for Emergency Calls to enable application sequencing for emergency calls.
  17. In the Emergency Call Resource-Priority Headers field, type the resource priority header value to define an emergency call.

    You can enter multiple values separated by commas.

  18. To start implicit application sequencing, select Enable Implicit Users Applications for SIP users.
    Note:

    This setting is not applicable for Session Manager releases earlier than 6.3.8.

  19. To enable SIP Resiliency, select the Enable SIP Resiliency check box.
  20. Select Enable Policy Based Assignment of Session Managers for automated assignment of Session Managers to a user's communication profile based on a defined policy.
  21. To enable the Branch Visiting User survivability feature, see Enabling Branch Visiting User survivability procedure.
  22. To enable mobile push notifications, see Enabling mobile push notifications procedure.
  23. In the Notification EC500 delay (secs) field, set the number of seconds by which Communication Manager delays the extension of incoming call notification from VoIP to the cellular network for a SIP user. Communication Manager delays the extension for SIP users provisioned with EC500.

    You can set the number of seconds between 4–10. This field appears when the Enable Mobile Push Notification check box is selected, and the EC500 feature is enabled in Communication Manager.

    Note:

    Any value higher than 10 seconds may interfere with coverage features of Communication Manager, and any value less than 4 seconds results in Communication Manager prematurely extending an incoming call to a cellular network.

  24. In the Log Retention (days) field, type the number of days for which logs are retained.

    The default number of days is 30. You can set the number of days between 1-180.

    Warning:

    A retention period of fewer than 30 days might prevent Avaya Services from troubleshooting or diagnosing some problems.

  25. In the Centralized Call History Retention (days) field, type the number of days for which centralized call history is retained.
    Note:

    The default number of days is 90. You can set the number of days between 1-180.

  26. In Stir/Shaken Ingress Normalization, select the option to set the message normalization for the inbound messages.

    The options are:

    • Transparent: This is the default option. Session Manager does not perform any action on the messages.

    • Normalize: Session Manager formats the Attestation-Info header and verstat parameter in the P-Asserted-Identity and From headers before routing the inbound messages.

    • Remove: Session Manager removes the information, such as, Attestation-Info header and verstat parameter in the P-Asserted-Identity and From headers before routing the inbound messages.

    To change the setting to Normalize or Remove, all the Session Manager and Branch Session Manager instances must be on Release 10.2 or later.

  27. Select the Enable Edge Topology check box to enable edge topology for core Session Manager and edge Branch Session Manager.

    By default, this field is disabled.

    You can enable the edge topology feature to the core Session Manager and edge Branch Session Manager instances running on Release 10.2 or later.

  28. Click Commit.
Related information
Global Settings page field descriptions