Mobile Communication Gateway 3100 network deployment 35When you deploy the MCG 3100, data originates from the BES for all of theMCC 3100 for BlackBerry clients. The RIM infrastructure manages theboundary between the untrusted and trusted network, making the overallsolution deployment less complex.MCC 3100 for NokiaThe HTTPS traffic from the public internet (untrusted) into the Enterprise IPnetwork (where the MCG 3100 resides) needs to be considered.The MCC 3100 for Nokia supports all device security configurations asadministered by the system administrator.Certificates to support HTTPS on the Nokia phones need to be deployedas part of the client deployment process. The Nokia devices require theMCG 3100 Fully Qualified Directory Name (FQDN) to generate certificates.The FQDN must resolve on both the cell data network (the internet) andon the wireless network that is used by the Nokia phone to communicatewith the MCG 3100.You can use wireless access in place of cell data access for HTTPSsignaling with the MCG 3100. After the MCC 3100 for Nokia is associatedwith the wireless network, the MCC 3100 for Nokia has Internet Protocol(IP) access to the MCG 3100.Mobile Communication Gateway 3100 network deploymentThe Mobile Communication Gateway 3100 (MCG 3100) requires thefollowing network infrastructure:• access to a CS 1000 including a call server, SIP gateway, and SIP ProxyServer• access to the CS 1000 TLAN, including all SIP infastructure, mediagateways, and any IP endpoint that can originate or terminate real-timetransport• access to a BlackBerry Enterprise Server (BES) if the MCG 3100supports the MCC 3100 for BlackBerryFigure 6 "Data access from BlackBerry and Nokia devices" (page 36) showsdata access from the BlackBerry and Nokia devices.Nortel Mobile Communication 3100 Series PortfolioNortel Mobile Communication 3100 — Planning and EngineeringNN42030-200 01.09 StandardRelease 2.0 1 November 2007Copyright © 2007, Nortel Networks.