Unsupported Error: Invalid Provisioning Credentials

[JasperD]

Hi,


Currently we provision our Yealink IP phones by pasting the provision link directly in the phones via the web page. My order is to automate this process with the Yealink Management Cloud Service. I want to make sure that we can send the ip phones from the dirstributor directly to the customer, so they can plug it in at their office and it will auto-provision. We have a testroom here and I tested this feature out but i constantly get the same "error" no matter what I change.

If I set the provision link in the YMCS and I set the phone to factory settings (To simulate it comes new out of the box), it will boot up again and will come with the error "Invalid Provision Credentials" and it will automaticly fill in the username box: provision-yealink. However if I click on "back" it will proceed to provision anyway.

Is there any way to skip this authorization part?

I hope someone can help me.

Kind regards,

Jasper

 

[JohnS_3CX]

Hi Jasper,

We do not provide any support for types of provisioning other than the ones you see on our guides.
To be frank, I don't know exactly what happens when you try to use YMCS and why the phone generates that message.

The best I could advise is to use the link as it appears in your management console under phone provisioning, but I think that is what you were using already and resulting in this error.

 

[JasperD]

Hi Jasper,

We do not provide any support for types of provisioning other than the ones you see on our guides.
To be frank, I don't know exactly what happens when you try to use YMCS and why the phone generates that message.

The best I could advise is to use the link as it appears in your management console under phone provisioning, but I think that is what you were using already and resulting in this error.

Hi John,

Thank you for your fast reply. I indeed already use that link.
Yealink support doesnt react to i thought maybe someone on the 3CX forums knows what goes wrong here.

 

[JohnS_3CX]

Perhaps it is because the phone tries to authenticate when it should instead skip that part and go straight to asking for the provisioning file.

See if you have the option to disable authentication based provisioning from YMCS, that might prevent this from happening.