Toggle sidebar Toggle sidebar

Automatic Provisioning of Snom D715 hotdesk phones

Status
Not open for further replies.

telis

Premier Customer
Advanced Certified
Joined
Aug 13, 2007
Messages
238
Reaction score
65
Hi,

We are deploying handset internally on a multiple subnet network.

1. We used to use DHCP option 66 to provision snom phones but this doesn't seem to work for us any more (is that correct?).
2. As far as I can tell you can't use the remote snom provisioning server based provisioning methods to deploy Hotdesk handsets. the option just isn't there.
3. And we can't use the "Local LAN (in the office)" method because this is L2 so doesn't reach all our subnets.

How do we deal with this?
 
telis said:
Hi,

We are deploying handset internally on a multiple subnet network.

1. We used to use DHCP option 66 to provision snom phones but this doesn't seem to work for us any more (is that correct?).
2. As far as I can tell you can't use the remote snom provisioning server based provisioning methods to deploy Hotdesk handsets. the option just isn't there.
3. And we can't use the "Local LAN (in the office)" method because this is L2 so doesn't reach all our subnets.

How do we deal with this?
Click to expand...
Put an SBC and configure the hotdesk phones in 3CX. Option66 won't be needed.
 
The 3CX system is on prem, where do we put the SBC?
 
telis said:
The 3CX system is on prem, where do we put the SBC?
Click to expand...
If you can't use Local LAN, put an SBC in each subnets that can't be reached by the PBX. This way, the SBC will detect the phones correctly and send them config updates.
 
Frederick Marcoux said:
If you can't use Local LAN, put an SBC in each subnets that can't be reached by the PBX. This way, the SBC will detect the phones correctly and send them config updates.
Click to expand...
OK. I suppose we could do that but we probably won't because other than the intial provisioning everything else works fine without adding an SBC for each subnet, we're not traversing NAT after all. Good idea though. Are there any other options?
 
telis said:
OK. I suppose we could do that but we probably won't because other than the intial provisioning everything else works fine without the SBC, we're not traversing NAT after all. Good idea though. Are there any other options?
Click to expand...
I would not take that chance.

And yes, put the PBX in the cloud and use SBCs everywhere, or correct the network config so that all subnets can see each other.

And even if it works fine without it, the fact that your L2 doesn't reach all subnets can cause issues with ext-to-ext calls.
 
Frederick Marcoux said:
I would not take that chance.

And yes, put the PBX in the cloud and use SBCs everywhere, or correct the network config so that all subnets can see each other.

And even if it works fine without it, the fact that your L2 doesn't reach all subnets can cause issues with ext-to-ext calls.
Click to expand...

I don't understand what you mean by "correct the config", I don't know how L2 can reach a different subnet! All subnets can see each other.
 
telis said:
I don't understand what you mean by "correct the config", I don't know how L2 can reach a different subnet!
Click to expand...
What is your network setup? If you have the PBX on-prem, and different subnets, you should just have to create routes between them (or allow traffic between them, depending on the type of firewall you use.)

If the PBX can see the phones locally, you don't need an SBC. If it can't, then you need a way to connect. Option66 works for both methods, you just point it to the PBX provisioning folder.
 
telis said:
we can't use the "Local LAN (in the office)" method because this is L2 so doesn't reach all our subnets.
Click to expand...
That's the part I'm wondering
 
Layer 2 is Ethernet frames only. It's doesn't understand TCP/IP. I thought "Local LAN (in the office)" used Layer 2 broadcasts to provision the handsets.

We have 6 sites, the 3CX server is on one site and there is a fully routed Layer 3 with no firewalling.
 
telis said:
Layer 2 is Ethernet frames only. It's doesn't understand TCP/IP. I thought "Local LAN (in the office)" used Layer 2 broadcasts to provision the handsets.

We have 6 sites, the 3CX server is on one site and there is a fully routed Layer 3 with no firewalling.
Click to expand...

Ah, it's multicast so there is a chance we might be able to forward it. Does anyone know the details of the multicast message?

https://www.3cx.com/docs/manual/configuring-ip-phones/

PnP Provisioning​

To use this method the phone must be on the same network as the PBX or you must have deployed them behind an SBC. To connect a phone on a remote network via SBC read this guide. To auto-provision phones using Plug and Play:

  1. Connect the phone. It will send a multicast message, which will be picked up by 3CX.
  2. The phone will appear in the “Phones” view of the 3CX Management Console. Select and assign the new phone to an extension with “Assign Ext”, or create a new one using “Add Ext”.
  3. In the extension’s provisioning tab that opens, leave “Provisioning Method” and “Mac Address” fields to default values. You can configure other phone settings, e.g. “Phone Display Language” and “Timezone”.
  4. Click “OK” to send a configuration file link and configure the phone. It should automatically restart and connect.
 
telis said:
Layer 2 is Ethernet frames only. It's doesn't understand TCP/IP. I thought "Local LAN (in the office)" used Layer 2 broadcasts to provision the handsets.

We have 6 sites, the 3CX server is on one site and there is a fully routed Layer 3 with no firewalling.
Click to expand...
6 sites should be reached via VPN or MPLS, so use the Local LAN. Not it doesn't "broadcast". You need Option66 of each DHCP pool to point to the PBX LOCAL IP.

Provisioning is done by sending a SIP NOTIFY once the phone is detected and configured in the PBX. Having them appear requires Multicast but you can set the MAC Address in the PBX and Option66 will allow the phones to get their config.

As for Multicast forwarding, it depends on your router/firewall mostly.
 
telis said:
Ah, it's multicast so there is a chance we might be able to forward it. Does anyone know the details of the multicast message?

https://www.3cx.com/docs/manual/configuring-ip-phones/

PnP Provisioning​

To use this method the phone must be on the same network as the PBX or you must have deployed them behind an SBC. To connect a phone on a remote network via SBC read this guide. To auto-provision phones using Plug and Play:

  1. Connect the phone. It will send a multicast message, which will be picked up by 3CX.
  2. The phone will appear in the “Phones” view of the 3CX Management Console. Select and assign the new phone to an extension with “Assign Ext”, or create a new one using “Add Ext”.
  3. In the extension’s provisioning tab that opens, leave “Provisioning Method” and “Mac Address” fields to default values. You can configure other phone settings, e.g. “Phone Display Language” and “Timezone”.
  4. Click “OK” to send a configuration file link and configure the phone. It should automatically restart and connect.
Click to expand...
It detects phones via Multicast.

It provisions them via SIP NOTIFY, not Multicast.
 
  • Like
Reactions: Evolute IT
Just to clarify, all option 66 does is pass the provisioning URL to a device. It won't configure firewalls, fix routes, or anything else related to the traffic successfully reaching 3CX. But provided you have your network configured correctly, option 66 works just fine.
 
telis said:
Hi,

We are deploying handset internally on a multiple subnet network.

1. We used to use DHCP option 66 to provision snom phones but this doesn't seem to work for us any more (is that correct?).
2. As far as I can tell you can't use the remote snom provisioning server based provisioning methods to deploy Hotdesk handsets. the option just isn't there.
3. And we can't use the "Local LAN (in the office)" method because this is L2 so doesn't reach all our subnets.

How do we deal with this?
Click to expand...

Hello,

Let's clarify a few things before further questions are posed:

1. How are your current phones setup in the extension settings? (LAN / SBC / STUN)

2. Are you using a local FQDN and split DNS? (Yes / No / Not Sure)

3. Are all your subnets in RFC1918 compliant address space? (look it up if not sure - confirm this 100%)



Find out the above first - these will decide the rest of the conversation
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Total: 207 (members: 4, guests: 203)

Forum statistics

Threads
111,832
Messages
589,280
Members
164,662
Latest member
DejanMDS
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom