Provisioning AXL - Product Specific Configuration Layout

Version 1
    This document was generated from CDN thread

    Created by: Laurent TRELET on 13-10-2009 08:58:11 AM
    Hello,
     
    I can't find in the AXL API documentation the way to configure the fields in the "Product Specific Configuration Layout" for a phone.
    This is a real problem for us because some fields are very important like the "Settings Access"... We can modify all the other fields for a phone with AXL but not for this part "Product Specific Configuration Layout".
     
    If someone has already solved this problem and know how to fill this fileds, I am interested in...
     
    I have one more question; If we develop applications using AXL (without certify our software by CISCO), can we have troubles with the CISCO TAC if we have issues on or cluster even if they are not linked to AXL utilization ?
     
    Finally, I have heard that there will be some changes with the AXL API on CUCM v8. I can't find the documentation on the net for the moment, maybe at the end of this year. I am afraid of this point, I don't know if we will have to use an AXL proxy if can't send AXL requests "manually" formated... Do you have information on this topic ?
     
    Thank you in advance.
     
    Regards.

    Subject: RE: Provisioning AXL - Product Specific Configuration Layout
    Replied by: Giggesh Thekkekeloth on 13-10-2009 12:21:05 PM
    Hi,
    To answer few of your questions,
    "Product Specific Configuration Layout" for a phone, can be set via the 'vendorConfig', it seems, the field inside which is specific to phone firmware.
     
    "If we develop applications using AXL (without certify our software by CISCO), can we have troubles with the CISCO TAC if we have issues on or cluster even if they are not linked to AXL utilization ?"
     
    In general. TAC will take the case. but CISCO Recommends to used certify products for scalability/reliability, reason, those developed product has chance of affecting the system/server performance in different way. May be, front end issue might be seems to be not related to AXL, but chance of root cause might be related to that later.

    "I have heard that there will be some changes with the AXL API on CUCM v8. I can't find the documentation on the net for the moment, maybe at the end of this year. "
     
    It seems, there are many schema changes in AXL on CUCM v8, which is still under dev, and the docs are not out yet. And it seems you can still send AXL requests "manually" formated.

    Subject: RE: Provisioning AXL - Product Specific Configuration Layout
    Replied by: David Staudt on 13-10-2009 12:48:42 PM
    <vendorConfig> is the field that holds the device specific configuraiton info.  This is a 'freeform' XML field, with some challenges:
      - Individual product schemas for this are not published
      - .NET/Axis (and likely other libraries for automatically consuming WSDL) do not cleanly handle fields of type 'xsi:any' .  You may need to 'manually' parse this field via XML DOM, etc.
      - Creating a phone via AXL does not populate <vendorConfig>.  This will happen the first time the phone is modified via the CCMAdmin web UI
     
    For products that have not completed interop testing with Cisco, TAC will do initial triage to determine if the issue is in the realm of core Cisco product support.  If the issue is determined to be somewhere in the integration with the 3rd party app,  TAC will refer the issue to the 3rd party and close the case; if  Cisco product performance is impacted, TAC will request the application be removed before further troubleshooting.
     
    UCM8 will likely introduce a revamped AXL schema with many improvements - and backward compatibility impacting changes.  However, as it has for awhile now, AXL will still support the old schemas for previous releases.  See recent AXL documentation for the backward compatibility plan.

    Subject: RE: Provisioning AXL - Product Specific Configuration Layout
    Replied by: Laurent TRELET on 15-10-2009 09:09:40 AM
    Hello and thank you for your answers Giggesh and David ! Both posts answer my questions...
     
    I made a "GetPhone" request and the "vendor config" part is the following :

    http://developer.cisco.com/html/js/editor/# <vendorConfig>


      <disableSpeaker>false</disableSpeaker>


      <disableSpeakerAndHeadset>false</disableSpeakerAndHeadset>


      <forwardingDelay>1</forwardingDelay>


      <pcPort>0</pcPort>


      <settingsAccess>1</settingsAccess>


      <garp>1</garp>


      <voiceVlanAccess>0</voiceVlanAccess>


      <videoCapability>0</videoCapability>


      <autoSelectLineEnable>0</autoSelectLineEnable>


      <webAccess>0</webAccess>


      <daysDisplayNotActive>1</daysDisplayNotActive>


      <displayOnTime>07:30</displayOnTime>


      <displayOnDuration>10:30</displayOnDuration>


      <displayIdleTimeout>01:00</displayIdleTimeout>


      <spanToPCPort>0</spanToPCPort>


      <loggingDisplay>1</loggingDisplay>


      <loadServer />


      <recordingTone>0</recordingTone>


      <recordingToneLocalVolume>100</recordingToneLocalVolume>


      <recordingToneRemoteVolume>50</recordingToneRemoteVolume>


      <recordingToneDuration />


      <displayOnWhenIncomingCall>0</displayOnWhenIncomingCall>


      <rtcp>0</rtcp>


      <moreKeyReversionTimer>5</moreKeyReversionTimer>


      <autoCallSelect>1</autoCallSelect>


      <logServer />


      <g722CodecSupport>0</g722CodecSupport>


      <headsetWidebandUIControl>0</headsetWidebandUIControl>


      <handsetWidebandUIControl>0</handsetWidebandUIControl>


      <headsetWidebandEnable>0</headsetWidebandEnable>


      <handsetWidebandEnable>0</handsetWidebandEnable>


      <peerFirmwareSharing>0</peerFirmwareSharing>


      <enableCdpSwPort>1</enableCdpSwPort>


      <enableCdpPcPort>1</enableCdpPcPort>


      <enableLldpSwPort>1</enableLldpSwPort>


      <enableLldpPcPort>1</enableLldpPcPort>


      <lldpAssetId />


      <powerPriority>0</powerPriority>

      </vendorConfig>

    If i copy those lines in the "vendor config" for a "AddPhone" request, it could work correctly ? (If the model is the same).
    I will try on my lab...

    Thank's again for your other answers on my last questions. It's interesting...

    Subject: RE: Provisioning AXL - Product Specific Configuration Layout
    Replied by: Sascha Monteiro on 17-10-2009 06:37:58 PM
    I have used this in the past and worked fine, I only list the fields that are non-default, i.e.;
    <vendorConfig>
    <settingsAccess>2</settingsAccess>
    <voiceVlanAccess>1</voiceVlanAccess>
    <webAccess>1</webAccess>
    </vendorConfig>

    Subject: RE: Provisioning AXL - Product Specific Configuration Layout
    Replied by: Manas Varma on 03-08-2010 12:01:20 PM
    I have used this in the past and worked fine, I only list the fields that are non-default, i.e.;
    <vendorConfig>
    <settingsAccess>2</settingsAccess>
    <voiceVlanAccess>1</voiceVlanAccess>
    <webAccess>1</webAccess>
    </vendorConfig>


    Can you please explain how would I perform the same operation if I am using C# in .NET Platform