PJSIP not ringing both devices at once

I am using the bria mobile app. I need my desk phone and app to ring at the same time since it’s the same extension. I have max contacts set to 5 but only my app rings. Am I missing something?

How many devices show registered under sip-asterisk info-peers. There’s different push notification settings like single device takeover etc. I use bria teams mostly to avoid all that but it likely has to do with your bria registration type or push type. You can check this by seeing if bria is stealing the active registration from your phone.

that’s probably the issue but can’t they be registered at the same time and ring at the same time?

Yes of course they can…but bria has settings for registration types…

There are four registration modes. Continuous and Standard are used if your VoIP service provider supports multiple registrations. Single Device Takeover and Single Device Emulation are used if your VoIP service provider does not support multiple registrations. Most VoIP service providers do support multiple registrations. The default value for new accounts is Single Device Takeover.

  • [OpenContinuous](javascript:void(0):wink:

The Continuous registration mode ensures that the Bria Push server is always registered on behalf of the Bria Mobile client. The Bria Mobile client still registers directly to the SIP server when in the foreground, but the Bria Push server does not de-register from the SIP server. In this mode, all inbound calls and all outbound calls from the Bria Mobile client are handled by the Bria Push server.

The Continuous mode, in particular, is used when a SIP server supports multiple registrations at the same time. This mode avoids any gap in SIP registration because the Bria Push server is always registered on behalf of the Bria Mobile client.

In the event of a call to the SIP account while the Bria Mobile client is in the foreground, the Bria Mobile client will receive an INVITE directly from the SIP server and via the Bria Push server. The Bria Mobile client will filter out these duplicate events and only allow one of the call attempts to progress.

  • [OpenSingle Device Takeover](javascript:void(0):wink:

The Single Device Takeover mode is an enhanced option of the Single Device Emulation mode. The Bria Mobile client and the Bria Push server take over registrations from each other without unregistering first . Neither the Push server or the Bria Mobile client sends SIP de-registration messages when transitioning from one element to the other. It aims to eliminate gaps that are present in the other registration mode. This mode is in some cases beneficial for SIP servers that only support single registration.

  • [OpenStandard](javascript:void(0):wink:

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.

  • [OpenSingle Device Emulation](javascript:void(0):wink:

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.

I don’t know that bria’s registration settings are doing that…you need to check your server to be sure.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.