On Fri, Sep 16, 2011 at 11:23 AM, Michael Picher wrote: > They are an option if you want to get an Ingate...
Thanks, I'll keep that in mind. On Fri, Sep 16, 2011 at 11:28 AM, Tony Graziano wrote: > I generally have never had an issue with inbound calls with them but if > you're having an issue with toronto just move your did presents to another > city and register there. It's not just with Toronto. The last issue was with Montreal2 and I'm currently on Chicago. Over the past 3 years we've bounced around from toronto (when it had capacity issues for something like 3 months, and before it went down a month or two after toronto2 came online), toronto2, montreal, montreal2, atlanta, chicago and newyork. Maybe more (not that there are many more). I understand that some people don't have (many) problems with voip.ms, so it may seem like the issue is on our side. However, as mentioned before, many of the problems have been confirmed to be on the voip.ms side. For example, we were getting busy signals and sometimes even "number not in service" messages randomly on the toronto2 server for a few months. This could be reproduced when the DID was routed to their IVR (where I had a test tone set up), which means our internet line and equipment were not involved. They confirmed that they had capacity issues with their carrier and had resolved this. However, it doesn't appear that they have any process in place to let them know when they're reaching capacity with their carriers (I asked if they had a process or were implementing a process and they didn't say yes). If this is the case, this means that they have to wait for customers to have issues until they can determine that they need to add more capacity. A little while later I had other problems that were resolved by switching to Atlanta. A month or two later they had issues with Atlanta which again I could reproduce with using the IVR on their system (confirms that it's not us). I reported it and they told me to use a different server since I only experienced the problems on atlanta. As far as I know, they didn't try to fix it. I then moved to montreal2. About 3 weeks later an issue popped up on their issue tracker with the atlanta server where they were losing packets. This would completely explain the problems that I reported 3 weeks earlier. Last week I had call quality issues on montreal2. Check dslreports and you'll see others had the same issue. This week on montreal2 I started getting busy signals again (nothing shows up in the CDR, which means it's not even being sent to us). I reported it and reproduced it at least 7 times while I had a live chat going. Again, I was told to try a different server. No trace was run. There was no indication that further troubleshooting would be done. I'm now on Chicago and haven't gotten a busy signal on one inbound call since moving. But how long until there's a problem with Chicago (which we've already had at least 2 issues with before). This just scratches the surface with the issues I've had. Voip.ms is no longer an option for us for inbound calls. Gotta wrap this up. I just found out that inbound and outbound calls aren't working. I just tried CallCentric and it's working. I'm not joking. This is #@$%!@#$%@# ridiculous.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
