A Conference extension allows users calling from phones connected to the system as well as callers outside the system (calling from a phone connected to the PSTN) to attend a group voice conversation.
To set up a Conference extension, first you need to define its general settings. Then you may customize it using specific options described below.
You may change settings at any time later on by clicking the Conference Center setup icon in the extension's management page.
All basic options related to the Conference Center extension are detailed below.
|Play sound <folder> <sound> before connecting to conference center|
Enable if you want a sound to be played to the caller prior to being connected to the extension.
|Conference room size|
Fill in the maximum number of users that can join the conversation. Between 2 and 99.
|Record conference conversations|
Here are the available options:
Enable music on hold
|If this option is not enabled, VoipNow will play the files located in the Default music on hold folder if there is only one user present in the conference.|
Music on hold folder
This folder contains the sound files that will be played in order when the caller is on hold or when the extension waits for an operation to be performed.
Default settings for scheduled conferences
Define scheduled conferences announcements and actions.
- Close the conference when all conference moderators exit: Terminate all calls if all conference moderators have logged out.
- Announce user count on joining conference: Announce any new participant about the number of users in the conference call.
- Announce users joining/leaving: Announce the users about any participant joining or leaving the conference call.
This section allows you to set up CallerID settings.
|CallerID name in public calls|
The options described below allow you to customize the CallerID name that will be displayed on the callee's screen when the extension is calling public destinations.
|CallerID number in public calls||The options described below allow you to customize the CallerID number that will be displayed on the callee's screen when the extension is calling public destinations.|
|Currently using CallerID numbers||Allows you to choose one or several CallerID numbers that will be sent when an outgoing call is initiated.|
The numbers available are the ones defined for the channel(s) (resource) used for routing the calls to public destinations.
Please note that a CallerID can be set as default even if it has not been assigned to the extension's DID pool.
Click here to see the fields required by the Public Phone Numbers form.
To associate a CallerID with the extension, you need to select the corresponding checkbox and click the Assign CallerIDs link. To disassociate a CallerID, you need to select the corresponding checkbox and click the Remove selected link.
Click here to expand what happens if you associate several CallerIDs to the extension.
1. If you have selected more than one CallerIDs for a resource (channel), then the system will send a random one to the public destination.
Let us assume that the outgoing calls are routed through a resource (channel), Resource #1, for which three public phone numbers have been defined and assigned to the client that owns the extension: 1123, 345876 and 2854478. If you associate all three of them with the extension, when initiating an outgoing call, the callee's phone terminal will display, if it supports the CallerID function, one of the three numbers.
2. If you have selected CallerIDs for more than one resource (channel), then the system will send the CallerID of the resource that routes the call.
Let us assume that the outgoing calls are routed through Resource #1, for which one public number has been defined and assigned to the client who owns the extension: 2255. You associate this number with the extension and another one, 6987560, defined for Resource #2. If it supports the CallerID function, when initiating an outgoing call, the callee's phone terminal will display 2255.
3. If calls are routed through a resource that does not have a public phone number assigned and you have a CallerID that belongs to another resource set as default, then the system will send the default CallerID.
Let us assume that the outgoing calls are routed through a resource (channel), Resource #1, for which no public phone numbers have been defined. Your default CallerID is set to 3689, which belongs to another resource (channel), Resource #2. If it supports the CallerID function, when initiating an outgoing call, the callee's phone terminal will display 3689.
Do not send CallerID on public calls
Applies if you do not want your CallerID to be sent to public destinations. If the callee's phone terminal supports the CallerID function, it will display the
Send public CallerID on internal calls
Applies if you want the public CallerID (when available) to be used for local and extended local calls as well. It allows the association between the CallerID of the Phone terminal user and an existing card code defined for the same CallerID.
Preserve original CallerID on transferred calls
|Applies if you want VoipNow to keep the original CallerID when the call is forwarded between destinations.|
Send SIP P-Asserted-Identity and P-Preferred-Identity headers
Allows the headers to be added to all outgoing INVITE requests sent from this extension.
The SIP P-Asserted-Identity header contains the caller ID number of the extension, e.g. P-Asserted-Identity:sip:email@example.com.
The P-Preferred-Identity header is sometimes used to indicate an additional identity of preference when there is a choice.
These headers are preserved only on outgoing external calls, e.g. P-Preferred-Identity: "John White" <sip:firstname.lastname@example.org>.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.