Vodia PBX

If you want to register, you have to use an extension not a trunk for the device. The PBX accepts only registrations from extensions.

Does the audio sound "good"? Or is there a low volume on the call? There are some analog signal amplifiers available, I have heared about cases where that helped. I guess a regular phone does display the caller-ID.

If you have a quiet moment you can make a backup of all files, then perform the upgrade, try it out and if you don't want to use it, you can restore the backup and continue with the old setup. P.S. Don't use the web interface for the web interface, use SSH to login and do it on the file system.

On the icall web site they say "In order to use iCall with a SIP phone you must use iCall wholesale/carrier services. The iCall softphone currently only allows use directly through the application." Are you sure that you account does support a SIP softphone registration?

Should work. $m is the domain. $d is the date (day) $h is the hour

There are potentially many fields that could be displayed on the accounts list... IMHO the ultimate solution is to be able to select what fields to show in this web page... The other problem is that one extension may have multiple registrations and then we would need several lines per account.

How do you reboot? Maybe it does not save it when you pull the plug. Try rebooting from the keyboard menu (maintenance, reboot).

In this case I would check if you can upgrade the phone to version 8.2.29. And I would really really double check the passwords. Do you have multiple domains? Then make sure that the domain is part of the username. 8.2.29 supports the simple user@domain notation. It does not have anything to do with the SBC, I am pretty sure.

Well, 3.4 only supports four prompts. If you must have more, you'll have to upgrade to version 4.

Did you locate the attendant file? it should be in /pbx/attendants/xx.xml. Maybe you can paste the file here and we can tell you what you can do with this file.

Can you manually start the executable? Try it with ".\pbxctrl --no-daemon --log 9".

Well, you are obviously not a customer... I don't think it is good style if market participants are publically talking about each other products. Anyway, your choice. About your question. The PBX is running as Windows service. Check the services manager if the service was installed and is running. Then you should be able to continue your evaluation. For Windows 7, there seems to be a hickup during the installation if the path contains a space character and you need to use the service manager to have it start up automatically.

Did you set the audio langauge to Dutch? There was a mistake in the file snom_gui_lang.xml, copy the content below into the file html/snom_gui_lang.xml and then it should work. <?xml version="1.0" encoding="utf-8" ?> <gui-languages> <language url="{http-url snom}/gui_lang_DK.xml" name="Dansk"/> <language url="{http-url snom}/gui_lang_DE.xml" name="Deutsch"/> <language url="{http-url snom}/gui_lang_EN.xml" name="English"/> <language url="{http-url snom}/gui_lang_SP.xml" name="Espanol"/> <language url="{http-url snom}/gui_lang_FR.xml" name="Francais"/> <language url="{http-url snom}/gui_lang_IT.xml" name="Italiano"/> <language url="{http-url snom}/gui_lang_NL.xml" name="Nederlands"/> <language url="{http-url snom}/gui_lang_PL.xml" name="Polski"/> <language url="{http-url snom}/gui_lang_RU.xml" name="Russian"/> <language url="{http-url snom}/gui_lang_SW.xml" name="Svenska"/> <language url="{http-url snom}/gui_lang_TR.xml" name="Turkce"/> </gui-languages> Will be also fixed in the next build.

We decided to take this setting out, on purpose. The problem with provisioning the VLAN is that it is not the job of the PBX to provision that. For example, if the PBX would provision something like the DNS server or the netmask or even the IP address, chaos would be the result. For getting devices into certain VLAN, there are protocols like LLDP-MED or 802.1X. I know that only few phones can do this today; but we should not make the mistake to try to fix this problem with the provisioning. The setting "admin_mode_password" is set by the PBX. The domain has a section for "Provisioning Parameters", where you can set the PIN for the phones. It would be better to have both a personal PIN and a administrator PIN (same for the phone web server password), so that the admin does not have to expose the password when a user wants to get on the phone web interface. The point behind this is that there is a system administrator that has to manage a (potentially) large number of devices and cannot remember the PIN or password for each device. And he does not want end users screw up the phone configuration. See above. This is the "Authentication Password" of the domain. Hmm. You mean you have this file in the html/snom directory? As far as a I can see it was included in the build process. But we might have to try this out here to see what the problem is. The agent group login/logout behavior has slightly changed. Now you are logged in if you are on the list of agents, there is no extra flag for this in the extension any more (we had a lot of problems explaining what it means to be "logged in" in version 3). You need to specify per ACD who is allowed to "jump" in or out of the ACD. Maybe the agent was able to get out, but now cannot get in any more.

Hmm... Long time ago! There was a problem with multiple domains and alias names, I dont remember which version had this problem. If you can, backup and upgrade to 3.4 or even better version 4.

You should pick another password if security is of any meaning to you...

Plug and play does what it should do. The end user should not "play" with the phone and then later you have to fix it. BTW you should change the password to something else than "password". This does not give you any security.

Can you give us a PCAP?

Can you get us a PCAP trace? Then we can see where the TLS goes wrong.

Yea, in that case a SIP trace would help. Probably a problem with the PSTN gateway or the dial plan. Or maybe you need to increase the "Maximum ring duration" in the admin settings.

Before upgrading, make a backup of the working directory of the PBX. Then if anything goes wrong, you can always move back. This will not help you with the firmware of the phones, though...

It assumes the support of the registered device for "check-sync". If it does not work for your soft phone, that's a feature! Also, some devices try to be smart and just reload the configuration. If nothing has changed (that requires a reboot), it will not reboot.

In version 4, we are promoting the use of RTCP-XR. The "XR" stands for extended reports, where both the phone and the PBX are reporting to each other on how the call quality is. The bottom line is the "MOS", which is a value between 1 and 5. The calculation of the MOS is a complex topic, espcially when it includes bursts. We include the report in the CDR, so that administrators and providers can actually track it. There you can find more than just the MOS, for example also information about bursts, packet loss, jitter and so on.

Hey Matt maybe one day you'll be a Linux guru with all that Sheeva stuff!

Sounds like you should use the gateway mode and set the domain and outbound proxy to that IP address. I guess they also gave you a password, so put it into the password field; the user name then needs to go into the field above the password. DTMF is negotiated automatically, the PBX support RFC2833 (which is now RFC4733) and the PBX indicates that is supports it.