Ok, I'm trying to confirm that this is a bug. I run for example a getMGCP AXL command against CM 6. The command works, I can view the trace log on the CM 6 server and the request is recieved and processed. The response is then generated on the server however it is killed and a 401 unauthorized error (random) is returned after the point it is processed on the server and before it gets back to me.
Now normally I'd think this is me, but this ONLY happens in cases (like getMGCP) where the response contains illegal characters (@, /, etc.) (such as in the domain name - e.g.([email protected]). I can replicate this with other calls e.g. executesqlquery (where I can get the mgcp gateways because it doesnt create the domainnames with @, but it dies when I include the units or subunits (that have @ or / in the unit or subunit name).
The rest of my calls in the same sequence using the same credentials work (I'm getting partitions, CSS, Route Lists, Route Groups, etc.) So I know its not a true 401. I also know it is working as I can see the response packet on the server (via the trace log) and it has all of the data (in the getmgcp call and executesqlquery call instances).
The same application works against 4 with all calls.
DOES AXL 6 NOT PROPERLY ENCODE ITS RESPONSES CAUSING THE SOAP MESSAGE TO BE DESTROYED WHEN ILLEGAL CHARACTERS ARE PRESENT?
This seems to be the case... and there is nothing I can do. This will happen with the following: MGCP, Route Patterns, Trans Patterns, etc. Anything that has special characters in its generated response soap message.