Menu

Error on accessing Device Management

Chris
2011-12-12
2013-04-25
  • Chris

    Chris - 2011-12-12

    Glad to see the project is back.

    Even with the new version, I get the following when trying to access the Device Management Tab.

    12/11/2011 7:40:39 PM  - Error - Calling GenPage for plugin, link: /ipphonexml_config?page=3 Error: The 'axl' start tag on line 5 does not match the end tag of 'data'. Line 6, position 290.

    a debug in my cisco router tells me

    Dec 11 19:44:55: Mon, 12 Dec 2011 01:44:55 GMT 192.168.150.8 /ios_xml_app/cme au
    th_required
            Protocol = HTTP/1.1 Method = POST
    Dec 11 19:44:55:        Content-Type = text/xml
            Content-Length = 110

    Did you add anymore debug to it?

     
  • bcstechnologies

    bcstechnologies - 2011-12-13

    I have added a debug file, which is called ipphonexml_debug.log.  It is actually going to C:\Windows\system32 right now, so I am opening a bug for that already too.  I believe the best course of action is to send me the output of a "show version" on your router, and also the output of "show telephony-service".  I just today acquired an extra router which I intend to use for testing.  I should be able to reproduce your error and figure out what needs fixing if I can get my router on the same versions.  Thank you for the feedback so soon!

     
  • bcstechnologies

    bcstechnologies - 2011-12-13

    Please download the latest version, the previous version had the AXL configuration hard-coded and so it was ignoring the authentication data you entered into the plugin.  Additionally, please make sure you have all of the configurations listed in the instructions found here:
    https://sourceforge.net/apps/mediawiki/ipphonexml/index.php?title=Plugin_Installation_and_Initial_Setup

    The "ip http server" and the "ixi application" commands were not in the previous documentation, and were probably overlooked…

     
  • Chris

    Chris - 2011-12-13

    Show Ver

    Cisco IOS Software, 2800 Software (C2800NM-SPSERVICESK9-M), Version 15.1(4)M2, R
    ELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (C) 1986-2011 by Cisco Systems, Inc.
    Compiled Mon 26-Sep-11 16:41 by prod_rel_team

    ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1)

    kov-ucme uptime is 5 weeks, 6 days, 18 hours, 1 minute
    System returned to ROM by reload at 21:38:52 CDT Tue Nov 1 2011
    System restarted at 21:40:33 CDT Tue Nov 1 2011
    System image file is "flash:c2800nm-spservicesk9-mz.151-4.M2.bin"
    Last reload type: Normal Reload
    Cisco 2821 (revision 1.0) with 249856K/12288K bytes of memory.
    Processor board ID FTX1244A6BM
    2 Gigabit Ethernet interfaces
    8 Voice FXO interfaces
    4 Voice FXS interfaces
    DRAM configuration is 64 bits wide with parity enabled.
    239K bytes of non-volatile configuration memory.
    250368K bytes of ATA CompactFlash (Read/Write)

    Show Telephony-Service

    CONFIG (Version=8.6)

    Version 8.6
    Max phoneload sccp version 17
    Max dspfarm sccp version 18
    Cisco Unified Communications Manager Express
    For on-line documentation please see:
    http://www.cisco.com/en/US/products/sw/voicesw/ps4625/tsd_products_support_serie
    s_home.html

    protocol mode default
    ip source-address 192.168.150.252 port 2000
    ip qos dscp:
    ef (the MS 6 bits, 46, in ToS, 0xB8) for media
    cs3 (the MS 6 bits, 24, in ToS, 0x60) for signal
    af41 (the MS 6 bits, 34, in ToS, 0x88) for video
    default (the MS 6 bits, 0, in ToS, 0x0) for serviceservice directed-pickup

    Other useful information also maybe:

    ixi transport http
    response size 8
    no shutdown
    request outstanding 2
    request timeout 30
    !
    ixi application cme
    response timeout 30
    no shutdown

    ip http server
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip http path flash:/web

     
  • Chris

    Chris - 2011-12-13

    I also tried the newest version with the same results.

     
  • bcstechnologies

    bcstechnologies - 2012-02-12

    Chrkov,

    Good news in that I have been able to reproduce your issue finally by adding more devices.  There is an internal buffer in the ixi application on CME that can only hold a 64k response, and you likely have more devices than I did so you were filling it up.  I am working on a solution to this, but in the mean time you can do the following on the Cisco router to verify that we are having the same issue:

    1) From IOS enable mode, run "debug cme-xml"
    2) Turn on terminal montiroing with the command "term mon"
    3) Run the request from HomeSeer to view devices (click "Device Management" tab)
    4) Check the IOS Console output for errors, if you see the below error then this is the issue:

    -ERROR BEGIN-
    Feb 12 16:06:27.280 CST: CME got a raw XML message.
    Feb 12 16:06:27.280 CST: doc 0x4B083324, doc->doc_type 3, req 0x4B13D6D0
    Feb 12 16:06:27.280 CST: CME extracted a XML document
    Feb 12 16:06:27.280 CST: Response buffer 0x49EBB9EC, len = 8192
    Feb 12 16:06:27.280 CST: First Tag ID  SOAP_HEADER_TAG_ID 58720257
    Feb 12 16:06:27.280 CST: First Attribute ID SOAP_ENV_ATTR 50331649
    Feb 12 16:06:27.280 CST: cme_xml_process_request
    Feb 12 16:06:27.280 CST: cme_xml_process_ISgetDevice
    Feb 12 16:06:27.280 CST: cme_xml_process_ISDevName all
    Feb 12 16:06:27.280 CST: build_ISgetDevice_resp_all got keyword 1
    Feb 12 16:06:27.284 CST: Not enough buffer for response, please config a larger one.
    Feb 12 16:06:27.284 CST: Not enough buffer for response, please config a larger one.
    Feb 12 16:06:27.284 CST: Not enough buffer for response, please config a larger one.
    Feb 12 16:06:27.284 CST: Not enough buffer for response, please config a larger one.
    Feb 12 16:06:27.284 CST: Not enough buffer for response, please config a larger one.
    Feb 12 16:06:27.284 CST: Not enough buffer for response, please config a larger one.
    -ERROR END-

     
  • bcstechnologies

    bcstechnologies - 2012-02-14

    The latest build has been posted, and the above issue noted has been resolved.  Please try this version to see if you have a more positive experience.  Additionally, please review the documentation on the Wiki as I have updated the integration procedures.

     

Log in to post a comment.