Non vedo il punto di domanda...ad ogni modo (e si trova, a ben cercare, nel manuale "OpenScape Office V3 HX Installation Guide") qui ci sono le risposte (anzi, la risposta) che cerchi:
Integrating OpenScape Office HX in a HiPath 3000 internetworkScenario:Multiple HiPath 3000 V8 (
un refuso...penso che valga V9 piuttosto che V8) communication systems with a local OpenScape Office HX connected to each of them are to be networked with one another. The networking of HiPath 3000 as well as the connection of OpenScape Office HX occur via the H.323-Q protocol (CorNet-NQ tunneled in the H.323 protocol).
OpenScape Office HX provides not only local features for the respective HiPath 3000 node (e.g., AutoAttendant, announcements, and fax), but also network-wide functions (such as call forwarding, call transfer or conferencing). Features such as Voicemail or the Multimedia Contact Center are, however, always provided by the OpenScape Office HX connected to the respective HiPath 3000 node.
RestrictionsThe following restrictions apply for an internetwork with OpenScape Office HX:
- Open numbering cannot be used. Only closed numbering is supported.
- It is not possible to cross-link the OpenScape Office applications between the local OpenScape Office HX systems. Consequently, the presence statuses of users of other OpenScape Office HX nodes are not visible, for example.
- A linked, multi-node call diversion or forwarding to OpenScape Office HX in a foreign HiPath 3000 node will not be followed.
- OpenScape Office HX is connected to the HiPath 3000 as an external H.323 gateway. Therefore, in this scenario, no additional networking with HiPath 4000 is possible via H.323-Q.
- Only route 8 of the HiPath 3000 may be used for the connection of the OpenScape Office HX.
- Due to the licensing model, the HiPath 3000 internetwork with the integrated OpenScape Office HX cannot be administered with the HiPath 5000 RSM.
PrerequisitesThe following preconditions should be checked before the setup:
- The components involved have the following states:
- HiPath 3000 V9 R1.x.x or later <-- ed Io aggiungo V9 R2.2.x almeno
- OpenScape Office HX V3 R2.x.x or later <-- ed Io aggiungo V3 R3.3.x almeno
- HiPath 3000 V9 and the networking of HiPath 3000 V9 and OpenScape Office HX have already been configured (see previous sections).
ProcedureThe steps described below must be performed on all HiPath 3000 nodes in the internetwork where an OpenScape Office HX is locally connected.
Activating the system flag "
Networked CTI domain" enables
CSTA monitoring for IP trunks (The only exceptions are trunks to which route 8 was assigned).
Come se non bastasse valgono anche le indicazioni presenti nella R.N. di HiPath 3000 V9 R2.2.x:Network- Only star networks are supported: the OpenScape Voice must be the central node in the IP-Trunking network. <-- beh...questa è interessante (anche SE credo che si riferiscano ad OSO LX piuttosto di OSO HX, anche perchè con HX non avrebbe senso una simile restrizione)
- Two HiPath 3000 systems cannot be networked via a direct IP connection. <-- come conseguenza della restrizione sopra indicata
- The HiPath 3000 gateways must not be networked with each other or to other communication systems other than the OpenScape Voice. <-- come conseguenza della restrizione sopra indicata
- HiPath 5000 RSM is not supported. <-- fare attenzione se si ha una rete di HiPath 3000 gestita con HiPath 5000 RSM!
- Networking to OpenScape Voice is via star network topology. <-- dove, per centro stella, intendono un OSO LX ad esempio...vedi sopra
- SIP-Q trunks should be configured automatically as Ext. SIP trunk with Trunk Group 10 and is not allowed to be changed manually to trunk group 16. <-- questi Trunks NON sono quelli che valgono tra HiPath 3000 ed OSO HX, CorNet-IP, bensì quelli tra HiPath 3000 ed OSO MX/LX...altrimenti si tratterebbe di una incongruenza con le restrizioni enunciate in OSO HX sopra
- HiPath 3000 parameter "Use always DSP" has to be set for SIP-Q trunk group 10. <-- come conseguenza della restrizione sopra indicata
- E.164 networking protocol must be used. <-- questa restrizione invece vale proprio nel caso di Internetworking tra vari sistemi HiPath 3000 V9 connessi ad un altro nodo dove c'è (anche) un OSO HX
In particolare, quest'ultima restrizione è meglio spiegata qui: When HiPath 3000 V9 is connected with OSO HX V3, E.164 system wide flag must be activated. In addition, in Settings Lines/Networking Routes, the location gateway route must have PABX number-incoming fields (like Country code and/or Local Area code and/or PABX number) configured.Dovrebbe bastare...
Saluti, Kimera.
