Vodia Telephone System

A new update 5.0.6 should be available within a day or so. It has the service flags control when permitted. It is under settings.

We will try to get that in our new release as far as Android is concerned.

No "Make calls with" is for outgoing which works and is also present in our pictures. But additionally there has to active calling accounts (I know they are terrible with naming), that is missing, OR somewhere else.

That picture with "Active Calling Account" and with the green slider on is from us. I don't see any such picture from you, unless I am missing something here.

Could this be a special SW from T mobile on this phone to avoid using other apps with the native dialer? That is, have they locked it? It would be a question for them why this setting is not available, why other apps can't use the native dialer? OR In this phone the setting is somewhere else? Because all Android phones have this setting (sometimes by different names), that is specially to allow other apps use the telecom system of Android in a consistent way.

That setting make calls with can be set to T-mobile. We want the "Active calling accounts" to be Vodia. Can you please show if that is on? It may be by another name depending on the phone. This one is from Samsung. Thanks,

You may have already done so, but just to make sure: When you upgraded, did it ask you about turning on the Vodia Phone. That has to be turned on. If you missed it, you can still get to it but it is a deeply hidden setting from Android. The reason is, now we use the native dialer for the calls, and the native dialer must allow Vodia Phone to use it. Under the native dialer, NOT our app, go to the three dots (burger) on top right, then Settings, then Other call settings (Calls in Pixel), then Calling accounts, then Active calling accounts, and you should see "Vodia Phone" with a switch in front. Turn it on. For some phones the setting names may be a little different. But that has to be turned on. OR You could clear the cache and settings of the app, uninstall it and install it again but at the beginning, please turn on that setting when it goes to that screen, then you can go back to the app to give the rest of the permissions. Thanks.

It will be out soon. Any specific complains or problems you may have with the Android, can you please mention them in detail if possible? That way we may be able to incorporate at least some of them before even this release, if small enough. At least we will have a starting point for the next one. Thanks,

Salesforce is integrated through user portal (under CRM settings) as each user has his/her own credentials. The integrations is REST API and only certain salesforce licenses support that. You also have to create a security token that you have to use together with the user credentials as explained here: https://doc.vodia.com/docs/crmsf2 Thanks.

Agreed. Right now, we are a little occupied with version 69. Version 69.0.4 was just released, where all of this has been done cleanly. Thanks,

Yes HubSpot has changed the API. You can still use the old API and authentication method of API key with only private apps, that you can create on HubSpot. Public apps are now OAuth based and we have added that support since 69.0.4, recently released. In the same area where you added the API key before, you have to press the Get OAuth Token button and using your Hubspot account credentials give it access. Then calls should be logged as before. If, it does not work for some reason, please put in a trouble ticket with us. Thanks,

For park, please drag the active call on the right to a park orbit, usually shown in the center. The transfer button or dragging the active call on the right to an extension box both do blind transfer. For attended transfer, simply hold the call in order to make the next call for consulting first before the transfer. Then you can drag that active call to the held call box below to complete the transfer IF the person says okay transfer the call to me. Yes, transfer got a little messy there, we will do it differently with the 69 coming out. Thanks.

When you upgraded, did it ask you about turning on the Vodia Phone. That has to be turned on. If you missed it, you can still get to it but it is a deeply hidden setting from Android. The reason is, now we use the native dialer for the calls, and the native dialer must allow Vodia Phone to use it. Under the native dialer, NOT our app, go to the three dots (burger) on top right, then Settings, then Other call settings (Calls in case of Pixel), then Calling accounts, then Active calling accounts, and you should see "Vodia Phone" with a switch in front. Turn it on. For some phones the setting names may be a little different. But that has to be turned on.

Although we don't have reports on this issue from others, we are trying to improve that area to make it more robust. The new release will have it within a few weeks.

We tested it right now with Samsung S22 Android 13 on 4G and it works fine. It's always a little difficult when we can't reproduce the problem here, that's when we need more information like pcap traces for that call. You can turn the pcap on for that extension on the pbx. You can download the pcap from the calls records page of the pbx and send it to us. Also it would be better if you did that through our ticket system: https://support.vodia.com That way we can keep track of it and also share more info. Thanks,

Can you please open a ticket with us so we can get into the details. Because we have tested it on several models and OS versions and neither incoming or outgoing are issues. Our other big partners had a few issues with a few customers because of the confusion about the "Vodia Phone" not being switched on in the native app but once they were able to communicate that, there has been no problems. Can you please confirm if that setting is on: When you upgraded, did it ask you about turning on the Vodia Phone. That has to be turned on. If you missed it, you can still get to it but it is a deeply hidden setting from Android. The reason is, now we use the native dialer for the calls, and the native dialer must allow Vodia Phone to use it. Under the native dialer, NOT our app, go to the three dots (burger) on top right, then Settings, then Other call settings (Calls in case of Pixel), then Calling accounts, then Active calling accounts, and you should see "Vodia Phone" with a switch in front. Turn it on. For some phones the setting names may be a little different. But that has to be turned on. OR You could clear the cache and settings of the app, uninstall it and install it again but at the beginning, please turn on that setting when it goes to that screen, then you can go back to the app to give the rest of the permissions. Just in case, you want to know the the reason for using the native dialer approach. It is to use a common telecom platform for all calls, VoIP or otherwise, so that all the related features are available in a consistent way and that each such app is aware of the status of the other such apps under a common platform for a better user experience like call waiting etc. The benefits were too many to ignore, in fact it is the recommended way for a VoIP app or calling app. - Call waiting: The app can now do call waiting with other apps which follow this scheme too, as well as normal GSM calls. So if you are on our app and new call comes in either through the app or even a GSM call, you should hear the knocking (beeps), when you pick it, it will ask whether to put the app call on hold and when you do, the app will go on hold while you finish the gsm call. Then you can go back to the app to resume the previous call. And vice versa. - All the call routing (handset, headset, speaker, bluetooth) and their volumes or ringtones and their volumes etc. are handled by the native app, so that there are no problems there. - Bluetooth is not only audio now but also the controls and caller id, like from your car or watch (when they support BT controls that is). So (when supported) the call should show on your car dash, and you can accept of reject the call from the car or steering buttons, or end call etc. The same for the watch. - Call logs will also go in the native history now. - Any other feature that is integrated from the OS with the native dialer should also be available for the app now, like call screening. - And many things of that nature ...

We now use the native android telecom system for the calls, so that is normal now. This has the benefit of call waiting working properly with the native dialer as well as other VoIP that also use the central telecom system. It also has the benefit of the car bluetooth call controls buttons working as well as the watch. Thanks,

That is odd, because if you look into our logs you will see we receive options and respond with 200ok and also send options and get 200ok. Regarding the attended transfer, I am sorry I did not completely get the problem. It has to open a new call to the person to whom you talk first and then complete the transfer. That is not working as intended? Thanks.

We will try with the Teams trunk headers if something can done there and if that works, we can then make that simpler by providing an easy option in Teams trunk.

Confirming: You have entered the url with https://... You have entered the username with the domain included after@: extension@domain.com You have entered the password. And your desktop phone is the same extension as the extension you entered in the chrome extension above.

That's what the default behavior of the notification is. If the display is on it is expected they can see the notification and take action. We can move away from that but then it creates other issues when you move away from their expected way of doing it. But we are still looking into it.

Here is the ticket with Android. I don't know if you can access this url, but here it is: https://issuetracker.google.com/issues/204914497

Well essentially their domain system admin could be doing this so that they don't share that company info with anyone else.

The reason for the button not clearing is that the phone does not empty a button if we want to unset it through provisioning. It keeps the old value. We have reached out to FyingVoice regarding this and awaiting their response as to whether they need to fix it or should we do something different on the PBX side. Note: For specific problems like these, it would be better if you opened a ticket with us, so that it can be tracked better internally. You can send an email to support@vodia.com. Thanks.

Can you please provide us with the logs? It's under Status->Logfile in admin mode. Click on Setup to turn off all other logs except the call log and trunk log. Then clear the logs and make the outbound call to Teams account and send us the logs. It will also be better if you could open a ticket with us regarding this issue, so that it could be better tracked. Thanks.