both. above we have a situation where the phone code field was blank, but the system was generating a 1 anyway. now we want to be able to have both with a 1 and without a 1. but at least you stated your need and the reason for it. So we'll move on! LOL
If the system is generating a 1 even though you didn't put a 1 in when you imported, there are several possibilities: You may have inadvertently "overridden" the phone code field during import. You may have put in a dial prefix of 91 instead of just 9 (ie: the phone code isn't actually generating the 1, it's coming from the dial prefix of the campaign).
If you want to use the omit phone code field, the entire campaign would lose that field at once. So you can no longer differentiate between which numbers should have the code and should not within the campaign. You could write a custom dialplan to add or remove the 1 based on the area code if you were willing to work that out (asterisk dial plan has an if/then function allowing conditional operation).
Alternately, you can verify that the database actually does not have a dial code on specific entries, although I am not sure vicidial will appreciate this concept at all.
Another method would be to import with an extra digit on all dial codes (this would allow the extra digit to be removed by :2 on the EXTEN:2 instead of EXTEN:1 in the dial command) and thus keep the phone_code populated but essentially ignoring a single 1 but keeping the 1 if there are two of them.
Many possibilities. Depends on whether you are ready to test import and / or check your database.