Reference7:Administration/PBX/Objects/Call Broadcast Conference: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
(anoying nowrap)
 
Line 3: Line 3:
This object is built-in to the PBX and thus does not need a registration to work.  It will run on the PBX that is set in the ''PBX'' field.  
This object is built-in to the PBX and thus does not need a registration to work.  It will run on the PBX that is set in the ''PBX'' field.  


{|
==External Conference Resource Name==
|valign=top nowrap=true|'''External Conference Resource Name'''
If the conference resource local to the broadcast conference object shall be used, you can leave this field empty.  Otherwise, you must configure the object ''Name'' of an existing resource.  When a called conference member picks up the call, it gets transferred to this object.  This object will usually be either a conference resource on another innovaphone PBX or a 3rd party conferencing unit.
If the conference resource local to the broadcast conference object shall be used, you can leave this field empty.  Otherwise, you must configure the object ''Name'' of an existing resource.  When a called conference member picks up the call, it gets transferred to this object.  This object will usually be either a conference resource on another innovaphone PBX or a 3rd party conferencing unit.


The call sent to the conferencing ressource will have a called party number that consists of the ''Conference Id Prefix'' + ''Conference Id'' + ''Conference Id Suffix''.  There will be no calling party number.
The call sent to the conferencing ressource will have a called party number that consists of the ''Conference Id Prefix'' + ''Conference Id'' + ''Conference Id Suffix''.  There will be no calling party number.


|-
==Create Dynamic Conference Id==
|valign=top nowrap=true|'''Create Dynamic Conference Id'''
Each individual conference running on a conferencing resource (a.k.a. ''conference room'') needs a distinct conference-id.  If this check box is ticked, conference ids will be created dynamically for new conferences.  Please note that a single broadcast conference object never uses more than one conference object at a time.
Each individual conference running on a conferencing resource (a.k.a. ''conference room'') needs a distinct conference-id.  If this check box is ticked, conference ids will be created dynamically for new conferences.  Please note that a single broadcast conference object never uses more than one conference object at a time.


|-
==Conference Id==
|valign=top nowrap=true|'''Conference Id'''
If no ''Create Dynamic Conference Id'' is not checked, then you need to specify the conference id to be used here.
If no ''Create Dynamic Conference Id'' is not checked, then you need to specify the conference id to be used here.
|-
 
|valign=top nowrap=true|'''3rd Party Conferencing Unit'''
==3rd Party Conferencing Unit==
Enables the next 2 check marks (which are not required if the conferencing resource is an innovaphone device).
Enables the next 2 check marks (which are not required if the conferencing resource is an innovaphone device).
|-
 
|valign=top nowrap=true|'''Conference Id Prefix'''
==Conference Id Prefix==
See above. Leave empty for the innovaphone CONF interface.
See above. Leave empty for the innovaphone CONF interface.
|-
 
|valign=top nowrap=true|'''Conference Id Suffix'''
==Conference Id Suffix==
See above. Leave '#' for the innovaphone CONF interface.
See above. Leave '#' for the innovaphone CONF interface.
|-
 
|valign=top nowrap=true|'''Alert Timeout'''
==Alert Timeout==
The broadcast conference object will call members and wait ''Alert Timeout'' seconds for the user to pick up the call.
The broadcast conference object will call members and wait ''Alert Timeout'' seconds for the user to pick up the call.
|-
 
|valign=top nowrap=true|'''Connecting Mode'''
==Connecting Mode==
This setting defines when members are connected to the conferencing unit.
This setting defines when members are connected to the conferencing unit.
{|left=3
{|left=3
Line 41: Line 38:
| '''When all users have answered, or at least one and after timeout'''||Same as above, except that if there are at least 2 members who have picked up and the timeout expired the members are connected.
| '''When all users have answered, or at least one and after timeout'''||Same as above, except that if there are at least 2 members who have picked up and the timeout expired the members are connected.
|}
|}
|-
 
|valign=top|'''Alert only at conference begin'''
==Alert only at conference begin==
If this is ticked, unconnected group members aren't alerted again with a new call to the conference if the conference is still running.
If this is ticked, unconnected group members aren't alerted again with a new call to the conference if the conference is still running.
|-
 
|valign=top nowrap=true|'''Only Group Members allowed'''
==Only Group Members allowed==
If this check box is not ticked, anyone can initiate the conference by calling the broadcast conference object.  If it is ticked, only group members can.
If this check box is not ticked, anyone can initiate the conference by calling the broadcast conference object.  If it is ticked, only group members can.
|-
 
|valign=top nowrap=true|'''Allow Announcement Calls'''
==Allow Announcement Calls==
If this is ticked, initiating announcement calls will trigger outgoing member invitation calls as announcement calls too.
If this is ticked, initiating announcement calls will trigger outgoing member invitation calls as announcement calls too.
|-
 
|valign=top nowrap=true|'''Call always as Announcement Call'''
==Call always as Announcement Call==
If this is ticked, all outgoing member invitation calls are sent as announcement calls.
If this is ticked, all outgoing member invitation calls are sent as announcement calls.
|}


  Only IP6000, IP800 and IP305 support local conferencing, one DSP is in use for each user in a conference call.
  Only IP6000, IP800 and IP305 support local conferencing, one DSP is in use for each user in a conference call.

Latest revision as of 22:30, 21 June 2011

A broadcast conference object uses a local or remote conferencing resource (e.g. a CONF interface) to implement an automatic multi-party conference. When the object is called, calls to all members of the groups the broadcast conference object is an active member itself are initiated. These calls then all participate in a single conference.

This object is built-in to the PBX and thus does not need a registration to work. It will run on the PBX that is set in the PBX field.

External Conference Resource Name

If the conference resource local to the broadcast conference object shall be used, you can leave this field empty. Otherwise, you must configure the object Name of an existing resource. When a called conference member picks up the call, it gets transferred to this object. This object will usually be either a conference resource on another innovaphone PBX or a 3rd party conferencing unit.

The call sent to the conferencing ressource will have a called party number that consists of the Conference Id Prefix + Conference Id + Conference Id Suffix. There will be no calling party number.

Create Dynamic Conference Id

Each individual conference running on a conferencing resource (a.k.a. conference room) needs a distinct conference-id. If this check box is ticked, conference ids will be created dynamically for new conferences. Please note that a single broadcast conference object never uses more than one conference object at a time.

Conference Id

If no Create Dynamic Conference Id is not checked, then you need to specify the conference id to be used here.

3rd Party Conferencing Unit

Enables the next 2 check marks (which are not required if the conferencing resource is an innovaphone device).

Conference Id Prefix

See above. Leave empty for the innovaphone CONF interface.

Conference Id Suffix

See above. Leave '#' for the innovaphone CONF interface.

Alert Timeout

The broadcast conference object will call members and wait Alert Timeout seconds for the user to pick up the call.

Connecting Mode

This setting defines when members are connected to the conferencing unit.

Direct after calling Members (including the initiator) are connected immediately.
With the first response Members are connected after the first called member picks up. The initiator will hear a tone meanwhile.
When all users have answered Members are connected only after all called member picked up. The initiator and all but the last called member will hear a tone meanwhile.
When all users have answered, or at least one and after timeout Same as above, except that if there are at least 2 members who have picked up and the timeout expired the members are connected.

Alert only at conference begin

If this is ticked, unconnected group members aren't alerted again with a new call to the conference if the conference is still running.

Only Group Members allowed

If this check box is not ticked, anyone can initiate the conference by calling the broadcast conference object. If it is ticked, only group members can.

Allow Announcement Calls

If this is ticked, initiating announcement calls will trigger outgoing member invitation calls as announcement calls too.

Call always as Announcement Call

If this is ticked, all outgoing member invitation calls are sent as announcement calls.

Only IP6000, IP800 and IP305 support local conferencing, one DSP is in use for each user in a conference call.
Some early IP6000 do not support this feature.  Refer to the upgrade details if you consider upgrading your hardware.


Please refer to Administration/Gateway/Interfaces for access to a generic conferencing resource if no Broadcast Conference is required.