Automatic detection and failover of multimedia message service center (MMSC) servers from user plane function voice (UPFV) in public cloud services

A computing system comprising:

• one or more processing devices;
• and
• memory communicatively coupled with and readable by the one or more processing devices and having stored therein processor-readable instructions which, when executed by the one or more processing devices, cause the one or more processing devices to perform operations comprising:
• identifying a failed status of a first multimedia message service center (MMSC) server in a cellular network;
• storing an identifier of the first MMSC server in a failure list;
• selecting a second MMSC server from an MMSC pool;
• sending, to a domain name system (DNS) server, a second Internet Protocol (IP) address request regarding the second MMSC server;
• receiving, from the DNS server, a second IP address of the second MMSC server;
• sending, to the second MMSC server, according to the second IP address, a second health check request;
• receiving, from the second MMSC server, a pass notification indicating a healthy status of the second MMSC server;
• and
• sending, to the second MMSC server, a messaging request.

One or more non-transitory, computer-readable storage media having computer-readable instructions thereon which, when executed by one or more processing devices, cause the one or more processing devices to perform operations comprising:

• receiving a messaging request from user equipment (UE) in a cellular network;
• sending, to a domain name system (DNS) server, a first Internet Protocol (IP) address request regarding a first multimedia message service center (MMSC) server;
• receiving, from the DNS server, a first IP address of the first MMSC server;
• sending, to the first MMSC server, according to the first IP address, a first health check request;
• identifying a failed status of the first MMSC server;
• storing an identifier of the first MMSC server in a failure list;
• selecting a second MMSC server from a MMSC pool;
• sending, to the DNS server, a second IP address request regarding the second MMSC server;
• receiving, from the DNS server, a second IP address of the second MMSC server;
• sending, to the second MMSC server, according to the second IP address, a second health check request;
• receiving, from the second MMSC server, a pass notification indicating a healthy status of the second MMSC server;
• and
• sending, to the second MMSC server, a messaging request.