Vodia PBX

If you are using option 66 with a DHCP server, you can just put the IP address of the PBX into the option 66 (and leave option 67 empty). For example, "192.168.12.43". Depending on the software version that you using on the phones, you have to put in "http://192.168.12.43" or "tftp://192.168.12.43". The 3xx series does not come with built-in certificates; therefore you must "trust the MAC address" (which is a version 4 setting for provisioning; in version 5 we have changed that concept to be a lot more secure). If it all does not help, send us a private message with remote HTTP access to the phone and the PBX and we'll fix it from here.

snom 300, 320, 360, 370, 720, 760, 821, 870, m9, PA1 and MeetingPoint.

That version simply does not support snom 710. snom 710 support was introduced in version 5.

What version of the PBX are you using?

If the trunk is in the domain, then it will be only in the domain. For global trunks, REFER will be always accepted no matter where the trunk ends up

Did you try the setting "Accept REFER" in the SIP trunk? Depending on your version, you will see a setting "assume that call comes from extension" where you need to put an extension number in that will be charged for the call.

The template should actually contain the time zone already. Can you check what has been generated in the "generated" folder?

This is probably at least the right area. We need to dig into the documentation again to see what could cause this kind of display. But I don't exclude that this is a "feature".

Hmm. Yea that should work. I have no idea why it should not work. Factory reset?

In the PBX. There is a folder in the working directory called "generated" (unless you have turned that feature of because of security concerns).

You will have to add this by yourself... The new snom ONE Polycom templates contains only the things that should be different from the defaults.

That's a complex question. We are keeping the SOAP calls unless there is a real reason to change them. New calls are preferably JSON/REST; but the number of actual available methods is still in its beginnings. For measuring the PBX status, there are SNMP sensors available. http://wiki.snomone.com/index.php?title=SNMP_Ports has more information.

110 is the emergency number in Germany. Can you check the m9 web interface if you spot the 110 in the "Security Settings" under "Emergency Numbers"?

Well calls to the cell phone are trunk calls, and they do cost money (if connected). If the purpose of your report is to find out what costs were caused, then this is correct.

We had that in the old times (pbxnsip) as a provisioning parameter. Polycom has the default to restore the volume--I guess that makes sense because the volume differs significantly depending on who is calling (device) and who is talking. Also it helps to keep the system in a kind of calibrated state. But of course you can change the polycom provisioning template and change the setting.

We make the log level higher, those messages are indeed annoying.

If you are only interested in trunk calls, you can forget about primarycallid and also callid. "SELECT * FROM cdr WHERE trunkid > 0" would be my first guess.

Debian has good documentation, for example http://wiki.debian.org/NetworkConfiguration shows you how to configure it by editing config files.

You have to keep in mind that those CDR are call leg CDR. That means you typically get two records for each telephone call. They contain the same Call-ID, so that you can group them together if you want. Most users want to see only the CDR for the trunks for billing purposes. When then trunk is empty, those users can just discard the record.

When the PBX updates the state of the buttons it does that by sending out those IM messages.

There is a translation item missing. We'll add it...

So you mean you find an address book entry via LDAP and now you want to actually call the person? How about lifting up the handset?

First of all, I would set the country code in the domain to "1", so that the PBX knows that 10 digits are the same like 1 + 10 digits. On the trunk there is a setting called "Rewrite global numbers" where you can instruct the PBX to use a specific format for outbound calls. You can do this differently for each trunk. If you want to present only the 911 calls with 10 digits and all other with 11, you can for example set up two different trunks--one for 911 and another one for all other calls.

We have made a newer build, 5.0.10m: http://snomone.com/downloads/snomONE/version-5.0.10m.xml, which we can hopefully soon turn into a 5.1.0 release. Your feedback and help is as always welcome.

Okay... TLS_RSA_WITH_AES_256_CBC_SHA would be a candidate, however in TLS1.0 is it vulnerable anyway. RC4 might be old, but does not have the vulnerability. Is there any place where you can control what ciphers are being offered? We have to add TLS1.1 anyway, and then it makes sense to support the AES CBC modes as well.