Howto:Gigaset N510 PRO - Gigaset - Testreport: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
 
(38 intermediate revisions by 7 users not shown)
Line 1: Line 1:
==Summary==
==Summary==


The Siemens Gigaset N510IP PRO DECT Basestation supports all required innovaphone features and is therefore qualified as [[Howto:What_is_a_%22recommended_product%22%3F|recommended product]].  
The Gigaset N510IP PRO DECT base-station 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.
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 Gigaset N510IP PRO DECT base-station was tested successfully also in a [[Howto:Hosting#Overview | hosted setup]]. The test results are the same as if the N510IP is used in a normal (in the same LAN as the PBX) setup. It is not required to activate MediaRelay on the Frontend.


==Certification Status==
==Certification Status==


<!-- {{Template:Compat Status "tested"}} -->
{{Template:Compat Status "tested"}}
{{Template:Compat Status "in progress"}}
<!-- {{Template:Compat Status "in progress"}}-->
<!-- {{Template:Compat Status "certified"|certificate=Siemens Gigaset S685IP_-_Siemens_-_3rd_Party_Product_-_Desc-product-cert.pdf}}-->
<!-- {{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. -->
Testing of this product has been finalized September 6th, 2013.


==Version==
==Version==
Firmware Version:
Firmware Version:
420250000000
* 42.078 (420780000000 / V42.00)


innovaphone Firmware:
innovaphone Firmware:
V9 HotFix1 (90600.01)
* V10 SR3
* TSP 8150


== Test Setup ==
== Test Setup ==
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]


==Device Setup==
==Device Setup==


{| border="1"  
{| border="1"
!Tested feature
!Tested feature
!Result
!Result
Line 52: Line 52:
|No
|No
|----
|----
|Fixed registrations works  
|Fixed registrations works
|Yes
|Yes
|----
|----
|Device registers w/o Extension (just by name)
|Device registers w/o Extension (just by name)
|Yes
|----
|Device registers by name with non-latin1 characters (e.g. UserÄÖÜ)
|Yes
|Yes
|----
|----
Line 66: Line 69:
|Device registers multiple identities
|Device registers multiple identities
|Yes
|Yes
|----
|2nd GK is supported
|According to [https://gigaset.atlassian.net/wiki/pages/viewpage.action?pageId=28540959 gigaset-wiki] only by DNS according to RFC3263
|----
|Device supports Redirection of Registration (Master redirects to Slave)
|No
|----
|----
|Device supports STUN protocol
|Device supports STUN protocol
Line 71: Line 80:
|----
|----
|Device sends NAT - keepalive messages
|Device sends NAT - keepalive messages
|Yes
|----
|Device is compatible with innovaphone's NAT traversal implementation
|Yes
|Yes
|----
|----
Line 80: Line 86:
|----
|----
|Device supports SIP over TCP
|Device supports SIP over TCP
|No
|Yes tested in LAN setup.
Hosting Setup, Yes tested with Gigaset Firmware 42.250 (422500000000 / V42.00) and innovaphone firmware V13r2sr15 in myApps Cloud.
 
Media Relay needs to be ticked at the Hardware ID of the User Object where the N510 IP PRO is registered.
|----
|----
|Device supports SRTP
|Device supports SRTP
|No
|Not tested, needs SIPS
|----
|----
|Device supports SIPS (SIP over TLS)
|Device supports SIPS (SIP over TLS)
|No
|Not OK, registration fails
|----
|----
|Device supports HTTPS
|Device supports HTTPS
|No
|Not for Admin access on the Web-page, probably as HTTP-client to retrieve firmware/configuration from remote servers
|----
|----
|Device supports VAD (Voice activity detection)
|Device supports VAD (Voice activity detection)
|not tested
|Not tested, according to manual supported
|----
|----
|Supported menu languages
|Supported menu languages
Line 105: Line 114:
=== Basic Call ===
=== Basic Call ===


{| border="1"  
{| border="1"
!Tested feature
!Tested feature
!Result  
!Result with MR
|----
|----
|call using g711a
|call using g711a
Line 116: Line 125:
|----
|----
|call using g729
|call using g729
|Yes
|----
|call using g722
|Yes
|Yes
|----
|----
Line 121: Line 133:
|No
|No
|----
|----
|Early media channel
|Device sets up an early media channel for incoming calls
|N/A
|----
|Device sets up an early media channel for outgoing calls
|Yes
|Yes
|----
|----
Line 136: Line 151:
|N/A
|N/A
|----
|----
|CGPN can be supressed
|CGPN can be suppressed
|Yes
|Yes
|----
|----
|Reverse Media Negotiaton
|Reverse Media Negotiation
|Yes
|Yes
|----
|----
Line 152: Line 167:
|----
|----
|Device shows diverting number
|Device shows diverting number
|Yes
|No
|----
|----
|Device supports distinctive ringing
|Device supports distinctive ringing
|No
|Yes
|----
|----
|Device supports asymetric codec negotiation
|Device supports asymetric codec negotiation
|not tested
|Not tested
|----
|----
|Device supports codec renegotiation during a conversation
|Device supports codec renegotiation during a conversation
Line 167: Line 182:
|----
|----
|Device shows correct display message in case of not existing CDPN
|Device shows correct display message in case of not existing CDPN
|No, it says "Not available"
|----
|Device shows correct display message in case that the call is declined
|Yes
|Yes
|----
|----
|Device shows correct display message in case that the call is declined
|3party conference possible
|Yes
|Yes
|----
|----
|SOAP Call works?
|Device supports display updates during call(needed for Directory Search object)
|Yes, auto answer possible.
|No
|----
|----
|Long Time Call (>30 min) works?
|Long Time Call (>30 min) works?
|Yes
|Yes
|----
|----
|Device supports display updates during call(needed for Directory Search object)
|Incoming SRTP call - SRTP not enabled on DUT
|No
|Yes
|----
|Incoming SRTP call - SRTP enabled on DUT
|Not tested, requires sips
|----
|----
|Voice Quality OK?
|Voice Quality OK?
Line 187: Line 208:
=== DTMF ===
=== DTMF ===


{| border="1"  
{| border="1"
!Tested feature
!Tested feature
!Result  
!Result
|----
|----
|DTMF tones sent correctly
|DTMF tones sent correctly
|Yes
|OK
|----
|----
|DTMF tones received correctly
|DTMF tones received correctly
|No
|OK, DTMFs are sent as RTP-Events (no DTMF dependent function on Gigaset device)
|}
|}


Line 208: Line 229:
|----
|----
|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)
|Yes
|}
|}
It is possible to configure the handling of the "R" button. Please take a look into the manual. [http://gigaset.com/de/de/pages/index.html product specifications]


=== Transfer with consultation ===
=== Transfer with consultation ===
Line 293: Line 312:
|----
|----
|inno1 calls testphone. testphone transfers to inno2.
|inno1 calls testphone. testphone transfers to inno2.
|No
|N/A, device does only transfer with consultation
|----
|----
|testphone calls inno1. inno1 transfers to inno2.
|testphone calls inno1. inno1 transfers to inno2.
Line 299: Line 318:
|----
|----
|testphone calls inno1. testphone transfers to inno2.
|testphone calls inno1. testphone transfers to inno2.
|No
|N/A, device does only transfer with consultation
|}
|}


Line 312: Line 331:
|----
|----
|inno1 calls testphone. testphone transfers to inno2.
|inno1 calls testphone. testphone transfers to inno2.
|No
|N/A, device does only transfer with consultation
|----
|----
|testphone calls inno1. inno1 transfers to inno2.
|testphone calls inno1. inno1 transfers to inno2.
Line 338: Line 357:
|inno1 makes call to a Waiting Queue. testphone picks up.
|inno1 makes call to a Waiting Queue. testphone picks up.
|Yes
|Yes
|}
=== DTMF Features ===
{| border="1"
!Tested feature
!Result
|----
|CFU Activate/Deactivate           
|Ok
|----
|CFB Activate/Deactivate       
|Ok
|----
|CFNR Activate/Deactivate       
|Ok
|----
|Pickup Group
|Ok
|----
|Pickup Directed       
|Ok
|----
|Park/Unpark       
|Ok
|----
|Park To/Unpark From       
|Ok
|----
|Call Completion Busy
|Nok, Gigaset rejects incoming call for starting CCBS/CCNR
|----
|Call Completion Cancel
|Not tested, since CCBS/CCNR does not work
|----
|Join Group/Leave Group
|Ok
|----
|Join All Groups/Leave All Groups
|Ok
|----
|Enable mobility/Disable mobility       
|Not tested, feature is invoked by mobile phone
|----
|Enable mobility cw/Disable mobility cw       
|Not tested, feature is invoked by mobile phone
|----
|Set presence
|Ok
|}
|}


Line 344: Line 412:
===Directory===
===Directory===


{| border="1"  
{| border="1"
!Tested feature
!Tested feature
!Result  
!Result
|----
|----
|Device built-in directory
|Device built-in directory
|not possible to connect to a LDAP phonebook(Estos Metadir)
|----
|----
|Exists
|Exists
|Yes, only local
|Yes
|----
|----
|Can be dialled from
|Can be dialled from
Line 358: Line 425:
|----
|----
|Does CLI resolution
|Does CLI resolution
|Yes
|----
|display update if directory object is used?
|Yes
|Yes
|}
|}


===Hands free===
*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.
 


{| border="1"  
{| border="1"
!Tested feature
!Tested feature
!Result  
!Result
|----
|External LDAP Server supported
|Yes, tested with Estos Metadir. PBX not supported as external LDAP server and LDAPS not supported.
|----
|----
|Loudspeaker operation works fine
|Can be dialled from
|Yes
|Yes
|----
|----
|Hands free works fine
|Does CLI resolution
|Yes
|Yes
|----
|----
|Volume adjustable during call
|display update if directory object is used?
|Yes
|Yes
|}
|}
Line 379: Line 455:
===Keys===
===Keys===


{| border="1"  
{| border="1"
!Tested feature
!Tested feature
!Result  
!Result
|----
|----
|Device has speed dial keys
|Device has speed dial keys
|Yes
|Yes, depending on handset
|----
|----
|Device has programmable function keys
|Device has programmable function keys
|Yes
|Yes, depending on handset
|----
|----
|Device has partner keys
|Device has partner keys
|No
|No
|}
|}
===CTI Features (with SOAP / TAPI / myPBX) ===
{| border="1"
!Tested feature
!Result
|----
|User Call - outgoing call
|Ok
|----
|User Connect - Answer incoming call
|Ok
|----
|User Reject - Reject alerting call
|Ok
|----
|User Disconnect - Disconnect active call
|Ok
|----
|User Hold - Put connected call on hold
|Ok
|----
|User Hold Retrieve - Retrieve call on hold
|Ok
|----
|User Transfer - Transfer with Consult
|Nok(myPBX), Ok(Tapi/Soap)
|----
|User Transfer - Transfer with Consult (Alerting only)
|Nok(myPBX), Ok(Tapi/Soap)
|----
|User Transfer - Blind Transfer
|Ok, Ok(Tapi/Soap)
|----
|3PTY - Make 3rd Party Call
|Nok(myPBX), Nok(Tapi/Soap)
|----
|Connected Number Update on Display
|No
|}
* tested with myPBX and TSP(8150)only


== Configuration ==
== Configuration ==
Line 397: Line 515:
=== innovaphone configuration ===
=== innovaphone configuration ===
Add a new PBX object of type "user":<br>
Add a new PBX object of type "user":<br>
[[Image:Siemens Gigaset S685IP - Siemens -Testreport_1.PNG]]
[[Image:Siemens Gigaset N510IP PRO - PBX_Userobject.png]]


=== 3rd party product configuration ===
=== 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
[[Image:Siemens Gigaset N510IP PRO - Gigaset_IP_Configuration_ENG.png]]


====Telephony Connection====
====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.
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.
Click on ''Select Provider'' and choose your country and ''innovaphonePBX''. This will ensure that all settings are configured correctly.
Line 409: Line 538:
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.  
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.  
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.
 
When using the Reverse Proxy, you have to set the protocol to TCP instead of UDP


[[Image:Siemens Gigaset S685IP - Siemens -Testreport_2.PNG]]
[[Image:Siemens Gigaset N510IP PRO - Gigaset_Telefonie_Connection_ENG.png]]


====Number Assignment====
====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.
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]]
 
[[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====
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.
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]]
[[Image:Siemens Gigaset N510IP PRO - Gigaset_VM_ENG.png]]
 
====Phone Directory - Adress Book====
 
You can import/export and save the local phonebook. Have a look at the configuration description in the Gigaset manual.
 
[[Image:Siemens Gigaset N510IP PRO - Gigaset_Phone_Directory_ENG.png]]
 
====Enhanced VoIP Settings====
 
If the device is used in a hosted setup, make sure that the following settings are configured:
* Automatic Negotiation of DTMF transmission: '''Yes'''
* Find target addr. automatically: '''Yes'''
 
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.
 
[[Image:Siemens Gigaset N510IP PRO - Gigaset_advanced_VoIP_Settings_ENG.png]]
 
=== Known problems ===
 
==== innovaphone PBX Version 12 ====
 
With the upcoming version 12 from innovaphone AG we have implemented the security feature [https://tools.ietf.org/html/rfc3261#section-22.4 SIP digest authentication] . If the client does not support this feature the PBX will reject the registration.
 
There is a config option to avoid this if you use a older firmware.
 
http://ip-of-pbx/!config change SIP /disable-digest-replay-check
http://ip-of-pbx/!config write
http://ip-of-pbx/!config activate
 
This problem has been '''fixed by Gigaset with N510 Firmware 42.240''', November 2016 and later
 
==== MoH ====
Customer reported that even when choosing as Providerprofile ''innovaphonePBX'', MoH was not audible when a call was put on hold by the Gigaset device. The reason for this is that the Gigaset signals the hold using a "sendonly" instead of an "inactive" SDP-attribute.
To fix this error, you can configure the innovaphone PBX to ignore the wrong hold-signaling:
 
http://ip-of-pbx/!config add SIP /take-sendonly-as-inactive
http://ip-of-pbx/!config write
http://ip-of-pbx/!config activate
 
Please keep in mind that this option will affect all SIP/UDP communication. So if you have for example another 3rd party SIP-device, which wants to play its own MOH - it will not work anymore.
 
==== Usernames with whitespace ====
Customer reported that when registering a Gigaset-device at an object-name with whitespace (e.g. John Doe), because of a bug on the Gigaset SIP-stack ut will not be possible to put a remote device on hold. As a workaround, don't remove the whitespace from the object-name (e.g. JohnDoe).
 
==== Recalling DECT device after transfer ====
With firmware v43, when you make a call transfer from a DECT phone to somewhere else, ~15 seconds you receive a recall call on the DECT phone.
Make a downgrade to v42 to work arround the problem.
The same happens in the gigaset N720 multi cell environment with firmwares above 098
 
==== innovaphone PBX Version 13 and Chat App ====
When using myApps to send chat messages to a user, the PBX broadcasts the IM-SETUP (instant-message) to all registered endpoints of the addressed user. Customer reported that Gigaset seems to take this as a regular media call and the phone starts ringing upon receiving a chat message, where in fact this is an instant messaging call. Bug needs to be reported to Gigaset. (Some newer systems of the N5xx series have an option to activate or disable the response to those IM messages.)


[[Category:Compat|{{PAGENAME}}]]
[[Category:Compat|{{PAGENAME}}]]

Latest revision as of 14:49, 30 November 2022

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.

The Gigaset N510IP PRO DECT base-station was tested successfully also in a hosted setup. The test results are the same as if the N510IP is used in a normal (in the same LAN as the PBX) setup. It is not required to activate MediaRelay on the Frontend.

Certification Status

The tests for this product have been completed.

Testing of this product has been finalized September 6th, 2013.

Version

Firmware Version:

  • 42.078 (420780000000 / V42.00)

innovaphone Firmware:

  • V10 SR3
  • TSP 8150

Test Setup

Testreport Terminals SIP or H323 1.PNG

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 name with non-latin1 characters (e.g. UserÄÖÜ) Yes
Device registers by extension Yes
Device registers with password Yes
Device registers multiple identities Yes
2nd GK is supported According to gigaset-wiki only by DNS according to RFC3263
Device supports Redirection of Registration (Master redirects to Slave) No
Device supports STUN protocol Yes
Device sends NAT - keepalive messages Yes
Device refreshes the PBX registration Yes
Device supports SIP over TCP Yes tested in LAN setup.

Hosting Setup, Yes tested with Gigaset Firmware 42.250 (422500000000 / V42.00) and innovaphone firmware V13r2sr15 in myApps Cloud.

Media Relay needs to be ticked at the Hardware ID of the User Object where the N510 IP PRO is registered.

Device supports SRTP Not tested, needs SIPS
Device supports SIPS (SIP over TLS) Not OK, registration fails
Device supports HTTPS Not for Admin access on the Web-page, probably as HTTP-client to retrieve firmware/configuration from remote servers
Device supports VAD (Voice activity detection) Not tested, according to manual supported
Supported menu languages many, check product specifications
3-party conference Yes

Test Results

Basic Call

Tested feature Result with MR
call using g711a Yes
call using g711u Yes
call using g729 Yes
call using g722 Yes
Overlapped sending No
Device sets up an early media channel for incoming calls N/A
Device sets up an early media channel for outgoing calls 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 No
Device supports distinctive ringing Yes
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 No, it says "Not available"
Device shows correct display message in case that the call is declined Yes
3party conference possible Yes
Device supports display updates during call(needed for Directory Search object) No
Long Time Call (>30 min) works? Yes
Incoming SRTP call - SRTP not enabled on DUT Yes
Incoming SRTP call - SRTP enabled on DUT Not tested, requires sips
Voice Quality OK? Yes

DTMF

Tested feature Result
DTMF tones sent correctly OK
DTMF tones received correctly OK, DTMFs are sent as RTP-Events (no DTMF dependent function on Gigaset device)

Hold/Retrieve

Tested feature Result
Device handles incoming hold correctly Yes
Device can put a call on hold using correctly(inactive or sendonly) Yes

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. N/A, device does only transfer with consultation
testphone calls inno1. inno1 transfers to inno2. Yes
testphone calls inno1. testphone transfers to inno2. N/A, device does only transfer with consultation

Blind Transfer (alerting only)

Tested feature Voice Ok?
inno1 calls inno2. inno2 transfers to testphone. Yes
inno1 calls testphone. testphone transfers to inno2. N/A, device does only transfer with consultation
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

DTMF Features

Tested feature Result
CFU Activate/Deactivate Ok
CFB Activate/Deactivate Ok
CFNR Activate/Deactivate Ok
Pickup Group Ok
Pickup Directed Ok
Park/Unpark Ok
Park To/Unpark From Ok
Call Completion Busy Nok, Gigaset rejects incoming call for starting CCBS/CCNR
Call Completion Cancel Not tested, since CCBS/CCNR does not work
Join Group/Leave Group Ok
Join All Groups/Leave All Groups Ok
Enable mobility/Disable mobility Not tested, feature is invoked by mobile phone
Enable mobility cw/Disable mobility cw Not tested, feature is invoked by mobile phone
Set presence Ok

Other Features

Directory

Tested feature Result
Device built-in directory
Exists Yes
Can be dialled from Yes
Does CLI resolution Yes
display update if directory object is used? 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.


Tested feature Result
External LDAP Server supported Yes, tested with Estos Metadir. PBX not supported as external LDAP server and LDAPS not supported.
Can be dialled from Yes
Does CLI resolution Yes
display update if directory object is used? Yes

Keys

Tested feature Result
Device has speed dial keys Yes, depending on handset
Device has programmable function keys Yes, depending on handset
Device has partner keys No

CTI Features (with SOAP / TAPI / myPBX)

Tested feature Result
User Call - outgoing call Ok
User Connect - Answer incoming call Ok
User Reject - Reject alerting call Ok
User Disconnect - Disconnect active call Ok
User Hold - Put connected call on hold Ok
User Hold Retrieve - Retrieve call on hold Ok
User Transfer - Transfer with Consult Nok(myPBX), Ok(Tapi/Soap)
User Transfer - Transfer with Consult (Alerting only) Nok(myPBX), Ok(Tapi/Soap)
User Transfer - Blind Transfer Ok, Ok(Tapi/Soap)
3PTY - Make 3rd Party Call Nok(myPBX), Nok(Tapi/Soap)
Connected Number Update on Display No
  • tested with myPBX and TSP(8150)only

Configuration

innovaphone configuration

Add a new PBX object of type "user":
Siemens Gigaset N510IP PRO - PBX Userobject.png

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

Siemens Gigaset N510IP PRO - Gigaset IP Configuration ENG.png

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.

When using the Reverse Proxy, you have to set the protocol to TCP instead of UDP

Siemens Gigaset N510IP PRO - Gigaset Telefonie Connection ENG.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.

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).

Siemens Gigaset N510IP PRO - Gigaset Call Manager.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. Siemens Gigaset N510IP PRO - Gigaset VM ENG.png

Phone Directory - Adress Book

You can import/export and save the local phonebook. Have a look at the configuration description in the Gigaset manual.

Siemens Gigaset N510IP PRO - Gigaset Phone Directory ENG.png

Enhanced VoIP Settings

If the device is used in a hosted setup, make sure that the following settings are configured:

  • Automatic Negotiation of DTMF transmission: Yes
  • Find target addr. automatically: Yes

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.

Siemens Gigaset N510IP PRO - Gigaset advanced VoIP Settings ENG.png

Known problems

innovaphone PBX Version 12

With the upcoming version 12 from innovaphone AG we have implemented the security feature SIP digest authentication . If the client does not support this feature the PBX will reject the registration.

There is a config option to avoid this if you use a older firmware. 

http://ip-of-pbx/!config change SIP /disable-digest-replay-check 
http://ip-of-pbx/!config write
http://ip-of-pbx/!config activate

This problem has been fixed by Gigaset with N510 Firmware 42.240, November 2016 and later

MoH

Customer reported that even when choosing as Providerprofile innovaphonePBX, MoH was not audible when a call was put on hold by the Gigaset device. The reason for this is that the Gigaset signals the hold using a "sendonly" instead of an "inactive" SDP-attribute. To fix this error, you can configure the innovaphone PBX to ignore the wrong hold-signaling: 

http://ip-of-pbx/!config add SIP /take-sendonly-as-inactive
http://ip-of-pbx/!config write
http://ip-of-pbx/!config activate

Please keep in mind that this option will affect all SIP/UDP communication. So if you have for example another 3rd party SIP-device, which wants to play its own MOH - it will not work anymore.

Usernames with whitespace

Customer reported that when registering a Gigaset-device at an object-name with whitespace (e.g. John Doe), because of a bug on the Gigaset SIP-stack ut will not be possible to put a remote device on hold. As a workaround, don't remove the whitespace from the object-name (e.g. JohnDoe).

Recalling DECT device after transfer

With firmware v43, when you make a call transfer from a DECT phone to somewhere else, ~15 seconds you receive a recall call on the DECT phone. Make a downgrade to v42 to work arround the problem. The same happens in the gigaset N720 multi cell environment with firmwares above 098

innovaphone PBX Version 13 and Chat App

When using myApps to send chat messages to a user, the PBX broadcasts the IM-SETUP (instant-message) to all registered endpoints of the addressed user. Customer reported that Gigaset seems to take this as a regular media call and the phone starts ringing upon receiving a chat message, where in fact this is an instant messaging call. Bug needs to be reported to Gigaset. (Some newer systems of the N5xx series have an option to activate or disable the response to those IM messages.)

Retrieved from "https://wiki.innovaphone.com/index.php?title=Howto:Gigaset_N510_PRO_-_Gigaset_-_Testreport&oldid=64423"