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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco ata-186 analog voip adapter 2

Status
Not open for further replies.

FortKnox

Technical User
May 10, 2004
254
US

Woot! I have a Cisco ata-186 device registered to my Definity R11.

When I status the station it says in service, which is good.

When I try to make a call it rings half a ring and dies, and then when I do a list trace ras ip-station I get:

20:17:03 rcv ARQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
20:17:03 snd ACF endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
20:17:04 rcv DRQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
20:17:04 UNKNOWN MESSAGE endpt 192.168.223.155:1719 switch 192.168.0.40:1719 9
20:17:33 RAS TRACE COMPLETE endpt 192.168.223.155:0 ext

Anyone have any idea?
 
I got it working!

I will document step-by-step later....I promise!

I know a bunch of you want to know how to hang analog telephones off your Definity with a cheap Cisco device.
 
If you have an ATA that came from Cisco or was used in a Cisco environment it probably has the signalling firmware on it for SCCP (called skinny protocol). For the intents of this article, I will concern myself with H.323 because it is the only protocol that my switch can handle. If your switch can do SIP protocol, lucky you.

First hook your ATA-186 up in a dhcp environment and lets hope your ata is setup for dhcp. If its not, you'll have to find documentation on how to reset your device to default settings. I will assume that you know how to determine what the ip address of your ata is. If you have trouble, post a question and I am sure someone will try to help.

I will assume that your pc is 192.168.0.2
I will assume that your Definity's clan is 192.168.0.3
I will assume that your ata's ip address is 192.168.0.4

You will have to get the h323 firmware, I got mine from Cisco's site using my Cisco account...hopefully you can find it on the web, but the most current build is this filename: ata_03_01_02_h323_040927_1.zip Take that and extract it to C:\ata_03_01_02_h323_040927_1

Open a ms-dos window to C:\ata_03_01_02_h323_040927_1 and type the following command:
sata186us.exe -h192.168.223.2 -p8002 -any -d3 ATA030102H323040927A.zup and it enter.
Plug a phone into Line 1 on the ata and take the phone off the hook and then press the button on top of the ata, you should hear a voice. When you do, dial:
100#192*168*0*2*8002# and hopefully at the end it will says "successfull"

Now this is the part that was extremely difficult to figure out b/c it wasnt very well documented by Cisco.

Now open a web browser and go to:
Now you are in the internal web server in your ata where you can make settings changes.

I will share with you the settings that I changed:
GkOrProxy: the ip of my clan board
LoginID0: the H.323 extension I setup on the Avaya
UID0: the H.323 extension I setup on the Avaya
PWD0: the security password I set on the station extension in the Avaya

You will need to set your codecs on the ata to whatever you are using on your Avaya according to this table:
•0—G.723(can be selected only if LBRCodec is set to 0)
•1—G.711A-law
•2—G.711µ-law
•3—G.729A (can be selected only if LBRCodec is set to 3)

The dial plan is tricky, I still havent quite figured it out, leave it default and test, you may need to change it.

Good luck!

Troubleshooting resources:
On the Avaya you can try:
list trace ras ip-add (then ip of your ata)
list trace ras ip-sta (the h.323 extension)
list trac sta (the h.323 extension)

ATA firmware files (requires Cisco login):
Every setting you need to know about on the ata:

You may find useful info here, but it made my head spin:

I would write more, but I am crunched for time.
 
Although it works fine, I just discovered that after several minutes the call drops without warning. While do a list trace and on the phone I see this right before the call drops. Any ideas would be welcomed.

1:52:15 rcv ARQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
21:52:15 snd ACF endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
21:54:34 denial event 2012: IP FURQ-Aged Endpt-no KA endpt 192.168.223.155 dac
21:54:34 snd URQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
21:54:34 snd URQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
21:54:34 rcv UCF endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext
21:54:34 rcv UCF endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext
21:54:34 rcv DRQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
21:54:34 denial event 1966: IP DRJ-Endpt not reg endpt 192.168.223.155 data0:c
21:54:34 snd DRJ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext
21:54:49 rcv RRQ endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext
21:54:49 snd RCF endpt 192.168.223.155:1719 switch 192.168.0.40:1719 ext 329
21:54:55 RAS TRACE COMPLETE endpt 192.168.223.155:0 ext
 
I have not found a single article or thread on God's entire Internet from someone who has made a claim that this works. Everyone states that they can make a call for a minute or two and then it disconnects.

If I unplug the ata, do a list trace stat 329 (the ata extension), then plug the ata in, I see no signs ever that the ata ever attempts to register with the Avaya until I initiate a call. Once I initiate a call, I see a registration reguest and a registration confirmation, then when I hang up the ata sends a DRQ, which I assume is a disconnect request, and the Avaya says "UNKNOWN MESSAGE." While on the call, while continuing to do a list trac stat 329, I never see any communication btw the ata and the Avaya, so I guess the Avaya gets ticked off and sends a unregistration request, the ata confirms, and once the ata realizes that Avaya doesnt want to be friends anymore, then it decides to kiss and makeup and sends a registration request which apparently it should be doing throughout its relationship.

The only thing I see in the ATA that I dont understand is a section called "ConnectMode" and according to Cisco, ConnectMode is a 32-bit bitmap used to control the connection mode of the selected call signaling protocol. Details about the available settings for ConnectMode can be seen here. If you understand it and want me to try one, tell me and I will.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top