SIP mwi

Business SIP Providers
Provider Plan Details Monthly Rate *
Vonage Business SIP Trunking
  • One provider & nationwide coverage
  • Easily integrated into your existing infrastructure
  • More uptime, flexibility and disaster recovery options
$25.00
Details
GoTrunk Ultimate SIP Trunking Solution
  • Free trial
  • No contract
  • Quality control
$0.00
Details
Message Waiting notifications in SIP are done with the notify method.

This is supported by:

The mailbox directive in the sip.conf needs to be set and pointing to the correct context for this to work (example: "mailbox=1234@context").

The 480i, 9133i, 9112i, 480i CT Cordless phones need RFC3842 compliant From: headers in the NOTIFY for MWI to work. In some Asterisk setups, <sip:@192.168.0.101> is sent, and this causes the message to be discarded. One reason for this can be an empty callerid= line in sip.conf. In such cases, a workaround is to put fromuser=sipphone (or any string) in sip.conf for any user with a mailbox. Use Asterisk 1.0.4 or later to avoid MWI-issues.

See also

  • RFC 3842: A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
  • MWI
  • SIP
  • PBX features
  • RFC 3265: SIP-Specific Event Notification


Message Waiting notifications in SIP are done with the notify method.

This is supported by:

The mailbox directive in the sip.conf needs to be set and pointing to the correct context for this to work (example: "mailbox=1234@context").

The 480i, 9133i, 9112i, 480i CT Cordless phones need RFC3842 compliant From: headers in the NOTIFY for MWI to work. In some Asterisk setups, <sip:@192.168.0.101> is sent, and this causes the message to be discarded. One reason for this can be an empty callerid= line in sip.conf. In such cases, a workaround is to put fromuser=sipphone (or any string) in sip.conf for any user with a mailbox. Use Asterisk 1.0.4 or later to avoid MWI-issues.

See also

  • RFC 3842: A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
  • MWI
  • SIP
  • PBX features
  • RFC 3265: SIP-Specific Event Notification


Created by: oej, Last modification: Sat 15 of Jan, 2011 (10:52 UTC) by spamblock
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+