Once set up, the asterisk-alpine container consumed 24 MB of RAM and less than 1% CPU, and requires 33 MB of storage. Repeat the configuration of the Raspberry Pi to set up lines and connect to the GrandStream HT-503 box. I did not immediately need any extra files but any use of the talking clock or answer machines will. Issue these commands to add any desired extras to Asterisk: apk update Do this by Secure Shell ( ssh) into the Synology and connect to the Asterisk container using: sudo docker exec -it asterisk-alpine shThe container is named asterisk-alpine in this example and sh is the command to execute. dont share location with synology ( will not find virtual dsm) now DSM is ready This type of VM should work with dsm 6.2, 6.2.1, 6.2.xs/3617xs loaders DSM 6.2.3 is showing synoboot drive as eSata in dsm. Create a terminal session to the running Docker container. I CAN go to on the LAN and see the files and such on the 213j. Alpine Linux and AsteriskNext set up Asterisk. This does go against the contained nature of Docker but for this situation it bypasses many problems. The container is free to open ports and chatter away. What I've missed? I try also with/without extra_lzma customized file (I think -but I am not so sure- in the past, when the server has workinged, I used this customized file.By applying Use the same network as Docker Host there is no need to specify port mapping or exposing ranges. Meanwhile, using Synology Assistant, I couldn't see anything in the LAN (as Synology server.) When I restart the server (having the prepared usb stick, connected in one of the usb port), either in UEFI mode or Legacy mode, the screen with "Happy hacking" appears, but after a while he restarts over and over again. (my server's HDD - a 3TB SATA-III has been erased and at this moment not even a partition is not created on him!) My intention is to make a fresh install of DSM 6.1.7 on ds3615xs. Here is the thread that I recommend reading. As most of you know by now Jun was able to find a way to install DSM 6 on non Synology boxes. To upgrade from DSM 6.0.2 to DSM 6.1.7 read here. So, I took a fresh new BL v1.02b and I've done all operations regarding the VID/PID/SN/MAC1 as I've done before. If for some reason you want to upgrade to DSM 6.0.2 first or simply you do not want to upgrade to DSM 6.1.7 but only to DSM 6.0.2 then use the link above. Ok! After a lot of failures to make my server working again (including playing with BL v1.03a2+ds918+, BL v1.03b+ds3615xs) I gave up and I've erased everything on the HDD, having in mind to start again, from the beginning with a clean install (as I've done in the past, considering if I've done that, then I should be able to do it again!) By my mistake, I validate the upgrade action, from 6.1.7 to 6.2 => my DSM server has been bricked out. The used HW is the one described in the signature. In the past I had a functional DSM 6.1.7 on ds3615xs using Jun's BL v1.02b.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |