Installation guide
Configuring analog trunks 5-14
Chapter 5: Configuring Analog and Digital Trunks
Wave Global Administrator Guide
Configuring analog trunks
You use the Trunk Configuration applet to configure analog trunk settings for the analog trunk
ports on the Integrated Services Card or on expansion cards and modules. Refer to your Service
Confirmation Letter, provided by your service provider, for the appropriate values to set.
Before configuring the trunks, configure the trunk groups you want to assign to the analog
trunks. For information about configuring trunk groups, see “About creating new trunk groups”
on page 5-2.
Caution: If you need to permanently remove an analog trunk module from your Wave
Server, or replace an analog trunk module with a different module, you must first
assign all ports of the module to None in the Trunk Group drop-down list in the Trunk
Configuration applet. For details about this drop-down list, see step 5 of “Configuring
analog channels” on page 5-16.
Complete the following tasks to configure analog trunks:
• Configuring analog trunk card or module settings
• Configuring analog channels
This section also describes how to customize AC impedance settings on analog trunk ports in
order to correct echo return loss problems. See page 5-18.
Using analog loop start trunks with mobile extensions
Using mobile extensions over trunks which do not support disconnect supervision can cause a
trunk to get stuck, requiring you to disable and re-enable the trunk via the Trunk Configuration
applet. This problem can occur when a user on a mobile extension connected via an analog loop
start trunk puts a call on hold and goes onhook. The problem stems from the fact that the CO
does not always propagate disconnects over loop start trunks, so Wave is never informed when
the user goes onhook.
It is highly recommended that all analog trunks be tested for disconnect supervision by calling
an external number from a Wave phone, connecting, and then having the called (external) party
hang up. If the Trunk Monitor indicates that the trunk cleared before the local extension went
onhook, then the trunk does support disconnect supervision and can be safely used for mobile
extensions. For more about mobile extensions, see “Using mobile extensions and imitating a
station on externally routed calls” on page 11-56.
Release 2.0
September 2010