Configuring call support for unregistered endpoints

Last Updated : Jan 28, 2020 |

About this task

Use this task to configure call support for unregistered endpoints. For example, unregistered endpoints might still require support in case of an emergency call or when someone is using a click to call feature.

Procedure

  1. Log in to the EMS web interface with administrator credentials.
  2. From the Device menu, click the SBC name to administer.
  3. Navigate to Configuration Profiles > URI Groups.
  4. In the application pane, click Add.

    The EMS server displays the Add URI window.

  5. In the Group Name field, type the name of the URI group.

    The group name must indicate that the URI group is for emergency calls from unregistered numbers.

    For example, in the Group Name field, type 911_Anonymous. If configuring a group for the click to call feature, type Click2Call.

  6. Click Next.
  7. In the URI Type field, click Plain.
  8. In the URI field, type anonymous@ucaas.

    This URI group is applied to a subscriber to allow unregistered Avaya SIP endpoints to dial an emergency number or use click to call.

  9. Click Finish.
  10. In the navigation pane, click Network & Flows > End Point Flows.

    In the content area, the EMS server displays an ordered list of call flows, Subscriber or Server, for the selected Avaya SBC security devices.

  11. Click the Subscriber Flows tab.
  12. Click Add.

    The EMS server displays the Add Flow window.

  13. In the Flow Name field, type the name of the endpoint flow.
  14. In the URI Group field, click the URI group that you created for emergency calls from unregistered SIP endpoints.
  15. In the Signaling Interface field, click the external interface for this Avaya SBC.
  16. Click Next.
  17. In the Source field, click Click To Call.
  18. In the Media Interface field, click the external interface for this Avaya SBC.
  19. In the End Point Policy Group field, click the policy for remote endpoints.
  20. In the Routing Profile field, click the routing profile that is mapped to the required Session Manager.
  21. Click Finish.