Hi mate

May i ask you what is your logic to save it as .asp, soap, xml?
The sample code you provided which was a soap request which used to send a <getPhone> soap request to your CCM.
And i think you might need to send this request through your application.

You may have fallen for the same problem I had. In most of the examples in the XML developers guide, the same HTTPS header is used with the same content length (613). This content length actually depends on the size of the SOAP payload. The examples didn't reflect this. Here is what I used to generate the HTTPS header for a given soap payload string (note the GetLength() call):
/*****************************************************************************/
//
// METHOD:GenerateAndAttachHTTPSHeader()
//
// PURPOSE: This method creates an HTTP header based on the current
// m_ManagementAddress and m_ManagementIPPort values, and the size of the given
// SOAP_RequestEnvelope text string. This header is placed at the beginning
// of the given SOAP_RequestEnvelope text and the collective text is returned
// to the caller.
//
// Returns : CString
//
/*****************************************************************************/
CString SSL_ConnectionHandler::GenerateAndAttachHTTPSHeader(CString SOAP_RequestEnvelope)
{
CString strHTTPHeader;
CString hostLineDetails;
CString ContentLengthLineDetails;
hostLineDetails.Format("Host: %s:%d\n",(char*)(LPCSTR)m_ManagementAddress,m_ManagementIPPort);
ContentLengthLineDetails.Format("Content-length: %d\n",SOAP_RequestEnvelope.GetLength());
strHTTPHeader = "POST /axl/ HTTP/1.1\n";
strHTTPHeader += hostLineDetails;
strHTTPHeader += "Accept: text/*\n";
strHTTPHeader += "Authorization: Basic ";
strHTTPHeader += m_authorisationText.c_str(); // add authorisation text.
strHTTPHeader += "\nContent-type: text/xml\n";
strHTTPHeader += ContentLengthLineDetails; // add Content-Length test for current request
strHTTPHeader += "Connection: Keep-Alive";
strHTTPHeader += "\n\n";
// put the HTTP header and SOAP XML together
return strHTTPHeader + SOAP_RequestEnvelope;
}

Of course, you should also make sure that:
1) You have enabled the All important AXL Service in the CUCM. (Without this you get a HTTP 404 error if I remember right).
2) The authorisationText in the header matches a valid CUCM End User whose User Group has the appropriate "Roll" associated for AXL access.