Comments on Don't Get XO for VoIPTypePad2008-05-13T03:01:13ZAndy Abramsonhttps://andyabramson.blogs.com/voipwatch/tag:typepad.com,2003:https://andyabramson.blogs.com/voipwatch/2008/05/dont-get-xo-for/comments/atom.xml/Craig Plunkett commented on 'Don't Get XO for VoIP'tag:typepad.com,2003:6a00d83451b99869e200e55237fb2388342008-05-13T11:10:46Z2008-05-13T19:37:25ZCraig Plunketthttp://profile.typekey.com/plunkman/Without doing some deeper analysis of the path between the endpoints, its a little unfair to automatically blame the last...<p>Without doing some deeper analysis of the path between the endpoints, its a little unfair to automatically blame the last mile provider, which might be the ILEC, if it is XO's DSL. Once a quarter, one of the Covad lines that I run one of my hotspots off of gets screwed over, and it takes a day of fingerpointing between Covad and VZ to resolve it, and I'm never sure if its a DSLAM or an upstream router issue. Your problem could have been a peer somewhere in the middle. You didn't describe any of the troubleshooting you did with any other apps besides VoIP between you that might have provided a smoking gun. You might well have been right, but it seems awfully glib to shoot them on reflex like that. I couldn't really give a rat's behind about XO, either way.</p>