pbx support

Please verify "Explicitly specify pickup preference" under the extension that is trying to pickup the call.

There seems to be some minor issue in that area. We will fix it in the future versions. It is not a blocker though.

Basically, snomONE would try to open the wav file using the browser. In the end the browser will use its default plugin for playing the wav file to play the selected file. If Safari can wav files in general, it should be able to play this file too.

We are conducting a poll to see what different types of operating systems are being used for snomONE (or pbxnsip) software. Getting this data is useful for us to see which one is the most popular OS for snomONE. Your participation is appreciated. Thanks

You can keep that field empty. But once you put anything there, then you have make sure you have the "proper" extensions are set.

You can add it to the address book at the domain level and then black list it there.

Which version of the software are you running? There were some issues in that area in the earlier versions. If you are running 4.5.0.1090, you should be able to do that.

Guys, let's stop this back and forth until we sort out the license issue that we talked about. Once you have the proper licence, this problem must go away. BTW, your attachment just shows that PBX is redirecting the user for a login attempt (302 Moved Temporarily).

Please try http://downloads.snom.net/snomONE/win64/v4.6/pbxctrl-4.6.0.1002.exe

Did you really navigate to "Admin > Settings > Ports" and looked at the "Port Range Start" and "Port Range end" as the wiki link says?

Please take a look at this wiki page http://wiki.snomone.com/index.php?title=RTP_Ports.

Assuming the calls were fine when running on the VPN, the new setup might have some networking issues. The firewalls on your network or the remote network could be blocking the UDP(RTP) traffic.

PBX versions 4.3 and earlier had both pbxnsip and snomONE versions. So, you could run the pbxnsip binary with licence created for those binaries. Since features and functionality of these 2 binaries are almost identical, we no longer create pbxnsip binaries. We create just snomONE binary and let the license key do the magic for enabling / disabling the features. If the phone is stuck on "updating initial configuration", then either you can reset (not reboot) the phone or use another TFTP server to serve the files or contact Polycom.

What do you mean by "they will not sell the PNP files"?. All the files are already in there in the PBX as templates. Whether the PBX does plug and play with the phone or not is a matter of license key. That's all.

Well, The software is a snomONE version. Running pbxnsip license may not be a good idea. It would be better if you can convert this license into snomONE license. Also, it is advisable to upgrade the software to 4.5.0.1090 ( Epsilon Geminids )

If you are running the pbxnsip version with pbxnsip license, then there should not be any issue. BTW, what is the version number (Admin->Status page) of the PBX?

We have already fixed it, under test now. If you are running centos64 bit version, then please try http://downloads.snom.net/snomONE/centos64/v4.6/pbxctrl-centos5-4.6.0.1002. If you are using other OS, let us know. As usual, please backup and then upgrade. Best is to try it on the test system and then deploy.

What version of the snomONE software & license are you using?

Not sure what the problem there. We are able to write to a shared drive (which is on a remote system) with the syntax we discussed earlier.

Today only ACD and Hunt can have their own music on hold. All the extension will have the domain level MoH. Not a big deal, technically, to extend it to the extension. Maybe in the future versions.

Hmm.. good to hear that it solved the issue. We will try to put some checks to avoid these issues in the future releases.

Is 4.5.0.1092 ok? That's the latest. http://downloads.snom.net/snomONE/freebsd/v4.5/pbxctrl-freebsd7.0-4.5.0.1092

If the problem is with the incoming call, then please take a look at http://wiki.snomone.com/index.php?title=Inbounds_Calls. Regarding the tcpdump, please open a ticket on support.snom.com and attach the tcpdump file there.

PBX really have to run under the admin/system account. The easy thing to do is to change the permission on the shared folder to give write access to remote users.

Probably PBX could not identify the trunk for whatever reasons. Can you set "Trunk->Explicitly list addresses for inbound traffic:" to the gateway address (192.168.0.250:5062 in this case) and test it again?