Status: Started
Owner: [email protected]
CC: [email protected], [email protected], [email protected]
Labels: Type-Defect Priority-Medium Component-SS7 Roadmap-Fix
Version-2.0.0.FINAL
New issue 278 by [email protected]: SCCP XUDT bad possible length
calculation
http://code.google.com/p/jss7/issues/detail?id=278
In SCCP stack when encoding XUDT message there is a bug when calculating
max possible length of data field when callingParty / calledParty addresses
filelds have big length.
The result is XUDT message of some length is not segmented (as it is
needed) and the message will be encoded in a wrong way and a peer can not
decode this.
A solution is: adding an extra check:
max possible message data length must be <= 254 - (3 + calling party field
length + called party field length)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
