Bulk import does not seem to send MAC to Yealink RPS

[IPEVA]

Hello all,

In 3CX (last rev), when we bulk-import users with MAC addresses from a CSV file, 3CX does not seem to communicate those MACs to Yealink RPS, so autoprov does not work.
We need to go into each user and click on OK to resend the MAC to RPS.

Are we totally wrong or is there an issue there ?

Thank you

David

 

[Charles_3CX]

That’s actually correct. When you import extensions via CSV the system will not send to RPS unless the extensions are edited and then OK is pressed at the top of the page.

 

[IPEVA]

Charles,

Don't you think there is room for improvement here ?
When you import 100 users to speed up setup time, the last thing you want is to edit 100 users just to press OK

David

 

[Martijn Hoefnagels]

Hi Charles,

Any update regarding David his question?
We have the same (issue) over here. We are using Fanvil H3W hotel phones for big upcoming projects. (368 & 640 rooms)
It will save additional time by not have to click and ok for each user.

Thanks in advance for your reply.
Regards,
Martijn

 

[IPEVA]

It seems noone but you and I thinks it's a major issue

 

[JohnS_3CX]

Hi all,

If you run a large installation like a hotel, its better to use a different mass provisioning method such as DHCP Option 66.

It will come in handy in the future too in case a phone needs to be factory reset, upon reboot it will automatically reprovision.

 

[Martijn Hoefnagels]

Hi John,
Thank you for your reply.
We have a full automatic provisioning active based on MAC address.
The original question was why an RPS file is not automatically created when importing a large batch of users, in my case hotel rooms, including all provisioning MAC addresses.
The answer had already been given by your colleague Charles I see, but we were wondering if this is possible in a different way or if this is on the roadmap.

Regard,
Martijn

 

[JohnS_3CX]

Hi Martijn,

AFAIK there are no plans for mass RPS provisioning via import (partly why I mentioned option 66).

Also since RPS expires, you lose the benefit of automatic reprovisioning upon reset in case you need to troubleshoot a device which is misbehaving, or in case someone resets the device by mistake.

 

[IPEVA]

The only reason I can foresee for a such restriction is the following:

with bulk import, one could import thousands of phones in a 3CX instance, covering all Yealink MAC address space, for instance, and thus, blocking Yealink RPS for a lot of people for 15 days.

This could be easily prevented by adding a limit to 1000 users per import.

David

 

[IPEVA]

Hi Martijn,

AFAIK there are no plans for mass RPS provisioning via import (partly why I mentioned option 66).

Also since RPS expires, you lose the benefit of automatic reprovisioning upon reset in case you need to troubleshoot a device which is misbehaving, or in case someone resets the device by mistake.

In a such case (only one device), I can revalidate the MAC address to repopulate RPS.