innovaphone wiki - User contributions [en]

Reference14r2:Concept App Service Recordings

2024-07-17T09:14:46Z

Ptr: /* Configuration */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX Recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX Recordings Admin APP-Object with the PBX Manager Plugin.
* Assign Recordings Admin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign Recordings App to users who will use the Recordings App.
* Start Recordings Admin App and configure the name of the PBX in the settings via upright option
* Assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin App in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbxmanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users Recordings App, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his Recordings App, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:14:26Z

Ptr: /* Configuration */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX Recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX Recordings Admin APP-Object with the PBX Manager Plugin.
* Assign Recordings Admin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign Recordings App to users who will use the Recordings App.
* Start Recordings Admin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin App in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbxmanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users Recordings App, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his Recordings App, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:12:40Z

Ptr: /* Encrypted Recordings */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX recordingsadmin APP-Object with the PBX Manager Plugin.
* Assign recordingsadmin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign recordings App to users who will use the Recordings App.
* Start recordingsadmin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin App in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbxmanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users Recordings App, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his Recordings App, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:11:45Z

Ptr: /* 4 Eyes Access */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX recordingsadmin APP-Object with the PBX Manager Plugin.
* Assign recordingsadmin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign recordings App to users who will use the Recordings App.
* Start recordingsadmin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin app in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbxmanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users Recordings App, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his Recordings App, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:11:17Z

Ptr: /* 4 Eyes Access */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX recordingsadmin APP-Object with the PBX Manager Plugin.
* Assign recordingsadmin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign recordings App to users who will use the Recordings App.
* Start recordingsadmin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin app in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbxmanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users Recordings app, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his recordings app, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:09:29Z

Ptr: /* Requirements */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings Apps
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX recordingsadmin APP-Object with the PBX Manager Plugin.
* Assign recordingsadmin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign recordings App to users who will use the Recordings App.
* Start recordingsadmin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin app in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbymanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users recordings app, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his recordings app, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:08:43Z

Ptr: /* recordingsadmin */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings App
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== Recordings Admin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX recordingsadmin APP-Object with the PBX Manager Plugin.
* Assign recordingsadmin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign recordings App to users who will use the Recordings App.
* Start recordingsadmin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin app in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbymanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users recordings app, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his recordings app, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Reference14r2:Concept App Service Recordings

2024-07-17T09:08:17Z

Ptr: /* recordings */

[[Category:Concept|Apps]]
{{FIXME|reason=This product is in the beta phase and is not yet finished}}

== Description ==
Recordings is an application running on the App platform which allows capturing the audio streams during a telephone call.
The user's phone can be configured to send bidirectional audio streams to the Recordings App and store them into the database.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform
* Firmware V14r2xx
* Recordings App
* App(innovaphone-recorder) licenses (per User)
* Device with PCAP Recording Interface:
** innovaphone deskphones
** innovaphone SoftphoneApp
** innovaphone gateway interfaces
* Reporting App

== Apps ==

=== Recordings ===
[[Image: Usrrecord.png]]

User version of the App allow you to:
* Access to the user specific records
* Access to the user specific logs
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

=== recordingsadmin ===
[[Image:Adminrecord.png]]

Admin version of the app allow you to:
* Access to all records
* Access to all logs
* Set up the records auto deletion retention time in days
* Set the PBX name
* Set the CryptKey to encrypt the .pcap files in the database
* Set the WebDAV credentials for the Record-to-URL
* Set specific trace levels
* Filter records by name, by date
* Play, Listen or Download the recording as a .zip file which contains the .WAV file and a .PDF with the call information
* Protect against deleting or delete a recording

== PBX Manager Plugin ==

With the Recordings PBX Manager Plugin, an App Object can be created, edited and deleted on the PBX.

== Configuration ==
* Download the Recordings App via App Store.
* Install the App on the App Platform Manager.
* Create an instance for the Recordings App on the App Platform Manager.
* Create a new PBX recordings APP-Object with the PBX Manager Plugin.
* Create a new PBX recordingsadmin APP-Object with the PBX Manager Plugin.
* Assign recordingsadmin App to authorized (admin) users, which will be allowed to open the Admin UI of the Recordings App.
* Assign recordings App to users who will use the Recordings App.
* Start recordingsadmin App and configure the name of the PBX in the settings via upright option
* assign Record to (URL) to recording devices/objects in format
: <code>http://</code>''ap.domain.tld''<code>/</code>''domain.tld''<code>/recordings/Files</code>
:at deskphones or gateway interfaces.
:At innovaphone deskphones, enable recording via Phone/User-X/Recording by setting ''Mode'' to <code>transparent</code> and ''Recorder'' to <code>HTTP Server</code>.

=== Access List ===
Unlike Recordings Admin App, which lists recordings of all users, Recordings App for users limits the listing of recordings to those made by the using user himself.

A possibility to extend the listing of the recordings to other extensions/users is provided by the Access List. In the Access List, additional extension can be defined, which will be listed to the Users of the App. This way the Recordings App Service can be accessed via different App Objects, with different Access Lists.

This way scenarios, like sharing recordings between team members or supervisor access to recordings of call agents are possible. 
For the configuration, see : [[Howto14r1:RecordingsApp#Access_list_configuration_through_the_Recordings_Plugin]]

=== Deletion of recordings ===
In the PBX Manager plugin, it can be configured how a deletion of a recording is processed. There are 3 modes selectable: "Recoverable", "Permanent" and "Denied". 
If "Recoverable" is selected, the users attached to this app object will transfer a recording to the recycle bin upon a delete operation, otherwise the recordings will be permanently deleted.
If "Denied" is selected, users are not able to delete a recording.

=== Scheduled deletion of old recordings ===
You can configure a time period between ''1 and 11000 days'' (in maximum round about 30 years), after which recordings are automatically removed. You can enter ''0 days'' here to disable the scheduled deletion.

== Call Information ==
The call information are retrieved from App Service "Reports". It requires an installed and running App Service "Reports". "Reports" does not
need own licenses to be run with recordings. With this method, it is possible to provide detailed call flow information for each recording.

== Call Recording Storage ==
If a 60 second Call with Codec G.711 is recorded, it will take approx. 1.5 MegaByte memory.

== Licensing ==

An appropriate license ''App(innovaphone-recorder)'' must be installed on the PBX to enable Recordings App functionality for specified users.

The Recorder App License can be assigned directly to a specific User Object or via a Config Template.

The recordings for users without an assigned Recorder App License will be unrecoverable deleted after a 30 day grace period.
If the TTL has been configured in RecordingsAdmin to be less than 30 days, the grace period is also shortened accordingly.

== Recording on Special Interfaces ==

* Trunk Interface/Gateway

The Trunk Interface acts as a substitute for the user's phone. For outgoing calls the call initiator is the owner of the recording and for him a license is required. With incoming calls, the first user answering the call owns the recording and a license for this user is required.

* Waiting Queue

The user answering the call is the owner, a license for this user is required.

== Upgrade from V13r3 or V14r1 to V14r2 Recordings App ==

=== Compatibility ===

A V14r2 Recordings App can not be used in the V13r3 or V14r1 PBX and App Platform environment.

=== License Changes ===

Licensing is the same as version 14r1

=== Database Conversion ===

Databases from previous versions (13r3,14r1) will be converted automatically

=== Update App Object configuration ===

If upgrading from a previous version, the app object configuration in the PBX Manager must be invoked.
Each app object configuration must be selected and "Ok"-ed for the new interoperation with App Service
"Reports" to be set up. In detail these are: the websocket connection, the "reporting" app usage and the
usage of the "Admin" and "Services" API.

=== Download recording ===

Once a recording is converted to .wav format, it can be downloaded. In version 14r2, this is done in a zip archive containing the wave audio file and a .pdf file containing
the call information.

== WebDav Access ==
WebDav access allows accessing the recordings database to download recordings in the original stored mode (pcap format). Clients such as WinSCP can be used for this purpose. In order to enable WebDav access credentials
(username, password) must be configured in the RecordingsAdmin gui.

Note: When webdav access credentials are configured, the recording itself must be configured to use these credentials as well.
For information on how to configure authentication for the recording clients, see [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]

== Encrypted Recordings ==

Recordings can be stored encrypted when in the Recordings Admin app in the settings tab a Crypt Key is configured. Encryption happens as long as a crypt key is configured, if it is deleted
then the next reecordings are stored unencrypted. The crypt key is linked to the recording, so if the user changes this key the previous key must be remebered to access previously stored recordings with that key

== 4 Eyes Access ==

This is an access mode where a user can only access the recordings when a "supervisor" is present and gives permission. The supervisor for access permission is configured in the recordings pbymanager plugin. There, a dropdown list
"Monitor" consisting of all the users on the pbx is given to select the supervisor. If a supervisor is configured the users recordings app, upon start, contacts the supervisor and asks for permission.

Note: The supervisor must be present during the whole user sessions. If the supervisor closes his recordings app, all permissions given to the users are revoked

== Notes ==

To each recording textual notes can be added. To achieve this a part of the "connect" app is invoked. Pressing the "Note" button on the recording entry opens a window beneath the entry where the connect app is invoked. Input and Handling of the notes is as in the connect app. Pressing the "note" button again closes the window.
To enable this functionality the appropriate connect app must be selected in the recordings pbxmanger plugin

== Watermark ==

In order to guarantee the validity of a recording a watermark can be added. To enable watermarking it must be selected in the recordings pbxmanager plugin. Recordings that existedin the db prior to enabling the watermarking will also be marked. The validity of a recording can then be checked in the recordings admin app by pressing the "verify" button.

== Troubleshooting ==

=== Recordings App Service ===
The App Service for Recordings App provides a log output on the App instance, after the Diagnostics option "App" is activated for the selected instance.

Additional Trace Level Options for the App Service are configurable via Recordings Admin App. These settings are available via an additional Menu in the upper right corner of the Recordings Admin UI:

*Recording - PCAP interface related traces, useful on issues with IP-Phone and Interface Media transmission from Endpoint to the App Service
*Call Information - traces related to the CDR information
*Conversion - traces for conversion process from VoIP codecs to WAV
*License - traces for on licensing issues
*GUI - traces related to the user interface of the Recordings App
*Connections - traces related to connections between RecordingsApp and PBX

The name of the Master PBX must be configured via the Recordings Admin App, otherwise a message ''PBX Name missing'' will be displayed.

=== PBX Configuration ===
*WebSocket connection from App Object to the Recordings App should show ''connected''
*A correct configuration of the CDR interface is required for transmission of metadata to the App Service "Reports".
*In case the connection between recordings and App Service "Reports" is not successful, a red "broken link" and the message "Still initializing" is shown on top of the RecordingsAdmin and an entry in the event log will be added.

=== PCAP Recording Interfaces ===
*Check URL for PCAP Recording provided on the IP-Phone or VoIP-Interface of a VoIP Gateway
*A Trace with enabled HTTP-Client option should show a successful HTTP PUT Request towards URL of the Recordings Service PCAP interface (e.g. <code>HTTPCLIENT WEBDAV_FILE_HTTP.2: PUT <nowiki>http://ap.company.com/company.com/recordings/Files/f9e5956e47d460010630009033302ab1-009033302ab1-11--username.pcap</nowiki></code>)

== Related Articles ==
[[Howto14r1:RecordingsApp|HowtoV14r1: Recordings App configuration]]

== Known Problems ==
=== Destination number is not displayed correctly when overlap dialing is used ===

If overlap dialing is used on the hardwarephone, the destination number is only displayed in the RecordingApp with the first digit dialed instead of the full number. The SoftphoneApp does not dial using overlap dialing, therefore is not affected by this problem.
 
Workaround: Configure an enblock timeout of e.g. 3 seconds in the Phone/User[1-6] -> ''Enblock Dialing Timeout [s]'' at the hardwarephone for the corresponding user.

Howto:Callflow Managementsystem CCS - Wbe AG - 3rd Party Product

2020-11-05T10:19:24Z

Ptr:

[[Image:wbe_logo.png|right]]
==Product name==
[http://www.wbe.ch/index.php?mode=callcenter Wbe CCS]

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

==Category==
{{Category:3rdParty Contact Center Applications}}
[[Category:3rdParty Contact Center Applications|{{PAGENAME}}]]

==Informationen zum Produkt==
Das Call Center System von WBe AG ist ein Anrufverfolgungssystem.
Das CCS-Monitoring bildet die Belegungszustände der TAPI überwachten Innovaphone-Ressourcen ab.
Das System CCS vermittelt Anrufe aufgrund eines speziellen Vermittlungsprogrammes, optimiert für CallCenter Anforderungen.
Parallel dazu setzt die CTI-Integration auf der Quelle der Anrufsteuerung auf und unterstützt alle bekannten Systempschnittstellen und Protokolle.

==Softwarestände der eingesetzten Anwendungen==
* UPDATE 9/2016 - Zertifizierung von 4.0.17.X mit Version V11 R2 SR8 - Zertifikat-Technologie-Partner
* IP 3010 V9 Hotfix 6
* novaalert V9.8

==Informationen zum PBX-System==
Die hier verwendete PBX ist eine Innovaphone IP3010. Der amtsseitige Anschluss ist ein PRI (S2M) Interface.
Für die Sprachübertragung zwischen den VoIP-Komponenten wird das Protokoll SIP verwendet.
Die Sprachendgeräte sind IP- Phones und SIP-Clients.
Die installierte Firmware-Version auf der IP3010 ist die Version 11r2 hotfix 6.
Die IP-Adresse der IP3010 ist hier 172.29.8.170

==Anbindung Callflow Managementsystem CCS==

Die Anbindung des CCS- Servers erfolgt über das SIP-Protokoll. Es wurde eine Anbindung über die Gateway-Funktion gewählt.
Gateways bieten die Möglichkeit Verbindungen zu VoIP-Geräten zu schalten, ohne diese direkt an der PBX anmelden zu müssen. Die Verbindungen werden auf der Innovaphone IP3010 im Menü "Routing" konfiguriert.

[[image:wbe_ccs_systemtopology.png]]

[[image:Wbe_ccs_routingconfiguration.png]]

Der erste Routing-Block routet die technische Nummern 566,567,568 Richtung CCS gehend. Die technische Nummern sind die Kennung für das Anmelden, Abmelden der Agenten über das Telefon und die Kennung für die Abfrage der Gruppen Mailbox.

Im zweiten Routing-Block ist die Richtung für die Anwahl der Testteilnehmer 551, 552, 553 kommend von der Richtung CCS eingestellt. CCS setzt den SIP-Treiber von Dialogic ein. Die Anrufzuweisung erfolgt über einen SIPTrunk- Kanal.

Die nächsten beiden Nummern sind Testnummern, 501 und 502 für den Gruppen- zugang. Die Nummern Richtung CCS sind Kennummern, welche durch das CCS als Gruppennummern ausgewertet werden.
Die 99 ist eine Nummer für den Test mit offener Numerierung. Die Kennung gibt das Routing Richtung CCS vor. Die nachfolgenden Nummern werden als Gruppen-Identifizierung ausgewertet, wobei die Kennung wahlweise mitberücksichtigt werden kann (Nummernwiederholung).

Die “0” ist die Kennung für die Amtsbelegung. Die Testumgebung ist über einen ISDN S2M- Primär- Anschluss mit dem öffentlichen Netz verbunden.
Der Primär-Anschluss wird im Test alternativ als ISDN- Vernetzung mit dem Call-flow Managementsystem CCS eingesetzt. Für den Testfall wird das ISDN Protokoll von DSS1 auf QSIG umkonfiguriert. Die Zugangs- Kennung ist die 515.

==Konfiguration des Gateways==

In der Konfiguration Gatekeeper ist das Gateway- Modul des Call Center Systems
CCS aufzunehmen.

Der “Name” ist frei wählbar. In unserem Beispiel CCS_Dialogic (SIP-Treiber).
Das Protokoll ist SIP/UDP oder SIP/TCP.
Im Feld “Mode” wird „Gateway without Registration“ ausgewählt.
Als Domains ist die kundenseitige Instllation zu berücksichtigen.
“Proxy” ist die IP-Adresse des CCS-Servers. In unserer Testumgebung die Adresse 172.29.8.175. Der Wert “Local Signaling Port” wurde auf 5060 gestellt.
Alle anderen Einstellungen sind Standardwerte.

[[image:wbe_ccs_gwconfig1.png]]

[[image:wbe_ccs_gwconfig2.png]]

==Konfiguration Callflow Managementsystem CCS==

Die Sprachressourcen respektive die Anzahl der SIP Kanäle ist einzutragen. Unter
Konfiguration Sprachleitungen im Auswahlfeld “Typ” ist Intel/Dialogic Voice Device
PRI einzustellen. Das CCS Gateway- Modul ist in die Systemsteuerung eingebun-
den. Die Kommunikation mit dem Dialogic Treiber ist identisch für die ISDN sowohl
für die SIPTrunk Ansteuerung.

Auch mit der SIP Ansteuerung können die Kanäle gemischt kommend und abgehend
(In/out) oder getrennt nach ankommend (In) und abgehend (Out) betrieben werden.
Nach der Beantwortung werden die SIP- Kanäle, welche an einer Anrufzuweisung
beteiligt sind, mit dem SIP Protokollaufruf refer in der Innovaphone umgekoppelt.

[[image:Wbe_ccs_ccsconfig1.png‎]]

[[image:Wbe_ccs_ccsconfig2.png‎]]

==Produktinformationen==
*Callflow Managementsystem CCS Produktebeschreibung
*[http://www.wbe.ch/linktoflyer.pdf Flyer Leistungsausweis]

==Schnittstellen/Protokolle==
*CSTA
*TAPI
*SOAP
*ISDN QSIP
*ISDN DSS1
*SIP
*URL
*XML
*Datenschnittstellen Herstellerspezifisch (z.B. SAP)

==Server Plattformen==
*Windows-Server Betriebsystem MS Windows
*Virtuelle Umgebung (VMware)

==Mögliche Einsatzbereiche==

==Über Wbe AG==
[http://www.wbe.ch/index.php?mode=kontakt Kontakt]

WBe AG

Honeywell-Platz 1

CH-8157 Dielsdorf

Phone: +41 (0)44 855 44 44

Fax: +41 (0)44 855 44 55

E-Mail: wbe@wbe.ch

Howto:Callflow Managementsystem CCS - Wbe AG - 3rd Party Product

2020-11-05T10:17:06Z

Ptr:

[[Image:wbe_logo.png|right]]
==Product name==
[http://www.wbe.ch/index.php?mode=callcenter Wbe CCS]

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

==Category==
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing|{{PAGENAME}}]]
{{Category:3rdParty Billing}}

{{Category:3rdParty Contact Center Applications}}
[[Category:3rdParty Contact Center Applications|{{PAGENAME}}]]

==Informationen zum Produkt==
Das Call Center System von WBe AG ist ein Anrufverfolgungssystem.
Das CCS-Monitoring bildet die Belegungszustände der TAPI überwachten Innovaphone-Ressourcen ab.
Das System CCS vermittelt Anrufe aufgrund eines speziellen Vermittlungsprogrammes, optimiert für CallCenter Anforderungen.
Parallel dazu setzt die CTI-Integration auf der Quelle der Anrufsteuerung auf und unterstützt alle bekannten Systempschnittstellen und Protokolle.

==Softwarestände der eingesetzten Anwendungen==
* UPDATE 9/2016 - Zertifizierung von 4.0.17.X mit Version V11 R2 SR8 - Zertifikat-Technologie-Partner
* IP 3010 V9 Hotfix 6
* novaalert V9.8

==Informationen zum PBX-System==
Die hier verwendete PBX ist eine Innovaphone IP3010. Der amtsseitige Anschluss ist ein PRI (S2M) Interface.
Für die Sprachübertragung zwischen den VoIP-Komponenten wird das Protokoll SIP verwendet.
Die Sprachendgeräte sind IP- Phones und SIP-Clients.
Die installierte Firmware-Version auf der IP3010 ist die Version 11r2 hotfix 6.
Die IP-Adresse der IP3010 ist hier 172.29.8.170

==Anbindung Callflow Managementsystem CCS==

Die Anbindung des CCS- Servers erfolgt über das SIP-Protokoll. Es wurde eine Anbindung über die Gateway-Funktion gewählt.
Gateways bieten die Möglichkeit Verbindungen zu VoIP-Geräten zu schalten, ohne diese direkt an der PBX anmelden zu müssen. Die Verbindungen werden auf der Innovaphone IP3010 im Menü "Routing" konfiguriert.

[[image:wbe_ccs_systemtopology.png]]

[[image:Wbe_ccs_routingconfiguration.png]]

Der erste Routing-Block routet die technische Nummern 566,567,568 Richtung CCS gehend. Die technische Nummern sind die Kennung für das Anmelden, Abmelden der Agenten über das Telefon und die Kennung für die Abfrage der Gruppen Mailbox.

Im zweiten Routing-Block ist die Richtung für die Anwahl der Testteilnehmer 551, 552, 553 kommend von der Richtung CCS eingestellt. CCS setzt den SIP-Treiber von Dialogic ein. Die Anrufzuweisung erfolgt über einen SIPTrunk- Kanal.

Die nächsten beiden Nummern sind Testnummern, 501 und 502 für den Gruppen- zugang. Die Nummern Richtung CCS sind Kennummern, welche durch das CCS als Gruppennummern ausgewertet werden.
Die 99 ist eine Nummer für den Test mit offener Numerierung. Die Kennung gibt das Routing Richtung CCS vor. Die nachfolgenden Nummern werden als Gruppen-Identifizierung ausgewertet, wobei die Kennung wahlweise mitberücksichtigt werden kann (Nummernwiederholung).

Die “0” ist die Kennung für die Amtsbelegung. Die Testumgebung ist über einen ISDN S2M- Primär- Anschluss mit dem öffentlichen Netz verbunden.
Der Primär-Anschluss wird im Test alternativ als ISDN- Vernetzung mit dem Call-flow Managementsystem CCS eingesetzt. Für den Testfall wird das ISDN Protokoll von DSS1 auf QSIG umkonfiguriert. Die Zugangs- Kennung ist die 515.

==Konfiguration des Gateways==

In der Konfiguration Gatekeeper ist das Gateway- Modul des Call Center Systems
CCS aufzunehmen.

Der “Name” ist frei wählbar. In unserem Beispiel CCS_Dialogic (SIP-Treiber).
Das Protokoll ist SIP/UDP oder SIP/TCP.
Im Feld “Mode” wird „Gateway without Registration“ ausgewählt.
Als Domains ist die kundenseitige Instllation zu berücksichtigen.
“Proxy” ist die IP-Adresse des CCS-Servers. In unserer Testumgebung die Adresse 172.29.8.175. Der Wert “Local Signaling Port” wurde auf 5060 gestellt.
Alle anderen Einstellungen sind Standardwerte.

[[image:wbe_ccs_gwconfig1.png]]

[[image:wbe_ccs_gwconfig2.png]]

==Konfiguration Callflow Managementsystem CCS==

Die Sprachressourcen respektive die Anzahl der SIP Kanäle ist einzutragen. Unter
Konfiguration Sprachleitungen im Auswahlfeld “Typ” ist Intel/Dialogic Voice Device
PRI einzustellen. Das CCS Gateway- Modul ist in die Systemsteuerung eingebun-
den. Die Kommunikation mit dem Dialogic Treiber ist identisch für die ISDN sowohl
für die SIPTrunk Ansteuerung.

Auch mit der SIP Ansteuerung können die Kanäle gemischt kommend und abgehend
(In/out) oder getrennt nach ankommend (In) und abgehend (Out) betrieben werden.
Nach der Beantwortung werden die SIP- Kanäle, welche an einer Anrufzuweisung
beteiligt sind, mit dem SIP Protokollaufruf refer in der Innovaphone umgekoppelt.

[[image:Wbe_ccs_ccsconfig1.png‎]]

[[image:Wbe_ccs_ccsconfig2.png‎]]

==Produktinformationen==
*Callflow Managementsystem CCS Produktebeschreibung
*[http://www.wbe.ch/linktoflyer.pdf Flyer Leistungsausweis]

==Schnittstellen/Protokolle==
*CSTA
*TAPI
*SOAP
*ISDN QSIP
*ISDN DSS1
*SIP
*URL
*XML
*Datenschnittstellen Herstellerspezifisch (z.B. SAP)

==Server Plattformen==
*Windows-Server Betriebsystem MS Windows
*Virtuelle Umgebung (VMware)

==Mögliche Einsatzbereiche==

==Über Wbe AG==
[http://www.wbe.ch/index.php?mode=kontakt Kontakt]

WBe AG

Honeywell-Platz 1

CH-8157 Dielsdorf

Phone: +41 (0)44 855 44 44

Fax: +41 (0)44 855 44 55

E-Mail: wbe@wbe.ch

Howto13r1:ASCOM DECT Interop - ASCOM - 3rd Party Product

2020-10-13T10:16:27Z

Ptr:

[[Image:Ascom_logo.jpg|right|280px]]

==Product Name==

*[http://www.ascom.com/ws/en/index-ws Ascom Wireless Solutions]

==Certification Status==







{{Template:Compat_Status_"referral_prod."-no-certificate}}

Testing of this product has been finalized January, 2014.

==Category==


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

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

==Functions==

* IP-DECT Basestation(IPBS 6.1.3) and robust DECT handset(d81)
* Wifi-handset(i62)

== Version ==


=== Product Version ===

*Ascom IP-DECT IPBS 6.1.3
*Ascom DECT Handset d81
*Ascom WiFi Handset i62 4.3.12

=== Innovaphone Version ===

*IP302 10.00 sr2
*IP800 10.00 sr2
*IP810 10.00 sr2
*IP6000 10.00 sr2
*IP6010 10.00 sr2

==Vendor==


[[Image:Ascom_logo_small.gif ]]

[http://www.ascom.com/ Ascom AG]

==Description==


Ascom Wireless Solutions is an established global leader in the provision of competitive solutions for wireless on-site communication to support and optimize mission-critical processes. The main focus is healthcare – hospitals, senior care and independent living – but we are also active in industry, secure establishments, retail and the hotel sector. One specific area is within mission-critical communication in hospitals. Ascom delivers innovative solutions within IP-DECT, VoWiFi, paging and nurse call systems. These solutions are based on Ascom Unite, the communication platform which links systems with sophisticated mission-critical working processes. Empowering individuals and organizations as a whole, our solutions add value to your daily operations, no matter how complex.

==Summary==


This [[Media:Innovaphone_v10_Wireless_Interoperability_Report.pdf | testreport]] proves full interoperability of Ascom Wireless systems (DECT and Wifi) to innovaphone IP-PBX systems. Included in the document are also the required configuration settings for the Innovaphone & Ascom devices.

==Contact==


{|
| colspan=99 | Gert Wallin
|-
| colspan=99 | Ascom Sweden Wireless Solutions
|-
| Phone: || +46 31 55 9514
|-
| Fax: || +46 31 55 20 31
|-
| Mail: || [mailto:gert.wallin@ascom.se gert.wallin@ascom.se]
|}

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

Category:3rdParty Terminal Devices

2020-10-13T10:14:24Z

Ptr:

SIP hardware and software endpoints

Howto:What is a 3rd Party Product

2020-10-13T10:11:16Z

Ptr: /* Terminal Devices */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''.

Products known as interoperable due to customer/3rd-pty manufacturer-testimonial, are marked as ''referral product'' within above mentioned list.


== 3rd-Party-Product Categories ==

'''3rd party devices are exclusively tested by their respective vendors''' and may be qualified as ''Referral Product'' if there is a written documentation made available in our wiki.

In case of any doubts concerning interoperability innovaphone recommends to do a Proof-Of-Concept to ensure interworking between innovaphone and the 3rd-party-product.

We differentiate 3rd-party-products into the following two main categories:
===3rd-party-terminals===
These are 3rd-party-IP-terminals which have been interop tested successfully with innovaphone PBXes.
To provide comparable results for our partners and customers, we impone generic [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Guidelines for Testing 3rd Party SIP Terminal Devices]] to be followed.
Tests and also documentation need to follow those guidelines to be documented within our wiki and get innovaphone referral product status.

===Other 3rd-party-products===
Other 3rd-pty-products except than terminals are categorized according to their usecase.
Available categories and existing products can be seen below.
For those 3rd-party-products, we as well require to do interoperability tests towards innovaphone products.
Those tests have to be done also by either the 3rd-party-product manufacturer or a partner which owns the 3rd-party-products. innovaphone itself does not care about those tests and will not support them.
As other 3rd-pty-products might be special in terms of functionality, usecase and configuration; innovaphone impones generation of a wiki-article following [[Howto:Guideline for Testing 3rd Party Products| the guideline for Testing 3rd Party Products]] to be listed as innovaphone referral product.



== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as referral product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
Follow above mentioned guidelines for
* [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Testing 3rd Party SIP Terminal Devices]]
* [[Howto:Guideline for Testing 3rd Party Products|Testing 3rd Party Products]]


= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== Alarm Server ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== App Development ==
[[:Category:3rdParty_App_Development|List of articles in ''{{Category:3rdParty_App_Development}}'']]

== Billing ==
[[:Category:3rdParty Billing|List of articles in ''{{Category:3rdParty Billing}}'']]

== Contact Center Applications ==
[[:Category:3rdParty Contact Center Applications|List of articles in ''{{Category:3rdParty Contact Center Applications}}'']]

== Cloud ==
[[:Category:3rdParty_Cloud|List of articles in ''{{Category:3rdParty_Cloud}}'']]

== Conferencing / Video Systems ==
[[:Category:3rdParty Conferencing / Video Systems|List of articles in ''{{Category:3rdParty Conferencing / Video Systems}}'']]

== CTI and integrations ==
[[:Category:3rdParty CTI and integrations|List of articles in ''{{Category:3rdParty CTI and integrations}}'']]

== Directory Services ==
[[:Category:3rdParty Directory Services|List of articles in ''{{Category:3rdParty Directory Services}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== Headsets ==
{{Category:3rdParty Headsets}}

== Healthcare ==
[[:Category:3rdParty Healthcare|List of articles in ''{{Category:3rdParty Healthcare}}'']]

== Hotel ==
[[:Category:3rdParty Hotel|List of articles in ''{{Category:3rdParty Hotel}}'']]

== Mobility Solutions ==
[[:Category:3rdParty Mobility Solutions|List of articles in ''{{Category:3rdParty Mobility Solutions}}'']]

== Music on Hold ==
[[:Category:3rdParty Music on Hold|List of articles in ''{{Category:3rdParty Music on Hold}}'']]

== Network Management ==
[[:Category:3rdParty Network Management|List of articles in ''{{Category:3rdParty Network Management}}'']]

== Recording ==
[[:Category:3rdParty Recording|List of articles in ''{{Category:3rdParty Recording}}'']]

== Reporting / Monitoring ==
[[:Category:3rdParty Reporting / Monitoring|List of articles in ''{{Category:3rdParty Reporting / Monitoring}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== SIP Terminal Devices ==
[[:Category:3rdParty Terminal Devices|List of articles in ''{{Category:3rdParty Terminal Devices}}'']]

== Wireless ==
[[:Category:3rdParty_Wireless|List of articles in ''{{Category:3rdParty_Wireless}}'']]

= Previous 3rd Party Products =

[[:Category:3rdParty PreviousProducts|List of previously tested 3rd party products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:What is a 3rd Party Product

2020-10-13T10:10:32Z

Ptr: /* What has to be done to list a new ''3rd party product''? */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''.

Products known as interoperable due to customer/3rd-pty manufacturer-testimonial, are marked as ''referral product'' within above mentioned list.


== 3rd-Party-Product Categories ==

'''3rd party devices are exclusively tested by their respective vendors''' and may be qualified as ''Referral Product'' if there is a written documentation made available in our wiki.

In case of any doubts concerning interoperability innovaphone recommends to do a Proof-Of-Concept to ensure interworking between innovaphone and the 3rd-party-product.

We differentiate 3rd-party-products into the following two main categories:
===3rd-party-terminals===
These are 3rd-party-IP-terminals which have been interop tested successfully with innovaphone PBXes.
To provide comparable results for our partners and customers, we impone generic [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Guidelines for Testing 3rd Party SIP Terminal Devices]] to be followed.
Tests and also documentation need to follow those guidelines to be documented within our wiki and get innovaphone referral product status.

===Other 3rd-party-products===
Other 3rd-pty-products except than terminals are categorized according to their usecase.
Available categories and existing products can be seen below.
For those 3rd-party-products, we as well require to do interoperability tests towards innovaphone products.
Those tests have to be done also by either the 3rd-party-product manufacturer or a partner which owns the 3rd-party-products. innovaphone itself does not care about those tests and will not support them.
As other 3rd-pty-products might be special in terms of functionality, usecase and configuration; innovaphone impones generation of a wiki-article following [[Howto:Guideline for Testing 3rd Party Products| the guideline for Testing 3rd Party Products]] to be listed as innovaphone referral product.



== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as referral product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
Follow above mentioned guidelines for
* [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Testing 3rd Party SIP Terminal Devices]]
* [[Howto:Guideline for Testing 3rd Party Products|Testing 3rd Party Products]]


= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== Alarm Server ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== App Development ==
[[:Category:3rdParty_App_Development|List of articles in ''{{Category:3rdParty_App_Development}}'']]

== Billing ==
[[:Category:3rdParty Billing|List of articles in ''{{Category:3rdParty Billing}}'']]

== Contact Center Applications ==
[[:Category:3rdParty Contact Center Applications|List of articles in ''{{Category:3rdParty Contact Center Applications}}'']]

== Cloud ==
[[:Category:3rdParty_Cloud|List of articles in ''{{Category:3rdParty_Cloud}}'']]

== Conferencing / Video Systems ==
[[:Category:3rdParty Conferencing / Video Systems|List of articles in ''{{Category:3rdParty Conferencing / Video Systems}}'']]

== CTI and integrations ==
[[:Category:3rdParty CTI and integrations|List of articles in ''{{Category:3rdParty CTI and integrations}}'']]

== Directory Services ==
[[:Category:3rdParty Directory Services|List of articles in ''{{Category:3rdParty Directory Services}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== Headsets ==
{{Category:3rdParty Headsets}}

== Healthcare ==
[[:Category:3rdParty Healthcare|List of articles in ''{{Category:3rdParty Healthcare}}'']]

== Hotel ==
[[:Category:3rdParty Hotel|List of articles in ''{{Category:3rdParty Hotel}}'']]

== Mobility Solutions ==
[[:Category:3rdParty Mobility Solutions|List of articles in ''{{Category:3rdParty Mobility Solutions}}'']]

== Music on Hold ==
[[:Category:3rdParty Music on Hold|List of articles in ''{{Category:3rdParty Music on Hold}}'']]

== Network Management ==
[[:Category:3rdParty Network Management|List of articles in ''{{Category:3rdParty Network Management}}'']]

== Recording ==
[[:Category:3rdParty Recording|List of articles in ''{{Category:3rdParty Recording}}'']]

== Reporting / Monitoring ==
[[:Category:3rdParty Reporting / Monitoring|List of articles in ''{{Category:3rdParty Reporting / Monitoring}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== Terminal Devices ==
[[:Category:3rdParty Terminal Devices|List of articles in ''{{Category:3rdParty Terminal Devices}}'']]

== Wireless ==
[[:Category:3rdParty_Wireless|List of articles in ''{{Category:3rdParty_Wireless}}'']]

= Previous 3rd Party Products =

[[:Category:3rdParty PreviousProducts|List of previously tested 3rd party products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:What is a 3rd Party Product

2020-10-13T10:09:58Z

Ptr: /* 3rd-party-terminals */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''.

Products known as interoperable due to customer/3rd-pty manufacturer-testimonial, are marked as ''referral product'' within above mentioned list.


== 3rd-Party-Product Categories ==

'''3rd party devices are exclusively tested by their respective vendors''' and may be qualified as ''Referral Product'' if there is a written documentation made available in our wiki.

In case of any doubts concerning interoperability innovaphone recommends to do a Proof-Of-Concept to ensure interworking between innovaphone and the 3rd-party-product.

We differentiate 3rd-party-products into the following two main categories:
===3rd-party-terminals===
These are 3rd-party-IP-terminals which have been interop tested successfully with innovaphone PBXes.
To provide comparable results for our partners and customers, we impone generic [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Guidelines for Testing 3rd Party SIP Terminal Devices]] to be followed.
Tests and also documentation need to follow those guidelines to be documented within our wiki and get innovaphone referral product status.

===Other 3rd-party-products===
Other 3rd-pty-products except than terminals are categorized according to their usecase.
Available categories and existing products can be seen below.
For those 3rd-party-products, we as well require to do interoperability tests towards innovaphone products.
Those tests have to be done also by either the 3rd-party-product manufacturer or a partner which owns the 3rd-party-products. innovaphone itself does not care about those tests and will not support them.
As other 3rd-pty-products might be special in terms of functionality, usecase and configuration; innovaphone impones generation of a wiki-article following [[Howto:Guideline for Testing 3rd Party Products| the guideline for Testing 3rd Party Products]] to be listed as innovaphone referral product.



== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as referral product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
Follow above mentioned guidelines for
* [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Testing 3rd Party SIP Devices]]
* [[Howto:Guideline for Testing 3rd Party Products|Testing 3rd Party Products]]


= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== Alarm Server ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== App Development ==
[[:Category:3rdParty_App_Development|List of articles in ''{{Category:3rdParty_App_Development}}'']]

== Billing ==
[[:Category:3rdParty Billing|List of articles in ''{{Category:3rdParty Billing}}'']]

== Contact Center Applications ==
[[:Category:3rdParty Contact Center Applications|List of articles in ''{{Category:3rdParty Contact Center Applications}}'']]

== Cloud ==
[[:Category:3rdParty_Cloud|List of articles in ''{{Category:3rdParty_Cloud}}'']]

== Conferencing / Video Systems ==
[[:Category:3rdParty Conferencing / Video Systems|List of articles in ''{{Category:3rdParty Conferencing / Video Systems}}'']]

== CTI and integrations ==
[[:Category:3rdParty CTI and integrations|List of articles in ''{{Category:3rdParty CTI and integrations}}'']]

== Directory Services ==
[[:Category:3rdParty Directory Services|List of articles in ''{{Category:3rdParty Directory Services}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== Headsets ==
{{Category:3rdParty Headsets}}

== Healthcare ==
[[:Category:3rdParty Healthcare|List of articles in ''{{Category:3rdParty Healthcare}}'']]

== Hotel ==
[[:Category:3rdParty Hotel|List of articles in ''{{Category:3rdParty Hotel}}'']]

== Mobility Solutions ==
[[:Category:3rdParty Mobility Solutions|List of articles in ''{{Category:3rdParty Mobility Solutions}}'']]

== Music on Hold ==
[[:Category:3rdParty Music on Hold|List of articles in ''{{Category:3rdParty Music on Hold}}'']]

== Network Management ==
[[:Category:3rdParty Network Management|List of articles in ''{{Category:3rdParty Network Management}}'']]

== Recording ==
[[:Category:3rdParty Recording|List of articles in ''{{Category:3rdParty Recording}}'']]

== Reporting / Monitoring ==
[[:Category:3rdParty Reporting / Monitoring|List of articles in ''{{Category:3rdParty Reporting / Monitoring}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== Terminal Devices ==
[[:Category:3rdParty Terminal Devices|List of articles in ''{{Category:3rdParty Terminal Devices}}'']]

== Wireless ==
[[:Category:3rdParty_Wireless|List of articles in ''{{Category:3rdParty_Wireless}}'']]

= Previous 3rd Party Products =

[[:Category:3rdParty PreviousProducts|List of previously tested 3rd party products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:What is a 3rd Party Product

2020-10-13T10:09:12Z

Ptr: /* What has to be done to list a new ''3rd party product''? */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''.

Products known as interoperable due to customer/3rd-pty manufacturer-testimonial, are marked as ''referral product'' within above mentioned list.


== 3rd-Party-Product Categories ==

'''3rd party devices are exclusively tested by their respective vendors''' and may be qualified as ''Referral Product'' if there is a written documentation made available in our wiki.

In case of any doubts concerning interoperability innovaphone recommends to do a Proof-Of-Concept to ensure interworking between innovaphone and the 3rd-party-product.

We differentiate 3rd-party-products into the following two main categories:
===3rd-party-terminals===
These are 3rd-party-IP-terminals which have been interop tested successfully with innovaphone PBXes.
To provide comparable results for our partners and customers, we impone generic [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Guidelines for Testing 3rd Party SIP Devices]] to be followed.
Tests and also documentation need to follow those guidelines to be documented within our wiki and get innovaphone referral product status.

===Other 3rd-party-products===
Other 3rd-pty-products except than terminals are categorized according to their usecase.
Available categories and existing products can be seen below.
For those 3rd-party-products, we as well require to do interoperability tests towards innovaphone products.
Those tests have to be done also by either the 3rd-party-product manufacturer or a partner which owns the 3rd-party-products. innovaphone itself does not care about those tests and will not support them.
As other 3rd-pty-products might be special in terms of functionality, usecase and configuration; innovaphone impones generation of a wiki-article following [[Howto:Guideline for Testing 3rd Party Products| the guideline for Testing 3rd Party Products]] to be listed as innovaphone referral product.



== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as referral product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
Follow above mentioned guidelines for
* [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Testing 3rd Party SIP Devices]]
* [[Howto:Guideline for Testing 3rd Party Products|Testing 3rd Party Products]]


= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== Alarm Server ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== App Development ==
[[:Category:3rdParty_App_Development|List of articles in ''{{Category:3rdParty_App_Development}}'']]

== Billing ==
[[:Category:3rdParty Billing|List of articles in ''{{Category:3rdParty Billing}}'']]

== Contact Center Applications ==
[[:Category:3rdParty Contact Center Applications|List of articles in ''{{Category:3rdParty Contact Center Applications}}'']]

== Cloud ==
[[:Category:3rdParty_Cloud|List of articles in ''{{Category:3rdParty_Cloud}}'']]

== Conferencing / Video Systems ==
[[:Category:3rdParty Conferencing / Video Systems|List of articles in ''{{Category:3rdParty Conferencing / Video Systems}}'']]

== CTI and integrations ==
[[:Category:3rdParty CTI and integrations|List of articles in ''{{Category:3rdParty CTI and integrations}}'']]

== Directory Services ==
[[:Category:3rdParty Directory Services|List of articles in ''{{Category:3rdParty Directory Services}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== Headsets ==
{{Category:3rdParty Headsets}}

== Healthcare ==
[[:Category:3rdParty Healthcare|List of articles in ''{{Category:3rdParty Healthcare}}'']]

== Hotel ==
[[:Category:3rdParty Hotel|List of articles in ''{{Category:3rdParty Hotel}}'']]

== Mobility Solutions ==
[[:Category:3rdParty Mobility Solutions|List of articles in ''{{Category:3rdParty Mobility Solutions}}'']]

== Music on Hold ==
[[:Category:3rdParty Music on Hold|List of articles in ''{{Category:3rdParty Music on Hold}}'']]

== Network Management ==
[[:Category:3rdParty Network Management|List of articles in ''{{Category:3rdParty Network Management}}'']]

== Recording ==
[[:Category:3rdParty Recording|List of articles in ''{{Category:3rdParty Recording}}'']]

== Reporting / Monitoring ==
[[:Category:3rdParty Reporting / Monitoring|List of articles in ''{{Category:3rdParty Reporting / Monitoring}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== Terminal Devices ==
[[:Category:3rdParty Terminal Devices|List of articles in ''{{Category:3rdParty Terminal Devices}}'']]

== Wireless ==
[[:Category:3rdParty_Wireless|List of articles in ''{{Category:3rdParty_Wireless}}'']]

= Previous 3rd Party Products =

[[:Category:3rdParty PreviousProducts|List of previously tested 3rd party products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:What is a 3rd Party Product

2020-10-13T10:08:56Z

Ptr: /* 3rd-party-terminals */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''.

Products known as interoperable due to customer/3rd-pty manufacturer-testimonial, are marked as ''referral product'' within above mentioned list.


== 3rd-Party-Product Categories ==

'''3rd party devices are exclusively tested by their respective vendors''' and may be qualified as ''Referral Product'' if there is a written documentation made available in our wiki.

In case of any doubts concerning interoperability innovaphone recommends to do a Proof-Of-Concept to ensure interworking between innovaphone and the 3rd-party-product.

We differentiate 3rd-party-products into the following two main categories:
===3rd-party-terminals===
These are 3rd-party-IP-terminals which have been interop tested successfully with innovaphone PBXes.
To provide comparable results for our partners and customers, we impone generic [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices|Guidelines for Testing 3rd Party SIP Devices]] to be followed.
Tests and also documentation need to follow those guidelines to be documented within our wiki and get innovaphone referral product status.

===Other 3rd-party-products===
Other 3rd-pty-products except than terminals are categorized according to their usecase.
Available categories and existing products can be seen below.
For those 3rd-party-products, we as well require to do interoperability tests towards innovaphone products.
Those tests have to be done also by either the 3rd-party-product manufacturer or a partner which owns the 3rd-party-products. innovaphone itself does not care about those tests and will not support them.
As other 3rd-pty-products might be special in terms of functionality, usecase and configuration; innovaphone impones generation of a wiki-article following [[Howto:Guideline for Testing 3rd Party Products| the guideline for Testing 3rd Party Products]] to be listed as innovaphone referral product.



== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as referral product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
Follow above mentioned guidelines for
* [[Howto:Guidelines for Testing 3rd Party SIP Devices|Testing 3rd Party SIP Devices]]
* [[Howto:Guideline for Testing 3rd Party Products|Testing 3rd Party Products]]


= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== Alarm Server ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== App Development ==
[[:Category:3rdParty_App_Development|List of articles in ''{{Category:3rdParty_App_Development}}'']]

== Billing ==
[[:Category:3rdParty Billing|List of articles in ''{{Category:3rdParty Billing}}'']]

== Contact Center Applications ==
[[:Category:3rdParty Contact Center Applications|List of articles in ''{{Category:3rdParty Contact Center Applications}}'']]

== Cloud ==
[[:Category:3rdParty_Cloud|List of articles in ''{{Category:3rdParty_Cloud}}'']]

== Conferencing / Video Systems ==
[[:Category:3rdParty Conferencing / Video Systems|List of articles in ''{{Category:3rdParty Conferencing / Video Systems}}'']]

== CTI and integrations ==
[[:Category:3rdParty CTI and integrations|List of articles in ''{{Category:3rdParty CTI and integrations}}'']]

== Directory Services ==
[[:Category:3rdParty Directory Services|List of articles in ''{{Category:3rdParty Directory Services}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== Headsets ==
{{Category:3rdParty Headsets}}

== Healthcare ==
[[:Category:3rdParty Healthcare|List of articles in ''{{Category:3rdParty Healthcare}}'']]

== Hotel ==
[[:Category:3rdParty Hotel|List of articles in ''{{Category:3rdParty Hotel}}'']]

== Mobility Solutions ==
[[:Category:3rdParty Mobility Solutions|List of articles in ''{{Category:3rdParty Mobility Solutions}}'']]

== Music on Hold ==
[[:Category:3rdParty Music on Hold|List of articles in ''{{Category:3rdParty Music on Hold}}'']]

== Network Management ==
[[:Category:3rdParty Network Management|List of articles in ''{{Category:3rdParty Network Management}}'']]

== Recording ==
[[:Category:3rdParty Recording|List of articles in ''{{Category:3rdParty Recording}}'']]

== Reporting / Monitoring ==
[[:Category:3rdParty Reporting / Monitoring|List of articles in ''{{Category:3rdParty Reporting / Monitoring}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== Terminal Devices ==
[[:Category:3rdParty Terminal Devices|List of articles in ''{{Category:3rdParty Terminal Devices}}'']]

== Wireless ==
[[:Category:3rdParty_Wireless|List of articles in ''{{Category:3rdParty_Wireless}}'']]

= Previous 3rd Party Products =

[[:Category:3rdParty PreviousProducts|List of previously tested 3rd party products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:Guidelines for Testing 3rd Party SIP Devices

2020-10-13T10:08:01Z

Ptr: Howto:Guidelines for Testing 3rd Party SIP Devices moved to Howto:Guidelines for Testing 3rd Party SIP Terminal Devices: Besser so

#REDIRECT [[Howto:Guidelines for Testing 3rd Party SIP Terminal Devices]]

Howto:Guidelines for Testing 3rd Party SIP Terminal Devices

2020-10-13T10:08:01Z

Ptr: Howto:Guidelines for Testing 3rd Party SIP Devices moved to Howto:Guidelines for Testing 3rd Party SIP Terminal Devices: Besser so

==Scope==

innovaphone supports use of 3rd party SIP devices connected to the innovaphone PBX. In fact, when connecting 3rd party devices, SIP (or SIPS) is the recommended protocol. We do not recommend to use H.323 for this purpose.

Although innovaphone usually does no 3rd party SIP device compatibility tests, vendors can do them on their own. Such tests may be documented in our wiki in so-called ''referral product'' pages. See ''What it means'' in [[Howto:What_is_a_"3rd_Party_Product"%3F#What_it_means | What is a "3rd Party Product"? ]] for more information on ''referral products''.

The 3rd-party-product-vendor or any appropriate partner are '''exclusively responsible''' for
* creation of any testplan
* definition of detailed teststeps
* regression testing upon new firmware releases
* up-to-date documentation of test results

If you intend to test your device for innovaphone SIP compatibility, here are some notes you should consider

; STUN/TURN : [https://en.wikipedia.org/wiki/STUN STUN] and [https://en.wikipedia.org/wiki/Traversal_Using_Relays_around_NAT TURN] are required. Although we do not strictly require 3rd party devices to support it, it is needed in cloud and ''anywhere workplace'' scenarios. Failing to support STUN/TURN limits use of the 3rd party device to LAN or VPN scenarios
; ICE : again, for cloud and ''anywhere workplace'' scenarios, we also use [https://en.wikipedia.org/wiki/Interactive_Connectivity_Establishment ICE] as the general mechanism to negotiate the best media connection between 2 devices. As ICE is the supported mechanism to use STUN/TURN, neither would be used properly if ICE is not implemented. As a result, failing to support it limits use of the 3rd party device to LAN or VPN scenarios
; DTLS : we do support use of [https://en.wikipedia.org/wiki/Datagram_Transport_Layer_Security DTLS], which is a end-to-end media encryption scheme. Although we do not strictly require 3rd party devices to support it, it is needed for [https://en.wikipedia.org/wiki/WebRTC WebRTC] compatibility. 3rd party devices which fail to support it will not be able to talk to WebRTC compliant endpoints (i.e. Web Browsers)
; TSIP : (also known as SIP over TCP). TCP based SIP (optionally encrypted with TLS) is required to route SIP requests through our ''reverse proxy''. Therefore, devices supporting SIP/UDP only will not work in such scenarios
; SIP Offer/Answer Model : with Reverse-Media-Negotiation. This is required for all devices which are registered to the PBX directly. So this is a requirement for all 3rd party phones at least
; DTMF : various features in the PBX are controlled via DTMF tones. Endpoints are required to send DTMF either using RFC 2976 (''SIP INFO'') or RFC 2833 (''RTP DTMF''). The PBX will not recognize in-band DTMF audio tones
; LDAP : the innovaphone infrastructure relies on [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP] for access to directory data. Although 3rd parties my provide their own contact infrastructure, not supporting LDAP results in an inconsistent user experience
; CTI : can be tested using a myApps, myPBX, SOAP or TAPI
:* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list)
:* Answer incoming call
:* Hold/Retrieve
:* Transfer

For more information regarding implemented RFCs, see [[Reference:Supported SIP Features and List of RFC's]]

Test results and other informational data concerning the 3rd-pty-product have to be put into the innovaphone wiki according to following standardized format.

===Creation of a 3rd-party-product article===

* Login to innovaphone wiki
* Open this instruction in the first browser tab
* Open the following URL in a second window

http://wiki.innovaphone.com/index.php?title=Howto:productname_-_companyname_-_3rd_Party_Product&action=edit

* Replace the terms "productname" and "companyname" by your data.
* Confirm your input by pressing Enter
* A new empty wiki page titled with the given URL is generated and opened in editor mode
* Copy the text content from the box below and paste it completely into the empty wiki-page

<code>

[[Image:CompanyLogo.png||200px|right]]

==Product Name==


CompanyName [https://www.linktoproductpage.com ProductName]

==Certification Status==




==Category==





==Vendor==



[[Image:CompanyLogo.png|150px]]

==Description==














==Functions==





==innovaphone CTI ready==



==innovaphone Reverse Proxy ready==



==innovaphone WebRTC ready==



==Supported Codecs==


==DTMF Support==



==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==



==Support LDAP Phonebook==



==Version==




Product versions used for interop testing:

* 3rd-Pty-Product Version

* innovaphone V12r2sr24

==Configuration==





==Summary==



==Contact==



{|
| CompanyName
|-
| ContactName
|-
| Street
|-
| ZIP City
|-
| Tel:
|-
| Mobile:
|-
| Mail: [mailto:contactname@companyname contactname@companyname]
|}

</code>

* Start editing according to the comments given
* DON'T forget to SAVE!
* Upload appropriate files/images indicated by a red link
* Inform your innovaphone contact when finished
* innovaphone will set the correct product category and grant referral status upon successful document check

IP6010 Specyfikacja techniczna PL

2019-12-18T11:03:49Z

Ptr:

{{Template:Disclaimer PL}}
==Zdjęcie produktu==

[[Image:IP6010.png]]

==Specyfikacja techniczna==
===innovaphone IP6010===
VoIP-PBX i brama Routing z 4 interfejsami S2M oraz funkcjamiReverse Proxy i SBC

===Obudowa===
{{Template:Leistungsmerkmale PL alt - Gehäuse gross}}

Waga: 1050 g

===Interfejs===
4 x S2M interfejsy: korzystanie z łącza E1 lub T1,tryb pracy TE lub NT, brama szczególnie zalecana dla rozwiązań typu „płynna migracja, dodatkowe „Power-off-Loop“ odcina zasilanie 2 ISDN PRI, łącznie 60 kanałów

1 x S0 interfejs: port ISDN BRI dla routingu, administracji, synchronizacji, tworzenia kopii zapasowych (Backup)itd., tryb pracy TE lub NT

{{Template:Leistungsmerkmale PL alt - Schnittstellen}}

{{Template:Leistungsmerkmale PL alt - CF}}

===Hardware===
{{Template:Leistungsmerkmale PL alt - Hardware gross}}

Digital Signal Processor (DSP) dla max.60 kanałów głosowych/konferencyjnych.

2 kanały HDLC

10 kanałów dla innovaphone serwera faksu z T.38 lub przez G.711. W przypadku G.711 transmisja faksu zajmuje 2 kanały DSP.

===Kodeki głosowe===
{{Template:Leistungsmerkmale PL - Sprach Codecs GW}}

===innovaphone PBX===
Platforma przewidziana dla max. 500 użytkowników PBX (all-in-one)

===Funkcje===
[[V11_Gateway_Firmware_Features PL#Datenblatt|Funkcje bram innovaphone oprogramowanie V11]]

[[V12_Gateway_Firmware_Features PL#Datenblatt|Funkcje bram innovaphone oprogramowanie V12]]

===Licencji specyficznych dla urządzeń===
{{Template:Leistungsmerkmale_PL_-_Licenses_Gateways}}
===Nr katalogowy===
01-06010-001

==Deklaracje CE==
===Deklaracje zgodności===
{{Template:CE-Decl_Gateways}}
===Numer WEEE===
{{Template:WEEE-Number}}
[[Category:Specyfikacja techniczna PL|{{PAGENAME}}]]

Howto:Hitchikers Guide to the "3rd Party Product Listing"

2017-09-08T13:24:00Z

Ptr: /* How it works */

innovaphone entertains an [[recprodredirector|''innovaphone listed 3rd party product'']] programme. Here is how it works.

=What it is all about=
The ''Listed 3rd Party Product'' programme has the following main objectives:
* Development of a closer partnership with 3rd party vendors
* Support of marketing and press activities through mutual presence on the respective web sites and coordinated press releases
* Guidance for innovaphone customers through the "''Which devices and 3rd party applications do work with innovaphone solutions''" jungle ([[:Category:Compat|''Compatibility List'']])
* Guidance for innovaphone and innovaphone partner sales and pre-sales staff regarding the opportunities brought by 3rd party applications

=How it works=
These are the required steps (not necessarily in exactly this order) to get listed:
* Someone (we, a partner, a 3rd party vendor) deems a 3rd party product interesting for this programme
* This idea is brought up to [mailto:presales@innovaphone.com presales] along with contact to the 3rd party vendor (usually the product manager)
* Presales will contact the vendor
* It is agreed which level (customer testimonial, engineered product, recommended product) is appropriate
* The initiator (vendor, partner, ...) creates the ''3rd party product page'' (see [[#How do I start the process?|the section below]])
* Once the entry meets the requirements, innovaphone will list it on its [[Recprodredirector|''3rd party product list'']]
* The vendor will add a note regarding the listing on its own publicly accessible web space along with a link to innovaphone’s web site
* If the entry qualifies as a ''recommended product'', the vendor is granted the right to use the logo
* The entry will possibly be published in the innovaphone Newsletters

== Requirements ==
Generally, the vendor must provide all wording to be used in the listing. If a joint press release is anticipated, a press contact is required
=== Customer Testimonial Entries (Referral Product)===
There must be a major customer project where the product has been used successfully with innovaphone devices. The interoperability tests are done and described by the vendor. A point of contact (innovaphone sales rep or partner) is available.
=== Engineered Product ===
The vendor will book presales lab time to work on interoperability issues at the vendors discretion. In most cases, innovaphone will sponsor the required PC hardware and operating system licenses plus the innovaphone devices necessary. The vendor will sponsor its own devices and/or any required non-innovaphone licenses.
=== Recommended Product ===
A reference installation is set up in innovaphone's compatibility lab. In most cases, innovaphone will sponsor the required PC hardware and operating system licenses plus the innovaphone devices necessary. The vendor will sponsor its own devices and/or any required non-innovaphone licenses. The vendor will perform the reference installation either through an on-site visit or by remote maintenance. Also,
Problems encountered will be analysed and possibly fixed. Technical assistance (either on-site at innovaphone premises or remote) is provided by the vendor. A decent test plan for the product's interoperability is worked out. agreed and executed (suggestions by the vendor may simplify and speed up this part).

=Are there different levels of certification?=
See above.

There is a chance that we are testing products in a one-shot, ad-hoc fashion. The result (a test result) will be added to the list. This does not require cooperation by the equipment vendor.

=Who may be listed?=
In principle, there is no limitation. However, there is quite some effort involved, so that there must be a significant potential to innovaphone.

=How does a ''Recommended Product'' certificate look like?=
[[Image:Sample-recprod-cert.png]]

=What is the Cost?=
innovaphone will charge standard presales support charges as per the then-current price list for engineering days in the innovaphone labs. No further cost.

=How do I start the process?=
If you intend to have your product certified, then contact your responsible innovaphone sales representative. She will then liaise with innovaphone presales. If the product listing is approved, innovaphone will create a new article in its wiki.

Howto:HospiX Open - MSI Solutions - 3rd Party Product

2016-11-18T15:54:27Z

Ptr:

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]

==Product name==
[http://www.msi-telesolutions.com/en/hospixopen.php HospiX Open]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]],
[[Category:3rdParty Hotel / Hospitality and Care|{{PAGENAME}}]]
{{Category:3rdParty Hotel / Hospitality and Care}}

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Management-Reports as a controlling instrument and to document communications traffic of all substations
*Comfortable service functions with a customized feature set for highest customer satisfaction
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Front Office and PMS-Integration
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Open Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Open is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Management reports for controlling and documentation of communication traffic
* Comfortable service features, tailored for highest customer satisfaction
The integrated interface HospiX Connect enables data exchange between HospiX Open and business-specific administrative systems (e.g. Front Office systems).
HospiX Open is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For hotels or other accomodation businesses with basic requirements and without a explicit Front Office System use [[ Howto:HospiX_Entry_-_MSI_Solutions_-_3rd_Party_Product | HospiX Entry]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Open is the ideal solution for medium-sized and large accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 50 rooms can be extended for individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Open - MSI Solutions - 3rd Party Product

2016-11-18T15:54:03Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]

==Product name==
[http://www.msi-telesolutions.com/en/hospixopen.php HospiX Open]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
[[Category:3rdParty Hotel / Hospitality and Care|{{PAGENAME}}]]
{{Category:3rdParty Hotel / Hospitality and Care}}

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Management-Reports as a controlling instrument and to document communications traffic of all substations
*Comfortable service functions with a customized feature set for highest customer satisfaction
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Front Office and PMS-Integration
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Open Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Open is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Management reports for controlling and documentation of communication traffic
* Comfortable service features, tailored for highest customer satisfaction
The integrated interface HospiX Connect enables data exchange between HospiX Open and business-specific administrative systems (e.g. Front Office systems).
HospiX Open is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For hotels or other accomodation businesses with basic requirements and without a explicit Front Office System use [[ Howto:HospiX_Entry_-_MSI_Solutions_-_3rd_Party_Product | HospiX Entry]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Open is the ideal solution for medium-sized and large accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 50 rooms can be extended for individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:50:22Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
{{Category:3rdParty Billing System / Call Management}},
[[Category:3rdParty Hotel / Hospitality and Care|{{PAGENAME}}]]
{{Category:3rdParty Hotel / Hospitality and Care}}

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:What is a 3rd Party Product

2016-11-18T15:49:54Z

Ptr: /* Hospitality / Care */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''. It has 3 major building blocks
* products known as interoperable due to customer testimonial (''referral product'')
* products which have been interoperability-enhanced by a joined effort of vendor and innovaphone engineers in innovaphone labs (''engineered product'')
* products tested by innovaphone (''tested product'')

All such products will be listed in the ''3rd party product list''. Products that have been tested OK in innovaphone labs additionally will bear the ''innovaphone recommended product'' [[Image:Recprod.PNG]] logo.

== What it means ==
So what exactly can you expect from a ''3rd party product''?

; Referral Product : has been used successfully in one or more major customer projects known to us. The project may be described in a user story, also, we may be able to provide contact information of the partner who has implemented the project upon request (contact your innovaphone sales rep)
; Engineered Product : vendor has worked with us in our labs to enhance/ensure interoperability based on his own requirements/test plans
; Recommended Product : product has passed tests in the innovaphone labs OK. This means that all relevant interface used to interact with the innovaphone devices do work as expected. It does not mean that the passing product is the greatest product in the world. Instead, it says that the product interfaces ok with innovaphone. There may or may not be a better product, or a product more suitable for specific requirements available. This decision is deliberately left to the market.

== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as recommended product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
See [[Howto:Hitchikers Guide to the "3rd Party Product Listing" |the ''hitchikers guide to the 3rd party product'']] for a description of the procedure.

= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== 3rd Party PBX ==
[[:Category:3rdParty PBX|List of articles in ''{{Category:3rdParty PBX}}'']]

== Alarm server Products ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== Billing System / Call Management ==
[[:Category:3rdParty Billing System / Call Management|List of articles in ''{{Category:3rdParty Billing System / Call Management}}'']]

== CTI and UMS applications ==
[[:Category:3rdParty CTI and UMS applications|List of articles in ''{{Category:3rdParty CTI and UMS applications}}'']]

== Call Center Applications ==
[[:Category:3rdParty Call Center Applications|List of articles in ''{{Category:3rdParty Call Center Applications}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== H.323 and SIP Terminals ==
[[:Category:3rdParty Terminals|List of articles in ''{{Category:3rdParty Terminals}}'']]

== Headsets ==
[[:Category:3rdParty Headsets|List of articles in ''{{Category:3rdParty Headsets}}'']]

== Hotel / Hospitality and Care ==
[[:Category:3rdParty Hotel / Hospitality and Care|List of articles in ''{{Category:3rdParty Hotel / Hospitality and Care}}'']]

== IP Voice Conferencing Systems ==
[[:Category:3rdParty IP Voice Conferencing Systems|List of articles in ''{{Category:3rdParty IP Voice Conferencing Systems}}'']]

== Music on Hold Solutions ==
[[:Category:3rdParty Music on Hold Solutions|List of articles in ''{{Category:3rdParty Music on Hold Solutions}}'']]

== Network Infrastructure Products ==
[[:Category:3rdParty Network Infrastructure Products|List of articles in ''{{Category:3rdParty Network Infrastructure Products}}'']]

== Network Management and Assessment Tools ==
[[:Category:3rdParty Network Management and Assessment Tools|List of articles in ''{{Category:3rdParty Network Management and Assessment Tools}}'']]

== Network Security Appliances ==
[[:Category:3rdParty Network Security Appliances|List of articles in ''{{Category:3rdParty Network Security Appliances}}'']]

== Professional Announcements ==
[[:Category:3rdParty Professional Announcements|List of articles in ''{{Category:3rdParty Professional Announcements}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== Solutions for Mobile Extensions ==
[[:Category:3rdParty Solutions for Mobile Extensions|List of articles in ''{{Category:3rdParty Solutions for Mobile Extensions}}'']]

== Voice Recording ==
[[:Category:3rdParty Voice Recording|List of articles in ''{{Category:3rdParty Voice Recording}}'']]

== 3rdParty Wireless System ==
[[:Category:3rdParty_Wireless_System|List of articles in ''{{Category:3rdParty_Wireless_System}}'']]

=List of all 3rd Party Products=
[[:Category:3rd Party Products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:43:01Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
{{Category:3rdParty Hospitality / Care}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Hospitality / Care|{{PAGENAME}}]]

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:41:11Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:40:49Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
{{Category:3rdParty Hospitality / Care}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Hospitality / Care|{{PAGENAME}}]]

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:38:55Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:38:34Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
[[Category:3rdParty Hospitality / Care}}

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:37:11Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
[[Category:3rdParty Hospitality / Care|{{PAGENAME}}]]

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:HospiX Entry - MSI Solutions - 3rd Party Product

2016-11-18T15:36:36Z

Ptr: /* Category */

[[Image:MSI_logo_200.png|right]]
[[Image:HospiX_200.png|right]]
==Product name==
[http://www.msi-telesolutions.com/de/hospixentry.php HospiX Entry]

==Certification Status==







{{Template:Compat_Status_referral_product_new}}

==Category==
{{Category:3rdParty Billing System / Call Management}}
[[Category:Referral Product|{{PAGENAME}}]]
[[Category:3rdParty Billing System / Call Management|{{PAGENAME}}]]
{{Category:3rdParty Hospitality / Care}}

==Functions==
Management System for Communication Services in Hotels and the Accommodation Business.

*Dual billing system for efficient recording and accounting of communication costs for telephone and internet
*Stand-alone mode (without PMS) with basic Frontoffice functionality.
*Front Office and PMS-Integration with additional licence
*Check-In/Check-Out (for groups also)
*Class of service change-over of extension lines
*Accounting according to flexible tariff models
*Invoice printing
*Intermediate invoices
*Wake-up calls
*Name setting for caller identification
*Room status setting
*System connection
*Multi-user

==Version==

*innovaphone PBX v10
*HospiX Entry Version 2.05 Build 578 or higher

==Vendor==

[[Image:MSI_logo_200.png|100px]]
{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
|}
[http://www.msi-telesolutions.com/en/index.php www.msi-telesolutions.com]

==Description==


HospiX Entry is a solution to support the operation of communication systems efficiently. The basic features include:
* Dual billing for efficient reporting and accounting of communication costs for telephony and internet
* Comfortable service features, tailored for highest customer satisfaction
The additional interface HospiX Connect enables data exchange between HospiX Entry and business-specific administrative systems (e.g. Front Office systems).
HospiX Entry is easily expandable through licenses and offers optional modules for a customized solution.

==Competitive Analysis==

For large hotels (50+ rooms) or other accomodation businesses with extended requirements and with explicit Front Office System use [[Howto:HospiX_Open_-_MSI_Solutions_-_3rd_Party_Product | HospiX Open]].


Use [[Howto:PhoneStat_-_MSI_Solutions_-_3rd_Party_Product | PhoneStat]] for call accounting without need for check-in and check-out

==Summary==
HospiX Entry is the ideal solution for small- and medium-sized accommodation facilities (hotels, motels, hostels, camping sites etc.).

==Pricing==

A Basic System for 25 rooms can be extended according to the individual situation. Pricing depends on the amount of extensions and extra modules. Please contact MSI Solutions for an offer.

==Contact==


{|
| colspan=99 |
|-
| colspan=99 | MSI Solutions GmbH
|-
| colspan=99 | Geisenhausenerstraße 17, 81379 Munich
|-
| colspan=99 | Germany
|-
| colspan=99 | '''Main:'''
|-
| Tel: || +49 89 748564-0
|-
| Fax: || +49 89 748564-33
|-
| Mail: || [mailto:info@msi-telesolutions.com info@msi-telesolutions.com]
|-
| colspan=99 | '''Sales:'''
|-
| Tel: || +49 89 748564-23
|-
| Mail: || [mailto:sales@msi-telesolutions.com sales@msi-telesolutions.com]
|-
| colspan=99 | '''Technical support:'''
|-
| Tel: || +49 89 748564-27
|-
| Mail: || [mailto:support@msi-telesolutions.com support@msi-telesolutions.com]
|}

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

Howto:What is a 3rd Party Product

2016-11-18T15:28:00Z

Ptr: /* List of 3rd party products */

= Overview =
== What it is all about ==
A major design principle for innovaphone products is [http://www.innovaphone.com/index.php?id=168 ''being based on standards''] strictly.

While this brings a number of substantial advantages to the customers, amongst others a huge base of 3rd applications that can work with innovaphone gear, it may sometimes create headaches for the innovaphone professional in charge of designing solutions. H450, TAPI, Empty Termcaps, DSS1, H.245, XML, SS7, .... it's easy to get lost in the standards jungle! Application interoperability thus is key to successful integration with 3rd party software.

To assist with determining application interoperability, innovaphone entertains a ''3rd party product list''. It has 3 major building blocks
* products known as interoperable due to customer testimonial (''referral product'')
* products which have been interoperability-enhanced by a joined effort of vendor and innovaphone engineers in innovaphone labs (''engineered product'')
* products tested by innovaphone (''tested product'')

All such products will be listed in the ''3rd party product list''. Products that have been tested OK in innovaphone labs additionally will bear the ''innovaphone recommended product'' [[Image:Recprod.PNG]] logo.

== What it means ==
So what exactly can you expect from a ''3rd party product''?

; Referral Product : has been used successfully in one or more major customer projects known to us. The project may be described in a user story, also, we may be able to provide contact information of the partner who has implemented the project upon request (contact your innovaphone sales rep)
; Engineered Product : vendor has worked with us in our labs to enhance/ensure interoperability based on his own requirements/test plans
; Recommended Product : product has passed tests in the innovaphone labs OK. This means that all relevant interface used to interact with the innovaphone devices do work as expected. It does not mean that the passing product is the greatest product in the world. Instead, it says that the product interfaces ok with innovaphone. There may or may not be a better product, or a product more suitable for specific requirements available. This decision is deliberately left to the market.

== What is a potential candidate for a ''3rd party product''? ==
Any product that actually interfaces to innovaphone gear may be considered as recommended product. However, as a rule of thumb, we do not list nor test basic network infrastructure devices.

== What has to be done to list a new ''3rd party product''? ==
See [[Howto:Hitchikers Guide to the "3rd Party Product Listing" |the ''hitchikers guide to the 3rd party product'']] for a description of the procedure.

= List of 3rd party products =
The list is structured in various categories. Please note that a single product may appear in more than one category. As an example, application suites including both CTI and Call Center functions are quite popular.

== 3rd Party PBX ==
[[:Category:3rdParty PBX|List of articles in ''{{Category:3rdParty PBX}}'']]

== Alarm server Products ==
[[:Category:3rdParty_Alarm_Server|List of articles in ''{{Category:3rdParty_Alarm_Server}}'']]

== Billing System / Call Management ==
[[:Category:3rdParty Billing System / Call Management|List of articles in ''{{Category:3rdParty Billing System / Call Management}}'']]

== CTI and UMS applications ==
[[:Category:3rdParty CTI and UMS applications|List of articles in ''{{Category:3rdParty CTI and UMS applications}}'']]

== Call Center Applications ==
[[:Category:3rdParty Call Center Applications|List of articles in ''{{Category:3rdParty Call Center Applications}}'']]

== Gateways ==
[[:Category:3rdParty Gateways|List of articles in ''{{Category:3rdParty Gateways}}'']]

== H.323 and SIP Terminals ==
[[:Category:3rdParty Terminals|List of articles in ''{{Category:3rdParty Terminals}}'']]

== Headsets ==
[[:Category:3rdParty Headsets|List of articles in ''{{Category:3rdParty Headsets}}'']]

== Hospitality / Care ==
[[:Category:3rdParty Hospitality / Care|List of articles in ''{{Category:3rdParty Hospitality / Care}}'']]

== IP Voice Conferencing Systems ==
[[:Category:3rdParty IP Voice Conferencing Systems|List of articles in ''{{Category:3rdParty IP Voice Conferencing Systems}}'']]

== Music on Hold Solutions ==
[[:Category:3rdParty Music on Hold Solutions|List of articles in ''{{Category:3rdParty Music on Hold Solutions}}'']]

== Network Infrastructure Products ==
[[:Category:3rdParty Network Infrastructure Products|List of articles in ''{{Category:3rdParty Network Infrastructure Products}}'']]

== Network Management and Assessment Tools ==
[[:Category:3rdParty Network Management and Assessment Tools|List of articles in ''{{Category:3rdParty Network Management and Assessment Tools}}'']]

== Network Security Appliances ==
[[:Category:3rdParty Network Security Appliances|List of articles in ''{{Category:3rdParty Network Security Appliances}}'']]

== Professional Announcements ==
[[:Category:3rdParty Professional Announcements|List of articles in ''{{Category:3rdParty Professional Announcements}}'']]

== SIP Provider ==
[[:Category:3rdParty SIP Provider|List of articles in ''{{Category:3rdParty SIP Provider}}'']]

== Solutions for Mobile Extensions ==
[[:Category:3rdParty Solutions for Mobile Extensions|List of articles in ''{{Category:3rdParty Solutions for Mobile Extensions}}'']]

== Voice Recording ==
[[:Category:3rdParty Voice Recording|List of articles in ''{{Category:3rdParty Voice Recording}}'']]

== 3rdParty Wireless System ==
[[:Category:3rdParty_Wireless_System|List of articles in ''{{Category:3rdParty_Wireless_System}}'']]

=List of all 3rd Party Products=
[[:Category:3rd Party Products]]

=List of all tested Products=
[[:Category:Compat]]

Howto:Checkliste VoIP

2009-03-13T12:07:40Z

Ptr:

[[Image:Checkliste VoIP Reseller.pdf|Checkliste VoIP Reseller]]

[[Image:Checklist_VoIP_eng.pdf|Checklist VoIP engl]]

=='''Content'''==

The Checklist VoIP will be useful to all Resellers to receive the information needed from the customer. Project based information is crucial for creating a customized and complete tender.

The checklist consists of 4 categories:

□ Customer Analysis

□ Your Targets and Requests

□ General Company Information

□ IT / Network technology

Good Luck!





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

Howto:Checkliste VoIP

2009-03-13T11:51:57Z

Ptr:

[[Image:Checkliste VoIP Reseller.pdf|Checkliste VoIP Reseller]]

[[Image:Checklist_VoIP_eng.pdf|Checklist VoIP engl]]

=='''Inhalt und Nutzen'''==

Die Checkliste VoIP soll innovaphone Resellern als nützliches Instrument zur Informationserhebung beim Kunden dienen. Im Idealfall beinhaltet sie sämtliche projektrelevanten Informationen, um daraus zeitnah ein vollständiges und maßgeschneidertes Angebot erstellen und vorlegen zu können.

Die Checkliste VoIP unterteilt sich in folgende Sektionen:

□ Kundenanalyse

□ Ihre Ziele und Wünsche

□ Allgemeine Firmeninformationen

□ EDV/Netzwerktechnik

Vielen Erfolg!





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

Howto:Checkliste VoIP

2009-03-13T11:51:36Z

Ptr:

[[Image:Checkliste VoIP Reseller.pdf|Checkliste VoIP Reseller]]
[[Image:Checklist_VoIP_eng.pdf|Checklist VoIP engl]]

=='''Inhalt und Nutzen'''==

Die Checkliste VoIP soll innovaphone Resellern als nützliches Instrument zur Informationserhebung beim Kunden dienen. Im Idealfall beinhaltet sie sämtliche projektrelevanten Informationen, um daraus zeitnah ein vollständiges und maßgeschneidertes Angebot erstellen und vorlegen zu können.

Die Checkliste VoIP unterteilt sich in folgende Sektionen:

□ Kundenanalyse

□ Ihre Ziele und Wünsche

□ Allgemeine Firmeninformationen

□ EDV/Netzwerktechnik

Vielen Erfolg!





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

File:Checklist VoIP eng.pdf

2009-03-13T11:46:16Z

Ptr:

Howto:Checkliste VoIP

2009-03-13T11:14:14Z

Ptr:

[[Image:Checkliste VoIP Reseller.pdf|Checkliste VoIP Reseller]]

=='''Inhalt und Nutzen'''==

Die Checkliste VoIP soll innovaphone Resellern als nützliches Instrument zur Informationserhebung beim Kunden dienen. Im Idealfall beinhaltet sie sämtliche projektrelevanten Informationen, um daraus zeitnah ein vollständiges und maßgeschneidertes Angebot erstellen und vorlegen zu können.

Die Checkliste VoIP unterteilt sich in folgende Sektionen:

□ Kundenanalyse

□ Ihre Ziele und Wünsche

□ Allgemeine Firmeninformationen

□ EDV/Netzwerktechnik

Vielen Erfolg!





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

Howto:Checkliste VoIP

2009-03-13T11:07:20Z

Ptr: /* '''Inhalt und Nutzen''' */

[[Image:Checkliste VoIP Reseller.pdf|Checkliste VoIP Reseller]]

=='''Inhalt und Nutzen'''==

Die Checkliste VoIP soll innovaphone Resellern als nützliches Instrument zur Informationserhebung beim Kunden dienen. Im Idealfall beinhaltet sie sämtliche projektrelevanten Informationen, um daraus zeitnah ein vollständiges und maßgeschneidertes Angebot erstellen und vorlegen zu können.

Die Checkliste VoIP unterteilt sich in folgende Sektionen:

□ Kundenanalyse

□ Ihre Ziele und Wünsche

□ Allgemeine Firmeninformationen

□ EDV/Netzwerktechnik

Vielen Erfolg!





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

Howto:Checkliste VoIP

2009-03-13T11:06:35Z

Ptr:

[[Image:Checkliste VoIP Reseller.pdf|Checkliste VoIP Reseller]]

=='''Inhalt und Nutzen'''==

Die Checkliste VoIP soll innovaphone Resellern als nützliches Instrument zur Informationserhebung beim Kunden dienen. Im Idealfall beinhaltet sie sämtliche projektrelevanten Informationen, um daraus zeitnah ein vollständiges und maßgeschneidertes Angebot erstellen und vorlegen zu können.

Die Checkliste VoIP unterteilt sich in folgende Sektionen:

□ Kundenanalyse

□ Ihre Ziele und Wünsche

□ Allgemeine Firmeninformationen

□ EDV/Netzwerktechnik

Vielen Erfolg!





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