Glen, One thing mentioned on the reflector was moving the CallIdentifier to the H323-UU-PDU part of the message rather than including it separately in each constituent part of the message. This moves it to the highest layer of commonality and also means that it is in the same place for all messages. This is important as the module that decides which call the message belongs to should not really have to know large amounts about the format of each message. Below should show the change I mean: H323-UU-PDU ::= SEQUENCE { h323-message-body CHOICE { setup Setup-UUIE, callProceeding CallProceeding-UUIE, connect Connect-UUIE, alerting Alerting-UUIE, userInformation UI-UUIE, releaseComplete ReleaseComplete-UUIE, facility Facility-UUIE, ..., progress Progress-UUIE, empty NULL -- used when a FACILITY message is sent, -- but the Facility-UUIE is not to be invoked -- (possible when transporting supplementary -- services messages) }, nonStandardData NonStandardParameter OPTIONAL, ..., h4501SupplementaryService SEQUENCE OF OCTET STRING OPTIONAL, -- each sequence of octet string is defined as one -- H4501SupplementaryService APDU as defined in -- Table 3/H.450.1 callIdentifier CallIdentifier } Regards, Pete ================================= Pete Cordell BT Labs E-Mail: pete.cordell@bt-sys.bt.co.uk Tel: +44 1473 646436 Fax: +44 1473 645499 =================================
participants (1)
-
Pete Cordell