Always run the Analog Trunk Tune-Up (UCX Release 7.0) or ectune utility (UCX Release 6.0) after the system has been installed and analog trunks connected to the system, but before it goes into production. If at anytime the trunks get changed, then the Analog Trunk Tune-up or ectune utility would need to be run again.
Configure the Card settings
Analog trunks are configured as DAHDI trunks on the UCX server.Step 1
The first step is to configure the installed analog card.- Go to PSTN Cards for details on configuring your installed analog hardware.
- You can configure one or more trunk groups here.
Step 2
The next step is to create the DAHDI trunk.- Go to Adding DAHDI Trunks for details on adding a DAHDI trunk
- On the Add DAHDI Trunk page, fill in all trunk specific parameters. You should configure at least the following fields:
- Trunk Name – Enter a descriptive name, e.g. Analog
- DAHDI Trunks – Select from the drop-down list the available groups and channels (The trunks groups configured in Step 1 will appear in the list.)
- Press the Submit Changes button to create the analog trunk
Step 3
The last step is to use the analog trunk in an Outbound Route:- Go to Outbound Routes for details on adding or editing an outbound route
- Under the section Trunk Sequence for Matched Routes, select the analog trunk that was created previously
- Press the Submit Changes button
Setting Disconnect Supervision parameters
If the analog trunk does not have disconnect supervision, then the DAHDI configuration needs to be changed to detect the busy or re-order tone applied by the far end (typically the central office).
Step 1 – Determine the Busy or Re-order tone pattern
Retrieve the Busy or Re-order Tone pattern for Release 7.0
The following process involves setting the debug level to a very high level, resulting in a significant number of messages accumulating in the log. Ensure that you disable the debugging level as soon as you finish the single test call!
- Navigate to PBX / PBX Tools
- In the Command field, enter command: core set debug 5 and click Execute
- Make a single (1) incoming call from outside using the analog trunk
- Hangup when the call reaches voicemail
- Wait for the call to be terminated on the UCX (default is 4 minutes)
- Disable the debug level 5 by entering command: core set debug 0 and clicking Execute
- Access the UCX by using SSH (eg. via PuTTY)
- From the UCX Command line, type: grep “busy detector” /var/log/asterisk/full
- If the system is already configured properly, this will not return any results (see note below)
- Unless the system is already configured correctly, there will likely be several lines similar to the following:
[2023-03-29 11:37:00.407] DEBUG[3300725][C-00000054] dsp.c: busy detector: FAILED with avgtone: 120 avgsilence 85 - From this, the UCX has identified the pattern as “120 msec on, 85 msec off” (note: your numbers may be different)
- You will enter this in Step 3, below.
Step 2 – Optimize the Busy Detect Count
You must also determine the number of beeps that you want to detect before checking to see if they match the reorder tone. The smaller the number there is a greater chance that the beeps could be caused by something else (like a call waiting tone, for example), but the larger the number the longer it will take before verifying that the beeps match the reorder timing, so the trunk will remain busy longer. E-MetroTel suggests using a Busy Detect Count of 4.
Step 3 – Set the Busy Detect Parameters
- Open UCX Administration
- From the System tab, select PSTN Cards
- From the top right corner of the page, select Global Settings
- Set Enable Busy Detect to Yes
- Set Busy Detect Count to 4 or a different value that you have chosen
- Set the Busy Pattern to the values determined for avgtone and avgsilence you determined above (in our example: 120,85) with no space between the comma and the second number.
- Press the Save button
- Press the Apply Config bar followed by the Reload DAHDI Configuration button