SQL Experience ... what would you do?

Coming into SQL yesterday afternoon I was switched to tower and reported approaching Coyote Hills. The response was what I was expecting, right base for runway 30 report cement plant BUT it “sounded” different. It sounded like the tower controller was down the hallway talking into the microphone, i.e. it was a faint. As I continued inbound, things got a lot stranger. As aircraft made calls to SQL tower, the SQL tower responses not only were faint but became choppy… you could hear only every other word. A few seconds latter you could only hear garbled responses from SQL tower. Planes already in contact with SQL were reporting back that the SQL response was unreadable. A plane on the ground must have just switched to tower frequency with a request and went through the whole process of indicating they were having difficulty hearing on COMM 1 and were going to switch to COMM 2 thinking they had the problem trying again on COMM 2 and getting no clear response. At this time, no one could understand SQL tower transmissions. So what do you do in a situation like that? We have all been trained on how to handle a radio failure in our planes when landing at class D airspace, i.e.

“Remain outside or above Class D airspace until direction of traffic and runway in use has been determined. Squawk 7600 before entering Class D airspace, enter the traffic pattern on a 45, and fly a typical pattern for landing. Look for light gun signals.”

But is there a standard procedure when the loss of radio communications is with the tower itself?

So I started to consider my Options….
Before I tell how this situation ended, I am curious how many great suggestions we have on how to handle this situation. This would be a great topic for a pilot discussion group.