innovaphone wiki - User contributions [en]

Howto:EManager Active Directory - effexx - 3rd Party Product

2026-07-14T05:59:18Z

Vsc:

[[File:Effexx logo.png||200px|right]]

==Product Name==

eManager Active Directory [https://www.effexx.com/e-soft Link]

==Category==

[[Category:Partner Apps|{{PAGENAME}}]]
{{Category:3rdParty_VoIPSystem_Management}}
[[Category:3rdParty VoIPSystem Management|{{PAGENAME}}]]

==Functions==


Initial setup of users
* Setting config template based on related AD group
* Optional setting user password and sending mail
* Setting homescreen apps

Regular sync of users
* Update template
* Assign softphone
* Assign hardphone
* Assign DECT device
* Configure mobility
* Manage hunt groups and assign users (static/dynamic with key)
* Manage pickup groups and assign users (including key)
* Manage additional groups (for example TAPI or ACD groups)
* Define internal and external send number

==Version==

1.2.3

==Vendor==


[[File:Effexx logo.png||200px]] [https://www.effexx.com effexx its GmbH]

==Description==


Users can be deployed and configured in various ways, such as with the built-in Active Directory (AD) replicator by innovaphone. Since this replicator is limited in applying a configuration template, groups, and more based on AD settings, we developed a tool called eManager to expand the replicator’s capabilities. The eManager is installed on a Windows Server system using IIS. It functions similarly to the replicator: synchronization from AD to PBX is performed cyclically in the background. After the initial configuration, the end user (customer) doesn’t need to take any further action other than configuring AD with the appropriate attributes and groups.

==Competitive Analysis==


If a customer wants to manage pickup groups using AD, they can create groups in Active Directory with the naming format ‘eManager_Pickup_GroupName’. After a user is added to this group, eManager creates a corresponding PBX group, adds all PBX users to it and creates a pickup key. Neither the systems integrator nor the customer needs to configure anything on the PBX for this group.

[[File:EManager overview.png||300px]]

Active Directory Groups:

[[File:EManager AD groups.png||600px]]

User MemberOf:

[[File:EManager AD Member of.png||200px]]

In project context we also provide REST based API calls for example to query unused numbers, resetting passwords and so on:

[[File:EManager AD API.png||400px]]

==Prerequisites==

* Windows Server 2019 or above
* HTTP PBX admin user (HTTPs port is open)
* Active Directory user with read permission (LDAPs port is open)
* Optional SMTP user (sending anonymously is possible) (SMTP port is open)

==Configuration==

The product will be installed by an effexx software expert and afterwards configured using the credentials for PBX, Active Directory and end customer preferred settings.

For example the optional mail configuration is as follows:

"Mail": {
"Host": "",
"Port": 25,
"Anonym": false,
"AnonymSendAddress": "noreply@example.com",
"AnonymSendName": "myApps login",
"UserName": "",
"CypherPwd": "",
"Iv": "",
"Subject": "your new calling password",
"Header": "Dear user,",
"Message": "Your new telephone password is as follwos: [pwd].[linebreak]Please use this one your phone or myApps.",
"Footer": "The inbox is not monitored; please do not reply to this message."
}










==Pricing==


We provide an installation with a three month trial period for two purposes:
* System integrator wants to test functionality and learn about eManager
* End customers wants to have a PoC setup before placing an order

The product is sold with one-time costs based on PBX user count. The API functionality is optional and conditions are agreed upon individually

==Contact==


{|
| colspan=99 | effexx its GmbH
|-
| colspan=99 | Obere Industriestraße 8
|-
| colspan=99 | 57250, Netphen
|-
| Tel: || +49 271 7095 0
|-
| Mail: || [mailto:apps@effexx.com apps@effexx.com]
|}

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

Howto:EManager Active Directory - effexx - 3rd Party Product

2026-07-14T05:58:40Z

Vsc: /* Category */

[[File:Effexx logo.png||200px|right]]

==Product Name==

eManager Active Directory [https://www.effexx.com/e-soft Link]














==Category==

[[Category:Partner Apps|{{PAGENAME}}]]
{{Category:3rdParty_VoIPSystem_Management}}
[[Category:3rdParty VoIPSystem Management|{{PAGENAME}}]]

==Functions==


Initial setup of users
* Setting config template based on related AD group
* Optional setting user password and sending mail
* Setting homescreen apps

Regular sync of users
* Update template
* Assign softphone
* Assign hardphone
* Assign DECT device
* Configure mobility
* Manage hunt groups and assign users (static/dynamic with key)
* Manage pickup groups and assign users (including key)
* Manage additional groups (for example TAPI or ACD groups)
* Define internal and external send number

==Version==

1.2.3

==Vendor==


[[File:Effexx logo.png||200px]] [https://www.effexx.com effexx its GmbH]

==Description==


Users can be deployed and configured in various ways, such as with the built-in Active Directory (AD) replicator by innovaphone. Since this replicator is limited in applying a configuration template, groups, and more based on AD settings, we developed a tool called eManager to expand the replicator’s capabilities. The eManager is installed on a Windows Server system using IIS. It functions similarly to the replicator: synchronization from AD to PBX is performed cyclically in the background. After the initial configuration, the end user (customer) doesn’t need to take any further action other than configuring AD with the appropriate attributes and groups.

==Competitive Analysis==


If a customer wants to manage pickup groups using AD, they can create groups in Active Directory with the naming format ‘eManager_Pickup_GroupName’. After a user is added to this group, eManager creates a corresponding PBX group, adds all PBX users to it and creates a pickup key. Neither the systems integrator nor the customer needs to configure anything on the PBX for this group.

[[File:EManager overview.png||300px]]

Active Directory Groups:

[[File:EManager AD groups.png||600px]]

User MemberOf:

[[File:EManager AD Member of.png||200px]]

In project context we also provide REST based API calls for example to query unused numbers, resetting passwords and so on:

[[File:EManager AD API.png||400px]]

==Prerequisites==

* Windows Server 2019 or above
* HTTP PBX admin user (HTTPs port is open)
* Active Directory user with read permission (LDAPs port is open)
* Optional SMTP user (sending anonymously is possible) (SMTP port is open)

==Configuration==

The product will be installed by an effexx software expert and afterwards configured using the credentials for PBX, Active Directory and end customer preferred settings.

For example the optional mail configuration is as follows:

"Mail": {
"Host": "",
"Port": 25,
"Anonym": false,
"AnonymSendAddress": "noreply@example.com",
"AnonymSendName": "myApps login",
"UserName": "",
"CypherPwd": "",
"Iv": "",
"Subject": "your new calling password",
"Header": "Dear user,",
"Message": "Your new telephone password is as follwos: [pwd].[linebreak]Please use this one your phone or myApps.",
"Footer": "The inbox is not monitored; please do not reply to this message."
}










==Pricing==


We provide an installation with a three month trial period for two purposes:
* System integrator wants to test functionality and learn about eManager
* End customers wants to have a PoC setup before placing an order

The product is sold with one-time costs based on PBX user count. The API functionality is optional and conditions are agreed upon individually

==Contact==


{|
| colspan=99 | effexx its GmbH
|-
| colspan=99 | Obere Industriestraße 8
|-
| colspan=99 | 57250, Netphen
|-
| Tel: || +49 271 7095 0
|-
| Mail: || [mailto:apps@effexx.com apps@effexx.com]
|}

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

Reference16r1:Concept IP270

2026-07-13T13:47:40Z

Vsc: /* myApps */

== Applies To ==
* innovaphone IP270
* Firmware V16r1final 1610869 onwards

== Requirements ==
* innovaphone PBX with at least firmware 16r1final 1610869
* innovaphone App Platform with Devices and Users Application with at least firmware 16r1final 1610869
* IP270 firmware with at least version 16r1final 1610869
* PhonePlatform with at least build 2165
* PBX-Port-license (once per user)
* App(softphone)-License (Order Number: 02-00050-004) and App(phone)-License (Order Number: 02-00050-005) required (once per user)
* optional app licenses (once per user)

== Concept ==
myApps-powered phone for use with the innovaphone PBX

New hardware running a Yocto-based Linux distribution and hosting a native myApps IP270 client

Telephony via the myApps-Softphone-application provided by the innovaphone PBX

Additional services of the myApps application platform

== Features ==
=== myApps-Features ===
See respective column for IP270 in [[Reference16r1:Concept_myApps_platform_services#Features|myApps-platform services]].

=== Telephony-Features ===
See columns for IP270 in [[Reference16r1:Concept_App_SoftphoneApp#Features|myApps-SoftphoneApp features]].

=== Headphone support ===
myApps-IP270 supports use of [[Reference9:Concept_USB_Headset|USB devices known for innovaphone desk phones]].

== Configuration ==
=== Start ===
The IP270 is factory-configured as a DHCP client and obtains an IP address from a DHCP server—if available—via the LAN connection.

When the device starts up, myApps launches automatically and offers the following configuration options upon first startup after delivery:
* Provisioning Code input field
* Start provisioning
* Skip provisioning

Text input after a factory reset or upon delivery can be performed using the [[#On-screen keyboard|onscreen keyboard]] or the device’s hardware keypad.

After successful provisioning, this page is no longer displayed.

The device can be reset to factory settings by performing a power cycle while holding down the Home button until the LED stops flashing. This resets the home screen to the provisioning state and disables SSH login and remote browser debugging.

=== Automatic Provisioning (Recommended) ===
When the device is started for the first time after delivery or factory reset, it displays the provisioning page, where a provisioning code can be entered.

The required provisioning code can be generated either by the administrator via UsersAdmin or by the user themselves via Profiles. In this process, the device is set up as a '''standard innovaphone phone'''.
The generated provisioning code can be entered on the device via the provisioning page.

After the provisioning code has been successfully entered, the device is added to Devices and assigned to the user. The myApps login page is displayed and the device may attempt to load latest firmware. The LED flashes during this process.

The device automatically reboots after approx. 5 minutes.

Afterwards, externally connected input devices such as a mouse and keyboard can be used for myApps login and navigation.

In the user object, a device entry in the format “<ip270-mac> | Phone IP270, Softphone IP270 | phone,softphone” is created.

Upon successful connection to the server, the user’s login credentials can be entered.

=== Manual Configuration ===
==== Domain Assignment ====
After the device starts up, skip the provisioning process and go to “Change Server” on the myApps login screen.

There, select “Platform Setup” and enter your own Sysclient URL under / CONFIG / Sysclient URL.

Adapt the URL to your own domain in the following format

wss://<ap>.<domain>/<domain>/devices/sysclients

After confirming with Set, the device MAC appears in Devices and can be renamed and categorized there by the administrator.

==== User Assignment ====
* The administrator creates the device for the respective user via UsersAdmin
* A device entry is made in the User Object in the following format: HW-ID | Name1, Name2 | softphone,phone
* The HW-ID is the device MAC in the format 00903365xxxx, where xxxx are the last 4 digits of the serial number on the back label
* Name1 (e.g. Softphone IP270) identifies the SoftphoneApp. This must be set as the default telephony application on the IP270. It does not need to be visible on the home screen.
* Name2 (e.g. Phone IP270) identifies the PhoneApp, which allows the IP270 to be controlled from a PC. This must be launched on the PC.

=== myApps ===
Log in to myApps via the login screen using the on-screen keyboard.
If the on-screen keyboard doesn't disappear automatically afterwards, tap an empty field in myApps.
Depending on the PBX settings, two-factor authentication may be required.

The "Softphone IP270" mandatorily must be set as the default telephony application.
 It is recommended to set the SoftphoneApp as focus application or to pin it.

==== Settings ====
* Lock: Lock screen manually
* Default Apps: "Softphone IP270" as telephony application
* More:
** Display: Backlight brightness for active and standby modes, power-saving options with display switch-off for adjustable start and end times
** Audio: Volume settings for ringtone, handset, speakerphone and headphone. Use with caution.
** Lockscreen: Pin code and timeout in minutes, three different c-lock screens, emergency number list.
** Trace: Definition of trace flags for error analysis. The trace file can be downloaded via the administrative UI.

==== Task bar ====
* Loudspeaker symbol: indicates set handsfree volume
* Counter [optional]: indicates active firmware upgrade process
* Warning sign [optional]: indicates enabled SSH and/or Remotebrowser debug connection. To be set via Administrative UI in Devices.

==== On-screen keyboard ====
Alphabetical keyboard with access to additional symbols via the Cmp key (Compose):
* Cmp + . to access more punctuation
* Cmp + - or , to access 'mathematical' symbols (+,-,=,etc)
* Cmp + ' or 0 or 9 to access more brackets and quotes
* Cmp + a to access variants with diacritics like á,à,â,ä,
* Cmp + q to access emojis
* Keyboard Symbol + Shift (arrow key up) switch to the main special character (!, @, #...).
Return to alphabetical keyboard using the ABC key.

=== Administrative UI ===
Access via Devices or directly from the device via Platform Setup without myApps login. Following options are available:

* SHOW - display system status
** ENET : NIC status, IP@ and MAC
** OS-VERSION : used yocto build & publication date
** SshD : SSH login status
** SshD toggle : de/activate SSH login
** UIDbg : Remotebrowserdebug status
** UIDbg toggle : de/activate remote browser debugging

* UPDATE - manual update according to provided update server path
** myApps Update : available myApps version to be installed upon selection
** rootfs2 Update : available phone platform build to be installed upon selection

* CONFIG
** Sysclient URL : URL to system device application for device management. Format : wss://<ap>.<domain>/<domain>/devices/sysclients Confirm entry with SET

* DEBUG - to be used when instructed by support
** various menus to display dedicated function status.
** TRACES : trace output according to set trace flags. Upon selection download to default download folder and opened in standard editor.
** COREDUMP : list of present compressed core dump files. Upon selection download to default download folder. Download may take a while - do not select multiple times.

* REBOOT
** restart system : reboot complete device
** restart myApps : restart myApps only

== Firmware Update ==
Device is operated with its own device firmware and hosts a native myApps client on top of it.

In the [https://store.innovaphone.com/ innovaphone Store], the device firmware can be found under the "Phone Platform" tab.

In Devices, the device can access the device firmware via the domain upgrade using the URL https://store.innovaphone.com/release/download/phoneplatform.json.

The native IP270 myApps client is available in the Store under “Firmware” and is provided via https://store.innovaphone.com/release/download/firmware.json for the Devices upgrade.

During firmware update, the LED flashes. In the myApps taskbar, a yellow indicator displays firmware download progress in percent; a red indicator that the firmware is being installed.

== Factory Reset ==
Reset the device to factory settings is performed by power cycle whilst holding down the Home button until the LED stops flashing.

==Best practice use cases==
The device can be used locally or controlled remotely. Intended use cases are described below.

===Prerequisites===
* Audio device used must always be connected locally to the IP270
* Video devices can be connected to the IP270 and/or the PC

===Device Security===
It is recommended to set a personal PIN and lock timer via myApps/Settings/More.
After lock timer expiry and the device is locked automatically. Alternatively, the device can be locked manually via the myApps menu.
The lock timer is not interrupted by input from an external device such as mouce or keyboard.

As security measure in case of forgotten PIN, after six incorrect PIN entries the user is logged out and system switches back to login screen.

Unlock using the button on the screen and enter the unlock code with the phone’s hardware keypad or an external hardware keyboard.

===Audio Device Handling===
General prioritization of audio devices when answering a call
# Handset when lifted
# Headphone if available and handset is not used
# Speakerphone if no headphone is available and handset is not used

Switching audio devices during an active call:
* In the SoftphoneApp using the button
* On the device using the Microphone (= handset), Headphone, or Speaker buttons

=== Local Telephony ===
==== Outgoing calls ====
* Use the hardware keypad or SoftphoneApp to dial. When entering a number via the hardware keypad, the SoftphoneApp opens.
* When lifting the handset, outgoing call and all signaling tones are played through it.
* To route the call to a connected headphone, initiate the call using the headphone-button either on the headphone or the IP270.
* To play audio in hands-free mode, initiate the call using the speaker button.

==== Incoming calls ====
* When answering a call using the headphone-button either on the headphone or the IP270, the call is played through the headphone.
* When answering by lifting the handset, the call is played through the handset
* Answering via the speaker button on the device plays the call through the speaker in hands-free mode
* Alternatively, answer via the SoftphoneApp using the green handset icon. If no headphone is connected and the handset is on the cradle, the call is answered in hands-free mode.

====Video====
* Video playback takes place in myApps on the IP270 if a video camera is connected to the IP270-PhoneApp.
* No Remote Phone app may be open at the same time.

=== Remote Control via PC ===
IP270 can be remote controlled using the PhoneApp. It is recommended to set the IP270-PhoneApp as default telephony application on the PC.

==== Outgoing calls ====
* Dial via PhoneApp. A headphone connected to the IP270 is the default audio device; otherwise, the handset is used.
* During an active call, lifting the handset routes the call to the handset.
* Switch to speakerphone using the speakerphone button.

==== Incoming calls ====
* When answering a call using the headphone button either on the headphone or the IP270, the call is played through the headphone.
* When answering by lifting the handset, the call is played through the handset.
* Answering via the speaker button on the device plays the call through the speaker in hands-free mode.
* If the call is answered via the PhoneApp on the PC, it will be played through the headphone; otherwise the handset will be used.

====Video====
* If the remote PhoneApp is opened on the PC or defined as default telephony application, the video call will be displayed there.

== Troubleshooting ==
* Set trace options as told by innovaphone support via myApps-Client/More/Trace
* Collect traces at Devices/<IP270>/Debug TRACES and/or COREDUMPS . Tracefiles will be downloaded and opened automatically - stay patient and do not doubleclick!

== Known issues ==
* No file downloads from applications
* No LLDP-med support
* USB input devices are detected after the provisioning reboot
* USB ports are not intended for charging devices such as cell phones, power banks, or similar items
* An external resource, such as a document, opened in myapps can be closed using the hardware Home button

== Related Articles ==
[[Reference16r1:Concept_myApps_platform_services]]

https://wiki.innovaphone.com/index.php?title=Reference14r1:Concept_App_SoftphoneApp

https://wiki.innovaphone.com/index.php?title=Reference9:Concept_USB_Headset

https://wiki.innovaphone.com/index.php?title=Datasheet_IP270

Howto:Talkbase - FROX AG - 3rd Party Product

2026-07-13T09:43:40Z

Vsc: /* Category */

[[Image:Logo_talkbase_RGB_pos.png||200px|right]]
==Product Name==
[http://talkbase.com talkbase]

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

==Category==
[[Category:3rdParty PreviousProducts|{{PAGENAME}}]]
{{3rdParty PreviousProduct}}

==Description==
Talkbase is a client-server structured attendant console. Our solution is for the operator via web reachable, so no plugins or installation are required on the clients. For the communication between the endpoints WebRTC is used and for the registration at pbx the standard VoIP protocol SIP. The server software will be installed on windows based operating systems.

==Applies To==
Tested with talkbase Version 2.14 and Innovaphone Virtual Appliance V12r2 final (build 12514900)

==Functions==
Short summary of the most important features:

'''Data search'''
*Search Engine
*Phonetic search

'''Directories'''
*Add, edit and delete directory entries
*Synchronization of data with Active Directory
*Notes
*Configurable column arrangement
*Flexible directory columns
*Tags (Keywords)
*Talkbase absences
*Calendar information from MS Exchange
*Support for multiple directories
*Configurable colors and icons
*Favorites

'''Call Handling'''
*Automated call distribution
*Parallel ringing
*Automatic caller identification
*Consult calls
*Blind transfers
*Direct dialing
*Call picking from queue
*Hold calls
*Mute
*Toggle between caller and callee
*Recall support on no answer
*Time-based forwarding of calls in the queue
*Beep when a new call is in the queue
*Reject call
*Longest idle time
*Park calls

'''Status Information'''
*Status display of logged-in operators
*Status display of all main numbers

'''Options'''
*Notifications and music while queued
*Music on hold
*Pause function for operators
*Active Directory based user management
*Multilingual (English and German)
*Automatic login (remember me function)
*WebRTC
*Personal logbook
*Centralized call journal
*Customizable key shortcuts for all functions
*Management of opening hours and forwardings
*E-mail templates for notifications
*Single Sign On (SSO) with Active Directory
*Alarming
*Temporarily redirect main number
*Modify call forwarding settings of users
*Change operator group in rush hour
*Caller history

==Installation==
please contact us at info@talkbase.com to get closer information about the installation procedure.

==More Information==
If you are more interested in talkbase and the used technologies check out our blog: https://blog.talkbase.com/

For a closer look at talkbase itself, visit our youtube channel: https://www.youtube.com/channel/UCkOMI-6ag7tTX3BPJn045rg

==Contact Details==
[[Image:Frox Icon O RGB.png]] [http://www.frox.ch FROX AG]

{|
| colspan=99 | Michael Rohr
|-
| colspan=99 | FROX AG
|-
| colspan=99 | Feldbachstrasse 80
|-
| colspan=99 | CH - 8634, Hombrechtikon
|-
| Tel: || +41 55 254 12 44
|-
| Mail: || [mailto:michael.rohr@frox.ch michael.rohr@frox.ch]
|}

Reference16r1:PBX/Objects/User

2026-07-09T07:24:44Z

Vsc: /* User / License / Apps */

With the User PBX object, the standard subscriber of the innovaphone PBX is configured.

The following tabs are available for configuration settings:

== General ==
General configuration options shared by all objects. For details refer to [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties|this page]].

These configuration settings can be applied either specifically to a user object or generically via a configuration template.

== User ==
Settings for this user object. Same meaning as for configuration templates [[{{NAMESPACE}}:PBX/Objects/Config_Template#Config|listed here]].

;Home Screen Apps: A user-dedicated comma separated list of applications to be displayed at myApps-homescreen. Application names must match with respective App-object-name. Definition syntax follows this [[{{NAMESPACE}}:Concept_myApps#Storage_and_format|format]] and typically is made via myApps or UsersAdminApp.

== License ==
License settings for this user object. Same meaning as for configuration templates [[{{NAMESPACE}}:PBX/Objects/Config_Template#License|explained here]].

== Apps ==
Apps available to this user. Can also be [[{{NAMESPACE}}:PBX/Objects/Config_Template#Apps|distributed]] via configuration templates.

== DECT ==
The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:
* '''Gateway:''' The system name (Name) of the IP DECT device.
* '''Display:''' A variable text that is output on the IP DECT handset display.
* '''IPEI:''' The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
* '''AC (Access Code):''' It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.

Reference16r1:PBX/Objects/Config Template

2026-07-09T07:01:13Z

Vsc: Created page with "Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the from the '''Config Template''' list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template. Config templates can be nested by assigning a previously defined config template to another config template. Referenced templates must not reference other templates..."

Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the from the '''Config Template''' list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template.

Config templates can be nested by assigning a previously defined config template to another config template. Referenced templates must not reference other templates in turn (these will be ignored then).

'''Note'''
When editing a Config template the changes will be applied to the User Objects that have this config template but if you delete the Config Template and create a new Template with the same Name and different settings no changes will be done on the User Object.
So in that case you need to go to the User Object and delete the previous Config Template and then select again the config template that looks the same since have the same name (Select Blank, click Apply, Select Config Template and click Apply/OK).

== General ==

See [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties]] for generic object properties.

== Config ==

The following configuration options can be configured thru templates:

;Filter: The filter configured here restricts the numbers which may be called by a endpoint registered to this object

;Diversion Filter: The filter configured here restricts the creation of call forwarding to matching numbers that can be set up by an H.323 endpoint registered to this object

;Block Execution: If enabled, the ''Diversion Filter'' prevents the execution of the call forwarding to matched numbers. This option is available at the User Object only.

;Response Timeout: Overrides the PBX global response timeout for this object

;Busy on ... Calls: If this value is set a call to this user object is rejected with User Busy if n or more calls are active on this user object. If the object is of the gateway type (Gateway, Trunk, ...) calls from endpoints registered to this object are rejected as well in this case. The switch will have no effect if the option 'Twin Phones' is set.

;External UC: A '''Long Name''' of a External UC object can be configured here. Presence Information for this user is then obtained from a UC Server which is registered to this Object. Instant messaging Sessions for this user are also forwarded to the External UC interface.

;Messages: define use of [[Reference13r1:PBX/Objects/Messages|messaging]]

;Push: Name of the Push object that should be used for push notifications towards myPBX for mobile phones.

;No Inband Disconnect: If this checkmark is set, a call disconnect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediately without the inband information being sent.

;Store Phone Config: If this checkmark is set, the PBX stores the config of the phone. The first time a phone registers the predefined config at the PBX is sent to the phone even if it is empty. Then the local config stored at the phone is merged into the received config and the result is returned to the PBX. After this the local config is deleted and no local config is stored on the phone anymore. Later config changes on the phone will be sent to the PBX and stored there. On registration the PBX sends the complete config to the phone again.

;Discard Phone Config: If this checkmark is set in addition to ''Store Phone Config'' the local config stored at the phone is discarded but not returned to the PBX when the phone registers the first time, i.e. the phone is configured with the config predefined at the PBX. This checkmark should be activated during normal PBX operation. When [[Howto:Firmware_Upgrade_V7_V8#Store_Phone_Config | migrating from a system with phone based config to PBX based config]] it might be required to disable the ''Discard Config on Phone'' flag. After the migration from local stored to pbx stored phone config is complete, the ''Discard Config on Phone'' should be re-enabled.

;Twin Phones: With this checkmark the twin phone mode is enabled for this object. Checkmark off (is not set) means that any additional calls a user may receive while in an existing call will signal on any other phone on which the user has an active registration. Checkmark on (is set) means if one phone is busy any additional calls are sent to the busy phone only (as call waiting) and not to the other phones on which the user may have active registrations. If "Call Waiting" is disabled on the busy phone a second call gets a busy tone and a missed call is displayed when the active call is terminated.

;Reject ext. Calls: If this checkmark is set a call from an external source to this object is rejected. A calling party numbering plan private is used to decide that the call is coming from an internal source. An invalid number destination is executed for calls rejected because of this.

;Do Not Disturb: Reject any incoming calls with Busy.

;Hide Connected Endpoint: With this check the destination to which a call is forwarded can be hidden to the caller. Helpful when e.g. forwarding a call to a non-public number.

;Call forward based on Presence: Use presence as indicator to forward calls to set destinations. When this checkmark is set, incoming calls are forwarded directly to targets defined as CFB if the initially called extension has set an active presence of type Busy/DND and targets defined as CFNR for presence of type Away. More details [[Courseware:IT_Advanced_-_More_on_advanced_PBX_object_properties_and_behavior#Forwardings_based_on_presence|see here]].

;Call forward on myApps offline: If this checkmark is set, a CFNR will be executed without delay if no myApps client is online for the user. In case of a myApps on a smartphone, the push will not be triggered if the smartphone is in standby and the call will follow the configured CFNR immediately.

;Onboarding seen: Tells if the user has already seen the onboarding page in myApps. If set, the page will not be displayed again, if the user logs in to myApps. The checkmark is automatically set after displaying the onboarding page.

== Licenses ==
Inheritated licenses from another template are visible and additional licenses for this template can be set with a check or excluded with an uncheck.

See [[{{NAMESPACE}}:PBX/Objects#License]] for license details.
== Apps ==
Inheritated Apps from another template are visible and additional Apps for this template can be set with a check or excluded with an uncheck.

Reference15r1:PBX/Objects/Config Template

2026-07-09T06:55:30Z

Vsc: /* Configuration Options available for Templates */

Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the from the '''Config Template''' list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template.

Config templates can be nested by assigning a previously defined config template to another config template. Referenced templates must not reference other templates in turn (these will be ignored then).

'''Note'''
When editing a Config template the changes will be applied to the User Objects that have this config template but if you delete the Config Template and create a new Template with the same Name and different settings no changes will be done on the User Object.
So in that case you need to go to the User Object and delete the previous Config Template and then select again the config template that looks the same since have the same name (Select Blank, click Apply, Select Config Template and click Apply/OK).

See [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties]] for generic object properties.

== Configuration Options available for Templates ==

The following configuration options can be configured thru templates:

;Filter: The filter configured here restricts the numbers which may be called by a endpoint registered to this object

;Diversion Filter: The filter configured here restricts the creation of call forwarding to matching numbers that can be set up by an H.323 endpoint registered to this object

;Block Execution: If enabled, the ''Diversion Filter'' prevents the execution of the call forwarding to matched numbers. This option is available at the User Object only.

;Response Timeout: Overrides the PBX global response timeout for this object

;Busy on ... Calls: If this value is set a call to this user object is rejected with User Busy if n or more calls are active on this user object. If the object is of the gateway type (Gateway, Trunk, ...) calls from endpoints registered to this object are rejected as well in this case. The switch will have no effect if the option 'Twin Phones' is set.

;External UC: A '''Long Name''' of a External UC object can be configured here. Presence Information for this user is then obtained from a UC Server which is registered to this Object. Instant messaging Sessions for this user are also forwarded to the External UC interface.

;Messages: define use of [[Reference13r1:PBX/Objects/Messages|messaging]]

;Push: Name of the Push object that should be used for push notifications towards myPBX for mobile phones.

;No Inband Disconnect: If this checkmark is set, a call disconnect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediately without the inband information being sent.

;Store Phone Config: If this checkmark is set, the PBX stores the config of the phone. The first time a phone registers the predefined config at the PBX is sent to the phone even if it is empty. Then the local config stored at the phone is merged into the received config and the result is returned to the PBX. After this the local config is deleted and no local config is stored on the phone anymore. Later config changes on the phone will be sent to the PBX and stored there. On registration the PBX sends the complete config to the phone again.

;Discard Phone Config: If this checkmark is set in addition to ''Store Phone Config'' the local config stored at the phone is discarded but not returned to the PBX when the phone registers the first time, i.e. the phone is configured with the config predefined at the PBX. This checkmark should be activated during normal PBX operation. When [[Howto:Firmware_Upgrade_V7_V8#Store_Phone_Config | migrating from a system with phone based config to PBX based config]] it might be required to disable the ''Discard Config on Phone'' flag. After the migration from local stored to pbx stored phone config is complete, the ''Discard Config on Phone'' should be re-enabled.

;Twin Phones: With this checkmark the twin phone mode is enabled for this object. Checkmark off (is not set) means that any additional calls a user may receive while in an existing call will signal on any other phone on which the user has an active registration. Checkmark on (is set) means if one phone is busy any additional calls are sent to the busy phone only (as call waiting) and not to the other phones on which the user may have active registrations. If "Call Waiting" is disabled on the busy phone a second call gets a busy tone and a missed call is displayed when the active call is terminated.

;Reject ext. Calls: If this checkmark is set a call from an external source to this object is rejected. A calling party numbering plan private is used to decide that the call is coming from an internal source. An invalid number destination is executed for calls rejected because of this.

;Do Not Disturb: Reject any incoming calls with Busy.

;Hide Connected Endpoint: With this check the destination to which a call is forwarded can be hidden to the caller. Helpful when e.g. forwarding a call to a non-public number.

;Call forward based on Presence: Use presence as indicator to forward calls to set destinations. When this checkmark is set, incoming calls are forwarded directly to targets defined as CFB if the initially called extension has set an active presence of type Busy/DND and targets defined as CFNR for presence of type Away. More details [[Courseware:IT_Advanced_-_More_on_advanced_PBX_object_properties_and_behavior#Forwardings_based_on_presence|see here]].

;Call forward on myApps offline: If this checkmark is set, a CFNR will be executed without delay if no myApps client is online for the user. In case of a myApps on a smartphone, the push will not be triggered if the smartphone is in standby and the call will follow the configured CFNR immediately.

;Onboarding seen: Tells if the user has already seen the onboarding page in myApps. If set, the page will not be displayed again, if the user logs in to myApps. The checkmark is automatically set after displaying the onboarding page.

;Licenses Tab:
Inheritated licenses from another template are visible and additional licenses for this template can be set with a check or excluded with an uncheck.

;Apps Tab:
Inheritated Apps from another template are visible and additional Apps for this template can be set with a check or excluded with an uncheck.

Reference15r1:PBX/Objects/User

2026-07-09T06:52:33Z

Vsc: Reverted edits by Vsc (talk) to last revision by Elievens

With the User PBX object, the standard subscriber of the innovaphone PBX is configured.

;Do Not Disturb: No calls are sent to the user if set. Can be set by 'External UC' applications (e.g. Estos Procall)

;Hide Connected Endpoint: In some cases it is desirable not to reveal the final destination of a call to a caller. For example a call centre agent should not be called directly by the customer or to suppress call forwarding destinations.

;Call forward based on Presence: enables use of forwarding based on presence. Typically set via ProfileApp. Feature description [[Courseware:IT_Advanced_-_More_on_advanced_PBX_object_properties_and_behavior#Forwardings_based_on_presence|see here]]

;Call forward on myApps offline: If this checkmark is set, a CFNR will be executed without delay if no myApps client is online for the user. In case of a myApps on a smartphone, the push will not be triggered if the smartphone is in standby and the call will follow the configured CFNR immediately.

;Onboarding seen: The information if a user has already seen the onboarding video.

;Home Screen Apps: Comma separated list of applications to be displayed at myApps-homescreen. New lines are indicated by ':' . Application names must match with respective App-object-name. Definition typically is made via myApps or UsersAdminApp.

In addition to these options, all those that can be set for a [[{{NAMESPACE}}:PBX/Objects/Config_Template]] object can be set for a ''User'' object too.

== General Configuration Options ==

The information about general configuration options shared by all objects can be found at [[{{NAMESPACE}}:PBX/Objects]].

== Configuration Options which can be defined by a Template ==

Some of the configuration options of a user object can be defined by Templates. More information about these options can be found at [[{{NAMESPACE}}:PBX/Objects/Config_Template]]

== DECT configuration options ==

The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:
* '''Gateway:''' The system name (Name) of the IP DECT device.
* '''Display:''' A variable text that is output on the IP DECT handset display.
* '''IPEI:''' The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
* '''AC (Access Code):''' It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.

Reference16r1:PBX/Objects/User

2026-07-09T06:52:09Z

Vsc: Created page with "With the User PBX object, the standard subscriber of the innovaphone PBX is configured. The following tabs are available for configuration settings: == General == General configuration options shared by all objects. For details refer to this page. == User / License / Apps == These configuration settings can be applied either specifically to a user object or generically via a configuration template. Details to the..."

With the User PBX object, the standard subscriber of the innovaphone PBX is configured.

The following tabs are available for configuration settings:

== General ==
General configuration options shared by all objects. For details refer to [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties|this page]].

== User / License / Apps ==
These configuration settings can be applied either specifically to a user object or generically via a configuration template.
Details to these options can be found at [[{{NAMESPACE}}:PBX/Objects/Config_Template|the configuration template description]].

;Home Screen Apps: User-dedicated comma separated list of applications to be displayed at myApps-homescreen. Application names must match with respective App-object-name. Definition syntax follows this [[{{NAMESPACE}}:Concept_myApps#Storage_and_format|format]] and typically is made via myApps or UsersAdminApp.

== DECT ==
The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:
* '''Gateway:''' The system name (Name) of the IP DECT device.
* '''Display:''' A variable text that is output on the IP DECT handset display.
* '''IPEI:''' The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
* '''AC (Access Code):''' It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.

Reference15r1:PBX/Objects/User

2026-07-09T06:41:27Z

Vsc: /* User / License / Apps */

With the User PBX object, the standard subscriber of the innovaphone PBX is configured.

The following tabs are available for configuration settings:

== General ==
General configuration options shared by all objects. For details refer to [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties|this page]].

== User / License / Apps ==
These configuration settings can be applied either specifically to a user object or generically via a configuration template.
Details to these options can be found at [[{{NAMESPACE}}:PBX/Objects/Config_Template|the configuration template description]].

;Home Screen Apps: User-dedicated comma separated list of applications to be displayed at myApps-homescreen. Application names must match with respective App-object-name. Definition syntax follows this [[{{NAMESPACE}}:Concept_myApps#Storage_and_format|format]] and typically is made via myApps or UsersAdminApp.

== DECT ==
The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:
* '''Gateway:''' The system name (Name) of the IP DECT device.
* '''Display:''' A variable text that is output on the IP DECT handset display.
* '''IPEI:''' The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
* '''AC (Access Code):''' It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.

Reference15r1:PBX/Objects/User

2026-07-09T06:40:26Z

Vsc: /* User / License / Apps */

With the User PBX object, the standard subscriber of the innovaphone PBX is configured.

The following tabs are available for configuration settings:

== General ==
General configuration options shared by all objects. For details refer to [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties|this page]].

== User / License / Apps ==
These configuration settings can be applied either specifically to a user object or generically via a configuration template.
Details to these options can be found at [[{{NAMESPACE}}:PBX/Objects/Config_Template|the configuration template description]].

;Home Screen Apps: User-dedicated comma separated list of applications to be displayed at myApps-homescreen. Syntax follows this [[{{NAMESPACE}}:Concept_myApps#Storage_and_format|format]]. Application names must match with respective App-object-name. Definition typically is made via myApps or UsersAdminApp.

== DECT ==
The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:
* '''Gateway:''' The system name (Name) of the IP DECT device.
* '''Display:''' A variable text that is output on the IP DECT handset display.
* '''IPEI:''' The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
* '''AC (Access Code):''' It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.

Reference15r1:PBX/Objects/User

2026-07-09T06:37:09Z

Vsc:

With the User PBX object, the standard subscriber of the innovaphone PBX is configured.

The following tabs are available for configuration settings:

== General ==
General configuration options shared by all objects. For details refer to [[{{NAMESPACE}}:PBX/Objects#General_Object_Properties|this page]].

== User / License / Apps ==
These configuration settings can be applied either specifically to a user object or generically via a configuration template.
Details to these options can be found at [[{{NAMESPACE}}:PBX/Objects/Config_Template|the configuration template description]].

;Home Screen Apps: User-dedicated comma separated list of applications to be displayed at myApps-homescreen. New lines are indicated by ':' . Application names must match with respective App-object-name. Definition typically is made via myApps or UsersAdminApp.

== DECT ==
The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:
* '''Gateway:''' The system name (Name) of the IP DECT device.
* '''Display:''' A variable text that is output on the IP DECT handset display.
* '''IPEI:''' The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
* '''AC (Access Code):''' It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.

Reference9:PBX/Objects/Edit Profiles

2026-07-09T05:55:37Z

Vsc:

You can set various profiles per user, for each profile you can have a [[Reference9:Concept_myPBX#Contacts |buddy list (aka contacts)]] in the myPBX/myApps client.

'''Name''' Name of the profile, the myPBX/myApps user can choose from profile names if more are configured.

== Properties of a Profile==

{|
|valign=top nowrap=true|'''Name'''
|Name of the user that shows up in the buddy list
|-
|valign=top nowrap=true|'''No'''
|Number of that user that shows up in the buddy list
|
|-
|valign=top nowrap=true|'''Display'''
|How the user should be named in the buddy list
|
|-
|valign=top nowrap=true|'''Extern'''
|If its not an user from the PBX choose '''tel''' for a external phone number, or '''sip''' for an external sip user via federation
|
|-
|valign=top nowrap=true|'''Presence'''
|If you want to monitor the users presence state (that is only for external users), for internal you see the presence state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federation
|-
|valign=top nowrap=true|'''Dialog'''
|If you want to monitor the users call state (that is only for external users), for internal you see the call state if you have the [[Reference9:PBX/Objects/Edit_Allow |access rights]], used for federation
|-
|}

* Note: For internal users configure either name or number. If the display is different to the one from the user configuration, only the name must be configured.

Reference16r1:Gateway/GK/GW

2026-07-08T13:32:41Z

Vsc: /* Interface (VoIP Interfaces) */

Below is an overview of all the gateway's configurable VoIP interfaces:
* '''Interface:''' The name of the interface. Clicking this name opens a popup page, on which all settings can be made. The settings are described in more detail in the following chapter "[[#Interface .28VoIP Interfaces.29|Administration/Gateway/VOIP/Interface (VoIP interfaces)]]".
* '''CGPN In, CDPN In, CGPN Out, CDPN Out:''' Precise details on CGPN In, CDPN In, CGPN Out and CDPN Out mappings are contained in the chapter entitled "[[#CGPN.2FCDPN Mappings|Administration/Gateway/Interfaces/CGPN-CDPN Mappings]]" further up in the text.
* '''Registration:''' If a terminal has successfully registered with a gateway, then this is indicated in this column through specification of the IP address <Name of the VoIP interface:Call number:IP address>.

== Interface (VoIP Interfaces) ==
Clicking the relevant VoIP interface (GW1-12 <Name of the VoIP interface>) in the Interface column opens a popup page, on which the VoIP interfaces can be individually configured. Like the PBX objects, this popup page also contains standard entry fields that occur, more or less, in all VoIP interfaces.

These standard fields are:
* '''Name:''' The descriptive name of the VoIP interface.
* '''Disable:''' A checked check box disables the relevant VoIP interface.
* '''Protocol:''' The protocol to be used, that is, H.323 or SIP. Depending on which protocol is used, the set-up of the entry fields changes.
* '''Mode:''' Describes the mode of registration. Possible registration modes are:
# Gateway without Registration - Logs the VoIP interface (gateway) on to the configured gatekeeper without a registration.
# Register as Endpoint - Registers a VoIP terminal with the configured gatekeeper.
# Register as Gateway - Registers a VoIP gateway with the configured gatekeeper.
# Gatekeeper/Registrar - Is required for managing all gatekeeper registrations on a gateway. (is only visible when running in test-mode or if a [[Reference:Gatekeeper_License|gatekeeper license]] is available)
# ENUM - Is used to register an ENUM connection with the relevant interface.
* '''Gatekeeper Address (primary):''' The primary Gatekeeper IP address at which the terminal or gateway is to register via the relevant interface. Only necessary for modes 2 and 3. (IPv6 addresses must be enclosed in square brackets)
* '''Gatekeeper Address (secondary):''' The alternative gatekeeper IP address at which the terminal or gateway is to register via the relevant interface, if registration with the primary gatekeeper fails. Only necessary for modes 2 and 3. (IPv6 addresses must be enclosed in square brackets)
* '''Local Domain:''' Replaces the existing system/domain name (for H323 federation only).
* '''Mask:''' By specifying a network mask, incoming calls can be filtered. Specification of the network mask 255.255.0.0 therefore allows incoming calls on the relevant interface for terminals from the IP address range 192.168.0.0 - 192.168.255.255 .
* '''Gatekeeper Identifier:''' It is also sufficient to specify only the gatekeeper ID. Every gatekeeper in a network can be identified by means of its own gatekeeper ID, so that several gatekeepers can be operated in a network, with each terminal nevertheless identifying the correct gatekeeper by means of Gatekeeper Discovery (uses the multicast address 224.0.1.41).
* '''STUN SERVER:''' The STUN server name or IP address must be configured if this device has no public IP address while the SIP server is accessible under a public IP address. The value is given by the SIP provider or administrator (for example, stun.xten.com or 64.69.76.23). You can choose any STUN server; it does not necessarily have to correspond to the one of the SIP provider.
* '''Local Signalling Port:''' Signalling Port used by the Interface.
* '''SIP - Register as Gateway/Endpoint:'''
** '''Remote Domain (SIP Only):''' SIP Domain of the remote SIP Server to register (often equal to the SIP Proxy).
** '''Proxy (SIP Only):''' DNS name or IP address of the SIP proxy where SIP messages (REGISTER,INVITE,etc) are to be sent to. Proxy can be omitted if domain part of AOR can be used as remote signaling destination and it's set at Remote Domain.
* '''SIP - Gateway without Registration:'''
** '''Remote Domain (SIP Only):''' Check the Domain/IP Address on the SIP URI "FROM" field and removes it if match.
** '''Local Domain (SIP Only):''' Check the Domain/IP Address on the SIP URI "TO" field and removes it if match.
** '''Proxy (SIP Only):''' DNS name or IP address of the SIP proxy where SIP messages (INVITE,etc) are to be sent to, this field it's mandatory.
** '''Filter Incoming Calls (SIP Only):''' Accept Incoming Call on this interface only if the domain part of the "To:" field SIP URI matches the ''Local Domain'' configured. If not accepted, the call may still be accepted by another interface
* '''H323/TLS - Gateway without Registration
** '''Federation:''' Turns on open federation, which means the domain part of a destination name is used to look up the remote gateway in the DNS
** '''Veriyfy Cert:''' If set, the remote ceritficate on an incoming call is verified against the domain part of the source name

=== Authorization section ===
In the '''Authorization''' section, you can store a password for the VoIP interface.
* '''Password / Retype:''' The security of the registration can be raised by specifying a password (Password). The password must be confirmed (Retype).

=== Alias List section ===
In the '''Alias List''' section, you specify the call name (H.323) and the call number (E.164) of the relevant registration. For VoIP end points, you should define the assigned direct dialling number or MSN as the E.164 address, and the name as the H.323 name. For VoIP gateways it is sufficient to define the name.
* '''Name:''' The H.323 name.
* '''Number:''' The E.164 call number.

=== Coder Preferences section ===
The standard entry fields in the '''Coder Preferences''' section were already described in chapter "[[Reference:Administration/Gateway/Interfaces#Interface .28ISDN.2C SIP .26 virtual interfaces.29|Administration/Gateway/Interfaces/Interface (physical and virtual interfaces)]]".

=== Media Properties ===
The standard entry fields in the '''Media Properties''' section were already described [[{{NAMESPACE}}:Gateway/Interfaces/Media_Properties | Media Properties]].

=== H.323 Interop Tweaks section ===
In addition to the standard fields, several advanced settings are available in the '''H.323 Interop Tweaks''' section. They are normally not necessary and are merely used to solve compatibility problems with some PBXs:
* '''No Faststart:''' The H.245 faststart procedure is enabled as standard. Outgoing calls are made with faststart, incoming calls with faststart are answered with faststart. A checked check box disables the H.245 faststart procedure. Outgoing calls are made without faststart, incoming calls with and without faststart are answered without faststart.
* '''No H.245 Tunneling:''' The H.245 tunneling procedure is enabled as standard. The voice data connection is negotiated in the TCP signalling connection*) already available. This can be advantageous in connection with NAT and firewalls.
A checked check box disables the H.245 tunneling procedure, meaning that a separate TCP connection is set up for this negotiation. This applies to the signalling connection leading out of the gatekeeper.
* '''Suppress HLC:''' A checked check box disables the transmission of HLC (High Layer Compatibility) information elements.
* '''Suppress FTY:''' A checked check box disables the transmission of FTY (Facility) information elements.
* '''Suppress Subaddress:''' A checked check box disables the transmission of Subaddress information elements.
*) From a technical viewpoint, the H.245 protocol does not establish its own TCP connection,
but shares the H.225 TCP connection.

=== SIP Interop Tweaks section ===
Miscellaneous interoperability options for SIP.
{|
|valign=top nowrap=true|'''Proposed Registration Interval'''
|Set in seconds, default is 120 seconds
|-
|valign=top nowrap=true|'''Accept INVITE's from Anywhere'''
|If disabled, registered interfaces will reject INVITE's not coming from the SIP server with "305 Use Proxy".
|-
|valign=top nowrap=true|'''Enforce Sending Complete'''
|Affects handling of "484 Address Incomplete" responses. If enabled and "484 Address Incomplete" is received, the call is cleared. If not enabled and "484 Address Incomplete" is received, the call is retained and re-initiated in case of new dialing digits.
|-
|valign=top nowrap=true|'''No Video'''
|Removes Video Capabilities from outgoing media offer.
|-
|valign=top nowrap=true|'''No Early Media'''
|Ignore any SDP answer received before final connect response. (Affects only outgoing SIP calls)
|-
|valign=top nowrap=true|'''No Inband Information on Error'''
|Controls interworking of Q.931 DISC message. If this option is set, DISC message is always interworked into BYE request.
|-
|valign=top nowrap=true|'''No Inband Disconnect'''
|TBD.
|-
|valign=top nowrap=true|'''No Remote Hold Signaling'''
|Disables interworking of "inactive" into RemoteHold (affects connected SIP calls only).
|-
|valign=top nowrap=true|'''Take Refer-To URI as Remote Target URI'''
|If enabled: When REFER is received and transfer is executed by the Gateway application and a new INVITE is sent, the Request-URI of this INVITE matches the URI that has been received in Refer-To header in REFER. 
If not enabled: The Request-URI of the outgoing INVITE is created by usual means. Userpart of the Request-URI usually contains the CDPN as provided by Gateway application.
|-
|valign=top nowrap=true|'''To Header when Sending INVITE'''
|Affects only outgoing diverted calls . '''Called Party''': If set we write CDPN into To header of outgoing INVITE (and DGPN into History-Info header). '''Original Called Party''': If set we write the DGPN into To header of outgoing INVITE (and CDPN into Request-URI).
|-
|valign=top nowrap=true|'''From Header when Sending INVITE'''
|Controls the local URI (From header) of outgoing calls. Applys to registered interfaces only. '''Fixed AOR''': Fixed AOR is used as From-URI regardless of the actual calling party number. '''AOR with CGPN as Display''': Fixed AOR is used as From-URI and calling party number is added as display string. '''CGPN in user part of URI''': Variable From-URI with actual calling party number.
|-
|valign=top nowrap=true|'''Identity Header when Sending INVITE'''
|Controls the identity header (P-Preferred-Identity, P-Asserted-Identity and Remote-Party-Id). '''CGPN in user part of URI''': Variable From-URI with actual calling party number. '''Fixed AOR''': Fixed AOR is used as Identity-URI regardless of the actual calling party number.
|-
|valign=top nowrap=true|'''Reliability of Provisional Responses'''
|Controls the support of PRACK (RFC-3262). '''Supported''': Supported as optional extension. '''Required''': Required as mandatory extension. '''Disabled''': Hide support for PRACK extension.
|-
|valign=top nowrap=true|'''Microsoft Presence Format'''
|Enables special Microsoft Presence format/scheme, only used for SIP Federation with Lync 2013.
|}

== CGPN/CDPN Mappings ==
A detailed description may be found in the chapter entitled "[[Reference:Administration/Gateway/Interfaces#CGPN.2FCDPN Mappings|Administration/Gateway/Interface/CGPN-CDPN Mappings]]".

Howto:KIAMO - Conecteo - 3rd Party Product

2026-07-08T12:29:29Z

Vsc: /* Category */

[[Image:Kiamo-logo.jpg‎||200px|right]]

==Product Name==

[http://kiamo.eu/ KIAMO]

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

Vendor test report and configuration hints were received September 19, 2018

==Category==
[[Category:3rdParty PreviousProducts|{{PAGENAME}}]]
{{3rdParty PreviousProduct}}

==Vendor==
A major provider in the market of customer interaction management solutions for contact centres, Conecteo offers Kiamo, the native multi-channel software solution. Kiamo CAPTURES, PRIORITISES and DISTRIBUTES all multimedia flows depending on business rules, availability and employee skills.
Designed for all users, the solution stands out from the competition due to its rich functionality, ergonomic design and reliability. Kiamo responds to the problems of Customer Relations managers who need a unified customer strategy to improve their quality of service and relational performance.

'''Deloitte Technology Fast50 winner'''
Conecteo bases its growth and durability on a solid team, having developed unique expertise in the implementation of contact centres within major companies and government departments, in heterogeneous environments.

'''ISTQB Certification'''
The Conecteo Quality team signed a partnership agreement with ISTQB® (International Software Testing Qualifications Board) due to its maturity regarding software tests, obtained through individual certifications. The ISTQB® partner programme recognises organisations which have adopted a qualitative approach to software testing. ISTQB® certifications are recognised internationally and act as testing reference.
The signature of this partnership confirms Conecteo's objective: deliver reliable, stable and efficient software.

[http://www.kiamo.eu Read more.]

==Product Description==
Kiamo is an open solution which is deployed rapidly and securely, without having to adapt the telephone architecture or information system already in use in your company.

Kiamo has numerous native and customizable connectors (CRM, ERP, DB, Quality Monitoring, etc.) allowing it to interface with the main Customer Relations business software (SAP, Salesforces, Coheris, MS Dynamics, etc.).
Kiamo is available in hosted or on-premise mode.
Via a single interface, Kiamo centralizes, prioritizes and distributes all inbound and outbound interactions (calls, emails, live chat, social networks, Web, paper mail, etc.) between customers/prospects and the Customer Relationship center.
With its advanced and particularly ergonomic functionality and 100% multi-channel capacity, the Kiamo solution appeals to both large companies and SMEs. Easy to configure, Kiamo allows men and women working in contact centers to concentrate on their core business.
By streamlining response processes and focusing on automatic management and prioritization of the flows in customer relationship centers, Kiamo helps companies increase their productivity, guarantee customer response times and develop customer loyalty.
The Kiamo solution has been installed for several years in companies of all sizes involved in different lines of business. Based on its powerful native multi-channel engine allowing it to manage hundreds of thousands of interactions simultaneously, Kiamo presents itself as the daily productivity tool of contact center players in SMEs and large companies.

==Features==

Cross-channel Contact Center application (Voice/Video, SMS, Social Networks, Custom Medias, Chat, Email…)

[[Image:Kiamo-features.png]]

===Multichannel-ACD===
Kiamo is the basis of your Customer Relations. Kiamo's powerful flow distribution engine allows you to apply your relational strategy according to the following 4 steps:
*'''Multi-channel capture:''' of all your contact flows: voice, emails, files, paper mail, social networks, video messaging, back-office tasks, live chat.
*'''Scheduling:''' thanks to automatic management and prioritisation of all flows, Kiamo organises, sorts and prioritises these according to your strategy.
*'''Intelligent distribution:''' taking into account all your business rules and the skills and availability of your agents, Kiamo assigns each task to the most appropriate adviser.
*'''Measurement and management:''' You manage your activities in real time via customisable supervision interfaces and consolidated dashboards.

[[Image:Kiamo-ACD.png]]

===Cross-Channel platform===

Kiamo's native cross-channel platform allows advisers to deliver homogeneous messages irrespective of the channel used. The exhaustive customer data makes the advisers more efficient and improves the quality of exchanges.

==Tested Versions==
* Kiamo 6.5
* innovaphone PBX V12r2sr16

==Configuration==
English installation guide can be [[Media:Kiamo-guide.pdf|downloaded here]].

==Contact==
Conecteo

3 Allée Jacques Latrille,

33650 Martillac,

France

Phone: +33 (0)5 47 48 33 20

Web: http://kiamo.eu

Partner Apps

2026-07-08T05:49:14Z

Vsc:

myApps Partner applications

For an overview with brief description, refer to [https://www.innovaphone.com/en/products/software/overview-all-apps.html this page].

Please note that innovaphone itself does not provide any technical support for products and applications described here. This is exclusively provided by the third-party manufacturers themselves, who can be reached via the contact details mentioned in the articles.

===3rdParty Terminal Device Provisioning===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Terminal Devices
</DynamicPageList>
===Alarm Server Solutions===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Alarm Server
</DynamicPageList>
===App Development===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty App Development
</DynamicPageList>
===Call Recording===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Recording
</DynamicPageList>
===Contact Center Applications===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Contact Center Applications
</DynamicPageList>
===Cloud===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Cloud
</DynamicPageList>
===Conferencing / Video Systems===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Conferencing / Video Systems
</DynamicPageList>
===CTI and integrations===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty CTI and integrations
</DynamicPageList>
===Directory Services===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Directory Services
</DynamicPageList>
===Music on Hold===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty_Music_on_Hold
</DynamicPageList>
===Network Equipment (SBCs)===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Network Equipment
</DynamicPageList>
===Reporting / Monitoring===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty Reporting / Monitoring
</DynamicPageList>
===VoIPSystem Management===
<DynamicPageList>
ordermethod = sortkey
mode = unordered
order = ascending
category = Partner Apps
category = 3rdParty VoIPSystem Management
</DynamicPageList>

Howto:MobiApp - NewVoice

2026-07-08T05:47:58Z

Vsc: Vsc moved page Howto:MobiApp - NewVoice to Howto:MobiApp - NewVoice - Partner App

#REDIRECT [[Howto:MobiApp - NewVoice - Partner App]]

Howto:MobiApp - NewVoice - Partner App

2026-07-08T05:47:58Z

Vsc: Vsc moved page Howto:MobiApp - NewVoice to Howto:MobiApp - NewVoice - Partner App

[[File:NV Logo RGB 200px.jpg|right|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]
== Product Name ==
[[File:MobiApp NV RGB 100px.jpg|100x100px|mobiapp_nv_rgb_100px.jpg/|mobiapp_nv_rgb_100px.jpg/]]

[https://newvoiceinternational.com/mobiapp/ MobiApp] by NewVoice International

== Certification Status ==

{{Template:Compat_Status_referral_product_new|type=App}}

This App has been listed June 2026.
== Category ==
[[Category:Partner Apps|{{PAGENAME}}]]
{{Category:3rdParty Alarm Server}}
[[Category:3rdParty Alarm Server|{{PAGENAME}}]]

== Vendor ==
[[File:NV Logo RGB 200px.jpg|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]

NewVoice International AG

NewVoice is one of the world's leading companies in alarm, process and crisis management, helping organizations to automatically detect critical events, send targeted alerts and effectively reduce risks.

[https://www.newvoice.global/ NewVoice - about us]

== Description ==
'''MobiApp''' delivers alerts and communication of the '''MobiCall''' alarming solution directly to mobile devices, enabling rapid and clear responses – even for lone workers and in critical situations.

'''MobiApp''' itself is available for download in GooglePlayStore and AppStore.

'''MobiApp Demo''' is available on the '''innovaphone myApps store''' and provides an overview of the features and capabilities of the '''MobiApp''' alerting solution from '''MobiCall''', developed by '''NewVoice International'''.

== Functions ==
After opening the app, users are presented with a welcome message and a start screen explaining that they can navigate through the app by swiping left or right.

=== MobiApp Functions ===
==== Alarm and Emergency Call ====
After confirming the welcome information, the first page, '''“Alarm – Notruf”''', is displayed. This page contains two buttons:
* '''“Alarm starten”''' This button demonstrates the alarm launch functionality of the MobiApp and provides an insight into how alarms can be triggered using a mobile application.
* '''“Notruf”''' This button demonstrates how an emergency call button can be implemented and used within the MobiApp.

==== Useful Links and Further Information ====
* '''“New Voice”''' Opens the NewVoice International website, where users can explore further information about the company and its solutions.
* '''“MobiCall.App PDF”''' Displays a flyer describing the available features and possibilities of the MobiApp. Please note that these features require a properly configured and operational MobiCall alarm server.
* '''“App live testen”''' Opens a manual that explains how to create an account for '''MobiTown''', an application by NewVoice International. After creating an account, users can download the live MobiApp from the Google Play Store or Apple App Store, connect it to a real environment, and test its full functionality. This is recommended to experience the complete potential of the MobiApp.

==== Lone Worker Protection ====
By swiping again from right to left, users can access the third page. This page contains three buttons related to lone worker protection:
* '''“Alleinarbeiterschutz”''' Provides general information about the possibilities of lone worker protection with the MobiApp.
* '''“MobiCall PNA”''' Displays information about the certification available for lone worker protection when using the MobiApp.
* '''“Mehr Infos”''' Opens the NewVoice International website, where users can find further details about the available lone worker protection features.

==== Settings and Additional Information ====
In the bottom-right corner of the app, a '''tool icon''' is available. This menu allows users to adjust the user interface settings and change the language. Additional information can also be accessed via the '''“Info”''' button.

=== Multi-PBX ready ===
No PBX needed for use of MobiApp

=== Cloud ready ===
Yes

=== Supported languages ===
English, German, Dutch, French, Chinese, Italian, Norwegian, Portugese, Spanish,

== Licensing ==
"MobiApp" is licensed with the [https://newvoiceinternational.com/mobicall/ NewVoice MobiCall solution].

"MobiApp Demo" does not require a license.

== Versions ==
=== Compatible innovaphone firmware versions ===

* innovaphone V16r1
=== Application versions used for interop testing ===


* NewVoice MobiApp Demo 16r1 final (1600005)

* innovaphone V16r1

== Configuration ==
Open the App, and test everything described above with the demo, to use the App in a real environment, follow the documentation of page 2 of the application "App live testen".

== Contact ==
{|
|NewVoice International AG
|-
|George Brigati
|-
|St. Gallerstraße 8
|-
|CH-8853 Lachen
|-
|Tel: +41 58 750 11 11
|-
|Mail: [mailto:contact@newvoice.global Contact NewVoice]
|}
For any questions please refer to [https://newvoiceinternational.com/technical-support/ our contact page].

For more Informations, also check our [https://mobicity.global/nvx/?app=MobiTown&lang=en MobiCity].
[[Category:Howto|{{PAGENAME}}]]

Howto:MobiApp - NewVoice - Partner App

2026-07-08T05:46:17Z

Vsc:

Howto:MobiApp - NewVoice - Partner App

2026-07-07T11:55:19Z

Vsc: /* Licensing */

[[File:NV Logo RGB 200px.jpg|right|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]
== Product Name ==
[[File:MobiApp NV RGB 100px.jpg|100x100px|mobiapp_nv_rgb_100px.jpg/|mobiapp_nv_rgb_100px.jpg/]]

[https://newvoiceinternational.com/mobiapp/ MobiApp] by NewVoice International

== Certification Status ==


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

== Vendor ==
[[File:NV Logo RGB 200px.jpg|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]

NewVoice International AG

NewVoice is one of the world's leading companies in alarm, process and crisis management, helping organizations to automatically detect critical events, send targeted alerts and effectively reduce risks.

[https://www.newvoice.global/ NewVoice - about us]

== Description ==
'''MobiApp''' delivers alerts and communication of the '''MobiCall''' alarming solution directly to mobile devices, enabling rapid and clear responses – even for lone workers and in critical situations.

'''MobiApp''' itself is available for download in GooglePlayStore and AppStore.

'''MobiApp Demo''' is available on the '''innovaphone myApps store''' and provides an overview of the features and capabilities of the '''MobiApp''' alerting solution from '''MobiCall''', developed by '''NewVoice International'''.

== Functions ==
After opening the app, users are presented with a welcome message and a start screen explaining that they can navigate through the app by swiping left or right.

=== MobiApp Functions ===
==== Alarm and Emergency Call ====
After confirming the welcome information, the first page, '''“Alarm – Notruf”''', is displayed. This page contains two buttons:
* '''“Alarm starten”''' This button demonstrates the alarm launch functionality of the MobiApp and provides an insight into how alarms can be triggered using a mobile application.
* '''“Notruf”''' This button demonstrates how an emergency call button can be implemented and used within the MobiApp.

==== Useful Links and Further Information ====
* '''“New Voice”''' Opens the NewVoice International website, where users can explore further information about the company and its solutions.
* '''“MobiCall.App PDF”''' Displays a flyer describing the available features and possibilities of the MobiApp. Please note that these features require a properly configured and operational MobiCall alarm server.
* '''“App live testen”''' Opens a manual that explains how to create an account for '''MobiTown''', an application by NewVoice International. After creating an account, users can download the live MobiApp from the Google Play Store or Apple App Store, connect it to a real environment, and test its full functionality. This is recommended to experience the complete potential of the MobiApp.

==== Lone Worker Protection ====
By swiping again from right to left, users can access the third page. This page contains three buttons related to lone worker protection:
* '''“Alleinarbeiterschutz”''' Provides general information about the possibilities of lone worker protection with the MobiApp.
* '''“MobiCall PNA”''' Displays information about the certification available for lone worker protection when using the MobiApp.
* '''“Mehr Infos”''' Opens the NewVoice International website, where users can find further details about the available lone worker protection features.

==== Settings and Additional Information ====
In the bottom-right corner of the app, a '''tool icon''' is available. This menu allows users to adjust the user interface settings and change the language. Additional information can also be accessed via the '''“Info”''' button.

=== Multi-PBX ready ===
No PBX needed for use of MobiApp

=== Cloud ready ===
Yes

=== Supported languages ===
English, German, Dutch, French, Chinese, Italian, Norwegian, Portugese, Spanish,

== Licensing ==
"MobiApp" is licensed with the [https://newvoiceinternational.com/mobicall/ NewVoice MobiCall solution].

"MobiApp Demo" does not require a license.

== Versions ==
=== Compatible innovaphone firmware versions ===

* innovaphone V16r1
=== Application versions used for interop testing ===


* NewVoice MobiApp Demo 16r1 final (1600005)

* innovaphone V16r1

== Configuration ==
Open the App, and test everything described above with the demo, to use the App in a real environment, follow the documentation of page 2 of the application "App live testen".

== Contact ==
{|
|NewVoice International AG
|-
|George Brigati
|-
|St. Gallerstraße 8
|-
|CH-8853 Lachen
|-
|Tel: +41 58 750 11 11
|-
|Mail: [mailto:contact@newvoice.global Contact NewVoice]
|}
For any questions please refer to [https://newvoiceinternational.com/technical-support/ our contact page].

For more Informations, also check our [https://mobicity.global/nvx/?app=MobiTown&lang=en MobiCity].
[[Category:Howto|{{PAGENAME}}]]

Howto:MobiApp - NewVoice - Partner App

2026-07-07T11:30:39Z

Vsc: /* Description */

[[File:NV Logo RGB 200px.jpg|right|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]
== Product Name ==
[[File:MobiApp NV RGB 100px.jpg|100x100px|mobiapp_nv_rgb_100px.jpg/|mobiapp_nv_rgb_100px.jpg/]]

[https://newvoiceinternational.com/mobiapp/ MobiApp] by NewVoice International

== Certification Status ==


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

== Vendor ==
[[File:NV Logo RGB 200px.jpg|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]

NewVoice International AG

NewVoice is one of the world's leading companies in alarm, process and crisis management, helping organizations to automatically detect critical events, send targeted alerts and effectively reduce risks.

[https://www.newvoice.global/ NewVoice - about us]

== Description ==
'''MobiApp''' delivers alerts and communication of the '''MobiCall''' alarming solution directly to mobile devices, enabling rapid and clear responses – even for lone workers and in critical situations.

'''MobiApp''' itself is available for download in GooglePlayStore and AppStore.

'''MobiApp Demo''' is available on the '''innovaphone myApps store''' and provides an overview of the features and capabilities of the '''MobiApp''' alerting solution from '''MobiCall''', developed by '''NewVoice International'''.

== Functions ==
After opening the app, users are presented with a welcome message and a start screen explaining that they can navigate through the app by swiping left or right.

=== MobiApp Functions ===
==== Alarm and Emergency Call ====
After confirming the welcome information, the first page, '''“Alarm – Notruf”''', is displayed. This page contains two buttons:
* '''“Alarm starten”''' This button demonstrates the alarm launch functionality of the MobiApp and provides an insight into how alarms can be triggered using a mobile application.
* '''“Notruf”''' This button demonstrates how an emergency call button can be implemented and used within the MobiApp.

==== Useful Links and Further Information ====
* '''“New Voice”''' Opens the NewVoice International website, where users can explore further information about the company and its solutions.
* '''“MobiCall.App PDF”''' Displays a flyer describing the available features and possibilities of the MobiApp. Please note that these features require a properly configured and operational MobiCall alarm server.
* '''“App live testen”''' Opens a manual that explains how to create an account for '''MobiTown''', an application by NewVoice International. After creating an account, users can download the live MobiApp from the Google Play Store or Apple App Store, connect it to a real environment, and test its full functionality. This is recommended to experience the complete potential of the MobiApp.

==== Lone Worker Protection ====
By swiping again from right to left, users can access the third page. This page contains three buttons related to lone worker protection:
* '''“Alleinarbeiterschutz”''' Provides general information about the possibilities of lone worker protection with the MobiApp.
* '''“MobiCall PNA”''' Displays information about the certification available for lone worker protection when using the MobiApp.
* '''“Mehr Infos”''' Opens the NewVoice International website, where users can find further details about the available lone worker protection features.

==== Settings and Additional Information ====
In the bottom-right corner of the app, a '''tool icon''' is available. This menu allows users to adjust the user interface settings and change the language. Additional information can also be accessed via the '''“Info”''' button.

=== Multi-PBX ready ===
No PBX needed for use of MobiApp

=== Cloud ready ===
Yes

=== Supported languages ===
English, German, Dutch, French, Chinese, Italian, Norwegian, Portugese, Spanish,

== Licensing ==
The MobiApp is licensed with the [https://newvoiceinternational.com/mobicall/ NewVoice MobiCall solution].

== Versions ==
=== Compatible innovaphone firmware versions ===

* innovaphone V16r1
=== Application versions used for interop testing ===


* NewVoice MobiApp Demo 16r1 final (1600005)

* innovaphone V16r1

== Configuration ==
Open the App, and test everything described above with the demo, to use the App in a real environment, follow the documentation of page 2 of the application "App live testen".

== Contact ==
{|
|NewVoice International AG
|-
|George Brigati
|-
|St. Gallerstraße 8
|-
|CH-8853 Lachen
|-
|Tel: +41 58 750 11 11
|-
|Mail: [mailto:contact@newvoice.global Contact NewVoice]
|}
For any questions please refer to [https://newvoiceinternational.com/technical-support/ our contact page].

For more Informations, also check our [https://mobicity.global/nvx/?app=MobiTown&lang=en MobiCity].
[[Category:Howto|{{PAGENAME}}]]

Howto:MobiApp - NewVoice - Partner App

2026-07-02T06:27:24Z

Vsc:

[[File:NV Logo RGB 200px.jpg|right|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]
== Product Name ==
[[File:MobiApp NV RGB 100px.jpg|100x100px|mobiapp_nv_rgb_100px.jpg/|mobiapp_nv_rgb_100px.jpg/]]

[https://newvoiceinternational.com/mobiapp/ MobiApp] by NewVoice International

== Certification Status ==


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

== Vendor ==
[[File:NV Logo RGB 200px.jpg|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]

NewVoice International AG

NewVoice is one of the world's leading companies in alarm, process and crisis management, helping organizations to automatically detect critical events, send targeted alerts and effectively reduce risks.

[https://www.newvoice.global/ NewVoice - about us]

== Description ==
'''MobiApp''' delivers alerts and communication of the '''MobiCall''' alarming solution directly to mobile devices, enabling rapid and clear responses – even for lone workers and in critical situations.

'''MobiApp''' itself is available for download in GooglePlayStore and AppStore.

'''MobiApp Demo''' is available on the '''innovaphone myApps portal''' and provides an overview of the features and capabilities of the '''MobiApp''' alerting solution from '''MobiCall''', developed by '''NewVoice International'''.

== Functions ==
After opening the app, users are presented with a welcome message and a start screen explaining that they can navigate through the app by swiping left or right.

=== MobiApp Functions ===
==== Alarm and Emergency Call ====
After confirming the welcome information, the first page, '''“Alarm – Notruf”''', is displayed. This page contains two buttons:
* '''“Alarm starten”''' This button demonstrates the alarm launch functionality of the MobiApp and provides an insight into how alarms can be triggered using a mobile application.
* '''“Notruf”''' This button demonstrates how an emergency call button can be implemented and used within the MobiApp.

==== Useful Links and Further Information ====
* '''“New Voice”''' Opens the NewVoice International website, where users can explore further information about the company and its solutions.
* '''“MobiCall.App PDF”''' Displays a flyer describing the available features and possibilities of the MobiApp. Please note that these features require a properly configured and operational MobiCall alarm server.
* '''“App live testen”''' Opens a manual that explains how to create an account for '''MobiTown''', an application by NewVoice International. After creating an account, users can download the live MobiApp from the Google Play Store or Apple App Store, connect it to a real environment, and test its full functionality. This is recommended to experience the complete potential of the MobiApp.

==== Lone Worker Protection ====
By swiping again from right to left, users can access the third page. This page contains three buttons related to lone worker protection:
* '''“Alleinarbeiterschutz”''' Provides general information about the possibilities of lone worker protection with the MobiApp.
* '''“MobiCall PNA”''' Displays information about the certification available for lone worker protection when using the MobiApp.
* '''“Mehr Infos”''' Opens the NewVoice International website, where users can find further details about the available lone worker protection features.

==== Settings and Additional Information ====
In the bottom-right corner of the app, a '''tool icon''' is available. This menu allows users to adjust the user interface settings and change the language. Additional information can also be accessed via the '''“Info”''' button.

=== Multi-PBX ready ===
No PBX needed for use of MobiApp

=== Cloud ready ===
Yes

=== Supported languages ===
English, German, Dutch, French, Chinese, Italian, Norwegian, Portugese, Spanish,

== Licensing ==
The MobiApp is licensed with the [https://newvoiceinternational.com/mobicall/ NewVoice MobiCall solution].

== Versions ==
=== Compatible innovaphone firmware versions ===

* innovaphone V16r1
=== Application versions used for interop testing ===


* NewVoice MobiApp Demo 16r1 final (1600005)

* innovaphone V16r1

== Configuration ==
Open the App, and test everything described above with the demo, to use the App in a real environment, follow the documentation of page 2 of the application "App live testen".

== Contact ==
{|
|NewVoice International AG
|-
|George Brigati
|-
|St. Gallerstraße 8
|-
|CH-8853 Lachen
|-
|Tel: +41 58 750 11 11
|-
|Mail: [mailto:contact@newvoice.global Contact NewVoice]
|}
For any questions please refer to [https://newvoiceinternational.com/technical-support/ our contact page].

For more Informations, also check our [https://mobicity.global/nvx/?app=MobiTown&lang=en MobiCity].
[[Category:Howto|{{PAGENAME}}]]

Howto:MobiApp - NewVoice - Partner App

2026-06-30T14:37:35Z

Vsc:

[[File:NV Logo RGB 200px.jpg|right|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]
== Product Name ==
[[File:MobiApp NV RGB 100px.jpg|100x100px|mobiapp_nv_rgb_100px.jpg/|mobiapp_nv_rgb_100px.jpg/]]

[https://newvoiceinternational.com/mobiapp/ MobiApp] by NewVoice International

== Certification Status ==


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

== Vendor ==
[[File:NV Logo RGB 200px.jpg|nv_logo_rgb_200px.jpg/|nv_logo_rgb_200px.jpg/]]

NewVoice International AG

NewVoice is one of the world's leading companies in alarm, process and crisis management, helping organizations to automatically detect critical events, send targeted alerts and effectively reduce risks.

[https://www.newvoice.global/ NewVoice - about us]

== Description ==
The '''MobiApp Demo''' is available in the '''innovaphone myApps portal''' and provides an overview of the features and possibilities of the MobiCall alarming solution [https://newvoiceinternational.com/mobiapp/ '''MobiApp'''], powered by '''NewVoice International'''.

== Functions ==
After opening the app, users are presented with a welcome message and a start screen explaining that they can navigate through the app by swiping left or right.

=== MobiApp Functions ===
==== Alarm and Emergency Call ====
After confirming the welcome information, the first page, '''“Alarm – Notruf”''', is displayed. This page contains two buttons:
* '''“Alarm starten”''' This button demonstrates the alarm launch functionality of the MobiApp and provides an insight into how alarms can be triggered using a mobile application.
* '''“Notruf”''' This button demonstrates how an emergency call button can be implemented and used within the MobiApp.

==== Useful Links and Further Information ====
* '''“New Voice”''' Opens the NewVoice International website, where users can explore further information about the company and its solutions.
* '''“MobiCall.App PDF”''' Displays a flyer describing the available features and possibilities of the MobiApp. Please note that these features require a properly configured and operational MobiCall alarm server.
* '''“App live testen”''' Opens a manual that explains how to create an account for '''MobiTown''', an application by NewVoice International. After creating an account, users can download the live MobiApp from the Google Play Store or Apple App Store, connect it to a real environment, and test its full functionality. This is recommended to experience the complete potential of the MobiApp.

==== Lone Worker Protection ====
By swiping again from right to left, users can access the third page. This page contains three buttons related to lone worker protection:
* '''“Alleinarbeiterschutz”''' Provides general information about the possibilities of lone worker protection with the MobiApp.
* '''“MobiCall PNA”''' Displays information about the certification available for lone worker protection when using the MobiApp.
* '''“Mehr Infos”''' Opens the NewVoice International website, where users can find further details about the available lone worker protection features.

==== Settings and Additional Information ====
In the bottom-right corner of the app, a '''tool icon''' is available. This menu allows users to adjust the user interface settings and change the language. Additional information can also be accessed via the '''“Info”''' button.

=== Multi-PBX ready ===
No PBX needed for use of MobiApp

=== Cloud ready ===
Yes

=== Supported languages ===
English, German, Dutch, French, Chinese, Italian, Norwegian, Portugese, Spanish,

== Licensing ==
The MobiApp is licensed with the [https://newvoiceinternational.com/mobicall/ NewVoice MobiCall solution].

== Versions ==
=== Compatible innovaphone firmware versions ===

* innovaphone V16r1
=== Application versions used for interop testing ===


* NewVoice MobiApp 16r1 final (1600005)

* innovaphone V16r1

== Configuration ==
Open the App, and test everything described above with the demo, to use the App in a real environment, follow the documentation of page 2 of the application "App live testen".

== Contact ==
{|
|NewVoice International AG
|-
|George Brigati
|-
|St. Gallerstraße 8
|-
|CH-8853 Lachen
|-
|Tel: +41 58 750 11 11
|-
|Mail: [mailto:contact@newvoice.global Contact NewVoice]
|}
For any questions please refer to [https://newvoiceinternational.com/technical-support/ our contact page].

For more Informations, also check our [https://mobicity.global/nvx/?app=MobiTown&lang=en MobiCity].
[[Category:Howto|{{PAGENAME}}]]

Reference16r1:Concept App Service Connector for Microsoft 365

2026-06-23T13:15:19Z

Vsc: /* Configuration */

[[Category:Concept|Apps]]
== Applies To ==

* Connector for Microsoft 365 from Version 16r1

= Overview =

Connector for Microsoft 365 synchronizes Microsoft Teams presences with the innovaphone PBX and back, and optionally additionally Calendar presence from Exchange Online (part of the Microsoft 365 Cloud Services).
It is also possible to search for your own contacts.

== Requirements ==

* innovaphone PBX
* innovaphone Application Platform (minimum version 120004)
* V16r1
* App(Connector for Microsoft 365)
* PBX-App(innovaphone-microsoft365) license per user - order no. 02-00050-009

== Concept ==

=== User Presence ===

==== Configuration ====
Please have a look into our [[Howto16r1:Configure User Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
If the Connector for Microsoft 365 app is fully configured, the app connects to Microsoft to obtain a token. With the token, the app gets the teams users (with a Teams license) through the Microsoft Graph API.
A presence subscription to Microsoft is started with the licensed users of the PBX to get presence changes in Microsoft Teams for these users. A user subscription is also started to get changes of the users (adding, deleting or update). If a user has changed, the Teams users are retrieved again. If the presence has changed, it is forwarded to the PBX. The presences of Teams are mapped to the presences of the PBX.

* User subscriptions are renewed every 60 minutes.
* Presence subscriptions are renewed every 10 minutes.
* License Check is made periodically.

The app synchronises the PBX presence with Teams through the Graph Api. The on-the-phone presence will be renewed every 5 minutes. The other presences have a lifetime of 1 day but the away has a lifetime of 7 days.
The lifetimes are described [https://learn.microsoft.com/en-us/graph/api/presence-setuserpreferredpresence?view=graph-rest-1.0&tabs=http here]

'''Please be aware:''' The actual change of presence or line state will be live, the above-mentioned subscriptions are needed to register against the Microsoft API for changes.
After successful subscription Microsoft will trigger the Connector for Microsoft 365 App every time a presence or line state for a user has changed.
The subscription will then be renewed in the above-mentioned time interval to receive further live updates.

===== User Matching =====
You now can choose the fields used for user matching on either side from the following options:
* PBX
** CN (Long Name property from the PBX user object)
** h323 (Name property from the PBX user object)
* Azure Portal
** displayName
** mail
** mailNickname
** onPremisesDistinguishedName
** onPremisesSamAccountName
** onPremisesUserPrincipalName
** userPrincipalName

Additionally, you have the possibility to remove a possibly contained domain from the Azure fields content. 
Example: 'user@domain.tld' is transformed to 'user', if this option is checked.

===== Mapping Table =====

{| class="wikitable"
|-
! Teams Presence
! PBX Presence
|-
| Away
| away
|-
| BeRightBack
| away
|-
| Busy
| busy
|-
| DoNotDisturb
| dnd
|-
| InACall
| on-the-phone
|-
| InAMeeting
| meeting
|-
| Inactive
| online
|-
| PresenceUnknown
| online
|-
| Available
| online
|-
| Offline
| online
|-
| Offwork
| online
|-
| OutOfOffice
| away
|-
| UrgentInterruptionsOnly
| dnd
|-
| Presenting
| on-the-phone
|-
| InAConferenceCall
| on-the-phone
|}

The value "online" unsets the Teams presence in the PBX.

===== Master/Slave =====

For Master/Slave combination the "Connector for Microsoft 365" App has to be added to the slave (if no full replication is on). The slave websocket connection is needed to display "on-the-phone" presence.

=== Calendar Presence ===

==== Configuration ====
Please have a look into our [[Howto15r1:Configure_Calendar_Presence_Sync_by_Connector_for_Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 15r1 the Connector for Microsoft 365 will offer a possibility to sync Azure Portal calendar events (Teams, Exchange online) via the Graph API with the PBX presence. 
For now the [https://wiki.innovaphone.com/index.php?title=Reference13r3:Concept_App_Service_Calendar Calendar App] is (along with other functions) also capable of syncing calendar events, but using the old EWS mechanism, which Microsoft announced as end of life starting from 2026. 
'''Warning:''' Please make sure to not use both apps for syncing calendar events in parallel, this is not supported and will most likely lead to conflicts and unexpected behaviours. 
 
When the configuration of the connector for Microsoft 365 Calendar Presence Sync is complete, the app connects to Microsoft to receive a token with the calendar app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, a subscription for calendar events is created at Microsoft to receive event changes in Microsoft Calendar for these users. 
 
A user subscription is also started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 
If a calendar event has been started or ended, it is forwarded to the PBX. 

* User subscriptions are renewed every 60 minutes.
* Event subscriptions are renewed every day.
* License Check is made every hour.

=== Contact Search ===

==== Configuration ====
Please have a look into our [[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365|Howto guide for basic configuration aid]].

==== Technical Overview ====
Introduced in 16r1 the Connector for Microsoft 365 will offer a possibility to search for your own contacts (Teams, Exchange online) via the Graph API.

When the configuration of the connector for Microsoft 365 Contact Search is complete, the app connects to Microsoft to receive a token with the contact search app registered in the Azure portal. 
With the token, the app can pick up the users from the Azure portal. 
These are matched against the users in the PBX, based on the configured "User Assignment" settings. 
For each matched user with a valid Connector for Microsoft 365 licence applied, the user can search with the Phone App, for example (a myApps search provider will be provided for all apps looking using search providers looking up contacts). The search string is made available to the Connector for Microsoft 365 via the microsoft365-api. The results are sent to the consumer, e.g. the Phone App and presented there. 
 
A user subscription is started to receive user changes (add, delete or update). 
If a user has changed, the users are retrieved again. 
 

* User subscriptions are renewed every 60 minutes.
* License Check is made every hour.

'''Be aware:''' Since the Connector for Microsoft 365 is an app in the Scope of myApps App Platform, IP Phones and other services not using Apps cannot benefit from this search service.

== Related Articles ==

=Known Limitation=

== General ==
''Applies to the User Presence and the Calendar Presence''

=== Synchronization Delay ===
In the official Graph-API documentation, Microsoft is providing an overview about expected latencies for change notifications. 
You can find a whole overview table here: 
https://learn.microsoft.com/en-us/graph/change-notifications-overview#latency 
 
For the user presences the resource "presence" is used and an average latency of 10 seconds but a maximum up to 1 minute is provided. 
Such a delay in syncing changed presences from Teams down to the PBX are considered normal and are caused by the Microsoft Graph-API. 
 
In case of calendar events the average is provided as "less than 1 minute" and the maximum to 3 minutes. 

== User Presence ==
=== Line states set by the PBX does not block calls in Teams ===
Line states set by a 3rd party application (like the Connector for Microsoft 365) through the graph API are currently '''only for display purpose and do not block new calls''' in Teams. 
 
https://techcommunity.microsoft.com/t5/teams-developer/ms-graph-setpresence-problems/m-p/2798805/highlight/true#M3957 
As you can see in the above linked discussion, there once existed a feature request on Microsoft Voice, which is no longer available since it was not voted.
=== Maximum number of supported users ===
The connector now supports multiple Microsoft Teams communication users, which is the prerequisite to subscribe for more than 650 users. There is a new ribbon (Manage Teams Accounts) that allows you to configure as many communication users as you need. Every configured communication user can be used to subscribe 650 users, for example:

*3 configured communication users x 650 licensed users = 1950 users can be subscribed
'''Please be aware''': Each communication user must have a Teams license applied.

This limitation is caused by Microsoft. 
In the documentation of the Graph-API you will find a hint to this limitation: 
https://learn.microsoft.com/en-us/graph/changenotifications-for-presence#subscribe-to-multiple-users-presence 
Trying to subscribe more than 650 users (with one communication user) by using the presence subscription API will be declined by the graph API with an error message, that too many users are requested. 

=== Communication User (UserSynctoPbx) ===
Users with MFA (multi-factor-authentication) are not supported as technical communication user for the Connector.

=== Multiple sites / instances require multiple communication users ===
Each instance or each site must have separate communication users, as Microsoft only allows one concurrent subscription per communication user. (otherwise an HTTP 409 conflict will occur)

This means that if you want to subscribe to the same Azure Portal backend from two different sites (or instances), you will need to have multiple communication users (each with an applied Teams licence) in order to be able to subscribe from all endpoints.

=== Subscription Timeout ===

==== Situation ====
Due to a current limitation in the Graph API it is not possible to cancel or delete an active presence subscription. 
As you can see in the [https://learn.microsoft.com/en-us/graph/api/subscription-delete?view=graph-rest-1.0&tabs=http|documentation of the current Graph API (1.0)] the “Delete subscription” chapter does not include presence subscriptions. 
It is also not possible to have multiple subscription in parallel. 

To make sure to only request a new presence subscription when the old one is not valid anymore, the app will store the state of the presence subscription and the time until it is valid in the database. 
As mentioned in the chapter “Technical Overview” we are creating presence subscriptions with a validity of 10 minutes. 
The presence subscription will be renewed as soon as it is no longer valid which will be 10 minutes after initial subscription. 

==== Impact ====
If settings are changed or the app instance is restarted it will check the corresponding database entry on startup. 
In case the last presence subscription was completed less than 10 minutes ago, there is still an active presence subscription and the app has to wait for it to become invalid. 
Some Changes (e.g., to the “Notification-URL”) will only take effect after a new created subscription. 

The current Beta Version of the Graph API is already providing a function to delete presence subscriptions, so we hope we can improve this behavior in the future. 

=Troubleshooting=
== General ==

===Creating an app trace===
For further analysis and creating a support ticket it will be useful to have a suitable app trace. 
Before creating the trace please make sure the following trace flags are activated for the app instance:
* App
* App WebSocket
* Config
* Database
* HTTP client
* TCP
* TLS
* Webserver

After setting the config flags, please make sure to
* stop the instance
* deleting the current instance log
* start the instance
'''Now please wait at least 5 Minutes before you save the log''', otherwise we could not have the whole picture in the trace.

The restart and deletion of the the old log is useful the see the complete initialization process right away.

===SSL Certificate for notification URL===
It also is useful to make sure the notification URL has a valid and public signed certificate. 
You can do that, using an SSL-Checker, for example: https://www.sslshopper.com/ssl-checker.html 
Without a valid, public signed certificate, Microsoft will decline the connection since it will not be possible to establish a trust relationship for the SSL/TLS secure channel.

===Correctness of notification URL===
You can try to open the notification URL in your Browser 
Most likely you will see a HTTP 404 (Not Found) error message, which is the expected behavior since we are not providing an HTML website, the HTTP GET request from the browser will not be answered with content. 
This is perfectly fine since Microsoft will send presence updates with HTTP POST and will not try to request content from our app. 
 
What you can find out by trying to open the URL in your browser are the two following things: 
* If you receive a HTTP 404 error message you are most likely connected to an App Platform, if not you need to check your DNS (and maybe also reverse proxy) settings.
* If the URL is modified and the used build number is added, an app has answered your request
** Example: <code>https://public.dns/your.domain/microsoft365/subscriptions</code> is modified to <code>https://public.dns/your.domain/microsoft365/1510411/subscriptions</code>
** If this is not the case, your URL is wrong. (Be aware: The URL depends on the settings of the web server path of your app instance)

'''Be aware:''' The URL-Recognition in the Application Platform is '''case sensitive'''.

=== Activation of "Public client flow" for the registered app in Azure Portal===
If the subscription is not working at all, please make sure "Public client flow" is activated for the registered app in the Azure portal (as described in our [[Howto16r1:Configure User Presence Sync by Connector for Microsoft365#Create_an_App_for_syncing_Teams_to_PBX|HowTo article]]). 
 
The App Service trace will contain the following message if this is not the case: 
<code>AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'.</code>

== User Presence ==
===GUI Feedback===
The app itself shows required states with green and red as connections to the Master PBX, Authentication and Presence Subscription to identify if there are problems. 
Sometimes it needs a little bit time until the states are changed. 
If the states remain, it is mandatory to enable logs on the app platform and check for more information. 
([[Howto13r3:Configure Connector for Microsoft365#Creating an app trace|Concept App Service Connector for Microsoft 365: Creating an app trace]])

====No connection to Master PBX====
Check the MasterPBX name. 
The field must only contain the name [pbx], '''not the full domain''' [pbx.domain.tld]. ([[Howto13r3:Configure Connector for Microsoft365#Synchronization from Teams to the PBX|Synchronization from Teams to the PBX - Master PBX field]])

====Presence subscription failed====
There are many reasons why the "Presence subscription failed" message could be displayed. 
We try to list the most common reasons:
* The permission for the registered app in the Azure portal are not correctly set ([[Howto13r3:Configure Connector for Microsoft365#Create an App for syncing Teams to PBX|Howto: Create an App for syncing Teams to PBX]])
* The Notification URL is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The App service is not reachable from the internet ([[Reference13r3:Concept App Service Connector for Microsoft 365#Correctness of notification URL|Concept App Service Connector for Microsoft 365: Correctness of notification URL]] )
* The certificate for the public endpoint (e.g. reverse proxy) is not valid, or not publicly signed ([[Reference13r3:Concept App Service Connector for Microsoft 365#SSL Certificate for notification URL|Concept App Service Connector for Microsoft 365: SSL Certificate for notification URL]])
* The user from PBX and the Azure Portal cannot be matched ([[Reference13r3:Concept App Service Connector for Microsoft 365#User Matching|Concept App Service Connector for Microsoft 365: User Matching]])
* The App Platforms clock time is wrong ([[Reference13r3:Concept App Service Connector for Microsoft 365#App Platform clock time is wrong|Concept App Service Connector for Microsoft 365: App Platform clock time is wrong]])
* No user has a valid Connector for Microsoft 365 App license ([[Reference13r3:Concept App Service Connector for Microsoft 365#Requirements|Concept App Service Connector for Microsoft 365: Requirements]])

===Teams License for communication user===
If presence subscription does not work, please check if all of the configured communication users have a Microsoft Teams license applied and no multifactor authentication is in use for this particular user. 
Also please make sure you can login with the configured credentials. (If you have set a password as an Administration, the user needs to change the password during the first login, therefore the given password will be invalid for API access). 
''Sometimes, after changing setting or after the instance has restarted it can take up to 12 minutes until the presence subscription is working correctly. (Due to the subscription timeout)''

= Known Issues =
== Special Characters In Password ==
If you are using special characters (*, &, (, ), etc.) in your password you could run into a problem with the authentication of the communication user. 
The authentication failed status is being displayed. 
For the moment the only workaround is to eliminate special characters from your password.

==App Platform clock time is wrong==
If the clock time at the App Platform is not correct, this will lead to an unstable behaviour of the Connector for Microsoft 365. 
Since the Connector for Microsoft 365 is using the Microsoft Graph APIs presence subscription function, it needs to provide in its request a precise time until the subscription validity will be expired. 
The app service is handling subscription and will automatically recreate a new subscription each time the previous one has expired. 

A wrong clock time will lead to false expiration times and thus
* the subscription will be expired earlier than expected (synchronisation is not working because there is no valid subscription)
* the subscription will be valid longer than expected (the app service is trying to create a new subscription because it is expecting the previous one to be expired - will lead to a 409 conflict error, because only one subscription can be valid at a time)

If you are not sure about the current time of the App Platform, you can login via SSH into the App Platform and execute the <code>date</code> command to check the current time. 
You will receive an output like:
Tue Mar 12 13:38:57 UTC 2024
Please be aware: The time is displayed in UTC, so please make sure to convert to your local time zone.

==Geoblocking==
Since there might be no reliable country assignment for Microsoft addresses, all Microsoft addresses must be enabled on the upstream firewall in the event of geoblocking in order to ensure functionality of the Office365 Connector. 
As an alternative you might be able to configure your firewall to bypass the geoblocking for the configured notification URL.

= Related Articles =
[[Howto16r1:Configure User Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Calendar Presence Sync by Connector for Microsoft365]] 
[[Howto16r1:Configure Contact Search by Connector for Microsoft365]]

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

Reference16r1:Concept App Service myApps Assistant

2026-06-18T14:00:10Z

Vsc:

[[Category:Concept|Apps]]
[[Category:Concept App Service myApps Assistant]]
== Applies To ==

* innovaphone from version 16r1

== New in version 16r1 ==
Apart from adding new parameters to the [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.assistant/com.innovaphone.assistant.htm local assistant JavaScript API], these parameters can also be configured in the Assistant App. This is the possibility to choose a LLM from a list of available models and to determine the timeout of your requests.

== Overview ==
The myApps Assistant App offers an interface for other apps to access a remote large language model (LLM). This might be a locally hosted open-source model like '''mixtral''' or '''deepseek-r1''' or a model hosted by providers such as openAI (e.g. gpt-3.5-turbo, gpt-4o...) or [https://mistral.ai/ mistral]. Other applications can integrate the assistant service via the [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.assistant/com.innovaphone.assistant.htm local assistant JavaScript API] in the client and thus offer the response of the LLM.

The service functions as an intermediary and contains a corresponding backend. Therefore, it is required to self-host an LLM Service or possess an account with an external service provider. In the event of the latter, you can configure your API key in the '''Settings App''' (former PBX Manager Plugin) for this app service, if needed.

Current implementation covers the openAI API Chat Completions API v1, which is also supported by several open source projects like e.g. https://ollama.com/ .


== Licensing ==
To enable the App for specified users, availability of the [https://www.innovaphone.com/en/services/licenses/app-licenses.html#assistant ''App(innovaphone-assistant)'' license] is required on the PBX.
Alternatively, [https://www.innovaphone.com/en/services/licenses/ucc-license.html the UCC license] can be used which also includes the App(innovaphone-assistant)-license.

The license can be assigned directly to a specific User Object or via Configuration Template.

== Application Setup ==
=== Installation ===
#Open the '''Settings App''' and select the '''"AP app installer"''' plugin. On the right panel, the App Store will be shown. Hint: upon first time access, the "Terms of Use of the innovaphone App Store" have to be accepted
#In the search field located on the top right corner of the store, search for '''"myApps Assistant"''' and select it
#From the drop down menu select the firmware version to be used, for example '''"Version 16r1"''' and click on install
#Confirm "I accept the terms of use" and continue by clicking on the install yellow button
#Wait until the install has been finished
=== App Generation ===
#Close and reopen the '''Settings App''' in order to refresh the list of the available coloured AP plugins
#Scroll to '''"AP assistant"''' and open the plugin
#Select '''" + Add an App"''' and create a '''"Assistant API"'''.
#Use existing default credentials or give own ones. where as '''"Name"''' is used as display name ''(all character allowed)'' and '''"SIP"''' is the administrative field ''(no space, no capital letters)''.
#Tick the appropriate configuration template(s) to distribute the application. The “Assistant API” is required for every user object that wants to use an application with the LLM configured here.
#Click OK to save the settings and a green check mark will be shown to inform you that the configuration is fine

Next to the “Assistant API”, the [[#Assistant App|"Assistant App"]] can be configured the same way. It offers a UI for manual queries also by use of the “Assistant API”. For configuration just repeat the above mentioned last five steps for that app ('''Assistant''') too.
=== Configuration ===
Configure the following fields according to the used LLM:
{{MyApps_Assistant_Configuration}}

Finding the right model name might sometimes be difficult. You could make an API call to your ai model service provider like that:
curl -H "Authorization: Bearer YOUR-API-KEY" --get <nowiki>http://YOUR-MODEL-SERICE-PROVIDER-ADDRESS/v1/models</nowiki>
The model service provider address could be the address of your ollama server, ''openai.inference.de-txl.ionos.com'' for IONOS or ''api.openai.com'' for openAI. (That API call will be implemented in version 16r1 making the configuration easier)

== myApps Assistant - App Service ==
The App Service performs tasks in the following areas:
* Question relay to an LLM
* Language recognition
* Caching
* Translations using the LLM (not yet fully tested)

== Assistant App ==
[[File:Reference15r1ConceptAppServiceMyAppsAssistant-AssistantUI-2.png|thumb|600x600px|/Reference15r1ConceptAppServiceMyAppsAssistant-AssistantUI-2.png|/Reference15r1ConceptAppServiceMyAppsAssistant-AssistantUI-2.png]]
Since version 15r1, the application also offers a user interface, where conversations can be held with the connected large language model. These conversations are stored in a database managed by the service.

There are a few parameters one can manage from within the hamburger menu. These are:

* '''Send on Enter''' - You might choose that option if you want a message to be send to the LLM on pressing ENTER. Alternatively it would be CTRL+ENTER
* '''Don't use an interface to other apps (no system prompt)''' - To allow the application access to myApps resources (such as the contacts and connect databases, call list, or the softphone app), a specially designed system prompt is sent to the model at the beginning of each conversation. If you do not require this feature and wish to reduce costs or processing time, you can disable the system prompt by checking the appropriate box.
* '''Offline mode (Conversations are stored on your device)''' - Normally, all your conversations are stored in the central service's database, which enables you to retrieve them from any device you are logged into. However, if your internet connection is interrupted, you will not be able to access them until the connection is restored. To address this issue, you may choose to store your conversation data on your device, allowing you to access it even without an internet connection. However, you should not enable this feature when using a hardware device that is not your own. If you do, make sure to disable it afterwards to delete any locally stored data. Note that deleting locally stored conversations is not synchronized across all devices if they are all in Offline Mode!

====== Currently implemented myApps features ======
The Assistant App integrates into the myApps platform and offers services from other apps via the [https://sdk.innovaphone.com/15r1/web1/com.innovaphone.assistant.plugin/com.innovaphone.assistant.plugin.htm local assistant.plugin JavaScript API]. This will be extended and improved in future releases. You may try the following prompts:

* Ask for the number of a contact stored in the contacts database "Can you please find the number of Sarah Sample!"
* Get information from Connect and Projects* "Please look up #AI in the '''internal''' '''database'''! Then tell me how we are planning to use it"
* Get your call list "What are my recent calls?"
* Calling someone "Can you please call Sarah Sample!"
* Get the current time and date "What time and data is it right now?"
* Start a new conversation "Please start a new conversation!"

For the above mentioned prompts the following APIs should be available to the user:

* com.innovaphone.assistant.plugin
* com.innovaphone.search
* com.innovaphone.calllist

For now only keyword search is possible. In order to make the LLM understand that you want to search in Connect and Projects Databases you need to mention that you want to use the '''internal databases!''' Better use two sentences to make the LLM understand better. The search results are the same as those you would get from the '''myApps Search App'''. Only the first 40 matches of the keywords are considered and from these only the first 10k characters.
 The prompts mentioned above may or may not work depending on the connected large language model. We cannot guarantee that the results will always be satisfactory, but as the application always sends the entire conversation to the model, it is recommended to start a new conversation if different topics are not directly related to each other.

The prompts were successfully tested on the following models:
* mixtral-q6-8192
* mixtral
* deepseek-r1:14b
* deepseek-r1:32b
* deepseek-r1:70b
* gpt-3.5-turbo
* gpt-4o

There are certainly many more. Currently only models with parameter sizes of more than 14 billion (14b) correctly understand the system prompt. Larger models perform better, but are slower and more expensive.

== Limitation ==
As most modern models support a maximum context window of usually 128k token (approx. 500.000 characters) you cannot send more in one message or per conversation. In order to reduce costs users are encouraged to start a new conversation for each new topic.[[File:Reference15r1 Concept App Service Assistant App-Config-2.png|thumb|/Reference15r1_Concept_App_Service_Assistant_App-Config-2.png|/Reference15r1_Concept_App_Service_Assistant_App-Config-2.png]]

== Troubleshooting ==
To troubleshoot this App Service, you need the traceflags ''App'', ''Database'', ''HTTP-Client'' in your App instance.

== Related Articles ==
* [[{{NAMESPACE}}:Apps/PbxManager/App_myApps_Transcriptions]]
* [https://sdk.innovaphone.com/16r1/web1/com.innovaphone.assistant/com.innovaphone.assistant.htm SDK Documentation - Assistant API]
* [[Howto:Setup a LLM Server]]

Reference16r1:Apps/PbxManager/App myApps Assistant

2026-06-18T13:54:56Z

Vsc: /* Configuration */

With the assistant settings plugin, the required app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.
== Configuration ==
{{MyApps_Assistant_Configuration}}

== Add an app ==
* [[Reference16r1:Concept_App_Service_myApps_Assistant#Assistant_App|Assistant]] - application to be used for manual user queries
* Assistant API - to be used for other services

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

Existing configuration templates will be listed, app objects can be assigned by checking the respective checkbox. 
'''Be Aware:''' Every user who should be able to use the assistant service needs to have it assigned (by using a config template, for example).

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service myApps Assistant]]

Template:MyApps Assistant Configuration

2026-06-18T13:54:18Z

Vsc: Created page with ";Remote Service URL :The URL where the remote service interacting with the LLM is hosted. If you are using a model hosted by openAI, Mistral or Aleph Alpha this could be something like: https://api.openai.com/v1/chat/completions ;API-Key :The secret ''api-key''. If you are not using a self-hosted model you might need an API-Key in order to make successful HTTP Requests to your provider. This key will be delivered by your LLM model provider (e.g. openAI https://platform...."

;Remote Service URL
:The URL where the remote service interacting with the LLM is hosted. If you are using a model hosted by openAI, Mistral or Aleph Alpha this could be something like: https://api.openai.com/v1/chat/completions

;API-Key
:The secret ''api-key''. If you are not using a self-hosted model you might need an API-Key in order to make successful HTTP Requests to your provider. This key will be delivered by your LLM model provider (e.g. openAI https://platform.openai.com/signup )

;LLM Model
:The actual LLM model you intend to use. There are a couple of open source models you could use. Depending on you provider this could be something like gpt-3.5-turbo, gpt-4o, luminous, mixtral-q6-8192, deepseek-r1:32b...

;Apply for all users
:Default model to be applied to all users. Possibility to apply individual model to users locally via Assistant App settings.

;Use ollama API
:The default ollama context window size may be configured to be 4096 token or to be a value adapted to the used hardware. You may safely turn that switch off, but in case the default is smaller than the texts you send to the LLM, turning that switch on will adapt the context window size to the text size send to the LLM (other LLM servers may return an error message when these additional API parameters are used).

;Onboarding message
:Individual message which appears on top of the Assistant application start screen.

;User feedback settings
:Collect user feedback: This is an option you only need to enable if you intend to train your own model with RLHF (Reinforcement Learning with Human Feedback) . Enabling that option user might vote for the LLM responses with a "like" or a "dislike" and these voting together with the data will be stored in your database.

Reference16r1:Apps/PbxManager/App myApps Assistant

2026-06-18T11:21:54Z

Vsc: /* Configuration */

With the assistant settings plugin, the required app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.
== Configuration ==
;Remote Service URL
:The URL where the remote service interacting with the LLM is hosted. If you are using a model hosted by openAI, Mistral or Aleph Alpha this could be something like: https://api.openai.com/v1/chat/completions

;API-Key
:The secret ''api-key''. If you are not using a self-hosted model you might need an API-Key in order to make successful HTTP Requests to your provider. This key will be delivered by your LLM model provider (e.g. openAI https://platform.openai.com/signup )

;LLM Model
:The actual LLM model you intend to use. There are a couple of open source models you could use. Depending on you provider this could be something like gpt-3.5-turbo, gpt-4o, luminous, mixtral-q6-8192, deepseek-r1:32b...

;Apply for all users
:Default model to be applied to all users. Possibility to apply individual model to users locally via Assistant App settings.

;Use ollama API
:The default ollama context window size may be configured to be 4096 token or to be a value adapted to the used hardware. You may safely turn that switch off, but in case the default is smaller than the texts you send to the LLM, turning that switch on will adapt the context window size to the text size send to the LLM (other LLM servers may return an error message when these additional API parameters are used).

;Onboarding message
:Individual message which appears on top of the Assistant application start screen.

;User feedback settings
:Collect user feedback: This is an option you only need to enable if you intend to train your own model with RLHF (Reinforcement Learning with Human Feedback) . Enabling that option user might vote for the LLM responses with a "like" or a "dislike" and these voting together with the data will be stored in your database.

== Add an app ==
* [[Reference16r1:Concept_App_Service_myApps_Assistant#Assistant_App|Assistant]] - application to be used for manual user queries
* Assistant API - to be used for other services

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

Existing configuration templates will be listed, app objects can be assigned by checking the respective checkbox. 
'''Be Aware:''' Every user who should be able to use the assistant service needs to have it assigned (by using a config template, for example).

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service myApps Assistant]]

Reference16r1:Apps/PbxManager/App myApps Assistant

2026-06-18T09:54:16Z

Vsc: /* Configuration */

With the assistant settings plugin, the required app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.
== Configuration ==
;Remote Service URL
:The URL where the remote service interacting with the LLM is hosted. If you are using a model hosted by openAI, Mistral or Aleph Alpha this could be something like: https://api.openai.com/v1/chat/completions

;API-Key
:The secret ''api-key''. If you are not using a self-hosted model you might need an API-Key in order to make successful HTTP Requests to your provider. This key will be delivered by your LLM model provider (e.g. openAI https://platform.openai.com/signup )

;LLM Model
:The actual LLM model you intend to use. There are a couple of open source models you could use. Depending on you provider this could be something like gpt-3.5-turbo, gpt-4o, luminous, mixtral-q6-8192, deepseek-r1:32b...

;Apply for all users
:Default model to be applied to all users. Possibility to apply individual model to users locally via Assistant App settings.

;Use ollama API
:The default ollama context window size may be configured to be 4096 token or to be a value adapted to the used hardware. You may safely turn that switch off, but in case the default is smaller than the texts you send to the LLM, turning that switch on will adapt the context window size to the text size send to the LLM. (Other LLM servers might throw en error when these supplementel API parameters are used)

;Onboarding message
:Individual message which appears on top of the Assistant application start screen.

;User feedback settings
:Collect user feedback: This is an option you only need to enable if you intend to train your own model with RLHF (Reinforcement Learning with Human Feedback) . Enabling that option user might vote for the LLM responses with a "like" or a "dislike" and these voting together with the data will be stored in your database.

== Add an app ==
* [[Reference16r1:Concept_App_Service_myApps_Assistant#Assistant_App|Assistant]] - application to be used for manual user queries
* Assistant API - to be used for other services

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

Existing configuration templates will be listed, app objects can be assigned by checking the respective checkbox. 
'''Be Aware:''' Every user who should be able to use the assistant service needs to have it assigned (by using a config template, for example).

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service myApps Assistant]]

Reference16r1:Apps/PbxManager/App myApps Assistant

2026-06-18T09:49:44Z

Vsc: /* Add an app object */

With the assistant settings plugin, the required app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.
== Configuration ==
;Remote Service URL
:The URL where the remote service interacting with the LLM is hosted. If you are using a model hosted by openAI, Mistral or Aleph Alpha this could be something like: https://api.openai.com/v1/chat/completions

;API-Key
:The secret ''api-key''. If you are not using a self-hosted model you might need an API-Key in order to make successful HTTP Requests to your provider. This key will be delivered by your LLM model provider (e.g. openAI https://platform.openai.com/signup )

;LLM Model
:The actual LLM model you intend to use. There are a couple of open source models you could use. Depending on you provider this could be something like gpt-3.5-turbo, gpt-4o, luminous, mixtral-q6-8192, deepseek-r1:32b...

;Apply for all users
:Default model to be applied to all users. Possibility to apply individual model to users locally via Assistant App settings.

;Use ollama API
:The default ollama context window size may be configured to be 4096 token or to be a value adapted to the used hardware. You may safely turn that switch off, but in case the default is smaller than the texts you send to the LLM, turning that switch on will adapt the context window size to the text size send to the LLM. (Other LLM servers might throw en error when these supplementel API parameters are used)

;Onboarding message
:Message which appears once at first usage of Assistant Application.

;User feedback settings
:Collect user feedback: This is an option you only need to enable if you intend to train your own model with RLHF (Reinforcement Learning with Human Feedback) . Enabling that option user might vote for the LLM responses with a "like" or a "dislike" and these voting together with the data will be stored in your database.

== Add an app ==
* [[Reference16r1:Concept_App_Service_myApps_Assistant#Assistant_App|Assistant]] - application to be used for manual user queries
* Assistant API - to be used for other services

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

Existing configuration templates will be listed, app objects can be assigned by checking the respective checkbox. 
'''Be Aware:''' Every user who should be able to use the assistant service needs to have it assigned (by using a config template, for example).

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service myApps Assistant]]

Reference16r1:Apps/PbxManager/App myApps Assistant

2026-06-18T09:49:29Z

Vsc:

With the assistant settings plugin, the required app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.
== Configuration ==
;Remote Service URL
:The URL where the remote service interacting with the LLM is hosted. If you are using a model hosted by openAI, Mistral or Aleph Alpha this could be something like: https://api.openai.com/v1/chat/completions

;API-Key
:The secret ''api-key''. If you are not using a self-hosted model you might need an API-Key in order to make successful HTTP Requests to your provider. This key will be delivered by your LLM model provider (e.g. openAI https://platform.openai.com/signup )

;LLM Model
:The actual LLM model you intend to use. There are a couple of open source models you could use. Depending on you provider this could be something like gpt-3.5-turbo, gpt-4o, luminous, mixtral-q6-8192, deepseek-r1:32b...

;Apply for all users
:Default model to be applied to all users. Possibility to apply individual model to users locally via Assistant App settings.

;Use ollama API
:The default ollama context window size may be configured to be 4096 token or to be a value adapted to the used hardware. You may safely turn that switch off, but in case the default is smaller than the texts you send to the LLM, turning that switch on will adapt the context window size to the text size send to the LLM. (Other LLM servers might throw en error when these supplementel API parameters are used)

;Onboarding message
:Message which appears once at first usage of Assistant Application.

;User feedback settings
:Collect user feedback: This is an option you only need to enable if you intend to train your own model with RLHF (Reinforcement Learning with Human Feedback) . Enabling that option user might vote for the LLM responses with a "like" or a "dislike" and these voting together with the data will be stored in your database.

== Add an app object ==
* [[Reference16r1:Concept_App_Service_myApps_Assistant#Assistant_App|Assistant]] - application to be used for manual user queries
* Assistant API - to be used for other services

;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

Existing configuration templates will be listed, app objects can be assigned by checking the respective checkbox. 
'''Be Aware:''' Every user who should be able to use the assistant service needs to have it assigned (by using a config template, for example).

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service myApps Assistant]]

Reference13r1:Concept Number Adjustments (Dialing Location)

2026-06-15T06:44:52Z

Vsc: /* Phone App, Softphone App */

[[Category:Concept|Number Adjustments]]
Very often numbers are not available in the standard e.164 international format, but in subscriber or national format and maybe also formated with space, bracket, hyphens or other characters. This article defines all mechanisms in the innovaphone PBX used to adjust numbers. This can be the calling party number for display or for reverse lookup, or the called party number obtained from a directory or other purposes. These mechanisms are implemented in the PBX, the endpoints or in gateways.

== PBX ==

=== Incoming Calls from Trunks ===

A Calling Party Numbers sent in a call from the gateway to the trunk should be formated in a way, that it can be used to call back the caller, in the "Unknown Number" format. Which means it should contain any necessary prefixes for national or international numbers.

The PBX Trunk objects adds the Trunk number as prefix.

=== Reverse Lookup ===

The reverse lookup assumes that a directory exists for the numbers in the international format. For this reason, the number is converted to the international format for the lookup. The prefixes configured in the ''Node'' object are used for this purpose. If no prefixes are configured, the root node prefixes configured on the PBX/Config page are used.

The reverse lookup is performed when the call is sent out to a user, so for different users there can be different results.

* If the start of the number matches the prefix for international numbers, the prefix is removed and the resulting number is used for the lookup
* If the start of the number matches the prefix for national numbers, the prefix is removed and the country code is added. The resulting number is used for the lookup
* If the start of the number matches the prefix for subscriber numbers, the prefix is removed and the country code and area code are added. The resulting number is used for the lookup

=== Type of number handling ===

For any calls sent to the PBX, e.g. outgoing calls from phones, the type of number of the calling party number and called party number is converted to the prefixes defined in the node of the object on which the call is received. If the prefix is not defined in the node, the prefix defined in PBX/config is used. The type of number is then set to Unknown.
For SIP calls a '+' at the beginning of the number is treated as a Type international.

The type of number values for International, National and Subscriber are converted into their respective prefixes.

This way an international number obtained from a directory can be directly used for dialing.

=== PBX internal calls ===

For internal calls, especially when nodes are used, as calling party number the shortest possible number, which can be used for call back, is presented to the called endpoint.

=== PBX database used as LDAP database ===

The user database of the PBX can be used as a directory. In case of a configuration with nodes (e.164 configuration), at a given user only the number within the node is stored. As "otherTelephoneNumber" the complete number from the root node is provided.
If the config option "Adjust LDAP results for e.164" is set, a '+' is added as prefix to this number, so that it can be directly used to be dialed as international number.

== Phone App, Softphone App ==

The myApps Phone App and Softphone App get the for the node of the user configured prefixes in the AttachResult or RegisterResult messages. These prefixes are used to adjust numbers from directories before they are dialed:
* If the number starts with '+' it is sent as it is to the PBX. The PBX then does the adjustment.
* If the number starts with what is configured as international prefix, the number is sent as it is to the PBX.
* If the number seems to be an international number, which means it matches the international prefix with the subscriber prefix removed from the beginning, the subscriber prefix is added.
* If the number seems to be a national number, which means it matches the national prefix with the subscriber prefix removed from the beginning, the subscriber prefix is added.
* If the number is 7 digits or longer, the subscriber prefix is added. (This can be set as ''Max. length internal number'' in PBX/Config/General; a reset of the PBX and the myApps is needed after changes.)
Settings are applied to search results from sources via search-api-provider. Manually entered numbers are assumed to contain the respective trunk prefix.

== IOS Callkit ==

Before a number is sent to callkit a prefix, which matches the subscriber prefix is removed and added again when the call is actually sent to the PBX, so that the formating done in callkit, which works based on public numbers, works.

== Android ConnectionService (similar functionality as CallKit under IOS) ==

Before a number is sent to ConnectionService a prefix, which matches the subscriber prefix is removed and added again when the call is actually sent to the PBX, so that the formating done in ConnectionService, which works based on public numbers, works.

Reference16r1:PBX/Config/General

2026-06-15T06:44:08Z

Vsc: /* Common */

== Configuration ==

=== Common ===

;PBX Mode: The PBX operating mode
:* '''Off''' - The PBX is disabled. After enabling the PBX a browser refresh is needed to activate additional PBX webpages.
:* '''Master''' - The PBX on this device acts as Master. Within a multisite installation exactly one PBX must be configured as Master.
:* '''Slave''' - The PBX on this device acts as Slave. Within a multisite installation several PBXes can be configured as Slave.
:* '''Standby''' - The PBX on this device acts as Standby for the Master. As long as the master is available, this PBX is not active, but just monitors the Master. If the Master is not available this PBX is active.
:* '''Standby-Slave''' - The PBX on this device acts as Standby for a Slave. As long as the slave is available, this PBX is not active, but just monitors the slave. If the slave is not available this PBX is active.

;System Name: The system Name. On all PBX within a multisite installation the same System Name must be configured. For H.323 endpoints this name is the gatekeeper identifier, for SIP endpoints it is the server name.

;Use as Domain: Uses the ''System Name'' as domain name, together with the name field in the user object the PBX constructs the email address (used for sending emails out ox myPBX). This mechanism is also used for Federation, to federate with other domains.

;PBX Name: The name of the PBX on this device. With this name a PBX is associated to a node. The field 'Name' (not Long Name) of a PBX Node object relates to this name.

;DNS: DNS Name of the PBX. If configured this will be used for myPBX redirects if a client tries to register at a PBX on which the user is not configured.

;Unknown Registrations: If this checkmark is set, the PBX accepts 'unknown' registrations. This means registrations with no matching object configured. If from an endpoint registered in this way a number of an object is dialed, which has no registration active and no 'HW-ID' configured the name used for the registration is configured as 'HW-ID' of this object. This is an easy way to deploy large numbers of phones.

:'''With PBX Pwd only:''' If checked only registrations with a PBX authentication or a verified certificate in case of H.323/TLS are accepted. In this case either "PBX Pwd" or "TLS only" is set in a device generated.

;Reverse Proxy Addresses: Up to 8 IP-Addresses (Mixed IPv4 and IPv6 allowed but no DNS names) can be entered in this field, separated by comma. Registrations from one of these addresses are assumed to be routed through a Reverse Proxy. To the address '/<certificate name>' can be added to also check the TLS certificate of the Reverse Proxy. If the reverse proxy certificate is to be verified, the certificate or the issuer of the reverse proxy certificate must be trusted in the PBX. (If you use a SAN certificate you have to enter the first SAN-Name)
:If empty addresses are used, unauthenticated registrations from unknown or internal addresses are not allowed, but any registration must be authenticated, with a password or the certificate from the reverse proxy.
; Assume TLS: If the ''Assume TLS'' checkmark is set, it is assumed, that the reverse Proxy did a successful check of the TLS certificate against the registration name.

;Media relay endpoint/Firewall public IP: For media relay endpoints (e.g. third party SIP phones) the public address of the firewall of the PBX network can be configured. This address is signaled in the SDP to received RTP from the phone. The firewall should have configured a port forwarding to the PBX or the TURN, for the RTP range of the PBX or TURN.

;Media relay endpoint/TURN: If this checkmark is set, the PBX allocates TURN endpoints for calls to or from media relay endpoints, which registerd thru the reverse proxy (e.g. third party SIP phones)

;IP address for App Platform
: The ip address of an App Platform can be configured here, with a DNS name used for it. If myApps uses a host to access the PBX different from the configured DNS name of the PBX, the hostname in any App url, which matches the configured AP DNS, is replaced by the AP IP. This way it is possible to configure a PBX with DNS names and access it with myApps when the DNS is not yet set up. If the checkmark ''Operation without DNS'' is set as well any matching DNS name is replaced also when an App service requests the URL of another App service (Example: Users requesting the URL of Devices for provisioning) and in the URL sent to the App services itself (Example: Devices uses this URL to construct the URL set at devices for the Devices registration).

: Note that this mode is intended to be able to run the PBX using DNS names while the DNS is not yet in place. Once the DNS is up and running, neither the DNS name of the AP nor its IP address should be configured here.

;Music On Hold URL: A URL for the Music On Hold. This file is read by the PBX using HTTP and sent to a held endpoint via RTP. The format of this URL is

:'''<nowiki>http://<addr>/<file>.$coder?coder=g711a,g711u,g722,g723,g729,opus-nb,opus-wb&repeat=true</nowiki>'''. <addr> is the IP address of the http server, no dns name is allowed here. <file> is the filename. $coder will be replaced by the actual coder used.

:Parameters: ''coder=g729,g711a,g711u,g723,opus-nb,opus-wb'' is the list of available coders. Only these coders must be specified for which a corresponding file exists. ''repeat=true'' should be specified in order to loop the file endlessly. ''random=true'' can be used to start the music on hold on a random point (this will work only if the URL is not local though).

:By default the built-in Music-On-Hold is played (Pseudo URL: "MOH?coder=g729,g711a,g723&repeat=true"). You can also play a dial tone (Pseudo URL "TONE") or a ring-back tone (Pseudo URL "TONE?tone=ringback").

:The maximum length of the URL is limited to 500 characters (bytes).

:If you configure a wrong (or invalid) URL then you will have silence as MOH. To prevent this situation when the MoH for some specific context/user(see below) is missing and silence is played instead of any MoH, an additional parameter ''fallback=true'' is available. If the file provided in the URL is missing (HTTP Error 404 Not Found is delivered by the HTTP Server) and the parameter ''fallback'' is provided, the default MoH will be played instead of silence. To use a custom file as fallback MoH, instead of default MoH, any file name can be provided with the ''fallback'' parameter: e.g. ''fallback=other_filename''. The file other_filename.g7xx must be placed in the same folder as a file provided with URL. A special filename ''fallback=ringback'' can be used to generate a ringback tone (equivalent to ''TONE?tone=ringback'') instead to play an alternative file.

:Within the URL %<id> can be used to put in some context information of the call. The information refers to the party which has put the receiving party on hold. For information about the receiving party itself, the id has to be preceded by '.' (e.g. '''.l''').

:'''l''' Long Name
:'''h''' Name (H.323 id)
:'''n''' Number
:'''N''' Node
:'''P''' PBX
:'''d''' Diverting Name
:'''#d''' Diverting Number

: See [[Howto:Dynamic_MOH]] for more details on how to use dynamic music on hold.

;External Music On Hold: To offload the device from playing the Music on hold, the Music On Hold can be played by a separate device. This device can register with a name configured here. To retrieve the Music On Hold a call is sent to this device. For each held endpoint a call is sent.

;Response Timeout: Global timeout (in seconds) after which any action for no response is taken (e.g. Call Forward on No Response). A timeout configured at any object overrides this value.

;Dial Complete Timeout: Global timeout (in seconds) after which any action for incomplete dialed number is taken (e.g. incomplete destination at trunk object).

;No. of Regs w/o Pwd: Number of registration without password authentication which are allowed per user. If 0 is configured no registration without password is possible.
Pls. note that registrations from 127.0.0.1 w/o password will be accepted anyway

;Security block time(s): Time for which a registration to a user is blocked after attempt with wrong password. Default is 20s. With a value of 0 this features is turned off.

;Recall Timeout: A value configured here enables recall after transfer. If a call is transferred and not answered within this time, the call is sent back to the transferring endpoint.

;No email as call destination: If checked an email address configured at a user cannot be used to call this user. This is useful, if there may be conflicts of email addresses with destinations to be called via federation.

;Chat no Attachments: If checked, no file attachments are allowed in chats for any user

;Retries on busy (14s): Number of retries (Each attempt runs for 14 seconds) of blind transfer to a busy endpoint, before a recall back to the initiator is executed. During an attempt, the PBX waits to see if the target is free, and then delivers the call. The default value are 4-retries if the field is empty. If there is a 0 configured no further (in addition to the initial) will be executed. (This function depends on the ''Recall Timeout'' so the ''Recall Timeout'' must not be empty)

;Max Call Duration (h): Number of hours until a call with media is disconnected automatically. Affects all calls with initialized media channels signalled via PBX.

;Group Default Visibility: Defines additional visibility for active group members. These are added to the visibility rights derived from the [[{{NAMESPACE}}:PBX/Objects/Visibility | Visibility settings]] in user or template definitions. Note that changes made here only take effect after a re-registration.

;Presence with Alert: Enable presentation of presence on phone upon alert. Setting applies for all PBX users.

;Enable External Transfer: Unless this checkbox is set any attempt to transfer an external call back to an external destination will result in disconnection of the call.

;No CLIR on Internal calls: If checked numbers are displayed even if received with presentation restricted. When sending a call presentation restricted can still be set and should be honored by a public network.

;Media Relay:
:;Off: No Media Relay is done in the PBX
:;On: All media traffic is routed through the PBX. With the '''No Media Relay if Addresses are identical or private''' checkmark, this is not done if the two call endpoints registration addresses are either private or equal (i.e. external endpoints behind the same NAT router). To identify an address as private the "Private Networks" configuration from ''IP4/General/Settings'' is used.
:;Auto: Media traffic is routed through the PBX if calls are between private and public registration addresses but not for calls between private and private or public and public registration addresses. To identify an address as private the "Private Networks" configuration from ''IP4/General/Settings'' is used. In v11 this was the behaviour if ''RTP Proxy'' was ''on''.
: Please note that when media relay is in effect for a call, '''video is not working'''. With ICE (available from v12r1), media relay in the PBX should be obsolete except for special applications. Check ''On'' or ''Auto'' only if you need to have this, since it creates CPU load on the PBX.

;Generate CDRs: If this checkbox is set, the PBX generates CDRs for all calls. For details, refer to the [[{{NAMESPACE}}:Concept_Call_Detail_Record_CDR_PBX|CDR description article]].

;Reverse Lookup URL
: A String in the LDAP URL Format according [https://tools.ietf.org/html/rfc2255 RFC2255] which will be used by the PBX to make a lookup for all external numbers.
: Number resolutions will be forwarded to internal applications like generated CDRs, Phone App etc..
: Example: ''ldaps://ap.innovaphone.com/dc=entries?givenname,sn,company?sub?(metaSearchNumber=+%n)?bindname=innovaphone.com\contacts''
:* dn: ''dc=entries''
:* attributes: ''givenname,sn,company''
:* scope: ''sub''
:* filter: ''(metaSearchNumber=+%n)''
:** %n is a placeholder for the given cgpn
:* extension: ''bindname=innovaphone.com\contacts''
:** The username for the authentication.
:'''Variables'''
:* %n - cgpn
:* %u - h323 name of the current object
:'''Password''': Password to authenticate access for the used ldap source. Leave empty if not required.
: Examples for use of different ldap directories are listed in the [[{{NAMESPACE}}:Concept_Number_Resolution_and_LDAP#PBX_Configuration|Concept Article]]

;Logo URL
:The URL to a customized logo image that will be displayed on the phones. Leave empty to keep the standard logo. The image size should be 220x150px or less with 24Bit color deep or less and an RGB range. The file format should be PNG or JPEG.

;Route Root-Node External Calls to: Destination object (Long Name) of Root-Node external calls. This configuration option is available on the Master or Standby PBX only. Any call which cannot be terminated inside the PBX is sent to this destination as long as neither the source nor the destination of the call can be associated with a node with a PBX configured. This object must be assigned to this PBX.
:'''For calls from local PBX only''': If set on a master, calls from a slave are not sent to this destination but sent back to the slave where the call came from. On the slave the call is then sent to a destination configured with 'Route Root-Node External Calls to'.

;Route PBX-Node External Calls to: Destination object (Long Name) of PBX-Node external calls. Any call which cannot be terminated inside the PBX is sent to this destination as long as the source nor the destination of the call can be associated with the node of this PBX. If a call is sent from or to an object defined inside the node of this PBX or in a node hierarchically below the node of this PBX the call is associated to the node of this PBX. This object must be assigned to this PBX, that is, it has to register to this PBX.

;Route Internal Calls to: Destination object (Long Name) to which any call is sent for which a PBX internal destination was found, except for those calls that originated from that object. This can be used to apply special routing on PBX internal calls.

;Escape Dialtone from: The PBX object (Long Name) to which a call is made to get a dialtone if a dialtone is configured for the escape of a node. As above, this object must be assigned to this PBX.

;Prefix for Intl/Ntl/Subscriber/Area-Code/Country-Code: Prefixes to be used to map International, National and Subscriber numbers.
:* '''International Prefix''' (<code>000</code> in Germany).
:* '''National Prefix''' (<code>00</code> in Germany).
:* '''Subscriber''' (in Germany, <code>0</code> is a commonly used trunk line access code).
::The SubscriberID is used for hotkey-actions within myAPPs-launcher. By use of node-objects, adjust the Subscriber Prefix in the respective [[{{NAMESPACE}}:PBX/Objects/Node#Number_Mapping_.28International.2C_National.2C_Subscriber_Prefix.29|node object number mapping]].
::For myPBX-launcher hotkeys, refer to the [[{{NAMESPACE}}:Phone/User/Directories#Dialing_location|dialing location settings]].

:* '''Area-Code''' (in Germany for example, the town Mannheim has area code <code>621</code>).
:* '''Country-Code''' (for Germany, <code>49</code> would be used)

: These settings resemble the same settings found in the [[{{NAMESPACE}}:PBX/Objects/Node | Node]] and [[{{NAMESPACE}}:PBX/Objects/PBX | PBX]] object. However, they apply to the ''root'' node instead (and should be consistent through all PBXs in a multi-PBX system).
'''Max. length internal number'''

If the dialled number is 7 digits or longer, the subscriber prefix is added. Applies to phone and softphone app. PBX and myApps must be reset following the change. Refer to the [[Reference13r1:Concept_Number_Adjustments_(Dialing_Location)#Phone_App,_Softphone_App|respective concept]].
;Adjust LDAP results for e.164: Add a "+" prefix to an PBX-internal LDAP-contact-search result. This is used for 3rd-party- and DECT-phones which are not able to benefit from the Dialing Location settings in case of LDAP-search in an E.164-setup. See also [[{{NAMESPACE}}:Concept_Number_Adjustments_%28Dialing_Location%29#PBX_database_used_as_LDAP_database|concept description]].

;Tones: The tones scheme to be used for PBX generated dialtones. This applies to dialtones generated for node prefixes, ringback on transfer and some more.

=== Slave PBX ===

If the PBX is operated in Slave mode, then the Slave PBX section is displayed

;Registration: The VOIP protocol used for the registration to the master. Possible choices are H.323, H.323/TCP or H.323/TLS.

;Master: The IP address of the PBX master

;License Only: If set, the PBX obtains license from master, but acts as master in all other respects.

;Alternate Master: The IP address of an alternative PBX master (standby, if available)

;Password: The password to be used for registration at the Master as configured in the corresponding PBX Object (The length of the password is limited to 16 characters)

;Master GK-ID: The System Name/Gatekeeper ID of the PBX Master were will register (Optional, usually used for DynPBX).

;Replication: This parameter allows you to select the replication style for the slave PBX: either ''All'' or ''Local'' (only users that need to be known in this PBX). For the replication process the [[Reference9:PBX/Config/Security|PBX Password]] is used which have to be the same password on all PBXes in the system.

;dyn PBX ID: This parameter allows to set replication from a specific DynPBX configured on the Master Device.

;Use local static User DB: A dynPBX has also this checkmark. The database of the main PBX is used, but be careful due to the increased memory usage. The dynPBX will create its own PBX datastructure which allocates memory.

;Route Master calls if no Master to: If the master is not available, master calls are sent to this destination. Destination has to be an object with active registration.

;Max Calls to Master/No Reroute: This parameter can be used to limit the calls to the master. If a call is sent to the master and there are already calls to/from the master equal to or exceeding this value, the call is rejected if '''No Reroute''' is set or is handled as if the master was not available otherwise.

;License Limits: Here we can set limit of licensing for this Slave PBX for Port, Mobility, Operator and Softwarephone.

For complete replication from master to slave, check also password in [[Reference9:PBX/Config/Security#PBX_password]]

=== Standby PBX ===

If the PBX is operated in Standby mode, then the Standby PBX section is displayed

;Master: The IP address of the PBX master

;Replicate from Master: Turns on full replication from the master PBX

;use TLS: Use LDAPS (TLS) instead of LDAP (TCP).

For complete replication from master to slave or standby, check also password in [[Reference9:PBX/Config/Security#PBX_password]]

Howto16r1:Firmware Upgrade V15r1 V16r1

2026-06-10T06:30:14Z

Vsc: /* New environment for App Platform */

== Applies To ==
This information applies to:

* All 16r1 capable innovaphone devices
: For a general overview of the upgrade process and a list of supported devices with 16r1, see [[Howto:Firmware Upgrade]]
== Licenses ==
In case of cloud or rental model, don't worry about licenses.

If the system is licensed on premise, you'll need to regenerate the license file for v16 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).

== Migration Policy ==
Before you begin, be sure that your whole installation is running the latest 15r1 service release. Create backups before you start and store them on an external location

=== AP Upgrade to Image 140037 or newer ===
* First, upgrade your application platform to at least image version 140037. After that you can go ahead.

=== Upgrade Sequence ===
In systems of multiple units, it is important to update the tree from top to bottom. In other words, update the master unit first, and then the machines at the lower levels. If you're using a DevicesApp update job that updates the entire system at once, you don't need to do anything here.

=== TechAssist Upgrade Helper ===
* Before you start, make sure that all TechAssist tests (you will receive the required tests in the last update in the previous major version) labelled <code>Pre Upgrade: xy</code> are positive, if available
* When you are finished, make sure that all TechAssist tests (you will receive new tests with the upgrade) are positive

== Changes visible to the end customers ==
Listed here are changes that should be communicated by resellers to end users prior to a upgrade, as the change will be visible/audible in the behaviour of the application/device.

* 16r1 introduces the feature of [[Reference16r1:Concept_Reconnect_Calls | Reconnect Calls for Seamless Handover & Roaming]]. As a result, calls will not be dropped on network interruptions or PBX reboots. Instead users receive visual (MyApps or phone display) and audio (in-band tone) feedback and the call is reconnected automatically.
* Chat App: The option for users to choose whether to send a chat message using ENTER or SHIFT+ENTER has been removed. Messages can now only be sent using CTRL+ENTER without pressing the send button.

== Manual steps needed after upgrade ==
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.

=== Connector for Microsoft 365 ===
If you plan to use the new '''Contact Search''' feature of the Connector for Microsoft 365, you need to perform two manual Steps:
# Create the '''microsoft365-api''' app object by using the Settings template
# Assign the '''microsoft365-api''' app object to every user who should be able to use the new Contact Search feature. (Of cause, you can use a template for that)
 
For a more detailed guide, please refer to the how-to article: [[Howto16r1:Configure Contact Search by Connector for Microsoft365#Creating the PBX app object using the PBX Manager Plugin]]

=== Remote Control ===
In order to use the Admin Configuration Panel of the Settings App – AP Remote Control, it is necessary to grant access to the '''admin''' API, available in the App tab of the Remote Control App object.

=== Working ===
For badge counts to work, the Working Manager app object must have '''Websocket''' and '''PbxSignal''' enabled.
For the Connect integration of the Working app, '''Websocket''', '''Services''' and '''connect'''(in the Apps tab) must be enabled in the Working User app.

=== Switchboard ===
For the Connect Integration (Call Notes) to work, the Switchboard App must have the '''Services''' (App-tab) and '''connect''' or '''messages''' (Apps-tab) enabled (the name depends when the PBX was installed).

=== Projects ===
* Projects requires '''App platform version 140029''' or higher, so updating the App Platform before Projects is recommended. The Store will prohibit the update if the App Plattform does not have the minimum required version.
* For some extra admin-functionalities the '''Projects App Object needs to have an admin mode''' (App-tab). Easiest way to set this new mode is to the open the Projects App via the Projects Plugin Settings App and to re-apply it (click the OK-button). The same plugin can also be used to distribute this mode via the Config Templates.
* The '''App Platform requires the correct Time and a Timezone''' set under AP Manager/Settings/General. This is needed for some automatic cleanup of deleted items and automatic task status updates (done around 00:00h on the due date).

=== For legacy support only: Change TLS Profile ===
The ''Normal'' profile has been updated to allow only TLS 1.3 and TLS 1.2. This setting is compatible with all supported firmware versions. So you don't need to do any changes.
However if you need older TLS versions for compatibility with legacy devices, consider changing the TLS profile to ''Legacy''. In that case please see [[Reference16r1:IP4/General/TLS]] for details.

== New Apps ==
New Apps will not be installed automatically by the upgrade. The installation description of new apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.

; App Charts: [[Reference16r1:Concept_App_Charts]]
; App Polls: [[Reference16r1:Concept App Polls]]
; App MQTT Broker: [[Reference16r1:Concept_App_MQTT_Broker]]
; App Service Conference Scaler: [[Reference16r1:Concept_App_Service_Conference_Scaler]]
; App Service Conference Transcriptions: [[Reference16r1:Concept_App_Service_Conference_Transcriptions]]
; App Service Transcriptions: [[Reference16r1:Concept_App_Service_Transcriptions]]
; App Service Documents: [[Reference16r1:Concept_App_Service_Documents]]
; App Service Connector for Whatsapp: [[Reference16r1:Concept_App_Service_Connector_for_Whatsapp]]
; App Service IP: [[Reference16r1:Concept App Service IP]]

== New environment for App Platform ==
The new [[Reference16r1:Concept_innovaphone_App_Platform_Container|App Platform Container]] provides an Docker container. This container offers a ready-to-use environment for myApps applications and the innovaphone PBX.
== New license ==
Introduction of UCC license which includes the following components:

Phone App, Softphone App, Video incl. screen sharing / application sharing, Voicemail, Mobility, Fax, Chat Premium, Connect, Conference App, Assistant App incl. AI integration, Documents and Conference Transcriptions.

For further information refer to the [https://www.innovaphone.com/en/services/licenses/ucc-license.html license guide].

== Removed ==
The following software is no longer included.

* IP110A (can still be used with 15r1 firmware on current PBX versions)
* IP240A (can still be used with 15r1 firmware on current PBX versions)
* CA on CF card feature

== Deprecated ==
The following software is based on legacy technology, with no further development and limited maintenance and support.

* ''Nothing''

== Previously deprecated and now no longer supported ==
The following software is based on legacy technology, with no further development and no more maintenance and support.

* ''Nothing''

==Known Problems==
===Long Update-duration===
When you update, it can be up to 10 minutes before you have access to your app platform again.

== Related Articles ==
*[[Howto:Firmware_Upgrade]]
* [[Howto15r1:Firmware_Upgrade_V14r2_V15r1]]
[[Category:Howto|{{PAGENAME}}]]

Howto:Poly Trio - Poly - 3rd Party Product

2026-06-09T14:37:46Z

Vsc:

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

==Product Name==


Poly [https://www.polycom.co.uk/voice-conferencing-solutions/conference-phones.html Poly Conference phones- Trio family]

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

==Category==
{{3rdParty PreviousProduct}}
[[Category:3rdParty PreviousProducts|{{PAGENAME}}]]

==Vendor==




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

About us 

Poly is a global communications company that powers meaningful human connection and collaboration.

Poly combines legendary audio expertise and powerful video and conferencing capabilities to overcome the distractions, complexity and distance that make communication in and out of the workplace challenging.

Poly believes in solutions that make life easier when they work together and with our partner’s services. Our headsets, software, desk phones, audio and video conferencing, analytics and services are used worldwide and are a leading choice for every kind of workspace.

Below a selection of Poly solutions for the modern workplace that were tested with Innovaphone PBX release 13r1 sr4

==Description==




<table>
<tr><td colspan=4>  </td></tr>
<tr>
<td colspan=4>Poly Group Workspace - audio and video conferencing solutions
</tr>
<tr>
<td colspan=4>Poly Trio 8300</td>
</tr>
<tr>
<td colspan=2>[[Image:trio8300.png]]</td>
<td colspan=2>Overview
 
User Interface: 3.5” Monochrome 
Mic pick up range: 4 meters 
Frequency Response: 220Hz-14kHz 
USB and Bluetooth: 1 x Type A USB, 1x Micro USB, Bluetooth 4.0 
NoiseBlock: Removes unwanted distractions 
Voice activity detection 
Trio Visual+: Adds videoconferencing capabilities. H.323 and SIP 
Android OS 
Secure Wi-Fi network connectivity: 2.4/5Ghz 
Adaptive jitter buffers 
Packet loss concealment 
Trio 8300 datasheet here [https://www.polycom.co.uk/content/dam/polycom/common/documents/data-sheets/poly-trio-8300-datasheet-enus.pdf]
</td>
</tr>
<tr><td colspan=4>  </td></tr><tr><td colspan=4>  </td></tr>

<tr>
<td colspan=4>Poly Trio 8500</td>
</tr>
<tr>
<td colspan=2>[[Image:trio8500.png]]</td>
<td colspan=2>Overview
 
User Interface: 5” Color touch 
Mic pick up range: 4.3 meters 
Frequency Response: 180Hz-14kHz 
USB and Bluetooth: 1 x Type A USB, 1x Micro USB, Bluetooth 4.0 
NoiseBlock: Removes unwanted distractions 
Voice activity detection 
3 illuminated mute buttons 
Trio Visual+: Adds videoconferencing capabilities. H.323 and SIP 
Android OS 
Secure Wi-Fi network connectivity: 2.4/5Ghz 
Adaptive jitter buffers 
Packet loss concealment 
Trio 8500 datasheet here [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/polycom-trio-8500-skype-for-business-data-sheet-enus.pdf]
</td>
</tr>
<tr><td colspan=4>  </td></tr><tr><td colspan=4>  </td></tr>

<tr>
<td colspan=4>Poly Trio 8800</td>
</tr>
<tr>
<td colspan=2>[[Image:trio8500.png]]</td>
<td colspan=2>Overview
 
User Interface: 5” Color touch 
Mic pick up range: 4.3 meters 
Frequency Response: 180Hz-14kHz 
USB and Bluetooth: 1 x Type A USB, 1x Micro USB, Bluetooth 4.0 
NoiseBlock: Removes unwanted distractions 
Voice activity detection 
3 illuminated mute buttons 
Trio Visual+: Adds videoconferencing capabilities. H.323 and SIP 
Android OS 
Secure Wi-Fi network connectivity: 2.4/5Ghz 
Trio 8500 datasheet here [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/polycom-trio-8500-skype-for-business-data-sheet-enus.pdf]
</td>
</tr>

<tr>
<td colspan=4>Video add-on options for Trio family</td>
</tr>
<tr>
<td colspan=1>[[Image:visual.png]]</td>
<td colspan=1>[[Image:eemini.png]]</td>
<td colspan=1>[[Image:eeusb.png]]</td>
<td colspan=1>
Hybrid Registration 
Airplay & Miracast 
Camera Controls
</td>
</tr>
</table>











==Functions==





* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes
* Answer incoming call yes
* Hold/Retrieve yes
* Transfer yes
* Call waiting
* Do not disturb
* Call Conference
* Shared Line
* Call Forward and divert
* Called, calling, and connected party information
* Missed-call notification
* 1-touch speed dial
* Redial
* Zero touch provisioning, management, configuration and remote debugging via Polycom Device Management System
* FTP/TFTP/HTTP/HTTPS server-based central provisioning
* WiFi connectivity
* Bluetooth
* Exchange/Calendar support - Display Calendar On Idle Screen
* Enhanced support for Click to join
* Reverse Name Lookup
* REST APIs
* Noise block technology
* Enhanced Layout Controls
* HDMI Content Share At Idle
* H.323 & H.239 Support
* EE Cube camera with Active Speaker tracking and Group Framing AI technologies
[[Image:eecube.png]]

[[Image:trio-idle.png]]

==innovaphone CTI ready==


==innovaphone Reverse Proxy ready==


* STUN yes (RFC8445)
* TURN yes (RFC8445)
* ICE yes (RFC8445)
* SIP/TCP yes (RFC3261)
* SIP/TLS yes (RFC3261)

==innovaphone WebRTC ready==


* Codec G.711 yes
* Codec OPUS yes
* DTLS encryption yes

==Supported Codecs==

* G.711 (A-law and μ-law)
* G.719
* G.722, G722.1, G722.1C
* G.729AB
* Poly Siren 7, Siren 14
* iLBC (3.33Kbps and 15.2Kbps)
* Opus (8Kbps - 24Kbps)
* SILK

==DTMF Support==


• Inband - DTMF tone are sent as inband audio signal 
• RFC2833 - DTMF tone events are relayed per RFC2833 
• Auto - Method to use based on call setup negotiation (either Inband or RFC2833 can be negotiated) 

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

* Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes

==Support LDAP Phonebook==


* Support LDAP Phonebook yes

==Version==




Product versions used for interop testing:

* 3rd-Pty-Product Version: 5.9.1

* innovaphone 13r1 sr6 IPVA[13.2105]

==Configuration==





Innovaphone PBX: PBX--> Objects --> new 
[[Image:inno-trio.png]] 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>



<PHONE_CONFIG>

<ALL 
bluetooth.device.name="Trio Inno" 
content.airplayServer.authType="passcode" 
content.airplayServer.enabled="1" 
content.airplayServer.name="Trio Inno" 
content.wirelessDisplay.sink.enabled="1" 
content.wirelessDisplay.sink.name="Trio Inno" 
device.prov.serverName.set="1" 
device.prov.ztpEnabled="0" 
device.prov.ztpEnabled.set="1" 
device.set="1" 
feature.obitalk.enabled="1" 
obitalk.accountCode="Innovaphone_DE-.8122243." 
system.name="InnoTRIO" 
mr.pair.uid.1="64167f477783" 
mr.pair.uid.2="00e0db4cde85" 
reg.1.address="8800@polycom-test.de" 
reg.1.auth.userId="8800" 
reg.1.outboundProxy.address="inno.voice-lab.local" 
reg.1.outboundProxy.port="5060" 
reg.1.outboundProxy.transport="TCPpreferred" 
reg.1.server.1.address="inno.voice-lab.local" 
reg.1.server.1.port="5060" 
reg.1.server.1.transport="TCPpreferred" 
/> 
</PHONE_CONFIG> 

 
[[Image:trio-loadconfig.png]]

==Contact==


{|
Company Name: Poly 
Contact Name: Erich Rohrmayer 
Tel: +49 89 262 059 102 
Mobile: +49 151 182 380 26 
Mail: [mailto:erich.rohrmayer@poly.com erich.rohrmayer@poly.com]
|}

Howto:Poly VVX - Poly - 3rd Party Product

2026-06-09T14:37:29Z

Vsc:

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

==Product Name==


Poly [https://www.polycom.co.uk/voice-conferencing-solutions/desktop-ip-phones.html Poly VVX phones]

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

==Category==
{{3rdParty PreviousProduct}}
[[Category:3rdParty PreviousProducts|{{PAGENAME}}]]

==Vendor==




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

About us 

Poly is a global communications company that powers meaningful human connection and collaboration.

Poly combines legendary audio expertise and powerful video and conferencing capabilities to overcome the distractions, complexity and distance that make communication in and out of the workplace challenging.

Poly believes in solutions that make life easier when they work together and with our partner’s services. Our headsets, software, desk phones, audio and video conferencing, analytics and services are used worldwide and are a leading choice for every kind of workspace.

Below a selection of Poly solutions for the modern workplace that were tested with Innovaphone PBX release 13r1 sr4

==Description==




<table>

<tr>
<td colspan=4>Desk phones</td>
</tr>
<tr>
<td>VVX 150 [[Image:PolyVVX150P1.png]]</td>
<td>VVX 250 [[Image:PolyVVX250P1.png]]</td>
<td>VVX 350 [[Image:PolyVVX350P1.png]]</td>
<td>VVX 450 [[Image:PolyVVX450P1.png]]</td>
</tr>

<tr>
<td>
Ideal for Common Area Phone deployments 
- 132x64 Monochrome backlit display 
- 2 line keys 
- 4 soft keys 
- In-call keys: 
Call transfer and Hold 
- Non illuminated audio keys 
- HD Voice 
- 2x 10/100 Ethernet ports 
VVX 150 datasheet [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/polycom-vvx-150-obi-edition-datasheet-enus.pdf]
</td>
<td>
Designed for SoHo, office environments, front line staff, retail, professional services 
- 2.8” Color backlit display 
- 4 line keys 
- 4 soft keys 
- In-call keys: 
- Call transfer and Hold 
- Illuminated audio keys 
- HD Voice 
- 1 USB port 
- 2x Gig-E ports 
VVX 250 datasheet [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/polycom-vvx-250-obi-edition-datasheet-enus.pdf]
</td>
<td>
Designed for knowledge whose work demand reliable connectivity and place moderate levels of calls 
- 3.5” Color backlit display 
- 6 line keys 
- 4 soft keys 
- In-call keys: 
Call transfer, Hold & Voice Mail 
- Illuminated audio keys 
- HD Voice 
- 2 USB ports (rear and side) 
- 2x Gig-E ports 
VVX 350 datasheet [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/polycom-vvx-350-obi-edition-datasheet-enus.pdf]
</td>
<td>
Designed for knowledge worker who place a high volume of calls and need many speed dials and feature keys to mimic key system performance 
- 4.3” Color backlit display 
- 12 line keys 
- 4 soft keys 
- In-call keys: 
Call transfer, Hold & Voice Mail 
- Illuminated audio keys 
- HD Voice 
- 2 USB ports (rear and side) 
- 2x Gig-E ports 
- Expansion module(s) 
VVX 450 datasheet [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/polycom-vvx-450-obi-edition-datasheet-enus.pdf]
</td>
</tr>
<tr><td colspan=4>The expansion modue EM50</td></tr>
<tr>
<td colspan=2>[[Image:EM50P1.png]]</td>
<td colspan=2>
Ideal solution for high call volume handlers: receptionist, call attendants 
- 4.3” color backlit display 
- 30 line keys 
- 3 soft keys (pages) 
- 1 USB port (side) 
Up to 2 modules can be attached together via USB 
EM50 datasheet [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/vvx-em50-datasheet-enus.pdf]
</td>
</tr>
<tr><td colspan=4>See here a demo of the unique feature of Poly phones: The Acoustic Fence[https://www.youtube.com/watch?v=2Njg1B4z36Q]</td></tr>
<tr><td colspan=4>  </td></tr>
</table>











==Functions==





* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes
* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes
* Answer incoming call yes
* Hold/Retrieve yes
* Transfer yes
* Distinctive incoming call treatment
* Call waiting
* Do not disturb
* Call Conference
* Call Park
* Voice Messages Center
* Shared Line
* Call Forward and divert
* Intercom (HS to HS)
* Called, calling, and connected party information
* Missed-call notification
* 1-touch speed dial
* Redial
* Zero touch provisioning, management, configuration and remote debugging via Polycom Device Management System
* Web Hook For Call Connected State
* SIP NATPR
* Call Quality Metrics Report to Polycom Device Management System
* Background Upgrades
* Integration with Voicebase and Deepgram Transcription Platform
* Application APIs
* Dynamic Search of Network Based Directory
* Up to 60 BLFs

==innovaphone CTI ready==


==innovaphone Reverse Proxy ready==


* STUN yes (RFC8445)
* TURN yes (RFC8445)
* ICE yes (RFC8445)
* SIP/TCP yes (RFC3261)
* SIP/TLS yes (RFC3261)
[[Image:vvx-ice.png]]

==innovaphone WebRTC ready==


* Codec G.711 yes
* Codec OPUS yes
* DTLS encryption yes

==Supported Codecs==

* G.722 yes
* G.711 A-law yes
* G.711 y-law yes
* G.723.1 (53) no
* G.729A yes
* Opus yes (RFC, WB, NB)
* iLBC yes

==DTMF Support==


• Inband - DTMF tone are sent as inband audio signal 
• RFC2833 - DTMF tone events are relayed per RFC2833 
• SIPInfo - DTMF tones are relayed with SIP INFO request 
• Auto - Method to use based on call setup negotiation (either Inband or RFC2833 can be negotiated) 

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

* Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes

==Support LDAP Phonebook==


* Support LDAP Phonebook yes - RFC 3494
[[Image:vvx-ldap.png]] 

==Version==




Product versions used for interop testing:

* 3rd-Pty-Product Version: 6.4.0.2

* innovaphone 13r1 sr6 IPVA[13.2105]

==Configuration==





Innovaphone PBX: PBX--> Objects --> new 
[[Image:inno-vvx450.png]] 
Poly VVX: load this code in an xml file and upload 
<?xml version="1.0" encoding="UTF-8"?>

<ParameterList> 
<Object><Name>VoiceService.1.X_P2P.1.</Name> 
<ParameterValueStruct><Name>InboundCallRoute</Name><Value X_UseDefault="Yes"></Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.X_P2PGlobal.</Name> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.</Name> 
<ParameterValueStruct><Name>Name</Name><Value>Innovaphone</Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.SIP.</Name> 
<ParameterValueStruct><Name>ProxyServer</Name><Value>inno.voice-lab.local</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>ProxyServerPort</Name><Value>5060</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>ProxyServerTransport</Name><Value>TCP</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>RegistrarServer</Name><Value>inno.voice-lab.local</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>RegistrarServerPort</Name><Value>5060</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>UserAgentDomain</Name><Value>polycom-test.de</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>OutboundProxy</Name><Value>inno.voice-lab.local</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>OutboundProxyPort</Name><Value>5060</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>X_OutboundProxyTransport</Name><Value>TCP</Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.Line.1.</Name> 
<ParameterValueStruct><Name>Enable</Name><Value>true</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>X_DisplayLabel</Name><Value>VVX 450</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>X_DisplayNumber</Name><Value>250</Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.Line.1.SIP.</Name> 
<ParameterValueStruct><Name>AuthUserName</Name><Value>450</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>AuthPassword</Name><Value>1234</Value></ParameterValueStruct> 
</Object> 
<Object><Name>DeviceInfo.Time.</Name> 
<ParameterValueStruct><Name>NTPServer1</Name><Value>0.de.pool.ntp.org</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>NTPServer2</Name><Value>1.de.pool.ntp.org</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>LocalTimeZone</Name><Value>GMT+01:00(Rome,Paris,Madrid)</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeEnable</Name><Value>true</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeStart</Name><Value>3/8/7/2</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeEnd</Name><Value>11/1/7/2</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeDiff</Name><Value>1</Value></ParameterValueStruct> 
</Object> 
<Object><Name>UserPref.</Name> 
<ParameterValueStruct><Name>TimeFormat</Name><Value>13:35</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DateFormat</Name><Value>Jan 31, 2014</Value></ParameterValueStruct> 
</Object> 
</ParameterList> 
 
[[Image:load-config.png]]

==Contact==


{|
Company Name: Poly 
Contact Name: Erich Rohrmayer 
Tel: +49 89 262 059 102 
Mobile: +49 151 182 380 26 
Mail: [mailto:erich.rohrmayer@poly.com erich.rohrmayer@poly.com]
|}

Howto:Poly DECT - Poly - 3rd Party Product

2026-06-09T14:37:20Z

Vsc:

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

==Product Name==


Poly [https://www.polycom.co.uk/voice-conferencing-solutions/dect-wireless-ip-phones.html Poly VVX D230 DECT IP phone]

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

==Category==
{{3rdParty PreviousProduct}}
[[Category:3rdParty PreviousProducts|{{PAGENAME}}]]

==Vendor==




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

About us 

Poly is a global communications company that powers meaningful human connection and collaboration.

Poly combines legendary audio expertise and powerful video and conferencing capabilities to overcome the distractions, complexity and distance that make communication in and out of the workplace challenging.

Poly believes in solutions that make life easier when they work together and with our partner’s services. Our headsets, software, desk phones, audio and video conferencing, analytics and services are used worldwide and are a leading choice for every kind of workspace.

Below a selection of Poly solutions for the modern workplace that were tested with Innovaphone PBX release 13r1 sr4

==Description==




<table>
<tr>
<td colspan=4>DECT - Poly VVX D230</td>
</tr>
<tr>
<td colspan=2>[[Image:DECTP1.png]]</td>
<td colspan=2>Key features

 - 2” color TFT (178 x 220 pixel) screen 
- DECT Wireless Range: 50m indoor / 300m outdoor 
- 100 hours standby / 10 hours talk time 
- Includes 10/100 POE Base Station with pass-through supporting 10 handsets per base, 8 SIP accounts, and 8 simultaneous calls 
- Wideband Audio Support, G.722 / Opus 
- Easy to manage with PDMS-SP, the same cloud management tool used to manage your VVX Obi Edition phones 
VVX D239 datasheet here [https://www.polycom.com/content/dam/polycom/common/documents/data-sheets/poly-vvx-d230-dect-iphone-ds-enus.pdf]
</td>
</tr>

</table>











==Functions==





* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes
* Answer incoming call yes
* Hold/Retrieve yes
* Transfer yes
* Distinctive incoming call treatment
* Call waiting
* Do not disturb
* Call Conference
* Call Park
* Voice Messages Center
* Shared Line
* Call Forward and divert
* Intercom (HS to HS)
* Called, calling, and connected party information
* Missed-call notification
* 1-touch speed dial
* Redial
* Handset locator button
* Base station with 2 port 10/100PoE
* Zero touch provisioning, management, configuration and remote debugging via Polycom Device Management System
[[Image:dect1.png]] 
[[Image:dect2.png]]
==innovaphone CTI ready==


==innovaphone Reverse Proxy ready==


* STUN yes (RFC8445)
* TURN yes (RFC8445)
* ICE yes (RFC8445)
* SIP/TCP yes (RFC3261)
* SIP/TLS yes (RFC3261)

==innovaphone WebRTC ready==


* Codec G.711 yes
* Codec OPUS yes
* DTLS encryption yes

==Supported Codecs==

* G.722 yes
* G.711 A-law yes
* G.711 y-law yes
* G.723.1 (53) no
* G.729A yes
* Opus yes (RFC, WB, NB)
* iLBC yes

==DTMF Support==


• Inband - DTMF tone are sent as inband audio signal 
• RFC2833 - DTMF tone events are relayed per RFC2833 
• SIPInfo - DTMF tones are relayed with SIP INFO request 
• Auto - Method to use based on call setup negotiation (either Inband or RFC2833 can be negotiated) 

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

* Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes

==Support LDAP Phonebook==


* Support LDAP Phonebook no
* Support XSI Directory yes

==Version==




Product versions used for interop testing:

* 3rd-Pty-Product Version: 7.0.0.6932

* innovaphone 13r1 sr6 IPVA[13.2105]

==Configuration==





Innovaphone PBX: PBX--> Objects --> new 
[[Image:inno-vvxd230.png]] 
Poly VVX: load this code in an xml file and upload 
<?xml version="1.0" encoding="UTF-8"?>
 
<ParameterList> 
<Object><Name>VoiceService.1.X_P2P.1.</Name> 
<ParameterValueStruct><Name>InboundCallRoute</Name><Value X_UseDefault="Yes"></Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.X_P2PGlobal.</Name> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.</Name> 
<ParameterValueStruct><Name>Name</Name><Value>Innovaphone</Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.SIP.</Name> 
<ParameterValueStruct><Name>ProxyServer</Name><Value>inno.voice-lab.local</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>ProxyServerPort</Name><Value>5060</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>ProxyServerTransport</Name><Value>TCP</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>RegistrarServer</Name><Value>inno.voice-lab.local</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>RegistrarServerPort</Name><Value>5060</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>UserAgentDomain</Name><Value>polycom-test.de</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>OutboundProxy</Name><Value>inno.voice-lab.local</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>OutboundProxyPort</Name><Value>5060</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>X_OutboundProxyTransport</Name><Value>TCP</Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.Line.1.</Name> 
<ParameterValueStruct><Name>Enable</Name><Value>true</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>X_DisplayLabel</Name><Value>VVX D230</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>X_DisplayNumber</Name><Value>230</Value></ParameterValueStruct> 
</Object> 
<Object><Name>VoiceService.1.VoiceProfile.1.Line.1.SIP.</Name> 
<ParameterValueStruct><Name>AuthUserName</Name><Value>230</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>AuthPassword</Name><Value>1234</Value></ParameterValueStruct> 
</Object> 
<Object><Name>DeviceInfo.Time.</Name>
<ParameterValueStruct><Name>NTPServer1</Name><Value>0.de.pool.ntp.org</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>NTPServer2</Name><Value>1.de.pool.ntp.org</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>LocalTimeZone</Name><Value>GMT+01:00(Rome,Paris,Madrid)</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeEnable</Name><Value>true</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeStart</Name><Value>3/8/7/2</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeEnd</Name><Value>11/1/7/2</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DaylightSavingTimeDiff</Name><Value>1</Value></ParameterValueStruct> 
</Object> 
<Object><Name>UserPref.</Name> 
<ParameterValueStruct><Name>TimeFormat</Name><Value>13:35</Value></ParameterValueStruct> 
<ParameterValueStruct><Name>DateFormat</Name><Value>Jan 31, 2014</Value></ParameterValueStruct> 
</Object> 
</ParameterList> 
 
[[Image:load-configd230.png]]

==Contact==


{|
Company Name: Poly 
Contact Name: Erich Rohrmayer 
Tel: +49 89 262 059 102 
Mobile: +49 151 182 380 26 
Mail: [mailto:erich.rohrmayer@poly.com erich.rohrmayer@poly.com]
|}

Reference16r1:Apps/PbxManager/App myApps Transcriptions

2026-06-09T09:41:14Z

Vsc:

With the transcription PBX-Manager plugin, the needed app object can be created and configured.
In addition, the app object can be assigned to specific config templates, if any exist.

== Configuration ==
Define Transcription API settings

;Remote Service URL
: URL to the used transcription service provider. Can be self-hosted (e.g. Faster-Whisper) or commercial services like openAI, [https://api.openai.com/v1/audio/transcriptions lemonfox] etc.

;API key
:API key to access commercially used service

;Model
:Language model used for speech recognition. Depends on transcription service provider. For openAI e.g. "whisper-1", others could be "Systran/faster-whisper-small" etc.

;Speaker labels
:Activate speaker recognition to assign speaker labels in the resulting transcription

== Add an app ==
Add Transcriptions API or Transcriptions app objects identified by credentials:
;Name
:The ''name'' displayed for the app object which must be unique.

;SIP
:The ''sip'' from the app object which must be unique.

==Related Articles==
* [[{{NAMESPACE}}:Concept App Service Transcriptions|Reference16r1:Concept App Service Transcriptions]]

Specyfikacja IP174

2026-06-09T06:48:38Z

Vsc: Created page with "{{datasheet_header|innovaphone IP174|Stacja interkomowa}} <div class="datasheets-mehrspaltig"> Image:IP174-x.png ===Oprogramowanie=== Urządzenie działa z wersją 16 i nowszą ===Obudowa=== * Montaż naścienny * Głośnik przedni – 80 mm, 4 omy, tworzywo sztuczne * Obudowa IP66 do montażu na zewnątrz, pylo- i wodoszczelna, odporna na mgłę solną * Klawisze foliowe * IP174-1: jeden klawisz szybkiego wybierania * IP174-4: 4 klawisze szybkiego wybierania * IP174..."

{{datasheet_header|innovaphone IP174|Stacja interkomowa}}
<div class="datasheets-mehrspaltig">
[[Image:IP174-x.png]]
===Oprogramowanie===
Urządzenie działa z wersją 16 i nowszą
===Obudowa===
* Montaż naścienny
* Głośnik przedni – 80 mm, 4 omy, tworzywo sztuczne
* Obudowa IP66 do montażu na zewnątrz, pylo- i wodoszczelna, odporna na mgłę solną
* Klawisze foliowe
* IP174-1: jeden klawisz szybkiego wybierania
* IP174-4: 4 klawisze szybkiego wybierania
* IP174-15: 12-klawiszowa klawiatura telefoniczna
* Każdy model: 3 klawisze trybu połączeń (głośnomówiący, bezpośredni/priorytetowy, PTT), 2 klawisze głośności
* Wskaźnik połączenia
* Wymiary (szer. x gł. x wys.): 130 x 70 x 303 mm
* Waga: ok. 1500 gramów
===Interfejsy===
* 10/100-BASE-TX (auto negocjacja), RJ-45 (modular Jack 8P8C)
* Zewnętrzny zasilacz 24 V (wejście)
* Wyjście 24 V DC (500 mA)
* Przekaźnik (NO/NC)
* Słuchawka (6-żyłowa)
* Zestaw słuchawkowy (6-żyłowy) z obsługą PTT
* Głośnik zewnętrzny
* Tylny port USB – wyłącznie do użytku wewnętrznego
===Hardware===
* Zasilanie: „Power over Ethernet+” zgodnie z IEEE 802.3at, Class 4
* 128 MB pamięci RAM, 16 MB pamięci Flash
* Temperatura pracy: od -25 °C do +70 °C
* Wilgotność: od 10% do 90% (bez kondensacji)
* Temperatura przechowywania: od -10 °C do +70 °C
{{Template:Leistungsmerkmale PL - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale PL - Voip Protokolle13}}
{{Template:Leistungsmerkmale PL - Netzwerk13}}

Tunelowanie PPTP do 4 tuneli jednocześnie, szyfrowanie za pomocą MPPE
{{Template:Leistungsmerkmale PL - Administration13}}
===Funkcje dodatkowe===
* Przycisk głośnomówiący – połączenia głośnomówiące w trybie pełnego dupleksu
* Przycisk bezpośredniego połączenia – pełnodupleksowe dołączanie do rozmowy w stanie bezczynności lub zajętości (funkcję można wyłączyć)
* Przycisk PTT – funkcja Talkback i klasyczne użycie PTT (funkcja wyciszenia mikrofonu)
* Komunikaty strefowe – nieograniczona liczba stref
{{Template:Leistungsmerkmale PL - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Deklaracje zgodności|patrz oddzielny arkusz informacyjny}}
===Numer katalogowy IP174-1: 01-01741-001===
===Numer katalogowy IP174-4: 01-01744-001===
===Numer katalogowy IP174-15: 01-17415-001===
</div>
{{Template:Datasheet_footer|PL}}
[[Category:Specyfikacja techniczna Phones PL|{{PAGENAME}}]]

Specyfikacja IP172

2026-06-09T06:48:16Z

Vsc: Created page with "{{datasheet_header|innovaphone IP172|Przemysłowa stacja interkomowa}} <div class="datasheets-mehrspaltig"> Image:IP172.png ===Oprogramowanie=== Urządzenie działa z wersją 16 i nowszą ===Obudowa=== * Montaż naścienny * Głośnik tylny – 46 mm, 50 Ohm, tworzywo sztuczne, do sygnalizacji dzwonienia * Obudowa IP66 do zastosowań w warunkach zewnętrznych, pylo- i wodoszczelna, odporna na mgłę solną * Klawisze foliowe * Klawiatura telefoniczna z 12 klawiszami..."

{{datasheet_header|innovaphone IP172|Przemysłowa stacja interkomowa}}
<div class="datasheets-mehrspaltig">
[[Image:IP172.png]]
===Oprogramowanie===
Urządzenie działa z wersją 16 i nowszą
===Obudowa===
* Montaż naścienny
* Głośnik tylny – 46 mm, 50 Ohm, tworzywo sztuczne, do sygnalizacji dzwonienia
* Obudowa IP66 do zastosowań w warunkach zewnętrznych, pylo- i wodoszczelna, odporna na mgłę solną
* Klawisze foliowe
* Klawiatura telefoniczna z 12 klawiszami
* 3 klawisze trybu połączeń (głośnomówiący, bezpośredni/priorytetowy, PTT), 2 klawisze głośności
* Wskaźnik połączenia
* Wymiary (szer. x gł. x wys.): 130 x 70 x 303 mm
* Waga: ok. 1500 gramów
===Interfejsy===
* 10/100-BASE-TX (auto negocjacja), RJ-45 (modular Jack 8P8C)
* Zewnętrzny zasilacz 24 V (wejście)
* Wyjście 24 V DC (500 mA)
* Przekaźnik (NO/NC)
* Słuchawka (6-żyłowa)
* Zestaw słuchawkowy (6-żyłowy) z obsługą PTT
* Głośnik zewnętrzny
* Tylny port USB – wyłącznie do użytku wewnętrznego
===Hardware===
* Zasilanie: „Power over Ethernet+” zgodnie z IEEE 802.3at, Class 4
* 128 MB pamięci RAM, 16 MB pamięci Flash
* Temperatura pracy: od -25 °C do +70 °C
* Wilgotność: od 10% do 90% (bez kondensacji)
* Temperatura przechowywania: od -10 °C do +70 °C
{{Template:Leistungsmerkmale PL - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale PL - Voip Protokolle13}}
{{Template:Leistungsmerkmale PL - Netzwerk13}}

Tunelowanie PPTP do 4 tuneli jednocześnie, szyfrowanie za pomocą MPPE
{{Template:Leistungsmerkmale PL - Administration13}}
===Funkcje dodatkowe===
* Przycisk głośnomówiący – połączenia głośnomówiące w trybie pełnego dupleksu
* Przycisk bezpośredniego połączenia – pełnodupleksowe dołączanie do rozmowy w stanie bezczynności lub zajętości (funkcję można wyłączyć)
* Przycisk PTT – funkcja Talkback i klasyczne użycie PTT (funkcja wyciszenia mikrofonu)
* Komunikaty strefowe – nieograniczona liczba stref
{{Template:Leistungsmerkmale PL - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Deklaracje zgodności|patrz oddzielny arkusz informacyjny}}
===Numer katalogowy IP172: 01-00172-001===
</div>
{{Template:Datasheet_footer|PL}}
[[Category:Specyfikacja techniczna Phones PL|{{PAGENAME}}]]

Specyfikacja IP171

2026-06-09T06:47:49Z

Vsc: Created page with "{{datasheet_header|innovaphone IP171|Stacja interkomowa do montażu naściennego}} <div class="datasheets-mehrspaltig"> Image:IP171.png ===Oprogramowanie=== Urządzenie działa z wersją 16 i nowszą ===Obudowa=== * Montaż naścienny * Głośnik przedni – 60 mm, 8 Ω, tworzywo sztuczne * Obudowa IP66 do montażu na zewnątrz, pylo- i wodoszczelna, odporna na mgłę solną * Wyświetlacz OLED, 128 x 64 pikseli * Podświetlane silikonowe klawisze funkcyjne (3 x dyna..."

{{datasheet_header|innovaphone IP171|Stacja interkomowa do montażu naściennego}}
<div class="datasheets-mehrspaltig">
[[Image:IP171.png]]
===Oprogramowanie===
Urządzenie działa z wersją 16 i nowszą
===Obudowa===
* Montaż naścienny
* Głośnik przedni – 60 mm, 8 Ω, tworzywo sztuczne
* Obudowa IP66 do montażu na zewnątrz, pylo- i wodoszczelna, odporna na mgłę solną
* Wyświetlacz OLED, 128 x 64 pikseli
* Podświetlane silikonowe klawisze funkcyjne (3 x dynamicznie programowalne, 3 x nawigacyjne)
* Podświetlana silikonowa klawiatura telefoniczna
* Podświetlane silikonowe klawisze trybu połączeń (głośnomówiący, bezpośredni/priorytetowy, PTT)
* Wskaźnik połączenia
* Czujnik światła otoczenia
* Wymiary (szer. x gł. x wys.): 132 x 70 x 303 mm
* Waga: ok. 1500 gramów
===Interfejsy===
* 10/100-BASE-TX (auto negocjacja), RJ-45 (modular Jack 8P8C)
* Zewnętrzny zasilacz 24 V (wejście)
* Wyjście 24 V DC (500 mA)
* Przekaźnik (NO/NC)
* Słuchawka (6-żyłowa)
* Zestaw słuchawkowy (6-żyłowy) z obsługą PTT
* Głośnik zewnętrzny
* Tylny port USB – wyłącznie do użytku wewnętrznego
===Hardware===
* Zasilanie: „Power over Ethernet+” zgodnie z IEEE 802.3at, Class 4
* 128 MB pamięci RAM, 16 MB pamięci Flash
* Temperatura pracy: od +5 °C do +55 °C
* Wilgotność: od 10% do 90% (bez kondensacji)
* Temperatura przechowywania: od -10 °C do +70 °C
{{Template:Leistungsmerkmale PL - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale PL - Voip Protokolle13}}
{{Template:Leistungsmerkmale PL - Netzwerk13}}

Tunelowanie PPTP do 4 tuneli jednocześnie, szyfrowanie za pomocą MPPE
{{Template:Leistungsmerkmale PL - Administration13}}
===Funkcje dodatkowe===
* Przycisk głośnomówiący – połączenia głośnomówiące w trybie pełnego dupleksu
* Przycisk bezpośredniego połączenia – pełnodupleksowe dołączanie do rozmowy w stanie bezczynności lub zajętości (funkcję można wyłączyć)
* Przycisk PTT – funkcja Talkback i klasyczne użycie PTT (funkcja wyciszenia mikrofonu)
* Komunikaty strefowe – nieograniczona liczba stref
{{Template:Leistungsmerkmale PL - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Deklaracje zgodności|patrz oddzielny arkusz informacyjny}}
===Numer katalogowy: 01-00171-001===
</div>
{{Template:Datasheet_footer|PL}}
[[Category:Specyfikacja techniczna Phones PL|{{PAGENAME}}]]

Specyfikacja IP170

2026-06-09T06:47:30Z

Vsc: Created page with "{{datasheet_header|innovaphone IP170|Stacja interkomowa do montażu podtynkowego}} <div class="datasheets-mehrspaltig"> Image:IP170.png ===Oprogramowanie=== Urządzenie działa z wersją 16 i nowszą ===Obudowa=== * Montaż podtynkowy * Głośnik przedni – 61 mm, 4 Ω * Klasa ochrony IP20 * Wyświetlacz OLED, 128 x 64 pikseli * Podświetlane silikonowe klawisze funkcyjne (3 x dynamicznie programowalne, 3 x nawigacyjne) * Podświetlana silikonowa klawiatura telefoni..."

{{datasheet_header|innovaphone IP170|Stacja interkomowa do montażu podtynkowego}}
<div class="datasheets-mehrspaltig">
[[Image:IP170.png]]
===Oprogramowanie===
Urządzenie działa z wersją 16 i nowszą
===Obudowa===
* Montaż podtynkowy
* Głośnik przedni – 61 mm, 4 Ω
* Klasa ochrony IP20
* Wyświetlacz OLED, 128 x 64 pikseli
* Podświetlane silikonowe klawisze funkcyjne (3 x dynamicznie programowalne, 3 x nawigacyjne)
* Podświetlana silikonowa klawiatura telefoniczna
* Podświetlane silikonowe klawisze trybu połączeń (głośnomówiący, bezpośredni/priorytetowy, PTT)
* Wskaźnik połączenia
* Czujnik światła otoczenia
* Wymiary (szer. x gł. x wys.): 94 x 31 x 269 mm
* Waga: ok. 650 gramów
===Interfejsy===
* 10/100-BASE-TX (auto negocjacja), RJ-45 (modular Jack 8P8C)
* Zewnętrzny zasilacz 24 V (wejście)
* Wyjście 24 V DC (500 mA)
* Przekaźnik (NO/NC)
* Słuchawka (6-żyłowa)
* Zestaw słuchawkowy (6-żyłowy) z obsługą PTT
* Głośnik zewnętrzny
* Tylny port USB – wyłącznie do użytku wewnętrznego
===Hardware===
* Zasilanie: „Power over Ethernet+” zgodnie z IEEE 802.3at, Class 4
* 128 MB pamięci RAM, 16 MB pamięci Flash
* Temperatura pracy: od +5 °C do +55 °C
* Wilgotność: od 10% do 90% (bez kondensacji)
* Temperatura przechowywania: od -10 °C do +70 °C
{{Template:Leistungsmerkmale PL - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale PL - Voip Protokolle13}}
{{Template:Leistungsmerkmale PL - Netzwerk13}}

Tunelowanie PPTP do 4 tuneli jednocześnie, szyfrowanie za pomocą MPPE
{{Template:Leistungsmerkmale PL - Administration13}}
===Funkcje dodatkowe===
* Przycisk głośnomówiący – połączenia głośnomówiące w trybie pełnego dupleksu
* Przycisk bezpośredniego połączenia – pełnodupleksowe dołączanie do rozmowy w stanie bezczynności lub zajętości (funkcję można wyłączyć)
* Przycisk PTT – funkcja Talkback i klasyczne użycie PTT (funkcja wyciszenia mikrofonu)
* Komunikaty strefowe – nieograniczona liczba stref
{{Template:Leistungsmerkmale PL - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Deklaracje zgodności|patrz oddzielny arkusz informacyjny}}
===Numer katalogowy: 01-00170-001===
</div>
{{Template:Datasheet_footer|PL}}
[[Category:Specyfikacja techniczna Phones PL|{{PAGENAME}}]]

Dati tecnici IP174

2026-06-09T06:36:39Z

Vsc: Created page with "{{datasheet_header|innovaphone IP174|Postazione intercom}} <div class="datasheets-mehrspaltig"> Image:IP174-x.png ===Firmware=== Dispositivo funzionante dalla Versione 16 o successive ===Box=== * Montaggio a parete * Altoparlante frontale da 80 mm, 4 Ohm, plastica * Box IP66 per uso esposto, a tenuta di polvere e acqua, resistente alla nebbia salina * Tasti a membrana * IP174-1: un tasto di selezione rapida * IP174-4: 4 tasti di selezione rapida * IP174-15: tastierin..."

{{datasheet_header|innovaphone IP174|Postazione intercom}}
<div class="datasheets-mehrspaltig">
[[Image:IP174-x.png]]
===Firmware===
Dispositivo funzionante dalla Versione 16 o successive
===Box===
* Montaggio a parete
* Altoparlante frontale da 80 mm, 4 Ohm, plastica
* Box IP66 per uso esposto, a tenuta di polvere e acqua, resistente alla nebbia salina
* Tasti a membrana
* IP174-1: un tasto di selezione rapida
* IP174-4: 4 tasti di selezione rapida
* IP174-15: tastierino telefonico a 12 tasti
* Ogni modello: 3 tasti modalità chiamata (vivavoce, diretto/priorità, PTT), 2 tasti volume
* Indicatore di chiamata
* Dimensioni (L x P x A): 130 x 70 x 303 mm
* Peso: ca. 1500 g
===Interfacce===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Alimentazione esterna 24 V PSU (ingresso)
* Uscita 24 V DC (500 mA)
* Relè (NO/NC)
* Cornetta (6 fili)
* Cuffia (6 fili) con supporto PTT
* Altoparlante esterno
* Porta USB posteriore - solo per uso interno
===Hardware===
* Alimentazione: “Power over Ethernet+” secondo IEEE 802.3at, Classe 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura di esercizio: da -25 °C a +70 °C
* Umidità: dal 10% al 90% (senza condensa)
* Temperatura di stoccaggio: da -10 °C a +70 °C
{{Template:Leistungsmerkmale IT - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale IT - Voip Protokolle13}}
{{Template:Leistungsmerkmale IT - Netzwerk13}}

Tunneling PPTP fino a 4 tunnel simultanei, cifratura tramite MPPE
{{Template:Leistungsmerkmale IT - Administration13}}
===Caratteristiche supplementari===
* Tasto vivavoce – chiamate vivavoce full duplex
* Tasto Direct in – intrusione full duplex su libero o occupato (disattivabile)
* Tasto PTT – uso talkback e PTT classico (funzione di mute del microfono)
* Annunci di zona – zone illimitate
{{Template:Leistungsmerkmale IT - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformità|vedere foglio informativo separato}}
===Numero d'ordine IP174-1: 01-01741-001===
===Numero d'ordine IP174-4: 01-01744-001===
===Numero d'ordine IP174-15: 01-17415-001===
</div>
{{Template:Datasheet_footer|IT}}
[[Category:Dati tecnici Phones IT|{{PAGENAME}}]]

Dati tecnici IP172

2026-06-09T06:36:14Z

Vsc: Created page with "{{datasheet_header|innovaphone IP172|Postazione intercom industriale}} <div class="datasheets-mehrspaltig"> Image:IP172.png ===Firmware=== Dispositivo funzionante dalla Versione 16 o successive ===Box=== * Montaggio a parete * Altoparlante posteriore da 46 mm, 50 Ohm, plastica, per la suoneria * Box IP66 per uso esposto, a tenuta di polvere e acqua, resistente alla nebbia salina * Tasti a membrana * Tastierino telefonico a 12 tasti * 3 tasti modalità chiamata (vivav..."

{{datasheet_header|innovaphone IP172|Postazione intercom industriale}}
<div class="datasheets-mehrspaltig">
[[Image:IP172.png]]
===Firmware===
Dispositivo funzionante dalla Versione 16 o successive
===Box===
* Montaggio a parete
* Altoparlante posteriore da 46 mm, 50 Ohm, plastica, per la suoneria
* Box IP66 per uso esposto, a tenuta di polvere e acqua, resistente alla nebbia salina
* Tasti a membrana
* Tastierino telefonico a 12 tasti
* 3 tasti modalità chiamata (vivavoce, diretto/priorità, PTT), 2 tasti volume
* Indicatore di chiamata
* Dimensioni (L x P x A): 130 x 70 x 303 mm
* Peso: ca. 1500 g
===Interfacce===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Alimentazione esterna 24 V PSU (ingresso)
* Uscita 24 V DC (500 mA)
* Relè (NO/NC)
* Cornetta (6 fili)
* Cuffia (6 fili) con supporto PTT
* Altoparlante esterno
* Porta USB posteriore - solo per uso interno
===Hardware===
* Alimentazione: “Power over Ethernet+” secondo IEEE 802.3at, Classe 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura di esercizio: da -25 °C a +70 °C
* Umidità: dal 10% al 90% (senza condensa)
* Temperatura di stoccaggio: da -10 °C a +70 °C
{{Template:Leistungsmerkmale IT - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale IT - Voip Protokolle13}}
{{Template:Leistungsmerkmale IT - Netzwerk13}}

Tunneling PPTP fino a 4 tunnel simultanei, cifratura tramite MPPE
{{Template:Leistungsmerkmale IT - Administration13}}
===Caratteristiche supplementari===
* Tasto vivavoce – chiamate vivavoce full duplex
* Tasto Direct in – intrusione full duplex su libero o occupato (disattivabile)
* Tasto PTT – uso talkback e PTT classico (funzione di mute del microfono)
* Annunci di zona – zone illimitate
{{Template:Leistungsmerkmale IT - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformità|vedere foglio informativo separato}}
===Numero d'ordine: 01-00172-001===
</div>
{{Template:Datasheet_footer|IT}}
[[Category:Dati tecnici Phones IT|{{PAGENAME}}]]

Dati tecnici IP171

2026-06-09T06:35:33Z

Vsc: Created page with "{{datasheet_header|innovaphone IP171|Postazione intercom da parete}} <div class="datasheets-mehrspaltig"> Image:IP171.png ===Firmware=== Dispositivo funzionante dalla Versione 16 o successive ===Box=== * Montaggio a parete * Altoparlante frontale da 60 mm, 8 Ohm, plastica * Box IP66 per uso esposto, a tenuta di polvere e acqua, resistente alla nebbia salina * Display OLED, 128 x 64 pixel * Tasti funzione in silicone retroilluminati (3 assegnabili dinamicamente, 3 di..."

{{datasheet_header|innovaphone IP171|Postazione intercom da parete}}
<div class="datasheets-mehrspaltig">
[[Image:IP171.png]]
===Firmware===
Dispositivo funzionante dalla Versione 16 o successive
===Box===
* Montaggio a parete
* Altoparlante frontale da 60 mm, 8 Ohm, plastica
* Box IP66 per uso esposto, a tenuta di polvere e acqua, resistente alla nebbia salina
* Display OLED, 128 x 64 pixel
* Tasti funzione in silicone retroilluminati (3 assegnabili dinamicamente, 3 di navigazione)
* Tastiera telefonica in silicone retroilluminata
* Tasti modalità chiamata in silicone retroilluminati (vivavoce, diretto/priorità, PTT)
* Indicatore di chiamata
* Sensore di luce ambientale
* Dimensioni (L x P x A): 132 x 70 x 303 mm
* Peso: ca. 1500 g
===Interfacce===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Alimentazione esterna 24 V PSU (ingresso)
* Uscita 24 V DC (500 mA)
* Relè (NO/NC)
* Cornetta (6 fili)
* Cuffia (6 fili) con supporto PTT
* Altoparlante esterno
* Porta USB posteriore - solo per uso interno
===Hardware===
* Alimentazione: “Power over Ethernet+” secondo IEEE 802.3at, Classe 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura di esercizio: da +5 °C a +55 °C
* Umidità: dal 10% al 90% (senza condensa)
* Temperatura di stoccaggio: da -10 °C a +70 °C
{{Template:Leistungsmerkmale IT - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale IT - Voip Protokolle13}}
{{Template:Leistungsmerkmale IT - Netzwerk13}}

Tunneling PPTP fino a 4 tunnel simultanei, cifratura tramite MPPE
{{Template:Leistungsmerkmale IT - Administration13}}
===Caratteristiche supplementari===
* Tasto vivavoce – chiamate vivavoce full duplex
* Tasto Direct in – intrusione full duplex su libero o occupato (disattivabile)
* Tasto PTT – uso talkback e PTT classico (funzione di mute del microfono)
* Annunci di zona – zone illimitate
{{Template:Leistungsmerkmale IT - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformità|vedere foglio informativo separato}}
===Numero d'ordine: 01-00171-001===
</div>
{{Template:Datasheet_footer|IT}}
[[Category:Dati tecnici Phones IT|{{PAGENAME}}]]

Dati tecnici IP170

2026-06-09T06:34:54Z

Vsc: Created page with "{{datasheet_header|innovaphone IP170|Postazione intercom da incasso}} <div class="datasheets-mehrspaltig"> Image:IP170.png ===Firmware=== Dispositivo funzionante dalla Versione 16 o successive ===Box=== * Montaggio da incasso * Altoparlante frontale da 61 mm, 4 Ohm * Classe di protezione IP20 * Display OLED, 128 x 64 pixel * Tasti funzione in silicone retroilluminati (3 assegnabili dinamicamente, 3 di navigazione) * Tastiera telefonica in silicone retroilluminata * T..."

{{datasheet_header|innovaphone IP170|Postazione intercom da incasso}}
<div class="datasheets-mehrspaltig">
[[Image:IP170.png]]
===Firmware===
Dispositivo funzionante dalla Versione 16 o successive
===Box===
* Montaggio da incasso
* Altoparlante frontale da 61 mm, 4 Ohm
* Classe di protezione IP20
* Display OLED, 128 x 64 pixel
* Tasti funzione in silicone retroilluminati (3 assegnabili dinamicamente, 3 di navigazione)
* Tastiera telefonica in silicone retroilluminata
* Tasti modalità chiamata in silicone retroilluminati (vivavoce, diretto/priorità, PTT)
* Indicatore di chiamata
* Sensore di luce ambientale
* Dimensioni (L x P x A): 94 x 31 x 269 mm
* Peso: ca. 650 g
===Interfacce===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Alimentazione esterna 24 V PSU (ingresso)
* Uscita 24 V DC (500 mA)
* Relè (NO/NC)
* Cornetta (6 fili)
* Cuffia (6 fili) con supporto PTT
* Altoparlante esterno
* Porta USB posteriore - solo per uso interno
===Hardware===
* Alimentazione: “Power over Ethernet+” secondo IEEE 802.3at, Classe 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura di esercizio: da +5 °C a +55 °C
* Umidità: dal 10% al 90% (senza condensa)
* Temperatura di stoccaggio: da -10 °C a +70 °C
{{Template:Leistungsmerkmale IT - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale IT - Voip Protokolle13}}
{{Template:Leistungsmerkmale IT - Netzwerk13}}

Tunneling PPTP fino a 4 tunnel simultanei, cifratura tramite MPPE
{{Template:Leistungsmerkmale IT - Administration13}}
===Caratteristiche supplementari===
* Tasto vivavoce – chiamate vivavoce full duplex
* Tasto Direct in – intrusione full duplex su libero o occupato (disattivabile)
* Tasto PTT – uso talkback e PTT classico (funzione di mute del microfono)
* Annunci di zona – zone illimitate
{{Template:Leistungsmerkmale IT - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformità|vedere foglio informativo separato}}
===Numero d'ordine: 01-00170-001===
</div>
{{Template:Datasheet_footer|IT}}
[[Category:Dati tecnici Phones IT|{{PAGENAME}}]]

Ficha técnica IP174

2026-06-09T06:32:35Z

Vsc: Created page with "{{datasheet_header|innovaphone IP174|Estación intercomunicadora}} <div class="datasheets-mehrspaltig"> Image:IP174-x.png ===Firmware=== Este dispositivo funciona con la versión 16 o superior ===Carcasa=== * Montaje en pared * Altavoz frontal de 80 mm, 4 Ohm, plástico * Carcasa IP66 para uso expuesto, estanca al polvo y al agua, resistente a la niebla salina * Teclas de membrana * IP174-1: una tecla de marcación rápida * IP174-4: 4 teclas de marcación rápida *..."

{{datasheet_header|innovaphone IP174|Estación intercomunicadora}}
<div class="datasheets-mehrspaltig">
[[Image:IP174-x.png]]
===Firmware===
Este dispositivo funciona con la versión 16 o superior
===Carcasa===
* Montaje en pared
* Altavoz frontal de 80 mm, 4 Ohm, plástico
* Carcasa IP66 para uso expuesto, estanca al polvo y al agua, resistente a la niebla salina
* Teclas de membrana
* IP174-1: una tecla de marcación rápida
* IP174-4: 4 teclas de marcación rápida
* IP174-15: teclado telefónico de 12 teclas
* Cada modelo: 3 teclas de modo de llamada (manos libres, directo/prioridad, PTT), 2 teclas de volumen
* Indicador de llamada
* Dimensiones (An x P x Al): 130 x 70 x 303 mm
* Peso: aprox. 1500 g
===Interfaces===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Fuente de alimentación externa 24 V PSU (entrada)
* Salida 24 V DC (500 mA)
* Relé (NO/NC)
* Microteléfono (6 hilos)
* Auricular/cascos (6 hilos) con soporte PTT
* Altavoz externo
* Puerto USB trasero - solo para uso interno
===Hardware===
* Alimentación: “Power over Ethernet+” según IEEE 802.3at, Clase 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura de funcionamiento: de -25 °C a +70 °C
* Humedad: del 10% al 90% (sin condensación)
* Temperatura de almacenamiento: de -10 °C a +70 °C
{{Template:Leistungsmerkmale ES - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale ES - Voip Protokolle13}}
{{Template:Leistungsmerkmale ES - Netzwerk13}}

Túnel PPTP de hasta 4 túneles simultáneos, cifrado mediante MPPE
{{Template:Leistungsmerkmale ES - Administration13}}
===Características adicionales===
* Tecla manos libres – llamadas manos libres full duplex
* Tecla Direct in – intrusión full duplex en libre u ocupado (puede desactivarse)
* Tecla PTT – uso talkback y PTT clásico (función de mute del micrófono)
* Anuncios por zonas – zonas ilimitadas
{{Template:Leistungsmerkmale ES - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformidades|véase hoja informativa separada}}
===Número de pedido IP174-1: 01-01741-001===
===Número de pedido IP174-4: 01-01744-001===
===Número de pedido IP174-15: 01-17415-001===
</div>
{{Template:Datasheet_footer|ES}}
[[Category:Fichas técnicas Phones ES|{{PAGENAME}}]]

Ficha técnica IP172

2026-06-09T06:31:46Z

Vsc: Created page with "{{datasheet_header|innovaphone IP172|Estación intercomunicadora industrial}} <div class="datasheets-mehrspaltig"> Image:IP172.png ===Firmware=== Este dispositivo funciona con la versión 16 o superior ===Carcasa=== * Montaje en pared * Altavoz trasero de 46 mm, 50 Ohm, plástico, para timbre * Carcasa IP66 para uso expuesto, estanca al polvo y al agua, resistente a la niebla salina * Teclas de membrana * Teclado telefónico de 12 teclas * 3 teclas de modo de llamada..."

{{datasheet_header|innovaphone IP172|Estación intercomunicadora industrial}}
<div class="datasheets-mehrspaltig">
[[Image:IP172.png]]
===Firmware===
Este dispositivo funciona con la versión 16 o superior
===Carcasa===
* Montaje en pared
* Altavoz trasero de 46 mm, 50 Ohm, plástico, para timbre
* Carcasa IP66 para uso expuesto, estanca al polvo y al agua, resistente a la niebla salina
* Teclas de membrana
* Teclado telefónico de 12 teclas
* 3 teclas de modo de llamada (manos libres, directo/prioridad, PTT), 2 teclas de volumen
* Indicador de llamada
* Dimensiones (An x P x Al): 130 x 70 x 303 mm
* Peso: aprox. 1500 g
===Interfaces===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Fuente de alimentación externa 24 V PSU (entrada)
* Salida 24 V DC (500 mA)
* Relé (NO/NC)
* Microteléfono (6 hilos)
* Auricular/cascos (6 hilos) con soporte PTT
* Altavoz externo
* Puerto USB trasero - solo para uso interno
===Hardware===
* Alimentación: “Power over Ethernet+” según IEEE 802.3at, Clase 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura de funcionamiento: de -25 °C a +70 °C
* Humedad: del 10% al 90% (sin condensación)
* Temperatura de almacenamiento: de -10 °C a +70 °C
{{Template:Leistungsmerkmale ES - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale ES - Voip Protokolle13}}
{{Template:Leistungsmerkmale ES - Netzwerk13}}

Túnel PPTP de hasta 4 túneles simultáneos, cifrado mediante MPPE
{{Template:Leistungsmerkmale ES - Administration13}}
===Características adicionales===
* Tecla manos libres – llamadas manos libres full duplex
* Tecla Direct in – intrusión full duplex en libre u ocupado (puede desactivarse)
* Tecla PTT – uso talkback y PTT clásico (función de mute del micrófono)
* Anuncios por zonas – zonas ilimitadas
{{Template:Leistungsmerkmale ES - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformidades|véase hoja informativa separada}}
===Número de pedido: 01-00172-001===
</div>
{{Template:Datasheet_footer|ES}}
[[Category:Fichas técnicas Phones ES|{{PAGENAME}}]]

Ficha técnica IP171

2026-06-09T06:30:33Z

Vsc: Created page with "{{datasheet_header|innovaphone IP171|Estación intercomunicadora de montaje en pared}} <div class="datasheets-mehrspaltig"> Image:IP171.png ===Firmware=== Este dispositivo funciona con la versión 16 o superior ===Carcasa=== * Montaje en pared * Altavoz frontal de 60 mm, 8 Ohm, plástico * Carcasa IP66 para uso expuesto, estanca al polvo y al agua, resistente a la niebla salina * Pantalla OLED, 128 x 64 píxeles * Teclas de función de silicona retroiluminadas (3 asi..."

{{datasheet_header|innovaphone IP171|Estación intercomunicadora de montaje en pared}}
<div class="datasheets-mehrspaltig">
[[Image:IP171.png]]
===Firmware===
Este dispositivo funciona con la versión 16 o superior
===Carcasa===
* Montaje en pared
* Altavoz frontal de 60 mm, 8 Ohm, plástico
* Carcasa IP66 para uso expuesto, estanca al polvo y al agua, resistente a la niebla salina
* Pantalla OLED, 128 x 64 píxeles
* Teclas de función de silicona retroiluminadas (3 asignables dinámicamente, 3 de navegación)
* Teclado telefónico de silicona retroiluminado
* Teclas de modo de llamada de silicona retroiluminadas (manos libres, directo/prioridad, PTT)
* Indicador de llamada
* Sensor de luz ambiental
* Dimensiones (An x P x Al): 132 x 70 x 303 mm
* Peso: aprox. 1500 g

===Interfaces===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Fuente de alimentación externa 24 V PSU (entrada)
* Salida 24 V DC (500 mA)
* Relé (NO/NC)
* Microteléfono (6 hilos)
* Auricular/cascos (6 hilos) con soporte PTT
* Altavoz externo
* Puerto USB trasero - solo para uso interno

===Hardware===
* Alimentación: “Power over Ethernet+” según IEEE 802.3at, Clase 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura de funcionamiento: de +5 °C a +55 °C
* Humedad: del 10% al 90% (sin condensación)
* Temperatura de almacenamiento: de -10 °C a +70 °C
{{Template:Leistungsmerkmale ES - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale ES - Voip Protokolle13}}
{{Template:Leistungsmerkmale ES - Netzwerk13}}

Túnel PPTP de hasta 4 túneles simultáneos, cifrado mediante MPPE
{{Template:Leistungsmerkmale ES - Administration13}}
===Características adicionales===
* Tecla manos libres – llamadas manos libres full duplex
* Tecla Direct in – intrusión full duplex en libre u ocupado (puede desactivarse)
* Tecla PTT – uso talkback y PTT clásico (función de mute del micrófono)
* Anuncios por zonas – zonas ilimitadas
{{Template:Leistungsmerkmale ES - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformidades|véase hoja informativa separada}}
===Número de pedido: 01-00171-001===
</div>
{{Template:Datasheet_footer|ES}}
[[Category:Fichas técnicas Phones ES|{{PAGENAME}}]]

Ficha técnica IP170

2026-06-09T06:29:53Z

Vsc: Created page with "{{datasheet_header|innovaphone IP170|Estación intercomunicadora empotrada}} <div class="datasheets-mehrspaltig"> Image:IP170.png ===Firmware=== Este dispositivo funciona con la versión 16 o superior ===Carcasa=== * Montaje empotrado * Altavoz frontal de 61 mm, 4 Ohm * Clase de protección IP20 * Pantalla OLED, 128 x 64 píxeles * Teclas de función de silicona retroiluminadas (3 asignables dinámicamente, 3 de navegación) * Teclado telefónico de silicona retroilu..."

{{datasheet_header|innovaphone IP170|Estación intercomunicadora empotrada}}
<div class="datasheets-mehrspaltig">
[[Image:IP170.png]]
===Firmware===
Este dispositivo funciona con la versión 16 o superior
===Carcasa===
* Montaje empotrado
* Altavoz frontal de 61 mm, 4 Ohm
* Clase de protección IP20
* Pantalla OLED, 128 x 64 píxeles
* Teclas de función de silicona retroiluminadas (3 asignables dinámicamente, 3 de navegación)
* Teclado telefónico de silicona retroiluminado
* Teclas de modo de llamada de silicona retroiluminadas (manos libres, directo/prioridad, PTT)
* Indicador de llamada
* Sensor de luz ambiental
* Dimensiones (An x P x Al): 94 x 31 x 269 mm
* Peso: aprox. 650 g

===Interfaces===
* 10/100-BASE-TX (auto negotiation), RJ-45 (modular Jack 8P8C)
* Fuente de alimentación externa 24 V PSU (entrada)
* Salida 24 V DC (500 mA)
* Relé (NO/NC)
* Microteléfono (6 hilos)
* Auricular/cascos (6 hilos) con soporte PTT
* Altavoz externo
* Puerto USB trasero - solo para uso interno

===Hardware===
* Alimentación: “Power over Ethernet+” según IEEE 802.3at, Clase 4
* 128 MByte RAM, 16 MByte Flash
* Temperatura de funcionamiento: de +5 °C a +55 °C
* Humedad: del 10% al 90% (sin condensación)
* Temperatura de almacenamiento: de -10 °C a +70 °C
{{Template:Leistungsmerkmale ES - Sprach Coder|G.722, Opus-NB, Opus-WB}}
{{Template:Leistungsmerkmale ES - Voip Protokolle13}}
{{Template:Leistungsmerkmale ES - Netzwerk13}}

Túnel PPTP de hasta 4 túneles simultáneos, cifrado mediante MPPE
{{Template:Leistungsmerkmale ES - Administration13}}
===Características adicionales===
* Tecla manos libres – llamadas manos libres full duplex
* Tecla Direct in – intrusión full duplex en libre u ocupado (puede desactivarse)
* Tecla PTT – uso talkback y PTT clásico (función de mute del micrófono)
* Anuncios por zonas – zonas ilimitadas
{{Template:Leistungsmerkmale ES - Lizenzen Telefone}}
{{Template:CE-Decl_Phones|Conformidades|véase hoja informativa separada}}
===Número de pedido: 01-00170-001===
</div>
{{Template:Datasheet_footer|ES}}
[[Category:Fichas técnicas Phones ES|{{PAGENAME}}]]