Export (0) Print
Expand All

2.5.3 Perform Client Bootstrap

Office

This use case, illustrated in the following diagram, describes how a client completes sign-in, obtains information such as the contact list, and other relevant parameters from the protocol server after sign-in.

Dd945434.897806a8-bda7-4659-8c34-95dca7b69d4b(en-us,office.12).jpg

Figure 8: Steps for performing client bootstrap

References

Preconditions

  • The protocol client is connected to the protocol server.

  • The protocol client is authenticated and registered with the protocol server.

Steps

  1. The protocol client sends a request for in-band provisioning, as described in [MS-SIPREGE]. In-band provisioning is a mechanism through which a protocol server can provide a protocol client with initial configuration information, at a point when the protocol client does not yet have access to global policies stored in Active Directory, or with server configuration information, such as the ABSUniform Resource Locator (URL) and Group Expansion web service URL. The protocol client sends a SUBSCRIBE request, as described in [MS-SIPREGE].

  2. The protocol server sends a 200 OK response to the SUBSCRIBE request that includes the protocol server configuration, various policies that the protocol client enforces, the URL of the ABS, and information essential for protocol client control of the user’s desktop phone. These categories of information are defined in provisioning extensions, as described in [MS-SIPREGE].

  3. The protocol client sends a SUBSCRIBE request for the Contacts and Groups information, as described in [MS-PRES] and [MS-SIPREGE].

  4. The protocol server returns the Contact List and Groups, as described in [MS-SIPREGE].

  5. The protocol client sends a SUBSCRIBE request for the user’s own presence information, such as the user’s contact card and calendar information, as described in [MS-PRES] and [MS-SIPREGE].

  6. The protocol server sends a 200 OK response with the information listed in step 5.

  7. The protocol client sends a SERVICE request to retrieve the user’s location profile for a VoIP call, as described in [MS-SIPRE] and [MS-SIPREGE].

  8. The protocol server sends a 200 OK response with the information listed in step 7.

    Note: This step assumes EnhancedEmergencyServices and LocationRequired settings are enabled in the user's location profile.

  9. The protocol client sends a SERVICE request to retrieve information about available conferencing servers (MCUs), as described in [MS-SIPREGE].

  10. The protocol server sends a 200 OK response with the information listed in step 9.

  11. The protocol client sends a SERVICE request to obtain Media Relay authentication (2) tokens, as described in [MS-AVEDGEA].

    Note: This step assumes an Audio/Video Edge Server (A/V Edge Server) is configured and both clients’ support [MS-ICE] or [MS-ICE2]. If an A/V Edge Server is not configured or one or both of the clients do not support [MS-ICE] or [MS-ICE2] the protocol exchange will differ; see the detailed protocol documents for those protocol exchanges.

  12. The protocol server sends a 200 OK response with the information listed in step 11.

  13. The protocol client sends a SERVICE request to publish the user’s presence information, as described in [MS-PRES].

  14. The protocol server acknowledges publishing the information listed in step 13.

  15. The protocol client issues a batch subscription request, as described in [MS-SIPREGE], for enhanced presence information, as described in [MS-PRES], for all members of the contact list that were returned by the server in step 4.

  16. The protocol server acknowledges the batch subscription request sent in step 15.

Note: The order in which the protocol client fetches the information need not be the exact order specified above and can be in any order of its choice.

Post-conditions

  • The protocol client is finished with bootstrapping and is ready to receive presence updates and initiate any communication.

Show:
© 2014 Microsoft