Jump to content


Popular Content

Showing content with the highest reputation since 12/10/2017 in all areas

  1. 1 point
    Kazoo does the same thing as the carriers. If you try create an IP auth device in callflow and then try create another IP auth device with the same IP (even if it is in a different account), Kazoo will give you a "SIP IP already in use" error. Kazoo does not care about inbound IP from carriers as long as the IP is added to the ACL. It knows which account to route the call to based on the DID number. So again, that is the same as what most carriers seem to do.
  2. 1 point
    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
  3. 1 point
    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 )).