So this is my second attempt at posting on how to set the username / password for the AXLPort object that AXIS generates from cisco's WSDL. Best forum software ever!
So if you're using the AXLAPIServiceLocator.getPort(url) function... (which I believe you should be using) then you'll notice this returns an AXLPort. If you look at the source you'll see that AXLPort is actually an AXLAPIBindingStub object. This object implements AXLPort (which is an interface) and extends Stub. All you have to do is cast the returned port to a Stub or AXLAPIBindingStub and then you can set the username and password.
I managed to solve this differently. Instead of specifying login and password in the constructor, I put them into the service URL (so http://login:pass@myccm/....), but I suppose in the end it's all the same.
I fully agree on the comment about the forum software. It's a disgrace. Not only is the board software very limited, the server also seems seriously underpowered.. I have some firsthand experience on how a board reacts when it cannot take the load.. it gets to a crawl, and this board constantly does that (besides not making what you want, posting nothing, double posting, losing attachments, etc).
A bit OT, but has either of you managed to get getPhone or getDeviceProfile working? All I get are invalid parameter exceptions for getPhone and invalid data from getDeviceProfile. Then I went to my old AXLconnector that sends plaintext XML, and it did work out just fine. So far I only have list operations working using the Axis generated classes from the WSDL.
I'm going to upload my newest axl.xsd and axlsoap.xsd these are finished for me until I find another error . The only problem is your CM may have data that my CM doesn't have so you may run into issues that I didn't run into.
BTW getPhone does work for me.
I would suggest using something like tcpmon to look at the messages as the go out over the wire... it's been very helpful in debugging the axl stubs.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...