[cisco-voip] UCCX 2 second delay step

Wes Sisk wsisk at cisco.com
Tue Aug 10 17:26:44 EDT 2010


This is also related to behavior before
CSCeg56289    Need call recovery support for call state mismatch

was implemented. Without that any call state mismatch caused a dropped 
call.  In the call flow:
PSTN     CM
->setup
<-call proceeding (call routed to CTI Route point)
<-alerting with alerting party number (call routed to CTI Port)
<-connect (connected to CTI port)
-> status message complaining about "alerting party number" IE, call 
state = alerting
! state mismatch, drop call.
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.

/Wes



On Tuesday, August 10, 2010 5:05:25 PM, Ryan Ratliff 
<rratliff at cisco.com> wrote:
> 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.
>
> UC actually has the ability to slow down how fast it transfers calls, 
> which is another way to mitigate this issue.
>
> 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.
>
> -Ryan
>
> On Aug 10, 2010, at 4:03 PM, Kevin Damisch wrote:
>
> 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?
>
> ------------------------------------------------------------------------
>
> 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.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100810/2526e8c6/attachment.html>


More information about the cisco-voip mailing list