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 creating and using a trusted host list for Transport Layer Security (TLS) sessions are provided. The proposed solutions described herein provide a mechanism of specifying authorization policy for TLS sessions where such authorization was traditionally implied by the possession of a certificate issued by a mutually trusted third party. The proposed solutions also provide for wildcard use and regular expression matching to simplify administration of the trusted host list.

Abstract: Methods, devices, and systems are provided for marking one or more entities of a call as internal/external such that certain call features can be invoked by servers and other devices residing behind a gateway. More specifically, entities of a call can be marked as internal/external based employing an assessment algorithm to determine whether the calling endpoint is an internal or external endpoint and/or whether a user of the calling or answering endpoint is an internal or external user. Once this determination is made, the call can be marked accordingly such that the appropriate features can be invoked.

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: 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, devices, and systems are provided for marking one or more entities of a call as internal/external such that certain call features can be invoked by servers and other devices residing behind a gateway. More specifically, entities of a call can be marked as internal/external based employing an assessment algorithm to determine whether the calling endpoint is an internal or external endpoint and/or whether a user of the calling or answering endpoint is an internal or external user. Once this determination is made, the call can be marked accordingly such that the appropriate features can be invoked.

Abstract: Methods, devices, and systems for controlling access to a password protected resource are provided. More specifically, different communication profiles can be mapped to a single user and that user can utilize a single password to gain access to the password protected resource using any one of his/her communication profiles. Each communication profile may have a unique authentication value associated therewith, but each unique authentication value may be determined based on the single password, thereby eliminating the need for a user to remember multiple passwords for each of his/her communication profiles.

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: 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: 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: 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: The present invention is directed to an architecture 200 for setting up a communication between first and second communication devices 216 and 220, the first communication device 216 corresponding to a first directing server 224 and first communication manager 204 separate from the first directing server 224, comprising a contact servicing agent 244 operable to (a) receive a call set up message at least one of addressed to and originated by the first communication device 216; (b) determine that the first communication device 216 has a corresponding first communication manager 204; (c) forward the call set up message to the first communication manager 204 and request the first communication manager 204 to perform at least one of call originating and terminating processing; and (d) rout the call set up message to a destination referenced in the call set up message.

Abstract: The present invention is directed to a telecommunications system 100 for routing a contact to a selected address, comprising (a) an input for receiving a contact message comprising a source address and a destination address of a subscriber communication device 116 associated with a subscriber and (b) mobility agent 160 for determining whether or not the source address in the contact message corresponds to a proxy server 128 and, when the source address corresponds to a proxy server 128, causing the contact not to be routed to a selected address and, when the source address does not correspond to a proxy server 128, causing the contact to be routed to the selected address.

Abstract: The present invention is directed to a telecommunications system 100 for routing a contact to a selected address, comprising (a) an input for receiving a contact message comprising a source address and a destination address of a subscriber communication device 116 associated with a subscriber and (b) mobility agent 160 for determining whether or not the source address in the contact message corresponds to a proxy server 128 and, when the source address corresponds to a proxy server 128, causing the contact not to be routed to a selected address and, when the source address does not correspond to a proxy server 128, causing the contact to be routed to the selected address.

Abstract: A telecommunications system infrastructure that facilitates easy insertion of feature software into existing such telecommunications systems and easy integration of the new calling features and their implementing software with existing features and their software. The infrastructure comprises the Lucent Technologies MMCX multimedia communications server (100) and middleware-compliant communications endpoints (101-102) executing the Lucent Technologies MMCX communications middleware (111-112). Feature-implementing software has a modular client/server construction, with feature managers (server modules, 300,350) executing on the MMCX server and feature administration agents (client modules, 303-353, 304-354) executing on the endpoints.