Jump to content

Vodia PBX

Administrators
  • Posts

    10,084
  • Joined

  • Last visited

Everything posted by Vodia PBX

  1. That should be resolved in the next build (68.0.1).
  2. There was actually a glitch with the permission check for the logo which was too restrictive. This should be working now in 68.0.1. The new Windows app should be puling pretty much all content from the PBX, as if it would be a browser. The problem is that the cache cannot be refreshed like in the browser, and this seems to cause problems.
  3. The ringer selection should now be fixed. Also there was on the same form a glitch that the default IVR language had the wrong text (actually no text). We'll roll it out in the next few days with a 68.0.x build.
  4. We have started with the next version of the front end that takes such things to the next level. For now, the solution is to call the service flag. We'll see if there is something simple that we can include in a 68.0.2 build or so to have better control over the service flags.
  5. In the iOS app you can click on the record, then there is a "mark as read" entry. For the other apps, we'll add a drop down item that does the same.
  6. I guess you already tried to reload the page? Maybe clear the cache before that? Also, there is version 68 out that comes with a lot of improvements for the front end, though I am not aware about a fix that would affect the logo. But the upgrade to 68 would also help to refresh the cache.
  7. Ok can you please set the log level for trunk, IVR high and get a log. There must be some hint why it does not dial the number in the log.
  8. You can pick up calls from the list of extensions on the left. You'll need to be in a group that has the permission "pickup". Then the extension should blink and you should see the caller-ID of the call that can be picked up.
  9. Well maybe that is part if the problem that the PBX is not able to dial the number that you entered. Can you dial the number from the front end?
  10. You can open a ticket at https://support.vodia.com. Anyhow, it seems that the front end is doing something, it show the cancel button and a progress dot. That is usually a sign that the call gets started but the other side does not seem to have interest in switching to T.38. We are most probably talking about a problem with your service provider, not so much the front end. You could enable the PCAP feature on your SIP trunk and attach it to the ticket.
  11. I would not speculate if they would change their TLS setup (back). But I agree it's largely a waste of time unfortunately. The PBX needs to add at least one more cipher that they are using, so that there can be a common cipher. Its not a huge deal but it will require a new build. The good news is that it is very easy to reproduce the problem.
  12. That is weird. Can you open a ticket, maybe include a screen video and/or give the support access to try remotely?
  13. 68.0.1 contains some more changes and handles more situations where the other side does not start the T.38 renegotiation process, if you want to give this a try.
  14. There is also something at https://doc.vodia.com/docs/click2dial (second part) if you want to have a "mini-softphone" on your webpages.
  15. You should see a few dots appearing when you click on the send button. Did you see the video about this yet? This should show how it should work:
  16. Those 8 seconds are used after the call was already disconnected and the system is waiting for the final cleanup, e.g. the 200 Ok for the BYE message. There must be some other problem before the hangup. Maybe you can get a PCAP for the call?
  17. Can you check if you selected a device for the ringer (in settings)?
  18. Does inbound FAX work for this extension? Maybe there is no license for this? Or any other hint in the log?
  19. Please make sure that there is no plan assigned to that tenant. You can see the "plan" when you edit the settings in the system:
  20. Well it could "not locate server". Can you actually locate anything on DNS? E.g. can you refresh the license? You can also just set the DNS server manually in /reg_ports.htm e.g. to 8.8.8.8.
  21. Can you check if what is in the DNS cache (/reg_dns.htm) makes sense? Also you can turn the email logging higher to see if there is any communication with the SMTP server.
  22. In 68.0, you can also just use Basic authentication for setting up the web socket. Make sure that the Host is matches the domain name, and the username in the authorization header the extension. The password is the web password. This works only if there is no 2nd factor required for the login. Otherwise you'll need to set up a session first and then use the session cookie in the web socket request. Also I would turn the web server log to 9 which should provide more information what is going on.
  23. Hmm seems like you need to add this yourself for now—just open the inspector in your browser and add it to the id="page". We'll include it in the next build.
  24. Like all files served by the PBX web server, you can also redesign the file there (makecall.htm). You might also want to check out https://doc.vodia.com/docs/click2dial where you can use the pbxcall element. This is very useful when you users have to log in (e.g. into a in-house CRM system) and you want to offer clickable numbers.
  25. No real workaround. You could set up some PHP server that acts like B2B to take the request and then send it to telnyx but it would be easier if they just accept the AES-CBC cipher again.
×
×
  • Create New...