first cry for help in 5 years - config file for CiscoISB7500

i'm not a newbie to LIRC.  i've worked on the irtoy code and even built
new firmware versions for that hardware.  but this new U-verse Cisco
ISB7500 box / remote has me stumped.

most of the files i have found out there (including here on the mailing
list) have mostly similar, odd behaviour; a 4 digit sequence (all on one
command line) takes over 12 seconds to blast.  and nothing happens.

i have my lircd set up and talking well to:
  Bose sound bar
  Kinivo HDMI switch
  LG TV
and until recently, my cable TV/DVR which was Spectrum/Time Warner; it
worked under a DRC800 Motorola configuration file.

so i know my hardware works fine.  then this past Friday i swapped out
Spectrum for U-verse.  new cable / DVR from Cisco.  the remote has
"S30-S1B" printed on the back.

what i can't find is a working Cisco ESB7500 config file.

i've tried to irrecord one several times with so far abject failure. the
seemingly best recording i had was on a raspberry pi zero w with a TIRA
blaster:

    irrecord --driver=tira -d /dev/ttyUSB0

it never timed out looking for gaps and key codes, figured out a Toggle
bit mask.  but when running the imported "cisco" file to my LIRCD running
pi, the other devices still work, but any commands to the cisco either do
nothing, blast for an inordinate amount of time of (this latest recorded
from the TIRA) gets "transmission failed ... Input/output error".

the seemingly "best" recording session produced:

#
# This config file was automatically generated
# using lirc-0.9.4c(tira) on Sun Feb 24 13:38:37 2019
# Command line used: --driver=tira -d /dev/ttyUSB0 -n ./att.conf
# Kernel version (uname -r): 4.14.79+
#
# Remote name (as of config file): cisco
# Brand of remote device, the thing you hold in your hand:
# Remote device model nr:
# Remote device info url:
# Does remote device has a bundled capture device e. g., a
#     usb dongle? :
# For bundled USB devices: usb vendor id, product id
#     and device string (use dmesg or lsusb):
# Type of device controlled
#     (TV, VCR, Audio, DVD, Satellite, Cable, HTPC, ...) :
# Device(s) controlled by this remote:

begin remote

  name  cisco
  driver tira
  bits           24
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   8
  pre_data       0x0
  post_data_bits  32
  post_data      0x0
  gap          99829
  toggle_bit_mask 0x504010
  frequency    38000

      begin codes
          4                        0x514015
          5                        0x500015
          6                        0x504015
          7                        0x540015
          8                        0x514015
          9                        0x000000
          0                        0x0AA208
          1                        0x540015
          2                        0x544015
          3                        0x440010
          ok                       0x114015
          cc                       0x040115
      end codes

end remote

which i imported to the lircd-running pi, removing the driver line.  the
digit 9 looks extremely suspect, regardless.

i've been out of the U-verse world for a few years this time round; the
previous "2-Wire" version of U-verse i had worked fine with the Motorola
VIP1200 config file.  in fact it was that version of U-verse system that
drove me to get into LIRC in the first place so i could program a "Closed
Captioning" script; it took something like 12 key presses to turn on - or
off - the Closed Captioning.

but this new one is driving me batty.

any hints or tips would be greatly appreciated.

of course if someone has a running config file, that would be sweet.  but
i'll take advice on being able to grow my own recorded file.  the setup on
that raspberry pi zero is:

   lirc  packages from the stretch repo, version 0.9.4c-9
   Tira (2.1?) from home-electro.com ... it shows up as:

[    1.598389] usb 1-1: New USB device found, idVendor=0403, idProduct=fa78
[    1.601809] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[   11.448898] usbserial: USB Serial support registered for generic
[   11.680369] usbserial: USB Serial support registered for FTDI USB
Serial Device
[   11.680851] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[   12.041244] usb 1-1: FTDI USB Serial Device converter now attached to
ttyUSB0
     and ...
Bus 001 Device 002: ID 0403:fa78 Future Technology Devices International, Ltd

i can't think of anything else to provide that may trigger an "ah ha"
moment for someone.

thank you for your consideration.