innovaphone wiki - User contributions [en]

Reference9:Concept USB Headset

2012-02-23T17:16:07Z

Pme: /* Supported Headsets */

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

The IP222 and IP232 telephones provide USB ports. This document describes how to install, configure and use USB headsets on these phones.

==Applies To==
This information applies to
* IP222 and IP232
Firmware V9hotfix7 and later.

USB Headset Support is ''in beta as of V9hotfix7'' and should thus not be used in production environments!

==More Information==

===Installation===
Follow the vendor setup directions for using the headset with a PC but connect the USB plug of the headset to an USB slot of the IP2x2 phone.
There is no need to install any vendor provided PC software.

Some headsets are designed to be connected both to a telephone via DHSG, AEI or a similar protocol and to a PC via USB.
In this case you must also set up the headset for use with a PC, sometimes a special keypress is required to fix this setting.

===Configuration===
Although a USB headset is detected automatically when it is connected it needs to be explicitely enabled.
This is required to let the phone know that the headset is really in use and should be served.

Enabling the headset has the following effects:

* a headset icon is displayed in the phone status line
* a normal inbound call is indicated by a ring tone in the headset (if this is supported by the headset)
* an automatically connected inbound call ((announcement, broadcast) is connected to the headset (not to the speaker as usual)
* a call initiated by pressing the ''Redial'' key while browsing a call list or a directory is connected to the headset
* a call initiated by pressing the ''Redial'' in indirect dialling mode is connected to the headset

The headset is enabled at the telephone either by setting "Menu/Phone Setup/Headset: On" or by a ''Headset'' function key with ''Mode: Enable''.
A ''Headset:Enable'' function key is more convenient for example when the headset is used only when the user leaves the telephone.

===Call control===
The IP2x2 telephones don't provide a hardware key to control the headset but if required a ''Headset'' function key with ''Mode: Control'' can be defined to setup/accept calls via headset directly on the telephone.
Headset call control can be performed in different ways:
* by the ''Talk'' key on the headsets base station
* by the ''Talk'' key on the headset itself
* by the ''Headset:Control'' function key
* by the ''Redial'' key (outbound calls only)

By default setting up outbound calls via a ''Talk'' key is disabled to prevent entering offhook state when the user is far from phone.
It can be enabled via the WEB interface by checking "Phone/Preferences/Start Outbound Call on Electronic Hook Switch (EHS) Signal".

For some headsets this is a must because they require that all call control is performed by a ''Talk'' key, otherwise the media connection between base and headset gets lost.

====Outbound Calls====
* enter a number and press ''Redial''
* select an entry in a call list or a directory and press ''Redial''
* press a ''Talk'' key and enter the number (if this function is enabled)
* press the ''Headset:Control'' function key and enter the number

To drop the call press a ''Talk'' key, the ''Disconnect'' key or the ''Headset:Control'' function key.

====Inbound Calls====
To accept an inbound call press a ''Talk'' key or the ''Headset:Control'' function key.
To drop the call press a ''Talk'' key, the ''Disconnect'' or the the ''Headset:Control'' function key.

===Volume control===
Usually the headset provides it's own volume control and this should be preferred.
The phone volume control can be used when the range of the headset volume control is not sufficient.

===Microphone Mute===
Usually the headset provides it's own ''Mute'' button and this should be preferred.



==Known Problems==
Monitor Mode does not work with USB headsets, i.e. the telephone speaker cannot switched on in addition to the headset.

==Supported Headsets==

{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse"
! align="center" style="background:#f0f0f0;"|''' Manufacturer'''
! align="center" style="background:#f0f0f0;"|'''Model'''
! align="center" style="background:#f0f0f0;"|'''Operation'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
|-
| style="vertical-align:top" rowspan="13" | GN Netcom / Jabra
| style="vertical-align:top" rowspan="5" | '''GN 9350e''' 9356-607-401 5706991007237
| Answer incomming call
| style="vertical-align:top" rowspan="5" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset Base
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Clean Audio Mode (Redial?)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| style="vertical-align:top" rowspan="8" | '''Pro 9470''' 9470-26-904-101 5706991009866
| Answer incomming call
| style="vertical-align:top" rowspan="8" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset Base
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Put current call on hold, and accept incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Reject incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Call last number dialed (mobile phones and supported softphones only)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Mute
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
|}

Reference9:Concept USB Headset

2012-02-23T13:18:33Z

Pme: /* Supported Headsets */

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

The IP222 and IP232 telephones provide USB ports. This document describes how to install, configure and use USB headsets on these phones.

==Applies To==
This information applies to
* IP222 and IP232
Firmware V9hotfix7 and later.

USB Headset Support is ''in beta as of V9hotfix7'' and should thus not be used in production environments!

==More Information==

===Installation===
Follow the vendor setup directions for using the headset with a PC but connect the USB plug of the headset to an USB slot of the IP2x2 phone.
There is no need to install any vendor provided PC software.

Some headsets are designed to be connected both to a telephone via DHSG, AEI or a similar protocol and to a PC via USB.
In this case you must also set up the headset for use with a PC, sometimes a special keypress is required to fix this setting.

===Configuration===
Although a USB headset is detected automatically when it is connected it needs to be explicitely enabled.
This is required to let the phone know that the headset is really in use and should be served.

Enabling the headset has the following effects:

* a headset icon is displayed in the phone status line
* a normal inbound call is indicated by a ring tone in the headset (if this is supported by the headset)
* an automatically connected inbound call ((announcement, broadcast) is connected to the headset (not to the speaker as usual)
* a call initiated by pressing the ''Redial'' key while browsing a call list or a directory is connected to the headset
* a call initiated by pressing the ''Redial'' in indirect dialling mode is connected to the headset

The headset is enabled at the telephone either by setting "Menu/Phone Setup/Headset: On" or by a ''Headset'' function key with ''Mode: Enable''.
A ''Headset:Enable'' function key is more convenient for example when the headset is used only when the user leaves the telephone.

===Call control===
The IP2x2 telephones don't provide a hardware key to control the headset but if required a ''Headset'' function key with ''Mode: Control'' can be defined to setup/accept calls via headset directly on the telephone.
Headset call control can be performed in different ways:
* by the ''Talk'' key on the headsets base station
* by the ''Talk'' key on the headset itself
* by the ''Headset:Control'' function key
* by the ''Redial'' key (outbound calls only)

By default setting up outbound calls via a ''Talk'' key is disabled to prevent entering offhook state when the user is far from phone.
It can be enabled via the WEB interface by checking "Phone/Preferences/Start Outbound Call on Electronic Hook Switch (EHS) Signal".

For some headsets this is a must because they require that all call control is performed by a ''Talk'' key, otherwise the media connection between base and headset gets lost.

====Outbound Calls====
* enter a number and press ''Redial''
* select an entry in a call list or a directory and press ''Redial''
* press a ''Talk'' key and enter the number (if this function is enabled)
* press the ''Headset:Control'' function key and enter the number

To drop the call press a ''Talk'' key, the ''Disconnect'' key or the ''Headset:Control'' function key.

====Inbound Calls====
To accept an inbound call press a ''Talk'' key or the ''Headset:Control'' function key.
To drop the call press a ''Talk'' key, the ''Disconnect'' or the the ''Headset:Control'' function key.

===Volume control===
Usually the headset provides it's own volume control and this should be preferred.
The phone volume control can be used when the range of the headset volume control is not sufficient.

===Microphone Mute===
Usually the headset provides it's own ''Mute'' button and this should be preferred.



==Known Problems==
Monitor Mode does not work with USB headsets, i.e. the telephone speaker cannot switched on in addition to the headset.

==Supported Headsets==

{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse"
! align="center" style="background:#f0f0f0;"|''' Manufacturer'''
! align="center" style="background:#f0f0f0;"|'''Model'''
! align="center" style="background:#f0f0f0;"|'''Operation'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
|-
| style="vertical-align:top" rowspan="13" | GN Netcom / Jabra
| style="vertical-align:top" rowspan="5" | GN 9350e
| Answer incomming call
| style="vertical-align:top" rowspan="5" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset Base
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Clean Audio Mode (Redial?)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| style="vertical-align:top" rowspan="8" | Pro 9470
| Answer incomming call
| style="vertical-align:top" rowspan="8" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset Base
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Put current call on hold, and accept incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Reject incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Call last number dialed (mobile phones and supported softphones only)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Mute
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
|}

Reference9:Concept USB Headset

2012-02-23T11:14:18Z

Pme: /* Supported Headsets */

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

The IP222 and IP232 telephones provide USB ports. This document describes how to install, configure and use USB headsets on these phones.

==Applies To==
This information applies to
* IP222 and IP232
Firmware V9hotfix7 and later.

USB Headset Support is ''in beta as of V9hotfix7'' and should thus not be used in production environments!

==More Information==

===Installation===
Follow the vendor setup directions for using the headset with a PC but connect the USB plug of the headset to an USB slot of the IP2x2 phone.
There is no need to install any vendor provided PC software.

Some headsets are designed to be connected both to a telephone via DHSG, AEI or a similar protocol and to a PC via USB.
In this case you must also set up the headset for use with a PC, sometimes a special keypress is required to fix this setting.

===Configuration===
Although a USB headset is detected automatically when it is connected it needs to be explicitely enabled.
This is required to let the phone know that the headset is really in use and should be served.

Enabling the headset has the following effects:

* a headset icon is displayed in the phone status line
* a normal inbound call is indicated by a ring tone in the headset (if this is supported by the headset)
* an automatically connected inbound call ((announcement, broadcast) is connected to the headset (not to the speaker as usual)
* a call initiated by pressing the ''Redial'' key while browsing a call list or a directory is connected to the headset
* a call initiated by pressing the ''Redial'' in indirect dialling mode is connected to the headset

The headset is enabled at the telephone either by setting "Menu/Phone Setup/Headset: On" or by a ''Headset'' function key with ''Mode: Enable''.
A ''Headset:Enable'' function key is more convenient for example when the headset is used only when the user leaves the telephone.

===Call control===
The IP2x2 telephones don't provide a hardware key to control the headset but if required a ''Headset'' function key with ''Mode: Control'' can be defined to setup/accept calls via headset directly on the telephone.
Headset call control can be performed in different ways:
* by the ''Talk'' key on the headsets base station
* by the ''Talk'' key on the headset itself
* by the ''Headset:Control'' function key
* by the ''Redial'' key (outbound calls only)

By default setting up outbound calls via a ''Talk'' key is disabled to prevent entering offhook state when the user is far from phone.
It can be enabled via the WEB interface by checking "Phone/Preferences/Start Outbound Call on Electronic Hook Switch (EHS) Signal".

For some headsets this is a must because they require that all call control is performed by a ''Talk'' key, otherwise the media connection between base and headset gets lost.

====Outbound Calls====
* enter a number and press ''Redial''
* select an entry in a call list or a directory and press ''Redial''
* press a ''Talk'' key and enter the number (if this function is enabled)
* press the ''Headset:Control'' function key and enter the number

To drop the call press a ''Talk'' key, the ''Disconnect'' key or the ''Headset:Control'' function key.

====Inbound Calls====
To accept an inbound call press a ''Talk'' key or the ''Headset:Control'' function key.
To drop the call press a ''Talk'' key, the ''Disconnect'' or the the ''Headset:Control'' function key.

===Volume control===
Usually the headset provides it's own volume control and this should be preferred.
The phone volume control can be used when the range of the headset volume control is not sufficient.

===Microphone Mute===
Usually the headset provides it's own ''Mute'' button and this should be preferred.



==Known Problems==
Monitor Mode does not work with USB headsets, i.e. the telephone speaker cannot switched on in addition to the headset.

==Supported Headsets==

{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse"
! align="center" style="background:#f0f0f0;"|''' Manufacturer'''
! align="center" style="background:#f0f0f0;"|'''Model'''
! align="center" style="background:#f0f0f0;"|'''Operation'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
|-
| style="vertical-align:top" rowspan="13" | GN Netcom / Jabra
| style="vertical-align:top" rowspan="5" | GN 9350e
| Answer incomming call
| style="vertical-align:top" rowspan="5" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset Base
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Clean Audio Mode (Redial?)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| style="vertical-align:top" rowspan="8" | Pro 9470
| Answer incomming call
| style="vertical-align:top" rowspan="8" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset Base
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Put current call on hold, and accept incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Reject incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Call last number dialed (mobile phones and supported softphones only)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Mute
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
|}

Currently, the IP2x2 present themselves to the headset like a PC. ''Dual mode'' headsets (that is, headsets which distinguish between "phone calls" and "pc sound") may get confused and behave strange. It is therefore currently not recommended to try to use those.

===Jabra BIZ 620 USB===
call control can be performed in any way

===Jabra SPEAK 410 USB (Mono/Stereo), Jabra BIZ 2400 USB (Mono/Stereo)===
call control can be performed in any way

Reference9:Concept USB Headset

2012-02-23T11:11:46Z

Pme: /* Supported Headsets */

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

The IP222 and IP232 telephones provide USB ports. This document describes how to install, configure and use USB headsets on these phones.

==Applies To==
This information applies to
* IP222 and IP232
Firmware V9hotfix7 and later.

USB Headset Support is ''in beta as of V9hotfix7'' and should thus not be used in production environments!

==More Information==

===Installation===
Follow the vendor setup directions for using the headset with a PC but connect the USB plug of the headset to an USB slot of the IP2x2 phone.
There is no need to install any vendor provided PC software.

Some headsets are designed to be connected both to a telephone via DHSG, AEI or a similar protocol and to a PC via USB.
In this case you must also set up the headset for use with a PC, sometimes a special keypress is required to fix this setting.

===Configuration===
Although a USB headset is detected automatically when it is connected it needs to be explicitely enabled.
This is required to let the phone know that the headset is really in use and should be served.

Enabling the headset has the following effects:

* a headset icon is displayed in the phone status line
* a normal inbound call is indicated by a ring tone in the headset (if this is supported by the headset)
* an automatically connected inbound call ((announcement, broadcast) is connected to the headset (not to the speaker as usual)
* a call initiated by pressing the ''Redial'' key while browsing a call list or a directory is connected to the headset
* a call initiated by pressing the ''Redial'' in indirect dialling mode is connected to the headset

The headset is enabled at the telephone either by setting "Menu/Phone Setup/Headset: On" or by a ''Headset'' function key with ''Mode: Enable''.
A ''Headset:Enable'' function key is more convenient for example when the headset is used only when the user leaves the telephone.

===Call control===
The IP2x2 telephones don't provide a hardware key to control the headset but if required a ''Headset'' function key with ''Mode: Control'' can be defined to setup/accept calls via headset directly on the telephone.
Headset call control can be performed in different ways:
* by the ''Talk'' key on the headsets base station
* by the ''Talk'' key on the headset itself
* by the ''Headset:Control'' function key
* by the ''Redial'' key (outbound calls only)

By default setting up outbound calls via a ''Talk'' key is disabled to prevent entering offhook state when the user is far from phone.
It can be enabled via the WEB interface by checking "Phone/Preferences/Start Outbound Call on Electronic Hook Switch (EHS) Signal".

For some headsets this is a must because they require that all call control is performed by a ''Talk'' key, otherwise the media connection between base and headset gets lost.

====Outbound Calls====
* enter a number and press ''Redial''
* select an entry in a call list or a directory and press ''Redial''
* press a ''Talk'' key and enter the number (if this function is enabled)
* press the ''Headset:Control'' function key and enter the number

To drop the call press a ''Talk'' key, the ''Disconnect'' key or the ''Headset:Control'' function key.

====Inbound Calls====
To accept an inbound call press a ''Talk'' key or the ''Headset:Control'' function key.
To drop the call press a ''Talk'' key, the ''Disconnect'' or the the ''Headset:Control'' function key.

===Volume control===
Usually the headset provides it's own volume control and this should be preferred.
The phone volume control can be used when the range of the headset volume control is not sufficient.

===Microphone Mute===
Usually the headset provides it's own ''Mute'' button and this should be preferred.



==Known Problems==
Monitor Mode does not work with USB headsets, i.e. the telephone speaker cannot switched on in addition to the headset.

==Supported Headsets==

{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse"
! align="center" style="background:#f0f0f0;"|''' Manufacturer'''
! align="center" style="background:#f0f0f0;"|'''Model'''
! align="center" style="background:#f0f0f0;"|'''Operation'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
! align="center" style="background:#f0f0f0;"|'''Control'''
! align="center" style="background:#f0f0f0;"|'''USB'''
! align="center" style="background:#f0f0f0;"|'''Jabra Link 14201-30'''
|-
| style="vertical-align:top" rowspan="13" | GN Netcom / Jabra
| style="vertical-align:top" rowspan="5" | GN 9350e
| Answer incomming call
| style="vertical-align:top" rowspan="5" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="5" | Headset Base
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
|-
| Clean Audio Mode (Redial?)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| style="vertical-align:top" rowspan="8" | Pro 9470
| Answer incomming call
| style="vertical-align:top" rowspan="8" | Phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="vertical-align:top" rowspan="8" | Headset Base
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| End current call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Put current call on hold, and accept incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Open phone line on target phone
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Reject incoming call
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Call last number dialed (mobile phones and supported softphones only)
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Volume
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
| Mute
| style="text-align:center" | No
| style="text-align:center" | not tested
| style="text-align:center" | Yes
| style="text-align:center" | not tested
| style="text-align:center" | No
| style="text-align:center" | not tested
|-
|}

Reference9:Concept Innovaphone Virtual Appliance (IPVA)

2012-02-07T13:54:55Z

Pme: /* Can The Emulated CompactFlash Be Increased In Size? */

[[Category:Concept9|{{PAGENAME}}]]
==Applies To==
This information applies to:
*V9
*innovaphone Virtual Appliance
*Intel/AMD CPUs
*VMware
**Workstation 7.1
**Player 3.x <ref>VMware Player Download(free): http://vmware.com/download/player/</ref>
**vSphere 4.1
**vSphere 5.x (see [[#V9HF4_Needed_For_vSphere_5 | V9HF4 Needed For vSphere 5]])

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.
Whereby, VMware<ref>http://www.vmware.com</ref> is is the solely supported virtualization platform to-date.

The IPVA is a software-only solution. It appears as and performs as an innovaphone "hard-box" excluding DSP-, ISDN-/AB-resources.

The following core-components are contained within the IPVA:
*innovaphone PBX
*innovaphone Gateway (a.k.a ''Relay'')
*integrated mass-storage (alike innovaphones' CF-card support)


==Configuration==
[[#Download|Download]] the IPVA.

*The compressed archive ''ipva-vmx.zip'' contains 1 virtual machine configuration file (*.vmx) and 4 virtual machine disk files (*.vmdk):
**ipva.vmx: The virtual machine configuration file
**hd-boot.vmdk: The virtual boot harddisk (hd)
**hd-cf.vmdk: The hd for emulation of a Compact Flash card
**hd-flash.vmdk: The hd for emulation of flash memory
**hd-dump.vmdk: The hd serving as a store for a crash dump

The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

===VMware Player===
*Copy the IPVA to e.g. your desktop
*Double-click on ipva.vmx
The IPVA is going to be started.

A shortcut (*.lnk file) to the vmx-file will start the IPVA without additional user interaction. Such a shortcut may also be copied into the Windows ''Autostart'' program folder, in order to have the IPVA started automatically on windows startup.
===VMware Workstation===
*Copy the IPVA to e.g. your desktop
*Double-click on ipva.vmx
The IPVA is going to be started.

The ''Workstation 7'' directory comprises the command line utility ''vmrun.exe''. A batch file according to the following pattern may be crafted to programmatically start the IPVA.
<pre>
"D:\Programme\VMware\VMware Workstation\vmrun" start "C:\Users\Tester\Desktop\ipva\ipva.vmx"
</pre>
'''Note''': By altering ''start'' into ''stop'' a virtual machine may be stopped.
===VMware vSphere 4.x===
The IPVA offered for downloading must be converted into a vSphere-processable form.
The IPVA can be converted by means of the tool ''VMware vCenter Converter Standalone''<ref>VMware vCenter Converter Standalone: https://www.vmware.com/tryvmware/?p=converter</ref>. A step-by-step guide may be found [http://blog.lewan.com/2009/12/22/vmware-vsphere-using-vmware-converter-to-import-vms-or-vmdks-from-other-vmware-products/ here].

'''Note:''' See known issue [[#Don't use Maintenance/Upload/DRAM on vSphere 4|Don't use Maintenance/Upload/DRAM on vSphere 4]].

===Network Configuration===
Manufacturer-configured as DHCP client only. I.e. a DHCP server must be available. Afterwards the network configuration may be administrated as used to within the web ui of other innovaphone boxes. If there's in no case a DHCP server available for the 1st-time configuration, read through [[#What_Is_The_Console_Good_For?|What Is The Console Good For?]].

===License Configuration===
For the IPVA9 license see [[Reference9:Licenses]].

The licensing procedure is the same as for other innovaphone products, except for one peculiarity: The MAC address, generated by VMware, may have been assigned already to another customer/installation. Such a conflict must be settled manually as explained below.

If, while generating licenses within ''my.innovaphone.com'', a message ([[Reference:My_Innovaphone#IP-VA_MAC_exists|My_Innovaphone#IP-VA_MAC_exists]]) is displayed:
<pre>
IP-VA MAC exists
</pre>
then a new MAC address must be assigned manually to the affected installation.

In order to assign a new MAC address:
*Power-off the virtual machine
*Open the file ipva.vmx for editing within a text editor.
*Edit the last 3 hex-values of the lines starting with ''ethernet0.generatedAddress'' & ''uuid.bios'' from e.g.
<pre>
ethernet0.generatedAddress = "00:0c:29:f4:c6:d9"
uuid.bios = "56 4d 64 b9 52 ce 38 57-66 29 e8 f2 77 f4 c6 d9"
</pre>
into e.g
<pre>
ethernet0.generatedAddress = "00:0c:29:f4:c6:da"
uuid.bios = "56 4d 64 b9 52 ce 38 57-66 29 e8 f2 77 f4 c6 da"
</pre>
(Note: in this example just the very last hex-value '''d9''' is going to be altered into '''da''')
*Within my.innovaphone.com try once again to generate licenses for the virtual machine with the new MAC address.

==Provision Of External Resources==
External Resources are required, in order to provide:
*Access to ISDN interfaces
*DSP conferencing channels

The IP1060<ref>[http://www.innovaphone.com/fileadmin/download/newsletter/EINLEGER_IP1060_Produktkatalog2009_2010_DE_ENG.pdf IP1060 Product Information]</ref> media gateway may be considered as a suitable complement for such purposes.
==Download==

[http://download.innovaphone.com/ice/9.00/#firmware IPVA.zip from http://download.innovaphone.com/ice/9.00/#firmware]

==Troubleshooting==
A new option has been added to ''Admistration/Diagnostics/Tracing''. The option ''trace(crash-dump)'' is going to read a post-mortem log from hd-dump.vmdk, if available.
==Known Issues==
===ESX 3.x is unsupported===
The IPVA does not run under ESX 3.x and below, since virtual IDE disks aren't supported.

===Don't use Maintenance/Upload/DRAM on vSphere 4===
Until further notice this way of uploading a new firmware is currently not supported. The VMM detects and assumes the guest (IPVA) is going to shutting-off. All the virtual harddisks may get lost in the aftermath.
vmware.log shows:
<pre>
...

Mar 02 13:02:25.439: vcpu-0| Vix: [4864986 vmxCommands.c:9609]: VMAutomation_HandleCLIHLTEvent. Do nothing.
Mar 02 13:02:25.462: vcpu-0| MsgHint: msg.monitorevent.halt (sent)
Mar 02 13:02:25.462: vcpu-0| The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

...and then when trying to power-on later...

Mar 03 08:37:00.260: vmx| Destroying virtual dev for ide0:1 vscsi=8303
Mar 03 08:37:00.260: vmx| VMMon_VSCSIStopVports: Invalid handle
Mar 03 08:37:00.260: vmx| VMMon_VSCSIDestroyDev: Not found
Mar 03 08:37:00.260: vmx| Destroying virtual dev for ide1:0 vscsi=8304
Mar 03 08:37:00.261: vmx| VMMon_VSCSIStopVports: Invalid handle
Mar 03 08:37:00.261: vmx| VMMon_VSCSIDestroyDev: Not found
...
</pre>

===Release Note For V9HF1===
This Note refers to the fix [[Support:DVL-Roadmap_Firmware_V9#IPVA.2C_RAM-Dependent_Flash_Limitation | Support:DVL-Roadmap Firmware V9#IPVA RAM-Dependent Flash Limitation]]
*From on V9HF1 the available flash directory<ref>Flash Directory: Storage for PBX objects</ref> space will be constrained, depending on the available RAM. A loss of PBX objects may occur after an upgrade to V9HF1. In order to prevent such a loss perform the upgrade as follows:
**1)Download and save the current configuration of the affected IPVA.
**2)Upload the new firmware file and reboot.
**3)Upload the config from step 1).
*From on V9HF1 an administrative reduction of the available RAM may lead into a loss of PBX objects. I.e. increasing the RAM isn't critical, while in contrast lowering the amount of RAM lowers the amount of flash directory space.

===V9HF4 Needed For vSphere 5===
V9 Hotfix4 is needed, in order to run the IPVA under vSphere 5.

==FAQ==
===Are Firmware Updates Possible?===
Yes, alike the well-known *.bin firmware files for other innovaphone products (ip6000.bin, ip2000.bin,..) , there's a similar bin-file (ipva.bin) for the IPVA. The file is contained on the boot-hd and can be found by browsing to e.g. http://192.168.0.5/drive/HD-BOOT . The versioning of ipva.bin is the same as for the other products. The firmware file may exactly be uploaded as for other products:
* by ''Upload/Firmware''
* by ''Upload/Dram''
* by a script for the innovaphone Update Process

===What is the ipva default password?===
*user: admin
*password: ipva

===Do I Always Need To Download The Entire IPVA?===
No, after the 1st-time deployment of an entire IPVA only the firmware file ''ipva.bin'' needs to be downloaded from ''download.innovaphone.com''. See [[#Are_Firmware_Updates_Possible.3F| Are Firmware Updates Possible?]] for how to proceed further.
===How Is The Network Connection Being Handled?===
The network connection is pre-configured to: ''Bridged: Connected directly to the physical network''
===What Is The Size Of the Emulated CompactFlash?===
1GB

===Can The Emulated CompactFlash Be Increased In Size?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated CompactFlash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/Compact-Flash/General)

===What Is The Size Of the emulated Flash Storage on the IPVA?===
The virtual flash storage used to store configuration file of the IPVA and LDAP directory of the PBX is defined with 64 MB and can not be changed. This is two times more than on IP6010. The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===How Much RAM Is Required Per IPVA Instance?===
The downloadable virtual appliance comes preconfigured with 64MB RAM. This amount is seen as a good trade-off for the majority of all installations.
The RAM-size can be administrated by VMware-means.
===How Many IPVA Instances Are Possible Per Host?===
There's no worst-case estimate available. For a best-case calculation,
*see [http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf Configuration Maximums VMware vSphere 4.1]
*see [[#How_Much_RAM_Is_Required_Per_IPVA_Instance.3F | How Much RAM Is Required Per IPVA Instance?]]
===Where Has PPP-Functionality Gone?===
PPP-scenarios (PPTP, PPPoE) are not envisaged with the IPVA, because it has only one network interface controller.

'''Update'''(07.Mar.2011), from on 90468:
*PPP has been integrated
*a second network interface is available (now ETH0 and ETH1)
**ETH1 comes pre-configured: ''host-only, disconnected''. I.e. it must be reconfigured manually and by VMware means to become functional.

===Does The IPVA Support Non-VMware Hypervisor Products?===
No, currently it doesn't.

===How do I perform a factory reset?===

replace the 3rd disk, served on IDE 1:0, named hd-flash.vmdk with an empty disk:

[[Image:VM_Settings.png]]

1)download the IPVA and watch out for the file hd-flash.vmdk

2)Power-off the IPVA instance

3)Replace hd-flash.vmdk with the one downloaded in step 1). If on vsphere it may have been assigned a different name. Ensure it’s the one on IDE 1:0.

4)Power-on the IPVA instance

===Why Does ''General/Info/DRAM'' Show Less Than the Configured Memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===Is VMWare Fault Tolerance (FT) supported by IPVA?===

Yes, we have successfully tested<ref>[[Howto:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance | Howto:Implement PBX with zero downtime using IPVA and VMWare Fault Tolerance]]</ref> VMWare Fault Tolerance<ref>VMWare Fault Tolerance: http://www.vmware.com/products/fault-tolerance/overview.html</ref> with a virtual machine running IPVA on VMWare vSphere 4.1.

===What Is The Console Good For?===
The console is a remains of the early development phase. It resembles the IP3000's serial console. It doesn't offer any convenience like command history or backspace funtionality. Nevertheless may the console be of help in exceptional situations where e.g. the required DHCP server isn't available for 1st-time configuration or in situations where the ip configuration was misconfigured. Thereby any command from a device's config is acceptable.

For instance to configure the static IP address 1.2.3.4/24 on ETH0:
*Click into the console
*Press ENTER
*Enter credentials
*Enter
<pre>
config change IP0 ETH0 /addr 1.2.3.4 /mask 255.255.255.0
config change DHCP0 /mode off
config write
reset
</pre>
Since no backspace is offered it may become a daring task to enter a single line without typos. In case of a typo hit ENTER and input the same line again.
The keyboard layout is the US layout.
[[Image:Ip-via-console.png|center|thumb|200px|Console-edit of IP address]]

Display the IP configuration for ETH0:
<pre>
config show IP0 ETH0
</pre>

Display the DHCP configuration for ETH0:
<pre>
config show DHCP0
</pre>

Additional the DNS-server(s) and the default gateway can be configured:
<pre>
config change IP0 ETH0 /addr 1.2.3.4 /mask 255.255.255.0 /dns 8.8.8.8 /dns2 8.8.4.4
config change IP0 RT0 /gateway 1.2.3.254
config change DHCP0 /mode off
config write
reset
</pre>

Also some simple diagnostics (ping and traceroute) are possible via the console (output is given in the console):
<pre>
mod cmd PING0 tracert 8.8.8.8
mod cmd PING0 ping 8.8.8.8
</pre>

Resetting the entire FLASH space - '''Note, all configuration will get lost'''. this is similar method to the manufacturer reset method from above [[#How_do_I_perform_a_factory_reset.3F|How do I perform a factory reset?]]
<pre>
mod cmd FLASHMAN0 reset all
reset
</pre>

==Notes==
<references/>

==Related Articles==
[[Reference9:Licenses]]

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

Reference9:Concept Innovaphone Virtual Appliance (IPVA)

2012-02-07T13:48:55Z

Pme: /* Can The Emulated CompactFlash Be Increased In Size? */

[[Category:Concept9|{{PAGENAME}}]]
==Applies To==
This information applies to:
*V9
*innovaphone Virtual Appliance
*Intel/AMD CPUs
*VMware
**Workstation 7.1
**Player 3.x <ref>VMware Player Download(free): http://vmware.com/download/player/</ref>
**vSphere 4.1
**vSphere 5.x (see [[#V9HF4_Needed_For_vSphere_5 | V9HF4 Needed For vSphere 5]])

==More Information==
The innovaphone Virtual Appliance (IPVA) is a virtual machine to be run on a virtualization platform.
Whereby, VMware<ref>http://www.vmware.com</ref> is is the solely supported virtualization platform to-date.

The IPVA is a software-only solution. It appears as and performs as an innovaphone "hard-box" excluding DSP-, ISDN-/AB-resources.

The following core-components are contained within the IPVA:
*innovaphone PBX
*innovaphone Gateway (a.k.a ''Relay'')
*integrated mass-storage (alike innovaphones' CF-card support)


==Configuration==
[[#Download|Download]] the IPVA.

*The compressed archive ''ipva-vmx.zip'' contains 1 virtual machine configuration file (*.vmx) and 4 virtual machine disk files (*.vmdk):
**ipva.vmx: The virtual machine configuration file
**hd-boot.vmdk: The virtual boot harddisk (hd)
**hd-cf.vmdk: The hd for emulation of a Compact Flash card
**hd-flash.vmdk: The hd for emulation of flash memory
**hd-dump.vmdk: The hd serving as a store for a crash dump

The file ''ipva.bin'' is the firmware file, which is only needed for update purposes.

===VMware Player===
*Copy the IPVA to e.g. your desktop
*Double-click on ipva.vmx
The IPVA is going to be started.

A shortcut (*.lnk file) to the vmx-file will start the IPVA without additional user interaction. Such a shortcut may also be copied into the Windows ''Autostart'' program folder, in order to have the IPVA started automatically on windows startup.
===VMware Workstation===
*Copy the IPVA to e.g. your desktop
*Double-click on ipva.vmx
The IPVA is going to be started.

The ''Workstation 7'' directory comprises the command line utility ''vmrun.exe''. A batch file according to the following pattern may be crafted to programmatically start the IPVA.
<pre>
"D:\Programme\VMware\VMware Workstation\vmrun" start "C:\Users\Tester\Desktop\ipva\ipva.vmx"
</pre>
'''Note''': By altering ''start'' into ''stop'' a virtual machine may be stopped.
===VMware vSphere 4.x===
The IPVA offered for downloading must be converted into a vSphere-processable form.
The IPVA can be converted by means of the tool ''VMware vCenter Converter Standalone''<ref>VMware vCenter Converter Standalone: https://www.vmware.com/tryvmware/?p=converter</ref>. A step-by-step guide may be found [http://blog.lewan.com/2009/12/22/vmware-vsphere-using-vmware-converter-to-import-vms-or-vmdks-from-other-vmware-products/ here].

'''Note:''' See known issue [[#Don't use Maintenance/Upload/DRAM on vSphere 4|Don't use Maintenance/Upload/DRAM on vSphere 4]].

===Network Configuration===
Manufacturer-configured as DHCP client only. I.e. a DHCP server must be available. Afterwards the network configuration may be administrated as used to within the web ui of other innovaphone boxes. If there's in no case a DHCP server available for the 1st-time configuration, read through [[#What_Is_The_Console_Good_For?|What Is The Console Good For?]].

===License Configuration===
For the IPVA9 license see [[Reference9:Licenses]].

The licensing procedure is the same as for other innovaphone products, except for one peculiarity: The MAC address, generated by VMware, may have been assigned already to another customer/installation. Such a conflict must be settled manually as explained below.

If, while generating licenses within ''my.innovaphone.com'', a message ([[Reference:My_Innovaphone#IP-VA_MAC_exists|My_Innovaphone#IP-VA_MAC_exists]]) is displayed:
<pre>
IP-VA MAC exists
</pre>
then a new MAC address must be assigned manually to the affected installation.

In order to assign a new MAC address:
*Power-off the virtual machine
*Open the file ipva.vmx for editing within a text editor.
*Edit the last 3 hex-values of the lines starting with ''ethernet0.generatedAddress'' & ''uuid.bios'' from e.g.
<pre>
ethernet0.generatedAddress = "00:0c:29:f4:c6:d9"
uuid.bios = "56 4d 64 b9 52 ce 38 57-66 29 e8 f2 77 f4 c6 d9"
</pre>
into e.g
<pre>
ethernet0.generatedAddress = "00:0c:29:f4:c6:da"
uuid.bios = "56 4d 64 b9 52 ce 38 57-66 29 e8 f2 77 f4 c6 da"
</pre>
(Note: in this example just the very last hex-value '''d9''' is going to be altered into '''da''')
*Within my.innovaphone.com try once again to generate licenses for the virtual machine with the new MAC address.

==Provision Of External Resources==
External Resources are required, in order to provide:
*Access to ISDN interfaces
*DSP conferencing channels

The IP1060<ref>[http://www.innovaphone.com/fileadmin/download/newsletter/EINLEGER_IP1060_Produktkatalog2009_2010_DE_ENG.pdf IP1060 Product Information]</ref> media gateway may be considered as a suitable complement for such purposes.
==Download==

[http://download.innovaphone.com/ice/9.00/#firmware IPVA.zip from http://download.innovaphone.com/ice/9.00/#firmware]

==Troubleshooting==
A new option has been added to ''Admistration/Diagnostics/Tracing''. The option ''trace(crash-dump)'' is going to read a post-mortem log from hd-dump.vmdk, if available.
==Known Issues==
===ESX 3.x is unsupported===
The IPVA does not run under ESX 3.x and below, since virtual IDE disks aren't supported.

===Don't use Maintenance/Upload/DRAM on vSphere 4===
Until further notice this way of uploading a new firmware is currently not supported. The VMM detects and assumes the guest (IPVA) is going to shutting-off. All the virtual harddisks may get lost in the aftermath.
vmware.log shows:
<pre>
...

Mar 02 13:02:25.439: vcpu-0| Vix: [4864986 vmxCommands.c:9609]: VMAutomation_HandleCLIHLTEvent. Do nothing.
Mar 02 13:02:25.462: vcpu-0| MsgHint: msg.monitorevent.halt (sent)
Mar 02 13:02:25.462: vcpu-0| The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

...and then when trying to power-on later...

Mar 03 08:37:00.260: vmx| Destroying virtual dev for ide0:1 vscsi=8303
Mar 03 08:37:00.260: vmx| VMMon_VSCSIStopVports: Invalid handle
Mar 03 08:37:00.260: vmx| VMMon_VSCSIDestroyDev: Not found
Mar 03 08:37:00.260: vmx| Destroying virtual dev for ide1:0 vscsi=8304
Mar 03 08:37:00.261: vmx| VMMon_VSCSIStopVports: Invalid handle
Mar 03 08:37:00.261: vmx| VMMon_VSCSIDestroyDev: Not found
...
</pre>

===Release Note For V9HF1===
This Note refers to the fix [[Support:DVL-Roadmap_Firmware_V9#IPVA.2C_RAM-Dependent_Flash_Limitation | Support:DVL-Roadmap Firmware V9#IPVA RAM-Dependent Flash Limitation]]
*From on V9HF1 the available flash directory<ref>Flash Directory: Storage for PBX objects</ref> space will be constrained, depending on the available RAM. A loss of PBX objects may occur after an upgrade to V9HF1. In order to prevent such a loss perform the upgrade as follows:
**1)Download and save the current configuration of the affected IPVA.
**2)Upload the new firmware file and reboot.
**3)Upload the config from step 1).
*From on V9HF1 an administrative reduction of the available RAM may lead into a loss of PBX objects. I.e. increasing the RAM isn't critical, while in contrast lowering the amount of RAM lowers the amount of flash directory space.

===V9HF4 Needed For vSphere 5===
V9 Hotfix4 is needed, in order to run the IPVA under vSphere 5.

==FAQ==
===Are Firmware Updates Possible?===
Yes, alike the well-known *.bin firmware files for other innovaphone products (ip6000.bin, ip2000.bin,..) , there's a similar bin-file (ipva.bin) for the IPVA. The file is contained on the boot-hd and can be found by browsing to e.g. http://192.168.0.5/drive/HD-BOOT . The versioning of ipva.bin is the same as for the other products. The firmware file may exactly be uploaded as for other products:
* by ''Upload/Firmware''
* by ''Upload/Dram''
* by a script for the innovaphone Update Process

===What is the ipva default password?===
*user: admin
*password: ipva

===Do I Always Need To Download The Entire IPVA?===
No, after the 1st-time deployment of an entire IPVA only the firmware file ''ipva.bin'' needs to be downloaded from ''download.innovaphone.com''. See [[#Are_Firmware_Updates_Possible.3F| Are Firmware Updates Possible?]] for how to proceed further.
===How Is The Network Connection Being Handled?===
The network connection is pre-configured to: ''Bridged: Connected directly to the physical network''
===What Is The Size Of the Emulated CompactFlash?===
1GB

===Can The Emulated CompactFlash Be Increased In Size?===
Yes, from within the ''Edit Virtual Machine'' dialog. Doing so just increases the size of the virtual harddisk. The emulated CompactFlash must be formatted afterwards and accordingly to benefit from the increased size. That step can be administrated from ''Administration/Compact Flash/Format''. Note: A recommendation for an upper size limit is not given.

'''vSphere / vSphere Client'''

1. At first backup all of your files from CF card 
2. Shutdown the corresponding IPVA 
3. Choose "Properties" of the IPVA 
4. Delete "Harddrive 2" (Hardrive file xxx/xxx_1.vmdk) 

hd-boot.vmdk > xxx.vmdk
hd-cf.vmdk > xxx_1.vmdk
hd-flash.vmdk > xxx_2.vmdk
hd-dump.vmdk > xxx_3.vmdk

5. Create new harddrive 
6. Configure the required size 
7. As "Node of virtual device" select "IDE(0:1)" 
8. Start the IPVA. 
9. "Format" the CF Card and "mount" it (General/General/Compact-Flash).

===What Is The Size Of the emulated Flash Storage on the IPVA?===
The virtual flash storage used to store configuration file of the IPVA and LDAP directory of the PBX is defined with 64 MB and can not be changed. This is two times more than on IP6010. The VMDK-File hd-flash.vmdk is allocated with 100 MB, because VMWare can not handle smaller virtual disks.

===How Much RAM Is Required Per IPVA Instance?===
The downloadable virtual appliance comes preconfigured with 64MB RAM. This amount is seen as a good trade-off for the majority of all installations.
The RAM-size can be administrated by VMware-means.
===How Many IPVA Instances Are Possible Per Host?===
There's no worst-case estimate available. For a best-case calculation,
*see [http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf Configuration Maximums VMware vSphere 4.1]
*see [[#How_Much_RAM_Is_Required_Per_IPVA_Instance.3F | How Much RAM Is Required Per IPVA Instance?]]
===Where Has PPP-Functionality Gone?===
PPP-scenarios (PPTP, PPPoE) are not envisaged with the IPVA, because it has only one network interface controller.

'''Update'''(07.Mar.2011), from on 90468:
*PPP has been integrated
*a second network interface is available (now ETH0 and ETH1)
**ETH1 comes pre-configured: ''host-only, disconnected''. I.e. it must be reconfigured manually and by VMware means to become functional.

===Does The IPVA Support Non-VMware Hypervisor Products?===
No, currently it doesn't.

===How do I perform a factory reset?===

replace the 3rd disk, served on IDE 1:0, named hd-flash.vmdk with an empty disk:

[[Image:VM_Settings.png]]

1)download the IPVA and watch out for the file hd-flash.vmdk

2)Power-off the IPVA instance

3)Replace hd-flash.vmdk with the one downloaded in step 1). If on vsphere it may have been assigned a different name. Ensure it’s the one on IDE 1:0.

4)Power-on the IPVA instance

===Why Does ''General/Info/DRAM'' Show Less Than the Configured Memory?===
Not all of the configured memory is available to the IPVA. E.g. a bit of memory is occupied by the VMM<ref>Virtual Machine Monitor: A component belonging to the virtualization platform</ref>. The indicator ''General/Info/DRAM'' displays the memory available to the IPVA and is truncated down to a whole number. A boot-trace reveals a bit more about IPVA-available memory as shown in the following excerpt:
<pre>
...
0:0000:030:4 - Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
0:0000:030:4 - mem(64946176)=61.93MB ...
</pre>

===Is VMWare Fault Tolerance (FT) supported by IPVA?===

Yes, we have successfully tested<ref>[[Howto:Implement_PBX_with_zero_downtime_using_IPVA_and_VMWare_Fault_Tolerance | Howto:Implement PBX with zero downtime using IPVA and VMWare Fault Tolerance]]</ref> VMWare Fault Tolerance<ref>VMWare Fault Tolerance: http://www.vmware.com/products/fault-tolerance/overview.html</ref> with a virtual machine running IPVA on VMWare vSphere 4.1.

===What Is The Console Good For?===
The console is a remains of the early development phase. It resembles the IP3000's serial console. It doesn't offer any convenience like command history or backspace funtionality. Nevertheless may the console be of help in exceptional situations where e.g. the required DHCP server isn't available for 1st-time configuration or in situations where the ip configuration was misconfigured. Thereby any command from a device's config is acceptable.

For instance to configure the static IP address 1.2.3.4/24 on ETH0:
*Click into the console
*Press ENTER
*Enter credentials
*Enter
<pre>
config change IP0 ETH0 /addr 1.2.3.4 /mask 255.255.255.0
config change DHCP0 /mode off
config write
reset
</pre>
Since no backspace is offered it may become a daring task to enter a single line without typos. In case of a typo hit ENTER and input the same line again.
The keyboard layout is the US layout.
[[Image:Ip-via-console.png|center|thumb|200px|Console-edit of IP address]]

Display the IP configuration for ETH0:
<pre>
config show IP0 ETH0
</pre>

Display the DHCP configuration for ETH0:
<pre>
config show DHCP0
</pre>

Additional the DNS-server(s) and the default gateway can be configured:
<pre>
config change IP0 ETH0 /addr 1.2.3.4 /mask 255.255.255.0 /dns 8.8.8.8 /dns2 8.8.4.4
config change IP0 RT0 /gateway 1.2.3.254
config change DHCP0 /mode off
config write
reset
</pre>

Also some simple diagnostics (ping and traceroute) are possible via the console (output is given in the console):
<pre>
mod cmd PING0 tracert 8.8.8.8
mod cmd PING0 ping 8.8.8.8
</pre>

Resetting the entire FLASH space - '''Note, all configuration will get lost'''. this is similar method to the manufacturer reset method from above [[#How_do_I_perform_a_factory_reset.3F|How do I perform a factory reset?]]
<pre>
mod cmd FLASHMAN0 reset all
reset
</pre>

==Notes==
<references/>

==Related Articles==
[[Reference9:Licenses]]

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

Howto talk:ESTOS Procall 5.0 as UC-Server for Presence

2011-09-29T09:20:10Z

Pme: Removing all content from page

Howto:ESTOS Procall 5.0 as UC-Server for Presence

2011-09-29T09:02:37Z

Pme: /* Configuration of ESTOS Procall 4.0 */

Estos Procall 4.0 can be used as external presence server.

==Requirements==
Version 9 hf3 (or higher) of innovaphone PBX.

==Configuration of PBX==
1. Add a new PBX object of type "External UC". Give it a Long Name (e.g. External UC) and a Name (e.g. ext-uc).

[[Image:external_uc_object.png]]

2. On the "UC" tab enter the URI for the resource list subscription (e.g. allusers@innovaphone.com). This URI is used by the PBX to query presence information for all its PBX users.

[[Image:external_uc_subscribe.png]]

3. Enter at the corresponding users under User/External UC the Long Name (e.g. External UC).

[[Image:external_uc_user.png]]

==Configuration of ESTOS Procall 4.0==
1. Open ESTOS UCServer administration and select under SIP/Federation the option Edge Server. Next click on configuration and insert the "External UC" Name (e.g. ext-uc), Password, IP Address (e.g. 172.31.4.1) and Port Number (e.g. 5060). In the dropdownlist Network select automatic and in Transport Protocol TCP.

[[Image:external_uc_edge_server.png]]

2. Under SIP Server activate these option and add a new network interface with corrosponding IP Address (e.g. 172.16.0.14), Port Number (e.g. 5060) and Protocol (e.g. TCP).

[[Image:external_uc_sip_server.png]]

3. There is a possibility to check the configuration. Click on Diagnosis and start the test.

[[Image:external_uc_diagnosis.png]]

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

File:External uc diagnosis.png

2011-09-29T09:01:39Z

Pme:

File:External uc sip server.png

2011-09-29T08:47:41Z

Pme:

File:External uc edge server.png

2011-09-29T08:38:53Z

Pme:

Howto:ESTOS Procall 5.0 as UC-Server for Presence

2011-09-29T07:57:23Z

Pme: /* Configuration of PBX */

Estos Procall 4.0 can be used as external presence server.

==Requirements==
Version 9 hf3 (or higher) of innovaphone PBX.

==Configuration of PBX==
1. Add a new PBX object of type "External UC". Give it a Long Name (e.g. External UC) and a Name (e.g. ext-uc).

[[Image:external_uc_object.png]]

2. On the "UC" tab enter the URI for the resource list subscription (e.g. allusers@innovaphone.com). This URI is used by the PBX to query presence information for all its PBX users.

[[Image:external_uc_subscribe.png]]

3. Enter at the corresponding users under User/External UC the Long Name (e.g. External UC).

[[Image:external_uc_user.png]]

==Configuration of ESTOS Procall 4.0==

Open ESTOS UCServer administration and select under SIP/Federation the option Edge Server. Next click on configuration and insert the "External UC" Name (e.g. ext-uc), Password, IP Address (e.g. 192.168.0.1) and Port Number (e.g. 5060). In the dropdownlist Network select automatic and in Transport Protocol TCP.

Under SIP Server activate these option and add a new network interface with corrosponding IP Address (e.g. 192.168.0.20), Port Number (e.g. 5060) and Protocol (e.g. TCP).

Last there is a possibility to check the configuration. Click on Diagnosis and start the test.

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

File:External uc user.png

2011-09-29T07:53:39Z

Pme:

File:External uc subscribe.png

2011-09-29T07:46:45Z

Pme:

File:External uc object.png

2011-09-29T07:35:33Z

Pme:

File:External uc object.jpg

2011-09-29T07:32:16Z

Pme:

Howto:ESTOS Procall 5.0 as UC-Server for Presence

2011-09-28T15:24:44Z

Pme: /* Configuration of ESTOS Procall 4.0 */

Estos Procall 4.0 can be used as external presence server.

==Requirements==
Version 9 hf3 (or higher) of innovaphone PBX.

==Configuration of PBX==
Add a new PBX object of type "External UC".
Give it a Long Name (e.g. External UC) and a Name (ext-uc).
On the "UC" tab enter the URI for the resource list subscription (e.g. allusers@innovaphone.com).
This URI is used by the PBX to query presence information for all its PBX users.
Then enter the "External UC" Long Name at the corresponding users under User/External UC.

==Configuration of ESTOS Procall 4.0==

Open ESTOS UCServer administration and select under SIP/Federation the option Edge Server. Next click on configuration and insert the "External UC" Name (e.g. ext-uc), Password, IP Address (e.g. 192.168.0.1) and Port Number (e.g. 5060). In the dropdownlist Network select automatic and in Transport Protocol TCP.

Under SIP Server activate these option and add a new network interface with corrosponding IP Address (e.g. 192.168.0.20), Port Number (e.g. 5060) and Protocol (e.g. TCP).

Last there is a possibility to check the configuration. Click on Diagnosis and start the test.

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

Howto:ESTOS Procall 5.0 as UC-Server for Presence

2011-09-28T14:46:11Z

Pme:

Reference9:PBX/Objects/Edit Groups

2011-06-30T15:39:26Z

Pme: /* Properties of Groups */

With this page the group assignment of an object can be changed. The existing list of group assignments can be changed or a new group assignment can be added (which in fact adds the object to this group).

== Properties of Groups ==

{|
|valign=top nowrap=true|'''Name'''
|The name identifies the group. If a name is entered, which does not yet exist, a new group is created. The same name used on objects located on different PBXs identifies different groups. Group functions are only available for endpoints registered on the same PBX. Don´t use existing "Name" for group name.
|-
|valign=top nowrap=true|'''Active'''
|The active flag controls the visibility of other group members to this object. If the active flag is not set, the other group members are not visible to this object. This mechanism is used in various ways by different object types. E.g. a broadcast object can only send calls to users, which are visible to the broadcast object, which means it sends calls to all members of groups in which the broadcast object itself is active. The other members to which the broadcast object is sending calls do not need to be active.

To do pickup the member from which the call shall be picked needs to be visible.

Care should be taken not to configure the active flag if not needed. On one hand the user may be allowed things which he should not be allowed to do (pickup or monitor with partner keys) on the other hand it costs memory and CPU power.
|-
|valign=top nowrap=true|'''Mode'''
|A group assignment may be 'static', which means not changeable from the endpoint or dynamic. If it is dynamic it can be changed from the endpoint to be either 'Dynamic-In' or 'Dynamic-Out'. If it is 'Dynamic-Out' it is treated by the PBX as if it was not present.
|}

Reference:Administration/PBX/Objects/Edit Groups

2011-06-30T15:38:48Z

Pme: /* Properties of Groups */

Howto:OptiCaller Client - OptiCaller AB - 3rd Party Product

2010-09-30T15:00:57Z

Pme: /* Summary */

==Product Name==

[http://www.opticaller.se/english.html OptiCaller Client]

==Certification Status==




{{Template:Compat Status "tested"}}


Testing of this product has been finalized for Windows Mobile on May 6th, 2010 and for Symbian on September 15, 2010.

==Category==

{{Category:RecProd Call Center Applications}}
[[Category:RecProd|{{PAGENAME}}]]

{{Category:RecProd Solutions for Mobile Extensions}}
[[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]

==Functions==

*Software for mobile PBX
*2-stage-dialing
*DTMF-Features
*Call Back (Data Call Back, SMS Call Back, Voice Call Back)
*Mobile Least Cost Routing

==Version==

Windows Mobile
1.6
Symbian
1.09

==Vendor==



http://www.opticaller.se

==Description==

'''OptiCaller'''

The OptiCaller application is designed primarily for mobile phones. It allows the user to make calls in a flexible, and above all, more cost-effective manner. It also makes it easy to manage PBX functions, e.g. call diversions, signing in or out of groups etc directly from a mobile phone.

'''Operator and system neutral'''

The architecture is operator independent, which means that the application works regardless of mobile operator. The application has very flexible configuration options and is adaptable to suite the majority of telephone exchanges on the market. Configuration and deployment of clients (OTA) is easily handled by a powerful provisioning system.

'''Mobile Extension (MEX)'''

OptiCaller greatly simplifies the use of the Mobile Extension feature where the mobile phone becomes an extension in the PBX. Using OptiCaller the user can call in the usual way and dial numbers manually, from the phone book or call history. OptiCaller then, transparently to the user, connects calls via the switchboard to the destination.

'''Mobile Least Cost Routing (LCR)'''

OptiCaller always takes control over how each call is connected and is thus giving the user the opportunity to call in the most cost efficient way. By choosing between calling directly, through the switch, Call-Back or Mobile VoIP, call costs can often be reduced by average 50%.

'''Platforms'''

OptiCaller is designed for Java, Symbian, iPhone, Android and Windows Mobile but is also available as a web application and can then be used from any web browser at any time.

==Summary==


*light and easy to use software
*mobility Licence on the PBX required
*2-stage-dialling for internal numbers shorter than 3 digits or 3 digits numbers starting with 1 is not possible on the Windows Mobile version
*2-stage-dialling for internal numbers shorter than 100 does not work
*using DTMF-Features without connect is not possible

For a detailed analysis of the product please have a look at the [[Howto:OptiCaller_Client_Windows_Mobile_-_OptiCaller_AB_-_Testreport]] and [[Howto:OptiCaller_Client_Symbian_-_OptiCaller_AB_-_Testreport]].

==Pricing==

Contact OptiCaller Software for free trials.
info@opticaller.se
Phone +46702121259

==Contact==


{|
| Tel: || +46702121259 Sales Contact Mattias Hansson
|-
| Fax: || +4684440451
|-
| Mail: || [mailto:info@opticaller.se info@opticaller.se]
|}

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

Howto:OptiCaller Client - OptiCaller AB - 3rd Party Product

2010-09-30T15:00:06Z

Pme: /* Summary */

==Product Name==

[http://www.opticaller.se/english.html OptiCaller Client]

==Certification Status==




{{Template:Compat Status "tested"}}


Testing of this product has been finalized for Windows Mobile on May 6th, 2010 and for Symbian on September 15, 2010.

==Category==

{{Category:RecProd Call Center Applications}}
[[Category:RecProd|{{PAGENAME}}]]

{{Category:RecProd Solutions for Mobile Extensions}}
[[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]

==Functions==

*Software for mobile PBX
*2-stage-dialing
*DTMF-Features
*Call Back (Data Call Back, SMS Call Back, Voice Call Back)
*Mobile Least Cost Routing

==Version==

Windows Mobile
1.6
Symbian
1.09

==Vendor==



http://www.opticaller.se

==Description==

'''OptiCaller'''

The OptiCaller application is designed primarily for mobile phones. It allows the user to make calls in a flexible, and above all, more cost-effective manner. It also makes it easy to manage PBX functions, e.g. call diversions, signing in or out of groups etc directly from a mobile phone.

'''Operator and system neutral'''

The architecture is operator independent, which means that the application works regardless of mobile operator. The application has very flexible configuration options and is adaptable to suite the majority of telephone exchanges on the market. Configuration and deployment of clients (OTA) is easily handled by a powerful provisioning system.

'''Mobile Extension (MEX)'''

OptiCaller greatly simplifies the use of the Mobile Extension feature where the mobile phone becomes an extension in the PBX. Using OptiCaller the user can call in the usual way and dial numbers manually, from the phone book or call history. OptiCaller then, transparently to the user, connects calls via the switchboard to the destination.

'''Mobile Least Cost Routing (LCR)'''

OptiCaller always takes control over how each call is connected and is thus giving the user the opportunity to call in the most cost efficient way. By choosing between calling directly, through the switch, Call-Back or Mobile VoIP, call costs can often be reduced by average 50%.

'''Platforms'''

OptiCaller is designed for Java, Symbian, iPhone, Android and Windows Mobile but is also available as a web application and can then be used from any web browser at any time.

==Summary==


*light and easy to use software
*mobility Licence on the PBX required
*2-stage-dialling for internal numbers shorter than 3 digits or 3 digits numbers starting with 1 is not possible on the Windows Mobile version
*2-stage-dialling for internal numbers shorter than 100 does not work
*using DTMF-Features without connect is not possible

For a detailed analysis of the product please have a look at the [[Howto:OptiCaller_Client_-_OptiCaller_AB_-_Testreport]] and [[Howto:OptiCaller_Client_Symbian_-_OptiCaller_AB_-_Testreport]].

==Pricing==

Contact OptiCaller Software for free trials.
info@opticaller.se
Phone +46702121259

==Contact==


{|
| Tel: || +46702121259 Sales Contact Mattias Hansson
|-
| Fax: || +4684440451
|-
| Mail: || [mailto:info@opticaller.se info@opticaller.se]
|}

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

Howto:OptiCaller Client - OptiCaller AB - 3rd Party Product

2010-09-30T14:55:29Z

Pme: /* Summary */

==Product Name==

[http://www.opticaller.se/english.html OptiCaller Client]

==Certification Status==




{{Template:Compat Status "tested"}}


Testing of this product has been finalized for Windows Mobile on May 6th, 2010 and for Symbian on September 15, 2010.

==Category==

{{Category:RecProd Call Center Applications}}
[[Category:RecProd|{{PAGENAME}}]]

{{Category:RecProd Solutions for Mobile Extensions}}
[[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]

==Functions==

*Software for mobile PBX
*2-stage-dialing
*DTMF-Features
*Call Back (Data Call Back, SMS Call Back, Voice Call Back)
*Mobile Least Cost Routing

==Version==

Windows Mobile
1.6
Symbian
1.09

==Vendor==



http://www.opticaller.se

==Description==

'''OptiCaller'''

The OptiCaller application is designed primarily for mobile phones. It allows the user to make calls in a flexible, and above all, more cost-effective manner. It also makes it easy to manage PBX functions, e.g. call diversions, signing in or out of groups etc directly from a mobile phone.

'''Operator and system neutral'''

The architecture is operator independent, which means that the application works regardless of mobile operator. The application has very flexible configuration options and is adaptable to suite the majority of telephone exchanges on the market. Configuration and deployment of clients (OTA) is easily handled by a powerful provisioning system.

'''Mobile Extension (MEX)'''

OptiCaller greatly simplifies the use of the Mobile Extension feature where the mobile phone becomes an extension in the PBX. Using OptiCaller the user can call in the usual way and dial numbers manually, from the phone book or call history. OptiCaller then, transparently to the user, connects calls via the switchboard to the destination.

'''Mobile Least Cost Routing (LCR)'''

OptiCaller always takes control over how each call is connected and is thus giving the user the opportunity to call in the most cost efficient way. By choosing between calling directly, through the switch, Call-Back or Mobile VoIP, call costs can often be reduced by average 50%.

'''Platforms'''

OptiCaller is designed for Java, Symbian, iPhone, Android and Windows Mobile but is also available as a web application and can then be used from any web browser at any time.

==Summary==


*light and easy to use software
*mobility Licence on the PBX required
*2-stage-dialling for internal numbers shorter than 3 digits or 3 digits numbers starting with 1 is not possible
*using DTMF-Features without connect is not possible

For a detailed analysis of the product please have a look at the [[Howto:OptiCaller_Client_-_OptiCaller_AB_-_Testreport]].

==Pricing==

Contact OptiCaller Software for free trials.
info@opticaller.se
Phone +46702121259

==Contact==


{|
| Tel: || +46702121259 Sales Contact Mattias Hansson
|-
| Fax: || +4684440451
|-
| Mail: || [mailto:info@opticaller.se info@opticaller.se]
|}

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

Howto:OptiCaller Client - OptiCaller AB - 3rd Party Product

2010-09-30T14:53:28Z

Pme: /* Version */

==Product Name==

[http://www.opticaller.se/english.html OptiCaller Client]

==Certification Status==




{{Template:Compat Status "tested"}}


Testing of this product has been finalized for Windows Mobile on May 6th, 2010 and for Symbian on September 15, 2010.

==Category==

{{Category:RecProd Call Center Applications}}
[[Category:RecProd|{{PAGENAME}}]]

{{Category:RecProd Solutions for Mobile Extensions}}
[[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]

==Functions==

*Software for mobile PBX
*2-stage-dialing
*DTMF-Features
*Call Back (Data Call Back, SMS Call Back, Voice Call Back)
*Mobile Least Cost Routing

==Version==

Windows Mobile
1.6
Symbian
1.09

==Vendor==



http://www.opticaller.se

==Description==

'''OptiCaller'''

The OptiCaller application is designed primarily for mobile phones. It allows the user to make calls in a flexible, and above all, more cost-effective manner. It also makes it easy to manage PBX functions, e.g. call diversions, signing in or out of groups etc directly from a mobile phone.

'''Operator and system neutral'''

The architecture is operator independent, which means that the application works regardless of mobile operator. The application has very flexible configuration options and is adaptable to suite the majority of telephone exchanges on the market. Configuration and deployment of clients (OTA) is easily handled by a powerful provisioning system.

'''Mobile Extension (MEX)'''

OptiCaller greatly simplifies the use of the Mobile Extension feature where the mobile phone becomes an extension in the PBX. Using OptiCaller the user can call in the usual way and dial numbers manually, from the phone book or call history. OptiCaller then, transparently to the user, connects calls via the switchboard to the destination.

'''Mobile Least Cost Routing (LCR)'''

OptiCaller always takes control over how each call is connected and is thus giving the user the opportunity to call in the most cost efficient way. By choosing between calling directly, through the switch, Call-Back or Mobile VoIP, call costs can often be reduced by average 50%.

'''Platforms'''

OptiCaller is designed for Java, Symbian, iPhone, Android and Windows Mobile but is also available as a web application and can then be used from any web browser at any time.

==Summary==


*light and easy to use software
*mobility Licence on the PBX required
*2-stage-dialling for internal numbers shorter than 3 digits or 3 digits numbers starting with 1 is not possible on the Windows Mobile version
*using DTMF-Features without connect is not possible

For a detailed analysis of the product please have a look at the [[Howto:OptiCaller_Client_-_OptiCaller_AB_-_Testreport]].

==Pricing==

Contact OptiCaller Software for free trials.
info@opticaller.se
Phone +46702121259

==Contact==


{|
| Tel: || +46702121259 Sales Contact Mattias Hansson
|-
| Fax: || +4684440451
|-
| Mail: || [mailto:info@opticaller.se info@opticaller.se]
|}

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

Howto:OptiCaller Client - OptiCaller AB - 3rd Party Product

2010-09-30T14:51:44Z

Pme: /* Version */

==Product Name==

[http://www.opticaller.se/english.html OptiCaller Client]

==Certification Status==




{{Template:Compat Status "tested"}}


Testing of this product has been finalized for Windows Mobile on May 6th, 2010 and for Symbian on September 15, 2010.

==Category==

{{Category:RecProd Call Center Applications}}
[[Category:RecProd|{{PAGENAME}}]]

{{Category:RecProd Solutions for Mobile Extensions}}
[[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]

==Functions==

*Software for mobile PBX
*2-stage-dialing
*DTMF-Features
*Call Back (Data Call Back, SMS Call Back, Voice Call Back)
*Mobile Least Cost Routing

==Version==

1.6 for Windows Mobile
1.09 for Symbian

==Vendor==



http://www.opticaller.se

==Description==

'''OptiCaller'''

The OptiCaller application is designed primarily for mobile phones. It allows the user to make calls in a flexible, and above all, more cost-effective manner. It also makes it easy to manage PBX functions, e.g. call diversions, signing in or out of groups etc directly from a mobile phone.

'''Operator and system neutral'''

The architecture is operator independent, which means that the application works regardless of mobile operator. The application has very flexible configuration options and is adaptable to suite the majority of telephone exchanges on the market. Configuration and deployment of clients (OTA) is easily handled by a powerful provisioning system.

'''Mobile Extension (MEX)'''

OptiCaller greatly simplifies the use of the Mobile Extension feature where the mobile phone becomes an extension in the PBX. Using OptiCaller the user can call in the usual way and dial numbers manually, from the phone book or call history. OptiCaller then, transparently to the user, connects calls via the switchboard to the destination.

'''Mobile Least Cost Routing (LCR)'''

OptiCaller always takes control over how each call is connected and is thus giving the user the opportunity to call in the most cost efficient way. By choosing between calling directly, through the switch, Call-Back or Mobile VoIP, call costs can often be reduced by average 50%.

'''Platforms'''

OptiCaller is designed for Java, Symbian, iPhone, Android and Windows Mobile but is also available as a web application and can then be used from any web browser at any time.

==Summary==


*light and easy to use software
*mobility Licence on the PBX required
*2-stage-dialling for internal numbers shorter than 3 digits or 3 digits numbers starting with 1 is not possible on the Windows Mobile version
*using DTMF-Features without connect is not possible

For a detailed analysis of the product please have a look at the [[Howto:OptiCaller_Client_-_OptiCaller_AB_-_Testreport]].

==Pricing==

Contact OptiCaller Software for free trials.
info@opticaller.se
Phone +46702121259

==Contact==


{|
| Tel: || +46702121259 Sales Contact Mattias Hansson
|-
| Fax: || +4684440451
|-
| Mail: || [mailto:info@opticaller.se info@opticaller.se]
|}

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

Howto:OptiCaller Client - OptiCaller AB - 3rd Party Product

2010-09-30T14:50:32Z

Pme: /* Certification Status */

==Product Name==

[http://www.opticaller.se/english.html OptiCaller Client]

==Certification Status==




{{Template:Compat Status "tested"}}


Testing of this product has been finalized for Windows Mobile on May 6th, 2010 and for Symbian on September 15, 2010.

==Category==

{{Category:RecProd Call Center Applications}}
[[Category:RecProd|{{PAGENAME}}]]

{{Category:RecProd Solutions for Mobile Extensions}}
[[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]

==Functions==

*Software for mobile PBX
*2-stage-dialing
*DTMF-Features
*Call Back (Data Call Back, SMS Call Back, Voice Call Back)
*Mobile Least Cost Routing

==Version==

1.6

==Vendor==



http://www.opticaller.se

==Description==

'''OptiCaller'''

The OptiCaller application is designed primarily for mobile phones. It allows the user to make calls in a flexible, and above all, more cost-effective manner. It also makes it easy to manage PBX functions, e.g. call diversions, signing in or out of groups etc directly from a mobile phone.

'''Operator and system neutral'''

The architecture is operator independent, which means that the application works regardless of mobile operator. The application has very flexible configuration options and is adaptable to suite the majority of telephone exchanges on the market. Configuration and deployment of clients (OTA) is easily handled by a powerful provisioning system.

'''Mobile Extension (MEX)'''

OptiCaller greatly simplifies the use of the Mobile Extension feature where the mobile phone becomes an extension in the PBX. Using OptiCaller the user can call in the usual way and dial numbers manually, from the phone book or call history. OptiCaller then, transparently to the user, connects calls via the switchboard to the destination.

'''Mobile Least Cost Routing (LCR)'''

OptiCaller always takes control over how each call is connected and is thus giving the user the opportunity to call in the most cost efficient way. By choosing between calling directly, through the switch, Call-Back or Mobile VoIP, call costs can often be reduced by average 50%.

'''Platforms'''

OptiCaller is designed for Java, Symbian, iPhone, Android and Windows Mobile but is also available as a web application and can then be used from any web browser at any time.

==Summary==


*light and easy to use software
*mobility Licence on the PBX required
*2-stage-dialling for internal numbers shorter than 3 digits or 3 digits numbers starting with 1 is not possible on the Windows Mobile version
*using DTMF-Features without connect is not possible

For a detailed analysis of the product please have a look at the [[Howto:OptiCaller_Client_-_OptiCaller_AB_-_Testreport]].

==Pricing==

Contact OptiCaller Software for free trials.
info@opticaller.se
Phone +46702121259

==Contact==


{|
| Tel: || +46702121259 Sales Contact Mattias Hansson
|-
| Fax: || +4684440451
|-
| Mail: || [mailto:info@opticaller.se info@opticaller.se]
|}

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

Howto:Wikitogo

2010-04-14T12:00:36Z

Pme: /* Installation */

Wikitogo is an offline version of the innovaphone wiki containing a weekly snapshot of this wiki.

==Applies To==
This information applies to all V7 devices and later.



==More Information==
innovaphone wiki is also the source for the innovaphone on-line help. This is great as you always have access to the latest information on-line.

However, once in a while you will need to go to a customer site where you don't have access to wiki.innovaphone.com. To help with this situation, we are maintaining an off line copy of innovaphone wiki, known as wikitogo. This is a 170MB self-containing copy of innovaphone wiki including web-server and database. It is updated each Sunday.

===Installation===
To have this at hand if need be, [http://download.innovaphone.com/ice/7.00/#wikitogo download] and unzip the Weekly Wiki2Go Update package to an empty folder on your PC now.

The wikitogo download package includes an autorun.inf, so when you copy it on a CD, it might launch innovaphone wiki immediately when inserted into the CD slot. However, you can start it from just everywhere by starting SERVER2GO\server2go.exe.

Note: You need administrator rights for using with Microsoft Windows 7 (32 or 64 bit)!

===Configuration===
The web interface of the V7 innovaphone devices is equipped with a Help button providing context sensitive online help for the current configuration page. In the default configuration it links to a corresponding wiki Reference page on the <code>http://wiki.innovaphone.com</code>. To link to the wikitogo installation on your PC a configuration change on the device is required. Read [[Reference:Configuration/General/Admin#Help_URL]] in order to understand how to change the default Help URL.

===Known Problems===
As always in innovaphone wiki, you will need to log-in to it. In wikitogo, the only account that exists though is <code>ice/technical</code>.

== Related Articles ==
[http://download.innovaphone.com/ice/7.00/#wikitogo http://download.innovaphone.com/ice/7.00/#wikitogo]

[[Reference:Configuration/General/Admin]]

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

Reference8:Delegated Authentication

2010-03-10T09:38:12Z

Pme: /* Configuration */

== Applies to ==
All devices with firmware version 8 and later.

== Overview ==
Each device has its own administrator/viewer accounts.

In version 8 and later a single device can act as an authentication server for the rest of the devices. User accounts that are managed on the authentication server can be used to login on each device in the installation. You can also configure devices to accept user accounts from a PBX or a Windows domain.

== How it works ==
Version 8 devices can use Kerberos to authenticate users that are not managed locally but on a remote Kerberos server.

=== Kerberos ===
A Kerberos server manages users and services for a realm that is specified by a distinct name. It shares a secret password with each user and each service.
Users can obtain a ticket for a service from the Kerberos server if they proove that they know their own password.
Services can then authenticate users by validating tickets instead of passwords. Therefore many devices can be accessed using the same user credentials but only the Kerberos server and the user have to know it.

=== Logging in ===
The main idea of how the centralized login process works in version 8 is the following:

[[Image:Login_kerberos_basic.png]]

# The browser sends user name and password to the box, using '''HTTPS basic authentication'''.
# The box then uses '''Kerberos''' to obtain a ticket on behalf of the user from the Kerberos server for its own web server.
If that was successful the password is valid and the user is authenticated.

=== Cross realm authentication ===
Cross-realm authentication means that users from one realm/domain can login to services from another realm/domain. To do so, the realms have to trust each other and have a shared secret password to decrypt tickets from the other realm. This password has to be configured on both Kerberos servers. The picture shows how cross-realm authentication is used to login with a Windows domain user at an innovaphone box.

[[Image:Login kerberos basic crossrealm.png]]

# The browser sends user name and password of a Windows domain user to the box, using HTTPS basic authentication.
# The box authenticates with the user credentials against the Windows Kerberos server and gets back a ticket-granting ticket.
# The box uses the ticket-granting ticket to get a ticket for the innovaphone Kerberos server.
# The box uses the cross-realm ticket to obtain a ticket on behalf of the user from the innovaphone Kerberos server for its own web server.
If that was successful the password is valid and the user is authenticated.

=== HTTPS for encryption ===
The box needs username and password in the clear to delegate authentication. Basic authentication is used to send that information from the web browser to the box. This message exchange has to be encrypted using HTTPS.

In order to protect user passwords from eavesdropping and to stay compatible with existing configurations at the same time, our devices implement the following behaviour if Kerberos is enabled.

'''HTTP'''
* No change to the normal behaviour
* Digest or Basic authentication is offered
* Local users from the box, only
'''HTTPS'''
* Basic authentication, only
* Local users and remote Kerberos users.

As a consequence you have to use HTTPS if you want to login with a Kerberos user account.

=== Authorization ===
Tickets issued by an innovaphone Kerberos server contain some information whether the user is an administrator or a viewer. When it comes to cross-realm authentication with a Windows domain the innovaphone Kerberos server can map between Windows group memberships and administrator rights.

=== Kerberos servers on the innovaphone platform ===
V8 gateways are capable of hosting multiple Kerberos servers at a time.

==== Stand-alone Kerberos server ====
Each gateway can host a single Kerberos server that can be configured freely.

==== The PBX as a Kerberos server ====
Each PBX also provides for Kerberos authentication for its users without additional configuration:
* The ''System Name'' of the PBX is the name of the realm.
* Users with both a password and rights defined can be used for delegated authentication.
* The ''Name'' of the user object in the PBX can be used as the user name for authentication.
* Users with the right ''Full PBX Administration'' are administrators in the Kerberos realm. Users with other rights are viewers.
* LDAP replication also works with the Kerberos information.
* There is a special user called ''_KADMIN_'' that can be used to add devices to the realm but not to login to the user interface.

== Configuration ==
Assumption: Synchronous system time (NTP)
=== Setting up the Kerberos server ===
The Kerberos server of a PBX is configured using the PBX/Security page (see [[Reference8:Administration/PBX/Security]]).

Configuration of the stand-alone Kerberos server is done using the General/Kerberos page (see [[Reference8:Configuration/General/Kerberos]]).
# Enter a LDAP password. This password is used to encrypt keys in the LDAP directory of the server.
# Configure the name of the realm.
Now the server is running. You can now create and manage user accounts.

=== Setting up the client devices ===
Configuration of the clients is done using the General/Admin page from the web administration interface (see [[Reference8:Configuration/General/Admin]]).

# Configure the ''Server Locations'' of the Kerberos servers of all involved realms. Don't forget servers that are needed for cross-realm authentication.
# ''Join'' the desired Kerberos realm. You will need administrator credentials from that realm in order to do that.
Now the device can authenticate users from the realm for HTTPS connections. You can deactivate the local user accounts on the device, if needed.

Note: The box that hosts the Kerberos server might also be a client device and have to join the realm.

=== Setting up cross-realm authentication ===
# On the server device, specify the ''Trusted Realms'', the corresponding passwords and the methods of authorization mapping.
# Configure the ''Server Location'' on each client device.

There are different methods of mapping authorization between realm:
* keep (works only with innovaphone servers)
* Grant administrator access to all users
* Grant viewer access to all users
* Map the Windows domain group membership from the ticket to administrator or viewer rights

If you use the latter, please specify the RID of the groups that shall have administrator or viewer rights, respectively.

==== Determining the RID of a Windows domain group ====
The RID (relative ID) of a Windows domain group is the last numeric part of the domain group SID (secure ID).

The easiest way to determine it for a group you are a member of is using the following command:

whoami /groups /sid

[Group 1] = "DOMAIN\Domain-Users" S-1-5-21-854245398-616249376-725345543-'''513'''
[Group 2] = "DOMAIN\Admins" S-1-5-21-854245398-616249376-725345543-'''1180'''

In this example the RID for ''DOMAIN\Domain-Users'' is ''513'' and the RID for ''DOMAIN\Admins'' is ''1180''.

==== Prerequisites for Windows groups ====
You can use a Windows group for authorization if
* it is in the domain of the users
* it is a global security group
* it does not contain nested groups

== Using it ==
Once configured you can use Kerberos user accounts for logging in to the administation interface of boxes using your web browser.
=== Use HTTPS for Kerberos users ===
Delegated authentication works only with HTTPS connections. Using HTTP the boxes accept only local user accounts.

=== User names ===
To distinguish between local users and users of a Kerberos realm, the name of the realm has to be prepended to the user name, separated by a backslash (''\''). Alternatively you can prepend the realm to the user name separated by an at (''@'').

Example:
* Local user: ''admin''
* Remote user: ''REALM\username'' or ''username@REALM''

Mind that realm names are case sensitive and that they are usually written in upper case letters.

== Security considerations ==
=== Use local users only for recovery purposes ===
Although the old local user accounts of devices can still be used to login, this should not be done.

We recommend to choose a different secure administrator password for each device. After Single Sign-On has been configured, the list of admin passwords should be locked away and used only for recovery purposes. For normal configuration only user accounts from the Kerberos realm should be used to access devices.

We recommend that because it is much easier to change the password of or delete a compromised user account on the Kerberos server than changing the local administrator passwords on each device.

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