<div>In Unity, 71098 MWI on & 71099 MWI off.</div>
<div> </div>
<div>I need to clarify our setup. We have 2 CallManager clusters and an Avaya s8700. </div>
<div> </div>
<div>It goes Unity>CCM_51>Intercluster Trunk>CCM_41>QSIG>Avaya s8700. </div>
<div> </div>
<div>How does this configuration impact the CSS's? </div>
<div> </div>
<div>CCM_51 - Has MWI_CSS, with the CCM_51 device partitions and the
partition that the route patterns (using the intercluster trunk) are in.</div>
<div><br>CCM_41 - Has MWI_CSS, with the CCM_41 device partitions and
the partition that the route patterns (using the QSIG trunks) are in.</div>
<div> </div>
<div>Shouldn't we be able to dial the Avaya's MWI on code (*50)
followed by an Avaya phone to light MWI, all from a phone on the CCM_41
cluster? </div>
<div> </div>
Thanks.<br>Brian<br><br><div><span class="gmail_quote">On 8/23/07, <b class="gmail_sendername">Wes Sisk</b> <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
In unity what DN is configured for message waiting?<br>
<br>
QSIG MWI works like this with Unity/CM:<br>
<br>
Unity MWI port (high port usually) goes offhook and specifies calling
party number = the DN to light MWI for and called party = MWI on number
in CM.<br>
When the call reaches the MWI on number CM recognizes this as an MWI
request and converts the SCCP call to a QSIG call with necessary
APDUs. Effectively this alters the call so the calling device is the
MWI on number and the called party number is the DN to light MWI for.<br>
<br>
At this point the MWI CSS must contain a route pattern that points to a
QSIG enabled route list that points the gateway and trunk that provides
the QSIG link between CM and PBX.<br>
<br>
<br>
Net result - are your DN's, CSS, and route patterns correct?<br>
<br>
/Wes<br>
<br>
Brian wrote:
<blockquote type="cite"><div><span class="e" id="q_114931a7d2307400_1">We have an environment with CCM 5.1(2)b and an Avaya S8700
connected via QSIG PRI's. We would like to convert some of the Avaya
sets to a Unity voicemail box. I have successfully been able to leave
and retrieve voicemail's on the Avaya phones that have a Unity VM.
However, I am unable to get MWI to work. In the Avaya world, *50XXXX
turns on MWI and #50XXXX turns it off. I've created route patterns to
point to the Avaya, but can not get the MWI to light. <br>
<br>
Does anyone have a similar environment where this is working? <br>
<br>
Thanks,<br>
Brian<br>
<br>
<br>
</span></div><pre><hr size="4" width="90%">
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre>
</blockquote>
</div>
</blockquote></div><br>