impiantitel

hi, I'm talking about the path on Linux PBX/..

If you can do a test you would like to know the result to adjust me accordingly

hi, I can't understand which is the basic and custom template path (Linux). I would like to add them manually but I do not know the route tnx, Damiano

as for modifying to *97 seems to me to be the most appropriate solution. about the behavior of the template for Yealink should check it, maybe I'm wrong. With 2 previous versions of Yealink it worked for me, with last fw it doesn't work. Please copy me a couple of examples that you enter in "Yealink General"? I make a comparison with my template. Thanks Damiano

hello, I normally enter the customizations for Yealink Templates Phones in the "Yealink General" window, and all phones regularly take these custom parameters. I have upgraded my Yealink phones to version 66.84.0.90 and now it doesn't work anymore (even if I enter the customizations in Yealink General, these parameters don't get them from the Yealink phone). Now to customize the Yealink template I have to edit the file "yealink_common.txt". Is this a known error? Is there a solution? ------------------------------------------------------------------------------------------------------------------------------------------------------------ I also found a bug (I think), basic Vodia sets the listening code of the voicemail = voice_mail.number.1 = {account} Then pressing the voicemail key from extension 215, for example, will dial 215, so it's an error. To fix it I tried to insert: voice_mail.number.1 = *97 The problem is that the * character doesn't take him in charge, in fact if for example imposed (only for test): voice_mail.number.1 = 333 At this point, by pressing the voicemail key, the telephone sends 333. This shows that it is currently impossible to set *97 for voicemail listening. Solution?

Thank you, as soon as I can, I'll try and catch you up, Unfortunately Yealink phone configuration side shows this: ### For security, the following parameters with password haven't been display in this file. ###account.1.password = ###static.auto_provision.server.password = ###ldap.password = I think it was more convenient if Vodia in the webpage /reg_ports.htm had 2 more options: LDAP Credentials (mandatory and complex): - user = - password = This way it would be easier for everyone and would be useful for every phone vendor (provisioning aside)

Thank you for your answer, I looked at what the Yealink phone receives but unfortunately I can not see in clear the pswd. The web pswd works, but since I wanted to create a manual template for Yealink phones, it becomes uncomfortable on every phone to modify the LDAP pswd. I find it strange that there can be no way to read what the Vodia server sends as LDAP pswd setting.

there are no answers to my two questions?

so, summarizing, if they supply an ok phone, the pswd is automatically given by the Vodia server. If instead they approve a phone manually I have not well understood which pswd LDAP I have to use. Second question was, where do I set the LDAP settings on the Vodia Server?

hi, I do not understand where you set the settings LDAP server side Vodia, especially I do not understand where you set the pswd LDAP

Okay I look forward to future instructions about the question of the Raspberry version, am I using latest building?

the new APP on Android is released today if I'm not mistaken, I did not think it was just in tests, sorry, I'm waiting for instructions Also Vodia Version: 63.0.5 on Raspberry is latest release?

maybe I explained myself wrong, I'm referring to the update APP for Android. Now you can frame the QR code, but how do you create the QR code? I sent the email to my account but it doesn't contain any QR code. Vodia Version: 63.0.5 on Raspberry

but how do you do it on Raspberry instead? This option does not exist Okay found

hi, I saw that you can login via QR code on new Android APP. How do I create the QR code for the desired extension? Can I send an email to the extension with all my login details? tnx Damiano

thanks 1000 Damiano

tnx

I have the same problem on Raspberry, can I please have the link to the update?I have the same problem on Raspberry, can I please have the link to the update?

Okay, it was just to signal the anomaly

the problem as it also highlights almoondsllc are not the IVR messages that are correctly in Italian, but the Default web language, even setting it in Italian remains the display in English. (I still did the procedure you wrote to me, but it's useless).

confirmation, even after the reboot remains in English even if set in Italian Version: 63.0.2

How do I delete the callback list? with *55xxxx you make the call, but if I want to delete the list how do I do it? If you set it up (perhaps by mistake), it suggests that you continuously call the list endlessly. There will also be a way to delete the list, I hope.

found and done, the only thing that doesn't release if I release I have also seen that what interests me is obtained with *54, how do I from the outside to make it respond to me *54?

I'll explain myself better: is used to allow an employee of a company to use the lines of the Company. - a user is out of the company, call the number 02345678 (example) Vodia answers and calls the user out of the company. At that point, the out-of-company user can call externally using the Company's lines. Can this be done?