Jump to content
Vodia PBX forum

Vodia PBX

Administrators
  • Content count

    8,975
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vodia PBX

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    https://vodia.com/doc
  • ICQ
    0

Profile Information

  • Gender
    Male

Recent Profile Visitors

190,557 profile views
  1. Associating certificates with domains

    Would that help much? In a multi domain environment you'll probably end up with the wrong certificate most of the time. The default is the server certificate right now (you can load wildcard certificates also into domains if they match).
  2. Logo Phone

    The PBX web interface will automatically resize the image to the needed sizes (there are more than one). When you drop an image, take a reasonably high resolution (e.g. 1024 x 768) so that the browser can down scale it (and not up scale it)
  3. Fraud Protection based on Rates / Billing

    There is a setting "Automatically recharge credit for domain" in the monthly billing section that can be used for that purpose.
  4. Associating certificates with domains

    Usually you can use a wildcard certificate as the server certificate that will match most of the domains (e.g. *.best-pbx-ever.com) if all you clients use domain names with that kind of name.
  5. SMS2Cellphone

    ACK will be fixed in the next build (58.4 we are).
  6. SMS2Cellphone

    The SMS feature should be described in https://vodia.com/doc/admin_messages did that help? Seems like you found it... You mean the JavaScript does not allow you to save it?
  7. Provisioning Username and Password

    Generally speaking, at least by default the PBX should never leak out passwords. However, you can (should) use the REST API for this. By default downloading passwords is disabled; there is a setting in pnp.xml called rest_show_passwords that you can change to true to make this possible. Then you can use the /rest/domain/<domain>/user_settings/<account> API call for this.
  8. Skype SIP trunk with TLS setup?

    The document is from 2011. Not sure if anything has changed since then? Maybe you can try to run a wireshark to see if there is even a basic handshake going on or the port is just not open.
  9. Text field instead of dropdown lists

    It is a trade off. We got criticized for leaving fields wide open, to the degree that customers don't know what would be reasonable values. Drop-downs solve that problem. In many cases there is no need for additional values. If there is a need for it you could customize that page and add the value that you are missing; however at the cost that you would miss future updates for the page. That's why it is better to come up with proposals for additional values that we happily include in the next build, so that everybody can benefit from it and that does not require you to miss out on future updates.It is a trade off. We got criticized for leaving fields wide open, to the degree that customers don't know what would be reasonable values. Drop-downs solve that problem. In many cases there is no need for additional values. If there is a need for it you could customize that page and add the value that you are missing; however at the cost that you would miss future updates for the page. That's why it is better to come up with proposals for additional values that we happily include in the next build, so that everybody can benefit from it and that does not require you to miss out on future updates.
  10. Deutsche Telekom - DeutschlandLAN SIP-Trunk

    Wir werden dann mal diese Zertifikate mit einbauen und das "DeutschandLAN SIP-Trunk Pooling" als Drop-Down einbauen. Dann sollte es einfach über Name/Password gehen und weniger als eine Minute dauern den Trunk einzurichten. Vielen Dank für die Pionierarbeit!
  11. CDR time differences

    TimeStart, TimeConnected and TimeEnd are always in GMT.
  12. Customize the Vodia 58.3

    There is a file helplinks.txt where you can set the links, also just the root for the help files.
  13. How to check if TLS is actually used on SIP trunks?

    The old snom phone models had a way to send sips Request-URI. Not sure if other devices or soft phones can do that today; but this is (IMHO) the way to tell the PBX that this call should be encrypted. The other thing that you can try is ZRTP end-to-end encryption. The PBX also supports that. But then both endpoints need to support this; for SIP trunks this will be very difficult. The VoIP security market is hard to understand. Lots of bla bla about VoIP security. We have tried a few things, even made our own firmware with ZRTP with elliptic curves for snom phone hardware; but the feedback was simple that there is no market for this at least from our perspective. The only thing that seems to sell are UDP-based SIP trunks. If you want to get all the traffic to a certain country, all you need to do is offer the lowest rates and users happily route all calls through your network, everything in plain RTP.
  14. Skype SIP trunk with TLS setup?

    They obviously don't advertise TLS. Seems they use also port 5061 for UDP, which might be a little but confusing; but it is only for UDP and it is okay. I would try setting the outbound proxy to sip:sip.skype.com;transport=tls and see what happens.
  15. SMS2Cellphone

    You can always add additional headers, even it if just the Authorization header. We even got MMS working this way (see https://vodia.com/doc/admin_messages)
×