https://wiki.innovaphone.com/api.php?action=feedcontributions&feedformat=atom&user=Twlinnovaphone wiki - User contributions [en]2026-05-09T07:55:23ZUser contributionsMediaWiki 1.42.3https://wiki.innovaphone.com/index.php?title=Howto13r2:Step-by-Step_Create_notifications_for_a_group_voicemail&diff=78002Howto13r2:Step-by-Step Create notifications for a group voicemail2025-10-02T10:43:19Z<p>Twl: </p>
<hr />
<div><!-- Keywords: Voicemail, MWI, Function key, step-by-step, easy, E-Mail--><br />
[[Category:Step-by-Step|Voicemail, MWI Function Key, Badge Count, E-Mail]]<br />
<br />
{{HOWTOMOD13r3 Translation Info}}<br />
<br />
This article explains how to set up a group voicemail. New voicemail notifications should be received via email and badge count information. It also explains an MWI feature key on a desk phone. This feature key flashes as well when a new voicemail is received for that voicemail group.<br />
<br />
[[Image:Create-a-mwi-key-overview.png]]<br />
<br />
== Purpose ==<br />
A common requirement is a voicemail box for a group of users. All users of this group should be notified of a new voicemail so no message is missed.<br />
<br />
=== Features ===<br />
* Notification of a new voicemail by a flashing MWI key<br />
* Notification of a new voicemail via the voicemail apps (myApps) badge count<br />
* Notification of a new voicemail by E-Mail<br />
<br />
=== Limitations ===<br />
== Requirements ==<br />
* Innovaphone PBX<br />
* Innovaphone myApps client<br />
* A voicemail license is needed for the group voicemail object (no voicemail license for the user is required)<br />
<br />
== Things to know before you begin ==<br />
* Name and number of the group voicemail object<br />
* Name (SIPid) of each member of the voicemail group<br />
* Value of the 'Custom'-flag of the voicemail object<br />
<br />
== Configuration ==<br />
<br />
In this scenario we have the following task to configure:<br />
* User lsv, mro and vgr should receive notifications of new voicemails via a badge count in their voicemail app, via MWI function key and E-mail<br />
* The name of the voicemail group will be ''group-vm''<br />
* The number of the voicemail group will be ''89''<br />
<br />
===PBX Manager ===<br />
Open your PBX Manager and select your voicemail plugin. Since we want to add a voicemail group we will select a voicemail group app<br />
<br />
[[Image:Create-a-mwi-key-1.png]]<br />
<br />
We are going to configure the following options<br />
<br />
* Name: The name is the name of the app and displayed to all users in their myApps client. In our case we will call it ''group-vm''<br />
* sip: This name is only used for internal purposes. It is important not to use any space in this name. In our case we will call it ''group-vm''<br />
* Number: Please choose any free number in your dial plan. In our scenario we will configure the ''89'' because this will be the number of the voicemail group.<br />
* PBX: Select the PBX, the voicemail object should be located at.<br />
* Node: Select the Node of a voicemail object. Please use ''root'' in a flat numbering plan.<br />
* email notifications: In case you want to receive the voicemail as e-mail as well, this option has to be enabled.<br />
* custom: Same value as the custom-flag of the voicemail-object.<br />
* MWI users: Please configure the name (SIPid) of every user of this voicemail group. Users should be separated by a comma.<br />
<br />
[[Image:Create-a-mwi-key-2.png]]<br />
<br />
Afterwards press OK.<br />
<br />
Every user of the group should have the voicemail app. Please use a config template to assign the app to every user of the group.<br />
<br />
[[Image:Create-a-mwi-key-3.png]]<br />
<br />
Please go to the advanced UI of your PBX and go to PBX/Objects and click show. Now search for the same config Template you just used to assign the app but this time open the phone config of this template.<br />
<br />
[[Image:Create-a-mwi-key-4.png]]<br />
<br />
Select ''Function-Keys'' on the left bar. To create a function we have to select a position on the phone. If we choose 1, the first position on the top left is used for this function key. As Type for the key we will select ''Message Waiting''. Then we click on ''Add''.<br />
<br />
[[Image:Create-a-mwi-key-5.png]]<br />
<br />
* We can specify an idle text and an active text, which will be displayed in their respective states. <br />
* As number we will configure the number of the group voicemail '''twice'''. In our case the group voicemail has the number ''89'', so we will configure ''8989''. Do '''not''' set ''Append Own Number''.<br />
* We have to set the name to the name of our group voicemail which is ''group-vm'' in our case.<br />
<br />
[[Image:Create-a-mwi-key-6.png]]<br />
<br />
To receive mails as well we need to edit the group voicemail object in the advanced UI. <br />
<br>This means we have to search for the object ''group-vm'' and edit the object's email settings. <br />
<br>If you only check the box next to the email text, the email address of this object will consist of the name(sipID) of the group voicemail as the user part and the system name as the domain part. <br />
<br>Of course you can also configure an arbitrary E-mail address in the text field next to it. <br />
<br>We recommend to configure a E-mail address of a distribution group. <br />
<br>'''Do not''' remove the Voicemail-license checkmark which is mandatory and set by PBXManager plugin!<br />
<br />
[[Image:Create-a-mwi-mail1.png]]<br />
<br />
In most cases, the last step can be skipped, since you probably already set up an SMTP connection to your mail server during the Install. If you are not sure whether you have done that, please go to PBX/Configuration/Authentication in your advanced UI and configure the following parameters.<br />
<br />
* SMTP Server: The IP address or DNS Name of the SMTP Server<br />
* Sender name: This name is used as sender name of the E-mails<br />
* Email address: The email address for sending mails<br />
* Username: The username of the email account to authenticate at the mail server<br />
* Password: The password of the email account to authenticate at the mail server<br />
<br />
[[Image:Create-a-mwi-mail2.png]]<br />
<br />
== Verification ==<br />
Create a call forwarding on one of your users to ''8989'' and call this user. Due to the call forwarding the call will be redirected to the group voice box. The Badge count of your group voicemail will increase, all users will receive an E-Mail and the MWI key on all phones will be blinking.<br />
<br />
== Known issues ==<br />
* Do not configure a space in the SIPid of the group voicemail.<br />
* A UC-license can not be applied to a group voicemail object. A single voicemail license is needed. This [[ReleaseNotes13r3:Firmware#152640_-_Voicemail_object:_Config_option_for_UC,_Voicemail_and_Reporting_licenses_was_lost|was fixed in 13r3sr10]].<br />
<br />
== Related Articles ==<br />
* [[Howto:Group_Voicemail]]<br />
* [[Courseware:IT_Connect_-_09.1_Even_more_Apps#The_Voicemail_App|iT Connect - The Voicemail App]]<br />
* [https://www.innovaphone.com/en/services/licenses/feature-licenses.html#voicemail Voicemail Licensing]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference15r1:Concept_App_Service_TechAssist&diff=73782Reference15r1:Concept App Service TechAssist2024-10-17T11:40:27Z<p>Twl: /* Internal Timers */</p>
<hr />
<div><br />
[[Category:Concept|Apps]]<br />
[[Category:Concept App Service TechAssist]]<br />
<!-- techassist, ticket, analyze, debug, tests --><br />
== Applies To == <br />
<br />
* innovaphone PBX from version 13r2<br />
<br />
== Overview ==<br />
The idea of the TechAssist app is to provide helpful tools for technicians, as well as to analyze static and runtime information of a system and check for problems and improvements. In this way, the app can help you find and solve problems and misconfigurations independently and quickly.<br />
For this purpose, the app supports<br />
* the execution of ''tests''<br />
** a bunch of manufacturer tests are supplied with the app<br />
** you can create and save your own tests<br />
** testresults can be downloaded to attach them to a support ticket<br />
* a PBX license overview<br />
<br />
== Licensing ==<br />
There are no licenses needed for this app<br />
<br />
== Installation ==<br />
The TechAssist App is installed by default for every new installation and is accessible from the Config Admin template.<br />
<br />
=== With the PBX manager AP app installer plug-in === <br />
[[File:Ap_app_installer.png]]<br />
<br />
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''<br />
* In the search field located on the top right corner of the store, search for '''"Techassist"''' and click on it<br />
* Select the proper firmware version, here '''"v14"''' and click on install<br />
* Tick "I accept the terms of use" and continue by clicking on the install yellow button<br />
* Wait until the install has been finished<br />
* Close and open the PBX manager to refresh the list of the available colored AP plugin<br />
* Click on the '''"AP techassist"''' and click on '''" + Add an App"'''<br />
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: TechAssist, SIP: techassist''<br />
''Hint : The App needs access-right to one devices-api. The access to "devices-api" will be set automatically. If you want to have another devices-apis working with techassist, you have to configure it manually in the advanced UI.''<br />
* Tick the appropriate template to distribute the App<br />
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good<br />
<br />
== Test Engine ==<br />
=== Overview ===<br />
==== Technical look inside ====<br />
[[File:Concept_TechAssist.png|thumb|upright=1.0|right|Technical Overview]]<br />
The app service receives multiple incoming websocket connections of the app objects from the PBXes. By assigning rights to a to your desired "devices-apis" (in the Apps tab), the app service receives the corresponding rights to connect to the respectively activated DevicesApps. All managed domains and devices can then be read in via this connection. (One TechAssist can only connect with one device-api)<br />
With this procedure, you can work with one DevicesApp instance and across all domains and devices in it.<br />
<br />
==== Submodules ====<br />
The app contains various sub-modules in order to be able to carry out the tests provided by the manufacturer and also to be able to integrate custom tests created by yourself.<br />
<br />
;scheduler<br />
: The scheduler initially loads all tests and performs a plausibility check of the individual tests. From this status onwards, the scheduler ensures that all tests are executed in the required time intervals.<br />
: Inside the Scheduler the tick is 5000 milliseconds, and test are executed sequentially to prevent high system load<br />
;cmd<br />
: The cmd submodule (derived from "command") can communicate with devices in the installation to query a status, the config or similar. The submodule takes care of all the information that tests from an installation want to have, consolidates them so that queries do not have to be executed multiple times and caches the results.<br />
;test<br />
: The test submodule is instantiated per test and provides all necessary functionalities within a test.<br />
<br />
==== UI Language ====<br />
By design, only the app itself is available in multiple languages. The content of the tests and technical output is intentionally only available in english.<br />
<br />
==== Tests ====<br />
The app contains a bunch of embedded test, but it is also possible to create and save your own tests.<br />
<br />
=== UI ===<br />
==== Expert Mode ====<br />
By default there are some expert information hidden in the left menu bar. You will find a switch for that in the left menu (non-mobile-view) to enable all menu items.<br />
<br />
==== Dealing with the Code Editor ====<br />
The Code Editor is a tool for viewing the tests supplied and writing your own tests based on these tests.<br />
<br />
The editor is divided into 3 basic areas.<br />
;Left - Code Editor<br />
:This is the code editor where you can write your test code in the browser. When you close the app, the content in the editor is saved, so that the next time you open the app you will find your old code again.<br />
<br />
;Top right - Menu bar<br />
:Here you will find the following functions:<br />
:Selection of all existing Tests (predefined vendor Tests and your own custom Tests)<br />
:Load the source code of the selected Test to the code editor<br />
:Delete the selected test from the app (This is only possible for custom tests)<br />
:Execute the source code (with or without cached commands in the service) in the Code Editor and show the result<br />
:Clear the Code Editor<br />
:Save the current Content from the code Editor as Test<br />
::The title of your test is divided from the ''title'' property in your test (lower based without non-alphanumeric characters). This means: If you save another Test with the same ''title'' the value will be saved in the other test.<br />
<br />
;Top right - Results<br />
:If you execute, save or delete a test you will get the response/results in this area<br />
<br />
=== Create your own Testscript ===<br />
You can create your own Test scripts in a JavaScript based environment.<br />
A test itself is a JavaScript object with some configurations properties and a section of ''freestyle'' code to use JavaScript habits to perform your test. If your test will be executed, an above layer will call your ''test()'' method and want to have a return object with your result.<br />
<br />
There already exists a global Object called '''tests_add'''. You can add your own Test as Property to this existing Object like:<br />
<syntaxhighlight lang="javascript"><br />
tests_add.my_new_test = tests_add.my_new_test || {<br />
title: 'Check for xyz',<br />
// configuration properties<br />
<br />
test: function (cmd, result, storage) {<br />
// your custom test code<br />
<br />
return {<br />
success: false,<br />
msg: '....'<br />
};<br />
}<br />
} <br />
</syntaxhighlight><br />
<br />
The way to add a test with <code>tests_add.my_new_test = tests_add.my_new_test || {}</code> is important so that two tests do not overwrite each other. Please also pay attention to this. In this example, we have a ''logical condition'' in the first line. If the test ''my_new_test'' already exists in the object ''tests_add'' the left side from the ''OR-condition'' is ''true'', and the existing test takes place. Otherwise, it is ''false'' and the right side (your new test object) will be written to ''tests_add.my_new_test''.<br />
<br />
==== Configuration Properties ====<br />
You must configure certain properties in your test so that the scheduler knows exactly how to handle your test.<br />
<br />
Example:<br />
<syntaxhighlight lang="javascript"><br />
tests_add.my_new_test = tests_add.my_new_test || {<br />
title: 'Unknown / New devices',<br />
description: 'Check for unassigned devices in your installation',<br />
todo: 'Please check the unknown devices in your installation and acceppt or delete the devices',<br />
author: 'slu@innovaphone.com',<br />
enabled: true,<br />
schedule: '1h',<br />
commands: { ... },<br />
<br />
test: function (cmd, result, storage) {<br />
// your custom test code<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
===== Mandatory properties =====<br />
<br />
; title<br />
: string | The title of your test, which is displayed in the UI<br />
; description<br />
: string | A short description of your test, which is displayed in the UI<br />
; todo<br />
: string | An instruction on what the user has to do if the check fails. It will be displayed above the logfile in failed tests. (You can use ''\r\n'' for line breaks)<br />
: Variable <nowiki>{{VERSION}}</nowiki> will be replaced to current Version of the app like "14r1"<br />
; author<br />
: string | The contact of the person who create the test<br />
; schedule<br />
: string | The time interval during which the test is to be carried out independently. The format is composed of a numerical value and interval value. This allows you to create combinations such as <code>5m (every 5 minutes), 10h (every 10 hours) or 1d (every day) </code>. A special case which is also allowed is the value ''none''. With a ''none'' value, your test will not be executed automatically, but is available in the app. So the user is able to execute your test manually.<br />
: Possible interval values are:<br />
: <code>s</code> (seconds)<br />
: <code>m</code> (minutes)<br />
: <code>h</code> (hours)<br />
: <code>d</code> (days)<br />
: <code>w</code> (weeks)<br />
: Please note that each execution of a test requires resources. For example, if you create a test with ''1m'' that is executed every minute, you may well create an unpleasant impact! The system automatically checks the execution time of your test against your specified interval. If your test runs for a longer time than your schedule, your ''schedule'' parameter is automatically doubled by the system.<br />
: Please note the [[#Submodules|Submodule Scheduler]] with Tick and synchronous execution. For example, it is not possible to execute a test every second.<br />
<br />
===== Optional properties =====<br />
<br />
; commands<br />
: object | An object in which you can list all the commands, values, etc. that you want to use later in your test. As soon as your test() method is called, the returns of these commands are passed in as parameters so that you can analyze them. For detailed documentation, please see the [[#Property_.22commands.22|commands-documentation]] below.<br />
; minBuild<br />
: int | The minimum build version of the app, that the Test will be executed.<br />
; oneTime<br />
: bool | If ''true'' the test will be self-deactivated after the first successful execution.<br />
; enabled<br />
: bool | If ''false'' the test will be loaded but not executed. The user will see the test in the list of test, and it is possible to enable it (default: ''true'')<br />
; hidden<br />
: bool | If ''true'' the test will be skipped by the system and will not be loaded (default: ''false'')<br />
<br />
==== Property "commands" ====<br />
The property ''commands'' is an object where you can define innovaphone specific commands that are executed before your test will be executed. The results of the given commands will be passed to your test in the parameter ''results''. Think about that, all your commands will be cached until the ''schedule'' timeout is exceeded. This means that you will only get a new result of the command after the schedule time has elapsed in relation to the time of your last execution. The only exceptions is when the user manually re-executes a test via the UI or caching has been explicitly disabled at the command<br />
<br />
You have to consider a special nested notation when creating your commands, so that you can use them later.<br />
<br />
===== outer commands-object =====<br />
Let's start with some first basic rules:<br />
* ''commands'' is an object with one property per command. At this moment we only list commands, we don't take care about specific devices, types of models or so on.<br />
* Every child-property (let's call it "command-object") is a new object which contains all needed information for this specific command<br />
* The title of the property "command-object" is defined by yourself<br />
** Spoiler: The title of your "command-object" should be used later if you want to read the result for a specific device<br />
* You can list multiple "command-objects"<br />
<br />
Up to here we have the following and can define it like this:<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
my_command_one: {},<br />
my_command_two: {},<br />
},<br />
</syntaxhighlight><br />
<br />
===== single command-object =====<br />
<br />
Then we have some new rules per "command-object":<br />
* A property called ''cmd'' is expected. This property contains the real command which shall be executed (Remember, at this moment we only list commands, we don't take care about specific devices, types of models or so on)<br />
** Example 1: <code>cmd: 'CMD0/box_info.xml'</code> will give you the xml output of the general overview page<br />
** Example 2: <code>cmd: '!mod cmd CDR0 qs'</code> will give you the amount of buffered CDRs in the CDR0 interface<br />
** Example 3: <code>cmd: 'cfg.txt'</code> will give you back the full configuration file<br />
** If you are already firm with the innovaphone based command syntax, you will see that you can use any HTTP command which can be sent to an innovaphone device<br />
* Some more properties can be defined optionally. See documentation below<br />
<br />
Up to here we have an idea of a specific "command-object" and can do the following now:<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
buffered_cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
},<br />
buffered_cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
With this command, we can collect the "buffered CDRs" on both CDR Interfaces in our boxes. Maybe you see it directly... This will not make really sense in a real setup because CDRs only generated by Gateways/PBXes. So we don't need to bother phones with these requests.<br />
So from now on we take care about our defined command. There are optional parameters that we can also list inside a "command-object" to let the system know what is the to-do with this command.<br />
<br />
;cmd<br />
: string | Any HTTP command you can send to an innovaphone device. There is a limit of 15 seconds for every http request. If your request exceeds this limit the request will be cancelled.<br />
;cat<br />
: array | An optional list of device types on which the command is to be executed. If ''cat'' is empty, it means all devices in your installation.<br />
: You can define the following device categories:<br />
: <code>pbx</code> - all PBXes<br />
: <code>gw</code> - all Gateways<br />
: <code>ap</code> - all App Platforms<br />
: <code>dect</code> - all Dect Gateways<br />
: <code>phone</code> - all Phones<br />
: <code>monitoring</code> - all categories based on Monitoring settings<br />
;cache<br />
: bool | If you set it to ''false'' you will never get a cached value. Please use this option wisely and only if you really need it. (default: ''true'')<br />
<br />
Now let's improve our example from above and get the bufferd CDRx information only from pbxes and gateways.<br />
<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
buffered_cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
cat: ['pbx', 'gw'],<br />
},<br />
buffered_cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
cat: ['pbx', 'gw'],<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
===== execution and results of commands =====<br />
Up to now, we have only defined commands that are to be executed on certain devices. When your test is executed, the previously defined commands are executed and the system collects the returns in a corresponding object (called <code>results</code>) which is passed into your <code>test(cmd, results)</code> method. There you can access the results and do whatever you want to test/analyze or whatever with the return value. You will find an example and some sample-code how to use the results-object in the description of the ''test() method''<br />
<br />
===== nested commands-objects =====<br />
You can now send any commands and the results will be returned to you for evaluation.<br />
As you may have already noticed, there is no possibility to place multiple commands in dependency. But this is the way to do this.<br />
<br />
For more complicated tests, it is necessary to execute several commands one after the other and to generate following commands dynamically on the basis of the result of the first command.<br />
<br />
For such tests, there is the possibility to specify an object "commands" within a "command-object". From this level, you can define a dynamic function in which you can apply your own code based on the first result, and then return a new ''commands-object''. In this return statement, you also have the option of returning another dynamic function in order to be able to create processes of any complexity. Please note that if you not return an ''object'' your return value will be discarded. The results of your nested ''command-objects'' will be passed to the ''test()'' method inside the ''results'' object.<br />
<br />
This is certainly not easy to understand. Therefore, let us take a closer look at it with an example.<br />
<br />
====== example: nested commands-object which generates the second command from the first result ======<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
certificates: {<br />
cmd: 'X509/mod_cmd.xml',<br />
cat: ['pbx', 'gw', 'dect'],<br />
commands: function(cmd, result) {<br />
// free style code to build the following commands<br />
var xml = cmd.parse_xml(result);<br />
//log(JSON.stringify(xml));<br />
<br />
var fingerprint;<br />
// get the fingerprint for single cert<br />
if (typeof xml.info.servercert.certificate['@fingerprint'] !== 'undefined') {<br />
fingerprint = xml.info.servercert.certificate['@fingerprint']<br />
}<br />
// use last certificates in case of multiple<br />
else {<br />
fingerprint = xml.info.servercert.certificate[xml.info.servercert.certificate.length - 1]['@fingerprint'];<br />
}<br />
cmd.log('Fingerprint: '+fingerprint);<br />
<br />
return {<br />
certificate: {<br />
cmd: 'X509/mod_cmd.xml?cmd=servercert-details&fingerprint='+fingerprint,<br />
}<br />
}<br />
}<br />
}<br />
},<br />
</syntaxhighlight><br />
<br />
Our goal is to check which key-length is used in the device certificate. But there i no direct command to get this information. So we have to do it in multipe steps.<br />
<br />
In this sample, we request the following in the commands object:<br />
# Execute our command "certificates" on devices (pbx, gw, dect) the command "X509/mod_cmd.xml" which will give you back the xml payload of the page [[{{NAMESPACE}}:General/Certificates]]<br />
# If the first request is done, the nested "commands" object should be called and we get the result from the first command<br />
## Now, inside the function <code>commands: function(cmd, result) {</code> we can use some free-style code to to what we need, to build a following command<br />
## Here we convert xml to an object and extract the certificate fingerprint from the result of the first request<br />
## then we return an object with "command-objects"<br />
### think about that is possible to add an new <code>commands: function(cmd, result) {</code> inside the return to add a new level :-)<br />
## this second command will be executed to for every device and the xml payload contains the device certifcate of the current device. (like the popup in the UI if you click on a specific certificate)<br />
#If all nested commands are processed, then your test() will be called, and you get all the results (in this case "certificates" and "certificate") in the results-object<br />
<br />
====== example: nested commands-object which generates various commands from the first result ======<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
config: {<br />
cmd: 'cfg.txt',<br />
cat: ['pbx'],<br />
commands: function(cmd, result) {<br />
var lines = result.split("\r\n");<br />
var output = {};<br />
<br />
// get pbx loc<br />
var loc = false;<br />
for (var l = 0; l < lines.length; l++) {<br />
if (!lines[l].startsWith('config change PBX0')) continue; // skip non pbx line<br />
if (lines[l].includes('/mode standby')) continue; // skip slave pbxes<br />
<br />
var match = lines[l].match(/config change PBX0 (.*) \/loc ([^ ][^/]+)/);<br />
loc = match[2].substr(0, match[2].length-1);<br />
l = lines.length;<br />
}<br />
cmd.log('use pbx loc: '+loc);<br />
<br />
// get user objects<br />
var regex = new RegExp('/\(loc='+loc+'\)(.*)\(guid;bin=([0-9A-Za-z]+)\)/');<br />
for (var l = 0; l < lines.length; l++) {<br />
// skip if user is not from this pbx<br />
if (!lines[l].includes('(loc='+loc+')')) continue;<br />
<br />
var match = lines[l].match(/\(guid;bin=([0-9A-Za-z]+)\)/);<br />
if (!match) continue;<br />
cmd.log('user found: '+match[1]);<br />
output[match[1]] = {cmd: 'PBX0/ADMIN/mod_cmd_login.xml?cmd=show&user-guid='+match[1]};<br />
}<br />
<br />
return output;<br />
}<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
Our goal is to get the xml output from the advanced ui for every pbx object. But there i no direct command to get this information. So we have to do it in multipe steps.<br />
<br />
In this sample, we request the following in the commands object:<br />
# Execute our command "config" on PBXes the get the plain configuration file<br />
# If the first request is done, the nested "commands" object should be called, and we get the result from the first command<br />
## Now, inside the function <code>commands: function(cmd, result) {</code> we can use some free-style code to do what we need, to build multiple following commands<br />
<br />
## Here we split the config file by lines breaks and iterate the whole config<br />
## then we generate an empty return object to fill it later<br />
### think about that is possible to add an new <code>commands: function(cmd, result) {</code> inside the return to add a new level :-)<br />
## If we have checked the pbx and the userobject we add with <code>output[match[1]] = {cmd: 'PBX0/ADMIN/mod_cmd_login.xml?cmd=show&user-guid='+match[1]};</code> a specific command to the retunr value<br />
<br />
In the end, we have a big return object with multiple cmd's<br />
In this case we will get all the results in the test() later and can do further stuff with the results.<br />
<br />
==== Executable method test() ====<br />
The upper layer expects a method <code>test(cmd, results, storage)</code> in your JavaScript object. This method has three parameters.<br />
<br />
;cmd<br />
:An object that offers you a wide range of predefined functions and options. You can see it as a kind of library, which is documented at the [[#cmd object|cmd object]].<br />
<br />
;results<br />
:An object of the results of your commands from the given ''command-objects'' in your test definition.<br />
<spoiler show="show sample strcuture of the results object" hide="hide sample strcuture of the results object"><br />
<syntaxhighlight lang="javascript"><br />
// structure of results object<br />
{<br />
// your command is the property<br />
'buffered_cdr0' : {<br />
// the unique id of the device is the property<br />
'1': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
'4': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
},<br />
'buffered_cdr1' : {<br />
// the unique id of the device is the property<br />
'1': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
'4': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<spoiler show="show best practice code to deal with the results object" hide="hide best practice code to deal with the results object"><br />
<syntaxhighlight lang="javascript"><br />
// you can use this inside your function "test: function (cmd, results, storage)" to iterate all commands over all affected devices<br />
<br />
Object.keys(results).forEach(function(command) {<br />
log.push('command: '+command);<br />
Object.keys(results[command]).forEach(function(device) {<br />
log.push('device: '+device);<br />
var output = results[command][device];<br />
});<br />
});<br />
<br />
// expected log array from the code above:<br />
// $ command: buffered_cdr0<br />
// $ device: 1<br />
// $ device: 4<br />
// $ command: buffered_cdr1<br />
// $ device: 1<br />
// $ device: 4<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<br />
;storage<br />
:If the test has written something to the test memory during the last execution, you will get the last value back here. (Note that the storage is not available for one-time tests in the code editor. There you will always get an empty storage)<br />
<br />
===== return test result =====<br />
Your test has to be return an object with your test result. The system expect an object with the following properties.<br />
<br />
; success<br />
: boolean | indicates if your test was successful or not<br />
; msg<br />
: string | an optional short message that will be displayed in the UI as preview<br />
; log<br />
: array | an optional array with lines of logfile that you can use to display detailed information in the UI at your test result. Use <code>log.push()</code> to fill up the logfile array. In the frontend, the log will be parsed and mac addresses <code>/(^|\W)([a-f0-9]{12})(\W|$)/i</code> will be updated with an internal link to devices app. (If you want to create instead debug output to the app-instance logfile you can use <code>cmd.log()</code>)<br />
;storage<br />
: string | an optional string, which can be json or similar, that is stored for this test. The next time the test is executed, the payload saved here is available inside the test again.<br />
<br />
<syntaxhighlight lang="javascript"><br />
test: function (cmd, results, storage) {<br />
// your stuff<br />
var count = 2;<br />
<br />
return {<br />
success: false,<br />
msg: 'There are '+count+' new/unassigned devices in your setup'<br />
};<br />
}<br />
</syntaxhighlight><br />
<br />
==== The full picture ====<br />
===== Complete sample test to check buffered CDRs =====<br />
<syntaxhighlight lang="javascript"><br />
tests_add.cdrs_buffered = tests_add.cdrs_buffered || {<br />
title: 'Buffered CDRs',<br />
description: 'This test will check if CDRs on a gateway was buffered and are not transmit to the CDR target yet',<br />
todo: 'Check the CDR target',<br />
author: 'slu@innovaphone.com',<br />
enabled: true,<br />
schedule: '10m',<br />
<br />
commands: {<br />
cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
cat: ['gw'],<br />
},<br />
cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
cat: ['gw'],<br />
},<br />
cdr2: {<br />
cmd: '!mod cmd CDR2 qs',<br />
cat: ['gw'],<br />
},<br />
cdr3: {<br />
cmd: '!mod cmd CDR3 qs',<br />
cat: ['gw'],<br />
},<br />
cdr4: {<br />
cmd: '!mod cmd CDR4 qs',<br />
cat: ['gw'],<br />
},<br />
},<br />
<br />
test: function (cmd, results, storage) {<br />
var log = [];<br />
var success = true;<br />
<br />
for (var n = 0; n < 5; n++) {<br />
Object.keys(results['cdr'+n]).forEach(function(i){<br />
var check = calculate_cdrs(results['cdr'+n][i]);<br />
// result was not good, lets create a human error message<br />
if (check !== true) {<br />
log.push(cmd.get_device(i).product+' / '+cmd.get_device(i).hwId+' / '+check+'% - '+results['cdr'+n][i]);<br />
if (success) success = false;<br />
}<br />
});<br />
}<br />
<br />
return {<br />
success: success,<br />
msg: success ? '' : 'Devices with buffered CDRs exists',<br />
log: log<br />
};<br />
<br />
function calculate_cdrs(str) {<br />
// QS messages: 0 max 2000 chars: 0 max 300000<br />
var check = 0;<br />
str = str.split(' ');<br />
// log.push(str);<br />
<br />
var messages_current = str[2];<br />
var messages_max = str[4];<br />
var chars_current = str[6];<br />
var chars_max = str[8];<br />
<br />
// check messages<br />
check = cmd.percent(messages_current, messages_max);<br />
if (check >= 30) return check;<br />
<br />
// check chars<br />
check = cmd.percent(chars_current, chars_max);<br />
if (check >= 30) return check;<br />
<br />
return true;<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
===== Complete sample test to check firmware versions =====<br />
<syntaxhighlight lang="javascript"><br />
tests_add.firmware_version = tests_add.firmware_version || {<br />
title: 'Supported firmware versions',<br />
description: 'Check if you have unsupported firmware version in use',<br />
todo: 'Update the firmware on affected devices',<br />
author: 'slu@innovaphone.com',<br />
schedule: '1d',<br />
commands: {<br />
box_info: {<br />
cmd: 'CMD0/box_info.xml',<br />
},<br />
},<br />
<br />
test: function (cmd, results, storage) {<br />
var log = [];<br />
var success = true;<br />
var msg = '';<br />
<br />
Object.keys(results.box_info).forEach(function(i){<br />
var xml = cmd.parse_xml(results.box_info[i]);<br />
if (typeof xml.info === 'undefined') return;<br />
if (typeof xml.info.sys === 'undefined') return;<br />
if (typeof xml.info.sys['@version'] === 'undefined') return;<br />
<br />
if (<br />
xml.info.sys['@version'].includes('6.00') ||<br />
xml.info.sys['@version'].includes('7.00') ||<br />
xml.info.sys['@version'].includes('8.00') ||<br />
xml.info.sys['@version'].includes('9.00') ||<br />
xml.info.sys['@version'].includes('10.00') ||<br />
xml.info.sys['@version'].includes('11.00') ||<br />
xml.info.sys['@version'].includes('11r1') ||<br />
xml.info.sys['@version'].includes('12r1') ||<br />
xml.info.sys['@version'].includes('13r1')<br />
) {<br />
log.push(cmd.get_device(i).product+' / '+cmd.get_device(i).hwId+' / '+xml.info.sys['@version']);<br />
if (success) success = false;<br />
}<br />
});<br />
<br />
return {<br />
success: success,<br />
msg: success ? '' : 'You use old firmware which is no longer be supported',<br />
log: log<br />
};<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
==== cmd object ====<br />
The '''cmd''' object provides you the following methods:<br />
<br />
<br />
<br />
===== get device information / system information =====<br />
<br />
====== get_domains() : object ======<br />
You will receive all existing domains<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var domains = cmd.get_domains();<br />
console.log(domains);<br />
{<br />
"1": {<br />
"id": 1,<br />
"name": "slu.de",<br />
"deployAdminPasswords": true,<br />
"isInstanceDomain": true,<br />
"categories": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_devices() : object ======<br />
You will receive all existing devices<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var devices = cmd.get_devices();<br />
console.log(devices);<br />
{<br />
"0_009033420623": {<br />
"id": "0_009033420623",<br />
"hwId": "009033420623",<br />
"domainId": 0,<br />
"product": "IP0011",<br />
"version": "13r3 dvl [13.7526/132035/600]",<br />
"type": "GW",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"1": {<br />
"id": 1,<br />
"hwId": "009033420621",<br />
"name": "PBX - pbx.slu.de",<br />
"domainId": 1,<br />
"product": "IP0011",<br />
"version": "13r3 beta4 [13.7688/137623/600]",<br />
"type": "GW",<br />
"pbxActive": true,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"2": {<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_devices_from_domain(int id) : object ======<br />
You will receive all devices which are assigned to the given domain<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var devices = cmd.get_devices_from_domain(1);<br />
console.log(devices);<br />
{<br />
"1": {<br />
"id": 1,<br />
"hwId": "009033420621",<br />
"name": "PBX - pbx.slu.de",<br />
"domainId": 1,<br />
"product": "IP0011",<br />
"version": "13r3 beta4 [13.7688/137623/600]",<br />
"type": "GW",<br />
"pbxActive": true,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"2": {<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_device(int id) : object ======<br />
You will receive a specific device<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var device = cmd.get_device(2);<br />
console.log(device);<br />
{<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== helper functions =====<br />
<br />
====== percent(int value, int total) : float ======<br />
Returns the number of percent of value to total<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var check = cmd.percent(50, 100);<br />
console.log(check);<br />
50<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== parse_xml(string xml, string element = <nowiki>''</nowiki>) : object ======<br />
Returns an object/array representation of given XML string. Note that very large XML inputs cannot be converted directly because there are some restrictions in the duktape environment. If you receive an exception with ''Error: RangeError: regexp executor recursion limit'' you have to define which element do you want to converted (See the second example).<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var json = cmd.parse_xml('<sample><item property_1="value_1" property_2="value_2">content of item</item><item_short prop_1="value_prop_1" /></sample>');<br />
console.log(json);<br />
{<br />
"sample": {<br />
"item": {<br />
"@property_1": "value_1",<br />
"@property_2": "value_2",<br />
"#": "content of item"<br />
},<br />
"item_short": {<br />
"@prop_1": "value_prop_1"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<spoiler show="show sample code with large xml payload" hide="hide sample code with large xml payload"><br />
<syntaxhighlight lang="javascript"><br />
<br />
var xml_registrations_on_big_pbx = '\<br />
<show state="up" time="267993" loc="pbx">\<br />
<attrs></attrs>\<br />
<reg cn="Fax" guid="829a6aeec2a76401c62600155d50c817" h323="fax" pwd="********" pwdx="********" prot="JSON">\<br />
<ep type="gk" addr="172.16.176.205" time="10"/>\<br />
<pseudo-common lics=".reporting."/>\<br />
<pseudo type="fax"/>\<br />
</reg>\<br />
<reg cn="Voicemail de" guid="5ceb0ee7c2a76401bb2600155d50c817" h323="voicemail-de" pwd="********" pwdx="********" prot="JSON">\<br />
<ep type="gk" addr="172.16.176.205" time="10"/>\<br />
<pseudo-common lics=".uc.voicemail.reporting."/>\<br />
<pseudo type="vm"/>\<br />
</reg>\<br />
... and so on ...\<br />
</show>';<br />
var json = cmd.parse_xml(xml_registrations_on_big_pbx, 'reg');<br />
console.log(json);<br />
[<br />
{"@cn":"Fax", "@guid":"829a6aeec2a76401c62600155d50c817", ... "ep":{"@type":"gk","@addr":"172.16.176.205","@time":"10"}, ...},<br />
{"@cn":"Voicemail", "@guid":"5ceb0ee7c2a76401bb2600155d50c817", ... "ep":{"@type":"gk","@addr":"172.16.176.205","@time":"10"}, ...},<br />
...<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== is_supported_version(string version) : object ======<br />
Return if the given Version string is supported according to [[Howto:Supported innovaphone versions]].<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
cmd.is_supported_version('13r3 sr9 [13.7886/1000/0]'); // return "true"<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_version_from_build(int build) : string ======<br />
Return the named version from given build number. (13r3, 14r1 or similar)<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
cmd.get_version_from_build(1410485); // return "14r1"<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== debug =====<br />
<br />
====== log(string message) : void ======<br />
You can write a logfile line to the app debug log<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var domains = cmd.log('my first logfile line');<br />
07-26 07:58:33.179 TechAssist@slu.de (b0728708) | Test "sample_test" | my first logfile line<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
=== Secret knowledge for good tests ===<br />
; bool PBX-Object config attributes<br />
: You will find config attributes like <code>no-subscribe="true"</code> (this is from a Trunk Object) in the config. Please note that if the attribute is ''missing'' or the value is ''false'' it is false, otherwise it is ''true''. For example, the value <code>no-subscribe="on"</code> is also true.<br />
; bool Interface config attributes<br />
: You will find config attributes like <code>/direct-sig on</code> (this is from a SIP interface) in the config. Please note that they are exists bool-attribute which are ''true'' if the attribute is existing. In the case of bool-attribute the following value make no matter. For example, the attribute <code>/direct-sig off</code> is also true.<br />
<br />
== Monitoring ==<br />
The App supports a monitoring interface where well known IT-Monitoring Systems or other Statistics Services can connect and collect various data for the whole innovaphone installation.<br />
<br />
===Requirements===<br />
* Only devices that are known by the ''Devices App'' will be included in the monitoring data<br />
* Only devices that have a non-empty "Name" in the ''Devices App'' will be included in the monitoring data<br />
* For included App statistics, the DNS Name in the App Platform has to be set<br />
* Depending on your external system (to support the automatic host matching magic) it can be needed that all devices has the same ''Name'' in your ''Devices App'' and your external System (Usually the FQDN is used)<br />
<br />
===Configurations===<br />
* In the PBX Manager, you have to configure the credentials for the HTTP authorization to get monitoring data<br />
* In the TechAssist App in the settings area, you can select categories (PBXes, Gateways, AP Platforms, Apps, DECT, Phones) which should be included in the monitoring data<br />
* For all app services that provide statistics, the TechAssist app object must have access rights to these apps (the apps must be checked in the "Apps" tab of the PBX object)<br />
<br />
===Internal Timers===<br />
*All Metrics will be updated every 5 minutes<br />
*App Metrics will be updated every 1 minute<br />
<br />
===Supported Integrations===<br />
We support various output formats over different interfaces. Your System can pull the information and append in the needed Interface/Format to the URL. <code><nowiki>Example: https://apps.slu.de/slu.de/techassist/monitoring/JSON (Here is "JSON" the used interface, see below)</nowiki></code><br />
<br />
If you use an old/legacy system that only support http basic-auth instead of digest-auth you can add a "/basic" to the endpoint url. <code><nowiki>Example: https://</nowiki>apps.slu.de/slu.de/techassist'''/basic'''/monitoring/JSON</code><br />
<br />
==== RAW ====<br />
The interface "/RAW" provides the internal TechAssist format as JSON.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
[<br />
{<br />
"id": "1",<br />
"title": "pbx.baebeca.de",<br />
"metrics": [<br />
{<br />
"id": "online",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "serialnumber",<br />
"value": "005056001338",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "product",<br />
"value": "IPVA",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "version",<br />
"value": "15r1 dvl [15.1.0130/1000/0]",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "versionIsSupported",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "uptime",<br />
"value": 2747,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "CPU",<br />
"value": 1,<br />
"valuePercent": 1,<br />
"comment": null,<br />
"min": 0,<br />
"max": 100<br />
},<br />
{<br />
"id": "CPU-R",<br />
"value": 0,<br />
"valuePercent": 0,<br />
"comment": null,<br />
"min": 0,<br />
"max": 26000<br />
},<br />
{<br />
"id": "MEM",<br />
"value": 46,<br />
"valuePercent": 0.09,<br />
"comment": null,<br />
"min": 0,<br />
"max": 49793<br />
},<br />
{<br />
"id": "ETH0",<br />
"value": 10,<br />
"valuePercent": 0,<br />
"comment": null,<br />
"min": 0,<br />
"max": 1000000<br />
}<br />
]<br />
},<br />
{<br />
"id": "47",<br />
"title": "ap.baebeca.de",<br />
"metrics": [<br />
{<br />
"id": "online",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "serialnumber",<br />
"value": "00155db3c306",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "product",<br />
"value": "AppPlatform x86_64",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "version",<br />
"value": "120010 (15r1 1510130 dvl )",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "versionIsSupported",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
""<br />
]<br />
}<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== CSV ====<br />
The interface "/CSV" provides a simple text based comma separated structure in the format <code><Hostname>;<Metric>;<Value>;<Comment></code>.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
pbx.baebeca.de;"online";1;<br />
pbx.baebeca.de;"serialnumber";005056001338;<br />
pbx.baebeca.de;"product";IPVA;<br />
pbx.baebeca.de;"version";15r1 dvl [15.1.0130/1000/0];<br />
pbx.baebeca.de;"versionIsSupported";1;<br />
pbx.baebeca.de;"uptime";3050;<br />
pbx.baebeca.de;"CPU";2;null<br />
pbx.baebeca.de;"CPU-R";0;null<br />
pbx.baebeca.de;"MEM";0.09;null<br />
pbx.baebeca.de;"ETH0";18;null<br />
ap.baebeca.de;"online";1;<br />
ap.baebeca.de;"serialnumber";00155db3c306;<br />
ap.baebeca.de;"product";AppPlatform x86_64;<br />
ap.baebeca.de;"version";120010 (15r1 1510130 dvl );<br />
ap.baebeca.de;"versionIsSupported";1;<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== JSON ====<br />
The interface "/JSON" provides a JSON formatted structure.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
{<br />
"pbx.baebeca.de": [<br />
{"device":"pbx.baebeca.de","metric":"online","value":1,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"serialnumber","value":005056001338,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"product","value":IPVA,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"version","value":15r1 dvl [15.1.0130/1000/0],"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"versionIsSupported","value":1,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"uptime","value":3050,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"CPU","value":2,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"CPU-R","value":0,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"MEM","value":0.09,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"ETH0","value":18,"comment":"null"}<br />
],<br />
"ap.baebeca.de": [<br />
{"device":"ap.baebeca.de","metric":"online","value":1,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"serialnumber","value":00155db3c306,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"product","value":AppPlatform x86_64,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"version","value":120010 (15r1 1510130 dvl ),"comment":""},<br />
{"device":"ap.baebeca.de","metric":"versionIsSupported","value":1,"comment":""},<br />
]<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== Checkmk ====<br />
The interface "/Checkmk" provides a native integration to your Checkmk system with [https://docs.checkmk.com/latest/en/piggyback.html Piggyback] information for all known hosts.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
<<<<pbx.baebeca.de>>>><br />
<<<check_mk>>><br />
AgentOS: innovaphone TechAssist<br />
Hostname: pbx.baebeca.de<br />
<<<uptime>>><br />
3050<br />
<<<kernel>>><br />
util 0<br />
cpu 1728891356864 0 0 1728891356960 0 0 0 0 0 0<br />
<<<mem>>><br />
MemTotal: 49793 kB<br />
MemFree: 49747 kB<br />
MemAvailable: 49747 kB<br />
Buffers: 0 kB<br />
Cached: 0 kB<br />
SwapTotal: 0 kB<br />
SwapFree: 0 kB<br />
Dirty: 0 kB<br />
Writeback: 0 kB<br />
<<<lnx_thermal>>><br />
<<<local>>><br />
0 "online" - online=1<br />
0 "serialnumber" - serialnumber=005056001338<br />
0 "product" - product=IPVA<br />
0 "version" - version=15r1 dvl [15.1.0130/1000/0]<br />
0 "versionIsSupported" - versionIsSupported=1<br />
0 "CPU-R" - CPU-R=0<br />
0 "ETH0" - ETH0=18<br />
<<<innovaphone>>><br />
<<<<ap.baebeca.de>>>><br />
<<<check_mk>>><br />
AgentOS: innovaphone TechAssist<br />
Hostname: ap.baebeca.de<br />
<<<uptime>>><br />
<<<kernel>>><br />
<<<mem>>><br />
<<<lnx_thermal>>><br />
<<<local>>><br />
0 "online" - online=1<br />
0 "serialnumber" - serialnumber=00155db3c306<br />
0 "product" - product=AppPlatform x86_64<br />
0 "version" - version=120010 (15r1 1510130 dvl )<br />
0 "versionIsSupported" - versionIsSupported=1<br />
<<<innovaphone>>><br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== Configure your Checkmk installation =====<br />
#Setup your Hosts in Checkmk<br />
#*Make sure that "Checkmk agent / API integrations" in the Hostconfiguration of your Application Platform is set to "API integrations if configured, else Checkmk agent", all other Hosts hat to bet set to "No API integrations, no Checkmk agent".<br />
#Create a new Rule for "Individual program call instead of agent access" in "Setup > Agents > Other integrations"<br />
#*Command line to execute: <code>curl --digest -u "user:pass" https://ap.domain.tld/domain.de/techassist/monitoring/Checkmk</code><br />
#*Explicit hosts: Set this to the Host of your Application Platform<br />
<br />
<br />
After that, you can run the service discovery and receive new checks for your devices<br />
<br />
[[File:Checkmk new checks.png|frameless|500px]]<br />
<br />
==== Icinga ====<br />
The interface "/Icinga" provides a native integration to your Icinga system for all known hosts.<br />
<br />
{{FIXME|reason=This interface is currently being researched, and it is being checked whether icinga can read such data as expected}}<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
[<br />
{<br />
"_host": "pbx.baebeca.de",<br />
"_ETH0_ipv4": "10.0.102.7",<br />
"online":1,<br />
"serialnumber":005056001338,<br />
"product":IPVA,<br />
"version":15r1 dvl [15.1.0130/1000/0],<br />
"versionIsSupported":1,<br />
"uptime":3353,<br />
"CPU":1,<br />
"CPU-R":0,<br />
"MEM":0.09,<br />
"ETH0":14<br />
},<br />
{<br />
"_host": "ap.baebeca.de",<br />
"_eth0_ipv4": "10.0.102.8",<br />
"_eth0_ipv6": "2001:4090:e000:9a1::8",<br />
"online":1,<br />
"serialnumber":00155db3c306,<br />
"product":AppPlatform x86_64,<br />
"version":120010 (15r1 1510130 dvl ),<br />
"versionIsSupported":1<br />
}<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== Configure your Icinga installation =====<br />
<br />
== Troubleshooting ==<br />
<br />
=== Startup Logfile ===<br />
If you enable the traceflag ''App'' in your App instance, you will find the following logs:<br />
<br />
AppService::AppStart TechAssist@slu.de<br />
App instance started 14C1363 14C1363<br />
...<br />
// App begins to load embedded tests<br />
JavaScript: Files tests/*<br />
...<br />
// Scheduler begins to load all the tests<br />
scheduler init<br />
init test "firmware_version"<br />
firmware_version: Test added successful<br />
init test "pbx_mediarelay"<br />
pbx_mediarelay: Test added successful</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference15r1:Concept_App_Service_TechAssist&diff=73781Reference15r1:Concept App Service TechAssist2024-10-17T11:17:11Z<p>Twl: /* Configure your Checkmk installation */</p>
<hr />
<div><br />
[[Category:Concept|Apps]]<br />
[[Category:Concept App Service TechAssist]]<br />
<!-- techassist, ticket, analyze, debug, tests --><br />
== Applies To == <br />
<br />
* innovaphone PBX from version 13r2<br />
<br />
== Overview ==<br />
The idea of the TechAssist app is to provide helpful tools for technicians, as well as to analyze static and runtime information of a system and check for problems and improvements. In this way, the app can help you find and solve problems and misconfigurations independently and quickly.<br />
For this purpose, the app supports<br />
* the execution of ''tests''<br />
** a bunch of manufacturer tests are supplied with the app<br />
** you can create and save your own tests<br />
** testresults can be downloaded to attach them to a support ticket<br />
* a PBX license overview<br />
<br />
== Licensing ==<br />
There are no licenses needed for this app<br />
<br />
== Installation ==<br />
The TechAssist App is installed by default for every new installation and is accessible from the Config Admin template.<br />
<br />
=== With the PBX manager AP app installer plug-in === <br />
[[File:Ap_app_installer.png]]<br />
<br />
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''<br />
* In the search field located on the top right corner of the store, search for '''"Techassist"''' and click on it<br />
* Select the proper firmware version, here '''"v14"''' and click on install<br />
* Tick "I accept the terms of use" and continue by clicking on the install yellow button<br />
* Wait until the install has been finished<br />
* Close and open the PBX manager to refresh the list of the available colored AP plugin<br />
* Click on the '''"AP techassist"''' and click on '''" + Add an App"'''<br />
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: TechAssist, SIP: techassist''<br />
''Hint : The App needs access-right to one devices-api. The access to "devices-api" will be set automatically. If you want to have another devices-apis working with techassist, you have to configure it manually in the advanced UI.''<br />
* Tick the appropriate template to distribute the App<br />
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good<br />
<br />
== Test Engine ==<br />
=== Overview ===<br />
==== Technical look inside ====<br />
[[File:Concept_TechAssist.png|thumb|upright=1.0|right|Technical Overview]]<br />
The app service receives multiple incoming websocket connections of the app objects from the PBXes. By assigning rights to a to your desired "devices-apis" (in the Apps tab), the app service receives the corresponding rights to connect to the respectively activated DevicesApps. All managed domains and devices can then be read in via this connection. (One TechAssist can only connect with one device-api)<br />
With this procedure, you can work with one DevicesApp instance and across all domains and devices in it.<br />
<br />
==== Submodules ====<br />
The app contains various sub-modules in order to be able to carry out the tests provided by the manufacturer and also to be able to integrate custom tests created by yourself.<br />
<br />
;scheduler<br />
: The scheduler initially loads all tests and performs a plausibility check of the individual tests. From this status onwards, the scheduler ensures that all tests are executed in the required time intervals.<br />
: Inside the Scheduler the tick is 5000 milliseconds, and test are executed sequentially to prevent high system load<br />
;cmd<br />
: The cmd submodule (derived from "command") can communicate with devices in the installation to query a status, the config or similar. The submodule takes care of all the information that tests from an installation want to have, consolidates them so that queries do not have to be executed multiple times and caches the results.<br />
;test<br />
: The test submodule is instantiated per test and provides all necessary functionalities within a test.<br />
<br />
==== UI Language ====<br />
By design, only the app itself is available in multiple languages. The content of the tests and technical output is intentionally only available in english.<br />
<br />
==== Tests ====<br />
The app contains a bunch of embedded test, but it is also possible to create and save your own tests.<br />
<br />
=== UI ===<br />
==== Expert Mode ====<br />
By default there are some expert information hidden in the left menu bar. You will find a switch for that in the left menu (non-mobile-view) to enable all menu items.<br />
<br />
==== Dealing with the Code Editor ====<br />
The Code Editor is a tool for viewing the tests supplied and writing your own tests based on these tests.<br />
<br />
The editor is divided into 3 basic areas.<br />
;Left - Code Editor<br />
:This is the code editor where you can write your test code in the browser. When you close the app, the content in the editor is saved, so that the next time you open the app you will find your old code again.<br />
<br />
;Top right - Menu bar<br />
:Here you will find the following functions:<br />
:Selection of all existing Tests (predefined vendor Tests and your own custom Tests)<br />
:Load the source code of the selected Test to the code editor<br />
:Delete the selected test from the app (This is only possible for custom tests)<br />
:Execute the source code (with or without cached commands in the service) in the Code Editor and show the result<br />
:Clear the Code Editor<br />
:Save the current Content from the code Editor as Test<br />
::The title of your test is divided from the ''title'' property in your test (lower based without non-alphanumeric characters). This means: If you save another Test with the same ''title'' the value will be saved in the other test.<br />
<br />
;Top right - Results<br />
:If you execute, save or delete a test you will get the response/results in this area<br />
<br />
=== Create your own Testscript ===<br />
You can create your own Test scripts in a JavaScript based environment.<br />
A test itself is a JavaScript object with some configurations properties and a section of ''freestyle'' code to use JavaScript habits to perform your test. If your test will be executed, an above layer will call your ''test()'' method and want to have a return object with your result.<br />
<br />
There already exists a global Object called '''tests_add'''. You can add your own Test as Property to this existing Object like:<br />
<syntaxhighlight lang="javascript"><br />
tests_add.my_new_test = tests_add.my_new_test || {<br />
title: 'Check for xyz',<br />
// configuration properties<br />
<br />
test: function (cmd, result, storage) {<br />
// your custom test code<br />
<br />
return {<br />
success: false,<br />
msg: '....'<br />
};<br />
}<br />
} <br />
</syntaxhighlight><br />
<br />
The way to add a test with <code>tests_add.my_new_test = tests_add.my_new_test || {}</code> is important so that two tests do not overwrite each other. Please also pay attention to this. In this example, we have a ''logical condition'' in the first line. If the test ''my_new_test'' already exists in the object ''tests_add'' the left side from the ''OR-condition'' is ''true'', and the existing test takes place. Otherwise, it is ''false'' and the right side (your new test object) will be written to ''tests_add.my_new_test''.<br />
<br />
==== Configuration Properties ====<br />
You must configure certain properties in your test so that the scheduler knows exactly how to handle your test.<br />
<br />
Example:<br />
<syntaxhighlight lang="javascript"><br />
tests_add.my_new_test = tests_add.my_new_test || {<br />
title: 'Unknown / New devices',<br />
description: 'Check for unassigned devices in your installation',<br />
todo: 'Please check the unknown devices in your installation and acceppt or delete the devices',<br />
author: 'slu@innovaphone.com',<br />
enabled: true,<br />
schedule: '1h',<br />
commands: { ... },<br />
<br />
test: function (cmd, result, storage) {<br />
// your custom test code<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
===== Mandatory properties =====<br />
<br />
; title<br />
: string | The title of your test, which is displayed in the UI<br />
; description<br />
: string | A short description of your test, which is displayed in the UI<br />
; todo<br />
: string | An instruction on what the user has to do if the check fails. It will be displayed above the logfile in failed tests. (You can use ''\r\n'' for line breaks)<br />
: Variable <nowiki>{{VERSION}}</nowiki> will be replaced to current Version of the app like "14r1"<br />
; author<br />
: string | The contact of the person who create the test<br />
; schedule<br />
: string | The time interval during which the test is to be carried out independently. The format is composed of a numerical value and interval value. This allows you to create combinations such as <code>5m (every 5 minutes), 10h (every 10 hours) or 1d (every day) </code>. A special case which is also allowed is the value ''none''. With a ''none'' value, your test will not be executed automatically, but is available in the app. So the user is able to execute your test manually.<br />
: Possible interval values are:<br />
: <code>s</code> (seconds)<br />
: <code>m</code> (minutes)<br />
: <code>h</code> (hours)<br />
: <code>d</code> (days)<br />
: <code>w</code> (weeks)<br />
: Please note that each execution of a test requires resources. For example, if you create a test with ''1m'' that is executed every minute, you may well create an unpleasant impact! The system automatically checks the execution time of your test against your specified interval. If your test runs for a longer time than your schedule, your ''schedule'' parameter is automatically doubled by the system.<br />
: Please note the [[#Submodules|Submodule Scheduler]] with Tick and synchronous execution. For example, it is not possible to execute a test every second.<br />
<br />
===== Optional properties =====<br />
<br />
; commands<br />
: object | An object in which you can list all the commands, values, etc. that you want to use later in your test. As soon as your test() method is called, the returns of these commands are passed in as parameters so that you can analyze them. For detailed documentation, please see the [[#Property_.22commands.22|commands-documentation]] below.<br />
; minBuild<br />
: int | The minimum build version of the app, that the Test will be executed.<br />
; oneTime<br />
: bool | If ''true'' the test will be self-deactivated after the first successful execution.<br />
; enabled<br />
: bool | If ''false'' the test will be loaded but not executed. The user will see the test in the list of test, and it is possible to enable it (default: ''true'')<br />
; hidden<br />
: bool | If ''true'' the test will be skipped by the system and will not be loaded (default: ''false'')<br />
<br />
==== Property "commands" ====<br />
The property ''commands'' is an object where you can define innovaphone specific commands that are executed before your test will be executed. The results of the given commands will be passed to your test in the parameter ''results''. Think about that, all your commands will be cached until the ''schedule'' timeout is exceeded. This means that you will only get a new result of the command after the schedule time has elapsed in relation to the time of your last execution. The only exceptions is when the user manually re-executes a test via the UI or caching has been explicitly disabled at the command<br />
<br />
You have to consider a special nested notation when creating your commands, so that you can use them later.<br />
<br />
===== outer commands-object =====<br />
Let's start with some first basic rules:<br />
* ''commands'' is an object with one property per command. At this moment we only list commands, we don't take care about specific devices, types of models or so on.<br />
* Every child-property (let's call it "command-object") is a new object which contains all needed information for this specific command<br />
* The title of the property "command-object" is defined by yourself<br />
** Spoiler: The title of your "command-object" should be used later if you want to read the result for a specific device<br />
* You can list multiple "command-objects"<br />
<br />
Up to here we have the following and can define it like this:<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
my_command_one: {},<br />
my_command_two: {},<br />
},<br />
</syntaxhighlight><br />
<br />
===== single command-object =====<br />
<br />
Then we have some new rules per "command-object":<br />
* A property called ''cmd'' is expected. This property contains the real command which shall be executed (Remember, at this moment we only list commands, we don't take care about specific devices, types of models or so on)<br />
** Example 1: <code>cmd: 'CMD0/box_info.xml'</code> will give you the xml output of the general overview page<br />
** Example 2: <code>cmd: '!mod cmd CDR0 qs'</code> will give you the amount of buffered CDRs in the CDR0 interface<br />
** Example 3: <code>cmd: 'cfg.txt'</code> will give you back the full configuration file<br />
** If you are already firm with the innovaphone based command syntax, you will see that you can use any HTTP command which can be sent to an innovaphone device<br />
* Some more properties can be defined optionally. See documentation below<br />
<br />
Up to here we have an idea of a specific "command-object" and can do the following now:<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
buffered_cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
},<br />
buffered_cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
With this command, we can collect the "buffered CDRs" on both CDR Interfaces in our boxes. Maybe you see it directly... This will not make really sense in a real setup because CDRs only generated by Gateways/PBXes. So we don't need to bother phones with these requests.<br />
So from now on we take care about our defined command. There are optional parameters that we can also list inside a "command-object" to let the system know what is the to-do with this command.<br />
<br />
;cmd<br />
: string | Any HTTP command you can send to an innovaphone device. There is a limit of 15 seconds for every http request. If your request exceeds this limit the request will be cancelled.<br />
;cat<br />
: array | An optional list of device types on which the command is to be executed. If ''cat'' is empty, it means all devices in your installation.<br />
: You can define the following device categories:<br />
: <code>pbx</code> - all PBXes<br />
: <code>gw</code> - all Gateways<br />
: <code>ap</code> - all App Platforms<br />
: <code>dect</code> - all Dect Gateways<br />
: <code>phone</code> - all Phones<br />
: <code>monitoring</code> - all categories based on Monitoring settings<br />
;cache<br />
: bool | If you set it to ''false'' you will never get a cached value. Please use this option wisely and only if you really need it. (default: ''true'')<br />
<br />
Now let's improve our example from above and get the bufferd CDRx information only from pbxes and gateways.<br />
<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
buffered_cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
cat: ['pbx', 'gw'],<br />
},<br />
buffered_cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
cat: ['pbx', 'gw'],<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
===== execution and results of commands =====<br />
Up to now, we have only defined commands that are to be executed on certain devices. When your test is executed, the previously defined commands are executed and the system collects the returns in a corresponding object (called <code>results</code>) which is passed into your <code>test(cmd, results)</code> method. There you can access the results and do whatever you want to test/analyze or whatever with the return value. You will find an example and some sample-code how to use the results-object in the description of the ''test() method''<br />
<br />
===== nested commands-objects =====<br />
You can now send any commands and the results will be returned to you for evaluation.<br />
As you may have already noticed, there is no possibility to place multiple commands in dependency. But this is the way to do this.<br />
<br />
For more complicated tests, it is necessary to execute several commands one after the other and to generate following commands dynamically on the basis of the result of the first command.<br />
<br />
For such tests, there is the possibility to specify an object "commands" within a "command-object". From this level, you can define a dynamic function in which you can apply your own code based on the first result, and then return a new ''commands-object''. In this return statement, you also have the option of returning another dynamic function in order to be able to create processes of any complexity. Please note that if you not return an ''object'' your return value will be discarded. The results of your nested ''command-objects'' will be passed to the ''test()'' method inside the ''results'' object.<br />
<br />
This is certainly not easy to understand. Therefore, let us take a closer look at it with an example.<br />
<br />
====== example: nested commands-object which generates the second command from the first result ======<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
certificates: {<br />
cmd: 'X509/mod_cmd.xml',<br />
cat: ['pbx', 'gw', 'dect'],<br />
commands: function(cmd, result) {<br />
// free style code to build the following commands<br />
var xml = cmd.parse_xml(result);<br />
//log(JSON.stringify(xml));<br />
<br />
var fingerprint;<br />
// get the fingerprint for single cert<br />
if (typeof xml.info.servercert.certificate['@fingerprint'] !== 'undefined') {<br />
fingerprint = xml.info.servercert.certificate['@fingerprint']<br />
}<br />
// use last certificates in case of multiple<br />
else {<br />
fingerprint = xml.info.servercert.certificate[xml.info.servercert.certificate.length - 1]['@fingerprint'];<br />
}<br />
cmd.log('Fingerprint: '+fingerprint);<br />
<br />
return {<br />
certificate: {<br />
cmd: 'X509/mod_cmd.xml?cmd=servercert-details&fingerprint='+fingerprint,<br />
}<br />
}<br />
}<br />
}<br />
},<br />
</syntaxhighlight><br />
<br />
Our goal is to check which key-length is used in the device certificate. But there i no direct command to get this information. So we have to do it in multipe steps.<br />
<br />
In this sample, we request the following in the commands object:<br />
# Execute our command "certificates" on devices (pbx, gw, dect) the command "X509/mod_cmd.xml" which will give you back the xml payload of the page [[{{NAMESPACE}}:General/Certificates]]<br />
# If the first request is done, the nested "commands" object should be called and we get the result from the first command<br />
## Now, inside the function <code>commands: function(cmd, result) {</code> we can use some free-style code to to what we need, to build a following command<br />
## Here we convert xml to an object and extract the certificate fingerprint from the result of the first request<br />
## then we return an object with "command-objects"<br />
### think about that is possible to add an new <code>commands: function(cmd, result) {</code> inside the return to add a new level :-)<br />
## this second command will be executed to for every device and the xml payload contains the device certifcate of the current device. (like the popup in the UI if you click on a specific certificate)<br />
#If all nested commands are processed, then your test() will be called, and you get all the results (in this case "certificates" and "certificate") in the results-object<br />
<br />
====== example: nested commands-object which generates various commands from the first result ======<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
config: {<br />
cmd: 'cfg.txt',<br />
cat: ['pbx'],<br />
commands: function(cmd, result) {<br />
var lines = result.split("\r\n");<br />
var output = {};<br />
<br />
// get pbx loc<br />
var loc = false;<br />
for (var l = 0; l < lines.length; l++) {<br />
if (!lines[l].startsWith('config change PBX0')) continue; // skip non pbx line<br />
if (lines[l].includes('/mode standby')) continue; // skip slave pbxes<br />
<br />
var match = lines[l].match(/config change PBX0 (.*) \/loc ([^ ][^/]+)/);<br />
loc = match[2].substr(0, match[2].length-1);<br />
l = lines.length;<br />
}<br />
cmd.log('use pbx loc: '+loc);<br />
<br />
// get user objects<br />
var regex = new RegExp('/\(loc='+loc+'\)(.*)\(guid;bin=([0-9A-Za-z]+)\)/');<br />
for (var l = 0; l < lines.length; l++) {<br />
// skip if user is not from this pbx<br />
if (!lines[l].includes('(loc='+loc+')')) continue;<br />
<br />
var match = lines[l].match(/\(guid;bin=([0-9A-Za-z]+)\)/);<br />
if (!match) continue;<br />
cmd.log('user found: '+match[1]);<br />
output[match[1]] = {cmd: 'PBX0/ADMIN/mod_cmd_login.xml?cmd=show&user-guid='+match[1]};<br />
}<br />
<br />
return output;<br />
}<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
Our goal is to get the xml output from the advanced ui for every pbx object. But there i no direct command to get this information. So we have to do it in multipe steps.<br />
<br />
In this sample, we request the following in the commands object:<br />
# Execute our command "config" on PBXes the get the plain configuration file<br />
# If the first request is done, the nested "commands" object should be called, and we get the result from the first command<br />
## Now, inside the function <code>commands: function(cmd, result) {</code> we can use some free-style code to do what we need, to build multiple following commands<br />
<br />
## Here we split the config file by lines breaks and iterate the whole config<br />
## then we generate an empty return object to fill it later<br />
### think about that is possible to add an new <code>commands: function(cmd, result) {</code> inside the return to add a new level :-)<br />
## If we have checked the pbx and the userobject we add with <code>output[match[1]] = {cmd: 'PBX0/ADMIN/mod_cmd_login.xml?cmd=show&user-guid='+match[1]};</code> a specific command to the retunr value<br />
<br />
In the end, we have a big return object with multiple cmd's<br />
In this case we will get all the results in the test() later and can do further stuff with the results.<br />
<br />
==== Executable method test() ====<br />
The upper layer expects a method <code>test(cmd, results, storage)</code> in your JavaScript object. This method has three parameters.<br />
<br />
;cmd<br />
:An object that offers you a wide range of predefined functions and options. You can see it as a kind of library, which is documented at the [[#cmd object|cmd object]].<br />
<br />
;results<br />
:An object of the results of your commands from the given ''command-objects'' in your test definition.<br />
<spoiler show="show sample strcuture of the results object" hide="hide sample strcuture of the results object"><br />
<syntaxhighlight lang="javascript"><br />
// structure of results object<br />
{<br />
// your command is the property<br />
'buffered_cdr0' : {<br />
// the unique id of the device is the property<br />
'1': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
'4': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
},<br />
'buffered_cdr1' : {<br />
// the unique id of the device is the property<br />
'1': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
'4': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<spoiler show="show best practice code to deal with the results object" hide="hide best practice code to deal with the results object"><br />
<syntaxhighlight lang="javascript"><br />
// you can use this inside your function "test: function (cmd, results, storage)" to iterate all commands over all affected devices<br />
<br />
Object.keys(results).forEach(function(command) {<br />
log.push('command: '+command);<br />
Object.keys(results[command]).forEach(function(device) {<br />
log.push('device: '+device);<br />
var output = results[command][device];<br />
});<br />
});<br />
<br />
// expected log array from the code above:<br />
// $ command: buffered_cdr0<br />
// $ device: 1<br />
// $ device: 4<br />
// $ command: buffered_cdr1<br />
// $ device: 1<br />
// $ device: 4<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<br />
;storage<br />
:If the test has written something to the test memory during the last execution, you will get the last value back here. (Note that the storage is not available for one-time tests in the code editor. There you will always get an empty storage)<br />
<br />
===== return test result =====<br />
Your test has to be return an object with your test result. The system expect an object with the following properties.<br />
<br />
; success<br />
: boolean | indicates if your test was successful or not<br />
; msg<br />
: string | an optional short message that will be displayed in the UI as preview<br />
; log<br />
: array | an optional array with lines of logfile that you can use to display detailed information in the UI at your test result. Use <code>log.push()</code> to fill up the logfile array. In the frontend, the log will be parsed and mac addresses <code>/(^|\W)([a-f0-9]{12})(\W|$)/i</code> will be updated with an internal link to devices app. (If you want to create instead debug output to the app-instance logfile you can use <code>cmd.log()</code>)<br />
;storage<br />
: string | an optional string, which can be json or similar, that is stored for this test. The next time the test is executed, the payload saved here is available inside the test again.<br />
<br />
<syntaxhighlight lang="javascript"><br />
test: function (cmd, results, storage) {<br />
// your stuff<br />
var count = 2;<br />
<br />
return {<br />
success: false,<br />
msg: 'There are '+count+' new/unassigned devices in your setup'<br />
};<br />
}<br />
</syntaxhighlight><br />
<br />
==== The full picture ====<br />
===== Complete sample test to check buffered CDRs =====<br />
<syntaxhighlight lang="javascript"><br />
tests_add.cdrs_buffered = tests_add.cdrs_buffered || {<br />
title: 'Buffered CDRs',<br />
description: 'This test will check if CDRs on a gateway was buffered and are not transmit to the CDR target yet',<br />
todo: 'Check the CDR target',<br />
author: 'slu@innovaphone.com',<br />
enabled: true,<br />
schedule: '10m',<br />
<br />
commands: {<br />
cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
cat: ['gw'],<br />
},<br />
cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
cat: ['gw'],<br />
},<br />
cdr2: {<br />
cmd: '!mod cmd CDR2 qs',<br />
cat: ['gw'],<br />
},<br />
cdr3: {<br />
cmd: '!mod cmd CDR3 qs',<br />
cat: ['gw'],<br />
},<br />
cdr4: {<br />
cmd: '!mod cmd CDR4 qs',<br />
cat: ['gw'],<br />
},<br />
},<br />
<br />
test: function (cmd, results, storage) {<br />
var log = [];<br />
var success = true;<br />
<br />
for (var n = 0; n < 5; n++) {<br />
Object.keys(results['cdr'+n]).forEach(function(i){<br />
var check = calculate_cdrs(results['cdr'+n][i]);<br />
// result was not good, lets create a human error message<br />
if (check !== true) {<br />
log.push(cmd.get_device(i).product+' / '+cmd.get_device(i).hwId+' / '+check+'% - '+results['cdr'+n][i]);<br />
if (success) success = false;<br />
}<br />
});<br />
}<br />
<br />
return {<br />
success: success,<br />
msg: success ? '' : 'Devices with buffered CDRs exists',<br />
log: log<br />
};<br />
<br />
function calculate_cdrs(str) {<br />
// QS messages: 0 max 2000 chars: 0 max 300000<br />
var check = 0;<br />
str = str.split(' ');<br />
// log.push(str);<br />
<br />
var messages_current = str[2];<br />
var messages_max = str[4];<br />
var chars_current = str[6];<br />
var chars_max = str[8];<br />
<br />
// check messages<br />
check = cmd.percent(messages_current, messages_max);<br />
if (check >= 30) return check;<br />
<br />
// check chars<br />
check = cmd.percent(chars_current, chars_max);<br />
if (check >= 30) return check;<br />
<br />
return true;<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
===== Complete sample test to check firmware versions =====<br />
<syntaxhighlight lang="javascript"><br />
tests_add.firmware_version = tests_add.firmware_version || {<br />
title: 'Supported firmware versions',<br />
description: 'Check if you have unsupported firmware version in use',<br />
todo: 'Update the firmware on affected devices',<br />
author: 'slu@innovaphone.com',<br />
schedule: '1d',<br />
commands: {<br />
box_info: {<br />
cmd: 'CMD0/box_info.xml',<br />
},<br />
},<br />
<br />
test: function (cmd, results, storage) {<br />
var log = [];<br />
var success = true;<br />
var msg = '';<br />
<br />
Object.keys(results.box_info).forEach(function(i){<br />
var xml = cmd.parse_xml(results.box_info[i]);<br />
if (typeof xml.info === 'undefined') return;<br />
if (typeof xml.info.sys === 'undefined') return;<br />
if (typeof xml.info.sys['@version'] === 'undefined') return;<br />
<br />
if (<br />
xml.info.sys['@version'].includes('6.00') ||<br />
xml.info.sys['@version'].includes('7.00') ||<br />
xml.info.sys['@version'].includes('8.00') ||<br />
xml.info.sys['@version'].includes('9.00') ||<br />
xml.info.sys['@version'].includes('10.00') ||<br />
xml.info.sys['@version'].includes('11.00') ||<br />
xml.info.sys['@version'].includes('11r1') ||<br />
xml.info.sys['@version'].includes('12r1') ||<br />
xml.info.sys['@version'].includes('13r1')<br />
) {<br />
log.push(cmd.get_device(i).product+' / '+cmd.get_device(i).hwId+' / '+xml.info.sys['@version']);<br />
if (success) success = false;<br />
}<br />
});<br />
<br />
return {<br />
success: success,<br />
msg: success ? '' : 'You use old firmware which is no longer be supported',<br />
log: log<br />
};<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
==== cmd object ====<br />
The '''cmd''' object provides you the following methods:<br />
<br />
<br />
<br />
===== get device information / system information =====<br />
<br />
====== get_domains() : object ======<br />
You will receive all existing domains<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var domains = cmd.get_domains();<br />
console.log(domains);<br />
{<br />
"1": {<br />
"id": 1,<br />
"name": "slu.de",<br />
"deployAdminPasswords": true,<br />
"isInstanceDomain": true,<br />
"categories": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_devices() : object ======<br />
You will receive all existing devices<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var devices = cmd.get_devices();<br />
console.log(devices);<br />
{<br />
"0_009033420623": {<br />
"id": "0_009033420623",<br />
"hwId": "009033420623",<br />
"domainId": 0,<br />
"product": "IP0011",<br />
"version": "13r3 dvl [13.7526/132035/600]",<br />
"type": "GW",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"1": {<br />
"id": 1,<br />
"hwId": "009033420621",<br />
"name": "PBX - pbx.slu.de",<br />
"domainId": 1,<br />
"product": "IP0011",<br />
"version": "13r3 beta4 [13.7688/137623/600]",<br />
"type": "GW",<br />
"pbxActive": true,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"2": {<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_devices_from_domain(int id) : object ======<br />
You will receive all devices which are assigned to the given domain<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var devices = cmd.get_devices_from_domain(1);<br />
console.log(devices);<br />
{<br />
"1": {<br />
"id": 1,<br />
"hwId": "009033420621",<br />
"name": "PBX - pbx.slu.de",<br />
"domainId": 1,<br />
"product": "IP0011",<br />
"version": "13r3 beta4 [13.7688/137623/600]",<br />
"type": "GW",<br />
"pbxActive": true,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"2": {<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_device(int id) : object ======<br />
You will receive a specific device<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var device = cmd.get_device(2);<br />
console.log(device);<br />
{<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== helper functions =====<br />
<br />
====== percent(int value, int total) : float ======<br />
Returns the number of percent of value to total<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var check = cmd.percent(50, 100);<br />
console.log(check);<br />
50<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== parse_xml(string xml, string element = <nowiki>''</nowiki>) : object ======<br />
Returns an object/array representation of given XML string. Note that very large XML inputs cannot be converted directly because there are some restrictions in the duktape environment. If you receive an exception with ''Error: RangeError: regexp executor recursion limit'' you have to define which element do you want to converted (See the second example).<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var json = cmd.parse_xml('<sample><item property_1="value_1" property_2="value_2">content of item</item><item_short prop_1="value_prop_1" /></sample>');<br />
console.log(json);<br />
{<br />
"sample": {<br />
"item": {<br />
"@property_1": "value_1",<br />
"@property_2": "value_2",<br />
"#": "content of item"<br />
},<br />
"item_short": {<br />
"@prop_1": "value_prop_1"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<spoiler show="show sample code with large xml payload" hide="hide sample code with large xml payload"><br />
<syntaxhighlight lang="javascript"><br />
<br />
var xml_registrations_on_big_pbx = '\<br />
<show state="up" time="267993" loc="pbx">\<br />
<attrs></attrs>\<br />
<reg cn="Fax" guid="829a6aeec2a76401c62600155d50c817" h323="fax" pwd="********" pwdx="********" prot="JSON">\<br />
<ep type="gk" addr="172.16.176.205" time="10"/>\<br />
<pseudo-common lics=".reporting."/>\<br />
<pseudo type="fax"/>\<br />
</reg>\<br />
<reg cn="Voicemail de" guid="5ceb0ee7c2a76401bb2600155d50c817" h323="voicemail-de" pwd="********" pwdx="********" prot="JSON">\<br />
<ep type="gk" addr="172.16.176.205" time="10"/>\<br />
<pseudo-common lics=".uc.voicemail.reporting."/>\<br />
<pseudo type="vm"/>\<br />
</reg>\<br />
... and so on ...\<br />
</show>';<br />
var json = cmd.parse_xml(xml_registrations_on_big_pbx, 'reg');<br />
console.log(json);<br />
[<br />
{"@cn":"Fax", "@guid":"829a6aeec2a76401c62600155d50c817", ... "ep":{"@type":"gk","@addr":"172.16.176.205","@time":"10"}, ...},<br />
{"@cn":"Voicemail", "@guid":"5ceb0ee7c2a76401bb2600155d50c817", ... "ep":{"@type":"gk","@addr":"172.16.176.205","@time":"10"}, ...},<br />
...<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== is_supported_version(string version) : object ======<br />
Return if the given Version string is supported according to [[Howto:Supported innovaphone versions]].<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
cmd.is_supported_version('13r3 sr9 [13.7886/1000/0]'); // return "true"<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_version_from_build(int build) : string ======<br />
Return the named version from given build number. (13r3, 14r1 or similar)<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
cmd.get_version_from_build(1410485); // return "14r1"<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== debug =====<br />
<br />
====== log(string message) : void ======<br />
You can write a logfile line to the app debug log<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var domains = cmd.log('my first logfile line');<br />
07-26 07:58:33.179 TechAssist@slu.de (b0728708) | Test "sample_test" | my first logfile line<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
=== Secret knowledge for good tests ===<br />
; bool PBX-Object config attributes<br />
: You will find config attributes like <code>no-subscribe="true"</code> (this is from a Trunk Object) in the config. Please note that if the attribute is ''missing'' or the value is ''false'' it is false, otherwise it is ''true''. For example, the value <code>no-subscribe="on"</code> is also true.<br />
; bool Interface config attributes<br />
: You will find config attributes like <code>/direct-sig on</code> (this is from a SIP interface) in the config. Please note that they are exists bool-attribute which are ''true'' if the attribute is existing. In the case of bool-attribute the following value make no matter. For example, the attribute <code>/direct-sig off</code> is also true.<br />
<br />
== Monitoring ==<br />
The App supports a monitoring interface where well known IT-Monitoring Systems or other Statistics Services can connect and collect various data for the whole innovaphone installation.<br />
<br />
===Requirements===<br />
* Only devices that are known by the ''Devices App'' will be included in the monitoring data<br />
* Only devices that have a non-empty "Name" in the ''Devices App'' will be included in the monitoring data<br />
* For included App statistics, the DNS Name in the App Platform has to be set<br />
* Depending on your external system (to support the automatic host matching magic) it can be needed that all devices has the same ''Name'' in your ''Devices App'' and your external System (Usually the FQDN is used)<br />
<br />
===Configurations===<br />
* In the PBX Manager, you have to configure the credentials for the HTTP authorization to get monitoring data<br />
* In the TechAssist App in the settings area, you can select categories (PBXes, Gateways, AP Platforms, Apps, DECT, Phones) which should be included in the monitoring data<br />
* For all app services that provide statistics, the TechAssist app object must have access rights to these apps (the apps must be checked in the "Apps" tab of the PBX object)<br />
<br />
===Internal Timers===<br />
*Hardware Metrics will be updated every 5 minutes<br />
*App Statistics will be updated every 1 minute<br />
<br />
===Supported Integrations===<br />
We support various output formats over different interfaces. Your System can pull the information and append in the needed Interface/Format to the URL. <code><nowiki>Example: https://apps.slu.de/slu.de/techassist/monitoring/JSON (Here is "JSON" the used interface, see below)</nowiki></code><br />
<br />
If you use an old/legacy system that only support http basic-auth instead of digest-auth you can add a "/basic" to the endpoint url. <code><nowiki>Example: https://</nowiki>apps.slu.de/slu.de/techassist'''/basic'''/monitoring/JSON</code><br />
<br />
==== RAW ====<br />
The interface "/RAW" provides the internal TechAssist format as JSON.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
[<br />
{<br />
"id": "1",<br />
"title": "pbx.baebeca.de",<br />
"metrics": [<br />
{<br />
"id": "online",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "serialnumber",<br />
"value": "005056001338",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "product",<br />
"value": "IPVA",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "version",<br />
"value": "15r1 dvl [15.1.0130/1000/0]",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "versionIsSupported",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "uptime",<br />
"value": 2747,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "CPU",<br />
"value": 1,<br />
"valuePercent": 1,<br />
"comment": null,<br />
"min": 0,<br />
"max": 100<br />
},<br />
{<br />
"id": "CPU-R",<br />
"value": 0,<br />
"valuePercent": 0,<br />
"comment": null,<br />
"min": 0,<br />
"max": 26000<br />
},<br />
{<br />
"id": "MEM",<br />
"value": 46,<br />
"valuePercent": 0.09,<br />
"comment": null,<br />
"min": 0,<br />
"max": 49793<br />
},<br />
{<br />
"id": "ETH0",<br />
"value": 10,<br />
"valuePercent": 0,<br />
"comment": null,<br />
"min": 0,<br />
"max": 1000000<br />
}<br />
]<br />
},<br />
{<br />
"id": "47",<br />
"title": "ap.baebeca.de",<br />
"metrics": [<br />
{<br />
"id": "online",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "serialnumber",<br />
"value": "00155db3c306",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "product",<br />
"value": "AppPlatform x86_64",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "version",<br />
"value": "120010 (15r1 1510130 dvl )",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "versionIsSupported",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
""<br />
]<br />
}<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== CSV ====<br />
The interface "/CSV" provides a simple text based comma separated structure in the format <code><Hostname>;<Metric>;<Value>;<Comment></code>.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
pbx.baebeca.de;"online";1;<br />
pbx.baebeca.de;"serialnumber";005056001338;<br />
pbx.baebeca.de;"product";IPVA;<br />
pbx.baebeca.de;"version";15r1 dvl [15.1.0130/1000/0];<br />
pbx.baebeca.de;"versionIsSupported";1;<br />
pbx.baebeca.de;"uptime";3050;<br />
pbx.baebeca.de;"CPU";2;null<br />
pbx.baebeca.de;"CPU-R";0;null<br />
pbx.baebeca.de;"MEM";0.09;null<br />
pbx.baebeca.de;"ETH0";18;null<br />
ap.baebeca.de;"online";1;<br />
ap.baebeca.de;"serialnumber";00155db3c306;<br />
ap.baebeca.de;"product";AppPlatform x86_64;<br />
ap.baebeca.de;"version";120010 (15r1 1510130 dvl );<br />
ap.baebeca.de;"versionIsSupported";1;<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== JSON ====<br />
The interface "/JSON" provides a JSON formatted structure.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
{<br />
"pbx.baebeca.de": [<br />
{"device":"pbx.baebeca.de","metric":"online","value":1,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"serialnumber","value":005056001338,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"product","value":IPVA,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"version","value":15r1 dvl [15.1.0130/1000/0],"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"versionIsSupported","value":1,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"uptime","value":3050,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"CPU","value":2,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"CPU-R","value":0,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"MEM","value":0.09,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"ETH0","value":18,"comment":"null"}<br />
],<br />
"ap.baebeca.de": [<br />
{"device":"ap.baebeca.de","metric":"online","value":1,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"serialnumber","value":00155db3c306,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"product","value":AppPlatform x86_64,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"version","value":120010 (15r1 1510130 dvl ),"comment":""},<br />
{"device":"ap.baebeca.de","metric":"versionIsSupported","value":1,"comment":""},<br />
]<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== Checkmk ====<br />
The interface "/Checkmk" provides a native integration to your Checkmk system with [https://docs.checkmk.com/latest/en/piggyback.html Piggyback] information for all known hosts.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
<<<<pbx.baebeca.de>>>><br />
<<<check_mk>>><br />
AgentOS: innovaphone TechAssist<br />
Hostname: pbx.baebeca.de<br />
<<<uptime>>><br />
3050<br />
<<<kernel>>><br />
util 0<br />
cpu 1728891356864 0 0 1728891356960 0 0 0 0 0 0<br />
<<<mem>>><br />
MemTotal: 49793 kB<br />
MemFree: 49747 kB<br />
MemAvailable: 49747 kB<br />
Buffers: 0 kB<br />
Cached: 0 kB<br />
SwapTotal: 0 kB<br />
SwapFree: 0 kB<br />
Dirty: 0 kB<br />
Writeback: 0 kB<br />
<<<lnx_thermal>>><br />
<<<local>>><br />
0 "online" - online=1<br />
0 "serialnumber" - serialnumber=005056001338<br />
0 "product" - product=IPVA<br />
0 "version" - version=15r1 dvl [15.1.0130/1000/0]<br />
0 "versionIsSupported" - versionIsSupported=1<br />
0 "CPU-R" - CPU-R=0<br />
0 "ETH0" - ETH0=18<br />
<<<innovaphone>>><br />
<<<<ap.baebeca.de>>>><br />
<<<check_mk>>><br />
AgentOS: innovaphone TechAssist<br />
Hostname: ap.baebeca.de<br />
<<<uptime>>><br />
<<<kernel>>><br />
<<<mem>>><br />
<<<lnx_thermal>>><br />
<<<local>>><br />
0 "online" - online=1<br />
0 "serialnumber" - serialnumber=00155db3c306<br />
0 "product" - product=AppPlatform x86_64<br />
0 "version" - version=120010 (15r1 1510130 dvl )<br />
0 "versionIsSupported" - versionIsSupported=1<br />
<<<innovaphone>>><br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== Configure your Checkmk installation =====<br />
#Setup your Hosts in Checkmk<br />
#*Make sure that "Checkmk agent / API integrations" in the Hostconfiguration of your Application Platform is set to "API integrations if configured, else Checkmk agent", all other Hosts hat to bet set to "No API integrations, no Checkmk agent".<br />
#Create a new Rule for "Individual program call instead of agent access" in "Setup > Agents > Other integrations"<br />
#*Command line to execute: <code>curl --digest -u "user:pass" https://ap.domain.tld/domain.de/techassist/monitoring/Checkmk</code><br />
#*Explicit hosts: Set this to the Host of your Application Platform<br />
<br />
<br />
After that, you can run the service discovery and receive new checks for your devices<br />
<br />
[[File:Checkmk new checks.png|frameless|500px]]<br />
<br />
==== Icinga ====<br />
The interface "/Icinga" provides a native integration to your Icinga system for all known hosts.<br />
<br />
{{FIXME|reason=This interface is currently being researched, and it is being checked whether icinga can read such data as expected}}<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
[<br />
{<br />
"_host": "pbx.baebeca.de",<br />
"_ETH0_ipv4": "10.0.102.7",<br />
"online":1,<br />
"serialnumber":005056001338,<br />
"product":IPVA,<br />
"version":15r1 dvl [15.1.0130/1000/0],<br />
"versionIsSupported":1,<br />
"uptime":3353,<br />
"CPU":1,<br />
"CPU-R":0,<br />
"MEM":0.09,<br />
"ETH0":14<br />
},<br />
{<br />
"_host": "ap.baebeca.de",<br />
"_eth0_ipv4": "10.0.102.8",<br />
"_eth0_ipv6": "2001:4090:e000:9a1::8",<br />
"online":1,<br />
"serialnumber":00155db3c306,<br />
"product":AppPlatform x86_64,<br />
"version":120010 (15r1 1510130 dvl ),<br />
"versionIsSupported":1<br />
}<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== Configure your Icinga installation =====<br />
<br />
== Troubleshooting ==<br />
<br />
=== Startup Logfile ===<br />
If you enable the traceflag ''App'' in your App instance, you will find the following logs:<br />
<br />
AppService::AppStart TechAssist@slu.de<br />
App instance started 14C1363 14C1363<br />
...<br />
// App begins to load embedded tests<br />
JavaScript: Files tests/*<br />
...<br />
// Scheduler begins to load all the tests<br />
scheduler init<br />
init test "firmware_version"<br />
firmware_version: Test added successful<br />
init test "pbx_mediarelay"<br />
pbx_mediarelay: Test added successful</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference15r1:Concept_App_Service_TechAssist&diff=73780Reference15r1:Concept App Service TechAssist2024-10-17T11:12:16Z<p>Twl: /* Configure your Checkmk installation */</p>
<hr />
<div><br />
[[Category:Concept|Apps]]<br />
[[Category:Concept App Service TechAssist]]<br />
<!-- techassist, ticket, analyze, debug, tests --><br />
== Applies To == <br />
<br />
* innovaphone PBX from version 13r2<br />
<br />
== Overview ==<br />
The idea of the TechAssist app is to provide helpful tools for technicians, as well as to analyze static and runtime information of a system and check for problems and improvements. In this way, the app can help you find and solve problems and misconfigurations independently and quickly.<br />
For this purpose, the app supports<br />
* the execution of ''tests''<br />
** a bunch of manufacturer tests are supplied with the app<br />
** you can create and save your own tests<br />
** testresults can be downloaded to attach them to a support ticket<br />
* a PBX license overview<br />
<br />
== Licensing ==<br />
There are no licenses needed for this app<br />
<br />
== Installation ==<br />
The TechAssist App is installed by default for every new installation and is accessible from the Config Admin template.<br />
<br />
=== With the PBX manager AP app installer plug-in === <br />
[[File:Ap_app_installer.png]]<br />
<br />
Go to the PBX manager and open the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. ''Hint : if you access it for the first time, you will need to accept the "Terms of Use of the innovaphone App Store"''<br />
* In the search field located on the top right corner of the store, search for '''"Techassist"''' and click on it<br />
* Select the proper firmware version, here '''"v14"''' and click on install<br />
* Tick "I accept the terms of use" and continue by clicking on the install yellow button<br />
* Wait until the install has been finished<br />
* Close and open the PBX manager to refresh the list of the available colored AP plugin<br />
* Click on the '''"AP techassist"''' and click on '''" + Add an App"'''<br />
* Enter a '''"Name"''' that is used as display name ''(all character allowed)'' for it and the '''"SIP"''' name that is the administrative field ''(no space, no capital letters)''. ''e.g : Name: TechAssist, SIP: techassist''<br />
''Hint : The App needs access-right to one devices-api. The access to "devices-api" will be set automatically. If you want to have another devices-apis working with techassist, you have to configure it manually in the advanced UI.''<br />
* Tick the appropriate template to distribute the App<br />
* Click OK to save the settings and a green check mark will be shown to inform you that the configuration is good<br />
<br />
== Test Engine ==<br />
=== Overview ===<br />
==== Technical look inside ====<br />
[[File:Concept_TechAssist.png|thumb|upright=1.0|right|Technical Overview]]<br />
The app service receives multiple incoming websocket connections of the app objects from the PBXes. By assigning rights to a to your desired "devices-apis" (in the Apps tab), the app service receives the corresponding rights to connect to the respectively activated DevicesApps. All managed domains and devices can then be read in via this connection. (One TechAssist can only connect with one device-api)<br />
With this procedure, you can work with one DevicesApp instance and across all domains and devices in it.<br />
<br />
==== Submodules ====<br />
The app contains various sub-modules in order to be able to carry out the tests provided by the manufacturer and also to be able to integrate custom tests created by yourself.<br />
<br />
;scheduler<br />
: The scheduler initially loads all tests and performs a plausibility check of the individual tests. From this status onwards, the scheduler ensures that all tests are executed in the required time intervals.<br />
: Inside the Scheduler the tick is 5000 milliseconds, and test are executed sequentially to prevent high system load<br />
;cmd<br />
: The cmd submodule (derived from "command") can communicate with devices in the installation to query a status, the config or similar. The submodule takes care of all the information that tests from an installation want to have, consolidates them so that queries do not have to be executed multiple times and caches the results.<br />
;test<br />
: The test submodule is instantiated per test and provides all necessary functionalities within a test.<br />
<br />
==== UI Language ====<br />
By design, only the app itself is available in multiple languages. The content of the tests and technical output is intentionally only available in english.<br />
<br />
==== Tests ====<br />
The app contains a bunch of embedded test, but it is also possible to create and save your own tests.<br />
<br />
=== UI ===<br />
==== Expert Mode ====<br />
By default there are some expert information hidden in the left menu bar. You will find a switch for that in the left menu (non-mobile-view) to enable all menu items.<br />
<br />
==== Dealing with the Code Editor ====<br />
The Code Editor is a tool for viewing the tests supplied and writing your own tests based on these tests.<br />
<br />
The editor is divided into 3 basic areas.<br />
;Left - Code Editor<br />
:This is the code editor where you can write your test code in the browser. When you close the app, the content in the editor is saved, so that the next time you open the app you will find your old code again.<br />
<br />
;Top right - Menu bar<br />
:Here you will find the following functions:<br />
:Selection of all existing Tests (predefined vendor Tests and your own custom Tests)<br />
:Load the source code of the selected Test to the code editor<br />
:Delete the selected test from the app (This is only possible for custom tests)<br />
:Execute the source code (with or without cached commands in the service) in the Code Editor and show the result<br />
:Clear the Code Editor<br />
:Save the current Content from the code Editor as Test<br />
::The title of your test is divided from the ''title'' property in your test (lower based without non-alphanumeric characters). This means: If you save another Test with the same ''title'' the value will be saved in the other test.<br />
<br />
;Top right - Results<br />
:If you execute, save or delete a test you will get the response/results in this area<br />
<br />
=== Create your own Testscript ===<br />
You can create your own Test scripts in a JavaScript based environment.<br />
A test itself is a JavaScript object with some configurations properties and a section of ''freestyle'' code to use JavaScript habits to perform your test. If your test will be executed, an above layer will call your ''test()'' method and want to have a return object with your result.<br />
<br />
There already exists a global Object called '''tests_add'''. You can add your own Test as Property to this existing Object like:<br />
<syntaxhighlight lang="javascript"><br />
tests_add.my_new_test = tests_add.my_new_test || {<br />
title: 'Check for xyz',<br />
// configuration properties<br />
<br />
test: function (cmd, result, storage) {<br />
// your custom test code<br />
<br />
return {<br />
success: false,<br />
msg: '....'<br />
};<br />
}<br />
} <br />
</syntaxhighlight><br />
<br />
The way to add a test with <code>tests_add.my_new_test = tests_add.my_new_test || {}</code> is important so that two tests do not overwrite each other. Please also pay attention to this. In this example, we have a ''logical condition'' in the first line. If the test ''my_new_test'' already exists in the object ''tests_add'' the left side from the ''OR-condition'' is ''true'', and the existing test takes place. Otherwise, it is ''false'' and the right side (your new test object) will be written to ''tests_add.my_new_test''.<br />
<br />
==== Configuration Properties ====<br />
You must configure certain properties in your test so that the scheduler knows exactly how to handle your test.<br />
<br />
Example:<br />
<syntaxhighlight lang="javascript"><br />
tests_add.my_new_test = tests_add.my_new_test || {<br />
title: 'Unknown / New devices',<br />
description: 'Check for unassigned devices in your installation',<br />
todo: 'Please check the unknown devices in your installation and acceppt or delete the devices',<br />
author: 'slu@innovaphone.com',<br />
enabled: true,<br />
schedule: '1h',<br />
commands: { ... },<br />
<br />
test: function (cmd, result, storage) {<br />
// your custom test code<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
===== Mandatory properties =====<br />
<br />
; title<br />
: string | The title of your test, which is displayed in the UI<br />
; description<br />
: string | A short description of your test, which is displayed in the UI<br />
; todo<br />
: string | An instruction on what the user has to do if the check fails. It will be displayed above the logfile in failed tests. (You can use ''\r\n'' for line breaks)<br />
: Variable <nowiki>{{VERSION}}</nowiki> will be replaced to current Version of the app like "14r1"<br />
; author<br />
: string | The contact of the person who create the test<br />
; schedule<br />
: string | The time interval during which the test is to be carried out independently. The format is composed of a numerical value and interval value. This allows you to create combinations such as <code>5m (every 5 minutes), 10h (every 10 hours) or 1d (every day) </code>. A special case which is also allowed is the value ''none''. With a ''none'' value, your test will not be executed automatically, but is available in the app. So the user is able to execute your test manually.<br />
: Possible interval values are:<br />
: <code>s</code> (seconds)<br />
: <code>m</code> (minutes)<br />
: <code>h</code> (hours)<br />
: <code>d</code> (days)<br />
: <code>w</code> (weeks)<br />
: Please note that each execution of a test requires resources. For example, if you create a test with ''1m'' that is executed every minute, you may well create an unpleasant impact! The system automatically checks the execution time of your test against your specified interval. If your test runs for a longer time than your schedule, your ''schedule'' parameter is automatically doubled by the system.<br />
: Please note the [[#Submodules|Submodule Scheduler]] with Tick and synchronous execution. For example, it is not possible to execute a test every second.<br />
<br />
===== Optional properties =====<br />
<br />
; commands<br />
: object | An object in which you can list all the commands, values, etc. that you want to use later in your test. As soon as your test() method is called, the returns of these commands are passed in as parameters so that you can analyze them. For detailed documentation, please see the [[#Property_.22commands.22|commands-documentation]] below.<br />
; minBuild<br />
: int | The minimum build version of the app, that the Test will be executed.<br />
; oneTime<br />
: bool | If ''true'' the test will be self-deactivated after the first successful execution.<br />
; enabled<br />
: bool | If ''false'' the test will be loaded but not executed. The user will see the test in the list of test, and it is possible to enable it (default: ''true'')<br />
; hidden<br />
: bool | If ''true'' the test will be skipped by the system and will not be loaded (default: ''false'')<br />
<br />
==== Property "commands" ====<br />
The property ''commands'' is an object where you can define innovaphone specific commands that are executed before your test will be executed. The results of the given commands will be passed to your test in the parameter ''results''. Think about that, all your commands will be cached until the ''schedule'' timeout is exceeded. This means that you will only get a new result of the command after the schedule time has elapsed in relation to the time of your last execution. The only exceptions is when the user manually re-executes a test via the UI or caching has been explicitly disabled at the command<br />
<br />
You have to consider a special nested notation when creating your commands, so that you can use them later.<br />
<br />
===== outer commands-object =====<br />
Let's start with some first basic rules:<br />
* ''commands'' is an object with one property per command. At this moment we only list commands, we don't take care about specific devices, types of models or so on.<br />
* Every child-property (let's call it "command-object") is a new object which contains all needed information for this specific command<br />
* The title of the property "command-object" is defined by yourself<br />
** Spoiler: The title of your "command-object" should be used later if you want to read the result for a specific device<br />
* You can list multiple "command-objects"<br />
<br />
Up to here we have the following and can define it like this:<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
my_command_one: {},<br />
my_command_two: {},<br />
},<br />
</syntaxhighlight><br />
<br />
===== single command-object =====<br />
<br />
Then we have some new rules per "command-object":<br />
* A property called ''cmd'' is expected. This property contains the real command which shall be executed (Remember, at this moment we only list commands, we don't take care about specific devices, types of models or so on)<br />
** Example 1: <code>cmd: 'CMD0/box_info.xml'</code> will give you the xml output of the general overview page<br />
** Example 2: <code>cmd: '!mod cmd CDR0 qs'</code> will give you the amount of buffered CDRs in the CDR0 interface<br />
** Example 3: <code>cmd: 'cfg.txt'</code> will give you back the full configuration file<br />
** If you are already firm with the innovaphone based command syntax, you will see that you can use any HTTP command which can be sent to an innovaphone device<br />
* Some more properties can be defined optionally. See documentation below<br />
<br />
Up to here we have an idea of a specific "command-object" and can do the following now:<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
buffered_cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
},<br />
buffered_cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
With this command, we can collect the "buffered CDRs" on both CDR Interfaces in our boxes. Maybe you see it directly... This will not make really sense in a real setup because CDRs only generated by Gateways/PBXes. So we don't need to bother phones with these requests.<br />
So from now on we take care about our defined command. There are optional parameters that we can also list inside a "command-object" to let the system know what is the to-do with this command.<br />
<br />
;cmd<br />
: string | Any HTTP command you can send to an innovaphone device. There is a limit of 15 seconds for every http request. If your request exceeds this limit the request will be cancelled.<br />
;cat<br />
: array | An optional list of device types on which the command is to be executed. If ''cat'' is empty, it means all devices in your installation.<br />
: You can define the following device categories:<br />
: <code>pbx</code> - all PBXes<br />
: <code>gw</code> - all Gateways<br />
: <code>ap</code> - all App Platforms<br />
: <code>dect</code> - all Dect Gateways<br />
: <code>phone</code> - all Phones<br />
: <code>monitoring</code> - all categories based on Monitoring settings<br />
;cache<br />
: bool | If you set it to ''false'' you will never get a cached value. Please use this option wisely and only if you really need it. (default: ''true'')<br />
<br />
Now let's improve our example from above and get the bufferd CDRx information only from pbxes and gateways.<br />
<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
buffered_cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
cat: ['pbx', 'gw'],<br />
},<br />
buffered_cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
cat: ['pbx', 'gw'],<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
===== execution and results of commands =====<br />
Up to now, we have only defined commands that are to be executed on certain devices. When your test is executed, the previously defined commands are executed and the system collects the returns in a corresponding object (called <code>results</code>) which is passed into your <code>test(cmd, results)</code> method. There you can access the results and do whatever you want to test/analyze or whatever with the return value. You will find an example and some sample-code how to use the results-object in the description of the ''test() method''<br />
<br />
===== nested commands-objects =====<br />
You can now send any commands and the results will be returned to you for evaluation.<br />
As you may have already noticed, there is no possibility to place multiple commands in dependency. But this is the way to do this.<br />
<br />
For more complicated tests, it is necessary to execute several commands one after the other and to generate following commands dynamically on the basis of the result of the first command.<br />
<br />
For such tests, there is the possibility to specify an object "commands" within a "command-object". From this level, you can define a dynamic function in which you can apply your own code based on the first result, and then return a new ''commands-object''. In this return statement, you also have the option of returning another dynamic function in order to be able to create processes of any complexity. Please note that if you not return an ''object'' your return value will be discarded. The results of your nested ''command-objects'' will be passed to the ''test()'' method inside the ''results'' object.<br />
<br />
This is certainly not easy to understand. Therefore, let us take a closer look at it with an example.<br />
<br />
====== example: nested commands-object which generates the second command from the first result ======<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
certificates: {<br />
cmd: 'X509/mod_cmd.xml',<br />
cat: ['pbx', 'gw', 'dect'],<br />
commands: function(cmd, result) {<br />
// free style code to build the following commands<br />
var xml = cmd.parse_xml(result);<br />
//log(JSON.stringify(xml));<br />
<br />
var fingerprint;<br />
// get the fingerprint for single cert<br />
if (typeof xml.info.servercert.certificate['@fingerprint'] !== 'undefined') {<br />
fingerprint = xml.info.servercert.certificate['@fingerprint']<br />
}<br />
// use last certificates in case of multiple<br />
else {<br />
fingerprint = xml.info.servercert.certificate[xml.info.servercert.certificate.length - 1]['@fingerprint'];<br />
}<br />
cmd.log('Fingerprint: '+fingerprint);<br />
<br />
return {<br />
certificate: {<br />
cmd: 'X509/mod_cmd.xml?cmd=servercert-details&fingerprint='+fingerprint,<br />
}<br />
}<br />
}<br />
}<br />
},<br />
</syntaxhighlight><br />
<br />
Our goal is to check which key-length is used in the device certificate. But there i no direct command to get this information. So we have to do it in multipe steps.<br />
<br />
In this sample, we request the following in the commands object:<br />
# Execute our command "certificates" on devices (pbx, gw, dect) the command "X509/mod_cmd.xml" which will give you back the xml payload of the page [[{{NAMESPACE}}:General/Certificates]]<br />
# If the first request is done, the nested "commands" object should be called and we get the result from the first command<br />
## Now, inside the function <code>commands: function(cmd, result) {</code> we can use some free-style code to to what we need, to build a following command<br />
## Here we convert xml to an object and extract the certificate fingerprint from the result of the first request<br />
## then we return an object with "command-objects"<br />
### think about that is possible to add an new <code>commands: function(cmd, result) {</code> inside the return to add a new level :-)<br />
## this second command will be executed to for every device and the xml payload contains the device certifcate of the current device. (like the popup in the UI if you click on a specific certificate)<br />
#If all nested commands are processed, then your test() will be called, and you get all the results (in this case "certificates" and "certificate") in the results-object<br />
<br />
====== example: nested commands-object which generates various commands from the first result ======<br />
<syntaxhighlight lang="javascript"><br />
commands: {<br />
config: {<br />
cmd: 'cfg.txt',<br />
cat: ['pbx'],<br />
commands: function(cmd, result) {<br />
var lines = result.split("\r\n");<br />
var output = {};<br />
<br />
// get pbx loc<br />
var loc = false;<br />
for (var l = 0; l < lines.length; l++) {<br />
if (!lines[l].startsWith('config change PBX0')) continue; // skip non pbx line<br />
if (lines[l].includes('/mode standby')) continue; // skip slave pbxes<br />
<br />
var match = lines[l].match(/config change PBX0 (.*) \/loc ([^ ][^/]+)/);<br />
loc = match[2].substr(0, match[2].length-1);<br />
l = lines.length;<br />
}<br />
cmd.log('use pbx loc: '+loc);<br />
<br />
// get user objects<br />
var regex = new RegExp('/\(loc='+loc+'\)(.*)\(guid;bin=([0-9A-Za-z]+)\)/');<br />
for (var l = 0; l < lines.length; l++) {<br />
// skip if user is not from this pbx<br />
if (!lines[l].includes('(loc='+loc+')')) continue;<br />
<br />
var match = lines[l].match(/\(guid;bin=([0-9A-Za-z]+)\)/);<br />
if (!match) continue;<br />
cmd.log('user found: '+match[1]);<br />
output[match[1]] = {cmd: 'PBX0/ADMIN/mod_cmd_login.xml?cmd=show&user-guid='+match[1]};<br />
}<br />
<br />
return output;<br />
}<br />
},<br />
},<br />
</syntaxhighlight><br />
<br />
Our goal is to get the xml output from the advanced ui for every pbx object. But there i no direct command to get this information. So we have to do it in multipe steps.<br />
<br />
In this sample, we request the following in the commands object:<br />
# Execute our command "config" on PBXes the get the plain configuration file<br />
# If the first request is done, the nested "commands" object should be called, and we get the result from the first command<br />
## Now, inside the function <code>commands: function(cmd, result) {</code> we can use some free-style code to do what we need, to build multiple following commands<br />
<br />
## Here we split the config file by lines breaks and iterate the whole config<br />
## then we generate an empty return object to fill it later<br />
### think about that is possible to add an new <code>commands: function(cmd, result) {</code> inside the return to add a new level :-)<br />
## If we have checked the pbx and the userobject we add with <code>output[match[1]] = {cmd: 'PBX0/ADMIN/mod_cmd_login.xml?cmd=show&user-guid='+match[1]};</code> a specific command to the retunr value<br />
<br />
In the end, we have a big return object with multiple cmd's<br />
In this case we will get all the results in the test() later and can do further stuff with the results.<br />
<br />
==== Executable method test() ====<br />
The upper layer expects a method <code>test(cmd, results, storage)</code> in your JavaScript object. This method has three parameters.<br />
<br />
;cmd<br />
:An object that offers you a wide range of predefined functions and options. You can see it as a kind of library, which is documented at the [[#cmd object|cmd object]].<br />
<br />
;results<br />
:An object of the results of your commands from the given ''command-objects'' in your test definition.<br />
<spoiler show="show sample strcuture of the results object" hide="hide sample strcuture of the results object"><br />
<syntaxhighlight lang="javascript"><br />
// structure of results object<br />
{<br />
// your command is the property<br />
'buffered_cdr0' : {<br />
// the unique id of the device is the property<br />
'1': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
'4': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
},<br />
'buffered_cdr1' : {<br />
// the unique id of the device is the property<br />
'1': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
'4': 'QS messages: 0 max 2000 chars: 0 max 300000',<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<spoiler show="show best practice code to deal with the results object" hide="hide best practice code to deal with the results object"><br />
<syntaxhighlight lang="javascript"><br />
// you can use this inside your function "test: function (cmd, results, storage)" to iterate all commands over all affected devices<br />
<br />
Object.keys(results).forEach(function(command) {<br />
log.push('command: '+command);<br />
Object.keys(results[command]).forEach(function(device) {<br />
log.push('device: '+device);<br />
var output = results[command][device];<br />
});<br />
});<br />
<br />
// expected log array from the code above:<br />
// $ command: buffered_cdr0<br />
// $ device: 1<br />
// $ device: 4<br />
// $ command: buffered_cdr1<br />
// $ device: 1<br />
// $ device: 4<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<br />
;storage<br />
:If the test has written something to the test memory during the last execution, you will get the last value back here. (Note that the storage is not available for one-time tests in the code editor. There you will always get an empty storage)<br />
<br />
===== return test result =====<br />
Your test has to be return an object with your test result. The system expect an object with the following properties.<br />
<br />
; success<br />
: boolean | indicates if your test was successful or not<br />
; msg<br />
: string | an optional short message that will be displayed in the UI as preview<br />
; log<br />
: array | an optional array with lines of logfile that you can use to display detailed information in the UI at your test result. Use <code>log.push()</code> to fill up the logfile array. In the frontend, the log will be parsed and mac addresses <code>/(^|\W)([a-f0-9]{12})(\W|$)/i</code> will be updated with an internal link to devices app. (If you want to create instead debug output to the app-instance logfile you can use <code>cmd.log()</code>)<br />
;storage<br />
: string | an optional string, which can be json or similar, that is stored for this test. The next time the test is executed, the payload saved here is available inside the test again.<br />
<br />
<syntaxhighlight lang="javascript"><br />
test: function (cmd, results, storage) {<br />
// your stuff<br />
var count = 2;<br />
<br />
return {<br />
success: false,<br />
msg: 'There are '+count+' new/unassigned devices in your setup'<br />
};<br />
}<br />
</syntaxhighlight><br />
<br />
==== The full picture ====<br />
===== Complete sample test to check buffered CDRs =====<br />
<syntaxhighlight lang="javascript"><br />
tests_add.cdrs_buffered = tests_add.cdrs_buffered || {<br />
title: 'Buffered CDRs',<br />
description: 'This test will check if CDRs on a gateway was buffered and are not transmit to the CDR target yet',<br />
todo: 'Check the CDR target',<br />
author: 'slu@innovaphone.com',<br />
enabled: true,<br />
schedule: '10m',<br />
<br />
commands: {<br />
cdr0: {<br />
cmd: '!mod cmd CDR0 qs',<br />
cat: ['gw'],<br />
},<br />
cdr1: {<br />
cmd: '!mod cmd CDR1 qs',<br />
cat: ['gw'],<br />
},<br />
cdr2: {<br />
cmd: '!mod cmd CDR2 qs',<br />
cat: ['gw'],<br />
},<br />
cdr3: {<br />
cmd: '!mod cmd CDR3 qs',<br />
cat: ['gw'],<br />
},<br />
cdr4: {<br />
cmd: '!mod cmd CDR4 qs',<br />
cat: ['gw'],<br />
},<br />
},<br />
<br />
test: function (cmd, results, storage) {<br />
var log = [];<br />
var success = true;<br />
<br />
for (var n = 0; n < 5; n++) {<br />
Object.keys(results['cdr'+n]).forEach(function(i){<br />
var check = calculate_cdrs(results['cdr'+n][i]);<br />
// result was not good, lets create a human error message<br />
if (check !== true) {<br />
log.push(cmd.get_device(i).product+' / '+cmd.get_device(i).hwId+' / '+check+'% - '+results['cdr'+n][i]);<br />
if (success) success = false;<br />
}<br />
});<br />
}<br />
<br />
return {<br />
success: success,<br />
msg: success ? '' : 'Devices with buffered CDRs exists',<br />
log: log<br />
};<br />
<br />
function calculate_cdrs(str) {<br />
// QS messages: 0 max 2000 chars: 0 max 300000<br />
var check = 0;<br />
str = str.split(' ');<br />
// log.push(str);<br />
<br />
var messages_current = str[2];<br />
var messages_max = str[4];<br />
var chars_current = str[6];<br />
var chars_max = str[8];<br />
<br />
// check messages<br />
check = cmd.percent(messages_current, messages_max);<br />
if (check >= 30) return check;<br />
<br />
// check chars<br />
check = cmd.percent(chars_current, chars_max);<br />
if (check >= 30) return check;<br />
<br />
return true;<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
===== Complete sample test to check firmware versions =====<br />
<syntaxhighlight lang="javascript"><br />
tests_add.firmware_version = tests_add.firmware_version || {<br />
title: 'Supported firmware versions',<br />
description: 'Check if you have unsupported firmware version in use',<br />
todo: 'Update the firmware on affected devices',<br />
author: 'slu@innovaphone.com',<br />
schedule: '1d',<br />
commands: {<br />
box_info: {<br />
cmd: 'CMD0/box_info.xml',<br />
},<br />
},<br />
<br />
test: function (cmd, results, storage) {<br />
var log = [];<br />
var success = true;<br />
var msg = '';<br />
<br />
Object.keys(results.box_info).forEach(function(i){<br />
var xml = cmd.parse_xml(results.box_info[i]);<br />
if (typeof xml.info === 'undefined') return;<br />
if (typeof xml.info.sys === 'undefined') return;<br />
if (typeof xml.info.sys['@version'] === 'undefined') return;<br />
<br />
if (<br />
xml.info.sys['@version'].includes('6.00') ||<br />
xml.info.sys['@version'].includes('7.00') ||<br />
xml.info.sys['@version'].includes('8.00') ||<br />
xml.info.sys['@version'].includes('9.00') ||<br />
xml.info.sys['@version'].includes('10.00') ||<br />
xml.info.sys['@version'].includes('11.00') ||<br />
xml.info.sys['@version'].includes('11r1') ||<br />
xml.info.sys['@version'].includes('12r1') ||<br />
xml.info.sys['@version'].includes('13r1')<br />
) {<br />
log.push(cmd.get_device(i).product+' / '+cmd.get_device(i).hwId+' / '+xml.info.sys['@version']);<br />
if (success) success = false;<br />
}<br />
});<br />
<br />
return {<br />
success: success,<br />
msg: success ? '' : 'You use old firmware which is no longer be supported',<br />
log: log<br />
};<br />
}<br />
}<br />
</syntaxhighlight><br />
<br />
==== cmd object ====<br />
The '''cmd''' object provides you the following methods:<br />
<br />
<br />
<br />
===== get device information / system information =====<br />
<br />
====== get_domains() : object ======<br />
You will receive all existing domains<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var domains = cmd.get_domains();<br />
console.log(domains);<br />
{<br />
"1": {<br />
"id": 1,<br />
"name": "slu.de",<br />
"deployAdminPasswords": true,<br />
"isInstanceDomain": true,<br />
"categories": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_devices() : object ======<br />
You will receive all existing devices<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var devices = cmd.get_devices();<br />
console.log(devices);<br />
{<br />
"0_009033420623": {<br />
"id": "0_009033420623",<br />
"hwId": "009033420623",<br />
"domainId": 0,<br />
"product": "IP0011",<br />
"version": "13r3 dvl [13.7526/132035/600]",<br />
"type": "GW",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"1": {<br />
"id": 1,<br />
"hwId": "009033420621",<br />
"name": "PBX - pbx.slu.de",<br />
"domainId": 1,<br />
"product": "IP0011",<br />
"version": "13r3 beta4 [13.7688/137623/600]",<br />
"type": "GW",<br />
"pbxActive": true,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"2": {<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_devices_from_domain(int id) : object ======<br />
You will receive all devices which are assigned to the given domain<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var devices = cmd.get_devices_from_domain(1);<br />
console.log(devices);<br />
{<br />
"1": {<br />
"id": 1,<br />
"hwId": "009033420621",<br />
"name": "PBX - pbx.slu.de",<br />
"domainId": 1,<br />
"product": "IP0011",<br />
"version": "13r3 beta4 [13.7688/137623/600]",<br />
"type": "GW",<br />
"pbxActive": true,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
},<br />
"2": {<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_device(int id) : object ======<br />
You will receive a specific device<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var device = cmd.get_device(2);<br />
console.log(device);<br />
{<br />
"id": 2,<br />
"hwId": "029033420621",<br />
"name": "AP - apps.slu.de",<br />
"domainId": 1,<br />
"product": "AppPlatform ARM",<br />
"version": "110002 dvl (13r3 137688 beta4 )",<br />
"type": "APP_PLATFORM",<br />
"pbxActive": false,<br />
"online": true,<br />
"ethIfs": [ ... ]<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== helper functions =====<br />
<br />
====== percent(int value, int total) : float ======<br />
Returns the number of percent of value to total<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var check = cmd.percent(50, 100);<br />
console.log(check);<br />
50<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== parse_xml(string xml, string element = <nowiki>''</nowiki>) : object ======<br />
Returns an object/array representation of given XML string. Note that very large XML inputs cannot be converted directly because there are some restrictions in the duktape environment. If you receive an exception with ''Error: RangeError: regexp executor recursion limit'' you have to define which element do you want to converted (See the second example).<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var json = cmd.parse_xml('<sample><item property_1="value_1" property_2="value_2">content of item</item><item_short prop_1="value_prop_1" /></sample>');<br />
console.log(json);<br />
{<br />
"sample": {<br />
"item": {<br />
"@property_1": "value_1",<br />
"@property_2": "value_2",<br />
"#": "content of item"<br />
},<br />
"item_short": {<br />
"@prop_1": "value_prop_1"<br />
}<br />
}<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br><br />
<spoiler show="show sample code with large xml payload" hide="hide sample code with large xml payload"><br />
<syntaxhighlight lang="javascript"><br />
<br />
var xml_registrations_on_big_pbx = '\<br />
<show state="up" time="267993" loc="pbx">\<br />
<attrs></attrs>\<br />
<reg cn="Fax" guid="829a6aeec2a76401c62600155d50c817" h323="fax" pwd="********" pwdx="********" prot="JSON">\<br />
<ep type="gk" addr="172.16.176.205" time="10"/>\<br />
<pseudo-common lics=".reporting."/>\<br />
<pseudo type="fax"/>\<br />
</reg>\<br />
<reg cn="Voicemail de" guid="5ceb0ee7c2a76401bb2600155d50c817" h323="voicemail-de" pwd="********" pwdx="********" prot="JSON">\<br />
<ep type="gk" addr="172.16.176.205" time="10"/>\<br />
<pseudo-common lics=".uc.voicemail.reporting."/>\<br />
<pseudo type="vm"/>\<br />
</reg>\<br />
... and so on ...\<br />
</show>';<br />
var json = cmd.parse_xml(xml_registrations_on_big_pbx, 'reg');<br />
console.log(json);<br />
[<br />
{"@cn":"Fax", "@guid":"829a6aeec2a76401c62600155d50c817", ... "ep":{"@type":"gk","@addr":"172.16.176.205","@time":"10"}, ...},<br />
{"@cn":"Voicemail", "@guid":"5ceb0ee7c2a76401bb2600155d50c817", ... "ep":{"@type":"gk","@addr":"172.16.176.205","@time":"10"}, ...},<br />
...<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== is_supported_version(string version) : object ======<br />
Return if the given Version string is supported according to [[Howto:Supported innovaphone versions]].<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
cmd.is_supported_version('13r3 sr9 [13.7886/1000/0]'); // return "true"<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
====== get_version_from_build(int build) : string ======<br />
Return the named version from given build number. (13r3, 14r1 or similar)<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
cmd.get_version_from_build(1410485); // return "14r1"<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== debug =====<br />
<br />
====== log(string message) : void ======<br />
You can write a logfile line to the app debug log<br />
<br />
<spoiler show="show sample code" hide="hide sample code"><br />
<syntaxhighlight lang="javascript"><br />
var domains = cmd.log('my first logfile line');<br />
07-26 07:58:33.179 TechAssist@slu.de (b0728708) | Test "sample_test" | my first logfile line<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
=== Secret knowledge for good tests ===<br />
; bool PBX-Object config attributes<br />
: You will find config attributes like <code>no-subscribe="true"</code> (this is from a Trunk Object) in the config. Please note that if the attribute is ''missing'' or the value is ''false'' it is false, otherwise it is ''true''. For example, the value <code>no-subscribe="on"</code> is also true.<br />
; bool Interface config attributes<br />
: You will find config attributes like <code>/direct-sig on</code> (this is from a SIP interface) in the config. Please note that they are exists bool-attribute which are ''true'' if the attribute is existing. In the case of bool-attribute the following value make no matter. For example, the attribute <code>/direct-sig off</code> is also true.<br />
<br />
== Monitoring ==<br />
The App supports a monitoring interface where well known IT-Monitoring Systems or other Statistics Services can connect and collect various data for the whole innovaphone installation.<br />
<br />
===Requirements===<br />
* Only devices that are known by the ''Devices App'' will be included in the monitoring data<br />
* Only devices that have a non-empty "Name" in the ''Devices App'' will be included in the monitoring data<br />
* For included App statistics, the DNS Name in the App Platform has to be set<br />
* Depending on your external system (to support the automatic host matching magic) it can be needed that all devices has the same ''Name'' in your ''Devices App'' and your external System (Usually the FQDN is used)<br />
<br />
===Configurations===<br />
* In the PBX Manager, you have to configure the credentials for the HTTP authorization to get monitoring data<br />
* In the TechAssist App in the settings area, you can select categories (PBXes, Gateways, AP Platforms, Apps, DECT, Phones) which should be included in the monitoring data<br />
* For all app services that provide statistics, the TechAssist app object must have access rights to these apps (the apps must be checked in the "Apps" tab of the PBX object)<br />
<br />
===Internal Timers===<br />
*Hardware Metrics will be updated every 5 minutes<br />
*App Statistics will be updated every 1 minute<br />
<br />
===Supported Integrations===<br />
We support various output formats over different interfaces. Your System can pull the information and append in the needed Interface/Format to the URL. <code><nowiki>Example: https://apps.slu.de/slu.de/techassist/monitoring/JSON (Here is "JSON" the used interface, see below)</nowiki></code><br />
<br />
If you use an old/legacy system that only support http basic-auth instead of digest-auth you can add a "/basic" to the endpoint url. <code><nowiki>Example: https://</nowiki>apps.slu.de/slu.de/techassist'''/basic'''/monitoring/JSON</code><br />
<br />
==== RAW ====<br />
The interface "/RAW" provides the internal TechAssist format as JSON.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
[<br />
{<br />
"id": "1",<br />
"title": "pbx.baebeca.de",<br />
"metrics": [<br />
{<br />
"id": "online",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "serialnumber",<br />
"value": "005056001338",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "product",<br />
"value": "IPVA",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "version",<br />
"value": "15r1 dvl [15.1.0130/1000/0]",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "versionIsSupported",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "uptime",<br />
"value": 2747,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "CPU",<br />
"value": 1,<br />
"valuePercent": 1,<br />
"comment": null,<br />
"min": 0,<br />
"max": 100<br />
},<br />
{<br />
"id": "CPU-R",<br />
"value": 0,<br />
"valuePercent": 0,<br />
"comment": null,<br />
"min": 0,<br />
"max": 26000<br />
},<br />
{<br />
"id": "MEM",<br />
"value": 46,<br />
"valuePercent": 0.09,<br />
"comment": null,<br />
"min": 0,<br />
"max": 49793<br />
},<br />
{<br />
"id": "ETH0",<br />
"value": 10,<br />
"valuePercent": 0,<br />
"comment": null,<br />
"min": 0,<br />
"max": 1000000<br />
}<br />
]<br />
},<br />
{<br />
"id": "47",<br />
"title": "ap.baebeca.de",<br />
"metrics": [<br />
{<br />
"id": "online",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "serialnumber",<br />
"value": "00155db3c306",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "product",<br />
"value": "AppPlatform x86_64",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "version",<br />
"value": "120010 (15r1 1510130 dvl )",<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
{<br />
"id": "versionIsSupported",<br />
"value": 1,<br />
"valuePercent": null,<br />
"comment": "",<br />
"min": null,<br />
"max": null<br />
},<br />
""<br />
]<br />
}<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== CSV ====<br />
The interface "/CSV" provides a simple text based comma separated structure in the format <code><Hostname>;<Metric>;<Value>;<Comment></code>.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
pbx.baebeca.de;"online";1;<br />
pbx.baebeca.de;"serialnumber";005056001338;<br />
pbx.baebeca.de;"product";IPVA;<br />
pbx.baebeca.de;"version";15r1 dvl [15.1.0130/1000/0];<br />
pbx.baebeca.de;"versionIsSupported";1;<br />
pbx.baebeca.de;"uptime";3050;<br />
pbx.baebeca.de;"CPU";2;null<br />
pbx.baebeca.de;"CPU-R";0;null<br />
pbx.baebeca.de;"MEM";0.09;null<br />
pbx.baebeca.de;"ETH0";18;null<br />
ap.baebeca.de;"online";1;<br />
ap.baebeca.de;"serialnumber";00155db3c306;<br />
ap.baebeca.de;"product";AppPlatform x86_64;<br />
ap.baebeca.de;"version";120010 (15r1 1510130 dvl );<br />
ap.baebeca.de;"versionIsSupported";1;<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== JSON ====<br />
The interface "/JSON" provides a JSON formatted structure.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
{<br />
"pbx.baebeca.de": [<br />
{"device":"pbx.baebeca.de","metric":"online","value":1,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"serialnumber","value":005056001338,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"product","value":IPVA,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"version","value":15r1 dvl [15.1.0130/1000/0],"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"versionIsSupported","value":1,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"uptime","value":3050,"comment":""},<br />
{"device":"pbx.baebeca.de","metric":"CPU","value":2,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"CPU-R","value":0,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"MEM","value":0.09,"comment":"null"},<br />
{"device":"pbx.baebeca.de","metric":"ETH0","value":18,"comment":"null"}<br />
],<br />
"ap.baebeca.de": [<br />
{"device":"ap.baebeca.de","metric":"online","value":1,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"serialnumber","value":00155db3c306,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"product","value":AppPlatform x86_64,"comment":""},<br />
{"device":"ap.baebeca.de","metric":"version","value":120010 (15r1 1510130 dvl ),"comment":""},<br />
{"device":"ap.baebeca.de","metric":"versionIsSupported","value":1,"comment":""},<br />
]<br />
}<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
==== Checkmk ====<br />
The interface "/Checkmk" provides a native integration to your Checkmk system with [https://docs.checkmk.com/latest/en/piggyback.html Piggyback] information for all known hosts.<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
<<<<pbx.baebeca.de>>>><br />
<<<check_mk>>><br />
AgentOS: innovaphone TechAssist<br />
Hostname: pbx.baebeca.de<br />
<<<uptime>>><br />
3050<br />
<<<kernel>>><br />
util 0<br />
cpu 1728891356864 0 0 1728891356960 0 0 0 0 0 0<br />
<<<mem>>><br />
MemTotal: 49793 kB<br />
MemFree: 49747 kB<br />
MemAvailable: 49747 kB<br />
Buffers: 0 kB<br />
Cached: 0 kB<br />
SwapTotal: 0 kB<br />
SwapFree: 0 kB<br />
Dirty: 0 kB<br />
Writeback: 0 kB<br />
<<<lnx_thermal>>><br />
<<<local>>><br />
0 "online" - online=1<br />
0 "serialnumber" - serialnumber=005056001338<br />
0 "product" - product=IPVA<br />
0 "version" - version=15r1 dvl [15.1.0130/1000/0]<br />
0 "versionIsSupported" - versionIsSupported=1<br />
0 "CPU-R" - CPU-R=0<br />
0 "ETH0" - ETH0=18<br />
<<<innovaphone>>><br />
<<<<ap.baebeca.de>>>><br />
<<<check_mk>>><br />
AgentOS: innovaphone TechAssist<br />
Hostname: ap.baebeca.de<br />
<<<uptime>>><br />
<<<kernel>>><br />
<<<mem>>><br />
<<<lnx_thermal>>><br />
<<<local>>><br />
0 "online" - online=1<br />
0 "serialnumber" - serialnumber=00155db3c306<br />
0 "product" - product=AppPlatform x86_64<br />
0 "version" - version=120010 (15r1 1510130 dvl )<br />
0 "versionIsSupported" - versionIsSupported=1<br />
<<<innovaphone>>><br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== Configure your Checkmk installation =====<br />
#Create a new Rule for "Individual program call instead of agent access" in "Setup > Agents > Other integrations"<br />
#*Command line to execute: <code>curl --digest -u "user:pass" https://ap.domain.tld/domain.de/techassist/monitoring/Checkmk</code><br />
#*Explicit hosts: Set this to the Host of your Application Platform<br />
#Make sure that "Checkmk agent / API integrations" in the Hostconfiguration of your Application Platform is set to "API integrations if configured, else Checkmk agent", all other Hosts hat to bet set to "No API integrations, no Checkmk agent".<br />
<br />
After that, you can run the service discovery and receive new checks for your devices<br />
<br />
[[File:Checkmk new checks.png|frameless|500px]]<br />
<br />
==== Icinga ====<br />
The interface "/Icinga" provides a native integration to your Icinga system for all known hosts.<br />
<br />
{{FIXME|reason=This interface is currently being researched, and it is being checked whether icinga can read such data as expected}}<br />
<br />
<spoiler show="show sample output" hide="hide sample output"><br />
<syntaxhighlight lang="javascript"><br />
[<br />
{<br />
"_host": "pbx.baebeca.de",<br />
"_ETH0_ipv4": "10.0.102.7",<br />
"online":1,<br />
"serialnumber":005056001338,<br />
"product":IPVA,<br />
"version":15r1 dvl [15.1.0130/1000/0],<br />
"versionIsSupported":1,<br />
"uptime":3353,<br />
"CPU":1,<br />
"CPU-R":0,<br />
"MEM":0.09,<br />
"ETH0":14<br />
},<br />
{<br />
"_host": "ap.baebeca.de",<br />
"_eth0_ipv4": "10.0.102.8",<br />
"_eth0_ipv6": "2001:4090:e000:9a1::8",<br />
"online":1,<br />
"serialnumber":00155db3c306,<br />
"product":AppPlatform x86_64,<br />
"version":120010 (15r1 1510130 dvl ),<br />
"versionIsSupported":1<br />
}<br />
]<br />
</syntaxhighlight><br />
</spoiler><br />
<br />
===== Configure your Icinga installation =====<br />
<br />
== Troubleshooting ==<br />
<br />
=== Startup Logfile ===<br />
If you enable the traceflag ''App'' in your App instance, you will find the following logs:<br />
<br />
AppService::AppStart TechAssist@slu.de<br />
App instance started 14C1363 14C1363<br />
...<br />
// App begins to load embedded tests<br />
JavaScript: Files tests/*<br />
...<br />
// Scheduler begins to load all the tests<br />
scheduler init<br />
init test "firmware_version"<br />
firmware_version: Test added successful<br />
init test "pbx_mediarelay"<br />
pbx_mediarelay: Test added successful</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference13r2:Gateway/Interfaces/SIP&diff=63471Reference13r2:Gateway/Interfaces/SIP2022-09-23T07:59:25Z<p>Twl: </p>
<hr />
<div>== SIP Registration section ==<br />
The entry fields for a '''SIP registration''' are:<br />
{|<br />
|valign=top nowrap=true|'''Name'''<br />
|Descriptive name for this registration.<br />
|-<br />
|valign=top nowrap=true|'''Disable'''<br />
|A switch to temporarily disable this interface without deleting the configuration.<br />
|-<br />
|valign=top nowrap=true|'''Type'''<br />
|<br />
*Provider: Creates a registration at a remote SIP server (of a SIP provider)<br />
*Open Federation: SIP/TLS interface without registration used to send and receive calls to federation partners.<br />
*Closed Federation: Like 'Open Federation' but even more restricted to pre-configured set of federation partners. In the 'Closed Federation' mode, the DNS queries for resolving the domain name of the federation partner are made without the '''Recursion Desired''' (RD) Flag. This means only DNS entries configured on the local DNS server are resolved, so the list of the partners for 'Closed Federation' must be maintained on the local DNS server.<br />
|-<br />
|valign=top nowrap=true|'''Transport'''<br />
|<br />
*UDP: SIP signaling using UDP as transport protocol (RFC 3261).<br />
*TCP: SIP signaling using TCP as transport protocol (RFC 3261).<br />
*TLS: SIP signaling using TLS as transport protocol (RFC 3261). [[Howto:Security works with innovaphone]]<br />
*Without registration: By default sip trunks are using with registration. Can be disabled here.<br />
|-<br />
|valign=top nowrap=true|'''AOR'''<br />
|Address of Record: SIP-URI used to register. Enter the registration ID followed by the SIP provider domain name (for example 8111111e0@sipgate.de or 8111111e0@x.x.x.x:5080 if you need to use the IP-address and a different Port number).<br />
|-<br />
|valign=top nowrap=true|'''Local Hostname'''<br />
|The Local Domain for SIP Federation enables to select the TLS Certificate according to the Domain Name. On the incoming SIP calls the host part of the URI is removed if equals with the Local Domain configured here, and the user part is used as Name (H323-ID) or Number (E164).<br />
|-<br />
|valign=top nowrap=true|'''Local Port'''<br />
|The local source port for SIP signalling can be configured here. If its empty a random port will be used. ''Dont use the same static port on multiple SIP Accounts!''<br />
|-<br />
|valign=top nowrap=true|'''Proxy'''<br />
|DNS name or IP address of the SIP proxy where SIP messages (REGISTER,INVITE,etc) are to be sent to. Proxy can be omitted if domain part of AOR can be used as remote signaling destination. (append ":<port>" if you need a different destination Port)<br />
|-<br />
|valign=top nowrap=true|'''STUN Server'''<br />
|The STUN servers to use. See [[{{NAMESPACE}}:IP4/General/STUN | STUN]] for details regarding the format. <br />
|}<br />
<br />
== Authorization ==<br />
Username and password for authorization. Username can be omitted if equal to userpart of AOR.<br />
<br />
== Media Properties ==<br />
<br />
The configuration of the media properties is evaluated for calls from/to this interface to/from a physical (ISDN, analog, TEST, ...) only. If media relay is active for a call using this interface an 'exclusive' coder config is used to prohibit the use of any other coder. This 'exclusive code media-relay' config can be used to solve interop problems with other equipment which does not support media renegotiation, because with this config no media renegotiation will be performed.<br />
<br />
For more information see [[{{NAMESPACE}}:Gateway/Interfaces/Media_Properties | Media Properties]] and [[Howto:Security works with innovaphone]]<br />
<br />
== SIP Interop Tweaks ==<br />
<br />
{|<br />
|valign=top nowrap=true|'''Proposed Registration Interval'''<br />
|Set in seconds, default is 120 seconds<br />
|-<br />
|valign=top nowrap=true|'''Accept INVITE's from Anywhere'''<br />
|If disabled, registered interfaces will reject INVITE's not coming from the SIP server with "305 Use Proxy".<br />
|-<br />
|valign=top nowrap=true|'''Enforce Sending Complete'''<br />
|Affects handling of "484 Address Incomplete" responses. If enabled and "484 Address Incomplete" is received, the call is cleared. If not enabled and "484 Address Incomplete" is received, the call is retained and re-initiated in case of new dialing digits.<br />
|-<br />
|valign=top nowrap=true|'''No Video'''<br />
|Removes Video Capabilities from outgoing media offer.<br />
|-<br />
<!--<br />
|valign=top nowrap=true|'''No Early Media'''<br />
|Ignore any SDP answer received before final connect response.<br />
|-<br />
|valign=top nowrap=true|'''No Inband Information on Error'''<br />
|Controls interworking of Q.931 DISC message. If this option is set, DISC message is always interworked into BYE request.<br />
|-<br />
|valign=top nowrap=true|'''No Inband Disconnect'''<br />
|TBD.<br />
|-<br />
|valign=top nowrap=true|'''No Remote Hold Signaling'''<br />
|Disables interworking of "inactive" into RemoteHold (affects connected SIP calls only).<br />
|-<br />
|valign=top nowrap=true|'''Take Refer-To URI as Remote Target URI'''<br />
|TBD.<br />
|-<br />
--><br />
|valign=top nowrap=true|'''To Header when Sending INVITE'''<br />
|Affects only outgoing diverted calls . <br />
*'''Called Party''': If set we write CDPN into To header of outgoing INVITE (and DGPN into History-Info header). <br />
*'''Original Called Party''': If set we write the DGPN into To header of outgoing INVITE (and CDPN into Request-URI).<br />
|-<br />
|valign=top nowrap=true|'''From Header when Sending INVITE'''<br />
|Controls the local URI (From header) of outgoing calls. Applys to registered interfaces only. <br />
*'''Fixed AOR''': Fixed AOR is used as From-URI regardless of the actual calling party number. <br />
*'''AOR with CGPN as Display''': Fixed AOR is used as From-URI and calling party number is added as display string. <br />
*'''CGPN in user part of URI''': Variable From-URI with actual calling party number.<br />
|-<br />
|valign=top nowrap=true|'''Identity Header when Sending INVITE'''<br />
|Controls the identity header (P-Preferred-Identity, P-Asserted-Identity and Remote-Party-Id) sent on outgoing calls<br />
*'''CGPN in user part of URI''': Variable Identity-URI with actual calling party number <br />
*'''Fixed AOR''': Fixed AOR is used as Identity-URI regardless of the actual calling party number<br />
*'''UUI''': the relayed call must include ''user-to-user-info'' (UUI). This UUI is used as Identity-URI. [[Howto:How_to_customize_the_From/Identity_header_value_at_SIP_interfaces|In the UUI]], the string <code>{initiator}</code> is replaced by the the call's ''diversion-info'' (a.k.a. ''leg-2-info'') if available or the calling party number otherwise<br />
|-<br />
|valign=top nowrap=true|'''Reliability of Provisional Responses'''<br />
|Controls the support of PRACK (RFC-3262). <br />
*'''Supported''': Supported as optional extension. <br />
*'''Required''': Required as mandatory extension. <br />
*'''Disabled''': Hide support for PRACK extension.<br />
|-<br />
|valign=top nowrap=true|'''Advanced'''<br />
|Allows the configuration of additional, not further documented, interop tweaks(e.g. /pai on). The same tweaks can be configured also globally(i.e. not for this SIP-Interface) at the SIP(or TSIP/SIPS)-module. Any tweaks configured at the SIP-Interface will overwrite globally configured tweaks.<br />
|}<br />
<br />
<br />
=== More frequently used ''Advanced'' Parameters ===<br />
There are some options which influence the stack behaviour to handle ambiguities in the SIP standard:<br />
<br />
; /pai on : send identity URI in <code>P-Asserted-Identity</code> header. By default, it is sent in the <code>P-Asserted-Identity</code> header for calls from the PBX to the endpoint, in the <code>P-Preferred-Identity</code> header otherwise<br />
; /ppi on : send identity URI in <code>P-Preferred-Identity</code> header <br />
<br />
Other options are available which instruct the stack to use non-standard or deprecated behaviour. Note that this should only be used in rare cases. Better have the vendor of your 3rd party SIP equipment fix its stack implementation:<br />
<br />
; /send-deprecated-diversion-header on : send call history information in the deprecated <code>Diversion</code> header in addition to the <code>History-Info</code> header <br />
; /single-audio-description : don't send SAVP+AVP, but SAVP or AVP media description in SDP<br />
; /no-authentication-info : don't send <code>Authentication-Info</code> header in REGISTER response<br />
; /send-no-historyinfo : don't send call history information (i.e. call forward) in outgoing Invite<br />
; /contact-addr [option] : adjust the Contact header to a fixed value necessary in scenarios of SIP Provider trunk without registration using TCP/TLS and uses Contact Header for Authentication. Example /contact-addr x.x.x.x:5061;user=phone;transport=TLS<br />
; /options-interval n : Send SIP options every "n" seconds to the configured remote SIP Address configured on the Interface.<br />
<br />
=== Extra Options ===<br />
{{3rd_Party_Input}}<br />
<br />
==== Disable Interworking of Hold Notifications to SIP Provider ====<br />
<br />
During the tests we concluded that when interworking the hold-notify message to SIP and sending to the SIP Provider two consecutive Re-Invites with "send-only" attributes, the IMS platform replies to the second re-invite with "inactive". By doing so this call is put on hold without any Music on Hold - just silence.<br />
To avoid this behaviour we need to disable the interworking of the hold-notify message by this setting: <br />
<br />
!config add SIP /no-hr-notify (Alternative: TSIP / SIPS)<br />
!config write<br />
!config activate<br />
<br />
==== SIP Options Interval (Optional) ====<br />
<br />
Some Provider uses SIP Options to monitor the SIP Trunks, so it's mandatory that Innovaphone replies to incoming SIP Options received. This is done by default. Additionally we can also send SIP Options to the SIP Proxy and have similar mechanism for redundancy. If the remote Proxy doesn't reply to outgoing SIP Options, the Innovaphone Gateway will send the call to the next interface. To enable sending of Options - messages, the following setting must be done:<br />
<br />
!config add SIP /options-interval 30 (Alternative: TSIP / SIPS)<br />
!config write<br />
!config activate<br />
<br />
This option will only take effect on connections "without registration". In connections with a registration there already exist a keep alive.<br />
<br />
==== Remove Comfort Noise (CN) Capability from SDP ====<br />
<br />
During the tests we found out that some specific 3rd party devices connected to the IMS network support only a single coder/payload in the offer. When doing the coder negotiation, this devices repeat the coder negotiation until they have only 1 coder in the offer or until they reach a specific number of retries. Since Innovaphone by default always include the payload 13 (Comfort Noise) in addition to the used voice coder/payload, this would make the remote device to do multiple re-invites to try to reach the single coder/payload in the offer.<br />
To avoid unnecessary signalling, we should disable the sending of Comfort Noise capability.<br />
<br />
!config add SIP /rem-cn-capability (Alternative: TSIP / SIPS)<br />
!config write<br />
!config activate<br />
<br />
==== Setting of P-Asserted ID instead of P-Preferred ID ====<br />
<br />
When using the feature of ReRouting the call (SIP 302 Move Temporary) to the SIP Trunk, the IMS platform checks the P-Asserted ID setting. By default we send as P-Preferred ID instead, so that will not work. As a result, we need to configure the following setting:<br />
<br />
!config add SIP /pai (Alternative: TSIP / SIPS)<br />
!config write<br />
!config activate</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference:IP73_WLAN_WiFi_Wireless_IP-Phone&diff=61668Reference:IP73 WLAN WiFi Wireless IP-Phone2022-04-06T13:09:29Z<p>Twl: </p>
<hr />
<div>This article describes the IP73 WLAN/WiFi wireless IP phone, differences to the deprecated IP62 Wireless IP phone and a list of compatible WLAN infrastructures.<br />
<br />
==Applies To==<br />
This information applies to:<br />
*innovaphone IP73 (50-00073-001)<br />
<br />
==Requirements==<br />
<br />
To perform configuration changes on the IP73 device a desktop programming kit (IP62/IP64/IP65/IP73) (Art.No. 50-00060-021 / Prod.ID DP1-UAAA/1A1) is required. The programming kit enables to connect the IP73 handset to a PC in order the configuration changes can be done using WinPDM software.<br />
<br />
==Feature Comparison==<br />
This chapter describes the differences in the feature sets between old and new WiFi handsets.<br />
<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"<br />
|+ Handset Features Matrix<br />
! Feature !! IP62 !! IP73 !! Description<br />
|-<br />
| Signaling Protocols || H.323/SIP || SIP only ||<br />
|-<br />
| Codecs || G.711, G.722, G.729 A || Opus Wideband, G.711, G.722, G.729 A/B/AB ||<br />
|-<br />
| Talk Time/ Standby Time || 15 h / 100 h || 10 h / 100 h || with U-APSD<br />
|-<br />
| WiFi Standards || 802.11 a/b/g/n || 802.11 a/b/g/n/ac, 802.11r, 802.11k || MCS 0-7 only, Fast BSS Transition (FT or 802.11r)<br />
|-<br />
| SSL Certificates || customer managed || preinstalled by innovaphone/customer managed ||<br />
|-<br />
| call diversion || ok || only with DTMF ||<br />
<br />
|-<br />
<br />
| Headset Connector || 2,5 mm || 3,5 mm ||<br />
<br />
|}<br />
<br />
Although the IP73 does not have access to a central LDAP phone book, the solution described in [[Reference9:PBX/Objects/Directory_Search]] can be used.<br />
<br />
==WLAN Infrastructure Compatibility==<br />
<br />
<br />
'''IMPORTANT''': Ask [mailto:presales_AT_innovaphone_D0T_com innovaphone Presales Team] for possible interop configuration recommendations and pitfalls before you order the WiFi equipment and start with the roll-out.<br />
<br />
Note that availability and combinations of controllers and access points may be subject to change by the manufacturer and are not in the responsability of innovaphone. Errors and omissions excepted.<br />
<br />
innovaphone does not support WLAN infrastructures not listed in this document.<br />
<br />
{|border="2" cellspacing="4" cellpadding="3" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse;empty-cells:show;"<br />
|+ Certified WLAN Platforms<br />
! Vendor !! AP Model(s) !! Controller Model(s) !! latest tested SW Version<br />
|-<br />
| Aruba ||AP 207, 214, 215, 224, 225, 275||7000/7200/9000/MX-VA-xxx||8.6.0.5<br />
|-<br />
| Aruba ||AP 304, 305, 314, 315, 324, 325, 334, 335, 344, 345, 504, 505, 514, 515, 534, 554, 555||7000/7200/9000/MX-VA-xxx|| 8.7.1.1<br />
|-<br />
| Cisco||AP 1702, 2702, 3702, 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130||3504, 5520, 8540, vWLC, Mobility Express Solution||8.10.105<br />
|-<br />
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9105, 9115, 9117, 9120, 9130||3504, 5520, 8540, vWLC, Mobility Express Solution||8.10.162<br />
|-<br />
| Cisco||AP 1702, 2702, 3702||Catalyst 9800||17.3.3<br />
|-<br />
| Cisco||AP 1832, 1852, 2802, 3802, 4800, 9115, 9117, 9120, 9130, 9136||Catalyst 9800||17.7.1<br />
|-<br />
| Cisco Meraki||MR20/MR30H/MR33/MR42/MR42E/MR52/MR53/MR53E/MR70/MR74/MR84 (802.11ac wave 2);MR36/MR44/MR46/MR46E/MR76/MR86 (802.11ax)||-||MR 27.7.1<br />
|-<br />
| Extreme Networks (Enterasys/IdentiFi) ||AP 3801, 3805, 3825, 3865, 3935|| Extreme Wireless C25, C35, C2110, C5110, C5210, v2110||10.51.10<br />
|-<br />
| Extreme Networks (Enterasys/IdentiFi) ||AP 122, 130, 230, 250, 550, 650|| Extreme Cloud ||AP 10.0r8, Cloud 20.1.1.3<br />
|-<br />
| Extreme Networks (Enterasys/IdentiFi) ||AP 310i/e, 410i/e, 505i/e, 510i/e, 360i/e, 460i/e, 560|| XCC Controllers E1120, E2120, E3120, VE6120/VE6125, VE6120H||05.16.01.0025<br />
|-<br />
| Extreme Networks (Enterasys/IdentiFi) || AP305c/cx, 410c, 460c, 510c/cx, 650|| Extreme Cloud C25, C35, C2110, C5110, C5210, v2110||AP 10.2.4.0, Cloud 20.1.1.3<br />
|-<br />
| Extreme Networks (Enterasys/IdentiFi) || AP310i/e, 410i/e, 460i/e, 510i/e, 650i|| Extreme WING NX 5500, 75xx, 9500, 9510, 9600, 9610, VX9000||7.5.2.0<br />
|-<br />
| Fortinet||AP1010/1014/1020/822/832, APU221EV/U223EV/U321EV/U323EV/U421EV/U423EV||MC1550/3x00/4x00/5000/6000<br>FortiWLC-50D ,200D, 500D, 1000D, 3000D<br>FWC- VM-50, 200, 500, 1000, 3000||8.5-2-5<br />
|-<br />
| Ruckus||SmartZone ZF R300, R310, T300, T310, R500, R510, H510, R600, R610, R710, R720||SmartZone platform, vSZ-(H,E,D), SZ100/300||5.2.0.0.699<br />
<br />
|}<br />
<br />
as of February 2022.<br />
<br />
=== DAS Compatibility ===<br />
[http://en.wikipedia.org/wiki/Distributed_antenna_system Distributed Antenna Systems (DAS)] provide a cost-effective solution for extending radio coverage inside large facilities. Simply put, a DAS can be seen as a long cable starting at a base station or access point to which many antennas are connected. While the architecture can be utilized to mitigate certain coverage issues, the innovaphone IP73 was not designed to accommodate for such RF environments. Furthermore it is difficult to ascertain and ensure WLAN reliability in regard to interference, capacity, roaming, location-based services, and some important [http://en.wikipedia.org/wiki/IEEE_802.11n 802.11n] features, such as [http://en.wikipedia.org/wiki/Multiple-input_multiple-output MIMO]. As a consequence thereof, innovaphone will not endorse nor provide RF support for WiFi deployments over any Distributed Antenna System.<br />
<br />
=== WPA3 Compatibility ===<br />
The IP73 already supports the configuration option for ''WPA3''. However, this should not yet be actively used.<br><br />
''WPA3'' is currently only recommended for demo purposes. Support for ''WPA3'' is implemented, but no successful interoperability tests have been performed. WPA3 is not recommended being used except for demo purposes.<br />
<br />
==Configuration==<br />
IP73 configuration is done via WinPDM-application available at [https://store.innovaphone.com the Software section of the innovaphone App Store]. Use of desktop programming kit (IP62/IP64/IP65) (50-00060-021) is required.<br />
===PBX Registration===<br />
====Authentication via client certificate====<br />
The recommended way to register an IP73 handset at the innovaphone PBX is SIP over TLS with authentication by a client certificate. The IP73 handset is delivered with a preinstalled device certificate already trusted by an innovaphone PBX.<br />
<br />
Prerequisites on the PBX for such type of authentication are:<br />
<br />
*The issuer of the IP73 client certificate is on the Trust List of the PBX gateway<br />
*The CN of the client certificate used by IP73 equals the MAC address of the IP73 itself (alternatively other CN and registration identity can be used)<br />
*User Object contains a Device with a Hardware Id matching the MAC address of the IP73<br />
<br />
On the IP73 following settings must be configured:<br />
*VoIP->SIP<br />
**SIP TLS client certificate: <select certificate with MAC address as CN> or <Automatic if preinstalled certificate is used><br />
**SIP Transport: TLS<br />
**Primary SIP proxy: <IP-address of the PBX><br />
**SIP proxy ID: <PBX system name><br />
**SIP proxy password: <no password is required><br />
**Registration and Authentication identity: MAC address<br />
<br />
====Authentication via username/hardware id and password====<br />
*VoIP->General->Endpoint ID: username or hardware id on User Object<br />
*VoIP->SIP<br />
**SIP Transport: TCP or UDP<br />
**SIP proxy password: <password on the User Object or PBX System password, depending on Users Device configuration><br />
**Registration and Authentication identity: Endpoint ID<br />
<br />
=== ICE/TURN ===<br />
ICE is enabled by default. It is required to provide STUN and TURN server configuration under VoIP->General to secure correct negotiation of media channels.<br />
<br />
=== Factory Reset ===<br />
You can use the local ''Admin menu'' on the Phone or the WinPDM Software (Rightclick on the device) to make a Factory Reset.<br />
<br />
==Troubleshooting==<br />
Log Options can be configured in the WinPDM software, under Device->Log.<br />
<br />
===Remote PCAP Tracing===<br />
You can activate the remote PCAP interface and Trace flags directly in the phone configuration (Admin Menu :: Logging :: Mode) or via WinPDM under Device->Log->PCAP capturing: RPCAP.<br />
<br />
Only IP traces are available via RPCAP, no innovaphone or device internal traces are logged.<br />
<br />
===PCAP to file via USB Tracing===<br />
It is possible to store PCAP trace file in the ''pcap'' folder on the handset by setting in the phone configuration (Admin Menu :: Logging :: Mode) or via WinPDM under Device->Log->PCAP capturing the option "PCAP to file".<br />
<br />
To access the file set Device -> General -> USB behavior to "Ask" and select "File transfer", when connect the handset to the WinPDM. Navigate to the folder ''pcap'' on the ''Handset diagnostics'' drive.<br />
<br />
===Trace Options===<br />
Following additional trace options are available:<br />
<br />
*WLAN Trace<br />
*Configuration Trace<br />
*GUI Trace<br />
*GLI Trace<br />
*Unite Trace<br />
*VoIP Trace<br />
*System Trace<br />
*Protector Trace<br />
*SaS Trace<br />
*Bluetooth Trace<br />
<br />
The resulting traces are available via USB file transfer and are encrypted. The encrypted log files can be encrypted by support only.<br />
<br />
===Logging via Syslog, SFTP or logfile===<br />
<br />
The handset can be configured to send Syslog messages to a Syslog server, an SFTP server or to a local logfile located in the folder ''tracelog''.<br />
<br />
The configuration is available via WinPDM Device -> Log -> Syslog or SFTP.<br />
<br />
===Handset Error Messages===<br />
<br />
====No network====<br />
The ''No network'' message indicates missing WLAN connection. It can be caused by wrong settings for SSID, Security, reg. domain and WLAN channels or lack of coverage.<br />
<br />
====No access====<br />
The ''No access'' message is caused by missing IP connectivity to the PBX or wrong configuration for authentication at the PBX.<br />
<br />
== Shortcuts ==<br />
<br />
There are additional hidden tools for information and analysing are available.<br />
<br />
;Handset Device Information<br />
:''*#34#'' in the main display<br />
<br />
;RSSI Indicator<br />
:''*#76#'' in the main display. Type again to exit.<br />
: Here you find the following information in the display:<br />
:* Line 1: SSID<br />
:* Line 2: Current AP<br />
:* Line 3: Current AP MAC<br />
:* Line 4: Previous AP<br />
:* Line 5: Previous AP MAC<br />
<br />
;Site Survey Tool<br />
:''*#77#'' in the main display.<br />
<br />
;Admin Menu<br />
: Go to the ''Settings menu'' and type in ''40022''<br />
<br />
==Known Problems==<br />
*A registration via Reverse Proxy with TLS authentication is not supported at the moment. A workaround with username/password can be implemented. A fix of the PBX software will follow.<br />
<br />
==Related Articles==<br />
*[[IP73 Technical Data EN]]<br />
*[[Reference:IP62 WLAN WiFi Wireless IP-Phone]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto13r1:Firewall_Settings&diff=57351Howto13r1:Firewall Settings2020-10-14T06:41:21Z<p>Twl: </p>
<hr />
<div><!-- Keywords: firewall settings, ports, workload, turn config, policies, firewall rules, firewall --><br />
==Applies To==<br />
This information applies to<br />
<br />
V13 and up<br />
<br />
==Scenario: Reverse Proxy in a DMZ==<br />
<br />
Here we would like to give an overview of the necessary ports and protocols for a reverse proxy in a DMZ.<br />
<br />
The scenario would be that a reverse proxy is used in a DMZ. The DMZ has a link to the WAN and LAN.<br />
<br />
===Configuration===<br />
<br />
*Before you can setup your Firewall you have to read the book [[Course13:IT_Connect_-_10.0_Reverse_Proxy|Reverse Proxy]] in the [[Special:Prefixindex/Course13:|V13 IT Connect Training]].<br />
* If you already have used some of the port forwards from the collumn ''WAN ⇒ DMZ'' for other Systems you have to combine all forwards in the reverse Proxy or use a separate ip address<br />
<br />
<br />
{| class="wikitable" border="1" cellspacing="0" cellpadding="10"<br />
! style="background-color: #EAECF0;text-align:center"|WAN &rArr; DMZ (Reverse Proxy) !! style="background-color: #EAECF0;text-align:center"|DMZ (Reverse Proxy) &rArr; inside (PBX) !! style="background-color: #EAECF0;text-align:center"|DMZ (Reverse Proxy) &rArr; inside (Application Platform) !! style="background-color: #EAECF0;text-align:center"|inside &rArr; DMZ (Reverse Proxy) !! style="background-color: #EAECF0;text-align:center"|DMZ (Reverse Proxy) &rArr; WAN<br />
|-<br />
| STUN/TURN (udp/tcp/3478) || / || / || STUN/TURN (udp/tcp/3478) || /<br />
|-<br />
| LDAPS (tcp/636)<br><br />
''&bull; <span style="font-size:11px;">optionally LDAP (tcp/389) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer LDAP lookups</span>''<br />
|| LDAPS (tcp/636)<br><br />
''&bull; <span style="font-size:11px;">optionally LDAP (tcp/389) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer LDAP lookups</span>''<br />
|| LDAPS (tcp/636)<br><br />
''&bull; <span style="font-size:11px;">optionally LDAP (tcp/389) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer LDAP lookups</span>''<br />
|| / <br />
|| /<br />
|-<br />
| HTTPS (tcp/443)<br><br />
''&bull; <span style="font-size:11px;">optionally HTTP (tcp/80) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer myApps</span>''<br><br />
''&bull; <span style="font-size:11px;">please also allow wss/ws (websocket) connections</span>''<br />
|| HTTPS (tcp/443)<br><br />
''&bull; <span style="font-size:11px;">optionally HTTP (tcp/80) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer myApps</span>''<br><br />
''&bull; <span style="font-size:11px;">please also allow wss/ws (websocket) connections</span>''<br />
|| HTTPS (tcp/443)<br><br />
''&bull; <span style="font-size:11px;">optionally HTTP (tcp/80) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer myApps</span>''<br><br />
''&bull; <span style="font-size:11px;">please also allow wss/ws (websocket) connections</span>''<br />
|| HTTPS (tcp/<your custom port>)<br><br />
''&bull; <span style="font-size:11px;">Advanced UI admin access</span>''<br />
|| / <br />
|-<br />
| H.323 (tcp/1300)<br><br />
''&bull; <span style="font-size:11px;">optionally H.323 (tcp/1720) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer Phone registrations</span>'' <br />
|| H.323 (tcp/1300)<br><br />
''&bull; <span style="font-size:11px;">optionally H.323 (tcp/1720) if you need plaintext or username/password auths with invalid certificates</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to offer Phone registrations</span>'' <br />
|| / <br />
|| / <br />
|| /<br />
|-<br />
| SIPS (tcp/5061)<br><br />
''&bull; <span style="font-size:11px;">optionally SIP (tcp/5060) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed '''only''' if you want to accept SIP registrations, i.e. for 3rd. Party SIP phones but not for SIP-Trunks</span>''<br />
|| SIPS (tcp/5061)<br><br />
''&bull; <span style="font-size:11px;">optionally SIP (tcp/5060) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed '''only''' if you want to accept SIP registrations, i.e. for 3rd. Party SIP phones but not for SIP-Trunks</span>''<br />
|| / <br />
|| /<br />
|| SIPS (tcp/5061)<br><br />
''&bull; <span style="font-size:11px;">optionally SIP (tcp/5060) if you need plaintext</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to register a SIP Trunk from the RP to Provider and your Provider doesn't support TURN</span>''<br />
|-<br />
| / || / || / || RTP (udp/16384-32767)<br><br />
''&bull; <span style="font-size:11px;">needed if you want to register a SIP Trunk from the RP to Provider and your Provider doesn't support TURN</span>'' <br />
|| RTP (udp/xxx)<br><br />
''&bull; <span style="font-size:11px;">negotiated in context of the outgoing sip/udp connecxtion</span>''<br><br />
''&bull; <span style="font-size:11px;">needed if you want to register a SIP Trunk from the RP to Provider and your Provider doesn't Support TURN</span>''<br />
|}<br />
<br />
=== The complete Workload Picture === <br />
<br />
[[Image:V13-workload.jpg|500px]]<br />
<br />
== Related Articles ==<br />
* [[Howto:Innovaphones_public_services]]<br />
* [[Course13:IT_Connect_-_10.0_Reverse_Proxy]]<br />
* [[Course12:Advanced_-_Reverse_Proxy]]<br />
<br />
[[Category:Howto|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Service_Voicemail&diff=57143Reference13r1:Concept App Service Voicemail2020-09-15T09:18:05Z<p>Twl: </p>
<hr />
<div>[[Category:Concept|Apps]]<br />
<br />
The App Services Voicemail is an App Service which can be installed on an innovaphone App Platform. It is used to store, delete and play the voicemails from the pbx. <br />
<br />
=Features=<br />
* Database for voicemails<br />
* Visual Voicemail notification in myApps, Voicemail App on all myApps capable devices<br />
* Delete, Play and Download Voicemails<br />
* MWI on IP phones<br />
* Email notification with a .wav attachment of the voicemail file<br />
* Available languages German, Danish, Dutch, English, Finnish, French, Italian, Norwegian, Polish, Portiuguese, Swedish, Spanish, and Czech<br />
* Custom XML voicemail scripts can be enabled<br />
<br />
=Requirements=<br />
innovaphone PBX and App Platform from on version 13r1<br />
<br />
=Details=<br />
<br />
=App Services=<br />
<br />
== innovaphone-voicemail==<br />
Main app to manage the voicemails. <br />
<br />
=Troubleshooting=<br />
=Known Problems=<br />
== Incomplete attachments in email notification == <br />
For details see [[Support:V13r1_voicemail_-_incomplete_attachments_in_email_notification]]<br />
= Related Articles =<br />
<!--optional bullet list, remove section if not needed--></div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto13r1:Firmware_Upgrade_V12r2_V13r1&diff=52569Howto13r1:Firmware Upgrade V12r2 V13r12019-06-28T10:46:07Z<p>Twl: /* Possible Migration scenarios */</p>
<hr />
<div>== Possible Migration scenarios == <br />
<br />
* PBX without Linux Application Platform or external Linux Application Platform <br />
** Update PBX<br />
** Installation App Platform (see below for more details)<br />
*** On local SSD (if Gateway is SSD capable) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br><br />
*PBX with Linux Application Platform on local SSD or CF-card<br />
** Update PBX<br />
** Installation App Platform (see below for more details)<br />
***On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br> <br />
* Virtual PBX (IPVA) without Linux Application Platform or external Linux Application Platform<br />
** Update PBX (IPVA)<br />
** Installation App Platform (see below for more details)<br />
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare)[http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br><br />
<br />
'''Changes that will be performed during the install/migration process:'''<br />
* CDR0 will be changed<br />
* DNS0 will be changed<br />
* LOG0 will be changed<br />
* IP0 /priority-tos will be changed<br />
* HTTP Client Authenticated URLs 1-n will be changed, depending on number of installed voicemails<br />
* HTTP, HTTPS Ports will be changed<br />
* STUN Server will be changed<br />
* TURN Server will be changed (Turn User & PW) <br />
* LDAP Server will be changed to "Force TLS", there for all replications and other LDAP accesses need to be changed to TLS<br />
* No of Regs w/o Pwd will be changed to "0"<br />
* PBX Object number will be changed to **1 <br><br><br />
All changes can be changed back to another or original value after the migration process manually if necessary.<br><br />
Make sure you store all these values upfront with a backup or manually.<br />
Always make a backup before you start a migration process.<br><br />
We advice to update all devices to the latest available Minor Release firmware version within your existing release before updating to V13.<br><br><br />
'''In this scenario example we show you the Migration steps: PBX with Linux Application Platform on a local SSD and we install an additional Gateway with SSD for the new AP Platform'''.<br><br><br />
Additional components who are necessary:<br />
* IPxx11 Gateway with new SSD<br />
* v13 Licenses<br><br><br />
<br />
== Preparation before you start ==<br />
* You have to disable ''Force HTTPS'' in the [[Reference13r1:Services/HTTP/Server|configuration]] before the update, because the installer is HTTP only<br />
** If you have forgot it and cannot reach the installer you have to access the advanced UI directly via https://ip/admin.xml?xsl=admin.xsl to deactivate it. After that you can open the installer<br />
<br />
== App Platform ==<br />
<br />
At first install the gateway with the new Application Platform.<br />
<br />
We assume it is in factory default. When a V13 firmware is already installed, you can access the gateway via its IP-address and you will get in the install GUI and can start the install process. If this is not the case, you can perform an update of the firmware to v13r1 via Maintenance, Update.<br />
<br />
''Tip: If an V13r1 is installed but you don't get the install gui immediately you can open it via [http://ipaddress/install.htm http://ipaddress/install.htm]<br />
* '''Install switch from HTTPS to HTTP, please be careful if you have deactivated HTTP, the redirection will fail''' !!<br />
<br />
''If not no secure passwords should be assigned automatically, you can use the default passwords by using the URL with a password switch [http://ipaddress/install.htm?stdpwd=on http://ipaddress/install.htm?stdpwd=on]. We recommend the use of secure passwords''<br />
<br />
''If the install doesn't start in your desired language or you want another language during the install process as the OS-language, use an appropriate language switch, for example ?lang=nl for Dutch or ?lang=en for English''<br />
<br />
<br><br />
<br />
As first you will be asked for the username and password of the gateway.<br />
<br />
As long as these are on the default values, you don't have to enter a value or just enter this default value.<br />
<br />
''Tip: On the right pane of the install you find the explanations for the parameters that you can fill out.''<br />
<br />
<br><br />
In the second step the install method will be asked.<br><br />
Here we select "Only update and network settings" to prepare the gateway for the installation of the App Platform.<br />
<br />
[[Image:Only update and network settings.png]]<br />
<br />
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway and the IP address of the App Platform.<br />
<br />
It is also possible to update the gateway to the latest possible firmware version.<br />
<br />
Be aware that if you choose for an update of the firmware, a restart will occur.<br />
<br />
[[Image:innovaphone PBX installation.png]]<br />
<br />
In the next step the App Platform will be downloaded and installed and started.<br />
<br><br />
<br />
[[Image:innovaphone App Platform.png]]<br />
<br />
== PBX ==<br />
<br />
After the App Platform is installed and started, we will follow-up with the update of the PBX (Master, in Distributed Systems).<br />
<br />
To proceed we need to install the latest version of the V13r1 firmware on the existing PBX.<br />
<br />
<br><br />
If the firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process.<br />
<br />
As first you will be asked for the username and password of the gateway.<br />
<br />
Here you enter the credential of the existing admin user (most of the time it is admin) of the gateway.<br />
<br />
The install will recognize that it is an existing PBX configuration and provides you with the appropriate Update scenarios.<br />
<br />
We choose for "Update existing PBX with installation of an external App Platform" as the selected scenario.<br />
<br />
''Tip: Be sure that you don't have any Object with H323 Name: "AP" in your config. If so you will have problems in connecting the AP Platform.''<br />
<br />
[[Image:Update existing PBX with installation of an external App Platform.png]]<br />
<br />
<br />
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway.<br />
<br />
It is also possible to update the gateway to the latest possible firmware version.<br />
<br />
Be aware that if you choose for an update of the firmware, a restart will occur.<br />
<br />
[[Image:innovaphone PBX installation2.png]]<br />
<br />
In the step, "Connect to external App Platform" we connect the PBX with the pre-defines gateway with the App Platform.<br />
<br />
To proceed we enter the IP-address off the App-Platform and its password.<br />
<br />
After pressing connect and a successful connection it will show connected.<br />
<br />
''Tip: The default password for the App-Platform is "pwd". If you don't enter a password the default password will be used automatically. If you changed the password on the App-Platform into a more secure password yourself before starting the Install to update the PBX, Be sure you use this same password to connect. Otherwise the connection will fail and the install can't proceed.''<br />
<br />
<br><br />
''Tip: With the search option you can searh for available App-platform in your network that are installed on a gateway. It is required that this gateway was in default factory setting.''<br />
<br />
''A search is not possible for an App-platforms that runs on a virtual machine. This can only be accessed via its IP-address.''<br />
<br />
<br />
[[Image:Connect to external App Platform.png]]<br />
<br />
<br />
Tip: When the next step will follow with "Connect to Devices" the there was already an entry in the advanced user interface in<br />
<br />
''General/Devices Registration''). Clear this entry and restart the Install process again.<br><br><br />
<br />
In the following step "innovaphone PBX Options" you enter the configuration just as you have seen and learned during the iT Connect op iT Update training.<br />
<br />
Here the PBX name and Domain name (System name) should match with your configuration.<br />
<br />
''Tip: As user please add an additional (not existing) new user as myApps Admin. Name and mail cannot be in use already.''<br />
<br><br />
''Tip: At the moment only lower case PBX names can be used. In case the PBX you want to update is using upper case you have to change it to lower case (at the moment) and your phones will loose registration. Later on you have to change the PBX entries of all objects to lower case.''<br><br />
In the following step "Emergency Administrator password, please save secure" the passwords will NOT be created randomly as you have learned during the iT Connect Training. The existing passwords of the PBX system remain as they are.<br />
<br><br />
<br />
In the following steps the configurations will be done as learned during your iT Connect Training.<br />
<br><br />
After finishing all the install steps, you can login into the system with the previously define myApps Admin in the myApps client.<br />
<br />
''Tip: If you cant login with the myApps Admin User, go to the Advanced User Interface ([https://ip.addr/admin.xml?xsl=admin.xsl https://ip.addr/admin.xml?xsl=admin.xsl]) and assign an existing user object the Template "Config Admin". You can then login with this user into myApps.''<br />
<br><br />
As mentioned in the beginning , know you can change your saved and special settings back to its original state if this is necessary for your configuration.<br />
<br><br />
To give the existing users the possibility to use the innovaphone myApps, you should inherit the existing templates to the new template "Config User". If the user didn't have any template at all, then assign them o the template "Config User".<br />
<br />
''Tip: The Users are only seen in Users App if they have the "Visible" flag in Visibility set. This is mostly done by Config Templates. So be aware that if you have another Config Template in use (that has not set the Visibility flag) even if you inheritate it from Config User it will not overwrite the older settings. So choose here the Visibility flag afterwards.'' <br />
<br />
[[Image:Change template.png]]<br />
<br />
''Tip: Assign Administrative users to the new template "Config Admin".''<br />
<br />
''Tip: In case you are using Apps that need a License the selectable box under License only appear after uploading the necessary license. In test mode everything works. So in case you are using test mode it is better to first upload your licenses, select the license boxes and than deactivate your test mode!<br />
<br />
== Provisioning ==<br />
<br />
If you want to use Provisioning and you are using Update Server/PHP Update Server 2 you have to consider that your phone needs to reach config.innovaphone.com via Update URL.<br><br />
That means that if you already provide an Update URL via DHCP that the Provisioning process will not be possible. Therefore delete the Update URL in your DHCP Server. <br><br />
In case you are using Update Server/PHP Update Server 2 for Certificates etc. your phone needs to reach your old Update Server after provisioning again. (further details will follow)<br><br />
<br />
Please Check: [[Reference13r1:Services/Update]]<br />
<br />
== Assign Hardware of a User to a phone or softwarephone App ==<br />
<br />
This can be done by the administrator in UsersAdmin App.<br> <br />
Alternative the User can do this via his Profile. At the instruction from myApps the user can be shown on which point he can assign the app. <br />
<br />
[[Image:Profile PhoneApp.png]]<br />
<br />
== Reverse Proxy ==<br />
<br />
Via the advanced user interface install the latest V13r1 firmware.<br />
<br />
In the next step we need the Devices App URL. Via the advanced user interface, in General/Devices Registration/Devices App URL.<br />
<br />
Copy this URL.<br />
<br />
<br />
[[Image:Device Registration2.png]]<br />
<br />
Paste this URL in the advanced user interface of the Reverse Proxy in the field General/Devices Registration/Devices App URL.<br />
<br />
From now on this device can be found in the Devices App in Devices.<br />
<br />
The MAC address and a wrench symbol will be displayed.<br />
<br />
Here you can now assign a meaningful name and the domain to the device.<br />
<br />
<br />
[[Image:Devices.png]]<br />
<br />
Via Categories you should assign this gateway also to the appropriate Category.<br />
<br><br />
<br />
[[Image:Devices2.png]]<br />
<br />
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''<br />
<br />
''These include at least: Alarmserver Global, Media Global, NTP-settings''<br />
<br><br />
<br />
Via the PBX Manager App and the Reverse Proxy plugin you can now configure the Reverse Proxy.<br />
<br />
You should add here a new Host entry for the App Platform in the Reverse Proxy via the option "Add Host".<br />
<br />
The DNS name of the App Platform will be displayed in the next step. Select the DNS name and it will be added to the Reverse Proxy entries.<br />
<br />
Via the advanced user interface you have to change the hostnames for every PBX (Slaves and Standby).<br />
<br><br />
<br />
In the first http forward field you need to enter the following string /PBX0/APPCLIENT/appclient.htm and forward it to the appropriate IP-address with the port numbers 80 and 443 and tag the checkbox Default.<br />
<br><br />
<br />
At least the following entries should be available as shown in the picture below.<br />
<br><br />
<br />
[[Image:Reverse Proxy Entries.png]]<br />
<br><br />
<br />
== STUN / TURN / Slave / Standby / DECT ==<br />
<br />
If you want to have access to the gateway to enter the install process, you have to enter the admin credentials to login.<br />
<br />
In the next step select "Manual Configuration" and you will enter the Advanced User Interface.<br />
<br />
Install the latest V13r1 firmware.<br />
<br />
In the following step we need the Device URL which can be found on two different ways.<br />
<br />
<!--<br />
# Via the App Manager, in Settings/General/Devices app URL , we copy the complete URL <br> <br><br />
<br />
<br><br />
<br />
[[Image:App Manager.png]]<br />
<br />
--><br />
<br />
# Via the Advanced User Interface of the PBX<br />
In General/Devices Registration/Devices App URL copy the complete URL.<br />
<br />
[[Image:Device Registration2.png]]<br />
<br />
<br />
Paste this URL via the Advanced User Interface of the Reverse Proxy Gateway in General/Devices Registration/Devices App URL .<br />
<br />
Now you can find this Gateway in the Devices App within Devices. It will be displayed with its MAC-address and a wrench symbol.<br />
<br />
Here you can now assign a meaningful name and the domain to the device.<br />
<br />
[[Image:Devices.png]]<br />
<br />
Via Category you should assign the Gateway to the appropriate category.<br />
<br />
<br />
[[Image:Devices2.png]]<br />
<br />
<br />
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''<br />
<br />
''These include at least: Alarmserver Global, Media Global, NTP-settings''<br />
<br />
''Tip: For a Slave, Standby PBX or DECT you should select TLS as Replication protocol.''<br />
<br />
== Configuration Changes ==<br />
=== SNMP disabled by default ===<br />
Up and including v12r2, SNMP was by default activated on a innovaphone device. In v13 it is by default deactivated, it can be activated by a new [[Reference13r1:Services/SNMP | Enable Checkmark]]. As a result, if you upgrade to v13 firmware SNMP is deactivated and needs to be enabled if SNMP is needed in the customer setup.<br />
<br />
===Config line size was increased to 32KB===<br />
<br />
Downgrade from 13r1 to 12r2 (or older firmware) will result in objects with a too large [[Howto:Config_size_Limitations#Global | config line]] being dropped.<br />
<br />
===PBX name in v13 can't include uppercase letter===<br />
<br />
So you should change it in your configuration in V12 before the upgrade of PBX.<br />
<br />
== Known issues ==<br />
* For the known issues, please have a look into our [http://wiki.innovaphone.com/index.php?title=Support:DVL-Roadmap_Firmware_13r1 Support:DVL-Roadmap Firmware 13r1]<br />
* [[Support:IP10x/IP11x_VLAN_configuration_disturbs_various_functions_in_V13r1_beta/final/sr1]]<br />
<br />
== Related Articles ==<br />
*[[Howto:Guideline V5 to V6 upgrade]]<br />
*[[Howto:Upgrade Issues V5 to V6]]<br />
*[[Howto:Firmware Upgrade V6 V7]]<br />
*[[Howto:Firmware Upgrade V7 V8]]<br />
*[[Howto:Firmware Upgrade V8 V9]]<br />
*[[Howto:Firmware Upgrade V9 V10]]<br />
*[[Howto:Firmware Upgrade V10 V11r1]]<br />
*[[Howto:Firmware Upgrade V11r1 V11r2]]<br />
*[[Support:Special_Precaution_required_when_upgrading_IPxx11_Gateways_from_pre-SR14_Firmware_Versions]]<br />
* [[Howto:Firmware Upgrade V11r2 V12r1]]<br />
* [[Howto:Firmware Upgrade V12r1 V12r2]]<br />
[[Category:Howto|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto13r1:Firmware_Upgrade_V12r2_V13r1&diff=52568Howto13r1:Firmware Upgrade V12r2 V13r12019-06-28T10:44:47Z<p>Twl: /* Possible Migration scenarios */</p>
<hr />
<div>== Possible Migration scenarios == <br />
<br />
* PBX without Linux Application Platform or external Linux Application Platform <br />
** Update PBX<br />
** Installation App Platform (see below for more details)<br />
*** On local SSD (if Gateway is SSD capable) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br><br />
*PBX with Linux Application Platform on local SSD or CF-card<br />
** Update PBX<br />
** Installation App Platform (see below for more details)<br />
***On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br> <br />
* Virtual PBX (IPVA) without Linux Application Platform or external Linux Application Platform<br />
** Update PBX (IPVA)<br />
** Installation App Platform (see below for more details)<br />
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare)[http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br><br />
<br />
'''Changes that will be performed during the install/migration process:'''<br />
* CDR0 will be changed<br />
* DNS0 will be changed<br />
* LOG0 will be changed<br />
* IP0 /priority-tos will be changed<br />
* HTTP Client Authenticated URLs 1-x will be changed, depending on number of installed voicemails<br />
* HTTP, HTTPS Ports will be changed<br />
* STUN Server will be changed<br />
* TURN Server will be changed (Turn User & PW) <br />
* LDAP Server will be changed to "Force TLS", there for all replications and other LDAP accesses need to be changed to TLS<br />
* No of Regs w/o Pwd will be changed to "0"<br />
* PBX Object number will be changed to **1 <br><br><br />
All changes can be changed back to another or original value after the migration process manually if necessary.<br><br />
Make sure you store all these values upfront with a backup or manually.<br />
Always make a backup before you start a migration process.<br><br />
We advice to update all devices to the latest available Minor Release firmware version within your existing release before updating to V13.<br><br><br />
'''In this scenario example we show you the Migration steps: PBX with Linux Application Platform on a local SSD and we install an additional Gateway with SSD for the new AP Platform'''.<br><br><br />
Additional components who are necessary:<br />
* IPxx11 Gateway with new SSD<br />
* v13 Licenses<br><br><br />
<br />
== Preparation before you start ==<br />
* You have to disable ''Force HTTPS'' in the [[Reference13r1:Services/HTTP/Server|configuration]] before the update, because the installer is HTTP only<br />
** If you have forgot it and cannot reach the installer you have to access the advanced UI directly via https://ip/admin.xml?xsl=admin.xsl to deactivate it. After that you can open the installer<br />
<br />
== App Platform ==<br />
<br />
At first install the gateway with the new Application Platform.<br />
<br />
We assume it is in factory default. When a V13 firmware is already installed, you can access the gateway via its IP-address and you will get in the install GUI and can start the install process. If this is not the case, you can perform an update of the firmware to v13r1 via Maintenance, Update.<br />
<br />
''Tip: If an V13r1 is installed but you don't get the install gui immediately you can open it via [http://ipaddress/install.htm http://ipaddress/install.htm]<br />
* '''Install switch from HTTPS to HTTP, please be careful if you have deactivated HTTP, the redirection will fail''' !!<br />
<br />
''If not no secure passwords should be assigned automatically, you can use the default passwords by using the URL with a password switch [http://ipaddress/install.htm?stdpwd=on http://ipaddress/install.htm?stdpwd=on]. We recommend the use of secure passwords''<br />
<br />
''If the install doesn't start in your desired language or you want another language during the install process as the OS-language, use an appropriate language switch, for example ?lang=nl for Dutch or ?lang=en for English''<br />
<br />
<br><br />
<br />
As first you will be asked for the username and password of the gateway.<br />
<br />
As long as these are on the default values, you don't have to enter a value or just enter this default value.<br />
<br />
''Tip: On the right pane of the install you find the explanations for the parameters that you can fill out.''<br />
<br />
<br><br />
In the second step the install method will be asked.<br><br />
Here we select "Only update and network settings" to prepare the gateway for the installation of the App Platform.<br />
<br />
[[Image:Only update and network settings.png]]<br />
<br />
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway and the IP address of the App Platform.<br />
<br />
It is also possible to update the gateway to the latest possible firmware version.<br />
<br />
Be aware that if you choose for an update of the firmware, a restart will occur.<br />
<br />
[[Image:innovaphone PBX installation.png]]<br />
<br />
In the next step the App Platform will be downloaded and installed and started.<br />
<br><br />
<br />
[[Image:innovaphone App Platform.png]]<br />
<br />
== PBX ==<br />
<br />
After the App Platform is installed and started, we will follow-up with the update of the PBX (Master, in Distributed Systems).<br />
<br />
To proceed we need to install the latest version of the V13r1 firmware on the existing PBX.<br />
<br />
<br><br />
If the firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process.<br />
<br />
As first you will be asked for the username and password of the gateway.<br />
<br />
Here you enter the credential of the existing admin user (most of the time it is admin) of the gateway.<br />
<br />
The install will recognize that it is an existing PBX configuration and provides you with the appropriate Update scenarios.<br />
<br />
We choose for "Update existing PBX with installation of an external App Platform" as the selected scenario.<br />
<br />
''Tip: Be sure that you don't have any Object with H323 Name: "AP" in your config. If so you will have problems in connecting the AP Platform.''<br />
<br />
[[Image:Update existing PBX with installation of an external App Platform.png]]<br />
<br />
<br />
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway.<br />
<br />
It is also possible to update the gateway to the latest possible firmware version.<br />
<br />
Be aware that if you choose for an update of the firmware, a restart will occur.<br />
<br />
[[Image:innovaphone PBX installation2.png]]<br />
<br />
In the step, "Connect to external App Platform" we connect the PBX with the pre-defines gateway with the App Platform.<br />
<br />
To proceed we enter the IP-address off the App-Platform and its password.<br />
<br />
After pressing connect and a successful connection it will show connected.<br />
<br />
''Tip: The default password for the App-Platform is "pwd". If you don't enter a password the default password will be used automatically. If you changed the password on the App-Platform into a more secure password yourself before starting the Install to update the PBX, Be sure you use this same password to connect. Otherwise the connection will fail and the install can't proceed.''<br />
<br />
<br><br />
''Tip: With the search option you can searh for available App-platform in your network that are installed on a gateway. It is required that this gateway was in default factory setting.''<br />
<br />
''A search is not possible for an App-platforms that runs on a virtual machine. This can only be accessed via its IP-address.''<br />
<br />
<br />
[[Image:Connect to external App Platform.png]]<br />
<br />
<br />
Tip: When the next step will follow with "Connect to Devices" the there was already an entry in the advanced user interface in<br />
<br />
''General/Devices Registration''). Clear this entry and restart the Install process again.<br><br><br />
<br />
In the following step "innovaphone PBX Options" you enter the configuration just as you have seen and learned during the iT Connect op iT Update training.<br />
<br />
Here the PBX name and Domain name (System name) should match with your configuration.<br />
<br />
''Tip: As user please add an additional (not existing) new user as myApps Admin. Name and mail cannot be in use already.''<br />
<br><br />
''Tip: At the moment only lower case PBX names can be used. In case the PBX you want to update is using upper case you have to change it to lower case (at the moment) and your phones will loose registration. Later on you have to change the PBX entries of all objects to lower case.''<br><br />
In the following step "Emergency Administrator password, please save secure" the passwords will NOT be created randomly as you have learned during the iT Connect Training. The existing passwords of the PBX system remain as they are.<br />
<br><br />
<br />
In the following steps the configurations will be done as learned during your iT Connect Training.<br />
<br><br />
After finishing all the install steps, you can login into the system with the previously define myApps Admin in the myApps client.<br />
<br />
''Tip: If you cant login with the myApps Admin User, go to the Advanced User Interface ([https://ip.addr/admin.xml?xsl=admin.xsl https://ip.addr/admin.xml?xsl=admin.xsl]) and assign an existing user object the Template "Config Admin". You can then login with this user into myApps.''<br />
<br><br />
As mentioned in the beginning , know you can change your saved and special settings back to its original state if this is necessary for your configuration.<br />
<br><br />
To give the existing users the possibility to use the innovaphone myApps, you should inherit the existing templates to the new template "Config User". If the user didn't have any template at all, then assign them o the template "Config User".<br />
<br />
''Tip: The Users are only seen in Users App if they have the "Visible" flag in Visibility set. This is mostly done by Config Templates. So be aware that if you have another Config Template in use (that has not set the Visibility flag) even if you inheritate it from Config User it will not overwrite the older settings. So choose here the Visibility flag afterwards.'' <br />
<br />
[[Image:Change template.png]]<br />
<br />
''Tip: Assign Administrative users to the new template "Config Admin".''<br />
<br />
''Tip: In case you are using Apps that need a License the selectable box under License only appear after uploading the necessary license. In test mode everything works. So in case you are using test mode it is better to first upload your licenses, select the license boxes and than deactivate your test mode!<br />
<br />
== Provisioning ==<br />
<br />
If you want to use Provisioning and you are using Update Server/PHP Update Server 2 you have to consider that your phone needs to reach config.innovaphone.com via Update URL.<br><br />
That means that if you already provide an Update URL via DHCP that the Provisioning process will not be possible. Therefore delete the Update URL in your DHCP Server. <br><br />
In case you are using Update Server/PHP Update Server 2 for Certificates etc. your phone needs to reach your old Update Server after provisioning again. (further details will follow)<br><br />
<br />
Please Check: [[Reference13r1:Services/Update]]<br />
<br />
== Assign Hardware of a User to a phone or softwarephone App ==<br />
<br />
This can be done by the administrator in UsersAdmin App.<br> <br />
Alternative the User can do this via his Profile. At the instruction from myApps the user can be shown on which point he can assign the app. <br />
<br />
[[Image:Profile PhoneApp.png]]<br />
<br />
== Reverse Proxy ==<br />
<br />
Via the advanced user interface install the latest V13r1 firmware.<br />
<br />
In the next step we need the Devices App URL. Via the advanced user interface, in General/Devices Registration/Devices App URL.<br />
<br />
Copy this URL.<br />
<br />
<br />
[[Image:Device Registration2.png]]<br />
<br />
Paste this URL in the advanced user interface of the Reverse Proxy in the field General/Devices Registration/Devices App URL.<br />
<br />
From now on this device can be found in the Devices App in Devices.<br />
<br />
The MAC address and a wrench symbol will be displayed.<br />
<br />
Here you can now assign a meaningful name and the domain to the device.<br />
<br />
<br />
[[Image:Devices.png]]<br />
<br />
Via Categories you should assign this gateway also to the appropriate Category.<br />
<br><br />
<br />
[[Image:Devices2.png]]<br />
<br />
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''<br />
<br />
''These include at least: Alarmserver Global, Media Global, NTP-settings''<br />
<br><br />
<br />
Via the PBX Manager App and the Reverse Proxy plugin you can now configure the Reverse Proxy.<br />
<br />
You should add here a new Host entry for the App Platform in the Reverse Proxy via the option "Add Host".<br />
<br />
The DNS name of the App Platform will be displayed in the next step. Select the DNS name and it will be added to the Reverse Proxy entries.<br />
<br />
Via the advanced user interface you have to change the hostnames for every PBX (Slaves and Standby).<br />
<br><br />
<br />
In the first http forward field you need to enter the following string /PBX0/APPCLIENT/appclient.htm and forward it to the appropriate IP-address with the port numbers 80 and 443 and tag the checkbox Default.<br />
<br><br />
<br />
At least the following entries should be available as shown in the picture below.<br />
<br><br />
<br />
[[Image:Reverse Proxy Entries.png]]<br />
<br><br />
<br />
== STUN / TURN / Slave / Standby / DECT ==<br />
<br />
If you want to have access to the gateway to enter the install process, you have to enter the admin credentials to login.<br />
<br />
In the next step select "Manual Configuration" and you will enter the Advanced User Interface.<br />
<br />
Install the latest V13r1 firmware.<br />
<br />
In the following step we need the Device URL which can be found on two different ways.<br />
<br />
<!--<br />
# Via the App Manager, in Settings/General/Devices app URL , we copy the complete URL <br> <br><br />
<br />
<br><br />
<br />
[[Image:App Manager.png]]<br />
<br />
--><br />
<br />
# Via the Advanced User Interface of the PBX<br />
In General/Devices Registration/Devices App URL copy the complete URL.<br />
<br />
[[Image:Device Registration2.png]]<br />
<br />
<br />
Paste this URL via the Advanced User Interface of the Reverse Proxy Gateway in General/Devices Registration/Devices App URL .<br />
<br />
Now you can find this Gateway in the Devices App within Devices. It will be displayed with its MAC-address and a wrench symbol.<br />
<br />
Here you can now assign a meaningful name and the domain to the device.<br />
<br />
[[Image:Devices.png]]<br />
<br />
Via Category you should assign the Gateway to the appropriate category.<br />
<br />
<br />
[[Image:Devices2.png]]<br />
<br />
<br />
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''<br />
<br />
''These include at least: Alarmserver Global, Media Global, NTP-settings''<br />
<br />
''Tip: For a Slave, Standby PBX or DECT you should select TLS as Replication protocol.''<br />
<br />
== Configuration Changes ==<br />
=== SNMP disabled by default ===<br />
Up and including v12r2, SNMP was by default activated on a innovaphone device. In v13 it is by default deactivated, it can be activated by a new [[Reference13r1:Services/SNMP | Enable Checkmark]]. As a result, if you upgrade to v13 firmware SNMP is deactivated and needs to be enabled if SNMP is needed in the customer setup.<br />
<br />
===Config line size was increased to 32KB===<br />
<br />
Downgrade from 13r1 to 12r2 (or older firmware) will result in objects with a too large [[Howto:Config_size_Limitations#Global | config line]] being dropped.<br />
<br />
===PBX name in v13 can't include uppercase letter===<br />
<br />
So you should change it in your configuration in V12 before the upgrade of PBX.<br />
<br />
== Known issues ==<br />
* For the known issues, please have a look into our [http://wiki.innovaphone.com/index.php?title=Support:DVL-Roadmap_Firmware_13r1 Support:DVL-Roadmap Firmware 13r1]<br />
* [[Support:IP10x/IP11x_VLAN_configuration_disturbs_various_functions_in_V13r1_beta/final/sr1]]<br />
<br />
== Related Articles ==<br />
*[[Howto:Guideline V5 to V6 upgrade]]<br />
*[[Howto:Upgrade Issues V5 to V6]]<br />
*[[Howto:Firmware Upgrade V6 V7]]<br />
*[[Howto:Firmware Upgrade V7 V8]]<br />
*[[Howto:Firmware Upgrade V8 V9]]<br />
*[[Howto:Firmware Upgrade V9 V10]]<br />
*[[Howto:Firmware Upgrade V10 V11r1]]<br />
*[[Howto:Firmware Upgrade V11r1 V11r2]]<br />
*[[Support:Special_Precaution_required_when_upgrading_IPxx11_Gateways_from_pre-SR14_Firmware_Versions]]<br />
* [[Howto:Firmware Upgrade V11r2 V12r1]]<br />
* [[Howto:Firmware Upgrade V12r1 V12r2]]<br />
[[Category:Howto|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto13r1:Firmware_Upgrade_V12r2_V13r1&diff=52567Howto13r1:Firmware Upgrade V12r2 V13r12019-06-28T10:44:25Z<p>Twl: </p>
<hr />
<div>== Possible Migration scenarios == <br />
<br />
* PBX without Linux Application Platform or external Linux Application Platform <br />
** Update PBX<br />
** Installation App Platform (see below for more details)<br />
*** On local SSD (if Gateway is SSD capable) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br><br />
*PBX with Linux Application Platform on local SSD or CF-card<br />
** Update PBX<br />
** Installation App Platform (see below for more details)<br />
***On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare) [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br> <br />
* Virtual PBX (IPVA) without Linux Application Platform or external Linux Application Platform<br />
** Update PBX (IPVA)<br />
** Installation App Platform (see below for more details)<br />
*** On external Gateway with SSD [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#ARM_Gateway Installation of AP Platform on SSD] <br />
*** On virtual machine (Hyper-V or VMWare)[http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 Installation of Virtual App Platform] <br><br><br />
<br />
'''Changes that will be performed during the install/migration process:'''<br />
* CDR0 will be changed<br />
* DNS0 will be changed<br />
* LOG0 will be changed<br />
* IP0 /priority-tos will be changed<br />
* HTTP Client Authenticated URLs 1- will be changed, depending on number of installed voicemails<br />
* HTTP, HTTPS Ports will be changed<br />
* STUN Server will be changed<br />
* TURN Server will be changed (Turn User & PW) <br />
* LDAP Server will be changed to "Force TLS", there for all replications and other LDAP accesses need to be changed to TLS<br />
* No of Regs w/o Pwd will be changed to "0"<br />
* PBX Object number will be changed to **1 <br><br><br />
All changes can be changed back to another or original value after the migration process manually if necessary.<br><br />
Make sure you store all these values upfront with a backup or manually.<br />
Always make a backup before you start a migration process.<br><br />
We advice to update all devices to the latest available Minor Release firmware version within your existing release before updating to V13.<br><br><br />
'''In this scenario example we show you the Migration steps: PBX with Linux Application Platform on a local SSD and we install an additional Gateway with SSD for the new AP Platform'''.<br><br><br />
Additional components who are necessary:<br />
* IPxx11 Gateway with new SSD<br />
* v13 Licenses<br><br><br />
<br />
== Preparation before you start ==<br />
* You have to disable ''Force HTTPS'' in the [[Reference13r1:Services/HTTP/Server|configuration]] before the update, because the installer is HTTP only<br />
** If you have forgot it and cannot reach the installer you have to access the advanced UI directly via https://ip/admin.xml?xsl=admin.xsl to deactivate it. After that you can open the installer<br />
<br />
== App Platform ==<br />
<br />
At first install the gateway with the new Application Platform.<br />
<br />
We assume it is in factory default. When a V13 firmware is already installed, you can access the gateway via its IP-address and you will get in the install GUI and can start the install process. If this is not the case, you can perform an update of the firmware to v13r1 via Maintenance, Update.<br />
<br />
''Tip: If an V13r1 is installed but you don't get the install gui immediately you can open it via [http://ipaddress/install.htm http://ipaddress/install.htm]<br />
* '''Install switch from HTTPS to HTTP, please be careful if you have deactivated HTTP, the redirection will fail''' !!<br />
<br />
''If not no secure passwords should be assigned automatically, you can use the default passwords by using the URL with a password switch [http://ipaddress/install.htm?stdpwd=on http://ipaddress/install.htm?stdpwd=on]. We recommend the use of secure passwords''<br />
<br />
''If the install doesn't start in your desired language or you want another language during the install process as the OS-language, use an appropriate language switch, for example ?lang=nl for Dutch or ?lang=en for English''<br />
<br />
<br><br />
<br />
As first you will be asked for the username and password of the gateway.<br />
<br />
As long as these are on the default values, you don't have to enter a value or just enter this default value.<br />
<br />
''Tip: On the right pane of the install you find the explanations for the parameters that you can fill out.''<br />
<br />
<br><br />
In the second step the install method will be asked.<br><br />
Here we select "Only update and network settings" to prepare the gateway for the installation of the App Platform.<br />
<br />
[[Image:Only update and network settings.png]]<br />
<br />
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway and the IP address of the App Platform.<br />
<br />
It is also possible to update the gateway to the latest possible firmware version.<br />
<br />
Be aware that if you choose for an update of the firmware, a restart will occur.<br />
<br />
[[Image:innovaphone PBX installation.png]]<br />
<br />
In the next step the App Platform will be downloaded and installed and started.<br />
<br><br />
<br />
[[Image:innovaphone App Platform.png]]<br />
<br />
== PBX ==<br />
<br />
After the App Platform is installed and started, we will follow-up with the update of the PBX (Master, in Distributed Systems).<br />
<br />
To proceed we need to install the latest version of the V13r1 firmware on the existing PBX.<br />
<br />
<br><br />
If the firmware V13r1 is installed, you can access the gateway via its IP-address and you enter into the install process.<br />
<br />
As first you will be asked for the username and password of the gateway.<br />
<br />
Here you enter the credential of the existing admin user (most of the time it is admin) of the gateway.<br />
<br />
The install will recognize that it is an existing PBX configuration and provides you with the appropriate Update scenarios.<br />
<br />
We choose for "Update existing PBX with installation of an external App Platform" as the selected scenario.<br />
<br />
''Tip: Be sure that you don't have any Object with H323 Name: "AP" in your config. If so you will have problems in connecting the AP Platform.''<br />
<br />
[[Image:Update existing PBX with installation of an external App Platform.png]]<br />
<br />
<br />
In the step "innovaphone PBX Installation" you enter the necessary network settings of the gateway.<br />
<br />
It is also possible to update the gateway to the latest possible firmware version.<br />
<br />
Be aware that if you choose for an update of the firmware, a restart will occur.<br />
<br />
[[Image:innovaphone PBX installation2.png]]<br />
<br />
In the step, "Connect to external App Platform" we connect the PBX with the pre-defines gateway with the App Platform.<br />
<br />
To proceed we enter the IP-address off the App-Platform and its password.<br />
<br />
After pressing connect and a successful connection it will show connected.<br />
<br />
''Tip: The default password for the App-Platform is "pwd". If you don't enter a password the default password will be used automatically. If you changed the password on the App-Platform into a more secure password yourself before starting the Install to update the PBX, Be sure you use this same password to connect. Otherwise the connection will fail and the install can't proceed.''<br />
<br />
<br><br />
''Tip: With the search option you can searh for available App-platform in your network that are installed on a gateway. It is required that this gateway was in default factory setting.''<br />
<br />
''A search is not possible for an App-platforms that runs on a virtual machine. This can only be accessed via its IP-address.''<br />
<br />
<br />
[[Image:Connect to external App Platform.png]]<br />
<br />
<br />
Tip: When the next step will follow with "Connect to Devices" the there was already an entry in the advanced user interface in<br />
<br />
''General/Devices Registration''). Clear this entry and restart the Install process again.<br><br><br />
<br />
In the following step "innovaphone PBX Options" you enter the configuration just as you have seen and learned during the iT Connect op iT Update training.<br />
<br />
Here the PBX name and Domain name (System name) should match with your configuration.<br />
<br />
''Tip: As user please add an additional (not existing) new user as myApps Admin. Name and mail cannot be in use already.''<br />
<br><br />
''Tip: At the moment only lower case PBX names can be used. In case the PBX you want to update is using upper case you have to change it to lower case (at the moment) and your phones will loose registration. Later on you have to change the PBX entries of all objects to lower case.''<br><br />
In the following step "Emergency Administrator password, please save secure" the passwords will NOT be created randomly as you have learned during the iT Connect Training. The existing passwords of the PBX system remain as they are.<br />
<br><br />
<br />
In the following steps the configurations will be done as learned during your iT Connect Training.<br />
<br><br />
After finishing all the install steps, you can login into the system with the previously define myApps Admin in the myApps client.<br />
<br />
''Tip: If you cant login with the myApps Admin User, go to the Advanced User Interface ([https://ip.addr/admin.xml?xsl=admin.xsl https://ip.addr/admin.xml?xsl=admin.xsl]) and assign an existing user object the Template "Config Admin". You can then login with this user into myApps.''<br />
<br><br />
As mentioned in the beginning , know you can change your saved and special settings back to its original state if this is necessary for your configuration.<br />
<br><br />
To give the existing users the possibility to use the innovaphone myApps, you should inherit the existing templates to the new template "Config User". If the user didn't have any template at all, then assign them o the template "Config User".<br />
<br />
''Tip: The Users are only seen in Users App if they have the "Visible" flag in Visibility set. This is mostly done by Config Templates. So be aware that if you have another Config Template in use (that has not set the Visibility flag) even if you inheritate it from Config User it will not overwrite the older settings. So choose here the Visibility flag afterwards.'' <br />
<br />
[[Image:Change template.png]]<br />
<br />
''Tip: Assign Administrative users to the new template "Config Admin".''<br />
<br />
''Tip: In case you are using Apps that need a License the selectable box under License only appear after uploading the necessary license. In test mode everything works. So in case you are using test mode it is better to first upload your licenses, select the license boxes and than deactivate your test mode!<br />
<br />
== Provisioning ==<br />
<br />
If you want to use Provisioning and you are using Update Server/PHP Update Server 2 you have to consider that your phone needs to reach config.innovaphone.com via Update URL.<br><br />
That means that if you already provide an Update URL via DHCP that the Provisioning process will not be possible. Therefore delete the Update URL in your DHCP Server. <br><br />
In case you are using Update Server/PHP Update Server 2 for Certificates etc. your phone needs to reach your old Update Server after provisioning again. (further details will follow)<br><br />
<br />
Please Check: [[Reference13r1:Services/Update]]<br />
<br />
== Assign Hardware of a User to a phone or softwarephone App ==<br />
<br />
This can be done by the administrator in UsersAdmin App.<br> <br />
Alternative the User can do this via his Profile. At the instruction from myApps the user can be shown on which point he can assign the app. <br />
<br />
[[Image:Profile PhoneApp.png]]<br />
<br />
== Reverse Proxy ==<br />
<br />
Via the advanced user interface install the latest V13r1 firmware.<br />
<br />
In the next step we need the Devices App URL. Via the advanced user interface, in General/Devices Registration/Devices App URL.<br />
<br />
Copy this URL.<br />
<br />
<br />
[[Image:Device Registration2.png]]<br />
<br />
Paste this URL in the advanced user interface of the Reverse Proxy in the field General/Devices Registration/Devices App URL.<br />
<br />
From now on this device can be found in the Devices App in Devices.<br />
<br />
The MAC address and a wrench symbol will be displayed.<br />
<br />
Here you can now assign a meaningful name and the domain to the device.<br />
<br />
<br />
[[Image:Devices.png]]<br />
<br />
Via Categories you should assign this gateway also to the appropriate Category.<br />
<br><br />
<br />
[[Image:Devices2.png]]<br />
<br />
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''<br />
<br />
''These include at least: Alarmserver Global, Media Global, NTP-settings''<br />
<br><br />
<br />
Via the PBX Manager App and the Reverse Proxy plugin you can now configure the Reverse Proxy.<br />
<br />
You should add here a new Host entry for the App Platform in the Reverse Proxy via the option "Add Host".<br />
<br />
The DNS name of the App Platform will be displayed in the next step. Select the DNS name and it will be added to the Reverse Proxy entries.<br />
<br />
Via the advanced user interface you have to change the hostnames for every PBX (Slaves and Standby).<br />
<br><br />
<br />
In the first http forward field you need to enter the following string /PBX0/APPCLIENT/appclient.htm and forward it to the appropriate IP-address with the port numbers 80 and 443 and tag the checkbox Default.<br />
<br><br />
<br />
At least the following entries should be available as shown in the picture below.<br />
<br><br />
<br />
[[Image:Reverse Proxy Entries.png]]<br />
<br><br />
<br />
== STUN / TURN / Slave / Standby / DECT ==<br />
<br />
If you want to have access to the gateway to enter the install process, you have to enter the admin credentials to login.<br />
<br />
In the next step select "Manual Configuration" and you will enter the Advanced User Interface.<br />
<br />
Install the latest V13r1 firmware.<br />
<br />
In the following step we need the Device URL which can be found on two different ways.<br />
<br />
<!--<br />
# Via the App Manager, in Settings/General/Devices app URL , we copy the complete URL <br> <br><br />
<br />
<br><br />
<br />
[[Image:App Manager.png]]<br />
<br />
--><br />
<br />
# Via the Advanced User Interface of the PBX<br />
In General/Devices Registration/Devices App URL copy the complete URL.<br />
<br />
[[Image:Device Registration2.png]]<br />
<br />
<br />
Paste this URL via the Advanced User Interface of the Reverse Proxy Gateway in General/Devices Registration/Devices App URL .<br />
<br />
Now you can find this Gateway in the Devices App within Devices. It will be displayed with its MAC-address and a wrench symbol.<br />
<br />
Here you can now assign a meaningful name and the domain to the device.<br />
<br />
[[Image:Devices.png]]<br />
<br />
Via Category you should assign the Gateway to the appropriate category.<br />
<br />
<br />
[[Image:Devices2.png]]<br />
<br />
<br />
''Tip: Now the device configurations are assigned to all devices and the corresponding category(s)''<br />
<br />
''These include at least: Alarmserver Global, Media Global, NTP-settings''<br />
<br />
''Tip: For a Slave, Standby PBX or DECT you should select TLS as Replication protocol.''<br />
<br />
== Configuration Changes ==<br />
=== SNMP disabled by default ===<br />
Up and including v12r2, SNMP was by default activated on a innovaphone device. In v13 it is by default deactivated, it can be activated by a new [[Reference13r1:Services/SNMP | Enable Checkmark]]. As a result, if you upgrade to v13 firmware SNMP is deactivated and needs to be enabled if SNMP is needed in the customer setup.<br />
<br />
===Config line size was increased to 32KB===<br />
<br />
Downgrade from 13r1 to 12r2 (or older firmware) will result in objects with a too large [[Howto:Config_size_Limitations#Global | config line]] being dropped.<br />
<br />
===PBX name in v13 can't include uppercase letter===<br />
<br />
So you should change it in your configuration in V12 before the upgrade of PBX.<br />
<br />
== Known issues ==<br />
* For the known issues, please have a look into our [http://wiki.innovaphone.com/index.php?title=Support:DVL-Roadmap_Firmware_13r1 Support:DVL-Roadmap Firmware 13r1]<br />
* [[Support:IP10x/IP11x_VLAN_configuration_disturbs_various_functions_in_V13r1_beta/final/sr1]]<br />
<br />
== Related Articles ==<br />
*[[Howto:Guideline V5 to V6 upgrade]]<br />
*[[Howto:Upgrade Issues V5 to V6]]<br />
*[[Howto:Firmware Upgrade V6 V7]]<br />
*[[Howto:Firmware Upgrade V7 V8]]<br />
*[[Howto:Firmware Upgrade V8 V9]]<br />
*[[Howto:Firmware Upgrade V9 V10]]<br />
*[[Howto:Firmware Upgrade V10 V11r1]]<br />
*[[Howto:Firmware Upgrade V11r1 V11r2]]<br />
*[[Support:Special_Precaution_required_when_upgrading_IPxx11_Gateways_from_pre-SR14_Firmware_Versions]]<br />
* [[Howto:Firmware Upgrade V11r2 V12r1]]<br />
* [[Howto:Firmware Upgrade V12r1 V12r2]]<br />
[[Category:Howto|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference13r1:App-Platform/Installation&diff=51784Reference13r1:App-Platform/Installation2019-04-16T11:40:21Z<p>Twl: /* Installation */</p>
<hr />
<div>The innovaphone App Platform can be automatically installed in one single step here.<br />
<br />
== Prerequisites ==<br />
* IP settings configured under [http://wiki.innovaphone.com/index.php?title=Reference13r1:App_Platform/IP App Platform/IP]<br />
* Proxy ARP enabled under [http://wiki.innovaphone.com/index.php?title=Reference13r1:IP4/ETH/IP IP4/ETH/IP]<br />
* mSATA module for an IPx11 or a CF card on an IPx10<br />
<br />
== Installation ==<br />
The default image URL is found by searching for a linux.json file on https://store.innovaphone.com/release/download<br />
In this case, your device must have internet access!<br />
<br />
You can also enter a direct URL to a remote or local webserver with the image file, e.g. http://store.innovaphone.com/beta/download/app-platform/80003/app-platform-armel.img<br />
<br />
The following steps are executed during installation:<br />
<br />
* download of the image through HTTP<br />
* upload of the image to the SSD/CF card<br />
* configuration of ram disk and starting of the ramdisk<br />
* the ram disk creates a new partition with the real size of the disk<br />
* starting of the new rootfs partition<br />
<br />
After the installation, the App Platform can be directly accessed through it's IP address.<br />
<br />
== Known issues ==<br />
This can't be used to install the former Linux Application Platform!<br />
Please refer to [http://wiki.innovaphone.com/index.php?title=Reference9:Concept_Linux_Application_Platform Concept Linux Application Platform] in this case.</div>Twlhttps://wiki.innovaphone.com/index.php?title=Reference13r1:App-Platform/Installation&diff=51652Reference13r1:App-Platform/Installation2019-04-01T07:22:55Z<p>Twl: /* Installation */</p>
<hr />
<div>The innovaphone App Platform can be automatically installed in one single step here.<br />
<br />
== Prerequisites ==<br />
* IP settings configured under [http://wiki.innovaphone.com/index.php?title=Reference13r1:App_Platform/IP App Platform/IP]<br />
* Proxy ARP enabled under [http://wiki.innovaphone.com/index.php?title=Reference13r1:IP4/ETH/IP IP4/ETH/IP]<br />
* mSATA module for an IPx11 or a CF card on an IPx10<br />
<br />
== Installation ==<br />
The default image URL is found by searching for a linux.json file on https://store.innovaphone.com/release/download<br />
In this case, your device must have internet access!<br />
<br />
You can also enter a direct URL to a remote or local webserver with the image file, e.g. http://store.innovaphone.com/alpha/download/app-platform/70004/app-platform-armel.img<br />
<br />
The following steps are executed during installation:<br />
<br />
* download of the image through HTTP<br />
* upload of the image to the SSD/CF card<br />
* configuration of ram disk and starting of the ramdisk<br />
* the ram disk creates a new partition with the real size of the disk<br />
* starting of the new rootfs partition<br />
<br />
After the installation, the App Platform can be directly accessed through it's IP address.<br />
<br />
== Known issues ==<br />
This can't be used to install the former Linux Application Platform!<br />
Please refer to [http://wiki.innovaphone.com/index.php?title=Reference9:Concept_Linux_Application_Platform Concept Linux Application Platform] in this case.</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51616Howto:HiMed - Testreport2019-03-20T14:24:10Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Config_User_HiMed.png]]<br />
<br />
=== HiMed configuration ===<br />
[[Image:Himed_Config.JPG]]<br />
[[Image:Himed_Config-Stellplatz.JPG]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=File:HiMed.png&diff=51536File:HiMed.png2019-03-13T10:26:06Z<p>Twl: </p>
<hr />
<div></div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51535Howto:HiMed - Siemens - 3rd Party Product2019-03-13T10:25:53Z<p>Twl: /* Vendor */</p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* HiMed 10.51 Pro20<br />
* innovaphone V12R2 SR21<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:HiMed.png]] [https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:HiMed - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | https://w3.siemens.com/mcms/topics/en/himed/Pages/contact-form.aspx<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51534Howto:HiMed - Testreport2019-03-13T10:20:22Z<p>Twl: /* innovaphone configuration */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Config_User_HiMed.png]]<br />
<br />
=== HiMed configuration ===<br />
[[Image:Himed_Config.JPG]]<br />
[[Image:Himed_Config-Stellplatz.JPG]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=File:Config_User_HiMed.png&diff=51533File:Config User HiMed.png2019-03-13T10:20:02Z<p>Twl: </p>
<hr />
<div></div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51532Howto:HiMed - Testreport2019-03-13T10:19:37Z<p>Twl: /* innovaphone configuration */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Config_User_HiMedpng.png]]<br />
<br />
=== HiMed configuration ===<br />
[[Image:Himed_Config.JPG]]<br />
[[Image:Himed_Config-Stellplatz.JPG]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51531Howto:HiMed - Testreport2019-03-13T10:15:18Z<p>Twl: /* Test Setup */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
=== HiMed configuration ===<br />
[[Image:Himed_Config.JPG]]<br />
[[Image:Himed_Config-Stellplatz.JPG]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51530Howto:HiMed - Testreport2019-03-13T10:13:37Z<p>Twl: /* Konftel 300IP configuration */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
=== HiMed configuration ===<br />
[[Image:Himed_Config.JPG]]<br />
[[Image:Himed_Config-Stellplatz.JPG]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=File:Himed_Config-Stellplatz.JPG&diff=51529File:Himed Config-Stellplatz.JPG2019-03-13T10:12:36Z<p>Twl: </p>
<hr />
<div></div>Twlhttps://wiki.innovaphone.com/index.php?title=File:Himed_Config.JPG&diff=51528File:Himed Config.JPG2019-03-13T10:12:19Z<p>Twl: </p>
<hr />
<div></div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51527Howto:HiMed - Testreport2019-03-13T10:08:51Z<p>Twl: /* innovaphone configuration */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:HiMed_PBX_Innovaphone.jpg]]<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=File:HiMed_PBX_Innovaphone.jpg&diff=51526File:HiMed PBX Innovaphone.jpg2019-03-13T10:08:07Z<p>Twl: </p>
<hr />
<div></div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51525Howto:HiMed - Testreport2019-03-13T09:51:17Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51524Howto:HiMed - Testreport2019-03-13T09:50:16Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|----<br />
|RFC 2833<br />
|Yes<br />
|----<br />
|SIP Info<br />
|No<br />
|----<br />
|inband-DTMF<br />
|No<br />
|----<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51523Howto:HiMed - Testreport2019-03-13T09:49:24Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|RFC 2833<br />
|Yes<br />
|SIP Info<br />
|No<br />
|inband-DTMF<br />
|No<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51522Howto:HiMed - Testreport2019-03-13T09:40:51Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|CGPN<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|CDPN<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51501Howto:HiMed - Testreport2019-03-08T13:34:04Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
<br />
==Certification Status==<br />
<br />
<!--{{Template:Compat Status "tested"}}--><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat_Status_"referral_prod."-no-certificate}}<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|CGPN<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|CDPN<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51500Howto:HiMed - Testreport2019-03-08T11:56:34Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
<br />
==Certification Status==<br />
<br />
<!--{{Template:Compat Status "tested"}}--><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat_Status_"referral_prod."-no-certificate}}<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|CGPN<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|CDPN<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
===Keys===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device has speed dial keys<br />
|No<br />
|----<br />
|Device has programmable function keys<br />
|No<br />
|----<br />
|Device has partner keys<br />
|No<br />
|}<br />
<br />
===CTI Features (with SOAP / TAPI / myPBX) ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|User Call - outgoing call <br />
|Yes<br />
|----<br />
|User Connect - Answer incoming call<br />
|No<br />
|----<br />
|User Reject - Reject alerting call<br />
|Yes<br />
|----<br />
|User Disconnect - Disconnect active call<br />
|Yes<br />
|----<br />
|User Hold - Put connected call on hold <br />
|Yes<br />
|----<br />
|User Hold Retrieve - Retrieve call on hold <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult (Alerting only)<br />
|Yes<br />
|----<br />
|User Transfer - Blind Transfer<br />
|Yes<br />
|----<br />
|3PTY - Make 3rd Party Call<br />
|No<br />
|----<br />
|Connected Number Update on Display<br />
|DUT: No myPBX: Yes<br />
|}<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51499Howto:HiMed - Testreport2019-03-08T11:47:00Z<p>Twl: </p>
<hr />
<div>==Summary==<br />
<br />
<br />
<br />
==Certification Status==<br />
<br />
<!--{{Template:Compat Status "tested"}}--><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat_Status_"referral_prod."-no-certificate}}<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|No<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|No<br />
|----<br />
|Device supports SRTP<br />
|No<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|No<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|No<br />
|----<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|No<br />
|----<br />
|call using g729<br />
|No<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|CGPN<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|CDPN<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
=== DTMF Features ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|CFU Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFB Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFNR Activate/Deactivate <br />
|Yes<br />
|----<br />
|Pickup Group <br />
|Yes<br />
|----<br />
|Pickup Directed <br />
|Yes<br />
|----<br />
|Park/Unpark <br />
|No<br />
|----<br />
|Park To/Unpark From <br />
|No<br />
|----<br />
|Call Completion Busy<br />
|No<br />
|----<br />
|Call Completion Cancel<br />
|No<br />
|----<br />
|Join Group/Leave Group<br />
|Yes<br />
|----<br />
|Join All Groups/Leave All Groups<br />
|Yes<br />
|----<br />
|Enable mobility/Disable mobility <br />
|Yes<br />
|----<br />
|Enable mobility cw/Disable mobility cw <br />
|Yes<br />
|----<br />
|Set presence<br />
|Yes<br />
|}<br />
<br />
==Other Features==<br />
<br />
===Directory===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device built-in directory<br />
|----<br />
|Exists<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
===Keys===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device has speed dial keys<br />
|No<br />
|----<br />
|Device has programmable function keys<br />
|No<br />
|----<br />
|Device has partner keys<br />
|No<br />
|}<br />
<br />
===CTI Features (with SOAP / TAPI / myPBX) ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|User Call - outgoing call <br />
|Yes<br />
|----<br />
|User Connect - Answer incoming call<br />
|No<br />
|----<br />
|User Reject - Reject alerting call<br />
|Yes<br />
|----<br />
|User Disconnect - Disconnect active call<br />
|Yes<br />
|----<br />
|User Hold - Put connected call on hold <br />
|Yes<br />
|----<br />
|User Hold Retrieve - Retrieve call on hold <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult (Alerting only)<br />
|Yes<br />
|----<br />
|User Transfer - Blind Transfer<br />
|Yes<br />
|----<br />
|3PTY - Make 3rd Party Call<br />
|No<br />
|----<br />
|Connected Number Update on Display<br />
|DUT: No myPBX: Yes<br />
|}<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51498Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:29:34Z<p>Twl: /* Certification Status */</p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* HiMed 10.51 Pro20<br />
* innovaphone V12R2 SR21<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:HiMed - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | https://w3.siemens.com/mcms/topics/en/himed/Pages/contact-form.aspx<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51497Howto:HiMed - Testreport2019-03-08T11:29:26Z<p>Twl: /* Certification Status */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
<br />
==Certification Status==<br />
<br />
<!--{{Template:Compat Status "tested"}}--><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat_Status_"referral_prod."-no-certificate}}<br />
<br />
Testing of this product has been finalized 28th of February, 2019.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|SNTP config has TZ string for timezone/dst autoconfig<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Fixed registrations works <br />
|Yes<br />
|----<br />
|Device registers w/o Extension (just by name)<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|PBX redirect (UserObject on Master/Phone at Slave registered)<br />
|Yes<br />
|----<br />
|Physical Location (@PBX) correct?<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|Yes<br />
|----<br />
|Device sends NAT - keepalive messages<br />
|Yes<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device refreshes the PBX registration<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|Yes<br />
|----<br />
|Device supports SRTP<br />
|Yes<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|Yes<br />
|----<br />
|Device supports HTTPS<br />
|Yes<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|Yes<br />
|----<br />
|Supported menu languages<br />
|Dansk, Turkce, Español, Nederlands, English, <br>Deutsch, Português, Suomi, Italiano, Svenska, <br>Greek, Français, Norsk, Polski, Russian<br />
|}<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|Yes<br />
|----<br />
|call using g729<br />
|Yes<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|Device sets up an early media channel for incoming calls<br />
|N/A<br />
|----<br />
|Device sets up an early media channel for outgoing calls<br />
|N/A<br />
|----<br />
|Device shows called id number<br />
|Yes<br />
|----<br />
|Device shows called id name<br />
|Yes<br />
|----<br />
|Device shows called id display info<br />
|No<br />
|----<br />
|Fax using T.38<br />
|N/A<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Reverse Media Negotiation<br />
|Yes<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|Yes<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|Yes<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device supports distinctive ringing<br />
|No<br />
|----<br />
|Device supports asymetric codec negotiation<br />
|Yes<br />
|----<br />
|Device supports codec renegotiation during a conversation<br />
|N/A<br />
|----<br />
|Device shows correct display message in case of busy CDPN<br />
|Yes<br />
|----<br />
|Device shows correct display message in case of not existing CDPN<br />
|Yes<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|3party conference possible<br />
|Yes<br />
|----<br />
|Device supports display updates during call(needed for Directory Search object)<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Registration redirecting works?<br />
|N/A<br />
|----<br />
|Incoming SRTP call - SRTP not enabled on DUT<br />
|Yes<br />
|----<br />
|Incoming SRTP call - SRTP enabled on DUT<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
=== DTMF Features ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|CFU Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFB Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFNR Activate/Deactivate <br />
|Yes<br />
|----<br />
|Pickup Group <br />
|Yes<br />
|----<br />
|Pickup Directed <br />
|Yes<br />
|----<br />
|Park/Unpark <br />
|No<br />
|----<br />
|Park To/Unpark From <br />
|No<br />
|----<br />
|Call Completion Busy<br />
|No<br />
|----<br />
|Call Completion Cancel<br />
|No<br />
|----<br />
|Join Group/Leave Group<br />
|Yes<br />
|----<br />
|Join All Groups/Leave All Groups<br />
|Yes<br />
|----<br />
|Enable mobility/Disable mobility <br />
|Yes<br />
|----<br />
|Enable mobility cw/Disable mobility cw <br />
|Yes<br />
|----<br />
|Set presence<br />
|Yes<br />
|}<br />
<br />
==Other Features==<br />
<br />
===Directory===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device built-in directory<br />
|----<br />
|Exists<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
===Keys===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device has speed dial keys<br />
|No<br />
|----<br />
|Device has programmable function keys<br />
|No<br />
|----<br />
|Device has partner keys<br />
|No<br />
|}<br />
<br />
===CTI Features (with SOAP / TAPI / myPBX) ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|User Call - outgoing call <br />
|Yes<br />
|----<br />
|User Connect - Answer incoming call<br />
|No<br />
|----<br />
|User Reject - Reject alerting call<br />
|Yes<br />
|----<br />
|User Disconnect - Disconnect active call<br />
|Yes<br />
|----<br />
|User Hold - Put connected call on hold <br />
|Yes<br />
|----<br />
|User Hold Retrieve - Retrieve call on hold <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult (Alerting only)<br />
|Yes<br />
|----<br />
|User Transfer - Blind Transfer<br />
|Yes<br />
|----<br />
|3PTY - Make 3rd Party Call<br />
|No<br />
|----<br />
|Connected Number Update on Display<br />
|DUT: No myPBX: Yes<br />
|}<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51496Howto:HiMed - Testreport2019-03-08T11:28:14Z<p>Twl: /* Version */</p>
<hr />
<div>==Summary==<br />
<br />
<br />
<br />
==Certification Status==<br />
<br />
<!--{{Template:Compat Status "tested"}}--><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat_Status_"referral_prod."-no-certificate}}<br />
<br />
Testing of this product has been finalized 20th of December, 2016.<br />
<br />
==Version==<br />
Firmware Version:<br />
10.51 Pro20<br />
<br />
innovaphone Firmware:<br />
12R2 SR21<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|SNTP config has TZ string for timezone/dst autoconfig<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Fixed registrations works <br />
|Yes<br />
|----<br />
|Device registers w/o Extension (just by name)<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|PBX redirect (UserObject on Master/Phone at Slave registered)<br />
|Yes<br />
|----<br />
|Physical Location (@PBX) correct?<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|Yes<br />
|----<br />
|Device sends NAT - keepalive messages<br />
|Yes<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device refreshes the PBX registration<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|Yes<br />
|----<br />
|Device supports SRTP<br />
|Yes<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|Yes<br />
|----<br />
|Device supports HTTPS<br />
|Yes<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|Yes<br />
|----<br />
|Supported menu languages<br />
|Dansk, Turkce, Español, Nederlands, English, <br>Deutsch, Português, Suomi, Italiano, Svenska, <br>Greek, Français, Norsk, Polski, Russian<br />
|}<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|Yes<br />
|----<br />
|call using g729<br />
|Yes<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|Device sets up an early media channel for incoming calls<br />
|N/A<br />
|----<br />
|Device sets up an early media channel for outgoing calls<br />
|N/A<br />
|----<br />
|Device shows called id number<br />
|Yes<br />
|----<br />
|Device shows called id name<br />
|Yes<br />
|----<br />
|Device shows called id display info<br />
|No<br />
|----<br />
|Fax using T.38<br />
|N/A<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Reverse Media Negotiation<br />
|Yes<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|Yes<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|Yes<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device supports distinctive ringing<br />
|No<br />
|----<br />
|Device supports asymetric codec negotiation<br />
|Yes<br />
|----<br />
|Device supports codec renegotiation during a conversation<br />
|N/A<br />
|----<br />
|Device shows correct display message in case of busy CDPN<br />
|Yes<br />
|----<br />
|Device shows correct display message in case of not existing CDPN<br />
|Yes<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|3party conference possible<br />
|Yes<br />
|----<br />
|Device supports display updates during call(needed for Directory Search object)<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Registration redirecting works?<br />
|N/A<br />
|----<br />
|Incoming SRTP call - SRTP not enabled on DUT<br />
|Yes<br />
|----<br />
|Incoming SRTP call - SRTP enabled on DUT<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
=== DTMF Features ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|CFU Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFB Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFNR Activate/Deactivate <br />
|Yes<br />
|----<br />
|Pickup Group <br />
|Yes<br />
|----<br />
|Pickup Directed <br />
|Yes<br />
|----<br />
|Park/Unpark <br />
|No<br />
|----<br />
|Park To/Unpark From <br />
|No<br />
|----<br />
|Call Completion Busy<br />
|No<br />
|----<br />
|Call Completion Cancel<br />
|No<br />
|----<br />
|Join Group/Leave Group<br />
|Yes<br />
|----<br />
|Join All Groups/Leave All Groups<br />
|Yes<br />
|----<br />
|Enable mobility/Disable mobility <br />
|Yes<br />
|----<br />
|Enable mobility cw/Disable mobility cw <br />
|Yes<br />
|----<br />
|Set presence<br />
|Yes<br />
|}<br />
<br />
==Other Features==<br />
<br />
===Directory===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device built-in directory<br />
|----<br />
|Exists<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
===Keys===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device has speed dial keys<br />
|No<br />
|----<br />
|Device has programmable function keys<br />
|No<br />
|----<br />
|Device has partner keys<br />
|No<br />
|}<br />
<br />
===CTI Features (with SOAP / TAPI / myPBX) ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|User Call - outgoing call <br />
|Yes<br />
|----<br />
|User Connect - Answer incoming call<br />
|No<br />
|----<br />
|User Reject - Reject alerting call<br />
|Yes<br />
|----<br />
|User Disconnect - Disconnect active call<br />
|Yes<br />
|----<br />
|User Hold - Put connected call on hold <br />
|Yes<br />
|----<br />
|User Hold Retrieve - Retrieve call on hold <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult (Alerting only)<br />
|Yes<br />
|----<br />
|User Transfer - Blind Transfer<br />
|Yes<br />
|----<br />
|3PTY - Make 3rd Party Call<br />
|No<br />
|----<br />
|Connected Number Update on Display<br />
|DUT: No myPBX: Yes<br />
|}<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Testreport&diff=51495Howto:HiMed - Testreport2019-03-08T11:26:07Z<p>Twl: New page: ==Summary== ==Certification Status== <!--{{Template:Compat Status "tested"}}--> <!-- {{Template:Compat Status "in progress"}} --> <!-- {{Template:Compat_Status_"referral_prod."|certifi...</p>
<hr />
<div>==Summary==<br />
<br />
<br />
<br />
==Certification Status==<br />
<br />
<!--{{Template:Compat Status "tested"}}--><br />
<!-- {{Template:Compat Status "in progress"}} --><br />
<!-- {{Template:Compat_Status_"referral_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"engineered_prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat_Status_"rec._prod."|certificate=Tpl_sip.business_Toplink_SIP_Provider_-_product-cert.pdf}} --><br />
<!-- {{Template:Compat Status "tested"}} --><br />
<!-- {{Template:Compat Status "rejected"}} --><br />
{{Template:Compat_Status_"referral_prod."-no-certificate}}<br />
<br />
Testing of this product has been finalized 20th of December, 2016.<br />
<br />
==Version==<br />
Firmware Version:<br />
2.5.23<br />
<br />
innovaphone Firmware:<br />
12R2<br />
<br />
== Test Setup ==<br />
<br />
[[Image:Testreport_Terminals_SIP_or_H323_1.PNG]]<br />
<br />
==Device Setup==<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result<br />
|----<br />
|DHCP is default<br />
|Yes<br />
|----<br />
|SNTP config has TZ string for timezone/dst autoconfig<br />
|Yes<br />
|----<br />
|DHCP yields correct default gateway<br />
|Yes<br />
|----<br />
|Fixed registrations works <br />
|Yes<br />
|----<br />
|Device registers w/o Extension (just by name)<br />
|Yes<br />
|----<br />
|Device registers by extension<br />
|Yes<br />
|----<br />
|Device registers with password<br />
|Yes<br />
|----<br />
|Device registers multiple identities<br />
|Yes<br />
|----<br />
|PBX redirect (UserObject on Master/Phone at Slave registered)<br />
|Yes<br />
|----<br />
|Physical Location (@PBX) correct?<br />
|Yes<br />
|----<br />
|Device supports STUN protocol<br />
|Yes<br />
|----<br />
|Device sends NAT - keepalive messages<br />
|Yes<br />
|----<br />
|Device usable in [[Howto:Hosting | hosting]] scenarios?<br />
|Yes<br />
|----<br />
|Device refreshes the PBX registration<br />
|Yes<br />
|----<br />
|Device supports SIP over TCP<br />
|Yes<br />
|----<br />
|Device supports SRTP<br />
|Yes<br />
|----<br />
|Device supports SIPS (SIP over TLS)<br />
|Yes<br />
|----<br />
|Device supports HTTPS<br />
|Yes<br />
|----<br />
|Device supports VAD (Voice activity detection)<br />
|Yes<br />
|----<br />
|Supported menu languages<br />
|Dansk, Turkce, Español, Nederlands, English, <br>Deutsch, Português, Suomi, Italiano, Svenska, <br>Greek, Français, Norsk, Polski, Russian<br />
|}<br />
<br />
==Test Results==<br />
<br />
=== Basic Call ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|call using g711a<br />
|Yes<br />
|----<br />
|call using g711u<br />
|Yes<br />
|----<br />
|call using g729<br />
|Yes<br />
|----<br />
|call using g722<br />
|Yes<br />
|----<br />
|Overlapped sending<br />
|No<br />
|----<br />
|Device sets up an early media channel for incoming calls<br />
|N/A<br />
|----<br />
|Device sets up an early media channel for outgoing calls<br />
|N/A<br />
|----<br />
|Device shows called id number<br />
|Yes<br />
|----<br />
|Device shows called id name<br />
|Yes<br />
|----<br />
|Device shows called id display info<br />
|No<br />
|----<br />
|Fax using T.38<br />
|N/A<br />
|----<br />
|CGPN can be suppressed<br />
|No<br />
|----<br />
|Reverse Media Negotiation<br />
|Yes<br />
|----<br />
|Device shows CDPN/CGPN on incoming call<br />
|Yes<br />
|----<br />
|Device shows CDPN/CGPN on outgoing call<br />
|Yes<br />
|----<br />
|Device shows connected number<br />
|Yes<br />
|----<br />
|Device shows diverting number<br />
|No<br />
|----<br />
|Device supports distinctive ringing<br />
|No<br />
|----<br />
|Device supports asymetric codec negotiation<br />
|Yes<br />
|----<br />
|Device supports codec renegotiation during a conversation<br />
|N/A<br />
|----<br />
|Device shows correct display message in case of busy CDPN<br />
|Yes<br />
|----<br />
|Device shows correct display message in case of not existing CDPN<br />
|Yes<br />
|----<br />
|Device shows correct display message in case that the call is declined<br />
|Yes<br />
|----<br />
|3party conference possible<br />
|Yes<br />
|----<br />
|Device supports display updates during call(needed for Directory Search object)<br />
|Yes<br />
|----<br />
|Long Time Call (>30 min) works?<br />
|Yes<br />
|----<br />
|Registration redirecting works?<br />
|N/A<br />
|----<br />
|Incoming SRTP call - SRTP not enabled on DUT<br />
|Yes<br />
|----<br />
|Incoming SRTP call - SRTP enabled on DUT<br />
|Yes<br />
|----<br />
|Voice Quality OK?<br />
|Yes<br />
|}<br />
<br />
=== DTMF ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|DTMF tones sent correctly<br />
|Yes<br />
|----<br />
|DTMF tones received correctly<br />
|Yes<br />
|}<br />
<br />
<br />
=== Hold/Retrieve ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device handles incoming hold correctly<br />
|Yes<br />
|----<br />
|Device can put a call on hold using correctly(inactive or sendonly)<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
||inno1 calls inno2. inno1 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. testphone transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
=== Blind Transfer (alerting only)===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Voice Ok?<br />
|----<br />
|inno1 calls inno2. inno2 transfers to testphone.<br />
|Yes<br />
|----<br />
|inno1 calls testphone. testphone transfers to inno2.<br />
|Yes<br />
|----<br />
|testphone calls inno1. inno1 transfers to inno2.<br />
|Yes<br />
|}<br />
<br />
<br />
=== DTMF Features ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|CFU Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFB Activate/Deactivate <br />
|Yes<br />
|----<br />
|CFNR Activate/Deactivate <br />
|Yes<br />
|----<br />
|Pickup Group <br />
|Yes<br />
|----<br />
|Pickup Directed <br />
|Yes<br />
|----<br />
|Park/Unpark <br />
|No<br />
|----<br />
|Park To/Unpark From <br />
|No<br />
|----<br />
|Call Completion Busy<br />
|No<br />
|----<br />
|Call Completion Cancel<br />
|No<br />
|----<br />
|Join Group/Leave Group<br />
|Yes<br />
|----<br />
|Join All Groups/Leave All Groups<br />
|Yes<br />
|----<br />
|Enable mobility/Disable mobility <br />
|Yes<br />
|----<br />
|Enable mobility cw/Disable mobility cw <br />
|Yes<br />
|----<br />
|Set presence<br />
|Yes<br />
|}<br />
<br />
==Other Features==<br />
<br />
===Directory===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device built-in directory<br />
|----<br />
|Exists<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|Yes<br />
|}<br />
<br />
<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|External LDAP Server supported<br />
|Yes<br />
|----<br />
|Can be dialled from<br />
|Yes<br />
|----<br />
|Does CLI resolution<br />
|N/A<br />
|----<br />
|display update if directory object is used?<br />
|N/A<br />
|}<br />
<br />
<br />
===Keys===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|Device has speed dial keys<br />
|No<br />
|----<br />
|Device has programmable function keys<br />
|No<br />
|----<br />
|Device has partner keys<br />
|No<br />
|}<br />
<br />
===CTI Features (with SOAP / TAPI / myPBX) ===<br />
<br />
{| border="1" <br />
!Tested feature<br />
!Result <br />
|----<br />
|User Call - outgoing call <br />
|Yes<br />
|----<br />
|User Connect - Answer incoming call<br />
|No<br />
|----<br />
|User Reject - Reject alerting call<br />
|Yes<br />
|----<br />
|User Disconnect - Disconnect active call<br />
|Yes<br />
|----<br />
|User Hold - Put connected call on hold <br />
|Yes<br />
|----<br />
|User Hold Retrieve - Retrieve call on hold <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult <br />
|Yes<br />
|----<br />
|User Transfer - Transfer with Consult (Alerting only)<br />
|Yes<br />
|----<br />
|User Transfer - Blind Transfer<br />
|Yes<br />
|----<br />
|3PTY - Make 3rd Party Call<br />
|No<br />
|----<br />
|Connected Number Update on Display<br />
|DUT: No myPBX: Yes<br />
|}<br />
<br />
== Configuration ==<br />
<br />
=== innovaphone configuration ===<br />
[[Image:Konftel300IP_Innovaphone_PBX.png]]<br />
<br />
<br />
=== Konftel 300IP configuration ===<br />
[[Image:Konftel300IP_Innovaphone_config.png]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51494Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:25:22Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* HiMed 10.51 Pro20<br />
* innovaphone V12R2 SR21<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:HiMed - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | https://w3.siemens.com/mcms/topics/en/himed/Pages/contact-form.aspx<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51493Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:22:30Z<p>Twl: /* Vendor */</p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* HiMed 10.51 Pro20<br />
* innovaphone V12R2 SR21<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | https://w3.siemens.com/mcms/topics/en/himed/Pages/contact-form.aspx<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51492Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:21:20Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* HiMed 10.51 Pro20<br />
* innovaphone V12R2 SR21<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | https://w3.siemens.com/mcms/topics/en/himed/Pages/contact-form.aspx<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51491Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:19:17Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* HiMed 10.51 Pro20<br />
* innovaphone V12R2 SR21<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | http://www.konftel.com/Support/Contact-Support<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51490Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:11:25Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
*OmniSound®<br />
*HD audio<br />
*Local 5-way conference<br />
*Supports expansion microphones<br />
*Free software upgrades<br />
*Built-in bridging function<br />
*Expandable for PA System<br />
*Connection for Wireless headset<br />
*User profiles<br />
*Phonebook (LDAP)<br />
*Web-based configuration<br />
*PoE (Power over Ethernet)<br />
*SD call recording<br />
*Conference guide<br />
*Two-year warranty<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* Konftel 300IP: 2.5.23<br />
* innovaphone V1xSRxy<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested with the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | http://www.konftel.com/Support/Contact-Support<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51489Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:10:05Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
*OmniSound®<br />
*HD audio<br />
*Local 5-way conference<br />
*Supports expansion microphones<br />
*Free software upgrades<br />
*Built-in bridging function<br />
*Expandable for PA System<br />
*Connection for Wireless headset<br />
*User profiles<br />
*Phonebook (LDAP)<br />
*Web-based configuration<br />
*PoE (Power over Ethernet)<br />
*SD call recording<br />
*Conference guide<br />
*Two-year warranty<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* Konftel 300IP: 2.5.23<br />
* innovaphone V1xSRxy<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===The HiMed Solution - An offering for all Stakeholders===<br />
<br />
The HiMed Cockpit multimedia terminal offers patients an unprecedented level of convenience. In addition to making phone calls, watching TV, listening to the radio and watching films, patients can now also surf the internet, retrieve information via the patient portal and use existing applications without leaving their bed. An integrated webcam even makes it possible for friends and relatives to pay a virtual visit to the hospital. The Cockpit can be easily and variably integrated in the patient rooms and can be used as BYOD access point.<br />
<br />
The Cockpit helps doctors and nurses by supporting the interactive processes at the patient’s bedside. The direct link to the hospital information system means that data (e. g. from the electronic patient records) can be viewed instantly and the necessary action can be taken. Information and Instructions can also be entered immediately.<br />
<br />
The Cockpit can be easily integrated into the patient’s room using the existing infrastructure in the building. This saves both time and money. Additional revenue is generated from the services offered such as telephone, TV, video on demand and the internet, while optimizing the processes at the patient’s bedside enhances the efficiency and attractiveness of the hospital.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested by the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | http://www.konftel.com/Support/Contact-Support<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51488Howto:HiMed - Siemens - 3rd Party Product2019-03-08T11:08:12Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
HiMed Siemens[https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
*OmniSound®<br />
*HD audio<br />
*Local 5-way conference<br />
*Supports expansion microphones<br />
*Free software upgrades<br />
*Built-in bridging function<br />
*Expandable for PA System<br />
*Connection for Wireless headset<br />
*User profiles<br />
*Phonebook (LDAP)<br />
*Web-based configuration<br />
*PoE (Power over Ethernet)<br />
*SD call recording<br />
*Conference guide<br />
*Two-year warranty<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* Konftel 300IP: 2.5.23<br />
* innovaphone V1xSRxy<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===HiMed===<br />
The multimedia terminal HiMed Cockpit offers patients comfort in a new dimension. In addition to phoning, watching TV, listening to the radio and watching movies, patients can surf the Internet, get information through a patient portal and use existing bedside treatments. The integrated webcam even allows a virtual hospital visit of relatives. The cockpit can be easily and variably brought into the patient room and can be used as an access point for BYOD - for mobile devices brought along.<br />
<br />
For the medical and nursing area, the cockpit actively supports the processes at the bedside. By linking to the hospital information system, information (eg from the electronic patient record) can be viewed directly on the bed and required measures and inputs can be carried out immediately.<br />
<br />
The cockpit can be easily and directly introduced into the patient room. House-wide, the existing infrastructure can be used for this purpose. This saves money and time. In addition, the income from the services offered, such as telephone, TV, video on demand and the Internet, as well as the optimization of processes at the bedside increase the profitability and attractiveness of the house.<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested by the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | http://www.konftel.com/Support/Contact-Support<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51487Howto:HiMed - Siemens - 3rd Party Product2019-03-08T10:23:06Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
Siemens HiMed [https://w3.siemens.com/mcms/topics/de/himed/seiten/default.aspx]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
*OmniSound®<br />
*HD audio<br />
*Local 5-way conference<br />
*Supports expansion microphones<br />
*Free software upgrades<br />
*Built-in bridging function<br />
*Expandable for PA System<br />
*Connection for Wireless headset<br />
*User profiles<br />
*Phonebook (LDAP)<br />
*Web-based configuration<br />
*PoE (Power over Ethernet)<br />
*SD call recording<br />
*Conference guide<br />
*Two-year warranty<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* Konftel 300IP: 2.5.23<br />
* innovaphone V1xSRxy<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===Konftel 300IP for innovative conference calls===<br />
The Konftel 300IP is a flexible SIP-based conference phone, perfect for companies that use IP voice services. Its clear, natural sound comes from OmniSound, Konftel’s patented wideband audio technology. The stylishly designed Konftel 300IP is packed with intelligent features for more efficient conference calls. <br />
<br />
Record and store meetings on a SD memory card. Use the conference guide to call pre-programmed groups with just a few simple pushes of a button. Conveniently import and export contact details via the Web interface. Create your own phone book with the personal user profile feature. <br />
<br />
The Konftel 300IP is also ideal for larger conferences since it can accommodate expansion microphones, an external wireless headset and a PA system. With the Konftel 300IP your company will have a conference phone that combines all the benefits of IP voice service with innovative new features.<br />
<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested by the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | http://www.konftel.com/Support/Contact-Support<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twlhttps://wiki.innovaphone.com/index.php?title=Howto:HiMed_-_Siemens_-_3rd_Party_Product&diff=51486Howto:HiMed - Siemens - 3rd Party Product2019-03-08T10:20:34Z<p>Twl: </p>
<hr />
<div>[[Image:Siemens.png||200px|right]]<br />
[[Image:HiMed.png||200px|right]]<br />
<br />
==Product Name==<br />
Siemens HiMed [http://www.konftel.com/Products/Konftel300IP Product site]<br />
<br />
==Certification Status==<br />
<br />
Testing of this product has been finalized 28th of Februar, 2019.<br />
<br />
==Category==<br />
<br />
{{Category:3rdParty_Terminals}}<br />
[[Category:Referral Product|{{PAGENAME}}]]<br />
[[Category:3rdParty_Terminals|{{PAGENAME}}]]<br />
<br />
==Functions==<br />
<!-- by vendor:<br />
- place here a short and concise list of features that are supported by your product <br />
--><br />
Summary of the most important features:<br />
*OmniSound®<br />
*HD audio<br />
*Local 5-way conference<br />
*Supports expansion microphones<br />
*Free software upgrades<br />
*Built-in bridging function<br />
*Expandable for PA System<br />
*Connection for Wireless headset<br />
*User profiles<br />
*Phonebook (LDAP)<br />
*Web-based configuration<br />
*PoE (Power over Ethernet)<br />
*SD call recording<br />
*Conference guide<br />
*Two-year warranty<br />
<br />
==Version==<br />
<!-- by inno:<br />
- version of software that was tested, as declared by the vendor or reseller(in case of customer testimonial), please not if patches have been applied<br />
--><br />
* Konftel 300IP: 2.5.23<br />
* innovaphone V1xSRxy<br />
<br />
==Vendor==<br />
<!-- by vendor<br />
- Official name of your company, at best linked to your companies web site url, Official name of the vendors web site <br />
- you may also add a logo<br />
- upload your company logo (.png preferred, suitable size)<br />
- replace logo below with yours <br />
--><br />
<br />
[[Image:Konftel_logo.png]] [http://www.konftel.com Konftel]<br />
<br />
<br />
==Description==<br />
<br />
===Konftel 300IP for innovative conference calls===<br />
The Konftel 300IP is a flexible SIP-based conference phone, perfect for companies that use IP voice services. Its clear, natural sound comes from OmniSound, Konftel’s patented wideband audio technology. The stylishly designed Konftel 300IP is packed with intelligent features for more efficient conference calls. <br />
<br />
Record and store meetings on a SD memory card. Use the conference guide to call pre-programmed groups with just a few simple pushes of a button. Conveniently import and export contact details via the Web interface. Create your own phone book with the personal user profile feature. <br />
<br />
The Konftel 300IP is also ideal for larger conferences since it can accommodate expansion microphones, an external wireless headset and a PA system. With the Konftel 300IP your company will have a conference phone that combines all the benefits of IP voice service with innovative new features.<br />
<br />
==Summary==<br />
<!-- by inno:<br />
- add remarks regarding the product, such as special features, firmware versions or licenses required on the inno side, <br />
parts of the product that has not been tested or limitations discovered. very short and concise (everything else is in <br />
the test report) <br />
- add link to product test report here<br />
--><br />
<!-- by inno:<br />
as an alternative, if the product has been tested by the vendor<br />
--><br />
This solution has been tested by the vendor. <br />
<br><br />
[[Howto:Konftel 300IP - Testreport]]<br />
<br />
==Contact==<br />
<!-- by vendor:<br />
- add name, address, phone, fax, email, web of primary recommended sales contact<br />
if suitable, you may consider specifying several contacs, depending on your sales structure <br />
(e.g. by country or vertical market)<br />
- in case of a customer testimonial the contact details of the reseller are not disclosed here. As contact person should act sales@innovaphone.com. In order to find the reseller responsible for this product, enter also the corresponding mantis ticket number in invisible tags. <br />
--><br />
<br />
{|<br />
| colspan=99 | http://www.konftel.com/Support/Contact-Support<br />
|}<br />
<br />
[[Category:Compat|{{PAGENAME}}]]</div>Twl