Abstract: Disclosed herein is a call coordination system configured to manage both static-type and dynamic-type emergency calls via a singular IP address and a single set of SIP peering connections. The call coordination system a unified structural framework wherein individual accounts, whether static or dynamic, are structured into hierarchical parent-child relationships to form linked accounts. These linked accounts can include both static-type and dynamic-type ES accounts. Upon receipt of an incoming call, the call coordination system can determine the call type and processes the call accordingly.

Abstract: Methods identifying inbound call traffic anomalies in a telecommunications system are provided. The method includes receiving expected values for data related to the telecommunications system, the data being associated with call detail records; for each metric in the received data, determining if an observed value is outside defined upper and lower thresholds; selecting a set of residuals based on an aggregation of data in the call detail records if the observed value is outside the defined upper and lower thresholds; computing an anomaly score based the selected set of residuals; determining if multiple, serial anomalous alerting windows are needed to create an alert if the computed anomaly score is greater than a minimum anomaly score; and declaring that the data supports an anomaly in the inbound call traffic if it is determined that multiple, serial anomalous alerting windows are not needed to create an alert.

Abstract: Techniques are disclosed to determine one or more specific data points that may be found in or added to call metadata that will assist and/or enhance confidence score algorithms. A call request for an inbound VoIP telephony call may be received by a telephony server in a servicing telecommunications carrier network. The call request may be intended for a called party serviced by the servicing telecommunications carrier network. The servicing telecommunications carrier network telephony server may obtain a plurality of data points associated with the call request wherein at least one of the data points is an interconnect carrier, the interconnect carrier data point identifying which carrier handed the call to the servicing carrier. The servicing telecommunications carrier network telephony server may then send the plurality of data points to a confidence score generating process comprising an algorithm configured to determine a confidence score using the data points.

Abstract: Techniques are described for obtaining current location data for a non-traditional telephony endpoint for emergency calling purposes. An emergency services (ES) provider receives, from a telephony server responding to a telecommunication session establishment request from a telephony endpoint, a location registration request, the location registration request including telephony endpoint identification information and a mobile device telephone number. The ES provider may send a short message service (SMS) message to the mobile device telephone number, the SMS message including an executable registration link that when executed on a mobile device receiving the SMS message causes the mobile device to retrieve location data of the mobile device. The ES provider may then receive the current location data from the mobile device and store it and the telephony endpoint identification information for subsequent use should a 911 call be made from that telephony endpoint.

Abstract: Techniques are described for obtaining current location data for a non-traditional telephony endpoint for emergency calling purposes. An emergency services (ES) provider receives, from a telephony server responding to a telecommunication session establishment request from a telephony endpoint, a location registration request, the location registration request including telephony endpoint identification information. The ES provider may push a quick response (QR) code to the telephony endpoint, the QR code when scanned by a mobile device causes the mobile device to retrieve its current location data. The ES provider may then receive the current location data from the mobile device and store it and the telephony endpoint identification information for subsequent use should a 911 call be made from that telephony endpoint. The ES provider may then send the telephony server an authorization acknowledgement for the telecommunication session establishment request.

Abstract: Techniques are described for determining when and how to re-route toll-free calls around a core telephony network experiencing significant disruptions. A core telephony network of a telephony service provider is monitored for anomalies. Upon detecting an anomaly, it is determined whether the anomaly is significant enough to warrant re-routing inbound toll-free calls around the core telephony network. The re-routing process comprises accessing an industry registry database including a plurality of toll-free numbers (TFNs) associated with a routing template comprising the instructions for routing toll-free calls. The routing template instructions may be switched to re-direct toll-free calls associated with one or more specific TFNs to a particular carrier. Within that particular carrier, the routing instructions may be switched to re-direct the toll-free calls away from the service provider's core telephony network to a network bypass cloud platform.

Abstract: A software development system is provided for creating and testing applications. The software development system includes a non-transitory computer-readable medium and a processor in communication with the medium.

Abstract: Some embodiments of the present inventive concept provide methods for processing unwanted text messages based on reporting of sending telephone in a telecommunications system. The method includes retrieving aggregated data associated with sending telephone numbers from a central repository accessible by a plurality of Carriers. The retrieved aggregated data is analyzed to identify sending telephone numbers that satisfy flagging criteria. The flagging criteria indicates a threat level associated with text messages sent from corresponding telephone numbers. Preventative and/or remedial action is implemented for each telephone number identified as satisfying flagging criteria. A severity of the preventative and/or remedial action is directly correlated with the threat level associated with the flagging criteria. Each of these sending telephone numbers is actively monitored.

Abstract: Techniques are described for managing out of service telephone numbers (TNs) before returning them to active service. A telephone number profile score may be calculated for an out of service TN entering an aging protocol, the aging protocol comprising a pre-determined number of days the TN must remain out of service. The out of service TN may then be assigned a profile based on its telephone number profile score, the profile indicative of how quickly the TN will achieve one or more quality thresholds. The number of days from entry into the aging protocol it will take the TN to achieve the one or more quality thresholds based on its assigned profile may be determined. The quality threshold status of the TN may then be updated each time it crosses one of the quality thresholds. Once it completes the aging process, the TN may be placed into an inventory of TNs eligible for active service.

Abstract: Methods for determining a cause of a detected anomalous event in a telecommunications system are provided. The methods include detecting an anomalous event in the telecommunications system and retrieving relevant call detail record (CDR) data associated with the detected anomalous event for at least one identified time interval responsive to detecting the anomalous event. The relevant CDR data includes both current CDR data for the at least one identified time interval and historical CDR data for past intervals corresponding to the at least one identified time interval. The relevant CDR data including the current CDR data and the historical CDR data is preprocessed and the preprocessed relevant CDR data is processed to determine a root cause of the detected anomalous event. Processing the preprocessed relevant CDR data includes comparing the current CDR data and the historical CDR data to determine the root cause of the detected anomalous event.

Abstract: Techniques are described for vetting unwanted calls. At an inbound customer call handling apparatus, a SIP INVITE is received from a destination carrier servicing the inbound customer intended for a destination user agent (UA) device of the inbound customer. The SIP INVITE includes a current origination identifier (ORIG ID) comprised of a fixed length character string. The call handling apparatus accesses a database of stored ORIG ID character strings, each stored ORIG ID character string in the database having been included with a previous SIP INVITE that has been previously associated with an unwanted inbound call. The call handling apparatus analyzes the current ORIG ID character string to determine if it matches any stored ORIG ID character strings in the database. When there is a match to a stored ORIG ID character string, the SIP INVITE is not forwarded to the destination UA device. Otherwise, it is forwarded to the destination UA device.

Abstract: Techniques for customizing an audio response to emergency test calls are provided. The technique includes receiving a Voice over Internet Protocol (VoIP) emergency test call from a test call device by an emergency service (ES) provider. Call information specific to the VoIP emergency test call is obtained from an ES provider customer database associated with the ES provider. The obtained call information specific to the VoIP emergency test call is provided to an emergency test call audio generation server. A customized audio response to the VoIP emergency test call is generated and returned to the test call device based on the provided call information specific to the VoIP emergency test call using text-to-speech technology.

Abstract: Techniques for managing transmission rates for users from each of a plurality of call engines (CEs) distributed on a communications network are provided. A list of users with at least one pending call in a corresponding queue from all other CEs is received, wherein each user's queue has a maximum queue depth calculated, in part, using a capped transmission rate in calls per second (CPS) for each user associated with their queue. It is determined, for each user, a total number of CEs having at least one pending call in their corresponding queue. A current CE transmission rate is calculated for each user by dividing the capped transmission rate for each user by the total number of CEs having at least one pending call in their corresponding queue. The current CE transmission rate indicates a rate at which calls in each user's queue are dequeued at each of the plurality of CEs.

Abstract: Disclosed are techniques for routing messages from a message delivery network (MDN) to one of a plurality of end user carriers, wherein there are a plurality of message routes capable of servicing each end user carrier. An MDN may receive a message from a sending message service provider. The MDN may identify a destination end user carrier servicing the end user device for the message. The MDN may produce a rank ordered list of message routes from the MDN to the destination end user carrier by solving a linear constrained optimization model configured to converge upon an optimized ranking of message routes from the MDN to the plurality of end user carriers. The MDN may then attach the rank ordered list of message routes to the message before forwarding the message to a gateway within the MDN. The gateway may then initially attempt delivery of the message using the highest ranked message route from the rank ordered list of message routes.

Abstract: Methods for ERL Correction are provided including receiving a VoIP emergency call from an emergency caller. The VoIP emergency call is identified by a unique ELIN. The ERL data associated with the unique ELIN is retrieved from a LIS using the unique ELIN. A notification is intercepted at the LIS. The notification contains both an original extension number or a DID number and the ERL data. The ERL data is matched using the ELIN to the ERL data to locate one of the original extension number and the DID number. A correct physical address is located using the original extension number or the DID number. Address data is corrected in the ERL to include the correct physical address of the emergency caller to provide a corrected ERL. The notification is reissued including the corrected ERL and the VoIP emergency call is routed to a PSAP with the corrected ERL.

Abstract: In some implementations, a computer may during a repeating interval in a local GCAC node: (a) receiving and storing key data from one or more other GCAC nodes, the key data indicative of resource usage data for each key in the respective one or more other GCAC nodes wherein each key is associated with an allocation limit equal to a number of resources it may use at any given time across all GCAC nodes; (b) storing current key data, the current key data indicative of the resource usage data for each key in the local GCAC node; (c) determining estimated network-wide key data, the estimated network-wide key data indicative of an estimated network-wide resource usage across all GCAC nodes for each key, the estimated network-wide key data based on a combination of the current key data for the local GCAC node and a weighted multiple of the key data in each of the one or more other GCAC nodes; (d) storing the estimated network-wide key data for each key; and (e) repeating steps (a)-(d) during each interval.

Abstract: Techniques are described for managing the recipients of application-to-person (A2P) short message service (SMS) messages. A send-to list comprised of telephone numbers to which to send A2P short message service (SMS) messages is received from an A2P sender. The opt-in/opt-out status of each telephone number on the send-to list is determined. Telephone numbers on the send-to list that cannot be verified as opt-in status are flagged as opt-out status. The A2P sender is then prevented from sending of A2P SMS messages to telephone numbers flagged as opt-out status.

Abstract: Methods for detecting anomalies in a telecommunications network are provided. The methods include calculating a call duration for each of a plurality of calls associated with a corresponding call detail record (CDR). Each CDR provides details associated with a single call in a plurality of fields. Each of the plurality of calls are categorized based on the calculated call duration for each call such that each of the plurality of calls is assigned to a duration bin, each duration bin including calls having similar calculated call durations. The CDRs are grouped using the duration bins and at least one carrier and/or a telecommunications provider. A plurality of summary statistics are calculated for each of the plurality of CDR groups. The calculated plurality of summary statistics are analyzed to determine whether an anomaly is present. Among other remedial measures, an external ticket may be generated informing affected carriers when an anomaly is present.

Abstract: A message delivery network may receive a message from a sending message service provider. The message delivery network may identify an end user carrier servicing the end user device for the message. The message delivery network may retrieve a pre-determined rank ordered list of message routes from the message delivery network to the end user carrier. The message delivery network may determine whether each message route is currently unavailable or demonstrating poor deliverability. The message delivery network may de-prioritize the message routes that are demonstrating poor deliverability. The message delivery network may update the rank ordered list of message routes based on the de-prioritized message routes. The message delivery network may attach the updated rank ordered list of message routes to the message. The message delivery network may forward the message to a gateway within the message delivery network. The gateway may deliver the message using the highest ranked message route.

Abstract: Techniques are disclosed for correlating delivery receipt (DLR) messages with short message service (SMS) messages sent in an application-to-person (A2P) manner through a messaging network comprising multiple data centers. SMS and DLR messages are received and stored into a correlator comprising a local and a global storage area. It is then determined whether a received DLR message corresponds to a received SMS message within a local timeout period associated with the received SMS message. When corresponding DLR and SMS messages have been received they are correlated and the DLR message is sent to the sending SMS client. When corresponding DLR and SMS messages have not been received the location of a global storage area of a correlator in a data center where the DLR and SMS messages are intended to be stored is derived.