System and method for enabling use of a single user identifier across incompatible networks for ucc functionality

A method for supporting a cross-domain communication session between communication platforms using a bridge server, the method comprising:

• registering, by a bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;
• receiving, by the bridge server, a request to establish a communication session with the user corresponding to the user identifier, the request being received from one of the communications platforms;
• creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as a incoming leg and any other of the communication legs are designated as outgoing legs;
• sending, by the bridge server, the request to establish the communication session over the outgoing legs;
• receiving, by the bridge server, a cancel message from the incoming leg;
• sending, by the bridge server, a cancel message over the outgoing legs;
• and
• destroying, by the bridge server, all of the communication legs.

A system for supporting a cross-domain communication session between communication platforms using a bridge server, the system comprising:

• a processor;
• and
• a memory coupled to the processor, the memory containing computer executable instructions for
• providing a bridge server;
• registering, by the bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;
• receiving, by the bridge server, a request to establish a communication session with a user corresponding to the user identifier, the request being received from one of the communications platforms;
• creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;
• sending, by the bridge server, the request to establish the communication session over the outgoing legs;
• receiving, by the bridge server, a communication acceptance from one of the outgoing legs;
• sending, by the bridge server, a cancel message over any of the outgoing legs from which the communication acceptance was not received;
• sending, by the bridge server, the communication acceptance over the incoming leg;
• and
• bridging, by the bridge server, the incoming leg and the outgoing leg from which the communication acceptance was received to establish the communication session.

A system for supporting a cross-domain communication session between communication platforms using a bridge server, the system comprising:

• a processor;
• and
• a memory coupled to the processor, the memory containing computer executable instructions for
• providing a bridge server;
• registering, by the bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;
• receiving, by the bridge server, a request to establish a communication session with the user corresponding to the user identifier, the request being received from one of the communications platforms;
• creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as a incoming leg and any other of the communication legs are designated as outgoing legs;
• sending, by the bridge server, the request to establish the communication session over the outgoing legs;
• receiving, by the bridge server, a cancel message from the incoming leg;
• sending, by the bridge server, the cancel message over the outgoing legs;
• and
• destroying, by the bridge server, all of the communication legs.

A system for supporting a cross-domain communication session between communication platforms, the system comprising:

• a bridge server registered with at least two communication platforms using a user identifier, wherein the at least two communication platforms are in separate and incompatible domains and wherein the user identifier is recognized by all of the at least two communication platforms;
• and
• a cross-domain database having a plurality of information specific to the at least two communication platforms and the user identifier,
• wherein the bridge server is configured to receive communications requests from the at least two communication platforms and to manage communication sessions between the at least two communication platforms using the plurality of information specific to the at least two communication platforms.