Summary
The SoundStation IP 550 supports all required innovaphone features and is therefore qualified as recommended product.
The configuration of the device was complicated, since advanced features like 'corporate directory' cannot be configured via the web interface.
- G722
- superior sound quality
Certification Status
The tests for this product have been completed.
Testing of this product has been finalized July 25th, 2008.
Test Setup
The Metadirectory Server is used as corporate directory server for the tested device. The G722 capable phone was needed to test the support for G722.
Version
Firmware Version:
3.0.1.0032
innovaphone Firmware:
Version: 7.00 dvl 08-70108
Estos Metadirectory:
Version: 2.0.0.962
Device Setup
Tested feature
|
Result
|
Register Device w/o specific configuration (requires DHCP)
|
No
|
DHCP is default
|
Yes
|
DHCP yields timeserver and time displays correctly
|
Yes
|
SNTP config has TZ string for timezone/dst autoconfig
|
Yes
|
DHCP yields correct default gateway
|
Yes
|
Device supports magic registration (e.g. by serial)
|
No
|
Fixed registrations works
|
Yes
|
Device registers w/o Extension (just by name)
|
Yes
|
Device registers by extension
|
No
|
Device registers with password
|
Yes
|
Device registers multiple identities
|
Yes
|
Device supports STUN protocol
|
No
|
Device sends NAT - keepalive messages
|
No
|
Device refreshes the PBX registration
|
Yes
|
Device supports SIP over TCP
|
Yes
|
Device supports SIPS (SIP over TLS)
|
Yes
|
Device supports HTTPS
|
No
|
Device supports VAD (Voice activity detection)
|
Yes
|
Test Results
Basic Call
Tested feature
|
Result
|
call using g711a
|
Yes
|
call using g711u
|
Yes
|
call using g729
|
Yes
|
call using g722
|
Yes
|
Overlapped sending
|
No
|
Early media channel
|
Yes
|
Device shows called id number
|
Yes
|
Device shows called id name
|
Yes
|
Device shows called id display info
|
No
|
Fax using T.38
|
N/A
|
CGPN can be supressed
|
No
|
Reverse Media Negotiaton
|
Yes
|
Device shows CDPN/CGPN on incoming call
|
Yes
|
Device shows CDPN/CGPN on outgoing call
|
Yes
|
Device shows connected number
|
No
|
Device shows diverting number
|
No
|
Device supports distinctive ringing
|
Yes
|
Device supports codec renegotiation during a conversation
|
Yes
|
Device shows correct display message in case of busy CDPN
|
No, just busy tone.
|
Device shows correct display message in case of not existing CDPN
|
No, just busy tone.
|
Device shows correct display message in case that the call is declined
|
No, just busy tone.
|
Voice Quality OK?
|
Yes
|
DTMF
Tested feature
|
Result
|
DTMF tones sent correctly
|
Yes
|
DTMF tones received correctly
|
Yes
|
Hold/Retrieve
Tested feature
|
Result
|
Device handles incoming hold (sendonly) correctly
|
Yes
|
Device can put a call on hold using correctly(inactive or sendonly)
|
Yes(but no MoH)
|
Transfer with consultation
Tested feature
|
Voice Ok?
|
MoH Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
Yes
|
Yes
|
inno1 calls inno2. inno1 transfers to testphone.
|
Yes
|
Yes
|
inno1 calls testphone. inno1 transfers to inno2.
|
Yes
|
Yes
|
inno1 calls testphone. testphone transfers to inno2.
|
Yes
|
Yes
|
testphone calls inno1. inno1 transfers to inno2.
|
Yes
|
Yes
|
testphone calls inno1. testphone transfers to inno2.
|
Yes
|
Yes
|
Transfer with consultation (alerting only)
Tested feature
|
Voice Ok?
|
MoH Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
Yes
|
Yes
|
inno1 calls inno2. inno1 transfers to testphone.
|
Yes
|
Yes
|
inno1 calls testphone. inno1 transfers to inno2.
|
Yes
|
Yes
|
inno1 calls testphone. testphone transfers to inno2.
|
Yes
|
Yes
|
testphone calls inno1. inno1 transfers to inno2.
|
Yes
|
Yes
|
testphone calls inno1. testphone transfers to inno2.
|
Yes
|
Yes
|
Blind Transfer
Tested feature
|
Voice Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
Yes
|
inno1 calls inno2. inno1 transfers to testphone.
|
Yes
|
inno1 calls testphone. inno1 transfers to inno2.
|
Yes
|
inno1 calls testphone. testphone transfers to inno2.
|
N/A
|
testphone calls inno1. inno1 transfers to inno2.
|
Yes
|
testphone calls inno1. testphone transfers to inno2.
|
N/A
|
Blind Transfer (alerting only)
Tested feature
|
Voice Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
Yes
|
inno1 calls testphone. testphone transfers to inno2.
|
Yes
|
testphone calls inno1. inno1 transfers to inno2.
|
Yes
|
Broadcast Group & Waiting Queue
Tested feature
|
Result
|
testphone makes call to a Broadcast Group. inno1 picks up.
|
Yes
|
inno1 makes call to a Broadcast Group. testphone picks up.
|
Yes
|
testphone makes call to a Waiting Queue. inno1 picks up before announcement is played.
|
Yes
|
testphone makes call to a Waiting Queue. inno1 picks up after announcement is played.
|
Yes
|
inno1 makes call to a Waiting Queue. testphone picks up.
|
Yes
|
Other Features
Directory
Tested feature
|
Result
|
Device built-in directory
|
Exists
|
Yes
|
Can be dialled from
|
Yes
|
Does CLI resolution
|
No
|
Hands free
Tested feature
|
Result
|
Loudspeaker operation works fine
|
Yes
|
Hands free works fine
|
Yes
|
Volume adjustable during call
|
Yes
|
Keys
Tested feature
|
Result
|
Device has speed dial keys
|
Yes
|
Device has programmable function keys
|
Yes
|
Configuration
innovaphone configuration
The Polycom IP550 registers at the PBX as a normal PBX user.
Polycom configuration
On the IP550, only the Line - settings have to be configured.
LDAP configuration
To configure a polycom device to access to a corporate directory via LDAP, following points must be resolved:
- The Estos Metadirectory server of version 2.0.0.962 is installed and configured. Do not use a version lower than the one mentioned in this article(e.g 2.0.0.718) since it will be not compatible to polycom devices.
- To enable advanced phone features like corporate directory on a polycom phone, you must order an additional license. The TFTP boot server used to store the polycom configs and firmware files, must also contain the license needed to activate the directory feature.
- configure the directory settings in the sip.cfg file. Use the polycom manual for reference.
- activate the 'corporate directory' feature in the sip.cfg file by the following option:
feature.19.name="corporate-directory" feature.19.enabled="1"
Category:Compat