Support

Hi All, The version 65.0 is officially out. Please go ahead and read take a look at all the advancements and bug fixes that were done in this build. https://doc.vodia.com/releasenotes650

You can assign the new password both on the desk phone's GUI and user portal and done.

1) If you programmed them manually, can't you reuse the same password then? 2) Even if you use a new password now, it won't affect your deskphone because you've manually registered them. Should be fine. You can try with one phone and see the results.

Nope it won't unless that deskphone reboots or re-provisions.

Nope, not needed. He can just create a new SIP password (if he's the domain / system admin) or ask the domain admin to create a new password for him and use that.

Hi, Unfortunately, we don't have that on the latest version. We might have to add this in our bucket list.

Please check your sonicwall configurations (which we've also replied via the ticket that you raised). The sonicwall has caused a lot of issues to many customers of ours. There is a setting that needs to be turned off (hoping that it's SIP Transformation as we're unable to find the snapshot of it from when it happened earlier) which should help your case out.

Can you just do LAN provisioning for these phones? Make sure you're on 64.0 to do this.

Also Henrik, You're sure you don't have any customized template files that might be causing this issue right?

Hi, Using the above solution that we gave you can go ahead and add more custom CSS rules to your portal.

Append this to the index.css and try it out. #accounts > tbody > tr > td:nth-child(2) a{ color: blue } OPTIONAL: #accounts > tbody > tr > td:nth-child(2) a:hover{ color: blue } #accounts > tbody > tr > td:nth-child(2) a:active{ color: blue }

Silly idea: Please try to clear all the cache and try it on incognito.

Yes please upgrade to 63.0: http://portal.vodia.com/downloads/pbx/version-63.0.xml

You can just use this doc page to change colors. https://doc.vodia.com/appearance

Reply from one of our customers on the same issue: "run the pbxctrl.exe as an ADMIN from the CMD received the message that “msvcr120.dll is missing.” So there is a prereq of MSVC++ redistributable 2013 that exists with v64. After installing the most recent and 2013 VC++ redistributables I was able to manually run v64."

We do have documentation about this part exactly as well: If you Ctrl + F for "\1" or "\2" on this https://doc.vodia.com/domain_dialplans , you will know more.

Have you tried to switch the setting "Use domain name instead of IP address" on /reg_pnp_settings.htm page?

Just make sure that all of your domains are FQDN and are accessible via port 80 and give it less than 2 hours. The certs should begin to be assigned in the same section as seen above. For more, Ctrl + F for "ACME" on https://doc.vodia.com/releasenotes610

Unfortunately, there is no way for that to be done. You can only record it, the application of it still has to be done from the web interface.

Hi, Unfortunately, the Night service number isn't a feature that we offer which can be changed via the phone itself.

Hi, Seems like an issue with your signalling. Your phones seem to be behind a NAT right? Have you configured this setting "Outbound proxy pattern" on /dom_settings.htm page and THEN provisioned the phones?

Is there a way that you can attach a screenshot here when it happens again?

011 is generally used for international calling. Maybe that's why it's clashing. Can you please go through this doc to know more about dial plans: https://doc.vodia.com/docs/domaindialplans ?

Here: https://doc.vodia.com/pnp_grandstream You can also try LAN / DHCP 66, provisioning.

If you're on the latest version of the PBX (64.0 and above), it should work fine. Please upgrade and try again, if you're not on it. If IP is not shown in the log file, meaning it's not even able to reach the PBX which hints to Firewall issue ?