Jump to content

martin

Members
  • Content Count

    202
  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Profiles

Forums

Resource Library: Monster UI Apps for KAZOO

Calendar

Everything posted by martin

  1. Billing Services (and service plans) have received a major overhaul in 4.3. APIs have changed for interacting with services so if any one has built on top of the `service_plans` API, they will need to take note and adjust their code. Cant find updated docs on this
  2. can u explain the use case for funny money and real money? I was using kazoo in 2016/17 and am trying to get back up to speed
  3. u normally use srv records in your dns to map a single domainname to multiple ip endpoints (your kazoo installs). If u have different zones and one is unreachable your calls and clients will be automaticly mapped to an other zone. If your did provider zallows you to put a domain name as destination u should be fine, if its only an ip address, your provider probably has a fallbasck solution, such as different destination ip addresses as destination. I hope i understood ur question. About srv records: borrowed from https://www.onsip.com/voip-resources/voip-fundamentals/dns-srv-records-sip What are SIP DNS SRV records? Let’s say your name is Al and you work for a company called Acme Corp. Your company has recently signed up for a corporate VoIP phone system and you’re given a SIP address, Al@acme.com. In an ideal world, your friends and colleagues who are also familiar with VoIP know that they can dial Al@acme.com to reach you wherever you have a device registered. How does this work? Dialing by domain names allows you to have a public SIP address that follows you much like your email address would. It doesn’t really matter where you are or what device you use; as long as you’re ‘logged in’ (registered), SIP communications will be redirected to your current location. A Domain Name Server (DNS) SRV record for SIP does the same thing as a mail exchange record for email. When someone calls you at Al@acme.com, the SRV record tells their SIP phone to do so by connecting to the domain belonging to your VoIP phone system (SIP) provider. This does two things for SIP providers and SIP users: 1. Greater stability From the RFC: If for some reason the ‘host’ with the highest priority cannot be reached, the SIP phone or proxy trying to reach the user within the domain will attempt to reach the next host defined within the SRV record. 2. Allows SIP users to get their own domains for their SIP addresses, regardless of the domain of their SIP provider We refer to this as SIP service or SIP hosting, and it’s a feature of an OnSIP account. OnSIP runs several SIP proxy servers, which can handle SIP users in multiple domains just like a mail server handles e-mail for multiple domains. SIP DNS SRV record settings To use OnSIP's SIP hosting, the zone file in the DNS SRV records of the user’s domain (acme.com) needs to point to sip.onsip.com. Calls to the user's domain will then be automatically redirected to an OnSIP SIP proxy. Here is what the DNS SRV record looks like: Service: SIP Protocol: UDP Name: acme.com (your domain name goes here) Priority: Weight: Port: 5060 Target: sip.onsip.com TTL: 1 hour Example DNS SRV record The following is an SRV DNS Lookup of sip.voice.google.com. As you can see below, the query returns 5 hostnames for inbound SIP traffic to that domain. Google Voice UDP Record $ dig _sip._udp.sip.voice.google.com SRV ; <<>> DiG 9.6.0-APPLE-P2 <<>> _sip._udp.sip.voice.google.com SRV ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8463 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 9 ;; QUESTION SECTION: ;_sip._udp.sip.voice.google.com. IN SRV ;; ANSWER SECTION: _sip._udp.sip.voice.google.com. 86400 IN SRV 20 1 5060 alt1.voice-sip.l.google.com. _sip._udp.sip.voice.google.com. 86400 IN SRV 10 1 5060 voice-sip.l.google.com. _sip._udp.sip.voice.google.com. 86400 IN SRV 50 1 5060 alt4.voice-sip.l.google.com. _sip._udp.sip.voice.google.com. 86400 IN SRV 30 1 5060 alt2.voice-sip.l.google.com. _sip._udp.sip.voice.google.com. 86400 IN SRV 40 1 5060 alt3.voice-sip.l.google.com. ;; AUTHORITY SECTION: google.com. 146471 IN NS ns3.google.com. google.com. 146471 IN NS ns2.google.com. google.com. 146471 IN NS ns1.google.com. google.com. 146471 IN NS ns4.google.com. ;; ADDITIONAL SECTION: alt1.voice-sip.l.google.com. 300 IN A 74.125.95.192 voice-sip.l.google.com. 300 IN A 74.125.95.192 alt4.voice-sip.l.google.com. 300 IN A 74.125.95.192 alt2.voice-sip.l.google.com. 300 IN A 74.125.95.192 alt3.voice-sip.l.google.com. 300 IN A 74.125.95.192 ns1.google.com. 342957 IN A 216.239.32.10 ns2.google.com. 342957 IN A 216.239.34.10 ns3.google.com. 319271 IN A 216.239.36.10 ns4.google.com. 342957 IN A 216.239.38.10 ;; Query time: 18 msec ;; SERVER: 207.172.3.8#53(207.172.3.8) ;; WHEN: Fri Mar 11 18:01:49 2011 ;; MSG SIZE rcvd: 494
  4. 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
  5. 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
  6. 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 )).
  7. 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
×
×
  • Create New...