CTel

We had to change VM from one provider to another, and was successfully done without any issues, however on the new system all things ok except the working mac based provisioning, now were not working on the new vm, despite its ablsolute copy. Suprisingly address book and rps were the only issues, however ldap/s were enabled on the firewall and it started working, but dont know how to get that to work for the remote provisiong PnP phones now. Any help appreciated.

Hello, Thanks for your input, the following issue got resolved for me by going to Tennant >> Settings >> Groups (edit the group and enable / disable) permissions.

@Scott1234 Thanks a lot for your input. It worked for me

Hi if there is a sample webitems.cfg file template available ?. Also when you want to change the web gui of the yealink handset after connecting to the pbx, what file will you change ? I could not understand the webitems.cfg and yealink_common.txt file difference. Some of the items that i need are actually on the yealink_common.txt files but when i change there it doesnot work. I only need my phones after connecting to one of the domains in vodia to give access as admin level so i can make use of all the features in the phone. Can anybody help me with this please. Thank you

Advanced features, Action URL, are not available after account login with PBX - yealink_webitems.cfg is blank in Vodia. Customize > Templates > Phones PnP > Yealink_webitems.cfg (Blank) Customize > Templates > Phones PnP > Yealink_common.txt (need configuration help) Since yealink has three different stages of login, can we specify somewhere in the pbx to edit the certain file and be able to access the web gui of yealink t53 handset as admin. As soon as we register handset with the pbx then these features gets hidden / disabled. Image attached for reference. Please advise if any ideas to fix it. Thanks

Yeah Thanks for the information, i also wanted to confirm that new clients and tennants created post issues are having no login issues, only those with old clients which were there pre update. for eg: if i create any new tennants now i will not have any issues with softphones or login from webpage and so on. im guessing some files or folders for tennants or domain file after the update has failed to work, can it work if i could overwrite tennant and domain folders from older back up directly in the server in the usr/local/pbx folder ?

the tennant addresses are subdomains, the system as soon as tennants are created, yes the system url address has https enabled from R3 (Lets encrypt), this server is on a public IP transit, and is resolving as per normal, not sure what could be the problem, should we downgrade to 67 and check ?

We are on version 68 atm, problem started appearing after the version 69 update, but then we revert back to 68 again, hoping that the problem would not appear no luck, but the login issue still persist. No DNS resolve issue as all the dns addresses are resolving as per required, and have no issues in loading pages.

We have discovered that there are login difficulties with apps, softphones, and browsers following the change from v68 to v69. The majority of our users are now impacted, thus we had to provide an opensource, free option like Zoiper or Microsip. It functions perfectly with these programmes, however Vodia, Softphone, and Weblogin do not. We are still experiencing problems and are expecting that the Vodia team will be able to provide some sort of resolution. Downgrading the pbx does not work either. If you have any information about similar kind of issues that have been solved, kindly post a reply. Thanks

We were using version 68 without any problems, but as soon as we updated to version 69, we started experiencing the same login problems with softphone and apps. Even when users reset the password, the prompt keeps saying "Incorrect password, please try again." Initially, we were unable to log into the admin portal on version 69, but RAW LOGIN enabled me to downgrade the software. However, we are currently stuck with this problem as even going back to version 68 does not work anymore. Any help would be appreciated. We are awaiting to hear from the Vodia Support about our issue but hoping this forum might help, Thanks