Will_Brazier Posted January 17, 2017 Posted January 17, 2017 Hi All, I've seen that quite a few people are using Gamma for their SIP trunk. I've also seen that someone is using them with FreePBX. Just wondering if anyone out there is able to help with trunk configuration for Gamma in FreePBX. So far I've had no luck even with lots of holes punched in the Firewall. The provider that's sold the gamma trunk to us isn't being much help and I haven't been able to find contact details for Gammas technical support myself. Asterisk forums have had some posts but still had no luck. Any help would be hugely appreciated! Will
FN-GM Posted January 17, 2017 Posted January 17, 2017 (edited) What firewall changes have you made? These are our Gamma FreePBX settings. Do they provide this same IP? You might have to use a different one. type=friend insecure=port,invite host=88.215.63.169 dissallow=all context=from-trunk allow=ulaw Edited January 17, 2017 by FN-GM
Will_Brazier Posted January 17, 2017 Author Posted January 17, 2017 Had the ports opened from Gamma to us that they specified for RTP and SIP. We've got a different IP from Gamma but your configuration has worked a treat. Thanks!
FN-GM Posted January 17, 2017 Posted January 17, 2017 Make sure you set your firewall to only accept SIP from the IP / IP's you specified. Otherwise you are open to attack.
Will_Brazier Posted January 17, 2017 Author Posted January 17, 2017 Ah Would do but actually made a huge mistake this morning. Tested the wrong DDI which would of worked regardless as it was with another Sip Trunk provider we were testing. Still no joy whatsoever with the Gamma Trunk. Gamma have said we need ports 5060 Gamma have asked for ports 60-40000 to be opened which is excessive. What ports do you have open? Their call package is the most competitive we've found but the fact it's not working is really starting to drive me nuts.
FN-GM Posted January 17, 2017 Posted January 17, 2017 We have the same range. Its not Gamma that dictate that, its the way SIP has been developed. It isn't really a problem as long as you lock the firewall down.
FN-GM Posted January 17, 2017 Posted January 17, 2017 We have the same range. Its not Gamma that dictate that, its the way SIP has been developed. It isn't really a problem as long as you lock the firewall down.
Will_Brazier Posted January 17, 2017 Author Posted January 17, 2017 Might be starting to get somewhere then with this. Looks like the issue is with the Firewall. Do you have your FreePBX behind a one to one NAT? We're using one public IP address with PAT.
Will_Brazier Posted January 17, 2017 Author Posted January 17, 2017 Might be starting to get somewhere then with this. Looks like the issue is with the Firewall. Do you have your FreePBX behind a one to one NAT? We're using one public IP address with PAT.
FN-GM Posted January 17, 2017 Posted January 17, 2017 Might be starting to get somewhere then with this. Looks like the issue is with the Firewall. Do you have your FreePBX behind a one to one NAT? We're using one public IP address with PAT. You can't use PAT. You need to have outgoing and incoming traffic on the trunk using the same public IP.
FN-GM Posted January 17, 2017 Posted January 17, 2017 Might be starting to get somewhere then with this. Looks like the issue is with the Firewall. Do you have your FreePBX behind a one to one NAT? We're using one public IP address with PAT. You can't use PAT. You need to have outgoing and incoming traffic on the trunk using the same public IP.
Will_Brazier Posted January 17, 2017 Author Posted January 17, 2017 It wouldn't have been PAT across multiple IP Addresses. Good news. Seems to be working, just waiting for Gamma to confirm they saw the calls going though their side. Turns out the FreePBX had a left over External IP address in it's Nat Settings from about 3 years ago with the old Public IP address that was causing the problem. all seems to be working now, Thanks
Will_Brazier Posted January 17, 2017 Author Posted January 17, 2017 It wouldn't have been PAT across multiple IP Addresses. Good news. Seems to be working, just waiting for Gamma to confirm they saw the calls going though their side. Turns out the FreePBX had a left over External IP address in it's Nat Settings from about 3 years ago with the old Public IP address that was causing the problem. all seems to be working now, Thanks
Blue_Cookeh Posted January 17, 2017 Posted January 17, 2017 I know you said it's working but does FreePBX not allow you to define a port range? Realistically you only need (I think it was) two ports per potential phone call. On our Avaya PBX I was able to restrict the ports down to just 20 odd which meant I wasn't punching a gigantic hole through the firewall, even if they were restricted to our Gamma and Avaya IPs.
Blue_Cookeh Posted January 17, 2017 Posted January 17, 2017 I know you said it's working but does FreePBX not allow you to define a port range? Realistically you only need (I think it was) two ports per potential phone call. On our Avaya PBX I was able to restrict the ports down to just 20 odd which meant I wasn't punching a gigantic hole through the firewall, even if they were restricted to our Gamma and Avaya IPs.
Will_Brazier Posted January 18, 2017 Author Posted January 18, 2017 Sorted one problem. Calls are now coming in and out. The External IP set up in FreePBX was old as the public IP on the connection changed last year. Now have the issue with calls coming in but we can't hear the remote caller. They can hear the person on the FreeBPBX side of the call but the voice doesn't come in from he person calling down the trunk.
Willott Posted January 18, 2017 Posted January 18, 2017 That sounds like a codec negotiation issue - I've seen that over IAX2/SIP combination - worth checking what codecs you have setup in priority order to your endpoints as I've seen asterisk apparently struggle with transcoding across multiple, worth checking they match the codec used on the gamma side of things.
FN-GM Posted January 18, 2017 Posted January 18, 2017 It could also be Nat or firewall rules not correct.
CAWJames Posted January 19, 2017 Posted January 19, 2017 I just port forward all relevant ports locked down to Gamma on the IP I gave them and pass them to my internal FreePBX box, so 5060 and 4000-60000. Works fine and I have a Sonicwall....(Notorious sip killers) Also note that you might get calls coming from an IP adjacent to the one given by Gamma... I find our 2 gamma trunks use 2 IP's each not just the one given.
Shaun_Dark_Lord Posted May 3, 2018 Posted May 3, 2018 What firewall changes have you made? These are our Gamma FreePBX settings. Do they provide this same IP? You might have to use a different one. type=friend insecure=port,invite host=88.215.63.169 dissallow=all context=from-trunk allow=ulaw Hi - Are these settings still valid, and do you have any additional Incoming settings? Thanks
FN-GM Posted May 3, 2018 Posted May 3, 2018 Hi - Are these settings still valid, and do you have any additional Incoming settings? Thanks They worked 5 mins ago I have no incoming settings. that public IP might be different not all customers use that IP. You will have been provided the correct IP to use. 1
Shaun_Dark_Lord Posted May 3, 2018 Posted May 3, 2018 They worked 5 mins ago I have no incoming settings. that public IP might be different not all customers use that IP. You will have been provided the correct IP to use. Thank you!!!!!!!!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now