Abstract: A request to authenticate a user is received at an authentication system. The request to authenticate the user requires one or more non-numeric metrics to authenticate the user. For example, the one or more non-numeric metrics may include a user name, a password, and a fingerprint scan. The request to authenticate the user that requires the one or more non-numeric metrics is validated. In response to validating the request to authenticate the user that requires the one or more non-numeric metrics, a first numeric code is generated (e.g., a password). The first numeric code is used to grant access to a telephone that requires authentication via a numeric keypad. The first numeric code is sent and displayed to the user. The user can then access the telephone by providing the numeric code at the telephone.

Abstract: Federated computing architectures allow for the interoperability of components and facilitates the exchange of data between varying systems and components. Endpoints, such as those utilizing Extensible Messaging and Presence Protocol (XMPP) assume the same XMPP stream is used for both messaging and presence. Such systems are unable to accommodate a representational state transfer (“REST”) or, in other words, be “RESTful,” where the messaging server and presence server are distinct servers and may be on different domains. Provided here are systems described to split the protocols and enable an endpoint to appear to communicate with a single server while a protocol splitter routes and receives messages from distinct servers handling messaging and presence separately.

Abstract: A first Session Initiation Protocol (SIP) REFER message is sent by an application server to a User Agent (UA). A UA is typically in a communication device, such as a telephone or personal computer. The first SIP REFER message requests the UA to provide a unique Uniform Resource Identifier (URI) for an instance of a networked application. For example, a networked application may be a call recording application. In response to sending the first SIP REFER message, a SIP NOTIFY message with the URI for the instance of the networked application is received by the application server. The application server sends a second SIP REFER message to the UA using the URI. The second SIP REFER message includes information for managing a widget. A widget is object, such as a button or sound. The widget is then displayed or played on a communication device according to a set of rules.

Abstract: Federated computing architectures allow for the interoperability of components and facilitates the exchange of data between varying systems and components. Endpoints, such as those utilizing Extensible Messaging and Presence Protocol (XMPP) assume the same XMPP stream is used for both messaging and presence. Such systems are unable to accommodate a representational state transfer (“REST”) or, in other words, be “RESTful,” where the messaging server and presence server are distinct servers and may be on different domains. Provided here are systems described to split the protocols and enable an endpoint to appear to communicate with a single server while a protocol splitter routes and receives messages from distinct servers handling messaging and presence separately.

Abstract: A communication device gets a widget resource Uniform Resource Identifier (URI) from the network. The widget resource URI is used by the communication device to get a widget (i.e., a graphical user interface object) of a networked application that is displayed on the communication device. In response to getting the widget resource URI, the communication device downloads a context document from the widget resource URI. The context document defines the widget or a location of a widget document that defines the widget for use in the communication device. The communication device identifies an attachment point for the widget (i.e., a place to display the widget) that is associated with an activation of a device object (e.g., a window). The communication device determines that the attachment point is within a scope. In response to determining that attachment point is within the scope, the widget is displayed on the communication device.

Abstract: A first Session Initiation Protocol (SIP) REFER message is sent by an application server to a User Agent (UA). A UA is typically in a communication device, such as a telephone or personal computer. The first SIP REFER message requests the UA to provide a unique Uniform Resource Identifier (URI) for an instance of a networked application. For example, a networked application may be a call recording application. In response to sending the first SIP REFER message, a SIP NOTIFY message with the URI for the instance of the networked application is received by the application server. The application server sends a second SIP REFER message to the UA using the URI. The second SIP REFER message includes information for managing a widget. A widget is object, such as a button or sound. The widget is then displayed or played on a communication device according to a set of rules.

Abstract: Telephonic and other endpoints often make presence information of other users available on the endpoint. Systems whereby every user sends a notification to every other user quickly becomes resource intensive. Providing presence information only to users subscribed to the presence of other users helps; but, maintaining such subscriptions is often overlooked. Providing automatic subscriptions based upon a triggering event allows presence information to be provided to associated users. The presence information may be time limited to allow for an appropriate amount of presence information to be provided for a duration most likely determined to be relevant. Upon expiration of the subscription, the utilized resources are released without requiring any human intervention.

Abstract: A system and method for integrating conventional enterprise communication systems into an IMS-based services environment are disclosed. In one embodiment, when a call request is received for a call between first and second local users of a PBX, the PBX determines whether a class of service for either the first or second local user is for Exposed Local Call (ELC) processing. If so, then call information is routed through a Session Initiation Protocol (SIP) core network that is coupled to an Internet Protocol Multimedia Subsystem (IMS) server to provide IMS services to the call.

Abstract: A communication system, method, and components are described. Specifically, a communication system having the ability to facilitate a semi-attended transfer in SIP for an IP-Multimedia Subsystem (IMS) environment is disclosed. The semi-attended transfer is possible even though one or more Back-to-Back User Agents are positioned between users engaged in the semi-attended transfer.

Abstract: Methods and systems for supporting the alternate routing of calls between endpoints, such as session initiation protocol (SIP) endpoints, are provided. An inner gateway alternate route (IGAR) application is invoked when the primary, Internet protocol, communication network is overloaded or otherwise unable to handle a call. The IGAR application assigns incoming and outgoing trunks, and serves as a contact point for session managers in routing the trunk call.

Abstract: A system and method for integrating conventional enterprise communication systems into an IMS-based services environment are disclosed. In one embodiment, when a call request is received for a call between first and second local users of a PBX, the PBX determines whether a class of service for either the first or second local user is for Exposed Local Call (ELC) processing. If so, then call information is routed through a Session Initiation Protocol (SIP) core network that is coupled to an Internet Protocol Multimedia Subsystem (IMS) server to provide IMS services to the call.