Avaya 3100 Mobile Communicator Deployment Guide de l'utilisateur Page 30

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 172
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 29
Gateway contains the tag x-nt-net-feature=x-nt-home. For example, the following request URI
triggers SBR:
INVITE sip:[email protected];x-nt-sip-line-service;x-nt-net-feature=x-nt-home SIP/
2.0
SBR causes the Avaya CS 1000 Network Routing Service-SIP Proxy Service (NRS-SPS) to
route the call attempt (INVITE) to the P-Asserted-Id in the SIP INVITE instead of using the
Request URI.
Using SBR means that all calls from a SIP user route to the home call server for origination,
allowing the call server to apply features such as Calling Line ID (CLID) and Network Class of
Service (NCOS) to SIP calls.
In the Avaya 3100 Mobile Communicator Gateway, use the User Prefix/Phone-context for Call
origination field to configure SBR. For information, see Avaya 3100 Mobile Communicator
Administration and Security, NN42030-600.
Avaya CS 1000 package requirements
Avaya CS 1000 requires the following packages to support Avaya 3100 Mobile Communicator:
• FMCL package (414)
• Mobile Extension (412)
• PCA (398)
• ISDN (145)
If the Avaya 3100 Mobile Communicator supports the CallPilot Message Waiting Indicator, the
following package must be licensed:
Premium Service and NMC (175, 219)
Avaya CS 1000 engineering for Avaya 3100 Mobile
Communicator
The Avaya 3100 Mobile Communicator - Web UI, Avaya 3100 MC - Client for BlackBerry, Avaya
3100 MC - Client for Nokia, Avaya 3100 MC - Client for Windows Mobile, and Avaya 3100
Mobile Communicator Gateway depend on the following Avaya CS 1000 components:
• Avaya CS 1000
Interworking requirements with CS 1000
30 Deployment Guide October 2010
Vue de la page 29
1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 171 172

Commentaires sur ces manuels

Pas de commentaire