Problem With Cisco ATA 186 SIP Mode

Problem With Cisco ATA 186 SIP Mode

Post by Jim Lawso » Sat, 09 Mar 2002 02:43:21



Greetings,

Several months ago, I had an ATA 186 analog adaptor up & running on my
local network.  Was able to place calls w/o any problems.  I've since
sent that particular adaptor to my brother in Hawaii for his use.  I now
have a new ATA, & it just refuses to work for me in SIP mode...

Network layout:

Internet <-> Linux Firewall <-> Internal Network <-> ATA

The ATA is configured with the following values:

DHCP = 0
Static IP = 192.168.0.201
Static Route = 192.168.0.1
Static Netmask = 255.255.255.0
UID0 = 1
PWD0 = 1
UseSIP = 1
SIPRegInterval = 3600
MaxRedirect = 5
SIPRegOn = 1
NATIP = xxx.xxx.xxx.xxx (my external interface)
SIPPort = 5060
MediaPort = 10000
Outbound Proxy = 0

I think those are the relevant parts of the ATA config.  As best I
remember, that's how I had the old ATA configured (and it worked).

ATA is running the latest firmware (v2.13)...

On my firewall, I have opened ports 10000 & 5060.  I am also forwarding
traffic from the outside bound to those ports to the IP of my ATA
(192.168.0.201)...  this has not changed since working with the old ATA.

If I disable SIP & use H.323, I am able to place a call.  Of course, I
can't hear anything (because it can't get back through my firewall), but
I've confirmed the call goes through via testing with my brother.

If I run a packet sniffer on my local LAN while running in H.323, I see
packets coming from the ATA.  My sniffer shows *no traffic at all* from
the ATA when I run in SIP mode...  as if the ATA weren't even sending
packets out it's interface.

I've also seen the following when sniffing:

arp who-has phone tell phone
(where phone = the name I have defined in /etc/hosts on the firewall)

I find that interesting, because I've never seen a device send out an
ARP request for it's own interface?  Is that normal?

Also, I've run Nmap on the ATA & the only port it shows open is 80...
Shouldn't 5060 & 10000 be open too?  Or are they only opened when a call
is in progress?

I'm really beating my head here.  If anyone has any ideas as to what the
problem is, I'd appreciate a pointer!  Is it a config problem, or is the
ATA bad?

Thanks!

 
 
 

1. Problem With Cisco ATA 186 SIP Mode

Greetings,

Several months ago, I had an ATA 186 analog adaptor up & running on my
local network.  Was able to place calls w/o any problems.  I've since
sent that particular adaptor to my brother in Hawaii for his use.  I now
have a new ATA, & it just refuses to work for me in SIP mode...

Network layout:

Internet <-> Linux Firewall <-> Internal Network <-> ATA

The ATA is configured with the following values:

DHCP = 0
Static IP = 192.168.0.201
Static Route = 192.168.0.1
Static Netmask = 255.255.255.0
UID0 = 1
PWD0 = 1
UseSIP = 1
SIPRegInterval = 3600
MaxRedirect = 5
SIPRegOn = 1
NATIP = xxx.xxx.xxx.xxx (my external interface)
SIPPort = 5060
MediaPort = 10000
Outbound Proxy = 0

I think those are the relevant parts of the ATA config.  As best I
remember, that's how I had the old ATA configured (and it worked).

ATA is running the latest firmware (v2.13)...

On my firewall, I have opened ports 10000 & 5060.  I am also forwarding
traffic from the outside bound to those ports to the IP of my ATA
(192.168.0.201)...  this has not changed since working with the old ATA.

If I disable SIP & use H.323, I am able to place a call.  Of course, I
can't hear anything (because it can't get back through my firewall), but
I've confirmed the call goes through via testing with my brother.

If I run a packet sniffer on my local LAN while running in H.323, I see
packets coming from the ATA.  My sniffer shows *no traffic at all* from
the ATA when I run in SIP mode...  as if the ATA weren't even sending
packets out it's interface.

I've also seen the following when sniffing:

arp who-has phone tell phone
(where phone = the name I have defined in /etc/hosts on the firewall)

I find that interesting, because I've never seen a device send out an
ARP request for it's own interface?  Is that normal?

Also, I've run Nmap on the ATA & the only port it shows open is 80...
Shouldn't 5060 & 10000 be open too?  Or are they only opened when a call
is in progress?

I'm really beating my head here.  If anyone has any ideas as to what the
problem is, I'd appreciate a pointer!  Is it a config problem, or is the
ATA bad?

Thanks!

2. Chopper Force on RPC?

3. how to connect ATA 186 Phone to ATA 186 Phone

4. 2004 Deluxe vs Premium

5. How different is the new ATA 186-I1 from the old ATA 186 -L-I1?

6. VxWorks on Linux

7. Configure Cisco ATA-186 Analog/SIP/h323 via 2600 and FXO voice cards

8. Multiple Profile Problem

9. Cisco ATA 186 and Ubiquity SIP UA

10. Configure Cisco ATA-186 Analog/SIP/h323 via 2600 and FXO voice cards

11. ATA 186 & AS5300 peer-to-peer - SIP