<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>Hi Jason, </div>
<div><br>
</div>
<div>It is on the roadmap, but the plan is to address it holistically by supporting +E.164 for both Agent DN, CTI Route Point/Port DN, External Phone Number Mask on UCCX devices etc. all at the same time instead of releasing support for individual components. </div>
<div><br>
</div>
<div>I believe this is on the roadmap for the 10.0 release, but it may be a stretch goal, but a lot of it depends on when Finesse will support +E.164 as we will not be building support for this into CAD. </div>
<div><br>
</div>
<div>
<div>Thank you, </div>
<div><br>
</div>
<div>Ryan LaFountain</div>
<div>Unified Contact Center</div>
<div>Cisco Services</div>
<div>Direct: +1 919 392 9898</div>
<div>Email: rlafount@cisco.com</div>
<div>Hours: M – F 9:00am – 5:00pm</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"Jason Aarons (AM)" <<a href="mailto:jason.aarons@dimensiondata.com">jason.aarons@dimensiondata.com</a>><br>
<span style="font-weight:bold">Date: </span>Monday, May 13, 2013 10:31 AM<br>
<span style="font-weight:bold">To: </span>"cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<span style="font-weight:bold">Subject: </span>[cisco-voip] Plans for UCCX Trigger to be e164 ? \+17043384588 ?<br>
</div>
<div><br>
</div>
<div 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">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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;
font-family:"Calibri","sans-serif";}
@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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">I can’t add a E164 trigger or CTI Route Point in appadmin? I can override it in ccmadmin, but first time a Appadmin Data Sync occurs they will break<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is there a roadmap to be able to put full E164 in Appadmin Triggers/CTI Ports?
<o:p></o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>