mikeboss

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

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

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:

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...

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: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28786 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, norefersub User-Agent: Telephone 1.5.1 Content-Type: application/sdp Content-Length: 480 v=0 o=- 0123456789 0123456789 IN IP4 192.168.1.101 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 4006 RTP/AVP 96 9 8 0 101 102 c=IN IP4 192.168.1.101 b=TIAS:96000 a=rtcp:4007 IN IP4 192.168.1.101 a=sendrecv a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=rtpmap:102 telephone-event/8000 a=fmtp:102 0-16 a=ssrc:1234123412 cname:12341234aabbccdd [5] 15:39:22.315 PACK: Last message repeated 2 times [5] 15:39:22.315 PACK: SIP Tx 192.168.1.101:55708: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.1.101:55708;rport=55708;branch=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: <sip:0788888888@172.20.20.111>;tag=001122334455 Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28786 INVITE User-Agent: Vodia-PBX/66.0.2 WWW-Authenticate: Digest realm="172.20.20.111",nonce="aaabbbbcccddeeefff8726823746",domain="sip:0788888888@172.20.20.111",algorithm=MD5 Content-Length: 0 [5] 15:39:22.318 PACK: SIP Rx 192.168.1.101:55708: ACK 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: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: sip:0788888888@172.20.20.111;tag=001122334455 Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28786 ACK Content-Length: 0 [5] 15:39:22.323 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=WWWWWWWWWWWWWWWWWWWWWW Max-Forwards: 70 From: "mibo" <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: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, norefersub User-Agent: Telephone 1.5.1 Authorization: Digest username="100", realm="172.20.20.111", nonce="aaabbbbcccddeeefff8726823746", uri="sip:0788888888@172.20.20.111", response="648a7b487cd057459a8a46353f7b64bc68", algorithm=MD5 Content-Type: application/sdp Content-Length: 480 v=0 o=- 0123456789 0123456789 IN IP4 192.168.1.101 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 4006 RTP/AVP 96 9 8 0 101 102 c=IN IP4 192.168.1.101 b=TIAS:96000 a=rtcp:4007 IN IP4 192.168.1.101 a=sendrecv a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=rtpmap:102 telephone-event/8000 a=fmtp:102 0-16 a=ssrc:1234123412 cname:12341234aabbccdd [8] 15:39:22.323 SIP: Tagging request with existing tag [9] 15:39:22.334 TRUN: Dialplan: Simple match begin of 0788888888 to * [9] 15:39:22.335 TRUN: Last message repeated 2 times [9] 15:39:22.335 TRUN: Dialplan: Evaluating * against 0788888888@localhost [5] 15:39:22.336 TRUN: Last message repeated 2 times [8] 15:39:22.336 TRUN: Using rule set "acd-ani ext-ani trunk-prefix dom-ani trunk-ani from" for user 100 [8] 15:39:22.336 TRUN: Processing rule acd-ani [8] 15:39:22.336 TRUN: Processing rule ext-ani [9] 15:39:22.337 TRUN: Placeholder ext-ani for user 100 is [8] 15:39:22.337 TRUN: Processing rule trunk-prefix [8] 15:39:22.337 TRUN: Processing rule dom-ani [9] 15:39:22.337 TRUN: Placeholder dom-ani is [8] 15:39:22.337 TRUN: Processing rule trunk-ani [9] 15:39:22.337 TRUN: Placeholder trunk-ani is [8] 15:39:22.337 TRUN: Processing rule from [9] 15:39:22.337 TRUN: Placeholder from is 100 [8] 15:39:22.337 TRUN: Using 100 vorname nachname [8] 15:39:22.339 TRUN: Using rule set "acd-ani ext-ani trunk-prefix dom-ani trunk-ani from" for user 100 [8] 15:39:22.339 TRUN: Processing rule acd-ani [8] 15:39:22.340 TRUN: Processing rule ext-ani [9] 15:39:22.340 TRUN: Placeholder ext-ani for user 100 is [8] 15:39:22.340 TRUN: Processing rule trunk-prefix [8] 15:39:22.340 TRUN: Processing rule dom-ani [9] 15:39:22.340 TRUN: Placeholder dom-ani is [8] 15:39:22.340 TRUN: Processing rule trunk-ani [9] 15:39:22.340 TRUN: Placeholder trunk-ani is [8] 15:39:22.340 TRUN: Processing rule from [9] 15:39:22.340 TRUN: Placeholder from is 100 [8] 15:39:22.340 TRUN: Using 100 vorname nachname [9] 15:39:22.340 TRUN: Generating hf header using {trunk} [9] 15:39:22.340 TRUN: Generating ht header using {request-uri} [9] 15:39:22.341 TRUN: Generating hrpi header using {from} [9] 15:39:22.344 TRUN: Variables for Swisscom inOne { "ani":"100", "ani-cnam":"vorname nachname", "ani-e164":"100", "ani-nanpa":"100", "ani-plus":"100", "ani-raw":"100", "ani-row":"100", "clip":"false", "close":"}", "disa":"false", "dom-ani":"", "dom-ani-e164":"", "dom-ani-nanpa":"", "dom-ani-plus":"", "dom-ani-row":"", "domain":"localhost", "domain-display":"", "domain-param1":"", "domain-param2":"", "domain-param3":"", "emergency":"false", "ext":"\"vorname nachname\" <sip:100@localhost>", "ext-ani":"100", "ext-ani-cnam":"100", "ext-ani-e164":"100", "ext-ani-nanpa":"100", "ext-ani-plus":"100", "ext-ani-raw":"100", "ext-ani-row":"100", "ext-display":"vorname nachname", "ext-param1":"", "ext-param2":"", "ext-param3":"", "ext-uri":"sip:100@localhost", "ext-user":"100", "from":"\"vorname nachname\" <sip:100@swisscom.ch>", "from-display":"vorname nachname", "from-extension":"true", "from-host":"localhost", "from-hostport":"localhost", "from-noclip":"\"vorname nachname\" <sip:100@localhost;user=phone>", "from-port":"", "from-scheme":"sip", "from-trunk":"false", "from-uri":"sip:100@localhost;user=phone", "from-uri-raw":"sip:100@localhost", "from-user":"100", "from-user-raw":"100", "global-uri-number":"+41788888888", "icid-value":"", "in-reply-to":"YYYYYYYYYYYYYYYYYYYYYYYYYYY", "ip-address":"{x-pre-adr}", "local-uri-number":"0788888888", "open":"{", "orig-ioi":"localhost", "pai":"\"\" <sip:>", "pai-display":"", "pai-host":"", "pai-hostport":"", "pai-noclip":"\"\" <sip:>", "pai-port":"", "pai-scheme":"sip", "pai-uri":"sip:", "pai-uri-raw":"", "pai-user":"", "pai-user-raw":"", "ppi":"\"\" <sip:>", "ppi-display":"", "ppi-host":"", "ppi-hostport":"", "ppi-noclip":"\"\" <sip:>", "ppi-port":"", "ppi-scheme":"sip", "ppi-uri":"sip:", "ppi-uri-raw":"", "ppi-user":"", "ppi-user-raw":"", "replacement":"sip:0788888888@swisscom.ch;user=phone", "request-uri":"sip:0788888888@swisscom.ch;user=phone", "rpi":"\"\" <sip:>", "rpi-display":"", "rpi-host":"", "rpi-hostport":"", "rpi-noclip":"\"\" <sip:>", "rpi-port":"", "rpi-scheme":"sip", "rpi-uri":"sip:", "rpi-uri-raw":"", "rpi-user":"", "rpi-user-raw":"", "to":"\"0788888888\" <sip:0788888888@localhost;user=phone>", "to-display":"0788888888", "to-host":"localhost", "to-hostport":"localhost", "to-noclip":"\"0788888888\" <sip:0788888888@localhost;user=phone>", "to-number":"0788888888", "to-port":"", "to-scheme":"sip", "to-uri":"sip:0788888888@localhost;user=phone", "to-uri-raw":"sip:+41788888888@localhost", "to-user":"0788888888", "to-user-raw":"+41788888888", "trunk":"<NC-USERNAME@swisscom.ch@swisscom.ch>", "trunk-account":"+41319188888", "trunk-ani":"", "trunk-display":"", "trunk-host":"swisscom.ch", "trunk-outbound-proxy":"sip:fs1.ims.swisscom.ch", "trunk-port":"", "trunk-registrar":"swisscom.ch", "trunk-uri":"NC-USERNAME@swisscom.ch@swisscom.ch", "trunk-user":"NC-USERNAME@swisscom.ch", "trunk-uuid":"aaaaaaaa-bbbb-cccc-ddd-eeeeeeeeeeee" } [5] 15:39:22.348 PACK: SIP Tx 192.168.1.101:55708: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.101:55708;rport=55708;branch=WWWWWWWWWWWWWWWWWWWWWW From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: <sip:0788888888@172.20.20.111>;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 INVITE Content-Length: 0 [9] 15:39:22.350 SIP: Using outbound proxy sip:fs1.ims.swisscom.ch because of registration trunk [5] 15:39:22.356 PACK: SIP Tx 195.186.128.164:5060: INVITE sip:0788888888@swisscom.ch;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.20.20.111:5060;branch=VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV From: <sip:NC-USERNAME@swisscom.ch@swisscom.ch>;tag=625718133 To: <sip:0788888888@swisscom.ch> Call-ID: 212c09a6@pbx CSeq: 16904 INVITE Max-Forwards: 70 Contact: <sip:NC-USERNAME@172.20.20.111:5060;transport=udp> Allow-Events: refer Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Remote-Party-ID: "vorname nachname" <sip:100@swisscom.ch> Content-Type: application/sdp Content-Length: 297 v=0 o=- 1656444696 1656444696 IN IP4 172.20.20.111 s=- c=IN IP4 172.20.20.111 t=0 0 m=audio 49312 RTP/AVP 0 8 9 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [7] 15:39:22.356 SIP: Use codec PCMU/8000 for call-leg 4 [5] 15:39:22.360 PACK: SIP Tx 192.168.1.101:55708: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.1.101:55708;rport=55708;branch=WWWWWWWWWWWWWWWWWWWWWW From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: <sip:0788888888@172.20.20.111>;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 INVITE Contact: <sip:100@172.20.20.111:5060> Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Require: 100rel RSeq: 1 Content-Type: application/sdp Content-Length: 283 v=0 o=- 14068563 14068563 IN IP4 172.20.20.111 s=- c=IN IP4 172.20.20.111 t=0 0 m=audio 51070 RTP/AVP 0 8 9 102 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:102 telephone-event/8000 a=fmtp:102 0-15 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 15:39:22.362 PACK: SIP Rx 192.168.1.101:55708: PRACK sip:100@172.20.20.111:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:55708;rport;branch=UUUUUUUUUUUUUUUUUUUUUUUUUUUU Max-Forwards: 70 From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: sip:0788888888@172.20.20.111;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28788 PRACK RAck: 1 28787 INVITE Content-Length: 0 [5] 15:39:22.364 PACK: SIP Tx 192.168.1.101:55708: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.101:55708;rport=55708;branch=UUUUUUUUUUUUUUUUUUUUUUUUUUUU From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: <sip:0788888888@172.20.20.111>;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28788 PRACK Contact: <sip:100@172.20.20.111:5060> User-Agent: Vodia-PBX/66.0.2 P-Asserted-Identity: <sip:0788888888@localhost> Content-Length: 0 [5] 15:39:22.855 PACK: SIP Tx 195.186.128.164:5060: INVITE sip:0788888888@swisscom.ch;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.20.20.111:5060;branch=VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV From: <sip:NC-USERNAME@swisscom.ch@swisscom.ch>;tag=625718133 To: <sip:0788888888@swisscom.ch> Call-ID: 212c09a6@pbx CSeq: 16904 INVITE Max-Forwards: 70 Contact: <sip:NC-USERNAME@172.20.20.111:5060;transport=udp> Allow-Events: refer Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Remote-Party-ID: "vorname nachname" <sip:100@swisscom.ch> Content-Type: application/sdp Content-Length: 297 v=0 o=- 1656444696 1656444696 IN IP4 172.20.20.111 s=- c=IN IP4 172.20.20.111 t=0 0 m=audio 49312 RTP/AVP 0 8 9 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 15:39:32.151 PACK: Last message repeated 4 times [5] 15:39:32.151 PACK: SIP Rx 192.168.1.101:55708: CANCEL sip:0788888888@172.20.20.111 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:55708;rport;branch=WWWWWWWWWWWWWWWWWWWWWW Max-Forwards: 70 From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: sip:0788888888@172.20.20.111 Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 CANCEL User-Agent: Telephone 1.5.1 Content-Length: 0 [5] 15:39:32.154 PACK: SIP Tx 192.168.1.101:55708: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.1.101:55708;rport=55708;branch=WWWWWWWWWWWWWWWWWWWWWW From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: <sip:0788888888@172.20.20.111>;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 CANCEL Contact: <sip:100@172.20.20.111:5060> User-Agent: Vodia-PBX/66.0.2 P-Asserted-Identity: <sip:0788888888@localhost> Content-Length: 0 [5] 15:39:32.156 PACK: SIP Tx 192.168.1.101:55708: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 192.168.1.101:55708;rport=55708;branch=WWWWWWWWWWWWWWWWWWWWWW From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: <sip:0788888888@172.20.20.111>;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 INVITE Contact: <sip:100@172.20.20.111:5060> Supported: 100rel, replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 P-Asserted-Identity: <sip:0788888888@localhost> Content-Length: 0 [8] 15:39:32.159 GENE: Remove leg 5: Call port 4, SIP call id YYYYYYYYYYYYYYYYYYYYYYYYYYY [5] 15:39:32.162 PACK: SIP Tx 195.186.128.164:5060: CANCEL sip:0788888888@swisscom.ch;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.20.20.111:5060;branch=VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV From: <sip:NC-USERNAME@swisscom.ch@swisscom.ch>;tag=625718133 To: <sip:0788888888@swisscom.ch> Call-ID: 212c09a6@pbx CSeq: 16904 CANCEL Max-Forwards: 70 Remote-Party-ID: "vorname nachname" <sip:100@swisscom.ch> Content-Length: 0 [5] 15:39:32.163 PACK: SIP Rx 192.168.1.101:55708: ACK sip:0788888888@172.20.20.111 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.101:55708;rport;branch=WWWWWWWWWWWWWWWWWWWWWW Max-Forwards: 70 From: "mibo" <sip:100@172.20.20.111>;tag=ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ To: sip:0788888888@172.20.20.111;tag=ej6zkbin7q Call-ID: YYYYYYYYYYYYYYYYYYYYYYYYYYY CSeq: 28787 ACK Content-Length: 0 [5] 15:39:32.662 PACK: SIP Tx 195.186.128.164:5060: CANCEL sip:0788888888@swisscom.ch;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.20.20.111:5060;branch=VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV From: <sip:NC-USERNAME@swisscom.ch@swisscom.ch>;tag=625718133 To: <sip:0788888888@swisscom.ch> Call-ID: 212c09a6@pbx CSeq: 16904 CANCEL Max-Forwards: 70 Remote-Party-ID: "vorname nachname" <sip:100@swisscom.ch> Content-Length: 0

--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.

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).

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 dem "inOne" genannten anschluss betreiben koennen... vom allerfeinsten waere dann natuerlich wenn wir eines tages ein vorgefertigtes template fuer "Swisscom inOne" beim trunk einrichten haetten bei welchem man bloss noch user, nummer und passwort eingeben koennte. was einwandfrei klappt mit der Vodia PBX: anmeldung und gespraeche inbound. jedoch kann ich ums verrecken keine outbound gespraeche aufbauen :-/ hier mal als hinweis die konfiguration welche bei FreePBX funktioniert: PEER Details: user=+41MeineNummer type=peer srvlookup=yes secret=MeinPasswort outboundproxy=fs1.ims.swisscom.ch nat=yes insecure=invite,port host=swisscom.ch fromuser=+41MeineNummer fromdomain=swisscom.ch dtmfmode=auto defaultuser=MeinUsername@swisscom.ch canreinvite=no disallow=all allow=alaw&ulaw&g729&gsm&slinear&ulaw User Context: +41MeineNummer USER Details: type=peer host=fs1.ims.swisscom.ch fromdomain=swisscom.ch disallow=all allow=alaw&ulaw&g729&gsm&slinear&ulaw Register String: +41MeineNummer@swisscom.ch:MeinPasswort:MeinUsername@fs1.ims.swisscom.ch/+41MeineNummer irgendjemand irgendwelche ideen? schoene gruesse aus der schweiz! grz, m.

just a heads up: behavior is still the same with release 63 (fresh install of V 63 on unmolested Raspbian).

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...

yes, as stated above: 62.1 (Build Date: Apr 11 2019 17:13:20)

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.

oh, there's a new Raspbian release from a few days ago. will try that, too.

nope, still the same: SSH connection refused after update 62.0 -> 62.1

I'm pretty sure I did a reboot... okay, will start from scratch. fresh install again. back in a few minutes.

hm, also hier immer noch das gleiche... jungraeuliches Raspbian auf Raspberry Pi 3 Model B+ Vodia Release 62.0 gemaess anleitung installiert SSH OK update via web GUI auf 62.1 (Build Date: Apr 11 2019 17:13:20) durchgefuehrt SSH Connection refused

der fehler besteht nach wie vor: Software-Version: 62.1 (Vodia mini PBX (Debian)) Build Date: Apr 8 2019 14:22:24 (Raspbian Stretch und anschiessend Vodia 62.1 frisch installiert)

aktuell bekomme ich beim installieren 62.1 (Vodia mini PBX (Debian)) Build Date Mar 25 2019 13:54:39 ich habe jetzt mal openssh-server deinstalliert und nutze stattdessen Dropbear SSH, das funktioniert.

I can confirm that this is fixed (release 62.1 build date Mar 29 2019 15:49:34)

okay, I tried it again (on a virtual machine this time). freshly installed debian stretch 64 bit. edited "install-debian.sh" so it'll download release 62.1 and installed it according to the manual. login to the web GUI, set a new password for the PBX, logged out -> unable to login with the new password, logging in without password is still possible.

isn't the version downloaded during install the same as the one from the update? I installed 62.1 without updating it, this was today in the morning (march 29th).

soll ich fehler betreffend 62.1 ueberhaupt melden? frische installation von 62.1 (mittels angepasstem install-debian.sh) auf debian64 lizenz installiert wenn ich in der web GUI das admin passwort anpasse und speichere greift die einstellung nicht. mit dem neu konfigurierten passwort kann man sich hinterher nicht anmelden, ohne passwort hingegen schon. fehler tritt auf release 62.0 (erneut frisch installiert auf debian64) nicht auf.

von einem frisch aufgespielten Raspbian Stretch (2018-11-13-raspbian-stretch-lite.img) /lib/systemd/system/ssh.service [Unit] Description=OpenBSD Secure Shell server After=network.target auditd.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run [Service] EnvironmentFile=-/etc/default/ssh ExecStartPre=/usr/sbin/sshd -t ExecStart=/usr/sbin/sshd -D $SSHD_OPTS ExecReload=/usr/sbin/sshd -t ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartPreventExitStatus=255 Type=notify [Install] WantedBy=multi-user.target Alias=sshd.service /etc/ssh/sshd_config wobei ich da eh ueblicherweise "PermitRootLogin yes" einstelle # $OpenBSD: sshd_config,v 1.100 2016/08/15 12:32:04 naddy Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options override the # default value. #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_ecdsa_key #HostKey /etc/ssh/ssh_host_ed25519_key # Ciphers and keying #RekeyLimit default none # Logging #SyslogFacility AUTH #LogLevel INFO # Authentication: #LoginGraceTime 2m #PermitRootLogin prohibit-password #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 #PubkeyAuthentication yes # Expect .ssh/authorized_keys2 to be disregarded by default in future. #AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2 #AuthorizedPrincipalsFile none #AuthorizedKeysCommand none #AuthorizedKeysCommandUser nobody # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no # Change to yes to enable challenge-response passwords (beware issues with # some PAM modules and threads) ChallengeResponseAuthentication no # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes #GSSAPIStrictAcceptorCheck yes #GSSAPIKeyExchange no # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. UsePAM yes #AllowAgentForwarding yes #AllowTcpForwarding yes #GatewayPorts no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PermitTTY yes PrintMotd no #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation sandbox #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS no #PidFile /var/run/sshd.pid #MaxStartups 10:30:100 #PermitTunnel no #ChrootDirectory none #VersionAddendum none # no default banner path #Banner none # Allow client to pass locale environment variables AcceptEnv LANG LC_* # override default of no subsystems Subsystem sftp /usr/lib/openssh/sftp-server # Example of overriding settings on a per-user basis #Match User anoncvs # X11Forwarding no # AllowTcpForwarding no # PermitTTY no # ForceCommand cvs server

release 62.1 direkt auf einem frischen Raspbian Jessie (anstelle Stretch) installiert und alles funktioniert wie es soll. benutztes image: 2017-07-05-raspbian-jessie-lite.img Raspbian Jessie bootet aber leider nicht mehr auf den neuen Raspberry Pi 3 Model B+

noch eine erkenntnis: wenn man direkt mittels angepasstem "install-mini3.sh" den release 62.1 auf einem frischen Raspbian installiert, geht SSH nach erfolgreicher installation und reboot ebenfalls nicht mehr.