Cisco CME can integrate with various non-Cisco voice mail systems using H.323. One of the H.323 voice systems supported by Cisco CME is the Stonevoice Switch Answering Machine (SSAM), a unified messaging system designed to provide access to and control over software-based voice mail services.
SSAM is a Windows 2000-based application that runs on an external PC. All traffic between Cisco CME and SSAM uses H.323. Figure 11-4 shows how the Stonevoice SSAM application integrates with Cisco CME.
Figure 11-4. Cisco CME with Stonevoice SSAM Voice Mail
When integrated with CME, SSAM supports the following:
For more information on the SSAM system, go to http://www.stonevoice.com/.
The following sections provide more details on integrating a Stonevoice system with Cisco CME, including
Configuring Cisco CME for Stonevoice
Communication between Cisco CME and SSAM is via H.323, so you have to configure an H.323 dial peer to direct calls into the SSAM system. You must configure a voice mail pilot number (for example, 9999) on SSAM for message retrieval and an individual voice mail number for each extension (ephone-dn). Because the original called number (the IP phone extension) is not preserved when the call is forwarded to SSAM via H.323, you must embed this information in the called number (the call forward number) delivered to SSAM.
Example 11-6 shows a sample Cisco CME configuration defining a voice mail pilot number of 9999 (used when you press the messages button on your IP phone), voice mail number 9001 for extension 1001, and 9002 for extension 1002.
Example 11-6. Configuring Cisco CME for SSAM
router#show running-config dial-peer voice 100 voip destination-pattern 9... session target ipv4:172.19.153.120 dtmf-relay h245-alphanumeric codec g711ulaw no vad ! telephony-service voicemail 9999 ! ephone-dn 1 number 1001 call-forward busy 9001 call-forward noan 9001 timeout 10 ! ephone-dn 2 number 1002 call-forward busy 9002 call-forward noan 9002 timeout 10
The voice dial peer command destination-pattern 9... ensures that all calls to 9999, 9001, and 9002 are directed to SSAM via H.323. The IP address 172.19.153.120 in this example belongs to the SSAM system.
The voicemail 9999 command under telephony service is the voice mail pilot number used when you press the messages button on your IP phone. This number must match the "Voicemail number" parameter on the SSAM Modify IP Telephony System page.
Individual voice mail forwarding numbers are defined for each extension. These are used in the call-forward busy and call-forward noan fields of the ephone-dn Cisco CME configuration. These numbers must be configured on the SSAM system for each individual user. For example, for the person on ephone-dn 1, you configure his or her extension (1001) in the "First extension number" field, and configure 9001 in the "Voicemail number" field of the SSAM Account Management page for this user.
MWI
MWI is controlled by the SSAM system outdialing with H.323 to a Cisco CME MWI DN. The extension for which the MWI must be turned on or off is embedded in the dialed number. The Cisco CME configuration for this is shown in Example 11-7.
Example 11-7. Configuring MWI for SSAM
router#show running-config ephone-dn 11 number 8000*....*1 secondary 8000*....*2 mwi on-off no huntstop ! ephone-dn 12 number 8000*....*1 secondary 8000*....*2 mwi on-off preference 1
You should configure as many of these MWI ephone-dns as you have "ports" on the SSAM system so that the maximum number of simultaneous calls can be handled correctly. Use the Cisco CME preference and no huntstop command designations to make sure the Cisco CME system hunts across any available MWI ephone-dns.
When the SSAM system makes an outgoing call to Cisco CME, the MWI information is embedded in the called party's telephone numberfor example, 8000*1001*1 or 8000*1001*2. The 8000 is the MWI DN's number, and the asterisks are used as delimiters. The extension for which MWI should be turned on or off is contained between the asterisks, and the final digit in the string specifies whether MWI is on (1) or off (2).
The notation 8000*....*1 in the ephone-dn definition accepts any extension number and represents the extension digits that Cisco CME extracts to determine for which IP phone to turn MWI on or off. The MWI on (ending in digit 1) and MWI off (ending in digit 2) strings are given on the same ephone-dn as the primary and secondary extensions on that ephone-dn, as shown in Example 11-7.
Analog Voice Mail |
Part I: Cisco IP Communications Express Overview
Introducing Cisco IPC Express
Building a Cisco IPC Express Network
Cisco IPC Express Architecture Overview
Part II: Feature Operation and Applications
Cisco IP Phone Options
Cisco CME Call Processing Features
Cisco CME PSTN Connectivity Options
Connecting Multiple Cisco CMEs with VoIP
Integrating Cisco CME with Cisco CallManager
Cisco IPC Express Automated Attendant Options
Cisco IPC Express Integrated Voice Mail
Cisco CME External Voice Mail Options
Additional External Applications with Cisco CME
Part III: Administration and Management
Cisco IPC Express General Administration and Initial System Setup
Configuring and Managing Cisco IPC Express Systems
Cisco IPC Express System Configuration Example
Part IV: Maintenance and Troubleshooting
Troubleshooting Basic Cisco IPC Express Features
Troubleshooting Advanced Cisco CME Features
Troubleshooting Cisco CME Network Integration
Troubleshooting Cisco UE System Features
Troubleshooting Cisco UE Automated Attendant
Troubleshooting Cisco UE Integrated Voice Mail Features
Part V: Appendixes
Appendix A. Cisco IPC Express Features, Releases, and Ordering Information
Appendix B. Sample Cisco UE AA Scripts
Appendix C. Cisco Unity Express Database Schema
Index