Jump to content

Vodia PBX

Administrators
  • Posts

    11,042
  • Joined

  • Last visited

Everything posted by Vodia PBX

  1. It depends on the phone type. Some phones support it (e.g. snom) and others don't.
  2. There were several discussions here on the forum and also talking to clients. What seems to be clear is that we need to split the flag weather to call the "app" into weather to call the "mobile app" (which would be iOS and Android) and weather to call the "desktop app" (which would be Windows, MacOS and browser). That seems to fulfill the requirements and expectations from the users.
  3. That was and is the correct way. However due to the expiry of the LetsEncrypt certificate last month and many snom phones running firmware that don't have the new certificate there is a lot of trouble in this space. Can you check if the records in SRAPS are like what you would expect? Also, can you check if the firmware that you are using on the phones is recent?
  4. Vodia PBX

    MacOS App

    The MacOS is brand new... I would expect a few weeks until the rough edges are gone.
  5. Hmm, Going through my check list: Making sure that your root CA list is update (might have to press the Reset button at the bottom) Make sure your license is current, maybe make sure that you are in a recent (I would say anything above 67 should do) Make sure that port 80 is open Make sure that the DNS A address points to your PBX Make sure you are not using DNS for ACME challenge (unless you are using dnsmadeeasy, but even that could be a problem) Rename the domain address, then wait a second and rename it back
  6. T42U and T58W are already on the list. We'll add the W79P, W76P, W73P however because they have not buttons like the desktop phones, this is just having them in the dropdown but they should also provision properly. W90 was also already there (DM).
  7. Its in "thought" stage. We have a few hardcoded flags like for handling trunks, but eventually we need something similar like the groups in the tenants.
  8. Yes that looks okay. We still have the topic of the buttons which is another tricky area with the Grandstream phones (every model seems to have their own PXX values ) and for that we would have to change the models.js but lets do one step at a time...
  9. As for recording there is no need for *93 or *94, you can use the button for that (it even starts blinking when recording is on).
  10. Hmm, it's not clear when the wss://user:pass@domain URI will work, but it's probably not a good idea to rely on it. But for sure setting a cookie should work. That means you'll need a step before opening the web socket and fetch the session cookie first using /rest/system/session like you would login from the welcome.js code.
  11. According to https://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api you should be able to use the username and password in the URL and this should just work?
  12. Hmm that might work depending what you use (e.g. C#, JavaScript). On the protocol layer, there needs to be an Authorization header with Basic authentication that contains the username:password (no tenant name there) and the Host header needs to contain the tenant DNS address.
  13. If all does not work, rename the DNS address of the tenant and then rename it back. This should generate a fresh certificate.
  14. Yes its possible, but not easy. You need to change the pop_grandstream.xml file and then add a new entry for the new file. The new file must be in the file system because there is to existing file built-in. If you put the pnp_grandsteam.xml into the file system as well you'll need to restart the service to have the PBX pick up file changes.
  15. I don't know... What is your expectation regarding WhatsApp? Does it ring only when you have it open? How do you know that someone wants to call you? LOL should they call you on GSM first? Or am I misunderstanding something here.
  16. It's not outrageous, if you really have a case where there are a lot of redirections the value of 10 might be indeed too low.
  17. So in a nutshell, you want to show the early state for all calls unless they are talking to an agent?
  18. Well there is a global setting called max_loop that you could increase. You can do this in /reg_settings.htm by clicking on the edit symbol in the header without having to edit the pbx.xml file and restarting the service.
  19. You can try version 68.0.3 if it works for you. That one should have the cipher.
  20. Try to set the transport layer to TCP and reprovison the phone. Maybe you try TLS and the phone does not like the certificate of the PBX. You would see that actually in the log if you turn pin the log level for TLS, however its very noisy.
  21. Well in that case as a first step I would turn the SIP logging on (possibly just filer by the IP address of the phone if possible) and see first of all if there are any packets and if yes, what the PBX response is. Maybe there is just a codec mismatch. But there should be some clue where the problem is.
  22. Can you call other extensions? Or the mailbox? Then the problem would be somewhere with the dial plan and the trunk.
  23. Are you using a ATA or the user front end?
×
×
  • Create New...