Vodia PBX

For a busy receptionist consider using a ACD. Then she can process one by one. Overlappng transfers can get messy for the phone and also for the receptionist. If calls are on hold and new calls are coming in, having the phone ringing would cause total confusion (at least to some receptionists!).

We tried that also in the beginning. But then it becomes difficult to call someone in the company directly, which is really useful if you are on the road and you want to call someone in your domain.

IMHO one of the points of DND is that the caller does not want to tell the caller that he or she is right now not willing to take calls. The caller should be in that foggy cloud of being busy or just not logged in. (One of my biggest concerns about the whole presence hype is that people don't want to have other people spy on them what they are doing right now, called the "presence state".)

One small trick: If the account does not have a PIN, the PBX does not offer the DISA option. But it makes sense. Outbound calls might cost a lot of money to the company when employees have a girls friend in some remote location on this planet. We have to look into adding an option to disable that feature, maybe per domain, maybe also per extension.

It depends a little bit on the type of phone if the DHCP or the settings have higher precedence. That is a question of trying things out. If you change just the pbx.xml file that has zero effect. You need to change this through the web interface (see for a trick on how to handcraft a URL that does this job: https://www.pbxnsipsupport.com/index.php?_m...kbarticleid=413). Keep in mind this changes the NTP server for all domains.

Hmm. Not yet... What is the use case?

Yes sir.

Ehh... You mean when you perform the same call it behaves differently? *00 is a bad example, this one will go to the cell mailbox if the cell phone is not logged in (that is a feature). It should use the "1" essentially for forking calls between desk phone and cell phone.

Hmm. I just cannot think of a situation where blocking the Caller-ID makes sense when calling 911 (except from abuses).

Could be a Windows firewall problem. If nothing else changed. I remember that some Windows update made the rules for Windows filewall more strict. Last resort is to install Wireshark and investigate the true flow of media. If the automatic start fails that can be a hint that there are too many CDR stored in the file system. Try to make the CDR duration shorter.

Yes, that is simple an upgrade problem. In 3.2 you could put the string "true" into the permission setting, in 3.4 you can list the accounts (which is more powerful). Now imagine you have an account with the name "true" or an account with the name "false". That is why the automatic update is not so straightforward... Yes you have to touch this setting, ...

That is done in version 4.

You can set up a gateway if both PBX are on routable IP addresses. For example, we do this between the different branch offices. The biggest hickup is the "localhost" name. If you have it, the PBX will easily mix up extensions between the different PBX. The way around this is to use telephone numbers, even if they are not reachable from the PSTN. This way the different PBX can determine if the call comes from an extension or a trunk.

Hehe. We need to be careful that we don't fail on the secondary email as well! Otherwise we might end up in a loop. An email notification about the failure of an email notification about the failure of an email notification about the failure of an email notification about the failure of an email notification about the failure of an email notification about the failure of an email notification about the failure of an email notification about the failure of an email notification and so on!

If you have a clear hierarchy of PBX then things should be simple. Just treat the PBX in the lower levels like extensions/soft phones. Registering them makes things easy and if helps to solve potential NAT problems. Gateway mode can be used to have a mesh of PBX. Maybe the word "federation" would be appropriate here. Like several companies calling each other.

Yes this is a old feature in the good old PBX systems, now also available on IP-PBX! Yea the lights go on if there is a redirection set at all. But you are right, it should be only set if there is a match between the destination and the current value of the redirection. Next V4 will have it...

Yes you can. The snom phones have a feature that defines which identity to use if the active one lost registration. If you point that to a secondary registration which goes to the PSTN gateway, it will automatically fail over. Hint: The second registration does not have to be "registered" (in the PBX that would be called a gateway trunk).

What did you put into the SMTP server setting? This setting does not take a scheme, e.g. smtp:my.server.com is not okay. Just use my.server.dom.

In the latest version you should see in the log which DNS server the PBX is talking to. Is there anything that would surprise you? Keep in mind that the PBX may change the DNS server from time to time. Every server that is on the list can be used by the PBX...

I doubt that. Those prompts are pretty old and they should be in the Dutch recordings. Do you hear anything? Or anything in the log saying that a file cannot be found?

I believe that you now have to enter the queue where you want to login or logout.

Maybe check out http://kiwi.pbxnsip.com/index.php/Failover, there is some help for Linux. Not sure where that is on the support site.

Go into your mailbox (maybe after entering your PIN code), then you can dial star codes from there.

Whow. It could be something like someone has root permissions and is clicking on the wrong button (maybe a cat?). Check if you have good passwords set...

What is in /etc/resolv.conf? Is that the DNS server that you want to use?