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: To provide better administrative access control for allowing access to network applications, an authorization framework is extended by dynamically adding administrative access control to the authorization framework. For example, the authorization framework can be extended by adding a plug-in to the authorization framework. The authorization framework manages the access control by generating tokens. For example, a token may be a digital certificate. The tokens define what access control an application, such as a client application has when accessing the network application. The tokens are based on the dynamically added administrative access control. When a request for a token is securely received, the authorization framework generates a token that identifies if the application (e.g., the client application) is allowed or not allowed to access the network application. The token is then used by the application to access the network application.

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: An indication of a change in a right to use a service or feature is received. For example, this can be based on an administrator granting access to a previously installed service or feature. In response, a notification is sent to a user of the change of the right to use the service or feature. The notification requests the user to provide a credential to approve the change of the right to use the service or feature. For example, a link may be provided in an email or text message that the user can click on to provide a password/user name. The credential is received and verified. In response to validating the credential, access is allowed according to the change of the right to use the service or feature. The user then has access to the service/feature without the administrator having to know the user's credential.

Abstract: An indication of a change in a right to use a service or feature is received. For example, this can be based on an administrator granting access to a previously installed service or feature. In response, a notification is sent to a user of the change of the right to use the service or feature. The notification requests the user to provide a credential to approve the change of the right to use the service or feature. For example, a link may be provided in an email or text message that the user can click on to provide a password/user name. The credential is received and verified. In response to validating the credential, access is allowed according to the change of the right to use the service or feature. The user then has access to the service/feature without the administrator having to know the user's credential.

Abstract: To provide better administrative access control for allowing access to network applications, an authorization framework is extended by dynamically adding administrative access control to the authorization framework. For example, the authorization framework can be extended by adding a plug-in to the authorization framework. The authorization framework manages the access control by generating tokens. For example, a token may be a digital certificate. The tokens define what access control an application, such as a client application has when accessing the network application. The tokens are based on the dynamically added administrative access control. When a request for a token is securely received, the authorization framework generates a token that identifies if the application (e.g., the client application) is allowed or not allowed to access the network application. The token is then used by the application to access the network application.

Abstract: An application compositor enables the creation a sequence of SIP and HTTP servlets that comprises a converged multi-protocol application. Applications are constructed based on rules that declaratively specify a multi-protocol sequence of servlets and the transitions between the servlets, minimizing programmer effort. The application compositor works with a servlet container within an application server to determine the sequence of servlets to be executed by the servlet container when running the application, and is called by the servlet container to perform transitions between servlets.

Abstract: System and method to revoke call-back requests, the method including: transmitting a plurality of communication requests from a caller to one or more callees; determining mootness of a request for a call-back from at least some of the callees; initiating, by use of a single command, a plurality of call-back cancellation requests to the at least some of the callees; and transmitting one or more call-back cancellation requests to the at least some of the callees. The method may further include determining a characteristic shared by the communication requests to the at least some of the callees. Determining a characteristic may include determining subject matter from message content, metadata, or sending time of the communication requests. The request for a call-back is determined by the caller or inferred by a callee. Call-back cancellation may include removal of a call indication from a notification list of the callee.

Abstract: System and method to revoke call-back requests, the method including: transmitting a plurality of communication requests from a caller to one or more callees; determining mootness of a request for a call-back from at least some of the callees; initiating, by use of a single command, a plurality of call-back cancellation requests to the at least some of the callees; and transmitting one or more call-back cancellation requests to the at least some of the callees. The method may further include determining a characteristic shared by the communication requests to the at least some of the callees. Determining a characteristic may include determining subject matter from message content, metadata, or sending time of the communication requests. The request for a call-back is determined by the caller or inferred by a callee. Call-back cancellation may include removal of a call indication from a notification list of the callee.

Abstract: The present invention provides methods, devices, and systems for facilitating an ad-hoc conference. More specifically, a “join-us” concept is employed that links functionality in non-real-time messaging systems with real-time ongoing state of calls information in a communications network. This combines the spontaneity and security of an ad-hoc conference call with the join-as-you-can nature of messaging and reservation of conference bridges.

Abstract: An application compositor enables the creation a sequence of SIP and HTTP servlets that comprises a converged multi-protocol application. Applications are constructed based on rules that declaratively specify a multi-protocol sequence of servlets and the transitions between the servlets, minimizing programmer effort. The application compositor works with a servlet container within an application server to determine the sequence of servlets to be executed by the servlet container when running the application, and is called by the servlet container to perform transitions between servlets.

Abstract: A proxy server causes an authentication authority to authenticate a client in response to a first Session Initiation Protocol (SIP) request of the client on a connection. It does not cause the client to be authenticated in response subsequent requests on the connection as long as the underlying connection is not broken, the subsequent requests are on behalf of the same client, the client has not been removed from the system, the client's password has not changed, a “safety net” timer has not expired, or any other policy that the server chooses to enforce. This eliminates the overhead of constant re-authentication in response to each SIP request.

Abstract: Methods, devices, and systems for smart load balancing are provided. SIP Requests destined for a particular AOR are delivered to one of several registered contact addresses according to associated availability score stored in routing element's contact resolution table. The availability score is periodically updated by the contact entity itself using the SIP PUBLISH mechanism to push the score to the routing element.

Abstract: Provided are methods, devices, and systems for maintaining a SIP survivable network. The present invention is adapted to allow SIP endpoints or User Agents to discover and select the controller or controllers that the SIP endpoint will register with. Selection of the controller or controllers may be based upon the relative attributes of the controllers and the needs of the SIP endpoint.

Abstract: Provided are methods, devices, and systems for maintaining a SIP survivable User Agent. The present invention is adapted to allow the User Agent to detect the status of the network, thus providing the User Agent to perform failover/failback operations. The User Agent may be adapted to determine the status of the network based on its own monitoring mechanisms and/or based on messages received from other network components.

Abstract: Methods, systems, and devices are provided that propose allocating bandwidth in a distributed network. According to a decentralized mode of operation, bandwidth between network devices is cooperatively shared and managed, allowing one or more call processing modules to selectively and intelligently place calls or perform activities. A single authoritative mode of operation for a given communication link is also provided, wherein one or more network devices may consult an authoritative member to determine if sufficient bandwidth is available to support an activity. Various triggering events or conditions may facilitate the transition from one mode to another. Audits or accountings are conducted, wherein devices may update or synchronize information stored in a control table related to system bandwidth.

Abstract: Provided are methods, devices, and systems for maintaining a SIP survivable network. The present invention may utilize messages, such as SIP NOTIFY messages, to trigger various network components to failover and failback based on the determined status of the SIP network.

Abstract: Methods, systems, and devices are provided that propose allocating bandwidth in a distributed network. According to a decentralized mode of operation, bandwidth between network devices is cooperatively shared and managed, allowing one or more call processing modules to selectively and intelligently place calls or perform activities. A single authoritative mode of operation for a given communication link is also provided, wherein one or more network devices may consult an authoritative member to determine if sufficient bandwidth is available to support an activity. Various triggering events or conditions may facilitate the transition from one mode to another. Audits or accountings are conducted, wherein devices may update or synchronize information stored in a control table related to system bandwidth.

Abstract: The present invention provides methods, devices, and systems for facilitating an ad-hoc conference. More specifically, a “join-us” concept is employed that links functionality in non-real-time messaging systems with real-time ongoing state of calls information in a communications network. This combines the spontaneity and security of an ad-hoc conference call with the join-as-you-can nature of messaging and reservation of conference bridges.

Abstract: A proxy server causes an authentication authority to authenticate a client in response to a first Session Initiation Protocol (SIP) request of the client on a connection. It does not cause the client to be authenticated in response subsequent requests on the connection as long as the underlying connection is not broken, the subsequent requests are on behalf of the same client, the client has not been removed from the system, the client's password has not changed, a “safety net” timer has not expired, or any other policy that the server chooses to enforce. This eliminates the overhead of constant re-authentication in response to each SIP request.