Br: New page: __toc__ =Applies To= This information applies to * Howto activate the Automatic iSC Reloading Service (so called Auto-iSC) * myApps Cloud v13 Through this service, it is possible to in...

__toc__

=Applies To=
This information applies to
* Howto activate the Automatic iSC Reloading Service (so called Auto-iSC)
* myApps Cloud v13

Through this service, it is possible to instruct innovaphone to automatically reload your iSC balance, to ensure that always enough iSC are available.
* The service itself is free of charge.

== Precondition ==
[[Image: Auto-iSC_00.png|thumb|upright=1.0|right|Precondition]]An Auto-iSC contract can be created after
* a hardware- or software rental-contract (or a cloud-contract) was successfully added and accepted by innovaphone and
* one month worth of iSC was manually placed onto the balance and activated.

== Activating the Automatic iSC Reloading Service ==
[[Image: Auto-iSC_01.png|thumb|upright=1.0|right|Activating]]In the portal my.innovaphone.com click on “Add contract” and
Select Automatic iSC Reloading Service

== Select Domain (Software rental domain or Cloud Instance) ==
[[Image: Auto-iSC_02.png|thumb|upright=1.0|right|Select Domain]]A small windows shows the available software rental contracts and domain names.
Select the domain name, for witch you would like to activate iSC Reloading Service and press continue.

== General information ==
[[Image: Auto-iSC_03.png|thumb|upright=1.0|right|Information]]This page give a rough description on the iSC Reloading Service.
Please press continue.

== Select the Reloading Service Timing ==
[[Image: Auto-iSC_04.png|thumb|upright=1.0|right|Timing]]Here you can specify the threshold, after which the mechanism will activate. Selecting e.g. 2 weeks (or 4 weeks) will initiate the reloading process 2 weeks (or 4 weeks) before the iSC balance does expire. If the available balance is lower then 2 weeks, the reloading process will be initiated anyway.

== Specify the amount of iSC to be reloaded ==
[[Image: Auto-iSC_05.png|thumb|upright=1.0|right|amount of iSC]]This page allows to select how many iSCs will be credited to your balance. Depending on the consumption of the system, innovaphone will calculate the average monthly consumption of iSCs. You can select for how many months in advance you want innovaphone to reload your account with iSCs.
Select the amount of months and press continue.

== Define the Term of the Automatic iSC Reloading Service ==
[[Image: Auto-iSC_06.png|thumb|upright=1.0|right|Term]]The Reloading Service is agreed for an indefinite term. You can terminate your order for this service at any time with immediate effect. Alternatively, you can specify an end date.
Please note: After the end of the Reloading Service, you will be responsible for ensuring manually that you always have sufficient iSC credit to use the rental items. If the iSC Balance does not suffice, it is not permitted and temporarily not possible to use the rental items (in particular emergency calls are not possible).

== Invoicing Partner ==
[[Image: Auto-iSC_07.png|thumb|upright=1.0|right|Invoicing Partner]]In order to carry out the purchase of iSCs on your behalf, through our partner network, we need information on your designated authorized innovaphone partner through whom you purchase innovaphone products and services.
* In case this form is filled by an end customer, the responsible authorized reseller is to be named.
* In case an authorised reseller is filling out this form, the corresponding distributor is to be named.

== Special Notes on the innovaphone iSC Reloading Service ==
[[Image: Auto-iSC_08.png|thumb|upright=1.0|right|Special Notes]]Carefully read and confirm the special notes for this service.

== Finalizing the Order for Automatic iSCs Reloading ==
[[Image: Auto-iSC_09.png|thumb|upright=1.0|right|Finalizing]]Carefully read and confirm the conditions for the offer to conclude the underlying contract. innovaphone will need to accept this contract. Typically this may take one working day.

== Activation ==
[[Image: Auto-iSC_10.png|thumb|upright=1.0|right|Activation]]The process is activated, as soon as accepted by innovaphone.
It may be cancelled at any time, through the portal my.innovaphone.com.

Howto:MyApps Cloud - connecting 2N-Intercom

2021-06-11T10:19:55Z

Br:

__toc__

=Applies To=
This information applies to
* Howto connect a 2N Intercom device to a myApps Cloud PBX
* myApps Cloud v13

==The article describes how to configure a 2N Intercom to register and connect to a myApps Cloud PBX==
For a better overview, the necessary configuration is divided in 2 parts:
* The first part covers the respective PBX object
* The second part describes the configuration of the 2N Intercom device.

==Disclaimer==
2N is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the 2N firmware itself, or malfunction caused through or due to changes in the 2N firmware.

== Considerations for this example configuration==
The parameters below are innovaphone default settings. These settings might be different in the specific cloud environment. Thus, please check your documentation and take a note of the corresponding parameters of your specific cloud instance.
* 2N does not deploy device certificates on its devices. Thus, secure TLS connections to the myApps Cloud platform are not possible. Due to this reason, this example uses a connection via SIP/TCP.
* The system name (devices domain name) of the PBX in this example is: company25.org
* The URL or the respective PBX in this example is: 01234-pbx.innovaphone.com

== Part 1 - Configuration on the myApps Cloud PBX ==

=== Step 1 - Setting of the PBX User Object ===
[[Image: inno-PBX-object_01.png|thumb|upright=1.0|right|Part 1, Step 1]]
* Open the PBX User Object, of the respective 2N Intercom User
* Define a secure password
* In the section Devices, please fill the fields as following:
** TLS only: 'off'
** Reverse Proxy: 'on'
** Media Relay: 'on'

== Part 2 - Configuration of the 2N Intercom ==
[[Image: 2N-IP-Intercom_01a.png|thumb|upright=1.0|right|Part 2, Step 1a]]
* Prior to proceed with the configuration of the 2N device, please make sure the device contains the most recent Firmware.

=== Step 1 - Tab: Services > Phone ===
<ol type="a">
<li> The basic SIP parameters to register on the PBX</li>
* Phone Number (ID): the PBX extension of the Intercom
* Domain: The system name (devices domain name) of the PBX
* Authentication ID: The name of the user object in the PBX
* Password: The name of the password, defined in the respective user object
* Proxy Address: The URL of the PBX [[Image: 2N-IP-Intercom_01b.png|thumb|upright=1.0|right|Part 2, Step 1b]]

<li> In the following, lets SIP Registrar</li>
* Registration Enabled: 'on'
* Registrar Address: The URL of the PBX
* Registration State: 'REGISTERED' should appear, as soon as the Intercom device successfully registered on the PBX

[[Image: 2N-IP-Intercom_01c.png|thumb|upright=1.0|right|Part 2, Step 1c]] <li>Configure the Intercom's public IP address</li>
* External IP Address: Public IP address, through which the device is reachable.
* - CLARIFICATION -
** As 2N Intercom devices do no support STUN, the device itself does not know the public IP address, through which it is reachable. Consequently, to make VoIP communication possible, this address has to be configured on the device.
** Please make sure, the entered IP address is a fixed, an not a dynamic IP address.
</ol>

[[Image: 2N-IP-Intercom_02.png|thumb|upright=1.0|right|Part 2, Step 2]]
=== Step 2 - Tab: Directory > Users ===
The Users list contains user information, relevant for the quick dialing.
* Register Username and extension number, of the person who shall answer the Intercom.

[[Image: 2N-IP-Intercom_03.png|thumb|upright=1.0|right|Part 2, Step 3]]
=== Step 3 - Tab: Hardware > Buttons ===
* Here you have to assign the previously defined user to the Intercoms quick dial buttons.
* Skipping this step, the Intercom will not dial the PBX.

== Part 3 - Testing ==
* Initiate a Test Call to verify your configuration...

File:Inno-PBX-object 01.png

2021-06-11T10:09:01Z

Br:

Howto:MyApps Cloud - connecting 2N-Intercom

2021-06-10T16:31:11Z

Br:

__toc__

= ++++ Document is in creation process ++++ =

=Applies To=
This information applies to
* Howto connect a 2N Intercom device to a myApps Cloud PBX
* myApps Cloud v13

==The article describes how to configure a 2N Intercom to register and connect to a myApps Cloud PBX==
For a better overview, the necessary configuration is divided in 2 parts:
* The first part covers the respective PBX object
* The second part describes the configuration of the 2N Intercom device.

==Disclaimer==
2N is a 3rd party brand. As such, innovaphone is not liable for any malfunction of the 2N firmware itself, or malfunction caused through or due to changes in the 2N firmware.

== Considerations for this example configuration==
The parameters below are innovaphone default settings. These settings might be different in the specific cloud environment. Thus, please check your documentation and take a note of the corresponding parameters of your specific cloud instance.
* 2N does not deploy device certificates on its devices. Thus, secure TLS connections to the myApps Cloud platform are not possible. Due to this reason, this example uses a connection via SIP/TCP.
* The system name (devices domain name) of the PBX in this example is: company25.org
* The URL or the respective PBX in this example is: 01234-pbx.innovaphone.com

== Part 1 - Configuration on the myApps Cloud PBX ==

=== Step 1 - Setting of the PBX User Object ===
* Open the PBX User Object, of the respective 2N Intercom User
* Define a secure password
* In the section Devices, please fill the fields as following:
** TLS only: 'off'
** Reverse Proxy: 'on'
** Media Relay: 'on'

== Part 2 - Configuration of the 2N Intercom ==
[[Image: 2N-IP-Intercom_01a.png|thumb|upright=1.0|right|Part 2, Step 1a]]
* Prior to proceed with the configuration of the 2N device, please make sure the device contains the most recent Firmware.

=== Step 1 - Tab: Services > Phone ===
<ol type="a">
<li> The basic SIP parameters to register on the PBX</li>
* Phone Number (ID): the PBX extension of the Intercom
* Domain: The system name (devices domain name) of the PBX
* Authentication ID: The name of the user object in the PBX
* Password: The name of the password, defined in the respective user object
* Proxy Address: The URL of the PBX [[Image: 2N-IP-Intercom_01b.png|thumb|upright=1.0|right|Part 2, Step 1b]]

<li> In the following, lets SIP Registrar</li>
* Registration Enabled: 'on'
* Registrar Address: The URL of the PBX
* Registration State: 'REGISTERED' should appear, as soon as the Intercom device successfully registered on the PBX

[[Image: 2N-IP-Intercom_01c.png|thumb|upright=1.0|right|Part 2, Step 1c]] <li>Configure the Intercom's public IP address</li>
* External IP Address: Public IP address, through which the device is reachable.
* - CLARIFICATION -
** As 2N Intercom devices do no support STUN, the device itself does not know the public IP address, through which it is reachable. Consequently, to make VoIP communication possible, this address has to be configured on the device.
** Please make sure, the entered IP address is a fixed, an not a dynamic IP address.
</ol>

[[Image: 2N-IP-Intercom_02.png|thumb|upright=1.0|right|Part 2, Step 2]]
=== Step 2 - Tab: Directory > Users ===
* Register Username and extension number, of the person who shall answer the Intercom.

[[Image: 2N-IP-Intercom_03.png|thumb|upright=1.0|right|Part 2, Step 3]]
=== Step 3 - Tab: Hardware > Buttons ===
* Connect the above defined user to the Intercom's quick dial button.

== Part 3 - Testing ==
* Initiate a Test Call to verify your configuration...

File:2N-IP-Intercom 03.png

2021-06-10T16:22:35Z

Br:

File:2N-IP-Intercom 02.png

2021-06-10T16:20:45Z

Br:

File:2N-IP-Intercom 01c.png

2021-06-10T15:20:30Z

Br:

File:2N-IP-Intercom 01b.png

2021-06-10T15:07:08Z

Br:

File:2N-IP-Intercom 01a.png

2021-06-10T15:02:44Z

Br: