<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>RE: Phone service - HTTP Connection failed error on 8941 phones</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=" />
  <subtitle>RE: Phone service - HTTP Connection failed error on 8941 phones</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=</id>
  <updated>2013-05-26T03:37:59Z</updated>
  <dc:date>2013-05-26T03:37:59Z</dc:date>
  <entry>
    <title>RE: IP Phone SDK7.1.2 - Push2Phone HTTP 404 error</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=15110099" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=15110099</id>
    <updated>2013-05-09T17:59:51Z</updated>
    <published>2013-05-09T17:59:51Z</published>
    <summary type="html">Re-attached to the wiki, should be working now...hope it helps!</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-05-09T17:59:51Z</dc:date>
  </entry>
  <entry>
    <title>RE: Does Cisco DX650 support XML Objects?</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=14566192" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=14566192</id>
    <updated>2013-04-23T15:33:53Z</updated>
    <published>2013-04-23T15:33:53Z</published>
    <summary type="html">The DX650 does not support any IP Phone Services XML APIs - applications can use the general design patterns (and far greater functionality) provided by Android itself to deliver custom services on the device.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-04-23T15:33:53Z</dc:date>
  </entry>
  <entry>
    <title>RE: #DEVICENAME# not working on 7940/7960</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=14012953" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=14012953</id>
    <updated>2013-04-08T21:01:16Z</updated>
    <published>2013-04-08T21:01:16Z</published>
    <summary type="html">I believe this is a limitation of the 7940/60 devices.  As these devices have long since been End of Life'ed, you will need to explore workarounds, e.g. adding a service URL parameter to specify the device name, and populating it per device.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-04-08T21:01:16Z</dc:date>
  </entry>
  <entry>
    <title>RE: IP Phone service not working on 9971</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12953407" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12953407</id>
    <updated>2013-03-13T05:54:44Z</updated>
    <published>2013-03-13T05:54:44Z</published>
    <summary type="html">Yep, so your script will need to handle this possibility, i.e. parameter being missing results in the same script action as if parameter is missing but null/empty</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-03-13T05:54:44Z</dc:date>
  </entry>
  <entry>
    <title>RE: Image not refreshing</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12751689" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12751689</id>
    <updated>2013-03-07T15:43:21Z</updated>
    <published>2013-03-07T15:43:21Z</published>
    <summary type="html">Can you grab a network packet capture (e.g. via Wireshark) of the traffic and inspect the actual HTTP header? </summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-03-07T15:43:21Z</dc:date>
  </entry>
  <entry>
    <title>RE: Image not refreshing</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12717810" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12717810</id>
    <updated>2013-03-06T21:40:09Z</updated>
    <published>2013-03-06T21:40:09Z</published>
    <summary type="html">A known issue with some phone models requires that the URL in the Refresh header be specified, e.g.:
Refresh: 0;url=http://page.to.refresh/to</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-03-06T21:40:09Z</dc:date>
  </entry>
  <entry>
    <title>RE: Remove CiscoIPPhoneStatusFile</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12484417" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12484417</id>
    <updated>2013-02-28T17:28:40Z</updated>
    <published>2013-02-28T17:28:40Z</published>
    <summary type="html">Generally an application would use CiscoIPPhoneExecute to push down a URL to another screen a URI like 'App:Close' or 'Init:Services' to clear the app.  Note, the CiscoIPPhoneStatus object can only be cleared by the app (or a phone reset), so if the object is displayed and the app 'goes away', users are stuck.
It is the general guidance to avoid CiscoIPPhoneStatus, but in certain cases it is still very useful...</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-02-28T17:28:40Z</dc:date>
  </entry>
  <entry>
    <title>RE: Re: New Message from Levent Ozturk in IP Phone Services (IPPS) - IP Pho</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12438978" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12438978</id>
    <updated>2013-02-27T16:03:42Z</updated>
    <published>2013-02-27T16:03:42Z</published>
    <summary type="html">The behaviour is phone/firmware specific and not configurable.  Just a guess as to whether this is the actual problem.  We can perhaps gain some more insight by comparing a network packet capture of a working vs non-working phone - and of course identifying the nature of the failure in the application script (on IIS?) would be the primary troubleshooting avenue.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-02-27T16:03:42Z</dc:date>
  </entry>
  <entry>
    <title>RE: Re: New Message from Levent Ozturk in IP Phone Services (IPPS) - IP Pho</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12395686" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12395686</id>
    <updated>2013-02-26T16:00:47Z</updated>
    <published>2013-02-26T16:00:47Z</published>
    <summary type="html">Some models handle un-specified input values differently.  For example, with a input fields 'requiredValue' and 'optionalValue', if the user submits the screen without putting anything into the optional field, the phone may request either:
GET /myService?requiredValue=something&amp;optionalValue=
or
GET /myService?requiredValue=something

This makes a difference in the server-side script, as 'if (optionalValue=="")' might work for the former, but won't for the latter (the optionalValue param was never received and is 'undefined'.)  You will want to check if optionalValue!=undefined before assuming it has any value (including empty string)</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-02-26T16:00:47Z</dc:date>
  </entry>
  <entry>
    <title>RE: 9971 Full Screen</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12222226" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12222226</id>
    <updated>2013-02-21T16:40:32Z</updated>
    <published>2013-02-21T16:40:32Z</published>
    <summary type="html">Unfortunately no.  One of the overriding goals of the phone UI teams has always been to ensure the device is always perceived/usable as a phone, with apps given sub function status.  As much as it may have made sense for fullscreen apps, the concept has always been declined due to UE reasons...
Options for changing app skin/appearance are not available.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-02-21T16:40:32Z</dc:date>
  </entry>
  <entry>
    <title>RE: CGI Execute Question</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11984931" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11984931</id>
    <updated>2013-02-15T20:41:46Z</updated>
    <published>2013-02-15T20:41:46Z</published>
    <summary type="html">If I understand your question correctly the answer is no, but the workaround is to use CiscoIPPhoneExecute to get the phone to make a URL request, which returns something like a CiscoIPPhoneText object with a Refresh header on it.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-02-15T20:41:46Z</dc:date>
  </entry>
  <entry>
    <title>RE: Sending XML Object Using Javascript</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11746617" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11746617</id>
    <updated>2013-02-08T20:39:15Z</updated>
    <published>2013-02-08T20:39:15Z</published>
    <summary type="html">Modern browsers prevent 'cross origin' requests like this, where the host that provided the javascript is different from the host that the XMLhttpRequest is going to.
http://en.wikipedia.org/wiki/Same_origin_policy
The usual recourse is to have the javascript post a custom request back to the origin web server, and have the web server make the actual post to the phone (i.e. proxy)
 </summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2013-02-08T20:39:15Z</dc:date>
  </entry>
  <entry>
    <title>RE: Filtering LDAP results from LDAP search</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=9046015" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=9046015</id>
    <updated>2012-12-03T20:41:31Z</updated>
    <published>2012-12-03T20:41:31Z</published>
    <summary type="html">The LDAPSearch component is fairly limited in what it can do, and beyond what's documented that's it.  It is included in the SDK more as a working example than as a robust enterprise solution.

It is quite possible to query LDAPs using today's CGI environments, with the obvious benefits being native inclusion and near infinite flexibility.  A few threads that might be helpful:
[url=http://forums.aspfree.com/code-bank-54/asp-code-query-ad-ldap-169652.html]http://forums.aspfree.com/code-bank-54/asp-code-query-ad-ldap-169652.html[/url]
[url=http://stackoverflow.com/questions/7946856/user-authentication-over-ldap-in-asp]http://stackoverflow.com/questions/7946856/user-authentication-over-ldap-in-asp[/url]</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-12-03T20:41:31Z</dc:date>
  </entry>
  <entry>
    <title>RE: Accessing IP Phone Information</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8863998" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8863998</id>
    <updated>2012-11-27T20:24:32Z</updated>
    <published>2012-11-27T20:24:32Z</published>
    <summary type="html">Not aware of any comprehensive list, unfortunately.  If you have a question about a particular parameter we can probably research it...</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-11-27T20:24:32Z</dc:date>
  </entry>
  <entry>
    <title>RE: CiscoIPPhoneExecute and UCM 8.6.1</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8402824" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8402824</id>
    <updated>2012-11-07T20:42:54Z</updated>
    <published>2012-11-07T20:42:54Z</published>
    <summary type="html">A network packet capture (via Wireshark) is usually the best way to inspect the actual authentication request and response for issues (make sure and capture from a PC connected to the phone's extra PC switch port.)  Feel free to attach the pcap here.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-11-07T20:42:54Z</dc:date>
  </entry>
  <entry>
    <title>RE: CiscoIPPhoneExecute and UCM 8.6.1</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8402391" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8402391</id>
    <updated>2012-11-07T20:08:05Z</updated>
    <published>2012-11-07T20:08:05Z</published>
    <summary type="html">The IP Phone Services XML interface capabilities are more dependent on the phone model/firmware than the UCM version, but the answer is generally: yes.
You should be able to consider the latest available guide/SDK as applicable to the current UCM release, if and until a newer doc/SDK is released.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-11-07T20:08:05Z</dc:date>
  </entry>
  <entry>
    <title>RE: Possible to get camera image from 99nn?</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8369427" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8369427</id>
    <updated>2012-11-06T23:54:42Z</updated>
    <published>2012-11-06T23:54:42Z</published>
    <summary type="html">Capturing from the camera is not supported.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-11-06T23:54:42Z</dc:date>
  </entry>
  <entry>
    <title>RE: Searching IPPS URL Parameter like #DEVICENAME#</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8151168" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8151168</id>
    <updated>2012-10-30T17:05:31Z</updated>
    <published>2012-10-30T17:05:31Z</published>
    <summary type="html">DEVICENAME is the only macro of its kind.
There is an API that can provide the logged in user by device: http://developer.cisco.com/web/emapi/home</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-10-30T17:05:31Z</dc:date>
  </entry>
  <entry>
    <title>RE: Multicast audio for PA system</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8130578" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=8130578</id>
    <updated>2012-10-29T20:50:58Z</updated>
    <published>2012-10-29T20:50:58Z</published>
    <summary type="html">I think in general your plan should work.  See the 'Interaction with Call Streaming' section for details on how it works with normal call operation.
Note also you can take advantage of the 'Idle URL' functionality, which will cause the phone to retrieve a URL (which you can then have trigger your streaming service) after a configurable idle period.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-10-29T20:50:58Z</dc:date>
  </entry>
  <entry>
    <title>RE: Phone service - HTTP Connection failed error on 8941 phones</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=7806172" />
    <author>
      <name>David Staudt</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=7806172</id>
    <updated>2012-10-18T16:05:48Z</updated>
    <published>2012-10-18T16:05:48Z</published>
    <summary type="html">Probably the best way to troubleshoot will be to take a look a the HTTP XML messages being sent between phone and application.  Can you get a network packet capture - i.e. via Wireshark running on a PC connected to the phone's extra switch port?  If you don't spot any immediate issues feel free to attach here.</summary>
    <dc:creator>David Staudt</dc:creator>
    <dc:date>2012-10-18T16:05:48Z</dc:date>
  </entry>
</feed>

