Status of Hunt Lists via RIS

Version 1
    This document was generated from CDN thread

    Created by: Alexander Wolf on 07-04-2009 09:53:19 AM
    Hello,
     
    I wonder if somebody does know how I get the status of Hunt/Route Lists from RisPort in 6.1(2).
     
    Back in 4.2(3) a standard SelectCMDevice did the job, but now this does not work anymore (of course I know that HuntList was removed from DeviceClass enum).
     
    RTMT is able to display status of Hunt Lists so the must be a (maybe not documented) way.
     
    Thanks in advance,
    Alex

    Subject: RE: Status of Hunt Lists via RIS
    Replied by: David Staudt on 10-04-2009 04:59:17 PM
    It looks like this may be effected by a defect: CSCsr98839.  This is targeted for fix in 7.1(2) - release targeted within the next several weeks.
     
    The defect notes indicate the request can be sent, but the response shows HuntList class erroneously as 'Unknown'.
     
    Is this the same symptom you see?


    Subject: RE: Status of Hunt Lists via RIS
    Replied by: Alexander Wolf on 14-04-2009 02:42:10 PM
    Well, this might be the same issue, but I can only guess.
    From my point of view there are the following issues (did some engineering/tests):
    The WSDL does not contain Huntlist for DeviceClass any more
    [url=https://<IP>:8443/realtimeservice/services/RisPort?WSDL]https://<IP>:8443/realtimeservice/services/RisPort?WSDL issues
     
    <......>
    <simpleType name="DeviceClass">
       <restriction base="string">
         <enumeration value="Any" /> 
          <enumeration value="Phone" /> 
         <enumeration value="Gateway" /> 
         <enumeration value="H323" /> 
         <enumeration value="Cti" /> 
         <enumeration value="VoiceMail" /> 
         <enumeration value="MediaResources" /> 
         <enumeration value="Unknown" />
       </restriction>
    </simpleType>
    <.......>

    If you ignore the WSDL and ask for Huntlist anyway, you get nothing back - no huntlist/routelist devices (but at least no exception - that means that internally Huntlist is still somehow known).

    By doing a man in the middle attack with Fiddler to track the communication between RTMT and CUCM (wasn't that easy, either) I now found a workaround to get the states.

    Calling [url=https://<IP>/ast/ASTIsapi.dll?OpenDeviceSearch?Type=7&NodeName=&SubSystemType=0&Status=&MaxDevices=200&Model=&SearchType=Name&SearchPattern=&Protocol=null]https://<IP>/ast/ASTIsapi.dll?OpenDeviceSearch?Type=7&NodeName=&SubSystemType=0&Status=&MaxDevices=200&Model=&SearchType=Name&SearchPattern=&Protocol=null

    gives back a list of the devices.

    This does the job for me right now.

    Thank you for the help.

    Regards,
    Alex