Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. Is there an option to not require to certificate verify?
  3. Today
  4. Yes, please take a back up and then upgrade. You can edit the link for 67.0 to say 67.0.4 for upgrading.
  5. Ok, do you suggest I upgrade to 67.0.4? Will that possibly fix the issue? I checked the settings in my Bandwidth account and everything seemed fine. And as I mentioned before, it was when I upgraded to version 67 that incoming SMS stopped working
  6. Depending where you are coming from you might have to change the setup on the bandwidth portal. They had an old API that was replaced with a newer one, which we are using now. We are now at 67.0.4.
  7. Hello all. Ever since I have upgraded my server to version 67, my inbound SMS service through Bandwidth no longer works. Outbound however works fine. It worked fine on version 66, and I haven't changed anything since then. In the logfile, it appears that the server is receiving the SMS message, but it's just not getting to the user from there. Here is what I see in the log file: [9] 22:03:28.554 Accept connection 105 from 52.72.24.132ⓘ [9] 22:03:28.554 Request /recvsmsⓘ POST /recvsms HTTP/1.1 Content-Length: 387 Host: 34.104.250.13 Connect
  8. The problem I have is users completing a blind transfer by pressing the BLF key and hanging up. Asking them to press transfer and b.trans would be an issue.
  9. Yesterday
  10. Guest

    Where is the TFTP directory

    Yes, I did try that. 1) I put http://download.fanvil.com/Firmware/Release/X4/20201027/x42.12.0.7275T20200914120531.z with AutoUpgradeInterval = 1 and EnableAutoUpgrad = 1 dont seem to upgrade. 2) What to do if you got different model of phone ? go down to a parent folder?
  11. If you're looking to update the firmware of the phone, then you don't need to do it via the TFTP folder anymore. You can simply navigate to the /reg_pnpparm.htm page on the PBX and add the URL of the firmware there as seen in the placeholder text.
  12. Guest

    Where is the TFTP directory

    I'm trying to deposite phone firmware in the tftp://xxx.xxx.xxx.xxx/pbx/tftp" folder. With TFTP software "filezilla". I need guidance. It's not working. please.
  13. Last week
  14. If you specify the field Extensions > " Explicitly specify pickup preference" with details of the extensions that you want to pick up the calls for. It will enable you to do so.
  15. Guest

    Call Pickup on Windows APP

    I should clarify. Without dialing *87. I'm looking for a way to either click on the call or drag and drop as long as I have the correct permissions. Similar to 3CX.
  16. Guest

    Call Pickup on Windows APP

    Is there a way to pickup a call ringing another extension from either the web app or windows app?
  17. We're currently looking into this and trying to reproduce this on our end so that we can identify the problem if any.
  18. Thank you. Even just an option to specify the delimiter or just leave out the spaces / hyphens would be ideal too.
  19. Thank you, I tried using CO-Lines but wasn't successful, and its good to know you are looking at retiring this option, as I don't want to build a setup around it if its going to disappear in future versions. The Domain level simultaneous call restriction is helpful when you wish to restrict a domain's total simultaneous calls, but not helpful if you want the Vodia PBX to move to the next option in the dial plan. It would be great to see an option to specify how many calls a trunk can handle at the trunk level in future releases of the product. In the meantime, might it be possible to ha
  20. Thank you for advising. Getting a carrier to change their ways is not easy, plus the ability to limit the number of calls in a trunk seems like a function that should be controllable at both the carrier and PBX level.
  21. Earlier
  22. You can use CO-lines with the trunk and set them to inbound and outbound only. That will limit the number of calls. That being said we have every intention to get rid of the CO lines because this is concept of the last century. It might make sense to add a setting to the trunk that just lists how many inbound and outbound calls are allowed. On domain level, we already have a limitation on how many calls can be on a trunk, however this now does not differentiate between inbound and outbound.
  23. In the next version we will use spaces. This is what pretty much the whole world is using today to make phone numbers readable. Except for USA, the area code also seems to be without parenthesis (and actually it often shown even if you are in the area). We'll have this "marinate" in the 67.1 build for some time and then we will eventually make this version 68.
  24. Currently, there are no ways of achieving that from under the trunk level itself, because that seems like trunk has higher authority on calling this in. But aren't there any settings on the trunk / carrier itself that will prevent this from happening? If the trunk / carrier stops playing the early media, will the error code be sent sooner in that case?
  25. This is a feature we're working on next. Will update everyone once this comes to life.
  26. What is the version of the PBX that you're on and the version of the App as well?
  27. Ohhh, this was only about the web display you meant? Functionality wise it wasn't causing us this problem. Also, we tested this on version 67.0.4 and even the display should be working fine. And we followed the same steps given on our documentation for disabling it too (the one that you mentioned here).
  28. To my understanding, on outgoing calls, the Vodia PBX waits for the carrier to either error the outgoing call or timeout before moving to the next dial plan option, if you have set Failover behavior to On all error codes. Some carriers play early media when call limits are reached on a trunk before sending the trunk an error code, thus the caller hears a message such as "All channels in use" before the PBX moves to the next option in the dial plan. This is confusing for the caller. It would be nice if we could set the number of concurrent calls that a trunk is allowed and thus if the maxim
  29. You can uncross your fingers Lyndon, I can advise that for me this worked ... its only just a little confusing that this Failover behavior option is located within Routing/Redirection section of the trunk which is predominantly to do with incoming call handling, though this is a routing thing so I guess it makes sense for it top be there Error codes from the carrier would generally be generated on outgoing calls which is what I wanted it for. i.e. when Vodia attempts to send a call out via a trunk and it cannot. Setting the parameter to "On all error codes" caused the system to move to t
  1. Load more activity
×
×
  • Create New...