Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


martin last won the day on December 15 2017

martin had the most liked content!

Community Reputation

10 Newbie

About martin

  • Rank
    Advanced Member

Recent Profile Visitors

366 profile views
  1. martin

    Bring your own Carrier

    Thats true, one could sent a 1. specific header (or how we call that, flag?), depending if the carrier allows it of course. 2. Add an ip to your system and ask a Kazoo guru to explain how to force that ip to be used for this specific account. Inbound is no issue, but if Kazoo allows IP auth, and customers can bring their own carrier, then the risk is rather high to have duplicate ip adresses. If not 100% guarunteed. If u have 1000 clients, this problem will exist. U could do smth with outbound CLI but that also depends on the provider and could be spoofed. I dont know how Kazoo handles this, but my brain does not see a solution other then stated
  2. martin

    Bring your own Carrier

    But if the carrier allows the ip to be used only once it should still work right? If its IP auth and the request comes from your server IP then it would be permitted. So u need to put the IPs of your kamailio server into the white list or ip list of your carrier. Im rereading the question, and have a feeling i did not really get the question )) If i want to use an outbound carrier for outbound calls, and they do ip auth, i add the IPs to their system and thats it. I can make calls. Inbound is indeed a matter of putting the ips from where the call will be setup in the Kazoo ACLs. Please let me know if i did not understand the question correctly
  3. Hi"! Well as i am a captain by profession and do this to learn it sometimes goes over my head )) meaning that if a problem becomes more complex, and lets say has mmore then three or four levels, i get lost. I cant see the big picture anymore. So thats why im a good fir for writing simple docs, but in a workflow kind a way. Per example: Here is how to acieve this step: 1. do this 2. and that because of this or that 3. etc U can see the style in here, here, here and here. I remember that one of the sad things was, that at that time the idea of dealing with docs in a different way was new and just being pushed a bit. But for some things i needed help, and it was not available. of course, being naive and enthausiastic u want to move more fast then what is posible sometimes. And expected a bit too much from 2600hz perhaps, but... now i see this new forum, a lot of new faces and feel some more energy here )).
  4. Hi there, I was active before on the old google groups in 2014/15 (Beltex, Yumminova and created some supportdocs posted as Robert (Bremer) and after some time off ready to get started again, so pre flight is the best place to start )) The things that needed the most work in that time where billing, call rating and limits and such. I started writing a few articles in some support panel and would like to do so again, in the right place. Could someone send me the link to the new structure or explain it? (where to find the latest instructions, where to ask if i am writing about a subject but cant really continue) That way i can help the community a bit, and get myself up to speed again, a lot has been changed, but much seems the same )) Also... (and if not let me write howto on it )) Can we, out of the box already use: 1. callrating, 2. limits, 3. other payment processor then braintree 4. other DID provider then bandwith Thanks, Martin