Vodia PBX

This feature is available in 5.2.2. When you add a redirection number, you will see the fields for the redirection time showing up below the redirection number.

Well honestly, then change the trunk provider. If you need to receive FAX, T.38 is a must-have. If you don't have it we all will go through a long, frustrating experience of FAX not going through randomly or not at all. We also have a SPA112 here, will add it to the provisioning process to make life easier for the next customers who set this device up.

If you "REGISTER sip:100.64.0.49 SIP/2.0" the PBX must have a domain "100.64.0.49" or a domain with the name "localhost" in it. Otherwise it will not match the domain.

Is 2003 Windows XP? That might be a problem now. We have started to use VS2014 to compile the images;not sure if this one still supports XP.

Can you get us a PCAP trace (from Wireshark, not from within the PBX=? Maybe the format is not right/understandable.

Well it is Vodia PBX, not Asterisk. Never mind. Anyway, we are working on including gateways in the provisioning procedure as well. It would be great to have a good template that we can send to the gateway (through a HTTP POST), with a few places like the outbound proxy and essential device parameters like the number of POTS lines. Then we can avoid those long discussions on how the device should be set up

Can you turn on the debugging window for JavaScript? In Chrome that's when you right click on the web page and select "Inspect Element". Then there is a tab called "Network", where you can see the interaction between the PBX and the browser. There you should see the websocket communication. It should contain something after 120 seconds that gives us a clue what is going on. 120 seconds could be a timeout caused by the network/firewall.

I guess you tried F5? Did you try from another browser? If it all does not work don't spend too much time on it, the next build fixes a couple of bugs with the user mode anyway. Let me know if you want to try a beta build (what OS).

This message is generated if there are too many calls in the domain (there is a setting for that in the admin/domain edit) or on the whole system. You will see more detail on log level 7 in the general category, especially if it was because of the system or because of the domain.

Just make a backup of the working directory of the PBX. In Windows, that should be no problem. The backup button was taken out because the files could get so large that it would make the whole system unstable when you click on that button. File system backup is much more safe and much less intrusive.

That sounds like there is something else going on which is not okay. Do you see the status in the web interface of the PBX immediately? What if you use the starcode? I assume you used PnP for the phones. DND is propagated with a SIP subscription, and that should be (in theory) immediate.

Bin da nicht der allergrößte Experte, aber counterpath Bria, Zoiper, Acrobits, media5, Nimbuzz und Join scheinen da die Alternativen zu sein.

There are several ways to start a call with the remote_call.htm link. If you have already a session, then the session authentication will be used. This is interesting if you are logged in from a web browser. Otherwise there are two ways for authentication. If the HTTP request contains a HTTP header "Authorization", it must contain a Basic authentication according to the RFC. In single domain environments where the domain names contain localhost, the username may not include the domain (123 instead of 123@domain). But it is better to include the domain anyway. Otherwise the URL itself may contain the authentication in the form username:password. The username is the username as used in the user parameter in the URL. Make sure that special characters are escaped using %xx. This click to dial works only if the extension has a web password set.

Yes we found that already. Will be fixed in the next version. If you want to have a snapshot build, let us know what OS.

Sounds like some problems with the network interface. Maybe try to use 10 MBit instead of 100 MBit? Could be something "stupid" like a broken Ethernet cable.

So the problem is within the page, meaning some of the updates are made in the browser and others don't? Then we can exclude problems with the web-browser slash websocket. Do you see the registration status of the ones that are not registered or are they grey?

I would not use 8.7.3.19, there is a version with a lot of improvements available http://wiki.snom.com/Firmware/V8/Patch which we included in 5.2.1.

Sounds to me like a problem on the phone. There are a couple of settings on the phone, like "DTMF echo on Speaker Phone". Can you try to flip them on/off if that makes any difference?

Yes, it cleans the extension up. Call redial, name, whatever a guest might have set up during the stay.

On a SoHo?! Well that I remember there was a tar command that can do that--but far from being trivial. I think you can also do that with the JTAG cable, but check the sheevaplug information for that.

Yes there is a cleanup code, designed for hotel environments when the guest checks out. Clean up an extension: *84

Do you want to backup the whole SoHo?! I would backup only the working directory of the PBX. All data in in that directory, nothing scattered around unless you tell the PBX to do so (like storing recordings externally)

Ergh, yea thats the old SoHo... I think you are better off using SSH and the standard Linux tools (tar, sftp) for making a backup.

It is in the admin mode, general then CDR/recordings and its name is "Record Location"

I did a little bit of research on the search terms "linux external drive reboot symbolic lnk", This seems to be a general Linux problem, not only for the embedded Linux. But I think it is also possible to specify an absolute path for the recording location, e.g. /media/usb/recordings/$i-$d.wav