Settings that apply to all the cards and spans can be configured via the Settings section located at the top right hand corner of the page.
If you made changes to the settings, you will need to follow the instructions at the top of the Web-based Configuration Utility page for the changes to take effect, including pressing the Apply Config pink bar along with any instructions to reload the DAHDI Configuration and/or restart the DAHDI service.
Global Settings
Field | Default Value | Description |
---|---|---|
Select Language | English | Specify the language. |
Enable Busy Detect | Yes | On trunk interfaces (FXS) and E&M interfaces (E&M, Wink, Feature Group D etc.) it can be useful to perform busy detection either in an effort to detect hangup or for detecting busies. This enables listening for the beep-beep busy pattern. |
Busy Detect Count | 10 | If busydetect is enabled, it is also possible to specify how many busy tones to wait for before hanging up. The default is 3, but is might be safer to set for 6 or even 8. mind that the higher the number, the more time that will be needed to hangup a channel, but lowers the probability that you will get random hangups. |
Busy Pattern | 500,500 | If busydetect is enabled, it is also possible to specify the cadence of your busy signal. In many countries, it is 500 msec on, 500 msec off. Without busypattern specified, any regular sound-silence pattern that repeats busycount times is accepted as a busy signal. If you specify busypattern, the length of the sound (tone) and silence is checked further reducing the chance of a false positive. |
Use Caller ID | Yes | Specify whether to use caller ID. |
Enable Call Waiting | Yes | Specify whether to enable call waiting on internal extensions. With this set to yes, busy extensions will hear the call-waiting tone, and can use hook-flash to switch between callers. The dial() app will not return the BUSY result for extensions. |
Use Caller ID Presentation | Yes | Specify whether to use the caller ID presentation for outgoing calls that the calling switch is sending |
Enable Three Way Calling | Yes | Support three way calling |
Enable Transfer | Yes | For FXS ports (either direct analog or over T1/E1): Support hook-flash call transfer (requires three way calling enabled), also enables call parking (overrides the canpark parameter)For digital ports using ISDN PRI protocols: Support switch-side transfer (called 2BCT, RLT or other names). This setting must be enabled on both ports involved, and the facilityenable setting must also be enabled to allow sending the transfer to the ISDN switch, since it is sent in a FACILITY message |
Enable Call Forwarding | Yes | Support call forward variable |
Enable Call Return | Yes | Support Call Return (*69, if your dialplan does not catch this first) |
Enable Echo Canceling | 512 taps | Enable echo cancellation is on by default, and set to 512 taps. Can be disabled (set to ‘No’) or other settings for greater or less processing. |
Enable EC when bridged | No | Generally, it is not necessary (and undesirable) to echo cancel when the circuit path is entrely TDM. You may, however, change this behavior by enabling the echo canceler during pure TDM bridging. |
Enable Echo Training | No | In some cases, the echo canceller does not train quickly enough and there is echo at the beginning of a call. Enabling echo training will cause DAHDI to briefly mute the channel, send an impulse, and use the impulse response to pre-train the echo canceller so it can start out with a much closer idea of the actual echo. Value may be yes, no, or a number of milliseconds to delay before training, default is 400. WARNING: In some cases this option can make echo worse! If you are trying to debug an echo problem, it is worth checking to see if your echo is better with the option set to yes or no. Use whatever setting that gives the best result. |
Answer Immediately | No | Specify whether the channel should be answered immediately or if the simple switch should provide dialtone, read digits, etc. Note: if yes the dialplan execution will always start at extension ‘s’ priority 1 regardless of the dialed number. |
Fax Detection | No | Enable fax detection |
Receive Gain | 0.0 | The values are in decibels (db). Positive number increases volume level, negative number decreases volume level. |
Transmit Gain | 0.0 | The values are in decibels (db). Positive number increases volume level, negative number decreases volume level. |
Other Global Dahdi Settings | Enter the dahdi parameter in the first box and the value in the second box. |
Note that the settings for Enable Echo Canceling have recently changed with the introduction of the Galaxy Mini. If you are experiencing echo issues please ensure that the value is set to 512 taps and that you have run the ectune procedures described in Optimize Trunk Settings.
System Settings
Field | Description |
---|---|
Tone Region | Choose your country or nearest neighbouring country for default tones (e.g. dialtone, ringtone, busytone etc.) |
Other Dahdi System Settings | Enter the dahdi parameter in the first box and the value in the second box. |
Driver Settings
Note – Depending on the level of Driver software in the system, overriding the physical Line Mode switch setting on a digital DAHDI card from T1 to E1 operation (or E1 to T1) will either have a specific drop down menu item in the Driver settings, or it may require using the Other Driver Settings field and inputting the desired operation (T1 or E1) in the value field. See below.
Field | Description |
---|---|
Driver Name | Specify the kernel module used by the installed analog hardware. |
Default Line Mode | The recommended way to set line mode on your Digium 1-, 2-, 4-port (span) digital telephony cards is to set the jumper(s) on the card for either T1 or E1 mode for each span on the card. With the jumper OFF, the span is ready for T1 mode; with the jumper ON, the span is ready for E1 mode. (See PRI Card – Interface Selection for details.) However, sometimes if a card is installed in a server without first setting the jumper(s) correctly, and it is inconvenient to remove the card from the server to access the jumper(s), then the “default_linemode” option can be passed when the card’s device driver is loaded. |
Other Driver Settings | Enter the dahdi parameter in the first box and the value in the second box. For example, if the Default Line Mode parameter noted above does not appear in the list of drop down settings, enter “default_linemode” in the first filed, and the desired setting of “t1” or “e1” in the second field. |
If an FXO card is installed in a country other than the default USA, use the drop-down list in the Opermode field to select the desired country and select the checkbox beside the field.
If you are experiencing echo issues please ensure that the Opermode is set to the correct country first then run the ectune procedures described in Optimize Trunk Settings.
Special Configuration for CLID
In some regions in Canada, Trinidad and potentially some countries in South America, there are Central Offices that send the CLID in a way that needs a special configuration of the opvxa24xx driver on the UCX to correctly display the CLID. In these situations, add the following parameter to the Other Driver Settings field for the opvxa24xx driver: cidsupport = 0. (See example below)
Important note: Make sure there are no spaces before or after the parameter name “cidsupport“.
Apply Changes
If you made changes to the settings, you will need to follow the instructions at the top of the UCX Administration page for the changes to take effect, including pressing the Apply Config pink bar along with any instructions to reload the DAHDI Configuration and/or restart the DAHDI service.