Vodia PBX

There are many differences between snom ONE and Asterisk. Asterisk uses their own proprietary protocol to talk to hardware. Because of the open source nature of Asterisk, other companies apart from Digium were able to come up with other PC cards as well, like Zycoo. But the standard which is used with the PC cards is pretty much a proprietary Asterisk-standard. snom ONE instead uses the "session initiation protocol" (SIP) instead to ensure that devices from different vendors can work together.

I don't think that will work. As far as I can tell, that is a PC card that requires external software before it talks SIP. My general recommendation is to go for external gateways (see http://forum.snomone.com/index.php?/topic/4009-compatible-pstn-and-isdn-gateway/).

The good news is that it runs Debian and that documentation is pretty good. The documentation for the PBX has only very few links to the actual hardware/OS: Essentially it is that page where you can set a static IP address for the system.

The file structure has changed for the snom phones. My recommendations: Make sure that you don't have any customized files either through the template editing from the web interface or in the html folder Provision a phone and take a look at the generated folder. There you can see what files are being generated. Then you can start modifying the templates for those files.

It must be either port 22 (which is the SSH default) or 8722 unless you changed it by yourself. Last resort would be a port scan; but snom used only those two ports.

I believe what we will do is to change the ringtones.xml like this: <tone name="internal" type="internal"> <vendor ua="Polycom.*">Internal</vendor> <vendor ua="Cisco-.*"><Bellcore-dr2></vendor> <vendor ua="Grandstream HT.*"><Bellcore-dr1></vendor> <vendor ua="snom.*">alert-internal</vendor> <vendor><http://127.0.0.1/Bellcore-dr2></vendor> </tone> Then the phones will use the setting for controlling the internal ring tone, which is a settings that can be controlled by the user through the local menu. The same applies for external. There is another setting for groups, which will be used for the custom1-4 (they will be all the same then).

There is a client side of it and a server side. On the client side, the general rules of trusting the server apply. The server has to be in the list of trusted Root CA. The best solution is to use a certificate that is issued by one of the generally trusted CA, so that you can also use https from your browser. By default the snom phones don't verify the server; if you want to make sure that there is no hanky panky going on you have to change that policy before provisioning the device. In the first provisioning you can actually change that policy, so that subsequent requests will verify the certificate. For the server, the question is "who are you?". Certificate-based authentication works very nicely when the phones have a client certificate installed; however for snom that is only the case for 7xx, 8xx and the m9 devices. For 3xx devices, all devices have the same certificate :-/ so you cannot trust them and instead have to set up username and password for automatic provisioning.

Try SSH on port 8722. Some early devices did not use the standard port for SSH, instead try to "hide" it by choosing that port number.

snom marketing is taking care about the hardware (mini, SoHo). Not sure if SoHo is still being sold, the focus is definitively on mini. The minis are looking good; they are are well received in the market as far as we can tell by looking at the software activation.

AFAIK the 7xx series has a list of trusted root CA that should match your cert as well. I dont think that the problem is here. I would definitely check the log file of the phone, there must be some hint what is going on.

There is "agent login/logout" which deals with the availability to receive calls from ACD. If you want a general login/logout, most people just use DND (Do Not Disturb). Also there is hot desking, where customers can redirect all traffic on an extension to a physical location. http://wiki.snomone.com/index.php?title=Call_Forwarding Re-provisioning phones every morning does not sound like a solution to me.

There is no "exhaustive" list. It all depends on the port settings in the PBX. But anyway because this is of general interest, here is a summary: SIP: Here you may have zero, one or more UDP, zero, one or more TCP or TLS ports. The port numbers are set in the web interface of the PBX. Ports may be bound to IPv4 and IPv6 addresses. By default, they are bound to both. Default is 5060 for UDP, 5060 and 5061 for TCP/TLS. HTTP: Here you may have zero, one or more TCP or TLS ports. The port numbers are set in the web interface of the PBX. Ports may be bound to IPv4 and IPv6 addresses. By default, they are bound to both. Default is 80 and 443. TFTP: Here you may have zero, one or more UDP ports. The port numbers are set in the web interface of the PBX. The default port is 69 (both for IPv4 and IPv6) SNMP: Here you may have zero, one or more UDP ports. The port numbers are set in the web interface of the PBX. The default port is 161 (both for IPv4 and IPv6) NTP: Here you may have zero, one or more UDP ports. The port numbers are set in the web interface of the PBX. The default is no port. LDAP: Here you may have zero, one or more TCP ports. The port numbers are set in the web interface of the PBX. The default port is 389 (both for IPv4 and IPv6) RTP: Here you have to specify a port range. Default is 49152 to 65535. If you want to lower the risk that other (potentially malicious) applications grab traffic from those ports, you should make the port range shorter; but for every call that you want to run on the system you must have at least 4 ports available. For example, if your system should be able to support 10 concurrent calls, you need to have at least 40 ports in that range.

This is a topic that we need to address properly. Workaround include the editing of ringtones.xml, but it is very difficult for end users to just change the ring melody.

Send an email to sales with the old invoice...

Well the snom web server does not have snom ONE files any more. On snomone.com, we have only 4.5.1 (see http://wiki.snomone.com/index.php?title=Updates).

In newer versions of iptables, you can actually use a owner rule: Try "iptables -m owner --help" to see if that is available on your system.

The later versions of snom ONE on SoHo/mini change not only the password for the PBX web interface, they also change the Linux password. IMHO a very important step for security those embedded systems. The usual passwords are snomONE and nosoup4u (lower case). You should be able to make an upgrade from the web interface if you are on 4.5.0.1024. In 4.5.0.1090 you can definitively set the password also for the root/Linux account. If you upgrade the SoHo to 4.5.1 do the check on https://snomone.com/upgradev4 to see if you need a new free license. 4.5.1 needs licenses which are bound to the MAC. If that upgrade check fails send us an email before you upgrade to 4.5.1 so that you are not ending up without license.

Oh if you are getting to the single user mode on Linux, then should be able to set the root password for the system. Did you just try passwd? I am not the biggest Linux expert, but we had a similar case with VMware and there the single user mode was the key. There is some information in the Internet about this, e.g. http://www.ghacks.net/2009/02/25/how-to-reset-the-root-password-in-linux/

If you still have file system access, just edit the pbx.xml file. There is a hash for the admin password. Clear it and restart the system. Then you can log to the web interface in without password as system administrator.

My first guess would be that the registration is not stable. Can you have the PBX send an email when the registration changes for that extension? You can set that in the registration tab in the extension settings (domain mode).

Yes, it stops at 20. Reason: 40 extensions are generally too much for the device. Remember that this is an embedded system with a small ARM processor, just like your smart phone...

Looks like the problem is that your destination advertises both IPv4 and IPv6 addresses. In 4.5, the PBX prefers IPv6. If your server has no IPv6 connectivity, that will fail. Solutions: Get IPv6 working Change the DNS so that you advertise only IPv4 Use the IP address Start the service with the argument --ipv6 false (e.g. pbxctrl --dir /pbx/dir --ipv6 false) Upgrade to version 5, where IPv4 is being preferred against IPv6

If you have any business with snom, then this is the wrong forum for you. This includes the decision to discontinue snom ONE as a cross-subsidized product. Thank you for your understanding.

Well, there are server ports and there are client ports. For server ports, having SIP (UDP/TCP/TLS) and HTTP (TCP/TLS), possibly TFTP (UDP) and maybe even SNMP (UDP) should be sufficient. Client ports like the DNS client can actually take random numbers. RTP is somewhat different first of all because it is a server port and you must specify a port range there. RTP is difficult to track down with netstat, but I don't think that we are trying to hide port numbers here. http://wiki.snomone.com/index.php?title=Ports has some information what the ports are actually doing. OF course the protocols itself are described in the RFC, we don't want to repeat that in the Wiki. BTW in Windows it seems to be easier to control the firewall, all you need to say there "trust that application". Not sure if there is a equivalent for CentOS/iptables.

Hi Vance, we did not promulgate the business model that you pursue. Sorry if you feel you got bumped into economy class.