Avaya Aura Communication Manager configuration

Last Updated : Jun 08, 2026 |

Communication Manager controls how long an incoming call alerts at a VoIP endpoint that uses SIP for call signaling. The time required to establish a call depends on various conditions, including the following:

  • Call setup latency through the push notification network.

  • Additional network connection steps required by iOS clients to present the incoming call notification to end users.

If you use the Apple Push Notification service in your deployment, you must change the default values of the following Communication Manager timers to provide Avaya Workplace Client for iOS users with sufficient time to answer the call. Otherwise, Communication Manager might drop the call or send it to coverage before the called party has a chance to answer the call.

Alternate route timer

By default, Communication Manager has a six second alternate router timer that expires when no 180 Ringing response is received from the called party. When the timer expires, Communication Manager drops the call. If you enable push notifications, increase this value of the Alternate Route Timer(sec) parameter to 10 seconds. This parameter is located in a Communication Manager SIP signaling group that is associated with the Session Manager instance used by mobile clients that are subscribed for push notifications.

Redirect on OPTIM Failure timer

The timer controls how long Communication Manager waits for a SIP 18x provisional response before canceling the call that was intended for an iOS client. The default value is 5,000 milliseconds. If you enable push notifications, increase this value to 10,000 milliseconds. The value is configured in the Redirect on OPTIM Failure field in a Communication Manager SIP trunk-group.

Coverage path number of ring cycles

This timer controls the number of ring cycles to alert the originally called party before directing them to the first coverage point in the coverage path. The exact duration of the wait time depends on the ring cycle length, which can be different in different countries. By default, Communication Manager waits for two ring cycles. In the Don't Answer field under Coverage Criteria, increase the Number of Rings to four ring cycles for the Coverage Paths that apply to users with Avaya Workplace Client running on an Apple device.

Note:
  • To avoid changing coverage behavior for users who do not use Avaya Workplace Client for iOS, you can create a new coverage path with the number of rings set to four cycles for Avaya Workplace Client for iOS users. For other users, keep the existing coverage path with the number of rings set to the default two cycles.

  • If an Avaya Workplace Client for iOS user already has a coverage path with the number of rings set to four cycles or higher, you do not need to edit this coverage path.

  • If a user has both a deskphone and Avaya Workplace Client for iOS, the higher number of rings applies to both endpoints. That is, an incoming call rings for four cycles on the deskphone even if Avaya Workplace Client for iOS is not logged in.

For more information about Communication Manager settings, see Administering Avaya Aura® Communication Manager.