cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2090
Views
45
Helpful
9
Replies

Unity Connection HA MWI Replication

e.parsonage
Level 1
Level 1

Hi All,

Has anyone had any problems with Unity Connection 8.5 HA MWI replication………..

MWI works fine if a message is received and listened on the same server be it the primary or failed over server, however if a message is received on a server and the system fails over before the message is dealt with, the MWI status isn’t carried across  when the server fails back or over ……………

Everything else works including single inbox so I don’t suspect DB problems, anyone else had this problem?

Hope that makes sense

1 Accepted Solution

Accepted Solutions

Rob Huffman
Hall of Fame
Hall of Fame

Hi there,

It sounds like it could be this bug;

CSCtn05523 - MWI/Notifications processing may stop after SBR

Description

Symptom:

No MWI or Notifications.

Conditions:

In a Cisco Unity Connection cluster where a node was unavailable for some amount of time while significant load was still on the system. After the network has recovered and Connection's Split-Brain Recovery (SBR) process has completed, at some point notifications fail.

Workaround:

Stop/start the Connection Notifier service in Cisco Unity Connection Serviceability.

Details

1st Found-in:                          (1)

8.5(1)

Status:

Fixed

Last Modified:

Oct 12,2011

Fixed-in:                          (22)

9.0(0.96000.1), 9.0(0.95070.39), 9.0(0.95070.38)

9.0(0.95010.1), 8.6(1.98000.43), 8.6(1.96000.16)

8.6(1.95050.1), 8.6(1.95020.80), 8.6(1.95020.1)

8.6(1.10001.1), 8.6(1.10000.43), 8.6(1.10000.1)

8.6(0.99981.2), 8.6(0.98000.9), 8.6(0.98000.29)

8.6(0.95180.9), 8.6(0.43), 8.5(1.12008.2), 8.5(1)ES20

8.0(3.22900.3), 8.0(3.22026.1), 8.0(3)ES21

Product:

Cisco Unity Connection

Platform:

Dependent

Severity:

3 - moderate

Customer Reported:                          (36)

Cheers!

Rob

View solution in original post

9 Replies 9

Rob Huffman
Hall of Fame
Hall of Fame

Hi there,

It sounds like it could be this bug;

CSCtn05523 - MWI/Notifications processing may stop after SBR

Description

Symptom:

No MWI or Notifications.

Conditions:

In a Cisco Unity Connection cluster where a node was unavailable for some amount of time while significant load was still on the system. After the network has recovered and Connection's Split-Brain Recovery (SBR) process has completed, at some point notifications fail.

Workaround:

Stop/start the Connection Notifier service in Cisco Unity Connection Serviceability.

Details

1st Found-in:                          (1)

8.5(1)

Status:

Fixed

Last Modified:

Oct 12,2011

Fixed-in:                          (22)

9.0(0.96000.1), 9.0(0.95070.39), 9.0(0.95070.38)

9.0(0.95010.1), 8.6(1.98000.43), 8.6(1.96000.16)

8.6(1.95050.1), 8.6(1.95020.80), 8.6(1.95020.1)

8.6(1.10001.1), 8.6(1.10000.43), 8.6(1.10000.1)

8.6(0.99981.2), 8.6(0.98000.9), 8.6(0.98000.29)

8.6(0.95180.9), 8.6(0.43), 8.5(1.12008.2), 8.5(1)ES20

8.0(3.22900.3), 8.0(3.22026.1), 8.0(3)ES21

Product:

Cisco Unity Connection

Platform:

Dependent

Severity:

3 - moderate

Customer Reported:                          (36)

Cheers!

Rob

I ran into that issue with 8.5(1) base during validation testing.  The bug that Rob provided above was determined to be the culprit.  +5 to Rob for being sharp with bug ID's and links as usual.

Hailey

Seriously. Rob is the man when it comes to whipping out those bug IDs. He must be using a different bug toolkit than I use. Good job Rob (+5).

-Bill

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Hi Rob,

Thanks for your reply, however based on this bug ID this should be fixed in the version I'm running.............

Cisco Unity Connection version: 8.5.1ES47.12900-47

I have now upgraded to the latest ES and works

Thanks for your suggestions Rob

Rob Huffman
Hall of Fame
Hall of Fame

Hi there,

I would open a TAC case to be sure that the fix was carried forward into

your ES. I've been bit more than once where we assumed a newer ES would have

the fix but in fact did not. TAC had to get a new fixed-in ES set up for special download.

Cheers!

Rob

PS: thanks Hailey!! It's always great to get a nod from you my friend

Hi Rob,

Thanks for your rapid reply again

I suppose the obvious thing to do is upgrade to 8.5 SU3 in that case................

I will see how it goes.................

Ellis

Ellis,

Just as a precaution, the latest images on cisco.com are not always the best to download as far as assuming they have the latest fixes.  Development writes a new ES almost every week, and these do not get posted.  I would recommend opening a TAC case to get the latest ES published to you like Rob suggested.

Thanks,

Brad

Rob Huffman
Hall of Fame
Hall of Fame

Hey Bill,

Nice to hear from you buddy! To get a high five from both you and Hailey here

today is SWEET!! Thanks so much

I am using the Beta Bug Search Tool - BST for most of my searches these days. The COTS

peeps from Cisco and COTS Advisory Board have been working hard to work out the kinks and

this v.2 is pretty good. It's much faster than BTK but needs some work on the navigation etc..

Just look in the Cisco Social Forum (Bug Toolkit) for the link and tour or at the top of the page on BTK itself.

Have a great weekend my friend! It's always nice to hear from you.

Cheers!

Huff

PS: I just noticed Brad's answer here as well. Hope all is well Mr. "B"!!  Between you, Bill

and Hailey we've got all the "high-priced" help on one thread

Eric....hope you get this worked out. Please let us know what your resolution turns out to be.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: