Apple Push Notification service (APNs) is a platform notification service created by Apple Inc. This service allows iOS users of Avaya Workplace Client for iOS to receive notification of new calls, voicemail messages, and other events. They receive these notifications regardless when the Avaya Workplace Client for iOS is idle in the background or is in quit state. However, if Avaya Workplace Client for iOS is on suspension, then Avaya Workplace Client for iOS automatically starts when a new call or instant message notification arrives.
Apple Push Notification service (APNs) works only on TLS transport type.
The iOS device sends notifications via an intermediate push notifications server provided by Avaya.
IP Office supports push notification with Avaya Workplace Client for iOS R3.8 and later.
On receiving a new call notification, and while Avaya Workplace Client for iOS is on suspension, it takes up to six seconds before the Avaya Workplace Client for iOS becomes active, and you can answer the call. The exact delay depends on the version of iOS and the device used. Therefore, the No Answer Time setting time is increased to more than 20 seconds to allow the calls to ring before going to voicemail or following the divert on no answer settings.
APNs service supports only a single iOS device per user. If the you use Avaya Workplace Client for iOS on two devices, for example, an iPad and an iPhone, only the last client to register will receive notifications.
While using iOS push notifications, always configure and enable voicemail or an alternate call destination number. When Avaya Workplace Client for iOS is not reachable, the No Answer Time setting triggers and the push notifications to a voicemail or a forward on no answer number.
Setting your iOS device with a GSM telephone number as your mobile twinning, and setting the Mobile Dial Delay (sec) to more than 10 seconds, allows the time for the call notification to be answered on a previously suspended client before it alerts the GSM call.
Note:
In IP Office,while using iOS push notifications, if you were using a secured port in the primary server, use the same secured port as a preferred port in secondary server. Any mismatch in the secured port configuration is not valid.