Vodia PBX

Yes, plus we just added at least the initial email with the web password. If the user is smart enough to go through old emails he might find it. Probably we should add a button that triggers the sending of this again. But still be must mandate that the user enters a valid email address - which is a challenge for some... Stupid end users!

Yea, I know the authentication is a pain. The first thing users can do is to set a permanent cookie (during login). That should help easy the pain. For some things, the above mechanism is already available (e.g. see http://wiki.pbxnsip.com/index.php/Netsuite). We are looking into other mechanisms like client certificates. This would be the right way of establishing trust relationships between the end user and the PBX and this would also make sure that the traffic between PBX and user is safe.

You mean something like "I forgot my password, send me an email"? In this case, the user has to contact the admin who can change the password.

The next day it will be free... But the next version will not lock it any more. Then you can read it anytime - at the risk of reading an unfinished write at the end of the file.

Still not done...

No, hardcoded... But I don't know how that would help stopping SPAM?! What about using username/password? I guess that would help to stop SPAM.

Hmm. No that is hard coded. IMHO the 80 bits are just overkill, why would you need it?

That response code usually reports about trouble with the codecs. Typically it means that there is no common codec that both sides can agree upon. However, in the case above, it does include G.711 and I can hardly believe that they don't support that codec. My second guess would be that they expect a certian packet length; however we don't insist on anything and it should be okay. Hard to say what is "not acceptable here".

You can only see the uptime. The local time can be seen approximately by the green line in the status page in those pictures (6-minute precision).

Just updated http://wiki.pbxnsip.com/index.php/Counterpath.

No, this is just about the HTTP/HTTPS socket. You can limit the access by choosing password that the end user does not know. Ouch, don't do that on 3.1.2! But it will work on 3.2.

You can also bind the http server only to your private IP address. In the port settings, put something like "192.168.1.2:80" and then it will bind only to that port... A new version will be available today.

Yea looks good to me... If you need numbers below 100, it is also no problem. Not sure about negative numbers, but 0-99 are definitevely okay.

Yea, that was a design decision ("feature"). Star usually means "clear", this is the way people can correct their input. And pound usually means "enter", which e.g. is useful when customers are using extensions with variable length.

You mean because the phone gets idle? That sounds like a feature to me. IMHO the whole hype around presence is completely over. I understand IM is useful, but I never understood what presence should be good for. My productivy dropped like a stone when people saw that I became online. Hiding my presence is a feature!

Ah, you are probably a victim of the Windows file locking mechanism. Seems like we have to Open and Close the file all the time...

Yea, that is the intention. When you perform a attended transfer to the cell phone, you will be able to hear if the other person picks up or the mailbox. There are other situations (e.g. when the PBX call the cell phone because there is a new voicemail message), but in all these cases the user has to interact with the PBX before the interaction happens.

Yes you can. All you need to do is use a symbolic link to another destination. We start to support SQL also from the PBX. Send an email to support@pbxnsip.com to get more infos on that.

Now that you have Xlite working, try presence! The presence works with the address book. As far as I remember the trick was that the presence is not peer to peer, it runs the the PBX as agent.

Nonono. Audio is always sent over UDP. TCP has huge delay if a packet gets lost. Instead of repeating a lost packet (and letting all other packets wait) you better just play back a little click and then the audio will go on.

Are you using failover in the trunk settings? There was another post today about that topic, see http://forum.pbxnsip.com/index.php?showtopic=2039. Maybe that solves the problem.

Well, that is just a speed dial. IMHO there is no reason to offer pressing "1" here, you might really want to hit the owner's mailbox. And you know that you are calling the cell phone number, even if you might not know the number itself.

Yea, we removed it. If you run version 3.2, you can just put "file:cdr.txt" into the SOAP CDR URL field and you'll get nicely formatted files in the file system.

We'll soon come out with a version 3.2, which does fix the problem.

Okay... From the IVR node, you should also be able to send the call to 8xxx, where xxx is the extension number. Anyway, AA is easier.