[jpos-users] [2.1.0-SNAPSHOT] QMUX support for per-MTI mapping and response validation

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jpos-users] [2.1.0-SNAPSHOT] QMUX support for per-MTI mapping and response validation

Alejandro Revilla
For those of you not on the jPOS Slack, 

We have a situation where 800-type messages are used to re-sync the STAN, so a 0800 with a STAN=0000001 would get a reply with STAN=xxxxxx, xxxxxx being the STAN the terminal was supposed to send in first place. In those messages, we need to use a different key on 0800s but revert to the default key (i.e. 41+11) for other messages. The configuration is easy:

 <key mti="0800">41</key>

In a follow-up commit (https://github.com/jpos/jPOS/commit/aac64d370029b4696245722378e8ef1ca86d9138) we are also making sure that a response has actually a valid response MTI. We found situations where a host would reply a 0200 with another 0200 (in their mind that would be a 'reject', but QMUX was handling it back to the application as a response to the original 0200). Most applications validate that, but just in case, we wanted to stop it at the MUX level as a safety net.

PS.- A nightly build has been forced
PPS.- For a complete list of changes, see http://jpos.org/wiki/ChangeLog

jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3Dnquy-NhdQyBXMT9L3jVeHVtg%3DeZ25pSsAM%2BxBUeTndiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.