☎️ Od trumny do trunku – Strowger, Asterisk i telefonia po godzinach
Krzysztof Strug, krótkofalowiec z @sp9fld, opowie o historii telefonii – od centrali Strowgera po współczesne rozwiązania #VoIP oparte na #Asterisk i #FreePBX. Nie zabraknie praktycznych przykładów i demo działającego środowiska.
📍 Gdzie? Wydział Matematyki i Informatyki UAM w Poznaniu
📅 Kiedy? sobota, 30 maja 2026
👉 Sprawdź agendę: https://piwo.sh/
🎟️ ODBIERZ DARMOWY BILET: https://app.evenea.pl/event/piwo2026/
@buersten
Ich würde eine reine SIP-Lösung z.B. #FreePBX oder von #Unifi nehmen.
Bei uns läuft eine FreePBX auf einem #RaspberryPi und als Clients verwenden wir Geräte von #Grandstream.
this is just cursed behaviour - whather #Groundwire registers when something else is using same external IP depends on what order SIP registrations arrive!
In this case its not a disaster as if I am on site I have far better devices available than my mobile phone to make SIP calls with (or can just use its LTE data), but its something worth being wary about as it could bite you in the arse if you are setting this up in somewhere where you don't have access to a different IP address to that shared by a #FreePBX inter-PBX #trunk
todays #VOIP discovery- - found another snakehead at the end of a #trunk - this time I am using #Acrobits #Groundwire #SIP client on #Android for a mobile extension on #cloud #PBX
Works *unless* I use a wifi connection with same external IP address as on-site PBX connected to cloud PBX (registered as PJSIP interPBX trunk and IP authentication).
When Groundwire extension tries to register as #endpoint on #FreePBX, #AOR records get all confused and #Groundwire shows "error"
tried adding external IP address to "Match (Permit)" in FreePBX extension entry - alas - this allows Groundwire to work but hoses outbound calls from the on-site PBX so had to be reverted (not a complete disaster as I can use the other wifi connection or LTE for Groundwire)
When setting #FreePBX with special #SIP Alert-Info on inbound route on DDI number, for distinctive ringing on #extensions linked to a ring group, beware that Alert-Info does *not* get transferred to extensions across intercompany #trunks (those with # at end of number)
Workaround to achieve this without custom #Asterisk dialplan (assuming you have outbound route with escape digits with direct route to inter-PBX #trunk)
* Set up ring group on remote #PBX with desired Alert-Info and extensions to be rung
* On ring group on original PBX, add local extensions list and at end route to remote ring group (for instance if ring group 610 and your escape code is 77 for remote PBX put 77610# in ring group extension list)
now distinctive ringing works across both PBX!
CVE Alert: CVE-2026-40520 - FreePBX - api - https://www.redpacketsecurity.com/cve-alert-cve-2026-40520-freepbx-api/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-40520 #freepbx #api