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 mobile device identifies multiple, different networks available to a client resident on the mobile device, and sends multiple registration messages to an outbound proxy over the multiple, different networks via first, second and third communication interfaces. The mobile device determines whether access has been lost to a first network of the multiple different networks, and sends an invite message via the second communication interface, based on the determination, for an outbound call via a second network of the multiple, different networks for routing the outbound call via the second network.

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 device includes a memory that stores multiple different types of applications and a data table, and a processing unit. The processing unit is configured to receive configuration data that sets up multiple network interfaces on the device, and assigns one of multiple different network addresses to each of the multiple network interfaces, store the configuration data in the data table, execute a first type of application of the multiple different types of applications, receive one or more first packets from executing the first type of application of the multiple different types of applications, retrieve a first Virtual Private Network (VPN) identifier associated with a first VPN from the data table based on the first type of application of the multiple different types of applications, and send the one or more first packets via the first VPN identified by the first VPN identifier.

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 phone docking station includes a docking port configured to physically dock with a mobile phone. The docking port further includes a charging port configured to connect with the docked mobile phone and to supply a charging current to a battery of the mobile phone, and a Universal Serial Bus (USB) port. The phone docking station further includes a system configured to carry VoIP traffic from an external network through the USB port to the mobile phone, and from the mobile phone through the USB port to the external network; and enable, via the USB port, media streaming from the phone docking station to the mobile phone, and from the mobile phone to the phone docking station.

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 mobile device identifies multiple, different networks available to a client resident on the mobile device, and sends multiple registration messages to an outbound proxy over the multiple, different networks via first, second and third communication interfaces. The mobile device determines whether access has been lost to a first network of the multiple different networks, and sends an invite message via the second communication interface, based on the determination, for an outbound call via a second network of the multiple, different networks for routing the outbound call via the second network.

Abstract: A device receives a personal Mobile Directory Number (MDN) associated with an individual subscriber, where the individual subscriber is further associated with one or more subscriber devices. The device receives a corporate MDN assigned to the individual subscriber. The device links the corporate 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) for routing calls to the individual subscriber's corporate MDN or personal MDN at the one or more subscriber devices.

Abstract: A method includes receiving, at a computing device, a call originally directed to a mobile device, and forwarding the call to at least one other device. The method further includes determining that the forwarded call is not answered by the at least one other device and forwarding two versions of the call to the mobile device, such that one of the two versions of the call is automatically directed toward a voicemail account associated with the mobile device. The other of the two versions of the call is then canceled.

Abstract: A network mobility device registers with a switch in a telephone network, and receives a first message from a docking station indicating that a mobile device has undocked from the docking station. The docking station includes a Voice over Internet Protocol (VoIP) phone that has a wired connection to a data network, and the mobile device includes a portable digital computing device. The network mobility device receives a call, destined for the mobile device, routed from the switch, and sends an alert message, based on the undocking of the mobile device and the received call, to the mobile device to notify a client of the mobile device of the call. The network mobility device forwards the call, based on the undocking of the mobile device, from the network mobility device to the client at the mobile device via the data network.

Abstract: A mobile device establishes a first network connection via a first communication interface when the mobile device is in a first docking status with a docking station. The mobile device sends Voice over Internet Protocol (VoIP) traffic associated with a VoIP call via the first network connection, and activates a second network connection via a second communication interface when the mobile device is in the first docking status, where the second network connection is different than the first network connection. The mobile device re-directs the VoIP traffic via the previously activated second network connection based on a change in docking status of the mobile device with the docking station to a second docking status.

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 includes a memory that stores multiple different types of applications and a data table, and a processing unit. The processing unit is configured to receive configuration data that sets up multiple network interfaces on the device, and assigns one of multiple different network addresses to each of the multiple network interfaces, store the configuration data in the data table, execute a first type of application of the multiple different types of applications, receive one or more first packets from executing the first type of application of the multiple different types of applications, retrieve a first Virtual Private Network (VPN) identifier associated with a first VPN from the data table based on the first type of application of the multiple different types of applications, and send the one or more first packets via the first VPN identified by the first VPN identifier.

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 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.