Don’t bother requesting. I’ll not upload any of my code as I only provide examples to get you on the right track so you don’t struggle like I have. My reasons why are numerous but the main ones are as follows:
1. I don’t need accusations that my files harmed someones production CUCM environment, their PC or their network. It’s not worth the trouble.
2. I’ve customized a majority of my wsdl generated files beyond the point of being useful to anyone but me. I’d be glad to offer pointers at generating your own and modifying them per the Cisco instructions but that is the only way I can help. I’m sorry if this is a disappointment to anyone.
3. It doesn’t teach you ANYTHING. Everyone wants answers but too many aren’t willing to work for them!
With that said, I should have some new content in the next couple of days. Stay tuned. I’ll be going over some useful items when dealing with LDAP integrated end users and even some tricks with remote destinations for mobility. If you aren’t already, get familiar with the data dictionary for your version of CUCM.
For those having trouble generating the AXLAPIService.cs….
Create a directory to keep all your wsdl related files in.
Find your wsdl.exe file and copy (not cut) it to the location you just created.
Copy the .wsdl file and any other files Cisco says you need into this folder.
Open a command prompt and navigate to the directory you created.
type wsdl.exe followed by the file names Cisco tells you to use.
This will most likely create your .cs file. If not, you have .net framework issues.