“Message sending failed”

failedYesterday afternoon, I was following the Newcastle v Swansea match on the BBCs Premier League live service. I thought it was going to end in a draw, but about a minute before full time Swansea scored. Meh! I immediately sent Jan a text, thinking he might like to know. As usual, minutes after I sent the message my phone beeped – I have delivery reports switched on. I checked the message, expecting it to read “Delivered”, as it always does. Instead, I was confronted with the following: “Jan Mob. Message failed.” That has never happened before. If the recipients phone is off, my phone doesn’t beep and I receive a message saying “Pending”. Once they switch their phone back on, the phone beeps and the “Pending” message changes to “Delivered”. I tried again. Beep beep. “Message failed”. I went and fetched the house phone to call him… “The person you are trying to reach is currently unavailable. Please try again later,” said a female voice – first in German, then in English. Hmm, odd. But he’d told me the night before that he might be allowed to go to the beach. Perhaps he was somewhere with no reception. I went to distract myself by reading some blogs.

unavailable_iconHalf an hour later, I could stand it no more. I dialled his number from out house phone. “The person you are trying to reach is currently unavailable. Please try again later.” I went into the kitchen and plugged in the hoover. Another half an hour, another attempt. “The person you are trying to reach is currently unavailable. Please try again later.” I made a cup of tea, ate a packet of Monster Munch and tried not to worry. For half an hour, then I tried again. It was 7:30 pm by this time, 8:30 in Turkey (he told me the night before that they’re an hour ahead). Even if he had been to the beach, surely he couldn’t still be there? Again “The person you are trying to reach is currently unavailable. Please try again later.” It occurred to me that if anything had happened, I wouldn’t find out until a member of his family thought to contact me. In emergencies, the authorities call your next of kin. Parents… siblings… wives. Not girlfriends. I pushed that thought out of my mind and resolved to try again later.

After each failed attempt, I tried to force myself to wait longer before dialling again, thinking up different things to distract me each time. I washed dishes, played Freecell on the computer, ate a small tub of icecream sitting on the floor in front of the radiator, got out the playing cards and had a game of Patience (sorry, but no it’s not called Solitaire… that’s a game with marbles!).

Half an hour ago, I sent another text message, asking how he was and whether he’d been allowed to go to the beach. It failed.
I know he’s probably fine and the issue is with his phone. If anything had happened I’d have heard by now, right? But still… aargh! I cannot wait to have him back here where I can keep an eye on him (at least while I’m not at work). One more sleep…

*Update* I have now spoken to the boyfriend via Facebook. His phone has been blocked for security reasons (pesumably because he went over a cost limit, leading them to think it was stolen), but he is fine. Good job I managed not to worry too much!

An update on the appendix situation

Thank you all for your lovely comments on yesterday’s post. After speaking to Jan last night, I was reassured that everything is looking good. He told me the surgery went well, and at the time I spoke to him he’d just started being able to feel his legs again as the general anaesthetic wore off. The downside, of course, was that he could also feel the pain from the surgery. He wasn’t allowed to eat yesterday, but today he was to be allowed soup and, if that went well, tomorrow he’ll be allowed solid foods. All going well, he will be allowed to take his original flight back with his colleagues. I’m hoping like mad that that’s the case – I don’t like to think of him on his own on a later flight having been so ill! With his colleagues around, some of whom I actually know, I feel like he’ll at least be in good hands.

little poo
little poo (Photo credit: roboppy)

On a (slightly) lighter note, after Jan informed me that he was going to have his appendix out, I googled appendicitis – as you do (or as I do anyway) – and found it that it’s caused by an infection or, more commonly, a blockage. The NHS websitte says “Some cases of appendicitis are thought to be caused by a small piece of faeces getting trapped in your appendix and causing a blockage. Bacteria in the appendix then start to multiply, causing it to fill up with pus and swell.” Other causes of the blockage include inflammatory bowel disease, such as Chron’s disease, and ulceritive colitis. Since Jan has neither of those, the most likely cause for him is probably the first one. So my boyfriend is in hospital because he got a bit of pooh in his appendix! At least a small source of amusement in amongst all the worry. (Yes, I find pooh funny… I may, in fact, be a five-year-old boy…)

I am writing this from work (but having finished working for the day, so I’m not doing anything naughty ;-)) and am about to go out for a meal with my colleagues. One less evening alone, and that much closer to having my boyfriend back home with me and I “have living, walking proof he’s all in one piece again” to quote The Pink Rachael, whose comment yesterday was absolutely spot on!