Jump to content
Vodia PBX forum

Vodia PBX

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vodia PBX

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

192,190 profile views
  1. It really depends on the device. On mobile phones and soft phones fortunately nobody yet had the idea that the app has to start dialing without pressing the enter button. What you enter is what you dial. The PBX will look at the country code and then convert the number into the +-format. On desktop phones there is still that desire that the phone will start dialing by itself. This is similar to the desire to press a 9 to start making a phone call. IMHO this is very confusing and there is no more need for that on practically all VoIP phones. Asking users to dial 9911 instead of 911 is now illegal in many environments. The easiest on VoIP phones it to tell users that they can dial the number just like they dial the number on their cell phones. Usually 99.99 % of the users get it immediately and will never look back. For analog devices like old FAX machines and legacy phones there is still the problem to determine when the number is complete. The easiest is to use a timeout which is okay in many cases because there is no human operating those devices any more or ask them to terminate their number with # instead of the enter button. Rotary dialers are not used any more. Yay!
  2. Looks like this is a TLS problem. We did have a problem some versions ago when the email server (especially Microsoft servers) were requesting a client certificate - the PBX would actually send it however the server would not like it. We fixed it also on the 64.0 branch. I would turn on TLS logging to see what is happening.
  3. Maybe this topic is drifting a little. Maybe the Pi build is not up to date for the showing of the QR codes in a single page. Sending a QR code out will be in the next version (65). Regarding the email example - many users have only email in their smart phone. How are they supposed to use the email?
  4. We don't have plans right now but it does sound interesting.
  5. /9 is unfortunate - we have only /8 and /16 which would mean that you would have to add 128 /16 blocks. Alternatively you could white list the /8 block, which would white list more addresses that you would actually need. If you want to do this in JavaScript, here is the code: for (var i = 128; i < 256; i++) fetch("/rest/system/access", {"body":"{\"ip\":\"166." + i + ".0.0\",\"netmask\":\"16\",\"type\":\"true\",\"comment\":\"Whatever\"}","method":"POST"});
  6. We have the QR code ready - however still struggling to understand how you would that email in a smart phone unless you have a mirror for taking the photo. A link to the play store with the credentials in it might make more sense - we are investigating this as well.
  7. 1) We had that in an older version and will bring that back 2) Usually you dial 00 or 011, but this is a good point 3) You can redirect users into conference rooms (even through attended transfer); we will sugarcoat this eventually. Hosting an audio conference on the phone itself is usually not a good idea. 4) Yes that is another topic that will eventually be available.
  8. 1) That is why they can enter it directly into the web interface - stripe takes actually care about the CC number and the sensitive information and this information never hits the PBX or any of our or your servers. They can also enter it into stripe.com however this is not easy. 2) That is true. One solution could be to lock everything down, so that the may be able to see e.g. the call logs, but make no changes. 1) You can do that, however this would require that you set up another web server. With the REST API you can set the stripe subscription ID into the PBX, so that the PBX can check if the subscription is still active and e.g. shut the domain if that is not the case. Might be interesting for the automatic charge function when their prepaid credit falls below the reload number. 2) That would be just a simple change of the template for the billing page (dom_billing).
  9. I agree one avenue is to do this locally on the phone. This will give you 100 % control. Try to use the snom general parameter, then you don't have to change the template for provisioning. And if you have to change it, change it only for this extension. The other thought is to set the extension to type "hotel room" - this also limits the features and you can e.g. define if rooms are allowed to call each other directly.
  10. There is a list of SIP User agents that are rejected - this should include SipVicious. Another simple thing you can do is to give the PBX a real domain name (not "localhost") and then block any request that does not match the domain name. This is a little bit like a password that can very effectively block such attempts. This makes a lot of sense if you are on public IP.
  11. The default behavior is not to hang up. Which is kind of reasonable - especially a short timeout would be unreasonable.
  12. That would be a scenario where something fishy was going on - for example a device was trying to start a call but could not get past the authentication phase. If the IP address of the source was blacklisted because of this the admin would get an email notification about this (important) event.
  13. Ahhh yes very good point. We have the same problem when all agents are suddenly logged out. We will add something that will do the redirection also to the calls that are queued up if the redirection flag is set.
  14. We have that problem in many places of the we front end and we are aware that this is an issue. Default so far means "reasonable" - if you want something specific you'll have to select it from the drop down.
  15. In the redirection settings (night mode) for the ACD there is a dropdown called "No agent has phone registered" - just use that one. You can use the mailbox prefix (usually "8") to send the call directly to the mailbox without ringing the extension.
  • Create New...