Configuring an Asterisk device

In order to change the configuration of an Asterisk device, right-click on the appropriate phone in the Flexor Manager Devices and Applications window and select the Configure option as shown below.

This will open the configuration window for this device. The screen below is from Flexor version 2.1.131.

The available configuration options are as follows:

Detected context

Extensions in Asterisk are defined as part of a context. In order to initiate and redirect calls, Flexor Connect for Asterisk needs to know which context  to use for a given extension. For SIP extensions, it is normally possible to determine what context to use for the extension, but this is not always correct. Furthermore, it is not possible to identify the correct context to use for IAX extensions. For these extensions, Flexor Connect for Asterisk will initially try to use the 'default' context which is available on many servers.

Override Detected Context

(Un-checked by default) If your extension is not available in the context that Flexor Connect for Asterisk chooses, it is necessary to enter the correct context manually. Check the 'Override detected context' button, and enter the correct context in the text box (your Asterisk administrator should be able to tell you what the correct context is for your extension).

Detected CallerID

Calls made from extensions in Asterisk can be assigned a CallerID to send with the call. In order to set this, Flexor Connect for Asterisk needs to know which CallerID to use for a given extension. For SIP and IAX extensions, it is normally possible to determine what CallerID to use for the extension, but this is not always the desired value. For these extensions, Flexor Connect for Asterisk will initially try to use the detected CallerID which is available on many servers.

Override Detected CallerID

(Un-checked by default) If you wish to specify a CallerID to send with the call, it is necessary to enter the CallerID manually. Check the 'Override detected CallerID' option, and enter the desired CallerID in the text box.

End Calls with Unlink event

(Un-checked by default) This option should only be checked if instructed to do so by Camrivox Support.

Allow CallerID Update

(Checked by default) This option should only be unchecked if instructed to do so by Camrivox support. If matches are not being made and the Call Summary reports number withheld please review the following FAQ.

Ignore Local Calls

(Unchecked by default) This option should only be checked if instructed to do so by Camrivox support. It's use maybe required if multiple Call Summary windows appear for the same in bound call.

Simple Asterisk Queues

(Checked by default) Please see the following section for further information on support for Asterisk Queues.

Trigger Ringing from NewState

(Unchecked by default) This option should only be checked if instructed to do so by Camrivox support.

Report call action failures

(Checked by default) This option allows you to choose whether you want to be notified if  an attempt to initiate or redirect a call fails. By default, this is turned on, but it is optional because Asterisk reports calls that you initiate, but then reject on your handset as having failed. Clearly, in this case you do not need to be told that the call never got through!

If you find you are often starting calls and then cancelling them on the handset, and you do not want the warning message, you can turn this option off. Otherwise, and particularly if you have enabled the auto-answer feature below, you can leave it turned on.

SIP Configuration

Auto-answer extension

If the device is using the SIP protocol, your Asterisk administrator may have provided an extension number which will make your phone auto-answer when it is called from Asterisk. If this is the case, enter the extension in the "Auto-dial extension" field. If this is configured, it means that when you  use click-to-dial from a CRM application you will not have to accept the call on your phone before it dials the number you want.

Auto-answer context

If the auto-answer extension requires a different context to be used from the detected or override context specified above then enter the context in the "Auto-answer context" field.

Location of Call Recordings

Path to Folder

Call recording integration can be configured for the Asterisk system so that links to call recordings can be placed within the Activity History in the CRM by Flexor. If call recording is configured on the Asterisk system, the file name will be sent to Flexor for each call. However, in order for the links within the Activity History to be click able, Flexor needs to know the UNC path to the folder where the recordings will be placed on the Asterisk server. (e.g. "\\Asterisk\CallRecordings\MyUserName\"). This information should be added to this field. If you are using Salesforce please contact support for additonal information to enable this.

Dialling Rules

To configure the dialling rules for the device, click the "Dialling Rules" button. For more information about configuring dialling rules, please see the Flexor Manager documentation on Configuring Dialing Rules.