<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Jimmy,<br>
<br>
Yes, I have configured this and seen this work many times.<br>
<br>
With QSIG enabled the redirecting number is wrapped in a FacilityIE I
believe. Have you configured any custom routing rules in Unity? Are
you watching status monitor or similar to look for redirect reason, or
simply observing the mailbox greeting? A detailed CM trace from the
CM4.2(3) cluster will clearly show what is going on. (Trace = detailed
CM SDI and SDL,
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml">http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml</a>
) Set up for qsig on both sides, reset trunk on both sides, and send a
call over. Hopefully send the call to the same node where Unity is
registered. If you cannot discern the trace unicast it to me along
with:<br>
calling party number<br>
redirecting party number<br>
timestamp of call<br>
voicemail pilot number<br>
DN/devicename of the unity port that answered the call<br>
<br>
/Wes<br>
<br>
Jimmy Pale wrote:
<blockquote cite="mid:00e801c84292$b335e010$19a1a030$@com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Times-Roman;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal">Per the SRND for CallManager:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">In
addition to the option of adding multiple
clusters by adding additional integrations for each new<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">Unified
CM cluster in Cisco Unity, Unified
CM supports Annex M.1, Message Tunneling for QSIG,<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">which
gives administrators the ability to
enable QSIG on intercluster trunks (ICTs) between Unified CM<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">clusters.
When QSIG is enabled on ICTs,
Cisco Unity needs to integrate with only one Unified CM<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">cluster
and designate ports only in this one
cluster for turning MWIs on and off, even when supporting<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">multiple
clusters. The Annex M.1 feature in
Unified CM allows for propagation of the MWI requests<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">across
the ICTs to the proper Unified CM
cluster and phone within that cluster. All calls originating in<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">other
clusters can be forwarded to the Unity
server integrated to that one cluster. There is no need to<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 10pt; font-family: "Times-Roman","serif";">designate
MWI ports on the other clusters
when Annex M.1 is enabled on the ICT.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have setup the ICT with QSig on two
CallManager clusters. It
is Unity version 4.2(1). The cluster that has Unity directly connected
is version
4.2(3). The version on the other side of that QSig ICT is 6.0. I can
dial
numbers to and from either CallManager cluster without problem. I am
finding
that when calling a phone registered to the CallManager that is NOT
directly
connected to Unity that the redirecting number is not present and the
call goes
to the opening greeting via the CFB, CFNA, or CFA. Redirecting number
is NOT an
option when using QSig on the ICT. So how does this work? If I get rid
of the
QSig on the ICT and select the redirecting number it goes to the
appropriate VM
box everytime. Also, with the ICT using QSig MWI does not work when a
message
is left on a phone across the trunk. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Has anyone gotten this to work? Any tips would
be great!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre>
</blockquote>
</body>
</html>