Vodia PBX

ACK. This was caused by some internal "optimizations" for the database. Will be fixed in the next release. We'll try to make a build later today for Centos32.

We have changed the login procedure. Now you can really stay logged in and also the login in controlled by REST/JSON. Anyway, we had to rename the file to make sure that everybody gets the update. Otherwise you would get locked out from your PBX! We forgot to reflect the chance in the reg_texts, but you can edit that template yourself and change login to welcome. Then you can start editing that file as usual.

Hmmm. We did not change anything in that area AFAICT. I guess we need to test this.

You can use the http://vodia.com/downloads/pbx/version-4.5.1.xml to upgrade to the last version that was made for version 4. I know on the SoHo is is not so simple, but do make a backup of the file system before attempting this update from SSH. From 4.3 to 4.5 is a big step, and you want to be sure it is not a one-way street.

Is there an overlap of extensions? For example, if you have an extension 20, then you will not be able to reach extensions with number 201, 202 and so on.

What version of the PBX are you using?

Well, how can the PBX help here. This sounds like a problem with the user interface of the phone. When the user presses a button on the phone, this does not mean that the PBX receives a message. Actually the PBX only gets the result of the transfer (or hangup) request. Maybe you can try a different phone type to see if the behavior is different/sufficient.

For transfers it is really a tricky topic what to show. For the web interface, I think it is reasonable to just show the caller and the called party. We have added a very detailed new record type for those who need to know the details, which can be pushed out by HTTP/JSON. It will require an external server to pick up the CDR; but they will contain really everything.

There were some hiccups over the weekend with missing files and installers that were not up-to-date. Hopefully we are in smooth water this week with the upgrade to 5.2.

Please note that we have moved the web files into a separate file, pbxctrl.dat. The file name starts with pbxctrl, because some older versions especially the snom ONE mini erases all files that don't start with pbxctrl. This makes it a lot easier to do the builds for the various platforms that we have accumulated over the time. If you perform a "manual" upgrade, you must also download that file. The best solution is to make a file system backup, and then upgrade the system from the web interface (see http://www.vodia.com/documentation/admin_swupdate). The XML file should contain everything you need for a successful upgrade.

Although I don't know why it would make any difference between 5.1.3 and 5.2.0, we also ran into issues when selinux was installed.

Well do another upgrade to 5.2.0, something went wrong with the build. Sorry.

Sorry we forgot to include the pbxctrl.dat in the install script... Should be fixed now.

Not yet. Just something to have something at all.

Did you use webmail.lync.io or http://webmail.lync.io? If you put in an address, it is supposed to be a URL

It is a difficult topic. The only common denominator seems to be MP3; however it is very difficult to produce that format in a system like the PBX (unless you want to bring in instability). IMHO it is still easier to pick a player that is able to play back WAV/GSM49 format.

See the other post, we just added that prompt.

We just added a pragmatic recording to have this off the table for now: http://vodia.com/downloads/pbx/audio/audio_en/aa_offer_cellphone.wav, will also be included in the 5.2.0 xml update file.

Der wird immer angezeigt (das schadet nicht). Offenbar unterstützt die Telekom das nicht. Die meisten Anbieter untertützen dass nicht; die Angst eine Caller-ID anzuzeigen die nicht vom Kunden kommt ist wohl zu groß. Aber vielleicht würde ich trotzdem mal nachfragen; bei ISDN gehts ja schliesslich auch.

Okay, let me try to understand: The problem is reproducible? Attended transfer, then where exactly does the call come it? This might be a issue with the user interface of the phone. The PBX cannot "see" what is being pressed on the phone and when. Call waiting is an easily forgotten test case between every button press, also in the call transfer scenario. Easy workaround is to disable call waiting; not sure if that is really addressing the problem.

Oh, ok. The ZIP files are still there, replace xml with zip. Though we try to focus on maintaining the xml files now, so that languages can be loaded through the web interface.

Well are the other files also in WAV/GSM format?

You mean dict.txt? That should be built into the image.

Plays fine for me... I guess you have a problem with the player.

How about sending this from the email of the one who organizes the meeting? Although I still wonder if that email would be considered a SPAM email.