Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Can BREW application get phone number associated with the device?

got this from an example...
...
char * numBegin;
...
// Get our phone number.
ITAPI_GetStatus(pMe->m_pITAPI, &ts);
numBegin = ts.szMobileID + 5;
if (*numBegin != 0)
STRCPY(pMe->m_szMyNumber, numBegin);
didn't test it on a real phone though... there are a lot of issues when using itapi that i haven't figured out yet. If you ever try it, let me know if this works... :)

got this from an example...
...
char * numBegin;
...
// Get our phone number.
ITAPI_GetStatus(pMe->m_pITAPI, &ts);
numBegin = ts.szMobileID + 5;
if (*numBegin != 0)
STRCPY(pMe->m_szMyNumber, numBegin);
didn't test it on a real phone though... there are a lot of issues when using itapi that i haven't figured out yet. If you ever try it, let me know if this works... :)

ITAPI_GetStatus.szMobileID is not the handset phone number, it is actually the MIN of the handset. This may or may not be the handset phone number. Where the MIN is not the phone number, it is not possible to retrieve the handset phone number as it is not stored on the handset, ie. it is allocated by the network.

ITAPI_GetStatus.szMobileID is not the handset phone number, it is actually the MIN of the handset. This may or may not be the handset phone number. Where the MIN is not the phone number, it is not possible to retrieve the handset phone number as it is not stored on the handset, ie. it is allocated by the network.

I was under the impression that the MIN corresponded to the actual phone number.. at least until LNP rolls out. Is this not the case? :confused:

I was under the impression that the MIN corresponded to the actual phone number.. at least until LNP rolls out. Is this not the case? :confused:

Well, at least here the MIN corresponds to the phone number, with some minor differences that have to be worked out with the local operators...

Well, at least here the MIN corresponds to the phone number, with some minor differences that have to be worked out with the local operators...

warpig,
The MIN is not guaranteed to be the phone number. Some operators do use the phone number as part of the MIN, but some don't

warpig,
The MIN is not guaranteed to be the phone number. Some operators do use the phone number as part of the MIN, but some don't

Can the MIN be used as a unique ID? that is, will no 2 phones have the same MIN? I remember reading before that a unique id wasn't supported, but is there any reason why the MIN would not work?
thanks,
-tyndal

Can the MIN be used as a unique ID? that is, will no 2 phones have the same MIN? I remember reading before that a unique id wasn't supported, but is there any reason why the MIN would not work?
thanks,
-tyndal

Meanwhile I have contacted BREW support, and that what they said:
"In the 15 digit (characters) TAPIStatus.szMobileID obtained using ITAPI_GetStatus(), the first 3 digits correspond to the Mobile Country Code (MCC). For example, the MCC for the United States is 310. The subsequent 2 digits correspond to the Mobile Network Code (MNC).The combination of the MCC and the MNC uniquely identify the carrier.
The rest 10 digits correspond to the phone number assigned to that handset.
Please note that some OEMs may pass 00000 as the MCC-MNC in TAPIStatus.szMobileID, and others may provide more meaningful values.
To obtain the MCC, MNC values for a specific carrier, you will need to contact the carrier."

Meanwhile I have contacted BREW support, and that what they said:
"In the 15 digit (characters) TAPIStatus.szMobileID obtained using ITAPI_GetStatus(), the first 3 digits correspond to the Mobile Country Code (MCC). For example, the MCC for the United States is 310. The subsequent 2 digits correspond to the Mobile Network Code (MNC).The combination of the MCC and the MNC uniquely identify the carrier.
The rest 10 digits correspond to the phone number assigned to that handset.
Please note that some OEMs may pass 00000 as the MCC-MNC in TAPIStatus.szMobileID, and others may provide more meaningful values.
To obtain the MCC, MNC values for a specific carrier, you will need to contact the carrier."

ziemowit
BREW support are wrong on this. Yes, the first 5 digits are the MCC and the MNC, but the last 10 are not guaranteed to be the phone number. The last 10 digits may be the phone number on some carriers, but others will use a arbitrary number.
The reason this is done is to simplify provisioning and front-of-house administration, where a handset can be activated by network based systems without need for programming of the phone.
You need to check with the carriers that you plan to deploy your app to.

ziemowit
BREW support are wrong on this. Yes, the first 5 digits are the MCC and the MNC, but the last 10 are not guaranteed to be the phone number. The last 10 digits may be the phone number on some carriers, but others will use a arbitrary number.
The reason this is done is to simplify provisioning and front-of-house administration, where a handset can be activated by network based systems without need for programming of the phone.
You need to check with the carriers that you plan to deploy your app to.

Quote: The last 10 digits may be the phone number on some carriers, but others will use a arbitrary numberWould you happen to know if the arbitrary number would be unique for a specific carrier?
What I really want to know is if there is a way to obtain (via a BREW API) a unique identifying number for a phone ... and it doesn't need to be a phone number.
Thanks,
:Paul
p.s., If anyone has real word experience with a carrier as to what gets returned in TAPIStatus.szMobileID I'd love to hear about it ... unfortunately, I'm working on a little skunk works project (with limited funds and all that that entails) and only have access to the BREW SDK.

Quote: The last 10 digits may be the phone number on some carriers, but others will use a arbitrary numberWould you happen to know if the arbitrary number would be unique for a specific carrier?
What I really want to know is if there is a way to obtain (via a BREW API) a unique identifying number for a phone ... and it doesn't need to be a phone number.
Thanks,
:Paul
p.s., If anyone has real word experience with a carrier as to what gets returned in TAPIStatus.szMobileID I'd love to hear about it ... unfortunately, I'm working on a little skunk works project (with limited funds and all that that entails) and only have access to the BREW SDK.

FYI, the first five digits are coming back as zero on most handsets, and in some cases the carriers are filling in values that are not in the range specified by tue ITU. Don't count on anything aside from the last 10 digits.

FYI, the first five digits are coming back as zero on most handsets, and in some cases the carriers are filling in values that are not in the range specified by tue ITU. Don't count on anything aside from the last 10 digits.