[brains, sorta]
Nov. 24th, 2004 05:13 pmIt is, in fact, a fairly major mental shift to be at work, have one's cell (mobile!) ring, appear to be a US number, and be
australian_joe.
My brain hasn't quite managed to recover from that yet. :) (I mean, phone call was a good thing, but... sudden dramatic mental shift!)
Ow. My brain hurts.
Still. Now I'm all chipper. :)
My brain hasn't quite managed to recover from that yet. :) (I mean, phone call was a good thing, but... sudden dramatic mental shift!)
Ow. My brain hurts.
Still. Now I'm all chipper. :)
no subject
Date: 2004-11-24 10:44 pm (UTC)no subject
Date: 2004-11-24 10:49 pm (UTC)no subject
Date: 2004-11-24 11:59 pm (UTC)I am guessing but do not know for sure that it works like this:
My telco says, ah, an international call to the US, and connects to a US telco. "I have a call for someone in your country. I don't understand how your system works. Will you take care of it for me? Just place the call for me and we'll pipe my part into that."
Sometimes the US provider correctly recognises that the origin of the call (for purposes of caller ID as displayed to the American phone) is a number in Australia), and displays that number.
Sometimes it deems the caller to be my Australian telco rather than me, and so displays *their* caller ID - which is "Unknown". Or perhaps it recognises that the call originated outside the US, with the same result.
Sometimes the "caller" is deemed to be the last link in the chain, ie. the US telco handling the US side of things, and displays *their* caller ID - which is a domestic US number.
There doesn't seem to be any pattern over which way it ends up.
I note with interest that when I'm in the US and calling from my Australian number via global roaming, it *always* displays my caller ID correctly. So I'm guessing it's the handover between the two domestic systems that's the issue.
no subject
Date: 2004-11-25 12:48 am (UTC)no subject
Date: 2004-11-25 01:11 am (UTC)no subject
Date: 2004-11-25 07:06 am (UTC)no subject
Date: 2004-11-25 04:48 pm (UTC)no subject
Date: 2004-11-25 05:38 pm (UTC)This also has the qualifier of "well", or else the tentative answer (which happens much less often) will have a qualifier of "I'm not entirely certain, but I think"
no subject
Date: 2004-11-25 04:49 pm (UTC)no subject
Date: 2004-11-29 01:31 am (UTC)no subject
Date: 2004-11-29 02:07 am (UTC)And... if there are questions being asked - rather than simply statements being made - why would someone answering it be a problem? I mean, not stopping if someone asks you to and/or explains that they didn't acually
want an answer would annoy me.
I think I've even seen you in question answering mode when it _was_ annoying me, but since it wasn't me you were answering the question of, I just wandered off to a different conversation. *shrug*
no subject
Date: 2004-11-29 02:57 am (UTC)no subject
Date: 2004-11-29 08:45 pm (UTC)The only examples in which I can see this applying would be if someone was attempting to have a private conversation and failing such that questions were asked too loudly, or if someone was specifically trying to determine what someone knows or does not know about something, rather than actually needing the information.
(like if one is trying to quiz a child, for example, having the other child answer isn't helpful)
no subject
Date: 2004-12-02 04:56 am (UTC)But no, I'm thinking a good deal more generally than those.
It's part of why one of my sayings is "People can usually forgive you for being wrong, but they never forgive you for being right."
no subject
Date: 2004-12-02 06:17 pm (UTC)Yeah, I thought so.
It's part of why one of my sayings is "People can usually forgive you for being wrong, but they never forgive you for being right."
Huh.
I think that I don't tend to have sufficiently concrete facts in my head often enough to run into this.