Jump to content

mikeboss

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mikeboss

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. this is great! first I took a snapshot of the working 66.0.2 VM, reinstalled V 66.0.3, configured the Swisscom inOne trunk using the dropdown and voilĂ ! it's working right away. couldn't be easier. again, thanks for the top notch support
  2. sure, no problem. it's just old habbits (32bit = less memory used). right now I'm running 3CX on a super tiny ESXi host (4.0 GB RAM), so this sure will do for Vodia, too. as soon as I'm able to fully use Vodia PBX with the Swisscom inOne trunk I'll finally be able to get rid of the 3CX VM
  3. yep, das mit dem @swisscom.ch@swisscom.ch ist mir auch aufgefallen. jedoch habe ich es trotz zahlreicher versuche mit anpassen der konfiguration nicht wegbekommen. SIP caller-ID Presentaion ist aktuell wieder unveraendert:
  4. not hard at all. I'm just trying to use as little memory as possible. I used to run the snomONE on an AMD Geode LX800 with 256 MB of RAM...
  5. log entries of a failed attempt to place an outbound call "Ladies and gentlemen: the story you are about to hear is true. Only the names have been changed to protect the innocent." [5] 15:39:22.306 PACK: SIP Rx 192.168.1.101:55708: INVITE sip:0788888888@172.20.20.111 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:55708;rport;branch=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Max-Forwards: 70 From: "NAME" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: sip:0788888888@172.20.20.111 Contact: "mibo" <sip:100@192.168.1.101:55708;ob> Call-ID: YYYYYYYY
  6. --2020-10-10 12:28:25-- http://portal.vodia.com/downloads/pbx/debian32/pbxctrl-debian32-66.0.2 Resolving portal.vodia.com (portal.vodia.com)... 54.175.147.78 Connecting to portal.vodia.com (portal.vodia.com)|54.175.147.78|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2020-10-10 12:28:25 ERROR 404: Not Found.
  7. thank you for your reply. yes, I do have a Dial Plan. I did test it with another VoIP provider and it worked right away (was able to place an outbound call immediately).
  8. hallo allerseits! seit geraumer zeit versuche ich erfolglos (m)eine Vodia PBX an den SIP-Trunk von Swisscom anzubinden. die Swisscom, ihreszeichens nummer eins der TelCos in der schweiz, bietet null support da dieses vorgehen offiziell nicht von ihr unterstuetzt wird (absichern der pfruende...). wie auch immer, FreePBX (Asterisk) und 3CX habe ich fehlerfrei ans laufen bekommen. mit der Vodia komme ich einfach nicht ans ziel. man koennte natuerlich einen echten SIP-Trunk bei Swisscom ordern. das lohnt jedoch nicht fuer private und kleine unternehmen. also moechte ich die Vodia PBX eben an
  9. just a heads up: behavior is still the same with release 63 (fresh install of V 63 on unmolested Raspbian).
  10. switched on "SSH access" in the web GUI and rebooted the Raspberry Pi. now I can see on the Raspberry's screen: FAILED to start OpenBSD Secure Shell server. I mean, it's no biggie for me. since I do have a screen and a keyboard attached to the system, I can install dropbear (which works with 62.1). but for others this might be a problem...
  11. yes, as stated above: 62.1 (Build Date: Apr 11 2019 17:13:20)
  12. did a fresh install of the latest Raspbian (2019-04-08-raspbian-stretch-lite.img) same procedure: installed 62.0 then updated to 62.1 using the web GUI. did a reboot and afterwards -> SSH connection refused.
  13. oh, there's a new Raspbian release from a few days ago. will try that, too.
  14. nope, still the same: SSH connection refused after update 62.0 -> 62.1
  15. I'm pretty sure I did a reboot... okay, will start from scratch. fresh install again. back in a few minutes.
×
×
  • Create New...