Vodia PBX

There were some people using Microsoft Speech Server some time ago. This was in the age of OCS, The setup was not straightforward, but it did work.

The other workaround is to get the ics from the PBX web site, so to add it to your personal calendar. Then you can add whoever you like, without the PBX being involved.

Yea that version still had some issues with the JavaScript translation. I believe we have that now under control, next version will look better!

There is no information in the trunk about the account. That may be okay, but then you should not send anything in the P-Preferred-Identity. You will easily in the INVITE packet that something is not right.

Previously the audio files landed in the audio_moh directory, overwriting whatever was there. This is not good, considering that there may be multiple tenants in the system. 5.2 will have the possibility to finally upload music on hold audio also in domain mode.

Maybe just open a ticket and give us access to the system; then we'll do it for you.

For that I would choose the gateway mode. You can also explicitly list the IP addresses where the trunk sends SIP packets from, if they should be different than the outbound proxy address. The IP replacement will work only if your firewall is configured accordingly. Inbound packets to port 5060 must be forwarded to the host (172.31.13.89).

To answer the original question: Yes that's possible in 5.1.3. The feature comes from the branch office area; but at the end of the day a branch office is also nothing else than a trunk.

There is a flag "Change names in To/From-headers" in the domain settings, which can be turned off. Also there is "Send P-Asserted Header in calls to extensions" which might also help. Though honestly I don't know in what exact shape these flags are in 5.1.3 are; they have a long history.

We'll do the complete change log with the release. We had to change the login.htm to welcome.htm because if you have made changes, you would not be able to login to the PBX any more... The new login makes it possible to stayed in for weeks, which is important in case you are a call center agent and dont want to get logged out all the time. Also we have changed the branding to be vodia.com. New feature is a "wall board" for agents, so that they can see which calls are coming in, and how the ACD did so far during the day.

We have made a new build for Windows, Centos64, Debian64 and also the new Vodia mini. Before we can release this as the new 5.2.0 version, we are looking for "volunteers" to try this out, especially on Windows 64 and 32 bit. If the upgrade works at all, it should be the best version ever. However we had problems with the new runtime environment in Windows, and frankly we were not able to test this on Win32 systems yet. Please make sure that you backup the working directory before doing this. The link is http://vodia.com/downloads/pbx/version-5.1.3d.xml; you must upgrade from the web interface because we introduce some new files that must be loaded into the working directory.

We have changed the strategy for Caller-ID. Instead of using the INFO messages that were pretty much special for snom phones, we use the P-Asserted-Identity now. This seems to work with all phones that we could test, including snom phones at least with a newer firmware.

Ouch.

In Windows we are in trouble right now because we have a new tool chain. If you want to get it working while we are trying to figure out what is happening, you can manually install the redistributables from http://www.microsoft.com/en-us/download/details.aspx?id=40784; then it should work.

Well apart from that, those messages are sent for a reason. If the address changes, there is a blind spot where phones cannot be reached. I know that in Germany and also other countries like Taiwan, because of the shortage of IPv4 addresses, service providers keep on changing IP addresses at night. If it happens really in the middle of the night, it should be fine as long as nobody makes phone calls during this time. Also seems like Outlook cannot have rules that apply to certain hours of the day . Can't wait to see IPv6 being rolled out to the mainstream, then those problems will disappear!

http://vodia.com/dow...sion-5.1.3d.xml now should have the redistributable.

Click in admin mode on "translations". There you can turn the editing on. If you are serious about making improvements, let us know your activation key and we'll add you to the list of authors!

You can check in the file system the dial plan entries. They are in XML spaghetti, but still readable. Also double check the text mode representation of the dial plan. If the XML database in the file system got screwed up, this is usually because the PBX could not write new records. Most of the time this happens when the file system is full.

For Win64, try http://vodia.com/downloads/snomONE/version-5.1.3c.xml not sure if that works for Win32

You should use the Callcentric setup from the trunk setup drop-down, then you can also define where the call will be terminated.

Ja das dürfte inzwischen ein Klassiker sein. Die meisten SIP-Trunk Anbieter erlauben es nicht dass eine Nummer angezeigt wird die nicht zum Anschluss gehört. Z.B. könnte man da ja die Rufnummer von Angela Merkel (soweit bekannt) anzeigen lassen, obwohl sie gar nicht am Telefon ist. Um das sicher durchführen zu können, muss der Anbieter wissen woher der ursprüngliche Anruf kommt. Wir verwenden dazu den In-Reply-To Header (RFC3261); aber wie gesagt das wird nur von ganz wenigen Anbietern unterstützt.

You can do that in the PBX. For example, see this: http://wiki.snomone.com/index.php?title=Logging_SIP_Settings

The PCAP trace that the SIP message flow is fine, no interoperability issue. There must be a timeout set either in the trunk (failover after 30 seconds?) or maybe a redirection settings in on of the extensions. I would double-check the trunk. There should be also something in the LOG.

Those scanners try out various accounts. Having found the PBX does not mean that they have found a valid account of the right password. They will probably keep on scanning for some time. But if you don't use the name "localhost" it will be difficult to find a valid account and domain name unless there is a human involved that knows what domains are being hosted. And choosing a good password will make it very hard to find valid credentials. On the PBX side (now called Vodia PBX). Setting the outbound proxy or listing the IP addresses makes sure that the PBX associates only those addresses with traffic on that trunk. Unfortunately the IETF was envisioning that anybody could call from anywhere (ENUM), and we still have that in the product if you leave the outbound proxy open. A JavaScript warning should pop up if you do that.

Hmm. Do you have the INVITE that is being sent to the SPA in this case? Especially the From-, To- and possibly other headers lie P-Asserted-Identity.