AnthonyP Posted April 8, 2021 Report Posted April 8, 2021 Good afternoon, We're wondering if anyone else has run into this before and potentially has a solution. What our customers want, is to use Bria across multiple devices with one set of SIP credentials. Counterpath(Bria) support says they do support this, however, it's up to the provider to handle two registrations with the same SIP credentials and send the call to the multiple endpoints. My understanding with Kazoo is the registrations walk on each other and only the most recent one gets used. Is there any way to allow one set of credentials to be used for multiple registrations, and signaling to go out to both? Thanks!
Karl Stallknecht Posted April 9, 2021 Report Posted April 9, 2021 (edited) Kazoo does not support this as far as I am aware. Edited April 9, 2021 by Karl Stallknecht (see edit history)
Logicwrath Posted April 9, 2021 Report Posted April 9, 2021 The setting to allow the same account to register multiple times has been turned off since Kazoo essentially generates revenue based on the number of accounts that get setup. As I understand it, you can register multiple devices using the same account. However, whichever device was the last one to check in to the cluster is likely the device that will receive any inbound calls. You can for example, create a generic account configured to dial out as a secondary phone number and register this one account onto multiple devices at the same time. Any outbound calls placed to this account should work normally. It would be the incoming calls that would generate a problem. However, in this use case, you may not require inbound calling since the main priority is the ability to switch phone numbers for an outbound call easily.
Administrators Darren Schreiber Posted April 10, 2021 Administrators Report Posted April 10, 2021 13 hours ago, Logicwrath said: The setting to allow the same account to register multiple times has been turned off since Kazoo essentially generates revenue based on the number of accounts that get setup. As I understand it, you can register multiple devices using the same account. However, whichever device was the last one to check in to the cluster is likely the device that will receive any inbound calls. You can for example, create a generic account configured to dial out as a secondary phone number and register this one account onto multiple devices at the same time. Any outbound calls placed to this account should work normally. It would be the incoming calls that would generate a problem. However, in this use case, you may not require inbound calling since the main priority is the ability to switch phone numbers for an outbound call easily. This is mostly correct. It wasn't about revenue, though. It was about controlling the features of the phone reliably from both the web interface and the phone itself - something that's impossible to do if the phones use the same registration. For example if someone enables call forwarding in their NY office to their cell while traveling to their SF office, then gets to SF, realizes they want to disable call forwarding, but it was set on their NY phone, now there's no way to do that if it's on the phone locally. But they'll still call support demanding we fix it (which we really can't, at least not without server-side sync which is model-specific and complex to build). So we decided early on not to do this.
AnthonyP Posted April 13, 2021 Author Report Posted April 13, 2021 Thanks for the replies, that has cleared this one up for us!
Joseph Watson Posted June 10, 2021 Report Posted June 10, 2021 Hey everyone, I am running into this as well. I built a "hack" we call the UC Proxy which allows this. But if we wanted to be able to allow multiple registrations on some device types, how hard would it be to modify kazoo to allow for this?
shamesaaron Posted June 17, 2021 Report Posted June 17, 2021 We use Enterprise Bria/Stretto and create four devices per user and add them to attribute pools. Attributes in the pool are associated to the correct bria user. Works perfect as long as you arent paying per sip device you create.
Customers Dhruv Posted August 20, 2021 Customers Report Posted August 20, 2021 Hi @AnthonyP We have been working with one of customer who uses MS Teams and they bought Bria Teams and ran into a problem you identified. In working with Bria our customer was given the following process to follow for setting up the pools described above by @shamesaaron : If you are setting up device pooling for all users (as in, all users will have multiple devices that each have their own sip credentials) please skip to step 2. If you are setting this up for only one user, please start with step 1. Make a new Voice account that is the same as the other one by going to the Voice and Video tab, and clicking the + button to add a new configuration, then adding all the same settings as the first one to it. This will be the configuration that uses device pooling. Under Voice and Video, click "Edit configuration" on the configuration you wish to have device pooling turned on. In the configuration go to the Service Compatibility Options tab Click the This service requires a different username for each SIP registration button, and also checkmark the This service requires a different password for each SIP registration button which will appear after the first it checked. Save and Close Go to the Team Member tab and click on the user with multiple devices. If you set up a second Voice Configuration, you will need to change the voice configuration for them to the new one. You will now see tabs for each SIP registration, enter the SIP registrations in each tab. Click Save and Close On every one of the user's devices, Log out of Bria. You will want to start with Bria signed out on every device. One at a time, log in on Bria. The first device to log in will take the first registration you set up, the second one will take the second, etc, until they are all assigned. Thanks, Dhruv
Recommended Posts