8 port FXO gateway needed



  • Alright folks, I need some recommendations for a solid known working 8 port FXO gateway.

    The client has phone service from Charter under a contract that is not cost effective to cancel at this time. Charter is handing off the service as 8 POTS lines.
    Even if I wanted to deal with the cancellation charges, porting to SIP is not advisable at this time because their internet service is not stable enough. Bringing in a new stable internet service on top of the cancellation charges would be overwhelmingly expensive.

    So for the next 3 years, I wanted to simply setup a basic FXO gateway.

    I started with a Grandstream GXW4108. I had it configured easily, but call quality was bad with large skips on the inbound audio. Support was so atrocious I gave up on it.

    I moved on to a Sangoma Vega 50. This unit was again easy to bring up as a trunk in FreePBX, but I had problems with it correctly answering calls. Support has been very responsive, but it has been 2 weeks with no resolution. Last week I did an in depth test of their lines with 10 calls in to each # and separate packet captures for each call and sent it all off to support. Sangoma support has now handed it off to Engineering.

    At this point the client is extremely fed up as I have had the new phones on their desk for over a month now. They understand the constraints I am under, but that still does not make them feel better.

    Can any of you recommend a solid 8 port FXO gateway?



  • So I never followed up on this.

    This was FreePBX 13. Fully patched and current and such at the time.

    The Grandsteam GXW4108 issues were a pain in the ass. So I purchased the Sangoma Vega 50.

    That unit also had issues, but I had solid support from Sangoma. Support confirmed nothing was wrong with the Vega 50. There was also nothing wrong with the FreePBX 13 install.

    But there was random packet loss, somehow only with talking to these devices.

    The environment was Server 2012 R2 + Hyper-V. No other VM had issues of any kinds.

    I was swapping gateways back and forth trying various things and in a fit of frustration I installed a clean FreePBX 13 on their other hypervisor. That one was running Server 2012 + HyperV.

    I connected the Grandstream to it and had zero issues. WTF.

    So I deleted that VM and live migrated the active FreePBX system and all the problems went away.

    The unit worked perfectly for 2 years (June 2018). At that time it was honorably retired as the site was able to get a solid fiber connection thanks to @Phil-CommQuotes.

    They have been running on a Twilio trunk ever since.



  • Unfortunately have not needed one of those in a very long time. Okay, maybe unfortunately is the wrong term there. But regardless, it's been a lot time since any FXO devices so large have crossed my path. Sangoma would have been my guess.



  • Audiocodes comes to mind MP-118 I think has an 8FXO option, probably over budget.
    Other option I can think off the top of my head is to see if AdTran has something. Total Access have an option of 8FXO but you have to get the very high end model (924e I think) and is probably also over budget.



  • We have the Grandstream GXW4108. I got it working, but it took some work. (Read: Hours and Hours)

    This is the guide I used: http://wiki.freepbx.org/display/FOP/Configuring+a+Grandstream+GXW-410X+Device+to+act+as+an+FXO+Gateway



  • @aaronstuder said in 8 port FXO gateway needed:

    We have the Grandstream GXW4108. I got it working, but it took some work. (Read: Hours and Hours)

    This is the guide I used: http://wiki.freepbx.org/display/FOP/Configuring+a+Grandstream+GXW-410X+Device+to+act+as+an+FXO+Gateway

    Setting up the gateway as a trunk was easy as shit. It was the call quality issues afterwards.



  • @aaronstuder said in 8 port FXO gateway needed:

    We have the Grandstream GXW4108. I got it working, but it took some work. (Read: Hours and Hours)

    I do not have my unit powered up at the moment, but I would assume it has a way to backup and restore configuration. Would you be willing to send yours? I have no qualms about the hardware, I just need it to work and it was not.



  • @aaronstuder you never responded, could I get your config for comparison? This issue is getting out of hand and I cannot count the time I have spent on it. I know I quit billing the client weeks ago.



  • Make sure the grandstream has the latest firmware too. If you have the old yellowish background you are running really old firmware. If it is blue background then you should be recent.



  • @JaredBusch sent via email. Sorry.



  • @aaronstuder said in 8 port FXO gateway needed:

    @JaredBusch sent via email. Sorry.

    I'm a little frustrated on why this thing is not working. Not your problem. thanks for sending your config for comparison.



  • So I never followed up on this.

    This was FreePBX 13. Fully patched and current and such at the time.

    The Grandsteam GXW4108 issues were a pain in the ass. So I purchased the Sangoma Vega 50.

    That unit also had issues, but I had solid support from Sangoma. Support confirmed nothing was wrong with the Vega 50. There was also nothing wrong with the FreePBX 13 install.

    But there was random packet loss, somehow only with talking to these devices.

    The environment was Server 2012 R2 + Hyper-V. No other VM had issues of any kinds.

    I was swapping gateways back and forth trying various things and in a fit of frustration I installed a clean FreePBX 13 on their other hypervisor. That one was running Server 2012 + HyperV.

    I connected the Grandstream to it and had zero issues. WTF.

    So I deleted that VM and live migrated the active FreePBX system and all the problems went away.

    The unit worked perfectly for 2 years (June 2018). At that time it was honorably retired as the site was able to get a solid fiber connection thanks to @Phil-CommQuotes.

    They have been running on a Twilio trunk ever since.



  • @JaredBusch said in 8 port FXO gateway needed:

    The unit worked perfectly for 2 years (June 2018). At that time it was honorably retired as the site was able to get a solid fiber connection thanks to @Phil-CommQuotes.

    Good reminder, I needed to email him today!



  • @scottalanmiller said in 8 port FXO gateway needed:

    @JaredBusch said in 8 port FXO gateway needed:

    The unit worked perfectly for 2 years (June 2018). At that time it was honorably retired as the site was able to get a solid fiber connection thanks to @Phil-CommQuotes.

    Good reminder, I needed to email him today!

    I'm here to help! Let's talk!