Cisco Cisco Prime Collaboration Provisioning 11.5 Betriebsanweisung
© 2012-2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 55 of 2
• idPrefix—String that is added to the beginning of the internally generated numeric to form the unique NBI
identifier. A null or empty string is valid, resulting in an NBI identifier that is just the internally generated
numeric.
Returns:
CupmApiResponseValue—Object with NBI ID.
Throws:
ListApiStatusExcepton—If the server cannot execute the NBI request.
SyncReturn:
• CupmApiResponseValue—Contains CupmApiResultValue which contains CupmApiStatus
andCupmApiList. CupmApiList contains one object, the EnumerationContextType, which is used to
retrieve the list using WS-Enumeration suggested standards.
• CupmApiFaultType—Included if the NBI request failed or had warnings.
Async return:
None—The command is synchronousSpecialized Requests
listSrstPhoneInfo Java Signature
Generates a list of PhoneInfo objects (each represents a Phone with its Users and Lines) that are associated with
the given SRST IP address and Prime Collaboration Provisioning IP address. The list of phones generated will
always be the set or a subset of the phones in the Prime Collaboration Provisioning IM database.
Syntax:
public ResponseReturn listSrstPhoneInfo (CUPMServiceStub stub, String cpIpAddr, String srstIpAddr, String
queryOption, String endPointReference, String idPrefix);
Paramaters:
• cpIpAddr—IP address of the Call Processor.
• srstIpAddr—IP address of the SRST.
• queryOption—The data selection criteria, defined by the PhoneInfoqueryOption enumeration.
o
ALL—(Default) all phones in Prime Collaboration Provisioning will be considered.
o
IN_CUPM_SUBSCRIBER_RECORD—Only the phones that are in the Prime Collaboration
Provisioning subscriber record will be selected.