When trying to create an atadefault.cfg file, I noticed the ptag.dat file is missing from all SCCP/MGCP bundles. The ptag.dat file can be retrieved from the SIP/H323 bundle in order to create the necessary binary file.
With the procedure given in the document, you should be able to create the atadefault file. If it gives an error, that the ptag.dat file is not found, it can be found in MGCP. Search for mgcp_ptag.dat . Then rename it to ptag.dat and proceed.
You are correct. There are two parameters that my example profile for Cisco ATA (SCCP) 2.16 release did not like. They were AltTftpURL and TOS.
My solution was to just put a hash (#) at the beginning of each of the offending lines to comment it out. I also preceded each of those lines with another hashed comment line explaining why I did what I did, so I would remember later on.
The formatting tool ran fine for me after that. The ATA 186 is currently deployed as emulating two 7960 IP Phones, with one line per "phone" under CallManager 3.0(12). Each phone port is connected to its own distinctive external ringer in the maintenance garage at a local school district; each shares a directory number with one of the two lines on the 7940 in the garage office. It works great.
The hardest part for me was figuring out how to set ConnectMode. Once I enabled 7960 emulation for my older version of CallManager, the ATA auto-registered fine.
Remember, if the settings I commented out are important to your configuration, you can always go back later to set those items via http/web browser, or use the IVR access codes.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...