Not Getting the Number for scheduledUnprovisionedEndpoints

[cdnadmin]

This document was generated from CDN thread

Created by: Michael Nelson on 13-09-2012 02:20:22 PM
 
We recently started seeing that the <number> element in the <scheduledUnproviosnedEndpoints> group is not being returned for endpoints that were scheduled as unprovisioned endpoints. We are pretty sure that the element was previously being returned.
 
Could upgrades to other components (bridges, call managers, etc) cause problems like this?
 
The following is output from a getCurrentMeetingStatusRequest:
 
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <ns2:getCurrentMeetingStatusResponse xmlns:ns2="http://amm.api.ctc.txbu.cisco.com">
         <return>
            <meetingStatus>
               <activeParticipants>
                  <isDialout>false</isDialout>
                  <isHost>false</isHost>
                  <joinTime>2012-09-13T17:04:00Z</joinTime>
                  <numScreens>1</numScreens>
                  <number>18131110003</number>
                  <videoBandwidth>5936000</videoBandwidth>
               </activeParticipants>
               <bridgeResourceName>tpa-exch-ctms</bridgeResourceName>
               <bridgeResourceType>CTMS</bridgeResourceType>
               <endTime>2012-09-13T17:15:00Z</endTime>
               <meetingId>97394199</meetingId>
               <scheduledUnprovisionedEndpoints>
                  <dialOut>false</dialOut>
                  <organizationKey>8a7b84753635832001364019173d22c2</organizationKey>
                  <ports>1</ports>
               </scheduledUnprovisionedEndpoints>
               <scheduledUnprovisionedEndpoints>
                  <dialOut>false</dialOut>
                  <organizationKey>8a7b84753635832001364019173d22c2</organizationKey>
                  <ports>1</ports>
               </scheduledUnprovisionedEndpoints>
               <startTime>2012-09-13T17:00:00Z</startTime>
               <subject>test meeting for unprovisioned endpoints</subject>
            </meetingStatus>
         </return>
      </ns2:getCurrentMeetingStatusResponse>
   </env:Body>
</env:Envelope>

Subject: RE: Not Getting the Number for scheduledUnprovisionedEndpoints
Replied by: John Yontz on 04-10-2012 06:36:22 PM
We had a separate e-mail discussion of this, but posting the answer here as well:

The getCurrentMeetingStatusResponse contains both schedule-time as well as attend-time information.  The activeParticipants objects will contain the number for all active participants in the meeting, whether they were scheduled as provisioned or unprovisioned.   The scheduledProvisionedEndpoints (which don’t appear in your example) and scheduledUnprovisionedEndpoints will contain the information that was provided at schedule-time only.  For the scheduledUnprovisionedEndpoints, the number would appear only if they were scheduled as unprovisioned (i.e. guest) dial-out endpoints.  In your example, they were scheduled as dial-in and as such, no number can be provided at schedule-time.  Therefore, you don’t see any number element in the scheduledUnprovisionedEndpoints elements.

If you schedule unprovisioned dial-out endpoints, you will see the number field in getCurrentMeetingStatusResponse as you expected.