www.seventest.com Forum Index www.seventest.com
Форум сайта Seventest
(Это закрытый форум. На нем общаются только зарегистрированные пользователи Seventest. Регистрация)
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

MAP_CANCEL_LOCATION - считает, что неправильная длина...

 
Post new topic   Reply to topic    www.seventest.com Forum Index -> Общие вопросы
View previous topic :: View next topic  
Author Message
Alex_P



Joined: 07 Apr 2008
Posts: 12

PostPosted: Mon Jul 14, 2008 5:11 pm    Post subject: MAP_CANCEL_LOCATION - считает, что неправильная длина... Reply with quote

Quote:
80 81 3f 83 de c0 1b 10 09 80 03 0e 19 0b 12 06 00 11 04 97 21 43 65 87 f0 0b 12 07 00 11 04 97 21 43 65 87 f9 3a 62 38 48 04 01 00 00 00 6b 1a 28 18 06 07 00 11 86 05 01 01 01 a0 0d 60 0b a1 09 06 07 04 00 00 01 00 02 01 6c 14 a1 12 02 01 01 02 01 03 30 0a 04 05 21 43 65 87 09 0a 01 01 07 26


Получается вот что:

Code:
Seventest online decoder

MTP2: Russian specifications, 2000
      0 .0000000 Backward sequence number...... 0 Dec
        1....... Backward indicator bit........ 1 Dec
      1 .0000001 Forward sequence number....... 1 Dec
        1....... Forward indicator bit......... 1 Dec
      2 ..111111 Length indicator.............. 63 Dec
        00...... Spare......................... Spare
MTP3: Russian specifications, 2000
      3 ....0011 Service indicator............. SCCP
        ..00.... Spare......................... 0 Dec
        10...... Network indicator............. National network
      4 ***b14** Destination point code........ 222 Dec
        ***b14** Originating point code........ 111 Dec
        0001.... Signalling link selection..... 1 Dec
SCCP: Russian specifications, 2001
      8 00001001 Message type.................. UDT

     -- Protocol class
      9 ....0000 Protocol class................ Class 0
        1000.... Message handling.............. Return on error

     10 00000011 Pointer....................... 3 Dec
     11 00001110 Pointer....................... 14 Dec
     12 00011001 Pointer....................... 25 Dec
     13 00001011 Length........................ 11 Dec

     -- Called party address
     14 .......0 Point code ind................ PC absent
        ......1. SSN ind....................... SSN present
        ..0100.. Global title ind.............. Transl. type & Numb. plan & Enc. scheme
        .0...... Routing ind................... Route on GT
        0....... Reserved for national use..... 0 Hex
     15 00000110 Subsystem number.............. HLR
     16 00000000 Translation type.............. 0 Hex
     17 ....0001 Encoding scheme............... BCD, odd number of digits
        0001.... Numbering plan................ ISDN/Telephony Numbering plan
     18 .0000100 Nature of address ind......... International number
        0....... Spare......................... 0
     19 ***b44** Address signal................ 79123456780
        1111.... Filler........................ 15 Dec

     25 00001011 Length........................ 11 Dec

     -- Calling party address
     26 .......0 Point code ind................ PC absent
        ......1. SSN ind....................... SSN present
        ..0100.. Global title ind.............. Transl. type & Numb. plan & Enc. scheme
        .0...... Routing ind................... Route on GT
        0....... Reserved for national use..... 0 Hex
     27 00000111 Subsystem number.............. VLR
     28 00000000 Translation type.............. 0 Hex
     29 ....0001 Encoding scheme............... BCD, odd number of digits
        0001.... Numbering plan................ ISDN/Telephony Numbering plan
     30 .0000100 Nature of address ind......... International number
        0....... Spare......................... 0
     31 ***b44** Address signal................ 79123456789
        1111.... Filler........................ 15 Dec

     37 00111010 Length........................ 58 Dec

     -- Data

TCAP: ITU-T Q.773 White book, 1997

     -- Message type
     38 ***b8*** TAG: class=1 code=2 type=1
     39 ***b8*** Length........................ 56 Dec

     -- BEGIN
     40 ***b8*** TAG: class=1 code=8 type=0
     41 ***b8*** Length........................ 4 Dec

     -- Originating transaction id
     42 ***B4*** .............................. 1000000 Hex

     46 ***b8*** TAG: class=1 code=11 type=1
     47 ***b8*** Length........................ 26 Dec

     -- Dialogue portion

     -- Dialogue portion
     48 ***b8*** TAG: class=0 code=8 type=1
     49 ***b8*** Length........................ 24 Dec

        -- External
        50 ***b8*** TAG: class=0 code=6 type=0
        51 ***b8*** Length........................ 7 Dec

           -- Dialogue as id

              -- Object id
              52 0....... Extension..................... Last octet
                 .0000000 OrgEntity..................... ITU-T recommendation
              53 00010001 Recommendation letter......... Q
              54 ***b16** Recomendation number.......... 773 Dec
              56 00000001 Modules....................... AS
              57 00000001 AS............................ Dialogue AS
              58 00000001 Version....................... 1 Dec

        59 ***b8*** TAG: class=2 code=0 type=1
        60 ***b8*** Length........................ 13 Dec

           -- Dialogue PDU
           61 ***b8*** TAG: class=1 code=0 type=1
           62 ***b8*** Length........................ 11 Dec

              -- Dialogue request
              63 ***b8*** TAG: class=2 code=1 type=1
              64 ***b8*** Length........................ 9 Dec

                 -- Application context name
                 65 ***b8*** TAG: class=0 code=6 type=0
                 66 ***b8*** Length........................ 7 Dec

                    -- ACN object id

                       -- Object id
                       67 0....... Extension..................... Last octet
                          .0000100 OrgEntity..................... ITU-T identified-org
                       68 00000000 Standard...................... ETSI
                       69 ***b8*** ETSI.......................... Mobile domain
                       70 00000001 Type of network............... GSM network
                       71 00000000 Modules....................... AC
                       72 00000010 Application context........... Location cancellation
                       73 00000001 Version....................... 1 Dec

     74 ***b8*** TAG: class=1 code=12 type=1
     75 ***b8*** Length........................ 20 Dec
     76 ***b8*** TAG: class=2 code=1 type=1
     77 ***b8*** Length........................ 18 Dec

        -- Invoke component
        78 ***b8*** TAG: class=0 code=2 type=0
        79 ***b8*** Length........................ 1 Dec

           -- Invoke id
           80 00000001 Invoke id..................... 01

        81 ***b8*** TAG: class=0 code=2 type=0
        82 ***b8*** Length........................ 1 Dec
        83 00000011 Local operation code.......... CANCEL LOCATION
Container: pMAP_ComponentPortion
Wrong Component Length. Must be: 144:bits Decoded: 48:bits
Undecoded data: 30 0A 04 05 21 43 65 87 09 0A 01 01

MAP: 3GPP TS 29.002 Ver 6.12.0, 2005

Remainder:
   07 26



Непонятно почему проблема с длиной, ведь после:
Code:

     76 ***b8*** TAG: class=2 code=1 type=1
     77 ***b8*** Length........................ 18 Dec

Действительно идёт 18 октетов...

Где грабли?
Back to top
View user's profile Send private message
Support
Сотрудник Seventest


Joined: 30 Sep 2005
Posts: 347
Location: Санкт-Петербург

PostPosted: Tue Jul 15, 2008 1:19 pm    Post subject: Re: MAP_CANCEL_LOCATION - считает, что неправильная длина... Reply with quote

Обратите внимание на:
...
Code:
SCCP: Russian specifications, 2001
      8 00001001 Message type.................. UDT

     -- Protocol class
      9 ....0000 Protocol class................ Class 0
        1000.... Message handling.............. Return on error

     10 00000011 Pointer....................... 3 Dec
     11 00001110 Pointer....................... 14 Dec
     12 00011001 Pointer....................... 25 Dec
     13 00001011 Length........................ 11 Dec

     -- Called party address
     14 .......0 Point code ind................ PC absent
        ......1. SSN ind....................... SSN present
        ..0100.. Global title ind.............. Transl. type & Numb. plan & Enc. scheme
        .0...... Routing ind................... Route on GT
        0....... Reserved for national use..... 0 Hex
     15 00000110 Subsystem number.............. HLR
     16 00000000 Translation type.............. 0 Hex
     17 ....0001 Encoding scheme............... BCD, odd number of digits
        0001.... Numbering plan................ ISDN/Telephony Numbering plan
     18 .0000100 Nature of address ind......... International number
        0....... Spare......................... 0
     19 ***b44** Address signal................ 79123456780
        1111.... Filler........................ 15 Dec

     25 00001011 Length........................ 11 Dec

     -- Calling party address
     26 .......0 Point code ind................ PC absent
        ......1. SSN ind....................... SSN present
        ..0100.. Global title ind.............. Transl. type & Numb. plan & Enc. scheme
        .0...... Routing ind................... Route on GT
        0....... Reserved for national use..... 0 Hex
     27 00000111 Subsystem number.............. VLR
     28 00000000 Translation type.............. 0 Hex
     29 ....0001 Encoding scheme............... BCD, odd number of digits
        0001.... Numbering plan................ ISDN/Telephony Numbering plan
     30 .0000100 Nature of address ind......... International number
        0....... Spare......................... 0
     31 ***b44** Address signal................ 79123456789
        1111.... Filler........................ 15 Dec

     37 00111010 Length........................ 58 Dec


У Вас длина всего сообщения 98, однако здесь у Вас указана длина уже 96 (38+58=96)

Далее:
Code:

TCAP: ITU-T Q.773 White book, 1997

-- Message type
38 ***b8*** TAG: class=1 code=2 type=1
39 ***b8*** Length........................ 56 Dec


Здесь опять то же самое: 40+56=96

в рекомендации

CancelLocationArg ::= [3] SEQUENCE {
identity Identity,
cancellationType CancellationType OPTIONAL,
extensionContainer ExtensionContainer OPTIONAL,
...}

Вы забыли про [3] и пытаетесь использовать конструкцию
CancelLocationArg ::= SEQUENCE {
identity Identity,
cancellationType CancellationType OPTIONAL,
extensionContainer ExtensionContainer OPTIONAL,
...}
Декодер ищет CancelLocationArg по тэгу 0xa3, соответственно, по
предлагаемому в хексе тэгу 0x30 он его найти не может, да, собственно, и не должен
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    www.seventest.com Forum Index -> Общие вопросы All times are GMT + 3 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


SwiftBlue Theme created by BitByBit
Powered by phpBB © 2001, 2002 phpBB Group