<!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 Derick,<br>
<br>
We recently worked a very similar case in TAC, 607585317. Is this the
same integration? Cisco account team are still engaged with that
customer and trying to get an answer out of Avaya.<br>
<br>
Net result was that CM sends the appropriate Q.SIG ctComplete APDUs to
Avaya. At least the APDU are correct per the specs we have. However,
the Avaya8700 fails to parse the ctComplete messages and therefore does
not perform the path replacement. <br>
<br>
Thus far CM integration with Avaya 8700 using Q.SIG is certified but
path replacement is not certified. Translation - some pretty dedicated
guys packed away in a lab with 8700 and CM could get basic call
functionality to work, but they could not get path replacement to work.<br>
<br>
You can see CM sending ctComplete in the CCM/SDI traces by the
following messages:<br>
01/03/2008 13:11:06.671 CCM|TRANSFQSIGASN - StructuredInput:value
CTCompleteRose ::= invoke :<br>
01/03/2008 13:11:06.671 CCM|TRANSFQSIGASN - StructuredInput:value
CTCompleteRose ::= invoke :<br>
<br>
If this is not the same installation then need to the ground work first
and confirm you're up to the same point. If you are at the same point
then we need some Avaya input.<br>
<br>
/Wes<br>
<br>
Derick Winkworth wrote:
<blockquote cite="mid:206514.46871.qm@web57202.mail.re3.yahoo.com"
type="cite">
<div>All:</div>
<div> </div>
<div>I am having a Path Replacement issue with an Avaya PBX.</div>
<div> </div>
<div>So, essentially, what we have is this:</div>
<div> </div>
<div>Avaya</div>
<div>|</div>
<div>| <- PRI/QSIG</div>
<div>|</div>
<div>GW1 <---- IOS Gateway (3845 12.4(11)T1)</div>
<div>|\</div>
<div>| \<br>
| \</div>
<div>| \</div>
<div>| CM <--- 4.2(3)</div>
<div>| /</div>
<div>| /</div>
<div>| /</div>
<div>|/</div>
<div>GW2</div>
<div>|</div>
<div>| <--- E&M</div>
<div>|</div>
<div>Edify</div>
<div> </div>
<div> </div>
<div> </div>
<div>I hope that comes out OK in your display, if not, it should come
out OK if you copy/paste to Notepad (fixed width font).</div>
<div> </div>
<div>So what is happening is this. A call is coming into the Avaya,
and that call is automatically forwarded out the QSIG trunk to an
extension for the Edify. This works. The edify answers and the
customer is getting "Level 1" support through the IVR. But then they
need to talk to an agent. ("Level 2").</div>
<div> </div>
<div>So what happens at that point is, they select that through the
menu, and the Edify does a hookflash-transfer back to an extension
which is hanging off of the Avaya PBX. The Callmanager will collapse
the call down all the way back to GW1, but then the call hairpins their
back to the Avaya PBX. So at this point, the call is coming into the
Avaya from the PSTN, over the PRI/QSIG trunk into GW1, and then
hairpinned rightback to the Avaya to the agent.</div>
<div> </div>
<div>We can't figure out why this is happening. Clearly the
Callmanager knows the two legs are belong to the same call, because the
channels on the Edify are released and the call is collapsed back down
to GW1. So why doesn't CallManager do a proper transfer-by-join so the
Avaya can just locally switch the PSTN leg directly to the Agent?</div>
<div> </div>
<div>So we did a test. We had the Avaya forward calls directly to an
IP phone registered to the Callmanager. We then did a call transfer
from the IP phone to the agent, and low-and-behold... it worked! </div>
<div> </div>
<div>But it doesn't work from the Edify.</div>
<div> </div>
<div>Anyone have any thoughts on this? </div>
<div> </div>
<div> </div>
<p> </p>
<hr size="1">Looking for last minute shopping deals? <a
moz-do-not-send="true"
href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping">
Find them fast with Yahoo! Search.</a>
<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>