Hello, I have CallManager 8.6 running and am trying to get a 9971 to register. I have a few softphones working with SCCP but can not get the 9971 to work.
This is a new lab setup and the callmanager is using the Demo Licenses. From what i have researched ( & ) i believe it has something to do with ITL. The phone attempts to update the trust list but then says 'no trust list installed' followed by ' TFTP timeout: ram/SEPXXXXXXXX.CNF.XML' Can someone please assist me? How can i get this phone to register without a USB Etoken?
I tried 'Prepare Cluster for Rollback to pre-8.0' in enterprise parameters but that didnt seem to work much thanks! Team, I haven't able to figure out this thing in my LAB.
Explanation The SFP module was identified as a Cisco SFP module, but its vendor ID and serial number match that of another SFP module in the system. The first [chars] is the interface in which the SFP module is installed, the second [chars] is the interface where the duplicate SFP module is installed.
![Error Error](/uploads/1/2/5/4/125499037/274669281.jpg)
I disabled security services on cluster and then enabled auto registration. I did a reset all for the 9971 phones.Phone is not getting regisetered and on 9971 status messages shows No trust list found and TFTP timeout.Same behaviour if i disable the autoregistration and configure the phone manually and enabled security services but still no go. Phone is getting correct ip,TFTP via DHCP and i have SCCP phone autoregister successfully in same subnet. I can certainly do a wireshark capture from the phone port however i would like to know if someone can point me to right direction.thanks.
Plink, Cisco and PowerShell walk into a barwaitI just did that gag. I've been banging my head against this one for many days. PowerShell automation of Cisco switches through SSH. A lot of command line based SSH clients are very old and don't have a scripting language like PowerShell in mind.
More modern ones, or SSH cmdlets made for PowerShell, are expensive for commercial use and I prefer to avoid them when possible. With no native SSH in PowerShell or.NET I needed a good, working solution. I tried a couple of.NET DLLs, but none of them worked consistently so I tried Plink, the command-line version of the tried and true PuTTy SSH client. While it works well for most SSH connections there is a well documented issue with Cisco IOS.
Well documented online at least. To sum up the issue, when you use -batch to feed Plink.exe a batch file against Cisco IOS it doesn't work. You usually get an 'invalid autocommand' error or something like 'only only command per line' if you try to be sneaky and fit it all on one line.
![Modules Modules](/uploads/1/2/5/4/125499037/942995303.jpg)
It turns out there is a workaround for this by using StdIn to redirect the output to a text file that PowerShell can read to validate the success or failure of the command. My head hurts just writing that.