search

hnimminh / libresbc

An open source Session Border Controller 🌟 The SBC you dream about 🗽 LibreSBC will help you save thousands of dollars.
https://github.com/hnimminh/libresbc
MIT License
357 stars 80 forks source link

[Deployement] FreeSWITCH require SignalWise PATs #51

Closed ibexnet closed 2 years ago

ibexnet commented 2 years ago

Describe the bug The installation via ansible fail with this message: "Failed to download key at https://files.freeswitch.org/repo/deb/debian-release/fsstretch-archive-keyring.asc: HTTP Error 401: Unauthorized"

To Reproduce

Actual behavior The installation process fail to download the fsstretch-archive-keyring.asc before installing the rquirement packages. I saw that the file under the link https://files.freeswitch.org/repo/deb/debian-release/fsstretch-archive-keyring.asc is password protected.

Expected behavior

Log & Screenshots

Additional context

ooliver1 commented 2 years ago

you should most definitely rename this issue to describe more

something like Failed to download key at <url> HTTP Error 401: Unauthorized

hnimminh commented 2 years ago

hmmm.., seem signalwire has changed, they require PAT to access their repo https://freeswitch.org/confluence/display/FREESWITCH/HOWTO+Create+a+SignalWire+Personal+Access+Token

camglegg commented 2 years ago

Also running into this issue. I am able to create the PAT.

It seems that Freeswitch already has Ansible playbook premade. There suggestion is:


# You could set the password here or on your CLI. We set it in group_vars/all in our Ansible Inventory
#  vars:
#    - signalwire_freeeswitch_key: pat_XXXXX

@hnimminh Do you think this is the best method? Or should we try something else?

Thanks in advance for your help.

hnimminh commented 2 years ago

@camglegg I will add that support libresbc deployment in this weekend, once done, I will need your help to verify the fix. I'm also thinking that use Docker, so that everyone can deploy libresbc easier.

camglegg commented 2 years ago

@camglegg I will add that support libresbc deployment in this weekend, once done, I will need your help to verify the fix. I'm also thinking that use Docker, so that everyone can deploy libresbc easier.

I am more than happy to test the Ansible and Docker configurations!

I was working on updating the freeswitch.yml platform task, but there is quite a bit going on in that file. It will most likely be faster for you to update it.

I really appreciate your help!! Let me know if there is anything you need from me.

hnimminh commented 2 years ago

@camglegg @ibexnet can you re-test on master branch?

Once you register and get SignalWire Personal Access Tokens, you will need to declare ansible extra variable to install FreeSWITCH (when you run ansible-playbook with tag platform or freeswitch), Example:

ansible-playbook playbooks/deployment.yml -i inventories/production -l "<machine-name>" -t "platform,libre,nginx,captagent" -e "signalwire_pat_token=Your-SignalWire-Personal-Access-Tokens"

camglegg commented 2 years ago

@camglegg @ibexnet can you re-test on master branch?

Once you register and get SignalWire Personal Access Tokens, you will need to declare ansible extra variable to install FreeSWITCH (when you run ansible-playbook with tag platform or freeswitch), Example:

ansible-playbook playbooks/deployment.yml -i inventories/production -l "<machine-name>" -t "platform,libre,nginx,captagent" -e "signalwire_pat_token=Your-SignalWire-Personal-Access-Tokens"

Yes! I will test this today. Thanks!

camglegg commented 2 years ago

@hnimminh The playbook works perfectly!

Target Machine: OS: Debian GNU/Linux 10 (Buster) x86_64 Host: KVM/QEMU Kernel: 4.19.0.20-amd64

Host Machine Ansible Version: 2.10.8 Python Version: 3.10.4

Playbook Runtime: 00:30:40

Let me know if you need anymore information and Thank you for the quick fix!

Full Log File (PAT Token Removed) cameronglegg_FreeSwitchPAT_ansible.log

hnimminh commented 2 years ago

Thanks @camglegg