home.social

#trunks — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #trunks, aggregated by home.social.

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

    #VOIP #telephony

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

    #VOIP #telephony

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

    #VOIP #telephony

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

    #VOIP #telephony

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

    #VOIP #telephony

  6. I really wish all the fediverse instances bring support for reactions😄. Coz now it's just a favourite button and iirc some instances like misskey etc have reactions support.
    I love reactions, coz of the versatile ways to react to a toot with emojis. 😅

    I see some clients like trunks, fedilab have reaction feature 🤔 so if I recat to some mastodon toots will others see the reaction?
    @trunksapp
    @apps

    #mastodon #fediverse #reactions #feature
    #expression #fedilab #trunks

  7. Now the other two are ported - all the #analogue #trunks are ceased and all traffic to and from the #PSTN from this #PBX is now #VOIP (using #PJSIP trunks on #FreePBX )

    I disconnected all the analogue lines as #Openreach leave battery on them, that way they show as RED alarm on #Asterisk and won't be selected for any calls (worst case is they return a busy trunk status and the route will go to the next trunk, but I've taken away all the analogue circuits from every PSTN route)

    #Telecoms #Telephony

  8. been checking last few days #blighters who are kicked out trying to get at our #VOIP #PBX - they don't even seem to be wanting to use the #SIP #trunks for getting free #telephone calls for actually talking to people (even spam/coldcalls), but appear to be edgelords attempting to use them for their own private vendetta and DDOS some individual/business phone as INVITE attempts are all to the same USA number(s)

    I'm assuming its not someone trying to call their *own* phone to find when someone *has* left a trunk open, as that would surely create a data trail authorities could pick up on?

    #hacking #cybercrime #cybersecurity