Vodia PBX

Check if they support RFC 3546 (Server Name Indication).

You could assign the star code to do a "login all" (*64) to a button as speed dial?

Wir müssen das einfach ins Drop-Down übernehmen. Dann sollte es sehr einfach sein, die ISDN-SIP-Umstellung hinzubekommen :-)

Wir haben den Trunk mit einem T-Entertain Anschluss ausprobiert und nach einigem hin-und-her zum Laufen bekommen. Eines der Hauptprobleme für uns ist dass wir das nicht von ausserhalb ausprobieren kann, sondern nur mit einem T-*-Anschluss (Deutsche Telekom bietet das nicht in Boston an). Am besten wäre es wenn wir mal über HTTP einen Zugang zu einer 58.2 und einem T-SIP-trunk bekommen könnten...

Is this for the administrator or for the user? In the domain view, even if password changes are generally turned off, the admin should still be able to change them.

Yea, the new import is really just about extensions. The critique on the old way was that it was very difficult to use, so the new one now has a preview and it should cover the most used case: bulk import of extensions correctly. Usually there are only very few ACD or AA to set up, so going through the interface is usually not such a big deal.

Ok if you have already enabled the accept redirect you should be half way there. The PBX now needs to know what dial plan to apply (who should pay for the call). What you can try here is to assign an extension the caller-ID that the speech server is using (as addition alias name, e.g. "40 +16171231234"), even if just for try. If the SIP INVITE shows in the From field a number that is found in the domain, it will use that extension for the dial plan and then the call should go through. If that is working at least we should know what knob to turn here.

That should in theory work. It is important that the client tell the PBX what domain to use, that is done with a TLS extension in the client hello. I would first make sure from a regular web browser that the PBX presents to the browser the right certificate. If that works, there must be a problem with the phone. Otherwise there must be a problem importing that certificate, for example the domain name does not match exactly the name in the certificate.

You must enable "Accept redirect" for that trunk. The MS server uses those redirects; by default they are not permitted. There are a couple of posts for this topic already on the forum and also in the Internet. Try searching for pbxnsip and microsoft speech server and also microsoft exchange and sip, this will show you a couple of more results on the topic.

I assume that you have provisioned the phone? Did you make any changes to the ringtones.xml file? Ultimately it would be great if you can get closer to 58.2; a lot of things have been improved for snom phones.

In theory if you select TLS as the default transport layer (either on system, domain or extension level) you should end up with TLS also on the Yealinks. You should be able to see that in the files generated by the PBX. You might want to move to 58.2 as there was a bug in the Yealink template regarding the transport layer if I remember correctly.

We don't have any specific Bria LDAP implementation, but the general purpose LDAP server in the PBX should work also with Bria as much as it does with other phones.

The LDAP should also show the domain address book.

The latest version also supports searching accounts inside the domain. CSV upload for accounts is a difficult topic. What we need is a bulk import feature from lists; the previous web interface was productive, but hard to get the format right. This time we will try to have a preview and select the fields that should be imported.

Also you need to keep in mind that the client certificate authentication is not there any more, and you must open that extension up for provisioning (trust).

I would say 20 more problems solved so far; if you are on 58.0 (or 58.1) it is safe to upgrade to 58.1 now, though we will probably still do a couple of more fixes.

In 58 you can use any character.

Most mobile operators know that trick and will cut you off as soon as 60 seconds.

It is hard to have everything working 100 % with a from-the-ground-up new web interface. We have already fixed a couple of bugs in 58.1 if you want to give that a try.

58.1 is currently still work in progress. We are working on some rough edges, but should be safe at this point to use it. Maybe upgrade once more when it is finally done.

Can you get the INVITE from the old system that goes out to the telnyx trunk? Then we might be able to set it up the same way.

Seems you are right, those files did not make it into the release image! We'll fix that ASAP.

If the preview in the web interface looks good, then the SVG should be good. Otherwise make sure that you don't use compressed SVG (.svgz) files. You might have to clear your cache or try from another browser to see if the SVG really made it. The browser cache can be quite a problem, we had to find this out during our own testing (OK I see you figured this out yourself). SVG might seem on the bleeding edge of what is happening in corporate world, but we are convinced that this will be mainstream very soon. Logos look so much better with SVG instead of blurred PNG or even JPG!

No they have to be the same. This is so because when they try to log in, the PBX counts the number of digits and then tries to match them with a scheduled conference. Having different length would make that difficult (Impossible?).

The easiest is just to install a new PBX fresh from the web site, e.g. 56.0. Then stop the service, copy the working directory over from the old server (except pbxctrl.exe and pbxctrl.dat) and restart the service. Then you can log in, activate the license and make a software upgrade to the latest version e.g. 58.0.