Vodia Telephone System

By the way what version of the app is it? 1.0.0 had a problem. We are on version 1.0.2 but the phone must have already updated, but just checking.

Just make sure your microsoft email is set for that user. Also there is sometimes the problem of router not connecting to IPv6 addresses which then takes 4 minutes or so to sign you in. If there is no problem with ipv6 connections then it should be immediate. Thanks.

Hmm I wonder if this could be one of those very rare Android phone or Vendor OS that does not allow the native dialer from other apps (which should be a no no but some of them do it). When you installed the app, did the phone take you to a screen called calling accounts where you had to turn on a switch for Vodia Phone 2? If it's available you should still be able to find it in the native dialer. In the native dialer, not the phone app, under setting then "other call settings" or "calls" (it's different with diff vendors), then Calling accounts, then active calling accounts, you should see Vodia Phone 2, turn it on to give Vodia app the permission to use the native app. But as I said this should have come up on initial install if your phone supported it, or on incoming call. You can also open a ticket so we could share info for a video call/screen share if you want. Thanks.

Not at the moment. We are looking into it. But trying to find out how to find a persons ticket, where the call should be logged?

That seems to be from the outside of the app? For now we want to see if you can access and dial the contacts from within the app. As you see in the attached image, the top tab says local contacts, those are local contacts shown within the app. Can you dial it from there in this phone model?

Could it be that it is a very long list. How many contacts are we talking about? If that is the case then we will have to maybe also replicate a huge local list as well (confirm if the list is in the thousands)? Thanks,

The oauth hubspot is supported only in v69. And v69.2.4 is pretty stable. But if they still want to stay with v68, then they can do it the old way with hubspot but have to create a private app (essentially integration) in Hubspot that uses the API key. You can open a ticket for further details if needed. Thanks,

In the ticket system (or if yo prefer here), can you please upload a small video so we know exactly what we are talking about. Opening ticket is recommended (if you already have a ticket, you can give us the number ticket here), so we can properly follow through and maybe also get one of these exact phones to test. Thanks.

There is an address book inside the Vodia app itself, it also shows your local numbers of the phone, can you please dial from there? We will look into the other scenario. Thanks.

Do you mean from the external address book (not the app, but the native address book of the phone) or the internal address of within the app itself? Because the internal address book of the app itself also shows in one tab the phones local contacts, from where you should be able to dial. Thanks.

Yes it is our new native app, still under feedback phase for things like UI. That is indeed strange because this is how it looks for us on multiple Samsung (low end to high end) and Pixel phones: Which phone vendor and model are you using? Thanks

Can you please turn on the stand alone mode. In the app settings, under Sync page, you will find the standalone mode, you can turn it on. This mode is not recommended because it will not use the android native dialer anymore (with all the benefits), but just to find out if that is causing the issue? Thanks.

Is it in speaker mode or normal mode when they hear the echo? Which make and model is the Android device? What version of the app are we talking about? Also, when you are in a call, is the native dialer being seen on screen (our app now uses the native dialer) or the app specific dialer is being used? Thanks.

That's strange. What phone model is it and what version of the app are you using? Can you please send a screenshot of the active call that shows the call control buttons including hold etc. If not here, you can open a ticket with us for more info to share. Thanks.

Yes you can also do that. Put the call on hold. Then you can make the next call to tell them there is a caller who wants to talk to you for example. Then when you do the tranfer, choose the held calls list to tranfer to and transfer to the previsouly held call. Thanks.

With the native dialer we use now, it does not have any extra features or buttons like transfer. That's why for other features, you have to switch back to the Vodia main app (either by pulling down from the top and clicking on Vodia call OR clicking on the vodia icon or from the tray, which ever suits you). From there you can press the transfer button and then transfer. Thanks.

It has been back ported, the new version of 68 should have it. Thanks.

The new release 5.0.15 has been released. It should be available on the playstore in a few hours or so. It should fix the problem and some other improvements. Thanks.

What version? I has been fixed in 69.

Can you please put in a ticket with Vodia so that we can share some information before we can suggest a possible solution. We may even need to do a screen share. Usually though the problem from Teams to Vodia side is the Teams route, which is a regular expression and depends on what you want. But for testing you could set it to .* for all numbers and also it seems to propagate after an hour or so after saving, so you can't immediately test the route setting. Thanks.

Can you please open a ticket with us, so we can look at it in more detail. That is certainly not the general behavior that others are experiencing. We may have to do a screen share to see this problem and understand it. Thanks,

Well many people are using it and they mostly use it as an extension as it was intended. Even with putting the DID there works well (maybe just the cosmetics may not look so good in case you name the accounts as DIDs), but by no means will anyone call it half baked, definitely people who are are using it and happy with it. Can you please tell us the remaining list wrong or not implemented?

Unfortunately it can't be done with the simple settings. If we do it, it will have to be done in code.

For manual flags in 68, yes you can. Just make sure the setting "Extensions that may change status" has the extension that is making the change. Also, because of status update issue on 68, the update does not happen live. So when you change the status on 68 for a manual service flag, can you leave the screen and come back to see the status change. In the next version, we may find a work around for that.

Like iOS, it will show status but not be changed with a click. That changing API is simply not there in 68.