Vodia PBX

Well that is how the phone does it, the PBX has no control over that. But in defense of the phone, IMHO it does make sense to put the other call on hold. I personally hate it when I receive a call and someone tells me that I am already in a conference. I would rather give my confirmation first. Having the other call on hold achieves that.

For incoming calls the phones usually don't look up the name... at least that is provisioned automatically. The PBX already puts the name into the From header. If you still want to do an LDAP lookup, make sure that you are using 5.1.2; regarding LDAP this version makes sure that the common name is unique in the result list.

We have build 5.1.2 for Windows 32/64, CentOS 32/64, Debian 32/64, ARM (snom ONE mini), FreeBSD 64 and MacOS Intel/PowerPC. Currently this is only available as upgrade; for new installations in Windows and Mac for time being please use the 5.1.1 installer and upgrade to 5.1.2 from there. Those who are using Polycom phones need to take care about their TFTP directory. We have updated the documentation for Polycom phones at http://www.snomone.com/documentation/pnp_polycom; instead of loading huge (!) files that contain the firmware for all devices, they are now using the split-up images. This makes it also a lot easier to deal with the newer and older devices in the same installation. The release notes are to be found still on the Wiki (http://wiki.snomone.com/index.php?title=Release_5.1). Especially those who love short messages services on their cell phones will like the fact that the PBX can now text users upon arrival of voicemail messages and missed calls. There was some discussion on the http://blog.snomone.com/ about it already, but now the messaging also is available in user space.

Hmm. Usually everything that we do is to use UTF-8. Anyway, having § in the password is not worth the trouble. In the next version (will be 5.1.3) we will take it out and avoid the encoding problem altogether. Thanks for the heads up, must have been quite difficult to find that one!

Hmm. Maybe it is time to try this with the latest beta firmware. http://wiki.snom.com/Firmware/V8/Beta seems to have newer versions.

Just send sales a quick email with the status screen and the activation key and they'll get you a code that you can put into the web interface.

There is no default PIN. This is because default passwords and default PIN a an invitation for unauthorized access. The PBX actually generates a random password and AFAIK also a default PIN. Unless you disable the writing to the generated folder, the PIN can be found there.

Thanks for sharing this!

That has already been fixed for 5.1.2. Will be released soon, send me a PM with the OS if you would like to have a preview build.

Why 5.0.3? Better choose 5.1.1 (latest). What is in the domains directory? Do you have more than one domain?

Well according to the RFC, CANCEL cannot be sent before a provisional response (e.g. 100 Trying) has been received. This is not easy to implement, as the PBX then has to hold back the CANCEL until a response has been received; and keeping in mind that the response can be a 2xx class response, or even worse first a 18x response and then a 2xx response, the PBX has to then send the CANCEL and possibly also a BYE after this (actually it is also allowed just to send the BYE). It even gets worse, because all that stuff also depends on the transport layer, as TCP and TLS do not loose packets. Also keep in mind, that the PBX has to keep the transaction in memory for a long time, e.g. when there is absolutely nothing coming back from the other side. Anyway, I would start with looking at the traffic that the PBX sends out on trunks. If the PBX really immediately sends out CANCEL after INVITE, we would have to check the reason why is that so. For example, if could be that the transaction timeout was explicitly set to 0 seconds, which would explain such a behavior.

The log looks "beautiful" (especially with the generated files inline ) I would not use 8.7.3.19 for a snom 370... For that phone model, 8.4.35 seems to be a better choice.

You can always check in the generated folder what has been generated for the extension (unless you have turned the generation off). There you usually also see the passwords.

That also must be set up in the extension, in the registration tab. The point is to keep certain extensions on the radar.

Extension status means registration status. Changed e.g. with DND are not admin topic.

What version are you on? These items are fine in the L&G...

It still looks like that the MAC 000413236BA0 was not assigned to an extension and the extension has been opened for provisioning the phone. The phone fetches the right file https://192.168.13.8:443/prov/snom360-000413236BA0.htm, but then that file does not make it. Can you double check if the MAC is assigned to the extension and that the extension list shows the remaining time that the phone can be provisioned? Also, make sure that you don't have any old files in the html folder or in the webpage templates. If you have made changes in version 4, they would still be there in version 5. You can always check in the "generated" folder on the PBX what has been generated on the fly for the PBX. I assume that that does not contain any files for the extension. If it all does not help, give us remote access and we'll take a look.

The "noresource" is fine; that's just the way the SIP authors wanted it (read it as "no more resource"). When you open the device for PnP, by default it is open only for 10 minutes. You can change that in the provisioning settings. When you go the extension account view, you should see how many minutes and seconds are left for the provisioning (P 9:45 means 9 minutes and 45 seconds left).

Well the question was very general. The answers are scattered all over the Internet. The wiki (wiki.snomone.com) may be a good starting point.

You got a good point here. Buttons don't show the caller-ID. Not sure what is the best way to address this. Polycom has this "silent ringing" feature, so that the phone is essentially ringing in the hunt group like the other phones, just silent. This approach would have the challenge to tell the phone to change the ring melody from silent to audible. Which makes this path difficult to go. Another way would be to send instant messages to the phone, so that I would render it on the display. I know this would work for most snom phones; however not sure about the rest of the industry. Another approach would be to use the CSTA Browser for this. This would inherently have the limitation that only Windows clients are supported; but it would be possible to show short bubbles in the display when the call to the group comes in. Then the last approach I can think about right now would be to use the web browser for this. Now that we have websocket, we could add that to the user-screen. It would work on many platforms; however the question is how big the user-acceptance is for having the web browser open the whole day for such things.

It is debatable where is exactly should show. The way it is implemented is that it is like a mailbox message if the user starts the recording on his own. Historically it therefore showed up in the mailbox. I would not put it under the CDR, because CDR tend to get deleted relatively soon and I would think it is more natural if such a recording gets handled like a mailbox message (regarding archiving).

Well... it seems that snom has introduced a feature that waits for the user to commit changes explicitly with a save button. IMHO it would make sense that the phone automatically pushes the button when it has been provisioned. The main problem is that the PBX provisions a shared secret into the phone that will be used later on during the next reboot cycle. If that shared secret gets lost, the phone always needs to be provisioned like it was the first time. For phones that have a certificate built-in and if you did not change the default certificates on the PBX it should actually work even without saving anything at all, the the certificate establishes a trust relationship that does not require a shared secret.

Depends. If this is a user-initiated recording (a.k.a. adhoc-recording) it will show up in the mailbox. Only automatic recordings will be listed in the domain and under the recordings tab.

You have probably been blacklisted. If you have file system access, check the accesslist directory for new entries. The other thing you can check is iptables. Depending on your distribution, you might have to either turn iptables completely off or fiddle with the details.

Well you don't need a hunt group for that. If the other phones just want to see when the hunt group is ringing, all they need to do is monitor the hunt group.