H.323 Signaling
This section describes some basic call flows for the Cisco ATA:
•Supported H.323 Messages
•H.323 Signaling Scenarios
Note The term Cisco ATA is used throughout this manual to refer to both the Cisco ATA 186 and the Cisco ATA 188, unless differences between the Cisco ATA 186 and Cisco ATA 188 are explicitly stated.
Supported H.323 Messages
The Cisco ATA supports the following H.323 request methods:
•Request—When registering with an H.323 gatekeeper or Gateway, an individual H.323 endpoint must begin the process by sending a request message.
•Confirm—H.323 gatekeepers and Gateways authorize individual H.323 endpoints to access and send data over the H.323 network with explicit confirmation messages.
•Reject—In the event that an H.323 gatekeeper or Gateway in unable to grant access permission to an H.323 endpoint, a rejection message is sent and call setup is halted.
•Setup—Once access to the H.323 network has been granted, H.323 components contact remote H.323 components via setup messages, initiating two-way voice, video, or data communication.
•Proceeding—When a remote H.323 component acknowledges receipt of call initiation information and agrees to perform necessary subsequent setup for two-way voice, video, or data communication, it responds with a proceeding message.
•Alerting—When a remote H.323 endpoint has begun to notify the called party of an incoming call (the phone begins to ring at the far end), an alerting message is sent back to the calling party.
•Connect—When the called party answers the call (the phone goes off hook), the remote H.323 endpoint transmits a connecting message notifying the calling party that two-way communication is ready to commence.
H.323 Signaling Scenarios
This section describes call flows for the following scenarios:
•H.323 Endpoint-to-Gatekeeper Registration
•H.323 Endpoint-to-Endpoint Call Setup with a Common Gatekeeper
•H.323 Call Setup from H.323 Network to Circuit Switched Network
Each of the call flows includes a call diagram, action descriptions table, and a sample log file.
H.323 Endpoint-to-Gatekeeper Registration
Figure D-1 illustrates the Cisco ATA registering with an H.323 gatekeeper. This scenario features registration with no authentication.
Figure D-1 Cisco ATA-to-H.323 Gatekeeper Registration
Table D-1 Action Descriptions
|
|
|
1. |
Gatekeeper Request (GRQ)—Cisco ATA to H.323 gatekeeper |
Cisco ATA sends a GRQ message to the H.323 gatekeeper to see if any gatekeepers are available for registration. |
2. |
Gatekeeper Confirmation (GCF) or gatekeeper Rejection (GRJ)—H.323 gatekeeper to Cisco ATA |
H.323 gatekeeper returns a GCF or GRJ message, indicating whether or not the responding gatekeeper is able to register new Cisco ATA devices. |
3. |
Registration Request (RRQ)—Cisco ATA to H.323 gatekeeper |
Cisco ATA sends a RRQ message to the H.323 gatekeeper in an attempt to register as part of that gatekeeper's zone. |
4. |
Registration Confirmation (RCF) or Registration Rejection (RRJ)—H.323 gatekeeper to Cisco ATA |
H.323 gatekeeper returns a RCF or RRJ message, indicating whether or not the gatekeeper will add the Cisco ATA to its zone. |
Table D-2 Log Listings
1. |
value RasMessage ::= gatekeeperRequest :
3w2d: requestSeqNum 037472,
3w2d: protocolIdentifier { 0 0 8 2250 0 2 },
3w2d: rasAddress ipAddress :
3w2d: undefinedNode FALSE
3w2d: gatekeeperIdentifier "c2600gk.komodo-tech.com",
3w2d: h323-ID :"c2600gw",
3w2d: e164 :"14085551102",
3w2d: e164 :"14088713483",
3w2d: e164 :"14088713484",
|
2. |
3w2d:value RasMessage ::= gatekeeperConfirm :
3w2d: requestSeqNum 037472,
3w2d: protocolIdentifier { 0 0 8 2250 0 2 },
3w2d: gatekeeperIdentifier "c2600gk.komodo-tech.com",
3w2d: rasAddress ipAddress :
|
3. |
value RasMessage ::= registrationRequest :
3w2d: protocolIdentifier { 0 0 8 2250 0 2 },
3w2d: discoveryComplete TRUE,
3w2d: manufacturerCode 020001
3w2d: productId '4B6F6D6F646F204520466F6E65'H,
3w2d: versionId '56657273696F6E20312E3130'H
3w2d: undefinedNode FALSE
3w2d: manufacturerCode 020001
3w2d: productId '4B6F6D6F646F204520466F6E65'H,
3w2d: versionId '56657273696F6E20312E3130'H
3w2d: willSupplyUUIEs FALSE
|
4. |
3w2d:value RasMessage ::= registrationConfirm :
3w2d: protocolIdentifier { 0 0 8 2250 0 2 },
3w2d: gatekeeperIdentifier "c2600gk.komodo-tech.com",
3w2d: endpointIdentifier "80F5235000009E12",
3w2d: willRespondToIRR FALSE
|
H.323 Endpoint-to-Endpoint Call Setup with a Common Gatekeeper
Figure D-2 illustrates a Cisco ATA initiating a connection to another Cisco ATA that is registered with the same H.323 gatekeeper. This scenario features registration with no authentication.
Note This scenario assumes that the H.323 configuration employs Slow Start Signaling with tunneling capability.
Figure D-2 H.323 Endpoint-to-Endpoint Call Setup with a Common Gatekeeper
Table D-3 Action Descriptions
|
|
|
1. |
Local Admission Request (ARQ)—Local H.323 endpoint to H.323 gatekeeper |
Cisco ATA sends a local ARQ message to the H.323 gatekeeper seeking authorization to place a call over the H.323 network. |
2. |
Local Admission Confirm (ACF) or Admission Reject (ARJ)—H.323 gatekeeper to the local H.323 endpoint |
H.323 gatekeeper returns a ACF or ARJ message, indicating whether or not the responding gatekeeper is going to allow the Cisco ATA device access to the network. |
3. |
Open TCP Channel for Q.931 messaging |
TCP port 1720 is opened, making way for the forward and reverse flow of Q.931 signaling messages between the H.323 endpoints. |
4. |
Q.931 Call Setup—Local H.323 endpoint to remote H.323 endpoint |
Call setup initiates from the local H.323 endpoint. |
5. |
Q.931 Call Proceeding—Remote H.323 endpoint to local H.323 endpoint |
Remote H.323 endpoint acknowledges call setup initiation. |
6. |
Remote Admission Request (ARQ)—Remote Cisco ATA to H.323 gatekeeper |
(Somewhat simultaneous, chronologically, to call setup and call proceeding) remote H.323 endpoint contacts the common H.323 gatekeeper, seeking authorization to complete the two-way H.323 network call. |
7. |
Remote Admission Confirm (ACF) or Admission Reject (ARJ)—H.323 gatekeeper to the remote Cisco ATA |
H.323 gatekeeper returns a ACF or ARJ message, indicating whether or not the responding gatekeeper is going to allow the Cisco ATA device access to the network. |
8. |
Q.931 Alerting—Remote H.323 endpoint to local H.323 endpoint |
Status message is sent to calling H.323 endpoint advising that the called party has been notified (phone ringing). |
9. |
Q.931 Connect—Remote H.323 endpoint to local H.323 endpoint |
Status message is sent to calling H.323 endpoint advising that the called party has answered the call (phone off hook). |
10. |
Open TCP Channel for H.245 |
Dynamically assigned TCP port is opened on both the local and remote H.323 endpoints, allowing for subsequent call setup activities (transmission and reception capability exchange, master-slave relationship determination, and so on). |
11. |
H.245 Terminal Capabilities |
Various endpoint transmission and reception capabilities defining operation of voice, video, and data are exchanged and acknowledged to ensure consistent, reliable two-way communication between endpoints. |
12. |
H.245 Terminal Capabilities |
13. |
H.245 Terminal Capabilities |
14. |
H.245 Terminal Capabilities |
15. |
Exchange of Master-Slave Determination Messages—Remote H.323 endpoint to local H.323 endpoint |
Determines master and slave assignments between H.323 endpoints. |
16. |
H.245 Open Audio Logical Channel—Local H.323 endpoint to remote H.323 endpoint |
Before actual transmission or reception of voice, video, or data, notification that the primary logical channel for the local H.323 endpoint has been opened, ensuring clear two-way communication. |
17. |
H.245 Open Audio Logical Channel Acknowledgement—Remote H.323 endpoint to local H.323 endpoint |
Remote H.323 endpoint acknowledges readiness. |
18. |
H.245 Open Audio Logical Channel—Remote H.323 endpoint to local H.323 endpoint |
Before actual transmission or reception of voice, video, or data, notification that the primary logical channel for the remote H.323 endpoint has been opened, ensuring clear two-way communication. |
19. |
H.245 Open Audio Logical Channel Acknowledgement—Local H.323 endpoint to remote H.323 endpoint |
Local H.323 endpoint acknowledges readiness. |
20. |
Bi-Directional Audio with Transcoding in the Endpoints |
Two-way communication ensues between endpoints over the H.323 network. |
Table D-4 Log Listings
1. |
value RasMessage ::= registrationRequest :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
2. |
value RasMessage ::= registrationConfirm :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
3. |
value H323_UserInformation ::=
h323-message-body setup :
protocolIdentifier { 0 0 8 2250 0 2 }
h323-ID :{"Firstname Lastname"}
productId '4D6963726F736F6674AE204E65744D656574696E...'H
conferenceID '2E9B85298E88D611AD4600A0CC5C89F1'H
conferenceGoal create :NULL
callType pointToPoint :NULL
sourceCallSignalAddress ipAddress :
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
mediaWaitForConnect FALSE
nonStandardIdentifier h221NonStandard :
data '0200000028000000000000001B00000081384274...'H
|
4. |
value ARQnonStandardInfo ::=
displayInformationElement "Firstname Lastname"
interfaceSpecificBillingId "FXS 1/1/0"
|
5. |
value RasMessage ::= admissionRequest :
callType pointToPoint :NULL
endpointIdentifier {"814EE09C0000001A"}
h323-ID :{"Firstname Lastname"}
srcCallSignalAddress ipAddress :
nonStandardIdentifier h221NonStandard :
data '8000000860132246697273746E616D65204C6173...'H
conferenceID '2E9B85298E88D611AD4600A0CC5C89F1'H
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
|
6. |
value RasMessage ::= admissionConfirm :
destCallSignalAddress ipAddress :
|
7. |
value H323_UserInformation ::=
h323-message-body callProceeding :
protocolIdentifier { 0 0 8 2250 0 2 }
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
|
8. |
value H323_UU_NonStdInfo ::=
protoParam qsigNonStdInfo :
|
9. |
value H323_UserInformation ::=
h323-message-body progress :
protocolIdentifier { 0 0 8 2250 0 2 }
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
nonStandardIdentifier h221NonStandard :
data '60011000011E041E028188'H
|
10. |
value H323_UU_NonStdInfo ::=
progIndParam progIndIEinfo :
|
11. |
value H323_UserInformation ::=
h323-message-body connect :
protocolIdentifier { 0 0 8 2250 0 2 }
conferenceID '2E9B85298E88D611AD4600A0CC5C89F1'H
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
nonStandardIdentifier h221NonStandard :
data 'C00100028006000400000002'H
|
12. |
value IRRperCallnonStandardInfo ::=
|
13. |
value RasMessage ::= infoRequestResponse :
endpointIdentifier {"814EE09C0000001A"}
nonStandardIdentifier h221NonStandard :
conferenceID '2E9B85298E88D611AD4600A0CC5C89F1'H
callType pointToPoint :NULL
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
|
14. |
value H323_UserInformation ::=
h323-message-body releaseComplete :
protocolIdentifier { 0 0 8 2250 0 2 }
reason undefinedReason :NULL
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
|
15. |
value RasMessage ::= disengageRequest :
endpointIdentifier {"814EE09C0000001A"}
conferenceID '2E9B85298E88D611AD4600A0CC5C89F1'H
disengageReason normalDrop :NULL
guid '2D9B85298E88D611AD4600A0CC5C89F1'H
|
16. |
value RasMessage ::= disengageConfirm :
|
17. |
value RasMessage ::= registrationRequest :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
18. |
value RasMessage ::= registrationConfirm :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
H.323 Call Setup from H.323 Network to Circuit Switched Network
Figure D-3 illustrates a Cisco ATA initiating a connection to a Circuit Switched Network (CSN) or Public Switched Telephone Network (PSTN) Gateway router through its local H.323 gatekeeper.
Note This scenario assumes that the H.323 configuration employs Fast Start Signaling with tunneling capability.
Figure D-3 H.323 Call Setup from H.323 Network to Circuit Switched Network
Table D-5 Action Descriptions
|
|
|
1. |
Local Admission Request (ARQ)—Local endpoint to H.323 gatekeeper |
Cisco ATA sends a local ARQ message to the H.323 gatekeeper seeking authorization to place a call over the H.323 network. |
2. |
Local Admission Confirm (ACF) or Admission Reject (ARJ)—H.323 gatekeeper to the local endpoint |
H.323 gatekeeper returns a ACF or ARJ message, indicating whether or not the responding gatekeeper is going to allow the Cisco ATA device access to the network. |
3. |
Open TCP Channel for Q.931 messaging |
TCP port 1720 is opened, making way for the forward and reverse flow of Q.931 signaling messages between the H.323 endpoint and the CSN/PSTN Gateway. |
4. |
Q.931 Call Setup—Local H.323 endpoint to remote H.323 endpoint |
Call setup initiates from the local H.323 endpoint. |
5. |
Q.931 Call Proceeding—Remote H.323 endpoint to local H.323 endpoint |
Gateway acknowledges call setup initiation. |
6. |
Gateway Admission Request (ARQ)—SCN/PSTN Gateway to H.323 gatekeeper |
(Somewhat simultaneous, chronologically, to call setup and call proceeding) Gateway contacts the common H.323 gatekeeper, seeking authorization to complete the two-way H.323 network-to-CSN/PSTN Gateway call. |
7. |
Gateway Admission Confirm (ACF) or Admission Reject (ARJ)—H.323 gatekeeper to CSN/PSTN Gateway |
H.323 gatekeeper returns a ACF or ARJ message, indicating whether or not the responding gatekeeper is going to allow the Gateway access to the network. |
8. |
Q.931 Alerting—Gateway endpoint to local H.323 endpoint |
Status message is sent to calling H.323 endpoint advising that the called party has been notified (phone ringing). |
9. |
Q.931 Connect—Gateway to local H.323 endpoint |
Status message is sent to calling H.323 endpoint advising that the called party has answered the call (phone off hook). |
10. |
Open TCP Channel for H.245 |
Dynamically assigned TCP port is opened on both the local H.323 endpoint and the Gateway, allowing for subsequent call setup activities (transmission and reception capability exchange, master-slave relationship determination, and so on). |
11. |
H.245 Terminal Capabilities |
Various endpoint transmission and reception capabilities defining operation of voice, video, and data are exchanged and acknowledged to ensure consistent, reliable two-way communication between the H.323 endpoint and the Gateway. |
12. |
H.245 Terminal Capabilities |
13. |
H.245 Terminal Capabilities |
14. |
H.245 Terminal Capabilities |
15. |
Exchange of Master-Slave Determination Messages—Remote H.323 endpoint to local H.323 endpoint |
Determines master and slave assignments between the H.323 endpoint and the Gateway. |
16. |
H.245 Open Audio Logical Channel—Local H.323 endpoint to remote H.323 endpoint |
Before actual transmission or reception of voice, video, or data, notification that the primary logical channel for the local H.323 endpoint has been opened, ensuring clear two-way communication. |
17. |
H.245 Open Audio Logical Channel Acknowledgement—Remote H.323 endpoint to local H.323 endpoint |
Gateway acknowledges readiness. |
18. |
H.245 Open Audio Logical Channel—Remote H.323 endpoint to local H.323 endpoint |
Before actual transmission or reception of voice, video, or data, notification that the primary logical channel for the Gateway has been opened, ensuring clear two-way communication. |
19. |
H.245 Open Audio Logical Channel Acknowledgement—Local H.323 endpoint to remote H.323 endpoint |
Local H.323 endpoint acknowledges readiness. |
20. |
Bi-Directional Audio with Transcoding Between Endpoint and Gateway |
Two-way communication ensues between the local H.323 endpoint and the CSN/PSTN Gateway. |
Table D-6 Log Listings
1. |
value RasMessage ::= registrationRequest :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
2. |
value RasMessage ::= registrationConfirm :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
3. |
value H323_UserInformation ::=
h323-message-body setup :
protocolIdentifier { 0 0 8 2250 0 2 }
h323-ID :{"Firstname Lastname"}
productId '4D6963726F736F6674AE204E65744D656574696E...'H
conferenceID '0C01EF01BD95D611AD4600A0CC5C89F1'H
conferenceGoal create :NULL
callType pointToPoint :NULL
sourceCallSignalAddress ipAddress :
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
mediaWaitForConnect FALSE
nonStandardIdentifier h221NonStandard :
data '0200000028000000000000001B00000081384274...'H
|
4. |
value ARQnonStandardInfo ::=
displayInformationElement "Firstname Lastname"
interfaceSpecificBillingId "FXS 1/1/1"
|
5. |
value RasMessage ::= admissionRequest :
callType pointToPoint :NULL
endpointIdentifier {"814EE09C0000001A"}
h323-ID :{"Firstname Lastname"}
srcCallSignalAddress ipAddress :
nonStandardIdentifier h221NonStandard :
data '8000000860132246697273746E616D65204C6173...'H
conferenceID '0C01EF01BD95D611AD4600A0CC5C89F1'H
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
|
6. |
value RasMessage ::= admissionConfirm :
destCallSignalAddress ipAddress :
|
7. |
value H323_UserInformation ::=
h323-message-body callProceeding :
protocolIdentifier { 0 0 8 2250 0 2 }
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
|
8. |
value H323_UU_NonStdInfo ::=
protoParam qsigNonStdInfo :
|
9. |
value H323_UserInformation ::=
h323-message-body progress :
protocolIdentifier { 0 0 8 2250 0 2 }
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
nonStandardIdentifier h221NonStandard :
data '60011000011E041E028188'H
|
10. |
value H323_UserInformation ::=
h323-message-body connect :
protocolIdentifier { 0 0 8 2250 0 2 }
conferenceID '0C01EF01BD95D611AD4600A0CC5C89F1'H
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
nonStandardIdentifier h221NonStandard :
data 'C00100028006000400000002'H
|
11. |
value RasMessage ::= infoRequestResponse :
endpointIdentifier {"814EE09C0000001A"}
nonStandardIdentifier h221NonStandard :
conferenceID '0C01EF01BD95D611AD4600A0CC5C89F1'H
callType pointToPoint :NULL
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
|
12. |
value H323_UU_NonStdInfo ::=
progIndParam progIndIEinfo :
|
13. |
value IRRperCallnonStandardInfo ::=
|
14. |
value MultimediaSystemControlMessage ::= request :terminalCapabilitySet :
protocolIdentifier { 0 0 8 245 0 3 }
multiplexCapability h2250Capability :
maximumAudioDelayJitter 20
receiveMultipointCapability
multicastCapability FALSE
multiUniCastConference FALSE
mediaDistributionCapability
transmitMultipointCapability
multicastCapability FALSE
multiUniCastConference FALSE
mediaDistributionCapability
receiveAndTransmitMultipointCapability
multicastCapability FALSE
multiUniCastConference FALSE
mediaDistributionCapability
centralizedConferenceMC FALSE
decentralizedConferenceMC FALSE
rtcpVideoControlCapability FALSE
mediaPacketizationCapability
h261aVideoPacketization FALSE
logicalChannelSwitchingCapability FALSE
t120DynamicPortCapability FALSE
|
|
capabilityTableEntryNumber 17
capability receiveAndTransmitDataApplicationCapability :
application nonStandard :
nonStandardIdentifier h221NonStandard :
data '52747044746D6652656C6179'H
capabilityTableEntryNumber 23
capability receiveUserInputCapability :hookflash :NULL
capabilityTableEntryNumber 22
capability receiveUserInputCapability :dtmf :NULL
capabilityTableEntryNumber 19
capability receiveUserInputCapability :basicString :NULL
capabilityTableEntryNumber 2
capability receiveAudioCapability :g711Alaw64k :20
capabilityDescriptorNumber 1
|
15. |
value MultimediaSystemControlMessage ::= request :masterSlaveDetermination :
statusDeterminationNumber 5917
|
16. |
value MultimediaSystemControlMessage ::= request :terminalCapabilitySet :
protocolIdentifier { 0 0 8 245 0 3 }
multiplexCapability h2250Capability :
maximumAudioDelayJitter 60
receiveMultipointCapability
multicastCapability FALSE
multiUniCastConference FALSE
mediaDistributionCapability
transmitMultipointCapability
multicastCapability FALSE
multiUniCastConference FALSE
mediaDistributionCapability
receiveAndTransmitMultipointCapability
multicastCapability FALSE
multiUniCastConference FALSE
mediaDistributionCapability
centralizedConferenceMC FALSE
decentralizedConferenceMC FALSE
rtcpVideoControlCapability FALSE
mediaPacketizationCapability
h261aVideoPacketization FALSE
|
|
capabilityTableEntryNumber 32768
nonStandardIdentifier h221NonStandard :
capabilityTableEntryNumber 15
capability receiveAndTransmitDataApplicationCapability :
application t120 :separateLANStack :NULL
capabilityTableEntryNumber 1
capability receiveAudioCapability :nonStandard :
nonStandardIdentifier h221NonStandard :
data '020000000000F4010000F4010100040000000000...'H
capabilityTableEntryNumber 2
capability receiveAudioCapability :g711Alaw64k :180
capabilityTableEntryNumber 3
capability receiveAudioCapability :g711Ulaw64k :180
capabilityTableEntryNumber 4
capability receiveAudioCapability :nonStandard :
nonStandardIdentifier h221NonStandard :
data '020000000000A0000000A0000400100000000000...'H
capabilityTableEntryNumber 5
capability receiveAudioCapability :nonStandard :
nonStandardIdentifier h221NonStandard :
data '020000000000A0000000A0000400100000000000...'H
capabilityTableEntryNumber 6
capability receiveAudioCapability :nonStandard :
nonStandardIdentifier h221NonStandard :
|
|
data '0200000000008000000080000500140000000000...'H
capabilityTableEntryNumber 7
capability receiveAudioCapability :nonStandard :
nonStandardIdentifier h221NonStandard :
data '0200000000008000000080000500140000000000...'H
capabilityTableEntryNumber 8
capability receiveAudioCapability :g7231 :
capabilityTableEntryNumber 10
capability receiveVideoCapability :h263VideoCapability :
temporalSpatialTradeOffCapability TRUE
capabilityTableEntryNumber 11
capability receiveVideoCapability :h263VideoCapability :
temporalSpatialTradeOffCapability TRUE
capabilityTableEntryNumber 12
capability receiveVideoCapability :h263VideoCapability :
temporalSpatialTradeOffCapability TRUE
capabilityTableEntryNumber 13
capability receiveVideoCapability :h261VideoCapability :
temporalSpatialTradeOffCapability TRUE
stillImageTransmission FALSE
|
|
capabilityTableEntryNumber 14
capability receiveVideoCapability :h261VideoCapability :
temporalSpatialTradeOffCapability TRUE
stillImageTransmission FALSE
capabilityDescriptorNumber 6
capabilityDescriptorNumber 7
capabilityDescriptorNumber 8
|
|
capabilityDescriptorNumber 9
capabilityDescriptorNumber 10
|
17. |
value MultimediaSystemControlMessage ::= response :terminalCapabilitySetAck :
|
18. |
value MultimediaSystemControlMessage ::= request :masterSlaveDetermination :
statusDeterminationNumber 7862592
|
19. |
value MultimediaSystemControlMessage ::= response :masterSlaveDeterminationAck :
|
20. |
value MultimediaSystemControlMessage ::= response :terminalCapabilitySetAck :
|
21. |
value MultimediaSystemControlMessage ::= response :masterSlaveDeterminationAck :
|
22. |
value MultimediaSystemControlMessage ::= request :openLogicalChannel :
forwardLogicalChannelNumber 1
forwardLogicalChannelParameters
dataType audioData :g711Alaw64k :20
multiplexParameters h2250LogicalChannelParameters :
mediaControlChannel unicastAddress :iPAddress :
|
23. |
value MultimediaSystemControlMessage ::= request :openLogicalChannel :
forwardLogicalChannelNumber 257
forwardLogicalChannelParameters
dataType audioData :g711Alaw64k :20
multiplexParameters h2250LogicalChannelParameters :
mediaGuaranteedDelivery FALSE
mediaControlChannel unicastAddress :iPAddress :
mediaControlGuaranteedDelivery FALSE
|
24. |
value MultimediaSystemControlMessage ::= response :openLogicalChannelAck :
forwardLogicalChannelNumber 257
forwardMultiplexAckParameters h2250LogicalChannelAckParameters :
mediaChannel unicastAddress :iPAddress :
mediaControlChannel unicastAddress :iPAddress :
|
25. |
value MultimediaSystemControlMessage ::= response :openLogicalChannelAck :
forwardLogicalChannelNumber 1
forwardMultiplexAckParameters h2250LogicalChannelAckParameters :
mediaChannel unicastAddress :iPAddress :
mediaControlChannel unicastAddress :iPAddress :
|
26. |
value RasMessage ::= registrationRequest :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
27. |
value RasMessage ::= registrationConfirm :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
endpointIdentifier {"814EE09C0000001A"}
|
28. |
value MultimediaSystemControlMessage ::= command :endSessionCommand :disconnect :NULL
|
29. |
value MultimediaSystemControlMessage ::= command :endSessionCommand :disconnect :NULL
|
30. |
value H323_UserInformation ::=
h323-message-body releaseComplete :
protocolIdentifier { 0 0 8 2250 0 2 }
reason undefinedReason :NULL
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
|
31. |
value RasMessage ::= disengageRequest :
endpointIdentifier {"814EE09C0000001A"}
conferenceID '0C01EF01BD95D611AD4600A0CC5C89F1'H
disengageReason normalDrop :NULL
guid '0B01EF01BD95D611AD4600A0CC5C89F1'H
|
32. |
value RasMessage ::= disengageConfirm :
|
33. |
value RasMessage ::= registrationRequest :
protocolIdentifier { 0 0 8 2250 0 2 }
gatekeeperIdentifier {"zonetwo"}
|