We have tested out other firmware, and they are working correctly. Most of the old firmware of 7940/60/70 are working fine. However, some of the new 7970 (7.x series loads) firmware also have the same problem.
Has anyone else run into this? Any comments/advise?
I know this sounds sarcastic but unfortunately it's the truth: welcome to xml development. It's not uncommon for different loads to act differently. So basically what I do is stick to the programming guide (except for the request headers which are not reliable) and if something doesn't work, try a different load and open a case.
The QueryStringParam is a feature that has proven to be quite problematic in the past (see my other thread from a few days ago). The documentation says the QueryStringParam should be appended, but there are no examples that would confirm this. But if one phone acts different than the others, it's definitely time for a case.
I'm a bit puzzled by your url though.. how can a http get to an xml page work as an application? And why does the order of the querystrings matter? In most programming languages, you have a means to get any query string parameter regardless of the order in which they are given.
I agree with you that phone loads behave slightly different. We have, at times, resolved problems by upgrading or downgrading the phone load, even when we are using simple XML object (no JTAPI/AXL stuff).
I am using a web server that acts differently based on the first parameter in the query sting. For example, http://someURL?Open will do one thing, but http://someURL?close will do another. The first parameter is what is looks for. The order after the first one does not matter. We are able to use http by adding xml content header in the http response. This has worked well for the past many years.
I have opened a TAC, but I got a response back that this is a developer support issue. That means, I now I have buy $5K/year subscription to resolve this issue which I believe is a bug in the firmware.
>That means, I now I have buy $5K/year subscription to resolve this issue which I believe is a bug in the firmware.
Join me in singing the "that's not right" song. It has happened to me many times - depending on which TAC engineer you get. You can try to push your luck by providing easy reproducability and traces upfront, make references to the appropriate documentation.. basically everything to support your thesis that it's a phone bug. It still very much depends on what engineer it gets to, but not all are so stubborn. In the end, if you can open TAC cases and are a Cisco partner, cases that prove to be a waste of their time will negatively influence your company's performance which means lower rebates so in the end your company loses anyway and you have sufficient motivation to only open cases when needed.
I'm still waiting to have the subscription approved.. somehow the last two approvals got lost somewhere in the process.. a third is pending. But what I don't get at all is that each case is $500 and there's not a single word about a refund in case your case turned out to be a bug on Cisco's side.. I mean.. pay $500 bucks to be allowed to tell Cisco about a bug in their product? Give me a break. I can understand why they ask for money in case it turns out I'm wasting their time or need them to support me in what it supposed to be my job, but as soon as a bug is opened, you should get the money back.
Have you guys come up with a solution to this yet? I'm having the same problem with the 7961 when using my modification of the intercom.asp that I've enabled two-way intercom.
I basically send http requests to other phones with certain parameters in the querystring that tell it which functions to perform.
Works on all phones just fine, except that when you dial from a 7961 to any other phone model other than our 7940's, it cannot display the page. But it will display the page just fine when you dial a 7940 phone.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...