Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. Hi Dhruv, the SMS and XMPP settings are useless, all you have to do is to enable presence. note however that, a message will be delivered to all registered devices until one replies with success. for example, if you have 3 (A,B,C) registered devices belonging to a user with a sms enabled number, an incoming message to that number will be delivered to the A device, if it fails, its delivered to B device , if it fails its delivered to C device, if it fails its dropped. if device A is a yealink you may have receive the message (tho you expected it in bria). so, i would recommend to 1) create 2 new users 2) assigned the Bria devices to those users 3) move the sms enabled numbers to those users, or get new ones 4) try it out i have successfully worked with bria & linphone & yealink
  4. Last week
  5. Hi @Izabell balash, Chuck & I have been trying to get SMS working on our Bria’s apps without any success. We have written up the attached set of steps we have taken to set up both SMS and XMPP on our Bria mobile apps. We hope that you or another community member might see what we are missing. Thanks so much, Dhruv D3UC unable to get SMS working on Bria -- description of steps taken.pdf
  6. Hi, I have enabled voicemail transcription for my user but it doesn't have transcribe the VM in the email yet. I've also set send emails to an alternate address. Thanks, Dhruv
  7. Awesome - i will check this out - thanks for the quick reply
  8. Hi! 1) I used quickcall for this. https://docs.2600hz.com/supported/applications/crossbar/doc/quickcall/
  9. We have a CRM application and we want to add calling capacities to it. We are currently looking into Kazoo and Twillio. Our solution is a .NET winform app that embeds the CEFSharp web browser, so we can connect either way. Here are my questions… 1) Does Kazoo have an API we can use to make and retrieve calls? 2) Does Kazoo have a Softphone we can use to embed in our solution. Is it HTML / WebRTC based or other? Love to hear how others approached this and what the possibilities are... Thanks!!! Gary
  10. Earlier
  11. Thanks, Might not be that many commits but just need to know if we need to resubmit them or not.
  12. 2600HZ USER GUIDE – SETTING UP YOUR WHITE LABEL DNS NOTE: We recommend completing this setup prior to setting up any new accounts. This will ensure all accounts will use your white label domain. User Story A KAZOO reseller account wants to use their one of their own domain names in place of zswitch.net for white-labeling purposes. How this works On its most basic level, DNS points human readable “names” to machine readable “data”. These are called DNS records. The most basic of which (an A record) points a “name” such as www.2600hz.com to an IP address 23.239.13.252. More advanced records can tell phones what port numbers to use, what servers they should prefer most and least and what protocols to use (SRV and NAPTR records). 2600hz uses over a dozen of these records for its hosted KAZOO service, zswitch.net. Resellers wishing to white-label zswitch must configure their domain names to include all these records. In this guide, we will show you how to point your domain to a supported DNS provider (easyDNS), configure your records, then replicate those records to another DNS provider (Amazon Route 53) for extremely reliable white-labeled DNS configuration. Here’s an illustration: Disclaimer If you are very familiar with DNS, you may be aware that there are other services and methods you could use to implement your DNS. This purpose of this document is to provide as easy a path as possible for those who are not as familiar with DNS to successfully white-label without complicating the process by explaining all possibilities. You are free to use the services and methods that suit you best. Before you start Purchase a new domain name specifically for your white-label branding via a Domain registrar, such as https://godaddy.com https://tucowsdomains.com https://namecheap.com Setup an account at https://easydns.com NOTE: Some DNS providers also offer domain registrar services. Using a DNS provider’s built in registrar service can seem like it simplifies nameserver settings, however it’s generally best to keep your registrar service with a major provider to ensure the security of your domain registration. Make sure you have access to your login credentials for both services, as you will need to update them below. Overview This guide is set up in parts. Part 1 Enter basic company setup information in the KAZOO Branding app. Part 2 Synch the server name for your DNS registration service with your DNS management service. Part 3 Copy the IP address and target data path information from the Branding app to correlated EasyDNS fields. Paths to define/remap include A records; CNAME; NAPTR; MX, SRV, and TXT. Part 4 For redundancy, consider copying the entire remapped data system to Amazon Web services. Part 1: Branding App Setup & Configuration 1. Access Your application Directory 2. Open the Branding application 3. General Tab : Review the initial configuration settings Enter your white label Domain name URL, using "portal" to prepend it. Enter the Realm Suffix using "sip" to prepend your URL name. The Realm Suffix will be used to generate the account realms of accounts created by your white label interface. 4. Select the "Check DNS" button to the right of the Domain Name field This displays a template of all domains records that need to be configured. You will want to keep a tab showing this open at all times, as you will be copying the information from this page to your DNS management system. Part 2: Set up your EasyDNS account and copy its nameservers to registrar Setup your account with easydns.com, selecting an appropriate plan for your expected volume Get your new nameservers from easyDNS Overwrite your nameservers on your registrar (godaddy or the like) account Part 3: Configure your DNS records You may want to keep 2 windows open, 1 showing the Branding app in KAZOO, the other showing the records entry window in your easyDNS software. To configure the different kinds of records, you will step through these links and assign the records shown in the branding app to the fields shown. Configure “A Records” "A Records" map host names to IP addresses. Click on the “A” option next to DNS Information in easyDNS (see above). Copy the data from the branding app. to easyDNS as shown in the illustration below: NOTES: Only copy the “A record” types listings to this page. “Expected Record Data” field in the Branding App = IP Address Make sure the IP address starts flush against the field and does not show a tab or space to the left. Enter a value for TTL A TTL is “Time To Live”. Set as seconds, it defines how long a DNS record should reside in a client’s DNS cache without being discarded or regenerated. A common value for TTL is 7200 seconds (2 hrs) and is our recommendation for all record entries. Most DNS providers charge based on record lookups. The higher this setting, the less lookups will hit your provider; also the higher your TTL is, the longer changes to your records will take to roll out. Save / CONFIRM your changes! Configure “CNAME Records” Once the “A records” are copied, move to the next page in easyDNS and copy the CNAME data from the Branding app. to the correct field in easyDNS. CNAME records map host names to other host names, including hosts at other domains. NOTES: You MUST add a dot to the end of the CNAME URL (see above). This will indicate that the URL is a fully qualified domain name and does not need to be appended by your domain name (for example .myreseller.com). Copy both the API and the WebGUI Use 7200 TTL as default to start Configure “NAPTR Records” NAPTR refers to the “Name Authority Pointer Record. It is used by your phone to map SIP servers and protocols. You will need to break out the information provided in the Branding app to the specified fields in the easyDNS listing. NOTES: The values in the KAZOO branding app are concatenated in a single string. Many applications will provide separate fields for these. See red arrows. In the branding app you will see a set of empty quotes; this is a “null” listing for Regex. Leave that field empty and copy the remaining to the “replacement” field. Configure “MX Records” for Outbound Faxing MX refers to the “mail exchange” record. This specifies the mail server responsible for accepting email messages on behalf of the domain name. From Branding App To EasyDNS Use *.sip, so anything .sip will be forwarded to the fax domain URL. Configure “SRV Records” SRV refers to the Service Record in the DNS. It is a specification of data in the Domain Name System defining the location, i.e., the hostname and port number, of servers for specified services. NOTES: You must put the “dot” at the end of the Target URL for this record also. The values in the KAZOO branding app are concatenated in a single string. Many applications will provide separate fields for these. See above red arrows. Each SRV value should be added as a separate line. For example the branding app image above shows 2 lines per sip account; you must add these as separate lines, so there should be a total of 4 entries in the easy SRV records list. See above orange arrows. Configure “TXT Records” (SPF Record) An SPF record is a specifically formatted TXT record. It lists all authorized hostnames / IP addresses that are permitted to send email on behalf of your domain. This will permit KAZOO to send emails such as voicemail notifications under your domain name. From Branding app: To EasyDNS Check for errors! You should now see in the Branding app page the list with all green checkmarks at the right. NOTE: You MUST resolve any and all errors for your branded solution to work correctly. If there are still red configuration error notes, go back in and see if you can find the error. Common mistakes include: Not copying the full URL over (missing the last digit for example) Unwanted space to the left of your pasted data. A missing “dot” at the end of URLs, which causes EasyDNS to append your company URL at the end. Additional Notes Make sure your records match EXACTLY. You may need to use the paging option at the bottom right of the branding app to see all records you need to apply. Part 4: For added redundancy: Copy these records to Amazon Web Services We recommend you copy all your settings to the Amazon Route 53 for additional redundancy. We have learned over the years that any DNS provider can and will have an outage eventually. This will allow your records to persist even if EasyDNS goes down. Here we will show you how to replicate your records using EasyDNS’s built-in replication feature. First, purchase the Amazon Route 53 integration service from EasyDNS. Then activate and copy your records. will copy all your records and supply you with additional nameservers: Once confirmed, you should see both nameservers listed. Finally, go back to your original Domain Registrar and add the AWS Route 53 nameservers, alternating between the EasyDNS and Route 53 name servers. SAVE AND TEST! You should now be able to test your new setup. Frequently Asked Questions Can I do all this DNS mapping in a single application, e.g. GoDaddy? While it seems like tedious work to juggle both a registrar (GoDaddy or other) and a DNS web hosting service (easyDNS), we recommend using both. Each is an expert in its field. Domain registrars focus on indexing and protecting your domain name and the most popular have solid reputations for just that. DNS hosting systems are focused on reliably providing the records computers need to enable services to run on your domain name. These also offer different levels of support; we have found easyDNS provides us with all the record types we need (including NAPTR which some do not recognize) and easily creates a redundant occurrence of all settings to Amazon’s Route 53 Web Service. There are likely other systems that offer similar solutions, we are happy to hear what works well for you. Can I add just my branding logo, etc. and not update my DNS? No, the KAZOO platform needs some way to “know” what branding to show. The hostname that you use to visit is how this is determined. For instance if you visit http://portal.myreselleraccount.com/, KAZOO will know to show the Branding we configured in this article. But if you just visit http://ui.zswitch.net/, it won’t know of any reseller branding and will default to KAZOO branding. Do all the Lines in the Branding app need to show a green checkmark? Yes, with one possible exception: there may be an instance where the TXT value does not show a green checkmark and the white-labeling redirect processes will still work properly. But you should be well versed in DNS, SPF and mail servers if you have a custom SPF record. If ANY other record does not have a green check mark, it WILL fail. What are some of the problems that occur if my setup is not correct? Your custom UI branding may not display. Your phones may not be able to register to make/receive calls. Your phones may may not fail over to a secondary cluster if their primary cluster does down. Your customers may not receive their email notifications. Your email notifications may go into the SPAM mailbox. API Reference Docs docs.2600hz.com Whitelabeling - Kazoo API Reference(opens in new tab) REST API Reference for Kazoo Crossbar API ####
  13. Ahh interesting, that was not intentional. Let me see what we can do about that.
  14. Do you plan on pulling the commits made to the repos when they were broken apart back in to the combined kazoo repo as you have lost just over a week of commits by doing a revert and deleting the repos?
  15. Hi gang, We got some great feedback and excitement regarding the 5.x breakening. Thanks for that, that was great to hear. However, after some internal deliberations we’ve come to the conclusion that we did it a bit prematurely. Sorry the whiplash and to disappoint, but we are going to REVERT the repository breakup we just did and postpone it for a later date. But don’t worry, the master branch that it came from (in github.com/2600hz/kazoo) has also been restored. We’ll be back to you with more news once we’ve had some time to re-group on this work.
  16. Boring? No! Vodka? Yep! :) Here is my homebrew-scale recipe: Container Terminal Management System (JMS), taxation (SOAP), Docflow, Customs (SOAP), Railways GW (REST) <--> ESB (enterprise service bus) <--> RabbitMQ/Kazoo
  17. @Kirill Sysoev you live!!! Tell me more about potatoes on KAZOO? Are they in vodka form? And I agree, the platform is becoming more general purpose for building apps that can leverage the scaling bits in KAZOO. Almost borg-like...
  18. Hi! With these changes Kazoo became a kind of an Erlang/OTP on steroids - a platform for building scalable applications. It is not only just about telephony finally. Two years ago I tried to urge people to sell potatoes with Kazoo (was kidding a bit): https://www.slideshare.net/KirillSysoev/kazoo-billing These days I'm in progress of building web-portal and billing for container terminal (700 000 TEU) ... with Kazoo Containers are like minutes. They arrive to terminal (call comes into PBX), stored over there for a while (call duration) and leave terminal (hangup) - and here we are, we've got CDR (container detail record) :) Yes!!! Many thanks for all the hard work!!! Regards, Kirill Are there more examples of non-telephony Kazoo usage?
  19. Below is a running list of trigger calls that are supported in KAZOO for Zapier "zaplets". We will update this as new calls are enabled. call_ended call_received new_call_recording sms_received account_zone_change bill_reminder cnam_request customer_update denied_emergency_bridge deregister first_occurrence inbound_fax_error inbound_fax low_balance missed_call new_account new_user outbound_fax_error outbound_fax outbound_smtp_fax_error password_recovery port_cancel port_comment ported port_pending port_rejected port_request port_scheduled port_unconfirmed register service_added topup transaction voicemail_full voicemail_new voicemail_saved webhook Actions supported in SMS SMS action accepts for sending sms_send fax_send ringout SMS action accepts for receiving to from body
  20. You would need it to be provisioned and assigned to a user in SmartPBX , and assign that user an SMS enabled number. Then when you text that number, a message will appear in bria and you can respond back to it and should receive it on your cell phone. Is there something more specific that you are asking? I feel like I am also a bit confused by your request.
  21. So what exactly routes inbound SMS to the Bria application and how can you control which users receive it? I'm kind of confused how that would work.
  22. @Karl Stallknecht @esoare Correct, so this is currently available only to native numbers, we're working on getting the rest functioning as well. You are also correct about the Bria, if you enable the presence setting you will be able to send and receive messages on the interface. Definitely sorry to hear that you're not able to see the point and this doesn't help you Everyone of our resellers is different, can't win them all! Eventually, we'll have SMS/Chat but we're also currently working on larger projects that have been re-prioritized due to the pandemic. It's on our radar, and not an afterthought - but some of our resellers can and will utilize this so we're looking forward to hearing about those use cases Keep up the great feedback!
  23. Hmm that seems like a huge shortfall. 95% of our DIDs are port-ins. After clicking through a ton of random DIDs in our account I was finally able to find one with the option available, but it's not much good if it's available this few and far between. What do you mean "bring your own number to" exactly? For Bria, is this what you're referring to? https://docs.counterpath.com/guides/mob/mob_Retail_Ios_5.6.1/UG/clients/UserGuides/Mobile/Accounts/mobSetUpXmppAccounts.htm Without building our own UI for SMS, I can't really see any point in using this nor do I see how it helps us 😕
  24. @Karl Stallknecht I see SMS on some numbers and not on other numbers... Which reminded me of @Darren Schreiber's note that SMS was going to be enabled on Native Numbers. i/e: NOT ported numbers in the hosted platform... I do have clients that ported in, and have asked for this though! I asked if ported numbers would eventually work with SMS in the chat, but will let 2600hz speak to that. I am happy I have a native number/s and can test these out!
  25. @Karl Stallknecht Ok so everything should be ok on your end now - please let me know if you are now able to see the SMS settings. And if you are reading this and also running into this issue, just ping me directly and we'll take a look at your account. Thank you everyone!
  26. Hey Karl, 1. Can you try clearing your cache and trying again? 2. Correct, there is no Chat/SMS UI for your end users to converse back and forth, but they can do it on a Bria or other messaging platforms that you can bring your own number to. 3. MMS is not currently supported, eventually it will be but not at the moment. Let me know if number 1 works for you, if not send an email to feedback@2600hz.com and we'll try and get it sorted for you. Thanks!
  27. Super excited to hear about this! Three questions though: 1. I don't have the "Messaging" option available...it simply doesn't show up. 2. If I understand correctly, there is no interface built out that would allow us to simply provide access for our clients to be able to send/receive SMS via a web portal...right? 3. Is MMS also supported?
  1. Load more activity
×
×
  • Create New...