I modified the authentication settings like this http://mywebserver/mypage.php. I see in my webserver's log that when I'm pushing something on the phone, the phone does a http GET with the username, pass and device.
What I don't understand is why the phone response is:
The data posted is XML= ... etc.
What am I missing ? Why is this error not documented?
This is an internal error. You should file a Defect with Cisco for this error. Be sure to include trace and log files. The most important of which would be a sniffer capture of the traffic between the phone and all other points.
No need to open a case.. I already did and here's what Cisco told me. Error 0:
The error 0 usually means that something failed in the authentication
process. When the phone tries to check credentials, it post them to the
authentication URL. If the URL is bad, unreachable, returns an error, or
even no response, the 0 seems to show itself.
The order in which the authentication occurs is as follows.
- Post XML to phone.
- Phone post credentials to the Authentication URL
- Authentication URL response with Clear Text Messages (Authorized,
- The phone then responds to the Post with a CiscoIPPhoneResponse or
CiscoIPPhoneError as appropriate.
If the phone doesn't make a request to the authentication URL, make sure
it has a URL. If it has a host name, check for DNS messaging in the
trace. Also power cycling the phone will clear any cached credentials or
DNS resolutions. The phone will cache credentials when they are valid
and only recheck on mismatch with a subsequent request or timeout of the
This occur when you have to push more than
once to get the event to take. It is typically because the socket on the
first attempt was being closed by the push agent before the phone
completely finished the push request. The phone bails out of the
processing logic and returns error 6.
The work around for this is
The phone has to be power-cycle to recover from this condition
I kept getting a 0 despite all that but never found time to set up a sniffing session (not so easy across vlans with the hardware I have) and I ended up upgrading the phones and right now things appear to be working so I'll await the next time something fails before setting up a sniffer session and reopening the case.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.