Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[ScreenOS] Understanding H.323 call flow and messages in the output of 'debug H.323.all'

0

0

Article ID: KB22410 KB Last Updated: 21 Jun 2012Version: 1.0
Summary:
This article provides information about the flow of the H.323 call and the different messages involved in the output of debug H.323 all.
Symptoms:
The setup in this article is a lab setup. IP addresses have been directly used to address the endpoints.

Network:

192.168.1.10 - 1.1 - (trust) - firewall-(untrust) - 10.10.10.1 - 10.10.10.2 - (untrust) - firewall -(trust)-192.168.2.1-192.168.2.15
Cause:

Solution:
  1. The 192.168.1.10 end point initiates the call and knows the called 192.168.1.10 end point. In a real-time scenario, the endpoints do not know the IP address, which is associated with the extensions numbers.

    Both the end points need to be registered with Gatekeeper Registration; this is performed to ask the gatekeeper for permission to place the call. It does so by sending the Admission Request message to the gatekeeper. The protocol used to communicate with the gatekeeper is H.225.0-RAS, which uses UDP as the underlying transport protocol.

    RAS packet received (192.168.1.10) -> (192.168.2.15).

    ## 2011-04-16 21:08:31 17:54:06 : GRQ - gatekeeperRequest
    ## 2011-04-16 21:08:31 17:54:06 : requestSeqNum
    ## 2011-04-16 21:08:31 17:54:06 : : 14
    ## 2011-04-16 21:08:31 17:54:06 : protocolIdentifier
    ## 2011-04-16 21:08:31 17:54:06 : : ObjectIdentifer (7)
    ## 2011-04-16 21:08:31 17:54:06 : nonStandardParameter
    ## 2011-04-16 21:08:31 17:54:06 : nonStandardIdentifier
    ## 2011-04-16 21:08:31 17:54:06 : objectIdentifier
    ## 2011-04-16 21:08:31 17:54:06 : : ObjectIdentifer (12)
    ## 2011-04-16 21:08:31 17:54:06 : Data: OctetString(4)
    ## 2011-04-16 21:08:31 17:54:06 : rasAddress
    ## 2011-04-16 21:08:31 17:54:06 : transportAddress
    ## 2011-04-16 21:08:31 17:54:06 : ipAddress - iP: 192.168.1.10 - port: 2081
    ## 2011-04-16 21:08:31 17:54:06 : endpointType
    ## 2011-04-16 21:08:31 17:54:06 : endpointType
    ## 2011-04-16 21:08:31 17:54:06 : terminalInfo
    ## 2011-04-16 21:08:31 17:54:06 : MC: FALSE
    ## 2011-04-16 21:08:31 17:54:06 : undefinedNode: FALSE

  2. When the 192.168.1.10 end point receives the permission from the gatekeeper, it will open a call signaling channel to the address provided by the gatekeeper in the ACF message. The call signaling messages are sent over TCP and the protocol is H.225.0 and it is embedded in Q.931.

    Q931 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:31 : Q931 - Setup (CRV:0x725d)

    ## 2011-04-16 21:08:31 : - (Bearer Capability 0x04)
    ## 2011-04-16 21:08:31 : - (Display 0x28)
    ## 2011-04-16 21:08:31 : - (User-User 0x7e)
    ## 2011-04-16 21:08:31 : userInformation
    ## 2011-04-16 21:08:31 : h323_UU_PDU
    ## 2011-04-16 21:08:31 : h323MessageBody
    ## 2011-04-16 21:08:31 : setup_UUIE
    ## 2011-04-16 21:08:31 : protocolIdentifier
    ## 2011-04-16 21:08:31 : : ObjectIdentifer (7)
    ## 2011-04-16 21:08:31 : sourceAddress
    ## 2011-04-16 21:08:31 : sequence_of_aliasAddress
    ## 2011-04-16 21:08:31 : Sequence of (1) items
    ## 2011-04-16 21:08:31 : aliasAddress
    ## 2011-04-16 21:08:31 : h323-ID: BMPString (28)
    ## 2011-04-16 21:08:31 : sourceInfo
    ## 2011-04-16 21:08:31 : endpointType
    ## 2011-04-16 21:08:31 : vendorIdentifier
    ## 2011-04-16 21:08:31 : h221NonStandard:
    ## 2011-04-16 21:08:31 : (5)
    ## 2011-04-16 21:08:31 : productId: OctetString (24)
    ## 2011-04-16 21:08:31 : versionId: OctetString (5)
    ## 2011-04-16 21:08:31 : terminalInfo
    ## 2011-04-16 21:08:31 : MC: FALSE
    ## 2011-04-16 21:08:31 : undefinedNode: FALSE
    ## 2011-04-16 21:08:31 : destCallSignalAddress
    ## 2011-04-16 21:08:31 : transportAddress
    ## 2011-04-16 21:08:31 : ipAddress - iP: 192.168.2.15 - port: 1720--dst-ip ip and port
    ## 2011-04-16 21:08:31 : activeMC: FALSE
    ## 2011-04-16 21:08:31 : conferenceID
    ## 2011-04-16 21:08:31 : globallyUniqueID: OctetString(17)
    ## 2011-04-16 21:08:31 : conferenceGoal
    ## 2011-04-16 21:08:31 : create: NULL
    ## 2011-04-16 21:08:31 : callType
    ## 2011-04-16 21:08:31 : pointToPoint: NULL
    ## 2011-04-16 21:08:31 : setup_UUIE_Extensions
    ## 2011-04-16 21:08:31 : sourceCallSignalAddress
    ## 2011-04-16 21:08:31 : transportAddress
    ## 2011-04-16 21:08:31 : ipAddress - iP: 192.168.1.10 - port: 2081
    ## 2011-04-16 21:08:31 : callIdentifier:
    ## 2011-04-16 21:08:31 : OctetString (17)
    ## 2011-04-16 21:08:31 : mediaWaitForConnect: FALSE
    ## 2011-04-16 21:08:31 : canOverlapSend: FALSE
    ## 2011-04-16 21:08:31 : nonStandardParameter
    ## 2011-04-16 21:08:31 : nonStandardIdentifier
    ## 2011-04-16 21:08:31 : h221NonStandard:
    ## 2011-04-16 21:08:31 : Data: OctetString(61)
    ## 2011-04-16 21:08:31 : setup: src 192.168.1.10/2081, dest 192.168.2.15/1720, h245 0.0.0.0/0
    ## 2011-04-16 21:08:31 : Q.931 dst IP changed 192.168.2.15:1720 to 192.168.2.15:1720
    ## 2011-04-16 21:08:31 : Q.931 src IP changed 192.168.1.10:2081 to 10.10.10.1:1285--translation performed by firewall
    ## 2011-04-16 21:08:31 :
    FS machine - S:FS_S_INIT E:FS_E_SETUP_NO_FS A:FS_A_NO_FAST_START
    ## 2011-04-16 21:08:31 : FS machine - state change: FS_S_INIT -->FS_S_DECLINED
    ## 2011-04-16 21:08:31 : FS machine - media action = MEDIA_NO_ACTION
    ## 2011-04-16 21:08:31 : H.323 HA: building sync cookie
    ## 2011-04-16 21:08:31 : H.323 HA: H323_HA_TYPE_Q931_FAST_START >fast start
    ## 2011-04-16 21:08:31 : H.323 HA active sync successful: context id 127 fast_start
    ## 2011-04-16 21:08:31 : H.323 HA active sync successful: context id 127 q931_tpkt
    Q931 packet received (192.168.1.10) -> (192.168.2.15).

    ## 2011-04-16 21:08:31 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:31 : H323 RSM (0) - Pak : 4, TPKT: 39 Data: 0
    ## 2011-04-16 21:08:31 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 39
    Q931 packet received (192.168.2.15) -> (10.10.10.1).
    ## 2011-04-16 21:08:31 : Data for this TPKT in next packet...
    ## 2011-04-16 21:08:31 : H.323 HA: building sync cookie
    ## 2011-04-16 21:08:31 : H.323 HA active sync successful: context id 127 q931_tpkt
    Q931 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:31 : H323 RSM (0) TPKT Cookie: 39
    ## 2011-04-16 21:08:31 : H323 RSM (0) - Pak : 39, Cookie TPKT: 39
    ## 2011-04-16 21:08:31 : H323 RSM (0) - Good: 39 is complete, no reassembly required (0)

  3. The 192.168.2.15 end point will first respond with the Q.931/H.225.0 message Call Proceeding to indicate that it has started on setting up the call.


  4. The called telephone (192.168.2.15) starts ringing and this is signaled to the other party with the Q.931/H.225.0 message Alerting.

    Q931 packet received (192.168.2.15) -> (10.10.10.1). >10.10.10.1 is the natted ip of 192.168.1.10
    ## 2011-04-16 21:08:31 : Q931 - Alerting (CRV:0x725d)

    ## 2011-04-16 21:08:31 : - (User-User 0x7e)
    ## 2011-04-16 21:08:31 : userInformation
    ## 2011-04-16 21:08:31 : h323_UU_PDU
    ## 2011-04-16 21:08:31 : h323MessageBody
    ## 2011-04-16 21:08:31 : alerting_UUIE
    ## 2011-04-16 21:08:31 : protocolIdentifier
    ## 2011-04-16 21:08:31 : : ObjectIdentifer (8)
    ## 2011-04-16 21:08:31 : destinationInfo
    ## 2011-04-16 21:08:31 : endpointType
    ## 2011-04-16 21:08:31 : terminalInfo
    ## 2011-04-16 21:08:31 : MC: FALSE
    ## 2011-04-16 21:08:31 : undefinedNode: FALSE
    ## 2011-04-16 21:08:31 : alerting_UUIE_Extensions
    ## 2011-04-16 21:08:31 : callIdentifier:
    ## 2011-04-16 21:08:31 : OctetString (17)
    ## 2011-04-16 21:08:31 : H.323 HA: building sync cookie
    ## 2011-04-16 21:08:31 : H.323 HA active sync successful: context id 127 q931_tpkt
    ## 2011-04-16 21:08:36 :
    Q931 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, TPKT: 116 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 116
    Q931 packet received (192.168.2.15) -> (10.10.10.1).
    ## 2011-04-16 21:08:36 : Data for this TPKT in next packet...
    ## 2011-04-16 21:08:36 : H.323 HA: building sync cookie
    ## 2011-04-16 21:08:36 : H.323 HA active sync successful: context id 127 q931_tpkt
    Q931 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 116
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 116, Cookie TPKT: 116
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Good: 116 is complete, no reassembly required (0)

  5. The called party picks up the handset and the endpoint can signal that the call has been accepted. This is performed by sending the Q.931/H.225.0 message Connect. At this point, the parties will need to negotiate parameters for audio (and optionally video) channels. The H.245 protocol is used for this negotiation.

    By default, H.245 will need another TCP channel, so the 192.168.2.15 end point will insert its H.245 address (the IP address and port, on which it listens for H.245 connections) in the Connect message.

    Q931 packet received (192.168.2.15) >(10.10.10.1). (192.168.1.15 is sending its capabilities)
    ## 2011-04-16 21:08:36: Q931 - Connect (CRV:0x725d)

    ## 2011-04-16 21:08:36 : - (Bearer Capability 0x04)
    ## 2011-04-16 21:08:36 : - (Display 0x28)
    ## 2011-04-16 21:08:36 : - (User-User 0x7e)
    ## 2011-04-16 21:08:36 : userInformation
    ## 2011-04-16 21:08:36 : h323_UU_PDU
    ## 2011-04-16 21:08:36 : h323MessageBody
    ## 2011-04-16 21:08:36 : connect_UUIE
    ## 2011-04-16 21:08:36 : protocolIdentifier
    ## 2011-04-16 21:08:36 : : ObjectIdentifer (8)
    ## 2011-04-16 21:08:36 : h245Address
    ## 2011-04-16 21:08:36 : transportAddress
    ## 2011-04-16 21:08:36 : ipAddress - iP: 192.168.2.15 - port: 1214
    ## 2011-04-16 21:08:36 : destinationInfo
    ## 2011-04-16 21:08:36 : endpointType
    ## 2011-04-16 21:08:36 : vendorIdentifier
    ## 2011-04-16 21:08:36 : h221NonStandard:
    ## 2011-04-16 21:08:36 : (5)
    ## 2011-04-16 21:08:36 : productId: OctetString (24)
    ## 2011-04-16 21:08:36 : versionId: OctetString (5)
    ## 2011-04-16 21:08:36 : terminalInfo
    ## 2011-04-16 21:08:36 : MC: FALSE
    ## 2011-04-16 21:08:36 : undefinedNode: FALSE
    ## 2011-04-16 21:08:36 : conferenceID
    ## 2011-04-16 21:08:36 : globallyUniqueID: OctetString(17)
    ## 2011-04-16 21:08:36 : connect_UUIE_Extensions
    ## 2011-04-16 21:08:36 : callIdentifier:
    ## 2011-04-16 21:08:36 : OctetString (17)
    ## 2011-04-16 21:08:36 : connect: src 0.0.0.0/0, dest 0.0.0.0/0, h245 192.168.2.15/1214
    ## 2011-04-16 21:08:36 : Q931 create gate > gates are opened
    ## 2011-04-16 21:08:36: 192.168.2.15 is the original ip address
    ## 2011-04-16 21:08:36 : seach from zone 1 to zone 2 > policy lookup from untrust to trust happens
    ## 2011-04-16 21:08:36 : Found policy 2
    ## 2011-04-16 21:08:36 : H323 RM Group: allocate a group for H323 (272) >allocating resources
    ## 2011-04-16 21:08:36 : h323_ifp_lookup: ifp=ethernet0/4, ifp2=bgroup0,sender_ip =192.168.1.10,recipient_ip=192.168.2.15
    ## 2011-04-16 21:08:36 : h245_rm_create_wide_open_gate: resource.ifp1 2, resource.ifp1 1, policy 1
    ## 2011-04-16 21:08:36 : H245 Gate : 0.0.0.0(0-0) to 192.168.2.15(1214-1214)
    ## 2011-04-16 21:08:36 : Xlated : 0.0.0.0(0) to 192.168.2.15(1214)
    ## 2011-04-16 21:08:36 : Q.931 H.245 IP changed 192.168.2.15:1214 to 192.168.2.15:1214 >for h245 negotiation gate is opened for port 1214FS machine - S:FS_S_DECLINED E:FS_E_CONNECT_NO_FS A:FS_A_INFO_REPORT
    ## 2011-04-16 21:08:36 : FS machine - event causes no action
    ## 2011-04-16 21:08:36 : FS machine - media action = MEDIA_NO_ACTION
    ## 2011-04-16 21:08:36 : H.323 HA: building sync cookie
    ## 2011-04-16 21:08:36 : H.323 HA: H323_HA_TYPE_GROUP
    ## 2011-04-16 21:08:36 : H.323 HA active sync successful: context id 127 rm group id
    ## 2011-04-16 21:08:36 : H.323 HA active sync successful: context id 127 q931_tpkt
    ## 2011-04-16 21:08:36 : h323_rm_notify_func: H.245 signaling gate - RM_HOLE_FIRST_HIT (272-1360)
    ## 2011-04-16 21:08:36 : h323_rm_h245_gate_check: H323 TCP packet received (192.168.1.10/2082) -> (192.168.2.15/1214).
    ## 2011-04-16 21:08:36 : policy=1, zone1=2, zone2=1
    ## 2011-04-16 21:08:36 : Allocate minor session!!!
    ## 2011-04-16 21:08:36 : H323 RSM (1) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Pak : 4, TPKT: 278 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (1) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 278
    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (1) TPKT Cookie: 278
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Pak : 289, Cookie TPKT: 278
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Pak : 289, Sec: 11, TPKT: 11
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Good: 289 is complete, no reassembly required (0)

  6. The calling end point opens a TCP channel to the H.245 address received in the Connect message and the gatekeeper will establish the second half of the H.245 signalling channel. The endpoints can start exchanging H.245 messages. The H.245 negotiation consists of the following three processes:


    • Deciding which endpoint is the master and which is the slave. This is more important for conferences with multiple participants, rather than a two-party call; however, it is still performed.

    • Exchanging information about the capability set of each party. The endpoints need to know the audio and video codecs that the other party supports.

    • Deciding about the actual parameters for the audio (and optionally video) channels; that is what codecs will be used and the IP addresses and ports for the RTP streams. This is known as the negotiation of logical channels.

  7. Finally, the two end points can start sending the RTP streams and the two people will hear one another. Each of the two directions can be encoded with a different codec.
    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session >> parent session
    ## 2011-04-16 21:08:36 : -> Request Message
    ## 2011-04-16 21:08:36 : terminalCapabilitiesSet - Not Implemented. Pass as is.
    ## 2011-04-16 21:08:36 : masterSlaveDetermination - Not Implemented. Pass as is.
    ## 2011-04-16 21:08:36 : H.245 Processing - no valid information has been set, skipping this item
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, TPKT: 153 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 153
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 153
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 164, Cookie TPKT: 153
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 164, Sec: 11, TPKT: 11
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Good: 164 is complete, no reassembly required (0)
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Request Message
    ## 2011-04-16 21:08:36 : terminalCapabilitiesSet - Not Implemented. Pass as is.
    ## 2011-04-16 21:08:36 : -> Request Message
    ## 2011-04-16 21:08:36 : masterSlaveDetermination - Not Implemented. Pass as is.
    ## 2011-04-16 21:08:36 : H.245 Processing - no valid information has been set, skipping this item
    ## 2011-04-16 21:08:36 : H.245 Processing - no valid information has been set, skipping this item
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, TPKT: 3 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 3
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 3
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 9, Cookie TPKT: 3
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 9, Sec: 6, TPKT: 6
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Good: 9 is complete, no reassembly required (0)
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Response Message
    ## 2011-04-16 21:08:36 : terminalCapabilitiesSetAck - Not Implemented. Pass as is.
    ## 2011-04-16 21:08:36 : -> Response Message
    ## 2011-04-16 21:08:36 : masterSlaveDeterminationAck - Not Implemented. Pass as is.
    ## 2011-04-16 21:08:36 : H.245 Processing - no valid information has been set, skipping this item

    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Request Message
    ## 2011-04-16 21:08:36 : openLogicalChannel
    ## 2011-04-16 21:08:36 : logicalChannelNumber
    ## 2011-04-16 21:08:36 : : 257
    ## 2011-04-16 21:08:36 : forwardLogicalChannelParameters
    ## 2011-04-16 21:08:36 : dataType
    ## 2011-04-16 21:08:36 : dataApplicationCapability
    ## 2011-04-16 21:08:36 : application
    ## 2011-04-16 21:08:36 : t120
    ## 2011-04-16 21:08:36 : separateLANStack
    ## 2011-04-16 21:08:36 : maxBitRate
    ## 2011-04-16 21:08:36 : : 0
    ## 2011-04-16 21:08:36 : multiplexParametersForward
    ## 2011-04-16 21:08:36 : h2250LogicalChannelParameters
    ## 2011-04-16 21:08:36 : Session Id: 0
    ## 2011-04-16 21:08:36 : Forward call
    ## 2011-04-16 21:08:36 : reverseLogicalChannelParameters
    ## 2011-04-16 21:08:36 : dataType
    ## 2011-04-16 21:08:36 : dataApplicationCapability
    ## 2011-04-16 21:08:36 : application
    ## 2011-04-16 21:08:36 : t120
    ## 2011-04-16 21:08:36 : separateLANStack
    ## 2011-04-16 21:08:36 : maxBitRate
    ## 2011-04-16 21:08:36 : : 0
    ## 2011-04-16 21:08:36 : multiplexParametersReverse
    ## 2011-04-16 21:08:36 : h2250LogicalChannelParameters
    ## 2011-04-16 21:08:36 : Session Id: 0
    ## 2011-04-16 21:08:36 : 2-Way call
    ## 2011-04-16 21:08:36 : H.245 Request - Processing (item: 1 of 1)
    ## 2011-04-16 21:08:36 : OLC: type=1 num=257 ifp=bgroup0 addr=0.0.0.0(0/0)
    ## 2011-04-16 21:08:36 : OLC: No IPs to translate
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, TPKT: 40 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 40
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 40
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 40, Cookie TPKT: 40
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Good: 40 is complete, no reassembly required (0)
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Request Message
    ## 2011-04-16 21:08:36 : openLogicalChannel
    ## 2011-04-16 21:08:36 : logicalChannelNumber
    ## 2011-04-16 21:08:36 : : 257
    ## 2011-04-16 21:08:36 : forwardLogicalChannelParameters
    ## 2011-04-16 21:08:36 : dataType
    ## 2011-04-16 21:08:36 : dataApplicationCapability
    ## 2011-04-16 21:08:36 : application
    ## 2011-04-16 21:08:36 : t120
    ## 2011-04-16 21:08:36 : separateLANStack
    ## 2011-04-16 21:08:36 : maxBitRate
    ## 2011-04-16 21:08:36 : : 0
    ## 2011-04-16 21:08:36 : multiplexParametersForward
    ## 2011-04-16 21:08:36 : h2250LogicalChannelParameters
    ## 2011-04-16 21:08:36 : Session Id: 0
    ## 2011-04-16 21:08:36 : Forward call
    ## 2011-04-16 21:08:36 : reverseLogicalChannelParameters
    ## 2011-04-16 21:08:36 : dataType
    ## 2011-04-16 21:08:36 : dataApplicationCapability
    ## 2011-04-16 21:08:36 : application
    ## 2011-04-16 21:08:36 : t120
    ## 2011-04-16 21:08:36 : separateLANStack
    ## 2011-04-16 21:08:36 : maxBitRate
    ## 2011-04-16 21:08:36 : : 0
    ## 2011-04-16 21:08:36 : multiplexParametersReverse
    ## 2011-04-16 21:08:36 : h2250LogicalChannelParameters
    ## 2011-04-16 21:08:36 : Session Id: 0
    ## 2011-04-16 21:08:36 : 2-Way call
    ## 2011-04-16 21:08:36 : separateStack
    ## 2011-04-16 21:08:36 : networkAccessParameters
    ## 2011-04-16 21:08:36 : distribution
    ## 2011-04-16 21:08:36 : unicast
    ## 2011-04-16 21:08:36 : networkAddress
    ## 2011-04-16 21:08:36 : transportAddress
    ## 2011-04-16 21:08:36 : unicastAddress
    ## 2011-04-16 21:08:36 : iPAddress
    ## 2011-04-16 21:08:36 : iP: 192.168.2.15 - port: 1503 > media ip and media port
    ## 2011-04-16 21:08:36 : associatedConference: FALSE
    ## 2011-04-16 21:08:36 : H.245 Request - Processing (item: 1 of 1)
    ## 2011-04-16 21:08:36 : OLC: type=1 num=257 ifp=ethernet0/4 addr=192.168.2.15(1502/1503) > (same media ip for rtp and rtsp)
    ## 2011-04-16 21:08:36 : same RTP & RTCP ip 192.168.2.15
    ## 2011-04-16 21:08:36 : OLC: 192.168.2.15 is the original ip address
    ## 2011-04-16 21:08:36 : OLC: found route for 192.168.2.15
    ## 2011-04-16 21:08:36 : OLC seach from zone 1 ip= 192.168.2.15 to zone 2 ip= 192.168.1.10
    ## 2011-04-16 21:08:36 : keep ip 192.168.2.15(1502, 1503)

    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, TPKT: 5 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 5
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 5
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 5, Cookie TPKT: 5
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Good: 5 is complete, no reassembly required (0)
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Response Message
    ## 2011-04-16 21:08:36 : openLogicalChannelReject
    ## 2011-04-16 21:08:36 : logicalChannelNumber
    ## 2011-04-16 21:08:36 : : 257
    ## 2011-04-16 21:08:36 : rejectCause
    ## 2011-04-16 21:08:36 : : unspecified
    ## 2011-04-16 21:08:36 : H.245 Processing - no valid information has been set, skipping this item
    ## 2011-04-16 21:08:36 : H323 RSM (1) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Pak : 4, TPKT: 11 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (1) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 11
    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (1) TPKT Cookie: 11
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Pak : 11, Cookie TPKT: 11
    ## 2011-04-16 21:08:36 : H323 RSM (1) - Good: 11 is complete, no reassembly required (0)
    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Response Message
    ## 2011-04-16 21:08:36 : openLogicalChannelAck
    ## 2011-04-16 21:08:36 : logicalChannelNumber
    ## 2011-04-16 21:08:36 : : 257
    ## 2011-04-16 21:08:36 : reverseLogicalChannelAckParameters
    ## 2011-04-16 21:08:36 : reverselogicalChannelNumber
    ## 2011-04-16 21:08:36 : logicalChannelNumber
    ## 2011-04-16 21:08:36 : : 258
    ## 2011-04-16 21:08:36 : forwardMultiplexAckParametersRes
    ## 2011-04-16 21:08:36 : h2250LogicalChannelAckParameters
    ## 2011-04-16 21:08:36 : H.245 Response - Processing (item: 1 of 1)
    ## 2011-04-16 21:08:36 : OLC-ACK: type=0 num=257 ifp=bgroup0 addr=0.0.0.0(0/0)
    ## 2011-04-16 21:08:36 : OLC-ACK: No IP to translate
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, TPKT: 4 Data: 0
    ## 2011-04-16 21:08:36 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 4
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : H323 RSM (0) TPKT Cookie: 4
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Pak : 4, Cookie TPKT: 4
    ## 2011-04-16 21:08:36 : H323 RSM (0) - Good: 4 is complete, no reassembly required (0)
    H245 packet received (192.168.2.15) -> (192.168.1.10).
    ## 2011-04-16 21:08:36 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:36 : -> Indication Message
    ## 2011-04-16 21:08:36 : openLogicalChannelConfirm
    ## 2011-04-16 21:08:36 : logicalChannelNumber
    ## 2011-04-16 21:08:36 : : 257
    ## 2011-04-16 21:08:36 : H.245 Processing - no valid information has been set, skipping this item
    ## 2011-04-16 21:08:57 : H323 RSM (1) TPKT Cookie: 0
    ## 2011-04-16 21:08:57 : H323 RSM (1) - Pak : 4, TPKT: 2 Data: 0
    ## 2011-04-16 21:08:57 : H323 RSM (1) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 2
    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:57 : h225 session refreshed id =16053 as parent session
    ## 2011-04-16 21:08:57 : H323 RSM (1) TPKT Cookie: 2
    ## 2011-04-16 21:08:57 : H323 RSM (1) - Pak : 2, Cookie TPKT: 2
    ## 2011-04-16 21:08:57 : H323 RSM (1) - Good: 2 is complete, no reassembly required (0)
    H245 packet received (192.168.1.10) -> (192.168.2.15).
    ## 2011-04-16 21:08:57 : h225 session refreshed id =16053 as parent session


Now take a look at what happens when the call is over:

  • The two end points stop sending the RTP streams. They announce the closing of logical channels (H.245 RequestCloseLogicalChannel).

  • The H.245 signalling channel is closed (The H.245 EndSessionCommand command message, followed by closing of the TCP connection).

  • The main signalling connection is also closed; the end points exchange the Q.931/H.225.0 ReleaseComplete messages and the TCP connection is closed.

  • Each of the two end points informs the gatekeeper about the completed call, with the H.225.0-RAS message Disengage Request (DRQ) and the gatekeeper confirms with Disengage Confirm (DCF).

Refer to the following debug logs (Make sure that you correctly understand the setup and configuration, prior to debugging):
## 2011-04-16 21:08:57 : -> Command Message
## 2011-04-16 21:08:57 : endSessionCommand
## 2011-04-16 21:08:57 : disconnect

## 2011-04-16 21:08:57 : H.245 Command - Processing (item: 1 of 1)
## 2011-04-16 21:08:57 : end session (from itf 9)
Q931 packet received (192.168.2.15) -> (10.10.10.1).
## 2011-04-16 21:08:57 : H323 RSM (1) TPKT Cookie: 0
## 2011-04-16 21:08:57 : H323 RSM (1) - Pak : 4, TPKT: 43 Data: 0
## 2011-04-16 21:08:57 : H323 RSM (1) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 43
Q931 packet received (192.168.1.10) -> (192.168.2.15).
## 2011-04-16 21:08:57 : Data for this TPKT in next packet...
## 2011-04-16 21:08:57 : H.323 HA: building sync cookie
## 2011-04-16 21:08:57 : H.323 HA active sync successful: context id 127 q931_tpkt
## 2011-04-16 21:08:57 : H323 RSM (1) TPKT Cookie: 43
## 2011-04-16 21:08:57 : H323 RSM (1) - Pak : 43, Cookie TPKT: 43
## 2011-04-16 21:08:57 : H323 RSM (1) - Good: 43 is complete, no reassembly required (0)
Q931 packet received (192.168.1.10) -> (192.168.2.15).
## 2011-04-16 21:08:57 : Q931 - Release Complete (CRV:0x725d)
## 2011-04-16 21:08:57 : h323_rm_free_rsg: group_idx=272
## 2011-04-16 21:08:57 : H.323 HA: building sync cookie
## 2011-04-16 21:08:57 : H.323 HA: H323_HA_TYPE_GROUP
## 2011-04-16 21:08:57 : H.323 HA active sync successful: context id 127 rm group id
## 2011-04-16 21:08:57 : H.323 HA active sync successful: context id 127 q931_tpkt
Q931 packet received (192.168.2.15) -> (10.10.10.1).
## 2011-04-16 21:08:57 : H323 RSM (0) TPKT Cookie: 0
## 2011-04-16 21:08:57 : H323 RSM (0) - Pak : 4, TPKT: 2 Data: 0
## 2011-04-16 21:08:57 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 2
H245 packet received (192.168.2.15) -> (192.168.1.10).
## 2011-04-16 21:08:57 : h225 session refreshed id =16053 as parent session
## 2011-04-16 21:08:57 : H323 RSM (0) TPKT Cookie: 2
## 2011-04-16 21:08:57 : H323 RSM (0) - Pak : 2, Cookie TPKT: 2
## 2011-04-16 21:08:57 : H323 RSM (0) - Good: 2 is complete, no reassembly required (0)
H245 packet received (192.168.2.15) -> (192.168.1.10).
## 2011-04-16 21:08:57 : h225 session refreshed id =16053 as parent session
## 2011-04-16 21:08:57 : -> Command Message
## 2011-04-16 21:08:57 : endSessionCommand
## 2011-04-16 21:08:57 : disconnect

## 2011-04-16 21:08:57 : H.245 Command - Processing (item: 1 of 1)
## 2011-04-16 21:08:57 : end session (from itf 8)
Q931 packet received (192.168.1.10) -> (192.168.2.15).
## 2011-04-16 21:08:57 : H323 RSM (0) TPKT Cookie: 0
## 2011-04-16 21:08:57 : H323 RSM (0) - Pak : 4, TPKT: 43 Data: 0
## 2011-04-16 21:08:57 : H323 RSM (0) - TPKT-Only Pak: 4 (sent: 4 kept: 0) TPKT Cookie: 43
Q931 packet received (192.168.2.15) -> (10.10.10.1).
## 2011-04-16 21:08:57 : Data for this TPKT in next packet...
## 2011-04-16 21:08:57 : H.323 HA: building sync cookie
## 2011-04-16 21:08:57 : H.323 HA active sync successful: context id 127 q931_tpkt
Q931 packet received (192.168.1.10) -> (192.168.2.15).
## 2011-04-16 21:08:57 : H323 RSM (0) TPKT Cookie: 43
## 2011-04-16 21:08:57 : H323 RSM (0) - Pak : 43, Cookie TPKT: 43
## 2011-04-16 21:08:57 : H323 RSM (0) - Good: 43 is complete, no reassembly required (0)
Q931 packet received (192.168.2.15) -> (10.10.10.1).
## 2011-04-16 21:08:57 : Q931 - Release Complete (CRV:0x725d)

## 2011-04-16 21:08:57 : h323_rm_free_rsg: group_idx=0
## 2011-04-16 21:08:57 : H.323 HA: building sync cookie
## 2011-04-16 21:08:57 : H.323 HA active sync successful: context id 127 q931_tpkt
Q931 packet received (192.168.2.15) -> (10.10.10.1).
## 2011-04-16 21:08:58 : session age out event: id 16053
## 2011-04-16 21:08:58 : h225 session let go id =16053
## 2011-04-16 21:09:00 : session age out event: id 16053
## 2011-04-16 21:09:00 : h225 session let go id =16053
## 2011-04-16 21:09:00 : Free Q.931 cookie

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search