- Joined
- Mar 17, 2026
- Messages
- 1
- Reaction score
- 0
New hosted 3cx customer here. We have already migrated one building over to 3CX, and it went extremely well. I am in the process of migrating our second building over, and we need intercom paging from the phones.
I have done this manually by going to each of the Yealink web interfaces and plugging in my multicast values and assigning a DSS key for the paging ground.
Of course, once you bounce the phone, the provisioning server overwrites the config.
What's the best way to handle this in the long run? Create a custom template with my parameters and then re-provision the phones? Or let the phones pull our initial config, then remove the provisioning server address from the phone for each user?
This building isn't so bad, only 5 phones, but our final building will have around 40-45 phones, and trying to avoid as much manual work as possible.
I have done this manually by going to each of the Yealink web interfaces and plugging in my multicast values and assigning a DSS key for the paging ground.
Of course, once you bounce the phone, the provisioning server overwrites the config.
What's the best way to handle this in the long run? Create a custom template with my parameters and then re-provision the phones? Or let the phones pull our initial config, then remove the provisioning server address from the phone for each user?
This building isn't so bad, only 5 phones, but our final building will have around 40-45 phones, and trying to avoid as much manual work as possible.
