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...)
 
(gpa 24.10.2007 - link under DTMF Commands added)
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
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 message waiting object (MWI) is used to store message waiting status for other endpoints.
The MWI status can be interrogated by these endpoints and is also sent actively to the endpoint if the status changes.
For H.323 endpoints H.450-7 messages are used for this purpose.
The endpoint can use this information to turn a message waiting LED on/off.


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 MWI status can be set by two methods:
* Normal call to the MWI object with DTMF commands
* H.450-7 MWI-ACTIVATE/MWI-DEACTIVATE facilities


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:
== Configuration ==


201 - Sends the MWI message, MWI LED on
{|
|valign=top nowrap| '''Announcement URL'''
| The URL for an announcement to be played when the MWI object is called. This announcement can be used to give explanation what DTMF commands are available. If no Announcement is configured the builtin Music on Hold is played.
|-
|valign=top  nowrap| '''Extern Name/Number'''
| The announcement can also be retrieved from another endpoint. If a Name or Number is configured a call is sent to this Name/Number when the MWI object is called. The configured URL is sent as User User Information (UUI) with this call, so that it can be used by the called endpoint to retrieve the announcement.
|}


202 - Sends the MWI message, MWI LED off
== DTMF Commands ==


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 DTMF commands are available when the MWI object is called:


The following specifications are made in the MWI section:
{|
* '''Announcement URL:''' The path of the audio file to be played.
|valign=top nowrap| '''*1*<dest>'''
* '''External Name/No:''' After the audio file has played, the call can be forwarded to a different subscriber or call number.
| Set MWI for the endpoint <dest>
|-
|valign=top nowrap| '''*2*<dest>'''
| Clear MWI for the endpoint <dest>
|-
|valign=top nowrap| '''#'''
| Clear MWI for the calling endpoint.
|}
 
Alternatively (for endpoints not being able to send '*' or '#'):
 
{|
|valign=top nowrap| '''1<dest>'''
| Set MWI for the endpoint <dest>
|-
|valign=top nowrap| '''2<dest>'''
| Clear MWI for the endpoint <dest>
|-
|valign=top nowrap| '''3'''
| Clear MWI for the calling endpoint.
|}
 
The MWI state could also be cleared by Feature-Codes.
 
See further information under: [[Reference:Feature_Codes#Local_Clear_of_MWI]].
 
== Call Diversions ==
 
Call Diversions can be configured for the object, but are of no real use. CFB or CFNR are never executed. CFU is executed.

Latest revision as of 14:18, 24 October 2007

The message waiting object (MWI) is used to store message waiting status for other endpoints. The MWI status can be interrogated by these endpoints and is also sent actively to the endpoint if the status changes. For H.323 endpoints H.450-7 messages are used for this purpose. The endpoint can use this information to turn a message waiting LED on/off.

The MWI status can be set by two methods:

  • Normal call to the MWI object with DTMF commands
  • H.450-7 MWI-ACTIVATE/MWI-DEACTIVATE facilities

Configuration

Announcement URL The URL for an announcement to be played when the MWI object is called. This announcement can be used to give explanation what DTMF commands are available. If no Announcement is configured the builtin Music on Hold is played.
Extern Name/Number The announcement can also be retrieved from another endpoint. If a Name or Number is configured a call is sent to this Name/Number when the MWI object is called. The configured URL is sent as User User Information (UUI) with this call, so that it can be used by the called endpoint to retrieve the announcement.

DTMF Commands

The following DTMF commands are available when the MWI object is called:

*1*<dest> Set MWI for the endpoint <dest>
*2*<dest> Clear MWI for the endpoint <dest>
# Clear MWI for the calling endpoint.

Alternatively (for endpoints not being able to send '*' or '#'):

1<dest> Set MWI for the endpoint <dest>
2<dest> Clear MWI for the endpoint <dest>
3 Clear MWI for the calling endpoint.

The MWI state could also be cleared by Feature-Codes.

See further information under: Reference:Feature_Codes#Local_Clear_of_MWI.

Call Diversions

Call Diversions can be configured for the object, but are of no real use. CFB or CFNR are never executed. CFU is executed.

Retrieved from "https://wiki.innovaphone.com/index.php?title=Reference:Administration/PBX/Objects/Message_Waiting&oldid=6607"