It sounds to me like you have at least a 1 to many relationship. One person can make many calls. If you have the ability to store conference calls then you have a many to many relationship. One call can include many people.
this is like a call's record.
Person (Nº5) made a call (Nº: 1)
Person (Nº5) made a call (Nº: 2)
Person (Nº7) made a call (Nº: 3)
One person can make lots of call's but 1 call can only be made form 1 person.
(Just edited) Yep... its 1 to N (my mistake) so is bether go for creating 3 tables??....
A,B,C,D,E,F... it's more field's... like A=Resolved, B=Private....
What i mean with this is if a query to a table with lots of field's is faster then a query to a table with 2 field's but have to open another table (3NF).