Abstract: An information bridge device, IBD (10, 20), comprising: —an API interface (application programming interface) (300) comprising: —an API input (301), for receipt of user input or request via an application (APP) (30) arranged located on a user device (1100) associated with a user (1000), and, an API output (302), for facilitating transfer of data (300F) relating to at least one Enterprise (2000) to the application (APP) (30), the information bridge device further comprising: —a metadata store (310), for storing metadata specific to the at least one Enterprise (2000), said metadata comprising, access information arranged to facilitate access to the at least one Enterprise (2000) by the information bridge device (IBD) (1020), an Enterprise data collector (330), arranged capable of receiving or collecting (300G 300H) Enterprise data from at least one contact option (2100) arranged in association with the at least one Enterprise (2000), and further arranged in co-operation with the metadata store (310) for identif

Abstract: A method of voice call diversion includes detecting an incoming voice call communication from a calling device, identifying an alternate communication option, providing the alternate communication option to the calling device, detecting a selection of the alternate communication option from the calling device, and diverting the incoming voice call communication so as to utilize the selected alternate communication option.

Abstract: A redirection bridge device, RBD (10, 20), comprising: —an API interface (300) comprising an API input (301), arranged capable of receiving a request (300A) from an application (APP) (30), arranged located on a user device (1100) associated with a user (1000), for the purposes of requesting metadata, said metadata being specific to at least one contact option (2100) arranged in association with at least one Enterprise (2000), a metadata store (310), for storing metadata specific to the at least one Enterprise (2000), and arranged to provide metadata to the API interface (300) in response to the request (300A), and, a Communications Manager (320), arranged in co-operation with the API interface (300) and the at least one contact option (2100), for facilitating contact between the user device (1100) and the at least one contact option (2100).

Abstract: A message interchange gateway for transferring messages between a first party and a second party includes an ingress module, arranged to accept at least one message from the first party, a session manger arranged to accept the at least one message from the ingress module, the session manager being further arranged in co-operation with a storage device having data, a message queuing module having at least one session-based message queue, and at least a first session handler having a first session. The first session handler is arranged in co-operation with a first session-based message queue for the processing of the at least one message according to an instruction from the session manager. The instruction is at least partially based on the data, and the first session handler is further arranged to dispatch, after processing, the at least one message from the first session-based message queue to the second party.

Abstract: A Multimedia Messaging Service Gateway (MMSGW) system for the reception of a content associated with a MMS message is described. The MMSGW includes an ingress for reception of a notification to the MMSGW of sending of the MMS message and for forwarding of the notification to an initial parser arranged to obtain metadata associated with the content for production of an IP object based on the notification. The MMSGW also includes a content retrieval for download of the content from the server according to the IP object, storage for one or more of the retrieved content or metadata associated with the retrieved content, an egress for transmitting a MMSGW process completion indicator, and an API for facilitating retrieval of one or more of the retrieved content or the metadata by a remote party.

Abstract: A method includes receiving a message from an XMPP client for delivery to a contact, querying an XMPP presence system for an XMPP address and presence information related to the contact, querying the XMPP presence system for an alternative address if an XMPP address is not available or the presence information indicates that the contact is unavailable, and delivering the message to the alternative address or storing the message for future delivery if an alternate address is unavailable.

Abstract: A message transfer system, method of transferring message and a software product. A message transfer system (10) comprising: an interface to a send agent (70), arranged to facilitate an input of an at least one message to the message transfer system, an interface to a delivery agent (80), arranged to facilitate an output of the at least one message from the message transfer system, a message queue, arranged to facilitate a processing of the at least one message through the message transfer system (10) between the interface to a send agent (70) and the interface to a delivery agent (80), wherein, the message transfer system (10) further comprises a message transfer node (20 22 23 24 25 26 27), arranged to comprise the message queue (90) such that the message queue (90) is arranged as distributed.

Abstract: A message interchange gateway for transferring messages between a first party and a second party includes an ingress module, arranged to accept at least one message from the first party, a session manger arranged to accept the at least one message from the ingress module, the session manager being further arranged in co-operation with a storage device having data, a message queuing module having at least one session-based message queue, and at least a first session handler having a first session. The first session handler is arranged in co-operation with a first session-based message queue for the processing of the at least one message according to an instruction from the session manager. The instruction is at least partially based on the data, and the first session handler is further arranged to dispatch, after processing, the at least one message from the first session-based message queue to the second party.

Abstract: A message transfer system includes an interface to a send agent, arranged to facilitate an input of an at least one message to the message transfer system, an interface to a delivery agent, arranged to facilitate an output of the at least one message from the message transfer system, a message queue, arranged to facilitate a processing of the at least one message through the message transfer system between the interface to a send agent and the interface to a delivery agent, and a message transfer node, arranged to include the message queue such that the message queue is arranged as distributed.

Abstract: A method for providing communication interaction visibility includes detecting an incoming voice call communication to a communication system, determining an identifier of a caller initiating the voice call communication, retrieving a communication history related to the identifier from a messaging gateway, and providing the communication history to an agent terminal of the communication system.