A method, a system, and a computer program product for determining whether signals are received by one or more devices in a virtual meeting. The method includes transmitting a data stream received from one or more host computing devices to one or more user computing devices in a plurality of user computing devices. The host and user computing devices are communicatively coupled using a real-time online connection. A first hash in a plurality of hashes is generated by the server using a portion of the data stream and stored in a memory location. The first hash is compared to a second hash received from the user computing devices. The second hash is generated by the user computing devices upon receipt of the transmitted data stream. Based on the comparison, a status of the real-time online connection between the host computing devices and the user computing devices is determined.

The present technology relates to an information processing device, an information processing method, and a program that enable appropriate extraction of an ALP packet from a packet of a second packet included in a first packet regardless of a difference in interpretation of a standard.

A payload length obtained on the basis of data of a header of a second packet included in a first packet is corrected.

Techniques are provided for a coordinated microservice system including a coordinator and multiple services, which interact with each other. Each of the services can have multiple execution instances, which run independently of each other. In operation, the current status of each instance is evaluated against one or more rules to determine whether the current status changes the topography of the services and updating the topography based on the changes. An execution plan is created for executing a command based on one or more predefined rules and the updated topography, where the execution plan includes one or more steps for executing the command on each instance of the service. The execution plan is executed on each instance of the service in accordance with the one or more predefined rules.

Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

The invention enables high-availability, high-scale, high security and disaster recovery for API computing, including in terms of capture of data traffic passing through proxies, routing communications between clients and servers, and load balancing and/or forwarding functions. The invention inter alia provides (i) a scalable cluster of proxies configured to route communications between clients and servers, without any single point of failure, (ii) proxy nodes configured for implementing the scalable cluster (iii) efficient methods of configuring the proxy cluster, (iv) natural resiliency of clusters and/or proxy nodes within a cluster, (v) methods for scaling of clusters, (vi) configurability of clusters to span multiple servers, multiple racks and multiple datacenters, thereby ensuring high availability and disaster recovery (vii) switching between proxies or between servers without loss of session.

The invention enables high-availability, high-scale, high security and disaster recovery for API computing, including in terms of capture of data traffic passing through proxies, routing communications between clients and servers, and load balancing and/or forwarding functions. The invention inter alia provides (i) a scalable cluster of proxies configured to route communications between clients and servers, without any single point of failure, (ii) proxy nodes configured for implementing the scalable cluster (iii) efficient methods of configuring the proxy cluster, (iv) natural resiliency of clusters and/or proxy nodes within a cluster, (v) methods for scaling of clusters, (vi) configurability of clusters to span multiple servers, multiple racks and multiple datacenters, thereby ensuring high availability and disaster recovery (vii) switching between proxies or between servers without loss of session.

A method, computer program, and computer system is provided for asynchronous Network-Based Media Processing (NBMP) request processing. A first function call corresponding to a CreateWorkflow request to an NBMP workflow manager is received. A hypertext transfer protocol (HTTP) status code and a delay value retrieved from a database are returned based on receiving the first function call, and the CreateWorkflow request is performed at a later time after the delay has elapsed, whereby a response to the request is performed asynchronously according to the retrieved delay value. A second function call corresponding to an UpdateWorkflow request to the NBMP workflow manager is received after performing the CreateWorkflow request, and results of performing the CreateWorkflow request are returned based on receiving the second function call, wherein a response to the CreateWorkflow request is provided asynchronously according to the retrieved delay value.

Described herein are techniques, devices, and systems for handling Session Initiation Protocol (SIP) messages with malformed header fields. A communication device that receives a SIP message from an additional communication device may identify one or more identified header fields of a plurality of first header fields in a message header of the SIP message that correspond to (e.g., match) one or more second header fields in a list of second header fields accessible to the communication device. If the communication device determines that the one or more identified header fields are not malformed, the communication device may process the SIP message without regard to remaining header fields in the message header. If, however, the communication device determines that at least one identified header field of the one or more identified header fields is malformed, the communication device may reject the SIP message.

Described herein are techniques, devices, and systems for handling Session Initiation Protocol (SIP) messages with malformed header fields. A communication device that receives a SIP message from an additional communication device may identify one or more identified header fields of a plurality of first header fields in a message header of the SIP message that correspond to (e.g., match) one or more second header fields in a list of second header fields accessible to the communication device. If the communication device determines that the one or more identified header fields are not malformed, the communication device may process the SIP message without regard to remaining header fields in the message header. If, however, the communication device determines that at least one identified header field of the one or more identified header fields is malformed, the communication device may reject the SIP message.

Described is an improved approach to implement fast detection of node death. Instead of just relying on multiple heart beats to fail in order to determine whether a node is dead, the present approach performs an on demand validation using RDMA to determine whether the node is reachable, where the approach of using RDMA is significantly faster than the heartbeat approach.