Abstract: Methods and systems are provided for remotely logging out one or more registered communication devices associated with a common extension through a requesting communication device in the registered communication devices. The requesting communication device renders a list of registered communication devices associated with the extension of a user to a display. The user of the requesting communication device selects at least one of the registered communication devices, by a touch input at the display, to unregister the at least one registered communication device from the extension. In response, a message is automatically sent from the requesting communication device to a server to update the registration status of the selected at least one registered communication device. The server then terminates the registration of the at least one registered communication device from the extension associated with the user restricting the at least one registered communication device from accessing the extension.

Abstract: Methods and systems are provided for remotely logging out one or more registered communication devices associated with a common extension through a requesting communication device in the registered communication devices. The requesting communication device renders a list of registered communication devices associated with the extension of a user to a display. The user of the requesting communication device selects at least one of the registered communication devices, by a touch input at the display, to unregister the at least one registered communication device from the extension. In response, a message is automatically sent from the requesting communication device to a server to update the registration status of the selected at least one registered communication device. The server then terminates the registration of the at least one registered communication device from the extension associated with the user restricting the at least one registered communication device from accessing the extension.

Abstract: In order to deal with multiple communication endpoints that use a single address of record (e.g., a telephone number), a list of friendly names is determined for the multiple communication endpoints. The friendly names identify individual communication endpoints. For example, a friendly name may be “Joe's Desktop.” When a Computer Telephone Integration (CTI) application is associated with a communication session, the list of friendly names is presented to a user. The user selects one of the friendly names. This results in a message being sent that indicates a communication endpoint associated with the selected friendly name. The message with the friendly name causes a new communication session to be automatically initiated from a communication endpoint associated with the selected friendly name or an answer of a forked communication session with the communication endpoint associated with the selected friendly name.

Abstract: When a first SIP INVITE is received a Session Border Controller (SBC) to establish a communication session between communication devices, a second SIP INVITE message is also sent by the SBC to a media recorder without a media line or a media attribute set to inactive. The second SIP INVITE message without the media line or the media attribute set to inactive indicates that there is currently no media associated with the communication session to the media recorder. The SBC receives one of a SIP PUBLISH message or a SIP NOTIFY message that indicates whether to start or stop recording the voice or video communication session. The SBC sends or does not send a media stream of the communication session between the communication devices based on whether the SIP PUBLISH or the SIP NOTIFY indicates whether to start or stop recording the voice or video communication session.

Abstract: In order to deal with multiple communication endpoints that use a single address of record (e.g., a telephone number), a list of friendly names is determined for the multiple communication endpoints. The friendly names identify individual communication endpoints. For example, a friendly name may be “Joe's Desktop.” When a Computer Telephone Integration (CTI) application is associated with a communication session, the list of friendly names is presented to a user. The user selects one of the friendly names. This results in a message being sent that indicates a communication endpoint associated with the selected friendly name. The message with the friendly name causes a new communication session to be automatically initiated from a communication endpoint associated with the selected friendly name or an answer of a forked communication session with the communication endpoint associated with the selected friendly name.

Abstract: Disclosed herein are systems, methods, and software to provide enhanced communication logs to user systems in a conferenced communication. In one example, a method of providing enhanced communication logs includes initiating a communication between at least two end user systems, and obtaining communication state information for the at least two end user systems. The method further provides extending the communication to a third end user system, and obtaining supplementary communication state information for the third end user system. The method also includes providing communication details to the end user systems of the communication based on the communication state information and the supplementary communication state information.

Abstract: Disclosed herein are systems, methods, and software to provide enhanced communication logs to user systems in a conferenced communication. In one example, a method of providing enhanced communication logs includes initiating a communication between at least two end user systems, and obtaining communication state information for the at least two end user systems. The method further provides extending the communication to a third end user system, and obtaining supplementary communication state information for the third end user system. The method also includes providing communication details to the end user systems of the communication based on the communication state information and the supplementary communication state information.

Abstract: Placing a call on hold provides advantages to the party initiating the hold. The party may engage in another call or perform another action and return to the call when convenient, provided the party placed on hold is still on the call. The party on hold monitors the inactive call and waits until the call is reactivated. The party on hold is provided with a means to alert the other party via a session initiation protocol (SIP) message formatted as a ring-ping message. The message is sent to the party who placed the call on hold and the user's device activates an indicator, such as to alert the holding party that the held party wishes to re-engage the call. If the holding party does not un-hold the call or otherwise acknowledge the ring-ping indicator, another action can be initiated, such as by inviting another party to join the call.

Abstract: When a first SIP INVITE is received a Session Border Controller (SBC) to establish a communication session between communication devices, a second SIP INVITE message is also sent by the SBC to a media recorder without a media line or a media attribute set to inactive. The second SIP INVITE message without the media line or the media attribute set to inactive indicates that there is currently no media associated with the communication session to the media recorder. The SBC receives one of a SIP PUBLISH message or a SIP NOTIFY message that indicates whether to start or stop recording the voice or video communication session. The SBC sends or does not send a media stream of the communication session between the communication devices based on whether the SIP PUBLISH or the SIP NOTIFY indicates whether to start or stop recording the voice or video communication session.

Abstract: Placing a call on hold provides advantages to the party initiating the hold. The party may engage in another call or perform another action and return to the call when convenient, provided the party placed on hold is still on the call. The party on hold monitors the inactive call and waits until the call is reactivated. The party on hold is provided with a means to alert the other party via a session initiation protocol (SIP) message formatted as a ring-ping message. The message is sent to the party who placed the call on hold and the user's device activates an indicator, such as to alert the holding party that the held party wishes to re-engage the call. If the holding party does not un-hold the call or otherwise acknowledge the ring-ping indicator, another action can be initiated, such as by inviting another party to join the call.