Question

Locked

X25 message size issue?

By dvanrooyen ·
Hi All,

I am currently experiencing issues with messages sent over one of our DTE's. The DTE's in question are used for card transactions to the card host.

Using the same card on the same device using one of the DTE's to the host yields a positive result. Using the same card and device communicating over a different DTE to the same host yields a comms error. The message being sent from the comms provider to the X25 network is correct, but the message received by the ISP from X25 is not correct. The size of the packet received via the DTE that is not working is different from the message received on DTE that is working. Below is a trace at ISP of the 2 different messages received from X25 network(DTE details ammended for security reasons):

Packet with issues:
*Mar 1 08:05:14.629: Serial0/0/0: X.25 I R1 Call (15) 8 lci 1
*Mar 1 08:05:14.629: From (10): XXXXXXXXXX To (10): 1111111111
*Mar 1 08:05:14.629: Facilities: (0)
*Mar 1 08:05:14.633: Serial0/0/0: X.25 O R1 Call Confirm (3) 8 lci 1
*Mar 1 08:05:15.033: Serial0/0/0: X.25 O D1 Data (4) Q 8 lci 1 PS 0 PR 0
*Mar 1 08:05:15.053: Serial0/0/0: X.25 I D1 RR (3) 8 lci 1 PR 1
*Mar 1 08:05:16.073: Serial0/0/0: X.25 I D1 Data (93) 8 lci 1 PS 0 PR 1
*Mar 1 08:05:20.033: Serial0/0/0: X.25 O R1 Clear (5) 8 lci 1
*Mar 1 08:05:20.033: Cause 0, Diag 0 (DTE originated/No additional information)
*Mar 1 08:05:20.061: Serial0/0/0: X.25 I R1 Clear Confirm (3) 8 lci 1

Healthy Packet:
*Mar 1 08:06:15.741: Serial0/1/0: X.25 I R1 Call (1 8 lci 1
*Mar 1 08:06:15.745: From (: XXXXXXXX To (10): 2222222222
*Mar 1 08:06:15.745: Facilities: (0)
*Mar 1 08:06:15.745: Call User Data (4): 0x01000000 (pad)
*Mar 1 08:06:15.745: Serial0/1/0: X.25 O R1 Call Confirm (3) 8 lci 1
*Mar 1 08:06:18.765: Serial0/1/0: X.25 I D1 Data (93) 8 lci 1 PS 0 PR 0
*Mar 1 08:06:18.765: Serial0/1/0: X.25 O D1 RR (3) 8 lci 1 PR 1
*Mar 1 08:06:19.121: Serial0/1/0: X.25 O D1 Data (4) Q 8 lci 1 PS 0 PR 1
*Mar 1 08:06:19.121: Serial0/1/0: X.25 O D1 Data (94) 8 lci 1 PS 1 PR 1
*Mar 1 08:06:19.133: Serial0/1/0: X.25 I D1 RR (3) 8 lci 1 PR 1
*Mar 1 08:06:19.173: Serial0/1/0: X.25 I D1 RR (3) 8 lci 1 PR 2
*Mar 1 08:06:19.181: Serial0/1/0: X.25 I D1 Data (4 Q 8 lci 1 PS 1 PR 2
*Mar 1 08:06:19.185: Serial0/1/0: X.25 O D1 Data (12) Q 8 lci 1 PS 2 PR 1
*Mar 1 08:06:19.185: Serial0/1/0: X.25 O D1 RR (3) 8 lci 1 PR 2
*Mar 1 08:06:19.201: Serial0/1/0: X.25 I D1 RR (3) 8 lci 1 PR 3
*Mar 1 08:06:19.229: Serial0/1/0: X.25 I D1 Data (12) Q 8 lci 1 PS 2 PR 3
*Mar 1 08:06:19.229: Serial0/1/0: X.25 O D1 RR (3) 8 lci 1 PR 3
*Mar 1 08:06:36.393: Serial0/1/0: X.25 I D1 Data (4) Q 8 lci 1 PS 3 PR 3
*Mar 1 08:06:36.393: Serial0/1/0: X.25 O D1 RR (3) 8 lci 1 PR 4
*Mar 1 08:06:36.397: Serial0/1/0: X.25 O R1 Clear (5) 8 lci 1
*Mar 1 08:06:36.397: Cause 0, Diag 0 (DTE originated/No additional information)
*Mar 1 08:06:36.473: Serial0/1/0: X.25 I R1 Clear Confirm (3) 8 lci 1

The comms provider suggest that the X25 guys check the window size, but they insist this is the same accross both DTE's which inclused the one that works correctly.
Could it be that the packet is being compressed at an X25 Network level?

Thanks

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Share your knowledge
Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums