<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>OK. So I just tried creating a route filter bigger than 1024 characters on CUCM and this is what I get. Once I change the clause to be shorter, it works without a hitch.<br><br><div style="margin-left: 40px;"><hr style="width: 100%; height: 2px;"><title>Cisco Unified CM Console</title><script language="JavaScript" type="text/javascript">
if (self.parent != null)
{
if (self.parent.frames.length != 0)
{
self.parent.location=document.location;
}
}
</script><link media="screen" href="/ccmadmin/themes/VtgBlaf/console.css" type="text/css" rel="StyleSheet"><link title="JLF - Preferred" href="/ccmadmin/themes/VtgBlaf/vtgblaf_percent.css" type="text/css" rel="stylesheet"><div class="content">
<h2></h2>
<h2></h2>
<h2>Access to the requested resource has been denied.</h2>
<p>The attempted action was a violation of security protocols and will not be
allowed. Please try another action.</p></div><hr style="width: 100%; height: 2px;"></div><br>Matt, you said you were able to do this with v5? <br><br>I'm going to test a phone with a PSS of greater than 1024 characters next.<br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><br>----- Original Message -----<br>From: "Matt Slaga (US)" <Matt.Slaga@us.didata.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca>, "Robert Singleton" <rsingleton@novateck.com>, "Voip List" <cisco-voip@puck.nether.net><br>Sent: Tuesday, January 23, 2007 10:37:11 PM GMT -05:00 US/Canada Eastern<br>Subject: RE: [cisco-voip] 512+512 char limit for calling searchspace+ CallManager 5.x<br><br>
<style></style>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial">I asked this question specifically to the BU regarding
Route Filter 1024 limits. I was told that this was fixed in CallManager
5.0 and I have tested it to be accurate. This problem was directly related
to a SQL limitation.</font></span></div>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial">I have not tested the 1024 limit for CSS partition
members.</font></span></div>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial">The 1024 limit does not apply to phones because CallManager
makes the decisions on both Route Filters and CSS partition members, it does not
send the list to be parsed by the phone.</font></span></div>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span class="375093503-24012007"><font size="2" color="#0000ff" face="Arial"></font></span> </div><br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr>
<font size="2" face="Tahoma"><b>From:</b> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Lelio
Fulgenzi<br><b>Sent:</b> Tuesday, January 23, 2007 5:35 PM<br><b>To:</b> Robert
Singleton; Voip List<br><b>Subject:</b> Re: [cisco-voip] 512+512 char limit for
calling searchspace+ CallManager 5.x<br></font><br></div>
<div></div>
<div><font size="2">wow, i pretty much remember someone pointing out the SQL issue
myself. i'm not sure how a phone has anything to do with it's callingsearchspace
and why it would store it locally, all that processing is done on the
callmanager.</font></div>
<div><font size="2"></font> </div>
<div><font size="2">from what i gather, as someone also alluded to, the SQL table
supports 1024 characters. if you look at the database, the callingsearchspace
table has a clause column which is 1024 characters and is not concatenated in
any way.</font></div>
<div><font size="2"></font> </div>
<div><font size="2">i wonder if there is some sort of SQL operation going on in
realtime that then hits this 1024 character when it does concatenate
things.</font></div>
<div> </div>
<div><font size="2"></font> </div>
<div><font size="2"></font> </div>
<div>--------------------------------------------------------------------------------<br>Lelio
Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<br>I'm changing my name to iPhone. Who do I pay trademark rights to?<br></div>
<blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">----- Original Message ----- </div>
<div style="background: rgb(228, 228, 228) none repeat scroll 0% 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;"><b>From:</b>
<a title="rsingleton@novateck.com" href="mailto:rsingleton@novateck.com" target="_blank">Robert
Singleton</a> </div>
<div style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;"><b>To:</b> <a title="cisco-voip@puck.nether.net" href="mailto:cisco-voip@puck.nether.net" target="_blank">Voip List</a> </div>
<div style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;"><b>Sent:</b> Tuesday, January 23, 2007 5:14
PM</div>
<div style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;"><b>Subject:</b> Re: [cisco-voip] 512+512 char
limit for calling search space+ CallManager 5.x</div>
<div><br></div>On Tue, 2007-01-23 at 12:26 -0500, Lelio Fulgenzi
wrote:<br>> Does anyone know if the 512+512 character limit for a calling
search<br>> space was modified in CallManager 5.x? This was based on some
SQL<br>> issue I believe as it expanded the calling search space out to
the<br>> actual names of the partitions.<br><br>A TAC engineer once told me
that the base source of this limitation was<br>because RAM allocation
limitations in the telephones themselves was only<br>1024 bytes.<br><br>I must
admit that it seems a bit unlikely that every model of Cisco<br>telephone,
some of which were originally designed and manufactured by<br>different
companies, would suffer the exact same limitation. Maybe it's<br>a lowest
common denominator
thing...<br><br>Robert<br><br>_______________________________________________<br>cisco-voip
mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck..nether.net/mailman/listinfo/cisco-voip</a><br></blockquote><p></p><hr size="1"><p></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></div></body></html>