Vodia PBX

Fro FAX with T.38, both the PSTN gateway and the FXS gateway needs to support it. If you are using a ITSP, then I would suggest to ask them if their switch supports T.38. As for Fax to email, there is a softphone out there (name?) what supports T.38 and fax-to-email. Maybe someone remembers what the name was.

Maybe we really need to expire DND, for example every night at 12 o'clock. But I am not sure if that would have some negative side effects. It is really difficult to find out that you are on DND in SIP, there is no standard that would indicate this.

If you want to receive a CDR email after each call, that feature is in 2.1.6 available.

You can check the extension status - is it on DND, are there registrations? Log in as user through the web interface and see your own status.

Well, ultimately that will be in the release notes. Out of my head currently: Agent queue fixes: The LIFO algorithm added all agents without delay at the same time Agent queue is not able to send daily emails with agent statistics all accounts can now have descriptive names dongle support for Linux (well maybe we have to drop debian 3.1 support because of that)

It is seconds. A value of ten means that after ten seconds not receiving anything from the ISP, the PBX would continue processing the dial plan and possibly choose another trunk for the call. I would say values between 5 and 10 seconds are a good balance between reasonable response times from the ISP and user patience until they hear a ringback tone.

Okay, how loud is that white noise? Is it comfort noise or SRTP junk?

Just go to the http port... But maybe lets first get some more exposure, don't spend too much time on trying to figure things out.

We have new German prompts, recorded in a professional studio. Makes the PBX sound even better! It is available for download from the home page.

Well the point is to present the numbers in a way that they can be dialled ("canonical" format). It makes life so much easier, also for address book lookups. If you can, let your PSTN gateway give you numbers that are in such a canonical format.

What version? We had that topic a few days before already, seems there must be something wrong.

Still working on getting 2.1.6 rock solid...

We added the option to send an email with the CDR after every call. I am using it already and it makes sense to me. It is my Outlook's job to sort the emails correctly into the right folder and I never have to worry about writing numbers down.

Well the problem is that when you call after hours to turn it on again then the PBX would wait until the next morning...

Hmm, can't reproduce this, but running the latest 2.1.6 build. Lets keep an eye on it.

Well, in that case the client must log into the web interface and change the state from there... If we would allow to call and change the state, then the next question would be how to get back to automatic mode.

Oh you mean someone has a personal DID and that someone should be able to tell if the DID has been dialled or the call came in through the AA? Hmm, at the moment I don't see a useful way of doing this...

Yes. It waits five seconds, then tries again - and gives up after around a hundred tries.

My suggestion is to use DNS SRV - if you can. The ratio of gains compared to efforts is greater than one. DNS A is just a dirty workaround with many problems.

The redirection timeout starts counting when a call goes into the ringback state - searching for an agent to pick the call up. The purpose is to redirect the call for example to a cell phone when all agents are out. Useful for small groups, for example sales groups when calls are coming in after hours. The other timeout that starts after entering the ringback state is the escalation time. It is used to include more agents in the group of ringing extensions. This is useful to include "boss" type of agents that usually should not be disturbed. If the escalation time is higher than the redirection timeout, then the redirection will kick in before any of the escalation agents has the chance to pick up the call.

DNS SRV solves a couple of problems: It makes it possible to use only the domain name, not the server name to locate the service. For example, you can use the name "domain.com", not "sip.domain.com" when calling someone. It makes it possible to hide the transport layer to the user. No need to include "transport=tls" in the URI. It makes it possible to support server farm directly from the client without special equipment in the middle. DNS SRV defines weight and priority for parallel servers and failover. While parallel servers are also done on DNS A by randomly shuffling the DNS A results, failover is only possible with DNS SRV and client support. With DNS SRV you can choose any port, not just the default port. This does not really increase security, as it is quite simple to look the port number up using DNS SRV. But it makes is possible to have several domains running on the same macine running on different ports. And it also makes it easier to decide weather to use IPV6 or IPv4 for a service. Well, this applies only to queries that respond directly with the IP address of the service.

If operators start to require that every DID has it's own registration - good night. Technically it is no problem having ten registrations, but when we are talking about more eventually the 16 MBit will be eaten up by REGISTER messages. From a license policy nothing is written in stone (or in C++). If there is a need to have a special version for German operators then that can be done. Now that we have the new German prompts!

You can write your own ringtones.xml (see attachment), you don't even have to restart the service to load the new ringtones if you use the config admin web page. In the hunt group and agent groups you can select what ringtone you want to have, that should make it possible to tell by the alert tone if the main number of the extension is being called. ringtones.xml

No way of resetting the statistics... The absolute time is only visible in the log. The number of days and HH:MM:SS since start up of the service is in the status screen.

Well, this is supposed to work... Maybe a problem after updating from a version that supported only one personal greeting to a version with multiple greetings?