If your interested in using the push staging server to test upcoming releases you will need to change the pushServerUrl attribute to point to our push staging server:
https://push-staging.softphone.com/push
Since the staging server is not an official release, we do not recommend moving all of your users to the server. Instead, you should select a number of users for testing and switch them to the staging server in one of the following ways:
For Bria Enterprise Users:
Please open a ticket in the Technical Assistance Center (TAC) to request a configuration change for your selected users. In your ticket, please provide the full provisioning username of your user(s).
Our team will configure the push staging url and let you know when it has been completed and close out the ticket.
You can reach out to us at pushservice@alianza.com with any feedback from your testing.
For Branded Customers
1. Modify user level attributes
If you're planning on creating new users specifically for testing against the staging server, you can override their pushServerUrl attribute by setting its value at the user level.
- Select the user you want to change and search for the pushServerUrl attribute:
- Edit and change the value to: https://push-staging.softphone.com/push
These users will now be configured to use the push staging server. If you want to move these users back to the production URL, simply edit them again and remove the user level value. It will be replaced with the inherited URL: https://push.softphone.com/push.
2. Create a new profile
If you want to have more flexibility over which users have access to the staging server, you can create a new profile to be used specifically for testing on the staging server.
- Create the profile by copying an existing profile. Change it's name to designate it as your test profile.
-
Next, change the pushServerUrl attribute in the new testing profile.
NOTE: make sure the new profile has Android and iOS template mappings in the template mappings section of the profile. If the profile you were copying from was using inherited templates, you may need to add the templates manually to the new profile.
- Now, you can move users back and forth between the staging and production servers by changing their assigned profile
Verification
You can confirm that your test users are using the staging server by checking the provisioning test output for a user. The pushServerUrl setting should be pointed to the correct server:
Branded Customers: If you see an error, "Access not allowed for this softphone platform", this means your new profile is missing a template mapping for the platform you are trying to test. See the note in step 2 above.
You should now have users configured to test against the push-staging server. Please reach out to us at pushservice@alianza.com to provide us with feedback from your testing.