Push Configuration

Using the Bria Push Service with Bria Enterprise iOS and Android clients 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 Apple and Google's instructions in the following links:
     • iOS Device (Apple APNS): https://support.apple.com/en-us/HT203609
     • Android Device (Google FCM): https://firebase.google.com/docs/cloud-messaging/concept-options
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 optionally set the "account1Sip.briaPush.OutboundProxy" attribute. 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. The "account1Sip.briaPush.RegistrationMode" attribute controls the Bria Push Service behavior for this and other scenarios as follows:
   • 0: Standard: Your VoIP service provider supports multiple registrations. In this mode, there may be short overlaps of registration where both the Push server and the Bria client are registered to the SIP server.
   • 1: Single Device Emulation: Your VoIP service provider does not support multiple registrations. Bria and the Bria Push server must unregister before the other one can register.
   • 2: Continuous: Your VoIP service provider support multiple registrations. The Bria Push server is always connected to the SIP server. Bria is only connected to the SIP server when Bria is in the foreground. When Bria is in the foreground, Bria ignores push notifications so you do not receive duplicates.
   • 3: Single Device Takeover: Your VoIP service provider does not support multiple registrations. Bria and the Bria Push server take over registrations from each other without unregistering first.
4. If the SIP service implements server managed NAT traversal or follows industry best practices where the SIP server sends responses to the originating IP address and port, the "account1Sip.briaPushNATEmulation" attribute should be left as is, with a default value of true. However, if users experience no push notifications or no audio, then "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 traveling 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.