47-5
Cisco ASA 5500 Series Configuration Guide using ASDM
OL-20339-01
Chapter 47      Configuring Cisco Intercompany Media Engine Proxy
  Information About Cisco Intercompany Media Engine Proxy
Call Fallback to the PSTN
Cisco Intercompany Media Engine provides features that manage the QoS on the Internet, such as the 
ability to monitor QoS of the RTP traffic in real-time and fallback to PSTN automatically if problems 
arise. Call fallback from Internet VoIP calls to the public switched telephone network (PSTN) can occur 
for two reasons changes in connection quality and signal failure for the Cisco Intercompany Media 
Engine. 
Internet connections can vary wildly in their quality and vary over time. Therefore, even if a call is sent 
over VoIP because the quality of the connection was good, the connection quality might worsen mid-call. 
To ensure an overall good experience for the end user, Cisco Intercompany Media Engine attempts to 
perform a mid-call fallback.
Performing a mid-call fallback requires the adaptive security appliance to monitor the RTP packets 
coming from the Internet and send information into an RTP Monitoring Algorithm (RMA) API, which 
will indicates to the adaptive security appliance whether fallback is required. If fallback is required, the 
adaptive security appliance sends a REFER message to Cisco UCM to tell it that it needs to fallback the 
call to PSTN.
The TLS signaling connections from the Cisco UCM are terminated on the adaptive security appliance 
and a TCP or TLS connection is initiated to the Cisco UCM. SRTP (media) sent from external IP phones 
to the internal network IP phone via the adaptive security appliance is converted to RTP. The adaptive 
security appliance inserts itself into the media path by modifying the SIP signaling messages that are 
sent over the SIP trunk between Cisco UCMs. TLS (signaling) and SRTP are always terminated on the 
adaptive security appliance. 
If signaling problems occur, the call falls back to the PSTN; however, the Cisco UCM initiates the PSTN 
fall back and the adaptive security appliance does not send REFER message.
Architecture and Deployment Scenarios for Cisco Intercompany Media Engine
This section includes the following topics:
• Architecture, page 47-5
• Basic Deployment, page 47-6
• Off Path Deployment, page 47-7
Architecture
Within the enterprise, Cisco Intercompany Media Engine is deployed with the following components for 
the following purposes: 
• The adaptive security appliance—Enabled with the Cisco Intercompany Media Engine Proxy, 
provides perimeter security functions and inspects SIP signaling between SIP trunks.
• Cisco Intercompany Media Engine (UC-IME) server— Located in the DMZ, provides an automated 
provisioning service by learning new VoIP routes to particular phone numbers, and recording those 
routes in Cisco UCM. The Cisco Intercompany Media Engine server does not perform call control.
• Cisco Unified Communications Manager (Cisco UCM)—Responsible for call control and 
processing. Cisco UCM connects to the Cisco Intercompany Media Engine server by using the 
Access Protocol to publish and exchange updates. The architecture can consist of a single Cisco 
UCM or a Cisco UCM cluster within the enterprise.