Support

What is your ticket # ?

This would be similar to connecting branch offices, see https://doc.vodia.com/trunk_branches. Have you checked that out? All we would need is the trunk connected to both the PBX's and on Vodia's end, the trunk can be registered as an extension.

You have to: 1. Give it the "permission to monitor the ACD" from inside the ACD settings 2. In the permissions section of that extension "manage the ACD" setting has been set?

Thanks for the update. We may need a little time to fix this. Will update once done.

Have you give the permission to monitor this ACD from under "Permissions" section of that Extension? You should see that "Calls in domain" section. We're still working on that.

Hi Ramesh, Automated texts in reply to audio calls are unfortunately not one of our features currently.

These are the providers we support as of now on the latest 66.0 version.

MAC- http://portal.vodia.com/downloads/app/mac/VodiaPhone-3.0.0.dmg Linux - http://portal.vodia.com/downloads/app/lin/VodiaPhone-3.0.0.AppImage

Please try this: https://drive.google.com/file/d/1jwlNC5GjJRuWQhsEcq6mQB2EHULaW9wM/view Please uninstall your old copies of the client before installing this one. Also make sure you update your app manually everytime after this point, because Microsoft won't be able to send you update notifications anymore.

We just tried this on version 66.0 and in both cases, the original caller ID showed as the external cell phone number as expected. This is how our inbound routing has been set.

Which Vodia phone? Windows? iOS? Mac? Linux? Android?

What was your older version number?

Which App is this? Can you make sure that the App has all the permissions for the Audio device it is being connected to?

Yes, the PBX needs to be on 66.0 for this to work.

The last option on that same page of "Seitch to T.38" Can you turn that on as well?

Your provisioning server address should be PBX's address (and that too only if it's PBX IP address and not it's domain name). Have you entered Yealink's RPS server's address on the PBX in that field?

That depends on the headset. You can also pick it up from the App itself.

Hi, Please upgrade the PBX to 65.0 and try this again.

We're working on it currently. Will update this thread ASAP.

1. Can you change the source from "2*" to just "*" ? 2. Why are you dialing 800# ? Is dialing just 800 not working? 3. Have you provisioned the phones AFTER you made all the multicast setting on the PBX? If not, can you please make the above changes and provision few of the phone to try out again? 4. Also, if PBX and phones are on the same LAN, you can even turn on the LAN prov.

Hi, Have you given all the permissions to your windows client? Please re-check them.

Can you upgrade the Visual studio package on this server? 2013 VC++ ?

How about this?

How to upgrade to 65.0 files: Assuming your system is 64 bit. Can you: 1. Download http://portal.vodia.com/downloads/pbx/win64/pbxctrl-v65.0-64.exe , rename it to pbxctrl.exe (if it's 32 bit, replace 64 with 32 in this link) 2. Download http://portal.vodia.com/downloads/pbx/dat/pbxctrl-65.0.dat, rename it to pbxctrl.dat 3. Install the msvcr120.dll and opus.dll downloadable from here: https://doc.vodia.com/install_win Replace the existing files (.exe and .dat in your current working directory on your server) with both of these files, and restart the service?

Hi, Can you please try to install this package and then upgrade to 65.0 from there? For Windows 32, the current location is http://portal.vodia.com/downloads/pbx/win32/pbxctrl-v62.0-32.zip For Windows 64, the current location is http://portal.vodia.com/downloads/pbx/win64/pbxctrl-v62.0-64.zip The Windows version should be updated with Visual studio and we've added that in our latest version to be supported regardless.