I am surprised I could not find anything on this issue, I just got off the phone with Apple product specialists (while ATT was on the phone) and they verified and documented the problems.
1. When you change the "settings/phone/Show My Caller ID" to "off" so no one can see your number, you CANNOT override it for specific calls. Normally, I used *82 as a phone prefix in the directory (or manually) to allow my number to sent to friends. This DOES NOT WORK! If you set the Show Caller ID off there is no way to override it, same goes for turning it on. You cannot turn it off selectively. IPhone seems to ignore any(most?) LASS(Local Area Signaling Services) prefix codes. Apple says that the *82 is the phone companies codes and the IPhone does not support it, however ATT says *82 is what to use. Bottom line: If you want default privacy for most outgoing calls and want to allow your number to go through for some calls, automatically or manually, this cannot be done! I don't really care what options we are given but I would like the same functionality as all other phones in this area of privacy. I suggested that the contacts (and mac Address Book) provide a setting for a contact to be sent your number anyway if calling iPhone is set to no send your ID by default.
2. If you store a contact and the number contains an LASS code such as *82 in front of the phone number, when that call comes in iPhone DOES NOT match up the caller with the contact entry, so no name, picture or sound to identify the caller. All other phones support this. Again, this always worked on other phones.
See this on LASS (Local Area Signalling Services):
http://www.tech-faq.com/lass-codes.shtml
http://www.asociacion-aecsi.es/doc/M...ss-codes.shtml
Notes:
[7] - *82 (1182) has been mandated to be the nationwide code for "Send CLID info regardless of the default setting on this phone line."
*82 is a standard US (and I think international) code for all phone systems including landlines. This code can be used on almost all phones. For instance, my mother has calls with no caller ID blocked so I have to use *82. I have about 200 contacts many with *82, if you change them to #31# then they would ONLY work on a GSM line. Not good.
Also, I tested #31# as a prefix in the contacts and when you call iPhones from that number the contact is still not displayed so #31# (or any prefix) voids the contacts entry (see item 2 above)..
I don't know about you but this is a big privacy issue for me. If you call a store, etc. they get your number and can send junk mail, calls, etc. I normally had ATT set Caller ID block and have *82 added for certain entries I wanted unblocked.
BTW, there are at least 2 Cingular phones (one is the 3100) that has the ID block in the phone as well but it ALLOWS you to set overrides in the contact directory selectively.
Apple put these in as feature requests. I think item 1 was a big oversight and item 2 is a downright bug.
Some suggested to use *67 to block calls which is not a solution if the phone blocks by default since you can't do the reverse (unblock a call) and... due to bug #2 you can't put *67 in a contacts and have the call recognized during incoming. Anyone else who does not like these problems please call Apple Iphone TS to let them know.
Don't get the wrong idea, other than this problem (and 16 hours on the phone the first weekend to get 2 Iphones activated) my wife and I love the phones and will buy rev2. We will NEVER go back to "old" phones.
Update and work arounds:
1. If I set the iPhone to block all calls, and use the GSM code *31# in the contacts, the call is unblocked for that number. This does work and I can replace *82 with *31# in all the affected contacts. But.. It does not provide the callers name etc for an inbound call. Also tried to *31#+ (added +) but nogo. See next item.
2. Since using a prefix in a contact prevents the contact from being displayed during an incoming call, I ADDED another number to that contact without the prefix. In other words, for a person I have 2 mobile numbers, *31#1408-123-4567 and 1408-123-4567. iPhone matched the second number and displays the callers name, etc. Still a bug but now I have a workaround. I will call Apple with the updated bug info.
1. When you change the "settings/phone/Show My Caller ID" to "off" so no one can see your number, you CANNOT override it for specific calls. Normally, I used *82 as a phone prefix in the directory (or manually) to allow my number to sent to friends. This DOES NOT WORK! If you set the Show Caller ID off there is no way to override it, same goes for turning it on. You cannot turn it off selectively. IPhone seems to ignore any(most?) LASS(Local Area Signaling Services) prefix codes. Apple says that the *82 is the phone companies codes and the IPhone does not support it, however ATT says *82 is what to use. Bottom line: If you want default privacy for most outgoing calls and want to allow your number to go through for some calls, automatically or manually, this cannot be done! I don't really care what options we are given but I would like the same functionality as all other phones in this area of privacy. I suggested that the contacts (and mac Address Book) provide a setting for a contact to be sent your number anyway if calling iPhone is set to no send your ID by default.
2. If you store a contact and the number contains an LASS code such as *82 in front of the phone number, when that call comes in iPhone DOES NOT match up the caller with the contact entry, so no name, picture or sound to identify the caller. All other phones support this. Again, this always worked on other phones.
See this on LASS (Local Area Signalling Services):
http://www.tech-faq.com/lass-codes.shtml
http://www.asociacion-aecsi.es/doc/M...ss-codes.shtml
Notes:
[7] - *82 (1182) has been mandated to be the nationwide code for "Send CLID info regardless of the default setting on this phone line."
*82 is a standard US (and I think international) code for all phone systems including landlines. This code can be used on almost all phones. For instance, my mother has calls with no caller ID blocked so I have to use *82. I have about 200 contacts many with *82, if you change them to #31# then they would ONLY work on a GSM line. Not good.
Also, I tested #31# as a prefix in the contacts and when you call iPhones from that number the contact is still not displayed so #31# (or any prefix) voids the contacts entry (see item 2 above)..
I don't know about you but this is a big privacy issue for me. If you call a store, etc. they get your number and can send junk mail, calls, etc. I normally had ATT set Caller ID block and have *82 added for certain entries I wanted unblocked.
BTW, there are at least 2 Cingular phones (one is the 3100) that has the ID block in the phone as well but it ALLOWS you to set overrides in the contact directory selectively.
Apple put these in as feature requests. I think item 1 was a big oversight and item 2 is a downright bug.
Some suggested to use *67 to block calls which is not a solution if the phone blocks by default since you can't do the reverse (unblock a call) and... due to bug #2 you can't put *67 in a contacts and have the call recognized during incoming. Anyone else who does not like these problems please call Apple Iphone TS to let them know.
Don't get the wrong idea, other than this problem (and 16 hours on the phone the first weekend to get 2 Iphones activated) my wife and I love the phones and will buy rev2. We will NEVER go back to "old" phones.
Update and work arounds:
1. If I set the iPhone to block all calls, and use the GSM code *31# in the contacts, the call is unblocked for that number. This does work and I can replace *82 with *31# in all the affected contacts. But.. It does not provide the callers name etc for an inbound call. Also tried to *31#+ (added +) but nogo. See next item.
2. Since using a prefix in a contact prevents the contact from being displayed during an incoming call, I ADDED another number to that contact without the prefix. In other words, for a person I have 2 mobile numbers, *31#1408-123-4567 and 1408-123-4567. iPhone matched the second number and displays the callers name, etc. Still a bug but now I have a workaround. I will call Apple with the updated bug info.
