Reference12r2:Concept Push Notifications for myPBX iOS and Android: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
Line 8: Line 8:


=== myPBX for iOS or Android ===
=== myPBX for iOS or Android ===
* Version 12r2sr23 or higher
* iOS since Version 12r2sr20
* Androis since Version 12r2sr23


=== Smartphone ===
=== Smartphone ===

Revision as of 10:52, 18 April 2019

With firmware version 12r2 sr20 the PBX is able to send Push notifications to the Apple (APNs) or Android Push Notification services. As a result, incoming calls are also indicated when the myPBX app is not started or runs in the background mode. The PBX is using a service provided by innovaphone AG at services.innovaphone.com to send the push notifications to the vendors Notification Service. No call meta data is transmitted, the push notification is only used to wake up the myPBX app. Only one Push object is needed for a system.

Requirements

PBX

  • Firmware version 12r2sr20 [125501] or higher
  • Internet access via HTTPS

myPBX for iOS or Android

  • iOS since Version 12r2sr20
  • Androis since Version 12r2sr23

Smartphone

  • iOS Version 12.0.1 or higher
  • Android Version 6.0 or higher

Configuration

PBX

  • Check the System Name of the PBX - it must be globally unique. We recommend to use the DNS domain name of the company using the PBX.
  • For the next steps, do not use Internet Explorer, Edge or FrontMotion Firefox Browser at the moment. It will not work!
  • Create a new PBX object of type Push.
    • The Name of the Push object is case sensitive and will be used in the User objects to identify the push service.
    • Do NOT set a password - this is later-on filled-in automatically!
    • Make sure to click on OK or Apply button before proceeding with next steps.
  • Navigate to the Push tab of the Push object and provide a valid E-Mail address that can be used to send an HTTP link for verification.
    • E-Mail must not be an E-Mail already used as E-Mail of another object.
  • Press Connect button, do not close the window until E-Mail verification is done.
  • Wait for the E-Mail and open the verification link in the browser.
  • Press OK button after Connect succeeded appears.
  • Navigate to Reference9:General/Certificates and trust to certificate *.innovaphone.com that should appear on the list of rejected certificates. You have to do this on every slave and/or standby PBX.

Rejected certs.png

  • The trust list should look like this afterwards:

Trusted certs.png

User Objects

  • For each user who is to receive push notifications on his myPBX-application, the Name of the push-object must be entered in his userobject at the Push field in the User tab.

iOS specific settings

  • On the iOS device make sure to allow push notifications for the myPBX app.

Troubleshooting

  • Check the trust list for certificate of the innovaphone AG.
  • Make sure the PBX can resolve the DNS host services.innovaphone.com.
  • Make sure the PBX can reach services.innovaphone.com via HTTPS.
  • Make sure you do not use Internet Explorer or Edge.
  • Make sure the mail used for Push is not used by another PBX object.
  • If there are problems with setting up the Push Service or if individual subscribers can not be reached, open a Support Ticket.
  • Only if you are not sure if the push service is operational at the moment, open a support ticket and send an email to push-support@innovaphone.com.
  • Make sure the myPBX App has Push Notifications allowed in the OS settings.
    • iOS: Also make sure, the iOS device has a valid GSM data connection or a WiFi connection with the internet, especially TCP port 5223 (see Troubleshooting Push Notifications article by Apple).
  • Once a domain is already registered with an email address, this domain cannot be authenticated with another email address. In this case you will not receive any email from our push service.

Known limitations

Push object creation and configuration of the connection is not working with Internet Explorer/Edge.

Use Firefox or Chrome to create and configure the Push object.

Call accept time for users with myPBX client only

In case no other endpoints are registered on the User object, but only the myPBX client, the PBX will not provide any alerting message to the calling party, until the myPBX client on the device restores the registration to the PBX via push notification. In case no registration appears after 10 seconds, the PBX will send "no user responding" as cause code to the calling party.

Push is not working if no device registered and a CFNR is configured

In case no endpoints are registered on the User object, and there is also a CFNR configured. The Push will not be executed and as result the CFNR will be exectuted immediately.

This is a known limitation and is under investigation.

A temporary workarround which will fix this issue has been found.

Solution: Create a Forking on the users object to its own number !

Push will work and if the device is able to register within 10 seconds the myPBX app will ring and the CFNR will be executed with the configured timer.