Session initiation protocol (SIP) overload protection

A device, comprising:

• a memory to store instructions;
• and
• a processor to execute the instructions to:
• generate a current load status associated with the device,
• generate address information associated with a Session Initiation Protocol (SIP) device provided upstream from the device,
• create a header that includes:
• the current load status,
• the address information, and
• information defining a time during which the header is to be considered valid by the SIP device,
• send a SIP message, that includes the header, to the SIP device,
• receive, from the SIP device, a first amount of traffic that is based on the current load status included in the header of the SIP message, and
• receive a second amount of traffic,
• the second amount of traffic being less than the first amount of traffic when another load status, associated with the device, is not sent to the SIP device within a particular amount of time after receiving the first amount of traffic.

A non-transitory computer-readable medium storing instructions, the instructions comprising:

• one or more instructions which, when executed by a device, cause the device to generate a load status associated with the device;
• one or more instructions which, when executed by the device, cause the device to generate address information associated with a Session Initiation Protocol (SIP) device provided upstream from the device,
• the one or more instructions to generate the address information including:
• one or more instructions to generate the address information based on an address received from the SIP device;
• one or more instructions which, when executed by the device, cause the device to create a header that includes:
• the load status, and
• the address information;
• one or more instructions which, when executed by the device, cause the device to send a message, that includes the header, to the SIP device;
• one or more instructions which, when executed by the device, cause the device to receive, from the SIP device, a first amount of traffic that is based on the load status included in the header of the message;
• and
• one or more instructions which, when executed by the device, cause the device to receive a second amount of traffic,
• the second amount of traffic being less than the first amount of traffic when another load status, associated with the device, is not sent to the SIP device within a particular amount of time after receiving the first amount of traffic.