One example involves a communications server providing communications services to remotely-situated client entities, wherein each client entity is associated with users and each user is associated with a communication device. The server may verify a first authentication factor for a user among the users, and generate a communication request that includes a first portion specifying at least one target endpoint associated with the user and a second portion associated with or indicating the security code and that includes a set of instructions which: are specific to the user, which specify how to communicate the security code for the user, and which specify different security codes for different types of communications. Via the server, the security code is sent to the user according to the set of instructions, and verified via a second authentication factor associated with or for the user by comparing input from the user to the security code.

One example involves a communications server providing communications services to remotely-situated client entities, wherein each client entity is associated with users and each user is associated with a communication device. The server may verify a first authentication factor for a user among the users, and generate a communication request that includes a first portion specifying at least one target endpoint associated with the user and a second portion associated with or indicating the security code and that includes a set of instructions which: are specific to the user, which specify how to communicate the security code for the user, and which specify different security codes for different types of communications. Via the server, the security code is sent to the user according to the set of instructions, and verified via a second authentication factor associated with or for the user by comparing input from the user to the security code.

In an example embodiment, a solution is provided that introduces a second level IVR component controlled by a call control service that also controls a first IVR component. Controlling the IVR components using this call control service (which also interfaces with client software operated by a human agent) allows for data collected during the IVR sessions or during a live session with the human agent to be shared among the components. This also acts to eliminate the need for a traditional “transfer” of a call from a human agent to an IVR or vice versa, which would often be accompanied by audible clicks or beeps discernable to the caller.

During a Session Initiation Protocol dialog setup, a media gateway or container executes or initiates two or more applications that provide features during a conference call. The applications are applied to messages or data in the conference call based on a sequence order established during the setup of the conference call. The sequence order and the application identities are stored in a shared database. When a failure occurs during the conference call, the applications are reestablished in the reconstructed or reestablished conference call. The application reconstruction includes reinitiating the applications with the same sequence as previously established before the failure. As such, the user has the same features applied in the same way before and after the failure, which improves the systems performance and expected operation.

During a Session Initiation Protocol dialog setup, a media gateway or container executes or initiates two or more applications that provide features during a conference call. The applications are applied to messages or data in the conference call based on a sequence order established during the setup of the conference call. The sequence order and the application identities are stored in a shared database. When a failure occurs during the conference call, the applications are reestablished in the reconstructed or reestablished conference call. The application reconstruction includes reinitiating the applications with the same sequence as previously established before the failure. As such, the user has the same features applied in the same way before and after the failure, which improves the systems performance and expected operation.

Described herein are techniques, devices, and systems for using an application server (AS) to trigger home subscriber server (HSS)-based proxy call session control function (P-CSCF) restoration for a user equipment (UE) in order to restore service to the UE via an in-service P-CSCF node. For example, an AS is configured to receive, from a serving CSCF (S-CSCF) node, an indication that a P-CSCF node assigned to a UE is unavailable, and, in response, the AS is configured to send, to a HSS, a request to initiate P-CSCF restoration for the UE. In turn, the HSS or a Unified Data Management (UDM) node is configured to send, to a control node, an indication to perform the P-CSCF restoration for the UE. The disclosed AS-triggered, HSS-based P-CSCF restoration procedure restores service to the UE.

In a telecommunication system comprising multiple switching nodes (10, 20, 30) having a respective local server (C1, C2, C3) and associated terminals (D1, D2, D3, D4) located within a network and a central DSS server (DSS) for controlling the telecommunication system by using a general switching protocol, the terminals (D1, D2, D3, D4) of a switching node (10, 20, 30) are controlled by the local server (C1, C2, C3) under a local protocol comprising control commands for node-internal call pickup. The pickup of a call directed from a third terminal (D4) to a first terminal (D3) assigned to a first switching node (10) through a second terminal (D1) assigned to another, second switching node (20) occurs across nodes by using the general switching protocol through transferring the control commands provided in the local protocol for call pickup to the general switching protocol and providing them across nodes through the central DSS server (DSS) to the multiple switching nodes (10, 20, 30) located within the network, and converting the registration of a terminal (D1, D2, D3, D4) for call pickup provided in the local protocol to the general switching protocol and forwarding it to the central DSS server.

In a telecommunication system comprising multiple switching nodes (10, 20, 30) having a respective local server (C1, C2, C3) and associated terminals (D1, D2, D3, D4) located within a network and a central DSS server (DSS) for controlling the telecommunication system by using a general switching protocol, the terminals (D1, D2, D3, D4) of a switching node (10, 20, 30) are controlled by the local server (C1, C2, C3) under a local protocol comprising control commands for node-internal call pickup. The pickup of a call directed from a third terminal (D4) to a first terminal (D3) assigned to a first switching node (10) through a second terminal (D1) assigned to another, second switching node (20) occurs across nodes by using the general switching protocol through transferring the control commands provided in the local protocol for call pickup to the general switching protocol and providing them across nodes through the central DSS server (DSS) to the multiple switching nodes (10, 20, 30) located within the network, and converting the registration of a terminal (D1, D2, D3, D4) for call pickup provided in the local protocol to the general switching protocol and forwarding it to the central DSS server.

A gateway device includes a call handling equipment (CHE) listener interface, an Internet Protocol (IP) interface, a provisioning engine, and a message parsing engine. The CPE listener interface forms a communication channel with a CHE and receives call event data from the CHE. The IP interface communicates with a cloud-based processing system. The provisioning engine receives, from the cloud-based processing system via the IP interface, instructions for parsing data from a data output format of the CHE into a consistent data format of the cloud-based processing system. The message parsing engine parses the call event data received from the CHE via the CHE listener interface, and formats the call event data according to the consistent data format. The gateway device transmits the formatted call event data to the cloud-based processing system via the IP interface.

A gateway device includes a call handling equipment (CHE) listener interface, an Internet Protocol (IP) interface, a provisioning engine, and a message parsing engine. The CPE listener interface forms a communication channel with a CHE and receives call event data from the CHE. The IP interface communicates with a cloud-based processing system. The provisioning engine receives, from the cloud-based processing system via the IP interface, instructions for parsing data from a data output format of the CHE into a consistent data format of the cloud-based processing system. The message parsing engine parses the call event data received from the CHE via the CHE listener interface, and formats the call event data according to the consistent data format. The gateway device transmits the formatted call event data to the cloud-based processing system via the IP interface.