McDewey

CUBE Enterprise G Media Gateway Control Protocol (MGCP) G Session Initiation Protocol (SIP) G H323 Protocol Suite G T30 Signaling G Components Used The information in this document is based on these software and hardware versions: Cisco IOS® Releases 12.4T, 15.0M, 15.0T, 15.1M, 15.1T, 15.2M, 15.2T, 15.3T on Cisco Integrated Services Routers (ISR) Series 2800, 3800, 2900, 3900, 3900e or the Cisco AS5400XM Universal Gateway Note: This configuration example is not limited to the software versions and hardware platforms listed here. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Background Information FoIP with CUBE operates in a multitude of environments and is implemented in order to leverage current VoIP networks for reliable fax services. There are multiple fax protocols that CUBE supports along with a multitude of switchover mechanisms. However, in the context of IP service providers, you must adhere to fax protocols and switchover methods that are supported by vendors outside of Cisco. In FoIP call flows, CUBE is between the Terminating Gateway (TGW) and the Originating Gateway (OGW). From a signaling perspective, the CUBE configuration either permits, or denies, the switchover from a voice call to a fax call. Due to the fact that FoIP protocols are negotiated end-to-end in a VoIP environment, it is essential that everything from the OGW to the TGW are configured in order to use the same FoIP protocol. It is important to know what FoIP flows are supported and what configuration is necessary on CUBE, as well as the TGWs and OGWs, in order to ensure reliable fax communication. CUBE Fax Call Flows