Configuring Call Handling
How to Configure Cisco Unified SCCP SRST
135
Cisco Unified SCCP and SIP SRST System Administrator Guide
OL-13143-04
phone is considered. If the
auto-line
command is configured on the phone, the specified autoline (if idle)
takes precedence over other nonauto lines. If no idle line is available on the transferor phone, a blind
transfer is initiated instead of the consultative transfer.
During the consultative transfer, the transferor line to the transferee party is locked on the transferor
phone to prevent it from being stolen by other phones sharing the same directory number. When the user
presses the Transfer soft key for a consultative transfer, the Transfer soft key does not display while
digits are being dialed and collected on this seized consultative transfer call leg. The method for
consultative transfer pattern matching, blind transfer, PSTN transfer blocking, or after-hour blocking
criteria remain the same although the manipulation after the matching is different. When the criteria for
the blind transfer is met, Cisco Unified SMST terminates the consultative transfer call leg, informs the
Cisco IOS software to transfer the call, and then terminates the original call bubble. The PARK FAC code
is handled in the same way as by a new call which requires that a ten-second timer is applied by the Cisco
IOS software.
Note
The enhancement, by default, collects the transfer digits from the new call leg. If required, you can
configure the system to collect the transfer digits from the original call leg. See the
“Configuring
Transfer Digit Collection Method” section on page 136
.
The error handling for transfer failure because of transfer blocking or interdigit timer expiration remains.
It includes displaying an error message on the prompt line and logging it if “debug ephone error” is
enabled, playing a fast-busy or busy tone, and terminating the consultative transfer call leg.
No new configuration is required to support these enhancements.
Conference Calls
No configuration steps are required for these conference call enhancements.
Single-Line Directory Number
If the initiating party for the conference call is a single-line directory number and the phone has multiple
directory numbers configured, the system selects another directory number’s idle channel for creating
the conference. If there are multiple directory numbers (dual-line or single-line directory numbers) on
the phone and each has calls on hold, the system prompts the user to select a line for the conference call.
Dual-Line Directory Number
If the initiating party for the conference call is a dual-line directory number, the system selects another
idle channel from the dual-line directory number. If the selected channel has a call on hold, the
conference operation will automatically select the hold channel and create the conference.
Octo-Line Directory Number
If the initiating party for the conference call is an octo-line directory number, the system selects an idle
channel from the initiating party directory number and the user must establish a new call to complete the
conference. If there is no idle channel on the same directory number, other idle directory numbers or
channels on the same phone are not selected. If there are existing calls on hold on the other channels of
the same directory number or other directory numbers, the user will not have the option to select them
to join the conference. If there is no idle channel on the same directory number, the conference will abort
with a No Line Available message.
