your engineer has changed the config register in a way that the console speed has been altered. To be able to get "understandable" characters back on your terminal sessions, you need to synchronize the speed setting between your router console port and the terminal program your are using.
The speed values that can be set, using the bits of the configuration register are 1200, 2400, 4800 & 9600 bps. Use the trial and error method to discover the new setting and then you will be able to communicate with your router and change the config register value to the one you need.
Don't forget to disconnect and then connect back your terminal session for the new speed setting to be effective.
Your engineer changed the config register to a value that didn't change the console speed from the usual 9600 bps (bits 5, 11 and 12 are set to 0), but he set bit 4 which is reserved... If you still can't access the router, I suggest you open a TAC case.
If he had changed any bit that controls the console speed (bits 5, 11 and 12), the trial and error method already suggested by Wassim would work.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.