slickrock22
Member
- Joined
- May 15, 2008
- Messages
- 46
- Reaction score
- 0
I have been an on premise Asterisk guy since I started fooling around with A@H 2.5. It has been an awesome ride. A few hardware glitches here and there and my end users asking for support while I am thousands of miles away on the beach in Costa Rica has finally pushed me over the edge. I have decided to go with a Hosted PBX solution. The tough choice was who do I go with. I spoke with 3 or 4 seemingly reputable companies like Bandwidth.com, a few local guys, Lylix, Aretta, Apptix, etc. The issues were things like not enough support for PBX config, no end user assistance via support, requirement for an on premise router to which all remote phones had to connect (single point of failure with residential grade internet bot a great idea), expensive per extension fees (we like to give staff an on premise phone as well as one at home). Probably a few more just cant remember.
I finally pulled the trigger last week on Aretta. I spoke with Marc at Aretta and he seemed knowledgeable and had a sense that he knew what he was talking about. Aretta has a good blend of a full PBXIAF implementation, Multi channel SIP channels managed internally, support for ends users, ability to buy fully supported handsets and so far what seems to be fair pricing. A big plus on top of all of that was that is seems they have the backing of Ward and crew. That to me was a big deal after having been truly blown away by the contribution of the PBXIAF team!
One of my biggest concerns of course are call quality. I am moving from safe PRI copper to SIP over the Internet. Now you need to know that 90% of our staff are remote around the US so it's not like instead of pointing to Chicago now pointing to Atlanta should cause much problem. Also I assumed since Aretta is procuring the SIP trunks that they would do whatever needed to ensure trunk quality. Having a fully supported off site PBX was worth the risk. This is officially my last piece of server equipment on premise.
I began porting the DID from my PRI provider to Aretta last week. They took the initiative and SSH'ed into my on premise box and created an IAX trunk between my provisioned Aretta NetPBX box and my existing On-Premise PBX. At there suggestion they changed my extension to connect to the Aretta NetPBX and kept all other users connected to my esiting on premise PBXIAF. This will serve for me to test out the new NetPBX in production until my DIDs are ported. This should create a near seemles transition upon DID porting. I cant say I have ever had a near seemless port when chaging phone systems or telco providers. We will wait to see if this is truly seemless.
To say the least I am very fired up about this change. I think for my type of company with more external then internal users, and a PBX admin that travels frequently, this is a no brainer.
I will keep everyone up to date as my transition progresses over the next few weeks. One thing I will be paying very close attention to is call quality both between extensions and over the SIP trunks.
I hope and pray this was not a mistake as my end users will hang me if this does not work.
Stay tuned,
Ryan
I finally pulled the trigger last week on Aretta. I spoke with Marc at Aretta and he seemed knowledgeable and had a sense that he knew what he was talking about. Aretta has a good blend of a full PBXIAF implementation, Multi channel SIP channels managed internally, support for ends users, ability to buy fully supported handsets and so far what seems to be fair pricing. A big plus on top of all of that was that is seems they have the backing of Ward and crew. That to me was a big deal after having been truly blown away by the contribution of the PBXIAF team!
One of my biggest concerns of course are call quality. I am moving from safe PRI copper to SIP over the Internet. Now you need to know that 90% of our staff are remote around the US so it's not like instead of pointing to Chicago now pointing to Atlanta should cause much problem. Also I assumed since Aretta is procuring the SIP trunks that they would do whatever needed to ensure trunk quality. Having a fully supported off site PBX was worth the risk. This is officially my last piece of server equipment on premise.
I began porting the DID from my PRI provider to Aretta last week. They took the initiative and SSH'ed into my on premise box and created an IAX trunk between my provisioned Aretta NetPBX box and my existing On-Premise PBX. At there suggestion they changed my extension to connect to the Aretta NetPBX and kept all other users connected to my esiting on premise PBXIAF. This will serve for me to test out the new NetPBX in production until my DIDs are ported. This should create a near seemles transition upon DID porting. I cant say I have ever had a near seemless port when chaging phone systems or telco providers. We will wait to see if this is truly seemless.
To say the least I am very fired up about this change. I think for my type of company with more external then internal users, and a PBX admin that travels frequently, this is a no brainer.
I will keep everyone up to date as my transition progresses over the next few weeks. One thing I will be paying very close attention to is call quality both between extensions and over the SIP trunks.
I hope and pray this was not a mistake as my end users will hang me if this does not work.
Stay tuned,
Ryan