CiscoIPPhoneError Number 6

[raymond009]

Hi,

I have got this error when post an XML execute to an ip phone. Seems quite many of people here also get this problem, anyone know the reason?

I am using IPC + CM Sim.

The script is from the SDK.

[aaronw.ca]

Error 6 is an older error that shouldn't show up that often, though the CM Sim may still report it.

This page provides general information on troubleshooting XML for the IP Phones:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_troubleshooting_guide_chapter09186a00801f018f.html

At the end of the above page the expected error and status codes are listed.

I would suggest that you try a simple XML service to ensure that the basics are working, and then try more complicated services.

Also, sometimes the samples in the SDK require modification to make them work: make sure you examine the asp pages (there is usually a comment section near the top of the asp page describing any required user modifications) and any readme files that came with the sample.

[grahamhanson]

Hi,

I'm afraid that you comment that Error 6 is an "older error that shouldn't show up that often" is not very helpful. Especially as the reference given only refers to errors 1, 2, 3 and 4!

I am pushing the following request-

http://10.150.17.133/phone/page1.xml"/>

The play works ok but the URL doesn't.

The first time I send the request to a phone (7940) there is a long delay before the response -

If I send the request again I get -

http://10.150.17.133/phone/page1.xml"/>

This is repeated until I reset the phone.

The webserver (Tomcat on my PC) serves the page Ok to a browser. The Tomcat logs do NOT show any attempt by the phone to retrieve the page.

Graham

[aaronw.ca]

I've seen the "Request Busy" before (as have others), and I would suggest it's a bug, though I haven't seen it noted in any bug notices to date.

One thing to check is whether that phone is configured with an idle url, as removing the idle url on a phone returning the "Request Busy" message has fixed it in the past, though so has resetting the phone. I would suggest first removing the idle url if any, and try again.

It seems to be phone-related, as pushing the same service to a different phone worked, while that particular phone continued reporting a "Request Busy" return status.

It may be related to a particular phone firmware, and upgrading the firmware may resolve it as well. I have found it difficult to reproduce, and annoying when it does occur.

[phooey]

Hi all,

One reason I got this message was because my web app didn’t always reply to the phones GET request in response to a pushed url, the phones seem quite sensitive to being ignored.

All my phones are monitored via tapi, when an event occurs (pickup/connect etc) they are pushed an ExecuteItem containing an url with the event as a parameter. Some of these events didn’t need a screen pop so I was just dropping the TCP connection, this was causing subsequent pushed urls to return “Request Busy”. Changing the no reply to an empty object fixed this problem.

However I still occasionally get the busy response, seemingly tied to the frequency of pushes. Try and send more than 5-7 urls in ten seconds (making a new tcp connection each time) and the phones will respond with busy. Looks like some kind of flood protection mechanism?

Regards,

Phooey.