Comment # 5
on bug 6112
from Anders Broman
(In reply to Guy Harris from comment #4)
> (In reply to Anders Broman from comment #2)
> > The code is generated from TCAP-Remote-Operations-Information-Objects {iso(1)
> > memberbody(2) usa(840) t1-114(10013) modules(0) informationObjects(1)
> > version4(4) }
> > :
> > ErrorCode ::= CHOICE {
> > national [PRIVATE 19] INTEGER (-128..127),
> > private [PRIVATE 20] INTEGER
> >
> > So it looks like a tag for integer is expected after "Private 20" changing
> > it to
> >
> > ErrorCode ::= CHOICE {
> > national [PRIVATE 19] INTEGER (-128..127),
> > private [PRIVATE 20] IMPLICIT INTEGER
> > }
> >
> > Makes the dissection work:
> > errorCode: private (20)
> > private: -127
> > private: 2320
> > ANSI Mobile Application Part
> >
> > Where
> > ANSI Mobile Application Part covers:
> > 0000 f2 00 ..
> >
> > Should the definition be IMPLICIT?
>
> Not according to
>
>
> ftp://ftp.3gpp2.org/Archive/TSGN%20(inactive)/Working/2001/2001_02_Chandler/
> Opening_Plenary/fyi%20T1%20Ballots/T1.114Ballot.pdf
>
> which says in the informative - not normative - Annex A:
>
> ErrorCode ::= CHOICE {
> national [PRIVATE 19] INTEGER -128..127,
> private [PRIVATE 20] INTEGER
> }
>
> I tried getting the current version of T1.114 from ATIS:
>
> https://www.atis.org/docstore/product.aspx?id=24593&type=2&Add=1
>
> but the password I used when trying to register for the Document Center
> doesn't work (I sent them an e-mail about it - perhaps it was too long or
> used invalid characters; Web sites have an annoying tendency 1) not to allow
> long passwords, 2) not to allow special characters in passwords, and 3) not
> telling you, when you register or set your password, that your password is
> invalid).
Initially I thought it may have been an error in the specification (I have a
copy) but I haven't found any amendment to it. Looking in some internal
documents for ANSI MAP which unfortunatly just specify the byte format not
using an ASN1 description they just expect a one byte errorcode following the
PRIVATE 20 tag. So it looks like ANSI MAP utelize the private errorcode as I
ammended the ASN1 description. Possibly we should add a check if it's ANSI MAP
before interpreting the errorcode in this way as opther ANSI TCAP users may use
it as specified in the original ASN1 description. But currently I think we only
have ANSI MAP over ANSI TCAP.
You are receiving this mail because:
- You are watching all bug changes.