I have an iPhone so naturally all of my contacts receive iMessages from me via my phone number. Majority of these contacts do not have my email address. While my iPhone is properly syncing with the Messages Beta App on Lion every time I respond to an iMessage it comes from my email address and my contacts ask who this is. Is there a way to fix this? Does Apple plan to address this for the final version?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Messages Beta: Sending iMessages from phone number and not email address?
- Thread starter bigdawg1192
- Start date
- Sort by reaction score
This is something were they really screwed up.
Redundant contacts, conversations etc... Really, Apple?
As much as all my receiving and sending addresses are set up on my iPhone, I'd rather the service take those to just route to my Apple ID and go from there...
It's ridiculous...
Glassed Silver:mac
Redundant contacts, conversations etc... Really, Apple?
As much as all my receiving and sending addresses are set up on my iPhone, I'd rather the service take those to just route to my Apple ID and go from there...
It's ridiculous...
Glassed Silver:mac
Nope - you need to share your Apple ID with your friends. Also setup your iPhone to use your email address as your callerID for text messages - this will help tons
Go To settings on your iPhone
then messages - then click receive at
Select Caller ID and click your email addy.
That's really a shame, people communicate via phone numbers this now requires getting additional information when you get someones contact info
Well on the one hand I agree, that is what people do... right now. On the other, I see where Apple is going with this. They're trying to "untether" us from phone numbers. Only then can we move forward technologically. That is, the freedom to communicate seemlessly between any internet-connected device. Think about it... with voip, you can call anyone from any computer, tablet, ipod, whatever. There's really no reason to use the number-based voice system anymore (other than that everyone already does). The concept of a "phone number" is outdated and should be retired. Of course, cell phone companies don't want this to happen. They make a lot of money by locking people into their plans and making it hard to switch networks.
The future is internet IDs (like an apple ID). Take it with you anywhere, use it for all communication (email, voice, facetime, etc) on any device. Apple is once again ahead of the curve and trying to force change a bit early.
This is exactly what I'm thinking. There is no need for the excessive cost that we're all paying today, except for keeping rich people rich.
Where I live, I have to pay 25 cents per minute to call someone with my phone, but using Jumblo (a VoIP provider), I pay three cents a minute. Granted I need to have 3G or wifi reception for it to be useable, but it saves me a ton of money.
Also, calling landlines is free. For me, being an expat, I can't even begin to tell you how liberating it is to be able to call family and friends in my home country for free without having me or them having to be by a computer.
What happens if the person cannot be reached via iMessage? On the iPhone it would send through as a text message. If the iMessage cannot be delivered it should be sent to the users iPhone where it is then sent via text to the recipient. But have that all nicely flowing.
Similarly with the contacts coming as emails, as apposed to phone numbers, that needs to be fixed. But Im not sure how without invading phone number privacy. Ie. you cant serve someone, someone else's phone umber just because they sent that person an iMessage via email.
J.
Similarly with the contacts coming as emails, as apposed to phone numbers, that needs to be fixed. But Im not sure how without invading phone number privacy. Ie. you cant serve someone, someone else's phone umber just because they sent that person an iMessage via email.
J.
What happens now is a little red exclamation point that says the message wasn't delivered. Forwarding via email is a good solution, but it would be cool if you could link a phone number for an SMS backup as well.
I agree... you should be able to link your number to the email address so you can be reached under the same conversation by people sending from iPads/iPhones. I send an iMessage from my laptop and it comes up as my email... I send it from my phone it goes to that same person as my phone number. It should be the same both ways.
Go into iPhone settings and make sure your caller ID is set to your email address...over time replies to you will transition from your phone number to email address and all will be well in the world...
Go into iPhone settings and make sure your caller ID is set to your email address...over time replies to you will transition from your phone number to email address and all will be well in the world...
Also, don't forget to tell people [that you know have an iPhone] to text your e-mail address instead of your phone number.
I'd like to see linking the number as well. I use several different email addresses for various people and purposes; but carry only one cell phone. The cell phone number is the "common denominator". The way this is implemented, I have to use a single email address for everyone I want to text with - and oh by the way, that has to be my apple id as well.
You don't have to use a single email address. Go into the settings for iMessage, FaceTime, etc. and you will see it allows you to add additional email addresses you can be contacted at. And if you access your Apple ID account, you will see that these show up as alternative email addresses on your account.
I don't see this option under Messages, but it is available under FaceTime (IOS 5.1 Beta 3).
What's the advantage again for having Caller ID set to your apple ID instead of your phone number?
Sometimes it means that messages sent from your phone, iPad, iPod touch and computer will end up in the same message thread on the receiving end.
The problem that needs to be solved is to create a secure and reliable way to link your number to your Apple ID/email. Without a way to do this 100% securely and reliably it is not going to happen. I imagine that this is a headache that Apple don't want to deal with. I do think that they should explain / document iMessage more and highlight the benefits of setting your caller ID to your Apple ID.
Ah, thanks. I noticed as soon as I split up caller ID between my phone and computer that messages weren't syncing up.
One annoying thing that I've mentioned before is that when they're all under the same caller ID, you get alerted on your phone when a message is received on your mac.
Still think Apple needs to put a priority system in place. First mac messages then iMessage.
I really like using Mac Messages but if this won't happen in the future I might have to remove it.
Ah, thanks. I noticed as soon as I split up caller ID between my phone and computer that messages weren't syncing up.
One annoying thing that I've mentioned before is that when they're all under the same caller ID, you get alerted on your phone when a message is received on your mac.
Still think Apple needs to put a priority system in place. First mac messages then iMessage.
I really like using Mac Messages but if this won't happen in the future I might have to remove it.
For me, the phone doesn't get any alerts if the Messenger app is active on the computer, which was quite annoying when I went out last Friday having left the app active on the computer...
Hmm, this is strange, I'd love to know what settings you have on your phone/osx messages.
It was like this from the very beginning. I downloaded the beta, installed it, entered my Apple ID and started sending messages. I got a bit surprised when my phone wasn't vibrating from receiving messages so I got worried that it didn't sync the messages at all - but they did. And being in a very active chat a bit later on, I noticed my phone going crazy as soon as I put Messages in the background, and calmed down as Messages was the active app...