econnrefused errors give no insight to cause

[joesanford]

As I've been working with escalus, I have noticed that any time it cannot connect, it gives nothing more than a badmatch on {error, econnrefused} with no insight into what it is trying to connect to, how the host responded, etc.

Can this be expanded to include useful information on dumps? I end up having to start tcpdumping traffic just to figure out where escalus is trying to connect to.