GXW4501 SIP to PRI call handoff long delay, 20 seconds


#1

We are using the GXW4501 gateway for connection to our Mitel connect phone system and we are getting a delay in call handoff on dial-in from VoIP to PRI only on sites using the GXW4501. We’ve adjusted everything from timing master to weird settings and cannot get rid of the delay. I’m including a PRI log for one call, it looks like a couple timeouts process before the call is handed off. Calls out have no delay

The logs show the 20 seconds, appreciate any suggestions

2022-10-26, 14:51:20:963:388 – Making new call for cref 32769
2022-10-26, 14:51:20:963:458 Adding facility ie contents to send in SETUP message:
2022-10-26, 14:51:20:963:472 ASN.1 dump
2022-10-26, 14:51:20:963:491 Context Specific [11 0x0B] <8B> Len:1 <01>
2022-10-26, 14:51:20:963:505 <00> - “~”
2022-10-26, 14:51:20:963:517 Context Specific/C [1 0x01] Len:19 <13>
2022-10-26, 14:51:20:963:530 Integer(2 0x02) <02> Len:1 <01>
2022-10-26, 14:51:20:963:542 <01> - “~”
2022-10-26, 14:51:20:963:554 Integer(2 0x02) <02> Len:1 <01>
2022-10-26, 14:51:20:963:566 <00> - “~”
2022-10-26, 14:51:20:963:578 Context Specific [0 0x00] <80> Len:11 <0B>
2022-10-26, 14:51:20:963:592 <55 6E 61 76 61 69 6C 61-62 6C 65> - “Unavailable”
2022-10-26, 14:51:20:963:603 ASN.1 end
2022-10-26, 14:51:20:963:616 interpretation Context Specific [11 0x0B] = 0 0x0000
2022-10-26, 14:51:20:963:628 INVOKE Component Context Specific/C [1 0x01]
2022-10-26, 14:51:20:963:657 invokeId Integer(2 0x02) = 1 0x0001
2022-10-26, 14:51:20:963:669 operationValue Integer(2 0x02) = 0 0x0000
2022-10-26, 14:51:20:963:681 operationValue = ROSE_QSIG_CallingName
2022-10-26, 14:51:20:963:692 callingName Name
2022-10-26, 14:51:20:963:704 namePresentationAllowedSimple Context Specific [0 0x00] =
2022-10-26, 14:51:20:963:720 <55 6E 61 76 61 69 6C 61-62 6C 65> - “Unavailable”
2022-10-26, 14:51:20:963:735
2022-10-26, 14:51:20:963:746 > DL-DATA request
2022-10-26, 14:51:20:963:757 > Protocol Discriminator: Q.931 (8) len=87
2022-10-26, 14:51:20:963:769 > TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent from originator)
2022-10-26, 14:51:20:963:780 > Message Type: SETUP (5)
2022-10-26, 14:51:20:963:793 TEI=0 Transmitting N(S)=0, window is open V(A)=0 K=7
2022-10-26, 14:51:20:963:804
2022-10-26, 14:51:20:963:815 > TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:20:963:826 > V(A)=0, V(S)=0, V®=0
2022-10-26, 14:51:20:963:836 > K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:20:963:847 > T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:20:963:875 > [ 00 01 00 00 08 02 00 01 05 04 03 80 90 a2 18 03 a9 83 81 1c 19 9f 8b 01 00 a1 13 02 01 01 02 01 00 80 0b 55 6e 61 76 61 69 6c 61 62 6c 65 1e 02 80 83 28 0c b1 55 6e 61 76 61 69 6c 61 62 6c 65 6c 0c 00 80 38 31 33 33 39 39 30 38 31 30 70 0b 80 33 32 31 37 32 35 33 34 30 30 ]
2022-10-26, 14:51:20:963:947 > Informational frame:
2022-10-26, 14:51:20:964:052 > SAPI: 00 C/R: 0 EA: 0
2022-10-26, 14:51:20:964:067 > TEI: 000 EA: 1
2022-10-26, 14:51:20:964:078 > N(S): 000 0: 0
2022-10-26, 14:51:20:964:089 > N®: 000 P: 0
2022-10-26, 14:51:20:964:099 > 87 bytes of data
2022-10-26, 14:51:20:964:124 > Protocol Discriminator: Q.931 (8) len=87
2022-10-26, 14:51:20:964:136 > TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent from originator)
2022-10-26, 14:51:20:964:147 > Message Type: SETUP (5)
2022-10-26, 14:51:20:964:159 > [04 03 80 90 a2]
2022-10-26, 14:51:20:964:172 > Bearer Capability (len= 5) [ Ext: 1 Coding-Std: 0 Info transfer capability: Speech (0)
2022-10-26, 14:51:20:964:183 > Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16)
2022-10-26, 14:51:20:964:194 > User information layer 1: u-Law (34)
2022-10-26, 14:51:20:964:206 > [18 03 a9 83 81]
2022-10-26, 14:51:20:964:259 > Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI) Spare: 0 Exclusive Dchan: 0
2022-10-26, 14:51:20:964:271 > ChanSel: As indicated in following octets
2022-10-26, 14:51:20:964:282 > Ext: 1 Coding: 0 Number Specified Channel Type: 3
2022-10-26, 14:51:20:964:294 > Ext: 1 Channel: 1 Type: CPE]
2022-10-26, 14:51:20:964:311 > [1c 19 9f 8b 01 00 a1 13 02 01 01 02 01 00 80 0b 55 6e 61 76 61 69 6c 61 62 6c 65]
2022-10-26, 14:51:20:964:324 > Facility (len=27, codeset=0) [ 0x9F, 0x8B, 0x01, 0x00, 0xA1, 0x13, 0x02, 0x01, 0x01, 0x02, 0x01, 0x00, 0x80, 0x0B, ‘Unavailable’ ]
2022-10-26, 14:51:20:964:336 > [1e 02 80 83]
2022-10-26, 14:51:20:964:349 > Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: User (0)
2022-10-26, 14:51:20:964:360 > Ext: 1 Progress Description: Calling equipment is non-ISDN. (3) ]
2022-10-26, 14:51:20:964:392 > [28 0c b1 55 6e 61 76 61 69 6c 61 62 6c 65]
2022-10-26, 14:51:20:964:406 > Display (len=12) Charset: 31 [ Unavailable ]
2022-10-26, 14:51:20:964:420 > [6c 0c 00 80 38 31 33 33 39 39 30 38 31 30]
2022-10-26, 14:51:20:964:432 > Calling Party Number (len=14) [ Ext: 0 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0)
2022-10-26, 14:51:20:964:444 > Presentation: Presentation allowed, User-provided, not screened (0) ‘8133990810’ ]
2022-10-26, 14:51:20:964:458 > [70 0b 80 33 32 31 37 32 35 33 34 30 30]
2022-10-26, 14:51:20:964:472 > Called Party Number (len=13) [ Ext: 1 TON: Unknown Number Type (0) NPI: Unknown Number Plan (0) ‘3217253400’ ]
2022-10-26, 14:51:20:964:483 – Stopping T203 timer
2022-10-26, 14:51:20:964:494 – Starting T200 timer
2022-10-26, 14:51:20:964:507 q931.c:6401 q931_setup: Call 32769 enters state 1 (Call Initiated). Hold state: Idle
2022-10-26, 14:51:20:964:518 pri_setup…
2022-10-26, 14:51:20:990:768 Receive the q921 packet ‘6’ bytes!
2022-10-26, 14:51:20:990:810
2022-10-26, 14:51:20:990:823 < TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:20:990:834 < V(A)=0, V(S)=1, V®=0
2022-10-26, 14:51:20:990:845 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:20:990:855 < T200_id=8192, N200=3, T203_id=0
2022-10-26, 14:51:20:990:871 < [ 00 01 01 02 ]
2022-10-26, 14:51:20:990:892 < Supervisory frame:
2022-10-26, 14:51:20:990:906 < SAPI: 00 C/R: 0 EA: 0
2022-10-26, 14:51:20:990:917 < TEI: 000 EA: 1
2022-10-26, 14:51:20:990:929 < Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:20:990:940 < N®: 001 P/F: 0
2022-10-26, 14:51:20:990:950 < 0 bytes of data
2022-10-26, 14:51:20:990:964 – Got ACK for N(S)=0 to (but not including) N(S)=1
2022-10-26, 14:51:20:990:976 – ACKing N(S)=0, tx_queue head is N(S)=-1 (-1 is empty, -2 is not transmitted)
2022-10-26, 14:51:20:991:033 – Stopping T200 timer
2022-10-26, 14:51:20:991:045 – Starting T203 timer
2022-10-26, 14:51:20:991:059 Done handling message for SAPI/TEI=0/0
2022-10-26, 14:51:20:993:629 Receive the q921 packet ‘16’ bytes!
2022-10-26, 14:51:20:993:643
2022-10-26, 14:51:20:993:654 < TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:20:993:665 < V(A)=1, V(S)=1, V®=0
2022-10-26, 14:51:20:993:676 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:20:993:686 < T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:20:993:702 < [ 02 01 00 02 08 02 80 01 02 18 03 a9 83 81 ]
2022-10-26, 14:51:20:993:713 < Informational frame:
2022-10-26, 14:51:20:993:724 < SAPI: 00 C/R: 1 EA: 0
2022-10-26, 14:51:20:993:734 < TEI: 000 EA: 1
2022-10-26, 14:51:20:993:745 < N(S): 000 0: 0
2022-10-26, 14:51:20:993:755 < N®: 001 P: 0
2022-10-26, 14:51:20:993:766 < 10 bytes of data
2022-10-26, 14:51:20:993:780 < Protocol Discriminator: Q.931 (8) len=10
2022-10-26, 14:51:20:993:792 < TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent to originator)
2022-10-26, 14:51:20:993:804 < Message Type: CALL PROCEEDING (2)
2022-10-26, 14:51:20:993:816 < [18 03 a9 83 81]
2022-10-26, 14:51:20:993:829 < Channel ID (len= 5) [ Ext: 1 IntID: Implicit Other(PRI) Spare: 0 Exclusive Dchan: 0
2022-10-26, 14:51:20:993:841 < ChanSel: As indicated in following octets
2022-10-26, 14:51:20:993:852 < Ext: 1 Coding: 0 Number Specified Channel Type: 3
2022-10-26, 14:51:20:993:863 < Ext: 1 Channel: 1 Type: CPE]
2022-10-26, 14:51:20:993:874 – Got ACK for N(S)=1 to (but not including) N(S)=1
2022-10-26, 14:51:20:993:890 – T200 requested to stop when not started
2022-10-26, 14:51:20:993:901 T203 requested to start without stopping first
2022-10-26, 14:51:20:993:912 – Starting T203 timer
2022-10-26, 14:51:20:993:925 Received message for call 0x7f755001a520 on link 0x7f75245c1ce0 TEI/SAPI 0/0
2022-10-26, 14:51:20:993:944 – Processing IE 24 (cs0, Channel ID)
2022-10-26, 14:51:20:993:960 q931.c:8939 post_handle_q931_message: Call 32769 enters state 3 (Outgoing Call Proceeding). Hold state: Idle
2022-10-26, 14:51:20:993:971 – start pri_outgoing_call_proceeding_timer --.
2022-10-26, 14:51:20:993:982
2022-10-26, 14:51:20:993:993 > TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:20:994:003 > V(A)=1, V(S)=1, V®=1
2022-10-26, 14:51:20:994:014 > K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:20:994:025 > T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:20:994:037 > [ 02 01 01 02 ]
2022-10-26, 14:51:20:994:047 > Supervisory frame:
2022-10-26, 14:51:20:994:058 > SAPI: 00 C/R: 1 EA: 0
2022-10-26, 14:51:20:994:069 > TEI: 000 EA: 1
2022-10-26, 14:51:20:994:079 > Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:20:994:090 > N®: 001 P/F: 0
2022-10-26, 14:51:20:994:100 > 0 bytes of data
2022-10-26, 14:51:20:994:119 Done handling message for SAPI/TEI=0/0
2022-10-26, 14:51:21:321:793 Receive the q921 packet ‘11’ bytes!
2022-10-26, 14:51:21:321:835
2022-10-26, 14:51:21:321:848 < TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:21:321:859 < V(A)=1, V(S)=1, V®=1
2022-10-26, 14:51:21:321:870 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:21:321:887 < T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:21:321:903 < [ 02 01 02 02 08 02 80 01 01 ]
2022-10-26, 14:51:21:321:913 < Informational frame:
2022-10-26, 14:51:21:321:924 < SAPI: 00 C/R: 1 EA: 0
2022-10-26, 14:51:21:321:935 < TEI: 000 EA: 1
2022-10-26, 14:51:21:321:946 < N(S): 001 0: 0
2022-10-26, 14:51:21:321:956 < N®: 001 P: 0
2022-10-26, 14:51:21:321:966 < 5 bytes of data
2022-10-26, 14:51:21:321:979 < Protocol Discriminator: Q.931 (8) len=5
2022-10-26, 14:51:21:321:991 < TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent to originator)
2022-10-26, 14:51:21:322:003 < Message Type: ALERTING (1)
2022-10-26, 14:51:21:322:060 – Got ACK for N(S)=1 to (but not including) N(S)=1
2022-10-26, 14:51:21:322:072 – T200 requested to stop when not started
2022-10-26, 14:51:21:322:083 T203 requested to start without stopping first
2022-10-26, 14:51:21:322:094 – Starting T203 timer
2022-10-26, 14:51:21:322:108 Received message for call 0x7f755001a520 on link 0x7f75245c1ce0 TEI/SAPI 0/0
2022-10-26, 14:51:21:322:124 q931.c:8790 post_handle_q931_message: Call 32769 enters state 4 (Call Delivered). Hold state: Idle
2022-10-26, 14:51:21:322:136
2022-10-26, 14:51:21:322:147 > TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:21:322:158 > V(A)=1, V(S)=1, V®=2
2022-10-26, 14:51:21:322:168 > K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:21:322:179 > T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:21:322:193 > [ 02 01 01 04 ]
2022-10-26, 14:51:21:322:203 > Supervisory frame:
2022-10-26, 14:51:21:322:214 > SAPI: 00 C/R: 1 EA: 0
2022-10-26, 14:51:21:322:224 > TEI: 000 EA: 1
2022-10-26, 14:51:21:322:235 > Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:21:322:246 > N®: 002 P/F: 0
2022-10-26, 14:51:21:322:256 > 0 bytes of data
2022-10-26, 14:51:21:322:274 Done handling message for SAPI/TEI=0/0
2022-10-26, 14:51:31:330:865 t203_expire
2022-10-26, 14:51:31:330:920
2022-10-26, 14:51:31:330:935 > TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:31:330:947 > V(A)=1, V(S)=1, V®=2
2022-10-26, 14:51:31:330:958 > K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:31:330:968 > T200_id=0, N200=3, T203_id=0
2022-10-26, 14:51:31:330:982 > [ 00 01 01 05 ]
2022-10-26, 14:51:31:330:993 > Supervisory frame:
2022-10-26, 14:51:31:331:004 > SAPI: 00 C/R: 0 EA: 0
2022-10-26, 14:51:31:331:015 > TEI: 000 EA: 1
2022-10-26, 14:51:31:331:026 > Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:31:331:037 > N®: 002 P/F: 1
2022-10-26, 14:51:31:331:047 > 0 bytes of data
2022-10-26, 14:51:31:331:066 – Starting T200 timer
2022-10-26, 14:51:31:340:912 Receive the q921 packet ‘6’ bytes!
2022-10-26, 14:51:31:340:928
2022-10-26, 14:51:31:340:939 < TEI: 0 State 8(Timer recovery)
2022-10-26, 14:51:31:340:950 < V(A)=1, V(S)=1, V®=2
2022-10-26, 14:51:31:340:961 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:31:340:971 < T200_id=8192, N200=3, T203_id=0
2022-10-26, 14:51:31:340:983 < [ 00 01 01 03 ]
2022-10-26, 14:51:31:340:994 < Supervisory frame:
2022-10-26, 14:51:31:341:005 < SAPI: 00 C/R: 0 EA: 0
2022-10-26, 14:51:31:341:016 < TEI: 000 EA: 1
2022-10-26, 14:51:31:341:027 < Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:31:341:038 < N®: 001 P/F: 1
2022-10-26, 14:51:31:341:049 < 0 bytes of data
2022-10-26, 14:51:31:341:061 – Got ACK for N(S)=1 to (but not including) N(S)=1
2022-10-26, 14:51:31:341:072 – Stopping T200 timer
2022-10-26, 14:51:31:341:083 – Starting T203 timer
2022-10-26, 14:51:31:341:096 Done handling message for SAPI/TEI=0/0
2022-10-26, 14:51:39:639:385 Receive the q921 packet ‘11’ bytes!
2022-10-26, 14:51:39:639:433
2022-10-26, 14:51:39:639:446 < TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:39:639:457 < V(A)=1, V(S)=1, V®=2
2022-10-26, 14:51:39:639:468 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:39:639:478 < T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:39:639:494 < [ 02 01 04 02 08 02 80 01 07 ]
2022-10-26, 14:51:39:639:504 < Informational frame:
2022-10-26, 14:51:39:639:515 < SAPI: 00 C/R: 1 EA: 0
2022-10-26, 14:51:39:639:526 < TEI: 000 EA: 1
2022-10-26, 14:51:39:639:536 < N(S): 002 0: 0
2022-10-26, 14:51:39:639:547 < N®: 001 P: 0
2022-10-26, 14:51:39:639:557 < 5 bytes of data
2022-10-26, 14:51:39:639:570 < Protocol Discriminator: Q.931 (8) len=5
2022-10-26, 14:51:39:639:582 < TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent to originator)
2022-10-26, 14:51:39:639:637 < Message Type: CONNECT (7)
2022-10-26, 14:51:39:639:649 – Got ACK for N(S)=1 to (but not including) N(S)=1
2022-10-26, 14:51:39:639:660 – T200 requested to stop when not started
2022-10-26, 14:51:39:639:671 T203 requested to start without stopping first
2022-10-26, 14:51:39:639:682 – Starting T203 timer
2022-10-26, 14:51:39:639:696 Received message for call 0x7f755001a520 on link 0x7f75245c1ce0 TEI/SAPI 0/0
2022-10-26, 14:51:39:639:712 q931.c:8854 post_handle_q931_message: Call 32769 enters state 8 (Connect Request). Hold state: Idle
2022-10-26, 14:51:39:639:725
2022-10-26, 14:51:39:639:737 > TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:39:639:747 > V(A)=1, V(S)=1, V®=3
2022-10-26, 14:51:39:639:758 > K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:39:639:769 > T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:39:639:781 > [ 02 01 01 06 ]
2022-10-26, 14:51:39:639:791 > Supervisory frame:
2022-10-26, 14:51:39:639:802 > SAPI: 00 C/R: 1 EA: 0
2022-10-26, 14:51:39:639:812 > TEI: 000 EA: 1
2022-10-26, 14:51:39:639:823 > Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:39:639:834 > N®: 003 P/F: 0
2022-10-26, 14:51:39:639:844 > 0 bytes of data
2022-10-26, 14:51:39:639:861 Done handling message for SAPI/TEI=0/0
2022-10-26, 14:51:39:640:052 q931.c:6487 q931_connect_acknowledge: Call 32769 enters state 10 (Active). Hold state: Idle
2022-10-26, 14:51:39:640:068
2022-10-26, 14:51:39:640:078 > DL-DATA request
2022-10-26, 14:51:39:640:089 > Protocol Discriminator: Q.931 (8) len=5
2022-10-26, 14:51:39:640:101 > TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent from originator)
2022-10-26, 14:51:39:640:112 > Message Type: CONNECT ACKNOWLEDGE (15)
2022-10-26, 14:51:39:640:126 TEI=0 Transmitting N(S)=1, window is open V(A)=1 K=7
2022-10-26, 14:51:39:640:136
2022-10-26, 14:51:39:640:147 > TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:39:640:157 > V(A)=1, V(S)=1, V®=3
2022-10-26, 14:51:39:640:168 > K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:39:640:179 > T200_id=0, N200=3, T203_id=8192
2022-10-26, 14:51:39:640:193 > [ 00 01 02 06 08 02 00 01 0f ]
2022-10-26, 14:51:39:640:204 > Informational frame:
2022-10-26, 14:51:39:640:215 > SAPI: 00 C/R: 0 EA: 0
2022-10-26, 14:51:39:640:225 > TEI: 000 EA: 1
2022-10-26, 14:51:39:640:236 > N(S): 001 0: 0
2022-10-26, 14:51:39:640:246 > N®: 003 P: 0
2022-10-26, 14:51:39:640:256 > 5 bytes of data
2022-10-26, 14:51:39:640:274 > Protocol Discriminator: Q.931 (8) len=5
2022-10-26, 14:51:39:640:421 > TEI=0 Call Ref: len= 2 (reference 1/0x1) (Sent from originator)
2022-10-26, 14:51:39:640:432 > Message Type: CONNECT ACKNOWLEDGE (15)
2022-10-26, 14:51:39:640:443 – Stopping T203 timer
2022-10-26, 14:51:39:640:454 – Starting T200 timer
2022-10-26, 14:51:39:653:611 Receive the q921 packet ‘6’ bytes!
2022-10-26, 14:51:39:653:650
2022-10-26, 14:51:39:653:663 < TEI: 0 State 7(Multi-frame established)
2022-10-26, 14:51:39:653:673 < V(A)=1, V(S)=2, V®=3
2022-10-26, 14:51:39:653:684 < K=7, RC=0, l3_initiated=0, reject_except=0, ack_pend=0
2022-10-26, 14:51:39:653:695 < T200_id=8192, N200=3, T203_id=0
2022-10-26, 14:51:39:653:709 < [ 00 01 01 04 ]
2022-10-26, 14:51:39:653:719 < Supervisory frame:
2022-10-26, 14:51:39:653:730 < SAPI: 00 C/R: 0 EA: 0
2022-10-26, 14:51:39:653:741 < TEI: 000 EA: 1
2022-10-26, 14:51:39:653:752 < Zero: 0 S: 0 01: 1 [ RR (receive ready) ]
2022-10-26, 14:51:39:653:763 < N®: 002 P/F: 0
2022-10-26, 14:51:39:653:773 < 0 bytes of data
2022-10-26, 14:51:39:653:785 – Got ACK for N(S)=1 to (but not including) N(S)=2
2022-10-26, 14:51:39:653:797 – ACKing N(S)=1, tx_queue head is N(S)=-1 (-1 is empty, -2 is not transmitted)
2022-10-26, 14:51:39:653:807 – Stopping T200 timer
2022-10-26, 14:51:39:653:818 – Starting T203 timer
2022-10-26, 14:51:39:653:831 Done handling message for SAPI/TEI=0/0


#2

#3

doing that now, I was unaware there was a ticketing system avialable, thankyou!