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

Wrong encoding of msisdn in UserIdentityAvp (expected TBCD) #105

Open
GoogleCodeExporter opened this issue Jul 27, 2015 · 0 comments
Open

Comments

@GoogleCodeExporter
Copy link

Diameter Sh Client RA v 2.8.0-SNAPSHOT 

According to 3GPP TS 29.329 point 6.3.2:
"The MSISDN AVP is of type OctetString. This AVP contains an MSISDN, in 
international number format as described
in ITU-T Rec E.164 [8], encoded as a TBCD-string"

UserIdentityAvpImpl.msisdn should  be encoded as TBCD String (currently is 
encoded using setAvpAsOctetString)

in net.java.slee.resource.diameter.base.events.avp.AvpUtilities.addAvp() there 
is already implemented exception for Address (issue #2758), it could be a good 
place to add other exception for TBCDString instance.

Original issue reported on code.google.com by [email protected] on 9 May 2014 at 7:52

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

No branches or pull requests

1 participant