[cisco-voip] 512+512 char limit for calling searchspace+ CallManager 5.x

[Lelio Fulgenzi]

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. 



Cisco Unified CM Console 


Access to the requested resource has been denied. 


The attempted action was a violation of security protocols and will not be allowed. Please try another action. 

Matt, you said you were able to do this with v5? 

I'm going to test a phone with a PSS of greater than 1024 characters next. 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message ----- 
From: "Matt Slaga (US)" <Matt.Slaga at us.didata.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "Robert Singleton" <rsingleton at novateck.com>, "Voip List" <cisco-voip at puck.nether.net> 
Sent: Tuesday, January 23, 2007 10:37:11 PM GMT -05:00 US/Canada Eastern 
Subject: RE: [cisco-voip] 512+512 char limit for calling searchspace+ CallManager 5.x 


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. 

I have not tested the 1024 limit for CSS partition members. 

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. 




From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi 
Sent: Tuesday, January 23, 2007 5:35 PM 
To: Robert Singleton; Voip List 
Subject: Re: [cisco-voip] 512+512 char limit for calling searchspace+ CallManager 5.x 



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. 

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. 

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. 



-------------------------------------------------------------------------------- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
I'm changing my name to iPhone. Who do I pay trademark rights to? 



----- Original Message ----- 
From: Robert Singleton 
To: Voip List 
Sent: Tuesday, January 23, 2007 5:14 PM 
Subject: Re: [cisco-voip] 512+512 char limit for calling search space+ CallManager 5.x 

On Tue, 2007-01-23 at 12:26 -0500, Lelio Fulgenzi wrote: 
> Does anyone know if the 512+512 character limit for a calling search 
> space was modified in CallManager 5.x? This was based on some SQL 
> issue I believe as it expanded the calling search space out to the 
> actual names of the partitions. 

A TAC engineer once told me that the base source of this limitation was 
because RAM allocation limitations in the telephones themselves was only 
1024 bytes. 

I must admit that it seems a bit unlikely that every model of Cisco 
telephone, some of which were originally designed and manufactured by 
different companies, would suffer the exact same limitation. Maybe it's 
a lowest common denominator thing... 

Robert 

_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck..nether.net/mailman/listinfo/cisco-voip 







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. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100208/431c6f77/attachment.html>