innovaphone wiki - User contributions [en]

Reference12r2:Concept Softwarephone

2020-05-25T10:24:22Z

She: /* Installation */

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

= General =

Innovaphone SoftwarePhone is the implementation of innovaphones HW phones software as a Windows process. So all the features native to the hardwarephones are present in SoftwarePhone as well. SoftwarePhone has no UI, it is operated via myPBX or 3rd Party CTI client (ex: Estos Procall).

=System Requirements=
The innovaphone SoftwarePhone requires:
*Windows 7 or higher
*innovaphone PBX with SoftwarePhones<v> License.
*innovaphone myPBX UC-Client as frontend with myPBX- or UC-license

= Installation =

Prior to installing the 10.00 Version of innovaphone SoftwarePhone an eventually installed 9.00 version must be manually deinstalled. From version 10.00 to 12r1 subsequent releases can be updated without first deinstalling the older version. From 12r2 on prior versions must be manually deinstalled.
When updating the installation, the previous configuration (if existing) is reused. Otherwise a default configuration is installed.
There are 2 ways to install Softwarephone:

* SetupSWPhone.exe. This is the preferred method if no installation parameters are required. It automatically installs all 3rd party SW to operate the headsets
* softwarephone.msi AND SpokesSDKNativeRuntime.msi. If the Softwarephone installation needs to be parametrized via Orca first install SpokesSDKNativeRuntime.msi, then
softwarephone.msi
* In our newest download packet, if you aren't using our exe file please install first HubSDKNativeRuntime.msi, Sennheiser_SDK_v7.5.9600.msi and than softwarephone.msi. Delete first the old pakets and install than the new ones.

The following items are installed:

* SoftwarePhone .exe and related files (dll) in Program files (x86)\innovaphone\SoftwarePhone
* Hid.tbl (the code definitoins of supported USB headsets) in Program files (x86) \innovaphone\SoftwarePhone
* The config files „swphone_config.cfg“ and „swphone_command.cfg” in the User Roaming directory (if no previous configuration is located there, otherwise the old configuration is used, Roaming Directory Location : <drive>:\Users\<User>\AppData\Roaming\innovaphone\SoftwarePhone\)

Installation Process:

* http port 80 ist checked to be available as the SoftwarePhone ’s web configuration port. If not free, a search starting at port 10006 is executed to find a free port. The URL file, containing the configuration servers web @ is adjusted to the determined free port
* SoftwarePhone is startet.

Resetting to defaults:

*Resetting to default configuration could be done by deletiong the config files in the Roaming Directory.

Unattended Installation of softwarephone for ALLUSERS:

*It's possible to install softwarephone for ALLUSERS by using the command:
Msiexec /i softwarephone.msi ALLUSERS=1

= Configuration =

The configuration is opened by selecting “Configuration” from the start menu. A browser connection is opend to the server running as part of SoftwarePhone and the configuration menu is displayed.

Default login is admin/swphone.

The configuration options are the same as for the hardware phones with a few specifics referring to SoftwarePhone running as a Windows process:

* Application
The Applicatons run mode and priority can be set and whether to register with the computers name at the PBX.
* Audio
The desired audio devices can be selected.
* Audio
The Audio –Input, -Output and –Ringing device can be selected.
* USB
Legacy configuration for customers who use a previous installation with a headset other than Jabra, Sennheiser or Plantronics. Headsets from these vendors are handled automatically and need not be configured.

The default credentials are admin / swphone

== '''„Audio and USB Configuration"''' ==

This config GUI is unique in the way that it can only be accessed (right click on the softwarephone icon) from the computer SoftwarePhone is running on. Here the typical End User Configurations are set: Audio and USB-headset parameters.

[[Image:default-usercfg.png]]

Above image shows the default configuration without any headset from vendors Jabra, Plantronics or Sennheiser plugged in. "Headset" in this case means any headset of beforementioned vendors that is detected. Note: The FIRST detected headset will become the active one, if more than 1 headset is plugged in. In case you have more than 1 headset plugged in and want to use a specific for Softwarephone operation you must configure it in the "USB Configuration | USB device" droplist.
The column on the right shows the actual values

[[Image:usercfg-headset-plugged-no-preferred.png]]

Above image shows a default configuration "Headset" with currently a "Sennheiser SC260 .." being plugged in and detected

[[Image:usercfg-headset-plugged-preffered-active.png]]

Above image shows the "Sennheiser SC260 .." configured as the prefered (USB Device) and being active.

Note: If you have configured a specific headset and you don't plug it in but instead another one then this other is fully operational and it stays that way until the prefered one is plugged in, then it becomes the active one.

'''Microphone:'''

The microphone selection.

'''Speaker:'''

The speaker selection

'''Ringer:'''

The Ringing device selection

'''Handsfree:'''

The open listening device selection. The device that plays the incoming audio stream when the speaker button is pressed in myPBX.

'''USB Device:'''

The USB headset selction.

'''USB Map:'''

Legacy for non Jabra, Plantronics and Sennheiser headsets. The codepage selection for the selected usb device. Here one or two choices are presented. If a selection item that refers to the selected USB Device use this. If only “generic HID Telephonie Page” is available you can try to use the headsets button (some headsets support the generic codes)

'''NOTE:''' If the headsets buttons do not work for call control, then call control is solely available through myPbx. Nevertheless the USB headset can be used as the audio-in/output device.

== '''[Tab:„Application“]''' ==

Admin mode Application configuration.

[[Image:swphone_application.jpg]]

'''Application Run Mode:'''

* Manual: SoftwarePhone needs to be started manually
* Login: SoftwarePhone will be started when the user logs in (don't set this option if myPBX Launcher have option "Run Softwarephone" in the same PC).

'''Application Priority:'''
* Normal: As every standard Windows Process. Sufficient in almost all cases
* High: Elevated Priority.

'''Register Mode:'''
* Default: Registration modes like the HW phones.

'''NOTE:''' Anonymous registration might not work in all environments, especially those that prevent multicasts. For example, when using SoftwarePhone over a vpn connection ensure that multicast forwarding is guaranteed. Also, if a virtual machine is running on the same computer it might prevent
multicasts being sent on the LAN.

* Computername:
The best way for registering SoftwarePhone at the PBX. It uses the computername as it is visible on the LAN. The computername is determined by SoftwarePhone and the appropriate parameters are set for the “Phone” modul. This configuration appears in the field “Name” under the “Phone” tab (Example for computer„LBU-VOSTRO-W7“ ):

[[Image:swphone_registration.jpg]]

== '''[Tab:"Audio”]:''' ==

Admin mode Audio configuration. Items see „Audio and USB Configuration“

== '''[Tab:“USB”]:''' ==

Admin mode Audio configuration. Items see „Audio and USB Configuration“

= Rollout =

Especially in larger installations it is desirable to have a mechanism for automatic configuration of the SoftwarePhones. This can be accomplished in the following way:

SoftwarePhones installation package (softwarephone .msi)can be parametrized by creating an [https://docs.microsoft.com/en-us/windows/desktop/msi/orca-exe Orca MSI database editor] transform with the parameters:
URL and POLL. Theses parameters are entered in the “Property” table

[[Image:download_orca.jpg]]

Saving Embedded Streams

By default, when saving a database to a new file with File and Save As…, Orca does not copy streams that are embedded in the database but not a member of any table. Select Copy embedded streams during 'Save As' to save streams to the new file when saving a database using the File with the Save As… option.

[[Image:orca_openfile.jpg]]

[[Image:orca_addrows.jpg]]

[[Image:orca_rows_content.jpg]]

[[Image:orca_savefile.jpg]]

It is recommended that the “POLL” value be set to “1” (shortest time: 1minute).
When SoftwarePhone is installed with the transform it starts, waits 1 min (poll period) then accesses the script file specified in the “POLL” parameter and executes the commands therein.
To register SoftwarePhone with the computername at the PBX the script file should look as follows (example showing the PBX @ “192.168.178.22” with the identifier „IP800-06-25-6e” :

…
#set the PBX @ and Identifier
config change PHONE SIG /prot H323 /gk-addr 192.168.178.22 /gk-id IP800-06-25-6e

#register with computername
mod cmd APP0 app-set /op OK /reg_mode ComputerName

#reset the automatic configuration update
config add UP1 /url

#reset SoftwarePhone and apply config
reset

Another method to provide configurations to the installed SoftwarePhone s is preparing a configuration template by configuring one SoftwarePhone entity, then using the generated “swphone_commands.cfg” file in the <users roaming directory >\innovaphone\SoftwarePhone
as the template, copying it to the update location and using it in the script file:

#invoke configuration template
mod cmd UP0 cfg <update directory location>/swphone_commands.cfg

This method is particularly helpful when many USB headset of the same type are used.

= Setting QoS =
See [[Howto:Softphone recommended settings]].

= Supported USB headsets =

The following USB headsets are supported for onhook/offhook and mute (MyPBX) functionality:

All Jabra, Plantronics and Sennheiser headsets that are supported by these vendors SDKs. Please check their
sites for more information.

https://www.plantronics.com/us/en/support/downloads-apps/hub-desktop

https://developer.jabra.com/site/global/sdks/windows/documentation/core.gsp

https://en-us.sennheiser.com/headset-software-pc

= Troubleshooting Connectivity Problems =

If you experience problems with softwarephone attaching to the PBX or not being able to make calls please check the following:

* '''check in the “Phone” tab whether the state is “up”'''

* '''check in the “General” tab if License is “Valid”'''

* '''Start a command window as Administrator and issue a "netstat –a –b > swphone_netstat.txt"'''

In the “swphone_netstat.txt” file search for “1720”. There should be an entry like this:

'''''TCP 0.0.0.0:1720 LBU-VOSTRO-W7:0 LISTENING'''''
'''[softwarephone.exe].'''

Please search for other occurances of “'''1720'''” to ensure that no other processes listen to this port.

* '''Make a softwarephone trace to see if the packets are received by softwarephone'''

In the “Maintenance” tab “Tracing” enable “'''H.323 Signaling'''”, “'''Phone'''” and “'''All TCP/UDP Traffic'''”. Then try to make the call. In the resulting trace you should see the events like the following:

'''''0:0103:337:3 - RECV RESULT[](662 from pla(192.168.178.22:60003) type: 1)
0:0103:337:3 - PHONE_LISTEN.1 -> PHONE_REG.1 : SIG_SETUP faststart=3ac8bec cmd=PROPOSAL cdpn=400'''''

If these events are no present in the trace it could be that the firewall settings prevent some of softwarephone’s functions. This could be the Firewall.

* '''Check the firewall settings for softwarephone'''

Please open the “System Administration\Windows-Firewall\Allow Program.. Ensure that softwarephone is enabled on the required interfaces. If this doesn’t solve the problem then temporaryly disable the firewall completely and try again.
Now even with the firewall disabled there could be some other security software that causes the problem. To find out if packets to the “h323hostcall” port (1720) are filtered by the firewall you can use the commands “'''netsh wfp capture start'''” to start a trace of the test and “'''netsh wfp capture stop'''” to stop the trace. The trace is written into the file: “'''wfpdiag.cab'''” . Extract the file: “'''wfpdiag.xml'''”. In this file search for “1720”. If the packet is filtered by the firewall an entry like the following can be found:

<netEvent>
<header>
<timeStamp>2013-11-05T11:20:27.367Z</timeStamp>
<flags numItems="8">
<item>FWPM_NET_EVENT_FLAG_IP_PROTOCOL_SET</item>
<item>FWPM_NET_EVENT_FLAG_LOCAL_ADDR_SET</item>
<item>FWPM_NET_EVENT_FLAG_REMOTE_ADDR_SET</item>
<item>FWPM_NET_EVENT_FLAG_LOCAL_PORT_SET</item>
<item>FWPM_NET_EVENT_FLAG_REMOTE_PORT_SET</item>
<item>FWPM_NET_EVENT_FLAG_APP_ID_SET</item>
<item>FWPM_NET_EVENT_FLAG_USER_ID_SET</item>
<item>FWPM_NET_EVENT_FLAG_IP_VERSION_SET</item>
</flags>
<ipVersion>FWP_IP_VERSION_V4</ipVersion>
<ipProtocol>6</ipProtocol>
'''<localAddrV4>192.168.178.21</localAddrV4>'''
'''<remoteAddrV4>192.168.178.22</remoteAddrV4>'''
<localPort>'''1720'''</localPort>
<remotePort>60007</remotePort>
<scopeId>0</scopeId>
<appId>
<data> …</data>
<asString>...</asString>
</appId>
<userId>S-1-5-21-3364624427-3176291796-194291593-006</userId>
</header>
<type>FWPM_NET_EVENT_TYPE_CLASSIFY_DROP</type>
<classifyDrop>
<filterId>105267</filterId>
<layerId>44</layerId>
<reauthReason>0</reauthReason>
<originalProfile>2</originalProfile>
<currentProfile>2</currentProfile>
</classifyDrop>
</netEvent>

where the

<localAddrV4>192.168.178.21</localAddrV4>

and the

<remoteAddrV4>192.168.178.22</remoteAddrV4>

should be your computers and the PBX’s @.

* Check if the setup from the PBX is received at the local computer and what happens with it

Sometimes, Antivirus Packages can implement their own network access policy. This can result in a h323 release complete with cause “User Busy” to an incoming Setup from the PBX before any other softwarephone is reached. To see which process Sends/Receives the packets in a flow you can use the “netmon”, Microsofts free Packet tracer.

= How to obtain debug traces of softwarephone using icollect =

Included in the installation path (C:\Program Files (x86)\innovaphone\SoftwarePhone) there is a tool called '''icollect.exe'''(accessible via start menu entry). After we reproduce a problem we can run this tool to generate debug files that are saved in the roaming folder (C:\Users\<User>\AppData\Roaming\innovaphone) as "debug-info.zip".

Before you reproduce the problem, please enable the ''File Trace'' flag at "http://localhost:10006/debug.xml" and set the appropriate trace flags:

Which flags for which problem:

; Softwarephone looses registration at PBX: H.323/RAS, H.323/H.225, H.323/H.245
; Call setup phase: Signalling, H.323/RAS, H.323/H.225, H.323/H.245
; Audio problems: Signalling, H.323/ICE, H.323/DTLS, DSP trace, DSP Audiochannel. Please enable "DSP Audiocapture" only if specifically asked by innovaphone since it captures the complete audio stream and thus can generates huge files on the HD
; Headset button problems: Signalling, KEYS

'''NOTE: Please when providing a crash dump captured by icollect always use the latest SR (service release) of the softwarephone. Don't send us crash dumps of older versions since this will just take more time/effort to be analysed by our developer team.'''

== Important files for support in the debug-info.zip==
* '''trace.txt''' -> Trace File, created when '''File Trace''' is activated in debug.xml. Also contains version number (to find it, search for Build: )
* '''swphone_config.cfg''' -> one part of the config, can be used to check trace-flags.
* '''swphone_commands.cfg''' -> second part of the config, can be used to check trace-flags. Also contains version number
* '''dmp'''-file: named innovaphone '''SoftwarePhone#[version]#[id].dmp''' contains crash dump
** if crash without dmp file, '''StartTrace.txt''' contains trace of swphone start
* '''Wave-in/Wave-out''': created when DSP & DSP Audiochannel & DSP Audiocapture are activated.

=Known Issue=

=== Things to do before starting ===
Before starting debugging softwarephone issues, is always the best thing to:

- check if audio drivers on the PC/Laptop are updated to the last version

- check if the headset drivers are updated to the last version

- check that the Headset SDK is updated to the latest version

- check that network drivers are updated to the last version

- change registration protocol of softwarephone from UPD (H323) to TCP or TLS (H323/TCP or H323 TLS) to avoid any signaling issue

After updating the driver, please reboot the PC even if not requested by the OS.

Most cases are solved after updating drivers/software, especially if softwarephone won't start or no ringtones/audio device is automatically selected.

Also, please check that the files " swphone_config.cfg " and " swphone_commands.cfg " in the C:\Users\%user%\AppData\Roaming\innovaphone\softwarephone\ are not 0 Kbyte.
In this case, best is to reinstall the softwarephone with the latest version, and, after configuring it, restart it and check that the file " swphone_commands.cfg " is bigger then 6 KB.
If something is overwriting it (Windows policy, Antivirus), do the following:

- uninstall softwarephone

- reinstall it with Administrator rights

- start softwarephone and configure it (saving the changes)

- without closing it, navigate to the " C:\Users\%user%\AppData\Roaming\innovaphone\softwarephone\ " folder and put " swphone_config.cfg " and " swphone_commands.cfg " in read-only. Doing this, softwarephone will save the changes. Remember that doing this, if you want to changes some settings on softwarephone, you need to remove the "read-only" flag on the files (and re-apply it after the changes)

=== G.711 only and G729 Optional===
The software phone does support G.711 and Opus codec only, no G.723 or G.722.
Optionally we can use G729 if G729 Channel licenses are present and available on the PBX.

===Another program is blocking the softphone===

Another program (e.g XCAPI) might be listening on tcp port 1720 as well. If you want to use both programs simultaneously you can change the signaling port of the softphone to another port like 1721.

<nowiki>http://localhost/!config add PHONE SIG /ep-addr 0.0.0.0:1721</nowiki>

If you want to find out which program is listening on which port we recommend using a little tool called TCP View. You’ll find it here:

http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

=== No license obtained from PBX if SIP Protocol is used===

When using Innovaphone softwarephone with SIP Protocol no license it's obtained from the PBX. It's necessary to use H.323 always.

=== Headset Basestation doesn't Ring ===

Often it's reported that the Basestation of Wireless Headsets doesn't Ring on incoming call, this is a feature that is missing and there exist already a Feature Request for it - [[Support:DVL-Feature_Requests#Alerting_on_Wireless_headset_base_also | Alerting on Wireless headset base also]] .

=== Windows Volume lowers automatically when receiving a call ===

The volume can be set for swphone exclusively by the Windows mixer. It appears in the mixer because it has a Audio stream Interface to the Windows Audio System, but no way adjust the volume by itself. When such an effect occurs it is best to check the Windows configuration: if it is set to Change volume for applications when certain Events occur:

[http://superuser.com/questions/74116/windows-7-lowers-applications-volume-automatically Windows 7 lowers applications' volume automatically]

=== H.323/TLS Connection not Trusted by Default ===

Please check the [[Reference11r1:Concept_H.323_over_TCP/TLS_(H.460.17)#Known_Issues|H.323/TLS Known Issues article]].

=== Softwarephone does not work on Terminal Server ===
The software phone can only run once on a single system. This also implies that it does not work for terminals server systems such as e.g. Citrix, as only the first client session running on a server would be able to start a software phone. Furthermore, multiple RTP streams would impose quit a bit of load on the server.

=== Softwarephone can't place calls (call setup disappear as I press the "call" button") ===

After windows major update, some windows systems had their microphone rights turned off for all the application using it. This prevent the softwarephone to properly use the microphone.
To check this, press "windows key + i", navigate in "Privacy" - "Microphone" - and check that "Allow apps to access you microphone" is turned on. Sometimes, even if turned on, there is the need to turn "Allow apps to access you microphone" completely off and the on to "refresh" the app rights (softwarephone included)

Also check that windows firewall is not blocking softwarephone communication.

Please check also this page: " http://wiki.innovaphone.com/index.php?title=Howto:Softwarephone_recommended_settings#Registration_Protocol ". With softwarephone, is recommended to not use H323/UDP as protocol.

=== When PC is not used for some time, softwarephone won't work anymore ===

We noticed this behaviour on some Windows PC. This was due to the power management settings of Windows, that was turning off the USB ports to save power (this happen most on laptops)
To avoid this, open "Control Panel" (with Category view) - "Hardware and sound" - "Power options" . Under "Preferred plan" click the "Change plan settings" for the plan you are currently using.
Click the "Change advanced power settings" link
Expand "USB selective suspend settings"
Select "Disabled" form the drop-down menu
Click "Apply" and the "ok"

If you're changing the settings on a laptop, you'll see two options: On Battery and Plugged in, so make sure to change those settings accordingly.
This will prevent Windows 10 to power off USB devices connected to your computer (so your usb bluetooth headset connector)

=== Softwarephone doesn't start after upgrade to new version ===

On windows 10 PC, can happen that after installing the new softwarephone version without manually uninstalling the old one, softwarephone won't start anymore, and in the Windows event viewer you will see the softwarephone app crash with relative ntdll.dll error.
To solve this, manually uninstall the softwarephone, reboot the PC and install the new version.

=== Softwarephone 12r2 keep crashing on Windows 10 ===

We noticed some issue between Softwarephone 12r2 and Windows 10. If your softwarephone after Windows 10 major update 1809, doesn't start or start and keep restarting, uninstall Softwarephone 12r2, delete the Softwarephone folder in the AppData/Roaming/Innovaphone/ path, restart the PC and install Softwarephone 12r1 with Administrator rights. This should solve the issue.

=== Issue with permission on Appdata folder ===

After major windows update, can happen that permission for the appdata/Roaming folder are reset. To restore them please do the following:

Open "Run" by pressing Windows + R keys together.
Type: as C:\Users\USERNAME\AppData
Note: Replace C: with the letter of the drive where Windows is installed. Also replace USERNAME with the username of the account you’re logged in.

Click OK

Right-click on the Roaming folder

Click Properties

Go to the Security tab

Click “Edit -> Add”

Type “Everyone”

Click “Check names -> Ok -> Full control”

Click OK to save the changes

Restart your computer

Now softwarephone should be able to access all necessary files again.

=== Not removed system tray icons ===
Sometimes if the softwarephone loose connection, wifi/copper/vpn will be switched or crashes the application in the system tray will not removed.

=== Headset not recognize by softwarephone on Windows 10 ===

After Major windows update, headset is not recognize anymore. This can happen in case authorization by the OS for softwarephone to bind the headset to the softphone is denied.
To restore the headset detection, uninstall softwarephone 12r2 version and install the latest 12r1 softwarephone release. Doing this, NET framework 3.5 will be reinstalled, authorization restored, and headset should be recognized again.
Once headset is recognize, you can reinstall softwarephone 12r2 (latest) version and headset will work with the 12r2 version of softwarephone again.

=== Softwarephone Mac address is 00000000000 ===

To be able to obtain a Mac address, on the PC network card, netbios must be enabled.

IP112 Dati tecnici IT

2020-02-27T09:17:25Z

She:

{{Template:Disclaimer IT}}
==Immagine==
[[Image:IP111.png]]

==IP112 - IT==
===innovaphone IP112/IP112A===
Telefono IP Gigabit da scrivania e montaggio a parete, per l'innovaphone PBX
===Firmware===
*IP112: Il telefono funziona dalla Versione 11 o successive
*IP112A: Il telefono funziona dalla Versione 13r1 o successive
===Box===
Display a colori, 320 x 240 Pixel (3,5 Zoll)

Tastiera telefonica

2 x 6 tasti funzione (16 dinamici se usati in multifunzionalità)

9 tasti speciali

Dimensioni: 21,3 x 15,7 x 3,5 cm (base)

Peso: ca. 630 g
===Interfacce===
1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) con “Power over Ethernet” secondo IEEE 802.3af e “Energy Efficient Ethernet” secondo IEEE 802.3az

1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) per connessione PC

Attacco per alimentatore esterno

1 x USB 2.0 attacco per cuffia
===Hardware===
Alimentazione: alimentatore esterno: 12 V, 6 W o Power over Ethernet secondo IEEE 802.3af, Classe 2

128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale IT - Hardware Telefone}}

Interruttore:
*IP112: meccanico
*IP112A: sensorico (sostituisce IP112, disponibile Q1/2020)
===Codec voce===
G.711 A-law / µ-law, G.722 only

G.729A (non soggetto a licenza dalla V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB

Dynamic Jitter Buffering

Compensazione eco acustico

===Servizi generali===
[[V11_Phone_Firmware_Features IT#Datasheet|servizi generali telefoni innovaphone V11]]

[[V12_Phone_Firmware_Features IT#Datasheet|servizi generali telefoni innovaphone V12]]

===Servizi supplementari===
* Vivavoce, ascolto amplificato
===Licenze===
{{Template:Leistungsmerkmale_IT_-_Licenses_Phone}}
===Numero d'ordine===
01-00112-001

==Dichiarazioni CE==
===Conformità===
{{Template:CE-Decl_Phones}}

===Numero WEEE===
{{Template:WEEE-Number}}
[[Category:Dati tecnici IT|{{PAGENAME}}]]

IP112 Specyfikacja techniczna PL

2020-02-27T09:17:16Z

She:

{{Template:Disclaimer PL}}
==Zdjęcie produktu==
[[Image:IP111.png]]

==IP112 - PL==
===innovaphone IP112/IP112A===
Gigabit telefon biurkowy VoIP z możliowością montażu na ścianie, dla systemu innovaphone PBX

===Oprogramowanie===
* IP112: Wersja oprogramowania 11 lub nowsza
* IP112A: Wersja oprogramowania 13r1 lub nowsza
===Obudowa===
Kolorowy wyświetlacz, 320 x 240 Pixel (3,5 Zoll)

Klawiatura telefonu

2 x 6 klawisze funkcyjne (16 klawiszy dynamicznie przypisanych, wielokrotnego użytku)

9 przycisków specjalnych

Wymiary: 21,3 x 15,7 x 3,5 cm (Podstawa)

Waga: ok. 630 g

===Interfejsy===
1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) z “Power over Ethernet” zgodnie z IEEE 802.3af i “Energy Efficient Ethernet” zgodnie z IEEE 802.3az

1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) do połączenia z komputerem

Gniazdo zasilacza

1 x USB 2.0 do podłączenia zestawu słuchawkowego

===Hardware===
Zasilanie: Zewnętrzny zasilacz: 12 V, 6 W lub Power over Ethernet zgodnie z IEEE 802.3af, Class 2

128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale PL - Hardware Telefone}}

Przełącznik:
* IP112: mechaniczny
* IP112A: sensoryczny/bezdotykowy (zastępuje model IP112, dostępny w pierwszym kwartale 2020)
===Kodeki głosowe===
G.711 A-law / µ-law, G.722 only

G.729A (dostępny bez licencji od wersji V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (od wersji V12)

Dynamic Jitter Buffering

Akustyczna eliminacja echa

===Funkcje ogólne===
[[V11_Phone_Firmware_Features PL#Datasheet|Funkcje telefonów innovaphone oprogramowanie V11]]

[[V12_Phone_Firmware_Features PL#Datasheet|Funkcje telefonów innovaphone oprogramowanie V12]]

===Dodatkowe funkcje===
* Tryb głośnomówiący

===Licencje===
{{Template:Leistungsmerkmale_PL_-_Licenses_Phone}}
===Nr katalogowy===
01-00112-001

==Deklaracje CE==
===Deklaracje zgodności===
{{Template:CE-Decl_Phones}}

===Numer WEEE===
{{Template:WEEE-Number}}
[[Category:Specyfikacja techniczna PL|{{PAGENAME}}]]

IP112 Technische gegevens NL

2020-02-27T09:17:08Z

She:

{{Template:Disclaimer NL}}
==Afbeelding==
[[Image:IP111.png]]

==Technische gegevens==
===innovaphone IP112/IP112A===
Gigabit IP-telefoon voor bureau en wandmontage voor gebruik met de innovaphone PBX

===Firmware===
* IP112: dient gebruikt te worden met Versie 11 of hoger
* IP112A: dient gebruikt te worden met Versie 13r1 of hoger

===Behuizing===
Kleurendisplay, 320 x 240 Pixel (3,5")

Telefoontoetsenbord

2 x 6 functietoetsen (16 dynamisch toewijsbaar door meervoudig gebruik)

9 speciale toetsen

Afmetingen: 21,3 x 15,7 x 3,5 cm (Basis)

Gewicht: ± 630 g

===Interfaces===
1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) met “Power over Ethernet” volgens IEEE 802.3af en “Energy Efficient Ethernet” volgens IEEE 802.3az

1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) voor verbinding met PC

aansluiting voor externe voeding

1 x USB 2.0 Aansluiting voor headset
===Hardware===
Stroomvoorziening: externe voeding: 12 V, 6 W of Power over Ethernet volgens IEEE 802.3af, Class 2

128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale NL - Hardware Telefone}}

Haak schakelaar
* IP112: mechanisch
* IP112A: sensor-gebaseerd (vervangt IP112, beschikbaar Q1/2020)
===Spraakcodecs===
G.711 A-law / µ-law, G.722 only

G.729A (licentievrij vanaf V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (ab V12)

Dynamic Jitter Buffering

Akoestische echocompensatie

===Algemene kenmerken===
[[V11_eindtoestellen_firmware_technische_gegevens_NL#Datasheet|Algemene kenmerken V11 innovaphone telefoons]]

[[V12_Eindtoestellen_firmware_technische_gegevens_NL#|Algemene kenmerken V12 innovaphone telefoons]]

===Extra kenmerken===
* Handsfree spreken en luisteren
===Licenties===
{{Template:Leistungsmerkmale_NL_-_Licenses_Phone}}
===Bestelnummer===
01-00112-001

==CE-Declaraties==
===Conformiteiten===
{{Template:CE-Decl_Phones}}

===WEEE-Nummer===
{{Template:WEEE-Number}}
[[Category:Technische gegevens NL|{{PAGENAME}}]]

IP112 Fichas técnicas PT

2020-02-27T09:17:00Z

She:

{{Template:Disclaimer PT}}

==Imagem==
[[Image:IP111.png]]

==Ficha técnica / Datasheet==
===innovaphone IP112/IP112A===
Telefone IP para mesa, também adequado para montagem na parede, para operação no innovaphone PBX


===Firmware===
*IP112: Telefone compatível com a versão 11 e superior
*IP112A: Telefone compatível com a versão 13r1 e superior

===Características===
Display colorido, 320 x 240 pixels (3,5 polegadas)

Teclado do telefone

2 x 6 teclas de função dinâmica (uso múltiplo de 16 teclas dinamicamente atribuíveis)

9 teclas especiais

Dimensões: 21 x 15,5 x 3,5 cm (base)

Peso: aprox. 630 g

===Interfaces===
1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) com “Power over Ethernet” conforme IEEE 802.3af e Eficiência energética segundo IEEE 802.3az

1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) para conexão de PC

Entrada para alimentação externa

1 x USB 2.0 para conexão de headfone / auscultadores

===Hardware===
Alimentação: PSU externa 12 V, 6 W (opcional) ou “Power over Ethernet” conforme IEEE 802.3af, Class 1

Memória interna: 128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale PT - Hardware Telefone}}

Interruptor do gancho:
* IP112: mecânico
* IP112A: sensorial (substitui o IP112, disponível Q1/2020)
===Codecs de Voz===
G.711 A-law / μ-law, G.722

G.729A (livre de licenciamento a partir da V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (a partir da V12)

Dynamic Jitter Buffering

Cancelamento de eco acústico

===Características gerais===

[[V12_Phone_Firmware_Features PT#Datasheet|Funções genéricas do innovaphone firmware V12 para telefones]]

===Características especiais===
* Função Viva Voz (função mãos livres)
===Licenças===
{{Template:Leistungsmerkmale_PT_-_Licenses_Phone}}

===Código do produto===
01-00111-001

==Certificados CE==
===Declaração de conformidade===
{{Template:CE-Decl_Phones}}

===Número WEEE===
{{Template:WEEE-Number}}
[[Category:Fichas técnicas PT|{{PAGENAME}}]]

IP112 Ficha técnica ES

2020-02-27T09:16:49Z

She:

{{Template:Disclaimer ES}}
==Foto==
[[Image:IP111.png]]

==Ficha técnica==
===innovaphone IP112/IP112A===
Teléfono IP Gigabit de escritorio, también montaje en pared, para la PBX innovaphone

===Firmware===
* IP112: Teléfono compatible con la versión 11 y superiores
* IP112A: Teléfono compatible con la versión 13r1 y superiores
===Carcasa===
Pantalla a color, 320 x 240 pixel (3.5 pulgadas)

Teclado teléfono

2 x 6 teclas de función (16 asignación dinámica y de uso múltiple) e)

9 teclas especiales

Medidas: 21,3 x 15,7 x 3,5 cm (base)

Peso: aprox. 630 g
===Interfaces===
1 x Gigabit Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) con “Power over Ethernet” conforme con 802.3af y “Energy Efficient Ethernet” conforme con 802.3az

1 x Gigabit Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) para conexión de PC

Conector para fuente de alimentación externa

1 x puerto USB 2.0 para la conexión de auriculares
===Hardware===
Fuente de alimentación: PSU externa 12 V, 6 W o Power over Ethernet 802.3af, Class 2

128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale ES - Hardware Telefone}}

Interruptor de gancho:
* IP112: mecánico
* IP112A: sensorial (reemplaza a IP112, disponible Q1/2020)
===Voice codecs===
G.711 A-law / µ-law, G.722 only

G.729A (sin licencia a partir de la V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (a partir de la V12)

Dynamic Jitter Buffering

Compensación de eco acústico

===Características generales===
[[V11_Firmware_teléfonos_Ficha_técnica_ES#Datasheet|generic features V11 innovaphone phones]]

[[V12_Firmware_teléfonos_Ficha_técnica_ES#Datasheet|generic features V12 innovaphone phones]]
===Características especiales===
* Función manos libres (no dispone de función altavoz)
===Licencias===
{{Template:Leistungsmerkmale_ES_-_Licenses_Phone}}
===Cód. Art===
01-00112-001

==Certificados CE==
===Declaración de conformidad===
{{Template:CE-Decl_Phones}}

===Número WEEE===
{{Template:WEEE-Number}}
[[Category:Fichas técnicas ES|{{PAGENAME}}]]

IP112 Fiche technique FR

2020-02-27T09:16:41Z

She:

{{Template:Disclaimer FR}}
==Illustration==
[[Image:IP111.png]]

===innovaphone IP112/IP112A===
Téléphone IP Gigabit pour le bureau ou le montage mural - système innovaphone PBX

===Firmware===
* IP112: L'appareil fonctionne avec la version 11 ou supérieure
* IP112A: L'appareil fonctionne avec la version 13r1 ou supérieure

===Boîtier===
Ecran couleur, 320 x 240 Pixels (3,5 pouces)

Clavier du téléphone

2 x 6 touches de fonctions (16 multifonctions configurables)

9 touches spéciales

Dimensions : 21,3 x 15,7 x 3,5 cm (base)

Poids : 630 g environ
===Interfaces===
1 x Ethernet Gigabit : 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) avec “Power over Ethernet” selon IEEE 802.3af et “Energy Efficient Ethernet” selon IEEE 802.3az

1 x Ethernet Gigabit : 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) pour connexion PC

Connexion pour bloc d'alimentation

1 x USB 2.0 connexion micro-casque
===Hardware===
Alimentation : bloc d'alimentation externe : 12 V, 6 W ou Power over Ethernet selon IEEE 802.3af, Classe 2

128 Mo DDR3, 16 Mo Flash

{{Template:Leistungsmerkmale FR - Hardware Telefone}}

Système de raccrochage du combiné:
* IP112: mécanique
* IP112A: sensoriel (remplace IP112, disponible T1/2020)

===Codecs voix===
G.711 A-law / µ-law, G.722 only

G.729A (aucune licence requise à partir des versions V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (à partir de la V12)

Dynamic Jitter Buffering

Compensation d'écho

===Fonctionnalités générales===
[[V11_Phone_Firmware_Features FR#Datasheet|Fonctionnalités générales téléphones innovaphone V11]]

[[V12_Phone_Firmware_Features FR#Datasheet|Fonctionnalités générales téléphones innovaphone V12]]

===Fonctionnalités supplémentaires===
* Mains libres, écoute amplifiée
===Licences===
{{Template:Leistungsmerkmale_FR_-_Licenses_Phone}}

===Référence No.===
01-00112-001

==Déclarations CE==
===Conformité===
{{Template:CE-Decl_Phones}}

===WEEE No.===
{{Template:WEEE-Number}}
[[Category:Fiche technique FR|{{PAGENAME}}]]

IP112 Technical Data EN

2020-02-27T09:16:30Z

She:

{{Template:Disclaimer EN}}
==Illustration==
[[Image:IP111.png]]

==Technical Data==
===innovaphone IP112/IP112A===
Gigabit IP telephone for desktop or wall mounting for the innovaphone PBX

===Firmware===
* IP112: operated with Version 11 or higher
* IP112A: operated with Version 13r1 or higher

===Housing===
Colour display, 320 x 240 pixel (3.5 inch)

Telephone keypad

2 x 6 function keys (16 dynamically assignable by multiple use)

9 special keys

Measurements: 21,3 x 15,7 x 3,5 cm (base)

Weight: ca. 630 g
===Interfaces===
1 x Gigabit Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) with “Power over Ethernet” according to 802.3af and “Energy Efficient Ethernet” according to 802.3az

1 x Gigabit Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) for PC connection

Connector for external power supply

1 x USB 2.0 port for headset connection
===Hardware===
Power supply: external PSU 12 V, 6 W or Power over Ethernet 802.3af, Class 2

128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale EN - Hardware Telefone}}

Hook switch:
* IP112: mechanical
* IP112A: sensorical (replaces IP112, available Q1/2020)

===Voice Codecs===
G.711 A-law / µ-law, G.722 only

G.729A (free of charge since V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (starting with V12)

Dynamic Jitter Buffering

Acoustic echo cancellation

===Generic Features===
[[V11_Phone_Firmware_Features EN#Datasheet|Generic features V11 innovaphone phones]]

[[V12_Phone_Firmware_Features EN#Datasheet|Generic features V12 innovaphone phones]]

===Supplementary Features===
* Hands-free, open listening

===Licenses===
{{Template:Leistungsmerkmale_EN_-_Licenses_Phone}}

===Order Number===
01-00112-001

==CE Declarations==
===Conformities===
{{Template:CE-Decl_Phones}}

===WEEE Number===
{{Template:WEEE-Number}}
[[Category:Technical Data EN|{{PAGENAME}}]]

= Related Documentation =
* [http://wiki.innovaphone.com/index.php?title=Howto:Videos#IP112 Tutorial Videos]

IP112 Technische Daten DE

2020-02-27T09:15:53Z

She:

{{Template:Disclaimer DE}}
==Illustration==
[[Image:IP111.png]]

==Technische Daten==
===innovaphone IP112/IP112A===
Gigabit IP-Telefon für Schreibtisch und Wandmontage zum Betrieb an der innovaphone PBX

===Firmware===
* IP112: betreibbar mit Version 11 oder höher
* IP112A: betreibbar mit Version 13r1 oder höher

===Gehäuse===
Farbdisplay, 320 x 240 Pixel (3,5 Zoll)

Telefontastatur

2 x 6 Funktionstasten (durch Mehrfachnutzung 16 dynamisch belegbar)

9 Spezialtasten

Maße: 21,3 x 15,7 x 3,5 cm (Basis)

Gewicht: ca. 630 g
===Schnittstellen===
1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) mit “Power over Ethernet” nach IEEE 802.3af und “Energy Efficient Ethernet” nach IEEE 802.3az

1 x Gigabit-Ethernet: 1000-BASE-T (auto negotiation), RJ-45 (modular Jack 8P8C) für PC Anbindung

Anschluss für Steckernetzteil

1 x USB 2.0 Anschluss für Kopfhörer
===Hardware===
Stromversorgung: externes Netzteil: 12 V, 6 W oder Power over Ethernet nach IEEE 802.3af, Class 2

128 MB DDR3, 16 MB Flash

{{Template:Leistungsmerkmale DE - Hardware Telefone}}

Gabelumschalter:
* IP112: mechanisch
* IP112A: sensorisch (ersetzt IP112, verfügbar Q1/2020)

===Sprach Coder===
G.711 A-law / µ-law, G.722 only

G.729A (lizenzfrei ab V11r2sr23/V12r1sr7)

Opus-NB, Opus-WB (ab V12)

Dynamic Jitter Buffering

Akustische Echo Kompensation

===Allgemeine Leistungsmerkmale===
[[V11_Phone_Firmware_Features DE#Datasheet|allgemeine Leistungmerkmale V11 innovaphone Telefone]]

[[V12_Phone_Firmware_Features DE#Datasheet|allgemeine Leistungmerkmale V12 innovaphone Telefone]]

===Zusätzliche Leistungsmerkmale===
* Freisprechen, Lauthören
===Lizenzen===
{{Template:Leistungsmerkmale DE - Lizenzen Telefone}}

===Bestellnummer===
01-00112-001

==CE-Deklarationen==
===Konformitäten===
{{Template:CE-Decl_Phones}}

===WEEE-Nummer===
{{Template:WEEE-Number}}
[[Category:Technische Daten DE|{{PAGENAME}}]]

Howto:Firmware Upgrade V11r2 V12r1

2020-02-26T10:24:36Z

She:

== Applies To ==
This information applies to:


* All PBX devices
* All DECT devices
* Linux Application Platform

== Migration Policy ==

== Configuration Changes ==
=== Automatic Media Relay ===
Up and including v12r2, the PBX and relay have done ''media-relay'' for all calls between ''public'' and ''private'' network addresses. From v12r1 on, this is done only if ''Media Relay'' explicitly set to <code>Auto</code> in the PBX or in a gateway interface.
<internal>communote: https://communote.innovaphone.com/microblog/global/portal/topics/12r1/notes/45172</internal>

== Linux Application Platform and its applications ==
xx11/11xx gateways can host a LinuxPlatform as well.
First LinuxImage which as well fits for the new hardware types is V10sr32 (Build 100210).
This build contains TWO linux images labeled
*Image-6010-3.4.10 - for old hardware types
*Image-IPx11-4.4.0 - for new hardware types (xx11/11xx)
Pay attention to the definition of used "Linux Kernel file" at Linux/General - especially when moving configuration files from "old" to "new" hardware types.

Please note that there is no v12 version of the linux application platform, so you still will be using [http://download.innovaphone.com/ice/10.00/#linux Linux Application Platform V10.00]!

==Known Problems==
=== Main Memory (RAM) Considerations ===
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot. As a rough rule of thumb, a v12r1 release will consume 1.5MB RAM and 0.8MB flash more compared to a v11r2 firmware.

Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Recommended__number_of_users_supported | to spec ]] will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in [[Reference:Device Health Check]].

Special care has to be taken for old devices with less memory than suggested by current specs. Most notably, these are the older IP30x models (hardware build 306 or less, which had 16MB RAM as opposed to 32MB in the current models). We do not recommend to upgrade such old hardware to a current firmware version unless it has been determined that the configuration in question will work.

=== Flash Memory Considerations ===
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, the IP800/IP22/IP24/IP38/IP302/IP305 may run out of flash memory during upgrade to v12r1. Here is the recommended procedure for upgrade on such devices:

* save entire configuration
* reset to factory defaults
* load saved configuration (this will reorganize flash memory usage)
* upgrade to new firmware

When there is still not enough flash memory available to store the new firmware, the web GUI will issue a ''Firmwareupdate failed:no space'' during firmware upload. If the firmware upload is done using the update client, a ''Error 0x00130001 Major FLASHMAN0 no space'' event will occur.

With the new firmware, the amount of flash memory allocatable for the LDAP directory (that is, PBX config and call lists) is less than before to accommodate for the larger requirements. It is reduced from 3200kB to 2816kB on the IP800 and from 3200kB to 2560kB on the IP22/IP24/IP38/IP302/IP305.

On older IP110, IP200a, IP230 and IP240 phones, the PPP module has been removed from the firmware to keep the flash memory allocatable for the LDAP directory (that is, local phone book and call lists) unchanged.
Following file naming applies:
* <code>ip110,ip200a,ip230,ip240.bin</code> support H.323 w/o PPP
* <code>ip110,ip200a,ip230,ip240</code>'''-sip'''.bin support SIP w/o PPP
* <code>xxx-no-ppp.bin</code> files are obsolete

=== No /DRIVE/CX0 any more ===
The /DRIVE/CX0 announcement file encoder has been removed. Use [https://www.innovaphone.com/en/support/convert.html the web based converter] instead.

=== SIP Digest Authentication ===
We have implemented protection against [https://tools.ietf.org/html/rfc2069#section-3.2 Replay Attacks] for the [https://tools.ietf.org/html/rfc3261#section-22.4 SIP Digest Authentication].

In v12 (or later) we exercise the "one-time digests" strategy.
A formally correct Digest Response is not accepted a second time.
A client is required to increment the "nc" parameter if it issues another request.

If the client does not support this requirement the PBX will reject the registration.
There is a config option to disable the protection.
'''But it is not recommended to disable this feature. It's a security feature.'''

# for SIP/UDP
http://ip-of-pbx/!config change SIP /disable-digest-replay-check
# for SIP/TCP
http://ip-of-pbx/!config change TSIP /disable-digest-replay-check
# for SIP/TLS
http://ip-of-pbx/!config change SIPS /disable-digest-replay-check
http://ip-of-pbx/!config write
http://ip-of-pbx/!config activate

You get a hint with the SIP/2.0 401 Unauthorized message (wireshark pcap)

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.88.142:5060;branch=z9hG4bK5d7b5284edaa9bed3e3a323dc78f4022;rport=5060;received=192.168.88.142
From: <sip:111@192.168.88.134>;tag=2469966351
To: <sip:111@192.168.88.134>;tag=1151509663
Call-ID: 3129114392@192_168_88_142
CSeq: 1903 REGISTER
Content-Length: 0
Date: Fri, 06 May 2016 13:54:31 GMT
'''Warning: Digest replay attack detected'''
WWW-Authenticate: Digest realm="192.168.88.134",nonce="859b13f3852c5701116600903340032b",qop="auth",algorithm=MD5

We have added a new option to the SIP module. If you have problems to register your SIP client with an authentication. Please use the latest available version V12r1.

http://ip-of-pbx/!config [^] change SIP /no-authentication-info
http://ip-of-pbx/!config [^] write
http://ip-of-pbx/!config [^] activate

Some SIP clients did not support it or did not work well. So you have to disable the authentication-info.

The client has to support the

RFC-2617:
nonce-count
This MUST be specified if a qop directive is sent (see above), and
MUST NOT be specified if the server did not send a qop directive in
the WWW-Authenticate header field. The nc-value is the hexadecimal
count of the number of requests (including the current request)
that the client has sent with the nonce value in this request. For
example, in the first request sent in response to a given nonce
value, the client sends "nc=00000001". The purpose of this
directive is to allow the server to detect request replays by
maintaining its own copy of this count - if the same nc-value is
seen twice, then the request is a replay.

=== Special Precaution required when upgrading IPxx11 Gateways from pre-V11r2 sr13 or any V12r1 preview ===
There is an issue with cache coherency when multiple device drivers access the internal flash memory. In particular, if the SSD is used (by Linux or WebDAV), wrong data may be read from the internal flash (resulting in lost PBX objects for example). This issue has been fixed in V11r2 SR14.

However, during a firmware upgrade, this may result in corruption of some inherent device information such as the device's MAC address.

See [[Support:Special Precaution required when upgrading IPxx11 Gateways from pre-SR14 Firmware Versions]]!

===Replicating objects from a dynPBX as dynPBX (Standby PBX)===
It’s necessary to a add a dynPBX Id in the configuration of a Standby PBX in V12 if you are trying to a replication objects from a dynPBX to a dynPBX. In V11 you had to leave it empty because it used its own Id to find it at the master.

== Related Articles ==
*[[Howto:Guideline V5 to V6 upgrade]]
*[[Howto:Upgrade Issues V5 to V6]]
*[[Howto:Firmware Upgrade V6 V7]]
*[[Howto:Firmware Upgrade V7 V8]]
*[[Howto:Firmware Upgrade V8 V9]]
*[[Howto:Firmware Upgrade V9 V10]]
*[[Howto:Firmware Upgrade V10 V11r1]]
*[[Howto:Firmware Upgrade V11r1 V11r2]]
*[[Support:Special_Precaution_required_when_upgrading_IPxx11_Gateways_from_pre-SR14_Firmware_Versions]]
*[[Howto:Firmware Upgrade V12r1 V12r2]]
*[[Howto:Firmware_Upgrade_V12r2_V13r1]]
[[Category:Howto|{{PAGENAME}}]]

Reference13r1:PBX/Objects/Trunk Line

2020-02-07T15:32:52Z

She:

The Trunk Line object is typically used to register gateways to external lines. Several registrations are accepted. Calls sent to the trunk object are sent to the registrations in a round-robin manor. If the call to a registration fails in a way that indicates a local problem the next registration is tried.

Some general diversions can be configured for incoming calls e.g. for calls to invalid numbers.

== Trunk Object specific configuration ==

;Loopback: Destination (Name or Number) to which calls are forwarded, which dialed the same Trunk object. This is typically used if the number of the Trunk object (e.g. 0) shall be used as extension number of the switchboard for incoming calls. If the '''Internal''' checkmark is set, this is executed also if the trunk is called from within the PBX with a calling party number matching the number of the trunk object. This can happen if for example an escape is configured for the node of the trunk object matching the number of the trunk object.

;Incomplete: Destination (Name or Number) to which calls are forwarded, which dialed an incomplete number. If the incoming call is enblock this can be determined immediatelly. For overlap receiving calls a timeout of 4s is used. Sometimes it is desired that calls without extension number are sent to the switchboard. In this case the number of the switchboard should be configured here.

;Invalid: Destination (Name or Number) to which calls are forwarded, which dialed an invalid number. Typically the number of the switchboard is configured here so that incoming calls whith an invalid extention are not lost. This is executed also for calls rejected because of the 'Reject ext. Calls' property at a called object.

;Busy: Destination (Name or Number) to which calls are forwarded, which dialed a busy number. If a CFB is configured at a called user this takes precedence. A CFB at at the called user to a number '''-''' turns this off for this user.

;Rejected: Calls which are rejected by the user (busy after alert), can be redirected to a configurable destination.

;No Answer: Destination (Name or Number) to which calls are forwarded, which dialed a destination which exists, but does not answer. The timeout value is configured in the '''Response Timeout''' field (on PBX/General or at the User object) which is used for CFNR as well. (There is no field '''Timeout''' configurable for this anymore) If a CFNR is configured at a called user this takes precedence. A CFNR at the called user to a number '''-''' turns this off for this user.

;Reroute supported: This check box turn on rerouting of incoming calls which are diverted to the same Trunk object. Normally an incoming call which is diverted to the same Trunk object is sent out on the Trunk as normal outgoing call. If this option is checked a reroute request is sent out instead. If the call is received from an ISDN interface this is mapped to partial rerouting. By doing this no channel is used on the ISDN interface for such a call (instead of 2) and the original calling party number is sent to the final destination by the ISDN network. Rerouting is supported only for CFU and CFB, not for CFNR.

:If your Provider does not support (partial) rerouting and you nevertheless configure ''Reroute supported'', the call forward will fail with a cause code ''Recovery on timer expiry.''

;Set Calling=Diverting No: Concerns calls that arrive on the PBX via the Trunk Line PBX object and are then forwarded by CFU, CFB or CFNR again to the Trunk Line object. For example: Subscriber A calls subscriber B. Subscriber B forwards the call from subscriber A to subscriber C. The CGPN (Calling Party Number) remains unchanged for a call diversion. Merely the DGPN (Diverting Party Number) is also sent as information, so that both call numbers are visible at the diversion destination (subscriber C). For an external call diversion to the PSTN, it may not be permitted to use an external CGPN (subscriber A), however. Therefore, the CGPN must be replaced by an associated call number, in this case the DGPN (subscriber B). If this check box is not enabled, the local telephone office, in such as case, will automatically replace the CGPN through "screening". If you enable this check box, the diversion call is signalled as a normal outgoing call. The CGPN is then a number that belongs to the connection (subscriber B).

; Set Diverting=Calling No: For calls from the PBX to the trunk, the ''calling party number'' (CGPN) is set as ''diverting number'' (DGPN) (a.k.a. ''leg2 info'') if there is none yet in the call. If set, the party the call needs to be billed to is always included in the DGPN thus

;Discard received diverting No: If set, received diverting info within calls from the trunk are discarded

;Outgoing Calls restricted: If this checkmark is set all calls sent out on the Trunk object are sent with CLIR (Calling Line Identification Restricted).

;Automatic Hangup: If this checkmark is set calls, which were already connected and then diconnected by remote party, are automatically released (hung up) two seconds after the disconnect, even if in-band info was indicated with the disconnect. This is useful when providers indicate but do not provide in-band info, or in general, because most providers only provide a busy tone in this situation and no announcement, so 2s are more then enough.

;Outgoing Calls CGPN: If a number is configured here all calls sent out to the Trunk object are sent with this number as Calling extension. For example the number of the switchboard can be configured here so that callbacks are not sent to the original caller but to the switchboard.

;Outgoing No Name: If this checkmark is set no calling name nor calling name display information is sent with outgoing calls

;No Presence/Dialog Subscribe: If checked, no presence or dialog subscriptions are forward out through this Trunk line object.

;Fake Connect on inc. Call: If this checkmark is set an incoming call is connected (send out a fake connect message) as soon as inband info is available from the destination of the call even if the destination did not connect the call already. This is esspecially useful for call forward out to a public network, so that the caller can hear the real inband info from the public network. Also timeouts can be avoided in such a case for the incoming call if the call is forwarded to a destination with slow alert or connect (e.g. GSM). Since v10 if there is no in-band info, now an alert is sent on this call in this case.

;Name as Number: This option allows to send a Name of a PBX object as calling number for outgoing calls. The source name of the call is compared to the first field. If the name starts with the configured string, any digit in the remaining name is sent as calling line id. The second field may contain a number which is added as prefix to the calling line id. For incoming calls the called number is matched to the second field and in case of a match a name is called composed of the first field and any additional dialed digits. This way the same number can be used to call an endpoint as is displayed as calling line id.

:If the configured name starts with '?' for a match only the part starting with the first '?' in the calling name is used. This way for a user a name can be configured with <name>?<external number> and when the user calls out of this trunk, the calling line id is replaced by the external number. For calling a user only the part before the '?' is used to find the user.

== Devices ==

The device configuration is used as always to allow the registrations of devices. In case of a trunk object this is typically a gateway or SBC.

The name of the device serves one special purpose, if the name starts with '#'. In this case, if a call is sent out to the trunk and the calling party number of this calls matches the digits following the '#', not just the next gateway is used, but instead the registration with the matching name is used. Incoming calls on such a registration are sent to the number following the '#'. This way multiple registrations to SIP providers can be mapped to internal numbers for incoming and outgoing calls.

== Multiple Gateway Registrations ==

If multiple Gateways are registered to a Trunk object, Gateways registered to the same device config are used round-robin. The gateways registered to different devices are used in the sequence of the configured devices.

== Call Diversions ==
;CFU: If configured a CFU is executed, so calls to the Trunk object are diverted.
;CFB: A CFB is executed if a call is rejected with User Busy by remote destination
;CFNR: A CFNR is executed if a call is rejected because of a local problem (no channel, no gateway registered, ...)

== Group Indications ==

The trunk object generates group indications for incoming and outgoing calls including a park position (a number from 0 to n), which is sort of a virtual channel number. Together with Park function keys on the phone this can be used to simulate an oldstyle key system, so that each phone can have Line keys (the Park function key) for each available line (the position). With these Line keys a line can be aquired, monitored, a call can be parked on the line and picked up from the line.

Reference13r1:Concept Software Rental

2020-01-22T10:04:01Z

She:

The software rental may include all the innovaphone software licenses indicated in the price list.
The rental fee is charged via the so-called iSC (innovaphone service credits), managed in the respective customer account. iSC can be purchased through an authorized innovaphone partner.

==Applies To==
This information applies to
* innovaphone PBX from version 13r1

==Requirements==
* innovaphone PBX version 13r1 sr3 or higher
* a running App Platform and access to the Devices App

==Rental program and Payment method==
innovaphone uses iSC (innovaphone Service Credits) as a currency for the flexible rental programe. The iSC are bound on a customer specific account. As soon as a software license is activated for renting, the account balance starts decreasing, in function of the given rental configuration.
* iSC can be ordered via the innovaphone sales channel and are managed through the myApps Platform. The delivery is realized in form of an activation key. Then iSC are loaded through the Devices App to a specific customer account. The customer account is logically connected to the my.innovaphone license portal. The rental licenses however, are managed exclusively via the Devices App. An direct access to my.innovaphone is '''not''' necessary!
* iSC are not bound to specific software licenses or devices, but to a customer account. Existing iSC balances can therefore be used flexibly, by the same customer, to rent other licenses or services.
* The rental program is operational, as long as a positive iSC balance is available on the customer account. The rental does terminate immediately when the iSC balance becomes zero. A negative iSC balance is not accepted.
* Starting 7 weeks before a customer will run out of iSC, a weekly alert email will remind the administrator to recharge the customer account with iSC. This feature has to be activated in the domain settings, <Edit> tab, by entering an email address in the field <E-mail address(es) for warning of rental expiration>.

====Software Rental Program====
This program can apply to two different scenarios (with a different pricing):
* software operated on devices at the customer's premises. This could eventually be the innovaphone PBX software, conferencing licenses, etc. installed on innovaphone hardware (a Gateway, such as IP3011) or a private virtual machine (IPVA) on a customer owned server, typically operated at the customers location.
* software operated within the myApps Cloud Service, a cloud platform operated by innovaphone. In this case an innovaphone PBX software, conferencing licenses, etc. are operated within the innovaphone cloud platform.

====Hardware licenses====
* Eventually needed Hardware licenses (e.g. channel licenses) have to be bound on the specific device in my.innovaphone itself (currently this is not be handled within the Devices App). Those need to be downloaded from my.innovaphone and on the device with the already known methods.

====Technical aspects====
The rental duration is calculated on each license or balance change in the domain. Consequently, after each change in the configuration new licenses, with a new duration are transferred to the gateways and also stored in the Devices App itself.
If the rental expires, the gateway reboots and the licenses are not operational anymore.
The licenses are also transferred after each reconnect of a gateway to the Devices App.
[[Remarks:]]
* For license and balance changes, the Devices App must be online and have access to my.innovaphone.com!

====FAQ====
* '''Question:''' Is it possible to divide a given activation key (e.g. containing 1000 iSC) and to charge various customer accounts? '''Answer:''' YES, this is possible! '''Procced like this:''' (1) Open [http://my.innovaphone.com my.innpvaphone.com] and click on the "Licences" tab. Following, select your project. (2) Press "Add" and paste the given activation key. Then press <Next>. (3) The iSC value, contained in the given activation key, is displayed. Press <OK> to bind this iSC value to your own balance. (4) Via the tab "Own Activations" followed by "Create", new activation keys can be created, until the balance is zero. (5) For further information, please refere to the aticle [http://wiki.innovaphone.com/index.php?title=Reference:My_Innovaphone Reference:My Innovaphone].

==Activation==
The procedure for the activation of Software Rental is nearly identical, for both previously mentioned scenarios.
* In the devices App, select the domain for which rental will be activated.
* Select the tab “Software Rental”
* If you already have a my.innovaphone account, please enter username and password, and press <Register>.
In case you still do not have a my.innovaphone account, please click on the link “New-Registration”.
* Depending on the previously selected option, the installation requires to fill out the respective data in regards to who is renting the software:
** Please enter the personal <email address> and <password> of the person in charge. Impersonalized emails accounts, team or group emails, such as team@..., sales@..., info@.... are not allowed here.
** In continuation, please enter company name, address, zip-code, city, country, etc.
* Please carefully read the conditions of the software rental contract, if you agree, please accept by press the respective button.
** Please be aware: If the email address is new and unknown to my.innovaphone, it might be verified by sending an email verification code.
* As a contract copy, the accepted rental contract will be sent by email to the person in charge.
* Finally, you will reach the software rental configuration screen.

==Charge iSC Account Balance==
* Press the button <Charge Balance>. [[Image:Ref13r1ConceptSwRental Charge01.png]]

* Paste the activation-key and press <Check> to verify its validity. [[Image:Ref13r1ConceptSwRental_Charge03.png]]

* If the activation-key contains the expected iSC value, proceed by charging the value onto your customer account. [[Image:Ref13r1ConceptSwRental_Charge04.png]]

* The new balance appears in the menu. Eventually prior activated software licenses are deducted immediately. [[Image:Ref13r1ConceptSwRental_Charge05.png]]

* An additional information field is indicating the monthly consumption of iSC, based on the rented software licenses (configuration below). In addition, the possible operation period is displayed, calculated on the given iSC balance. [[Image:Ref13r1ConceptSwRental_Charge06.png]]

[[Remarks:]]
* The rental costs are deducted in seconds, starting from the moment of activation. If no iSC are loaded into the customer iSC account, the operation of the rented installation will not initiate or be discontinued automatically.

==Configuration==
* In the first step, use the drop-down menu, to select the PBX for “software rental” operations, and press <Add to rent>. [[Image:Ref13r1ConceptSwRental_Config01.pngRef13r1ConceptSwRental_Config01.png]]

* Select the required software licenses, jointly with amount of licenses needed (e.g. Port-Lic x 25, UC-Lic x 25, etc.). Beneath each license item, the corresponding charges in iSC per month are displayed. To add this license to the PBX press <Add license>. [[Image:Ref13r1ConceptSwRental_Config01.pngRef13r1ConceptSwRental_Config03.png]]

* The areas and values marked with yellow color indicate the changes, compared to the prior configuration. Thus, it is possible to see the consumption preview per PBX (important, in case there are more than one PBXs) and the total consumption preview for the entire account. - Further licenses can be included by pressing <Add license> [[Image:Ref13r1ConceptSwRental_Config04.png]]

* To finalize the configuration, when all required software licenses have been configured, press <Apply> [[Image:Ref13r1ConceptSwRental_Config05.png]]

* Please verify, the monthly iSC consumption, for the newly created software renting configuration. To accept and activate the charging of the iSC balance, press <Change with costs>. [[Image:Ref13r1ConceptSwRental_Config06.png]]

* The software configuration of this PBX is activated successfully. The new monthly iSC consumption is displayed, beneath the PBX name. The iSC account balance is decreasing, in accordance with the configured iSC charges. The calculation is made on a per second basis. [[Image:Ref13r1ConceptSwRental_Config07.png]]

==Known Issues==
===Reinstall of the PBX or Devices App===
Currently the leased licenses are bound to the PBX only when clicked on the confirmation button ''"Chargeable change"/"Kostenpflichtig ändern"''. If the PBX has to be reinstalled you need to edit rental licenses and then click on this button to load the rental licenses in the PBX again

===No mixed licenses===
If you have licenses of different versions you can only use the software of the smallest version. As well please be aware if you have software rental licenses of v13 and the PBX receives from another device v12 licenses that this causes problems.

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

Howto:Working with multiple Door Cameras

2020-01-16T13:16:25Z

She: /* doors */

==Applies To==
This information applies to

* V10 and innovaphone PBX platform
* innovaphone phones supporting video
* web server running PHP 5

some innovaphone phones support display of a door phone camera picture (see [[Howto:Door Phone with Video in V10 and later]]). However, only one camera is supported. This article describes a solution for use of multiple door cameras.



==More Information==
=== Overview ===
When multiple door cameras are used, the standard mechanism described in [[Howto:Door Phone with Video in V10 and later]] is not sufficient, as the URL used in the phone is static and will always show the same door camera. Instead, the image should switch from one camera to the next continuously. Also, when the operator is called by the door phone, the picture from the calling door should be shown always and the phone UI should switch to the ''Video'' app. This can be achieved using a this SOAP-based utility.

=== Prerequisites ===
This SOAP script requires a web server running PHP5. A [[Reference10:Concept_Linux_Application_Platform | Linux Application Platform ]] is fine, but any other PHP platform should do too.

For the ''switch to video app'' feature, you need at least script version 1005 and telephone firmware which includes fix ''17611 - Phones: Remote Control Facility "switch2App"'' (that is, v12r2 - beta 1 (125048) or later).

===Download ===
*[http://download.innovaphone.com/ice/wiki-src#doorcontrol http://download.innovaphone.com/ice/wiki-src#doorcontrol ] - download the complete file package of scripts and files described in this article.

=== Installation ===
Unpack the downloaded file (see [[#Download]]). Copy the content of the <code>Solution/sources</code> directory (including the sub directories) to your web server.

==== On a Linux Application Platform ====
To install the utility on a [[ Reference10:Concept_Linux_Application_Platform| Linux Application Platform ]], you may proceed as follows
* open the LAP's file system using a SFTP client such as e.g. WinSCP (if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]]). Note that you must use SFTP rather than WebDAV, as WebDAV will not give access to the executable web server files
** create the new directory called <code>doorcontrol</code> underneath the <code>/var/www/innovaphone</code> directory.
** copy the files <code>doors.xml</code>, <code>switchops.xml</code> and <code>DoorControl.php</code> to the new directory
** create a subdirectoy <code>/doorcontrol/classes</code>
** change to this directory
** copy the file <code>innopbx.class.php</code> to the new directory
* log in to the LAP's admin UI (if you have not yet changed it, the default credentials will be <code>admin/linux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** go to ''Administration/Web Server/Change web server properties and public access to the web/webdav''
** add <code>doorcontrol</code> to ''Public Web Paths''
* log in the LAP's root shell (using e.g. putty, if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** <code>cd</code> to <code>/var/www/innovaphone</code>
** change owner of <code>doorcontrol</code> and all its sub -directories to <code>www-data</code> (e.g. <code>chown -R www-data doorcontrol</code>)

After you have finished the configuration open your web browser and go to <code>http://your-web-server-name-or-ip/path-you-installed-the-toolto/DoorControl.php?debug</code>. You should see something like
''number'' seconds since last switch ...
switching to next ''name-of-door''
...

===Configuration===
Configuration needs to be done in the <code>doors.xml</code> file that comes with the <code>DoorControl.php</code> script and on the phone that is used to monitor the door video(s).

When the ''switch to video app'' function is used (see [[#PBX | below]]), additional configuration on the PBX is required.
==== doors.xml ====
The utility comes with a working sample configuration (in <code>doors.xml</code>). This file must reside in the same directory you installed the PHP script (<code>DoorControl.php</code>) too. The sample file looks like this:
<code xml>
<?xml version="1.0" encoding="UTF-8"?>
<doors
pbx="1.2.3.4"
pbxhttp="demo"
pbxpw="demo"
pbxuser="_TAPI_"
interval="5"
switch="false"
>
<door name="door" url="http://wiki.innovaphone.com/images/innoWiki.png"/>
<door name="behnke" url="https://www.innovaphone.com/content/images/innovaphone-slider-uc.png" proxy="true" content-type="image/png"/>
</doors>
</code>
===== doors =====
The root tag <code>doors</code> has a few attributes which define the PBX access (used to determine if a phone is being called by a door phone):
; pbx : the IP address of the PBX
; pbxhttp : the HTTP user to be used to access the SOAP service on the PBX (usually the ''Name''' of a PBX user object with minimum [[Reference9:PBX/Objects/Edit_Rights|''Groups/Call Forwards only'' access right]] or the admin user of the box)
; pbxpw : the password of the HTTP user
; pbxuser : the ''Long Name'' of a user object that is used to access the SOAP service on the PBX

Also, the interval between switching the available door cams must be defined
; interval : the number of seconds the utility will wait before switchign to the next camera

Finally, you can optionally have the phone switch to the ''video app'' automatically:
; switch : <code>true</code> or <code>false</code>. If set to ''true'', the script will notify the phone when it detects a call from a door, so that the phone switches to the video app. This requires fix [[Support:DVL-Roadmap_Firmware_12r2#17611_-_Phones:_Remote_Control_Facility_.22switch2App.22 | Remote Control Facility "switch2App"]] and therefore firmware ''v12r2 beta 1'' or later. Also it requires at least script version 1004.
====== door ======
Each sub-tag <code>door</code> defines an available door camera.
; url
: the URL to retrieve a single picture from this camera. You must use the single-picture URL here (usually ending in <code>.jpg</code>), not the picture stream (<code>.mjpg</code>). Otherwise, the phone will never switch to the next camera.
; name
: the ''Name'' of the PBX user object the door phone is registered with

'''Proxy Access to Door Camera '''

In normal operation, this script will not deliver the door cam image itself to the caller. Instead, it will tell the calling client the URL where the current door cam image can be retrieved (using a <code>HTTP/1.1 307 Temporary Redirect</code> response with a <code>Location: ...</code> header). The phone will then refer to this URL and retrieve the image itself.

However, in rare situations this may not work (e.g. [http://www.axis.com/global/en AXIS] cameras are known to be incompatible with the HTTP client built-in to the innovaphone phone when the image requires authentication). In this case, the script behaviour can be modified so that the image actually is retrieved by the script and then returned to the caller.

; proxy
: if this is set to <code>true</code>, the image will be retrieved by the script and returned to the caller directly
; user
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication user-name here
; pw
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication password here
; content-type
: you can optionally specify the value used for the <code>Content-Type:</code> HTTP header (normally not necessary)
; proxy-skip-ssl-verify [since build 1009]
: if this is set to <code>true</code>, SSL-Certificate of the given <code>url</code> will not be verified
; proxy-resize [since build 1009]
: if this is set to <code>true</code>, the big pictures will be resized for IP-Phone. The size is depending on the phone model and must not be configured. You can use this method if your camera is not able to provide small images. Please note that this increase the ressource usage on your webserver and should only used if your camera does not support the resize process itself.

==== Phone ====
The ''door operator''s phone (that is, the phone that shall monitor the video image of the door(s)) needs some configuration as follows.

The ''Background Image'' property in [[Reference11r1:Phone/Preferences | Phone/Preferences ]] must be set to the DoorControl.php script on your web server. It supports 2 arguments
; id : e.g. <code>id=operator</code>, the ''Long Name'' of the PBX user object the retrieving phone is registered with. The script will use this name to query the PBX if the phone is currently being called by a door phone. (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; hw : e.g. <code>hw=0090333e0c57</code>, the ''Hardware Id'' used to register the operator's phone (optional, may be omitted if the operator does not have multiple registrations or mobility). Requires at least script version 1004 (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; debug : if this is set, the script will not deliver the requested picture but will spit out some debug information

Please note that you must also add the query arguments not processed by the <code>DoorPhone.php</code> script but by the phone itself, namely
; refresh : e.g. <code>refresh=1</code>, see ''Background Image'' in [[Reference11r1:Phone/Preferences]] and [[Howto:Door Phone with Video in V10 and later]]

So you may end up with something like <code>http://my.door.tld/path-on-web-server/DoorControl.php?refresh=1&id=operator&hw=009033000000</code>.

===== Picture Sources with Password Protection =====
If your camera is password protected, you must configure its URL and password in ''Services/HTTP/Client/Authenticated URLs''.

===== Multiple Agents =====
If you want to serve this function to multiple Agents (e.g. over a Waiting queue), you have to use a separate Mobility Object per agent and configure the doorcall-trigger on each agent separately

==== PBX ====
From build 1005 on, the script can also switch the active app page on the ''door operator'' phone when a call from a door comes in. This feature requires additional configuration on the PBX.

* create a PBX ''Voicemail'' object (you could set ''Long name'' and ''Name'' to <code>doorcall-trigger</code> for example)
* in the 'Voicemail'' tab, tick the ''Trace'' check-mark
* furthermore, set the ''Script URL'' to something like <code>http://my.door.tld/path-on-web-server/switchops.xml</code>
* open the <code>switchops.xml</code> script itself and fix the url found in the ''string'' argument of the <code>lib-strcat</code> tag near line 23 so that it points to your installed <code>DoorControl.php</code>, e.g.
<code xml><lib-strcat out-string="$url" string="http://1.2.3.4/doorcontrol/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: into
<code xml><lib-strcat out-string="$url" string="http://my.door.tld/path-on-web-server/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: note that anything including and behind <code>/DoorControl.php?</code> must stay unchanged!
* add a ''Fork''ing for the PBX user running the ''door operator'' phone towards the newly created ''Voicemail'' object
: it is ok for the new ''Voicemail'' object to have no ''Number'' property, so you can target the ''Fork''ing to its ''Name''

== Debugging ==
You can debug the retrieval of the image files using a normal brwoser. If you enter the URL to the script in to the address bar of your browser
E. g. <code>http://my.door.tld/path-on-web-server/DoorControl.php</code>, the browser will retrieve the current image. If you add a <code>?debug=1</code> argument, as in
<code>http://my.door.tld/path-on-web-server/DoorControl.php?debug=1</code>, you will see various debug messages instead of the picture.

Debugging the ''switch to video app'' function is a bit more tricky. You proceed as follows:

* clear all trace flags on the PBX where the ''voicemail'' PBX object is installed
* tick the ''Trace'' flag in the ''Voicemail'' tab of this ''Voicemail'' PBX object
* check if the forking is configured correctly
* look at the PBX ''Calls'' screen (or at the PBX calls logging)
* from a door, call the ''door operator''
* the call should trigger a call to the ''Voicemail'' object while the ''door operator''s phone is ringing
* obtain the PBX trace
: it should look something like

: The ''Voicemail'' PBX object gets call

1:1224:494:0 - vm(T):new vm=doorcall-trigger
1:1224:494:1 - script='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml'

: it determines the name of the ''door operator'' and constructs proper arguments for the switchapp call

1:1231:137:2 - iprt.30.0(DBG):call diverting name:
1:1231:137:3 - iprt.30.0(DBG):doorOp
1:1231:137:4 - iprt.30.0(DBG):http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/DoorControl.php?switchapp=1&h323=doorOp
...
1:1231:664:0 - iprt.30.1(T):running file='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml' ver=''

: finally it receives confirmation from the script that some calls have been switched

1:1231:664:1 - iprt.30.1(DBG):switchops.xml: switched 1 call(s) for door 'DoorOp'

=== Error: Allocation limit exceded ===
The filesize is too big for the Phone and will be rejected. Reduce the filesize via URI if your camera support this. (eg. image.jpg?size=640x480) 
If your camera does not support the resize process, you can use the <code>proxy-resize</code> method described above.

=== Error: bad state XML ===
Remove ''state.xml'' from doorcontrol folder, after that you get a correct error message if you reload the Doorcontrol.php in Webbrowser

==Known Problems==
=== Wrong Caller Name ===
* Forking to a VM Object without mobility object (license required) will display the name of the forking target in the caller display and his callist. (To prevent this behavior, use a mobility object for the forking to <code>doorcall-trigger</code>)

=== 3rd party SOAP Application show multiple calls ===
Some SOAP applications show a permanent call to the ''doorcall-trigger'', even though the agent on the desk phone has already picked up. 
To turn this off, the solution must be adjusted as follows:

You have to edit the ''switchops.xml'' and add a ''<pbx-disc />'' at the end of the function ''Main''
<code xml>
<voicemail xmlns="http://www.innovaphone.com/xsd/vm.xsd">
<function define="Main">
...
<exec url="$url"/>
<pbx-disc />
</function>
</voicemail>
</code>

Additional you have to update the [[Reference10:PBX/Objects/Edit_Forks|Forking configuration]] of the agent, use a Mobility or UC License for the Agent and create (or use an existing) Mobility Object in your PBX. 
Configure the ''Object'' and ''Min-Alert''=1 in the forking of the agent.

==Related Articles==
[[Howto:Door Phone with Video in V10 and later]]



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

Howto:Working with multiple Door Cameras

2020-01-16T13:12:29Z

She: /* On a Linux Application Platform */

==Applies To==
This information applies to

* V10 and innovaphone PBX platform
* innovaphone phones supporting video
* web server running PHP 5

some innovaphone phones support display of a door phone camera picture (see [[Howto:Door Phone with Video in V10 and later]]). However, only one camera is supported. This article describes a solution for use of multiple door cameras.



==More Information==
=== Overview ===
When multiple door cameras are used, the standard mechanism described in [[Howto:Door Phone with Video in V10 and later]] is not sufficient, as the URL used in the phone is static and will always show the same door camera. Instead, the image should switch from one camera to the next continuously. Also, when the operator is called by the door phone, the picture from the calling door should be shown always and the phone UI should switch to the ''Video'' app. This can be achieved using a this SOAP-based utility.

=== Prerequisites ===
This SOAP script requires a web server running PHP5. A [[Reference10:Concept_Linux_Application_Platform | Linux Application Platform ]] is fine, but any other PHP platform should do too.

For the ''switch to video app'' feature, you need at least script version 1005 and telephone firmware which includes fix ''17611 - Phones: Remote Control Facility "switch2App"'' (that is, v12r2 - beta 1 (125048) or later).

===Download ===
*[http://download.innovaphone.com/ice/wiki-src#doorcontrol http://download.innovaphone.com/ice/wiki-src#doorcontrol ] - download the complete file package of scripts and files described in this article.

=== Installation ===
Unpack the downloaded file (see [[#Download]]). Copy the content of the <code>Solution/sources</code> directory (including the sub directories) to your web server.

==== On a Linux Application Platform ====
To install the utility on a [[ Reference10:Concept_Linux_Application_Platform| Linux Application Platform ]], you may proceed as follows
* open the LAP's file system using a SFTP client such as e.g. WinSCP (if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]]). Note that you must use SFTP rather than WebDAV, as WebDAV will not give access to the executable web server files
** create the new directory called <code>doorcontrol</code> underneath the <code>/var/www/innovaphone</code> directory.
** copy the files <code>doors.xml</code>, <code>switchops.xml</code> and <code>DoorControl.php</code> to the new directory
** create a subdirectoy <code>/doorcontrol/classes</code>
** change to this directory
** copy the file <code>innopbx.class.php</code> to the new directory
* log in to the LAP's admin UI (if you have not yet changed it, the default credentials will be <code>admin/linux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** go to ''Administration/Web Server/Change web server properties and public access to the web/webdav''
** add <code>doorcontrol</code> to ''Public Web Paths''
* log in the LAP's root shell (using e.g. putty, if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** <code>cd</code> to <code>/var/www/innovaphone</code>
** change owner of <code>doorcontrol</code> and all its sub -directories to <code>www-data</code> (e.g. <code>chown -R www-data doorcontrol</code>)

After you have finished the configuration open your web browser and go to <code>http://your-web-server-name-or-ip/path-you-installed-the-toolto/DoorControl.php?debug</code>. You should see something like
''number'' seconds since last switch ...
switching to next ''name-of-door''
...

===Configuration===
Configuration needs to be done in the <code>doors.xml</code> file that comes with the <code>DoorControl.php</code> script and on the phone that is used to monitor the door video(s).

When the ''switch to video app'' function is used (see [[#PBX | below]]), additional configuration on the PBX is required.
==== doors.xml ====
The utility comes with a working sample configuration (in <code>doors.xml</code>). This file must reside in the same directory you installed the PHP script (<code>DoorControl.php</code>) too. The sample file looks like this:
<code xml>
<?xml version="1.0" encoding="UTF-8"?>
<doors
pbx="1.2.3.4"
pbxhttp="demo"
pbxpw="demo"
pbxuser="_TAPI_"
interval="5"
switch="false"
>
<door name="door" url="http://wiki.innovaphone.com/images/innoWiki.png"/>
<door name="behnke" url="https://www.innovaphone.com/content/images/innovaphone-slider-uc.png" proxy="true" content-type="image/png"/>
</doors>
</code>
===== doors =====
The root tag <code>doors</code> has a few attributes which define the PBX access (used to determine if a phone is being called by a door phone):
; pbx : the IP address of the PBX
; pbxhttp : the HTTP user to be used to access the SOAP service on the PBX (usually the ''Name''' of a PBX user object or the admin user)
; pbxpw : the password of the HTTP user
; pbxuser : the ''Long Name'' of a user object that is used to access the SOAP service on the PBX

Also, the interval between switching the available door cams must be defined
; interval : the number of seconds the utility will wait before switchign to the next camera

Finally, you can optionally have the phone switch to the ''video app'' automatically:
; switch : <code>true</code> or <code>false</code>. If set to ''true'', the script will notify the phone when it detects a call from a door, so that the phone switches to the video app. This requires fix [[Support:DVL-Roadmap_Firmware_12r2#17611_-_Phones:_Remote_Control_Facility_.22switch2App.22 | Remote Control Facility "switch2App"]] and therefore firmware ''v12r2 beta 1'' or later. Also it requires at least script version 1004.
====== door ======
Each sub-tag <code>door</code> defines an available door camera.
; url
: the URL to retrieve a single picture from this camera. You must use the single-picture URL here (usually ending in <code>.jpg</code>), not the picture stream (<code>.mjpg</code>). Otherwise, the phone will never switch to the next camera.
; name
: the ''Name'' of the PBX user object the door phone is registered with

'''Proxy Access to Door Camera '''

In normal operation, this script will not deliver the door cam image itself to the caller. Instead, it will tell the calling client the URL where the current door cam image can be retrieved (using a <code>HTTP/1.1 307 Temporary Redirect</code> response with a <code>Location: ...</code> header). The phone will then refer to this URL and retrieve the image itself.

However, in rare situations this may not work (e.g. [http://www.axis.com/global/en AXIS] cameras are known to be incompatible with the HTTP client built-in to the innovaphone phone when the image requires authentication). In this case, the script behaviour can be modified so that the image actually is retrieved by the script and then returned to the caller.

; proxy
: if this is set to <code>true</code>, the image will be retrieved by the script and returned to the caller directly
; user
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication user-name here
; pw
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication password here
; content-type
: you can optionally specify the value used for the <code>Content-Type:</code> HTTP header (normally not necessary)
; proxy-skip-ssl-verify [since build 1009]
: if this is set to <code>true</code>, SSL-Certificate of the given <code>url</code> will not be verified
; proxy-resize [since build 1009]
: if this is set to <code>true</code>, the big pictures will be resized for IP-Phone. The size is depending on the phone model and must not be configured. You can use this method if your camera is not able to provide small images. Please note that this increase the ressource usage on your webserver and should only used if your camera does not support the resize process itself.

==== Phone ====
The ''door operator''s phone (that is, the phone that shall monitor the video image of the door(s)) needs some configuration as follows.

The ''Background Image'' property in [[Reference11r1:Phone/Preferences | Phone/Preferences ]] must be set to the DoorControl.php script on your web server. It supports 2 arguments
; id : e.g. <code>id=operator</code>, the ''Long Name'' of the PBX user object the retrieving phone is registered with. The script will use this name to query the PBX if the phone is currently being called by a door phone. (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; hw : e.g. <code>hw=0090333e0c57</code>, the ''Hardware Id'' used to register the operator's phone (optional, may be omitted if the operator does not have multiple registrations or mobility). Requires at least script version 1004 (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; debug : if this is set, the script will not deliver the requested picture but will spit out some debug information

Please note that you must also add the query arguments not processed by the <code>DoorPhone.php</code> script but by the phone itself, namely
; refresh : e.g. <code>refresh=1</code>, see ''Background Image'' in [[Reference11r1:Phone/Preferences]] and [[Howto:Door Phone with Video in V10 and later]]

So you may end up with something like <code>http://my.door.tld/path-on-web-server/DoorControl.php?refresh=1&id=operator&hw=009033000000</code>.

===== Picture Sources with Password Protection =====
If your camera is password protected, you must configure its URL and password in ''Services/HTTP/Client/Authenticated URLs''.

===== Multiple Agents =====
If you want to serve this function to multiple Agents (e.g. over a Waiting queue), you have to use a separate Mobility Object per agent and configure the doorcall-trigger on each agent separately

==== PBX ====
From build 1005 on, the script can also switch the active app page on the ''door operator'' phone when a call from a door comes in. This feature requires additional configuration on the PBX.

* create a PBX ''Voicemail'' object (you could set ''Long name'' and ''Name'' to <code>doorcall-trigger</code> for example)
* in the 'Voicemail'' tab, tick the ''Trace'' check-mark
* furthermore, set the ''Script URL'' to something like <code>http://my.door.tld/path-on-web-server/switchops.xml</code>
* open the <code>switchops.xml</code> script itself and fix the url found in the ''string'' argument of the <code>lib-strcat</code> tag near line 23 so that it points to your installed <code>DoorControl.php</code>, e.g.
<code xml><lib-strcat out-string="$url" string="http://1.2.3.4/doorcontrol/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: into
<code xml><lib-strcat out-string="$url" string="http://my.door.tld/path-on-web-server/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: note that anything including and behind <code>/DoorControl.php?</code> must stay unchanged!
* add a ''Fork''ing for the PBX user running the ''door operator'' phone towards the newly created ''Voicemail'' object
: it is ok for the new ''Voicemail'' object to have no ''Number'' property, so you can target the ''Fork''ing to its ''Name''

== Debugging ==
You can debug the retrieval of the image files using a normal brwoser. If you enter the URL to the script in to the address bar of your browser
E. g. <code>http://my.door.tld/path-on-web-server/DoorControl.php</code>, the browser will retrieve the current image. If you add a <code>?debug=1</code> argument, as in
<code>http://my.door.tld/path-on-web-server/DoorControl.php?debug=1</code>, you will see various debug messages instead of the picture.

Debugging the ''switch to video app'' function is a bit more tricky. You proceed as follows:

* clear all trace flags on the PBX where the ''voicemail'' PBX object is installed
* tick the ''Trace'' flag in the ''Voicemail'' tab of this ''Voicemail'' PBX object
* check if the forking is configured correctly
* look at the PBX ''Calls'' screen (or at the PBX calls logging)
* from a door, call the ''door operator''
* the call should trigger a call to the ''Voicemail'' object while the ''door operator''s phone is ringing
* obtain the PBX trace
: it should look something like

: The ''Voicemail'' PBX object gets call

1:1224:494:0 - vm(T):new vm=doorcall-trigger
1:1224:494:1 - script='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml'

: it determines the name of the ''door operator'' and constructs proper arguments for the switchapp call

1:1231:137:2 - iprt.30.0(DBG):call diverting name:
1:1231:137:3 - iprt.30.0(DBG):doorOp
1:1231:137:4 - iprt.30.0(DBG):http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/DoorControl.php?switchapp=1&h323=doorOp
...
1:1231:664:0 - iprt.30.1(T):running file='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml' ver=''

: finally it receives confirmation from the script that some calls have been switched

1:1231:664:1 - iprt.30.1(DBG):switchops.xml: switched 1 call(s) for door 'DoorOp'

=== Error: Allocation limit exceded ===
The filesize is too big for the Phone and will be rejected. Reduce the filesize via URI if your camera support this. (eg. image.jpg?size=640x480) 
If your camera does not support the resize process, you can use the <code>proxy-resize</code> method described above.

=== Error: bad state XML ===
Remove ''state.xml'' from doorcontrol folder, after that you get a correct error message if you reload the Doorcontrol.php in Webbrowser

==Known Problems==
=== Wrong Caller Name ===
* Forking to a VM Object without mobility object (license required) will display the name of the forking target in the caller display and his callist. (To prevent this behavior, use a mobility object for the forking to <code>doorcall-trigger</code>)

=== 3rd party SOAP Application show multiple calls ===
Some SOAP applications show a permanent call to the ''doorcall-trigger'', even though the agent on the desk phone has already picked up. 
To turn this off, the solution must be adjusted as follows:

You have to edit the ''switchops.xml'' and add a ''<pbx-disc />'' at the end of the function ''Main''
<code xml>
<voicemail xmlns="http://www.innovaphone.com/xsd/vm.xsd">
<function define="Main">
...
<exec url="$url"/>
<pbx-disc />
</function>
</voicemail>
</code>

Additional you have to update the [[Reference10:PBX/Objects/Edit_Forks|Forking configuration]] of the agent, use a Mobility or UC License for the Agent and create (or use an existing) Mobility Object in your PBX. 
Configure the ''Object'' and ''Min-Alert''=1 in the forking of the agent.

==Related Articles==
[[Howto:Door Phone with Video in V10 and later]]



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

Howto:Working with multiple Door Cameras

2020-01-16T13:11:41Z

She: /* On a Linux Application Platform */

==Applies To==
This information applies to

* V10 and innovaphone PBX platform
* innovaphone phones supporting video
* web server running PHP 5

some innovaphone phones support display of a door phone camera picture (see [[Howto:Door Phone with Video in V10 and later]]). However, only one camera is supported. This article describes a solution for use of multiple door cameras.



==More Information==
=== Overview ===
When multiple door cameras are used, the standard mechanism described in [[Howto:Door Phone with Video in V10 and later]] is not sufficient, as the URL used in the phone is static and will always show the same door camera. Instead, the image should switch from one camera to the next continuously. Also, when the operator is called by the door phone, the picture from the calling door should be shown always and the phone UI should switch to the ''Video'' app. This can be achieved using a this SOAP-based utility.

=== Prerequisites ===
This SOAP script requires a web server running PHP5. A [[Reference10:Concept_Linux_Application_Platform | Linux Application Platform ]] is fine, but any other PHP platform should do too.

For the ''switch to video app'' feature, you need at least script version 1005 and telephone firmware which includes fix ''17611 - Phones: Remote Control Facility "switch2App"'' (that is, v12r2 - beta 1 (125048) or later).

===Download ===
*[http://download.innovaphone.com/ice/wiki-src#doorcontrol http://download.innovaphone.com/ice/wiki-src#doorcontrol ] - download the complete file package of scripts and files described in this article.

=== Installation ===
Unpack the downloaded file (see [[#Download]]). Copy the content of the <code>Solution/sources</code> directory (including the sub directories) to your web server.

==== On a Linux Application Platform ====
To install the utility on a [[ Reference10:Concept_Linux_Application_Platform| Linux Application Platform ]], you may proceed as follows
* open the LAP's file system using a SFTP client such as e.g. WinSCP (if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]]). Note that you must use SFTP rather than WebDAV, as WebDAV will not give access to the executable web server files
** create the new directory called <code>doorcontrol</code> underneath the <code>/var/www/innovaphone</code> directory.
** copy the files <code>doors.xml</code>, <code>switchops.xml</code> and <code>DoorControl.php</code> to the new directory
** create a subdirectoy <code>/doorcontrol/classes</code>
** change to this directory
** copy the file <code>innopbx.class.php</code> to the new directory
* log in to the LAP's admin UI (if you have not yet changed it, the default credentials will be <code>admin/linux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** go to ''Administration/Web Server/Change web server properties and public access to the web/webdav''
** add <code>doorcontrol</code> to ''Public Web Paths''
* log in the LAP's root shell (using e.g. putty, if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** <code>cd</code> to <code>/var/www/innovaphone</code>
** change owner of <code>doorcontrol</code> and all its sub -directories to <code>www-data</code> (e.g. <code>chown -R www-data doorcontrol</code>)

===Configuration===
Configuration needs to be done in the <code>doors.xml</code> file that comes with the <code>DoorControl.php</code> script and on the phone that is used to monitor the door video(s).

When the ''switch to video app'' function is used (see [[#PBX | below]]), additional configuration on the PBX is required.
==== doors.xml ====
The utility comes with a working sample configuration (in <code>doors.xml</code>). This file must reside in the same directory you installed the PHP script (<code>DoorControl.php</code>) too. The sample file looks like this:
<code xml>
<?xml version="1.0" encoding="UTF-8"?>
<doors
pbx="1.2.3.4"
pbxhttp="demo"
pbxpw="demo"
pbxuser="_TAPI_"
interval="5"
switch="false"
>
<door name="door" url="http://wiki.innovaphone.com/images/innoWiki.png"/>
<door name="behnke" url="https://www.innovaphone.com/content/images/innovaphone-slider-uc.png" proxy="true" content-type="image/png"/>
</doors>
</code>
===== doors =====
The root tag <code>doors</code> has a few attributes which define the PBX access (used to determine if a phone is being called by a door phone):
; pbx : the IP address of the PBX
; pbxhttp : the HTTP user to be used to access the SOAP service on the PBX (usually the ''Name''' of a PBX user object or the admin user)
; pbxpw : the password of the HTTP user
; pbxuser : the ''Long Name'' of a user object that is used to access the SOAP service on the PBX

Also, the interval between switching the available door cams must be defined
; interval : the number of seconds the utility will wait before switchign to the next camera

Finally, you can optionally have the phone switch to the ''video app'' automatically:
; switch : <code>true</code> or <code>false</code>. If set to ''true'', the script will notify the phone when it detects a call from a door, so that the phone switches to the video app. This requires fix [[Support:DVL-Roadmap_Firmware_12r2#17611_-_Phones:_Remote_Control_Facility_.22switch2App.22 | Remote Control Facility "switch2App"]] and therefore firmware ''v12r2 beta 1'' or later. Also it requires at least script version 1004.
====== door ======
Each sub-tag <code>door</code> defines an available door camera.
; url
: the URL to retrieve a single picture from this camera. You must use the single-picture URL here (usually ending in <code>.jpg</code>), not the picture stream (<code>.mjpg</code>). Otherwise, the phone will never switch to the next camera.
; name
: the ''Name'' of the PBX user object the door phone is registered with

'''Proxy Access to Door Camera '''

In normal operation, this script will not deliver the door cam image itself to the caller. Instead, it will tell the calling client the URL where the current door cam image can be retrieved (using a <code>HTTP/1.1 307 Temporary Redirect</code> response with a <code>Location: ...</code> header). The phone will then refer to this URL and retrieve the image itself.

However, in rare situations this may not work (e.g. [http://www.axis.com/global/en AXIS] cameras are known to be incompatible with the HTTP client built-in to the innovaphone phone when the image requires authentication). In this case, the script behaviour can be modified so that the image actually is retrieved by the script and then returned to the caller.

; proxy
: if this is set to <code>true</code>, the image will be retrieved by the script and returned to the caller directly
; user
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication user-name here
; pw
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication password here
; content-type
: you can optionally specify the value used for the <code>Content-Type:</code> HTTP header (normally not necessary)
; proxy-skip-ssl-verify [since build 1009]
: if this is set to <code>true</code>, SSL-Certificate of the given <code>url</code> will not be verified
; proxy-resize [since build 1009]
: if this is set to <code>true</code>, the big pictures will be resized for IP-Phone. The size is depending on the phone model and must not be configured. You can use this method if your camera is not able to provide small images. Please note that this increase the ressource usage on your webserver and should only used if your camera does not support the resize process itself.

==== Phone ====
The ''door operator''s phone (that is, the phone that shall monitor the video image of the door(s)) needs some configuration as follows.

The ''Background Image'' property in [[Reference11r1:Phone/Preferences | Phone/Preferences ]] must be set to the DoorControl.php script on your web server. It supports 2 arguments
; id : e.g. <code>id=operator</code>, the ''Long Name'' of the PBX user object the retrieving phone is registered with. The script will use this name to query the PBX if the phone is currently being called by a door phone. (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; hw : e.g. <code>hw=0090333e0c57</code>, the ''Hardware Id'' used to register the operator's phone (optional, may be omitted if the operator does not have multiple registrations or mobility). Requires at least script version 1004 (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; debug : if this is set, the script will not deliver the requested picture but will spit out some debug information

Please note that you must also add the query arguments not processed by the <code>DoorPhone.php</code> script but by the phone itself, namely
; refresh : e.g. <code>refresh=1</code>, see ''Background Image'' in [[Reference11r1:Phone/Preferences]] and [[Howto:Door Phone with Video in V10 and later]]

So you may end up with something like <code>http://my.door.tld/path-on-web-server/DoorControl.php?refresh=1&id=operator&hw=009033000000</code>.

===== Picture Sources with Password Protection =====
If your camera is password protected, you must configure its URL and password in ''Services/HTTP/Client/Authenticated URLs''.

===== Multiple Agents =====
If you want to serve this function to multiple Agents (e.g. over a Waiting queue), you have to use a separate Mobility Object per agent and configure the doorcall-trigger on each agent separately

==== PBX ====
From build 1005 on, the script can also switch the active app page on the ''door operator'' phone when a call from a door comes in. This feature requires additional configuration on the PBX.

* create a PBX ''Voicemail'' object (you could set ''Long name'' and ''Name'' to <code>doorcall-trigger</code> for example)
* in the 'Voicemail'' tab, tick the ''Trace'' check-mark
* furthermore, set the ''Script URL'' to something like <code>http://my.door.tld/path-on-web-server/switchops.xml</code>
* open the <code>switchops.xml</code> script itself and fix the url found in the ''string'' argument of the <code>lib-strcat</code> tag near line 23 so that it points to your installed <code>DoorControl.php</code>, e.g.
<code xml><lib-strcat out-string="$url" string="http://1.2.3.4/doorcontrol/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: into
<code xml><lib-strcat out-string="$url" string="http://my.door.tld/path-on-web-server/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: note that anything including and behind <code>/DoorControl.php?</code> must stay unchanged!
* add a ''Fork''ing for the PBX user running the ''door operator'' phone towards the newly created ''Voicemail'' object
: it is ok for the new ''Voicemail'' object to have no ''Number'' property, so you can target the ''Fork''ing to its ''Name''

== Debugging ==
You can debug the retrieval of the image files using a normal brwoser. If you enter the URL to the script in to the address bar of your browser
E. g. <code>http://my.door.tld/path-on-web-server/DoorControl.php</code>, the browser will retrieve the current image. If you add a <code>?debug=1</code> argument, as in
<code>http://my.door.tld/path-on-web-server/DoorControl.php?debug=1</code>, you will see various debug messages instead of the picture.

Debugging the ''switch to video app'' function is a bit more tricky. You proceed as follows:

* clear all trace flags on the PBX where the ''voicemail'' PBX object is installed
* tick the ''Trace'' flag in the ''Voicemail'' tab of this ''Voicemail'' PBX object
* check if the forking is configured correctly
* look at the PBX ''Calls'' screen (or at the PBX calls logging)
* from a door, call the ''door operator''
* the call should trigger a call to the ''Voicemail'' object while the ''door operator''s phone is ringing
* obtain the PBX trace
: it should look something like

: The ''Voicemail'' PBX object gets call

1:1224:494:0 - vm(T):new vm=doorcall-trigger
1:1224:494:1 - script='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml'

: it determines the name of the ''door operator'' and constructs proper arguments for the switchapp call

1:1231:137:2 - iprt.30.0(DBG):call diverting name:
1:1231:137:3 - iprt.30.0(DBG):doorOp
1:1231:137:4 - iprt.30.0(DBG):http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/DoorControl.php?switchapp=1&h323=doorOp
...
1:1231:664:0 - iprt.30.1(T):running file='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml' ver=''

: finally it receives confirmation from the script that some calls have been switched

1:1231:664:1 - iprt.30.1(DBG):switchops.xml: switched 1 call(s) for door 'DoorOp'

=== Error: Allocation limit exceded ===
The filesize is too big for the Phone and will be rejected. Reduce the filesize via URI if your camera support this. (eg. image.jpg?size=640x480) 
If your camera does not support the resize process, you can use the <code>proxy-resize</code> method described above.

=== Error: bad state XML ===
Remove ''state.xml'' from doorcontrol folder, after that you get a correct error message if you reload the Doorcontrol.php in Webbrowser

==Known Problems==
=== Wrong Caller Name ===
* Forking to a VM Object without mobility object (license required) will display the name of the forking target in the caller display and his callist. (To prevent this behavior, use a mobility object for the forking to <code>doorcall-trigger</code>)

=== 3rd party SOAP Application show multiple calls ===
Some SOAP applications show a permanent call to the ''doorcall-trigger'', even though the agent on the desk phone has already picked up. 
To turn this off, the solution must be adjusted as follows:

You have to edit the ''switchops.xml'' and add a ''<pbx-disc />'' at the end of the function ''Main''
<code xml>
<voicemail xmlns="http://www.innovaphone.com/xsd/vm.xsd">
<function define="Main">
...
<exec url="$url"/>
<pbx-disc />
</function>
</voicemail>
</code>

Additional you have to update the [[Reference10:PBX/Objects/Edit_Forks|Forking configuration]] of the agent, use a Mobility or UC License for the Agent and create (or use an existing) Mobility Object in your PBX. 
Configure the ''Object'' and ''Min-Alert''=1 in the forking of the agent.

==Related Articles==
[[Howto:Door Phone with Video in V10 and later]]



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

Howto:Working with multiple Door Cameras

2020-01-16T13:11:13Z

She: /* Installation */

==Applies To==
This information applies to

* V10 and innovaphone PBX platform
* innovaphone phones supporting video
* web server running PHP 5

some innovaphone phones support display of a door phone camera picture (see [[Howto:Door Phone with Video in V10 and later]]). However, only one camera is supported. This article describes a solution for use of multiple door cameras.



==More Information==
=== Overview ===
When multiple door cameras are used, the standard mechanism described in [[Howto:Door Phone with Video in V10 and later]] is not sufficient, as the URL used in the phone is static and will always show the same door camera. Instead, the image should switch from one camera to the next continuously. Also, when the operator is called by the door phone, the picture from the calling door should be shown always and the phone UI should switch to the ''Video'' app. This can be achieved using a this SOAP-based utility.

=== Prerequisites ===
This SOAP script requires a web server running PHP5. A [[Reference10:Concept_Linux_Application_Platform | Linux Application Platform ]] is fine, but any other PHP platform should do too.

For the ''switch to video app'' feature, you need at least script version 1005 and telephone firmware which includes fix ''17611 - Phones: Remote Control Facility "switch2App"'' (that is, v12r2 - beta 1 (125048) or later).

===Download ===
*[http://download.innovaphone.com/ice/wiki-src#doorcontrol http://download.innovaphone.com/ice/wiki-src#doorcontrol ] - download the complete file package of scripts and files described in this article.

=== Installation ===
Unpack the downloaded file (see [[#Download]]). Copy the content of the <code>Solution/sources</code> directory (including the sub directories) to your web server.

==== On a Linux Application Platform ====
To install the utility on a [[ Reference10:Concept_Linux_Application_Platform| Linux Application Platform ]], you may proceed as follows
* open the LAP's file system using a SFTP client such as e.g. WinSCP (if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]]). Note that you must use SFTP rather than WebDAV, as WebDAV will not give access to the executable web server files
** create the new directory called <code>doorcontrol</code> underneath the <code>/var/www/innovaphone</code> directory.
** copy the files <code>doors.xml</code>, <code>switchops.xml</code> and <code>DoorControl.php</code> to the new directory
** create a subdirectoy <code>/doorcontrol/classes</code>
** change to this directory
** copy the file <code>innopbx.class.php</code> to the new directory
* log in to the LAP's admin UI (if you have not yet changed it, the default credentials will be <code>admin/linux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** go to ''Administration/Web Server/Change web server properties and public access to the web/webdav''
** add <code>doorcontrol</code> to ''Public Web Paths''
* log in the LAP's root shell (using e.g. putty, if you have not yet changed it, the default credentials will be <code>root/iplinux</code>, see [[Reference10:Concept_Linux_Application_Platform#Default_Credentials | Concept Linux Application Platform]])
** <code>cd</code> to <code>/var/www/innovaphone</code>
** change owner of <code>doorcontrol</code> and all its sub -directories to <code>www-data</code> (e.g. <code>chown -R www-data doorcontrol</code>)

If you now type <code>http://</code>''lap-ip-addr''<code>/doorcontrol/DoorControl.php?debug</code>, you should see the message mentioned above.

===Configuration===
Configuration needs to be done in the <code>doors.xml</code> file that comes with the <code>DoorControl.php</code> script and on the phone that is used to monitor the door video(s).

When the ''switch to video app'' function is used (see [[#PBX | below]]), additional configuration on the PBX is required.
==== doors.xml ====
The utility comes with a working sample configuration (in <code>doors.xml</code>). This file must reside in the same directory you installed the PHP script (<code>DoorControl.php</code>) too. The sample file looks like this:
<code xml>
<?xml version="1.0" encoding="UTF-8"?>
<doors
pbx="1.2.3.4"
pbxhttp="demo"
pbxpw="demo"
pbxuser="_TAPI_"
interval="5"
switch="false"
>
<door name="door" url="http://wiki.innovaphone.com/images/innoWiki.png"/>
<door name="behnke" url="https://www.innovaphone.com/content/images/innovaphone-slider-uc.png" proxy="true" content-type="image/png"/>
</doors>
</code>
===== doors =====
The root tag <code>doors</code> has a few attributes which define the PBX access (used to determine if a phone is being called by a door phone):
; pbx : the IP address of the PBX
; pbxhttp : the HTTP user to be used to access the SOAP service on the PBX (usually the ''Name''' of a PBX user object or the admin user)
; pbxpw : the password of the HTTP user
; pbxuser : the ''Long Name'' of a user object that is used to access the SOAP service on the PBX

Also, the interval between switching the available door cams must be defined
; interval : the number of seconds the utility will wait before switchign to the next camera

Finally, you can optionally have the phone switch to the ''video app'' automatically:
; switch : <code>true</code> or <code>false</code>. If set to ''true'', the script will notify the phone when it detects a call from a door, so that the phone switches to the video app. This requires fix [[Support:DVL-Roadmap_Firmware_12r2#17611_-_Phones:_Remote_Control_Facility_.22switch2App.22 | Remote Control Facility "switch2App"]] and therefore firmware ''v12r2 beta 1'' or later. Also it requires at least script version 1004.
====== door ======
Each sub-tag <code>door</code> defines an available door camera.
; url
: the URL to retrieve a single picture from this camera. You must use the single-picture URL here (usually ending in <code>.jpg</code>), not the picture stream (<code>.mjpg</code>). Otherwise, the phone will never switch to the next camera.
; name
: the ''Name'' of the PBX user object the door phone is registered with

'''Proxy Access to Door Camera '''

In normal operation, this script will not deliver the door cam image itself to the caller. Instead, it will tell the calling client the URL where the current door cam image can be retrieved (using a <code>HTTP/1.1 307 Temporary Redirect</code> response with a <code>Location: ...</code> header). The phone will then refer to this URL and retrieve the image itself.

However, in rare situations this may not work (e.g. [http://www.axis.com/global/en AXIS] cameras are known to be incompatible with the HTTP client built-in to the innovaphone phone when the image requires authentication). In this case, the script behaviour can be modified so that the image actually is retrieved by the script and then returned to the caller.

; proxy
: if this is set to <code>true</code>, the image will be retrieved by the script and returned to the caller directly
; user
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication user-name here
; pw
: if authentication is required by the camera and ''proxy'' mode is used, you can provide the authentication password here
; content-type
: you can optionally specify the value used for the <code>Content-Type:</code> HTTP header (normally not necessary)
; proxy-skip-ssl-verify [since build 1009]
: if this is set to <code>true</code>, SSL-Certificate of the given <code>url</code> will not be verified
; proxy-resize [since build 1009]
: if this is set to <code>true</code>, the big pictures will be resized for IP-Phone. The size is depending on the phone model and must not be configured. You can use this method if your camera is not able to provide small images. Please note that this increase the ressource usage on your webserver and should only used if your camera does not support the resize process itself.

==== Phone ====
The ''door operator''s phone (that is, the phone that shall monitor the video image of the door(s)) needs some configuration as follows.

The ''Background Image'' property in [[Reference11r1:Phone/Preferences | Phone/Preferences ]] must be set to the DoorControl.php script on your web server. It supports 2 arguments
; id : e.g. <code>id=operator</code>, the ''Long Name'' of the PBX user object the retrieving phone is registered with. The script will use this name to query the PBX if the phone is currently being called by a door phone. (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; hw : e.g. <code>hw=0090333e0c57</code>, the ''Hardware Id'' used to register the operator's phone (optional, may be omitted if the operator does not have multiple registrations or mobility). Requires at least script version 1004 (Special chars have to be [https://en.wikipedia.org/wiki/Percent-encoding#Character_data encoded])
; debug : if this is set, the script will not deliver the requested picture but will spit out some debug information

Please note that you must also add the query arguments not processed by the <code>DoorPhone.php</code> script but by the phone itself, namely
; refresh : e.g. <code>refresh=1</code>, see ''Background Image'' in [[Reference11r1:Phone/Preferences]] and [[Howto:Door Phone with Video in V10 and later]]

So you may end up with something like <code>http://my.door.tld/path-on-web-server/DoorControl.php?refresh=1&id=operator&hw=009033000000</code>.

===== Picture Sources with Password Protection =====
If your camera is password protected, you must configure its URL and password in ''Services/HTTP/Client/Authenticated URLs''.

===== Multiple Agents =====
If you want to serve this function to multiple Agents (e.g. over a Waiting queue), you have to use a separate Mobility Object per agent and configure the doorcall-trigger on each agent separately

==== PBX ====
From build 1005 on, the script can also switch the active app page on the ''door operator'' phone when a call from a door comes in. This feature requires additional configuration on the PBX.

* create a PBX ''Voicemail'' object (you could set ''Long name'' and ''Name'' to <code>doorcall-trigger</code> for example)
* in the 'Voicemail'' tab, tick the ''Trace'' check-mark
* furthermore, set the ''Script URL'' to something like <code>http://my.door.tld/path-on-web-server/switchops.xml</code>
* open the <code>switchops.xml</code> script itself and fix the url found in the ''string'' argument of the <code>lib-strcat</code> tag near line 23 so that it points to your installed <code>DoorControl.php</code>, e.g.
<code xml><lib-strcat out-string="$url" string="http://1.2.3.4/doorcontrol/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: into
<code xml><lib-strcat out-string="$url" string="http://my.door.tld/path-on-web-server/DoorControl.php?switchapp=1&h323=" string2="$leg2-name-enc"/></code>
: note that anything including and behind <code>/DoorControl.php?</code> must stay unchanged!
* add a ''Fork''ing for the PBX user running the ''door operator'' phone towards the newly created ''Voicemail'' object
: it is ok for the new ''Voicemail'' object to have no ''Number'' property, so you can target the ''Fork''ing to its ''Name''

== Debugging ==
You can debug the retrieval of the image files using a normal brwoser. If you enter the URL to the script in to the address bar of your browser
E. g. <code>http://my.door.tld/path-on-web-server/DoorControl.php</code>, the browser will retrieve the current image. If you add a <code>?debug=1</code> argument, as in
<code>http://my.door.tld/path-on-web-server/DoorControl.php?debug=1</code>, you will see various debug messages instead of the picture.

Debugging the ''switch to video app'' function is a bit more tricky. You proceed as follows:

* clear all trace flags on the PBX where the ''voicemail'' PBX object is installed
* tick the ''Trace'' flag in the ''Voicemail'' tab of this ''Voicemail'' PBX object
* check if the forking is configured correctly
* look at the PBX ''Calls'' screen (or at the PBX calls logging)
* from a door, call the ''door operator''
* the call should trigger a call to the ''Voicemail'' object while the ''door operator''s phone is ringing
* obtain the PBX trace
: it should look something like

: The ''Voicemail'' PBX object gets call

1:1224:494:0 - vm(T):new vm=doorcall-trigger
1:1224:494:1 - script='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml'

: it determines the name of the ''door operator'' and constructs proper arguments for the switchapp call

1:1231:137:2 - iprt.30.0(DBG):call diverting name:
1:1231:137:3 - iprt.30.0(DBG):doorOp
1:1231:137:4 - iprt.30.0(DBG):http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/DoorControl.php?switchapp=1&h323=doorOp
...
1:1231:664:0 - iprt.30.1(T):running file='http://172.16.100.202:8080/wiki-src/sample/DoorControl/sample/sources/switchops.xml' ver=''

: finally it receives confirmation from the script that some calls have been switched

1:1231:664:1 - iprt.30.1(DBG):switchops.xml: switched 1 call(s) for door 'DoorOp'

=== Error: Allocation limit exceded ===
The filesize is too big for the Phone and will be rejected. Reduce the filesize via URI if your camera support this. (eg. image.jpg?size=640x480) 
If your camera does not support the resize process, you can use the <code>proxy-resize</code> method described above.

=== Error: bad state XML ===
Remove ''state.xml'' from doorcontrol folder, after that you get a correct error message if you reload the Doorcontrol.php in Webbrowser

==Known Problems==
=== Wrong Caller Name ===
* Forking to a VM Object without mobility object (license required) will display the name of the forking target in the caller display and his callist. (To prevent this behavior, use a mobility object for the forking to <code>doorcall-trigger</code>)

=== 3rd party SOAP Application show multiple calls ===
Some SOAP applications show a permanent call to the ''doorcall-trigger'', even though the agent on the desk phone has already picked up. 
To turn this off, the solution must be adjusted as follows:

You have to edit the ''switchops.xml'' and add a ''<pbx-disc />'' at the end of the function ''Main''
<code xml>
<voicemail xmlns="http://www.innovaphone.com/xsd/vm.xsd">
<function define="Main">
...
<exec url="$url"/>
<pbx-disc />
</function>
</voicemail>
</code>

Additional you have to update the [[Reference10:PBX/Objects/Edit_Forks|Forking configuration]] of the agent, use a Mobility or UC License for the Agent and create (or use an existing) Mobility Object in your PBX. 
Configure the ''Object'' and ''Min-Alert''=1 in the forking of the agent.

==Related Articles==
[[Howto:Door Phone with Video in V10 and later]]



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

IP1202 Ficha técnica ES

2019-12-20T11:09:35Z

She:

{{Template:Disclaimer ES}}
==Foto==
[[Image:IP1202.png]]
==Ficha técnica==
===innovaphone IP1202/4, innovaphone IP1202, innovaphone IP1202e===
Gateway IP DECT y estación base para la PBX innovaphone

* IP1202/4: estación base multicelda de 4 canales
* IP1202/4s: estación base de 4 canales de celda única sin capacidad de expansión para otra estación base
* IP1202: estación base multicelda de 8 canales
* IP1202e: estación base multicelular de 8 canales incl. antena externa conectividad
===Carcasa===
Tamaño: 170 x 174 x 38 mm

Plástico blanco

Peso: 400 g
===Interfaces===
Ethernet: RJ 45, 10/100-BASE-TX (auto negotiation), Power over Ethernet (802.3af, Class 2)

Información válida solo para el IP1202e: 2 conectores MCX para antenas externas

Para más información acerca de las antenas adecuadas, le invitamos a consultar el apartado Servicios/Descargas/Documentos externos de la página web innovaphone.

===DECT===
interfaz radio GAP / CAP

Frecuencias: 1880-1900 MHz

Llamadas simultáneas:
* IP1202/4, IP1202/4s: hasta 4
* IP1202, IP1202e: hasta 8

Se pueden registrar hasta 1000 terminales en cada celda
Capacidad multicelda - excluyendo el modelo IP1202/4s

Roaming

Handover (solo terminales CAP handsets) - excluyendo el modelo IP1202/4s

Sincronización On air

Potencia radio RF con antena interna (e.r.p.): 23 dBm - 28 dBm (EU), 17 dBm - 21,6 dBm (US)

===Hardware===
Power over Ethernet o

Local power supply 21 - 56 V DC, max. 5 W
===Condiciones de funcionamiento===
Temperatura ambiente recomendada: -10 °C hasta +55 °C

Temperatura de almacenamiento: -25 °C hasta +55 °C

Humedad almacenamiento: 15% - 90% (no condensada)

===Administración===
Via navegador web

Protegida por contraseña

Administración y actualización software
===Protocolos VoIP===
H.323 versión 5, incluyendo extensiones propietarias

H.323 a través de UDP, TCP, TLS

SIP Versión 2, conforme a RFC 3261

SIP a través de UDP, TCP, TLS

RTP, SRTP (SDES, DTLS), RTCP, ICE

===Voice Codecs===
G.711 A-law / μ-law, G.723.1 (5.3 kbps), G.729AB, G722, G722.2 (AMR-WB)

VAD, CNG

Dynamic Jitter Buffering

Echo Compensation conforme con G.168

===Red===
STUN, TURN

RSTP, EAP-TLS/EAP-MD5 según IEEE 802.1X

VLAN-ID según IEEE 802.1Q

Soporte DHCP y LLDP/MED

Soporte NTP

===Características especiales===
Indicador LED

Especialmente diseñado para los dispositivos innovaphone IP61, IP63, IP64 e IP65

Una serie de códigos permiten utilizar algunas funcionalidades especiales de la PBX innovaphone, como funcionalidades de grupo, "captura de llamada", "llamada en espera" y "entrada dinámica a un grupo".

Acceso al directorio central de la PBX y a otras bases de datos externas a través de LDAP.

===Cód. Art.===
* IP1202: 50-01202-001
* IP1202/4: 50-01202-002
* IP1202e: 50-01202-003
* IP1202/4s: 50-01202-010

* Dual-Directional-Antenna para IP1202e: 50-01202-004
* Single-Directional-Antenna para IP1202e: 50-01202-005
* Omni-Directional-Antenna para IP1202e: 50-01202-006

==Certificados CE==
===Declaración de conformidad===
{{Template:CE-Decl_Wireless}}
*EN 50385, 2002
*EN 301 406, v2.1.1 (Radio)
*EN 60945 (EMC)
===Número WEEE===
{{Template:WEEE-Number}}
[[Category:Fichas técnicas ES|{{PAGENAME}}]]

IP1202 Ficha técnica ES

2019-12-20T11:07:20Z

She:

{{Template:Disclaimer ES}}
==Foto==
[[Image:IP1202.png]]
==Ficha técnica==
===innovaphone IP1202/4, innovaphone IP1202, innovaphone IP1202e===
Gateway IP DECT y estación base para la PBX innovaphone

* IP1202 / 4: estación base multicelda de 4 canales
* IP1202 / 4s: estación base de 4 canales de celda única sin capacidad de expansión para otra estación base
* IP1202: estación base multicelda de 8 canales
* IP1202e: estación base multicelular de 8 canales incl. antena externa conectividad
===Carcasa===
Tamaño: 170 x 174 x 38 mm

Plástico blanco

Peso: 400 g
===Interfaces===
Ethernet: RJ 45, 10/100-BASE-TX (auto negotiation), Power over Ethernet (802.3af, Class 2)

Información válida solo para el IP1202e: 2 conectores MCX para antenas externas

Para más información acerca de las antenas adecuadas, le invitamos a consultar el apartado Servicios/Descargas/Documentos externos de la página web innovaphone.

===DECT===
interfaz radio GAP / CAP

Frecuencias: 1880-1900 MHz

Llamadas simultáneas:
* IP1202/4, IP1202/4s: hasta 4
* IP1202, IP1202e: hasta 8

Se pueden registrar hasta 1000 terminales en cada celda
Capacidad multicelda - no IP1202/4s

Roaming

Handover (solo terminales CAP handsets) - no IP1202/4s

Sincronización On air

Potencia radio RF con antena interna (e.r.p.): 23 dBm - 28 dBm (EU), 17 dBm - 21,6 dBm (US)

===Hardware===
Power over Ethernet o

Local power supply 21 - 56 V DC, max. 5 W
===Condiciones de funcionamiento===
Temperatura ambiente recomendada: -10 °C hasta +55 °C

Temperatura de almacenamiento: -25 °C hasta +55 °C

Humedad almacenamiento: 15% - 90% (no condensada)

===Administración===
Via navegador web

Protegida por contraseña

Administración y actualización software
===Protocolos VoIP===
H.323 versión 5, incluyendo extensiones propietarias

H.323 a través de UDP, TCP, TLS

SIP Versión 2, conforme a RFC 3261

SIP a través de UDP, TCP, TLS

RTP, SRTP (SDES, DTLS), RTCP, ICE

===Voice Codecs===
G.711 A-law / μ-law, G.723.1 (5.3 kbps), G.729AB, G722, G722.2 (AMR-WB)

VAD, CNG

Dynamic Jitter Buffering

Echo Compensation conforme con G.168

===Red===
STUN, TURN

RSTP, EAP-TLS/EAP-MD5 según IEEE 802.1X

VLAN-ID según IEEE 802.1Q

Soporte DHCP y LLDP/MED

Soporte NTP

===Características especiales===
Indicador LED

Especialmente diseñado para los dispositivos innovaphone IP61, IP63, IP64 e IP65

Una serie de códigos permiten utilizar algunas funcionalidades especiales de la PBX innovaphone, como funcionalidades de grupo, "captura de llamada", "llamada en espera" y "entrada dinámica a un grupo".

Acceso al directorio central de la PBX y a otras bases de datos externas a través de LDAP.

===Cód. Art.===
* IP1202: 50-01202-001
* IP1202/4: 50-01202-002
* IP1202e: 50-01202-003
* IP1202/4s: 50-01202-010

* Dual-Directional-Antenna para IP1202e: 50-01202-004
* Single-Directional-Antenna para IP1202e: 50-01202-005
* Omni-Directional-Antenna para IP1202e: 50-01202-006

==Certificados CE==
===Declaración de conformidad===
{{Template:CE-Decl_Wireless}}
*EN 50385, 2002
*EN 301 406, v2.1.1 (Radio)
*EN 60945 (EMC)
===Número WEEE===
{{Template:WEEE-Number}}
[[Category:Fichas técnicas ES|{{PAGENAME}}]]

Howto13r1:Create a second Voicemail

2019-11-19T08:16:01Z

She:

==Applies To==
This information applies to

* v13r1 and up



==More Information==
This article describes "How to create a second Voicemail" for the same language.
If you just want to create a voicemail in another language than you can use our Installer.

===Configuration===

1.Create a new instance via our "App" App.

[[Image:Voicemail1.png]]

2. Add voicemail

[[Image:Voicemail2.png]]

[[Image:Voicemail3.png]]

[[Image:Voicemail4.png]]

3. Attach Voicemail to your Config template

[[Image:Voicemail5.png]]

4. Insert URL into Services/HTTP/Client. Be sure that your password is the same as used in instance.

[[Image:Voicemail6.png]]

'''It is important to know, that by adding via PBX Manager a Voicemail Object the passwords will be set again.'''

So either you check out the password via Webconsole and insert it in Services/HTTP/Client or you have to set all passwords again afterwards.

- Password of Voicemail App Object (via Advanced GUI)

- Password of Instance

- Password of Services/HTTP/Client

== Related Articles ==
*[[Course13:IT_Connect_-_13_Design_of_the_Application_Platform#Create_a_new_App_Service_Instance]]
*[[Howto:V13_Access_Voicemail_Files]]

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

Howto13r1:Create a second Voicemail

2019-11-19T08:15:30Z

She:

==Applies To==
This information applies to

* v13r1 and up



==More Information==
This article describes "How to create a second Voicemail" for the same language.
If you just want to create a voicemail in another language than you can use our Installer.

===Configuration===

1.Create a new instance via our "App" App.

[[Image:Voicemail1.png]]

2. Add voicemail

[[Image:Voicemail2.png]]

[[Image:Voicemail3.png]]

[[Image:Voicemail4.png]]

3. Attach Voicemail to your Config template

[[Image:Voicemail5.png]]

4. Insert URL into Services/HTTP/Client. Be sure that your password is the same as used in instance.

[[Image:Voicemail6.png]]

'''It is important to know, that by adding via PBX Manager a Voicemail Object the passwords will be set again.'''

So either you check out the password via Webconsole and insert it in Services/HTTP/Client or you have to set all passwords again afterwards.
- Password of Voicemail App Object (via Advanced GUI)
- Password of Instance
- Password of HTTP/Service/Client

== Related Articles ==
*[[Course13:IT_Connect_-_13_Design_of_the_Application_Platform#Create_a_new_App_Service_Instance]]
*[[Howto:V13_Access_Voicemail_Files]]

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

Reference13r1:Concept App Service Fax

2019-10-21T10:16:22Z

She:

[[Category:Concept|Apps]]

The App Service Fax is an App Service which can be installed on an innovaphone App Platform. It provides sending or receiving FAX documents with the innovaphone PBX and an user app to manage the documents.

== Applies To ==
* innovaphone PBX from version 13r1

== Features ==
The App Service Fax sends PDF documents as FAX documents and converts received FAX documents to PDF.

== Requirements ==
* innovaphone App Platform
* Device with a FAX interface for each PBX fax object
* SIP Name of Fax Object must be the same as Name of Fax instance!

== Technical Overview ==
[[Image:Concept fax.png]]

== Apps ==
=== innovaphone-fax ===
This app is provided for the users to send fax documents and view or download received documents. The app reads the argument mailbox=<sip name> to work with the given account instead of the user logged in. It uses the com.innovaphone.search API to search for contacts with FAX numbers.

Howto13r1:Hosting - Dedicated AP for every customer

2019-10-08T10:19:40Z

She: /* Install customer PBX and AP */

==Applies To==
This information applies to

* V13



=The Idea=

This description is to simplify the installation of "one PBX and one Application Platform per customer" that can be used for Cloud setups

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the hosting platform
* copy a template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of templates
* copying the template to a customer system

If you set up a Hosting scenario, please check our [http://wiki.innovaphone.com/index.php?title=Howto:V13_Hosting Considerations]

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create template before you run through the Installer!''' 

=Create a Template =

This template will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the template)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first customer PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

Example: http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master 
Explanation: 
'''00001-pbx.cloud.de''' - DNS of first customer PBX 
'''00001.cloud.de''' - Domain/System Name of first customer PBX 
'''apaddr=172.16.115.46''' - IP of App Platform 
'''apdns=00001-apps.cloud.de''' - DNS of App Platform from customer PBX 
'''pbxloc=master''' 
'''location=master''' - Choose master or slave depending on your scenario. 

Click through Installer.

[[Image:CloudSetup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.

== Related Articles ==
*[[Howto:V13_Hosting]]
* [[Reference13r1:Concept_App_Platform]]
* [[Howto:V13_Hosting_-_Central_AP_for_multiple_customers]]
* [[Reference13r1:Concept_Talking_to_the_v13_Application_Platform_using_PHP]]

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

Reference13r1:Concept Provisioning

2019-10-08T10:13:02Z

She: /* Implementation */

=Overview=
In 13r1 provisioning of phones is done with Devices. From a user point of view a provisioning code is entered on a new phone and then the rest happens automatically. There are different kind of provisioning. A user who adds a new phone, an adminitrator who performs rollout for many phones and maybe more. The different types of provisioning are defined one after the other.

== User adding a new phone ==

From a user point of view this should work as follows:

* The user unpacks the phone and connects it to the network (we assume 13r1 is on the phone already, but maybe an old build)
* On the display a form requesting a provisioning code is displayed
* The user opens myApps/Profile and selects to add a new phone
* Drop down to select a category is provided
* When the user has sent the request a provisioning code is displayed
* The user adds the provisioning code on the phone
* The phone is updated to the current version of the installation, configured, a device is added to the user in the PBX

=== Implementation ===

;Setup:
:* The Devices PBX app object must have a websocket connection flag.
:* The UsersAdmin PBX app object must have a websocket connection flag, the Services flag and the "devices-api" App.

;User connects a 13r1 phone to the network:
:* The standard update url config.innovaphone.com is requested.
:* The provision code form is displayed.

;User selects to add a new phone on myApps/Profile:
:* The Users instance asks Devices for a list of categories configured for provisioning
:* The Users Instance requests a provisioning code from Devices with selected category
:* Devices requests a provisioning code from config.innovaphone.com and supplies the devices URL to config.innovaphone.com
:* config.innovaphone.com generates a random provisioning code of 12 digists without any structure
:* config.innovaphone.com stores the provisioning code and URL in the database
:* Devices stores the provisioning code together with domain and category in the database
:* Users stores the provisioning code and with the requesting user in the database

;The user enters the provisioning code:
:* The code is sent to config.innovaphone.com
:* config.innovaphone.com configures the Devices URL of the customer
:* The phone connects to Devices and sends the provisioning code
:* Devices assigns the phone to a domain and category
:* Devices updates the phone
:* Devices configures the phone
:* Devices sends the mac address and provisioning code to a Users instance of matching domain. If no Users with matching domain is connected, the mac address is stored in the database so that the info can be sent, when a matching Users connects
:* Users configures a device for the user

=== Update Software functionality in Devices ===

A list of jobs is stored. This list contains domain and category of the devices to be updated. With a job the json which was current on the time of creation is stored. When a device registers it is updated according to the latest matching job.

=== Update Config functionality in Devices ===

A list of jobs is stored. This list contains doman, category and a type of config with related parameters. When a device registers it is updated according to the latest jobs of all types.

== Rollout of many phones on UsersAdmin ==

On UsersAdmin under "Register phones" phones can be provisioned for many users at once.

To provision the phones:

* Select new phone registrations and follow the steps.
* On the first step the connection with Devices is stablished.
* On the second step, the provisioning category (the categories are configured on Devices for a given domain) and the phone app are selected. A dropdown menu will be displayed if there is more than one option.
* On the third step the users must be selected
* On the fourth step the provisioning codes list is displayed. This list can also be downloaded as a CSV file. Every user must enter his code on his phone. After that, the state should change from "Pending" to "Registered".

== Offline Provisioning ==

There is also the possibility for offline provisioning: [[{{NAMESPACE}}:Concept_Offline_Provisioning]]

== Show provisioning code display on phones ==

You have to issue the following command to show the provisioning code display on phones again:
''!vars create UPDATE/PROVISIONING-CODE h prompt''

No reboot or config write is required

=Related Articles=
* [[{{NAMESPACE}}:Concept_Offline_Provisioning]]
* [[{{NAMESPACE}}:Services/Provisioning]]
* [[{{NAMESPACE}}:Services/Update]]

Reference13r1:Concept App Platform

2019-09-06T15:21:44Z

She: /* Virtual machine */

= General =
* V13 uses [https://buildroot.org/ buildroot]
* this is an own (innovaphone) collection of packages
* For further information see: [https://buildroot.org/docs.html Buildroot Documentations]

== Requirements ==

* V13 or up
* Gateway (arm): IPx10 (with CF card) or IPx11 (with mSATA SSD)
* Virtual (x86_64): HyperV or VMWare

== Default credentials ==

'''During INSTALL, the default passwords are replaced with the global Admin PW!'''
* SSH-Login with '''admin''' and '''ipapps'''
* root login with '''root''' and '''iplinux''' (the root login is not directly possible, you have to login as admin first and use the command ''su root'')
* manager App (web login) '''pwd'''

= App Platform - arm (Gateway)=

* The installation image has a size of ~50MB. During installation, the following partitions are created:
** /dev/sda1 fat32: 200MB (contains ramdisk, rootfs and kernel)
** /dev/sda2 ext4: depends on disk size (contains databases, log files and apps)
** /dev/sda3 ext4: 500MB (contains the rootfs)
** /dev/sda4 swap: 512MB

= App Platform - x86-64 (Virtual Machine) =

* The default disk size is 16GB. It should be increased '''before''' the first start if needed!

* Multiple CPUs are supported, default is one CPU

* default RAM: 512MB
* static IP address, DNS, Gateway can be configured with the command '''setip''' on the console. Run '''setip --help''' to get a list of parameters. (Example: setip --addr=x.x.x.x --mask=x.x.x.x --gateway=x.x.x.x --dns1=x.x.x.x)
* If you have permission problems change to su user (Password is iplinux or your new admin password)
* To figure out your ip address you can use the command: ''ip address'' on the console.
* '''loadkeys de''' can be used to change to german keyboard layout (etc.)

* partitions:
** /dev/sda1 ext2: 350MB (contains ramdisk, rootfs and kernel)
** /dev/sda2 ext4: depends on disk size (contains databases, log files and apps)
** /dev/sda3 ext4: 500MB (contains the rootfs)
** /dev/sda4 swap: 512MB

= Installation =
==ARM Gateway==

If you setup a Gateway with the install procedure, the App Platform is installed automatically (Https Download has to be allowed and shouldn't be blocked by any firewall.) 
You can also install it manually:
* Open App Platform -> General and '''Enable Linux Support'''. Restart the gateway.
* You need to enable Proxy-ARP on [[Reference13r1:IP4/ETH/IP|ETH0]] or [[Reference13r1:IP4/ETH/IP|ETH1]], so your Gateway and the Linux Appliance will share the same physical interface.
* Open App Platform -> IP and configure the IP settings of the App Platform. Restart the Gateway.
* Open App Platform -> Installation and select the given version or enter an own path to the ''app-platform-armel.img'' image file.
* The installation runs without any further required step.

==Virtual machine==

* Import the image into your server environment.
* Edit the disk size, if needed.
* Start the machine and wait until it reboots and starts again.
* Note: If you need to access an IP addresses available through a VPN connection from from inside the virtual machine, it could be that you need to set the network of your VM to NAT (and also add the URL for an IP to /etc/hosts)

[https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#Configuration More Configuration Hints regarding VM Ware]

== Backup of the Apps ==

Each App Service can have multiple instances and each instance has its own database. The manager app itself also has its own database. 
There are no other files which need to be backuped. 
The standard way to backup the databases is through the Devices App [[Reference13r1:Concept_App_Service_Devices#Backups]]. 
 
An alternate way is to use a command file which is similar to the command files from the firmware.

===Commands===
* '''times''' 0,12 # backup only at 0 or 12 o'clock
* '''backup-instances''' http://user:pw@ip/path/#I-#D.dump PUT
** PUT and POST are supported, all instances including the manager itself are saved
* '''backup-instance''' http://user:pw@ip/path/#I-#D.dump apidemo example.com PUT
** backup a single instance with instance name and instance domain
* '''backup-manager''' http://user:pw@ip/path/#I-#D.dump

===Hash parameters===
* #L App Platform label (neu), e.g. 10024
* #A App label (neu), e.g. 130004
* #I instance name (neu), e.g. reporting1
* #D instance domain (neu), e.g. innovaphone.com
* #m MAC address of the LAP, e.g. 00ab11eeff
* #d Current date and time (plain UTC without daylight saving and timezone adjustments) 20051010-170130
* #bn rolling backup index
* ## escapes a hash mark

= App Platform Infrastructure and Concept =
== Webserver ==
The app platform includes a webserver that is highly optimized for handling many Websocket connections at a low memory footprint.
All apps use that webserver by registering for specific HTTP subpath. So they can all use the same HTTP/HTTPS ports - typically the standard ports.

=== Import Custom SSL Certificate ===
You have to upload a PEM Certificate with the following chain structure and without password encoding.

-----BEGIN RSA PRIVATE KEY-----
(certificate Key: your_domain_name.key)
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
(certificate: your_domain_name.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Intermediate certificate: DigiCertCA.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Root certificate: TrustedRoot.crt)
-----END CERTIFICATE-----

== Database ==
The app platform creates a database for each app instance with a given password. In the installer there will be used randomly generated passwords. You can set a new database password for every instance in the Application Platform.

The apps should store all data in that database. That makes sure that a consistent backup and restore of app instances can be done by the app platform manager.
In hosted scenarios, having separate databases for each instance also makes sure that the data of different customers are clearly separated and can easily be moved from one physical platform to another.

The default configuration decline database request from extern. If you need external access you can change the PGSQL configuration in the file ''/mnt/sda2/pgsql/pg_hba.conf''. (Please think about it before you do it, because a better way is to create your own local app with local database access.)

== App Platform Manager ==
The App Platform Manager is the central component of the App Platform. It does the following:
* Installing app services by downloading the binaries from an app store.
* Running and monitoring app services. If an app service crashes it is restarted, automatically.
* Management of app instances and providing them with the environment they need:
** A database
** A webserver path
** A password for authentication
* Backup and restore of app instances.
* Collecting debug information like tracing and crash dumps.
* System monitoring (CPU usage, memory usage, etc).

== App Services ==
App services are runned by the App Platform Manager. They implement an interface that is used by the manager to start, stop and configure app instances. Each service runs in a separate child process of the manager.

== App Instances ==
The actual functionality of an app service is provided by app instances. They run in the same process as the app service but have a distinct webserver path and their own database. There can be 0..n instances of an app service. Instances can optionally host (web) apps that can be opened in the myApps client.

Each instance of an App service has two passwords. The instance password itself and a database password. If you want to change it you must update the password on both sides. 
The instance password must match to the password in the corresponding PBX App objects, while one instance can have different App objects. 
The database password must be just known to the manager and not outside of the App Platform.

== Relationship between app instances and app objects in the PBX ==
Typically an app instance is connected to one or more app objects in a customer PBX. This is done by configuring the same parameters on both sides:
* URL
* Password
The password is used by the PBX for authenticating itself, users and services against the app instance.

Some apps need a websocket connection with the PBX. When "websocket" is activated at the app object, the PBX establishes a websocket connection to the app instance and provides the APIs that are configured at the app object.

=== Supported scenarios ===
It is important to understand that the concept does not do any assumptions on how PBXes and APs are correlated. So you can have
* One AP for one customer
* One AP for many customers
* Many APs for one customer
* Many APs for many customers

Attention: The V13 installer can only configure the scenario "''One AP for one customer''". If you want to have a different scenario, you have to configure it manually.

For hosting or cloud scenarios you need special scenarios. Please refer our [[Howto:V13_Hosting| V13 Hosting]] instructions.

=== Restrictions ===
Currently we don't have redundancy for app instances or APs.

= Tracing =
Each App Service has its own log file, which can be accessed through the Manager App. You can configure a log file size for each App Service. 
Each App Intance has its own trace flags. The following trace flags can be set: 

* Alarm client: used by the manager to send alarms to an alarm server
* App: logs from the App Service itself
* App WebSocket: logs app websocket connections (e.g. from PBX objects to an App Service or from the UI to the App Service)
* AppSharing: just native clients
* AppProxy: just native clients, logs requests which are proxied between the local webserver and the remote server
* Audio: just native clients
* Browser: just native clients
* Command: the command interface is used to execute shell commands, e.g. used by the manager App
* Config: logs config changes of an App
* Database: database logs
* DB files: database file logs
* DNS: DNS request logging
* DTLS: just native clients, DTLS request logging
* Ethernet: interface to get ethernet adapater infos, just manager App
* File: logs for file system access (synchronous), e.g. manager App
* Files: logs for file system access (asynchronous)
* HTTP client: http client logs
* HTTP file: logs for static HTTP files
* ICE: just native clients
* LDS: local domain sockets
* Media: just native clients
* Media channel: just native clients
* Process: IProcess interface logs which is used for spawning, killing processes etc.
* SMTP: SMTP client logs
* TCP: TCP logs
* Time: ITime interface logs
* TLS: TLS logs
* TURN: just native clients
* UDP: UDP logs
* Video: just native clients
* WebSocket client: logs outgoing websocket connections
* Webserver traffic: logs incoming HTTP traffic, which is forwarded from the webserver to the App
* WebDAV service: logs WebDAV requests to the App
* Webserver: enables webserver specific logs

= How-Tos =

== Resizing the disk of a Virtual machine ==

* stop the VM
* expand the disk using your VM utilities
* start the VM and boot from the first boot entry '''rescue/setup'''
* login with '''root''' and '''iplinux'''
* call '''/home/root/install_step1.sh log.txt resize'''
* the VM reboots automatically after a successful resize

== Shrink the physically size of PostgreSQL database files ==
Tuples that are deleted in your databse are not physically removed from the database-file. So the claimed space on the harddisk is still in use after the delete operation.
If you need to free up some disk space you can force to reorganize the physically database-file on your harddisk.

'''Important: You are operating on the Database, you have to make a Backup of your Database before you do this!'''

Login via SSH to the APPlatform with the ''admin'' User
su root
sudo -u postgres reindexdb -a
sudo -u postgres vacuumdb -a -f

Note: This may take some time and CDRs (or other data written to a DB) won't be received during this time.

After the process you can check the free dispace via <code>df -h</code>. You can check the claimed space from the database file with the command <code>du -sh /mnt/sda2/pgsql/</code>.

== Change IP Addresses / DNS Names ==

If you want to change the System Name or the DNS Name of the PBX and/or AP Platform you must change records manually '''in the described order'''!
You have to know the Admin password to directly Login to the AP-Plattform.

=== App Platform ===
; Settings - General
* ''Devices app URL''
* ''App platform DNS name''

; Settings - Alarms and Events
* ''URL''

; All Instances
* ''Domain''
* ''Webserver path''

=== PBX ===
Download the configuration and ''search/replace'' in the config file. Upload the config file and reboot.

Manual:
* ''URL'' in all PBX Object (Apps, Voicemail ...)
* [[Reference13r1:PBX/Config/General|IP address for App Platform]]
* [[Reference13r1:PBX/Config/myApps|Reset Password Page]]
* [[Reference13r1:PBX/Config/Authentication|Verification link]]

Depending on your change you have to activate/deactivate the Setting [[Reference13r1:PBX/Config/General|Operation without DNS]]

=== Additional Devices / Steps ===
* ''Devices Registration URL''
* ''Alarm server''
* Reverse Proxy configuration
* Change ''Domain Name'' in Devices if you have also changed the system name

== How to recover from a broken File System ==
Sometimes you may find messages in the ''messages'' log file (in ''var/log'') like

initial error at 1500329378: ext4_journal_start_sb:328
last error at 1500329378: ext4_journal_start_sb:328

Or you get events like "Broken file system" from your AP.

This indicates a file system failure on the Linux Installation.

When the Linux file system is broken, you can try to repair it using some command line Linux tools.

If this doesn't fix your issue, you need to replace the SSD with a new one, re-install the App Platform and any applications and restore your backups.

=== Gateway ===

* Open the WebGUI of the gateway running your LAP and proceed to ''App Platform/General''
** terminate Linux (''Status/Stop'')
** modify the Kernel command line from root=/dev/sda3 to root=/dev/ram0
** modify the Initrd file to ramdisk.ext2.xz
** modify the ramdisk size to 100000
** start Linux again
:: This will run Linux on another (hopefully sane) partition.

* use [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html putty] to log in to the LAP's command line
** on the command prompt, use <code>e2fsck -p -f /dev/sda2</code>
** on the command prompt, use <code>e2fsck -p -f /dev/sda3</code>
:: this should fix any issue on the file system

* go back to the WebGUI of the gateway running your LAP and proceed to ''App Platform/General''
** terminate Linux (''Status/Stop'')
** modify the ''Kernel command line'' from ''root=/dev/ram0'' to <code>root=/dev/sda3</code>
** clear the Initrd file field
** clear the ramdisk size field
** start Linux again
:: This will run Linux on the original partition.

=== VM ===

Restart the VM and select the first entry in the boot menu from grub.

* use [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html putty] to log in to the LAP's command line
** on the command prompt, use <code>e2fsck -p -f /dev/sda2</code>
** on the command prompt, use <code>e2fsck -p -f /dev/sda3</code>
:: this should fix any issue on the file system
* Reboot your VM

Reference13r1:Concept App Platform

2019-09-06T15:20:11Z

She: /* Virtual machine */

= General =
* V13 uses [https://buildroot.org/ buildroot]
* this is an own (innovaphone) collection of packages
* For further information see: [https://buildroot.org/docs.html Buildroot Documentations]

== Requirements ==

* V13 or up
* Gateway (arm): IPx10 (with CF card) or IPx11 (with mSATA SSD)
* Virtual (x86_64): HyperV or VMWare

== Default credentials ==

'''During INSTALL, the default passwords are replaced with the global Admin PW!'''
* SSH-Login with '''admin''' and '''ipapps'''
* root login with '''root''' and '''iplinux''' (the root login is not directly possible, you have to login as admin first and use the command ''su root'')
* manager App (web login) '''pwd'''

= App Platform - arm (Gateway)=

* The installation image has a size of ~50MB. During installation, the following partitions are created:
** /dev/sda1 fat32: 200MB (contains ramdisk, rootfs and kernel)
** /dev/sda2 ext4: depends on disk size (contains databases, log files and apps)
** /dev/sda3 ext4: 500MB (contains the rootfs)
** /dev/sda4 swap: 512MB

= App Platform - x86-64 (Virtual Machine) =

* The default disk size is 16GB. It should be increased '''before''' the first start if needed!

* Multiple CPUs are supported, default is one CPU

* default RAM: 512MB
* static IP address, DNS, Gateway can be configured with the command '''setip''' on the console. Run '''setip --help''' to get a list of parameters. (Example: setip --addr=x.x.x.x --mask=x.x.x.x --gateway=x.x.x.x --dns1=x.x.x.x)
* If you have permission problems change to su user (Password is iplinux or your new admin password)
* To figure out your ip address you can use the command: ''ip address'' on the console.
* '''loadkeys de''' can be used to change to german keyboard layout (etc.)

* partitions:
** /dev/sda1 ext2: 350MB (contains ramdisk, rootfs and kernel)
** /dev/sda2 ext4: depends on disk size (contains databases, log files and apps)
** /dev/sda3 ext4: 500MB (contains the rootfs)
** /dev/sda4 swap: 512MB

= Installation =
==ARM Gateway==

If you setup a Gateway with the install procedure, the App Platform is installed automatically (Https Download has to be allowed and shouldn't be blocked by any firewall.) 
You can also install it manually:
* Open App Platform -> General and '''Enable Linux Support'''. Restart the gateway.
* You need to enable Proxy-ARP on [[Reference13r1:IP4/ETH/IP|ETH0]] or [[Reference13r1:IP4/ETH/IP|ETH1]], so your Gateway and the Linux Appliance will share the same physical interface.
* Open App Platform -> IP and configure the IP settings of the App Platform. Restart the Gateway.
* Open App Platform -> Installation and select the given version or enter an own path to the ''app-platform-armel.img'' image file.
* The installation runs without any further required step.

==Virtual machine==

* Import the image into your server environment.
* Edit the disk size, if needed.
* Start the machine and wait until it reboots and starts again.
* Note: If you need to access an IP addresses available through a VPN connection from from inside the virtual machine, it could be that you need to set the network of your VM to NAT (and also add the URL for an IP to /etc/hosts)

[https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#Configuration More Configuration Hints]

== Backup of the Apps ==

Each App Service can have multiple instances and each instance has its own database. The manager app itself also has its own database. 
There are no other files which need to be backuped. 
The standard way to backup the databases is through the Devices App [[Reference13r1:Concept_App_Service_Devices#Backups]]. 
 
An alternate way is to use a command file which is similar to the command files from the firmware.

===Commands===
* '''times''' 0,12 # backup only at 0 or 12 o'clock
* '''backup-instances''' http://user:pw@ip/path/#I-#D.dump PUT
** PUT and POST are supported, all instances including the manager itself are saved
* '''backup-instance''' http://user:pw@ip/path/#I-#D.dump apidemo example.com PUT
** backup a single instance with instance name and instance domain
* '''backup-manager''' http://user:pw@ip/path/#I-#D.dump

===Hash parameters===
* #L App Platform label (neu), e.g. 10024
* #A App label (neu), e.g. 130004
* #I instance name (neu), e.g. reporting1
* #D instance domain (neu), e.g. innovaphone.com
* #m MAC address of the LAP, e.g. 00ab11eeff
* #d Current date and time (plain UTC without daylight saving and timezone adjustments) 20051010-170130
* #bn rolling backup index
* ## escapes a hash mark

= App Platform Infrastructure and Concept =
== Webserver ==
The app platform includes a webserver that is highly optimized for handling many Websocket connections at a low memory footprint.
All apps use that webserver by registering for specific HTTP subpath. So they can all use the same HTTP/HTTPS ports - typically the standard ports.

=== Import Custom SSL Certificate ===
You have to upload a PEM Certificate with the following chain structure and without password encoding.

-----BEGIN RSA PRIVATE KEY-----
(certificate Key: your_domain_name.key)
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
(certificate: your_domain_name.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Intermediate certificate: DigiCertCA.crt)
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
(Root certificate: TrustedRoot.crt)
-----END CERTIFICATE-----

== Database ==
The app platform creates a database for each app instance with a given password. In the installer there will be used randomly generated passwords. You can set a new database password for every instance in the Application Platform.

The apps should store all data in that database. That makes sure that a consistent backup and restore of app instances can be done by the app platform manager.
In hosted scenarios, having separate databases for each instance also makes sure that the data of different customers are clearly separated and can easily be moved from one physical platform to another.

The default configuration decline database request from extern. If you need external access you can change the PGSQL configuration in the file ''/mnt/sda2/pgsql/pg_hba.conf''. (Please think about it before you do it, because a better way is to create your own local app with local database access.)

== App Platform Manager ==
The App Platform Manager is the central component of the App Platform. It does the following:
* Installing app services by downloading the binaries from an app store.
* Running and monitoring app services. If an app service crashes it is restarted, automatically.
* Management of app instances and providing them with the environment they need:
** A database
** A webserver path
** A password for authentication
* Backup and restore of app instances.
* Collecting debug information like tracing and crash dumps.
* System monitoring (CPU usage, memory usage, etc).

== App Services ==
App services are runned by the App Platform Manager. They implement an interface that is used by the manager to start, stop and configure app instances. Each service runs in a separate child process of the manager.

== App Instances ==
The actual functionality of an app service is provided by app instances. They run in the same process as the app service but have a distinct webserver path and their own database. There can be 0..n instances of an app service. Instances can optionally host (web) apps that can be opened in the myApps client.

Each instance of an App service has two passwords. The instance password itself and a database password. If you want to change it you must update the password on both sides. 
The instance password must match to the password in the corresponding PBX App objects, while one instance can have different App objects. 
The database password must be just known to the manager and not outside of the App Platform.

== Relationship between app instances and app objects in the PBX ==
Typically an app instance is connected to one or more app objects in a customer PBX. This is done by configuring the same parameters on both sides:
* URL
* Password
The password is used by the PBX for authenticating itself, users and services against the app instance.

Some apps need a websocket connection with the PBX. When "websocket" is activated at the app object, the PBX establishes a websocket connection to the app instance and provides the APIs that are configured at the app object.

=== Supported scenarios ===
It is important to understand that the concept does not do any assumptions on how PBXes and APs are correlated. So you can have
* One AP for one customer
* One AP for many customers
* Many APs for one customer
* Many APs for many customers

Attention: The V13 installer can only configure the scenario "''One AP for one customer''". If you want to have a different scenario, you have to configure it manually.

For hosting or cloud scenarios you need special scenarios. Please refer our [[Howto:V13_Hosting| V13 Hosting]] instructions.

=== Restrictions ===
Currently we don't have redundancy for app instances or APs.

= Tracing =
Each App Service has its own log file, which can be accessed through the Manager App. You can configure a log file size for each App Service. 
Each App Intance has its own trace flags. The following trace flags can be set: 

* Alarm client: used by the manager to send alarms to an alarm server
* App: logs from the App Service itself
* App WebSocket: logs app websocket connections (e.g. from PBX objects to an App Service or from the UI to the App Service)
* AppSharing: just native clients
* AppProxy: just native clients, logs requests which are proxied between the local webserver and the remote server
* Audio: just native clients
* Browser: just native clients
* Command: the command interface is used to execute shell commands, e.g. used by the manager App
* Config: logs config changes of an App
* Database: database logs
* DB files: database file logs
* DNS: DNS request logging
* DTLS: just native clients, DTLS request logging
* Ethernet: interface to get ethernet adapater infos, just manager App
* File: logs for file system access (synchronous), e.g. manager App
* Files: logs for file system access (asynchronous)
* HTTP client: http client logs
* HTTP file: logs for static HTTP files
* ICE: just native clients
* LDS: local domain sockets
* Media: just native clients
* Media channel: just native clients
* Process: IProcess interface logs which is used for spawning, killing processes etc.
* SMTP: SMTP client logs
* TCP: TCP logs
* Time: ITime interface logs
* TLS: TLS logs
* TURN: just native clients
* UDP: UDP logs
* Video: just native clients
* WebSocket client: logs outgoing websocket connections
* Webserver traffic: logs incoming HTTP traffic, which is forwarded from the webserver to the App
* WebDAV service: logs WebDAV requests to the App
* Webserver: enables webserver specific logs

= How-Tos =

== Resizing the disk of a Virtual machine ==

* stop the VM
* expand the disk using your VM utilities
* start the VM and boot from the first boot entry '''rescue/setup'''
* login with '''root''' and '''iplinux'''
* call '''/home/root/install_step1.sh log.txt resize'''
* the VM reboots automatically after a successful resize

== Shrink the physically size of PostgreSQL database files ==
Tuples that are deleted in your databse are not physically removed from the database-file. So the claimed space on the harddisk is still in use after the delete operation.
If you need to free up some disk space you can force to reorganize the physically database-file on your harddisk.

'''Important: You are operating on the Database, you have to make a Backup of your Database before you do this!'''

Login via SSH to the APPlatform with the ''admin'' User
su root
sudo -u postgres reindexdb -a
sudo -u postgres vacuumdb -a -f

Note: This may take some time and CDRs (or other data written to a DB) won't be received during this time.

After the process you can check the free dispace via <code>df -h</code>. You can check the claimed space from the database file with the command <code>du -sh /mnt/sda2/pgsql/</code>.

== Change IP Addresses / DNS Names ==

If you want to change the System Name or the DNS Name of the PBX and/or AP Platform you must change records manually '''in the described order'''!
You have to know the Admin password to directly Login to the AP-Plattform.

=== App Platform ===
; Settings - General
* ''Devices app URL''
* ''App platform DNS name''

; Settings - Alarms and Events
* ''URL''

; All Instances
* ''Domain''
* ''Webserver path''

=== PBX ===
Download the configuration and ''search/replace'' in the config file. Upload the config file and reboot.

Manual:
* ''URL'' in all PBX Object (Apps, Voicemail ...)
* [[Reference13r1:PBX/Config/General|IP address for App Platform]]
* [[Reference13r1:PBX/Config/myApps|Reset Password Page]]
* [[Reference13r1:PBX/Config/Authentication|Verification link]]

Depending on your change you have to activate/deactivate the Setting [[Reference13r1:PBX/Config/General|Operation without DNS]]

=== Additional Devices / Steps ===
* ''Devices Registration URL''
* ''Alarm server''
* Reverse Proxy configuration
* Change ''Domain Name'' in Devices if you have also changed the system name

== How to recover from a broken File System ==
Sometimes you may find messages in the ''messages'' log file (in ''var/log'') like

initial error at 1500329378: ext4_journal_start_sb:328
last error at 1500329378: ext4_journal_start_sb:328

Or you get events like "Broken file system" from your AP.

This indicates a file system failure on the Linux Installation.

When the Linux file system is broken, you can try to repair it using some command line Linux tools.

If this doesn't fix your issue, you need to replace the SSD with a new one, re-install the App Platform and any applications and restore your backups.

=== Gateway ===

* Open the WebGUI of the gateway running your LAP and proceed to ''App Platform/General''
** terminate Linux (''Status/Stop'')
** modify the Kernel command line from root=/dev/sda3 to root=/dev/ram0
** modify the Initrd file to ramdisk.ext2.xz
** modify the ramdisk size to 100000
** start Linux again
:: This will run Linux on another (hopefully sane) partition.

* use [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html putty] to log in to the LAP's command line
** on the command prompt, use <code>e2fsck -p -f /dev/sda2</code>
** on the command prompt, use <code>e2fsck -p -f /dev/sda3</code>
:: this should fix any issue on the file system

* go back to the WebGUI of the gateway running your LAP and proceed to ''App Platform/General''
** terminate Linux (''Status/Stop'')
** modify the ''Kernel command line'' from ''root=/dev/ram0'' to <code>root=/dev/sda3</code>
** clear the Initrd file field
** clear the ramdisk size field
** start Linux again
:: This will run Linux on the original partition.

=== VM ===

Restart the VM and select the first entry in the boot menu from grub.

* use [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html putty] to log in to the LAP's command line
** on the command prompt, use <code>e2fsck -p -f /dev/sda2</code>
** on the command prompt, use <code>e2fsck -p -f /dev/sda3</code>
:: this should fix any issue on the file system
* Reboot your VM

Howto13r1:Create a second Voicemail

2019-09-05T08:40:51Z

She: /* More Information */

==Applies To==
This information applies to

* v13r1 and up



==More Information==
This article describes "How to create a second Voicemail" for the same language.
If you just want to create a voicemail in another language than you can use our Installer.

===Configuration===

1.Create a new instance via our "App" App.

[[Image:Voicemail1.png]]

2. Add voicemail

[[Image:Voicemail2.png]]

[[Image:Voicemail3.png]]

[[Image:Voicemail4.png]]

3. Attach Voicemail to your Config template

[[Image:Voicemail5.png]]

4. Insert URL into Services/HTTP/Client. Be sure that your password is the same as used in instance.

[[Image:Voicemail6.png]]

It is important to know, that by adding via PBX Manager a Voicemail Object the passwords will be set again.

So either you check out the password via Webconsole and insert it in Services/HTTP/Client or you have to set all passwords again afterwards. (Instance and Object)

== Related Articles ==
*[[Course13:IT_Connect_-_13_Design_of_the_Application_Platform#Create_a_new_App_Service_Instance]]
*[[Howto:V13_Access_Voicemail_Files]]

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

Howto13r1:Hosting

2019-08-23T14:59:17Z

She: /* Considerations */

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}
__toc__


==Applies To==
This information applies to

* V13 and up

== Considerations ==

Before starting your v13 Installation you have to check the customer network and his requirements first.

Decide for the needed szenario:
* [[Howto:V13_Hosting_-_Central_AP_for_multiple_customers|Howto:V13 Hosting - Central AP for multiple customers]]
* [[Howto:V13 Hosting - Dedicated AP for every customer|Howto:V13 Hosting - Dedicated AP for every customer]]

* Decide for an Upgrade or new Installation/Parallel Installation. If you want to Upgrade than please test it before and read this article [http://wiki.innovaphone.com/index.php?title=Howto:V13_Firmware_Upgrade_V12r2_V13r1 Upgrade]
* Decision of Internet Access Scenario and Firewall settings [http://wiki.innovaphone.com/index.php?title=Course12:Advanced_-_Reverse_Proxy#Internet_Access_Scenarios Internet Access Scenarios]
* Decision of internal DNS / Installation Scenarios [http://wiki.innovaphone.com/index.php?title=Howto:V13_Installation_Scenarios Installation Scenarios]
* Decision of DHCP or fixed IPs [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 App Platform]
* Creating external DNS names (for every customer PBX, App Platform or adminpbx)
* Certificates
* Use Setup-Data.xls from Training [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_02_Lesson_on_Setting_up_the_basic_System Setup Data]

== Automation ==
* [[Reference13r1:Concept_Talking_to_the_v13_Application_Platform_using_PHP]]

Howto13r1:Hosting

2019-08-23T14:59:09Z

She: /* Considerations */

Howto13r1:Hosting - Central AP for multiple customers

2019-08-22T11:59:52Z

She: /* Configuration of customer PBXs */

==Applies To==
This information applies to
* V13r1 an up



== Objective ==

Setting up various PBXs for many customers, which are using only one AP!

'''System Requirements'''

Virtual Machines (HyperV, VMWare) or Physical Devices with SSD.

If you set up a Hosting scenario, please check our [http://wiki.innovaphone.com/index.php?title=Howto:V13_Hosting Considerations]

==Setting up Application platform & administrative PBX ==

'''Download respective images'''

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

'''Setup administrative PBX & Application Platform'''

Setup as learned in our courses.
*Master PBX to start a new system with external App Platform
*Network settings
*Connect AP platform
*App Platform is being installed
*innovaphone PBX options. We used the following options:
**Domain name: cloud.com
**PBX Name: adminpbx
**DNS PBX: adminpbx.cloud.com
**DNS AP: apps.cloud.com
*Save passwords
*E-mail account
*Apps are installed
*PBX and AP Certificates
*Test mode
*Done!!!

==Configuration of customer PBXs==

Every customer receives his own PBX

''' Add domain to devices'''

Open devices in your admin PBX (adminpbx.cloud.com).

Add Customer Domain (company01.com).

Choose a password. This password will be used for devices. If you select "Deploy the domain password on all devices" than it will be used as admin password as well.

[[Image:AddDomain.png]]

'''Setup PBX'''

Setup another machine (e.g. IPVA) and choose "Do manual configuration" or "Update and network settings only"
*Set pbx settings. We used the following options:
**System name: company01.com
**PBX name: pbx
**DNS PBX: pbx.company01.com
*Use as Domain
*Set PBX password
*Create config template "Config Admin". Add Apps to template.
*Create admin user and add template to user

'''Connect PBX to devices'''

Insert Device Registration URL

[[Image:DeviceRegistration.png]]

'''Edit device settings'''

Open devices on your adminpbx.
The MAC address of your new device is shown.
Choose Name and Domain.

[[Image:EditDeviceEntry.png]]

'''Create new category and assign it to device'''

[[Image:AddCategory.png]]

[[Image:AssignCategory.png]]

'''Change main page to myApps'''

Till now, inserting the DNS of PBX shows Advanced GUI.
To change this insert the following commands:
*!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
*!config write
*!config activate

[[Image:ConfigChangeHTTP0.png]]

''' Connect new PBX to Application Platform'''

Login to your new PBX, using HTTPS! (e.g. pbx.company01.com)
Open PBX Manager
Connect App Platform

Use Host of your AP Platform.

[[Image:ConnectAP.png]]

[[Image:ConnectAP2.png]]

Now you can see in your Apps App that the Domain is registered:

[[Image:RegisteredAccessDomain.png]]

Verify received eMail and check that App Platform is connected.

'''Create Devices & Devices Api Object'''

*Create both App objects on your new customer pbx (you can use Devices App from your adminPBX to use the AdvancedGUI).
**First Object "Devices"''
***Long Name: Devices
***Name: devices
***Critical activated
***Hide from LDAP activated
***Example URL: https://apps.cloud.com/cloud.com/devices/innovaphone-devices
***Websocket activated
***Password has to be the same as you choosed when "adding your Domain to Devices"

**Second Object "Devices Api**
***Long Name: DevicesApi
***Name: devices-api
***Critical activated
***Hide from LDAP activated
***Example URL: https://apps.cloud.com/cloud.com/devices/innovaphone-devices-api
***Websocket activated
***Password has to be the same as you choosed when "adding your Domain to Devices"

[[Image:CreateApps.png]]

Both apps have to be connected.

''' Open devices on your new PBX'''
*Open new myApps and choose Devices for your home screen

== Create instances of needed App services ==
Create
*for every customer
*for every needed app
*a new app service instance

More information can be find here: [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_13_Design_of_the_Application_Platform#Installing_an_App| Installing an App]

== Related Articles ==
* [[Reference13r1:Concept_App_Platform]]
* [[Howto:V13_Install_many_APs_for_many_customers]]

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

Howto13r1:Hosting - Central AP for multiple customers

2019-08-22T11:25:43Z

She: /* Objective */

==Applies To==
This information applies to
* V13r1 an up



== Objective ==

Setting up various PBXs for many customers, which are using only one AP!

'''System Requirements'''

Virtual Machines (HyperV, VMWare) or Physical Devices with SSD.

If you set up a Hosting scenario, please check our [http://wiki.innovaphone.com/index.php?title=Howto:V13_Hosting Considerations]

==Setting up Application platform & administrative PBX ==

'''Download respective images'''

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

'''Setup administrative PBX & Application Platform'''

Setup as learned in our courses.
*Master PBX to start a new system with external App Platform
*Network settings
*Connect AP platform
*App Platform is being installed
*innovaphone PBX options. We used the following options:
**Domain name: cloud.com
**PBX Name: adminpbx
**DNS PBX: adminpbx.cloud.com
**DNS AP: apps.cloud.com
*Save passwords
*E-mail account
*Apps are installed
*PBX and AP Certificates
*Test mode
*Done!!!

==Configuration of customer PBXs==

Every customer receives his own PBX

''' Add domain to devices'''

Open devices in your admin PBX (adminpbx.cloud.com).

Add Customer Domain (company01.com).

Choose a password. This password will be used for devices. If you select "Deploy the domain password on all devices" than it will be used as admin password as well.

[[Image:AddDomain.png]]

'''Setup PBX'''

Setup another machine (e.g. IPVA) and choose "Do manual configuration" or "Update and network settings only"
*Set pbx settings. We used the following options:
**System name: company01.com
**PBX name: pbx
**DNS PBX: pbx.company01.com
*Use as Domain
*Set PBX password
*Create config template "Config Admin". Add Apps to template.
*Create admin user and add template to user

'''Connect PBX to devices'''

Insert Device Registration URL

[[Image:DeviceRegistration.png]]

'''Edit device settings'''

Open devices on your adminpbx.
The MAC address of your new device is shown.
Choose Name and Domain.

[[Image:EditDeviceEntry.png]]

'''Create new category and assign it to device'''

[[Image:AddCategory.png]]

[[Image:AssignCategory.png]]

'''Change main page to myApps'''

Till now, inserting the DNS of PBX shows Advanced GUI.
To change this insert the following commands:
*!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
*!config write
*!config activate

[[Image:ConfigChangeHTTP0.png]]

''' Connect new PBX to Application Platform'''

Login to your new PBX, using HTTPS! (e.g. pbx.company01.com)
Open PBX Manager
Connect App Platform

Use Host of your AP Platform.

[[Image:ConnectAP.png]]

[[Image:ConnectAP2.png]]

Now you can see in your Apps App that the Domain is registered:

[[Image:RegisteredAccessDomain.png]]

Verify received eMail and check that App Platform is connected.

'''Create Devices & Devices Api Object'''

*Create both App objects on your adminPBX via Device/Advanced GUI.
**First Object "Devices"''
***Long Name: Devices
***Name: devices
***Critical activated
***Hide from LDAP activated
***Example URL: https://apps.cloud.com/cloud.com/devices/innovaphone-devices
***Websocket activated
***Password has to be the same as you choosed when "adding your Domain to Devices"

**Second Object "Devices Api**
***Long Name: DevicesApi
***Name: devices-api
***Critical activated
***Hide from LDAP activated
***Example URL: https://apps.cloud.com/cloud.com/devices/innovaphone-devices-api
***Websocket activated
***Password has to be the same as you choosed when "adding your Domain to Devices"

[[Image:CreateApps.png]]

Both apps have to be connected.

''' Open devices on your new PBX'''
*Open new myApps and choose Devices for your home screen

== Create instances of needed App services ==
Create
*for every customer
*for every needed app
*a new app service instance

More information can be find here: [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_13_Design_of_the_Application_Platform#Installing_an_App| Installing an App]

== Related Articles ==
* [[Reference13r1:Concept_App_Platform]]
* [[Howto:V13_Install_many_APs_for_many_customers]]

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

Reference13r1:Concept App Service Recordings

2019-08-21T10:34:42Z

She:

[[Category:Concept|Apps]]

== Applies To ==

* innovaphone PBX from version 13r1

== Apps ==

=== recordings ===
[[Image: Usrrecord.png‎]]
User version of the App allow you to :
* Access to the user specific records
* Filter records by name, by date

=== recordingsadmin ===
[[Image:Adminrecord.png]]
Admin version of the app allow you to :
* Access to all records
* Set up the records auto deletion retention time in days
* Filter records by name, by date

== Description ==

Recordings is an application running on the app platform which allows to capture the audio streams during a telephone call.

The users phone can be configured to send bi-directional audio streams to the Recordings App and store them into the database.

== Setting up ==

=== Setting up the Recordings App on the App Platform ===
On the App Platform click the “App Store”, find and install “Recordings”.

[[Image:Recordings1.png]]

Now click “Add” to add an instance and fill the entries:

[[Image:Recordings2.png]]

Save, then select the new instance and click Start. The Recording App on the App Platform is now up and running:

[[Image:Recordings3.png]]

=== Installing the App Object on the PBX ===

Prerequisite for installing and configuring the Recordings App Object is that an “AP” object is set up properly on the PBX and the user has the pbxmanager app available (as required for configuration of all other app objects). Select the pbxmanager app, then the “AP recordings”:

[[Image:Recordings4.png]]

Now you can configure a “User” object (TYPE selector) via which a user can access and administrate his own recordings and/or an “Admin” object which allows the access to all recordings. “NAME” and “SIP” can be freely chosen. The “Licenses” entry specifies how many licenses from the installed Recordings Service License are allocated for this object. For example:

[[Image:Recordings5.png]]

After pressing “Ok” the installed entry appears:

[[Image:Recordings6.png]]

Note: The checkmark between “USER” and “10” indicates that the Pbx Object has successfully opened a connection to the Recordings App.
Similarly an administrator object can be configured:

[[Image:Recordings7.png]]

Note: The administrator does not claim licenses

The App is known to the pbx under the “SIP” name. For the user to be able to use the app the checkbox must be ticked in the “Apps” tab:

[[Image:Recordings8.png]]

Note: the “arecordings” aka AdminRecordings app and the “urecordings” aka UserRecordings app are enable for the User. Please do not get confused by the appearance of “recordings” and “recordingsadmin” in the selection. These are dormant leftovers from previous configurations

=== Setting up the users phone ===

In order to set up the users phone for recording the Record to (URL) entry must be set:

[[Image:Recordings9.png]]

This entry consists of the app platform server address (http://172.16.67.100/) ,the “Webserver path” (as configured in Pic 2) and the “Files” submodule name. Furthermore, under “Recording” the “Recorder”: HTTP Server must be selected. The mode can be set as appropriate.:

[[Image:Recordings10.png]]

In the above example the mode “transparent” is set so the recording starts automatically when the call is established. We recommend that the users phone beconfigured via a configuration script or template.

Note: pressing the function key after recording has started pauses the recording, another press resumes recording until it stops when the call terminates.

=== Setting up reporting to provide the recordings app with the call information ===
In order to have call information (caller name, number..) the reporting information must be passed from the pbx to the recordings app. If this is not configured the calls are still recorded but appear with “No CDR” indistinguishable on the GUIs.
First enable CDR generation :

[[Image:Recordings11.png]]

Then configure the cdr target:

[[Image:Recordings12.png]]

“Type” must be “HTTP”.
Address: the app platform server ip address,
Port: must be 80
Method: must be “External(Post)”
Path: the webserver path as configured in Pic 1 plus “cdr” as the submodulename

== User and Admin GUI ==

=== User Gui ===

The User Gui allows a user to access the OWN recordings

He can listen, delete, filter through his records. Furthermore he can save the Record as wav file.
Every record will be saved per default for 30 days in Recordings App. (This can be modified by the admin in Recordingsadmin App)
If the user wants to save his Record for longer than he can press the lock symbol of his Record.

In the following picture we see the Gui showing one call:

[[Image:Recordings13.png]]
Pic 13

The GUI consists of a header containing a

* Search field to the left
The search can either be a search for names or phone numbers. The search is dynamic, so every every character or digit entered lists the matching substrings

* followed by a Sort button “A-Z”/”Z-A”
Sort the entries in ascending or descending order

* and a “settings” button to the right
the button opens a menu where display filters for name and/or recording periodcan be set:

[[Image:Recordings14.png]]

The above example shows just one recording entry, which comprises of the following items:

* an arrow indicating the call direction (bottom left to top right: outgoing, top right to bottom left: incoming).
* The partners name and number
* A conversion button
Since the recordings are stored in pcap format and the respective codec used for the call, the recording must be converted to a wave file before it can be played back (or downloaded). Note: depending on the codec used during the call this conversion process can be time consuming. The most time consuming codecs are: G729 and Opus.
* The date and time
The date and time of the recording
* A lock button
The recordings are automatically deleted after a specific time which can be set in the Administrator GUI. If the user wants to avoid this and permanently flag the recording, this button can be engaed. The button appears Orange for permanently flagged recordings.
* A delete checkmark
To delete recording(s) they can be selected here, A confirm button triggers the deletion.

==== Conversion process ====

When pressing the conversion button a thread is started on the app platform for this purpose. The conversion button changes to a circling activity icon with the percentage completed indicator below. Multiple conversions can be started, however they are processed subsequently . Once the convertion process is completed the activity indicator changes to a download icon (to download the wave file) with the duration of the audio file underneath. Additionally a player interface opens in the recording item:

[[Image:Recordings15.png]]
Pic 15

The wave file generated by the conversion process is stored temporarily in the database to allow for subsequent access without the nessecity to go through the conversion process again. After a lifetime of 1 hour this temporary file is deleted and the player item in the recording entry disappears.

=== Admin Gui ===

TheAdmin Gui allows a user to access ALL recordings. Its layout is similar to the users Gui with the addition that both parties of the call are showm with the call initiator in the top row.:

[[Image:Recordings16.png]]
Pic16

The settings menu contains, besides the filter settings an item to configure the time how long the recordings are held in the database before they are permanently deleted:

[[Image:Recordings17.png]]

== Appendix ==

Howto13r1:Hosting - Central AP for multiple customers

2019-08-21T08:58:41Z

She: /* Objective */

==Applies To==
This information applies to
* V13r1 an up



== Objective ==

Setting up various PBXs for many customers, which are using only one AP!

'''System Requirements'''

Virtual Machines (HyperV, VMWare) or Physical Devices with SSD.

If you set up a Hosting scenario, please check our [http://wiki.innovaphone.com/index.php?title=Howto:V13_Hosting Considerations]

==Setting up Application platform & administrative PBX ==

'''Download respective images'''

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

'''Setup administrative PBX & Application Platform'''

Setup as learned in our courses.
*Master PBX to start a new system with external App Platform
*Network settings
*Connect AP platform
*App Platform is being installed
*innovaphone PBX options. We used the following options:
**Domain name: cloud.com
**PBX Name: adminpbx
**DNS PBX: adminpbx.cloud.com
**DNS AP: apps.cloud.com
*Save passwords
*E-mail account
*Apps are installed
*PBX and AP Certificates
*Test mode
*Done!!!

==Configuration of customer PBXs==

Every customer receives his own PBX

''' Add domain to devices'''

Open devices in your admin PBX (adminpbx.cloud.com).

Add Customer Domain (company01.com).

Choose a password. This password will be used for devices. If you select "Deploy the domain password on all devices" than it will be used as admin password as well.

[[Image:AddDomain.png]]

'''Setup PBX'''

Setup another machine (e.g. IPVA) and choose "Do manual configuration" or "Update and network settings only"
*Set pbx settings. We used the following options:
**System name: company01.com
**PBX name: pbx
**DNS PBX: pbx.company01.com
*Use as Domain
*Set PBX password
*Create config template "Config Admin". Add Apps to template.
*Create admin user and add template to user

'''Connect PBX to devices'''

Insert Device Registration URL

[[Image:DeviceRegistration.png]]

'''Edit device settings'''

Open devices on your adminpbx.
The MAC address of your new device is shown.
Choose Name and Domain.

[[Image:EditDeviceEntry.png]]

'''Create new category and assign it to device'''

[[Image:AddCategory.png]]

[[Image:AssignCategory.png]]

'''Change main page to myApps'''

Till now, inserting the DNS of PBX shows Advanced GUI.
To change this insert the following commands:
*!config change HTTP0 /home PBX0/APPCLIENT/appclient.htm
*!config write
*!config activate

[[Image:ConfigChangeHTTP0.png]]

''' Connect new PBX to Application Platform'''

Login to your new PBX, using HTTPS! (e.g. pbx.company01.com)
Open PBX Manager
Connect App Platform

Use Host of your AP Platform.

[[Image:ConnectAP.png]]

[[Image:ConnectAP2.png]]

Now you can see in your Apps App that the Domain is registered:

[[Image:RegisteredAccessDomain.png]]

Verify received eMail and check that App Platform is connected.

'''Create Devices & Devices Api Object'''

*Create both App objects on your adminPBX via Device/Advanced GUI.
**First Object "Devices"''
***Long Name: Devices
***Name: devices
***Critical activated
***Hide from LDAP activated
***Example URL: https://apps.cloud.com/cloud.com/devices/innovaphone-devices
***Websocket activated
***Password has to be the same as you choosed when "adding your Domain to Devices"

**Second Object "Devices Api**
***Long Name: DevicesApi
***Name: devices-api
***Critical activated
***Hide from LDAP activated
***Example URL: https://apps.cloud.com/cloud.com/devices/innovaphone-devices-api
***Websocket activated
***Password has to be the same as you choosed when "adding your Domain to Devices"

[[Image:CreateApps.png]]

Both apps have to be connected.

''' Open devices on your new PBX'''
*Open new myApps and choose Devices for your home screen

== Create instances of needed App services ==
Create
*for every customer
*for every needed app
*a new app service instance

More information can be find here: [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_13_Design_of_the_Application_Platform#Installing_an_App| Installing an App]

== Related Articles ==
* [[Reference13r1:Concept_App_Platform]]
* [[Howto:V13_Install_many_APs_for_many_customers]]

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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:58:06Z

She: /* The Idea */

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

This description is to simplify the installation of "one PBX and one Application Platform per customer" that can be used for Cloud setups

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the hosting platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

If you set up a Hosting scenario, please check our [http://wiki.innovaphone.com/index.php?title=Howto:V13_Hosting Considerations]

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Image:CloudSetup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:57:04Z

She: /* The Idea */

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:55:49Z

She: /* Install customer PBX and AP */

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Image:CloudSetup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:55:24Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Image:CloudSetup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.


If you set up a Hosting scenario, please check our [http://wiki.innovaphone.com/index.php?title=Howto:V13_Hosting Considerations]
[[Category:Howto|{{PAGENAME}}]]

Howto13r1:Hosting

2019-08-21T08:53:05Z

She: New page: __toc__  Before starting your v13 Installation you have to check the customer network and his requirements first. ==Ap...

__toc__


Before starting your v13 Installation you have to check the customer network and his requirements first.

==Applies To==
This information applies to

* v13

'''This article is under construction'''

== Considerations ==

* Decision of amount of Application platforms in conjunctions with PBXs.There you find the options and manuals to set it up [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#Relationship_between_app_instances_and_app_objects_in_the_PBX Relationship between app instances and app objects in the PBX]
* Upgrade, new Installation or Parallel Installation. If you want to Upgrade than please test it before and read this article [http://wiki.innovaphone.com/index.php?title=Howto:V13_Firmware_Upgrade_V12r2_V13r1 Upgrade]
* Decision of Internet Access Scenario and Firewall settings [http://wiki.innovaphone.com/index.php?title=Course12:Advanced_-_Reverse_Proxy#Internet_Access_Scenarios Internet Access Scenarios]
* Decision of internal DNS / Installation Scenarios [http://wiki.innovaphone.com/index.php?title=Howto:V13_Installation_Scenarios Installation Scenarios]
* Decision of DHCP or fixed IPs [http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Platform#App_Platform_-_x86-64_.28Virtual_Machine.29 App Platform]
* Creating external DNS names (for every customer PBX, App Platform or adminpbx)
* Certificates
* Use Setup-Data.xls from Training [http://wiki.innovaphone.com/index.php?title=Course13:IT_Connect_-_02_Lesson_on_Setting_up_the_basic_System Setup Data]

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:51:41Z

She: /* Applies To */

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Image:CloudSetup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

File:CloudSetup.png

2019-08-21T08:51:16Z

She:

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:51:06Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13sr4 and up



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Image:CloudSetup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:35:59Z

She: /* Applies To */

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13sr4 and up



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:30:32Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:29:59Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:29:40Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

=Setup of Admin Devices=
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

=Create your first cusomter PBX=
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:29:15Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

=Initial Set-Up=

==of the IPVA==

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

==of the AP==
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

=Create a Prototype / Template =

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

==Setup of Admin Devices==
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

==Create your first cusomter PBX==
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:27:50Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

==Initial Set-Up==

===a) of the IPVA===

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

===b) of the AP===
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

==Create a Prototype / Template ==

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

==Setup of Admin Devices==
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

==Create your first cusomter PBX==
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:27:32Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

==Initial Set-Up==

===a) of the IPVA===

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

===b) of the AP===
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

==Create a Prototype / Template ==

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

==Setup of Admin Devices==
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

==Create your first cusomter PBX==
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:27:15Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 

=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

==Initial Set-Up==

===a) of the IPVA===

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

===b) of the AP===
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

==Create a Prototype / Template ==

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

==Setup of Admin Devices==
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

==Create your first cusomter PBX==
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:26:55Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype/template (1 x IPVA; 1 x AP)
* finalising the set-up of admin devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes/templates
* copying the prototypes to a customer system

==Configuration we used in the setup==
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 
=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

==Initial Set-Up==

===a) of the IPVA===

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

===b) of the AP===
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

==Create a Prototype / Template ==

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

==Setup of Admin Devices==
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

==Create your first cusomter PBX==
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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

Howto13r1:Hosting - Dedicated AP for every customer

2019-08-21T08:25:19Z

She:

{{FIXME|reason=This article is still work in progress and the documentation has to be finished}}

==Applies To==
This information applies to

* V13



=The Idea=

In this article we describe a setup "one PBX and one Application Platform per customer"

This description is to simplify the installation of a cloud environment in single steps.

* Starting with the download of the images from our store,
* doing a set-up, based on the environment of the cloud platform
* copy a prototype (1 x IPVA; 1 x AP)
* finalising the set-up of central devices (central Devices App, Revers Proxy, NAT)
* finalising the configuration of prototypes
* copying the prototypes to a customer system

=Configuration we used in the setup=
In the example we use the following options: 
'''It is important to use a Subdomain, to be able to create later on for every customer their own DNS 00001.cloud.de and insert it to your Devices App.''' 
Domain: admin.cloud.de 
DNS PBX: admin-pbx.cloud.de 
DNS AP: admin-apps.cloud.de 
Folder: 00-AP and 00-IPVA 

For the first customer: 
Domain: 00001.cloud.de 
DNS PBX: 00001-pbx.cloud.de 
DNS AP: 00001-apps.cloud.de 
Folder: 01-AP and 01-IPVA 
=Download respective images=

Select in the [https://store.innovaphone.com/release/download.htm innovaphone store]

* Firmware / IPVA
* App Platform / App Platform x86_64
* Download Package

=Install images on virtualisation platform=
Installation of the above images on the virtualisation platform.

For example:

* on vmWare, use the files with extensions *.ovf (vSphere Client > file > deploy OVF template ....)
** Network Configuration of IPVA thru vmware console [https://wiki.innovaphone.com/index.php?title=Reference12r1:Concept_Innovaphone_Virtual_Appliance#What_Is_The_Console_Good_For.3F Reference12r1:Concept Innovaphone Virtual Appliance]

* on Hyper-V, use the files with extensions *.vhd (Hyper-V Manager > ....) 

==Initial Set-Up==

===a) of the IPVA===

In order to run the IPVA we suggest the following configuration, which has to be done manually via the PBX console: 
This IP address should be available and not in use by anything else!

[[login: admin / ipva]]
* config change DHCP0 /mode off * config show DHCP0 * config change IP0 ETH0 /addr 172.99.1.1 /mask 255.255.0.0 /dns 1.1.1.1 /dns2 1.0.0.1 * config show IP0 ETH0 * config change IP0 RT0 /gateway 172.99.0.1 * config show IP0 RT0 * config change NTP0 /addr 172.99.0.1 /alt-addr 172.99.0.2 /interval 60 * config show NTP0 * config change SYSCLIENT /sysadmin ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients * config write * reset

===b) of the AP===
Configuration via console of the respective virtual platform client:

[[login: root / iplinux]]
* loadkeys de * setip --addr=172.99.1.10 --mask=255.255.0.0 --dns1=1.1.1.1--dns2=1.0.0.1 --gateway=172.99.0.1 * ifconfig * exit

Connect to Application Platform and insert to Settings > Devices app URL

ws://admin-apps.cloud.de/admin.cloud.de/devices/sysclients

'''Create prototype/template before you run through the Installer!''' 

==Create a Prototype / Template ==

This prototype will serve in a later stage as a pair of devices, to produce a preconfigured customer setup. The customer then, runs the installer on this copy, to finalize the own installation.
* Copy 00-IPVA --> IPVA Template
* copy 00-AP --> AP Template

==Setup of Admin Devices==
* Set another fix IP for your IPVA and AP (not the one you already used for the prototype)
* Delete sysclient Info in Devices and AP.
* Click through Installer of IPVA (as learned in the training)
* During Install process connect to Application Platform

==Create your first cusomter PBX==
*Connect to your devices
*Add customer domain and password (pwd)
*Don't choose the flag "Deploy the domain password on all devices" (Noch mal überprüfen!)
*Rename new PBX and new AP
*Insert IP for IPVA via Advanced GUI
*Insert new IP for AP via console

==Install customer PBX and AP==
Insert the following line into your browser: (adjusted to your needs)

http://00001-pbx.cloud.de/install.htm?domain=00001.cloud.de&apaddr=172.16.115.46&apdns=00001-apps.cloud.de&pbxloc=master&location=master

Click through Installer.

[[Bild:Cloud Setup.png]]

'''Be sure to use this URL!''' If you don't use this URL and use our normal Installer than your new installed IPVA, AP will not have any Devices App due to the already set sysclient.
This is on purpose for other scenarios.



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