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

Developer

Forums

Forums:

Trying to add a custom vcard extension to the Pantech device for Preffered number fails. 

Case1 : 
Added this vCard from sample APP: 
BEGIN:VCARD 
VERSION:3.0 
N:;NEW 
FN:NEW 
TEL;TYPE=CELL:4 
TEL;TYPE=HOME,PREF:8583331111 
TEL;TYPE=WORK:1999 
X-VZW-NWFLDS:NO 
X-VZW-SOURCEID:VZW 
X-VZW-CONID:NOR 
REV:979537517 
END:VCARD 

 

where 8583331111preferred is set as preferred number on device. 

And when we read this back from the device, the vCard looks like this. 
BEGIN:VCARD 
VERSION:3.0 
N:;NEW 
FN:NEW 
TEL;TYPE=CELL:4 
TEL;TYPE=PREF;TYPE=HOME:8583331111 
TEL;TYPE=WORK:1999 
X-VZW-NWFLDS:NO 
X-VZW-SOURCEID:VZW 
X-VZW-CONID:NOR 
REV:979537517 
END:VCARD 




Case 2: 

We created a new contact in the device (native), and when tried to read this record, the vCard returned was 



BEGIN:VCARD 

VERSION:3.0 

N:;Dev 

FN:Dev 

TEL;TYPE=CELL:222225 

TEL;TYPE=HOME:555888 

TEL;TYPE=WORK:5555 

X-VZW-NWFLDS:NO 

X-VZW-SOURCEID:VZW 

X-VZW-CONID:NOR 

REV:979545476 

END:VCARD 



Note: We have selected 222225 as preferred number on device. But in VCARD it is sent as normal telephone number.

Hi Anand, 
 
CDM8999 implements OEM contact based on pim_IContact with Pantech’s own field definition per Verizon UI. BMP IRecordStore is not compatible with Verizon UI implemented in CDM8999. IRecordStore itself functions as separate vCard IO but it’s not fully interact with OEM UI per above reasons Solution: Use pim_IContact with appropriate field names for full access of OEM UI 
Thanks, Mahesh

Hi Anand, 
 
CDM8999 implements OEM contact based on pim_IContact with Pantech’s own field definition per Verizon UI. BMP IRecordStore is not compatible with Verizon UI implemented in CDM8999. IRecordStore itself functions as separate vCard IO but it’s not fully interact with OEM UI per above reasons Solution: Use pim_IContact with appropriate field names for full access of OEM UI 
Thanks, Mahesh