Summary
Due to the various not working features(e.g. hold) ant the complicated setup on innovaphone side, innovaphone does not recommend to use this 3rd party product.
Version
3rd party Firmware Version:
1.54.004
3rd party Hardware Version:
PA168S
innovaphone Firmware:
Version 6.00 sr2-hotfix4
Certification Status
The tests for this product have been completed.
Testing of this product has been finalized June 4th, 2008.
Device Setup
Tested feature
|
Result
|
Register Device w/o specific configuration (requires DHCP, GK detection and “magic” alias)
|
No
|
DHCP is default
|
?
|
DHCP yields timeserver and time displays correctly
|
N/A
|
SNTP config has TZ string for timezone/dst autoconfig
|
N/A
|
DHCP yields correct default gateway
|
Yes
|
Device supports magic registration (e.g. by serial)
|
No
|
GK discovery works
|
No
|
Fixed GK registrations works
|
Yes
|
Registrations supports GK-ID
|
No
|
Device registers w/o Extension (just by name)
|
No
|
Device registers by extension
|
Yes
|
Device registers with H.235 password
|
not tested
|
Device registers multiple identities
|
No
|
Device can configure IP address, GK attributes (gk-id, gk-ip, alias) from DHCP (vendor specific)
|
No
|
Device refreshes the PBX registration
|
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
|
Overlapped sending
|
No
|
Early media channel
|
?
|
Device shows called id number
|
N/A
|
Device shows called id name
|
N/A
|
Device shows called id display info
|
N/A
|
Fax using T.38
|
N/A
|
CGPN can be supressed
|
N/A
|
Reverse Media Negotiaton
|
No
|
Device shows CDPN/CGPN on incoming call
|
N/A
|
Device shows CDPN/CGPN on outgoing call
|
N/A
|
Device shows connected number
|
N/A
|
Device shows diverting number
|
N/A
|
Device supports distinctive ringing
|
Yes
|
Device supports asymetric codec negotiation
|
No
|
Device supports codec renegotiation during a conversation
|
No
|
Device shows correct display message in case of busy CDPN
|
N/A
|
Device shows correct display message in case of not existing CDPN
|
N/A
|
Device shows correct display message in case that the call is declined
|
N/A
|
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 (remote) correctly
|
N/A
|
Device handles incoming hold (local) correctly
|
Yes
|
Device can put a call on hold using correctly(inactive or sendonly)
|
N/A
|
Transfer with consultation
Tested feature
|
Voice Ok?
|
MoH Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
No
|
No
|
inno1 calls inno2. inno1 transfers to testphone.
|
No
|
No
|
inno1 calls testphone. inno1 transfers to inno2.
|
No
|
No
|
inno1 calls testphone. testphone transfers to inno2.
|
N/A
|
N/A
|
testphone calls inno1. inno1 transfers to inno2.
|
No
|
No
|
testphone calls inno1. testphone transfers to inno2.
|
N/A
|
N/A
|
Transfer with consultation (alerting only)
Tested feature
|
Voice Ok?
|
MoH Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
No
|
No
|
inno1 calls inno2. inno1 transfers to testphone.
|
No
|
No
|
inno1 calls testphone. inno1 transfers to inno2.
|
No
|
No
|
inno1 calls testphone. testphone transfers to inno2.
|
N/A
|
N/A
|
testphone calls inno1. inno1 transfers to inno2.
|
No
|
No
|
testphone calls inno1. testphone transfers to inno2.
|
N/A
|
N/A
|
Blind Transfer
Tested feature
|
Voice Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
No
|
inno1 calls inno2. inno1 transfers to testphone.
|
No
|
inno1 calls testphone. inno1 transfers to inno2.
|
No
|
inno1 calls testphone. testphone transfers to inno2.
|
N/A
|
testphone calls inno1. inno1 transfers to inno2.
|
No
|
testphone calls inno1. testphone transfers to inno2.
|
N/A
|
Blind Transfer (alerting only)
Tested feature
|
Voice Ok?
|
inno1 calls inno2. inno2 transfers to testphone.
|
No
|
inno1 calls inno2. inno1 transfers to testphone.
|
No
|
inno1 calls testphone. inno1 transfers to inno2.
|
No
|
inno1 calls testphone. testphone transfers to inno2.
|
N/A
|
testphone calls inno1. inno1 transfers to inno2.
|
No
|
testphone calls inno1. testphone transfers to inno2.
|
N/A
|
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.
|
No
|
testphone makes call to a Waiting Queue. inno1 picks up before announcement is played.
|
No
|
testphone makes call to a Waiting Queue. inno1 picks up after announcement is played.
|
No
|
inno1 makes call to a Waiting Queue. testphone picks up.
|
No
|
Other Features
Directory
Tested feature
|
Result
|
Device built-in directory
|
Exists
|
N/A
|
Can be dialled from
|
N/A
|
Does CLI resolution
|
N/A
|
Hands free
Tested feature
|
Result
|
Loudspeaker operation works fine
|
N/A
|
Hands free works fine
|
N/A
|
Volume adjustable during call
|
N/A
|
Keys
Tested feature
|
Result
|
Device has speed dial keys
|
N/A
|
Device has programmable function keys
|
N/A
|
Configuration
The configuration must be done exactly like shown in the screenshots below, otherwise the phone will not refresh its registration at the PBX.
On innovaphone side you must create a PBX User, using as Hardware-ID the phone number assigned at the Arnesys phone.
On Arnesys side, it is important to configure only the phone number and the service address. All other registration fields should be left empty.