Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Gamma IPDC SIP and v8 3

Status
Not open for further replies.

Ploes

IS-IT--Management
Mar 7, 2012
26
GB
Hi

I'm quite new to the IP Office system, but I've managed to get a new IPDC (IP Direct Connect) SIP trunk on our system working for inbound, but not outbound calls.
I'm sure its to do with the TO: header and/or the SIP URI Options but all the questions here on the forum reference much older releases!

Thanks for any help
 
Gamma usually requires the use of a STUN server to function, try 137.177.123.13 :)

 
There are already older non-IPDC SIP trunks running on the IP office. Stun is already running.

I've put the new SIP trunk in its own linegroup and added an 8N - N shortcode to use the new group, keeping it away from the current stuff.

...that said, I've just noticed I've only got one way voice on incoming calls also so maybe I wasnt as close as I thought!
 
then your STUN server isnt working.

check my recent FAQ for a list of STUN servers

best one is:

> stun.ekiga.net
Server: fs01.vale.local
Address: 1.0.0.12

Non-authoritative answer:
Name: stun.voipbuster.com
Addresses: 77.72.169.164
77.72.169.166
77.72.169.160
77.72.169.162
Aliases: stun.ekiga.net

so head back and enter a new IP and click "Run STUN"

you want to make sure you see

Firewall/NAT Type : Full Cone NAT
Public IP: <Public IP The IPO is routing SIP Traffic on>
Public Port: 5060

biggest mistake people make it their NAT rules. If your public port is not 5060 and some other random port then you need to change your router depending on the model

e.g - Draytek / Zyxel / Netgear type router - disable SIP ALG
Cisco based devices - your NAT rule must be Extendible.


ACSS - SME
General Geek



1832163.png
 
I think I'm waiting till I get a spare IPO back from a client then.

I'll report back in a few days.

One odd thing is that SIP ALG was already disabled on our Draytek 2830, but that was a good shout!
 
Open Ports. What ports should be open? Just 5060 or is somthing else needed?
 
I've got the exact same problem, I've got all the right ports open in and out, the STUN server I'm using (146.101.248.221) is returning the correct public facing IP reading "Port restricted Cone NAT" and I made sure under the SIP trunk line transport tab I've told it to look at LAN1 network topology info.

But my headers are still sending back out to gamma with the internal IP of the IPO not the public address :s

I'd pull my hair out if I had any!

Any help with this would be awesome.
 
I also have these ports open as per the Gamma document they sent through but thought this might be helpful if any of you had missed it.


Traffic on the following ports must be forwarded through relevant routers and firewalls on the customer premises to allow access to the Gamma IP Direct Connect Network:

- UDP Port 5060 egress/ingress to 83.245.6.81 (IPDC SIP signalling gateway),
- UDP all ports between 6000 - 40000 egress/ingress to 83.245.6.82 (IPDC Media gateway) Omission of this setting will result in one-way speech
 
Change your STUN server to 77.72.169.160

what router / firewall are you using?

You dont need all those ports open only udp/5060

ACSS - SME
General Geek



1832163.png
 
This line:

- UDP all ports between 6000 - 40000 egress/ingress to 83.245.6.82 (IPDC Media gateway) Omission of this setting will result in one-way speech

Is utter bollocks, that port range is not required to be open at all, just 5060. I never open any ports other than 5060 with SIP and depending on router sometimes that isn't even required, opening that huge port range is crazyness :)


 
You only need that number of ports if you manage to get it going with a good router and without STUN.

I've had it working both ways with Gamma IPDC.

Gamma seem very anti-STUN and don't provide one themselves. Its up to you what to make of that.

Dave
 
They need to invest in SBC's like every good SIP provider does, they are just too chesap to do so and so make you open up loads of ports. Best to use STUN I would say :)

 
It's a Sonicwall I believe on the site I'm trying to get working, I've been told all the ports I've requested are open in and out, he also said he'd turned off any sip translation on the Sonicwall as in general he found it caused more problems.

I'll try your STUN server address hairless and see where that gets me. Just gotta wait for the firewall chap to open it up for me.

The guys here who have Gamma trunks working with a STUN server do you have Registration required ticked and your public ip address selected in your SIP Credentials tab?
 
I've got notes of when I was testing this that I used 77.72.169.166 as the STUN port 3478, set it to Restricted Cone NAT, hit Run STUN and it filled in the rest after two/three mins.
 
if you are registering your SIP trunks, then you shouldn't need STUN its really only trusted trunks.

On the Sonic wall make sure there are no SIP transform sets on.

Also, when you run STUN is the port thats filled out say 5060 or some random 10xxx port number?



ACSS - SME
General Geek



1832163.png
 
the run stun element should set the nat type for you , that is not an option you need to fill in , also when using gamma trunks under youre sip line /use network network topology needs to be set to none , i know this seems strange but it follows the IP route rules.

APSS (SME)
ACSS (SME)
 
Monty, if you set it to NONE then the STUN server will be irrelevant, which will negate what we have been explaining ;-)

ACSS - SME
General Geek



1832163.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top