Abstract: In some implementations, a device may receive a session initiation protocol (SIP) message. The device may determine that the SIP message does not include a parameter indicating that a first portion of the SIP message is to be processed as a telephone number. The device may perform one or more actions including one or more of: determining whether a second portion of the SIP message includes information identifying a service; determining whether the first portion of the SIP message includes a code; determining whether the first portion of the SIP message is formatted according to a format associated with a telephone number; or determining whether the first portion of the SIP message includes characters that are different than hexadecimal characters. The device may selectively cause the SIP message to be routed using the first portion of the SIP message or routed using the second portion of the SIP message.

Abstract: In some implementations, a device may receive a session initiation protocol (SIP) message. The device may determine that the SIP message does not include a parameter indicating that a first portion of the SIP message is to be processed as a telephone number. The device may perform one or more actions including one or more of: determining whether a second portion of the SIP message includes information identifying a service; determining whether the first portion of the SIP message includes a code; determining whether the first portion of the SIP message is formatted according to a format associated with a telephone number; or determining whether the first portion of the SIP message includes characters that are different than hexadecimal characters. The device may selectively cause the SIP message to be routed using the first portion of the SIP message or routed using the second portion of the SIP message.

Abstract: A network device may include a memory storing instructions and processor configured to execute the instructions to receive a file transfer request that includes at least a network location corresponding to a file to be transferred; determine whether the network location is internal or external to a network to which the network device belongs; modify the network location when it is determined that the network location included in the file transfer request is external to the network; and retrieve the file to be transferred using the modified network location.

Abstract: A network device may include a memory storing instructions and processor configured to execute the instructions to receive a file transfer request that includes at least a network location corresponding to a file to be transferred; determine whether the network location is internal or external to a network to which the network device belongs; modify the network location when it is determined that the network location included in the file transfer request is external to the network; and retrieve the file to be transferred using the modified network location.

Abstract: A network device may include a memory storing instructions and processor configured to execute the instructions to receive, from a first service provider, a file transfer request that includes at least a network location corresponding to a file to be transferred; determine whether the network location is internal or external to a second service provider network to which the network device belongs; modify the network location when it is determined that the network location included in the file transfer request is external to the second service provider network; retrieve the file to be transferred using the modified network location; and forward the retrieved file to a terminating user equipment (UE) device.

Abstract: A method, a device, and a non-transitory storage medium having instructions to establish a web connection with a user device and provide access to a carrier-grade network in support of a Web Real Time Communication (WebRTC) session; obtain service data that includes data pertaining to a user of the user device; assign a level of trustworthiness to the service data; generate a message, wherein the message includes a request to initiate the WebRTC session; package the service data in the message based on the level of trustworthiness; and transmit the message to another device.

Abstract: A network traffic monitoring system detects an identity associated with a telephone call that enters a network and queries a first identity source list that includes entries representative of illegitimate identities and a second identity source list that includes entries representative of legitimate identities to determine whether the detected identity associated with the telephone call matches an entry included in the first identity source list or an entry included in the second identity source list. If the detected identity matches the entry included in the first identity source list, the network traffic monitoring system automatically determines that the detected identity is fake. If the detected identity matches the entry included in the second identity source list, the network traffic monitoring system analyzes one or more attributes of the telephone call other than the detected identity to determine whether the detected identity is fake.

Abstract: A method, a device, and a non-transitory storage medium having instructions to establish a web connection with a user device and provide access to a carrier-grade network in support of a Web Real Time Communication (WebRTC) session; obtain service data that includes data pertaining to a user of the user device; assign a level of trustworthiness to the service data; generate a message, wherein the message includes a request to initiate the WebRTC session; package the service data in the message based on the level of trustworthiness; and transmit the message to another device.

Abstract: (“TRE”) provides an automatic routing, selecting, processing for calls placed in an international network according to a selected International Tier Level for premium or guaranteed delivery. In one embodiment, a platform initiates international tiered routing information to a gateway based on a pre-set platforms' knowledge of the terminating gateway topology, Automatic Number Identification, and assigned services that requires such transmission. In one embodiment, a user may select a tier to route an international call. In another embodiment, the contextual fields of a communication mechanism define tags and tier levels indicating determining, routing and handling information to be sent to a validated gateway, or routing devices. In one embodiment, contextual tags includes customized domain name and global descriptors of compatible network components, delivery control, trunk group service ID, trunk-related tier level, and other trunk-related service attributes for tiered routing.

Abstract: A device receives a Session Initiation Protocol (SIP) response that includes a load header associated with a downstream Session Initiation Protocol (SIP) device. The device also determines an amount of traffic to send to the downstream Session Initiation Protocol (SIP) device based on the load header. The device further sends the determined amount of traffic to the downstream Session Initiation Protocol (SIP) device.

Abstract: A device receives a Session Initiation Protocol (SIP) response that includes a load header associated with a downstream Session Initiation Protocol (SIP) device. The device also determines an amount of traffic to send to the downstream Session Initiation Protocol (SIP) device based on the load header. The device further sends the determined amount of traffic to the downstream Session Initiation Protocol (SIP) device.

Abstract: A device receives a Session Initiation Protocol (SIP) response that includes a load header associated with a downstream Session Initiation Protocol (SIP) device. The device also determines an amount of traffic to send to the downstream Session Initiation Protocol (SIP) device based on the load header. The device further sends the determined amount of traffic to the downstream Session Initiation Protocol (SIP) device.

Abstract: The APPARATUSES, METHODS AND SYSTEMS FOR TIERED ROUTING ENGINE (“TRE”) provides an automatic routing, selecting, processing for calls placed in an international network according to a selected International Tier Level for premium or guaranteed delivery. In one embodiment, a platform initiates international tiered routing information to a gateway based on a pre-set platforms' knowledge of the terminating gateway topology, Automatic Number Identification, and assigned services that requires such transmission. In one embodiment, a user may select a tier to route an international call. In another embodiment, the contextual fields of a communication mechanism define tags and tier levels indicating determining, routing and handling information to be sent to a validated gateway, or routing devices.

Abstract: A device receives a Session Initiation Protocol (SIP) response that includes a load header associated with a downstream Session Initiation Protocol (SIP) device. The device also determines an amount of traffic to send to the downstream Session Initiation Protocol (SIP) device based on the load header. The device further sends the determined amount of traffic to the downstream Session Initiation Protocol (SIP) device.

Abstract: A method for routing an international call includes receiving a call and identifying a first international carrier based on an Internet protocol address associated with the call or a tunnel through which the call was received. The method also includes identifying a second international carrier based on the identified first international carrier. The second international carrier may represent a terminating carrier associated with forwarding the call to a called party. The method may further include forwarding the call to the identified second international carrier.

Abstract: A method for processing a call is provided. The method includes receiving an inbound call leg via a network device. The inbound call leg is processed using an interactive voice response (IVR) device, and an outbound call leg is generated based on processing the inbound call leg. The outbound call leg is made available to the network device. The inbound call leg and the outbound call leg are handed off from the IVR device to the network device.