Vasil Velichkov
Vasil Velichkov
Hi @jain-ab, Can you provide the initial message in XER or another format, the exact ASN.1 files as extracting the ASN.1 from the specs is a tedious and time consuming...
> ../a38473-f40.asn Can you share this file? You can use [markdown](https://guides.github.com/features/mastering-markdown/) to format your messages.
Hi @jkalmar, > It seems that there is some bug because I'm not able to decode message the asn1c just encoded. Could you provide the message in `XER` format? The...
Ok, that's good to know, but still could you please print it as XER as this could facilitate debugging. > It seems that in PDUSessionResourceSetupRequestTransfer the QosFlowSetupRequestList is the troubling...
Hi @jkalmar, There is a bug - the elements count is not calculated correctly when there are two IE elements with different IDs but with the same type (`UPTransportLayerInformation` in...
And here is the `XER` output of `./converter-example -p PDUSessionResourceSetupRequestTransfer -iaper message.aper` after applying the workaround and regenerating the code. ```xml 130 2000000 4000000 134 139 0001000101000110000100000001000000111111111111100000000000000000 0000000000000000000000000000000000000000000000000000000000000000 00010001010001100001000000010000 40...
Hi @brchiu, Just tested it using your branch and it works like a charm. Many thanks.
> From asn1c: > >000104008200~~10~~00031e8480033d0900008600~~0a~~00008b00~~80~~8000150011 >4610103ffe000000000000000000001146101040010105008800~~10~~010100 >0105008000010500090000 > >From Nokalva: > >0001040082000900031e8480033d09000086000100008b001c8000150011 >4610103ffe0000000000000000000011461010400101050088000e010100 >0105008000010500090000 > >The difference in in one byte only (7th, counting from 1). The wrong one has...
> What would be a solution in your opinion? It appears that one should copy CHOICE_encode_oer to OPEN_TYPE_encode_oer, and replace encoding of the outermost tag with the encoding of length,...
> @velichkov but is it correct??? The specification is quite complex. From Rec. ITU-T X.691 (08/2015) ``` 16 Encoding the bitstring type ... 16.2 Where there are no PER-visible constraints...