Fraktul: The phones should have a RAL value, the sum of these should not exceed the RAL specifications of the device you are using.

Laymans terms: Each device in the wiring loop uses so much power, the device can only supply power up to its specification on each port so the sum of the power values each phone uses cant exceed this power value.

Eg there is no magical 'phone usage' value for all phones, you might have 4 phones work fine then switch to 3 new phones which are greedy on the power and find there is not enough power to drive these.

Maverick:
First off security is a big issue for every one and hence the reason why we are deploying the network the way we are with locking down Configs / Passwords etc, at this stage it is not possible for sniff the details from your config files, it is fully encrypted with all user names and passwords so sniffing the packets will not give away user details unlike some of the other services out there .

Encrypting the configs and encrypting the SIP auth process are two different things, perhaps you are reffering to using CHAP for the auth process in which case the username is actually sent in plaintext. Unless you are encrypting the data stream before the SIP auth in other words its easy enough to get the username, if you are in a position to sniff traffic in the first place (unlikely with UBS connections).