6941 IP phone

Version 1
    This document was generated from CDN thread

    Created by: Bernhard Beckmann on 28-01-2010 06:15:02 PM
    I am currently testing a 6941 phone (FW: 8.5.3 @ CUCM 7.1.3)

    Two issues:
    1. #DEVICENAME# is not changed to its SEP value if the service is on a line button (SURL). It works fine via the phone's service button path.
    Wireshark traces:
    GET /manualshowall?device=#DEVICENAME# HTTP/1.1 ... (line button SURL)
    GET /manualshowall?device=SEP001121FFA018 HTTP/1.1 ... (via service button)
    On a 7971, both scenarios work just fine.

    2.  Encoding (UTF-8) from 'CiscoIPPhoneInput' doesn't seem to comply with any RFCs?
    Example user input : "MÜ" ("Ü" = umlaut)
    7965, 7971 send: "M%C3%9C"   bytes: 4D 25 43 33 25 39 43
    6941 sends:        "M??"            bytes: 4D C3 96            
       
    Bugs or am I missing the point?

    Thanks,
    Bernie

    Subject: RE: 6941 IP phone
    Replied by: Anitha V on 05-02-2010 05:53:17 AM
    Hi Bernhard,
     
    Could you please share the corresponding wireshark traces for both the scenarios along with IP address details?
     
    Thanks and Regards,
    Anitha

    Subject: RE: 6941 IP phone
    Replied by: Bernhard Beckmann on 09-02-2010 10:19:56 AM
    Anitha,
     
    First, the #DEVICENAME# issue, which is more annoying:
     
    IP addresses:
    Application server: 192.168.100.15
    6941 IP phone: 192.168.100.233
    7965 IP phone: 192.168.100.62
     
    Please find attached two Wireshark traces, one for the 6941 ("SURL_err_6941.pcap") and one for the 7965 phone ("SURL_ok_7965.pcap").
     
    Thanks,
    Bernie

    Subject: RE: 6941 IP phone
    Replied by: Anitha V on 10-02-2010 06:29:59 AM
    Hi Bernie,
     
    This looks like a defect.
     
    Investigating this issue, will get back to you soon.
     
    Regards,
    Anitha

    Subject: RE: 6941 IP phone
    Replied by: Anitha V on 10-02-2010 08:18:01 AM
    Hi Colin,
     
    Looks like both the issues which you reported are defects.
     
    The 1st issue related to 'devicename' should be fixed on 9.0(2) and the corresponding defect ID is CSCtb64081
    The 2nd issue related to 'UTF-8 encoding, is a enhancement issue. Will be taken care in future release and the coresponding defect Id is CSCte94630.
     
    Hope this helps.
     
    Anitha
    Cisco Developer Services
     

    Subject: 7925 IP phone
    Replied by: Bernhard Beckmann on 10-02-2010 02:58:46 PM
    Thanks, Anitha.

    7925 IP phones seem to have another issue. This one's actually project critical (>150 pieces 7925):

    There, POSTing CiscoIPPhoneExecute doesn't work for URL's like http://....
    URI's, such as "Play:chime.raw", within the same message are okay.

    Sporadically, the 7925 responds with Status="0" (=success), though the URL request is never sent back to the application server. Sometimes, there is an HTTP 500 Internal Server Error. After a couple of consecutive POSTs, the 7925 even restarts!!!

    CUCM: 7.1(3)
    7925 F/W: CP7925G-1.3.3

    Please find attached two Wireshark traces again, one for the 7925 ("7925_err_500.pcap") and one for a 7965 phone ("7965_ok.pcap").

    Thanks,
    Bernie

    Subject: RE: 7925 IP phone
    Replied by: Anitha V on 22-02-2010 11:04:34 AM
    Hi Bernard,
     
    Will look into this issue and get back to you.
     
    Regards,
    Anitha

    Subject: RE: 7925 IP phone
    Replied by: Bernhard Beckmann on 17-03-2010 11:59:00 AM
    Hi Anitha,
     
    when removing one space behind 'URL=', it works. Strange that the phone responses with 'ResponseItem Status="0" Data="Success"' when the space is included. It shouldn't restart in any case which might become a security issue. Another point, which is not critical for the current deployment case: each service assigned to a 7925's service menu (Subscribe Services in Phone Configuration) appears twice there.
     
    Thanks.
     
    Bernie

    Subject: RE: 7925 IP phone
    Replied by: Anitha V on 26-03-2010 05:03:12 AM
    Hi Bernie,
     

    Services appear twice because
    Service Provisioning is set to BOTH, you set to Internal or External to fix it.
     
    Also, 7925 does not handle the extra space following
    ¿URL=¿, which is a defect and i have created a defect CSCtf85595 for that issue.
     
    Regards,
    Anitha