Jump to content

Vodia PBX

  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender

Recent Profile Visitors

193,835 profile views

Vodia PBX's Achievements

Grand Master

Grand Master (14/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare
  • Week One Done Rare

Recent Badges



  1. You can also take a look at https://doc.vodia.com/docs/click2dial (the pbxcall element) if you have control over the web server.
  2. Now that 68 is out of the door its time to look into the topic. The new GDMS is much better structured. Our worry is that we need a co-existance—rumor has it that older devices are not going to work with the new platform, is that true?
  3. The browser is easier to control the app. At least we are able to clear the cache and make sure that everything is up to date. We are changing that in the Windows app as well, but its not so straightforward. The email that the PBX sends out should be the confirmation on what as been sent. Are you saying what the FAX receiver has is different from what's in the confirmation email?
  4. Trying to understand what the problem is... So when a call comes in on the iPhone, I'll kill the app? That did work as it IMHO should on the iPhone, though the caller still hears ringback but it will eventually then go to voicemail?
  5. Turns out it did not make it into the build... Please try one more time.
  6. That should be resolved in the next build (68.0.1).
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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?
  • Create New...