Vodia PBX

There is no option. This behavior is neccessary because there are (buggy) user-agents out there which offer SRTP keys over insecure transport layer and if the PBX does not answer the crypto-line in a response then the call would not establish. A UA that does not support SRTP should silently ignore this.

This is a good idea. One drawback is that the call is already connected and the first coin fell down. But probably it make sense for longer phone calls where the employee does not want to pay the whole conversation (or the PBX operator has a great rate for calling the mobile).

How far did you get? Can you enter the buttons from the web interface?

Before you can change the buttons, the admin has to assign a profile to the extension. Then the user can change his profile, based on the profile.

I believe VNC can do it; however did not have the chance to try it out. The CS410 uses this mode internally to receive the media from the MoH plug.

What specific flag did you turn on? There are several flags in the domain, and you may override the flag in the account setting as well.

That is what is in the "To"-header. Technically that is where the call went, and parties may be interested in that. The problem with the redirections is that you actually need to show the whole path. For example, first it went to the AA, then the caller wanted to go to hunt group A, but because it was night mode it actually went to hunt group B, and there extension C picked the call up, and finally transferred it to D, on his cell phone. A realistic scenario. Which number do you want to see in the CDR?

The PBX has no chance to store the file name location as it gets lost during the upload process. Check out http://www.w3.org/TR/html401/interact/forms.html for more information. What we need are icons that allow a playback from the web page; we'll do that in 4.

Seems like OCS needs that little + sign... It makes it clear that this is not an extension but a telephone number. One of those dirtly little tricks to get it working!

IMHO just an alternative, it is not the same like faxback (a lot more Windows-centric).

There is also COMISDN (www.comisdn.com), a french company. They have something that plugs into the Windows FAX stuff. I saw it working today.

Try setting it to E.164 without the + in the beginning...

That looks like E.164 (without the + in the beginning). Check your trunk settings.

Just don't enter an email address. In this case you can set the email address later.

Interesting... There were cases when the counter was "on the edge" where the PBX made trouble. I thought those cases were fixed; seems like we have to put this on the bug radar again.

TLS should not eat so much CPU power that you experience a delayed ringback. But not using TLS makes it possible to run Wireshark on the PBX and see when messages are going out and coming in. That should help to track the problem down.

You should see something in the log that tells you more details. For example, it could be that you are holding a call on another extension when you dial the park call (common problem if you have more than one identity on a phone).

If you set the country code of the domain the PBX will try to put the number into the right format automatically. In USA, international numbers can just start with 011.

Recording the conference does not follow the general recording rules. For example, you also don't need a special license to record a conference. This is like the mailbox messages also don't follow the general recording rules, the recordings also have a hardcoded message name format.

No. You simply cannot blacklist someone in the domain...

Well currently the PBX can redirect only to one number (the "cell phone", but it can be pf course any number), but they are pretty flexible with the times. Workarounds would include service flags; but that will be ugly and complicated. Or you create a new DID on the PBX and loop the call back, then into a hunt group and then into different destinations. Ugly!

Sorry, http://wiki.pbxnsip.com/index.php/Global_Configuration_File.

Not sure if Aastra is able to display instant messages right on the screen.

Did you assign a dial plan for the domain or for the hunt group? Logging should tell you what the PBX is trying to do.

Does the ACD connect the call (meaning: does the caller have to pay for the call)? There is a option that tells the PBX to connect the call only when the agent picks the call up; but for a busy group that is usually way too long. What is the event for connecting the call? If the handset is ringing for so long you should redirect the call out of the queue, for example into a hunt group. It is just not good to keep the handset ringing for so long. You might even redirect the call back into the same ACD; customer will not be amused to get kicked back into the queue (especially at the beginning of the queue!!!) - but this is still better than a dropped call.