Avaya 3100 Mobile Communicator Deployment Podręcznik Użytkownika Strona 31

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 172
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 30
- Each user requires one Universal Extension (UEXT). Each UEXT supports the SIP
interface on the client. Configure the UEXT with the Fixed Mobile Convergence Line
(FMCL) subtype.
The FMCL subtype requires an Incremental Software Management (ISM)
independent of the Mobile Extension (MOBX) subtype.
- SIP Access Port license
• SIP Gateway
• SPS, using the Avaya CS 1000 NRS-SPS on the Linux-based NRS.
- Configure each Avaya 3100 Mobile Communicator Gateway as a Dynamic Gateway
Endpoint with an endpoint name. Configure the Dynamic Gateway Endpoint with
authentication turned off.
- Each client requires the configuration of an NRS-SPS User Endpoint (UE). Clients
use the UE for user name and password information, not for SIP routing. Therefore,
the NRS-SPS must never match a destination number against the client UEs
(including the corresponding UEXT Target DN).
• SPS, using the Avaya CS 1000 Release 6.0 NRS
Avaya 3100 Mobile Communicator Gateway must be configured to use proxy mode
when registering to this server.
The Direct Inward Dial (DID) number for the Dial in Service DN terminates on the Avaya 3100
Mobile Communicator Gateway.
Configure the Avaya CS 1000 with a mobility prefix to support the client. The UEXT target DN
uses the mobility prefix as a prefix to identify mobile users. The Mobility Prefix is the Local
Exchange code (NXX) that directs the call to the Avaya 3100 Mobile Communicator within the
desired dialing plan. The Mobility Prefix is a unique digit sequence that does not conflict with
the existing Avaya CS 1000 Universal Dialing Plan (UDP), Coordinated Dialing Plan (CDP),
and routing configuration.
The Multiple Access Directory Number (MADN) is a DN that appears on multiple terminal
numbers (TN). The Multiple Appearance Directory Number Redirection Prime (MARP) is a
designation that is put on one of the TNs to identify that specific features apply to the DN that is
on multiple TNs should be configured for the group on the TN that is the MARP. For more
information, see Avaya Communication Server 1000 Features and Services Fundamentals,
NN43001-106.
The Avaya CS 1000 NRS-SPS supports the Source Based Routing (SBR) feature. SBR
ensures that, for all users of an Avaya 3100 Mobile Communicator Gateway, the CLID NCOS
and dial plan they see on their mobile phone is consistent with their desk phone. The SPS
routes all Avaya 3100 Mobile Communicator call attempts to the user's home call server so
that those features configured on the home call server can be applied to the Avaya 3100 Mobile
Communicator call. For information about Source Based Routing (SBR), see
Avaya CS 1000
Source Based Routing on page 29.
Avaya CS 1000 engineering for Avaya 3100 Mobile Communicator
Deployment Guide October 2010 31
Przeglądanie stron 30
1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 171 172

Komentarze do niniejszej Instrukcji

Brak uwag