Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Authentication problem with XML push on CM 3.2(2.4)

Hi everyone;

We're having a problem performing an XML push to 7960 phones at a customer site. This customer is using CM 3.2(2.4) with a phone app load of P00303020204.

The specific problem is related to authentication by the phone against the AUTHENTICATE.ASP installed on CM.

Here's two scenarios:

1. We perform a push passing a user name and password that is not associated with the device in question. The response in this case is what we expect - <CiscoIPPhoneError Number="4"/>.

Response as follows:

HTTP/1.1 200 OK

Content-Type: text/xml

Date: Tue, 22 Oct 2002 13:17:20 GMT

Expires: Thu, 26 Oct 1995 00:00:00 GMT

Last-Modified: Tue, 22 Oct 2002 13:17:20 GMT

Pragma: no-cache

Server: Allegro-Software-RomPager/3.12

<CiscoIPPhoneError Number="4"/>

2. We do a push with a VALID user name and password associated with the device. The response in this case is HTML (not XML) indicating that the object on the ROM is protected!

Response as follows:

HTTP/1.1 401 Unauthorized

WWW-Authenticate: Basic realm="SEP0009B70A91F6"

Content-Type: text/html

Server: Allegro-Software-RomPager/3.12



<TITLE>Protected Object</TITLE>



<H1>Protected Object</H1>

This object on the RomPager server is protected.<P>

Return to <A HREF="">last page</A><P>



When trying the user name, password, and device name used in the second scenario directly against the AUTHENTICATE.ASP file, using the following URL "", we get "AUTHORIZED" as a response (which is what we expect).

However, it seems when this same information is passed to the phone which should relay it to the ASP file we get the HTTP 401 error.

Anyone know what the problem might be?



New Member

Re: Authentication problem with XML push on CM 3.2(2.4)

What are you using to push the message to the phone? Browser? If this is some custom application most make the mistake of not putting the authentication in the headers correctly. But it looks like you might be past that. If this is a custom app talking to the phone how are you doing it?

*** *** growing fast!!

New Member

Re: Authentication problem with XML push on CM 3.2(2.4)

The error happens when we post using a product of ours (Envoy) and a small diagnostic utility.

Both apps work fine on other 3.2 and 3.1 systems. It's just THIS specific CM system that we're having a problem with. Way strange !

I know there was a firmware load that had an issue where push was disabled but the customer has upgraded to the latest and greatest and therefore should be having any problems.

Could the problem be related to MLA? The customer doesn't believe they have MLA installed but I'm grasping at straws here !

(PS I like the look and feel of IPT Networkers - nice site)