Telephony

Last Updated : Aug 29, 2026 |
Prolog information
Use the standard Avaya Aura® Communication Manager and Avaya Aura® Session Manager configuration to enable audio and video calls in Avaya Workplace Client. You do not need to configure any other components, but you must obtain licenses for video.
Note:
The phone number that you dial must have a minimum of 10 digits.
If there are multiple soft clients, the user can choose the default soft client for telephone services. Alternatively, if you want the user to use Avaya Workplace Client for Windows as the default application for telephone services, you can use Group Policy to perform the necessary configuration. For more information about using Group Policy, see Microsoft help documentation.

Emergency calls

Do not use Avaya Workplace Client on Android or iOS to make emergency calls as you cannot rely on the use of the mobile device for location information. Avaya recommends that you check the product documentation that accompanies your mobile device to learn about the emergency calling features available on your device.
Note:
Avaya Workplace Client starts a call by using the cellular network if the following conditions are met:
  • The value of the CELLULAR_DIRECT_ENABLED parameter is set to 1.
  • The dialed number matches any number specified in the CELLULAR_DIRECT_NUMBER_LIST parameter.
For example, if you set the value of the CELLULAR_DIRECT_ENABLED parameter to 1 and if the user dials 911, which you specify in CELLULAR_DIRECT_NUMBER_LIST, Avaya Workplace Client starts the call by using the cellular network. You cannot use these configuration parameters for mobile devices without cellular radio capabilities. For example, iPad.
Important:
You can use Avaya Workplace Client on Avaya Vantage™ to make emergency calls. For more information, see Emergency calls.
To make emergency calls on Windows and Mac using HELD and LLDP, Avaya Workplace Client uses the following components:
  • HTTP Enabled Location Delivery (HELD) server: Facilitates communication between the client and the LIS.
  • Location Information Server (LIS): Determines the location of the client.
  • Presence Information Data Format – Location Object (PIDF-Lo): It is an XML-based format used to encode location information of the client, within the SIP message.
LIS determines the client's location from the network and provides the location with the civic address details to the client in the PIDF-Lo format. Based on the network mode, LIS uses the following methods:
  • Ethernet network: LIS uses LLDP and Chassis ID to determine the client location. The client must have LLDP enabled and the network must support LLDP packets.
    Note:
    MacOS does not provide API to capture LLDP data without root access. You must install a separate daemon that runs with root access in the background and captures the LLDP data, and the client can then retrieve this data from the daemon. For more information, see Installing LLDP daemon on MacOS
  • Wi-Fi network: The LIS uses Basic Service Set Identifier (BSSID) to determine the location of the client.
To configure the emergency call location service feature:
  • Ensure the client connects to a HELD server.
  • Verify that the LIS is set up to use LLDP for Ethernet networks and BSSID for Wi-Fi networks.
  • Confirm that the PIDF-Lo data is correctly formatted and includes all the required civic address details.
When configured, the client includes the PIDF-Lo data in the SIP message for all emergency calls, ensuring accurate location information is sent to emergency service providers.