Bitswap

Archive for the ‘B 11.00 Implement and Troubleshoot Messaging’ Category

CallManager & UnityExpress integration

Posted by Andy on August 13, 2009

CallManager & UnityExpress integration

Advertisements

Posted in 11.02 Cisco Unity Express, B 11.00 Implement and Troubleshoot Messaging | Leave a Comment »

Cisco Unity Express users import

Posted by Andy on April 9, 2009

Cisco Unity Express 7.x does not import SIP users (configured under voice register pool) from CME. Looks like they need to be created manually.

Posted in 11.02 Cisco Unity Express | Leave a Comment »

Nice and simple way to upgrade CUE to 7.0.2

Posted by Andy on April 8, 2009

software install clean url ftp://172.16.1.250/cue-vm-k9.nm-aim.7.0.2.pkg
, sure , you need to download and unpack software first.

Read the rest of this entry »

Posted in 11.02 Cisco Unity Express | Leave a Comment »

Why I cant ping CallManager from Unity Conection when adding VM Ports ?

Posted by Andy on April 8, 2009

It seems to be bug.  I did some debug on cuc and it definily send some packets out 

screenshot-4_8_2009-12_40_41-am

However even without successfull ping to CM ports registered pretty normal . Pay attention , on PREFIX , it needs to be exactly as in CM without “-X”

screenshot-4_8_2009-12_41_35-am

Posted in 11.01 Cisco Unity Connection | Leave a Comment »

Partitions and CSS for UnityConnection access

Posted by Andy on April 7, 2009

 

Partitions and CSS for UnityConnection

Partitions and CSS for UnityConnection

Based on http://cisco.com/en/US/docs/voice_ip_comm/connection/7x/integration/cucm_sccp/guide/cucintcucmskinny050.html

 

Partition / css from CUCM point of view:

Posted in 11.01 Cisco Unity Connection | 1 Comment »

Cisco Unity Connection documentation roadmap

Posted by Andy on April 2, 2009

Posted in 11.01 Cisco Unity Connection | Tagged: | Leave a Comment »

CUE Unsupported Deployments

Posted by Andy on April 1, 2009

Unsupported Deployments

The following deployment scenarios are not supported (up to Cisco CME 3.2 and Cisco Unity Express 2.1):

•Sites networked with SIP as the VoIP protocol. While Cisco CME by itself supports SIP trunking, these deployments are not yet supported if Cisco Unity Express is used in conjunction with Cisco CME. Only H.323 VoIP trunking is supported.

•Multiple Cisco Unity Express systems in the same router chassis.

•A “centralized” Cisco Unity Express model where a single Cisco Unity Express system provides voice mail to IP phones at more than one Cisco CME or Cisco SRST site.

•SIP phones as Cisco Unity Express voice mail subscribers-only SCCP IP phones are supported.

•Analog phones as Cisco Unity Express voice mail subscribers. Analog phones (FXS ports) can connect to Cisco Unity Express as “outside” callers into the AA and voice-mail systems, but cannot receive subscriber features such as call-forward busy (CFB), call-forward no answer (CFNA), or message waiting indicator (MWI.)

Posted in 11.02 Cisco Unity Express | 2 Comments »

Lab #2

Posted by Andy on March 31, 2009

Continue from Lab#1 , sites interconnected via ipipgateway, ( more here )

1. Connect CM phones to Unity Connection
2. Connect CM1 phones to Unity Express
3. Connect CM2 phones to Unity Connection
4. Connect CM2 phones to Unity Express on CM1
———————————————-
5. Connect CM1&CM2 phones to Unity Connection(MWI Relay , SIP)
6. Connect CM1&CM2 phones to Unity Express
7. Connect CM2&CM phones to Unity Connection

test according to 

http://cisco.com/en/US/docs/voice_ip_comm/connection/7x/integration/cucm_sccp/guide/cucintcucmskinny210.html

Posted in 11.01 Cisco Unity Connection, 11.02 Cisco Unity Express | Tagged: | 3 Comments »