DanielA

In addition to this, there are numerous users complaining that their apps do not ring, or a blank white page is displayed, or no audio. The mobile apps are very unreliable.

Hi Team, @Vodia PBX I'd expect that the phone should still ring (audible/vibrate) upon inbound call - not just play a notification tone and display as a bar at the top of the screen? Is this expected behaviour? Tested on 4.0.16 on PBX versions 68.0.4 and 68.0.9beta seems to behave the same on Google Pixel and Samsung Galaxy S20 5G.

@Vodia PBX Having similar issues. Device Galaxy A12 latest android update. We're currently using push-au.vodia.net which I believe was recently relocated from US to AU. End User gets very sporadic push/wake on inbound calls. "When I got a call from my colleague this morning it rang. But has not worked this rest of the day. " Any suggestions?

@RichardDCG FYI - Bit of relevant info for you. We've got a ticket open with support currently regarding faxing from the user portal. The user portal will fit the page width to fit to a US-Letter page size - this leads to having a section of the bottom of the page cut off when faxing an A4 document.

No IP's blocked, these services are typically connecting via 4G. We have whitelisted the carriers IP ranges for 4G services as well as our customers physical locations IPs. If an IP was blocked, I wouldn't have expected the app to completely lock up and need to be uninstalled and reinstalled to get it to function again.

Hi team, App users seem to be having issues where the app will display a blank white screen on android or displays no content on iOS. Only fix looks to be to uninstall and re-install the app and re-login using the QR code. If the PBX is restarted or updated it appears to drop all the connections and the apps lock up needing to be uninstalled and reinstalled again. We have quite a few users utilising the mobile apps and its not giving the best user experience. PBX is running 67.0.6 (Debian64) (Aug 10 2021 14:30:04 Build), and the apps are all the latest versions. Any feedback/guidance would be appreciated. Thanks

Hi, Wondering if it is possible for FAX detection on an auto attendant to redirect to a fax extension?

Hey @GregV Thanks for the info. I had attempted to use the call forward no answer to return calls to reception, however, the feature sync would show an active call forward in the indication bar on the Yealinks - which just confused users. Sounds like I'll have to have a bit more of a tinker.

Hi Team, iOS users are able to manage the "Disable Calling the App" from within their mobile app, whereas Android users do not currently have this option. Can this please be added.

1gig seems a bit on the low side - we we're running with 4GB and it currently sits around 1.4gb First time it happened to us, the Azure VM just restarted itself and everything came back online. Second time we had to manually intervene. Since upgrading we haven't had an issue (still keeping an eye on it though) I'd suggest opening a support ticket - support.vodia.com

We encountered this issue a few weeks back - what version are you running? Upgraded to 67.0.6 and haven't encountered the issue again.

Any ideas? @Support

Hi, Following the documentation you referred to - I was able to obtain an Insights Insert key. Looks like these are handled @ https://insights.newrelic.com/ as they have not yet been added to the new dashboard layout. Vodia still doesn't pattern match the key. The issue I'm running into is that when Vodia attempts to post the data, I'm receiving a 403 forbidden response. From the Vodia log: POST /platform/v1/metrics HTTP/1.1 Host: platform-api.newrelic.com X-License-Key: **************** Content-Type: application/json nAccept: application/json Content-Length: 546 {"agent":{"host":"*****","pid":"pbxctrl","version":"67.0.6"},"components":[{"name":"*****","guid":"com.vodia.pbx","duration":***,"metrics":{"Component/Traffic/SIP[packets/sec]":*******,"Component/Traffic/HTTP[packets/sec]":*****,"Component/Load/Media[usage]":[***,***,*,**,****],"Component/PBX/CDR[units]":*****,"Component/PBX/Emails[units]":***,"Component/PBX/Uptime[sec]":*******,"Component/PBX/Minutes[units]":*****,"Component/PBX/Registrations[units]":***,"Component/PBX/Subscriptions[units]":****,"Component/PBX/Calls[units]":**}}]} HTTP/1.1 403 Forbidden Content-Length: 32 Date: Mon, 26 Jul 2021 00:19:17 GMT Content-Type: text/plain; charset=utf-8 {"error": "Invalid license key"} Looking at the Newrelic documentation - is the endpoint that vodia is using correct? Newrelic docs show the endpoint as: https://metric-api.newrelic.com/metric/v1 The docs also refer to the header value of "Api-Key" not "X-License-Key" Api-Key Yes Required. The Insert API key authenticates you to use the Metric API. If this is provided as both a header and a query parameter, the values must match.

Hi Team, As previously mentioned, the keys available from newrelic do not validate in the license key field. Over-riding the pattern match on the field to add any of the available license keys from new relic also does not work. Any update/feedback on how to get this to work?

@Vodia support Any update on this? Would really like to start monitoring our servers.

Even tried to remove the pattern match on the field to add the licence key. Still no good.

@Vodia support I have tried every key that new relic has to offer from the portal and none validate in that field. I have setup keys using all key types (User, Ingest - License, Ingest - Browser) and none work.

Nope - I've even tested with the reminder timer set to 5 seconds with voicemail default.

Hi Team, We've run into a few issues and are wanting to setup external monitoring on our Vodia servers. I can see that there is a section to input a new relic license key? Can you provide some further information on how to setup the new relic integration?

Probably a poor choice of words on my behalf. Transferring a call to another extension. If they start an attended transfer via a BLF key and hang up before speaking to the other extension, it gives the appearance of a blind/cold transfer. In this case, the transfer reminder doesn't function and the call would hit the receiving extensions voicemail. In some cases, users would want the called returned to the extension that transferred the call instead of an extensions voicemail. Currently, the transfer reminder will work on the yealink handsets if you specifically use the B.Trans key - but trying to explain to a user that they have to press 3-4 extra keys to transfer the call blind rather than pressing the BLF key doesn't get received well.

Have another customer that has raised this same request. With the default config, the handsets (Yealink T54W) will complete a BLF transfer as an attended transfer. They want to be able to press a BLF key to initiate the transfer then hang up. Is there anyway this can ringback to the reception handset should they not pick up the transferred call? This customer previously had an iPecs which worked in this manner.

You cannot CSV upload the category field - which is a bit of a pain. I'm unsure of how you would utilise this? Doesn't look like it would help. We have a customer that owns multiple unrelated businesses. Each has their own address book. Perfect world - it would be great to be able to create multiple address books per tenant. Set one as default, then add others and have the ability to select the relevant address book on a per extension basis. Or even add a relationship to a department or building - and if an extension is in that dept or build, have an option to display dept/building address book entries.

Hi Team, Wondering if it would be possible to have an address book based on a department? We have a couple of clients that have multiple sites and their address books are not the same across all sites. Thought is would be a good option to be able to specify a Department and/or Building to specify an address book? Or a way to add multiple domain address books and select which one the user sees from the admin portal?

The problem I have is users completing a blind transfer by pressing the BLF key and hanging up. Asking them to press transfer and b.trans would be an issue.

At the moment, we have chosen not to display the DID management section to users. Which is a shame - I'd prefer to have them see DID management and use it - just restricted to their own numbers. If you could work on having the option to link a DID to a domain to achieve this - it would be greatly appreciated. Linking a did to a trunk makes sense if you are running individual trunks per tenancy - but we are running a call termination service as a global trunk. We have a few customers that have a 10 or 100 number ranges - I'd love to be able to assign all their DIDs to their tenancy and let them self manage.