I decoded (see below) a couple of those signals and looked them up in file I got from Rob (see below). That indicates the two setup codes that could generate those signals are CD/0147 and Tape/0218. But it also indicates that neither of those those setup codes are built-in on either the 9960 or the 7562.
The easiest option may be updating by .wav file. I believe .wav files for the 7562 are available from an OFA website. I believe .wav files for the 9960 are only available from OFA customer support over the phone (to the USA). I expect phone calls to the USA wouldn't be your best choice. For more info about getting .wav files search the forum at[Link: remotecentral.com]
or ask some questions there.
It is also possible to make your own .wav file for either the 9960 or the 7562 using the free JP1 software available from Rob's website at [Link: hifi-remote.com]
A .wav file you make that way would be customized to your specific needs and thus much better than an official .wav file from OFA. But there is a fair amount of learning required to know how to use the JP1 software to produce a .wav file.
A .wav file is loaded into the remote by inductive pickup from a telephone handset or a PC speaker. No extra hardware nor physical connection is required (but on some telephone handsets and some PC speakers it won't work because they produce too little magnetic field. It isn't the sound that carries the info. It is the magnetic field the speaker generates in the process of producing the sound).
An upgrade file created with the JP1 software is a lot easier to load directly into the remote by JP1 cable than to transform to .wav and load through the PC speaker. But that way requires buying or building the cable (see Rob's website).
However you do it, you'll need the info from decoding those Pronto Hex string you find. To do that you need DecodeIr.dll and the JP1 version of IrTool.exe[Link: john.fine.home.comcast.net][Link: remotecentral.com]
Run IrTool with DecodeIr in the same directory, then copy/paste each Pronto Hex string from that page you linked into IrTool and press Decode. A pop up dialog should appear with the decode info. For example the STOP command decodes as: NEC1, device=103, OBC=17, EFC=121.
If you get one of those two setup codes I mentioned above, NEC1 device=103 is built into the setup code. You can use the EFC numbers to program specific functions to specific buttons (some of the buttons you want might already be the default in the setup code). If you don't know how to use EFC numbers, it is explained in many threads in that rc-one4all forum I mentioned. But the EFC numbers are useless unless you have a compatible setup code, which I think requires update by either .wav file or JP1 cable.
If you use the JP1 software to produce a file you need to input the NEC1 and 103 to the setup sheet and use either OBC or EFC number to define each function (EFC number is an encrypted form of OBC number that OneForAll uses to try to hide information, but their encryption was cracked long ago).