Referencing thread690-1208811 - Updated-Using a Cisco ATA190/SIP

[demanding]

I have a Cisco ATA190/SIP device that we want to test in our environment for misc. analogs and a few fax lines. We expect a lot of this will fade away and have already seen that in a couple of offices but in the meantime, want to see if this will work because management wants to do away with our gateways, etc. since we are all on SIP trunks now. We have CM6.0.2 and Session Mngr 6.2 - several questions:

1 - I have configured a test ext in CM with a trunk group over to Session Mngr (noting the same text ext set up as SIP). We have done this for special AV modem connections a vendor needed. I figured the same would apply to my test.

2 - I can get into the ATA device using the usual admin login but I do not have any way to change the config...like I have seen in old ATA documentation where you can add information about the system you are connecting to...maybe I do not even need to do this? Maybe that is strictly for Cisco Call Manager?

3 - So, should I add this ATA (that has DHCP/IP Address) to System Manager as a Managed Element or? And if so, what behavior should I expect? Just leery something might act up.

Maybe I'm making this harder than it needs to be...

 

[kyle555]

I'd say follow this:

http://www.devconnectprogram.com/fileMedia/download/fcd19bc6-8f22-4da3-ba57-3d7d84972e75

Basically, register the ATA as a SIP station to SM.

 

[demanding]

Thanks. I have that set up already (per comment re: other connections our AV vendor needed). So, I have the test ext programmed as a SIP station but it just ignores it.

 

[ZeroZeroOne]

I don't have any experience with the Cisco ATA190 but I have configured the AudioCodes MP114 and Cisco 7941 sets. Hopefully, the ATA190 will be similar.

For those you only need to build SIP stations. Assuming you use System Manager, build a user account for each port with an appropriate communication address and Session Manager Profile. I found the Cisco 7941 doesn't handle TLS very well - at least not on Avaya ASM 6.3 - so I created a TCP only Application Sequence.

While you can log into the AudioCodes, Cisco phones aren't directly programmable and require an .xml file with all their config info. The file name is based on the MAC address of the specific phone and in the format SEPxxxxxxxxxxxx.cnf.xml where the x's are the MAC. On Cisco's site, the file name for ATA's is ATA<MAC>.cnf.xml. The file needs to be on a TFTP server and Option 150 set in the DHCP scope to indicate the IP Address of the TFTP Server.

Option 150 for Cisco Phones

Name: TFTPServer
Data: xxx.xxx.xxx.xxx
Code: 150 (for Option 150)
Description: TFTP Server for Cisco Endpoints

I can attached the the config file for the Cisco 7941 but I'm not sure it will be the same for the ATAs.

For additional reading, check out Cisco's documentation:

http://www.cisco.com/c/en/us/td/doc...inistration/guide/sip/ATA190/a190_ag2str.html