Matevz

Hi Team would like to update on this, there seems to be more issues: Sometimes I will get double toast notification on incoming calls, now the issue today is, there is no pop-ups on incoming calls on multiple workstations

Hi There we just moved to latest version and noticed that Incoming call pop up doesn't disappear after phone has been answered by someone else or has completed on another destination PBX v69.2.4 Windows app v.6.1.9 happens on multiple devices cheers Matt

thanks, will attempt latest version again, I can see windows desktop app is performing better now, so hopefully we can finally transition

Hi Team we have sold the PBX to one of our customers with hope CRM integration with Hubspot will work; however due to too many issues with PC softphone client on v69, we cannot upgrade our production server to that version. Any chance you could push update for OAuth and Hubspot integration to v68 so I can use this feture on your most stable Version 68.0.37? thank you

same issue with 2 clients running v68.0.37 had to move them to webapp

Thanks, have updated now to beta build, I can see you fixed date issue with timezone, which is great. Would be good to change format (not major) and match it to same one as on filter: Issue with notification is still present: I don't get double notifications now (I only get big one) but the issue is when clicking on it, it will bring client to the front, but it won't answer the call. Not sure about emergency calls as I reverted now to v68 (need to have a working PBX)

Hi Team emergency toast is not related to headset as it is happening with another user on Jabra. double notification seems to be completely random, some users will get it and some won't having more issues with extension busy, even though it app is running, sometimes calls will stay in the app and when you minimize and maximize it will refresh example, flashing dropped call: when switching to home tab it will go away We will run this version for another day, but will probably need to revert to v68 as this is still not there, definitely not ready for production cheers Matt

Hi can confirm emergency call is still happening. I think it is related to Headset as it only happened to 2 users in our organization who use Yealink Headset It immediately happened when I've connected headset to the app (not that this feature works though) console:

Hi There I did get 3x yesterday running 69.2.3 build, will monitor and report back if more appear. There are also other issues still: - Toast notification doesn't go away on incoming call, I would get 2 notification (one bigger and one smaller one); small one will go away and big one stays. Also when clicking on big one, nothing happens - when clicking on History tab, it is always a day behind, unless I open it after 12PM; we are NZ Time zone and this started happening after v69

Hi There had to move us to latest - 69.2.3 as push notifications broke on v68 and still no resolution, immediately after logging in I get same error message...

thanks for confirming this, my AU contact has escalated this already, but due to timezone issue there might be big delay on getting this working again... big issue as I have 2 customers who rely on this heavily and are now loosing business...

Hi Richard, yes exactly same error here. I've managed to get some calls through OK - 2 out of 10 so looks like intermittent issue got message back from AU contact at Vodia, his one is working OK, but he is running 69.2.3

Hi having same issue, not just IOS, also affecting android I suspect issue with Vodia Push server, have tried AU and US one (they are same) no luck. Can see: [9] 11:43:18.125 TLS: HTTP 138.197.53.25: Send Client Hello(030365F7..00020017) [5] 11:43:18.314 TLS: HTTP 138.197.53.25: Alert Fatal (2): Handshake failure (40) suspect someone didn't renew certificate? case logged, hopefully it can be resolved soon...

Hi There went to v69.2.1 today and immediately after logging in got a emergency call notification again log below: [9] 9:27:17.668 SIP: Send 72 bytes to 202.126.201.202:51840 [9] 9:27:18.376 WEBS: Request from 202.126.201.202:55352 for /rest/user/105@xxxxxo.nz/emergency GET /rest/user/105@xxxxxxxxr.co.nz/emergency HTTP/1.1 Host: xxxxxxxx Connection: keep-alive sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="102" sec-ch-ua-mobile: ?0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) VodiaPhone/6.0.9 Chrome/102.0.5005.167 Electron/19.1.9 Safari/537.36 sec-ch-ua-platform: "Windows" Accept: */* Sec-Fetch-Site: same-origin Sec-Fetch-Mode: cors Sec-Fetch-Dest: empty Referer: https://xxxxxsr_portal.htm Accept-Encoding: gzip, deflate, br Accept-Language: en-US Cookie: session=1n5a9qo39ptj163hfd42 [8] 9:27:18.376 WEBS: REST: GET /rest/user/105@axxxxxxo.nz/emergency [9] 9:27:18.376 GENE: Extension 105 as member of group Default has no permission emergency [9] 9:27:18.376 WEBS: REST: Return 403 Permission Denied HTTP/1.1 403 Permission Denied Cache-Control: no-cache Content-Length: 0 [9] 9:27:19.145 WEBS: Send websocket 79 other that than, click to dial - tel protocol in windows still doesn't work (mentioned in release notes) also when going to call history it is day behind every time you open it (I believe issue is with NZ time zone as we are a day ahead)

sorry, it is probably about 10th time I've went to v69.x and had to revert due to too many bugs on windows app... My office team is getting frustrated so will have to wait until the app gets fixed

same issue here, has been from the start of v69 overlap seems to be new feature of 69.2

Hi team have tested v69.2 a bit and getting some random pop-ups about emergency calls (on multiple computers) pressing any of the buttons will discard the notification and it will re-appear does look like it only started happening when enabling headset integration (yealink wh62) which still doesn't work cheers matt

as this issue seems to be resolved now, there are more issues with headsets dropping the calls, notifications for calls not coming through, failed calls... This app just doesn't get anywhere. Going back to v68, and seriously considering another vendor... It is too bad as I really like the PBX logic and setup, just softphone app never worked OK

Hi team I've had similar issue, where it will randomly stop ringing some extensions using softclient after couple of seconds. some members would ring for longer period, some will drop after couple of seconds. Running latest version 69.1.2 Have managed to resolve it with workaround by using extension through Chrome/edge webapp, but this way I've lost ability to associate app with tel protocol. Ticket is still open with support

Thank you, Anton, I am using Vodia app installed as Webapp (initially mentioned) as windows store one is causing issues, I haven't been able to resolve yet with support... Still unsure which way to go, use Windows store app or Webapp (chrome/edge), currently Webapp is performing a lot better for us.

Hi most of CRM and websites will integrate html code with phone number as clickable URL containing TEL protocol: When you click on it it will automatically launch the application which is associated in windows with this protocol (Skype, softclient, teams....) I know it is definitely possible with webRTC version (web app) - we have another PBX which can do this - when you login to the webrtc client it will automatically ask you to associate default tel protocol with the webRTC application on windows.

Thank you, that did the trick for me

Thanks for update. Will try to push clients more towards call queues in future. In regard to CDR report via email, it would be good to get this also fixed: Currently it shows ringgroup members instead of the extension that actually got the call.

Hi There trying to pull some info on call history on huntgroup (ring group) when I export the CSV it shows the active call on all agents that are in the queue, where it should show the person who actually received the call I know you can run daily report on ringgroup, but how would I get for example: how many calls extension 200 received (part of the ringgroup) in the last month? cheers Matt

Hi there I am trying to figure out where this settings, but when extension is busy/unreachable, when I call it I get the message: "we couldn't connect you to the extension, press 1 for callback" I don't want this option to be enabled as I want to just use voicemail greeting that is set in all options on extension I've got Mailbox explanation prompt - set to not on personal greeting and all options in files section are set to Greeting1 Where can this be disabled? works ok when extension is busy or no answer. This is cellphone extension and is unreachable when phone doesn't have signal or is off cheers Matt