
Data access planning
This section describes things to consider when planning data access.
Avaya CS 1000 data access considerations on page 53
Avaya CS 1000 data access considerations
The Avaya 3100 Mobile Communicator Gateway requires data access to the TLAN of the
Avaya CS 1000. The Avaya 3100 Mobile Communicator Gateway uses the Avaya CS 1000
SPS as the SIP Signaling Proxy. The media for all calls to and from Avaya 3100 MC - Clients is
anchored on the Avaya 3100 Mobile Communicator Gateway. The Avaya 3100 Mobile
Communicator Gateway will accept or transmit RTP to any IP endpoint within the enterprise
(for example, Media Cards, Other SIP clients, IP sets).
Example
If an UNISTIM set calls a user answering through the Avaya 3100 MC - Client on the mobile
phone the RTP for the active call will be between the Avaya 3100 Mobile Communicator
Gateway and IP set directly and then forwarded from the Avaya 3100 Mobile Communicator
Gateway to the Avaya CS 1000 media gateway (for the trunk call to the mobile phone)
Careful consideration is required based on the data network and security requirements of the
Enterprise to allow the public internet traffic to reach the Avaya 3100 Mobile Communicator
Gateway from the clients while at the same time giving the Avaya 3100 Mobile Communicator
Gateway access to the TLAN of the Avaya CS 1000 for SIP and RTP.
Service DN
The Service DN is a PSTN DID DN that is downloaded to the Mobile Client from the Avaya
3100 Mobile Communicator Gateway when it registers to the Avaya 3100 Mobile
Communicator Gateway for the first time. When the Mobile Client originates a direct outbound
call it dials the Service DN and is connected to the Avaya CS 1000. The Avaya CS 1000 is
configured to translate the Service DN to the format <mobility prefix><service DN>. The Avaya
CS 1000 then maps the call to the SPS/NRS for resolution. The SPS/NRS then maps the call to
the Avaya 3100 Mobile Communicator Gateway based on the routing rule built to resolve all
dialing strings preceded by the mobility prefix.
In the following example, 888 is the mobility prefix and 5066404681 is the service Directory
Number (DN).
Data access planning
Deployment Guide October 2010 53
Comentarios a estos manuales