Abstract: An approach to secure API access for distinct types of users. A request for access to an API from a user is initiated and followed by sending a request for a login credential to the user based on a type of API requested: Data API or Interaction API. The login credential is received along with the network location of the user. Authenticating the login credential and create an API specific token. Assigning the API specific token to a user activity and granting the user access to the specific API.

Abstract: An approach is provided in which an information handling system sends a first request to a user over a voice channel through a first communication network. The request is in an audio format and requests a user data set from the user. The information handling system establishes a messaging channel with a user device utilized by the user through a second communication network. The messaging channel is an end-to-end digital data channel between the information handing system and the user device. The information handling system receives a set of user data corresponding to the first request from the user device over the messaging channel, and sends the set of user data to a conversation system.

Abstract: A method for third-party authorization is presented. A client request is received by a resource server in a computer system from a client, wherein the client request includes an access token. An introspection request for the access token based on the client request. The introspection gateway uses a third-party authorization server from a plurality of third-party authorization servers to handle the introspection request. A resource server response is received from the introspection gateway, wherein the resource server response identifies a set of scopes for the access token. A determination is made as to whether the access token has sufficient scope from the resource server response. In response to the access token having the sufficient scope, the client is granted access to the resource server.

Abstract: A computer system comprising a resource server running on the computer system. The resource server receives a client request from a client in which the client request includes an access token. The resource server sends an introspection request to an introspection gateway, wherein the introspection request is for introspection of the access token based on the client request, and wherein the introspection gateway uses a third-party authorization server from a plurality of third-party authorization servers to handle the introspection request. The resource server receives a response from the introspection gateway, wherein the response identifies a set of scopes for the access token. The resource server determines whether the access token has sufficient scope from a resource server response. The client is granted access to the resource server in response to the access token having the sufficient scope.

Abstract: Processing mid-dialog SIP messages by receiving a mid-dialog SIP message from a SIP user agent client, creating a new SIP session, associating the new SIP session with the mid-dialog SIP message, identifying an application that is associated with the mid-dialog SIP message, providing to the application the mid-dialog SIP message in the context of the new SIP session, receiving an acknowledgement from the application that the application will accept the mid-dialog SIP message, and responsive to receiving the acknowledgement, providing to the application the mid-dialog SIP message in the context of the new SIP session.

Abstract: Processing mid-dialog SIP messages by receiving a mid-dialog SIP message from a SIP user agent client, creating a new SIP session, associating the new SIP session with the mid-dialog SIP message, identifying an application that is associated with the mid-dialog SIP message, providing to the application the mid-dialog SIP message in the context of the new SIP session, receiving an acknowledgement from the application that the application will accept the mid-dialog SIP message, and responsive to receiving the acknowledgement, providing to the application the mid-dialog SIP message in the context of the new SIP session.

Abstract: An approach to secure API access for distinct types of users. A request for access to an API from a user is initiated and followed by sending a request for a login credential to the user based on a type of API requested: Data API or Interaction API. The login credential is received along with the network location of the user. Authenticating the login credential and create an API specific token. Assigning the API specific token to a user activity and granting the user access to the specific API.

Abstract: An approach is provided in which an information handling system sends a first request to a user over a voice channel through a first communication network. The request is in an audio format and requests a user data set from the user. The information handling system establishes a messaging channel with a user device utilized by the user through a second communication network. The messaging channel is an end-to-end digital data channel between the information handing system and the user device. The information handling system receives a set of user data corresponding to the first request from the user device over the messaging channel, and sends the set of user data to a conversation system.

Abstract: An approach is provided in which an information handling system sends a request in audio format to a user over a voice channel requesting a user data set. The information handling system receives utterances from the user over the voice channel and determines that the utterances do not provide enough information to complete the requested user data set. In turn, the information handling system establishes a messaging channel with the user and sends a request in digital format to the user over the messaging channel to provide additional data to complete the user data set.

Abstract: Processing mid-dialog SIP messages by receiving a mid-dialog SIP message from a SIP user agent client, creating a new SIP session, associating the new SIP session with the mid-dialog SIP message, identifying an application that is associated with the mid-dialog SIP message, providing to the application the mid-dialog SIP message in the context of the new SIP session, receiving an acknowledgement from the application that the application will accept the mid-dialog SIP message, and responsive to receiving the acknowledgement, providing to the application the mid-dialog SIP message in the context of the new SIP session.

Abstract: A method for third-party authorization is presented. A client request is received by a resource server in a computer system from a client, wherein the client request includes an access token. An introspection request for the access token based on the client request. The introspection gateway uses a third-party authorization server from a plurality of third-party authorization servers to handle the introspection request. A resource server response is received from the introspection gateway, wherein the resource server response identifies a set of scopes for the access token. A determination is made as to whether the access token has sufficient scope from the resource server response. In response to the access token having the sufficient scope, the client is granted access to the resource server.

Abstract: An approach is provided in which an information handling system sends a request in audio format to a user over a voice channel requesting a user data set. The information handling system receives utterances from the user over the voice channel and determines that the utterances do not provide enough information to complete the requested user data set. In turn, the information handling system establishes a messaging channel with the user and sends a request in digital format to the user over the messaging channel to provide additional data to complete the user data set.

Abstract: A method for third-party authorization is presented. A client request is received by a resource server in a computer system from a client, wherein the client request includes an access token. An introspection request for the access token based on the client request. The introspection gateway uses a third-party authorization server from a plurality of third-party authorization servers to handle the introspection request. A resource server response is received from the introspection gateway, wherein the resource server response identifies a set of scopes for the access token. A determination is made as to whether the access token has sufficient scope from the resource server response. In response to the access token having the sufficient scope, the client is granted access to the resource server.

Abstract: An approach is provided in which an information handling system sends a request in audio format to a user over a voice channel requesting a user data set. The information handling system receives utterances from the user over the voice channel and determines that the utterances do not provide enough information to complete the requested user data set. In turn, the information handling system establishes a messaging channel with the user and sends a request in digital format to the user over the messaging channel to provide additional data to complete the user data set.

Abstract: An approach is provided in which an information handling system sends a request in audio format to a user over a voice channel requesting a user data set. The information handling system receives utterances from the user over the voice channel and determines that the utterances do not provide enough information to complete the requested user data set. In turn, the information handling system establishes a messaging channel with the user and sends a request in digital format to the user over the messaging channel to provide additional data to complete the user data set.

Abstract: Processing mid-dialog SIP messages by receiving a mid-dialog SIP message from a SIP user agent client, creating a new SIP session, associating the new SIP session with the mid-dialog SIP message, identifying an application that is associated with the mid-dialog SIP message, providing to the application the mid-dialog SIP message in the context of the new SIP session, receiving an acknowledgement from the application that the application will accept the mid-dialog SIP message, and responsive to receiving the acknowledgement, providing to the application the mid-dialog SIP message in the context of the new SIP session.

Abstract: In some examples, a system for conference management can include a processor to initiate a conference comprising a plurality of cameras and at least one user and process a series of images with at least one service to generate service output, the series of images comprising an aggregation of images from the plurality of cameras. The processor can also detect metadata associated with each of the series of images by the at least one service and aggregate the metadata and the service output based on a timestamp for each image to detect an event. Furthermore, the processor can generate an alarm in response to detecting the event and modify the conference by adding additional cameras or additional users.

Abstract: In some examples, a system for conference management can include a processor to initiate a conference comprising a plurality of cameras and at least one user and process a series of images with at least one service to generate service output, the series of images comprising an aggregation of images from the plurality of cameras. The processor can also detect metadata associated with each of the series of images by the at least one service and aggregate the metadata and the service output based on a timestamp for each image to detect an event. Furthermore, the processor can generate an alarm in response to detecting the event and modify the conference by adding additional cameras or additional users.

Abstract: Processing mid-dialog SIP messages by receiving a mid-dialog SIP message from a SIP user agent client, creating a new SIP session, associating the new SIP session with the mid-dialog SIP message, identifying an application that is associated with the mid-dialog SIP message, providing to the application the mid-dialog SIP message in the context of the new SIP session, receiving an acknowledgement from the application that the application will accept the mid-dialog SIP message, and responsive to receiving the acknowledgement, providing to the application the mid-dialog SIP message in the context of the new SIP session.

Abstract: A system for maintaining SIP application session affinity, the system including a destination inspector configured to inspect a SIP request to determine whether the SIP request indicates as its destination a logical name of a SIP container, a request router configured to route the SIP request to the SIP container that is identified by the logical name if the SIP request indicates as its destination the logical name of the SIP container, and a destination assignor configured to assign the SIP request to a SIP container in accordance with a predefined assignment protocol if the SIP request does not indicate as its destination the logical name of a SIP container.