Reference16r1:Concept Conference Scaler App: Difference between revisions
Jump to navigation
Jump to search
| (4 intermediate revisions by 2 users not shown) | |||
| Line 24: | Line 24: | ||
== More information == | == More information == | ||
=== Conference Scaler App (innovaphone-conferencescaler) === | === Conference Scaler App (innovaphone-conferencescaler) === | ||
[[File:Conferencescaler.png|110px]] | [[File:Conferencescaler.png|110px|conferencescaler.png/|conferencescaler.png/]] | ||
The hidden app offers an interface via the Service API (com.innovaphone.conferencescaler), that is used by the conference object. | The hidden app offers an interface via the Service API (com.innovaphone.conferencescaler), that is used by the conference object. | ||
| Line 45: | Line 45: | ||
# Make sure the Instance is running. | # Make sure the Instance is running. | ||
# Create via the settings plugin a new Conference Scaler app object. | # Create via the settings plugin a new Conference Scaler app object. | ||
# Select the Conference Interfaces to be used by the Conference Scaler app. | # Select the Conference Interfaces to be used by the Conference Scaler app inside the Setting plugin. | ||
# Allow the use of the Conference Scaler app on the Conference | # Allow the use of the Conference Scaler app on the Conference settings plugin. | ||
# Currently, for technical reasons, the Conference Scaler app object requires video and app sharing licenses or a UC license, which should be configured in the PBX Advanced UI | |||
== Restrictions / Known issues == | == Restrictions / Known issues == | ||
| Line 52: | Line 53: | ||
* Using the Conference Scaler app generates an overhead depending on usage patterns, so the increase in the number of participants does not correspond to a multiple of x interfaces. (One participant will take up an estimation of 1,5x CPU-Load as the usual conference flow (because data is additionally send to a different interface). So for an interface with max. 100 Video participants this amount will decrease to a maximum participant limit of 66 (as 100/1,5=66). Therefore if you want to achieve a maximum of X video participants you need to take that information into account for calculating the needed interfaces) | * Using the Conference Scaler app generates an overhead depending on usage patterns, so the increase in the number of participants does not correspond to a multiple of x interfaces. (One participant will take up an estimation of 1,5x CPU-Load as the usual conference flow (because data is additionally send to a different interface). So for an interface with max. 100 Video participants this amount will decrease to a maximum participant limit of 66 (as 100/1,5=66). Therefore if you want to achieve a maximum of X video participants you need to take that information into account for calculating the needed interfaces) | ||
* In case of failure of the App Platform the Conference Scaler app will not be available as well. Therefore it will not be possible to join or continue an ongoing conference. | * In case of failure of the App Platform the Conference Scaler app will not be available as well. Therefore it will not be possible to join or continue an ongoing conference. | ||
* Room reservations are not | * Room reservations are not needed anymore | ||
* Video sharing between the conference interfaces is handled via multicast and this requires that the interfaces are on the same network | * Video sharing between the conference interfaces is handled via multicast and this requires that the interfaces are on the same network (Multicast addresses differs between 239.0.0.0 - 239.255.255.255) | ||
* Only SCNF interfaces are currently supported | * Only SCNF interfaces are currently supported | ||
* For now only Hardware Gateways are supported, no IPVAs are able to be used currently | |||
== Troubleshooting == | == Troubleshooting == | ||
Latest revision as of 15:04, 13 March 2026
|
FIXME: This product is in the beta phase and is not yet finished |
The Conference Scaler app is required to use multiple conference interfaces within one conference.
Applies to
- Conference Scaler app
Requirements
- innovaphone PBX
- innovaphone Application Platform
- V16r1
- At least one innovaphone Gateway with CONF/SCNF Interfaces
- The Devices API must be available for the settings plugin therefore the gateways have to be connected to devices
Setting Plugins
Conference Scaler
With the Conference Scaler settings plugin the Conference Scaler app object can be created, edited and deleted on the PBX. Furthermore, the conference interface to be used can be configured if the Devices API is available.
Conference
In the conference plugin, the menu item "Additional Features" appears for conferences. With this setting you can enable the use of the Conference Scaler within the conference object. Additionally, you can activate the use of PBX channels licenses.
More information
Conference Scaler App (innovaphone-conferencescaler)
The hidden app offers an interface via the Service API (com.innovaphone.conferencescaler), that is used by the conference object.
Parameters:
- URL
http://<ap.domain.tld>/<domain.tld>/<instance-name>/innovaphone-conferencescaler
Features
- Allows the use of multiple conference interfaces within multiple conference
- This removes previous participant limits
- Adds flexibility to existing infrastructure
- The Conference Scaler app nominates one conference interface which will manage the control for voice streams. This conference interface will then receive and distribute the audio streams to all interfaces which are connected to the Conference Scaler app
- The Conference Scaler app will split the participants in a Round Robin maner, therefore the load will be evenly distributed to the interfaces
- If an interface has reached its limit for participants, the Conference Scaler app will then select a different and free Interface for a new incoming call
Configuration
- Download the Conference Scaler app via App Store. (or use the Settings Plugin "app installer" to install the App + Instance automatically and skip to step 5)
- Install the Conference Scaler app on the App Platform.
- Create an instance in the Conference Scaler app on the App Platform.
- Make sure the Instance is running.
- Create via the settings plugin a new Conference Scaler app object.
- Select the Conference Interfaces to be used by the Conference Scaler app inside the Setting plugin.
- Allow the use of the Conference Scaler app on the Conference settings plugin.
- Currently, for technical reasons, the Conference Scaler app object requires video and app sharing licenses or a UC license, which should be configured in the PBX Advanced UI
Restrictions / Known issues
- Currently, for technical reasons, the Conference Scaler app object requires video and app sharing licenses or a UC license, which should be configured in the PBX Advanced UI
- Using the Conference Scaler app generates an overhead depending on usage patterns, so the increase in the number of participants does not correspond to a multiple of x interfaces. (One participant will take up an estimation of 1,5x CPU-Load as the usual conference flow (because data is additionally send to a different interface). So for an interface with max. 100 Video participants this amount will decrease to a maximum participant limit of 66 (as 100/1,5=66). Therefore if you want to achieve a maximum of X video participants you need to take that information into account for calculating the needed interfaces)
- In case of failure of the App Platform the Conference Scaler app will not be available as well. Therefore it will not be possible to join or continue an ongoing conference.
- Room reservations are not needed anymore
- Video sharing between the conference interfaces is handled via multicast and this requires that the interfaces are on the same network (Multicast addresses differs between 239.0.0.0 - 239.255.255.255)
- Only SCNF interfaces are currently supported
- For now only Hardware Gateways are supported, no IPVAs are able to be used currently
Troubleshooting
If you can reproduce the problem, take a screenshot (depending on the issue), save the browser logs and the app logs, and send them as an attachment to your support ticket.