Multiple Extensions/Identities on provisioned Snom D765

[Jamie Lupton]

Hi,

I am trying to get a solution to the following issue.

Case Requirement
We have a requirement to be able to make a call from a few different numbers, on the same handset. For example, during account management, we'd use our own DDi, and if we're involved in helping with customer service, we'd use the main switchboard number. So that customers are presented with the number they need to call back on.

The idea is to create different extensions (which would be used for outbound calls only), set the CLI accordingly, use the SIP credentials for these extensions on identities on the phone. Simply put, we'd have a button for each outbound number/line.

I'm aware that 3CX cannot remotely provision multiple extensions onto a single phone, but from reading other threads, it seems that there should be no reason why we couldn't manually provision it by logging into the phone web admin, and entering the SIP credentials manually.

What I've tried so far
I created an extension in 3CX and set up correctly. I used the SIP details to enter into the phone, and it would not register. I then added a new SNOM D765 in the provisioning, and it would not allow me to use the same MAC address of the hardware, as it was already in use on the main extension. I then tried using a fake MAC address to circumvent it. This time the extension registered on the phone, but calling is forbidden. (I presume it is checking allowed mac addresses).

It seems that the limitation in 3CX is that there is no way to just set up a dumb extension with SIP credentials, which can be entered into any client/phone. This can't be the case. We may wish to use Bria as well in future as it allows always online (unlike the 3CS app) - I guess this would be blocked the same way?

Does anyone know what I'm overlooking here? This is a deal-breaker!

Kind Regards,

Jamie.

 

[YiannisH_3CX]

Hello @Jamie Lupton

Please note that having 2 accounts on the same device is not supported by 3CX but you should be able to register the account to the handset manually. No need to create a phone under the extension as you will not be provisioning the device but manually registering it.
If the phones are remote the to PBX make sure that the option "Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked)" is not enabled under the extension settings and that you are using the correct SIP credentials to register the account. Check an already provisioned account and compare the details.

You could also achieve the required functionality by adding a second trunk to your PBX. That way the users can select an Outbound caller ID based on the trunk the call goes out from. You can of course control that by using Outbound rules.

 

[Jamie Lupton]

Thanks for the reply.

I followed the steps and unfortunately it hasn't solved the problem. I've got the extension on the phone identity, and both the phone and the 3CX dashboard, show it as registered successfully. It's only when I call, I get 'forbidden'.

There is nothing ticked under the Options>Restrictions section at all. All of our phones are connected over open internet so the option "Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked)" is actually disabled on the main extension as well.

When setting the extension up, as I have not provisioned a phone on it, many of the options such as ports, and mac address are not enabled, and cannot be edited.

Has anyone managed to get this to work? Are there any settings anywhere to switch off the MAC address filtering etc? Or a way to spoof the system so it thinks it's the same phone?