Skip to main content
H
Hari_Chandrasekhar
Participant
July 29, 2008
Question

NetStream.Play.UnpublishNotify

  • July 29, 2008
  • 3 replies
  • 2452 views
I am facing a strange behavior with the netstream events with an edge server / origin server configuration. When a publisher stops publishing live streams, the subscribers connected through the edge server are not receiving "NetStream.Play.UnpublishNotify" event. But if the clients connect directly to the origin server, the events are received correctly without any delay. While connecting to the edge servers, if the stream is published again after disconnecting, the clients somehow receives the "UnpublishNotify" event at that time followed by the publish event. I am seeing this issue only for the "UnpublishNotify" Event. The publish event is being sent correctly. This behavior is happening only when connecting to the edge servers. Is there any configuration to change this behavior?
(We are using FMS 3)
    This topic has been closed for replies.

    3 replies

    A
    Anonymous
    August 4, 2008
    Yes, I've contacted Adobe FMS engineers directly and they said it is solved in version 3.0.2. We've updated our FMS servers and it is working now.
    A
    Anonymous
    July 30, 2008
    An issue that sounds like this one was found and is fixed in the upcoming version of the FMS. If you need more urgent support on this issue, I would recommend contacting support directly.

    -glenn
    A
    Anonymous
    July 30, 2008
    I've faced exactly same behaviour yesterday and wrote on it to Adobe.
    After digging the Flash AS 3.0 documentation I found this:
    -=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-
    info property
    info:Object [read-write]
    Language Version : ActionScript 3.0
    Player Version : Flash Player 9
    An object with properties that describe the object's status or error condition.
    The information object could have a code property containing a string that represents a specific event or a level property containing a string that is either "status" or "error".
    The information object could also be something different. The code and level properties might not work for some implementations and some servers might send different objects.
    -=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-
    Read the last sentence: "...The code and level properties might not work for some implementations and some servers might send different objects..."
    The part of documentation was about NetStatusEvent, now the question is: this is a bug or we just faced this because of implementation origin - edge server configuration?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices