Scan Mode on 7925

New Message from David Staudt in Administration XML (AXL) - Administration

2012-10-12T20:37:26Z

OK - this is starting to make sense. I get slightly different results executing the query select * from device where name= 'SEP00233341C798' from executeSQLQuery and from the console using run sql From AXL I get 001f76a7-358a-552c-86ea-52647dc9f3c4 SEP00233341C798 ... snip ... 0 0 1 2 64 1 ... snip ... t 2 2 It seems like I am somehow getting the field name as "vendorConfig" rather than "xml". This is the cause of my cornfusion. As always David, thanks so much for your help! Wesley A. Schochet System Architect Children's of Minnesota + wes.schochet@childrensmn.org ( 651-855-2081 È 651-592-5441 >>> On 10/12/2012 at 1:43 PM, Cisco Developer Community Forums wrote: David Staudt has created a new message in the forum "Administration XML Questions": -------------------------------------------------------------- Updating vendor config settings is tricky: - Vendor config data is stored in a single field in the database, as a chunk of XML itself - Note that the - The application would need to read the existing XMchunk of XML is not XML-escaped or wrapped in a CDATA, it is present as just XML, which makes it part of the overall XML response document L from this field, update the XML, and then send the XML back in an update - The vendor config XML schema/parameters are not formally documented, however they are usually pretty self-explanatory - The vendor config XML for a given model could change due to new firmware version for that model - almost always this is just to add new fields, however As the XML is returned in a chunk, which can have more or less arbitrary schema itself (xsi:any), your typical WSDL consuming layers (.NET/Axis) will not make it easy to get access to it. It may be easier to just use XML parser handling. -- To respond to this post, please click the following link: http://developer.cisco.com/web/axl/forums/-/message_boards/view_message/7570177 or simply reply to this email. Confidentiality Statement: This email/fax, including attachments, may include confidential and/or proprietary information and may be used only by the person or entity to which it is addressed. If the reader of this email/fax is not the intended recipient or his or her agent, the reader is hereby notified that any dissemination, distribution or copying of this email/fax is prohibited. If you have received this email/fax in error, please notify the sender by replying to this message and deleting this email or destroying this facsimile immediately.

RE: Scan Mode on 7925

2012-10-12T18:42:53Z

Updating vendor config settings is tricky: - Vendor config data is stored in a single field in the database, as a chunk of XML itself - Note that the chunk of XML is not XML-escaped or wrapped in a CDATA, it is present as just XML, which makes it part of the overall XML response document - The application would need to read the existing XML from this field, update the XML, and then send the XML back in an update - The vendor config XML schema/parameters are not formally documented, however they are usually pretty self-explanatory - The vendor config XML for a given model could change due to new firmware version for that model - almost always this is just to add new fields, however As the XML is returned in a chunk, which can have more or less arbitrary schema itself (xsi:any), your typical WSDL consuming layers (.NET/Axis) will not make it easy to get access to it. It may be easier to just use XML parser handling.

Scan Mode on 7925

2012-10-12T18:27:26Z

I am trying to update the Scan Mode field on a few hundred 7925 phones. I thought I could do a relatively simple SQL update, but I am not understanding the table structure. This info is in the vendor config field / block. Any insight would be appreciated! Confidentiality Statement: This email/fax, including attachments, may include confidential and/or proprietary information and may be used only by the person or entity to which it is addressed. If the reader of this email/fax is not the intended recipient or his or her agent, the reader is hereby notified that any dissemination, distribution or copying of this email/fax is prohibited. If you have received this email/fax in error, please notify the sender by replying to this message and deleting this email or destroying this facsimile immediately.