I have seventy-some connections that we are trying to move from old legacy DEC equipment to various Cisco terminal servers. These are "reverse" connections that are established by a network host via LAT. The connections remain up indefinitely, and then the host and the devices connected to the serial lines communicate back and forth. There are many cases where things happen too quick for the devices on the serial lines to handle. By that I mean, over the years, the host, the network and now the terminal servers have gotten too fast. I need to institute a delay of some sort for the communications initiated by the host, and received by the device connected to the Cisco terminal server. Ideally, I would prefer to implement a delay when certain strings are sent by the host. I've tried dispatch-timeout and dispatch-machine, but further research shows that these will only work for TCP connections. I also don't believe that I can use route-maps to send packets on a round about way through the network to implement a delay (yes, bad design, but worthy of trying) on account that the connections are via LAT, not IP. This isn't a buffering problem. Does anyone have any ideas on how to implement any sort of delay for these communications, even if it is on EVERY packet? Thanks.