Vodia PBX

Yea this is really not the right place to ask this question... I have heard that the snom forum will be alive soon. Just one idea :-P You can actually use snom ONE as a pure provisioning server for snom phones. You'll have to tweak the templates a little bit, so that the outbound proxy etc are pointing to the other device. This will make it possible to provision snom phones with multicast PnP or even with the new XML-RPC.

When a hunt group calls extensions, it never goes into the extensions mailbox. Except when you explicitly send them to the mailbox in the final stage (usually with prefix 8). The hunt group might be also a way to solve the problem if you want to call the extension directly without that extension mailbox picking up ever. Just call the extension through a hunt group, which has only this one extension in stage 1 (with a long ring duration).

Ops mailbox was full again... Please try again.

It is actually not either or. The automatic flag defines the transitions from active to inactive and from inactive to active. The user may do additional transitions. Classical example is when the assistant arrives earlier in the morning or leaves earlier, she can make the transition earlier. The difficult part is later because the service flag does not wait. But in a realistic environment, the assistant would just see that the LED went on and changes it back to off until it really has to be on.

I would definitively recommend to use 8.7.3.19 for the 710. Although it sounds like a rounding error, those two versions are quite different.

Supporting that is easy on the surface, and I think the PBX did and does that for many years. If someone subscribes for the presence state the PBX happily relays the messages. However the true problem is that you have to merge device state and PBX state. If it great if that soft phone feels that it is available, but what if there is a call recording a voice message of that extension because the DND has been set? Our answer was so far to leave the SIP presence state alone and use a PBX extension state in parallel. The PBX extension state is set only by the PBX, regardless of what device is registered. This way others can see when the extension is on a cell phone or on a ATA, without having to worry about those devices capability to generate PUBLISH messages.

Send a private message with a link, e.g. DropBox.

Yes that would be definitively a bug. Calls should be deleted at least after the PBX does not receive any more media for more than 180 seconds I believe. If you can reproduce it and get us a PCAP trace it would be great.

In theory it is allowed to switch codecs during the conversation. But many implementations have problems with this. For example, some DSP cannot be reprogrammed quick enough when a codec change has been detected. Locking the codec down has the disadvantage that the PBX must start transcoding (translating), which reduces the conversation quality. So there is a trade-off, the default favors the quality.

What version are your currently running on the PBX and on the phone? Assuming they are more or less up-to-date, this sounds like a routing issue. Are you using TLS? Then that problem should not exist at all.

We have found a subtle problem with the trunk settings that affects version 5.0.3 t o 5.0.6. The introduction of the conditional headers in 5.0.3 had the side effect, that the Privacy header could always contain the value id, regardless of the call being anonymous or not. The value should be changed to "{if clip true}id{fi clip true}" or just leave the field empty. The easiest way to check the value of the header is to switch to the text-based view for the trunk editing. There you will find the value HeaderPrivacy. We will change the default for this header in the next version. Sorry for the inconvenience.

You need to check if there is a Privacy: id header present. The easiest way to check that is to go the text mode in the trunk settings, and look for the Privacy setting. Take the id out if there is something,

That's actually a feature that we had since 5.0.0. Some phones (snom 7xx, 8xx, m9, and possibly also others like Polycom) have a client certificate X.501 build in that serves like a passport, signed by some trusted authority. The PBX is asking for that password upon connection establishment and when available, it trusts the phone to be that MAC address. This makes it very easy to have a secure provisioning. For the phones that don't come with client certificates, we added a new method in 5.0.6 where we open a window in time where the PBX trusts the phone also without certificate. This is not as secure as certificates, but in most practical applications during the installation phase okay and actually very convenient. This replaces the old settings which could have had the name "always trust MAC which the PBX can see in layer 2 of the Ethernet packet", and it has the huge advantage that is also works in the cloud.

Did you modify any of the templates? Then you might have problems. If you did, try to clean that up again the latest 5.0.6 has a lot of changes and it is better to start with a "fresh" provisioning template. Because there is no more "trust the MAC address" (always) option any more, you should enable the PnP from the domain accounts overview. Then the PBX will provision new password in the phone, so that next time you dont have to open the trust MAC for the extension.

That link should not be there any more. Did you change the dom_header.htm? Starting the provisioning should be in the action action selection dropdown, 2nd from the top.

We need to set up a test for that. It is easy to reproduce and then it should also be easy to fix that. I suspect this is the side effect of a fix that we did for phones that loose registration while the hunt group is ringing.

We changed something in 5.0.6 because of the video relay. It could be that this already solved the problem, but we need to check.

That's actually okay. It tries snom720.htm and snom720-000413XXXXXX.htm, and the one with the MAC should be working. It is mapped to the same file as the snom720.htm before.

Hmm yea we have to take that link out or make it possible to set up a new CO-line from there.

With the analog part I can not help you... However on the SIP side, if you can, use a VPN that makes the setup a lot more easier. Then you can just use a gateway trunk with full control over all headers, so that it should be easy to get the gateway working.

Yes, sorry there were a lot of changes in the web interface and also the new MAC-based provisioning required changes in the file names. If you have changed pnp.xml, I would revert back to the default and check what changes you did to the pnp.xml and if they are still necessary.

We have released a new version 5.0.6 with some greatimprovements. First of all, we got back from the old PAC/WAC/SAC into theweb world by supporting websockets now. This relatively new standard is usedfor real-time updates from the server to the web browser. Classical examplesfor this include instant messaging, but we can use this also for updatingextension status on the web client and showing active calls. These things weredone in previous versions of the PBX using AJAX, but this technology came atthe price of a high traffic overhead and always had the danger of missing anupdate. It was a hack to be honest. The new websocket architecture is clean andIMHO very promising for client user interface design, and who knows maybe for telephonyin general. The design in 5.0.6 can be improved, give us a few versions to prettifyit and add features that did not make it into the first version. The second big change is regarding the provisioning. This areais the most critical area for those persons, who have to install the PBX. We haveadded the certificate-based provisioning which works like a charm, but faced problemswith customers who were using phones that don’t have certificates. We had acase where a reseller was installing a phone and we were sitting there for twohours trying to get the “plug and play” working just to find out that the passwordwas put into the wrong place. This was calling for action. The new provisioningopens a window in time when the PBX trusts the MAC address of the phone, and duringthat time the PBX provisions a secret into the phone that can be used later forauthentication purposes. This works very well, even in the cloud and stillprovides a reasonable security. We will have to explain this in more detail on theWiki and even take some short videos on how to plug phones into the system. Last not least, we added domain logging. Now when you are ina domain and click on the log link, you will see only messages that affect thedomain. For the system administrators, this makes it easier to filter all othermessages out. And for the domain administrator this is the first time that thisperson sees log messages at all. This underlines our determination to makecloud deployments easier. The new version is available as usual from the wiki at http://wiki.snomone.com/index.php?title=Release_5.0.

You can create CO lines in the trunk, but not from the account list.

The madness is that according to the SIP standard, the one who sent an INVITE cannot cancel the request before a response have arrived. That makes the whole procedure difficult, and it is even difficult to say which device is buggy. In an extreme case, the phone does not respond for an hour and then the PBX is supposed to send the CANCEL. You can imagine what that means for keeping the memory clean from garbage. I would definitively use TLS instead of UDP, not only because of this. The next problem that you will be facing with UDP is fragmentation, not to mention eavesdropping and ALG messing with the packets. If HTTP would have used UDP, nobody would talk about the world wide web today anymore.

You can see it this way: The snom ONE mini is a piece hardware. You can run snom ONE on a PC, in Windows, in Linux, if you like, on a MAC (e.g. MAC mini), or if you like you can run it on a snom ONE mini. There are other ARM-based platforms available too, check out the GuruPlug platform for example. The special thing is that with the snom ONE mini, you get a preinstalled old version of the snom ONE software. IMHO the snom ONE mini hardware is great for small offices that need low-power and silent hardware. If the pre-installed software is insufficient, you can upgrade to version 5.