Jump to content
  1. Welcome to the 2600Hz Forums!

    1. Forum Rules & Announcements

      We're so glad you're here. Find out how to make your stay with us even more enjoyable.

      48
      posts
    2. 29
      posts
    3. 39
      posts
    4. Introductions

      ATTENTION: INTRODUCTION POST REQUIRED FOR NEW ACCOUNTS  

      Welcome to the 2600Hz Community and forums! In our perpetual effort to provide a better experience to our community and make everyone feel welcome, we ask that all new members make their inaugural post here, with an introduction and little bit about what brings you into the wonderful world of KAZOO and 2600Hz. Please include any details you deem relevant about yourself as a member and your organization, and how you're using KAZOO, and enjoy your stay! 

      239
      posts
  2. Platform Basics

    1. Product Discussion

      Collecting product guidance, documentation and demo media, and platform releases and announcements, the main question and discussion area for high level product topics and news. 

      4.6k
      posts
    2. Tips and Feedback

      Collecting tips and tricks, product feedback, and product focus groups and surveys, this area serves as a dialog on best practices and input for the KAZOO team. 

      1.3k
      posts
    3. Starting Out and Training

      Combining the pre-flight and 2600Hz training sections, this area will consolidate learning resources from the community. In addition, this area will serve as an additional discussion and feedback area for our newly launched Learning Management System (LMS), KAZOO Academy. Make sure to check back here for updates on that platform and to provide feedback and get community support! 

      246
      posts
  3. 2600Hz Mobile

    1. 2600Hz Mobile

      A place for discussion and questions about mobile devices, network, and general topics on 2600Hz mobile. 

      305
      posts
  4. 2600Hz Open Source Developers

    1. 522
      posts
  5. Vendor Discussion

    1. Hardware Endpoints

      A comprehensive discussion area for all devices used as endpoints on our platform. 

      404
      posts
    2. PSTN, Software, and Services

      Collecting topics on PSTN connectivity, software, and additional services.

      490
      posts
  • Upcoming Events

  • Posts

    • Soft transition from customers that are on office cloud based systems (with similar FromIP)  and cloud based system to kazoo onprem. Some have more advanced SDK driven call control applications to then dial 4 digit dial across and in terms of migrations.  CustA is on existing PBX but we are slowing added customer to kazoo so interim we do 4 digit dialing. Other PBX cluster systems without DID number to just dial xxx over a trunk like Mitel - Freepbx days but in this case its def different as anything and everything is DID driven.  We did also do a customer and  created fake DIDs 1xxx-xxx-xxxxt to insert/remove and auto assign  but there is a headache in managing this way for each customer on xxxx did. It did work for 1 Customer. and not dynamic to any callflow (unless maybe we modify the insert) OR what if we modified FS directory and did a domain matching based and takes out the dynamicness of Kazoo. I did do a route you suggested a few years back with adding Device as IP Auth and it woks that way for cust1.kaz.com  but when I add another customer from the same cloud Carrier. I Try to call from the same cloud system  custb.domain.com to kazoo cluster cust2.kaz.com domain routing but it chooses that account with the device IP auth. We thought of doing fake IPs per customer to auth based but hard to find a viable solution. i thought trunkstore would do the trick or potentially modifying the function doc in the lookup_did /lookup_user_flags but that is way far beyond my scope. Or maybe we look at a kamailio front proxy to route different things but If there is something like this what would be it called to even consider a feature request for the PBX trunkstore config. Like me i thought sip domain based auth routing it would just work ext to ext dialing.    
    • I guess I would ask what purpose the other tenent-based cloud system is providing and why you are using KAZOO (also a tenant-based cloud system) as a class 5 switch for them? Connectivity/trunkstore is more class 4 switching hence why extension dialing isn't supported
    • Oh so if we have multiple customer on the Same FROM IP (tenant based cloud system) this wont work.  will this be something on 5.x if it comes out to community.  workaround i swapped the from header as the to domain also from domain. and put a X-Header in to process via a middle proxy agent box but that seems hacky but it works but hoping it could treat it like a pbx trunk 4digit dialing across. 
  • Forum Statistics

    • Total Topics
      7.2k
    • Total Posts
      36.5k
×
×
  • Create New...