
Figure 3: Sample Avaya 3100 Mobile Communicator Gateway firewall configuration
If a user calls a client, the SIP signaling comes through the SPS. Real Time Protocol (RTP) for
announcements or Avaya 3100 Mobile Communicator Instant Conference calls takes place
between the Avaya 3100 Mobile Communicator Gateway and the IP telephone without using
the SPS.
To allow public internet traffic to reach the Avaya 3100 Mobile Communicator Gateway from
clients, while simultaneously providing Avaya 3100 Mobile Communicator Gateway access to
the ECS TLAN for SIP and RTP, you must carefully consider the data network and security
requirements of the Enterprise.
Proprietary communication between the Avaya 3100 Mobile Communicator Gateway and the
Avaya 3100 MC - Client for BlackBerry (without the BES, using HTTP), the Avaya 3100 MC -
Client for Nokia (using HTTPS), and the Avaya 3100 MC - Client for Windows Mobile (using
HTTPS) enables clients to initiate and modify calls for the user on the ECS. In the BES
configuration, the Avaya 3100 MC - Client for BlackBerry communicates with the BES, which
communicates with the Avaya 3100 Mobile Communicator Gateway. The Avaya 3100 MC -
Client for Nokia and Avaya 3100 MC - Client for Windows Mobile communicates directly with
the Avaya 3100 Mobile Communicator Gateway, as well as the Avaya 3100 MC - Client for
BlackBerry when configured without the BES.
Access to user records in an active directory server configured against the Avaya 3100 Mobile
Communicator Gateway uses a tunnel over HTTP or HTTPS. Configure the Avaya 3100 Mobile
Communicator Gateway to specify the query search base, which limits the search to a subtree
of the base.
Security requirements
Deployment Guide October 2010 19
Comentarios a estos manuales