Vodia PBX

Don't call the button "13", better call it "dnd". That feature requires version 7.1.33 on snom.

Ouch, probably because first the extension is busy, and then the call gets disconnected without being connected. Both reasons to send an email out. The good news is that it does not get forgotten!

You mean you get one email for the missed call and another email for the CDR? Or are they exactly the same?

Not in the star code. But the PBX sends along with the star code a label for the button, which provides additional information. If you want to hard code a specific number, then you can still use the *87xxx starcode for "end-user" initiated call pickup.

Exactly. The "LED" is in the screen and looks like a DND symbol.

Yes, the whole DND cloud is a "pain in the neck" problem. Therefore, we introduces a couple of things in 3.0: At midnight the PBX may reset DND on all extensions The buttons may now have a name "dnd" (snom phones) which are synchronized with the state of the PBX. This works with the defeult configuration of the PBX. The problem remains if users turn DND on locally on the phone. If that is the case, the PBX has no chance to fix the problem.

Should be fixed in 2.1.12, see http://wiki.pbxnsip.com/index.php/Release_Notes_2.1.12.

That translates into *601 meaning pick a call up and 5775 being the call-identifier. The PBX automatically tells the phone what code to use for the next pickup. So you don't have to configure anything.

Well in that trace we see that the Asterisk drops the connection. When the PBX picks the call up, Asterisk tries to re-negotiate the codecs (obviously because it wants to change the IP address of the RTP) and then sends a BYE (no idea why). Maybe you have to upgrade to the latest 1.4 version. Maybe you have to put something like canreinvite=false or something like that into the configuration files, so that it does not attempt to make the PBX talk directly to the Vegastream.

There was another post recently. Bottom line. There is (static registrations). However, be prepared for a lot of problems with offline cell phones that will pickup immediately.

Nope. Ehh don't remember, did you send some traces?

Resellers in the Netherlands can now download and use the Dutch prompts! Check out http://pbxnsip.com/software for the latest audio files.

The email timestamps are always in GMT. That is because the one who receives it might not be in central time. The send time is corrected with an additional argument which looks like -0800 meaning subtract 8 hours. There was a problem with the second argument, but that should be fixed now in the 2.1.12 version. Look for a header like this: Date: Tue, 22 Jul 2008 04:45:55 +0200 You make one step forward and count the steps backward... Welcome to the software world !

Eeeh, what is "type officestar"? Connection with freepbx will probably run through a trunk. That should be prettys straightforward. Check out http://wiki.pbxnsip.com/index.php/Trunk_Settings for trunks.

Well, surprisingly the PBX advertizes the public IP address but sends it to the private IP address... What is the output of the route command? Maybe there is something wrong for the routing tables.

No, that is not a bug. The idea that people fork potentially calls to a lot of cell phones (half of them being powered of, in the tunnel and redirected to the mailbox) just do not sound like a solution to me. The agent "mailbox" always picks up immediately, and the PBX has a very hard time figuring out if it is a natural person picking up or a machine. Though there is a work-around. You can add a static registration to the extension, then the PBX will also include the cell phone in the group. Maybe you can try this and see if it meets your business demands. I believe it is better to try the agents in house (potentially using hot desking), then if that fails escalate the call to a specific extension and potentially also forking it to a cell phone. If then the mailbox picks up, okay then it is last resort and even the caller cannot expect much more.

No problem!

Unfortunately, that is not possible yet. The way the PBX does it is by putting a call on hold first, and that is a feature not supported very well from the cell phones (or the base stations). The PBX just hears MoH.

That should work... Any chance for a PCAP trace?

What versions of the PBX? What version of the phone?

Yes, that is no problem. You can use the magic letter "t" in the Extension mode of the trunk (see http://wiki.pbxnsip.com/index.php/Inbound_...k#Extended_Mode).

Counterpath had a version that runs on Windows Mobile, but I have not seen a publically released version. The alternative is to use VPN, which is supported on the Nokia WiFi-enabled phones. It does not use SRTP, but VPN makes sure the call is being encrypted.

It is still not done, but at least it seems we now know that it will be done using the calling-card account. There we can use the authentication mechanisms and then we can do the call-back. Authentication can also be done while the call is still not connected, so that the caller will have no cost.

Understandable. It is frustrating to waste time on something like this. Because of that, I always recommend to use copy & paste even for short strings like the MAC address... It just makes this much more i*-proof.. The alternative is to use a USB dongle. That also has the benefit of making the license independent from the MAC.

There is a settings called "c2d_root" that you can set (see http://wiki.pbxnsip.com/index.php/Global_Configuration_File). If you specify the DNS name there, the PBX will be more than happy to use the string you provide there. For example, you can put there "http://pbxnsip.abptech.com".