Errors / ambiguities / problems found in specs at last week's int erop

Reinhard Scholl Reinhard.Scholl at ETSI.FR
Wed Mar 1 11:33:49 EST 2000


It looks like the syntax for Progress changed between H.225.0v2 and v3.
Seems like this would present some rather basic interoperability problems.
Do I simply have the wrong syntax for v3?

This is the syntax for Progress in the published H.225.0v2 Recommendation
from the ITU:

Progress-UUIE ::= SEQUENCE
{
        protocolIdentifier                      ProtocolIdentifier,
        destinationInfo                 EndpointType,
        h245Address                             TransportAddress OPTIONAL,
        callIdentifier                          CallIdentifier,
        h245SecurityMode                        H245Security OPTIONAL,
        ...,
        tokens                                  SEQUENCE OF ClearToken OPTIONAL,
        cryptoTokens                    SEQUENCE OF CryptoH323Token OPTIONAL,
        fastStart                               SEQUENCE OF OCTET STRING OPTIONAL,
}

...and this is the syntax for the same type in v3:

Progress-UUIE ::= SEQUENCE
{
        protocolIdentifier              ProtocolIdentifier,
        destinationInfo         EndpointType,
        h245Address                     TransportAddress OPTIONAL,
        callIdentifier                  CallIdentifier,
        h245SecurityMode                H245Security OPTIONAL,
        tokens                          SEQUENCE OF ClearToken OPTIONAL,
        cryptoTokens                    SEQUENCE OF CryptoH323Token OPTIONAL,
        fastStart                       SEQUENCE OF OCTET STRING OPTIONAL,
        ...,
        multipleCalls                   BOOLEAN,
        maintainConnection              BOOLEAN
}

Paul Long
Smith Micro Software, Inc.



More information about the sg16-avd mailing list