server interact with the SIP server. For some customer’s SIP servers, the registration
mode may not matter or make a substantive difference to the behavior of the SIP Server
or the reliability of the reachability of the Bria Mobile client. For another customer’s, the
registration mode will matter quite a bit because one of the registration modes works
best to address the particular limitations of the customer’s SIP Server. Customer
administrators and IT staff should carefully understand these registration mode options
and their potential impacts.
l
Standard (0)
The Standard registration mode allows both the Bria Push servers and the Bria
Mobile clients to register to a customer’s SIP account in an alternating manner. In
this mode, there may be short overlaps of registration where both the Bria Push
server and the Bria Mobile client are registered to the SIP server. Some PBXs, SIP
servers or SIP services may have issues with this registration overlap. If you
encounter an issue with registering to the SIP server or receiving push
notifications, select a different registration mode.
l
Single Device Emulation (1)
The Single Device Emulation registration mode ensures that both the Bria Mobile
client and the Bria Push server unregister before the other one registers. In other
words, the Bria Mobile client and the Bria Push server never register to a PBX, SIP
server, or SIP service at the same time. The Bria Mobile client controls the
registrations by requesting the Bria Push server to register only after the Bria
Mobile client has de-registered and alternately, by receiving confirmation that the
Bria Push server has de-registered before the Bria Mobile client registers directly
to the SIP server. The Bria Mobile clients will also not register while they are in a
call delivered through the Bria Push server so that they do not cause potential
issues with the call in progress being terminated by the SIP Server.
Note that when in the Single Device Emulation registration mode, there are
periods of time (typically fractions of a second) when neither the Bria Mobile client
or the Bria Push server will be registered to the PBX, SIP server or SIP service.
This gap could lead to a missed call if the call is presented to the SIP server at the
same time that neither element is actively registered. This is a downside of the
requirement of the SIP server that only one element be registered at any one time.
l
Continuous (2)
CounterPath Corporation 25
Bria Mobile User Guide Getting started