Vodia PBX

You can let the PBX send out an email when the trunk registration status changes. This way we reminded our ITSP that the service was not available for five minutes at 3 AM... Pretty impressive.

Yea, we made some progress... The emails with WAV attachments are now assembled in the (low prio) email thread. That makes it possible to send out pretty long recordings as well, so that we can start dreaming about sending out every conversation recording out by email and get if off the file system.

When I hear dropped calls in a conference three things come to my mind: 1. Does the moderator press *9? That would actually be a feature. 2. Are those who are disconected speaking from time to time? Or could the PBX think that they are dropped out already. 3. What about the CPU load? Could it be that the system is running out of juice?

Your wish has been fulfilled. It is included in the next 3.0 release. Though it is sooo flexible the documentation will not be easy. And the account index shows the real account names now. No more searching for accounts.

In SuSE10 if you install the service the firewall will block everything by default. Maybe RedHat now does the same. The crazy thing is that you see the packets in wireshark, but the firewall won't forward them the the PBX. It took us days to figure that out. This is not a PBX-specific problem. There must be something about this problem in the RedHat documentation.

Someone is sending RTP from another source. According to IETF it is legal, but raises questions where the RTP comes from, that's why the PBX writes something in the log. Only in the case of MoH it makes sense, IMHO.

If you are using the RHEL4 build, it should also run fine on RHEL5. The PBX is not very demanding on features, so that version change should be no problem. What version? If guess you are on 2.1. The 3.0 version does some of the network stuff in a more elegant way, and it is about to be released anyway. If you are installing a new system, IMHO it makes sense to jump directly to 3.0. That is true. I guess someone needs to sit down and pencil every step down when setting up the system.

Currently we don't have this. But it sounds like a good productivity tool. We can beef up the camp on a little bit for this.

Probably a problem with the PHP version. Seems the old form does not exist any more, see http://www.phpbuilder.com/board/printthread.php?t=10304087.

Do you have to use busy tone detection? There are many cases where you don't have to and then I agree detecting can be a pain in the neck. Unfortunately, analog lines were designed for the ear, not for machines trying to figure out if the party already hung up or not. That is causing a lot of grief.

Oh you mean we could just have taken GMT and set the offset to +0000? Hmm, that seems to sweet to be true... That would be extremly simple.

Oh yea, that would be very important. It must pick up, otherwise it would be pointless sending the call there. But I don't know Zopier in that detail.

Yea we have to add a new web page with the options that control what emails are actually being sent out. Though the default should be that all of these emails are sent, because each one of them reports a problem that the administrator should look into.

Just enter the list of IP addresses, seperated by space characters.

Yout don't need to have option 66, you can also provision the phones with a settings url (see http://wiki.pbxnsip.com/index.php/Snom#Manual_Setup). I don't know. Then all phones are ringing. Wouldn't the park orbit be a solution? You can also put that on a button and then they just have to IM the park orbit/button. Park is the hold of the key system. That is very understandable. But IMHO the park button would serve them better. My suggestion would be the plug and play with the setting URL, and then using park orbits via the buttons. That would work pretty smooth and they have to push just one button.

It seems that the RH version was a little sensitive to a race condition that we had (see http://wiki.pbxnsip.com/index.php/Release_Notes_2.1.14). If you like, update to http://www.pbxnsip.com/protect/pbxctrl-rhes4-2.1.13.2494. But this is not the final 2.1.14 version (trunk and tel:alias changes are not in that image yet). In general, you can use ulimit -c unlimited to enable core dumps. You must do that before the PBX is started, a good place is in the startup script.

First of all, you can turn the email logging off for the address change my manually changing the settings "email_regstatus" (http://wiki.pbxnsip.com/index.php/Global_Configuration_File); not sure what version has it. Save the pbx.xml file and see if you have the setting. Second, if there are so many registration changes you are in trouble (well, at least the setup is having problems). This message tells you that there is a device that is changing the ports all the time, and that makes it pretty unreliable to call the device, or just send MWI messages. Check if there is a router with a buggy NAT implementation somewhere. I don't get the part with the email loop. You mean it sends an email about the failure of sending an email?

You can use the shared line feature in the buttons. That should behave pretty much like the good old shared line in cheap key systems.

Oh, maybe you don't need to run the call through the AA at all? If you can route the call based on the DID number, you can send the call directly to the Zoiper or a analog ATA. That is absolutely no problem. No need to detect a FAX tone! And then Zopier can also negotiate the right codec right from the beginning. Probably you just have to configure the trunk according to http://wiki.pbxnsip.com/index.php/Inbound_Calls_on_Trunk, and you are all set.

Hmm. Okay, it seems we need to write the cell phone number also into the CDR. The disadvantage is that this number will also be visible to the user, so we probably have to introduce another CDR field that says "classified".

We are holding our first German based pbxnsip training on the 8th and 9th of October. The location will be at Snom Head Quarters in Berlin, Germany. As an Advanced partner of Snom we will demonstrate the range of Snom IP phones along with 2 days of pbxnsip training. http://www.snom.com/en/events/snomiversity For more details please email eusales at pbxnsip.com.

It should be fixed in version 3. The countdown runs, release should be shortly.

Backup, backup, backup. Okay, that is clear. A restart does some sanity checking. But does not repair, it just deletes inconsistent accounts and relations. Fixing would require editing the files, especially in the users and user_alias directory. In the end it is a relational database, and probably some pointers got out of sync. Maybe send a email to support@pbxnsip.com to see ifwe can help you.

If you hear that, you are pretty far. Maybe try to call the FAX directly (without the AA), there might be an issue that is not related to the CNG tone detection.

We hope that we can release 3 this week or beginning of next week... At least we have a feature freeze now.