Abstract: Techniques described herein may use presence information to enhance the user experience when contacting entities such as call centers. In one implementation, a method may include receiving presence information relating to a state of a voice line. The presence information may include a wait time associated with the voice line, the wait time corresponding to an estimated time that a caller to the voice line will wait before reaching a human operator. The method may also include providing, by the one or more devices and to a user device that includes the voice line in a contact list, the presence information for display as part of the contact list.

Abstract: A gateway may be configured to establish a first data connection between the gateway device and a client device. The first data connection may be based on a Web Real-Time Communication application programming interface. The gateway may establish a second data connection between the gateway device and an Internet Protocol (“IP”) Multimedia Subsystem (“IMS”) core; and facilitate communications, that are based on a Rich Communication Services (“RCS”) standard, between the client device and the IMS core. Facilitating the communications may include outputting communications, that are based on communications received from the client device via the first data connection, to the IMS core via the second data connection, and outputting communications, that are based on communications received from the IMS core via the second data connection, to the client device via the first data connection.

Abstract: A device may determine that a user device should be authenticated; and determine a confidence measurement based on an established activity pattern of the user device. The confidence measurement may relate to a likelihood that an authorized user of the user device is in possession of the user device. The device may authenticate the user device based on the confidence measurement.

Abstract: A network device receives a personal Mobile Directory Number (MDN) associated with an individual subscriber, wherein the individual subscriber is further associated with one or more subscriber devices. The network device receives an additional MDN assigned to the individual subscriber, and sends a notification, requesting the individual subscriber's acceptance of the additional MDN assigned to the individual subscriber, to at least one of the one or more subscriber devices. The network device receives, from one of the one or more subscriber devices, an acceptance of the additional MDN from the individual subscriber. The network device links the additional MDN, the personal MDN, and the one or more subscriber devices, within an Implicit Registration Set (IRS) at a Home Subscriber Server (HSS) in an Internet Protocol Multimedia Subsystem (IMS) network for routing calls to the individual subscriber's additional MDN or personal MDN at the one or more subscriber devices.

Abstract: A system may include a first Internet Protocol Multimedia Subsystem (IMS) network comprising one or more devices configured to receive a first registration request for a first mobile directory number (MDN), associated with a subscriber, wherein the first MDN corresponds to a home mobile directory number with respect to the first IMS network; and register the first MDN with the first IMS network. The one or more device may be further configured to detect a service point trigger, associated with the subscriber, to register a second MDN, foreign to the first IMS network, with a second IMS network, in response to the first MDN being registered; and send a second registration request to the second IMS network, to register the second MDN with the second IMS network.

Abstract: A user device may identify a received a signal indicating an incoming call; determine that another user device has answered the call; generate call log information that indicates that the other user device has answered the call; and store or output the generated call log information. Additionally, or alternatively, a set of user devices may receive a ring signal indicating an incoming call; a particular user device, in the set of user devices, may answer the call; and another user device, in the set of user devices, may store a unified call log. The unified call log may indicate that the particular user device answered the call, and may further indicate that the other user device did not miss the call.

Abstract: A device may determine that a user device should be authenticated; and determine a confidence measurement based on an established activity pattern of the user device. The confidence measurement may relate to a likelihood that an authorized user of the user device is in possession of the user device. The device may authenticate the user device based on the confidence measurement.

Abstract: A user device may identify a received a signal indicating an incoming call; determine that another user device has answered the call; generate call log information that indicates that the other user device has answered the call; and store or output the generated call log information. Additionally, or alternatively, a set of user devices may receive a ring signal indicating an incoming call; a particular user device, in the set of user devices, may answer the call; and another user device, in the set of user devices, may store a unified call log. The unified call log may indicate that the particular user device answered the call, and may further indicate that the other user device did not miss the call.

Abstract: A device may be configured to receive information regarding a call center. The received information may include an interactive voice response (“IVR”) menu configuration that includes contact information for contacts associated with the call center, and audible options to place a call to the contacts via the contact information for the contacts. The device may parse the IVR menu configuration to generate a graphical user interface (“GUI”) menu configuration, which may comprise visual selectable options that correspond to the audible options. Selection of a particular one of the visual selectable options may cause a call to be placed to a particular contact that is associated with the particular visual selectable option. The device may further store or output the GUI menu configuration.

Abstract: A device may be configured to receive information regarding a call center. The received information may include an interactive voice response (“IVR”) menu configuration that includes contact information for contacts associated with the call center, and audible options to place a call to the contacts via the contact information for the contacts. The device may parse the IVR menu configuration to generate a graphical user interface (“GUI”) menu configuration, which may comprise visual selectable options that correspond to the audible options. Selection of a particular one of the visual selectable options may cause a call to be placed to a particular contact that is associated with the particular visual selectable option. The device may further store or output the GUI menu configuration.

Abstract: A gateway may be configured to establish a first data connection between the gateway device and a client device. The first data connection may be based on a Web Real-Time Communication application programming interface. The gateway may establish a second data connection between the gateway device and an Internet Protocol (“IP”) Multimedia Subsystem (“IMS”) core; and facilitate communications, that are based on a Rich Communication Services (“RCS”) standard, between the client device and the IMS core. Facilitating the communications may include outputting communications, that are based on communications received from the client device via the first data connection, to the IMS core via the second data connection, and outputting communications, that are based on communications received from the IMS core via the second data connection, to the client device via the first data connection.

Abstract: A system may include a first Internet Protocol Multimedia Subsystem (IMS) network comprising one or more devices configured to receive a first registration request for a first mobile directory number (MDN), associated with a subscriber, wherein the first MDN corresponds to a home mobile directory number with respect to the first IMS network; and register the first MDN with the first IMS network. The one or more device may be further configured to detect a service point trigger, associated with the subscriber, to register a second MDN, foreign to the first IMS network, with a second IMS network, in response to the first MDN being registered; and send a second registration request to the second IMS network, to register the second MDN with the second IMS network.

Abstract: Techniques described herein may use presence information to enhance the user experience when contacting entities such as call centers. In one implementation, a method may include receiving presence information relating to a state of a voice line. The presence information may include a wait time associated with the voice line, the wait time corresponding to an estimated time that a caller to the voice line will wait before reaching a human operator. The method may also include providing, by the one or more devices and to a user device that includes the voice line in a contact list, the presence information for display as part of the contact list.

Abstract: A network device receives a personal Mobile Directory Number (MDN) associated with an individual subscriber, wherein the individual subscriber is further associated with one or more subscriber devices. The network device receives an additional MDN assigned to the individual subscriber, and sends a notification, requesting the individual subscriber's acceptance of the additional MDN assigned to the individual subscriber, to at least one of the one or more subscriber devices. The network device receives, from one of the one or more subscriber devices, an acceptance of the additional MDN from the individual subscriber. The network device links the additional MDN, the personal MDN, and the one or more subscriber devices, within an Implicit Registration Set (IRS) at a Home Subscriber Server (HSS) in an Internet Protocol Multimedia Subsystem (IMS) network for routing calls to the individual subscriber's additional MDN or personal MDN at the one or more subscriber devices.