Abstract: Techniques for determining a global state for multiple related calls are disclosed. A first call between a first device and a second device is established, where the first call is assigned a user call identifier. A second call between the first device and a third device is established. A shared call operation is established by assigning the user call identifier to the second call. The user call identifier is assigned to the second call in addition to already being assigned to the first call. A first status of the first call and a second status of the second call are determined. The first status and the second status are used to determine a global state of the shared call operation. The global state of the shared call operation is updated in response to one or both of the first status or the second status changing.

Abstract: Techniques for determining a global state for multiple related calls are disclosed. A first call between a first device and a second device is established, where the first call is assigned a user call identifier. A second call between the first device and a third device is established. A shared call operation is established by assigning the user call identifier to the second call. The user call identifier is assigned to the second call in addition to already being assigned to the first call. A first status of the first call and a second status of the second call are determined. The first status and the second status are used to determine a global state of the shared call operation. The global state of the shared call operation is updated in response to one or both of the first status or the second status changing.

Abstract: Handling a related call using a shared call state. The computing system establishes a first call between a first entity and a second entity, assigns a user call identifier to the first call. Next, the second entity instructs that a second call between the first entity and a third entity is to be established. The computing system then establishes the second call between the first entity and the third entity, assigns the same user identifier to the second call, such that the first call and the second call are included in a shared call operation. A first global state of the shared call operation is identified based on a status of at least one of the first call and the second call. When the status of at least one of the first call and the second call changes, the global state of the shared call operation changes from the first global state to a second global state.

Abstract: Handling a related call using a shared call state. The computing system establishes a first call between a first entity and a second entity, assigns a user call identifier to the first call. Next, the second entity instructs that a second call between the first entity and a third entity is to be established. The computing system then establishes the second call between the first entity and the third entity, assigns the same user identifier to the second call, such that the first call and the second call are included in a shared call operation. A first global state of the shared call operation is identified based on a status of at least one of the first call and the second call. When the status of at least one of the first call and the second call changes, the global state of the shared call operation changes from the first global state to a second global state.

Abstract: Disclosed are systems, methods, and non-transitory computer-readable media for delivering content to a client device placed on hold. A communication system establishes a communication session between a client device placed on hold and a content delivery service, during which the content delivery service streams content to the client device via the established communication session. The communication session between the client device that initiated the hold and the client devices that are placed on hold is terminated, thereby allowing the client device that initiated the hold to establish communication sessions other client devices if so desired. A unique identifier generated to reference the hold is provided to the client device that initiated the hold, which the client device may then use to reference the hold to execute a desired action, such as ending the hold, terminating the communication session, retrieving a status of the hold, etc.

Abstract: In general, techniques are described for a batch configuration mode for configuring network devices. A network device comprising a committed data source and a control unit may implement the techniques. The control unit may receive a plurality of separate commit commands instructing the network device to commit configuration changes to the committed data source. Each of the plurality of commit commands instructs the network device to commit an associated portion of the configuration changes to the committed data source. The control unit then groups two or more of the plurality of separate commit commands to form a batch of commit commands and executes the batch of commit commands to commit the portions of the configuration changes associated with the grouped commit commands to the committed data source as if the grouped portions of the configuration changes were associated with a single commit command.

Abstract: A multi-chassis router allows an administrator to install software from a single user interface. The multi-chassis router automatically forwards the software to each chassis within the multi-chassis router when given a single command to install the software from an administrator. The multi-chassis router also automatically validates the software on each chassis. After reporting the results of the validations, the multi-chassis router may wait for the administrator to issue a commit command before committing each chassis within the multi-chassis router to the software. Alternatively, in response to a failed validation or for other reason, an administrator can issue a single ROLLBACK command. This allows each chassis within the multi-chassis router to have the same software during all stages of a software installation and ensures software on each chassis is compatible with software on every other chassis.

Abstract: A network device may include logic configured to invoke proactive programs based on the expiration of a long time period within the network device, wherein the proactive programs collect data relating to operations of the network device, invoke reactive programs based on the detection of at least one of an event or expiration of a short time period, wherein the reactive programs collect, correlate and analyze data relating to the detected event or expiration of a short time period, determine a corrective action based on collected and analyzed data, and perform the determined corrective action within the network device.

Abstract: A multi-chassis router allows an administrator to install software from a single user interface. The multi-chassis router automatically forwards the software to each chassis within the multi-chassis router when given a single command to install the software from an administrator. The multi-chassis router also automatically validates the software on each chassis. After reporting the results of the validations, the multi-chassis router may wait for the administrator to issue a commit command before committing each chassis within the multi-chassis router to the software. Alternatively, in response to a failed validation or for other reason, an administrator can issue a single ROLLBACK command. This allows each chassis within the multi-chassis router to have the same software during all stages of a software installation and ensures software on each chassis is compatible with software on every other chassis.

Abstract: A multi-chassis router allows an administrator to distribute configuration data from a single user interface. Additionally, the multi-chassis router presents a software image consistent with that of a standalone router and uses configuration data syntax that is consistent with that of a standalone router. The multi-chassis router automatically distributes and validates relevant configuration data at each chassis within the multi-chassis router. In effect, an administrator does not need to account for the multiple chassis configuration, and an administrator familiar with the configuration data syntax for a standalone router can use that knowledge to configure the multi-chassis router.

Abstract: A network device may include logic configured to detect that an event has occurred in the network device, determine an XML document structure based on the detected event, and generate an XML document with the determined structure including information relating to the detected event.

Abstract: A network device may include logic configured to detect that an event has occurred in the network device, determine an XML document structure based on the detected event, and generate an XML document with the determined structure including information relating to the detected event.

Abstract: A network device may include logic configured to detect that an event has occurred in the network device, determine an XML document structure based on the detected event, and generate an XML document with the determined structure including information relating to the detected event.

Abstract: A multi-chassis router allows an administrator to install software from a single user interface. The multi-chassis router automatically forwards the software to each chassis within the multi-chassis router when given a single command to install the software from an administrator. The multi-chassis router also automatically validates the software on each chassis. This allows each chassis within the multi-chassis router to have the same software during all stages of a software installation and ensures software on each chassis is compatible with software on every other chassis. In effect, an administrator does not need to account for the multiple chassis configuration, and an administrator familiar with software installation on a standalone router can use that knowledge to install software on the multi-chassis router.

Abstract: A network device may include logic configured to detect that an event has occurred in the network device, determine an XML document structure based on the detected event, and generate an XML document with the determined structure including information relating to the detected event.

Abstract: A network device may include logic configured to invoke proactive programs based on the expiration of a long time period within the network device, wherein the proactive programs collect data relating to operations of the network device, invoke reactive programs based on the detection of at least one of an event or expiration of a short time period, wherein the reactive programs collect, correlate and analyze data relating to the detected event or expiration of a short time period, determine a corrective action based on collected and analyzed data, and perform the determined corrective action within the network device.