Skip to content

Cross-connect will not work #73

@SummaNetworks

Description

@SummaNetworks

When connected to 2 DRAs, the traffic shall be sent to the originator if still OK, and then try the second one. So, currently the message delivery will select the peer based on the list of peers obtained from the configuration:

  1. Peer dra1.realm.com for realm.com
  2. Peer dra2.realm.com for realm.com
    So, when reading the selectedPeer, the stack will load using the realm, and simply use the first from the list of peers obtained, not being always the originator of the message. It should select the peer that originated the message.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions