Almost 2 years ago, I wrote an article about vmcam and how to use it. Unfortunately, later that year a lot of providers made some changes in their IPTV setups, rendering vmcam rather useless. What happened is that their servers dropped support for the old protocol (1154) in favor of a newer version (1155) which vmcam did not support at that time.
Recently there have been quite some developments on this issue. One of our readers (marri) reported in the comments on his progress in reverse engineering the Amino firmware update process and managed to obtain root access to his box. Another reader mailed us last week with what turned out to be a rather crucial piece of information about the new protocol.
I started looking into this tip and found the apparent solution almost too easy to be true. From the information provided, it seemed that the only difference between protocol 1154 and 1155 was the start of each message. Where messages in protocol 1154 would start with:
protocol 1155 would start them with:
where [length] is a 5 digit string containing the length of the entire message.
After updating vmcam to support this change it turned out to be correct! The replies from the server are unchanged between protocols, so the only necessary change was this small addition to the start of each sent message.
With this updated version of vmcam, both protocols are supported. 1154 is still the default, so if you need to use 1155 you will either have to specify it on the command line:
vmcam -m 1155
or in the config file:
Note that vmcam is not compatible with libssl1.1, so you’ll need an older version to compile the program. Also, like in my previous vmcam article, the server keys are now even more outdated (~2 years more) than they were back then. I have successfully compiled vmcam this time with libssl-dev_1.0.1e-2+deb7u20_amd64 (download .deb), which also requires libssl1.0.0_1.0.1e-2+deb7u20_amd64 (download .deb) to be available.