Blue Box: The VoIP Security Podcast

RSS feed back...

It looks like FeedBurner finally refreshed its DNS info and the RSS feed is back in action. My apologies for the interruption. Please do let me know if there is anything else strange going on with the website or feed. Thanks.

Blue Box RSS feed dead - waiting for Feedburner to update its DNS

Ah, the joys of switching domain name providers. I transferred blueboxpodcast.com from one registrar to another last week shortly before the domain name was set to expire. Unfortunately, I made one serious mistake - I didn't check the DNS nameservers for the domain at the new registrar (GoDaddy) to ensure they were pointing to the new nameservers. They weren't... they will still pointing to the old nameservers. As a result, when the domain name expired at the end of the day on Friday, the web site was no longer available and had the message that the domain name had expired.

MANY THANKS to the couple of you who contacted me on Saturday to let me know about this!

So I fixed the web site yesterday morning so that "www.blueboxpodcast.com" pointed over to TypePad, where I host this site, and that all seems to be back in action. If you type in "blueboxpodcast.com" without the "www", it was going to a generic GoDaddy page but I've set up the forwarding now so that this should now redirect you to www.blueboxpodcast.com once the DNS propagation occurs.

What is still dead, though, is the RSS feed... which is rather annoying since that is what podcast subscription tools like iTunes use! In working through the issues this morning, it appears to be the issue that

Feedburner is not using the updated DNS information.

The Blue Box RSS feed, which is http://feeds.feedburner.com/BlueBox is somehow pointing over to the old page. Yet the base feed for this site, http://www.blueboxpodcast.com/atom.xml resolves perfectly fine and does have the RSS information. (Please don't switch to subscribe to that one... I do like the stats I get through Feedburner.)

So it appears that I'm waiting for FeedBurner to update its DNS. I've tried all sorts of options in the FeedBurner settings, including the "Resync Feed" but nothing works because it seems that it is unable to get to the new site (because of DNS).

I've filed a help request in the FeedBurner Google Group (which appears to be the only way to get help). Hopefully FeedBurner will age out its DNS info soon and the feed will be back in action.

What I find strange, though, is that I'm 99% sure that all the DNS records had a TTL of 1 hour (and I'm 100% positive the new ones do). So my question to FeedBurner is - if that is the case, why aren't they respected the TTL settings of the domains?

I'll update this post once I have more information.

Technorati Tags: feeds, rss, feedburner, google, dns, bluebox

Returning from the hiatus...

Blue Box listeners,

Well, it's been a while. A long while. This summer turned out to be a bit crazier than Jonathan or I ever expected. The good news is that the renovation at my home is finally done and I've moved into my home office. The box of podcasting gear has come up from the basement. I'm not traveling for several weeks... so everything looks good to finally get the huge queue of back episodes out the door.

My goal this week is to get some of the older main shows out first followed by some of the excellent Special Editions that our volunteer production team has put together. If things work out the way I hope I should be getting you a show a day for the rest of the week. (We'll see.)

Thanks for your patience and continued interest in the show. We have very definitely not "podfaded"... and we'll be back with more shows and interviews in the weeks and months ahead! Thanks for continuing to listen.

Dan & Jonathan

New Blue Box shows coming soon...

My apologies for the long delay... we haven't "podfaded". We have several main shows recorded that I'm hoping to get out this week and I've got a host of volunteers ready to help with getting some of our backlog of "Special Edition" shows out... I just have to put the pieces in place so that those volunteers can help! Unfortunately, the process of buying a new home and selling our existing home has severely hit my available time and that's the primary reason for the delays. Within the next month or so that should hopefully all wind down and I can resume the regular activity....

Thanks for your patience!

Wow! The offers of production assistance have been wonderful...

WOW! I don't know that there is much else Jonathan and I can say after the incredible response we've had to our request for production assistance (also in SE#24). The offers started coming in within a few hours of SE#24 going live and I think we're up to 12 people now who have said that they'd help. THANK YOU! We're both overwhelmed and humbled by the many great folks who have offered to help... and also the words they sent our way saying how much the show mattered to them. Thank you! At this point, it would definitely look like we're all set for the moment, so it doesn't appear we need any further assistance. Now we just have to get set up to make use of all the offers that have come in! Stay tuned for more info - and more shows!

Technorati Tags: blue box, bluebox

Looking for a few good audio production assistants...

As we discuss in Blue Box Special Edition #24, we find ourselves in a bit of a dilemma. With each conference/show that we go to, we accumulate more great recordings of interviews that we do, panel sessions we record and other similar sessions. The goal is to turn these into "Special Edition" podcasts that we can make available in the podcast feed. We have two shows coming up this month, VoiceCon and VON, where we will record more sessions and interviews. Additionally, we do get requests to interview people that sometimes are quite interesting.

The problem we have is finding the time to do the post-production on the recordings to turn them into podcasts. We could, of course, just slap a generic intro and outro on a recording and throw it out there in the feed... but I think you all know that we don't want to waste your time! For instance, including the Q&A portion of a panel session where you can't hear the audience questions is pretty useless. Or including the part of the interview where announcements came over an intercom and you can't hear the interviewee is rather silly. So we want to take the time to go through a recording and see how we can "tighten it up". Remove breaks or big gaps of silence... speakers setting up laptops... interruptions to interviews etc. We don't remove every "um" or pause... we do want it to feel natural, after all, but we try to edit out the big gaps, errors, interruptions, etc.

The challenge of course is that to do this you have to listen all the way through a podcast, editing along the way. Sometimes you don't have to make many edits at all. Sometimes there a bunch of things to edit out. But it takes time... if the panel is 45 minutes you've got to have at least that much time (and probably double if you do much editing and keep stopping/starting). Unfortunately time is something neither Jonathan nor I are finding a whole lot of these days. I now have a queue of probably 10 or 12 recordings we've made over the past 6 months that are just sitting there waiting for me to get the cycles to turn them into Special Editions. Some are 20-minute interviews. Some are 45-minute or hour-long panels from conferences.

So therefore our request in show #24:

we're looking for a few good production assistants!

What we'd love to do is to find a couple of people who would be willing to work this way:

• I get to you the WAV file of the recording as well as the intro/outro.
• You edit the file in whatever audio tool you prefer: Audacity, Garage Band, SoundForge, whatever... (I use Audacity)
• When you are done, you export to a MP3 and get the MP3 to me.
• I do a final check, set the ID3 tags, etc. and upload the MP3 file, create the show notes, etc.

The good news about most of the recordings we make is that they are not overly time-sensitive. We want them up as soon as we can, but if it takes some time to do the post-production as you fit it in around other work, that's generally perfectly fine.

Obviously if you have experience with audio editing that's great. If it's something you've been interested to try your hand with, we're open to having you give it a try. (Please do realize that I'm a control-freak and audio quality stickler, so it's a new thing for me to even *consider* letting other people work on our files... but I've reached the point where I think it's more important to get the content *out*! So I'm willing to try it out... :-)

We can't offer you any money or anything like that (this is a labor of passion, not profit!) but we're certainly glad to give credit in show notes, Blue Box website, etc. You'll also be helping the greater community of security professionals interested in VoIP by getting more content out there in a more rapid manner. (i.e. faster than if we're waiting for me!) You may also gain skills in audio production (if you don't already have them) that may assist you in other endeavors.

Anyway, if you are interested, drop us an email with the subject line "Production assistance" and with a little bit of background about yourself. Sometime in the next week or two (probably after March 20th) we'll start seeing what we can do if there are people interested.

Thanks - and thanks for your patience, too.

Dan & Jonathan

New Audio comment line number - +1-415-830-5439 (and ditching K7.net)

Here is our new comment line number: +1-415-830-5439.

Here's the story...

To my immense annoyance, it seems that we have once again lost our K7.net call-in number for comments: +1-206-350-7280. That isn't the bad part, really... what annoys me most is that the number still appears to work! You can call it up and leave a message, but if it goes anywhere, it is not going to us! In the past, when we've lost our K7 number, the number has been inactive to some period of time, so callers just got a message saying that the number was no longer in use. Now it appears that the number has been reallocated already - or at least is accepting calls.

So please do not call that number!

I'm going to use this failure as an opportunity to completely drop our usage of K7.net. K7.net is a "unified messaging" service that is widely used by podcasters because it provides a very simple and easy - and free - service: Callers call in to a phone number, leave a message, and then you receive an email with the comment attached as a WAV file. It is great for a podcaster. Simple. Easy. Just works.

However, there is this wee minor little detail that is shown in the terms of service at the bottom of the sign-up page:

If a K7 number is inactive for 30 days (use is determined as a voice message or fax message to that number) , we may terminate the account for non-use.

This has been the bane of many podcaster's existence. If you don't get a call in 30 days, you lose your number. This impacts podcasters, especially, because our shows may live on out there on the Internet for an incredibly long time. You can still download Blue Box podcast #1 from two years ago which has the wrong comment line included (in fact, it is 2 or 3 numbers ago). So losing your number is really quite bad from a community-building point-of-view. If you put out frequent shows and get frequent comments, this usually isn't a problem. However, if you are a show like ours where we've been only doing maybe two shows a month it may be more of a challenge. I know that here in New England, the New England Podcasters group was instituting a "reminder day" where it was a monthly day to call your comment line to be sure you kept it. In any event, we seem to have lost our number.

Now, I can't really complain about the service because it is free and the K7 folks have always been very up front about the termination for non-use clause. All I can really do is find another alternative.

I have now done so. My new employer, Voxeo, has a website for developers called evolution.voxeo.com where you can create voice applications in several different XML variants (VoiceXML, CCXML or Voxeo's own CallXML). You can create a free developer account and with that you can create apps that have their own inbound phone number. For free. Anyone can do so. There is, at least currently, no expiration date or termination clause for non-use (although the terms of use do of course indicate that Voxeo can change or revoke the numbers at any time). So what's the catch? Well, Voxeo hopes that you like to develop apps on our platform so much that ultimately you'll need our hosting services for your applications.

So I've created my own little experiment in the form of a new comment line: +1-415-830-5439.

Right now it's just a computer-generated voice but I'll add in my own prompts soon. Interestingly, this number is also reachable via some other phone numbers:

• Skype: +99000936 9992002622
• FWD: **86919992002622
• SIP: sip:9992002622@sip.voxeo.net

And while we are NOT going to switch from using our SIP "bluebox@voipuser.org" address, it's nice to know that it is available.

Since I know many of our listeners like to know the code underneath things, here is the full text of my "application" that does this:

<?xml version="1.0" encoding="UTF-8"?> 
<callxml version="2.0"> 
<block> 
<text> Thank you for the calling the comment line for Blue Box, The Voice over IP Security Podcast.  Please leave your comment after the tone.  Thank you.</text> 
<recordaudio maxtime="3m" value="mailto:blueboxpodcast@gmail.com?subject= 
Voicemail message - listener comment&fromname= 
Voxeo Messaging&fromaddress= 
dyork@lodestar2.com&body= 
Voicemail message&filename=comments.wav"/> 
</block> 
</callxml>

It uses Voxeo's own CallXML language which was developed before VoiceXML and CCXML (Call Control XML) were standardized. Why did I use CallXML versus VoiceXML and CCXML? Primarily because I wanted to learn CallXML - and also, frankly, because it seemed to have the easiest commands to do what I was trying to do. It basically says a piece of text and then records up to 3 minutes of audio and emails it to our standard comment line. Ta da... same thing as I was doing with K7.net, but without the annoying termination after 30 days of non-use.

Anyway, that's the new number and the story behind it. Hopefully I won't be changing it again anytime soon!

Technorati Tags: blue box, bluebox, k7.net, voxeo

Our Blue Box Frappr map has grown to 315 member!

We've pretty much ignored our Frappr map for probably most of the last year after Frappr went from AJAX-based Google maps to Flash-based Yahoo!Maps that took forever to load (and didn't show the world outside of North America). Today I randomly happened to look at it and found that Frappr's back to using Google Maps and that our map had grown to over 315 members! Very cool to see! If you haven't joined the map but are open to doing so, you can go to the map or click on the embedded map here:

NOTE: One of our listeners commented in the Blue Box Skype group chat that you do need to be careful about how you are signing into Frappr as it sometimes will add you with your email address versus your Frappr ID.

Technorati Tags: bluebox, frappr, blue box

Blue Box podcast #70 successfully recorded... on *conference WiFi*!

I'm delighted to report that Jonathan and I successfully recorded Blue Box #70 this morning. It was a bit surreal, actually. There I was at the Javits Center in a vacant room on conference WiFi and Jonathan's audio quality was outstanding! In fact, when I listened to the recording afterward his audio sounded far better than my audio that was recorded off of my local USB headset! Of course, in contrast to the stats I showed yesterday, here's how our call looked today:

0.0% packet loss on receiving Jonathan's signal! Very cool! And a 94ms round trip sure beats a 200-300ms round trip, eh?

To get this good quality on a conference WiFi really speaks to the efforts of the Interop NOC team to deliver this kind of network. Kudos to them!

For those curious, I recorded the show locally on my MacBook Pro using WireTap Studio from Ambrosia Software. Given that our recording levels were quite different, I'm probably going to need to run the recording through the Levelator in order to bring the levels in line.

It should be posted probably some time early tomorrow. I'm at Interop all day today and so the post-production will probably be done during my time out at JFK and flying home later today.

Technorati Tags: bluebox

Blue Box Comment Line number changed - now +1-206-350-7280

Unfortunately, the comment line for the podcast has had to be changed. The new number is:

+1-206-350-7280

We use a free service from K7.net and unfortunately if no one calls the service for 30 days, they terminate your user account. You have no way to get back the phone number that you previously had (which, okay, it's a free service, so I can't complain!) and you have to register a new one. I keep using it primarily because it's simple... people call and leave a voicemail - and a WAV file shows up in our inbox. Simple. Easy.

But it does have this 30-day rule. Given that we've had a stretch between shows, there haven't been people calling in. Usually I call it once a month just to make sure that we keep the number... but I've been a bit distracted lately and forgot to do so. So we lost the number, which is too bad because the old one spelled out "blue" with the last 4 digits.

Somewhere in here I'm going to set up a local Asterisk server with an inbound phone number and at that point I'll move the comment line over to it and stop using K7.net. However, until that time, we've just got to make sure that someone leaves an audio comment at least once a month!

(Disappointing that this happened just as I announced the call-in contest for the book for our anniversary show...)