Vodia PBX

It is actually Tag-Length-Value encoded. There were actually some other posts about this subject, see http://forum.snomone.com/index.php?/topic/6345-strange-cdr-logging-format/

There is a settings "record_compress" which tells the PBX to use GSM codes to save the recordings. Try turning it off (http://wiki.snomone.com/index.php?title=Global_Configuration_File); then the PBX should send the recording in linear format.

Version 5 is not only snom. You can for example also provision Polycom phones with it. In a nutshell, snom phones are (as the name snom ONE suggests) supported to the highest degree; but snom ONE version 5 continues where pbxnsip was when snom integrated pbxnsip. For example, Polycom phones can also be automatically be provisioned. In the next few weeks, we have to document the details on which devices are supported with what features.

Okay, we updated the procedure to use the general software update mechanism. This way, you can just copy & paste the XML URL into the SW update section and let the PBX do all the work. See http://wiki.snomone.com/index.php?title=Language_Prompts. On the mini please check how much memory is left on the flash (see the status screen in the web). It cannot hold all languages at the same time, so you have to make a choice.

The SSH password is the same as the admin login to the PBX. What language are you adding? We can make a XML file for that, so that you can just use the XML file for the upgrade.

You can see in the "generated" folder what the PBX sends to the phone. Maybe there you can see what the problem is. I also remember that there was a change in the language names between the versions on the phone side. Maybe the text has to be now "Englais" for French English or something like that...

I guess the system has the time right (e.g. check the time stamps in the log file). Also there is a extra slash after 11/23; but I think that can also not be the problem. Maybe anything wrong with the space? E.g. instead of a space character a TAB? If the first dates worked fine, then I don't see a reason why the others would not work.

Right, instead of rebooting the phone all the time, you can just simulate the same in the web browser. Did you overwrite the domain settings in the extension by accident? Language has three layers: system, domain and account. Only if the account is set to "domain default" it will take the language from the domain (or the system if the domain is also on default).

We have finished the version 5.0.3. The release notes can be found at http://wiki.snomone.com/index.php?title=Release_5.0, as usual. This release takes snom phone provisioning to the next level. We added device-specific button profiles and integrated the snom XML RPC mechanism into the PBX. Also we found a major glitch on the fax2email for non-Windows builds that might give you that aha-effect for this feature. P.S. Make a backup before the upgrade, please. Memory has become so cheap, it is a mistake not to have backups.

Wenn man {5} eingibt, müssen es exakt 5 Stellen sein. {5,} bedeutet dass es mindestens 5 Stellen sein müssen. Statt [0-9]{5}[0-9]* könnte man auch [0-9]{5,} eintippen. Das nur am Rande...

Yea... The webpages give customers a large degree of freedom for customization--however when upgrading the system the pages get stuck at the last edit. That is a problem. Merging would be the solution, however it is not trivial.

How many CDR do you have in your cdr* directories??? What do you see when you start it with pbxctrl.exe --dir xxx --log 9?

I does ring a bell somewhere, but not concrete enough yet. Does this happen with the m9 at all? Or is it specific to the desktop phones? I think I remember there was something that the PBX received "random" REFER messages, which would be related to a specific firmware version on the phones. If this happens well into the call we can exclude general SIP routing problems. How many calls are usually active on that system? Could it be that we are running out of resources, e.g. number of RTP ports? Is this the Windows 64 bit PBX build?

Ich würde es mal mit ![0-9]{9}[0-9]*([0-9]{3}$)!\1!t!100 probieren.

Thats not good. You should tell the PBX (once that it is running) to write the log to a file and then take a look at it. If there is really nothing in the log that hints at a PBX problem, the PBX service maybe depending on another service. Anything in the Windows event log?

Whow a factory reset of snom ONE! But that sounds like you have some customization in the html folder or in the webpages folder. Next time, try to remove those directories only and restart the service...

My Italian is pretty basic, but I would assume that you have selected something in "Tono di chiamata" like Custom 1. Did you modify the ringtones.xml file? The tones there are pretty much hardwired in the phone. Try to select the "Custom 1" tone, then it should ring differently.

Is there any chance to upgrade the system to version 5 or at least version 4? Also, what you should check if the registration is stable. I am not sure if that feature was already in 3.1, but can you tell the PBX to send out an email to the administrator when the registration status of the agent has changed (in the registration tab for the extension). Unstable registration would explain this behavior. The 25 seconds could be the request timeout from the PBX. If the phone does answer not anything at all, it would consider this a timeout response code and move on.

I assume you already set the hunt group ring melody. Are you using plug and play with the 300? Then everything should be automatic.

Generally speaking, you should avoid dialog state subscriptions because they are resource killers; that's why we came up with "buttons". But yes, white-listing the devices does help.

As long as the registrar returns 2xx the PBX stays with the address. Only when the registration fails, it goes through the whole algorithm with DNS & everything. AFAIK that's the way it is today (5.0).

You could try to get him out with *87...

So are you still running version 3.1? In the meantime we added some options so that after some time the PBX can take the caller out of the queue and send them to another location. And a lot of other features have been added to the ACD as well.

The problem is that we also had to do some magic on the PBX side to make it possible to see the status of ACD and conference rooms. Also the old AC got easily blacklisted by the PBX which needed some more changes.

FYI - you need to run 5.0.3 for that...