innovaphone wiki - User contributions [en]

Howto:OpenTalk - 3rd Party Product

2024-02-21T05:51:14Z

M.lasarsch:

[[Image:OpenTalk_LOGO_1C_SCHWARZ.png||200px|right|alt=OpenTalk|OpenTalk]]

==Product Name==


[https://opentalk.eu OpenTalk]

==Certification Status==


==Category==


==Vendor==



[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]

==Description==


OpenTalk is an open-source video-conferencing solution, both available for on-premise installation and SaaS on [https://register.opentalk.eu/ meet.opentalk.eu].

==Functions==


* video conferences
* easy and modern web-ui with mobile support
* phone dial-in
* integration into 3rd party products
* voting and polls
* breakout rooms for sub-conferences

==Version==
Product versions used for interop testing:
* [https://gitlab.opencode.de/opentalk/ot-setup OpenTalk Git 1.7.0]
* innovaphone 13r3sr3 (137781)

==Configuration==
The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

==Contact==
{|
| OpenTalk GmbH
|-
| Schwedter Str. 9a
|-
| 10119 Berlin
|-
| Web: [https://opentalk.eu opentalk.eu]
|-
| Mail: [mailto:mail@opentalk.eu mail@opentalk.eu]
|}

Howto:OpenTalk - 3rd Party Product

2024-02-21T05:49:41Z

M.lasarsch:

[[Image:OpenTalk_LOGO_1C_SCHWARZ.png||200px|right|alt=OpenTalk|OpenTalk]]

==Product Name==


[https://opentalk.eu OpenTalk]

==Certification Status==


==Category==


==Vendor==



[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]

==Description==


OpenTalk is an open-source video-conferencing solution, both available as on-premise installation and SaaS on [https://register.opentalk.eu/ meet.opentalk.eu].

==Functions==


* video conferences
* easy and modern web-ui with mobile support
* phone dial-in
* integration into 3rd party products
* voting and polls
* breakout rooms for sub-conferences

==Version==
Product versions used for interop testing:
* [https://gitlab.opencode.de/opentalk/ot-setup OpenTalk Git 1.7.0]
* innovaphone 13r3sr3 (137781)

==Configuration==
The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

==Contact==
{|
| OpenTalk GmbH
|-
| Schwedter Str. 9a
|-
| 10119 Berlin
|-
| Web: [https://opentalk.eu opentalk.eu]
|-
| Mail: [mailto:mail@opentalk.eu mail@opentalk.eu]
|}

Howto:OpenTalk - 3rd Party Product

2024-02-19T07:49:36Z

M.lasarsch:

==Product Name==


[https://opentalk.eu OpenTalk]

==Certification Status==
{{Template:Compat_Status_referral_product_new}}

Testing of this product has been finalized Januar 2024.

==Category==
[[Category:Referral Product|{{PAGENAME}}]]

{{Category:3rdParty}}
[[Category:3rdParty|{{PAGENAME}}]]

==Vendor==




[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]

OpenTalk GmbH

Schwedter Str. 9a

10119 Berlin

https://opentalk.eu

==Description==




The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

Howto:OpenTalk - 3rd Party Product

2024-02-19T07:45:09Z

M.lasarsch:

==Product Name==


OpenTalk [https://opentalk.eu OpenTalk]

==Certification Status==
{{Template:Compat_Status_referral_product_new}}

Testing of this product has been finalized Januar 2024.

==Category==
[[Category:Referral Product|{{PAGENAME}}]]

{{Category:3rdParty}}
[[Category:3rdParty|{{PAGENAME}}]]

==Vendor==




[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]

OpenTalk GmbH
Schwedter Str. 9a
10119 Berlin

https://opentalk.eu

==Description==




The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

Howto:OpenTalk - 3rd Party Product

2024-02-19T07:44:45Z

M.lasarsch:

==Product Name==


OpenTalk [https://opentalk.eu OpenTalk]

==Certification Status==
{{Template:Compat_Status_referral_product_new}}

Testing of this product has been finalized Januar 2024.

==Category==
[[Category:Referral Product|{{PAGENAME}}]]

{{Category:3rdParty}}
[[Category:3rdParty|{{PAGENAME}}]]

==Vendor==




[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]
OpenTalk GmbH
Schwedter Str. 9a
10119 Berlin

https://opentalk.eu

==Description==




The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

Howto:OpenTalk - 3rd Party Product

2024-02-19T07:43:29Z

M.lasarsch:

[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]

==Product Name==


OpenTalk [https://opentalk.eu OpenTalk]

==Certification Status==
{{Template:Compat_Status_referral_product_new}}

Testing of this product has been finalized Januar 2024.

==Category==
[[Category:Referral Product|{{PAGENAME}}]]

{{Category:3rdParty}}
[[Category:3rdParty|{{PAGENAME}}]]

==Vendor==




[[Image:OpenTalk_LOGO_1C_SCHWARZ.png|200px|alt=OpenTalk|OpenTalk]]
OpenTalk GmbH
Schwedter Str. 9a
10119 Berlin

https://opentalk.eu

==Description==




The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

File:OpenTalk LOGO 1C SCHWARZ.png

2024-02-19T07:38:17Z

M.lasarsch: M.lasarsch uploaded a new version of File:OpenTalk LOGO 1C SCHWARZ.png

OpenTalk Logo

File:OpenTalk LOGO 1C SCHWARZ.png

2024-02-19T07:29:21Z

M.lasarsch:

OpenTalk Logo

Howto:OpenTalk - 3rd Party Product

2024-02-19T07:23:51Z

M.lasarsch:

The following describes how to integrate OpenTalk seamlessly into the innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|800px|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

[[File:Innovaphone opentalk 2.png|800px|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|800px|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via innovaphone.

This must be decided and set up depending on the use case.

Howto:OpenTalk - 3rd Party Product

2024-02-19T07:19:15Z

M.lasarsch: Created page with "The following describes how to integrate OpenTalk seamlessly into the Innovaphone myApps/PBX. The PBX must be available in at least version 137781. You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup === OAuth2 basic settings === Navigate within myApps as follows: '''Devices > PBX > Config > Authentication''' * Select the '''Authentication type''': PBX and O..."

The following describes how to integrate OpenTalk seamlessly into the Innovaphone myApps/PBX.
The PBX must be available in at least version 137781.

You also need an existing OpenTalk installation, a description of how to install OpenTalk on premise can be found here: https://gitlab.opencode.de/opentalk/ot-setup

=== OAuth2 basic settings ===
Navigate within myApps as follows: '''Devices > PBX > Config > Authentication'''
* Select the '''Authentication type''': PBX and OAuth2
* Set an '''OAuth2 provider name''', e.g: Innovaphone auth. with OpenTalk
* Set the '''OAuth2 domain''', or the URL to your OpenTalk installation: opentalk.yourdomain.com

[[File:Innovaphone opentalk 1.png|thumb|alt=OpenTalk OAuth basic|OpenTalk OAuth basic settings]]

=== Activate and set up OAuth2 ===
Navigate within myApps as follows '''Devices > Services > OAuth2 > Config'''.

* Enable the OAuth2 "Config" with the checkbox '''Enable:''' √.

* Set the '''DNS name of this gateway''', for example: pbx.yourdomain.com

* Set the '''OpenID known configuration URL''', for example: https://accounts.opentalk.ihredomain.de/auth/realms/realm-name/.well-known/openid-configuration

* Set the '''Client ID''' to the client ID you defined in the keycloak, e.g.: pbxauth

* Set the '''upn (unique email address):''' email

The '''OpenID known configuration URL''' is always made up of the '''domain for the keycloak''' and the '''realm name'''. So please replace the above part accounts.opentalk.yourdomain.com with your own keycloak domain. The realm name above is the realm you have configured in Keycloak. If we assume that the Keycloak installation is based on the provided OpenSource installation (https://gitlab.opencode.de/opentalk/ot-setup) and no changes have been made to the realm, the realm name is opentalk.

'''Tip:''' The '''OpenID known configuration URL''' can be tested by calling it in a browser, if successful a JSON is returned confirming the correct URL for the known configuration.

* [[File:Innovaphone opentalk 2.png|thumb|alt=OpenTalk configuration|OpenTalk configuration]]

=== Verify OAuth2 configuration ===
Navigate within myApps as follows: '''Devices > Services > OAuth2 > State'''

You have the option to check the configuration from the previous steps independently, if all parameters have been set correctly, the test result should be as follows:

[[File:Innovaphone opentalk 3.png|thumb|alt=OpenTalk verify OAuth|OpenTalk verify OAuth]]

=== Innovaphone LDAP and Keycloak User Federation ===
Navigate within myApps as follows: '''Devices > Services > LDAP > Server'''
* Set an LDAP user that is used within Keycloak as a service user for LDAP queries
* Activate the Force TLS option in any case

First select the correct realm in Keycloak, do not edit the master realm in this context. Select "opentalk" or the realm you have created.

Navigate within the Keycloak as follows: '''User federation > Add new provider > LDAP'''
'''Connection URL:''' ldaps://pbx.yourdomain.com:636
'''Use Truststore SPI:''' Only for ldaps
'''Bind type:''' simple

The other settings and options under '''LDAP searching and updating''' depend heavily on the type of use of the Keycloak LDAP connection, e.g. should the user creation be realized via Keycloak or should everything be managed centrally via Innovaphone.

This must be decided and set up depending on the use case.

File:Innovaphone opentalk 3.png

2024-02-19T07:12:36Z

M.lasarsch:

OpenTalk verify settings

File:Innovaphone opentalk 2.png

2024-02-19T07:11:44Z

M.lasarsch:

OpenTalk configuration

File:Innovaphone opentalk 1.png

2024-02-19T07:10:21Z

M.lasarsch:

OpenTalk integration - OAuth basic