Media5 Mediatrix 4104, Справочное руководство, Страница: 134 / 466

Chapter 5 - Web Interface – Telephony Miscellaneous
112 Mediatrix 4104
6. Define the duration, in seconds, of dynamic subscription to a messaging service in the MWI
Expiration Time field.
This parameter is set for all the lines of the Mediatrix 4104. You cannot have a different behaviour
for each line.
7. Enable the MWI by selecting Active in the MWI Activation field.
The MWI subscription refresh is not supported when the caller ID is DTMF-based.
8. Click Submit if you do not need to set other parameters.
MWI Method #2
This method does not require any special settings or configuration.
MWI Notify Service
The Mediatrix 4104 offers the possibility to extend some key features to remote extensions located in Branch
or Home Offices across the SCN.
This service is available only when using the IP Communication Server v3.1 product as a SIP Redirect server.
For instance, a designated analog voice mail system at a main site can provide voice mail for the home or
branch office. The home office user is notified of the message waiting via a message waiting LED on the
telephone or a special tone when picking up the telephone.
How does the Service Work?
The MWI Notify service is a proprietary feature. In this solution, the analog voice mail system is configured to
seize a designated outgoing line and dial a pre-defined string such as “*72xxx” to notify the server it must give
a message waiting indication to extension “xxx”. Once voice messages have been retrieved, the analog voice
mail system seizes the designated outgoing line and dials a pre-defined string such as “*73xxx” to notify the
server to turn off the message waiting indicator for extension “xxx”.
The service uses the Route Manager currently available in the IP Communication Server v3.1 to send a special
command to the Mediatrix unit.
The following is the basic sequence of operations for the MWI Notify service:
1. The analog voice mail system dials the following digits:
*72101
where *72 is a prefix and 101 the user extension.
2. The Mediatrix unit sends a standard INVITE to the IP Communication Server v3.1 containing the
complete dialed string (
*72101 ).
a. The IP Communication Server looks for the registered user “*72101” in the Registrar database.
b. The IP Communication Server cannot find the user, so it asks the Route Manager to process
the request.
c. Provided that the Route Manager is properly configured, it recognizes the “*72” prefix and
associates it to the proper route conditions.
3. The IP Communication Server answers the request with a “Moved Temporarily”. It contains
information about the target(s) in the
Contact header plus a proprietary p-MxBlindMWINotify=yes/
no field.
a. The Mediatrix unit retrieves the location from the IP Communication Server’s answer and the
p-MxBlindMWINotify field.
b. The Mediatrix unit parses the answer from the IP Communication Server and recognizes p-
MxBlindMWINotify as a special command.
4. The Mediatrix unit sends a NOTIFY to the location received from the IP Communication Server by
using the proper yes or no value (*72 = yes, *73 = no) specified by the route condition.
Standards Supported draft-mahy-sip-message-waiting-02.txt (expired) with proprietary
modifications