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
 
I normally use voiceflex too and have never had a problem with them. But this config doesn't help me at all, the Gamma trunk I'm using doesn't need to register.
 
heck I thought this was the config in question.... LOL

ACSS - SME
General Geek



1832163.png
 
Indeed, Monty you need to change the Manager account login and/or take down that config, we can configure at will over the net at the moment :)

 
I can't login otherwise i would have kicked it :)
Monty, you are having a couple of failed logins on your audit trial from me :)


BAZINGA!

I'm not insane, my mother had me tested!

 
andy sean ,, cheers for that totally missed that one ,,,must of been a friday , changed Remote manager , system , admin, security but missed manager , operator and monitor ....once again thanks lads
now locked

APSS (SME)
ACSS (SME)
 
the best way to secure it, is to remove your 0.0.0.0 IP route and only allow traffic from your IP and Gamma's.



ACSS - SME
General Geek



1832163.png
 
I guess you won't have them because i did something wrong.
Damn, i would loved doing a reboot on it :)


BAZINGA!

I'm not insane, my mother had me tested!

 
Holy cardigans Batman, what's with all those URI's and line groups[shocked], but did you try setting the network toplogy to none, btw all those IP routes are not required, the 0.0.0.0 one will cover them :)

 
I see your problem straight away

Your source port is wrong. STUN is discovering it as 43280. the NAT rule needs to be extendible (Cisco Speak) for fixing your source and destination ports. (I know you have a sonicwall and I believe the NAT rule needs to be bi-directional?)

Example on my Cisco 877 in the office:

ip nat inside source static udp 1.0.0.253 5060 93.xxx.xxx.xxx 5060 extendable

This rule ensures all udp/5060 is NATed on port 5060 on the interfaces IP address and is fixed.

ACSS - SME
General Geek



1832163.png
 
Actually Andy I do that as well as a lot of the companies we deal with that have a number of DDIs but not routing to users, and its then easy to keep a handle of all the numbers they hold and also allows for useful outbound presentation.

ACSS - SME
General Geek



1832163.png
 
Sean is good at identifying issues when it comes to being bi...

Also Tom in that config users can easily bypass your barring by dialling the 141(witheld) prefix before international or premium rate numbers, so you need 14109N barred, 14100N barred etc :)


 
Yes, I can see why that could be handy, I would keep the incoming groups as 0 though so inbound routing is easier, but that's just my preference :)

 
I was looking at that too, looks like a migration? just make all your inbound groups 0 - no need to double up on ICRs

ACSS - SME
General Geek



1832163.png
 
Thanks HSM, from your last post I've been able to go back to the Sonicwall chap who has just traced what changes the sonicwall is making to my STUN traffic and is trying to put it right which I'm hoping will fix my problem (fingers crossed)

I'll let you know when he gets back to me.
 
its SIP traffic, not STUN traffic that needs to be fixed. :)

the IPO STUN client sends dummy SIP traffic to the STUN server to determine the settings.

ACSS - SME
General Geek



1832163.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top