XML Services issue on IP Phone 79xx

Version 1

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Florian Kroessbacher on 13-07-2011 04:37:11 AM
    Hy Marco

    we are running ASC V9 with 7941,7942,7961,7962,7975 and the EvoIP Active Module well.

    can u upload the Capture File, to look into it

    cheers Floh

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Florian Kroessbacher on 13-07-2011 05:07:57 AM
    Where can i find the CAP

    cheers
    This document was generated from CDN thread

    Created by: Marco Menozzi on 13-07-2011 04:17:11 AM
    Sorry to bother this alias but Cisco TAC redirected me to CDN forum on XML specific issue.
     
    I apologize in advance for the length of the mail but I hope to find someone that could help us here.
     
    <pre>We are experiencing a problem on recording application for a big customer, the biggest bank in Italy. Follows description of the problem.

    IP Phone does not show ¿START¿ button in WebPage pushed by recorder. IP Phone shows correctly the title (<Title>) and the text (<Text>) of the WebPage pushed by the recorder, but softkeys (<SoftkeyItem>) are not displayed. User sees on the phone softkeys from the previous page (login page, pushed by login application). If the softkeys are pressed, nothing happens.

    Impacted models: 7911,7941,7942,7961,7962,7975
    Not impacted models: 6941,7912,7940,7960

    Problem impact is big, since we are testing a recording application for a bank.

    I attach a trace of HTTP and XML messages exchanged between the phone (7911) and the applications (filter ¿http¿):
    - Login application (10.113.200.22)
    - Recording application (10.182.192.29-30)
    - IP phone (10.254.194.150)

    Service flow is the following:
    1. user accesses XML service ¿Recording¿ and interacts with login application  (packets 21-25-65)
    2. User authenticates and a page with message ¿User ee21065 logged in¿ is displayed (packets 71-77)
    3. A call is received by the phone
    4. User accesses XML service ¿Recording¿ and same page than point 2 is displayed (page 667 and 776)
    5. User presses ¿Start Rec¿ softkey (packet 971)
    6. Recording application sends 302 Moved temporarly to active recorder (this is used to do failover on active or standby recorder) ¿ packet 976
    7. Ip phone sends its request to the recorder ¿ packet 987
    8. Recorder answers with a webpage with ¿START¿ softkey ¿ packet 991
    9. Ip phone shows the title (¿ASC VOIP Recording Service¿), but showed softkeys remain the ones showed on point 4 and 5 (¿Start Rec¿, ¿Logout¿ and ¿Exit¿)
    10. IP phone refreshes every 3 seconds the page, but the result does not change ¿ packets 1310, 1635 and so on

    Thanks in advance for any support

    regards

    Marco</pre>

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Marco Menozzi on 13-07-2011 04:43:25 AM
    Yes sure.

    I attach a working scenario and a not-working scenario, if I find how to do

    Thanks

    Marco

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Marco Menozzi on 13-07-2011 06:04:17 AM
    Hi Florian

    the problem is that as soon as I try to attach the files to this web site the site becomes unavailable to me for half an hour. If you can share your mail address I'll send to you directly.

    Thanks

    Marco

     blink

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Florian Kroessbacher on 13-07-2011 06:08:59 AM
    try
     
    florian.kroessbacher  gmail  com

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Florian Kroessbacher on 15-07-2011 06:47:06 AM
    For all out there!

    The solution was that the 3rd Gen phones work diffrent to the 2nd Gen Phones if the
    in the Header the Expire Header is set to a false Value.

    In our special Case the Epxire was set to

    Expires: -1\r\n

    and the 3rd Gen Phone Stuck after this Response.

    Now we set  with date and time in the Future an everything works well.

    cheers Floh

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Andrea Sala on 19-07-2011 06:26:09 AM
     
    Hi,
    I'm working with Marco on this problem. The application has been modified in such a way to set a date 1 year in the future. So that the user will close the session itself before page expires. Could this be a problem?
     
    Andrea

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Marco Menozzi on 19-07-2011 04:57:36 AM
    Florian

    let me thank you also here in the forum for your precious support in finding this limitation.

    I would take this opportunity then to wide the audience for another related question.

    Now customer set this Expiry Date as a date in the future. We are wondering if this solution could lead to other issues that we are not aware of.

    Thanks in advance

    regards

    Marco

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Stephan Steiner on 19-07-2011 05:15:39 AM
    Are you guys using ASP? (or ASP.NET)
    I found that when I developed on Tomcat, -1 wouldn't work.... the value seems to have a special meaning on IIS, whereas on Tomcat you need to put an actual date and time into the expires header. So, for my JSP pages, when I wanted page expire, I needed to set an expiration date that was in the past - then everything worked as it's supposed to.

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Marco Menozzi on 19-07-2011 05:22:51 AM
    Stephan

    I haven't immediately an answer to that. Florian is away this week I think so he couldn't comment too.

    I only understood from customer site that putting a future date instead of "-1" value it works. I was wondering if someone is aware of any drawbacks in setting this value as a future date.

     blink

    Thanks

    Marco

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Stephan Steiner on 19-07-2011 05:34:28 AM
    Well.. a value in the future would undo the expiration mode I suppose (haven't tried with the newer phones though) - at least if the documentation is correct about that. If you set it a few seconds into the future, then unless the user does something immediately, if he peforms an action at the time where the date is in the past, you're effectively what I'm doing. Of course, it may be desired that pages don't expire immediately.. so in that case it's perfectly fine to set the value in the future (but should be done for all phone types).
    When trying to find a solution for -1, I'd suggest you use a value that's in the past.. the phones will realize that the document has expired and perform the same thing as the 79xx series does when you send -1 from an ASP page.

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Stephan Steiner on 19-07-2011 11:22:25 AM
    Are you using the content expiration header settings as per the XSI developer guide (using the SoftKey:Exit command and expecting to land at a certain point.. not using exit/cancel buttons that you tie to an actual url within your application)? If so, SoftKey:Exit might not always perform as desired. If you're using your own custom exit/cancel keys/urls, then it doesn't matter (I'm doing the latter even though I'm setting the date/time to DateTime.now - 1 second).
    I've never fully understood when SoftKey:Exit does something and when it does something else so I figured it's best to use something I know that works.

    Subject: RE: XML Services issue on IP Phone 79xx
    Replied by: Andrea Sala on 20-07-2011 05:14:41 AM
    Thanks for your answer,
    yes, developer is using Softkey:Exit, but it seems to work well based on tests I've done. What do you expect to happen when you say "not always perform as desired"?
     
    Andrea