Jump to content

ConwayTyler

Members
  • Posts

    3
  • Joined

  • Last visited

ConwayTyler's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • First Post Rare
  • One Month Later Rare
  • Week One Done Rare

Recent Badges

0

Reputation

  1. @Vodia PBX Thanks for the reply, that makes a lot of sense. I dug through some of the Electron docs and I think you're right about it being related to notifications. Do you know what build of 69.1.4 a fix will be available in? I'm on the build from Nov 30 2023 14:04:04. I re-tested this and the app is definitely interpreting Windows dismissing the notification as a user rejection. On Windows, if you go to the settings app and then ease of access, you can change the duration of time that Windows shows the notification for. If I change the value to 30 seconds as in the screenshot below the App on Desktop works as expected for me. I think this might be a good workaround until a more permanent fix is deployed for the app.
  2. Hi all, Since we're getting crickets from support on this still aside from chasing the "update to the latest version", we updated to 69.1.4 and verified the latest app from the Microsoft Store and retested. I decided to do some further debugging on my own, and here's what I've got. The scenario is someone dials into a DID, which is mapped to an AA. The caller dials my extension, 1119, and is then transferred. I get two rings, and everything is expected up to this point in the logs: POST /rest/user/1119@somehost.somedomain.com/calls HTTP/1.1 Host: somehost.somedomain.com Connection: keep-alive Content-Length: 49 Accept: */* Accept-Encoding: gzip, deflate, br Accept-Language: en-US Content-Type: application/json; charset=utf-8 Cookie: session=xmkewf0yyhq8h9fx4nm7 Origin: localhost Sec-Fetch-Dest: empty Sec-Fetch-Mode: cors Sec-Fetch-Site: cross-site User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) VodiaPhone/5.1.1 Chrome/91.0.4472.164 Electron/13.5.0 Safari/537.36 [8] 23:59:24.637 REST: POST /rest/user/1119@somehost.somedomain.com/calls {"reject":"ce3edcaf-5b9a-4ffd-8ff6-a323d6cfc861"} Huh? What the heck? The desktop app is sending a call reject. The critical line here is: [8] 23:59:24.637 REST: POST /rest/user/1119@somehost.somedomain.com/calls {"reject":"ce3edcaf-5b9a-4ffd-8ff6-a323d6cfc861"} So, what happens next in the logs? The call rings out until voicemail picks up. To double-triple verify what was happening, I ran the Vodia Desktop app with electron debugging and extracted the post requests into HARs, which are attached. Sure enough, the app on my Windows machine sends rejects without interaction from me. har.txt
  3. Same issue as 69.1.2, support keeps trying to close the ticket. Hope it's resolved in 69.1.4
×
×
  • Create New...