Make sure you have a username and password set up in the /conf/publish.password file. Or for testing purposes you could disable authentication temporarily by editing conf/[application]/Application.xml and changing RTP/Authentication/Method to none.
Another idea is to turn on debug logging by editing conf/log4j.properties and changing the log level on the first line from INFO to DEBUG. Maybe something will show up as the culprit.
That guide is for Wowza 3, but it should work if you follow the instructions using the configuration files in Wowza 4. Do not copy old configuration files from Wowza 3 to Wowza 4, rather start with Wowza 4 files.
If you still do not have this working, do a short test then send us some files. First delete the current access log, then re-start Wowza (important to restart so we can see logging for startup), and run through testing, however you are using Wowza and Cisco Content Server. Then zip up the /conf folder and current access log showing the re-start and your testing to
email@example.com. Include a link to this thread for reference.