Search
402 results for “pbx”
-
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!
-
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!
-
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!
-
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!
-
Anyone familiar with old SIP equipment? Specifically an Audiocodes MP-1xx FXS?
I have a two port 112 unit that I'm trying to get port 1 to call port 2 without having a PBX or a SIP registration. Not sure why there isn't some fallback configuration or paging option.
I know a Cisco ATA would be the choice for this, but this is what I have at the moment :)
-
What am I fishing for here? #telephone calls 😁
This is all above board (as its internal monitoring)- but old tech way is surprisingly most GDPR compliant - it separates call metadata (which I don't want, I can get that from other sources) from audio which I do want.
I'm not even interested in exact *content* of calls here, what I'm monitoring is overall audio quality to make sure nothing is glitched / daleked at our end now calls are 100% #VOIP (alas, I can't do anything about ropey #LTE networks our staff and service users might be using)
I'm also testing how #Grandstream #ATA and cloud #PBX handle long telephone calls (such as intercept feed from the other #PBX)
Contents of #tape are not kept long term, they are be erased once I've assessed the audio quality..
-
RE: https://infosec.exchange/@enablesecurity/116300709031150946
VoIP/WebRTC security has needed a DVWA equivalent for a long time. We built DVRTC: full dockerized VoIP stack, intentionally vulnerable, 7 guided exercises.
Live instance at pbx1.dvrtc.net — try it now.
https://www.enablesecurity.com/blog/introducing-dvrtc-damn-vulnerable-real-time-communications/
#infosec #webrtc #voipsecurity #penetrationtesting #training
-
RE: https://infosec.exchange/@enablesecurity/116300709031150946
VoIP/WebRTC security has needed a DVWA equivalent for a long time. We built DVRTC: full dockerized VoIP stack, intentionally vulnerable, 7 guided exercises.
Live instance at pbx1.dvrtc.net — try it now.
https://www.enablesecurity.com/blog/introducing-dvrtc-damn-vulnerable-real-time-communications/
#infosec #webrtc #voipsecurity #penetrationtesting #training
-
RE: https://infosec.exchange/@enablesecurity/116300709031150946
VoIP/WebRTC security has needed a DVWA equivalent for a long time. We built DVRTC: full dockerized VoIP stack, intentionally vulnerable, 7 guided exercises.
Live instance at pbx1.dvrtc.net — try it now.
https://www.enablesecurity.com/blog/introducing-dvrtc-damn-vulnerable-real-time-communications/
#infosec #webrtc #voipsecurity #penetrationtesting #training
-
RE: https://infosec.exchange/@enablesecurity/116300709031150946
VoIP/WebRTC security has needed a DVWA equivalent for a long time. We built DVRTC: full dockerized VoIP stack, intentionally vulnerable, 7 guided exercises.
Live instance at pbx1.dvrtc.net — try it now.
https://www.enablesecurity.com/blog/introducing-dvrtc-damn-vulnerable-real-time-communications/
#infosec #webrtc #voipsecurity #penetrationtesting #training
-
RE: https://infosec.exchange/@enablesecurity/116300709031150946
VoIP/WebRTC security has needed a DVWA equivalent for a long time. We built DVRTC: full dockerized VoIP stack, intentionally vulnerable, 7 guided exercises.
Live instance at pbx1.dvrtc.net — try it now.
https://www.enablesecurity.com/blog/introducing-dvrtc-damn-vulnerable-real-time-communications/
#infosec #webrtc #voipsecurity #penetrationtesting #training
-
Le financement pour le jeu de rôle Téméraire est lancé.
Et c'est déjà un succès !
On vous raconte ça ici : https://buff.ly/PBxMSxv
-
Just over a month and I've tamed all the #trunks (with abundant snake heads at the end), made sure 1500+ #blighters are yeeted (with more trying every day) got inter #PBX #trunk working between on-premises and cloud #FreePBX - just waiting for porting of first analogue number to check this (and CLID presentation) works and then main office one can follow.
Took many late evenings, a lot of research of everything from old #BritishTelecom training manuals to some from Universities in India and the Indian telecom companies, and I've learned a lot more about #SIP even since 2008 when I built the first #VOIP #PBX used at work.
Thankfully #routers seem to handle #SIP over #NAT a lot better than they used to (even got an extension it working over #LTE with #Linphone)
-
Just over a month and I've tamed all the #trunks (with abundant snake heads at the end), made sure 1500+ #blighters are yeeted (with more trying every day) got inter #PBX #trunk working between on-premises and cloud #FreePBX - just waiting for porting of first analogue number to check this (and CLID presentation) works and then main office one can follow.
Took many late evenings, a lot of research of everything from old #BritishTelecom training manuals to some from Universities in India and the Indian telecom companies, and I've learned a lot more about #SIP even since 2008 when I built the first #VOIP #PBX used at work.
Thankfully #routers seem to handle #SIP over #NAT a lot better than they used to (even got an extension it working over #LTE with #Linphone)
-
Just over a month and I've tamed all the #trunks (with abundant snake heads at the end), made sure 1500+ #blighters are yeeted (with more trying every day) got inter #PBX #trunk working between on-premises and cloud #FreePBX - just waiting for porting of first analogue number to check this (and CLID presentation) works and then main office one can follow.
Took many late evenings, a lot of research of everything from old #BritishTelecom training manuals to some from Universities in India and the Indian telecom companies, and I've learned a lot more about #SIP even since 2008 when I built the first #VOIP #PBX used at work.
Thankfully #routers seem to handle #SIP over #NAT a lot better than they used to (even got an extension it working over #LTE with #Linphone)
-
Just over a month and I've tamed all the #trunks (with abundant snake heads at the end), made sure 1500+ #blighters are yeeted (with more trying every day) got inter #PBX #trunk working between on-premises and cloud #FreePBX - just waiting for porting of first analogue number to check this (and CLID presentation) works and then main office one can follow.
Took many late evenings, a lot of research of everything from old #BritishTelecom training manuals to some from Universities in India and the Indian telecom companies, and I've learned a lot more about #SIP even since 2008 when I built the first #VOIP #PBX used at work.
Thankfully #routers seem to handle #SIP over #NAT a lot better than they used to (even got an extension it working over #LTE with #Linphone)
-
Just over a month and I've tamed all the #trunks (with abundant snake heads at the end), made sure 1500+ #blighters are yeeted (with more trying every day) got inter #PBX #trunk working between on-premises and cloud #FreePBX - just waiting for porting of first analogue number to check this (and CLID presentation) works and then main office one can follow.
Took many late evenings, a lot of research of everything from old #BritishTelecom training manuals to some from Universities in India and the Indian telecom companies, and I've learned a lot more about #SIP even since 2008 when I built the first #VOIP #PBX used at work.
Thankfully #routers seem to handle #SIP over #NAT a lot better than they used to (even got an extension it working over #LTE with #Linphone)
-
As an experiment, I asked #MS365 #Copilot to explain how to set up #SIP trunk on #FreePBX using #PJSIP (consider that I have already successfully set up several of these, to external providers and an inter-PBX line between two servers).
Results it returned were horribly mangled and mixed up from various providers sites, if you followed them the trunk likely won't work at all, and even if it did it would end up in completely wrong context/dialplan.
It didn't mention such things as fromuser and took a few prompts to point out potential firewall issues.
You need to know (or learn) the basics of #telephony before starting, or else it will all go tits up very quickly - #AI is still no substitute for "boots on the ground" who have put in research for what they are trying to achieve..
-
Three Sweden targets broader B2B base with mobile-first communications tier
Operator builds tiered proposition on Telavox Platform, aiming to move beyond PBX-centric UCaaS and embed AI into business…
#Sweden #Sverige #SE #Europe #Europa #EU #artificialintelligenceAI #CloudPBX #nyheter #sweden #Telavox #ThreeSweden #UCaaS #voiceservices #Voice-over-IMS
https://www.europesays.com/2798819/ -
Building new #FreePBX #Asterisk #VOIP server (about 10 years since I built the last one) was also an eye-opener of how much #tech world seems to have been deskilled with the rush to #cloud (even before AI) - it seems fewer folk want to build a server from bare metal or even VPS and are flocking to proprietary cloud #PBX (that nearly all run Asterisk under the hood anyway), it might be that #telephony is "uncool" but also remaining engineers have simply stopped helping one another, perhaps not wanting to aid the competition?
I didn't even get much AI slop when searching for info on community forums, as there is so little there and many unanswered threads..
-
#Telephone set #BritishTelecom 8746 now with replaced 21A microphone insert, working correctly with #Grandstream #HT802 v2 ATA linked to #FreePBX I built on cloud VPS - accepts both #MF (tone) and #LoopDisconnect #dialling (although dialling a full UK mobile number is quite a long process and I had to make sure the timer was at least 4 seconds (or the digits get sent to register before you've dialled any 0 and call fails due to wrong number being sent to #PBX !)
Ring voltage (set to 55V RMS) is strong enough to ring the 4k bell in 8746
So currently this corner of the office looks like its back in 1980s 😁
-
#Telephone set #BritishTelecom 8746 now with replaced 21A microphone insert, working correctly with #Grandstream #HT802 v2 ATA linked to #FreePBX I built on cloud VPS - accepts both #MF (tone) and #LoopDisconnect #dialling (although dialling a full UK mobile number is quite a long process and I had to make sure the timer was at least 4 seconds (or the digits get sent to register before you've dialled any 0 and call fails due to wrong number being sent to #PBX !)
Ring voltage (set to 55V RMS) is strong enough to ring the 4k bell in 8746
So currently this corner of the office looks like its back in 1980s 😁
-
#Telephone set #BritishTelecom 8746 now with replaced 21A microphone insert, working correctly with #Grandstream #HT802 v2 ATA linked to #FreePBX I built on cloud VPS - accepts both #MF (tone) and #LoopDisconnect #dialling (although dialling a full UK mobile number is quite a long process and I had to make sure the timer was at least 4 seconds (or the digits get sent to register before you've dialled any 0 and call fails due to wrong number being sent to #PBX !)
Ring voltage (set to 55V RMS) is strong enough to ring the 4k bell in 8746
So currently this corner of the office looks like its back in 1980s 😁
-
#Telephone set #BritishTelecom 8746 now with replaced 21A microphone insert, working correctly with #Grandstream #HT802 v2 ATA linked to #FreePBX I built on cloud VPS - accepts both #MF (tone) and #LoopDisconnect #dialling (although dialling a full UK mobile number is quite a long process and I had to make sure the timer was at least 4 seconds (or the digits get sent to register before you've dialled any 0 and call fails due to wrong number being sent to #PBX !)
Ring voltage (set to 55V RMS) is strong enough to ring the 4k bell in 8746
So currently this corner of the office looks like its back in 1980s 😁
-
CW: lots of nerd talk about dreamcast and phone lines with dubious delivery
In the service of totally overdoing some #Dreamcast #RetroGaming, I've successfully patched the #DreamPi gateway to be less useful. Buckle up, because this is a kinda long post with little in the way of delivery. :bec_smug:
Normally the DreamPi throws its modem into voice mode, plays a dial tone to fake out the dreamcast, listens to the digits dialed, and then switches to data mode and kicks off a handshake. Stays off-hook the entire time.
This makes sense if you're using an electrically-simple Line Voltage Inducer and a straight connection between the Dreamcast and the modem for minimum part count get-up-and-go. It's actually a really clever workaround.
My tweak adjusts the modem behavior such that it stays on-hook until it detects an incoming ring, then answers and jumps straight into data mode.
This change was made because presently we're using a Valcom DLE-200B phone line simulator which does provide 'local' tone, ringing voltage, and ringdown.
This necessarily means that we lose out on capturing the dialed digits, but it turns out we don't need those at all for pretty much any of the PPP-based games with central servers, and I'm not interested in playing anything outside of that scope.
So now we have a dreampi that can only work in PPP mode and it requires a line simulator to work correctly. Why?
All, ultimately, so that we can hook the DreamPi and two dreamcasts up to a TDM-based #PBX instead of the line simulator, wherein either of the latter can dial the former, thinking they're dialing Dreamcast Online Services. It goes through the whole ring-in process, which terminates at DreamPi, handshakes, and tunnels to Dreamcast Live -- getting us the goods.
And there's lots of Friday left to go :3
#RetroGaming #OtherNetworks #PhoneLab #RetroLab #POTS #Modem
-
CW: lots of nerd talk about dreamcast and phone lines with dubious delivery
In the service of totally overdoing some #Dreamcast #RetroGaming, I've successfully patched the #DreamPi gateway to be less useful. Buckle up, because this is a kinda long post with little in the way of delivery. :bec_smug:
Normally the DreamPi throws its modem into voice mode, plays a dial tone to fake out the dreamcast, listens to the digits dialed, and then switches to data mode and kicks off a handshake. Stays off-hook the entire time.
This makes sense if you're using an electrically-simple Line Voltage Inducer and a straight connection between the Dreamcast and the modem for minimum part count get-up-and-go. It's actually a really clever workaround.
My tweak adjusts the modem behavior such that it stays on-hook until it detects an incoming ring, then answers and jumps straight into data mode.
This change was made because presently we're using a Valcom DLE-200B phone line simulator which does provide 'local' tone, ringing voltage, and ringdown.
This necessarily means that we lose out on capturing the dialed digits, but it turns out we don't need those at all for pretty much any of the PPP-based games with central servers, and I'm not interested in playing anything outside of that scope.
So now we have a dreampi that can only work in PPP mode and it requires a line simulator to work correctly. Why?
All, ultimately, so that we can hook the DreamPi and two dreamcasts up to a TDM-based #PBX instead of the line simulator, wherein either of the latter can dial the former, thinking they're dialing Dreamcast Online Services. It goes through the whole ring-in process, which terminates at DreamPi, handshakes, and tunnels to Dreamcast Live -- getting us the goods.
And there's lots of Friday left to go :3
#RetroGaming #OtherNetworks #PhoneLab #RetroLab #POTS #Modem
-
CW: lots of nerd talk about dreamcast and phone lines with dubious delivery
In the service of totally overdoing some #Dreamcast #RetroGaming, I've successfully patched the #DreamPi gateway to be less useful. Buckle up, because this is a kinda long post with little in the way of delivery. :bec_smug:
Normally the DreamPi throws its modem into voice mode, plays a dial tone to fake out the dreamcast, listens to the digits dialed, and then switches to data mode and kicks off a handshake. Stays off-hook the entire time.
This makes sense if you're using an electrically-simple Line Voltage Inducer and a straight connection between the Dreamcast and the modem for minimum part count get-up-and-go. It's actually a really clever workaround.
My tweak adjusts the modem behavior such that it stays on-hook until it detects an incoming ring, then answers and jumps straight into data mode.
This change was made because presently we're using a Valcom DLE-200B phone line simulator which does provide 'local' tone, ringing voltage, and ringdown.
This necessarily means that we lose out on capturing the dialed digits, but it turns out we don't need those at all for pretty much any of the PPP-based games with central servers, and I'm not interested in playing anything outside of that scope.
So now we have a dreampi that can only work in PPP mode and it requires a line simulator to work correctly. Why?
All, ultimately, so that we can hook the DreamPi and two dreamcasts up to a TDM-based #PBX instead of the line simulator, wherein either of the latter can dial the former, thinking they're dialing Dreamcast Online Services. It goes through the whole ring-in process, which terminates at DreamPi, handshakes, and tunnels to Dreamcast Live -- getting us the goods.
And there's lots of Friday left to go :3
#RetroGaming #OtherNetworks #PhoneLab #RetroLab #POTS #Modem
-
CW: lots of nerd talk about dreamcast and phone lines with dubious delivery
In the service of totally overdoing some #Dreamcast #RetroGaming, I've successfully patched the #DreamPi gateway to be less useful. Buckle up, because this is a kinda long post with little in the way of delivery. :bec_smug:
Normally the DreamPi throws its modem into voice mode, plays a dial tone to fake out the dreamcast, listens to the digits dialed, and then switches to data mode and kicks off a handshake. Stays off-hook the entire time.
This makes sense if you're using an electrically-simple Line Voltage Inducer and a straight connection between the Dreamcast and the modem for minimum part count get-up-and-go. It's actually a really clever workaround.
My tweak adjusts the modem behavior such that it stays on-hook until it detects an incoming ring, then answers and jumps straight into data mode.
This change was made because presently we're using a Valcom DLE-200B phone line simulator which does provide 'local' tone, ringing voltage, and ringdown.
This necessarily means that we lose out on capturing the dialed digits, but it turns out we don't need those at all for pretty much any of the PPP-based games with central servers, and I'm not interested in playing anything outside of that scope.
So now we have a dreampi that can only work in PPP mode and it requires a line simulator to work correctly. Why?
All, ultimately, so that we can hook the DreamPi and two dreamcasts up to a TDM-based #PBX instead of the line simulator, wherein either of the latter can dial the former, thinking they're dialing Dreamcast Online Services. It goes through the whole ring-in process, which terminates at DreamPi, handshakes, and tunnels to Dreamcast Live -- getting us the goods.
And there's lots of Friday left to go :3
#RetroGaming #OtherNetworks #PhoneLab #RetroLab #POTS #Modem
-
CW: lots of nerd talk about dreamcast and phone lines with dubious delivery
In the service of totally overdoing some #Dreamcast #RetroGaming, I've successfully patched the #DreamPi gateway to be less useful. Buckle up, because this is a kinda long post with little in the way of delivery. :bec_smug:
Normally the DreamPi throws its modem into voice mode, plays a dial tone to fake out the dreamcast, listens to the digits dialed, and then switches to data mode and kicks off a handshake. Stays off-hook the entire time.
This makes sense if you're using an electrically-simple Line Voltage Inducer and a straight connection between the Dreamcast and the modem for minimum part count get-up-and-go. It's actually a really clever workaround.
My tweak adjusts the modem behavior such that it stays on-hook until it detects an incoming ring, then answers and jumps straight into data mode.
This change was made because presently we're using a Valcom DLE-200B phone line simulator which does provide 'local' tone, ringing voltage, and ringdown.
This necessarily means that we lose out on capturing the dialed digits, but it turns out we don't need those at all for pretty much any of the PPP-based games with central servers, and I'm not interested in playing anything outside of that scope.
So now we have a dreampi that can only work in PPP mode and it requires a line simulator to work correctly. Why?
All, ultimately, so that we can hook the DreamPi and two dreamcasts up to a TDM-based #PBX instead of the line simulator, wherein either of the latter can dial the former, thinking they're dialing Dreamcast Online Services. It goes through the whole ring-in process, which terminates at DreamPi, handshakes, and tunnels to Dreamcast Live -- getting us the goods.
And there's lots of Friday left to go :3
#RetroGaming #OtherNetworks #PhoneLab #RetroLab #POTS #Modem