Vodia PBX

Yes you can use a separate DID for each domain (in the latest build you can even use a separate provider for each domain, which also means that you can use separate credentials). That will naturally separate accounts a little bit.

We have no bias for specific vendors. Our main objective is to make sure that our partners give the user the best phones for their environment if possible. "Best" can mean a well known brand, it can mean CAPEX or it can mean OPEX (usually OPEX is more important)—which is essentially how much work it takes to install and run the phones. We do support Grandstream phones. They have a very large product range, and it can be challenging to keep up with their weird way of numbering settings. The relatively new series GRP26xx is a sign of hope because the abandoned the P-values and use "readable" names for the settings. We hope that newer models will support these settings, which will make future integrations easier. For example for Yealink, despite the large range of supported phones, everything can be maintain in one template. Also, Fanvil has recently added great new devices which we support well. As for branded phones, there are Cisco 3PCC phones which are well known for end users and which sometimes makes a sale easier. Also Poly(com) phones have a very good reputation especially in the USA. There are also other great brands for certain countries, e.g. Gigaset, Snom or Auerswald in Germany. We do our best to support a large range of features on those devices. There are also other vendors like Panasonic where the brand name still is very strong but with an aging portfolio. Some clients insist they want to keep their phones, and in that case we support a basic feature set so that those phones can still be used.

Is there a way to add a tag to the Twilio API call? Then adding a tag, e.g. the domain name would be very simple.

There are two things: Being part of a ACD and being logged in. The login in and out can be controlled by the user. But being on the ACD must be controlled by an admin. There is a list who can add themselves to a ACD ("jump in"). In order to do that, the agent needs to dial the log in star code—the logging in also takes care about adding the agent to the ACD.

Sometimes the problem is that the OS is too old for the play store. In that case you could try to manually install the APK. Then updates would not work any more, but at least you could use the app with that version.

The 66.0.6 version was a little bit soo sensitive for the number of connections. Its okay to disable that for now (later versions are working better where you can turn this on again).

You can select your "favorites" in the Windows app. This is a little bit like the BLF buttons on the phone. If you want to log in or out, you can click on the ACD tab where you can log yourself in and out (and others if you are the manager).

We are working on that one.

If this is Android 10, this should work in theory. Are you able to install the app from the Google play store?

Ich würde auf jeden Fall erst mal die IO über den WAN-Port mit dem Internet verbinden und dafür sorgen dass da eine aktuelle Version läuft (66.0). Dann sollte einen Eintrag beim Thema DSL geben wo man die Telekom auswählen kann. Es gibt aber bei der Telekom Anschlüsse, die gehen nur mit den Geräten von der Telekom (Huawei OEM). Die werden dann auch nach vielen Stunden nicht funktionieren. Diese Anschlüsse gehen dann nur über den LAN-Anschluss an diesen Telekom-Geräten. Das ist zwar dann doppelt NAT, sollte aber trotzdem problemlos funktionieren. Wichtig ist hier dass die Subnetze sich nicht überlappen dürfen, also z.B. 192.168.1.x und 192.168.2.x oder besser 192.168.1.x und 172.16.1.x.

Thanks so much! If you like try the latest 66.0.7 build.

According to https://cloud.google.com/speech-to-text/docs/languages "it-IT" should be correct?!

We actually made a new version that should handle the certificate situation better. You might have to delete all Root CA and reset them. Enabling the API is not very straightforward, we also needed to tinker with the Google console to get it working. The response in the PBX log for web client usually provides some useful tips from Google what needs to be done.

We have a few improvements int the pipeline for the callback. However they are not done yet.

Ok after some digging it seems that the problem is that the GlobalSign certificate which expires at the end of the year is not part of the standard certificate distribution any more. But it seems of you manually import it into the PBX, it will work: -----BEGIN CERTIFICATE----- MIIDujCCAqKgAwIBAgILBAAAAAABD4Ym5g0wDQYJKoZIhvcNAQEFBQAwTDEgMB4G A1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjIxEzARBgNVBAoTCkdsb2JhbFNp Z24xEzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDYxMjE1MDgwMDAwWhcNMjExMjE1 MDgwMDAwWjBMMSAwHgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMjETMBEG A1UEChMKR2xvYmFsU2lnbjETMBEGA1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZI hvcNAQEBBQADggEPADCCAQoCggEBAKbPJA6+Lm8omUVCxKs+IVSbC9N/hHD6ErPL v4dfxn+G07IwXNb9rfF73OX4YJYJkhD10FPe+3t+c4isUoh7SqbKSaZeqKeMWhG8 eoLrvozps6yWJQeXSpkqBy+0Hne/ig+1AnwblrjFuTosvNYSuetZfeLQBoZfXklq tTleiDTsvHgMCJiEbKjNS7SgfQx5TfC4LcshytVsW33hoCmEofnTlEnLJGKRILzd C9XZzPnqJworc5HGnRusyMvo4KD0L5CLTfuwNhv2GXqF4G3yYROIXJ/gkwpRl4pa zq+r1feqCapgvdzZX99yqWATXgAByUr6P6TqBwMhAo6CygPCm48CAwEAAaOBnDCB mTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUm+IH V2ccHsBqBt5ZtJot39wZhi4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5n bG9iYWxzaWduLm5ldC9yb290LXIyLmNybDAfBgNVHSMEGDAWgBSb4gdXZxwewGoG 3lm0mi3f3BmGLjANBgkqhkiG9w0BAQUFAAOCAQEAmYFThxxol4aR7OBKuEQLq4Gs J0/WwbgcQ3izDJr86iw8bmEbTUsp9Z8FHSbBuOmDAGJFtqkIk7mpM0sYmsL4h4hO 291xNBrBVNpGP+DTKqttVCL1OmLNIG+6KYnX3ZHu01yiPqFbQfXf5WRDLenVOavS ot+3i9DAgBkcRcAtjOj4LaR0VknFBbVPFd5uRHg5h6h+u/N5GJG79G+dwfCMNYxd AfvDbbnvRG15RjF+Cv6pgsH/76tuIMRQyV+dTZsXjAzlAcmgQWpzU/qlULRuJQ/7 TBj0/VLZjmmx6BEP3ojY+x1J96relc8geMJgEtslQIxq/H5COEBkEveegeGTLg== -----END CERTIFICATE----- Obviously, it is only a question of time until Google changes it. Hopefully they don't forget .

If you like, try the latest 66.0.7 build this should include a new setup for easybell. You'll have to set up a new trunk though.

Yes absolutely. The PBX (in recent versions) requests only RSA certificates, not sure why Google sends the ECC certificate. That should be the case for PBX versions built after November 19. What build date are you using?

What you can do is for the single number account just assign in the trunk settings where to send the call to a specific account: For the multiple account trunk, in Germany usually you can just look for a prefix: For example if you have number 0305550..0305559 you could use 555 as the prefix and then assign 0..9 to your extensions and accounts. We'll make an update for easy bell so that this weird 00 or not behavior automatically gets resolved.

I have the feeling that Google uses a different server setup in Europe than they do in the USA. You can easily check what they send by using the browser to https://speech.googleapis.com and then inspect the certificate (ignore the 404 not found):

We support easybell for some time. What they are saying is they are contacting whatever was provided in the contact header for a single line account (which makes a lot of sense) and the E164 format if there are multiple numbers. It would make sense to use the E164 format all the time, including in the Contact header. You can set the contact header explicitly for the trunk to the E164-formatted number—would that solve the problem in all cases (and set the number interpretation for the trunk to E164)? If yes we could change the template for easybell and make this the default for easybell. The alternative would be to have the PBX look at the To-header, and not the Request-URI for an incoming call.

Can you try 66.0.7?

Yes there are some providers that can't keep the same format even in a single packet. In order to handle this we need to add that provider to the drop down list with a script code that digs out the relevant information. What provider is this?

... or just wait a little until the next version is out where we have some easier way of uploading the ringtones.

Is the PBX on public IP or in the LAN? In any case I would get a PCAP https://doc.vodia.com/pcap and see what ports are advertised by the PBX and in what direction the RTP/STUN/DTLS packets are sent.

If you have previously turned on translations the PBX will not get updates for new translations. You can delete the dict.json file in the PBX directory if you want to revert to the built-in translations (which I would recommend unless you really need your own translations). It is a hidden feature for a reason.