Attention is currently required from: daniel, laforge, lynxis lazus.

View Change

5 comments:

• File src/ss7_as_vty.c:

  • Patch Set #4, Line 269: "When receiving a TCAP Continue/End/Abort message where no ASP can be assosiated (either via session tracking or by TCAP range for dtid). How should this message handled.\n"

    Done

    This was not addressed.

  • Patch Set #4, Line 547: const char *tcap_unroutable_str = get_value_string_or_null(osmo_ss7_as_tcap_unroutable_vals,

    No, it is also used by LOAD_SHARE_AS.

    Done

• File src/tcap_as_loadshare.c:

  • Patch Set #3, Line 510: rc = -ENOKEY;

    Not sure what you mean.

    Done

• File src/tcap_as_loadshare.c:

  • Patch Set #4, Line 478: /*! When a TCAP MSU from an ongoing session (TCAP != Begin) could not routed either by the TCAP session tracking or

    Done

    This was not addressed...

  • Patch Set #4, Line 506: /* Message is handled and will be routed elsewhere */

    afaiu this comment is misleading, since case "rc" is actually an error and the message is not being […]

    Done

To view, visit change 43008. To unsubscribe, or for help writing mail filters, visit settings.