<!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">
This is also related to behavior before<br>
CSCeg56289 Need call recovery support for call state mismatch <br>
<br>
was implemented. Without that any call state mismatch caused a dropped
call. In the call flow:<br>
PSTN CM<br>
->setup<br>
<-call proceeding (call routed to CTI Route point)<br>
<-alerting with alerting party number (call routed to CTI Port)<br>
<-connect (connected to CTI port)<br>
-> status message complaining about "alerting party number" IE, call
state = alerting<br>
! state mismatch, drop call.<br>
The status message appears for many reasons, some controllable, some
not. For 'best interoperability' wait 2 seconds before answering the
call. This allows the status message to pass while CO and CPE are in
the same call state. Once that is done answer the call and all is well.<br>
<br>
/Wes<br>
<br>
<br>
<br>
On Tuesday, August 10, 2010 5:05:25 PM, Ryan Ratliff
<a class="moz-txt-link-rfc2396E" href="mailto:rratliff@cisco.com"><rratliff@cisco.com></a> wrote:<br>
<blockquote cite="mid:AE144009-42D4-4313-9774-5F0210F3A9B2@cisco.com"
type="cite">Before the accept step is usually done to make CTI apps
play nice with Unity or other AA services that are transferring calls
into IPCC. Unity doing a release to switch (ie blind transfer) into
IPCC more often than not causes timing issues when IPCC tries to
redirect a call from a CTI RP to a CTI Port at the same time Unity is
completing the transfer.
<div><br>
</div>
<div>UC actually has the ability to slow down how fast it transfers
calls, which is another way to mitigate this issue.</div>
<div><br>
</div>
<div>I'm not sure what doing it after the Accept step would get you,
since I think (with UCCX) that the Accept step actually takes care of
redirecting the call to a media port. My IPCCX knowledge pretty much
stopped back in the CRS days so somebody else may want to correct me on
that part.<br>
<div><br>
</div>
<div>
<div><span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;">
<div>-Ryan</div>
</span></div>
<br>
<div>
<div>On Aug 10, 2010, at 4:03 PM, Kevin Damisch wrote:</div>
<br class="Apple-interchange-newline">
<span class="Apple-style-span"
style="border-collapse: separate; font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;">
<div link="blue" vlink="purple" lang="EN-US">
<div class="Section1" style="page: Section1;">
<div
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri,sans-serif;">As
a best practice, I have seen the 2 second delay step added before the
Accept step, and I have also seen it added after the Accept step
instead. Does it matter where it goes? And why?<o:p></o:p></div>
</div>
<br>
<hr><font color="Gray" face="Arial" size="1"><br>
This communication (including any attachments) is intended only for the
use of the individual or entity to which it is addressed, and may
contain information that is privileged, confidential and exempt from
disclosure under applicable law. If you are not the intended recipient,
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify Vital Support Systems at 515 334 5700 and delete or
destroy all copies and the original document.<br>
</font>_______________________________________________<br>
cisco-voip mailing list<br>
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net"
style="color: blue; text-decoration: underline;">cisco-voip@puck.nether.net</a><br>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
style="color: blue; text-decoration: underline;">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div>
</span></div>
<br>
</div>
</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>
<br>
</body>
</html>