You might also try changing to a different point of presence if you have another one close (try pinging a few of them). New York works well for us and we have another account registered on Chicago.
Mike On Mon, Apr 18, 2011 at 9:13 AM, Tim Byng <[email protected]> wrote: > On Sat, Apr 16, 2011 at 11:24 AM, Michael Picher wrote: > >> Where's voip.ms on this? Have they captured traffic or have you sent >> them a pcap of this happening? (they most likely won't be able to deal with >> an xml trace). >> >> I took a quick look at the trace and they definitely seem to be sending >> you the BYE message. You'd think they should be able to tell you why. >> > > They captured a trace with a dropped call on their end on April 7th. I've > gotten a few updates that they're still "looking into it". I have no idea > why it's taking so long. > > >> >> btw, pfsense is a very good firewall product, don't feel like you've >> wasted any time. there were times with Cisco ASA's I wish they did what I >> wanted to do too... all products have their nuances. >> > > Good point. You're absolutely right about all products having their > nuances. I was really frustrated the other day and can see things a little > more clearly today. BTW, I'm not using pfSense at this moment, as the box > started freezing on Friday and I had to take it offline. It's an older box, > so it's possible (and likely) that it's a hardware issue. I'll probably get > back to pfSense again in the future (with a better machine to run it on). > > At this point I'm going to concentrate on voip.ms and not on so much on my > firewall. I've been using sipXecs and voip.ms for almost two years now, > and up until a few weeks ago I only had a couple of dropped calls. What I > need to do is to figure out what happened a few weeks ago that caused calls > to start being dropped so frequently. I didn't change anything on my end > when this started happening (I switched to pfSense afterwards to see if it > would help, which it didn't). The last changes I made were in early February > when I applied a firmware update on my router. However, the dropped call > issue didn't start happening until about a month and a half after this, and > the problem continued after switching to pfSense, so I don't think that it's > related. > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected]
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
