Message-Waiting Indication (MWI)

Message-Waiting Indication (MWI)
             2006-4-21
 
 
    MWI is a common feature of telephone networks and uses an audible indication (such as a special dial tone) that a message is waiting. The IETF draft A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP) draft-ietf-sipping-mwi-03.txt defines MWI as "a SIP event package carrying message waiting status and message summaries from a messaging system to an interested user agent."
In this feature, a UA (on behalf of the analog FXS phone) subscribes to a voice-mail server to request notification of mailbox status. When the mailbox status changes, the voice-mail server notifies the UA. The UA then indicates that there is a change in mailbox status by providing an MWI tone when the user takes the phone off-hook.
1、           SUBSCRIBE and NOTIFY
In SIP networks, the event notification mechanisms used to carry message waiting status are the SUBSCRIBE and NOTIFY methods. The SUBSCRIBE method requests notification of an event. The NOTIFY method provides notification that an event requested by an earlier SUBSCRIBE method has occurred.
2、           The basic MWI subscription and notification flow
1)        The user enables the MWI service for the FXS phone by configuring the voice gateway.
2)        The UA sends a subscription request to the server on the user's behalf.
3)        The voice-mail server notifies the UA when there is a change in voice-mail status.
4)        The UA notifies the phone user with an audible tone.
 
3、           Unsolicited MWI
In addition to the MWI status forwarded by using the SUBSCRIBE and NOTIFY methods, unsolicited MWI notify is also supported. With unsolicited MWI, MWI service is initially configured on the voice-mail server. The UA does not need to subscribe to the voice-mail server to receive MWI service. If configured for unsolicited MWI, the voice-mail server automatically sends a SIP notification message to the UA if the mailbox status changes.
4、           MWI tone
The frequency and cadence of the MWI tone may vary from country to country. For North America, it is defined in GR-506. After you configure the cp tone command under your voice port, Cisco IOS software chooses the correct MWI tone accordingly.
5、           Multiple FXS
Each voice port has its own subscription and notification process. If there are multiple dial peers associated with an FXS voice port, multiple subscriptions are sent to the voice-mail server. If the voice port does not have MWI enabled, the voice gateway returns a 481 Call Leg/Transaction Does Not Exist message to the voice-mail server.
6、           Sample Output for the debug ccsip messages Command
The following sample output is from the perspective of a SIP UA acting on the behalf of an analog FXS phone. The output shows that when the phone connected to the UA is called and the line is busy, the caller leaves a message. The UA, connected to the voice-mail server, receives notification and provides a tone to the user. The user listens to the message and deletes it.
Router# debug ccsip messages00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:INVITE sip:78002@csps-release.gb.com:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK24E9From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>Date: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Supported: 100rel,timerMin-SE: 1800Cisco-Guid: 3659524871-1844515286-2148452871-566800187User-Agent: Cisco-SIPGateway/IOS-12.xAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTERCSeq: 101 INVITEMax-Forwards: 70Remote-Party-ID: "SIPMWI-1" <sip:78001@192.168.1.174>;party=calling;screen=no;privacy=offTimestamp: 1022206059Contact: <sip:78001@192.168.1.174:5060>Expires: 180Allow-Events: telephone-eventContent-Type: application/sdpContent-Length: 234 v=0o=CiscoSystemsSIP-GW-UserAgent 5421 615 IN IP4 192.168.1.174s=SIP Callc=IN IP4 192.168.1.174t=0 0m=audio 16818 RTP/AVP 18 19c=IN IP4 192.168.1.174a=rtpmap:18 G729/8000a=fmtp:18 annexb=noa=rtpmap:19 CN/8000a=ptime:20 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK24E9Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>CSeq: 101 INVITEContent-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 407 Proxy Authentication RequiredVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK24E9Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=5ea400de-695763f1CSeq: 101 INVITEProxy-Authenticate: DIGEST realm="CISCO.com", nonce="40871b34", qop="auth", algorithm=MD5Content-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:ACK sip:78002@csps-release.gb.com:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK24E9From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=5ea400de-695763f1Date: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Max-Forwards: 70CSeq: 101 ACKContent-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:INVITE sip:78002@csps-release.gb.com:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK612From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>Date: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Supported: 100rel,timerMin-SE: 1800Cisco-Guid: 3659524871-1844515286-2148452871-566800187User-Agent: Cisco-SIPGateway/IOS-12.xAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTERCSeq: 102 INVITEMax-Forwards: 70Remote-Party-ID: "SIPMWI-1" <sip:78001@192.168.1.174>;party=calling;screen=no;privacy=offTimestamp: 1022206059Contact: <sip:78001@192.168.1.174:5060>Expires: 180Allow-Events: telephone-eventProxy-Authorization: Digest username="78001",realm="CISCO.com",uri="sip:192.168.1.37",response="df92654ce55d7346398013442919e7fc",nonce="40871b34",cnonce="2AEBD5CD",qop=auth,algorithm=MD5,nc=00000001Content-Type: application/sdpContent-Length: 234 v=0o=CiscoSystemsSIP-GW-UserAgent 5421 615 IN IP4 192.168.1.174s=SIP Callc=IN IP4 192.168.1.174t=0 0m=audio 16818 RTP/AVP 18 19c=IN IP4 192.168.1.174a=rtpmap:18 G729/8000a=fmtp:18 annexb=noa=rtpmap:19 CN/8000a=ptime:20 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>CSeq: 102 INVITEContent-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:INVITE sip:78002@192.168.1.174:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1Record-Route: <sip:78001.474b6083-19c218c7-16e9de49-93b83d71@192.168.1.174:5060;maddr=192.168.1.37>Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>Date: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Supported: 100rel,timerMin-SE: 1800Cisco-Guid: 3659524871-1844515286-2148452871-566800187User-Agent: Cisco-SIPGateway/IOS-12.xAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTERCSeq: 102 INVITEMax-Forwards: 69Remote-Party-ID: "SIPMWI-1" <sip:78001@192.168.1.174>;party=calling;screen=no;privacy=offTimestamp: 1022206059Contact: <sip:78001@192.168.1.174:5060>Expires: 180Allow-Events: telephone-eventContent-Type: application/sdpContent-Length: 234 v=0o=CiscoSystemsSIP-GW-UserAgent 5421 615 IN IP4 192.168.1.174s=SIP Callc=IN IP4 192.168.1.174t=0 0m=audio 16818 RTP/AVP 18 19c=IN IP4 192.168.1.174a=rtpmap:18 G729/8000a=fmtp:18 annexb=noa=rtpmap:19 CN/8000a=ptime:20 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1,SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A843C-187BDate: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Timestamp: 1022206059Server: Cisco-SIPGateway/IOS-12.xCSeq: 102 INVITEAllow-Events: telephone-eventContent-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:SIP/2.0 486 Busy hereVia: SIP/2.0/UDP 192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1,SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A843C-187BDate: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Timestamp: 1022206059Server: Cisco-SIPGateway/IOS-12.xCSeq: 102 INVITEAllow-Events: telephone-eventReason: Q.850;cause=17Content-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:ACK sip:78002@192.168.1.174:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A843C-187BCSeq: 102 ACKContent-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 180 RingingFrom: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A59035E8274E4600A8F3D15C3DAB9631Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174CSeq: 102 INVITEContent-Length: 0 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 200 OKFrom: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A59035E8274E4600A8F3D15C3DAB9631Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612Record-Route: <sip:7200@gb.com:5060;maddr=192.168.1.37>,<sip:78002@csps-release.gb.com:5060;maddr=192.168.1.37>Contact: sip:7200@192.168.1.30:5060Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174CSeq: 102 INVITEContent-Length: 166Content-Type: application/sdp v=0o=192.168.1.30 7542610 7542610 IN IP4 192.168.1.30s=No Subjectc=IN IP4 192.168.1.30t=0 0m=audio 22840 RTP/AVP 18a=rtpmap:18 G729/8000a=fmtp:18 annexb=no 00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:ACK sip:78002@csps-release.gb.com:5060;maddr=192.168.1.37 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK10EFFrom: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A59035E8274E4600A8F3D15C3DAB9631Date: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174Route: <sip:7200@gb.com:5060;maddr=192.168.1.37>,<sip:7200@192.168.1.30:5060>Max-Forwards: 70CSeq: 102 ACKProxy-Authorization: Digest username="78001",realm="CISCO.com",uri="sip:192.168.1.37",response="631ff1eec9e21b02fcbdbe932c9f7b5b",nonce="40871b34",cnonce="81C16CF6",qop=auth,algorithm=MD5,nc=00000002Content-Length: 0 00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:REGISTER sip:csps-release.gb.com:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK171FFrom: "78002" <sip:78002@192.168.1.174>;tag=AA7F4-1F83To: <sip:78002@csps-release.gb.com>Date: Fri, 24 May 2002 02:07:48 GMTCall-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3BUser-Agent: Cisco-SIPGateway/IOS-12.xMax-Forwards: 70Timestamp: 1022206068CSeq: 14 REGISTERContact: <sip:78002@192.168.1.174:5060>Expires: 60Content-Length: 0 00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK171FCall-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3BFrom: "78002" <sip:78002@192.168.1.174>;tag=AA7F4-1F83To: <sip:78002@csps-release.gb.com>CSeq: 14 REGISTERContent-Length: 0 00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 401 UnauthorizedVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK171FCall-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3BFrom: "78002" <sip:78002@192.168.1.174>;tag=AA7F4-1F83To: <sip:78002@csps-release.gb.com>CSeq: 14 REGISTERWWW-Authenticate: DIGEST realm="CISCO.com", nonce="40871b3d", qop="auth", algorithm=MD5Content-Length: 0 00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:REGISTER sip:csps-release.gb.com:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK21B5From: "78002" <sip:78002@192.168.1.174>;tag=AA7F4-1F83To: <sip:78002@csps-release.gb.com>Date: Fri, 24 May 2002 02:07:48 GMTCall-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3BUser-Agent: Cisco-SIPGateway/IOS-12.xMax-Forwards: 70Timestamp: 1022206068CSeq: 15 REGISTERContact: <sip:78002@192.168.1.174:5060>Expires: 60Authorization: Digest username="78002",realm="CISCO.com",uri="sip:192.168.1.37",response="134885a71dd9690370196089e445e955",nonce="40871b3d",cnonce="7446932B",qop=auth,algorithm=MD5,nc=00000001Content-Length: 0 00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK21B5Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3BFrom: "78002" <sip:78002@192.168.1.174>;tag=AA7F4-1F83To: <sip:78002@csps-release.gb.com>CSeq: 15 REGISTERContent-Length: 0 00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 200 OKVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK21B5Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3BFrom: "78002" <sip:78002@192.168.1.174>;tag=AA7F4-1F83To: <sip:78002@csps-release.gb.com>CSeq: 15 REGISTERContact: <sip:78002@192.168.1.174:5060>;expires=60Content-Length: 0 00:11:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Sent:BYE sip:78002@csps-release.gb.com:5060;maddr=192.168.1.37 SIP/2.0Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK79AFrom: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A59035E8274E4600A8F3D15C3DAB9631Date: Fri, 24 May 2002 02:07:39 GMTCall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174User-Agent: Cisco-SIPGateway/IOS-12.xMax-Forwards: 70Route: <sip:7200@gb.com:5060;maddr=192.168.1.37>,<sip:7200@192.168.1.30:5060>Timestamp: 1022206074CSeq: 103 BYEReason: Q.850;cause=16Proxy-Authorization: Digest username="78001",realm="CISCO.com",uri="sip:192.168.1.37",response="dffc15fe72d26b93d78162852ae1a341",nonce="40871b34",cnonce="AF9FD85E",qop=auth,algorithm=MD5,nc=00000003Content-Length: 0 00:11:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 100 TryingVia: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK79ACall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A59035E8274E4600A8F3D15C3DAB9631CSeq: 103 BYEContent-Length: 0 00:11:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:Received:SIP/2.0 200 OKFrom: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612To: <sip:78002@csps-release.gb.com>;tag=A59035E8274E4600A8F3D15C3DAB9631Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK79ACall-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174CSeq: 103 BYEContent-Length: 0 
 
 文来自CSDN博客，转载请标明出处：http://blog.csdn.net/lengxingfei/archive/2006/04/21/671452.aspx