[Yealink T41P & T46S provisioning problem]

Solved. The solution is to POST MAC in the Extension-Provisioning settings instead of the VoIP Phones section.

[Yealink T41P & T46S provisioning problem]

6 hours ago, Vodia PBX said:

Please make sure that you are using the release Yealink template. We have seen cases where the customized templates did not do the authentication {require-credentials} and then the template is rendered without a user. 

The other thing is that you might have to start the MAC pairing explicitly like you would do from the extensions list web page or the history section in the provisioning tab for the extension.

Thank you for the prompt response. This is a recently installed Vodia PBX instance. The Yealink templates haven't been touched/changed. The issue has been found while provisioning a first customer on this PBX instance.

Sorry, not sure that I understand the second part of your message. Do you suggest going to the Extensions web page, and then pressing "+" in the MAC column for each extension, and then manually populating "Bind to MAC address" field? If so, then we are trying to automate this to avoid mundane and time-consuming tasks. Imagine doing that for 200-300 extensions   

The script posts extension, mac, vendor and model to the 'rest/system/prov_phones' (VoIP Phones section). Then, if we check Provisioning section "Bind to MAC address" is populated with the phones MAC. 

However, if we don't press "Save" in the provisioning section for each extension before the phone sends a config request, the PBX can't match the request to the extension. It's as if a DB record of MAC-extension binding doesn't get created unless "Save" is pressed.

We are super impressed by the stability, ease of management, and a possibility of automation. If only you guys could help with this automation question, it'd be a life-saver for us   

 

[Yealink T41P & T46S provisioning problem]

Lyndon thanks for your initial post. You saved us a lot of time troubleshooting this issue. We are experiencing exactly same issue as you described in your first post (step 7).

A question to Vodia Team. A scenario:

1. We create all domain settings (General settings, Service flags, Extensions, VoiP phones etc.) via API first.

2. Then, we open account for MAC based provisioning (via GUI) and factory reset the phone.

3. While the phone is rebooting, it's getting the PBX address from the Yealink RPS.

4. After that, the phone requests the config from the Vodia PBX, but it doesn't get provisioned with the account settings, it's exactly at the same state described in step 7 in the first post of this thread. The Vodia log shows that phone config request is reaching the PBX, but the PBX can't match it to any accounts, and the PBX pushes a generic config (not sure how it's called in Vodia). The phone will be sitting with that generic config forever.

5. Finally, if we go to Extensions--> Select the extension in question --> Provisioning ( Bind to MAC address is populated with the phone's MAC. It has been populated via API) and just press Save. The phone immediately gets fully provisioned with the account settings. It looks like pressing Save (without making any changes), makes Vodia push the extension config.

UPD. If we create VoIP phones settings via API, and then (before factory resetting the phone) we just press Save in Extensions--> Select the extension in question --> Provisioning section. Then, we factory reset the phone, and it gets provisioned with the account settings. Looks like the phone doesn't get bound to MAC unless Save is pressed?? 

What are we doing wrong? Can this be fixed as we would like to automate domain provisioning as much as possible?

We are on ver. 66.0.5.

Thank you