How to edit H323-ASN1 content

his page describes the way to edit the ASN1 content of H323 messages by the H323 Encoder.


Copying ASN1 content of RAS messages from the Event-Editor

The ASN1 content of a RAS message displayed in detailed format by the Clarinet Event-Editor can be used for defining the RAS messages ( GRQ, ARQ...) within the IP profile.
  • select the ASN1 content displayed in detailed format by the Event-Editor.
  • copy it to the clipboard (right click of the mouse).
  • edit the RAS message in the Clarinet IP profile.
  • paste it to the Literal PDU buffer of the RAS message.
D5 H225 RAS message 
 value RasMessage ::= gatekeeperRequest : 
  { 
    requestSeqNum 1, 
    protocolIdentifier { 0 0 8 2250 0 3 }
    rasAddress ipAddress : 
      { 
        ip 'C0A802F1'H -- 192.168.2.241 -
        port 1719 
      }, 
    endpointType 
    { 
      mc FALSE, 
      undefinedNode FALSE 
    }, 
    endpointAlias 
    { 
      h323-ID : "CLA2411", 
      e164 : "241" 
    } 
  } 

Following the "Paste", the ASN1 content can be modified and re-encoded by:

èEncode literal PDU

The hex string is saved in the Clarinet IP-profile.


Copying Hex content of RAS messages from the Event-Editor

When the ASN1 content is important, it could be easier to display it under the hex format.

  • select the hex content of the RAS messages displayed in hex format by the Event-Editor.
  • copy it to the clipboard (right click of the mouse).
  • edit the RAS message in the Clarinet IP profile.
  • paste it to Hex PDU buffer of the RAS message.
D5 H225 RAS message 
00 20 00 00 06 00 08 91 4a 00 03 00 c0 a8 02 f1 
06 b7 00 00 02 40 06 00 43 00 4c 00 41 00 32 00 
34 00 31 00 31 01 00 57 40 

Following the "Paste", the ASN1 content can be decoded by: 

èDecode hex PDU è Ras message

Then the the ASN1 content in the "Literal PDU" buffer can be modified and re-encoded by:

èEncode literal PDU

The hex string is saved in the Clarinet IP-profile.


Copying ASN1 content of H225-Sig messages from the Event-Editor

The ASN1 content of a H225-Sig message displayed in detailed format by the Clarinet Event-Editor can be used for defining the the H225-Sig messages ( SETUP, CALL PROC...) within the IP profile.
  • select the ASN1 content of the User-User IE displayed in detailed format by the Event-Editor
  • copy it to the clipboard (right click of the mouse).
  • edit the User-User IE in Coding mode within the Clarinet IP profile.
  • paste it to the Literal PDU buffer of the User-User IE.
IE:(0/7e) len:94 >> User-user 
 Oct 3 : 00000101 Protocol = X208/X209 (ASN.1) 
 value H323-UserInformation ::= 
 { 
  h323-uu-pdu 
   { 
    h323-message-body connect : 
    { 
     protocolIdentifier { 0 0 8 2250 0 3 }, 
     h245Address ipAddress : 
      { 
       ip 'C0A802D3'H -- 192.168.2.211 --, 
       port 1024 
      }, 
     destinationInfo 
     { 
     vendor 
      { 
       vendor 
       { 
        t35CountryCode 0, 
        t35Extension 0, 
        manufacturerCode 89 
       }, 
       productId '57656C6C54656368204C616E2D50686F6E6520313031'H -- "WellTech Lan-Phone 101" --, 
       versionId '31'H -- "1" -- 
      }, 
      terminal 
      { 
      }, 
      mc FALSE, 
      undefinedNode FALSE 
     }, 
     conferenceID '00611455F5ADD6110001008034000001'H, 
     callIdentifier 
     { 
     guid '80F7AC55F5ADD6110002008034000001'H 
     }, 
     multipleCalls FALSE, 
     maintainConnection FALSE 
    }, 
   h245Tunneling FALSE 
  } 
 } 

Following the "Paste", the ASN1 content can be modified and re-encoded by:

èEncode literal PDU

The hex string is saved in the Clarinet IP-profile.


Copying Hex content of H225-Sig messages from the Event-Editor

When the ASN1 content is important, it could be easier to display it under the identified  format.

  • select the hex content of the User-User IE displayed in identified format by the Event-Editor.
  • copy it to the clipboard (right click of the mouse).
  • edit the User-User IE in Hex mode within the Clarinet IP profile.
  • paste it to Hex PDU buffer of the User-User IE.
IE:(0/7e) len:94 >> User-user 
05 22 c0 06 00 08 91 4a 00 03 00 c0 a8 02 d3 04 
00 22 c0 00 00 00 59 15 57 65 6c 6c 54 65 63 68 
20 4c 61 6e 2d 50 68 6f 6e 65 20 31 30 31 00 31 
00 00 61 14 55 f5 ad d6 11 00 01 00 80 34 00 00 
01 17 0c 00 11 00 80 f7 ac 55 f5 ad d6 11 00 02 
00 80 34 00 00 01 01 00 01 00 08 80 01 00 

Following the "Paste", the ASN1 content can be decoded by: 

èDecode hex PDU è H323-UserInformation

Then the the ASN1 content in the "Literal PDU" buffer can be modified and re-encoded by:

èEncode literal PDU

The hex string is saved in the Clarinet IP-profile.


Copying a part of ASN1 content of H225-Sig messages from the Event-Editor

When the ASN1 content is important, it could be easier to display it under the identified  format.

  • select the partial hex content of the User-User IE displayed in identified format by the Event-Editor. 
  • copy it to the clipboard (right click of the mouse).
  • edit the User-User IE in Coding mode within Clarinet IP profile.
  • paste the partial hex content to the Hex PDU buffer of User-User IE.
IE:(0/7e) len:94 >> User-user 
05 22 c0 06 00 08 91 4a 00 03 00 c0 a8 02 d3 04 
00 22 c0 00 00 00 59 15 57 65 6c 6c 54 65 63 68 
20 4c 61 6e 2d 50 68 6f 6e 65 20 31 30 31 00 31 
00 00 61 14 55 f5 ad d6 11 00 01 00 80 34 00 00 
01 17 0c 00 11 00 80 f7 ac 55 f5 ad d6 11 00 02 
00 80 34 00 00 01 01 00 01 00 08 80 01 00 

Following the "Paste", the ASN1 content can be decoded by: 

èDecode hex PDU è H323-UserInformation

Then the the ASN1 content in the "Literal PDU" buffer can be modified and re-encoded by:

èEncode literal PDU

The hex string is saved in the Clarinet IP-profile.


Modifying ASN1 Logical Channel of H225-Sig messages in IP profiles

The "Literal PDU" buffer displays the ASN1 content of the H225-Sig messages. When it includes a fastart option, the content of the "Open Logical Channel" field is encoded in Hexa value.
To modify  the "Open Logical Channel" field:

  • select the hex content of "Open Logical Channel"

fastStart 
        {
         '0000000C2013800B0500010000000000000080'H
--value OpenLogicalChannel ::= 
--{
-- forwardLogicalChannelNumber 1,
-- forwardLogicalChannelParameters 
-- {
-- dataType audioData : g711Alaw64k : 20,
-- multiplexParameters h2250LogicalChannelParameters : 
-- {
-- sessionID 1,
-- mediaControlChannel unicastAddress : iPAddress : 
-- {
-- network '00000000'H 0.0.0.0,
-- tsapIdentifier 0
-- },
-- silenceSuppression TRUE
-- }
-- }
--}
,

The Decode selected PDU button becomes active and the content can be decoded by:

èDecode PDU èOpen Logical Channel

The ASN1 content of "Open Logical Channel" is displayed in a secondary window and can be modified:

value OpenLogicalChannel ::= 
 {
 forwardLogicalChannelNumber 1,
 forwardLogicalChannelParameters 
  {
   dataType audioData : g711Alaw64k : 20,
   multiplexParameters h2250LogicalChannelParameters : 
    {
       sessionID 1,
       mediaControlChannel unicastAddress : iPAddress : 
         {
            network '00000000'H -- 0.0.0.0 --,
            tsapIdentifier 16588
         },
      silenceSuppression TRUE
    }
  }
 }

If any modification, the ASN1 content of "Open Logical Channel" must be re-encoded by:

Encode literal PDU

Then validate with OK to go back the primary editing H323 Encoder window.

 

home     Quick start     Specifications     Connections     Features     How to?     Notes     Search     Site Map

updated:  27-Feb-04