We use voip.ms for three smaller not-for-profit clients. We found in the past that all our problems were due to firewalls: due to the way SIP works, firewall problems can be intermittent and vexing. Without those specific (expensive but rubbish) firewalls the problems do not occur.
On the first site have had no problems for a year now, using 15 softphones and pfSense (with HAVP and Snort) as a firewall using voip.ms' PBX features. On a second site we have no problems over the last 3 months using 4 Polycom SoundPoint ip 335's connecting to voip.ms' PBX features. On a third site setup a month ago, we are experiencing no problems with sipXecs 4.6 on AWS EC2 connected to voip.ms through sipXecs' built-in iptables (and the AWS security group setup properly). On this sipXecs 4.6 instance we have a backup trunk to Toronto that is registered, and we use IP authentication on the primary trunk to New York (with an inbound DID redirected using an URI to port 5080). No problems at all to date. Fingers crossed... knocking on wood, etc. We have a sipXecs alarm set on the secondary registered connection, and it did registered a drop once for a couple of minutes two weeks ago. I would say that voip.ms' support isn't geared towards people having problems with their firewalls... I'm guessing they are usually right that it's the end-user's device, not voip.ms' servers. It must be a very frustrating job! They have always been polite and reasonably helpful to me. But don't expect emergency support within the hour, unless it really is their systems down. Indeed, voip.ms documents somewhere on their website that they not support T.38. As always, YMMV, in other words, it might not work for you even though it works great for me! Nicholas Drayer Managing Director Dyrand Systems T. 604.408.4415 Ext. 319 www.dyrand.com From: [email protected] [mailto:[email protected]] On Behalf Of Tony Graziano Sent: November-19-12 4:51 PM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] voip.ms impression We use voip.ms<http://voip.ms> for small occasional use and its very good for testing. Our production systems use Appia (we are a reseller) who can also provide t.38 service which we have found to work well in a production environment. At the same time, most of our sip servers sit behind application aware firewalls and ensure connections using SIP the protocol are in now way impaired by other applications on the network. These application aware devices also have IDS and are completely cloud managed and monitored. I would agree voip.ms<http://voip.ms> works but not always that well at every POP and they do seem to have occasional problems with call quality and completion depending on the number you call. Whether this is ISP routing, edge or internal issues at their POP is sometimes a little unclear, but they are good enough to use for failover, backup or testing but not particulary in large production environments (IMO). On Mon, Nov 19, 2012 at 7:25 PM, Mark Wood <[email protected]<mailto:[email protected]>> wrote: We have been using voip.ms<http://voip.ms> for 6-8 months so far and I want to get some feedback from users that have been at it for longer. Specifically we (main and subaccounts) experience times where our outbound calls just hang after dialing and sometimes abruptly connect, or sometimes not at all. When a subaccount calls to report problems to us and we check our home page it will show all of our accounts as 'not registered', and then slowly one by one they will show as 'registered'. We had an incident over the weekend with a security office that couldn't receive any inbound calls. We logged in to the voip.ms<http://voip.ms> site to check the registrations and initiate a support ticket and the site again said 'not registered'. The instructions had us do and 'echo test' procedure and the results were the same as when they were routed to the subaccount. The support response 12 hours later was 'works for us' and then 'check your routers and firewalls'. Comments? Who are other good candidates for reselling VoIP like this model? Thanks, Mark W. Wood office: (760)202-0224 X2010 Direct: (760)459-1981 [New Image.BMP] www.redphonetech.com<http://www.redphonetech.com> _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected]<mailto:[email protected]> Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! [http://www.ezuce.com/image/image_gallery?uuid=61c95dd3-a26d-4363-95b1-131231e1edf0&groupId=284283&t=1340112036507%22+style=%22width:+310px;+height:+310px;]<http://sipxcolab2013.eventbrite.com/?discount=tony2013> LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected]<mailto:[email protected]> Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
<<inline: image001.png>>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
