Normal incoming call, TRACE OFF

The following example illustrates a normal incoming call with TRACE OFF:
EZB2301I VC F001XU038    incoming call from 00000039 user data CC
EZB2325I VC F001XU038    facilities: pkt1024.
EZB2320I VC F001XU038    NPSI logon LU VL038001
EZB2330I VC F001XU038    call complete
    ...some time later...
EZB2350I VC F001XU038    call cleared, cause=00 diagnostic=C5
EZB2351I VC F001XU038    connection terminated for 00000039: sent 1 received 
1 dropped 0
EZB2352I VC 010 closed
Notes:
  1. The VC identifier F001XU038 ties together the events associated with a single virtual circuit. Messages for one VC are intermixed with messages for other VCs.
  2. The X.25 address originating the call (00000039) is reported in the EZB2301I message.
  3. X.25 calls can optionally request facilities to be applied, such as window size, packet size, throughput class, and reverse charging. These are reported in the EZB2325I message.
  4. EZB2330I call complete indicates the virtual circuit is ready for transferring TCP/IP data.
  5. An X.25 call can be closed by the originator, the acceptor, or the X.25 network. The cause and diagnostic codes in the EZB2350I message indicate the reason. In the example, cause=00 indicates the originator has closed the connection. Lists of cause and diagnostic codes can be found in X.25 NPSI Diagnosis, Customization, and Tuning.
  6. EZB2351I reports the number of IP datagrams transferred on the virtual circuit.
  7. After the EZB2352I closed message is issued, the virtual circuit is ready for reuse by another incoming call or to originate a new call.