Hi,
The kaltura-*config.sh scripts are indeed only necessary in RPM based systems, because Debian, Ubuntu and all other dists using deb as their install format make use of the wonderful debconf mechanism so they can prompt for input interactively while running the postinst hook.
In the case of batch, no additional input is required because all needed input was received during the kaltura-base postinst.
You can re-run the batch postinst by running:
# dpkg-reconfigure kaltura-batch
You probably want to do both:
# dpkg-reconfigure kaltura-base
and:
# dpkg-reconfigure kaltura-batch
Then, tail /opt/kaltura/log/kaltura_batch.log for errors