Similarly
One weekend, way back, I was assigned to be on call (although that was not in my contract), for the DBA to if he ran into problems with a large and critical database something. DBA had remote access, I did not. I would also be busy that Saturday preparing a moto trials event, and would be camping out on the terrain to the odd moped youth from getting themselves and the non-stops into disarray. But I had my phone charged and on me, and of bloody course the DBA called at about ten o'clock in the evening. So, sitting at a small campfire (it was late October) I guided him through the more intricate incantations of stuffing a database dump into a backup saveset, then on to another system to free up space, after which he could get on with whatever he needed to inflict on the database. Took about an hour in all.
So far so good.
Coming into work Monday I was immediately pounced upon by a philosopher who had managed to become head of the IT 'department' (just five people, him included), demanding to know why I had been unreachable that weekend during a most urgent database something. Now, being on the phone with the DBA might have resulted in not being able to simultaneously answer other calls, but there had actually been no other calls at all, before, during or after. So my best guess was (and still is) that nITwIT philosopher just had the wrong number for me, and just mashed 'redial' every time instead of looking it up. But he insisted the number was right , so mine must have been unright which obviously was my fault.
Well, end of contract then. No big loss.