13.1.14 Private Network
•All PBXs in the network must be
•Only
•Mailboxes for extensions connected to other PBXs in the network must be set up manually.
•An extension can receive Message Waiting notifications from multiple VPSs connected to PBXs in the network. When multiple notifications of the number of unheard messages in an extension user’s message box are sent from different VPSs, the most recent notification will be displayed.
•A flexible button cannot be customized as a Message Waiting button for another extension at a different PBX.
•Whether or not Enhanced QSIG information is transmitted can be set in the TIE table.
•When PBXs are connected by PRI23 cards, the card must be set to ISDN Standard mode. If set to T1 mode, the card must be removed and reinstalled to allow the mode to be changed. When the card is
•PBX Code Method
The number used in this method must be no more than 8 digits.
•When using a mailbox number containing more than 5 digits, the version of the
•Transfer to Mailbox
It is possible to transfer calls to a mailbox of a VPS at another PBX, by creating a flexible button containing the following:
[T] + extension number of VPS at other PBX + [P] + [#] + 6
Then, the extension user can transfer calls to a mailbox by pressing this key, entering the mailbox number, and going on hook.
•The VM Menu feature cannot be used in a Centralized Voice Mail network. When extensions belonging to a PBX that is not connected to the VPS have a mailbox in the VPS, the VM Menu feature should be disabled for the mailbox using the Class of Service (COS) setting of the VPS. Otherwise, there may be an answering delay of about 6 seconds.
PC Programming Manual References
3.35
11.1
11.2
→ Network MSW Data Transmission for Centralized VM
→ Network MSW Data Transmission for Centralized VM
13.1
→ Error Log for Centralized
→ Error Log for Centralized
Feature Manual References
19.1.4 Voice Mail DPT (Digital) Integration
Document Version | Feature Manual |
245