Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

ATA 186 to CallManager over PIX

I have an ATA 186 (v2.15.ms) and Call Manager 3.1.(2c). The ATA box works fine on the local LAN, but doesn't work outside PIX.

The following is my PIX config. What am I missing? Do I need other TCP ports opened? I did open any any, but it dodn't seem to fix the problem.

Also, I did see a transient connection in CM error log, which tells me that I am not completing the registration process.

Thank you,

Vladimir

fixup protocol skinny 2000

static (inside,outside) 192.168.2.4 10.30.1.50 netmask 255.255.255.255 0 0

conduit permit icmp any any

conduit permit tcp host 192.168.2.4 eq 2000 any

  • Other Collaboration Voice and Video Subjects
3 REPLIES
New Member

Re: ATA 186 to CallManager over PIX

According to a troubleshooting document I found it says "If you are using a firewall, make sure it is a Cisco PIX firewall, version 5 or later versions". Here is the link if you would like to read it. http://www.cisco.com/univercd/cc/td/doc/product/voice/ata/ataincfg/186ugch5.htm

Silver

Re: ATA 186 to CallManager over PIX

try no fixup protocol skinny 2000

also what do you mean by "doesn't work"? isn't it able to register withing the callmanager?can you place a call froman analog phone connected but there is no voice passed?

New Member

Re: ATA 186 to CallManager over PIX

Well, let me clarify.

I am able to register the phone since the last post. I fixed it by editing the phone .cnf file that contains the private IP address of the call manager. This seems to be a very poor solution, but it works.

My problem now is that I think the RTP stream is "broken". Basically, it seems that PIX doesn't change the private IP address of the remote phone (going over NAT), which means that there is only one way conversation. When I speak to headset attached to ATA the other side doesn't hear anything, but it works the other way around.

Any ideas? Has anyone done this before? Am I approaching the problem correctly?

-Vladimir

P.S.: I posted something that might resemble a diagram in "ATA remote location design recommendation" thread.

101
Views
3
Helpful
3
Replies