Hello,
I’m trying to get to the bottom of an issue I’m having with PushPublishing to Edgecast. When I start a stream everything works great, with PushPublisher#PingResult.onResult returning true for hours, days and even weeks.
But then sometimes I start to get a few PushPublisher#PingResult.onResult returning false. And then the below is logged and the stream does not play off EC.
2013-04-07 09:33:12 EDT comment server INFO 200 - PushPublisher#PingResult.onResult: false - - - 179123.801 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-04-07 09:33:12 EDT comment server WARN 200 - PushPublisher: ping timeout: reset connection - - - 179123.801 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-04-07 09:33:12 EDT comment server INFO 200 - PushPublisher.resetConnection: com.wowza.wms.plugin.pushpublish.protocol.rtmp.PushPublisherRTMPSession@7f7090 - - - 179123.801 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-04-07 09:33:12 EDT comment server INFO 200 - PushPublisher.sessionClosed - - - 179123.802 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-04-07 09:33:12 EDT comment server INFO 200 - PushPublisher.sessionOpened: - - - 179123.809 - - - - - - - - - - - - - - - - - - - - - - - - -
It appears Wowza is not sending any data to the FMS (Edgecast) when this happens. The tcp connection is there, viewed with netstat. To get it working again I need to push to a different ingest location
What can cause the PushPublisher#PingResult.onResult to return false and then to reset the connection?
Thanks
Austin