<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><title>Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX</title><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Which is why I recommend customers setting up Forward on Failure for CTI Ports, even if the UCCX BU doesn’t “support it”, I can’t tell you how many customers have been glad they set it up first outage.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Someone else mentioned they are going to field test it, but I got customers that have it setup and are happy with it. Rings a Ling Group when UCCX/UCCE fails and un-registers.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Chris Ward (chrward)<br><b>Sent:</b> Monday, July 26, 2010 4:10 PM<br><b>To:</b> Bennie Grant; Steve G; cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Reorder tone. Call drops if I recall.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>+Chris<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Bennie Grant<br><b>Sent:</b> Monday, July 26, 2010 4:07 PM<br><b>To:</b> Steve G; cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Pardon my ignorance here, but I have a related question. If a call is ON the CTI Port when the UCCX server drops (so the CTI Ports deregister) - what happens to those calls? Do they follow the CFUR, the “failure” forward, or do the calls simply drop?<br><br>Cheers<o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><hr size=3 width="95%" align=center></span></div><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From: </span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Steve G <<a href="smgustafson@gmail.com">smgustafson@gmail.com</a>><br><b>Date: </b>Mon, 26 Jul 2010 20:27:37 +0100<br><b>To: </b><<a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br><b>Subject: </b>Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX<br><br>Thanks all. I'm going to test in a lab and see what the behavior is. It is not an option in UCCX, so hopefully it would ignore it on a jtapi resync.<br><br>On Mon, Jul 26, 2010 at 11:43 AM, Ryan Ratliff <<a href="rratliff@cisco.com">rratliff@cisco.com</a>> wrote:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Agreed, depending on how the AXL stuff works it will either overwrite the setting OR ignore it completely. IMO if they don't let you set it via the UCCX admin then the AXL sync should ignore that setting. Either way I'd test it with a dummy RP before deploying live.<br><span style='color:#888888'><br>-Ryan<br></span><br>On Jul 26, 2010, at 1:32 PM, Tanner Ezell wrote:<br><br>Well, the whole idea is that the call hits CUCM, hits the CTI Route<br>Point which is owned by the JTAPI user and is controlled by UCCX (cti<br>route point rings uccx, uccx does call control, transfers call to cti<br>port, etc etc..).<br><br>In theory, if the device is unregistered, CFUR will hit and take<br>action but yes, I believe jtapi resync will overwrite those settings.<br><br>I'm not at a UCCX box at the moment but check under the Trigger<br>settings, if it was going to be there it would be near 'forward when<br>busy'<br><br>On Mon, Jul 26, 2010 at 12:37 PM, Fuermann, Jason <<a href="JBF005@shsu.edu">JBF005@shsu.edu</a>> wrote:<br>> I think the problem you’re going to run into is if you data resync in UCCX.<br>> It will overwrite the CFUR. As far as messing up UCCX, I’m not a developer<br>> on it, but I highly doubt it.<br>><br>><br>><br>> From: <a href="cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>> [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ryan Ratliff<br>> Sent: Monday, July 26, 2010 10:31 AM<br>> To: Steve G<br>> Cc: <a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX<br>><br>><br>><br>> If UCCX doesn't support setting the CFUR then I would like to think it would<br>> ignore the field entirely. You can sure as heck test it, and I'd also be<br>> asking your CSE what version of UCCX will support this field in CUCM and if<br>> there is a bug to track it.<br>><br>><br>><br>> -Ryan<br>><br>><br>><br>> On Jul 26, 2010, at 11:22 AM, Steve G wrote:<br>><br>> We are on CUCM 7.1.3 and it is supported in this version of CUCM. However,<br>> the TAC rep says it is not supported with UCCX and could cause Jtapi issues<br>> is you are not supposed to configure anything on the CTI RP in CUCM, but do<br>> it all on UCCX. Also, let's say we set the CTI RP to Forward Unregistered,<br>> and then updated Jtapi. Wouldn't that clear out the forward unregistered<br>> settings?<br>><br>> On Mon, Jul 26, 2010 at 8:12 AM, Tanner Ezell <<a href="tanner.ezell@gmail.com">tanner.ezell@gmail.com</a>><br>> wrote:<br>><br>> It's not really a UCCX thing. What version of UCM? If you're version<br>> supports forward on unregistered then that's all you can do..<br>><br>> On Mon, Jul 26, 2010 at 11:07 AM, Steve G <<a href="smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br>>> Anyone??? going once, going twice...<br>>><br>>> On Fri, Jul 23, 2010 at 11:08 AM, Steve G <<a href="smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br>>>><br>>>> I meant CTI Route Points...not CTI Ports.<br>>>><br>>>> On Fri, Jul 23, 2010 at 11:05 AM, Steve G <<a href="smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br>>>>><br>>>>> In UCCX is there a way to configure a CTI Port to forward Unregistered<br>>>>> to<br>>>>> anther number...ie Hunt Pilot? We are running into an issue where CTI<br>>>>> ports<br>>>>> become unregistered and don't recover without manual intervention of<br>>>>> updating the jtapi triggers in UCCX. We have a TAC rep saying that we<br>>>>> can<br>>>>> not modify the CTI ports in CUCM as that is not supported. So if UCCX<br>>>>> has a<br>>>>> jtapi problem we are dead in the water until we can login and<br>>>>> update/resync<br>>>>> the jtapi triggers.<br>>>>> I am extremely new to UCCX so please forgive me if my terminology is<br>>>>> wacky.<br>>>>> Thanks,<br>>>>> Steve<br>>><br>>><br>><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> <a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>><br>>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>><br>><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><pre>*************************************************************************<o:p></o:p></pre><pre>Please consider the environment before printing this e-mail<o:p></o:p></pre><pre>*************************************************************************<o:p></o:p></pre><pre>This email and any files transmitted with it are confidential and<o:p></o:p></pre><pre>intended solely for the use of the individual or entity to whom they<o:p></o:p></pre><pre>are addressed. If you have received this email in error please notify<o:p></o:p></pre><pre>the system manager. <a href="http://www.mettoni.com">http://www.mettoni.com</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Mettoni Ltd<o:p></o:p></pre><pre>Registered in England and Wales: 4485956<o:p></o:p></pre><pre>9400 Garsington Road, Oxford Business Park, Oxford, OX4 2HN<o:p></o:p></pre><pre>*************************************************************************<o:p></o:p></pre></div></body></html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>