WEBVTT

00:00.000 --> 00:09.440
This is dedicated to all the hackers and the crackers, to the hackers and the crackers.

00:09.760 --> 00:15.520
I see in binary, I speak source code, step on my toes, I'll post a million jpegs of you

00:15.520 --> 00:20.800
in a fag pose, in your digital stance, getting firewalls hoes, cause I'm riding the net in

00:20.800 --> 00:26.440
my six foes, I was a dick with my 56, now with my cable I'm able to get that stable,

00:26.440 --> 00:31.740
on the out, my name is Ace and I'm a Leo, on the digital highway, my name is Neo and

00:31.740 --> 00:37.240
I'm a hero, in a flash, I'll screw you on burning Dreamcast, you need some ISO, let me through

00:37.240 --> 00:42.680
my hard drive rifle, our exchange you could never stifle, and a digital hug, you just caught

00:42.680 --> 00:48.940
the love bug, I bootlegged your CD, I caused the fight between Un and Jay-Z, cause CG, it's

00:48.940 --> 00:53.380
all gonna be free, whether we take it by force or we take it nicely, you feel that rattle

00:53.380 --> 00:58.040
your bones, when I tell you we just hacked out Jones, and NASDAQ leaves your fight on

00:58.040 --> 01:03.100
your back, cause I am he who loves to hack and crack, cause I am he who loves to hack and

01:03.100 --> 01:08.980
crack, this is dedicated to the hackers and the criminals, their real phones, source code,

01:09.160 --> 01:14.860
ISO, RAM, SIFC, good afternoon, and welcome to Binary Revolution Radio number 110.

01:15.480 --> 01:22.660
Today's air date, August 23rd, 2005, and Strom is back with us, he's been released by North Korea,

01:22.660 --> 01:26.120
for attempting to hacksaw their phone system.

01:26.460 --> 01:27.380
Oh, is that where I was?

01:27.880 --> 01:31.160
Yes, we actually had a couple of issues with you last week, I think North Korea is a new

01:31.160 --> 01:36.220
one, right now I think we actually put you down, last week you put you down in Camp X3 in

01:36.220 --> 01:36.780
Guantanamo.

01:37.320 --> 01:38.720
Ah, I see.

01:39.520 --> 01:39.740
Yeah.

01:40.300 --> 01:43.380
I had a blindfold on the whole time, I really didn't know where I was, so.

01:44.120 --> 01:50.120
Yes, he was with a national marionette version of Kim Jong Il, or whatever it is, I don't

01:50.120 --> 01:52.320
even know how to pronounce his damn name, I just see it online all the time.

01:53.520 --> 01:59.200
Yeah, so, this is another episode of Binary Revolution Radio, still alive and kicking,

02:00.380 --> 02:01.960
and, you know, get Strom back.

02:02.680 --> 02:07.940
No special guest this week, because we're just going to kick back and rehash our DEF CON

02:07.940 --> 02:12.620
presentation, because more than a few people requested it, and we decided to give the masses

02:12.620 --> 02:13.320
what they want.

02:13.560 --> 02:17.020
Probably these ten people that said they wanted it are the only ten people that want to listen

02:17.020 --> 02:22.440
to it, but, you know, we're going to try to, it's a hefty presentation, but we're going

02:22.440 --> 02:22.900
to try.

02:23.940 --> 02:27.500
Real clock, like the guy in those FedEx commercials from the 80s.

02:28.060 --> 02:28.800
Yes, there we go.

02:29.060 --> 02:29.300
God.

02:29.680 --> 02:31.320
FedEx, or was that, yeah, no, that was FedEx.

02:31.380 --> 02:32.120
That was FedEx, yeah.

02:33.560 --> 02:34.000
Oh, God.

02:34.160 --> 02:35.380
Actually, isn't he dead?

02:35.920 --> 02:38.280
I don't recall whether that guy who talks really fast is dead.

02:38.660 --> 02:39.960
I think he is, sadly.

02:40.540 --> 02:42.980
Well, Moog died on Monday.

02:44.020 --> 02:45.120
Oh, yes, yes, Moog.

02:45.360 --> 02:47.540
Well, for, yeah, we can talk about this.

02:47.560 --> 02:50.480
It's a little kind of news related, and it's, it's hacking related.

02:50.940 --> 02:54.900
You want to go give a, not presentation, but a little introduction on him?

02:55.420 --> 02:55.720
Yes.

02:56.440 --> 03:00.960
Robert Moog, I think was Robert, was the guy who invented the Moog synthesizer.

03:01.820 --> 03:03.780
The first synthesizer ever.

03:04.820 --> 03:08.400
Which wasn't necessarily the first, but was, I think, the first commercially successful

03:08.400 --> 03:08.760
one.

03:09.960 --> 03:11.000
True, that could be it.

03:11.060 --> 03:11.620
That could be the first.

03:11.720 --> 03:12.440
I'm not sure.

03:13.000 --> 03:16.320
He basically, he did a lot of work with it.

03:18.600 --> 03:22.820
Basically, they really hail him as the founder of synthesizers.

03:23.460 --> 03:25.980
I can't, that word never rolls off the tongue easy with me.

03:26.500 --> 03:26.940
Synthesizers.

03:27.500 --> 03:27.700
Yes.

03:28.100 --> 03:28.500
Synthesizers.

03:30.240 --> 03:31.560
That's right.

03:31.720 --> 03:33.660
He's a cool, it was a very cool story.

03:33.660 --> 03:39.720
I was reading something on news.pbk, news.bbc.co.uk about him, and he,

03:39.720 --> 03:42.360
he, he was, he was a very interesting character.

03:44.040 --> 03:47.240
Of course, he doesn't have any, you know, the other question is, I, I always wondered

03:47.240 --> 03:53.260
what's up with these synthesizer people who have weird last names like Arp and Moog.

03:54.440 --> 03:56.720
Arp, Arp was the, was the guy's initials.

03:56.760 --> 03:58.320
It was Aaron Perlman or something.

03:58.740 --> 03:59.120
Oh, really?

03:59.220 --> 04:00.180
I thought it was his last name.

04:00.260 --> 04:01.280
I thought it was something Arp.

04:01.840 --> 04:03.120
Yeah, no, it was the initial.

04:03.620 --> 04:04.420
I stand corrected.

04:05.340 --> 04:06.520
Anyway, we're drifting already.

04:06.660 --> 04:07.740
Boy, this is, this is going to get bad.

04:07.800 --> 04:10.840
See, this is why, this is why we need like a third person here to keep us on track.

04:12.540 --> 04:15.240
We have a couple of housekeeping things tonight.

04:15.240 --> 04:21.260
Right, now we have CID, C-I-D, and he tells us the street name for the Denver 2600 troop

04:21.260 --> 04:27.100
is Arapahoe, and he says, like the Native Americans, at which point I say, what Native Americans?

04:27.400 --> 04:28.900
Also, like the county.

04:30.640 --> 04:35.780
Well, if you live in Denver, well, Denver is in Arapahoe County, of course.

04:36.620 --> 04:38.520
Oh, I don't know that.

04:39.020 --> 04:39.320
I do.

04:39.320 --> 04:40.120
I live in Essex.

04:40.500 --> 04:41.320
I've been to Denver.

04:41.840 --> 04:45.200
I live in Essex, and then I go into Boston, which is Middlesex.

04:45.640 --> 04:48.980
I live in Los Angeles County, and then I go to school in Los Angeles County, and then

04:48.980 --> 04:50.400
I go to work in Los Angeles County.

04:51.460 --> 04:54.400
Los Angeles County is just amazingly huge, so, yeah.

04:55.180 --> 04:56.720
As we established two weeks ago, didn't we?

04:56.720 --> 04:58.120
Yeah, I think that was, yeah.

04:58.260 --> 04:59.240
That's where I learned that.

05:00.680 --> 05:03.340
And we have, I'm not, I'm going to butcher this name.

05:03.460 --> 05:07.700
He included some type of pronunciation key, but I couldn't understand it.

05:07.700 --> 05:09.780
It's RUACH.

05:10.120 --> 05:13.640
It's E-capitalized U, so I guess where the emphasis is.

05:14.280 --> 05:18.360
And he's our current leader for the Youngest Listener Contest, as he is 12.

05:19.180 --> 05:22.440
So, congratulations, I guess, for being young or something.

05:22.980 --> 05:27.360
Yes, congratulations on listening at such a young age and expanding your horizons and

05:27.360 --> 05:28.920
blah, blah, blah, blah, blah, blah.

05:29.080 --> 05:30.060
All that stuff.

05:30.600 --> 05:31.560
Do you have any housekeeping tonight?

05:31.980 --> 05:32.820
I certainly do.

05:32.820 --> 05:37.260
I would like to announce that I'm going to start doing a segment, or at least try to

05:37.260 --> 05:39.160
start doing a segment on the show, where I review music.

05:40.820 --> 05:41.640
And what I would like to do...

05:41.640 --> 05:43.200
Completely unrelated to hacking, but we won't get into that.

05:43.540 --> 05:48.300
Well, no, I mean, it is sort of semi-related, because this is Binary Evolution Radio, I

05:48.300 --> 05:53.100
figure, and part of the Binary Evolution is the availability of all sorts of cool music

05:53.100 --> 05:53.960
for free online.

05:54.880 --> 05:54.960
True.

05:54.960 --> 05:59.660
We kind of do this already with our closing music, but it would be nice to have people

05:59.660 --> 06:02.540
actually send us songs and have us review them.

06:03.500 --> 06:03.800
Indeed.

06:04.040 --> 06:07.720
And actually, this is where it all sort of stemmed from, because we were running out of...

06:07.720 --> 06:13.860
I was sick and tired of actually just randomly going around and picking out music from, once

06:13.860 --> 06:15.040
again, epitonic.com.

06:15.580 --> 06:17.340
It's a really fun site to play around with.

06:18.180 --> 06:21.880
So, I just, you know, Strong came up to me and said, hey, why don't I do this?

06:21.880 --> 06:26.960
And I was like, ah, it sounds weird, but actually, no, we need music, so go right ahead.

06:27.500 --> 06:27.700
Yeah.

06:27.960 --> 06:33.620
So, anyone out there, if you're in a band or you write music or whatever, and you'd like

06:33.620 --> 06:37.300
to let us review it, at least, send it to...

06:37.300 --> 06:38.620
Do we have a place for them to send it?

06:40.880 --> 06:42.660
Just send it to you right now, I think.

06:43.040 --> 06:46.120
Yeah, just send it to me directly, strongcarlson at gmail.com.

06:48.280 --> 06:50.400
Or, yeah, radio.binrev.com.

06:50.400 --> 06:56.120
Don't use that, because I don't think the space on it can handle the large amount of

06:56.120 --> 06:56.780
files, so...

06:56.780 --> 07:00.640
Or get in touch with me first, and we'll figure out a way to transfer the file or something.

07:01.420 --> 07:01.580
Yes.

07:01.640 --> 07:06.380
Well, we'll find a way to get your music, and we'll include it on the show if it's good.

07:06.800 --> 07:06.960
Yeah.

07:06.960 --> 07:09.320
If it's up to Strom's insanely high standards.

07:10.000 --> 07:14.180
Well, I'll just do a review of it, you know, and my review, of course, is no indication as

07:14.180 --> 07:15.780
to whether or not you should actually listen to it.

07:15.780 --> 07:21.500
So even if I say it sucks, download it and listen to it, and Strom's going to be in a

07:21.500 --> 07:22.480
little director's chair.

07:23.120 --> 07:23.320
Yeah.

07:23.320 --> 07:24.260
And you're going to say, it stinks!

07:25.740 --> 07:26.620
A little balding.

07:26.840 --> 07:27.920
It's going to sound like a...

07:27.920 --> 07:29.040
Oh, God, what's the guy's name?

07:31.480 --> 07:32.100
Jay Sherman.

07:32.300 --> 07:32.600
That's what it is.

07:32.600 --> 07:33.280
Yeah, Jay Sherman.

07:33.640 --> 07:34.220
The critic, yeah.

07:34.660 --> 07:35.720
Yeah, I forget who was the voice.

07:35.760 --> 07:36.720
John Lovett, that's it.

07:36.800 --> 07:37.020
Okay.

07:37.720 --> 07:38.320
Also balding.

07:39.060 --> 07:40.100
Yes, also balding, indeed.

07:41.320 --> 07:41.660
Okay.

07:41.840 --> 07:42.220
Is that it?

07:42.220 --> 07:48.540
So, yeah, and preferably, you know, if you've got like a demo disc or something with a bunch

07:48.540 --> 07:54.380
of songs on it, I'd love to review that, or if not, just one song will do, and I'll try

07:54.380 --> 07:55.160
and review the one song.

07:56.780 --> 07:57.480
Sounds like a plan.

07:58.780 --> 07:59.220
All right.

07:59.420 --> 08:00.700
I guess we should go into email now.

08:00.860 --> 08:01.600
Do you think we should go into email?

08:02.060 --> 08:05.980
I think we should go into email as soon as I put the pasta sauce on this pasta.

08:05.980 --> 08:33.060
Anyway, our first email tonight is from DeBeave, from Telefreak.com fam, or Telefreak.org, whatever

08:33.060 --> 08:33.380
it is.

08:33.380 --> 08:35.040
He says, woo, go Perl.

08:35.640 --> 08:38.380
There was one part of the show in which you discussed reporting with Perl.

08:38.500 --> 08:41.200
Great thing to check out is PDF API 2.

08:41.580 --> 08:43.920
This allows you to create PDF files on the fly.

08:44.640 --> 08:49.460
Granted, it takes a bit of playing around to get with, to get, but it is nice.

08:50.420 --> 08:55.440
Besides, we all know that managers love the PDF format, and I will fully agree with that,

08:55.500 --> 08:59.020
that managers love PDF, and developers love PDF, too, so we'll go into this.

08:59.020 --> 09:08.040
PDF API 2 is pretty cool, and I find it's a lot easier to use than PHP's PDF library.

09:08.180 --> 09:09.500
I still have nightmares.

09:11.560 --> 09:16.540
In reality, that's really not saying much that it's better than PHP, but we won't get into that.

09:16.840 --> 09:17.960
Like being the tallest midget.

09:18.520 --> 09:19.120
Yeah, exactly.

09:19.260 --> 09:19.820
There we go.

09:19.820 --> 09:24.880
So, one of the things I do like about Perl, and for PDF, that matter, is the forms function,

09:25.520 --> 09:31.020
and I've been really fooling around with that at work, because, once again, managers love PDFs,

09:31.020 --> 09:36.900
and I like to make little pre-created forms where it's just, you know, you just have to fill it out.

09:36.980 --> 09:43.200
Basically, what you do is you create a PDF, and then you fill in all kinds of little text boxes that are assigned field names,

09:43.800 --> 09:48.960
and you can fill all kinds of, you know, dynamic data into there, and it's a lot of fun.

09:49.480 --> 09:55.180
I've been trying to automate a lot of stuff with that at work, and it's gone over amazingly well,

09:55.180 --> 10:01.020
and with PDF, it can be basically faxed, emailed, you know, printed out, anything you want.

10:02.100 --> 10:07.200
It's a whole lot easier than designing the form in your program, but it's a little less cooler,

10:07.560 --> 10:11.600
because you do it, it's all WYSIWYG, that's the big plus about it, you know.

10:11.740 --> 10:13.880
But, once again, you know, what else are you going to use?

10:13.960 --> 10:14.240
Word?

10:15.000 --> 10:17.200
I just have nightmares about that.

10:18.880 --> 10:21.340
Our next email tonight is Chuck in Maryland.

10:21.680 --> 10:22.280
Do you want me to read this one?

10:22.900 --> 10:23.680
No, sure, go right ahead.

10:23.980 --> 10:24.260
Okay.

10:25.180 --> 10:25.980
Chuck writes,

10:26.580 --> 10:28.380
Dear Black Ratchet and Strom Carlson,

10:28.500 --> 10:29.120
I like the show.

10:29.220 --> 10:29.980
Keep up the good work.

10:30.540 --> 10:32.620
I'm glad that you spent last week talking about Perl.

10:32.880 --> 10:35.160
Perl is one of our greatest weapons for automating tasks.

10:35.660 --> 10:43.600
I love how you can write a little Perl code to piece together other tools and modules to do something fairly complicated.

10:44.180 --> 10:46.880
One of my favorite features of Perl is the backtick syntax,

10:47.100 --> 10:50.040
which will easily run any command line tool with any command line options,

10:50.340 --> 10:52.040
and put the output into a Perl variable.

10:52.040 --> 10:57.560
Then you can parse the output with Perl's powerful text parsing capabilities to determine if the command was successful,

10:57.900 --> 11:00.800
and if necessary, pull out information needed for the next command.

11:01.080 --> 11:02.200
In short, it rocks.

11:02.920 --> 11:06.960
Anyway, I just wanted to point this out in case some listeners are not aware of this powerful feature.

11:06.960 --> 11:07.820
Have a good one.

11:07.820 --> 11:17.200
And I thought there was more to that, so I'm going to go edit out that gap right there.

11:17.620 --> 11:19.040
Also edit out the part where I stumbled.

11:19.040 --> 11:19.880
So, yeah.

11:21.260 --> 11:27.740
Anyway, Chuck, one of the – it's cool with, like, the backtick syntax.

11:27.940 --> 11:29.480
I'm just stumbling over words tonight.

11:29.900 --> 11:33.680
It's cool with the backtick feature, and it's a cool feature,

11:33.680 --> 11:39.680
but there are tons of tutorials online that just list, like, line after line of caveats about it.

11:39.680 --> 11:43.580
But it's a whole, you know, sending – you've got to really watch your back

11:43.580 --> 11:48.380
and make sure everything is scrubbed up if you're ever taking user input and putting it into a –

11:48.380 --> 11:50.220
wouldn't that be really watch your backtick?

11:50.860 --> 11:51.260
Yes.

11:51.540 --> 11:53.600
Ooh, aren't we getting fancy tonight?

11:53.880 --> 11:54.300
Oh, yes.

11:54.960 --> 11:55.340
Yes.

11:55.520 --> 11:56.780
Yes, watch your backticks.

11:57.760 --> 12:02.500
Another – it's a – the safer way that people recommend is the system function,

12:02.500 --> 12:07.420
which is, you know, it's basically system, and, you know, you put your – it's the same thing.

12:07.500 --> 12:10.680
It doesn't actually write it out to a variable, but what I usually do in it

12:10.680 --> 12:15.160
is I usually write the output to a file, at which point I can safely muck about

12:15.160 --> 12:18.840
and rip everything apart and put it back together and grab what I need to it

12:18.840 --> 12:21.860
and then run the next command, much like you would do in the backtick syntax.

12:22.720 --> 12:28.180
So it doesn't actually – you know, it's not as simple as using the backtick,

12:28.180 --> 12:32.160
but it's a lot safer, and it has a lot of more sanity checks with it.

12:32.900 --> 12:36.280
And I'd just like to point out there are tons of powerful features in Perl.

12:36.380 --> 12:37.360
You just need to find them.

12:38.560 --> 12:42.560
Another thing I noticed in your email is how you were just saying how Perl just takes

12:42.560 --> 12:45.500
all kinds of small bits, and you can string them together and make powerful utilities.

12:46.900 --> 12:49.780
That's the entire Unix idea right there.

12:50.920 --> 12:54.880
It's, you know, all just designed to have all kinds of small little utilities.

12:54.880 --> 12:57.260
You string them together, and you make this giant thing,

12:58.280 --> 13:00.380
and that way you don't need to include all the bloat.

13:02.500 --> 13:03.780
So, what, bloat is bad?

13:03.900 --> 13:05.140
No, this is a new concept.

13:05.700 --> 13:06.560
Yeah, bloat is.

13:06.880 --> 13:10.400
No, it was the old concept that apparently people forgot in the 1980s

13:10.400 --> 13:11.440
when they were designing Windows.

13:13.220 --> 13:14.320
Yeah, we won't get into that.

13:14.320 --> 13:16.720
That's another show topic entirely.

13:18.240 --> 13:23.240
Anyway, our homework assignment last week was to send in your Apple experiences.

13:23.640 --> 13:25.540
And, boy, did we receive quite a few responses,

13:26.220 --> 13:28.080
most of which varied from neutral to positive.

13:28.200 --> 13:31.780
We didn't actually get a scathing review of Apple in the entire week,

13:31.820 --> 13:33.760
which I was quite surprised about.

13:33.760 --> 13:37.800
But for those of you who, yeah, Sue, well, you already did yours.

13:37.860 --> 13:38.940
You kind of inspired this.

13:39.400 --> 13:41.160
Well, no, I've got an even more scathing review now.

13:41.780 --> 13:43.040
What, have you got a more scathing review?

13:43.220 --> 13:43.600
Oh, yeah.

13:43.780 --> 13:44.480
What happened now?

13:44.660 --> 13:45.620
We'll have to go over that.

13:45.800 --> 13:47.600
We'll do that in your personal hacking stories.

13:47.900 --> 13:48.160
Okay.

13:49.760 --> 13:52.680
Right now, out of the, we got like about ten or so,

13:52.720 --> 13:54.580
and I picked the most two I'm using on the air.

13:54.580 --> 13:57.920
One positive and the most negative one we could find,

13:58.060 --> 13:59.920
which was not too negative in the first place.

13:59.920 --> 14:02.240
And I just want to say thank you for everyone who wrote in.

14:03.460 --> 14:07.060
I'll go read the, you know, Life Warped, who's our first email.

14:07.340 --> 14:09.640
And he says, I've abused most of my products.

14:09.740 --> 14:12.280
I had an iPod mini that was carried around for nine months.

14:12.540 --> 14:14.900
I banged it up and drowned it in the sink at one point.

14:15.300 --> 14:19.840
Finally, it died after being electrocuted in an accident while wiring an old house.

14:20.320 --> 14:24.340
I swear, capitalized, exclamation points,

14:24.620 --> 14:26.580
I turned off the breaker, and I did.

14:26.720 --> 14:27.960
Only it was mislabeled.

14:27.960 --> 14:32.540
I currently have a 20-gigabyte iPod and a 999 iBook, last series,

14:33.100 --> 14:35.500
that was been dropped downstairs on a cement floor

14:35.500 --> 14:37.840
and thrown out of a moving vehicle.

14:38.280 --> 14:42.400
See the accident at hcdb.com slash tinyurl.com

14:42.400 --> 14:45.940
slash charlie7 yankee Oscar uniform.

14:46.520 --> 14:52.140
It also survived an aftermarket DL DVD plus WRW slash RAM drive.

14:53.520 --> 14:54.200
Wow.

14:54.200 --> 14:57.560
If you look at this URL that he sent in,

14:57.860 --> 15:00.600
this iBook went through World War III almost.

15:00.940 --> 15:03.840
I just want to wonder, what the hell happened to that car?

15:04.500 --> 15:08.520
It was mucked up to no, like, it's almost irreconizable.

15:08.760 --> 15:09.500
It's disgusting.

15:09.760 --> 15:10.800
Let's pull it up and take a look.

15:11.500 --> 15:11.780
Yes.

15:12.280 --> 15:13.120
Oh, you haven't checked it out?

15:13.120 --> 15:15.440
Oh, God, it's a hoot.

15:15.540 --> 15:19.380
And I think it's hilarious that this person apparently took these pictures

15:19.380 --> 15:21.240
right after the accident.

15:22.320 --> 15:23.560
Well, I think that's what you do.

15:23.740 --> 15:26.560
You pull out your camera and you take photos for insurance purposes.

15:26.620 --> 15:28.300
Yeah, but he took all kinds of photos.

15:28.420 --> 15:30.200
He was getting very artsy almost, I would like to say.

15:31.200 --> 15:31.900
Well, I don't know.

15:31.900 --> 15:34.060
That thing is upside down.

15:35.360 --> 15:35.800
Mashed.

15:37.560 --> 15:39.720
Yeah, I'm surprised the iBook survived,

15:39.940 --> 15:42.460
and I'm more impressed that these people survived afterwards.

15:43.660 --> 15:46.780
Please email us and tell us what the heck happened.

15:46.900 --> 15:50.220
We will definitely read your email on air, because I am just dead curious.

15:50.220 --> 15:55.480
Anyway, out of all the emails we got, you had the most abused equipment.

15:56.700 --> 15:59.320
You seem to have the most unluckiest life in the world.

16:00.500 --> 16:03.220
Seriously, I want to know, how the heck did your iPod end up being electrocuted?

16:04.120 --> 16:05.920
Were you just shoving it in outlets for fun?

16:06.540 --> 16:10.140
I mean, even if you did cut the breaker, what were you doing to it?

16:11.880 --> 16:13.320
I'm not sure if I want to know.

16:13.980 --> 16:14.180
Jeez.

16:14.180 --> 16:22.160
So, well, LifeWarp, you win Gratuitous Kudos for the most entertaining story, at least, or something.

16:22.420 --> 16:22.980
I don't know.

16:23.560 --> 16:24.520
Congratulations, I guess.

16:24.760 --> 16:27.200
And just be careful.

16:27.420 --> 16:29.500
God, I don't want to know what's going to happen to you.

16:31.280 --> 16:33.440
Well, you'll probably end up folded up like the iBook.

16:34.040 --> 16:34.780
Yeah, goodness.

16:36.580 --> 16:39.460
Actually, I'm curious how far that iBook flew after that accident,

16:39.600 --> 16:42.120
because, boy, that sounds like a mess right there.

16:43.360 --> 16:43.520
Yeah.

16:43.520 --> 16:46.520
Our next email is from Sporty, and Sporty says,

16:46.680 --> 16:51.840
Hey, guys, I've had a great and meh experience with Apple in the past three years.

16:52.380 --> 16:53.360
And he goes on the list.

16:53.800 --> 16:57.540
G4 GrabPipe, 450 PPC, rock solid, about three years old.

16:58.440 --> 17:00.240
iPod, five gigabyte, first generation.

17:00.460 --> 17:03.420
It died after about 3.5 or so years.

17:04.320 --> 17:06.040
The Centronic connector broke internally.

17:06.240 --> 17:10.740
The Centronic connector has a very small circuit board that is attached very nicely to it on the inside.

17:10.740 --> 17:15.400
The tiny board is hooked up to a larger board and by several small connecting wires.

17:16.080 --> 17:19.060
The small circuit board is attached to the case by several tabs.

17:19.180 --> 17:25.240
After years of plugging and unplugging, those tabs snap, which caused the wires to only support the connector and the main board.

17:25.580 --> 17:26.360
Sadly, they broke.

17:26.360 --> 17:30.020
Fourth generation iPod mini, six months old, solid.

17:30.520 --> 17:32.800
Third generation iPod, 20 gigabytes, present.

17:33.640 --> 17:35.880
Won't remember, it hits audible click setting.

17:36.000 --> 17:37.840
It won't stay off after a complete battery drain.

17:38.580 --> 17:40.660
iBook G4, 12 inches, PPC 900.

17:40.660 --> 17:49.560
After about a year and the circuit board died, got a blue line across the screen horizontally and pushing the CPU too much caused a freeze.

17:50.800 --> 17:51.200
Wow.

17:51.420 --> 17:55.500
Like, I got to say, you have a lot of Apple equipment.

17:56.140 --> 18:01.980
And out of all your stuff that you said, I got to agree with Strom's opinion that he,

18:02.540 --> 18:05.960
Apple has become a lot more craptacular recently, as he would say.

18:05.960 --> 18:12.360
And I guess that's the point of this email I'd like to state is, this is very highly unscientific,

18:12.540 --> 18:14.220
and as always, your mileage may vary.

18:15.000 --> 18:16.980
But, boy, he has a lot of stuff.

18:17.040 --> 18:19.320
I like to say that I have two pieces of Apple equipment.

18:19.660 --> 18:23.540
I have, well, technically I have four if you really want to count the mouse and keyboard.

18:23.800 --> 18:30.980
But I have a blue and white G3, which is probably about three and a half years old, maybe four.

18:31.100 --> 18:31.840
I have no clue.

18:32.280 --> 18:33.460
And it works fine.

18:33.460 --> 18:35.940
And I also have my iPod, which I mentioned before.

18:36.360 --> 18:43.880
And beyond the battery life that it's recently suffered, my second pair of iPod headphones are starting to fall apart.

18:44.760 --> 18:49.740
One of the outside shells has started to crack, and it separates.

18:49.940 --> 18:55.700
So it dangles by a wire, which is really, really annoying for an earbud because it just sort of falls apart in your ear.

18:57.080 --> 19:00.520
But either way, well, I think you really should replace those anyway.

19:00.520 --> 19:05.700
From what I hear, I don't know how true this is, but you're more likely to get mugged while wearing white earphones.

19:07.240 --> 19:09.120
Honestly, at this point, they can probably have it.

19:09.460 --> 19:10.960
Oh, my God, I got an iPod.

19:11.260 --> 19:11.720
Wait a minute.

19:11.780 --> 19:13.840
It only lasts like 30 minutes on a single charge.

19:15.480 --> 19:17.660
Well, what about the aftermarket battery kit?

19:17.660 --> 19:20.220
I'm actually thinking about sending it into Apple.

19:20.340 --> 19:31.100
I've recently found out that they've dropped their iPod repair service thingy to like $60, $65 or something.

19:31.500 --> 19:31.720
Hmm.

19:31.920 --> 19:36.100
And that's something I'll consider because it's a whole hell of a lot cheaper than a new iPod.

19:36.500 --> 19:36.740
Right.

19:36.860 --> 19:40.100
But apparently the batteries online are even cheaper than that.

19:41.060 --> 19:41.480
Oh, really?

19:41.800 --> 19:42.240
Oh, yeah.

19:42.240 --> 19:48.440
Well, I think it's like $65 for shipping replacement, and they'll send you a refurb out.

19:48.800 --> 19:54.520
And one of the always fun things about refurbs is you never know if you're going to get something slightly better.

19:54.700 --> 20:01.600
And even if they send me a different model, it's going to be better than what I have because I have the lowest-end model possible.

20:02.240 --> 20:03.200
The very first one.

20:03.700 --> 20:05.120
Yes, the first one.

20:05.160 --> 20:05.840
That's where it is.

20:06.540 --> 20:07.880
That'd be cool if I had 10 gigs.

20:08.020 --> 20:10.200
I'd be like, yeah, 100% more storage.

20:10.200 --> 20:11.000
All right, go me.

20:12.240 --> 20:16.140
Actually, I was watching my local news station.

20:16.240 --> 20:18.440
We'll go sort of segue into a story about this.

20:18.980 --> 20:26.120
And they were talking about, you know, how Apple is a mean corporation because they do not send you your identical iPod back.

20:27.020 --> 20:29.740
And I just looked at that and said, that's an RMA.

20:29.840 --> 20:30.720
What did you expect?

20:30.720 --> 20:43.180
And I was just shocked how the entire concept of the RMA system, which for someone like me who was a sysadmin for more than a few years, it's very intricately familiar with.

20:43.880 --> 20:51.160
And, you know, I'm very familiar with it, and it just seems so odd that someone just did not understand the concept of RMA stuff.

20:51.160 --> 20:53.640
Well, that's what we call a slow news day.

20:54.280 --> 20:54.440
Yeah.

20:54.700 --> 21:02.440
Well, it was part of their whole, you know, consumer awareness, blah, blah, blah, blah, blah, blah, blah, blah.

21:03.560 --> 21:05.360
You know, their slow news day.

21:06.360 --> 21:08.320
Well, she usually has her stories on.

21:09.720 --> 21:11.400
It doesn't have to be a slow news day.

21:11.480 --> 21:16.820
They usually allow her five minutes every week where she reports something, and she decided to pick on Apple this week.

21:16.820 --> 21:20.360
So, Susan Warnick, if you're listening, nice hair.

21:20.500 --> 21:20.840
I don't know.

21:21.900 --> 21:22.500
Nice hair.

21:23.380 --> 21:28.920
Well, she used to have, like, this horrible 80s hair, and she actually got on –

21:28.920 --> 21:29.820
And that's knocked into her?

21:29.940 --> 21:30.500
Well, no, no, no.

21:30.500 --> 21:31.540
She went on, like, Oprah.

21:31.820 --> 21:32.560
I think it was Oprah.

21:32.660 --> 21:33.360
Some talk show.

21:33.360 --> 21:41.520
And because they have, like, bad hairstyles or bad looks from newscasters across the country, and she made the cut.

21:42.260 --> 21:44.960
So they gave her, like, a remake or something.

21:44.960 --> 21:47.880
It sounds Oprah-ish, so I wouldn't be surprised.

21:49.600 --> 21:50.920
Yes, this has been Rev Radio.

21:51.040 --> 21:51.960
We're talking about Oprah.

21:52.320 --> 21:53.020
Can I pick A1?

21:53.600 --> 21:54.540
Yeah, tell me about it.

21:56.860 --> 22:00.160
So anyway, let's go into a personal show and tell here.

22:01.760 --> 22:06.980
I spent most of my week watching our tech monkeys at work clean up the Zotob.

22:07.160 --> 22:08.880
I don't know how to pronounce it, to be honest with you.

22:08.880 --> 22:17.080
And that was fun, because about, oh, two years ago, I'd be doing that, and I'd probably be doing it a whole lot better than they were doing it.

22:17.600 --> 22:23.580
I found it incredibly amusing that Microsoft released this patch a week before the virus came out,

22:23.580 --> 22:30.180
and we have this, you know, quote, unquote, intricate patch release system in which, you know, it has to go through an approval process.

22:30.300 --> 22:35.620
In reality, they tested it for about, oh, from the looks of it, about six hours, and they said,

22:35.700 --> 22:41.920
okay, all you people apply this to your servers, and they never applied it to any of my department's servers.

22:41.920 --> 22:44.560
And I just laughed when I found that one out.

22:45.380 --> 22:50.260
I actually don't think we were owned by it, because we were thankfully running Windows 2003,

22:50.520 --> 22:57.580
which is theoretically, it's not invulnerable, but it's a little more difficult to be infected by it that way.

22:58.840 --> 23:04.760
And, yeah, so, I dodged a bullet, but I was enjoying watching everyone else run around, like,

23:04.900 --> 23:07.520
screaming their heads cut off and just critiquing them.

23:07.560 --> 23:09.940
It's fun to look on, it's fun to be on the outside and looking in.

23:10.460 --> 23:10.780
Always.

23:10.780 --> 23:15.360
Yeah, I also rescued Strom from North Korea, or wherever he was last week.

23:15.780 --> 23:21.040
Yes, Ratchet personally came to laugh me out of the detention facility.

23:21.320 --> 23:28.360
Yes, I called up Juan from South America, and I rented a Black Hawk, and it was really cool.

23:28.440 --> 23:30.420
If you ever saw Rambo, it was a lot like that.

23:31.860 --> 23:32.600
Except, you know, I was...

23:32.600 --> 23:34.900
I thought it was more like the rescue scene in Brazil.

23:35.800 --> 23:37.620
Oh, no, no, you were wearing a blindfold, how did you know?

23:37.620 --> 23:42.520
Huh? Huh? Huh? How about that, huh? Huh? Huh?

23:44.200 --> 23:44.600
Anyway.

23:46.760 --> 23:49.420
Oh, yes, my big news story.

23:49.480 --> 23:52.740
I don't think I actually ever told anyone this besides exclaiming it in the IRC channel.

23:52.740 --> 23:55.700
So, Yappel has hit 2,000 phones.

23:56.560 --> 23:57.000
Yay!

23:57.920 --> 23:58.800
Yeah, 2,000 phones.

23:58.960 --> 24:00.280
And that was...

24:00.280 --> 24:05.440
I knew that was on the horizon, and I actually came to a shocking realization about, right after DEF CON,

24:05.520 --> 24:10.100
that we have over 160 registered users, which is, wow.

24:10.560 --> 24:12.120
That's a lot of people.

24:12.120 --> 24:17.720
So, in accordance to that, I actually spanned out all of our, quote-unquote, top five lists,

24:17.760 --> 24:20.420
and I now made them top ten lists, so...

24:20.420 --> 24:20.980
Oh, Dave, let me...

24:20.980 --> 24:22.000
You haven't thought on your heels now.

24:22.520 --> 24:26.220
Oh, yes, you know, because top ten was just never around before he was there.

24:26.460 --> 24:26.920
Of course.

24:27.320 --> 24:27.580
Yeah.

24:29.180 --> 24:30.080
What have you been doing?

24:30.080 --> 24:32.360
You were talking about your Apple woes.

24:32.500 --> 24:34.840
What Apple woes do you have this week?

24:35.280 --> 24:40.720
Well, see, for those of you who aren't familiar with my Apple iPod disaster,

24:41.180 --> 24:44.660
I had an iPod that just, you know, up and died on me.

24:44.780 --> 24:45.700
It wouldn't charge.

24:45.880 --> 24:46.620
It wouldn't play.

24:47.100 --> 24:49.440
It was just all sorts of screwed up.

24:49.780 --> 24:53.540
So, I went to Apple, and I said, hey, look, it won't charge and play at the same time.

24:53.980 --> 24:56.040
So, it turns out the USB was fried.

24:56.380 --> 24:58.500
After much argument, they finally gave me a replacement,

24:59.120 --> 25:03.760
and all was good until my replacement stopped charging in the car.

25:05.300 --> 25:08.300
And so, I figured, well, this is fantastic.

25:09.040 --> 25:14.720
And I went back to the Apple store, and I said, hey, look, it's broken again.

25:16.080 --> 25:17.920
I said, oh, no, blah, blah, blah, blah, blah.

25:17.940 --> 25:19.020
It can't possibly be broken.

25:19.120 --> 25:19.740
It's not our thing.

25:19.840 --> 25:21.260
Our hardware is perfect, blah, blah, blah, blah.

25:21.780 --> 25:25.840
So, he plugs it into the Mac and works perfectly there.

25:26.920 --> 25:30.260
And so, at this point, I decide to go for broke,

25:30.260 --> 25:34.240
because I figure I haven't actually tested it with my computer at home,

25:34.320 --> 25:37.120
but I imagine that it's the same problem at this point.

25:38.120 --> 25:41.960
So, I say, well, you know, it doesn't work with any of my equipment at home,

25:42.080 --> 25:43.740
my charger, my computer, anything.

25:44.800 --> 25:47.320
So, no, there's nothing we can do about it.

25:47.400 --> 25:48.480
It looks fine.

25:48.480 --> 25:53.660
So, he pulls up a diagnostic where it shows the USB power thing.

25:53.840 --> 25:56.820
It shows a zero when there's no power on the USB, and a one when there is.

25:57.360 --> 26:00.280
So, he plugs it in, and he says, it seems to be working fine.

26:00.920 --> 26:01.920
The one shows up.

26:02.300 --> 26:05.920
He said, let me take this back to my car and see if it does that.

26:06.480 --> 26:08.120
So, I go back to the car, plug it in.

26:08.680 --> 26:13.080
USB power turns one, but the iPod won't charge, which I think is kind of odd.

26:13.080 --> 26:15.140
And, that's really weird.

26:15.560 --> 26:15.700
Yeah.

26:16.100 --> 26:17.920
So, I go back, and I say, hey, you know what?

26:17.960 --> 26:22.060
The USB power says one, but it will not actually charge in the car.

26:23.140 --> 26:24.920
He says, well, there's nothing we can do.

26:24.980 --> 26:28.080
You're plugged it into a third-party piece of equipment in the car.

26:29.980 --> 26:35.200
I said, well, do you have something here that you can give me that I can test it with?

26:35.520 --> 26:36.160
And so, he says, yeah.

26:36.200 --> 26:37.320
And then he walks off, and he comes back.

26:37.380 --> 26:39.880
Oh, actually, I just realized that would be third-party equipment, too.

26:40.260 --> 26:41.500
So, we can't do a damn thing.

26:43.080 --> 26:53.740
So, at this point, I lose it, and I just glare at the guy, and I say, well, do you have any Apple brand lube so I can go fuck myself like you're asking me to?

26:59.360 --> 27:00.820
And what did he respond to that?

27:01.980 --> 27:03.860
He didn't quite know how to respond to it.

27:06.000 --> 27:11.560
So, what is your current status of your iPod that works but sort of doesn't?

27:11.560 --> 27:16.900
Well, it seems to work fine as long as I plug it into the computer.

27:18.120 --> 27:18.920
That's really weird.

27:19.080 --> 27:29.360
I actually was thinking about getting a FireWire charger for my car, since considering my battery only lasts about two hours or so, and that would be handy to have a charger in the car.

27:29.460 --> 27:30.140
It would also be handy to have a charger.

27:30.140 --> 27:30.840
Well, actually, yeah.

27:30.920 --> 27:43.280
While I was on vacation, I suddenly needed to – my fun hacking story of the week is that I was trying to load a new album onto my iPod at my parents' house before we left for the lake.

27:44.560 --> 27:45.640
I mean, North Korea.

27:45.640 --> 27:45.860
North Korea.

27:46.100 --> 27:46.640
Yeah, sorry.

27:46.960 --> 27:47.880
Before we left for North Korea.

27:47.880 --> 27:52.220
Yeah, and so I mounted the iPod –

27:52.220 --> 27:53.360
The lake in North Korea.

27:53.480 --> 27:53.880
That was it.

27:53.940 --> 27:54.380
There it is.

27:54.500 --> 27:54.620
Yeah.

27:54.840 --> 28:01.800
My iPod wouldn't actually connect to my computer, so I figured, oh, something's wrong with the computer.

28:01.940 --> 28:07.400
It won't connect, so I plugged it into the Linux box downstairs and tried to mount the iPod via NFS.

28:08.260 --> 28:19.380
I sort of kind of succeeded, but only because this was the first time I had ever set up NFS, and I could read from the iPod, but any time I tried to write, I could create a file, but I wouldn't be able to actually write any data.

28:20.200 --> 28:23.220
So I ended up hosing the iTunes database on the iPod.

28:24.560 --> 28:29.540
Yeah, which meant that I went to go listen to music in the car on the way there, and nothing showed up on the list.

28:31.240 --> 28:31.640
So –

28:31.640 --> 28:34.180
Wah, wah, wah, wah, wah.

28:34.180 --> 28:42.180
But I did – so I figured, you know, okay, if I get a FireWire cable, I'll be able to use the iPod with my laptop.

28:42.740 --> 28:55.520
So I eventually found a FireWire cable which came with a car charger in Page, Arizona, and I did actually get my iPod working, but I haven't tried that charger in my car yet, so I should do that.

28:56.380 --> 28:56.620
Yes.

28:57.320 --> 29:01.860
Right now what I have is I have a – I don't have something for my car, but my work –

29:01.860 --> 29:09.960
I just – I have a workstation with FireWire on it, but unfortunately it runs Windows and my iPod is Mac, so I basically have to plug it in, and –

29:09.960 --> 29:17.060
but because it's in the computer, it tries to mount it all the time, and I can't play the songs, and it just drives me up a wall.

29:17.140 --> 29:18.880
I still need, like, a wall jack for it.

29:19.220 --> 29:20.840
So for some reason I've lost mine.

29:21.300 --> 29:23.440
I have no idea how I did that, but I did.

29:23.440 --> 29:31.080
Well, you could always go to your friendly neighborhood Apple store and purchase some Apple brand lube – I mean, the FireWire plug thing.

29:31.780 --> 29:34.700
Well, see, I'm not sure if they still have that because it's just so damn old.

29:34.860 --> 29:35.640
They're all like –

29:35.640 --> 29:37.520
No, I saw one at the Apple store.

29:38.080 --> 29:41.680
I'll have to go over there, my Apple store in the North Shore Mall at Danvers.

29:41.680 --> 29:49.140
Because I know, like, they have, like, all the docking stuff, but I don't have the docking port, and it makes me sad.

29:51.200 --> 29:52.160
It's just, you know.

29:52.680 --> 30:01.220
Yeah, no, they do have the AC adapter with the FireWire port on the back of it, so you just get the FireWire cable and plug it into both of them.

30:01.440 --> 30:03.460
Oh, I guess I'll have to look at that then.

30:05.120 --> 30:05.720
Damn them.

30:05.860 --> 30:06.780
Damn them to hell.

30:07.600 --> 30:08.040
We're Apple.

30:08.320 --> 30:08.960
Oh, that's your money.

30:09.420 --> 30:10.620
Yeah, it's going to be like 50 bucks.

30:10.620 --> 30:16.700
And something that always ticked me off about Apple is I bought a keyboard and a mouse from them.

30:16.780 --> 30:23.420
And normally a keyboard and a mouse would cost somewhere around $30, but because they're Apple-branded products, it cost me close to 70 bucks.

30:23.600 --> 30:33.200
And it just drove – all right, before I go into this, let's just go straight into our top main topic tonight, which is basically –

30:33.200 --> 30:33.940
Asterisk.

30:34.620 --> 30:40.140
Asterisk Redux 2005 non-extended edition.

30:40.140 --> 30:41.400
I don't know.

30:41.640 --> 30:44.220
This is an abbreviated version of the talk we gave at DEF CON.

30:44.620 --> 30:44.860
Yes.

30:45.960 --> 30:51.500
This is – if you want – I'll probably put this up on my site, so if you want to follow along.

30:51.560 --> 30:57.800
We're actually reading directly off the Power – not PowerPoint, sorry, OpenOffice slides that we did.

30:57.880 --> 31:01.020
What is the OpenOffice presentation thing called?

31:01.020 --> 31:02.460
OpenOffice Impress, I think.

31:03.100 --> 31:04.720
No, no, I think it's Presenter or something.

31:04.720 --> 31:05.340
Is it?

31:05.780 --> 31:07.240
It's called Impress on my system.

31:08.080 --> 31:08.340
Oh, really?

31:08.380 --> 31:11.240
I thought Impress was – it doesn't say.

31:11.300 --> 31:12.240
It just says OpenOffice.

31:12.440 --> 31:13.180
Oh, well, whatever.

31:13.980 --> 31:15.600
The OpenOffice PowerPoint.

31:16.280 --> 31:18.020
Yeah, the OpenOffice PowerPoint clone.

31:18.020 --> 31:23.200
So anyway, would you like to get started?

31:23.900 --> 31:24.280
Sure.

31:24.940 --> 31:25.340
All right.

31:25.520 --> 31:28.480
This is How to Be Your Own Telephone Company with Asterisk.

31:28.480 --> 31:34.940
Presented by Strom Carlson and Black Ratchet, DEF CON 13, July 2005.

31:35.580 --> 31:39.000
This was rated a bullshit presentation by Alex.net.

31:39.880 --> 31:40.400
Yes.

31:40.500 --> 31:52.140
This is a website, AL3X.net, and they rated what's cool, what's okay, and what's cool, what might be okay, and what's bullshit, DEF CON 13.

31:52.140 --> 31:59.640
And we were rated bullshit, along with 90% of the other presentations there, along with Stanks, which really took me off.

31:59.860 --> 32:04.020
But we had fun, you know, with that, and we decided to put that right on our title slide.

32:06.420 --> 32:07.080
All right.

32:07.180 --> 32:08.480
Let's get started here.

32:12.180 --> 32:14.820
Let me actually set this up so I can – there we go.

32:14.820 --> 32:22.100
We're just going to skip the brief history of telephone switching because we –

32:22.100 --> 32:22.480
Oh, we are?

32:22.600 --> 32:22.900
Okay.

32:23.280 --> 32:23.540
Yeah.

32:23.720 --> 32:30.460
Basically, there's been telephone switching since 1890, and it's been culminated to such a thing as Asterisk.

32:30.980 --> 32:34.280
Which is now this PBX – well, actually, what is Asterisk is the first slide.

32:34.980 --> 32:40.440
Asterisk is a free open source PBX that runs on Linux, and it is, without question, the best thing since sliced bread.

32:40.440 --> 32:45.240
Basically, it's a PBX you run on any Linux box.

32:45.340 --> 32:51.440
You can run it, you know, under your desk, on your laptop, in Colo somewhere, wherever you need telephony.

32:52.200 --> 32:53.960
And it's a great, great tool.

32:55.940 --> 33:01.100
It was originally written by Mark Spencer of digium.com, and now has a large number of contributors,

33:01.260 --> 33:04.160
though Mark is very, very healthily involved in the project.

33:04.600 --> 33:06.720
I think he's more than neck deep into it.

33:07.140 --> 33:07.440
Yes.

33:07.440 --> 33:10.780
He is, in fact, suffocating underneath the weight of it.

33:11.800 --> 33:14.920
I wouldn't go that far, because he's still doing fine, but –

33:14.920 --> 33:15.220
Yes.

33:17.460 --> 33:17.940
So –

33:17.940 --> 33:22.900
He's working right along, but he's still intricately involved in the design process and the coding process.

33:23.800 --> 33:24.040
Yes.

33:24.440 --> 33:27.060
And, oh, for those of you trying to follow along with the slideshow,

33:27.120 --> 33:30.700
we unfortunately don't have a thing like you had in the children's book,

33:30.700 --> 33:33.280
where when you hear the tone, advance the slide.

33:34.320 --> 33:35.680
So, we'll just tell you to –

33:35.680 --> 33:37.880
Just follow along. It becomes incredibly obvious.

33:38.160 --> 33:38.440
Yes.

33:39.340 --> 33:40.760
So, why asterisk?

33:41.080 --> 33:43.440
Well, first off, should we do this together?

33:43.920 --> 33:44.520
Of course.

33:45.860 --> 33:46.800
It's free!

33:51.160 --> 33:53.500
How much are you paying your PBX vendor right now?

33:53.620 --> 33:54.360
That's what I want to know.

33:54.440 --> 33:55.700
The software itself is free.

33:55.760 --> 33:58.720
I'm paying my PBX vendor, you know, countless amounts of money.

33:58.720 --> 34:01.020
He and I have a very, very personal relationship.

34:01.880 --> 34:02.760
We're not going there.

34:03.520 --> 34:07.540
Anyway, asterisk is this totally free open-source PBX.

34:07.600 --> 34:10.200
There is a version of asterisk called Asterisk Business Edition,

34:11.200 --> 34:14.340
which you can pay Digium money for,

34:14.440 --> 34:17.600
and it's a very, very stable, very, very well-supported version of asterisk.

34:17.600 --> 34:23.260
But for the vast majority of circumstances, you won't need that.

34:23.660 --> 34:26.960
You can just run the either stable version,

34:27.180 --> 34:29.140
or if you want to be on the hemorrhaging edge of things,

34:29.620 --> 34:31.140
the CVS head version.

34:31.740 --> 34:32.480
Like Strom and I.

34:32.720 --> 34:34.120
Yes, we're CVS head junkies.

34:34.200 --> 34:36.120
We haven't touched stable in God knows how long.

34:37.480 --> 34:38.700
Stable is for wussies.

34:40.880 --> 34:42.800
Or for mission-critical applications.

34:42.800 --> 34:44.080
True.

34:45.940 --> 34:49.120
So, asterisk runs on commodity PC hardware.

34:49.900 --> 34:52.940
Pretty much any PC you have lying around will run asterisk.

34:53.840 --> 34:55.680
I mean, not if it's a 386,

34:55.780 --> 34:58.920
but for the most part, we'll show you in a minute

34:58.920 --> 35:01.440
how almost any PC will run asterisk.

35:02.100 --> 35:04.560
It has broad support for VoIP protocols and hardware.

35:04.760 --> 35:07.940
Pretty much the goal of asterisk is to work with almost everything.

35:09.200 --> 35:09.900
Like Linux.

35:10.400 --> 35:10.700
Yes.

35:12.100 --> 35:12.740
So cute.

35:12.800 --> 35:14.680
Got some piece of telephony equipment.

35:15.200 --> 35:19.460
Chances are you can either have a talk with asterisk right out of the box,

35:19.720 --> 35:22.180
or tweak it a bit and get it to talk to asterisk.

35:22.580 --> 35:22.920
Indeed.

35:23.480 --> 35:24.800
And we both proved that.

35:25.280 --> 35:25.520
Mm-hmm.

35:26.180 --> 35:28.640
It's very easy to interconnect with other asterisk boxes,

35:28.780 --> 35:30.520
and you can form your own VoIP network, really,

35:30.600 --> 35:31.960
and that's kind of what Ratchet and I have done.

35:32.420 --> 35:34.880
This is all over our asterisk boxes right now.

35:34.940 --> 35:36.700
We're actually recording the show on asterisk.

35:36.980 --> 35:37.300
Yep.

35:37.300 --> 35:38.180
That's how we always done it.

35:38.640 --> 35:38.860
Mm-hmm.

35:39.220 --> 35:41.380
We're both talking on Cisco VoIP phones,

35:41.380 --> 35:42.860
which talk to our asterisk boxes,

35:42.940 --> 35:43.920
which are talking to each other.

35:44.540 --> 35:44.900
Mm-hmm.

35:44.900 --> 35:50.460
And asterisk is configurable to do almost whatever you want it to do.

35:50.920 --> 35:52.520
You can tweak it to your needs.

35:52.580 --> 35:55.880
You can write your own code if you feel it's necessary.

35:56.840 --> 35:58.800
Asterisk will, unfortunately, not do your dishes,

35:58.800 --> 36:02.340
but we're working on that module.

36:02.340 --> 36:04.740
We'll get the, what is it, the dish dial tone module,

36:04.900 --> 36:06.180
or was it Chan Dish?

36:06.820 --> 36:08.620
It's Chan Dish Wash.

36:09.640 --> 36:11.440
Chan underscore dishwasher dot SO.

36:11.720 --> 36:12.240
That's it.

36:12.760 --> 36:13.000
Yes.

36:14.740 --> 36:15.260
Okay.

36:15.980 --> 36:18.220
Section, asterisk, and hardware.

36:19.940 --> 36:22.260
So physical, tangible stuff.

36:22.260 --> 36:25.600
In case you didn't know what hardware was.

36:26.960 --> 36:30.440
Anyway, if you go to this wiki on VoIPinfo.org,

36:30.560 --> 36:32.360
VoIP-info.org, sorry,

36:33.040 --> 36:35.640
there's a page called Asterisk Dimensioning,

36:35.720 --> 36:37.640
where people post, you know,

36:37.740 --> 36:39.800
their stress test of asterisk

36:39.800 --> 36:41.000
and what they have it running on

36:41.000 --> 36:41.940
and how much it'll support.

36:42.740 --> 36:46.200
Someone running a 133 megahertz Pentium 1

36:46.200 --> 36:47.760
with 16 megabytes of RAM

36:47.760 --> 36:49.980
got three concurrent calls going

36:49.980 --> 36:51.200
before quality degraded.

36:52.580 --> 36:54.200
Which is just simply amazing.

36:54.600 --> 36:54.860
Mm-hmm.

36:55.760 --> 36:57.000
Considering that I think

36:57.000 --> 36:59.700
132 megahertz Pentium 1s

36:59.700 --> 37:03.640
are borderline for playing MP3s even.

37:06.080 --> 37:08.500
If you don't do anything else with it,

37:08.540 --> 37:09.340
it'll run fine.

37:09.520 --> 37:10.280
I mean, you, you,

37:10.920 --> 37:12.740
just don't do anything with it.

37:12.880 --> 37:14.580
And it will probably become painful

37:14.580 --> 37:15.980
if it even thinks even a little bit.

37:16.540 --> 37:17.020
Yeah.

37:18.380 --> 37:20.020
But pretty much the upshot of this

37:20.020 --> 37:22.120
is that any PC you have lying around will work.

37:22.220 --> 37:24.060
A 2.4 gigahertz P4

37:24.060 --> 37:26.280
with 512 megabytes of RAM

37:26.280 --> 37:29.460
gets 790 simultaneous calls.

37:30.380 --> 37:34.280
So your PC will more than handle

37:34.280 --> 37:35.700
the load you're going to put through it

37:35.700 --> 37:36.980
unless you are going to put

37:36.980 --> 37:37.920
hundreds of calls through it

37:37.920 --> 37:38.540
at the same time,

37:38.560 --> 37:40.300
in which case you are insane.

37:40.940 --> 37:42.600
I'm running my asterisk box

37:42.600 --> 37:47.100
on a dual processor 433 Celeron.

37:47.100 --> 37:48.500
So, and it runs fine.

37:48.540 --> 37:49.160
I've never done it.

37:49.560 --> 37:51.080
Yeah, I'm running my asterisk box

37:51.080 --> 37:52.760
on a 1 gigahertz P3

37:52.760 --> 37:54.420
with 300d4 megabytes of RAM,

37:54.500 --> 37:55.500
and I haven't had a single

37:55.500 --> 37:56.060
wimper trouble.

37:56.620 --> 37:56.940
Mm-hmm.

37:56.940 --> 38:01.700
So, let's get into the telephones

38:01.700 --> 38:02.460
that you can buy.

38:03.200 --> 38:03.880
You can either,

38:04.360 --> 38:06.360
there are several options

38:06.360 --> 38:07.340
for asterisk hardware

38:07.340 --> 38:09.440
as far as the actual voice terminal goes.

38:09.760 --> 38:10.740
You have the choice

38:10.740 --> 38:13.640
of purchasing a VoIP telephone

38:13.640 --> 38:15.960
that's plugged into your Ethernet network

38:15.960 --> 38:17.700
and have it talk to your asterisk box.

38:17.700 --> 38:20.980
Or you can purchase a terminal adapter

38:20.980 --> 38:22.900
and plug an analog telephone

38:22.900 --> 38:23.880
into the terminal adapter

38:23.880 --> 38:24.960
and plug your terminal adapter

38:24.960 --> 38:25.500
into the network

38:25.500 --> 38:26.740
and have it talk VoIP to wherever.

38:27.120 --> 38:29.520
Or you can get a card from Digium

38:29.520 --> 38:31.120
which goes into your asterisk box

38:31.120 --> 38:32.640
which you plug analog telephones

38:32.640 --> 38:33.280
directly into.

38:34.000 --> 38:35.200
So, we're going to go over

38:35.200 --> 38:36.380
the various types of phones

38:36.380 --> 38:36.980
you can buy.

38:38.280 --> 38:40.020
The popular VoIP telephones,

38:40.260 --> 38:43.000
the two pretty much generally

38:43.000 --> 38:44.360
considered to be the cream of the crop

38:44.360 --> 38:45.380
as far as these goes,

38:45.900 --> 38:47.460
are the Cisco 7960

38:47.460 --> 38:49.260
and the Polycom IP600.

38:50.340 --> 38:52.180
Ratchet and I both have 7960

38:52.180 --> 38:53.480
that we're talking on right now.

38:54.080 --> 38:54.440
Yay!

38:55.060 --> 38:57.280
And you can buy these used on eBay

38:57.280 --> 38:59.720
for generally about $250 to $300.

39:00.720 --> 39:01.460
Or so.

39:01.620 --> 39:02.980
I mean, there's deals to be had.

39:03.060 --> 39:07.200
I picked up my 7960 for $120 or so

39:07.200 --> 39:09.400
at the MIT flea.

39:10.540 --> 39:13.780
So, I mean, there's deals to be had.

39:13.780 --> 39:14.820
You just have to look out for it.

39:15.100 --> 39:16.900
We won't go into what biological favors

39:16.900 --> 39:17.920
Ratchet had to perform

39:17.920 --> 39:19.600
in order to get the Cisco 7960

39:19.600 --> 39:20.260
that cheaply,

39:20.340 --> 39:23.480
but I am still trying

39:23.480 --> 39:24.380
to repress those memories.

39:27.280 --> 39:28.520
The SNOM 190

39:28.520 --> 39:30.460
is a more mid-range phone

39:30.460 --> 39:33.160
that's $175 to $250,

39:33.460 --> 39:34.360
although I think you can get them

39:34.360 --> 39:35.080
cheaper these days.

39:36.300 --> 39:37.880
And that's kind of, you know,

39:38.240 --> 39:40.380
it's not as nice as the Cisco,

39:40.560 --> 39:42.240
but it's a pretty passable VoIP phone.

39:42.720 --> 39:44.940
I'm still waiting for the SNOM Carlson.

39:45.920 --> 39:47.120
Yeah, I'm really in trouble

39:47.120 --> 39:48.360
if SNOM ever makes a phone call

39:48.360 --> 39:48.940
to Carlson.

39:51.960 --> 39:52.960
And there's also the

39:52.960 --> 39:54.900
Grandstream Budgetone, isn't there?

39:54.960 --> 39:55.420
Yeah, that's right.

39:55.500 --> 39:55.880
Yeah, yeah.

39:56.280 --> 39:57.060
The Grandstream,

39:57.340 --> 39:58.760
not the Grand Scream,

39:58.880 --> 40:00.440
well, maybe that is a better name for it.

40:01.320 --> 40:03.380
But the Grandstream Budgetone 100

40:03.380 --> 40:06.120
is the kind of very low-end

40:06.120 --> 40:07.080
VoIP telephone.

40:07.080 --> 40:09.000
It's roughly comparable

40:09.000 --> 40:10.060
in quality to that

40:10.060 --> 40:11.740
$5 telephone set

40:11.740 --> 40:12.700
you buy at the drugstore.

40:14.640 --> 40:15.900
And that's not

40:15.900 --> 40:17.060
an exaggeration.

40:17.220 --> 40:18.320
These phones are not

40:18.320 --> 40:19.160
very high quality.

40:19.700 --> 40:20.880
But I have sort of

40:20.880 --> 40:21.420
a take-up on it

40:21.420 --> 40:22.700
called a NetWeb 302,

40:22.920 --> 40:24.840
and the dial tone

40:24.840 --> 40:25.920
essentially sounds like this.

40:27.220 --> 40:29.740
And it's disgusting to use,

40:29.820 --> 40:31.300
and I'm really regretting

40:31.300 --> 40:32.140
that I ever bought it.

40:32.140 --> 40:34.700
Waste of money

40:34.700 --> 40:35.960
unless you're really, really broke

40:35.960 --> 40:36.680
or you're just, you know,

40:36.700 --> 40:37.480
looking for some

40:37.480 --> 40:38.860
cheapo VoIP phone

40:38.860 --> 40:39.700
to play around with.

40:40.100 --> 40:41.120
Yes, it's a cheapo VoIP phone

40:41.120 --> 40:41.720
to play around with,

40:41.740 --> 40:42.520
and I learned by lesson.

40:43.220 --> 40:43.460
Yes.

40:43.960 --> 40:46.140
But that's from $40 to $75

40:46.140 --> 40:47.760
if you want to buy that online.

40:49.600 --> 40:52.200
So, VoIP terminal adapters.

40:53.100 --> 40:54.220
The one that you can buy

40:54.220 --> 40:54.820
from Digium

40:54.820 --> 40:55.880
is called the Eeksy.

40:57.120 --> 40:57.720
That's the...

40:57.720 --> 40:58.640
I-A-X-Y.

40:58.920 --> 41:00.280
Yes, I-A-X-Y.

41:00.280 --> 41:01.840
Although, I-A-X,

41:01.920 --> 41:02.560
as it turns out,

41:02.600 --> 41:03.640
is pronounced Eeksy.

41:04.680 --> 41:06.980
So, it's not I-A-X.

41:07.660 --> 41:08.560
But the Digium Eeksy

41:08.560 --> 41:10.160
is a great little tiny...

41:10.160 --> 41:11.000
It's absolutely,

41:11.740 --> 41:12.740
ridiculously tiny.

41:13.720 --> 41:15.460
It's got one Ethernet port

41:15.460 --> 41:15.900
on the back

41:15.900 --> 41:17.380
and one analog telephone port.

41:17.480 --> 41:18.460
Of course, it's PowerJack.

41:19.220 --> 41:20.140
And it speaks

41:20.140 --> 41:22.400
asterisk's native Eeksy protocol,

41:22.560 --> 41:23.460
which we'll get into in a bit.

41:24.220 --> 41:25.320
And that's $100.

41:26.760 --> 41:27.940
You can also

41:27.940 --> 41:29.840
get third-party equipment.

41:29.840 --> 41:32.240
There's the Sipporah SPA-2002,

41:32.560 --> 41:34.280
which is also surprisingly tiny.

41:35.040 --> 41:36.020
And that is...

41:36.020 --> 41:36.900
Instead of speaking Eeksy,

41:36.940 --> 41:37.660
it speaks SIP,

41:38.520 --> 41:39.100
as you would gather

41:39.100 --> 41:39.620
from their name.

41:39.940 --> 41:41.080
Yes, we'll cover these later.

41:41.820 --> 41:43.020
Yeah, we'll cover all this later.

41:43.800 --> 41:45.260
And so that has

41:45.260 --> 41:46.200
one Ethernet port

41:46.200 --> 41:47.880
and two telephone ports

41:47.880 --> 41:49.240
on the back of it.

41:49.980 --> 41:51.100
And that's $70.

41:51.500 --> 41:52.960
So you can do two stations.

41:53.080 --> 41:53.620
And the Sipporahs

41:53.620 --> 41:54.980
are surprisingly configurable.

41:54.980 --> 41:56.300
When you buy them

41:56.300 --> 41:57.200
unlocked,

41:58.180 --> 41:59.360
they come with,

42:00.180 --> 42:00.520
God,

42:00.580 --> 42:01.080
an option

42:01.080 --> 42:02.320
to do everything.

42:02.480 --> 42:03.460
Like there was...

42:03.460 --> 42:04.520
I plugged a Western

42:04.520 --> 42:05.500
electric phone into one

42:05.500 --> 42:07.380
and it wouldn't ring

42:07.380 --> 42:08.440
correctly for some reason.

42:08.580 --> 42:09.340
I looked on the

42:09.340 --> 42:10.680
configuration page

42:10.680 --> 42:11.880
and to my surprise,

42:12.000 --> 42:13.060
there's actually a setting

42:13.060 --> 42:14.340
to configure the frequency

42:14.340 --> 42:15.440
of the ring voltage

42:15.440 --> 42:16.480
that the thing sends out.

42:17.040 --> 42:18.660
It was set at 25 hertz.

42:18.720 --> 42:19.760
I set it back to 20 hertz

42:19.760 --> 42:20.800
and my Western electric phone

42:20.800 --> 42:21.340
rang beautifully.

42:21.940 --> 42:22.220
Yay!

42:24.260 --> 42:25.440
So that's what that was.

42:26.600 --> 42:27.480
There's also

42:27.480 --> 42:29.080
models you can get

42:29.080 --> 42:30.560
where the...

42:30.560 --> 42:31.280
you actually route

42:31.280 --> 42:32.020
the rest of your network

42:32.020 --> 42:32.900
traffic through

42:32.900 --> 42:34.580
the...

42:34.580 --> 42:36.200
through the terminal adapter

42:36.200 --> 42:37.100
so that when

42:37.100 --> 42:38.280
you...

42:38.280 --> 42:39.100
when you place

42:39.100 --> 42:39.520
heavy loads

42:39.520 --> 42:40.060
on your network,

42:40.180 --> 42:40.820
the terminal adapter

42:40.820 --> 42:41.660
will act as some sort

42:41.660 --> 42:42.560
of router, basically.

42:43.260 --> 42:44.040
And it'll

42:44.040 --> 42:45.080
give priority

42:45.080 --> 42:45.960
to its own traffic

42:45.960 --> 42:46.620
so you don't

42:46.620 --> 42:47.360
degrade the quality

42:47.360 --> 42:48.120
of your voice calls.

42:49.280 --> 42:50.080
There's...

42:50.080 --> 42:51.260
I forget which

42:51.260 --> 42:52.360
model of Sephora

42:52.360 --> 42:53.640
it is, but...

42:53.640 --> 42:54.320
I think that's the

42:54.320 --> 42:56.840
3002 or 3003

42:56.840 --> 42:57.520
or 300...

42:57.520 --> 42:58.480
3000 something.

42:58.600 --> 42:59.100
They have all kinds

42:59.100 --> 43:00.220
of weird model numbers.

43:00.440 --> 43:00.620
Yeah.

43:00.780 --> 43:01.240
Just go to

43:01.240 --> 43:01.980
sephora.com

43:01.980 --> 43:02.480
and check it out

43:02.480 --> 43:02.880
for yourself.

43:02.980 --> 43:03.220
Yes.

43:04.120 --> 43:04.900
There's also the

43:04.900 --> 43:05.520
Grandstream

43:05.520 --> 43:06.940
HandyTone 286

43:06.940 --> 43:08.400
which is a

43:08.400 --> 43:10.120
SIP terminal adapter.

43:10.220 --> 43:10.860
I think this one

43:10.860 --> 43:12.240
only has one FXF port.

43:12.240 --> 43:12.920
I think it actually

43:12.920 --> 43:13.680
has two ports.

43:13.760 --> 43:14.180
I think you were

43:14.180 --> 43:14.780
wrong on that

43:14.780 --> 43:15.100
and I believe

43:15.100 --> 43:16.280
the 486 has four.

43:16.780 --> 43:17.120
Does it?

43:17.640 --> 43:18.500
I don't know.

43:19.420 --> 43:20.000
I'm not sure

43:20.000 --> 43:20.440
about that,

43:20.480 --> 43:20.800
but I wouldn't

43:20.800 --> 43:21.380
be surprised.

43:21.700 --> 43:21.860
Yeah.

43:22.380 --> 43:23.160
Anyway, I haven't

43:23.160 --> 43:23.600
used it,

43:23.660 --> 43:24.580
but I'm sure

43:24.580 --> 43:25.160
the quality

43:25.160 --> 43:25.560
is somewhat

43:25.560 --> 43:26.260
better than

43:26.260 --> 43:26.700
the actual

43:26.700 --> 43:27.480
telephone itself.

43:28.260 --> 43:28.560
Mm-hmm.

43:29.440 --> 43:30.340
So, that's 65 bucks.

43:30.600 --> 43:31.400
It's a whole lot

43:31.400 --> 43:32.460
easier to make

43:32.460 --> 43:33.680
adapters rather than

43:33.680 --> 43:34.520
phones.

43:34.520 --> 43:34.740
Yeah.

43:35.080 --> 43:35.700
Because the adapter

43:35.700 --> 43:36.500
is just little boxes

43:36.500 --> 43:37.020
while the phone

43:37.020 --> 43:37.620
has all sorts

43:37.620 --> 43:38.060
of usability

43:38.060 --> 43:38.880
and human factor

43:38.880 --> 43:39.520
considerations

43:39.520 --> 43:40.100
that go into it.

43:40.220 --> 43:40.400
Yes.

43:40.680 --> 43:41.140
And then there's

43:41.140 --> 43:41.740
the granddaddy

43:41.740 --> 43:42.080
of them all,

43:42.120 --> 43:42.540
the Cisco

43:42.540 --> 43:43.980
ATA-186.

43:44.320 --> 43:45.160
This was the one

43:45.160 --> 43:45.760
that Vonage

43:45.760 --> 43:46.480
used to send out

43:46.480 --> 43:47.340
way, way back

43:47.340 --> 43:47.940
in the early days

43:47.940 --> 43:48.440
of Vonage.

43:49.920 --> 43:51.020
And it's made

43:51.020 --> 43:51.480
by Cisco,

43:51.680 --> 43:52.060
so you know

43:52.060 --> 43:52.720
it has to be good.

43:53.020 --> 43:53.260
Mm-hmm.

43:54.300 --> 43:55.240
And that's between

43:55.240 --> 43:56.780
50 and 125 bucks.

43:57.580 --> 43:57.980
Ironically,

43:58.200 --> 43:59.180
here's the funny thing,

43:59.880 --> 44:00.460
at least the way

44:00.460 --> 44:01.420
I understand it.

44:01.600 --> 44:02.140
The group that

44:02.140 --> 44:02.900
originally developed

44:02.900 --> 44:04.520
the Cisco ATA-186

44:04.520 --> 44:06.380
went from Cisco

44:06.380 --> 44:07.040
and started up

44:07.040 --> 44:07.440
Sephora

44:07.440 --> 44:08.340
and started making

44:08.340 --> 44:08.940
their own terminal

44:08.940 --> 44:09.400
adapters.

44:10.340 --> 44:10.960
And now Sephora

44:10.960 --> 44:11.520
is being bought

44:11.520 --> 44:12.020
by Cisco.

44:12.540 --> 44:14.880
What a tangled

44:14.880 --> 44:15.600
web we leave.

44:15.900 --> 44:16.200
Weave.

44:17.320 --> 44:18.040
What a tangled

44:18.040 --> 44:18.760
web we leave,

44:18.820 --> 44:19.180
of course.

44:20.320 --> 44:20.980
Yeah, true.

44:21.100 --> 44:21.640
It actually does

44:21.640 --> 44:22.020
kind of work.

44:22.100 --> 44:22.380
Oh, well.

44:23.760 --> 44:24.580
And finally,

44:24.700 --> 44:25.440
on to the really

44:25.440 --> 44:26.060
cool things,

44:26.160 --> 44:27.040
the Digium Zaptel

44:27.040 --> 44:27.460
cards.

44:28.220 --> 44:28.920
These are cards

44:28.920 --> 44:29.520
that you buy

44:29.520 --> 44:30.260
and you stick

44:30.260 --> 44:31.000
inside your

44:31.000 --> 44:31.780
asterisk box.

44:32.740 --> 44:33.500
And you can

44:33.500 --> 44:34.580
plug analog telephones

44:34.580 --> 44:35.560
or telephone lines

44:35.560 --> 44:36.320
directly into them.

44:37.500 --> 44:38.300
So there's

44:38.300 --> 44:39.660
the TDM-400P,

44:39.780 --> 44:40.160
which is the

44:40.160 --> 44:40.820
analog card.

44:40.820 --> 44:42.140
that one

44:42.140 --> 44:43.220
comes with

44:43.220 --> 44:43.980
little modules

44:43.980 --> 44:44.820
and you specify

44:44.820 --> 44:45.460
which modules

44:45.460 --> 44:45.940
you want.

44:46.540 --> 44:46.940
So you can

44:46.940 --> 44:47.440
either choose

44:47.440 --> 44:48.040
modules that

44:48.040 --> 44:48.800
connect telephones

44:48.800 --> 44:49.540
to your asterisk

44:49.540 --> 44:50.920
box or you

44:50.920 --> 44:51.240
can choose

44:51.240 --> 44:51.820
modules that

44:51.820 --> 44:52.440
connect telephone

44:52.440 --> 44:53.040
lines to your

44:53.040 --> 44:53.700
asterisk box.

44:54.460 --> 44:55.100
So in case

44:55.100 --> 44:56.040
you have a home

44:56.040 --> 44:56.640
phone line that

44:56.640 --> 44:57.160
you want to share

44:57.160 --> 44:57.720
among multiple

44:57.720 --> 44:58.200
extensions,

44:58.680 --> 44:59.560
you can do that.

45:01.160 --> 45:02.060
Asterisk makes it

45:02.060 --> 45:02.660
all easy.

45:02.660 --> 45:04.660
asterisk.

45:04.660 --> 45:05.100
Asterisk.

45:06.100 --> 45:07.260
I forget if it was

45:07.260 --> 45:08.380
no, I was going

45:08.380 --> 45:08.720
to say about

45:08.720 --> 45:09.120
Linux.

45:09.540 --> 45:09.840
It makes

45:09.840 --> 45:10.580
difficult things

45:10.580 --> 45:11.400
easy and easy

45:11.400 --> 45:11.840
things like

45:11.840 --> 45:12.460
poking yourself

45:12.460 --> 45:12.840
in the eye

45:12.840 --> 45:13.320
with a white

45:13.320 --> 45:13.800
hot sewing

45:13.800 --> 45:14.040
needle.

45:16.440 --> 45:17.160
All right.

45:18.800 --> 45:19.520
Asterisk makes

45:19.520 --> 45:20.160
everything easy.

45:20.300 --> 45:20.820
We'll just leave

45:20.820 --> 45:21.220
it with that.

45:22.480 --> 45:23.120
Obviously, you're

45:23.120 --> 45:23.720
not an advertising

45:23.720 --> 45:24.040
major.

45:24.640 --> 45:25.120
Obviously, I'm

45:25.120 --> 45:25.320
not.

45:25.320 --> 45:26.780
There's also

45:26.780 --> 45:29.040
the TDE-405P

45:29.040 --> 45:29.880
and 410P,

45:30.120 --> 45:31.100
and these are

45:31.100 --> 45:33.040
quad-span T1E1

45:33.040 --> 45:33.440
cards.

45:34.060 --> 45:34.780
So say you're

45:34.780 --> 45:35.420
doing a larger

45:35.420 --> 45:36.320
asterisk installation

45:36.320 --> 45:36.620
and you're

45:36.620 --> 45:37.060
bringing in a

45:37.060 --> 45:37.960
channelized T1

45:37.960 --> 45:38.560
or a primary

45:38.560 --> 45:39.580
rate ISDN line

45:39.580 --> 45:40.280
into your asterisk

45:40.280 --> 45:40.580
box.

45:40.820 --> 45:41.560
You get this

45:41.560 --> 45:42.140
card, and the

45:42.140 --> 45:42.680
thing just goes

45:42.680 --> 45:43.160
right in.

45:44.340 --> 45:45.080
It's a beautiful,

45:45.200 --> 45:45.840
beautiful card.

45:46.620 --> 45:48.120
The TDM-400P

45:48.120 --> 45:48.940
fully loaded with

45:48.940 --> 45:49.760
modules is about

45:49.760 --> 45:51.680
$300, and the

45:51.680 --> 45:52.680
TDE-405 and

45:52.680 --> 45:53.960
410P are about

45:53.960 --> 45:54.560
$1,500.

45:56.040 --> 45:56.660
But if you're

45:56.660 --> 45:57.060
going to buy a

45:57.060 --> 45:57.720
T1, it's well

45:57.720 --> 45:58.100
worth it.

45:58.800 --> 45:59.480
Yeah, considering

45:59.480 --> 45:59.980
how much you're

45:59.980 --> 46:00.740
going to spend on

46:00.740 --> 46:01.660
the T1, you've

46:01.660 --> 46:02.260
got the pockets

46:02.260 --> 46:03.200
for the 405 and

46:03.200 --> 46:03.760
410P.

46:05.920 --> 46:06.440
Since we're

46:06.440 --> 46:07.100
moving on, you

46:07.100 --> 46:07.480
know, we have

46:07.480 --> 46:08.060
all these phones.

46:08.160 --> 46:08.500
How the heck

46:08.500 --> 46:09.280
do we interconnect

46:09.280 --> 46:10.080
them with other

46:10.080 --> 46:11.000
voice-over IP

46:11.000 --> 46:11.420
things?

46:11.820 --> 46:12.320
We're going to

46:12.320 --> 46:12.820
go over the

46:12.820 --> 46:13.900
various ways to

46:13.900 --> 46:14.420
connect them.

46:15.000 --> 46:15.920
Asterisk is fun,

46:16.320 --> 46:16.920
but it's really

46:16.920 --> 46:17.720
fun when you can

46:17.720 --> 46:18.660
call outside of

46:18.660 --> 46:19.340
your asterisk box.

46:19.960 --> 46:20.860
Who says that?

46:21.900 --> 46:22.840
No, I'm calling

46:22.840 --> 46:23.460
my living room

46:23.460 --> 46:24.420
repeatedly over and

46:24.420 --> 46:24.820
over and over.

46:24.820 --> 46:25.680
Hey, it's a

46:25.680 --> 46:26.780
PBXSR, man.

46:27.600 --> 46:28.300
Anyway, the

46:28.300 --> 46:29.240
first major

46:29.240 --> 46:29.940
protocol there is

46:29.940 --> 46:30.640
called Session

46:30.640 --> 46:31.200
Initiation

46:31.200 --> 46:31.900
Protocol, which

46:31.900 --> 46:33.640
is abbreviated as

46:33.640 --> 46:33.820
SIP.

46:33.880 --> 46:34.520
We've heard SIP

46:34.520 --> 46:35.300
more than a few

46:35.300 --> 46:36.660
times, and that's

46:36.660 --> 46:37.600
what we need.

46:37.700 --> 46:38.260
We're not talking

46:38.260 --> 46:38.920
about drinking

46:38.920 --> 46:39.360
drinks.

46:40.100 --> 46:41.740
SIP is okay.

46:42.020 --> 46:42.620
It's signaling

46:42.620 --> 46:43.640
protocol only.

46:43.820 --> 46:44.900
The actual media

46:44.900 --> 46:45.820
transport is handled

46:45.820 --> 46:47.340
by RTP, which is

46:47.340 --> 46:48.220
a real-time

46:48.220 --> 46:48.600
protocol.

46:48.760 --> 46:49.140
It's another

46:49.140 --> 46:49.960
streaming audio

46:49.960 --> 46:50.360
protocol.

46:51.140 --> 46:51.940
The protocol was

46:51.940 --> 46:52.660
developed by the

46:52.660 --> 46:54.520
IETF and not the

46:54.520 --> 46:55.980
ITU, which is the

46:55.980 --> 46:56.460
International

46:56.460 --> 46:57.240
Telecommunications

46:57.240 --> 46:58.040
Union, people who

46:58.040 --> 46:59.800
essentially design all

46:59.800 --> 47:00.520
the major standards

47:00.520 --> 47:01.420
for telephone systems.

47:02.220 --> 47:03.220
And instead of phone

47:03.220 --> 47:03.880
numbers, it uses

47:03.880 --> 47:05.560
something similar to a

47:05.560 --> 47:06.480
URL, and it would be

47:06.480 --> 47:08.160
SIP colon slash slash

47:08.160 --> 47:10.000
strom at stromcarlson.com.

47:11.200 --> 47:12.320
SIP is intended to be a

47:12.320 --> 47:13.240
peer-to-peer protocol,

47:14.420 --> 47:15.280
meaning, you know, we

47:15.280 --> 47:16.000
don't have to connect to a

47:16.000 --> 47:16.900
central server to find out

47:16.900 --> 47:17.900
what's going on, which is

47:17.900 --> 47:18.800
sort of true.

47:18.900 --> 47:19.420
We'll go into that

47:19.420 --> 47:19.660
later.

47:20.480 --> 47:21.920
It's fairly ubiquitous.

47:22.180 --> 47:22.960
Most VoIP phones,

47:23.060 --> 47:23.940
terminal adapters, et

47:23.940 --> 47:24.560
cetera, et cetera, et

47:24.560 --> 47:25.460
cetera, they all speak

47:25.460 --> 47:26.540
SIP because everyone

47:26.540 --> 47:27.540
uses SIP, such as

47:27.540 --> 47:28.600
Vonage, Packet H,

47:28.760 --> 47:29.480
Broadvoice, et

47:29.480 --> 47:29.720
cetera.

47:30.500 --> 47:31.860
SIP does not play well

47:31.860 --> 47:33.100
with NAT, Network

47:33.100 --> 47:33.960
Address Translation.

47:34.080 --> 47:34.840
If you're behind some

47:34.840 --> 47:36.140
type of firewall, you

47:36.140 --> 47:37.740
have to open about, oh,

47:38.020 --> 47:39.380
15,000 ports to get

47:39.380 --> 47:40.160
RTP working.

47:40.700 --> 47:41.560
And the reason why

47:41.560 --> 47:42.500
this is, is basically

47:42.500 --> 47:43.520
when you're initiating a

47:43.520 --> 47:44.480
phone call because it's a

47:44.480 --> 47:45.500
signaling protocol only,

47:45.820 --> 47:46.720
you talk to the

47:46.720 --> 47:47.880
computer and say, hey,

47:47.900 --> 47:48.620
I have a phone call

47:48.620 --> 47:50.560
for you, connect to me

47:50.560 --> 47:51.560
at this IP address.

47:51.620 --> 47:52.580
And if it assumes that

47:52.580 --> 47:54.980
it's a 192.168

47:54.980 --> 47:56.200
address, the computer on

47:56.200 --> 47:56.840
the other side is

47:56.840 --> 47:57.460
going, what?

47:57.540 --> 47:58.160
I don't know where to

47:58.160 --> 47:58.820
connect to that to.

47:59.020 --> 48:00.640
And it's lots of,

48:00.660 --> 48:01.260
there's lots of

48:01.260 --> 48:01.880
kludges and works

48:01.880 --> 48:02.700
around for it, but

48:02.700 --> 48:04.920
it's, it's not good.

48:05.000 --> 48:06.600
It's, it's, it's very

48:06.600 --> 48:07.440
much a kludge.

48:08.400 --> 48:09.600
Another protocol is

48:09.600 --> 48:10.560
H323.

48:10.860 --> 48:11.780
It's developed, it

48:11.780 --> 48:12.760
was the first real

48:12.760 --> 48:14.560
voiceover IP and all

48:14.560 --> 48:15.620
that stuff developed in

48:15.620 --> 48:17.140
1996 by the ITU.

48:17.140 --> 48:18.460
Uh, it's far more

48:18.460 --> 48:19.620
similar to traditional

48:19.620 --> 48:20.520
telephony signaling

48:20.520 --> 48:21.880
protocols than SIP.

48:22.560 --> 48:23.740
However, it does also

48:23.740 --> 48:25.300
use RTP for media

48:25.300 --> 48:25.800
transport.

48:26.240 --> 48:27.760
Uh, used internally by

48:27.760 --> 48:28.740
inter-exchange carriers,

48:28.940 --> 48:29.640
which are people that

48:29.640 --> 48:30.960
carry, uh, phone calls

48:30.960 --> 48:33.560
between, uh, various

48:33.560 --> 48:34.580
telephone companies.

48:34.580 --> 48:35.540
Inter-exchange carriers,

48:35.640 --> 48:36.200
yeah, are the long

48:36.200 --> 48:36.900
distance companies.

48:37.100 --> 48:37.520
So, yeah, long

48:37.520 --> 48:38.120
distance companies.

48:38.180 --> 48:38.640
That's what I was

48:38.640 --> 48:39.020
looking for.

48:39.200 --> 48:39.380
Yeah.

48:39.740 --> 48:41.360
AT&T, MCI, Global

48:41.360 --> 48:42.260
Crossing, and so on.

48:42.360 --> 48:43.020
Yeah, exactly.

48:43.400 --> 48:43.560
Great.

48:43.900 --> 48:46.100
Um, H323 sucks and

48:46.100 --> 48:46.900
therefore it's fairly

48:46.900 --> 48:48.200
unpopular in the do-it-yourself

48:48.200 --> 48:48.700
VoIP world.

48:48.820 --> 48:49.740
It's, uh, difficult to

48:49.740 --> 48:51.320
implement in software and

48:51.320 --> 48:52.420
it's a major pain in the

48:52.420 --> 48:53.120
ass to get working.

48:53.500 --> 48:54.640
For example, the original

48:54.640 --> 48:55.760
copy of Microsoft Net

48:55.760 --> 48:57.400
Meeting uses H323.

48:57.960 --> 48:58.280
Ugh.

48:58.280 --> 49:00.840
And our, our quote that

49:00.840 --> 49:02.140
we found, uh, Strom was

49:02.140 --> 49:03.160
sitting in pound asterisk

49:03.160 --> 49:04.580
on freenode.net, I

49:04.580 --> 49:04.820
believe.

49:05.260 --> 49:05.480
Mm-hmm.

49:05.540 --> 49:05.880
That's one.

49:06.020 --> 49:07.280
And it's, uh, was, uh,

49:07.700 --> 49:08.960
major developer's, uh,

49:08.980 --> 49:10.380
handle is Jerjer, and we

49:10.380 --> 49:11.300
got a quote of, just

49:11.300 --> 49:13.420
don't use H323 and all

49:13.420 --> 49:14.320
your problems will be

49:14.320 --> 49:14.780
solved.

49:15.780 --> 49:16.960
And that is so true.

49:17.440 --> 49:18.300
And very much so.

49:18.780 --> 49:19.440
Uh, one of the other

49:19.440 --> 49:20.960
major, uh, protocols out

49:20.960 --> 49:21.980
there is the EECS

49:21.980 --> 49:23.040
protocol, which stands for

49:23.040 --> 49:24.520
inter-asterisk exchange.

49:24.840 --> 49:26.240
And it's developed by Mark

49:26.240 --> 49:27.340
Spencer of Digium, so

49:27.340 --> 49:28.040
you know it has to be

49:28.040 --> 49:28.220
good.

49:28.840 --> 49:29.660
Uh, it covers both

49:29.660 --> 49:30.340
signaling and media

49:30.340 --> 49:30.760
transport.

49:31.320 --> 49:32.160
It's a streamlined

49:32.160 --> 49:32.860
simple protocol.

49:33.020 --> 49:33.720
Essentially what Mark

49:33.720 --> 49:34.920
did is he looked at,

49:35.440 --> 49:36.880
SIP, he looked at H323

49:36.880 --> 49:38.200
and said, both these

49:38.200 --> 49:38.440
suck.

49:38.500 --> 49:39.220
Let me go design my own

49:39.220 --> 49:40.100
protocol that solves all

49:40.100 --> 49:40.680
the shortcomings of

49:40.680 --> 49:40.900
these.

49:41.100 --> 49:43.000
And thus, EECS was born.

49:43.840 --> 49:44.860
Um, does not suffer the

49:44.860 --> 49:45.880
same, you know, NAT

49:45.880 --> 49:47.520
traversal issues of, like,

49:47.580 --> 49:49.100
RTP and SIP and all

49:49.100 --> 49:49.720
that good stuff.

49:50.200 --> 49:51.060
Uh, data and signaling

49:51.060 --> 49:52.840
happen via UDP on port

49:52.840 --> 49:53.760
4569.

49:54.000 --> 49:55.140
Focus small single hole in

49:55.140 --> 49:55.880
your firewall and you're

49:55.880 --> 49:56.260
all set.

49:57.140 --> 49:57.960
Considering it's called

49:57.960 --> 49:59.360
inter-asterisk exchange,

49:59.440 --> 50:00.260
it's very well supported

50:00.260 --> 50:01.360
by asterisk, duh.

50:02.280 --> 50:03.520
Um, support in the

50:03.520 --> 50:04.240
terminal equipment is

50:04.240 --> 50:04.520
rare.

50:04.640 --> 50:05.460
Like, for example, the

50:05.460 --> 50:06.220
phone I was talking

50:06.220 --> 50:07.300
about, the reason why I

50:07.300 --> 50:08.520
got it mainly is because

50:08.520 --> 50:09.540
it's support EECS, and

50:09.540 --> 50:10.740
it was one of the few

50:10.740 --> 50:12.200
devices out there that

50:12.200 --> 50:12.580
did that.

50:12.580 --> 50:14.920
Uh, Digium EECS terminal

50:14.920 --> 50:16.380
adapter seeks it, and that's

50:16.380 --> 50:17.600
about it, besides my phone.

50:17.600 --> 50:19.960
Uh, it's a protocol from

50:19.960 --> 50:21.200
any, uh, public service,

50:21.620 --> 50:22.640
public Swiss telephone

50:22.640 --> 50:24.260
network, uh, termination

50:24.260 --> 50:24.760
providers.

50:24.980 --> 50:26.480
And, because it's just very

50:26.480 --> 50:27.680
fire and forget, set it up,

50:27.720 --> 50:28.400
and you don't need to worry

50:28.400 --> 50:29.660
about configuring it and

50:29.660 --> 50:30.700
fixing everything, and

50:30.700 --> 50:32.380
suddenly it stops working.

50:32.480 --> 50:33.800
It's, it's a very, it's a

50:33.800 --> 50:34.980
fairly robust protocol.

50:35.980 --> 50:37.000
Um, a couple other

50:37.000 --> 50:38.380
protocols that are really not

50:38.380 --> 50:41.560
used a lot is, uh, MGCP,

50:41.760 --> 50:42.620
which is the Media Gateway

50:42.620 --> 50:43.400
Control Protocol.

50:43.720 --> 50:44.880
The only thing I've ever

50:44.880 --> 50:46.000
seen this used for is one

50:46.000 --> 50:46.820
of my ATAs.

50:46.940 --> 50:48.220
It was previously used by

50:48.220 --> 50:50.580
AT&T Call Vantage, and

50:50.580 --> 50:51.680
that's the only place I've

50:51.680 --> 50:52.300
ever seen it used.

50:52.420 --> 50:53.740
Apparently AT&T used it for

50:53.740 --> 50:54.060
a while.

50:54.160 --> 50:55.120
I don't think they still use

50:55.120 --> 50:55.980
it, but I could be wrong.

50:56.440 --> 50:57.580
And I picked up a use

50:57.580 --> 50:59.340
ATA, which I had to

50:59.340 --> 51:01.360
reflash and reconfigure, and

51:01.360 --> 51:02.660
that's the only thing I have

51:02.660 --> 51:04.020
ever seen using MGCP.

51:04.800 --> 51:05.620
Uh, the other thing is

51:05.620 --> 51:06.680
Cisco's Skinny Client

51:06.680 --> 51:07.840
Control Protocol, which is

51:07.840 --> 51:09.660
SCCP, and with Cisco

51:09.660 --> 51:10.380
phones, you have two

51:10.380 --> 51:10.720
options.

51:10.820 --> 51:11.680
You can use SIP, or you

51:11.680 --> 51:12.540
can use SCCP.

51:13.340 --> 51:13.620
SCCP.

51:14.220 --> 51:15.960
Uh, Cisco's Call Manager,

51:16.100 --> 51:16.720
which is their voice

51:16.720 --> 51:19.460
solution, uses SCCP, and

51:19.460 --> 51:20.560
they use SIP because

51:20.560 --> 51:21.580
everyone else uses SIP.

51:21.780 --> 51:23.660
So, uh, there's two

51:23.660 --> 51:24.300
drivers for it.

51:24.320 --> 51:25.460
There's Chan Skinny and

51:25.460 --> 51:26.600
Chan SCCP2.

51:26.600 --> 51:31.200
Uh, SCCP2, goodness, that

51:31.200 --> 51:32.040
doesn't roll right off the

51:32.040 --> 51:33.880
tongue, does it, uh, is a

51:33.880 --> 51:35.160
third-party plug-in, which

51:35.160 --> 51:36.400
has fairly better support

51:36.400 --> 51:37.120
than Chan Skinny.

51:37.840 --> 51:40.700
Uh, but, they're, but, if

51:40.700 --> 51:41.740
you have a, if you have the

51:41.740 --> 51:42.700
choice, use SIP.

51:42.820 --> 51:44.060
Some older Cisco phones don't

51:44.060 --> 51:46.400
use, can't use SIP, and

51:46.400 --> 51:47.280
you're forced to use one of

51:47.280 --> 51:48.080
these, but if you can get

51:48.080 --> 51:50.380
away with it, use SIP.

51:50.500 --> 51:51.760
Just save yourself some time

51:51.760 --> 51:52.060
and effort.

51:52.380 --> 51:53.620
There's two drivers for

51:53.620 --> 51:54.760
asterisk for SIP for

51:54.760 --> 51:55.880
Skinny, and they both kind

51:55.880 --> 51:56.220
of suck.

51:57.540 --> 51:58.420
Okay, and we're going to go

51:58.420 --> 51:59.620
interconnecting asterisk with

51:59.620 --> 52:00.460
Codex, and this is a

52:00.460 --> 52:01.420
Strom's thing, and if you'd

52:01.420 --> 52:02.840
really like to blitz right

52:02.840 --> 52:03.480
through this, because we're

52:03.480 --> 52:04.280
kind of running short on

52:04.280 --> 52:04.600
time.

52:05.540 --> 52:05.900
All right.

52:06.680 --> 52:08.140
Well, in order to

52:08.140 --> 52:09.140
understand Codex, you need

52:09.140 --> 52:10.600
to understand how audio is

52:10.600 --> 52:11.460
encoded on the, on the

52:11.460 --> 52:13.380
telephone network, so we're

52:13.380 --> 52:14.280
going to just kind of breeze

52:14.280 --> 52:14.740
through this.

52:14.820 --> 52:15.460
See if you have an analog

52:15.460 --> 52:16.880
waveform, which gets sliced

52:16.880 --> 52:17.740
up into a bunch of

52:17.740 --> 52:18.580
different time slices.

52:19.020 --> 52:20.140
It's still analog, but, you

52:20.140 --> 52:21.000
know, just little slices,

52:21.440 --> 52:22.460
little pulses of amplitude,

52:22.620 --> 52:23.800
so this becomes pulse-amplitude

52:23.800 --> 52:24.340
modulation.

52:25.460 --> 52:27.060
It's still analog, but it's

52:27.060 --> 52:27.900
sliced up into a little bit

52:27.900 --> 52:28.240
of time.

52:28.240 --> 52:29.880
Then each value is

52:29.880 --> 52:32.660
quantized, and you wind up

52:32.660 --> 52:34.260
with PCM, false code

52:34.260 --> 52:37.020
modulation, which is what

52:37.020 --> 52:37.860
happens on the phone

52:37.860 --> 52:39.260
network, and also just raw

52:39.260 --> 52:42.480
PCM at 44.1 kilohertz is

52:42.480 --> 52:43.520
what you hear when you

52:43.520 --> 52:44.660
listen to a compact disc.

52:45.560 --> 52:47.040
So PCM is cool.

52:48.280 --> 52:49.040
However, for the phone

52:49.040 --> 52:49.800
network, you know, you

52:49.800 --> 52:51.680
don't want to, you don't

52:51.680 --> 52:52.760
want to use all that

52:52.760 --> 52:54.820
bandwidth, because 44.1

52:54.820 --> 52:55.920
kilohertz is kind of

52:55.920 --> 52:57.960
unnecessarily wide band

52:57.960 --> 52:59.000
for a telephone call.

52:59.860 --> 53:01.040
And even if you go down

53:01.040 --> 53:03.840
to basically, if you look

53:03.840 --> 53:04.840
at the range of human

53:04.840 --> 53:06.380
voice frequencies, the

53:06.380 --> 53:07.380
vast majority of them

53:07.380 --> 53:08.620
are under 4,000 hertz.

53:09.780 --> 53:11.620
So using the Nyquist

53:11.620 --> 53:12.640
theorem, we kind of just

53:12.640 --> 53:14.900
realize that 8,000 hertz

53:14.900 --> 53:16.820
is the best frequency to

53:16.820 --> 53:18.660
encode voice at for the

53:18.660 --> 53:19.380
telephone network.

53:20.020 --> 53:21.240
So you do eight, you know,

53:21.240 --> 53:23.300
if you want to do 16 bits

53:23.300 --> 53:24.940
at 8,000 hertz, that

53:24.940 --> 53:26.800
gives a fairly good, clear

53:26.800 --> 53:28.540
representation of the voice

53:28.540 --> 53:29.220
on the other end.

53:29.620 --> 53:31.340
But 16-bit would be 128

53:31.340 --> 53:32.380
kilobits a second.

53:32.700 --> 53:34.100
And that's a little much

53:34.100 --> 53:35.140
to send over the phone

53:35.140 --> 53:35.920
network when you consider

53:35.920 --> 53:37.820
that this specification was

53:37.820 --> 53:38.960
kind of derived in the

53:38.960 --> 53:40.760
50s and 60s.

53:40.760 --> 53:44.260
So what happens is something

53:44.260 --> 53:45.000
called mu-law

53:45.000 --> 53:45.640
compounding.

53:46.060 --> 53:47.640
And that basically uses a

53:47.640 --> 53:49.060
logarithmic scale to

53:49.060 --> 53:53.480
compress, to give a lot of

53:53.480 --> 53:55.760
resolution to the voice

53:55.760 --> 53:56.920
frequencies close to the

53:56.920 --> 53:57.880
center of the amplitude,

53:58.660 --> 53:59.400
close to the center of the

53:59.400 --> 54:00.780
waveform at the lower

54:00.780 --> 54:01.860
amplitudes where most of the

54:01.860 --> 54:02.500
action happens.

54:03.000 --> 54:05.000
And it still allows you to do

54:05.000 --> 54:06.180
higher amplitudes, though it's

54:06.180 --> 54:06.800
less resolution.

54:06.800 --> 54:07.920
But honestly, at those

54:07.920 --> 54:09.760
higher amplitudes, the

54:09.760 --> 54:10.920
resolution doesn't matter

54:10.920 --> 54:11.400
so much.

54:12.160 --> 54:13.960
So basically, you get 16

54:13.960 --> 54:14.940
bits of apparent audio

54:14.940 --> 54:16.080
quality and 8 bits of

54:16.080 --> 54:17.280
address space.

54:19.020 --> 54:20.840
However, 64 kilobits a second

54:20.840 --> 54:23.040
is quite a bit too much for

54:23.040 --> 54:24.580
some people, especially on

54:24.580 --> 54:25.980
low bandwidth connections or

54:25.980 --> 54:27.280
in cases where a lot of

54:27.280 --> 54:28.260
telephone calls have to be

54:28.260 --> 54:28.940
put to your connection

54:28.940 --> 54:30.680
suddenly that just doesn't

54:30.680 --> 54:31.280
have enough bandwidth.

54:31.740 --> 54:32.680
So there are various

54:32.680 --> 54:34.260
compression schemes which are

54:34.260 --> 54:36.300
used to further compress voice

54:36.300 --> 54:38.020
and further encode the voice

54:38.020 --> 54:39.800
into a smaller amount of

54:39.800 --> 54:40.020
data.

54:40.940 --> 54:42.420
The first one is called

54:42.420 --> 54:44.100
adaptive differential pulse

54:44.100 --> 54:44.840
code modulation.

54:45.820 --> 54:47.420
It's a takeoff on regular

54:47.420 --> 54:48.360
differential pulse code

54:48.360 --> 54:49.360
modulation, which instead of

54:49.360 --> 54:50.520
using an 8-bit sample,

54:50.640 --> 54:51.500
uses 4 bits.

54:51.540 --> 54:52.520
And what it does is instead

54:52.520 --> 54:54.920
of encoding each sample

54:54.920 --> 54:56.740
individually, it describes the

54:56.740 --> 54:58.000
change from one sample to

54:58.000 --> 54:58.420
the next.

54:59.140 --> 55:01.220
So it uses 4 bits regardless

55:01.220 --> 55:02.600
of the original source

55:02.600 --> 55:03.040
resolution.

55:03.040 --> 55:04.740
And that can kind of get

55:04.740 --> 55:06.060
ugly if you've got a really

55:06.060 --> 55:07.500
high-frequency sound.

55:08.420 --> 55:09.640
So adaptive differential

55:09.640 --> 55:11.760
PCM uses a varying number

55:11.760 --> 55:12.700
of bits depending on the

55:12.700 --> 55:13.700
complexity of the sample.

55:14.200 --> 55:15.720
However, it's capped at 32

55:15.720 --> 55:16.900
kilobits a second, so you

55:16.900 --> 55:18.160
will lose a little tiny bit

55:18.160 --> 55:18.700
of resolution.

55:21.580 --> 55:23.920
LPC is linear predictive

55:23.920 --> 55:24.280
coding.

55:25.200 --> 55:26.720
What it does is it uses

55:26.720 --> 55:27.980
bow coders to compress the

55:27.980 --> 55:28.780
speech even further.

55:29.480 --> 55:31.920
Instead of actually compressing

55:31.920 --> 55:32.980
the speech itself, what

55:32.980 --> 55:34.860
happens is it describes how

55:34.860 --> 55:35.860
to regenerate that speech

55:35.860 --> 55:38.560
on the other end, which

55:38.560 --> 55:39.800
kind of works, although

55:39.800 --> 55:41.540
vocoders are also used in

55:41.540 --> 55:43.780
the singing synthesizer

55:43.780 --> 55:44.540
effects in a lot of

55:44.540 --> 55:45.060
modern music.

55:45.220 --> 55:46.380
So if you listen to your

55:46.380 --> 55:47.800
mobile phone or your

55:47.800 --> 55:48.680
compressed audio really

55:48.680 --> 55:49.560
carefully, you can actually

55:49.560 --> 55:50.500
start to hear that sort of

55:50.500 --> 55:50.800
stuff.

55:50.800 --> 55:59.100
So those are the main types of

55:59.100 --> 55:59.780
compression schemes.

56:00.100 --> 56:01.900
So as we went over, on the

56:01.900 --> 56:03.680
PSTN, it's 64 kilobits a

56:03.680 --> 56:04.840
second synchronous bandwidth

56:04.840 --> 56:05.980
for wireline telephones.

56:06.560 --> 56:07.760
MU-Law companding in North

56:07.760 --> 56:09.820
America and I believe Japan, and

56:09.820 --> 56:11.120
A-Law companding in the rest of

56:11.120 --> 56:11.500
the world.

56:12.220 --> 56:13.560
If you're doing bit robbing in

56:13.560 --> 56:15.660
band, it's 56 kilobits a second

56:15.660 --> 56:17.460
instead of 64, but it sounds

56:17.460 --> 56:18.300
roughly the same.

56:18.300 --> 56:20.200
And essentially what bit robbing

56:20.200 --> 56:22.220
is, is it takes a little, it

56:22.220 --> 56:24.500
takes a bit every sample and

56:24.500 --> 56:25.660
says whether or not the line

56:25.660 --> 56:26.980
has been supervised or it does

56:26.980 --> 56:28.420
other type of area signaling in

56:28.420 --> 56:28.580
it.

56:29.140 --> 56:29.460
Right.

56:31.640 --> 56:34.840
So for mobile phones, which

56:34.840 --> 56:36.600
are, which obviously sound

56:36.600 --> 56:38.720
worse, you only get between 4

56:38.720 --> 56:40.380
and 13 kilobits a second as

56:40.380 --> 56:41.580
opposed to 64, you've got

56:41.580 --> 56:42.340
another record of a telephone

56:42.340 --> 56:42.700
network.

56:43.280 --> 56:43.500
Yikes.

56:43.940 --> 56:44.740
Yeah, there's all sorts of

56:44.740 --> 56:46.220
crazy audio codecs and as I'm

56:46.220 --> 56:47.300
sure many of you know, it

56:47.300 --> 56:48.280
sounds like crap.

56:48.300 --> 56:51.980
So what are the costs of speech

56:51.980 --> 56:52.380
compression?

56:53.220 --> 56:55.080
Well, first off, there's an

56:55.080 --> 56:56.840
increased CPU load required for

56:56.840 --> 56:57.560
transcoding.

56:57.900 --> 56:59.040
If you're doing everything in

56:59.040 --> 57:00.400
MULA, you know, the CPU doesn't

57:00.400 --> 57:01.060
have to do any work.

57:01.120 --> 57:01.920
It just has to switch the

57:01.920 --> 57:03.180
packets and that's really easy.

57:03.280 --> 57:06.640
I mean, even a 286, I think, or a

57:06.640 --> 57:09.260
386 can route to Ethernet packets

57:09.260 --> 57:10.760
fast enough to saturate T1.

57:11.740 --> 57:14.300
So as long as it's just telling the

57:14.300 --> 57:15.380
packets where to go, there's not a

57:15.380 --> 57:16.360
lot of load that's required.

57:16.360 --> 57:18.340
But if you've got to compress the

57:18.340 --> 57:20.580
audio from, you know, MULA down to

57:20.580 --> 57:23.240
GSM or something, then the CPU has

57:23.240 --> 57:23.940
to do that work.

57:24.480 --> 57:26.600
And so it cuts down on the capacity of

57:26.600 --> 57:28.020
your asterisk box to handle calls.

57:28.380 --> 57:32.540
That 790 call box we described

57:32.540 --> 57:35.220
earlier, when you go to GSM, it drops

57:35.220 --> 57:37.180
down to maybe 100 to 200 concurrent

57:37.180 --> 57:37.640
calls.

57:37.640 --> 57:40.180
That's pretty CPU intensive.

57:41.180 --> 57:43.060
There is no guarantee that two pieces

57:43.060 --> 57:44.220
of equipment will speak the same

57:44.220 --> 57:45.800
codecs, and this is especially true if

57:45.800 --> 57:47.120
using some sort of non-standard

57:47.120 --> 57:49.880
bitrate or some weird variation on a

57:49.880 --> 57:50.260
codec.

57:50.960 --> 57:52.840
That may work well for you, but may be

57:52.840 --> 57:54.260
completely incompatible with everyone

57:54.260 --> 57:54.540
else.

57:54.860 --> 57:55.080
Yes.

57:56.240 --> 57:58.280
Some codecs require licensing, so you

57:58.280 --> 57:59.900
have to actually pay money to use them.

58:00.700 --> 58:05.000
The G.729 codec from Digium requires a

58:05.000 --> 58:08.280
$10 license per box per channel.

58:08.840 --> 58:10.180
So if you've got a box and you want to

58:10.180 --> 58:12.660
have, you know, say you have two boxes and

58:12.660 --> 58:13.900
you want to have, you know, five telephone

58:14.600 --> 58:16.540
calls between them at any given time using

58:16.540 --> 58:19.780
that codec, you have to buy five licenses

58:19.780 --> 58:22.500
for each box at $10 a pop.

58:22.500 --> 58:25.540
Yeah, well, that sounds expensive.

58:26.100 --> 58:26.760
Yeah, it does.

58:27.620 --> 58:29.060
And the other thing is that codecs don't

58:29.060 --> 58:30.880
handle all sorts of sounds that well.

58:31.280 --> 58:32.980
People will have trouble understanding

58:32.980 --> 58:34.700
certain words, and it's difficult to

58:34.700 --> 58:36.020
understand people who have poor diction.

58:36.840 --> 58:38.220
And when you think about it, it's very

58:38.220 --> 58:38.520
thin.

58:39.600 --> 58:41.160
Your diction isn't all that bad.

58:41.980 --> 58:44.600
I have, I stumble over words a lot.

58:45.340 --> 58:46.820
I'm sure mine's just as horrible.

58:48.780 --> 58:50.660
But if you think about it, you know, the

58:50.660 --> 58:53.640
codec was designed to compress speech, but

58:53.640 --> 59:00.040
you know, there are cases where, what was

59:00.040 --> 59:00.380
I going to say?

59:00.480 --> 59:01.820
The codecs are designed to compress

59:01.820 --> 59:02.940
speech, but they're designed under the

59:02.940 --> 59:03.960
assumption that people are going to be

59:03.960 --> 59:04.820
talking normally.

59:05.360 --> 59:07.660
And when they do, you know, tests, they

59:07.660 --> 59:09.820
find people who enunciate, and they

59:09.820 --> 59:11.640
enunciate and they speak in, you know,

59:11.660 --> 59:12.880
perfectly standard English.

59:13.340 --> 59:15.300
But the standard and the vernacular are a

59:15.300 --> 59:15.780
bit different.

59:16.380 --> 59:18.520
And so, you know, if you mumble or if you

59:18.520 --> 59:20.580
have poor diction or, you know,

59:20.580 --> 59:22.180
whatever, it's going to sound like

59:22.180 --> 59:22.320
crap.

59:22.500 --> 59:24.240
I think a very good, interesting way to

59:24.240 --> 59:25.500
put this, it's a lot like handwriting

59:25.500 --> 59:26.060
recognition.

59:26.620 --> 59:27.580
If you have a person with perfect

59:27.580 --> 59:28.660
handwriting, you'll work well.

59:28.720 --> 59:29.860
If you have someone like me who looks

59:29.860 --> 59:32.120
like, you know, a doctor writing it,

59:32.280 --> 59:33.660
it'll fail miserably.

59:35.080 --> 59:37.400
And the other thing is that, you know,

59:37.420 --> 59:38.600
there are a lot of sounds on the phone

59:38.600 --> 59:39.340
that aren't voice.

59:40.080 --> 59:42.160
Background noise, and especially music on

59:42.160 --> 59:42.460
hold.

59:42.740 --> 59:44.420
In codec land, that's pure torture.

59:45.440 --> 59:46.880
You can be like Oedipus and gouge your

59:46.880 --> 59:47.300
eyes out.

59:47.300 --> 59:50.300
And some of them are so absolutely

59:50.300 --> 59:51.820
horrible that it'll even make you have

59:51.820 --> 59:52.540
sex with your mother.

59:55.000 --> 59:56.460
Someone actually came up with that during

59:56.460 --> 59:57.980
our DEF CON presentation, and we just

59:57.980 --> 59:59.020
absolutely loved that term.

59:59.220 --> 01:00:00.040
We thought it was a hoot.

01:00:00.960 --> 01:00:02.400
Thank you, whoever you are, if you're

01:00:02.400 --> 01:00:03.020
listening to the show.

01:00:03.900 --> 01:00:05.740
Anyway, Strom, what are the benefits of

01:00:05.740 --> 01:00:06.320
speech compression?

01:00:06.800 --> 01:00:07.980
There has to be one benefit.

01:00:08.380 --> 01:00:09.780
There's only one bullet point on this

01:00:09.780 --> 01:00:11.680
slide, and that's each call uses less

01:00:11.680 --> 01:00:12.020
bandwidth.

01:00:12.020 --> 01:00:15.540
That's the only benefit of speech

01:00:15.540 --> 01:00:15.940
compression.

01:00:16.280 --> 01:00:18.520
So, if you've got the bandwidth to throw

01:00:18.520 --> 01:00:20.720
at your calls, please don't compress

01:00:20.720 --> 01:00:20.920
them.

01:00:21.020 --> 01:00:22.080
Use MULA or ALA.

01:00:24.720 --> 01:00:27.880
So, what codecs are supported by

01:00:27.880 --> 01:00:28.280
asterisk?

01:00:28.800 --> 01:00:31.300
There's G.711, which is MULA or ALA

01:00:31.300 --> 01:00:31.800
commanding.

01:00:32.400 --> 01:00:35.020
There's G.726, which is 32 kilobits a

01:00:35.020 --> 01:00:36.280
second ADPCM.

01:00:36.280 --> 01:00:40.720
There's G.729, which is a kind of linear

01:00:40.720 --> 01:00:43.280
predictive codec, which uses a code table to

01:00:43.280 --> 01:00:44.600
regenerate the sound.

01:00:45.520 --> 01:00:48.120
So, this is kind of the same concept as the

01:00:48.120 --> 01:00:48.500
vocoder.

01:00:49.040 --> 01:00:51.540
It says, okay, this sound sounds like code

01:00:51.540 --> 01:00:54.240
number 35, so play code number 35 for two

01:00:54.240 --> 01:00:54.560
frames.

01:00:55.140 --> 01:00:57.860
And this one sounds like 72, so play 72 for a

01:00:57.860 --> 01:00:58.040
frame.

01:00:59.520 --> 01:01:01.940
And G.729 requires the license from Digium.

01:01:03.440 --> 01:01:06.060
There's GSM, which is 13 kilobits a second.

01:01:06.280 --> 01:01:09.380
Which is a predictive codec, and that's the

01:01:09.380 --> 01:01:11.300
one that's used on GSM phones.

01:01:11.480 --> 01:01:12.000
Surprise, surprise.

01:01:12.580 --> 01:01:12.960
Wow.

01:01:13.380 --> 01:01:15.760
So, if you want your desk phone to sound as

01:01:15.760 --> 01:01:17.580
bad as your mobile phone, you can use GSM.

01:01:19.740 --> 01:01:21.860
There's the Internet Low Bandwidth Codec,

01:01:21.940 --> 01:01:24.780
which is the 13.3 kilobits per second LPC

01:01:24.780 --> 01:01:25.840
used by Skype.

01:01:27.460 --> 01:01:30.460
And it sounds passively okay, but for people

01:01:30.460 --> 01:01:33.560
who rave about Skype's audio quality, it sounds

01:01:33.560 --> 01:01:36.740
just like ILBC to me, and that's what it is.

01:01:37.020 --> 01:01:38.460
So, sorry you lose.

01:01:39.780 --> 01:01:41.800
There's also an open source codec called

01:01:41.800 --> 01:01:44.080
Speaks, S-P-E-E-X.

01:01:44.820 --> 01:01:47.840
It's also a 13.3 kilobits per second code excited

01:01:47.840 --> 01:01:49.440
linear prediction, much like GSM.

01:01:49.440 --> 01:01:52.040
And I think it's based on the Augvorbis stuff.

01:01:53.500 --> 01:01:58.740
And finally, there is LPC-10, which is for you to use

01:01:58.740 --> 01:02:01.620
in situations where you've got no bandwidth whatsoever

01:02:01.620 --> 01:02:03.120
and you still need to get a phone call through.

01:02:03.420 --> 01:02:06.880
This is 2.4 kilobits per second linear predictive coding,

01:02:07.100 --> 01:02:09.900
and it sounds more ghastly than you can possibly imagine.

01:02:09.900 --> 01:02:12.860
And he's not kidding about that.

01:02:13.440 --> 01:02:15.740
And just to prove how ghastly it sounds,

01:02:15.840 --> 01:02:17.140
I'm going to have up on my website,

01:02:17.280 --> 01:02:19.980
blackratchet.org, a bunch of...

01:02:19.980 --> 01:02:22.160
If you remember from our first episode, 105,

01:02:22.440 --> 01:02:25.760
we had a song from this band called Red Eye Flight.

01:02:25.820 --> 01:02:26.620
It was called Natalie.

01:02:27.280 --> 01:02:30.680
And what we have done is we got permission from them

01:02:30.680 --> 01:02:33.100
to use it, and basically they released it

01:02:33.100 --> 01:02:33.700
at Creative Commons.

01:02:34.540 --> 01:02:36.360
And what we've done is we've encoded them

01:02:36.360 --> 01:02:38.880
with various old codecs we talked about.

01:02:38.880 --> 01:02:43.620
So essentially, it sounds okay in some, like U-Law,

01:02:43.720 --> 01:02:45.800
and it sounds like crap in a lot of it.

01:02:46.000 --> 01:02:47.260
And actually, speaking of U-Law,

01:02:47.360 --> 01:02:48.780
you're listening right now to U-Law

01:02:48.780 --> 01:02:51.600
because we both use U-Law to record the show.

01:02:51.880 --> 01:02:54.560
And it sounds like phones, but, you know,

01:02:54.700 --> 01:02:56.100
it doesn't sound that bad.

01:02:56.660 --> 01:02:59.560
It would sound a whole lot worse if we were using LPC-10.

01:02:59.920 --> 01:03:00.040
Yeah.

01:03:03.080 --> 01:03:05.380
No, it would just sound like robots talking,

01:03:05.460 --> 01:03:07.300
and you would really, really want to go have sex

01:03:07.300 --> 01:03:08.660
with your mother after listening to that one.

01:03:09.160 --> 01:03:09.480
Yes.

01:03:09.640 --> 01:03:09.980
Oh, yeah.

01:03:10.220 --> 01:03:10.860
We should do.

01:03:10.940 --> 01:03:12.300
We should re-encode this with LPC-10.

01:03:12.900 --> 01:03:13.060
Yeah.

01:03:13.240 --> 01:03:15.580
Anyway, let's get into interconnecting asterisk

01:03:15.580 --> 01:03:18.220
because, you know, asterisk is fun.

01:03:18.300 --> 01:03:20.280
You can talk to other people using asterisk.

01:03:20.360 --> 01:03:21.460
You can talk to people using VoIP.

01:03:21.580 --> 01:03:23.360
But what happens if you want to call your mom

01:03:23.360 --> 01:03:25.200
who doesn't have some type of VoIP set up?

01:03:25.660 --> 01:03:27.080
And presumably, you're calling your mom

01:03:27.080 --> 01:03:28.260
not to ask her out on a date.

01:03:29.160 --> 01:03:30.120
Yeah, okay.

01:03:30.120 --> 01:03:30.200
Okay.

01:03:31.600 --> 01:03:32.880
Let's just drop that, all right?

01:03:33.880 --> 01:03:35.520
But it's so fun to talk about.

01:03:36.400 --> 01:03:36.980
Oh, yeah.

01:03:37.080 --> 01:03:37.820
What are you, from Arkansas?

01:03:38.320 --> 01:03:38.720
No.

01:03:38.720 --> 01:03:40.240
Not too many from Arkansas out there.

01:03:40.340 --> 01:03:40.720
Sorry.

01:03:40.720 --> 01:03:43.320
Anyway, let's go over various companies

01:03:43.320 --> 01:03:46.400
that provide an ability to take your VoIP conversation

01:03:46.400 --> 01:03:48.720
and forward it over to the PSTN,

01:03:48.800 --> 01:03:50.300
which is the Public Switch Telephone Network.

01:03:51.260 --> 01:03:53.080
First company we're going to talk about is NuFone.

01:03:53.480 --> 01:03:54.420
NuFone is cool.

01:03:54.520 --> 01:03:55.240
I like NuFone.

01:03:55.460 --> 01:03:57.260
They have very cheap rates,

01:03:57.400 --> 01:03:59.640
and they're essentially geared for asterisk.

01:04:00.040 --> 01:04:01.940
They use asterisk exclusively, I believe.

01:04:02.780 --> 01:04:04.240
Their caller ID is spoofable,

01:04:04.240 --> 01:04:07.660
and they have insanely easy to provision 800 numbers,

01:04:07.780 --> 01:04:08.980
or 888 or 866.

01:04:09.720 --> 01:04:10.960
Essentially, you click a button,

01:04:11.100 --> 01:04:12.220
and they send you an email saying,

01:04:12.340 --> 01:04:12.760
here's your number.

01:04:12.880 --> 01:04:13.760
Use it wherever you want.

01:04:14.340 --> 01:04:17.760
And I never thought I'd have about five or six 800 numbers

01:04:17.760 --> 01:04:18.440
ever to my name.

01:04:18.440 --> 01:04:21.220
And with NuFone, I do.

01:04:21.360 --> 01:04:21.860
Thank God.

01:04:22.520 --> 01:04:24.100
NuFone's cool because they're very easygoing.

01:04:25.240 --> 01:04:27.100
Essentially, when I first set my account up with them,

01:04:27.180 --> 01:04:28.340
I said, what happens?

01:04:28.660 --> 01:04:30.200
I PayPal them a bunch of money,

01:04:30.360 --> 01:04:33.260
and they said, okay, well, that'll be fine.

01:04:33.880 --> 01:04:35.860
So what happens when my PayPal money runs out?

01:04:35.920 --> 01:04:36.900
Are you going to shut off my service?

01:04:37.300 --> 01:04:38.440
Oh, no, we'll just send you an email.

01:04:39.180 --> 01:04:40.620
Just send us some money, and we'll be fine.

01:04:41.100 --> 01:04:41.860
Oh, okay.

01:04:43.960 --> 01:04:46.560
They have proper call completion progress,

01:04:46.560 --> 01:04:48.920
and we'll go over this later about why this is such a big deal.

01:04:49.000 --> 01:04:52.680
But essentially, it allows you to hear rings, busies, and intercepts,

01:04:52.680 --> 01:04:54.040
which for some people,

01:04:54.120 --> 01:04:56.120
that's a major problem with their VoIP providers.

01:04:56.920 --> 01:05:00.480
The problem with NuFone is they're Michigan DIDs only.

01:05:00.600 --> 01:05:01.660
DIDs are phone numbers.

01:05:02.320 --> 01:05:04.280
So you can only get phone numbers in Michigan,

01:05:04.400 --> 01:05:05.940
which is good if your parents live in Michigan

01:05:05.940 --> 01:05:09.100
or if you want to call actually has unlimited long distance.

01:05:09.240 --> 01:05:11.560
But for most of us, that doesn't do very well.

01:05:12.020 --> 01:05:13.400
They're also not too freak-friendly.

01:05:13.400 --> 01:05:19.820
They disabled caller ID spoofing during DC12 with Lucky 225 and Strom.

01:05:20.020 --> 01:05:22.600
I believe Not Theory got a cease and desist order from them.

01:05:23.560 --> 01:05:26.400
And it makes me to believe that they don't trust us for some reason.

01:05:27.160 --> 01:05:30.940
I think they also turned off all caller ID delivery during DEFCON 13.

01:05:31.880 --> 01:05:32.740
I heard that.

01:05:32.800 --> 01:05:34.420
I didn't actually get a chance to play with that,

01:05:34.520 --> 01:05:35.760
so I can't say that.

01:05:36.300 --> 01:05:36.460
Yes.

01:05:37.380 --> 01:05:38.220
Astrolink is cool.

01:05:38.680 --> 01:05:39.500
Astrolink is other kind.

01:05:39.980 --> 01:05:41.360
You know more about Astrolink.

01:05:41.360 --> 01:05:41.800
Yeah.

01:05:42.060 --> 01:05:45.200
Well, we were really, really happy with Astrolink until DEFCON happened.

01:05:45.720 --> 01:05:48.440
So for the most part, they're reliable,

01:05:48.640 --> 01:05:51.060
although for some reason lately they've been really jittery,

01:05:51.620 --> 01:05:53.480
even with my own box.

01:05:53.640 --> 01:05:55.640
We set up a system for DEFCON,

01:05:55.720 --> 01:05:57.920
which we won't go into detail here because we don't have the time.

01:05:58.260 --> 01:06:00.800
But we set up an asterisk-based schedule of the convention,

01:06:01.280 --> 01:06:03.460
and we decided to use Astrolink for our carrier

01:06:03.460 --> 01:06:07.160
because they said they would be more than happy to handle that much load.

01:06:07.160 --> 01:06:09.920
And all of our calls became jittery.

01:06:10.760 --> 01:06:12.980
And so the jitter problem continues.

01:06:13.120 --> 01:06:15.300
I'm sure it will go away in the near future,

01:06:15.380 --> 01:06:17.460
but for the time being it's jittery.

01:06:17.560 --> 01:06:19.600
But up until DEFCON happened,

01:06:19.720 --> 01:06:21.840
Astrolink was nothing but reliable for me.

01:06:22.100 --> 01:06:23.200
So I'll sing the praises there.

01:06:23.920 --> 01:06:25.860
They do their inbound via toll-free numbers,

01:06:26.060 --> 01:06:28.460
and they deliver class of service,

01:06:28.600 --> 01:06:31.100
also known as ANII digits if you want it.

01:06:31.780 --> 01:06:33.340
And they also do proper call completion.

01:06:33.460 --> 01:06:35.460
The only problem is the account management interface

01:06:35.460 --> 01:06:37.440
is a little kludgy on their website,

01:06:37.640 --> 01:06:39.000
but it's actually gotten better.

01:06:40.060 --> 01:06:40.460
Kludgy.

01:06:40.760 --> 01:06:41.240
Kludge.

01:06:41.600 --> 01:06:43.240
Kludgy, kludgy, close enough.

01:06:44.360 --> 01:06:45.520
I can't stand that.

01:06:46.740 --> 01:06:47.660
Voice Pulse Connect.

01:06:48.320 --> 01:06:49.820
Well, you don't hear me insulting Orge.

01:06:50.600 --> 01:06:52.080
Yeah, I got away from that.

01:06:52.140 --> 01:06:52.520
Leave me alone.

01:06:53.640 --> 01:06:54.860
Voice Pulse Connect is cool.

01:06:55.440 --> 01:06:57.440
Their pros is they have unlimited incoming minutes

01:06:57.440 --> 01:06:58.560
on inbound EECS calls.

01:06:58.560 --> 01:07:00.700
They're inbound numbers.

01:07:00.880 --> 01:07:02.940
They have inbound numbers everywhere,

01:07:03.300 --> 01:07:04.800
and they're the only EECS provider

01:07:04.800 --> 01:07:06.080
that actually does this.

01:07:06.900 --> 01:07:09.480
They have proper call progress because...

01:07:09.480 --> 01:07:11.000
Does Astrolink have proper call progress?

01:07:11.360 --> 01:07:11.580
Yeah.

01:07:12.120 --> 01:07:12.720
I just did that.

01:07:13.100 --> 01:07:13.480
Oh, okay.

01:07:13.540 --> 01:07:13.820
I forget.

01:07:13.960 --> 01:07:14.240
No, no.

01:07:14.280 --> 01:07:15.360
Voice Pulse is the one that we don't like.

01:07:15.400 --> 01:07:16.140
We'll get to them next.

01:07:16.940 --> 01:07:18.900
But the problem is with Voice Pulse

01:07:18.900 --> 01:07:21.880
is that they are the most expensive EECS providers

01:07:21.880 --> 01:07:23.540
for outbound call termination.

01:07:24.540 --> 01:07:25.400
How much do they cost?

01:07:25.400 --> 01:07:26.560
Two point...

01:07:26.560 --> 01:07:28.740
Two point, like...

01:07:28.740 --> 01:07:29.140
Seven.

01:07:29.700 --> 01:07:31.540
Yeah, two point seven nine or two point eight

01:07:31.540 --> 01:07:32.320
or something like that.

01:07:32.560 --> 01:07:32.920
Yes.

01:07:33.160 --> 01:07:33.600
And meanwhile...

01:07:33.600 --> 01:07:34.240
They're only three cents a minute.

01:07:34.640 --> 01:07:34.840
Yeah.

01:07:34.960 --> 01:07:36.200
And a new phone, for example,

01:07:36.380 --> 01:07:38.160
costs two cents a minute.

01:07:38.540 --> 01:07:40.040
And the next provider, VoIP Chess,

01:07:40.460 --> 01:07:42.700
is going to cost one point three cents a minute.

01:07:42.800 --> 01:07:44.120
And that's their major pro.

01:07:44.500 --> 01:07:45.240
They're cheap.

01:07:46.180 --> 01:07:47.480
Actually, I think they don't...

01:07:47.480 --> 01:07:48.680
We got corrected on that.

01:07:48.720 --> 01:07:50.740
I think it's like one point two nine cents a minute.

01:07:50.980 --> 01:07:51.260
Yeah.

01:07:51.560 --> 01:07:52.420
One point two nine.

01:07:52.420 --> 01:07:53.080
So, yeah.

01:07:53.080 --> 01:07:53.800
You pay a whole mil.

01:07:54.700 --> 01:07:54.940
Yeah.

01:07:55.080 --> 01:07:56.360
Shouts to Avid for that one.

01:07:57.560 --> 01:08:00.060
VoIP Chat, they don't have incoming service,

01:08:00.160 --> 01:08:01.420
so you can't get phone numbers from them.

01:08:02.000 --> 01:08:05.100
Their caller ID delivery is unreliable at best.

01:08:05.560 --> 01:08:07.460
And they don't have proper call completion.

01:08:07.700 --> 01:08:09.160
So, please be sure about this.

01:08:09.300 --> 01:08:11.540
I think I tried spoofing with VoIP Jet recently,

01:08:11.620 --> 01:08:12.480
and it started working.

01:08:13.740 --> 01:08:15.220
Proper call completion or caller ID?

01:08:15.460 --> 01:08:17.400
The caller ID and the proper call completion.

01:08:17.600 --> 01:08:19.520
In fact, let's do a little test,

01:08:19.580 --> 01:08:21.420
since I've got my asterisk box in front of me.

01:08:21.860 --> 01:08:22.200
Okay.

01:08:26.280 --> 01:08:27.100
Let me see.

01:08:27.600 --> 01:08:30.060
Let me do a disconnected number.

01:08:33.220 --> 01:08:34.980
508-995-9972.

01:08:35.600 --> 01:08:37.700
I like 310-Gladstone-4-9999.

01:08:37.700 --> 01:08:38.700
All right.

01:08:41.160 --> 01:08:41.840
Oh, wow.

01:08:42.980 --> 01:08:44.060
It's so busy now.

01:08:45.300 --> 01:08:47.080
Please try your call again later.

01:08:47.500 --> 01:08:48.380
So, yes.

01:08:49.020 --> 01:08:51.800
VoIP Jet now does proper call completion,

01:08:51.940 --> 01:08:52.560
so you can hear...

01:08:52.560 --> 01:08:52.860
Hallelujah!

01:08:52.860 --> 01:08:53.260
...and whatnot.

01:08:54.120 --> 01:08:56.000
So, disregard that bit on the slide.

01:08:56.120 --> 01:09:00.200
And I think they now also do caller ID correctly.

01:09:02.300 --> 01:09:02.700
Okay.

01:09:02.860 --> 01:09:04.020
And our final provider tonight,

01:09:04.140 --> 01:09:05.540
and this is basically where we're going to wrap it up.

01:09:05.600 --> 01:09:06.760
We have more of this presentation.

01:09:06.920 --> 01:09:08.420
I think we're going to have to break this over two parts.

01:09:08.720 --> 01:09:08.940
Mm-hmm.

01:09:09.080 --> 01:09:10.180
It's Broadvoice.

01:09:10.540 --> 01:09:12.160
And the cool thing about Broadvoice

01:09:12.160 --> 01:09:15.320
is that they have cheap direct number dial numbers

01:09:15.320 --> 01:09:16.160
in most rate centers.

01:09:16.280 --> 01:09:17.040
I got one in Boston.

01:09:18.400 --> 01:09:19.380
From what we can tell,

01:09:19.440 --> 01:09:20.420
they're run by phone freaks,

01:09:20.460 --> 01:09:21.340
which is always a plus.

01:09:21.340 --> 01:09:26.060
In fact, when you order their service

01:09:26.060 --> 01:09:30.280
and you buy the hardware that they ship to you,

01:09:30.340 --> 01:09:32.740
they also ship to you a little pin,

01:09:33.420 --> 01:09:34.540
which is the Bell logo

01:09:34.540 --> 01:09:36.480
with the no-smoking cross through it.

01:09:39.040 --> 01:09:41.180
Which is kind of sad, but cool at the same point.

01:09:41.500 --> 01:09:41.700
Yeah.

01:09:42.280 --> 01:09:42.620
Yes.

01:09:43.300 --> 01:09:44.840
So, the other cool thing about Broadvoice

01:09:44.840 --> 01:09:47.260
is they have a 24-by-7 phone support,

01:09:47.380 --> 01:09:49.000
so you can call them up any time.

01:09:49.000 --> 01:09:51.760
And the coolest feature, in my opinion,

01:09:51.860 --> 01:09:54.000
about Broadvoice is they have caller ID with name,

01:09:54.780 --> 01:09:56.360
which all of these other caller ID things

01:09:56.360 --> 01:09:57.120
that we were talking about,

01:09:57.380 --> 01:09:59.220
they only provide caller ID numbers.

01:09:59.840 --> 01:10:01.620
But this actually has CNAM lookups.

01:10:02.300 --> 01:10:02.480
Mm-hmm.

01:10:02.900 --> 01:10:05.640
However, the problem with them is that they are SIP only.

01:10:05.800 --> 01:10:07.360
They don't support EECs,

01:10:07.440 --> 01:10:09.000
which is something I always really want to like.

01:10:09.320 --> 01:10:10.680
They're actually based in Massachusetts,

01:10:10.860 --> 01:10:12.120
and I really want to just send them a resume

01:10:12.120 --> 01:10:15.260
and say, hire me and let me set up your EECs setup

01:10:15.260 --> 01:10:16.680
so I can use EECs with you.

01:10:17.780 --> 01:10:19.660
But I should actually do that,

01:10:19.680 --> 01:10:20.240
just for the hell of it.

01:10:21.480 --> 01:10:23.120
Broadvoice is prone to service outages.

01:10:23.280 --> 01:10:24.120
They had a nice...

01:10:24.960 --> 01:10:26.740
Gee, Strom,

01:10:26.880 --> 01:10:29.060
have you ever had a service outage with Broadvoice?

01:10:29.400 --> 01:10:30.020
Oh, well,

01:10:30.120 --> 01:10:32.140
my incoming number doesn't work right now.

01:10:33.320 --> 01:10:33.720
Wow.

01:10:33.980 --> 01:10:34.120
Yeah.

01:10:34.180 --> 01:10:35.520
See, how long has it not been working?

01:10:36.360 --> 01:10:37.960
I haven't really tested it,

01:10:38.040 --> 01:10:40.280
but apparently this has been out for several weeks now.

01:10:40.700 --> 01:10:41.060
Yes.

01:10:42.000 --> 01:10:43.120
What's their response to you?

01:10:44.100 --> 01:10:46.600
Their response to me when I called on Sunday was,

01:10:46.700 --> 01:10:48.740
well, we are getting engineers to look at it,

01:10:48.780 --> 01:10:49.840
and they will contact you.

01:10:50.400 --> 01:10:50.760
Yes.

01:10:50.820 --> 01:10:52.700
I heard someone say Broadvoice,

01:10:52.800 --> 01:10:53.580
when they say that,

01:10:53.660 --> 01:10:54.340
they're essentially saying,

01:10:54.600 --> 01:10:56.380
I'm going to hide under my desk now

01:10:56.380 --> 01:10:57.680
and hope you don't call back.

01:10:59.360 --> 01:11:01.340
I think someone said that on the asterisk,

01:11:01.400 --> 01:11:02.380
one of the asterisk lists.

01:11:02.640 --> 01:11:03.640
And for the most part,

01:11:03.720 --> 01:11:04.740
they also had a weekend

01:11:04.740 --> 01:11:05.780
where they got into their fight

01:11:05.780 --> 01:11:06.600
with Global Crossing,

01:11:07.120 --> 01:11:08.680
and Global Crossing cut them off,

01:11:08.780 --> 01:11:10.100
and no numbers were brought,

01:11:10.240 --> 01:11:11.220
inbound or outbound.

01:11:12.020 --> 01:11:12.740
That's annoying.

01:11:14.200 --> 01:11:15.080
How would you like it

01:11:15.080 --> 01:11:17.440
if your phone service dropped out for a weekend?

01:11:18.500 --> 01:11:19.460
Their phone support,

01:11:19.560 --> 01:11:20.520
while it's 24-7,

01:11:20.660 --> 01:11:22.260
is slow at best.

01:11:22.860 --> 01:11:24.860
I've waited on phone for hours

01:11:24.860 --> 01:11:26.520
at a very odd time,

01:11:26.600 --> 01:11:27.300
like 1 a.m.,

01:11:27.300 --> 01:11:28.660
when I would think no one would be calling.

01:11:29.580 --> 01:11:29.980
Apparently,

01:11:30.180 --> 01:11:31.640
the phone rings,

01:11:31.780 --> 01:11:33.920
and the guy kind of wakes up from his nap

01:11:33.920 --> 01:11:34.460
and decides,

01:11:34.600 --> 01:11:35.300
looks at the phone,

01:11:35.380 --> 01:11:35.540
says,

01:11:35.660 --> 01:11:37.960
maybe I'll get some coffee and a snack,

01:11:38.080 --> 01:11:39.100
and I'll have that first.

01:11:39.140 --> 01:11:41.600
I assume they're hiding under their desk still,

01:11:41.640 --> 01:11:41.960
or something.

01:11:42.840 --> 01:11:45.460
And while they have caller ID with name support,

01:11:45.700 --> 01:11:48.300
sometimes it's just very flaky.

01:11:48.300 --> 01:11:48.640
You know,

01:11:48.760 --> 01:11:50.400
the slide point says,

01:11:50.500 --> 01:11:50.600
you know,

01:11:50.660 --> 01:11:51.740
will CNAM work today?

01:11:52.460 --> 01:11:53.200
Not always.

01:11:53.340 --> 01:11:55.560
Sometimes it just gives me this strange number

01:11:55.560 --> 01:11:56.860
that's six digits long,

01:11:57.920 --> 01:12:00.820
and does the same number with the caller ID name.

01:12:00.960 --> 01:12:01.240
Of course,

01:12:01.380 --> 01:12:01.620
you know,

01:12:01.680 --> 01:12:02.880
sometimes it also says,

01:12:03.560 --> 01:12:03.780
you know,

01:12:03.820 --> 01:12:05.300
617-555,

01:12:05.500 --> 01:12:05.780
Boston,

01:12:05.900 --> 01:12:06.320
Massachusetts.

01:12:06.640 --> 01:12:06.940
Well,

01:12:07.140 --> 01:12:07.640
yeah,

01:12:07.900 --> 01:12:08.100
but,

01:12:09.060 --> 01:12:09.280
all right,

01:12:09.340 --> 01:12:09.940
555,

01:12:10.020 --> 01:12:11.320
it gives you a number,

01:12:11.600 --> 01:12:12.880
and it just says Boston,

01:12:12.940 --> 01:12:13.300
Massachusetts,

01:12:13.380 --> 01:12:14.480
rather than the actual name.

01:12:14.620 --> 01:12:14.780
So,

01:12:14.900 --> 01:12:16.200
it's flaky.

01:12:16.960 --> 01:12:17.360
Unfortunately,

01:12:17.660 --> 01:12:18.940
I haven't had a day yet

01:12:18.940 --> 01:12:20.660
where all the numbers come up as cat sex,

01:12:20.780 --> 01:12:23.120
but if they want to play that practical joke on me,

01:12:23.160 --> 01:12:23.640
that would be amusing.

01:12:24.160 --> 01:12:25.040
That would be amusing,

01:12:25.240 --> 01:12:25.540
indeed.

01:12:26.600 --> 01:12:27.000
So,

01:12:27.080 --> 01:12:27.200
anyway,

01:12:27.280 --> 01:12:29.020
we're just going to sort of blitz right through this,

01:12:29.120 --> 01:12:31.920
and we're going to continue this at some later point.

01:12:32.180 --> 01:12:33.620
We'll have asterisk part two.

01:12:34.600 --> 01:12:35.860
We won't do this next week,

01:12:35.900 --> 01:12:36.760
just so you know.

01:12:36.820 --> 01:12:38.580
We'll have some other topic for you,

01:12:38.580 --> 01:12:40.740
so you can get back to computers a little bit.

01:12:42.160 --> 01:12:44.720
What are we going to do next week?

01:12:44.760 --> 01:12:45.680
The future of telephony?

01:12:46.840 --> 01:12:47.300
I don't know.

01:12:47.340 --> 01:12:48.900
I think we should have a computer topic next week.

01:12:48.940 --> 01:12:50.460
Do you feel like a computer topic?

01:12:50.760 --> 01:12:52.260
Strom is in charge next week.

01:12:52.440 --> 01:12:52.620
You know,

01:12:53.140 --> 01:12:54.220
strap yourselves in,

01:12:54.300 --> 01:12:55.780
because Lord knows what he's going to do.

01:12:56.100 --> 01:12:58.060
I'm going to be on vacation on the weekend.

01:12:58.880 --> 01:12:59.420
All right.

01:12:59.780 --> 01:13:00.080
Well,

01:13:00.340 --> 01:13:03.480
I will have to think up a topic for next week.

01:13:03.840 --> 01:13:06.800
It's either going to be some sort of computer topic,

01:13:06.800 --> 01:13:07.120
maybe,

01:13:07.320 --> 01:13:07.580
you know,

01:13:08.100 --> 01:13:09.780
odd computer hardware stories,

01:13:10.700 --> 01:13:13.080
because I've been dealing with a lot of sun equipment lately,

01:13:13.080 --> 01:13:14.880
which is not PC equipment,

01:13:15.000 --> 01:13:15.240
obviously,

01:13:15.420 --> 01:13:17.160
or the future of telephony.

01:13:18.100 --> 01:13:19.440
We may have telephones.

01:13:19.640 --> 01:13:19.820
Okay.

01:13:20.340 --> 01:13:21.220
Strom is a phone freak.

01:13:21.400 --> 01:13:22.760
We never deny that.

01:13:23.560 --> 01:13:23.960
Well,

01:13:24.040 --> 01:13:26.200
I'm just thinking of things that will actually go over well.

01:13:26.700 --> 01:13:27.000
Yes.

01:13:27.280 --> 01:13:27.580
True.

01:13:28.120 --> 01:13:28.900
We don't want to suck.

01:13:29.440 --> 01:13:29.620
Yes.

01:13:29.620 --> 01:13:30.300
So,

01:13:30.540 --> 01:13:31.280
do you have any announcements?

01:13:31.980 --> 01:13:32.160
Hmm.

01:13:32.840 --> 01:13:33.240
Again,

01:13:33.540 --> 01:13:34.660
Strom's music review.

01:13:35.100 --> 01:13:36.300
Send in your song.

01:13:36.500 --> 01:13:37.620
Send in your demo album,

01:13:38.220 --> 01:13:39.600
and we'll play it,

01:13:39.680 --> 01:13:40.920
and we'll give you guys a review,

01:13:41.040 --> 01:13:42.940
and we'll get you guys in front of some listeners.

01:13:44.260 --> 01:13:45.420
Because we're cool like that.

01:13:45.700 --> 01:13:45.920
Yes.

01:13:46.660 --> 01:13:47.220
Let's see.

01:13:47.360 --> 01:13:48.340
Boston 2600,

01:13:48.500 --> 01:13:50.060
my Boston 2600 group,

01:13:50.080 --> 01:13:53.260
is trying to start an up-to-date list of current 2600 groups,

01:13:53.680 --> 01:13:56.680
and we want to start having a way of coordinating things

01:13:56.680 --> 01:13:58.700
with the various groups for hope and other things.

01:13:58.700 --> 01:14:01.780
We're calling the project 2600 United,

01:14:01.980 --> 01:14:03.440
and I think in a couple of weeks,

01:14:03.500 --> 01:14:05.980
you're going to have a couple of my good friends on,

01:14:06.040 --> 01:14:08.400
and we're going to discuss the various projects we have planned for hope

01:14:08.400 --> 01:14:10.340
and try to stir up some interest for them.

01:14:10.840 --> 01:14:11.160
Oh,

01:14:11.220 --> 01:14:12.820
and the other thing I totally forgot about.

01:14:13.400 --> 01:14:13.840
Speaking of that.

01:14:13.860 --> 01:14:13.880
Well,

01:14:13.880 --> 01:14:15.000
let me get the email address out here.

01:14:15.180 --> 01:14:15.200
So,

01:14:15.260 --> 01:14:18.460
that would be 2600United at gmail.com,

01:14:18.520 --> 01:14:20.960
or you can join us on FNET,

01:14:21.000 --> 01:14:21.980
which is the IRC thing,

01:14:22.040 --> 01:14:24.760
and we're either in pound Boston-2600

01:14:24.760 --> 01:14:26.940
or pound Boston-2600.

01:14:27.040 --> 01:14:27.580
Your choice.

01:14:27.580 --> 01:14:28.740
People are usually there,

01:14:29.260 --> 01:14:32.160
and I'm usually there 9 to 5 lurking.

01:14:32.560 --> 01:14:34.060
Just give me a couple minutes to respond,

01:14:34.120 --> 01:14:34.680
because I'm at work.

01:14:35.980 --> 01:14:36.240
So,

01:14:36.360 --> 01:14:37.280
just drop us a line,

01:14:37.340 --> 01:14:38.260
or you can just email me,

01:14:38.320 --> 01:14:40.040
and I'll point you into contact with the correct people.

01:14:41.300 --> 01:14:42.040
And you were saying,

01:14:42.260 --> 01:14:42.400
yeah,

01:14:42.440 --> 01:14:42.800
I forgot about,

01:14:42.860 --> 01:14:45.340
TORCON is coming up in San Diego in a couple of weeks.

01:14:45.980 --> 01:14:46.140
Oh,

01:14:46.140 --> 01:14:46.500
when's that?

01:14:46.700 --> 01:14:47.360
Do you have an,

01:14:47.580 --> 01:14:50.120
let me pull up the date.

01:14:50.220 --> 01:14:50.520
It's at

01:14:50.520 --> 01:14:51.620
TORCON.org,

01:14:51.740 --> 01:14:54.880
T-O-R-C-O-N.O-R-G.

01:14:56.420 --> 01:14:58.400
The Schmoo group should say you should go there.

01:14:58.580 --> 01:14:58.760
So,

01:14:58.920 --> 01:15:00.440
that's all I know about TORCON.

01:15:00.780 --> 01:15:01.000
Mm-hmm.

01:15:02.180 --> 01:15:02.400
Well,

01:15:02.440 --> 01:15:03.640
it's a two-track,

01:15:04.380 --> 01:15:08.000
it's from September 16th to the 18th at the San Diego Convention Center,

01:15:08.000 --> 01:15:09.980
and I will be there.

01:15:10.780 --> 01:15:12.640
And I think Natas is thinking about going,

01:15:12.760 --> 01:15:12.880
so.

01:15:12.900 --> 01:15:13.020
Yeah,

01:15:13.100 --> 01:15:13.500
Natas is definitely thinking about going.

01:15:13.500 --> 01:15:16.020
Run into Strom and run into Natas in San Diego.

01:15:16.460 --> 01:15:16.760
Mm-hmm.

01:15:18.800 --> 01:15:19.200
Anyway,

01:15:19.720 --> 01:15:20.040
Shouts?

01:15:20.500 --> 01:15:21.320
I have Shouts.

01:15:21.500 --> 01:15:24.500
I actually went into the IRC channel and asked who wanted Shouts.

01:15:24.600 --> 01:15:24.700
So,

01:15:24.780 --> 01:15:26.100
I have a Shouts the Ponyboy,

01:15:26.820 --> 01:15:28.020
Emmanuel Bobstein,

01:15:28.340 --> 01:15:29.300
Centro...

01:15:29.300 --> 01:15:31.520
I think that was Emmanuel Boobstein.

01:15:32.240 --> 01:15:32.640
Boobstein?

01:15:32.740 --> 01:15:33.680
I thought it was Bobstein.

01:15:33.940 --> 01:15:34.240
Boobstein,

01:15:34.260 --> 01:15:34.620
I don't know,

01:15:34.680 --> 01:15:34.920
whatever.

01:15:35.340 --> 01:15:35.720
He's new.

01:15:35.820 --> 01:15:36.180
I haven't seen,

01:15:36.260 --> 01:15:37.900
I think the first time I saw him was today.

01:15:38.580 --> 01:15:39.620
And Kyle L.

01:15:39.700 --> 01:15:41.140
wants me to say that he's lame.

01:15:41.320 --> 01:15:41.440
So,

01:15:41.560 --> 01:15:42.380
Kyle L.,

01:15:42.380 --> 01:15:43.020
you be lame.

01:15:43.040 --> 01:15:43.380
You're lame.

01:15:43.560 --> 01:15:44.160
Let's say it together.

01:15:44.380 --> 01:15:44.480
Yes.

01:15:44.900 --> 01:15:46.020
Kyle L.,

01:15:46.020 --> 01:15:47.140
you're lame.

01:15:47.540 --> 01:15:47.680
Yeah.

01:15:47.840 --> 01:15:48.140
Whatever.

01:15:48.200 --> 01:15:48.980
That didn't work so well.

01:15:49.780 --> 01:15:50.520
We're lame.

01:15:51.280 --> 01:15:51.560
Yes,

01:15:51.560 --> 01:15:51.920
we're lame.

01:15:51.980 --> 01:15:53.040
We can't coordinate.

01:15:54.760 --> 01:15:57.980
Our closing music is a group called Nordbeat,

01:15:57.980 --> 01:16:01.660
and I got this back from when mp3.com was active,

01:16:01.780 --> 01:16:02.280
dear God.

01:16:03.000 --> 01:16:04.180
It's called Nordbeat's Him,

01:16:04.440 --> 01:16:06.260
and I actually went to their website today,

01:16:06.260 --> 01:16:12.960
and they call themselves Nordbeat Trance Music and Software Company.

01:16:13.140 --> 01:16:13.260
So,

01:16:13.340 --> 01:16:14.400
I thought that was a hoot,

01:16:14.440 --> 01:16:15.980
and I'll just try to give them shouts out for that.

01:16:17.020 --> 01:16:17.420
Email,

01:16:17.560 --> 01:16:17.920
as always,

01:16:18.020 --> 01:16:19.560
at radioatbinrev.com,

01:16:19.560 --> 01:16:21.700
and I guess we'll see you next week.

01:16:21.880 --> 01:16:22.700
Same hack time.

01:16:22.980 --> 01:16:23.680
Same hack channel.

01:16:23.680 --> 01:16:23.720
Same hack channel.

01:16:23.720 --> 01:16:53.700
And I'll see you next week.

01:16:53.720 --> 01:17:23.700
And I'll see you next week.

01:17:23.720 --> 01:17:53.700
And I'll see you next week.

01:17:53.700 --> 01:17:54.620
And I'll see you next week.

01:17:54.620 --> 01:17:54.940
Yeah.

01:17:54.940 --> 01:17:55.660
And I'll see you next week.

01:17:55.700 --> 01:17:56.500
And I'll see you next week.

01:17:56.500 --> 01:18:26.480
Thank you.

01:18:26.500 --> 01:18:56.480
Thank you.

01:18:56.500 --> 01:19:26.480
Thank you.

01:19:26.500 --> 01:19:56.480
Thank you.

01:19:56.500 --> 01:19:58.500
Thank you.