With ffmpeg it literally takes out what you want so you can use it later. Eg. below -ss means starting time is 16 minutes and 30 seconds and -to means extract until 17 minutes and 23 seconds
-i = the input file
output file = CCME-flash-and-2-phone-setup-final.mp4
ffmpeg -i CCME-flash-and-2-phone-setup.mp4 -ss 00:16:30 -to 00:17:23 -c copy CCME-flash-and-2-phone-setup-fin........
This normally works but if not use my mencoder solution if the output video does not play past the joined time.
the contents of list.txt need to look like this:
then run ffmpeg
ffmpeg -f concat -i list.txt -c copy CME-2-router-dial-peer-final.mp4
The result is almost instant joining since there is no video processing since we are........
The problem for me is that Ihad two videos with different types of audio streams. ffmpeg would join them but they would not play past the point of the join.
So Iused mencoder like below and it joined the audio and made them both mp3 streams and it worked!
-oac mp3lame specifies the audio to be convered into an mp3 stream using the lame codec.
after the oac the two files are the ones to be joined.
the -o is the name of the outp........
1.) Install dynagen and dynamips
2.)Also configure your bridge or br0
If you don't have a br0 on your Linux machine then follow this guide or video for Debian:
Alternatively you can use NIO_linux_eth:eth0 for f0/0 below but remember the host machine cannot talk to the router then.
Getting started, let's enable ephones and DNs we can add a phone with a telephone number:
!this enables ephone registration otherwise phones cannot register
!max-ephones 2 says we can have a maximum of 2 phones, change to your needs (or to the limit set by your IOS image)
The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs.
QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard
For some reason, perhaps you don't want to run a daemon or let Letsencrypt have access to your production server.
There is a way to use it like a normal CSR/CA setup in manual mode.
./letsencrypt-auto certonly --manual -d realtechtalk.com - www.realtechtalk.com
Eventually you will get prompted to create a certain path and file with certain data:
Create a file containing just this data: