Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transport profile on inbound messages #638

Closed
emilbokenstrand opened this issue Oct 31, 2023 · 2 comments
Closed

Transport profile on inbound messages #638

emilbokenstrand opened this issue Oct 31, 2023 · 2 comments

Comments

@emilbokenstrand
Copy link

For the Peppol Transaction Statistics Reporting we need the transport profile that being used. All our participants are set up with profile 'peppol-transport-as4-v2_0' but when I want to extract the transport profile for inbound messages I always get 'bdxr-transport-ebms3-as4-v1p0'.

I use the following code upon receiving a file when trying to extract it:
network.oxalis.api.inbound.InboundMetadata.getProtocol and my oxalis version is 6.1.1

Am I doing something wrong?

@aaron-kumar
Copy link
Member

Fixed with commit a4aa946

@nkoudelia
Copy link

@aaron-kumar I'm using norstella/oxalis-as4:6.4.0 but the StatisticsService plugin is still reporting all incoming messages to use bdxr-transport-ebms3-as4-v1p0. Is there something wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants