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> 
