Howto:Siemens Gigaset S685IP - Siemens -Testreport: Difference between revisions
Jump to navigation
Jump to search
m (New page: ==Summary== ==Certification Status== <!--{{Template:Compat Status "tested"}}--> {{Template:Compat Status "in progress"}} <!-- {{Template:Compat Status "certified"|certificate=Tpl_sip.b...) |
No edit summary |
||
| (41 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
==Summary== | ==Summary== | ||
The Siemens Gigaset S685IP DECT phone supports all required innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F|recommended product]]. | |||
The usage of wideband codecs of the phone were tested successfully. The integration of the innovaphone voicemail in the Gigaset solution is possible. The message waiting indication will be displayed on the handsets. The handsets support 3-party conference calls. | |||
Currently, the phones cannot access a LDAP phone book directory. The S685 IP base-station supports up to 2 concurrent VoIP calls. | |||
==Certification Status== | ==Certification Status== | ||
{{Template:Compat Status "tested"}} | |||
{{Template:Compat Status "in progress"}} | <!-- {{Template:Compat Status "in progress"}} --> | ||
<!-- {{Template:Compat Status "certified"|certificate= | <!-- {{Template:Compat Status "certified"|certificate=Siemens Gigaset S685IP_-_Siemens_-_3rd_Party_Product_-_Desc-product-cert.pdf}}--> | ||
<!-- {{Template:Compat Status "tested"}} --> | <!-- {{Template:Compat Status "tested"}}--> | ||
<!-- {{Template:Compat Status "rejected"}} --> | <!-- {{Template:Compat Status "rejected"}} --> | ||
Testing of this product has been finalized January 11th, 2011. | |||
==Version== | ==Version== | ||
Firmware Version: | Firmware Version: | ||
022270000000 / 047.00 | |||
EEPROM version: | |||
185 | |||
innovaphone Firmware: | innovaphone Firmware: | ||
v8 HotFix8 (80500.28) | |||
== Test Setup == | == Test Setup == | ||
| Line 34: | Line 38: | ||
|---- | |---- | ||
|Register Device w/o specific configuration (requires DHCP) | |Register Device w/o specific configuration (requires DHCP) | ||
| | |No | ||
|---- | |---- | ||
|DHCP is default | |DHCP is default | ||
| | |Yes | ||
|---- | |---- | ||
|DHCP yields timeserver and time displays correctly | |DHCP yields timeserver and time displays correctly | ||
| | |No, set static to public NTP server | ||
|---- | |---- | ||
|SNTP config has TZ string for timezone/dst autoconfig | |SNTP config has TZ string for timezone/dst autoconfig | ||
| | |No, set static to public NTP server | ||
|---- | |---- | ||
|DHCP yields correct default gateway | |DHCP yields correct default gateway | ||
| | |Yes | ||
|---- | |---- | ||
|Device supports magic registration (e.g. by serial) | |Device supports magic registration (e.g. by serial) | ||
| | |No | ||
|---- | |---- | ||
|Fixed registrations works | |Fixed registrations works | ||
| | |Yes | ||
|---- | |---- | ||
|Device registers w/o Extension (just by name) | |Device registers w/o Extension (just by name) | ||
| | |Yes | ||
|---- | |---- | ||
|Device registers by extension | |Device registers by extension | ||
| | |Yes | ||
|---- | |---- | ||
|Device registers with password | |Device registers with password | ||
| | |Yes | ||
|---- | |---- | ||
|Device registers multiple identities | |Device registers multiple identities | ||
| | |Yes | ||
|---- | |---- | ||
|Device supports STUN protocol | |Device supports STUN protocol | ||
| | |Yes | ||
|---- | |---- | ||
|Device sends NAT - keepalive messages | |Device sends NAT - keepalive messages | ||
| | |Yes | ||
|---- | |||
|Device is compatible with innovaphone's NAT traversal implementation | |||
|Yes | |||
|---- | |---- | ||
|Device refreshes the PBX registration | |Device refreshes the PBX registration | ||
| | |Yes | ||
|---- | |---- | ||
|Device supports SIP over TCP | |Device supports SIP over TCP | ||
| | |No | ||
|---- | |---- | ||
|Device supports SRTP | |Device supports SRTP | ||
| | |No | ||
|---- | |---- | ||
|Device supports SIPS (SIP over TLS) | |Device supports SIPS (SIP over TLS) | ||
| | |No | ||
|---- | |---- | ||
|Device supports HTTPS | |Device supports HTTPS | ||
| | |No | ||
|---- | |---- | ||
|Device supports VAD (Voice activity detection) | |Device supports VAD (Voice activity detection) | ||
| | |not tested | ||
|---- | |---- | ||
|Supported menu languages | |Supported menu languages | ||
| | |many, check [http://gigaset.com/de/de/product/GIGASETS685IP.html product specifications]. | ||
|---- | |||
|3-party conference | |||
|Yes | |||
|} | |} | ||
| Line 103: | Line 113: | ||
|---- | |---- | ||
|call using g711a | |call using g711a | ||
| | |Yes | ||
|---- | |---- | ||
|call using g711u | |call using g711u | ||
| | |Yes | ||
|---- | |---- | ||
|call using g729 | |call using g729 | ||
| | |Yes | ||
|---- | |---- | ||
|Overlapped sending | |Overlapped sending | ||
| | |No | ||
|---- | |---- | ||
|Early media channel | |Early media channel | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows called id number | |Device shows called id number | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows called id name | |Device shows called id name | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows called id display info | |Device shows called id display info | ||
| | |Yes | ||
|---- | |---- | ||
|Fax using T.38 | |Fax using T.38 | ||
| | |N/A | ||
|---- | |---- | ||
|CGPN can be supressed | |CGPN can be supressed | ||
| | |Yes | ||
|---- | |---- | ||
|Reverse Media Negotiaton | |Reverse Media Negotiaton | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows CDPN/CGPN on incoming call | |Device shows CDPN/CGPN on incoming call | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows CDPN/CGPN on outgoing call | |Device shows CDPN/CGPN on outgoing call | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows connected number | |Device shows connected number | ||
| | |No | ||
|---- | |---- | ||
|Device shows diverting number | |Device shows diverting number | ||
| | |Yes | ||
|---- | |---- | ||
|Device supports distinctive ringing | |Device supports distinctive ringing | ||
| | |No | ||
|---- | |---- | ||
|Device supports asymetric codec negotiation | |Device supports asymetric codec negotiation | ||
| | |not tested | ||
|---- | |---- | ||
|Device supports codec renegotiation during a conversation | |Device supports codec renegotiation during a conversation | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows correct display message in case of busy CDPN | |Device shows correct display message in case of busy CDPN | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows correct display message in case of not existing CDPN | |Device shows correct display message in case of not existing CDPN | ||
| | |Yes | ||
|---- | |---- | ||
|Device shows correct display message in case that the call is declined | |Device shows correct display message in case that the call is declined | ||
| | |Yes | ||
|---- | |---- | ||
|SOAP Call works? | |SOAP Call works? | ||
| | |Yes, auto answer possible. | ||
|---- | |---- | ||
|Long Time Call (>30 min) works? | |Long Time Call (>30 min) works? | ||
| | |Yes | ||
|---- | |||
|Device supports display updates during call(needed for Directory Search object) | |||
|No | |||
|---- | |---- | ||
|Voice Quality OK? | |Voice Quality OK? | ||
| | |Yes | ||
|} | |} | ||
| Line 182: | Line 195: | ||
|---- | |---- | ||
|DTMF tones sent correctly | |DTMF tones sent correctly | ||
| | |Yes | ||
|---- | |---- | ||
|DTMF tones received correctly | |DTMF tones received correctly | ||
| | |Yes | ||
|} | |} | ||
=== Hold/Retrieve === | === Hold/Retrieve === | ||
| Line 196: | Line 208: | ||
|---- | |---- | ||
|Device handles incoming hold correctly | |Device handles incoming hold correctly | ||
| | |Yes | ||
|---- | |---- | ||
|Device can put a call on hold using correctly(inactive or sendonly) | |Device can put a call on hold using correctly(inactive or sendonly) | ||
| | |Yes (not by R-key but by menu option) | ||
|} | |} | ||
| Line 210: | Line 222: | ||
|---- | |---- | ||
|inno1 calls inno2. inno2 transfers to testphone. | |inno1 calls inno2. inno2 transfers to testphone. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
||inno1 calls inno2. inno1 transfers to testphone. | ||inno1 calls inno2. inno1 transfers to testphone. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. inno1 transfers to inno2. | |inno1 calls testphone. inno1 transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. testphone transfers to inno2. | |inno1 calls testphone. testphone transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|testphone calls inno1. inno1 transfers to inno2. | |testphone calls inno1. inno1 transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|testphone calls inno1. testphone transfers to inno2. | |testphone calls inno1. testphone transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|} | |} | ||
| Line 242: | Line 254: | ||
|---- | |---- | ||
|inno1 calls inno2. inno2 transfers to testphone. | |inno1 calls inno2. inno2 transfers to testphone. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
||inno1 calls inno2. inno1 transfers to testphone. | ||inno1 calls inno2. inno1 transfers to testphone. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. inno1 transfers to inno2. | |inno1 calls testphone. inno1 transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. testphone transfers to inno2. | |inno1 calls testphone. testphone transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|testphone calls inno1. inno1 transfers to inno2. | |testphone calls inno1. inno1 transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|---- | |---- | ||
|testphone calls inno1. testphone transfers to inno2. | |testphone calls inno1. testphone transfers to inno2. | ||
| | |Yes | ||
| | |Yes | ||
|} | |} | ||
| Line 273: | Line 285: | ||
|---- | |---- | ||
|inno1 calls inno2. inno2 transfers to testphone. | |inno1 calls inno2. inno2 transfers to testphone. | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls inno2. inno1 transfers to testphone. | |||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. inno1 transfers to inno2. | |inno1 calls testphone. inno1 transfers to inno2. | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. testphone transfers to inno2. | |inno1 calls testphone. testphone transfers to inno2. | ||
| | |No | ||
|---- | |---- | ||
|testphone calls inno1. inno1 transfers to inno2. | |testphone calls inno1. inno1 transfers to inno2. | ||
| | |Yes | ||
|---- | |---- | ||
|testphone calls inno1. testphone transfers to inno2. | |testphone calls inno1. testphone transfers to inno2. | ||
| | |No | ||
|} | |} | ||
| Line 298: | Line 310: | ||
|---- | |---- | ||
|inno1 calls inno2. inno2 transfers to testphone. | |inno1 calls inno2. inno2 transfers to testphone. | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 calls testphone. testphone transfers to inno2. | |inno1 calls testphone. testphone transfers to inno2. | ||
| | |No | ||
|---- | |---- | ||
|testphone calls inno1. inno1 transfers to inno2. | |testphone calls inno1. inno1 transfers to inno2. | ||
| | |Yes | ||
|} | |} | ||
| Line 314: | Line 326: | ||
|---- | |---- | ||
|testphone makes call to a Broadcast Group. inno1 picks up. | |testphone makes call to a Broadcast Group. inno1 picks up. | ||
| | |Yes | ||
|---- | |---- | ||
|inno1 makes call to a Broadcast Group. testphone picks up. | |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. | |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. | |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 | ||
|} | |} | ||
| Line 338: | Line 350: | ||
|---- | |---- | ||
|Device built-in directory | |Device built-in directory | ||
|not possible to connect to a LDAP phonebook(Estos Metadir) | |||
|---- | |---- | ||
|Exists | |Exists | ||
| | |Yes, only local | ||
|---- | |---- | ||
|Can be dialled from | |Can be dialled from | ||
| | |Yes | ||
|---- | |---- | ||
|Does CLI resolution | |Does CLI resolution | ||
| | |Yes | ||
|} | |} | ||
===Hands free=== | ===Hands free=== | ||
| Line 357: | Line 369: | ||
|---- | |---- | ||
|Loudspeaker operation works fine | |Loudspeaker operation works fine | ||
| | |Yes | ||
|---- | |---- | ||
|Hands free works fine | |Hands free works fine | ||
| | |Yes | ||
|---- | |---- | ||
|Volume adjustable during call | |Volume adjustable during call | ||
| | |Yes | ||
|} | |} | ||
===Keys=== | ===Keys=== | ||
| Line 374: | Line 385: | ||
|---- | |---- | ||
|Device has speed dial keys | |Device has speed dial keys | ||
| | |Yes | ||
|---- | |---- | ||
|Device has programmable function keys | |Device has programmable function keys | ||
| | |Yes | ||
|---- | |---- | ||
|Device has partner keys | |Device has partner keys | ||
| | |No | ||
|} | |} | ||
| Line 386: | Line 397: | ||
=== innovaphone configuration === | === innovaphone configuration === | ||
Add a new PBX object of type "user":<br> | |||
[[Image:Siemens Gigaset S685IP - Siemens -Testreport_1.PNG]] | |||
=== 3rd party product configuration === | === 3rd party product configuration === | ||
== | ====Telephony Connection==== | ||
First you have to create a registration from the DECT/IP base-station to the PBX. Go to ''Telephony->Connections'' and ''edit'' the first entry. | |||
Click on ''Select Provider'' and choose your country and ''innovaphonePBX''. This will ensure that all settings are configured correctly. | |||
The device still needs the IP address of the PBX to register at and the name of the user for whom the registration shall be made. Click on ''Show advanced settings'' in order to enter as ''Domain'' name the IP address of your innovaphone PBX. | |||
Please note that the registration credentials configured at the Gigaset phone use the ''number'' of the corresponding PBX object, not its name. Registration by using the name is also possible, but will result in CGPN display problems when making calls from the Gigaset phone to a mobility enabled user. | |||
[[Image:Siemens Gigaset S685IP - Siemens -Testreport_2.PNG]] | |||
====Number Assignment==== | |||
If you have more than one DECT handset registered to your base-station, you can use the ''Telephony->Number Assignment'' menu to assign a DECT handset to a specific PBX registration. | |||
[[Image:Siemens Gigaset S685IP - Siemens -Testreport_3.PNG]] | |||
====Voicemail==== | |||
To get the current voicemail status displayed on your DECT handset, you have to enter the corresponding innovaphone voicemail number in the ''Telephony->Network Mailbox'' menu. | |||
[[Image:Siemens Gigaset S685IP - Siemens -Testreport_4.PNG]] | |||
[[Category:Compat|{{PAGENAME}}]] | |||
Latest revision as of 16:15, 26 July 2011
Summary
The Siemens Gigaset S685IP DECT phone supports all required innovaphone features and is therefore qualified as recommended product.
The usage of wideband codecs of the phone were tested successfully. The integration of the innovaphone voicemail in the Gigaset solution is possible. The message waiting indication will be displayed on the handsets. The handsets support 3-party conference calls.
Currently, the phones cannot access a LDAP phone book directory. The S685 IP base-station supports up to 2 concurrent VoIP calls.
Certification Status
The tests for this product have been completed.
Testing of this product has been finalized January 11th, 2011.
Version
Firmware Version:
022270000000 / 047.00
EEPROM version:
185
innovaphone Firmware:
v8 HotFix8 (80500.28)
Test Setup
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 | No, set static to public NTP server |
| SNTP config has TZ string for timezone/dst autoconfig | No, set static to public NTP server |
| 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 | Yes |
| Device registers with password | Yes |
| Device registers multiple identities | Yes |
| Device supports STUN protocol | Yes |
| Device sends NAT - keepalive messages | Yes |
| Device is compatible with innovaphone's NAT traversal implementation | Yes |
| Device refreshes the PBX registration | Yes |
| Device supports SIP over TCP | No |
| Device supports SRTP | No |
| Device supports SIPS (SIP over TLS) | No |
| Device supports HTTPS | No |
| Device supports VAD (Voice activity detection) | not tested |
| Supported menu languages | many, check product specifications. |
| 3-party conference | 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 | Yes |
| Device shows called id number | Yes |
| Device shows called id name | Yes |
| Device shows called id display info | Yes |
| Fax using T.38 | N/A |
| CGPN can be supressed | Yes |
| 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 | Yes |
| Device supports distinctive ringing | No |
| Device supports asymetric codec negotiation | not tested |
| Device supports codec renegotiation during a conversation | Yes |
| Device shows correct display message in case of busy CDPN | Yes |
| Device shows correct display message in case of not existing CDPN | Yes |
| Device shows correct display message in case that the call is declined | Yes |
| SOAP Call works? | Yes, auto answer possible. |
| Long Time Call (>30 min) works? | Yes |
| Device supports display updates during call(needed for Directory Search object) | No |
| 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 correctly | Yes |
| Device can put a call on hold using correctly(inactive or sendonly) | Yes (not by R-key but by menu option) |
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. | No |
| testphone calls inno1. inno1 transfers to inno2. | Yes |
| testphone calls inno1. testphone transfers to inno2. | No |
Blind Transfer (alerting only)
| Tested feature | Voice Ok? |
|---|---|
| inno1 calls inno2. inno2 transfers to testphone. | Yes |
| inno1 calls testphone. testphone transfers to inno2. | No |
| 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 | not possible to connect to a LDAP phonebook(Estos Metadir) |
| Exists | Yes, only local |
| Can be dialled from | Yes |
| Does CLI resolution | Yes |
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 |
| Device has partner keys | No |
Configuration
innovaphone configuration
Add a new PBX object of type "user":
3rd party product configuration
Telephony Connection
First you have to create a registration from the DECT/IP base-station to the PBX. Go to Telephony->Connections and edit the first entry.
Click on Select Provider and choose your country and innovaphonePBX. This will ensure that all settings are configured correctly.
The device still needs the IP address of the PBX to register at and the name of the user for whom the registration shall be made. Click on Show advanced settings in order to enter as Domain name the IP address of your innovaphone PBX.
Please note that the registration credentials configured at the Gigaset phone use the number of the corresponding PBX object, not its name. Registration by using the name is also possible, but will result in CGPN display problems when making calls from the Gigaset phone to a mobility enabled user.
Number Assignment
If you have more than one DECT handset registered to your base-station, you can use the Telephony->Number Assignment menu to assign a DECT handset to a specific PBX registration.
Voicemail
To get the current voicemail status displayed on your DECT handset, you have to enter the corresponding innovaphone voicemail number in the Telephony->Network Mailbox menu.
