Reference:Administration/PBX/Objects/Message Waiting: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
(New page: The Message Waiting PBX object was implemented to integrate external applications of other manufacturers (voicemail solutions) in the innovaphone PBX. Since some applications do not suppor...)
(No difference)

Revision as of 16:30, 29 March 2007

The Message Waiting PBX object was implemented to integrate external applications of other manufacturers (voicemail solutions) in the innovaphone PBX. Since some applications do not support the transmission of so-called MWI messages (LED on/off), the status regarding whether a message for a particular object exists is lost if say an MWI-enabled VoIP telephone is restarted.

The MWI object in the PBX is able to note the status for every object. For this, however, the external application (voicemail) must be prompted to send the current status for the individual user to the innovaphone PBX via H.450.7. The H.323 SETUP message must also be sent the call number of the relevant subscriber, or otherwise the PBX does not know which subscriber the MWI message should be sent to.

The status can also be sent using DTMF. Dazu muss einfach nur die Rufnummer des MWI-Objektes (z.B.: 20) gefolgt des entsprechenden DTMF-Code gewählt werden:

201 - Sends the MWI message, MWI LED on

202 - Sends the MWI message, MWI LED off

Furthermore, in the case of a call to this object, an audio file in the relevant coder format that is stored on a HTTP server can be played or even forwarded to a different subscriber.

The following specifications are made in the MWI section:

  • Announcement URL: The path of the audio file to be played.
  • External Name/No: After the audio file has played, the call can be forwarded to a different subscriber or call number.