Reference12r2:PBX/Objects/Push: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
; URL: is configured automatically. | ; URL: is configured automatically. | ||
; Account: Usually the account to register at the push service is the PBX domain (Gatekeeper ID). This can be overridden by this value. If the account does not contain a '/' the complete account is formed by adding this value with '/' to the domain. If the account contains a '/' it is used as it is. | |||
; E-Mail: must be valid email address. Is used to send an activation link to. | ; E-Mail: must be valid email address. Is used to send an activation link to. | ||
= Related Articles = | = Related Articles = | ||
[[Reference12r2:Concept_Push_Notifications_for_myPBX_iOS_and_Android]] | [[Reference12r2:Concept_Push_Notifications_for_myPBX_iOS_and_Android]] | ||
Revision as of 19:28, 6 October 2020
With the Push PBX object the PBX can send notifications towards myPBX App on iOS or Android devices via the vendor Push Notification service.
General Configuration Options
- Long Name
- must be unique in the PBX.
- Name
- is used in the User object to identify the push service.
- Password
- is configured automatically while creating a connection to the push service. Leave empty.
Push Configuration Options
- URL
- is configured automatically.
- Account
- Usually the account to register at the push service is the PBX domain (Gatekeeper ID). This can be overridden by this value. If the account does not contain a '/' the complete account is formed by adding this value with '/' to the domain. If the account contains a '/' it is used as it is.
- must be valid email address. Is used to send an activation link to.
Related Articles
Reference12r2:Concept_Push_Notifications_for_myPBX_iOS_and_Android