I need immediate help on how do I configure my ATA 186 for SIP with Deltathree 's Proxy Server. ALSO in my setup the ATA 186 box with ver 2.14 will be assigned a statically Natted IP address ( Valid IP address ) . There is also a Checkpoint firewall in the setup. In one of the url's on the cisco site I read that to configure the ATA for NAT support with SIPyou have to configure three parameters ie1. SIP Port 2. MediaPort 3. NATIP
My douth is that for the third parameter ie NATIP
Document says the wan ip shud be the NATIP whereas the StaticRoute ip shud be the lan ip address. In this case the ATA 186 StaticIp address and the StaticRoute address will be the same ??? IS that right ?
Awaiting for any help on this
I use the ATA 186 with DeltaThree with a public IP address and work fine, I have the same problem, any news ?
In case of working with ATA186 in NAT enviorment you must understand that it will support only NAT123 and not symmetric NAT.
If you can give your E-mail aqddress I can send you our little utility to determine which NAT type you have at your location.
To answer you question the NAT IP address should be equal to the WAN IP address. Under the web configuration base page please put you routable public IP address facing the public internet.
Renzil here, Can you Pls email me ur utility for dertimining the NAT type ?
My email id is email@example.com
some one help me
i had same problem
iam able to call out side PSTN, when i use Public address
but some of our office are behind NAT using Linux IPtables
i have flushed the Rules, still iam not able to call,
iam getting FAST BUSY TONE.
i have server with 2 ethernet ports
one is public address 202.x.x.254
and another IP address is 192.168.9.254
i have assigned the ATA 186 , 192.168.8.202
subnet is 255.255.255.0
gateway is 192.168.9.254
iam trying to call, iam not able to
some one guide me where is the wrong, iam doing
what is ip address to be add in NATIP and NATServer
In both cases that you guys have describe the NATTIP should be the public IP address that the 'world' public-internet see you as.
In that field you should put the external IP address of you NAT/FW public leg IP address.
i have Put the same in NATIP is my Public IP address
still iam not able make a call
still iam getting fast busy
The NAT IP should be the IP external IP address of your 2501 router.
Other then I will recomm3nd you to verify the following:
1. Is the account is still valid in D3 network? Can you make phone calls from that account on a non NAT environment?
2. Can you make calls from the ATA on a non NAT environment?
3. Do you get dial-tone before making the call?
Yes the Account is active
i can make call using the same Box when i configure for Public IP
but iam not able to when i Use NAT using 2501 Router
yes i gave the 2501 NAT Public IP in ATA
but no luck
you have any yahoo ID
i would like to chat and sort out the Problem
reply me thanks
its become very serious problem, becoz of this iam not able to use the account
I have the same problem, making ATA work behind NAT. (shared connections DSL, CABLE etc)
Can you please send me the utility? (firstname.lastname@example.org)
I can initiate a call (ring the other party) but then no sound transmission (both ways). I tried both codecs 0 and 3 (rx and tx). that means 723 and 729 I think. still no improvements.
BTW, I can see the calls in call logs.
What do you think might be the reason for that?
Many thanks in advance,
Point the ATA at:
natrelay.deltathree.com and make sure that the NATIP address is something other than 0.0.0.0 (it doesn't matter what it is). That will tell the ATA to send and receive on the same port. The SIP NAT traversal is taken care of by this NAT relay server, and the RTP NAT traversal is taken care of by IOS.
You may have to prefix your number with 7777. (eg to call Movie Phone, dial 777712127773456). That is a temporary work around.
Use your regular account information for the Username and Password.
Let me know what the results of this are. I'd especially appreciate feedback regarding the quality of the call and if the delay or packet loss was excessive.