Now, this is an interesting thing
you're going to see in your lab.
What happens when messages and calls collide?
And some of you think about this.
So I'm going to grab my Android here.
If you call me right now, and I'm like, oh, my gosh.
My phone's not supposed to be ringing.
I'm in the recording studio.
And I click message you instead, and I
send you either one of the custom messages, or I send,
I'm in the recording studio.
I'll call you later, how is that stored?
Is it stored as a text or a call?
Because, technically, it's both.
I was getting an incoming call, and I rejected it
with something.
This is really important that you realize this.
I was helping one of my coworkers.
He was like, hey, there was this murder in Canada,
and it's really strange.
They keep seeing text messages in the call logs.
I was like, oh, I bet it's type 300.
And he was like, Heather, you're so weird.
How do you know that?
And I was like, type 300 is the response when
you ignore a call.
Well, guess what.
The tools won't parse that most often as a text message.
It may just parse it as calls and not show you the text
because how do you show someone a text message in a call log?
It doesn't make sense.
The database has the truth.
When you look at log type 100, that means a call.
Log type 200, MMS.
And log type 300, message--
all within that call log.
So it's really strange.
But think about all the things that people could type.
In this murder investigation, all
of the things that the person was responding with
correlated to the murder.
The tools didn't parse it because it's
hidden in a call log.
You're going to see what this looks like in your lab.