CUCM 9.1 AXLAPIService.cs execution time http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=10928846 2013-06-19T06:17:43Z 2013-06-19T06:17:43Z Juerg Ott http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10974374 2013-01-22T08:43:43Z 2013-01-22T08:43:37Z

[quote=Robert Rittenhouse]Does it still take a long time after you compile your application for release? This could help as well: http://developer.cisco.com/web/axl/forums/-/message_boards/message/5356009?p_p_auth=7Z6zd4NL#_19_message_5837993  [/quote]  Hi Robert, without generate the serialization xml assembly it will take around 50 sec, with the serialization xml assembly it take 20-25 sec. that is still slow. do you not has this problem with your projects? Jürg  

Juerg Ott 2013-01-22T08:43:37Z Robert Rittenhouse http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10943855 2013-01-21T15:44:25Z 2013-01-21T15:44:25Z

Does it still take a long time after you compile your application for release? This could help as well: http://developer.cisco.com/web/axl/forums/-/message_boards/message/5356009?p_p_auth=7Z6zd4NL#_19_message_5837993  

Robert Rittenhouse 2013-01-21T15:44:25Z Juerg Ott http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10941270 2013-01-21T15:24:40Z 2013-01-21T15:24:40Z

Hi Michael, Hi Leandro, Thanks for your answers ... so I know it's not a mistake on my part, but only the large class that is autogenerated from the WSDL file;) As soon i know exactly know what functions i need, i will try to remove al the other code.. Jürg  

Juerg Ott 2013-01-21T15:24:40Z Michael Dunsdon http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10931552 2013-01-21T14:35:11Z 2013-01-21T14:35:11Z

Hi If you're using the autogenerated .net classes from the .wsdl file (all 250,000 lines of it) then you can also improve things considerebaly by removing any code you're not actually using. Can't really do that until the end though as you probably don't know yet what it is you want to use. Made a huge improvement to my code although in hindsight I probably should have stuck to native soap as the .net classes have their own set of issues.   Mike

Michael Dunsdon 2013-01-21T14:35:11Z Leandro Wajswajn http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10930840 2013-01-21T13:45:26Z 2013-01-21T13:45:26Z

Hi Juerg, That's normal, at least that was my case with 8.6 too. The work around I found was to do the native XML SOAP calls instead of wrapping up the Webservice through VB.NET. I'm just doing the based HTTPRequest calls and reading the XML; that way it really works fast! Pros: Performance Cons: You have to parse XML responses. I can share a code-snippet in case you want. Thanks, Leandro

Leandro Wajswajn 2013-01-21T13:45:26Z Juerg Ott http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10928845 2013-01-21T13:02:48Z 2013-01-21T13:02:09Z

Hello,  i am a new user with the AXL .  i connect to a Call Manager 9.1 and use Visual Studio 2012 C# with .NET Framework 4.0. I sucessfully create my AXLAPIService.cs and i am able to do some simple querys like listPhone.. My problem is that if i start the application and try to open the interface with AXLAPIService AXLService = new AXLAPIService(ccmIp, user, password);  it will take around 25 - 35 seconds before i get a result. Is this a normal? how can i speedup this? i was make already the serialization assembly but this will not solve the performance issue. thanks Jürg

Juerg Ott 2013-01-21T13:02:09Z