The Boston Diaries

The ongoing saga of a programmer who doesn't live in Boston, nor does he even like Boston, but yet named his weblog/journal “The Boston Diaries.”

Go figure.

Tuesday, January 06, 2015

… and this bug exists because of a work-around for that bug …


The last day at work in 2014 (Debtember 18th), I spent it running yet another IOT, which involves running tcpdump to capture the network traffic on our end to verify that we receive and send the data properly. After running a test, I would load the resulting capture into wireshark, filter for the SIP protocol only to find—


Project: Sippy-Cup” was getting the packets and responding correctly—well, as “correctly” as these things go, but I was not seeing any packets under wireshark, no matter what I did. But the whole test setup is so jury-rigged that it wouldn't surprise me at all if we were, in fact, doing NAT over avian carriers that it seemed rather pointless to spend the next few hours trouble shooting my inability to do network captures when the other participants were able to capture enough of the transaction to let us continue running the test.

Especially as I was one day from retirement a few hours away from a two-week Christmas vacation.

And then today, I learned that we were, in fact, capturing data.

Why was wireshark not showing the packets?

Because I was telling wireshark to filter on SIP, which defaults to port 5060. We were running our SIP component on port 5061, because of some odd-ball router on our network that oh-so-helpfully looks for SIP traffic and attempts to proxy it anywhere else than our SIP component.

And because we were running on a non-standard port, wireshark wasn't showing us the proper packets as it was looking only for packets on port 5060.

I swear, I think IP-over-avaian-carriers would be easier to deal with.

Obligatory Picture

[The future's so bright, I gotta wear shades]

Obligatory Contact Info

Obligatory Feeds

Obligatory Links

Obligatory Miscellaneous

You have my permission to link freely to any entry here. Go ahead, I won't bite. I promise.

The dates are the permanent links to that day's entries (or entry, if there is only one entry). The titles are the permanent links to that entry only. The format for the links are simple: Start with the base link for this site:, then add the date you are interested in, say 2000/08/01, so that would make the final URL:

You can also specify the entire month by leaving off the day portion. You can even select an arbitrary portion of time.

You may also note subtle shading of the links and that's intentional: the “closer” the link is (relative to the page) the “brighter” it appears. It's an experiment in using color shading to denote the distance a link is from here. If you don't notice it, don't worry; it's not all that important.

It is assumed that every brand name, slogan, corporate name, symbol, design element, et cetera mentioned in these pages is a protected and/or trademarked entity, the sole property of its owner(s), and acknowledgement of this status is implied.

Copyright © 1999-2024 by Sean Conner. All Rights Reserved.