Just curious,
Is there a reason you’re using PushPublisher between two wowza servers? I believe Live Stream Repeater is recommended between two wowza based CDNs. PushPublish is more for wowza to FMS/CDN. In any case I believe you need to send the info along the netstream metadata.
Cheers,
Pete
Hellas,
did anyone succesdfully push-publish a stream to ustream.tv ?
We already push streams to different CDN providers including livestream.com but have now an issue with ustream.tv.
We can successfully connect to the ingest server but we are able to publish the stream.
We tried already with different options of
publisher.setRemoveDefaultAppInstance(true);
publisher.setConnectionFlashVerion(“FMLE/3.0”);
without any success.
publisher.setHostname(“1.xxxxxxxxx.fme.ustream.tv”);
publisher.setPort(1935);
publisher.setDstApplicationName(“ustreamVideo”);
publisher.setDstAppInstanceName(“777xxxxx”);
publisher.setDstStreamName(“nilJslfZP83FFZLvBGR2DCxxxxxxxxx”);
Any ideas ?
Thanks in advance for your help.
Hi Richard,
thanks a lot for your assistance. Removing the line
publisher.setRemoveDefaultAppInstance(true);
doesn’t make a lot of difference. I get definitly connected but it looks to me that I get some sort of time out.
I see in the log about every 120 seconds
INFO server comment - PushPublisher.sessionClosed
INFO server comment - PushPublisher.sessionClosed: reconnect: isCurrentSession:true tryConnect:true
INFO server comment - PushPublisher.sessionOpened:
Regards
Joe
Richard
the encoding device is not capable of generating a rtmp ingest just an rtp/udp stream so we want to use the Wowza as an ingest service for different CDN’s.
Meanwhile I managed to publish the stream to ustream.tv and automatically get the channel online.
The issue was the way ustream.tv reads the rtmp connection string. But thanks to the pushpublish library you can manipulate different options.
The only thing I still see is the disconnect of the PushPublisher object and the reconnect.
INFO server comment - PushPublisher.sessionClosed
Regards
Joe
Hi Tom,
I sent you an email with all the instructions how far I got but I still see the disconnect issue.
Hope you have more luck.
Cheers
Joe
Wanted to update this thread and add that I have had this module working with Edgecast for some time; I just got done broadcasting a 48 hour long live stream with it in fact. I see a few others here are using it with EC as well so maybe update the original post to reflect this/add Edgecast to the list of CDN’s?
Am trying to configure RTSP stream for Blackberry & Windows Mobile Devices and push the stream from wowza to Akamai CDN. Can someone help, please… thanks.
Am trying to configure RTSP stream for Blackberry & Windows Mobile Devices and push the stream from wowza to Akamai CDN. Can someone help, please… thanks.
Guys, is there any chance that when I push the stream from our Wowza through the AddOn package to [let’s say] Akamai, the clients connecting to the stream through Akamai will be able to use the SharedObject running on the Wowza? (e.g. to be able to chat with each other).
Thanks for any advice.
George.
I am trying to get this AddOn working with Limelight. They sent me a document that explains how to set it up with the .jar files etc. I have gone through the entire process and the module is functioning(I think) But I am getting this error:
PushPublisher.internalConnect[rtmp://*.pri.xxx.fmspush.llnw.net:1935/impact/definst/push-hd.stream]: java.nio.channels.UnresolvedAddressException
In there documentation it shows things like PushPublisher.Session open etc. I am by no means a java expert. Anyone set this up with Limelight that could give me some suggestions?
Thanks!
When I try to use the simplevideo streaming I am getting the following:
[ AccessManager.Reject ] :
:
I have gone through their document and setup my host,stream name, and authentication method with user/pass. This is my encode path and I am wondering if this may be part of the issue with rtmp push: Live Video -> MPEG-TS Encoder --> Wowza -> LL. In their examples they show their FMS sending a stream name etc. My current setup doesn’t work that way. Is there a possibility that this could be part of the issue?
We are using an mpeg-ts encoder. I will try rebuilding this again and see what happens. When starting this in the stream manager I am just specifying my stream name aka hd.stream which contains my udp://0.0.0.0 and my port number. This should work as far as I can tell.
Got the plugin working with Akamai (yay!) and now trying to get it to work with Ustream. I can see that I’m trying to connect but I have a feeling that the /definst/ may be getting in the way. Is there an easy way to remove that from the URI? I don’t see it in the push-publish example so I’m wondering if that is getting inserted by the actual pre-compiled pushpublish plugin?
Please please please help me to get this working… We are newbies here and want help. Possible?
Got the plugin working with Akamai (yay!) and now trying to get it to work with Ustream. I can see that I’m trying to connect but I have a feeling that the /definst/ may be getting in the way. Is there an easy way to remove that from the URI? I don’t see it in the push-publish example so I’m wondering if that is getting inserted by the actual pre-compiled pushpublish plugin?
Hi,
I am looking to push to youtube live using youtube’s own cdn. Is this possible with the Push Publish Addon?
James
Yes, you can publish with an RTMP encoder. We have streamed to Youtube using FMLE in previous projects.
Hello bmckim,
thanx for sharing the code. Could you please also share your conf/live/Application.xml file.
Thanx
-s.
Got it working!
Here is my code in case anyone wants to reuse.
// Source stream publisher.setAppInstance(appInstance); publisher.setSrcStreamName("test"); // Destination stream publisher.setHostname(dstHost); publisher.setDstApplicationName(dstApp); publisher.setDstStreamName(dstStream); publisher.setPort(1935); publisher.setSendFCPublish(true); publisher.setSendReleaseStream(true); publisher.setSendOriginalTimecodes(true); publisher.setAkamaiUserName(akamaiUsername); publisher.setAkamaiPassword(akamaiPassword); publisher.connect(); publishers.put(stream, publisher);
To see published streams in JConsole you have to add IMediaStream to /conf/Server.xml /AdminInterface /ObjectList
Richard
Hi,
Is this still working in the same way? I’m trying to continous information about whether the pushpublish plugin has a working connection to Level 3, for monitoring purposes. I’d like to somehow trigger an alarm if that connection fails. Is there anyway I can get this type of information through JMX? I tried adding IMediaStream in the Server.xml but I’m not seeing anything in JConsole.
To integrate an alarm, an email alert for example, you would have to use the PushPublish API. Take a look at the /sample folder in the Push package as a starting place. Then you can add IPushPublisherRTMPNotify interface to detect problems and add email alert. Take a look at this post for an example of using IPushPublisherRTMPNotify
Richard
Ok. That’s not exactly what I’m looking for. I was hoping there was a way to get information about connections that can be pushed to an external montioring system and have alarms and such triggered from there. The benefit would be seeing trends and such. Is there no information to be had through JMX? Something similar to wowza application connections and so on?
© 2007–2024 Wowza Media Systems™, LLC. All rights reserved. Security & Privacy PolicyLegalSystem Status