Incorrect Packet Downlink Assignment message in TbfTest.err

Saurabh Sharan Saurabh.Sharan at radisys.com
Tue Mar 8 14:21:55 UTC 2016


Hello All,
This mail is to highlight the necessity of the "[PATCH] Fix encoding of padding bits to start with 0 bit"
In the latest master osmo-pcu 0.2.752-173e, the identified bug in encoding of padding bits is generating incorrect Control message.

Example of an incorrect Packet Downlink Assignment message from the current TbfTest.err log is @ line number 3433
Sending data request: trx=0 ts=4 sapi=5 arfcn=0 fn=0 block=0 data=4f 08 20 00 44 02 00 02 08 04 00 c0 0b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
Incorrect encoding has resulted in the analyzer interpreting PFI present with value 21.

Whereas with the fix for encoding padding bits result is
Sending data request: trx=0 ts=4 sapi=5 arfcn=0 fn=0 block=0 data=4f 08 20 00 44 02 00 02 08 04 00 c0 03 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b

Output of the message analyzer(http://www.3gpp-message-analyser.com/) is attached in the mail.

Please review the patch and let us know procedure for a merge to master.

Regards
Saurabh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20160308/d605e423/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: osmolog.txt
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20160308/d605e423/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: paddingFixlog.txt
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20160308/d605e423/attachment-0001.txt>


More information about the osmocom-net-gprs mailing list