Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

A fully operational MDM setup requires a To have a fully functional Mobile Device Management system, it is necessary to have a properly deployed set of CapaInstaller services that are deployed correctly in within the company's network infrastructure. Consult the illustration and tables below when setting up your network for CapaInstaller MDM.

Table of Contents
maxLevel2
minLevel2



Services

Service

Port Number

Data Type

Direction

Destination DNS URL - Outgoing

Description

cimdm

443 (SSL)

TCP

PUBLIC

->

DMZ

mobile

Mobile devices

get

retrieve configurations and applications

cimdm

443 (SSL)

TCP

DMZ → PUBLIC

api.capaone.com

Gateway for:

Apple Push Network Service (APNS):

http://support.apple.com/kb/TS4264 

Google Cloud Messaging:

http://en.wikipedia.org/wiki/Google_Cloud_Messaging

Microsoft Open Mobile Alliance (OMA):

https://en.wikipedia.org/wiki/OMA_Device_Management

Self
Selfvice
Service Portal9443(
SSL
Default)TCPPUBLIC
->
DMZ
Used to access the Self-Service portal from the devices

cibackend

5023 (

CapaInstaller MDM default

Default)

TCP

DMZ → SERVER 


cimdm get profiles and configurations

cifrontend

5022 (

CapaInstaller Public Frontend

Default)

TCP

DMZ → SERVER 


cimdm authenticates users when enrolling devices

cifrontend
80
443 (SSL)TCPSERVER → PUBLICdownload.capainstaller.com
retrieve
Retrieve updated information about device models and versions



Devices

Communication from For end-user devices to services to support mobile device management, the devices must communicate with different network services


Devices                           

Port Number

Data Type

Direction

Destination DNS URL - Outgoing

Description

All devices443 (SSL)TCPLAN
-> Public
→ PUBLICDMZ ServerUsed for secure communication between iOS devices and the MDM server.
All devices8443

Devices                           

Port Number

Data Type

Direction

Destination DNS URL if Outgoing

Description

TCPLAN -> Public

Android devices

5228 (Google server)

TCP

LAN

-> Public

→ PUBLIC

android.apis.google.com

gcm-http.googleapis.com

fcm.googleapis.com

This port is used for communication between Android devices and Google Cloud Messaging (GCM), which
is used for sending
sends push notifications and other data to Android devices.

Android devices

5229 (Google server)

TCP

LAN

-> Public

→ PUBLIC

android.apis.google.com

gcm-http.googleapis.com

fcm.googleapis.com

This port is used for communication between Android devices and GCM over a secure connection.

Android devices

5230 (Google server)

TCP

LAN

-> Public

→ PUBLIC

android.apis.google.com

gcm-http.googleapis.com

fcm.googleapis.com

This port is used for communication between Android devices and GCM for sending and receiving multicast messages.
Android devices443 (Google server)TCPLAN
-> Public
→ PUBLIC

android.apis.google.com

gcm-http.googleapis.com

fcm.googleapis.com

play.google.com

This port is used for secure communication between Android devices and the MDM server.
Apple devices2195 (Apple server)TCPLAN
-> Public
→ PUBLICgateway.push.apple.com Used for sending push notifications to iOS devices.
Apple devices2196 (Apple server)TCPLAN
-> Public
→ PUBLICfeedback.push.apple.comUsed by the APNs Feedback Service to send feedback to the MDM server about failed push notifications.
Apple devices5223 (Apple server)TCPLAN
-> Public
→ PUBLIC
Used for communication between iOS devices and
the
APNs. It is also used for device activation.
Windows Phone device443 (Microsoft server)TCPLAN
-> Public
→ PUBLIC