[Android local address book slow to open]

On 4/2/2024 at 9:49 PM, Vodia Support EU said:

Hello, unfortunately I can't reproduce the behavior either. The change was done in less than a second (Samsung Z4 and Xiomi Mi 11). In any case, I would uninstall the app (then restart the phone) and then reinstall it.

thanks, unfortunately I have tried this as well to no avail.

[Android local address book slow to open]

I have a potential new client that is testing the Vodia app and has reported;

"I am noticing that the Vodia app is very slow when changing the contact list from PBX Contact to Phone Contacts

It actually takes about 20-30 seconds"

 

Has anyone else experienced this and is there a work around?

The phone is;

Samsung S22 Ultra

Running the latest updates

 

I haven't been able to replicate this issue on my test mobile adn am putting this out to the group...

[transfer a call on Android App not possible?]

On 11/11/2023 at 8:55 AM, Vodia Telephone System said:

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.

Thank you, this worked for me as well.

Any idea on when Vodia will be addressing this issue or releasing a new version?

 

Cheers

[Version 69 interface is BAD]

Could you please provide us with a timeline if possible on the customiseable front end. This is one of the major areas holding us back from using v69.

[Call flow through hunt groups]

I have now also made the change to mx_loops and resolved my issue too, thank you

[Ring Groups: stage extensions does not go to stage 3]

There is a modification to Duc's requirement and the flow now is AA-RG-AA-VoiceMail.

As has been previously pointed out the call does not proceed beyond the second ring group and never reaches VM. This is not an indefinite loop but a 2 stage flow using 2 ring groups only.

Our system is using v68.0.30 and there must be a way to increase the imposed flow limit.

[Hunt Group Flow Failure/Limitation]

I have a situation where we have a requirement in a Call Flow for a customer to:

Auto Attendant>Hunt Group>Hunt Group>Voice Mail

The issue is that when the incoming call reaches the "final stage" on the second Hunt that the call just terminates.

 

I have seen this response on another thread that had exactly the same issue.

"Well there is a global setting called max_loop that you could increase. You can do this in /reg_settings.htm by clicking on the edit symbol in the header without having to edit the pbx.xml file and restarting the service."

This is the section that I have identified in the reg_settings.htm in the Customize>Template location:

<div class="row">
                <div class="form-group has-feedback">
                  <label for="max_loop" class="col-sm-6 control-label">[[max_loop]]</label>
                  <div class="col-sm-6">
                    <input class="form-control" type="number" min="1" step="1" id="max_loop">
                    <span class="glyphicon form-control-feedback" aria-hidden="true"></span>
                  </div>
                </div>
              </div>

If this is the correct location can you please advise on the change?

There must be a way of increasing the limit that is imposed on the incoming call flow that can be increased.

Any responses are appreciated as I need to resolve this one quickly.

 

Kind Regards

[Call flow through hunt groups]

Can you please elaborate on the change to be made?

This is the section that I have identified in the reg_settings.htm in the Customize>Template location:

<div class="row">
                <div class="form-group has-feedback">
                  <label for="max_loop" class="col-sm-6 control-label">[[max_loop]]</label>
                  <div class="col-sm-6">
                    <input class="form-control" type="number" min="1" step="1" id="max_loop">
                    <span class="glyphicon form-control-feedback" aria-hidden="true"></span>
                  </div>
                </div>
              </div>

If this is the correct location can you please advise on the change?

 

Kind Regards 

[Minimize to Tray]

11 hours ago, anton said:

Hi Brett,

Thanks for the feedback. We'll try to get it updated asap.

The app can be brought back from the Tray shortcut icon

 

1. Sometimes it hides in that menu

2. Can be dragged and fixed to be visible at all the time

Thanks Anton, I am aware of this as it is one of our end users that kept on using the shortcut on his desktop which was opening a new session. When our support team investigated his reported issue they found 15 Vodia sessions running in the background.

[Minimize to Tray]

One of our Engineers has just reported the below issue to me related to the app being minimized to the system tray.

"basically, when the user clicks the x it minimizes it to the task bar. this is normal. What isn't normal is when it is minimized and the user clicks the shortcut on their desktop  / start bar it doesn't maximize the existing Vodia process. it just opens and hides a bunch of processes in the background. I have since educated the users but the App should be maximizing existing app if someone reruns the shortcut."

[Version 69 interface is BAD]

On 6/22/2023 at 10:24 AM, RichardDCG said:

if you have a lot of extensions and park bays, you need to minimise the extensions to easily use the parking.  It's easier to drag/drop to park if they are in the middle.

I completely agree with this as well

[Version 69 interface is BAD]

One of the regular pieces of feedback we are receiving when people are first testing 69.0.4 is that it looks like a sheet of white paper as compared to 68.0.30.

Is there any ability to at least add a graphic into the centre of the screen to be visually more appealing. This will be the first thing that our customers would comment on after a change to 69.0.4 would be made?

In addition can you please advise when the end user documentation will be updated for the 69.0.4 softphone?

[Cannot Retrieve On Hold calls coming through a Hunt group]

this has now been resolved, we had to revert the system back to 68.0.26

[Minimize to Tray]

thank you all, I have just update via the Microsoft store and confirmed the feature now works

[Cannot Retrieve On Hold calls coming through a Hunt group]

Our production environment is currently 68.0.28 and is multi tenanted running on the latest version of Debian.

No updates or changes have been made and in the last couple of days an issue has presented itself. 

If an external call comes in through a hunt group and an agent answers the call and puts them on hold then they cannot retrieve the call. The agent appears to have retrieved the call but yet the caller is still listening to on hold music.

I have successfully tested a DID on an extension with an incoming external call and putting them on hold and retrieving the call. I have also successfully tested Call parks with no issue.

Can anyone offer any assistance or advice on this?

[Minimize to Tray]

Has there been any further update on this subject as i believe that it is still an active request to be able to minimise to the system tray rather than close the application

[Version 69]

On 2/2/2023 at 3:50 AM, WaveVoIP said:

Attached I have a screenshot of the user front end for v69. Blank canvas is an understatement. There is literally nothing on it anymore.. I had to make a ticket with support to make sure there wasn't an issue with the PBX. But they told me that it is in fact how it's supposed to look now. Which is a shame. I would assume most people who deploy and manage the system are not web designers and have little to no css / html experience, and don't have the ability to get someone to do it for them without hiring an external dev. So unless Vodia ends up changing the front end in a new update, or someone in the forum is kind enough to provide templates to change the front end to something that is nice and professional enough for us to actually use and put our names on to give out to clients. Then I would say most people will stay with v68 if the user front end is important to them. I know I will be until something about it changes.

This post summarises our outlook on 69.0.2 as well. We will not be moving this into production until something changes.

[Is there an issue with V68?]

We have now had identified that prior to v68 our IVR custom messages played once(as designed). Since upgrading to v68.0.2 the IVR message is now repeating and there is no option for it to not repeat.

[Merging Calls in the Vodia App]

11 hours ago, Support said:

By 2 mobile phones you mean GSM calls or there are Vodia apps on those 2 phones?

GSM calls

[Merging Calls in the Vodia App]

On 4/22/2021 at 1:15 AM, Vodia Telephone System said:

Merging a call as in a 3-way conference?

In the desktop version you can already do it (and it will soon be coming to the mobile app version too).

If one or more callers are on hold and you are talking to someone, then you can merge them all into a conference with a click of the conference button.

You will have to have at least one ad-hoc conference room set up in that domain though.

Thanks for the reply.

I have an adhoc conference room setup and have been testing with 2 mobile phones but cannot seem to be able to conference the calls. I click on the conference button whilst in an active call with a second call on hold but nothing happens.

Can you please advise?

[App ringing when already in a call]

10 hours ago, Support said:

What is the version of the PBX that you're on and the version of the App as well?

Vodia = 67.0.1

Vodia App = 3.5.5

[App ringing when already in a call]

I have received some comments from our team that the App is ringing in their headset from a new incoming call from a hunt group when they are already in a call. Is there a way to stop this behaviour?

Thanks

[Merging Calls in the Vodia App]

We currently use Bria and once you're in a call it comes up with the option to 'merge call'. Is this function available within the Vodia Windows app?

I know it is easy to do when using a Yealink handset but looking for the solution when using the Vodia App.

Thanks

[SIP Option PING on PRTG]

I am trying to setup SIP Option Ping on our PRTG Monitoring server using an extension that we have setup just for this purpose. We are constantly receiving a timeout request even though the corrent SIP credentials have been supplied. After Googling the issue I managed to identify an article which states

"prtg should probably make it obvious to the user that the sensor doesn't support pjsip.

observations: credentials are a sip extension and secret (not a root account on the pbx) the extension used to configure the sensor must be set to CHAN_SIP (not CHAN_PJSIP, which is the default on many systems) on my freepbx server, CHAN_SIP is on port 5061, so i configured the sensor accordingly"
 

Can anyone provide any insight into this or any possible suggestions?

[Minimize to Tray]

This is something that I had also requested in a different thread. All the recent updates to the app have been great so thank you for those as they have have addressed most of our concerns around the app.

We are just concerned about now deploying this to our customers and they close the app without realising it and as a result missing incoming calls which could result in loss of revenue.