CounterPath Hosted Bria Push Checklist for Stretto SAAS

Using the Bria Push Service with Bria Stretto is easy - most users will only need the "Account1Sip.briaPush.enabled" setting to be provisioned as true. 

To be sure that Push will work, consult the following checklist:

Your Device

1. The mobile device must have public Internet access to Apple's APNS and Google's FCM push notification systems.
   • If the mobile device is running inside a restricted network, please follow instructions from Apple and Google from the following links, respectively:
     

     iOS Device (Apple APNS): https://support.apple.com/en-us/HT203609 
     Android Device (Google FCM): https://developers.google.com/cloud-messaging/http

2. The mobile device must have public Internet access to CounterPath's Push Servers. See the Address List for details.

Your Server

Make sure that your server meets the following criteria. If you're not sure, contact your Server Administrator or SIP Service Provider to inquire if they meet the following:

1. The SIP server must allow registration from the Bria Push Server. If the SIP server is running inside a restricted network of an organization, the organization must provide access to the Bria Push Server and set the "SIP Proxy" parameter. See the Address List for details.
2. For best interoperability, the SIP server should map SIP Address-Of-Record to Contact URI. The Bria Push Server will generate a unique Contact URI for each SIP account, on a per device basis, to route incoming calls. As such, the SIP server must set the Request-URI of the INVITE message to be sent to the Bria Push Server, to be the same value as the Contact header as specified by the Bria Push Server in the REGISTER message. Otherwise, the Bria Push Server will run heuristics to identify the unique SIP account, and if no unique SIP account is determined, push notifications for incoming calls will not be sent.†
3. For the best user experience, the SIP server should support multiple simultaneous registrations for each SIP account. If available, the Bria Push Service can register with the SIP server in parallel with the Bria mobile client app. If not available, the "account1Sip.briaPushSingleRegistration" attribute can be enabled. Note that using the single registration option may cause a momentary pause in service when the Bria mobile client app transitions between background and foreground states.†
4. If SIP service implements server managed NAT traversal or follows industry best practice where SIP server sends responses to the originating IP address and port, the "account1Sip.briaPushNATEmulation" attribute can be left as its default value of true. Otherwise users may experience no push notifications or no audio, in which case "account1Sip.briaPushNATEmulation" should be set to false.

† CounterPath will be improving this behavior to ensure optimal interoperability.

Address List

Clients should automatically route to the correct nearest regional server, but we recommend ensuring that ALL addresses are accessible in case of travelling users, etc. 

Please also note that IP addresses may change in the future; if you manually configure your firewall/etc. for these addresses and experience issues in the future, please revisit this page to find the latest information.

Current limitations:

• Only IPv4 SIP servers are currently supported for calls involving the push server. The Bria mobile client will support IPv6-only networks utilizing DNS64/NAT64 when communicating with IPv4 SIP servers.