Vodia PBX

Oh forgot to say: *98<ext>#; the # terminates your entry.

Oh the system had probably problems interpreting the numbers right. 2121234567 in the USA has a different meaning (+12121234567) than in the UK (+442121234567). That's why we always recommend to set the country code right in the beginning.

You can put more than one cell phone into one extension. Separate the numbers with spaces. Then they will all ring; the first one who connects the call will get the call. Hunt groups can also include the cell phone of the extensions; there is a setting for that on the extension level (redirection tab). There you can also define the hours when the forking should take place, so that none of the users has to be afraid to get called in the middle of the night or on the weekend.

Recording comes in two flavors: Ad-hoc and automatic. Ad-hoc is initiated by the user while automatic is initiated by the system based on rules. Automatic is all about turning it off (if the caller does not want to be recorded). You can actually have ad-hoc and automatic going on at the same time. The snom 3xx series had this recording button which for many many years was practically unused. We put a XML text there that offers several options depending on if the call is being recorded or not. Unfortunately (or fortunately) the 7xx/8xx-Series does not have that button any more and the soft key is hard-coded to send INFO events. It would be ideal if that soft-button would behave like the hard button did, and allow XML programming. Then we would also have a great solution for 7xx and 8xx. The star-code is really only a hack. The first problem is that the other side can hear the tones. The second problem is that the PBX may have false alarms, for example if you call your cell phone mailbox and press *12 in a completely different context. That's why these out-of-call solutions are preferable.

You can always try out with a 30-day trial key (add it on top of your existing license).

You mean in the auto attendant? That can be done with *98<AA-Number>. If you are calling from outside, you need to make it either into the private virtual assistance for your cell phone where you can dial a number (incl. star codes) or go to your mailbox. In the mailbox main menu, you can also dial star codes.

We were using version 4.0.3F, which seems to support VVX500 and VVX1500 (and a large range of other non-VVX-devices). The XXV300/400 series seem to require version 4.1.4. I wonder if you can actually mix both firmware versions in deployments, that is a riddle we still have to solve. But from a provisioning and operations standpoint I would be optimistic that the 4.1.4 will also work with the 5.0.8.

Check: Is the INVITE coming from the same IP address where the PBX registered? Do you have multiple domains? If the answer if yes, is the trunk in the right domain? If it is global, do the alias names (DID) of the accounts have a global number? You can check that in the user_alias directory. Does it work when you enter e.g. the auto attendant in the field "send call to extension"? If yes, then the problem if finding the right destination in the domain.

Is this the backup of the whole system? Or just a domain? As for the whole system, this function should be really limited to environments where you have no file system access (e.g. snom ONE mini). Especially when the backup gets large, making a backup becomes a significant burden for the PBX.

The JavaScript for editing the trunk headers has changed. Especially with the Privacy header there were some changes necessary. But if you just upgrade without hitting the save button, then IMHO it should work. Where does it fail? Registration, inbound or outbound calls? Anyway, if you can go to the text mode in the trunk and copy & paste the settings, we can take a look what potentially went wrong. Also for the sake of search engines and other users that might have the same problem it would be good to know which service provider you are using.

Well, well, well... It was simply still buggy. Next version will have it fixed.

Yes, you need to have a conference room in the domain. If the code contains the room, then it will pick the room (e.g. *53123 for 123). Otherwise it will pick a "random"--if you have only one room in the domain, then this is not very random.

Please check if you have files in the html folder and/or the webpages folder. The changes we had to make for 5.0.8 affected some of the header files, will all sorts of funny side effects. Sorry for the mess, that was a major cleanup thunderstorm that was overdue in order to make progress possible.

We have to look into this when we work on the branding topics again. There are some other settings that we also have to look into, like help links etc.

Hmm. Actually it seems that this feature got lost during the conversion from pbxnsip to snom ONE.

That was probably also caused by the inclusion of the wrong files in the build... Pls try again with the new 5.0.8 build and make sure that you don't have any old web file modifications lingering in the system...

That was probably also caused by the inclusion of the wrong files in the build... Pls try again with the new 5.0.8 build.

We have made a new build for 5.0.8. The confusion with the file naming for V5 was immense. Seems there was a file with the suffix _v5 that was actually never used slip into the build and caused a lot of chaos in the extension area. These problems affected the web client side; the PBX itself was not affected by this. Also please keep in mind that Linux blocks the ports for up to 10 minutes after the restart for exclusive use, which can result in missing page loads, again with all kinds of side effects. You'll see the log message that port so-and-so could not be opened all over again until they were opened.

Is it same like the regular BLF, just with a *90 in front of the number. So yes, 100 % the same behavior :-S

You can edit the login.htm in the templates. Or just wait a few hours for the new 5.0.8 build that will present English as first choice again...

Also, in Linux you have to wait up to ten minutes before the system has really all sockets, exclusively. In the meantime, HTTP requests may not make it and then the JavaScript hangs.

Seems like we had an endless loop in the JavaScript... that has all kinds of "funny" side effects. We'll keep on testing of the problem is really solved.

Well double check in the pbx.xml file if the password from snom is really there (provpass). That was definitively a major problem with 5.0.7 and earlier versions.

ACK. That bug did creep in. We wanted to stress test the multi-language capability and picked German to stress it... Anyway, it was nothing major to fix it and we overwrote the version. Just update again. Also, if you have made modifications to the translations or header files (*header_v5.htm and *footer_v5.htm), you will have to store that somewhere and then revert to the default. We did a lot of changes regarding the unfortunate _v5 file naming, which causes some major problems if you have modified one of those files. It is all part of a major cleanup that we have done on the web interface. You will also notice that we removed all those backward-compatible mode files that made maintaining the webpages a real pain. This will help avoiding future chaos.

Please check if you have made changes to the pages. There were a lot of cleanup-changes in the web interface that may cause these kind of effects (no more _V5 pages next to other non-_v5 pages with numerous exceptions). I just checked, as user you can change your SIP password (unless this was disabled on the admin level). Sorry about the inconvenience but the mess in the web pages was getting too much.