Vodia PBX

Check out http://wiki.pbxnsip.com/index.php/Login. In Linux, you need to do some additional steps to run the PBX as a service. Check out http://wiki.pbxnsip.com/index.php/Installing_in_Linux. If you are not familar with Linux daemons, our suggestion is to get started with Windows first and then later consider using Linux. You can easily move the configuration from Windows to Linux.

You must re-install the voice prompts to get that working...

That is done in the latest and greatest (but no image available yet).

There is little difference between Linux and Windows... Once you got the service running and make it to the web interface, things are pretty much the same in Linux and Windows. Did you see the Wiki yet? http://wiki.pbxnsip.com, it contains a lot of information about how to log in, how to create your first domain, extensions and so on...

Well we put some extra checks into the code - but we were never able to reproduce the problem in the lab really, so it is not clear if those extra fixes did the job...

That sounds like there is a problem with the sending of the performance email? Or the CDR email? That is what happens around midnight!

Does anyone use IPv6? It would be very interesting to get feedback if the IPv6 support is fine or there is anything outstanding. The PBX should support SIP, HTTP, TLS, SRTP, dual IPv4/IPv6, multiple addresses, and everything else that we could dream of. Especially in Vista it should run just great. So far we could test this only on our lab, it would be very interesting to ehar feedback from the real world. See http://www.pbxnsip.com/ipv6 for some more details.

Hmm. I run Windows XP, and there things were okay. Once that you try to register the TSP, the registry is "poisoned". Maybe you have a "fresh" XP left? Manually playing with the registry sounds extremly dangerous to me, TAPI goes deep into the OS and it is easy to screw everything up.

As long as you set speed dial things should be simple. You can also specify the park orbits (extensions) that the extension should search for a free parking space.

Whow is that reproducable? What are the last words (log level 9, log into a file)?

If you put a pound sign behind the destination, then the PBX waits for a timeout. For example, the destination would be "4#". http://wiki.pbxnsip.com/index.php/Auto_Att...ct_Destinations

So far we know about these topics: Teach mode was not working. A workaround is to disable the pass-through mode. It makes sense to show the account in trunk gateway mode in the web interface. Not areally a bug, but something that we should change. It seems there is no easy way to put a mailbox message into one's own mailbox (need to check *98 again).

I think we are talkíng about a couple of weeks. 2.1.4 seems to be stable to far, and so far there was nothing really urgent that required a 2.1.5.

Check out http://en.wikipedia.org/wiki/Telephone_Number_Mapping. Maybe someone wants to add a hint how to do this with the PBX . There is already something on the Wiki http://wiki.pbxnsip.com/index.php/ENUM.

Well, if that number is external the audio depends on what the carrier is sending. When putting an internal number, the call should play ringback as soon as the PBX received a 18x code from the device. That is where the "comfort" noise comes into the game. Comfort means that the PBX or the carrier sends some decent noise to indicate that the channel is still engaged.

To me it looks like the SOAP Envelope is missing in the reply. See http://wiki.pbxnsip.com/index.php/Linking_..._to_an_IVR_Node.

Call recording for a conference makes sense, however the scary part is that conferences tend to be quite long and so will the files be. I guess we have no choice but making call recording for conferences a feature that you select when setting up the conference.

In the 2.1.5 (upcoming) we fixed it so that it will automatically move to rtp_decode mode...

Can you try to set the setting "allow_pass_through" to false? You can do this by appending "?save=save&allow_pass_through=false" to the web URL when you are logged in as admin (e.g. http://192.168.1.2/reg_settings.htm?save=s..._through=false).

These features are still in there, and they now can even contain DTMF sequences to make the recording start less accidential. Maybe the key that you have does not include the record feature. You can for example use www.opinionatedgeek.com/dotnet/tools/Base64Decode to decode the key - check if the record flag is there an set to true.

The key to get this working is to use multiple service flags. I would set up a "root" auto attendant that takes care about normal business. Then several service flags can take care about the "exceptions" and route calls in these cases to other auto attendants. This works nice for periodic schedules (e.g. setting office hours) and it also works nice if the flags are always turned on and off manually. Changing a periodic flag dynamically... hmm worth a try. Maybe it is enough to just call the service flag and change it's state. But I remember there was a lot of trouble when the user and the PBX both try to change the state. If possible it is better to make a clear decision.

ENUM is a long story. In pbxnsip, inbound calls must run through a trunk that can be used for ENUM. It must not have a outbound proxy, so that any incoming call can be matched. Outbound calls can run through the same trunk, using the enum=yes flag in the replacement pattern. That part is relatively easy. The challenge is to get listed in the/a ENUM tree and to guarantee QoS. Especially if you have no idea where the call comes from, you might end up with QoS problems on your Internet line. The idea is nice, bypass all operators and do business calls directly between the businesses. However I am a little bit sceptical that QoS will be the problem. If the internet access provider does not provide QoS you are on your own. If they do so, they can easily also take care about ENUM...

Well, that is a double-sworded thing... Those files keep on changing. Maybe we should put them somewhere under CVS control so that we can live with future changes... And also keep the files in the generated directory in the eye - they are the best templates for small changes that you need in the installations. dialplans.xml timezones.xml pnp.xml

There are different ways for detecting caller-ID (DTMF and FSK). I think the default is FSK, maybe you are in an environment where DTMF is being used?

Okay, that was a good proposal - done. Structured it a little bit different, but it should cover the topics.