Support

One q: Is your reminder timer larger than the voicemail timer?

Can you give a call to our support team along with the Anydesk ID and we can take a look?

If both of those check marks are seen, then you need to just follow ahead with the documentation. When you go to the user portal > CRM > Zoho > Get auth code, do you see another window pop up which needs your Zoho account's login? If yes, that's all that's needed from Vodia's end. If not, then that's what you have to look further into. Your login creds might be wrong on there?

That seems to be the problem. Please try to upgrade to 67.0.5 once again and then try the above steps. Then turn on the necessary logs and try again.

The ports that you mentioned should be the only ones needed for the integration, but just to confirm, you turned on the Zoho integration from under /dom_crm.htm and then from under the user portal correct? Both had a green check mark next to it? If yes, then from the PBX's end the integration was done. You can then turn on the admin level logs for , "trunks", "CRM Related events" and "call messages" to the highest and make the call and see if there are any PBX related issues.

Have you covered this doc: https://doc.vodia.com/docs/zoho-crm We updated it with the IP addresses that need to be whitelisted in your firewall as well.

Could you divulge more details about this use case? Attended trasnfer to who? Another extension or a park orbit? If it's another extension, then how would it turn into a Blind transfer if you never got to speak with that extension to call it an attended transfer?

We will test this and let you know more.

Who's perspective are you looking at this from? The agent group monitor?

This is still there: https://doc.vodia.com/docs/admin-sip-and-audio We will let you know shortly about the other one.

If you backup only the domain files, that should be enough too. But we generally use this https://doc.vodia.com/docs/how-to-backup-the-pbx

We usually make it via the inspect element > Console. Unfortunately, we don't have that functionality.

Please also make sure this is the case: https://doc.vodia.com/docs/vodiaports

Here: https://api.vodia.com/

API for Max calls in ACD: curl -u admin:pass GET -D - http://<PBX_URL_OR_IP_ADDRESS>/rest/domain/<PBX_DOMAIN_NAME_OR_IP>/user_settings/1000 -X POST -d "{'maxcall':'5'}"

Yes it is stable one. But always take a backup of your current system before you upgrade everytime to be on the safe side.

"from=13159612166&to={open-curly}from{close-curly}&body=Thank you."

Please try {open-curly} and {close-curly} (see https://doc.vodia.com/docs/phone-provisioning-variables).

API: curl -u admin:password GET -D - http://<PBX_URL_OR_IP_ADDRESS>/rest/domain/<PBX_DOMAIN_NAME_OR_IP>/config -X POST -d "{'max_calls':'444'}"

Hi, This won't happen automatically, but you can manually do that everyday. But again, the calls can't be allocated to specific accounts. It shall be assigned to the PBX as a whole.

Yes it may impact it. This should've been resolved in 67.0.4 but you can also try 67.0.5. Also please go to Certificates > Hit reset at the bottom before you try the above.

Can you privately send us the system login to your PBX and we will take a look at your Activesync here? You don't have 2FA turned on, on your system right?

1. What is the PBX version that you're on? Build version and date? 2. Which browser are you using?

We do have a field called as "category" when you create new address book logins, is that not helping?

What version of the PBX are you on when you test this? Are you testing the GAPS or just the normal manual provisioning of the phones to the PBX? Or is there something else that is not working? We've had no customers complain about this, so rest assured this should be working. Are you following this doc https://doc.vodia.com/docs/pnp-grandstream to avoid any trail errors? Moreover, we're fine tuning some of their phones at the moment.