Skip to content
Snippets Groups Projects
  • George Joseph's avatar
    22db16fa
    endpoint/stasis: Eliminate duplicate events on endpoint status change · 22db16fa
    George Joseph authored
    
    When an endpoint is created, its messages are forwarded to both the tech
    endpoint topic and the all endpoints topic. This is done so that various
    parties interested in endpoint messages can subscribe to just the tech
    endpoint and receive all messages associated with that particular technology,
    as opposed to subscribing to the all endpoints topic. Unfortunately, when the
    tech endpoint is created, it also forwards all of its messages to the all
    topic. This results in duplicate messages whenever an endpoint publishes its
    messages.
    
    This patch resolves the duplicate message issue by creating a new function
    for Stasis caching topics, stasis_cp_sink_create. In most respects, this acts
    as a normal caching topic, save that it no longer forwards messages it receives
    to the all endpoints topic. This allows it to act as an aggregation "sink",
    while preserving the necessary caching behaviour.
    
    ASTERISK-25137 #close
    Reported-by: Vitezslav Novy
    
    ASTERISK-25116 #close
    Reported-by: default avatarGeorge Joseph <george.joseph@fairview5.com>
    Tested-by: default avatarGeorge Joseph <george.joseph@fairview5.com>
    
    Change-Id: Ie47784adfb973ab0063e59fc18f390d7dd26d17b
    22db16fa
    History
    endpoint/stasis: Eliminate duplicate events on endpoint status change
    George Joseph authored
    
    When an endpoint is created, its messages are forwarded to both the tech
    endpoint topic and the all endpoints topic. This is done so that various
    parties interested in endpoint messages can subscribe to just the tech
    endpoint and receive all messages associated with that particular technology,
    as opposed to subscribing to the all endpoints topic. Unfortunately, when the
    tech endpoint is created, it also forwards all of its messages to the all
    topic. This results in duplicate messages whenever an endpoint publishes its
    messages.
    
    This patch resolves the duplicate message issue by creating a new function
    for Stasis caching topics, stasis_cp_sink_create. In most respects, this acts
    as a normal caching topic, save that it no longer forwards messages it receives
    to the all endpoints topic. This allows it to act as an aggregation "sink",
    while preserving the necessary caching behaviour.
    
    ASTERISK-25137 #close
    Reported-by: Vitezslav Novy
    
    ASTERISK-25116 #close
    Reported-by: default avatarGeorge Joseph <george.joseph@fairview5.com>
    Tested-by: default avatarGeorge Joseph <george.joseph@fairview5.com>
    
    Change-Id: Ie47784adfb973ab0063e59fc18f390d7dd26d17b