Configuring SIP MWI Features
First Published: May 27, 2004
Last Updated: June 22, 2010
This module describes message-waiting indication (MWI) in a SIP-enabled network.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for SIP MWI" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Prerequisites for SIP MWI
•Restrictions for SIP MWI
•Information About SIP MWI
•How to Configure SIP MWI
•Configuration Examples for SIP MWI
•Configuration Example for SIP MWI NOTIFY - QSIG MWI Translation
•Configuration Example for SIP VMWI
•Additional References
Prerequisites for SIP MWI
SIP MWI NOTIFY - QSIG MWI Translation Feature
•Ensure that you have a working SIP network with the following:
–A voice-messaging system that provides a SIP MWI Notify message to the phone—including Cisco Unified Communications Manager (formerly known as Cisco CallManager), Release 5.0 or later or Cisco Unified Communications Manager Express (Cisco Unified CME, formerly known as Cisco CallManager Express) Release 4.0 or later.
–Voice messaging on Cisco Unity 4.0.1 or later releases (colocated or integrated with the Cisco Unified Communications Manager) or an ISDN Q-signaling (QSIG) PBX.
•Connect gateway and Cisco routers directly to a PBX.
•Ensure that phones connected to PBXs support MWI notification.
SIP Audible Message-Waiting Indicator for FXS Phones Feature
•The MWI tone is generated by the voice-mail server. Be sure that you understand how to configure MWI service on a voice-mail server (such as Cisco Unity).
Restrictions for SIP MWI
SIP MWI NOTIFY - QSIG MWI Translation Feature
•Visual MWI for phones is a functionality of the phone itself and is not addressed in this document.
•The feature supports only SIP unsolicited notify and does not support SIP subscribe notify.
•This feature is not supported in trunk groups in ISDN circuits. In this scenario, trunk groups disable the SIP MWI feature.
SIP Audible Message-Waiting Indicator for FXS Phones Feature
•The SIP Audible Message-Waiting Indicator for FXS Phones feature does not provide the following functionality:
–Security or authentication services
–Call redirection to the voice-mail server when the line is busy or there is no answer
–Instructions on accessing the voice-mail server or retrieving voice messages
Information About SIP MWI
The SIP Audible Message-Waiting Indicator for FXS Phones feature enables an FXS port on a voice gateway to receive audible MWI in a SIP-enabled network. The FXS port on a voice gateway is an RJ-11 connector that allows connections to basic telephone service equipment.
This feature provides the following benefits:
•Message waiting is now indicated to FXS phone users through an audible tone, replicating the functionality users have with traditional telephone systems.
•By means of the Cisco IOS command-line interface, you can enable or disable MWI under the voice port and configure one voice-mail server per user agent (UA) or voice gateway.
To configure SIP MWI support, you should understand the following concepts:
•SUBSCRIBE/NOTIFY MWI
•Unsolicited MWI
SUBSCRIBE/NOTIFY MWI
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 Cisco 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.
Note For information on the SUBSCRIBE and NOTIFY methods, see the "Configuring Additional SIP Application Support" chapter of the Cisco IOS SIP Configuration Guide.
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.
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.
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.
Figure 95 shows the basic MWI subscription and notification flow.
Figure 95 MWI 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.
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.
SIP MWI NOTIFY - QSIG MWI Translation
In Cisco IOS Release 12.4(11)T, the SIP MWI NOTIFY - QSIG Translation feature enhances MWI functionality to include SIP-MWI-NOTIFY-to-QSIG-MWI translation between Cisco gateways or routers over a LAN or WAN and extends message waiting indicator (MWI) functionality for SIP MWI and QSIG MWI interoperation to enable sending MWI over QSIG from a Cisco IOS SIP gateway to a PBX.
When the SIP Unsolicited NOTIFY is received from voice mail, the Cisco router translates this event to activate QSIG MWI to the PBX via PSTN. The PBX will switch the MWI lamp either on or off on the corresponding IP phone as appropriate.
This feature supports only Unsolicited NOTIFY. Subscribe NOTIFY is not supported by this feature.
In Figure 96, the Cisco router receives the SIP Unsolicited NOTIFY, performs the protocol translation, and initiates the QSIG MWI call to the PBX, where it is routed to the appropriate phone.
Figure 96 SIP MWI to ISDN QSIG When Voice Mail and Cisco Router are On the Same LAN
Whether the SIP Unsolicited NOTIFY is received via LAN or WAN does not matter as long as the PBX is connected to the gateway or Cisco router, and not to the remote voice mail server.
In Figure 97, a voice mail system, such as Cisco Unity, and Unified CME are connected to the same LAN and a remote Unified CME is connected across the WAN. In this scenario, the protocol translation is performed at the remote Unified CME router and the QSIG MWI message is sent to the PBX.
Figure 97 SIP MWI to ISDN QSIG When PBX is Connected to a Remote Cisco Router
How to Configure SIP MWI
This section contains the following procedures for configuring the SIP Audible MWI for FXS Phones feature:
•Configuring SIP MWI NOTIFY - QSIG MWI Translation
•Configuring Voice-Mail Server Settings on the UA
•Configuring the Voice-Mail Server for Unsolicited
•Enabling MWI Under an FXS Voice Port
•Verifying MWI Settings
•Configuring VMWI on analog phones connected to FXS
•Troubleshooting Tips
Note•Before you perform a procedure, familiarize yourself with the following information:
–"Prerequisites for SIP MWI" section
–"Restrictions for SIP MWI" section
•For help with a procedure, see the verification and troubleshooting sections listed above.
Configuring SIP MWI NOTIFY - QSIG MWI Translation
This section contains information for configuring SIP MWI NOTIFY - QSIG MWI Translation on a gateway.
Note All configuration for this feature is done on the gateway or Cisco router.
Configuring the Gateway
To configure SIP MWI NOTIFY - QSIG MWI Translation on a gateway, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice-port slot/port
4. mwi
5. exit
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
voice-port slot/port
Router(config)# voice-port 2/2 |
Enters voice-port configuration mode for the specified PRI or BRI voice port. |
Step 4 |
mwi
Router (config-voiceport)# mwi |
Enables MWI on this voice port. Note If the voice port is not configured for MWI, the gateway returns a 481 Call Leg/Transaction Does Not Exist message to the voice-mail server. If multiple dial peers are associated with the same voice port, multiple subscriptions are sent to the voice-mail server. |
Step 5 |
exit
Router(config-dial-peer-voice)# exit |
Exits the current configuration mode. |
Configuring Voice-Mail Server Settings on the UA
To configure voice-mail server settings on the UA, perform the following steps.
Note This configuration initiates the capability of a UA or voice gateway to indicate voice-mail status changes. One voice-mail server is configured per voice gateway.
SUMMARY STEPS
1. enable
2. configure terminal
3. sip-ua
4. mwi-server {ipv4:destination-address | dns:host-name} [expires seconds] [port port] [transport {tcp | udp}] [unsolicited]
5. exit
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enters privileged EXEC mode. Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
sip-ua
Router(config)# sip-ua |
Enters SIP user-agent configuration mode. |
Step 4 |
mwi-server {ipv4:destination-address | dns:host-name} [expires seconds] [port port] [transport {tcp | udp}] [unsolicited]
Router(config-sip-ua)# mwi-server dns:test.example.com expires 86000 port 5060 transport udp unsolicited |
Configures voice-mail server settings on a voice gateway or UA. Keywords and arguments are as follows: •ipv4:destination-address—IP address of the voice-mail server. •dns:host-name—Host device housing the domain name server that resolves the name of the voice-mail server. The argument should contain the complete hostname to be associated with the target address; for example, dns:test.example.com. •expires seconds—Subscription expiration time, in seconds. Range is from 1 to 999999. Default is 3600. •port port—Port number on the voice-mail server. Default is 5060. •transport—Transport protocol to the voice-mail server. Valid values are tcp and udp. Default is UDP. •unsolicited—Requires the voice-mail server to send a SIP notification message to the voice gateway or UA if the mailbox status changes. Removes the requirement that the voice gateway subscribe for MWI service. |
Step 5 |
exit
Router(config-sip-ua)# exit |
Exits the current mode. |
Configuring the Voice-Mail Server for Unsolicited
To configure the Cisco Unity voice-mail server to be unsolicited, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. sip-ua
4. mwi-server ipv4:x.x.x.x unsolicited
5. exit
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
sip-ua
Router(config)# sip-ua |
Enters SIP-user-agent configuration mode. |
Step 4 |
mwi-server ipv4:x.x.x.x unsolicited
Router (config-sip-ua)# mwi-server ipv4:192.0.10.150 unsolicited |
Configures the specified voice-mail (MWI) server to be unsolicited. (That is, requires the server to send a SIP notification message to the voice gateway or user agent if the mailbox status changes. Removes the requirement that the voice gateway subscribe for MWI service.) |
Step 5 |
exit
Router(config-sip-ua)# exit |
Exits the current configuration mode. |
Enabling MWI Under an FXS Voice Port
To enable MWI under the specified FXS voice port, perform the following steps.
Note 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.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice-port port
4. cptone locale
5. mwi
6. exit
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enters privileged EXEC mode. Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
voice-port port
Router(config)# voice-port 2/2 |
Enters voice-port configuration mode. To find the port argument for your router, see the Cisco IOS Voice Command Reference, Release 12.3T. |
Step 4 |
cptone locale
Router(config-voiceport)# cptone us |
Specifies a regional analog voice-interface-related tone, ring, and cadence setting for a specified FXS voice port. |
Step 5 |
mwi
Router(config-voiceport)# mwi |
Enables MWI for a specified FXS voice port. |
Step 6 |
exit
Router(config-voiceport)# exit |
Exits the current mode. |
Verifying MWI Settings
To verify MWI settings, perform the following step.
SUMMARY STEPS
1. show sip-ua mwi
DETAILED STEPS
Step 1 show sip-ua mwi
Use this command to display SIP MWI settings from the voice-mail server. The command displays endpoint status as OFF if a message is deleted or if no message is waiting. The endpoint status changes to ON when a message is waiting.
The following sample output shows endpoint status as OFF if a message is deleted or if no message is waiting. The endpoint status changes to ON when a message is waiting.
MWI server: dns:unity-vm.example1.com
MWI server: 192.168.1.30, port 5060, transport 1
MWI server dns lookup retry cnt: 0
endpoint 8000 mwi status ON
endpoint 8000 mwi status ON
endpoint 8001 mwi status OFF
Configuring VMWI on analog phones connected to FXS
There are two types of visual message waiting indicator (VMWI) features: Frequency-shift Keying (FSK) and DC voltage. The message-waiting lamp can be enabled to flash on an analog phone that requires an FSK message to activate a visual indicator. The DC Voltage VMWI feature is used to flash the message-waiting lamp on an analog phone which requires DC voltage instead of an FSK message. For all other applications, such as MGCP, FSK VMWI is used even if the voice gateway is configured for DC voltage VMWI. The configuration for DC voltage VMWI is supported only for Foreign Exchange Station (FXS) ports on the Cisco VG224 analog voice gateway with analog device version V1.3 and V2.1.
The Cisco VG224 can only support 12 Ringer Equivalency Number (REN) for ringing 24 onboard analog FXS voice ports. To support ringing and DC Voltage VMWI for 24 analog voice ports, stagger-ringing logic is used to maximize the limited REN resource. When a system runs out of REN because too many voice ports are being rung, the MWI lamp temporarily turns off to free up REN to ring the voice ports.
To enable MWI under the specified FXS voice port, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice-port port
4. mwi
5. vmwi dc-voltage
or
vmwi fsk
6. exit
7. sip-ua
8. mwi-server {ipv4:destination-address | dns:host-name} [unsolicited]
9. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
voice-port port
Router(config)# voice-port 2/0 |
Enters voice-port configuration mode. •port—Syntax is platform-dependent. Type ? to determine. |
Step 4 |
mwi
Router(config-voiceport)# mwi |
Enables MWI for a specified voice port. |
Step 5 |
vmwi dc-voltage
or vmwi fsk
Router(config-voiceport)# vmwi dc-voltage |
(Optional) Enables DC voltage or FSK VMWI on a Cisco VG224 onboard analog FXS voice port. You do not need to perform this step for the Cisco VG202 and Cisco VG204. They support FSK only. VMWI is configured automatically when MWI is configured on the voice port. This step is required for the VG224. If an FSK phone is connected to the voice port, use the fsk keyword. If a DC voltage phone is connected to the voice port, use the dc-voltage keyword. |
Step 6 |
exit
Router(config-sip-ua)# exit |
Exits to the next highest mode in the configuration mode hierarchy. |
Step 7 |
sip-ua
Router(config)# sip-ua |
Enters Session Initiation Protocol user agent configuration mode for configuring the user agent. |
Step 8 |
mwi-server {ipv4:destination-address | dns:host-name} [unsolicited]
Router(config-sip-ua)# mwi-server ipv4:1.5.49.200 or Router(config-sip-ua)# mwi-server dns:server.yourcompany.com unsolicited |
Specifies voice-mail server settings on a voice gateway or user agent (ua). Note The sip-server and mwi expires commands under the telephony-service configuration mode have been migrated to mwi-server to support DNS format of the Session Initiation Protocol (SIP) server. |
Step 9 |
end
Router(config-voiceport)# end |
Exits voice-port configuration mode and returns to privileged EXEC mode. |
Troubleshooting Tips
Note For general troubleshooting tips and a list of important debug commands, see the Verifying and Troubleshooting SIP Features chapter in the Cisco IOS SIP Configuration Guide.
•Use the debug ccsip messages command for debugging purposes.
•Use the debug vpm all command for showing the VMWI state of a voice-port
Following is sample output for this command:
•Sample Output for the debug ccsip messages Command
•Sample relevant output for the debug vpm all command
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 messages
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
INVITE sip:78002@csps-release.example1.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK24E9
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Cisco-Guid: 3659524871-1844515286-2148452871-566800187
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO,
UPDATE, REGISTER
Remote-Party-ID: "SIPMWI-1" <sip:78001@192.168.1.174>;party=calling;screen=no;privacy=off
Contact: <sip:78001@192.168.1.174:5060>
Allow-Events: telephone-event
Content-Type: application/sdp
o=CiscoSystemsSIP-GW-UserAgent 5421 615 IN IP4 192.168.1.174
m=audio 16818 RTP/AVP 18 19
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK24E9
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK24E9
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=5ea400de-695763f1
Proxy-Authenticate: DIGEST realm="example.com", nonce="40871b34", qop="auth",
algorithm=MD5
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
ACK sip:78002@csps-release.example1.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK24E9
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=5ea400de-695763f1
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
INVITE sip:78002@csps-release.example1.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK612
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Cisco-Guid: 3659524871-1844515286-2148452871-566800187
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO,
UPDATE, REGISTER
Remote-Party-ID: "SIPMWI-1" <sip:78001@192.168.1.174>;party=calling;screen=no;privacy=off
Contact: <sip:78001@192.168.1.174:5060>
Allow-Events: telephone-event
Proxy-Authorization: Digest
username="user1",realm="example.com",uri="sip:192.168.1.37",response="df92654ce55d734
6398013442919e7fc",nonce="40871b34",cnonce="2AEBD5CD",qop=auth,algorithm=MD5,nc=00000001
Content-Type: application/sdp
o=CiscoSystemsSIP-GW-UserAgent 5421 615 IN IP4 192.168.1.174
m=audio 16818 RTP/AVP 18 19
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
INVITE sip:78002@192.168.1.174:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1
Record-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=z9hG4bK612
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Cisco-Guid: 3659524871-1844515286-2148452871-566800187
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO,
UPDATE, REGISTER
Remote-Party-ID: "SIPMWI-1" <sip:78001@192.168.1.174>;party=calling;screen=no;privacy=off
Contact: <sip:78001@192.168.1.174:5060>
Allow-Events: telephone-event
Content-Type: application/sdp
o=CiscoSystemsSIP-GW-UserAgent 5421 615 IN IP4 192.168.1.174
m=audio 16818 RTP/AVP 18 19
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP
192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1,SIP/2.0/UDP
192.168.1.174:5060;re
ceived=192.168.1.174;branch=z9hG4bK612
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A843C-187B
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Server: Cisco-SIPGateway/IOS-12.x
Allow-Events: telephone-event
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP
192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1,SIP/2.0/UDP
192.168.1.174:5060;re
ceived=192.168.1.174;branch=z9hG4bK612
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A843C-187B
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Server: Cisco-SIPGateway/IOS-12.x
Allow-Events: telephone-event
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
ACK sip:78002@192.168.1.174:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.37:5060;branch=474b6083-19c218c7-16e9de49-93b83d71-1
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A843C-187B
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A59035E8274E4600A8F3D15C3DAB9631
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A59035E8274E4600A8F3D15C3DAB9631
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK612
Record-Route:
<sip:7200@example1.com:5060;maddr=192.168.1.37>,<sip:78002@csps-release.example1.com:5060;
maddr=192.168.1.37>
Contact: sip:7200@192.168.1.30:5060
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Content-Type: application/sdp
o=192.168.1.30 7542610 7542610 IN IP4 192.168.1.30
00:11:29: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
ACK sip:78002@csps-release.example1.com:5060;maddr=192.168.1.37 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK10EF
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A59035E8274E4600A8F3D15C3DAB9631
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Route: <sip:7200@example1.com:5060;maddr=192.168.1.37>,<sip:7200@192.168.1.30:5060>
Proxy-Authorization: Digest
username="user1",realm="example.com",uri="sip:192.168.1.37",response="631ff1eec9e21b0
2fcbdbe932c9f7b5b",nonce="40871b34",cnonce="81C16CF6",qop=auth,algorithm=MD5,nc=00000002
00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
REGISTER sip:csps-release.example1.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK171F
From: "user2" <sip:78002@192.168.1.174>;tag=AA7F4-1F83
To: <sip:78002@csps-release.example1.com>
Date: Fri, 24 May 2002 02:07:48 GMT
Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3B
User-Agent: Cisco-SIPGateway/IOS-12.x
Contact: <sip:78002@192.168.1.174:5060>
00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK171F
Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3B
From: "user2" <sip:78002@192.168.1.174>;tag=AA7F4-1F83
To: <sip:78002@csps-release.example1.com>
00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK171F
Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3B
From: "user2" <sip:78002@192.168.1.174>;tag=AA7F4-1F83
To: <sip:78002@csps-release.example1.com>
WWW-Authenticate: DIGEST realm="example.com", nonce="40871b3d", qop="auth", algorithm=MD5
00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
REGISTER sip:csps-release.example1.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK21B5
From: "user2" <sip:78002@192.168.1.174>;tag=AA7F4-1F83
To: <sip:78002@csps-release.example1.com>
Date: Fri, 24 May 2002 02:07:48 GMT
Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3B
User-Agent: Cisco-SIPGateway/IOS-12.x
Contact: <sip:78002@192.168.1.174:5060>
Authorization: Digest
username="user2",realm="example.com",uri="sip:192.168.1.37",response="134885a71dd969037019
6
089e445e955",nonce="40871b3d",cnonce="7446932B",qop=auth,algorithm=MD5,nc=00000001
00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK21B5
Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3B
From: "user2" <sip:78002@192.168.1.174>;tag=AA7F4-1F83
To: <sip:78002@csps-release.example1.com>
00:11:38: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK21B5
Call-ID: 6CD62112-6DF011D6-8006CA07-21C8AF3B
From: "user2" <sip:78002@192.168.1.174>;tag=AA7F4-1F83
To: <sip:78002@csps-release.example1.com>
Contact: <sip:78002@192.168.1.174:5060>;expires=60
00:11:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
BYE sip:78002@csps-release.example1.com:5060;maddr=192.168.1.37 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.174:5060;branch=z9hG4bK79A
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A59035E8274E4600A8F3D15C3DAB9631
Date: Fri, 24 May 2002 02:07:39 GMT
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
User-Agent: Cisco-SIPGateway/IOS-12.x
Route: <sip:7200@example1.com:5060;maddr=192.168.1.37>,<sip:7200@192.168.1.30:5060>
Proxy-Authorization: Digest
username="user1",realm="example.com",uri="sip:192.168.1.37",response="dffc15fe72d26b9
3d78162852ae1a341",nonce="40871b34",cnonce="AF9FD85E",qop=auth,algorithm=MD5,nc=00000003
00:11:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK79A
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A59035E8274E4600A8F3D15C3DAB9631
00:11:44: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
From: "SIPMWI-1" <sip:78001@192.168.1.174>;tag=A842C-2612
To: <sip:78002@csps-release.example1.com>;tag=A59035E8274E4600A8F3D15C3DAB9631
Via: SIP/2.0/UDP 192.168.1.174:5060;received=192.168.1.174;branch=z9hG4bK79A
Call-ID: DBAC09D2-6DF111D6-8011CA07-21C8AF3B@192.168.1.174
Sample relevant output for the debug vpm all command
Process vmwi. vmwi state: OFF
The phone is not onhook (1). Delay the vmwi processing.
Process dc-voltage vmwi. State: OFF
*Mar 2 02:33:34.841: [2/0] c2400_dc_volt_mwi: on=0
The phone is not onhook (1). Delay the vmwi processing.
Process vmwi. vmwi state: ON
Configuration Examples for SIP MWI
The following example shows that SIP MWI is configured on the gateway.
Router# show running-config
Building configuration...
Current configuration : 14146 bytes
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
boot system flash:c2430-is-mz.mwi_dns
logging buffered 9000000 debugging
network-clock-participate E1 1/0
network-clock-participate E1 1/1
ip domain name example1.com
ip name-server 192.168.1.1
ip dhcp excluded-address 172.16.224.97
isdn switch-type primary-qsig
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none
codec preference 1 g711ulaw
codec preference 2 g729r8
codec preference 3 g726r32
voice hpi capture buffer 100000
voice hpi capture destination flash:t1.dat
voice translation-profile Out
pri-group timeslots 1-10,16
interface FastEthernet0/0
ip address 192.168.1.172 255.255.255.0
interface FastEthernet0/1
ip address 10.2.141.19 255.255.0.0
ip route 0.0.0.0 0.0.0.0 192.168.1.2
ip rtcp report interval 30000
! Enable MWI on voice ports 2/0 and 2/1.
session target sip-server
destination-pattern 789...
destination-pattern 789...
session target sip-server
! Configure the voice-mail server settings on the gateway with the mwi-server command.
authentication username user1 password password1 realm example.com
mwi-server dns:test.example.com expires 60 port 5060 transport udp unsolicited
registrar dns:csps-release.test.example.com expires 3600
sip-server dns:csps-release.test.example.com
Configuration Example for SIP MWI NOTIFY - QSIG MWI Translation
The following example shows a sample configuration of the SIP MWI NOTIFY - QSIG MWI Translation feature on a SIP gateway.
dial-peer voice 1000 voip
session target ipv4:10.120.70.10
incoming called-number .T
Configuration Example for SIP VMWI
Router# show running-config
Building configuration...
mwi-server ipv4:9.13.40.83 expires 3600 port 7012 transport udp unsolicited
Additional References
General SIP References
•"SIP Features Roadmap" chapter—Describes how to access Cisco Feature Navigator; also lists and describes, by Cisco IOS release, SIP features for that release.
•"Basic SIP Configuration" chapter—Describes underlying SIP technology; also lists related documents, standards, MIBs, RFCs, and how to obtain technical assistance.
References Mentioned in This Chapter (listed alphabetically)
•RFC 3842, "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)" at http://www.ietf.org/rfc/rfc3842.txt
•Cisco IOS Voice Command Reference at http://www.cisco.com/en/US/docs/ios/voice/command/reference/vr_book.html
•Cisco IOS Voice Configuration Library at http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/
cisco_ios_voice_configuration_library_glossary/vcl.htm
Feature Information for SIP MWI
Table 62 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(1) or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 62 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Table 62 Feature Information for Configuring SIP MWI Features
|
|
|
SIP Audible Message-Waiting Indicator for FXS Phones |
12.3(8)T |
This feature enables an FXS port on a voice gateway to receive audible MWI in a SIP-enabled network. The following section provides information about this feature: •Enabling MWI Under an FXS Voice Port |
SIP MWI NOTIFY - QSIG MWI Translation |
12.4(11)T |
This feature was introduced. This feature is used to configure SIP MWI NOTIFY - QSIG MWI Translation on a gateway. The following section provides information about this feature: •SIP MWI NOTIFY - QSIG MWI Translation |
VMWI on analog phones connected to FXS |
15.1(2)T |
This feature introduces support fpor VMWI on analog phones connected to FXS. The following section provides information about this feature: •Configuring VMWI on analog phones connected to FXS |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2006-2010 Cisco Systems, Inc. All rights reserved.