Howto:Gigaset N510 PRO - Gigaset - Testreport: Difference between revisions
Line 473: | Line 473: | ||
[[Image:Siemens Gigaset N510IP PRO - Gigaset_Number_Assignment.png]] | [[Image:Siemens Gigaset N510IP PRO - Gigaset_Number_Assignment.png]] | ||
To work with CTI clients like myPBX we need to configure the Call Manager with the handset that should handle this CTI calls and the mode (headset/handsfree). | |||
[[Image:Siemens Gigaset N510IP PRO - Gigaset_Call_Manager.png]] | |||
====Voicemail==== | ====Voicemail==== |
Revision as of 16:05, 13 June 2013
Summary
The Gigaset N510IP PRO DECT base-station 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.
Certification Status
The tests for this product have been completed.
Testing of this product has been finalized September 16th, 2011.
Version
Firmware Version:
420250000000
innovaphone Firmware:
V9 HotFix2 (90600.02)
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 suppressed | Yes |
Reverse Media Negotiation | 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 asymmetric 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 | No |
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) |
- It is possible to configure the handling of the "R" button. Please take a look into the manual or configuration. product specifications
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 without 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 |
- It is possible to configure a connection to an online source like DE - Klicktel. Please take a look into the manual or configuration.
- It is possible to import and export the local Phonebook.
- You can add the call to the local phonebook from the call-list.
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 |
CTI Features (with SOAP / TAPI / myPBX)
Tested feature | Result |
---|---|
User Call - outgoing call | |
User Connect - Answer incoming call | |
User Reject - Reject alerting call | |
User Disconnect - Disconnect active call | |
User Hold - Put connected call on hold | |
User Hold Retrieve - Retrieve call on hold | |
User Transfer - Transfer with Consult | |
User Transfer - Transfer with Consult (Alerting only) | |
User Transfer - Blind Transfer | |
3PTY - Make 3rd Party Call | |
Connected Number Update on Display |
Configuration
innovaphone configuration
Add a new PBX object of type "user":
3rd party product configuration
IP Configuration
First you have to configure the general IP Configuration for the base-station.
- IP Address
- Subnet Mask
- Default Gateway
- DNS
Telephony Connection
In the next step 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.
To work with CTI clients like myPBX we need to configure the Call Manager with the handset that should handle this CTI calls and the mode (headset/handsfree).
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.
Phone Directory - Adress Book
You can import/export and save the local phonebook. Have a look at the configuration description in the Gigaset manual.
Enhanced VoIP Settings
At last you can configure some enhanced VoIP Settings like the handling of the "R" button. For more information have a look at the configuration description in the Gigaset manual.