[cisco-voip] Single Unity Two CM Clusters MWI issue

[Andrew Dignan]

Thanks Wes,

My problem however is that it is "not" working as designed.  What I was
expecting was it to "flood" the MWI requests out all the MWI ports. 
However, it is only sending it out one MWI port at a time.  You can watch
it start at the highest numbered available port, timeout, and move down
the list.  Therefore, MWI on the second cluster takes about 2-3 minutes to
turn on because Unity is trying all the other MWI ports first.

I didn't install Unity at this site but I can't find any registry settings
that would disable Unity blasting MWI out all ports so not sure what
exactly is going on.  I have done many an install like this but haven't
had this problem before.

Regards,

Andy

> This is by design.  Unity does not store internally which switch a phone
> is on, so it floods MWI requests out to every switch.
>
> CM 4.1 finally supports MWI notification over ICT by implementing QSIG
> enhancments to the ICT protocol.  Thus CM can do it, but Unity has not
> changed gears to work like this yet.
>
> /Wes
>
> Andrew Dignan wrote:
>
>>Ok here is the topology (still having the problem).
>>
>>Two CallManager Clusters (No CME).  I have allocated the ports as
>> follows:
>>
>><b>Cluster 1:</b>
>>Ports 1-14 > Answer Calls
>>Ports 15-16 > Dialout MWI
>>
>><b>Cluster 2:</b>
>>Ports 17-30 > Answer Calls
>>Ports 31-32 > Dialout MWI
>>
>>- The Dialout MWI ports do not have a CSS that can access the phones on
>>the other cluster
>>- All VM Ports and MWI Numbers are the same on both clusters.
>>
>>Here is what happens now, when a message is left on a phone that is
>>registered to Cluster 2, you can fire up Port Status Monitor and you see
>>it pick a Dialout MWI port that is registered to Cluster 1.  As I stated
>>above the Dialout MWI port on Cluster 1 cannot dial phones on Cluster 2
>> so
>>the MWI fails.  It finally times out on those two ports and chooses a
>>Dialout MWI port registered to Cluster 2 which obviously lights the light
>>then.
>>
>>It was my understanding that for MWI it would blast it out all ports so
>> it
>>wouldn't matter that MWI ports couldn't dial phones on the other cluster.
>>These are two seperate companies using the same Unity server so I was
>> just
>>keep everything seperate.
>>_______________________________________________
>>cisco-voip mailing list
>>cisco-voip at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>