Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Earlier
  4. Moving an account within KAZOO User Stories I mistakenly added and configured a sub account under the wrong parent account; my “North Carolina” office should be under “East” and not “West.” I want to move a sub account from one home account to another parent account – for example, move my XXX East account from US to Canada? Overview There are two ways to achieve this: Use the Cluster Manager app. In the KAZOO environment. Execute an SSH command at the server level. This is an option available to Global Infrastructure clients who are experienced system administrators. NOTE: This process can be unsafe; it should only be used if an account was created under the wrong account in error, and needs to be moved. USING CLUSTER MANAGER (OPTION 1) Obtain the account ID of the account you want to move from. This ID will referenced as MOVE_ACCOUNT from now on. This can be obtained from the UI via the Accounts Manager app. Open your Accounts app Navigate to the account you want to move to Select the account, and select Overview Copy the account ID String and save it on a notepad From Account: 2. Obtain the account ID of the account you want to move the MOVE_ACCOUNT TO This ID will be referenced as DESTINATION_ACCOUNT from now on. Repeat the steps above and copy to a place that clearly labels this Account ID is the TO: Account ID number. 3. Browse to https://ui.zswitch.net and login using your credentials and the name of your account on our hosted platform (XYZ Parent Account) Open the Apps menu, and select the Cluster Manager app Click the Scripts tab from within the Cluster Manager app Click the Red Button labeled Run Command 4. Type the command below into the command dialog box sup crossbar_maintenance move_account MOVE_ACCOUNT DESTINATION_ACCOUNT NOTE: While this process should take less than 5 seconds, you may want to increase the “Abort After” value to about 5 minutes. This should give ample time for the process to resolve before timing out and requiring a restart. 6. Click the Select Servers button 7. From the Cluster drop down, select the name of the cluster where the accounts live that you would like to move (pre, or prod). You do not need to select anything for Zone, or Services 8. Uncheck servers in the Filter Results section, so that you ONLY HAVE ONE server checked NOTE: You MUST select the server that contains your KAZOO applications; a Freeswitch or Database only server will cause this process to fail. To ensure this, you can follow these steps: Filter your server list using kazoo_applications type of servers first. "Select All" to unselect everything. Reselect the first server on the. list. 9. Click NEXT 10. Click Run Tasks Now! to execute the command you typed into the dialog box, on the server that remained checked on the previous page. 11. Watch the "Running/Queued" section of the tasks tab to ensure the task completes. You may need to refresh the list periodically, but clicking the refresh button (2 spinning arrows) at the top of the list. You can also go to the "Completed Logs" section to see that your "Run Command" task completed successfully. 12. Once the task is complete, confirm the account is now moved by re-opening the Accounts Manager app in the UI of your cluster. ADVANCED USERS (OPTION 2) This is an option available to Global Infrastructure clients who are experienced system administrators. Via SSH: Obtain the account ID of the account you want to move, I'll reference this ID as MOVE_ACCOUNT from now on. This can be obtained from the UI via the Accounts Manager app. Obtain the account ID of the account you want to move the MOVE_ACCOUNT under, I will reference this ID as DESTINATION_ACCOUNT from now on. This can also be obtained from the UI via the Accounts Manager app. SSH to one of the servers in your cluster where the account you want to move is assigned, and where kazoo_apps is running. Run the command below: sup crossbar_maintenance move_account MOVE_ACCOUNT DESTINATION_ACCOUNT API Reference Doc: docs.2600hz.com https://docs.2600hz.com/dev/applications/crossbar/doc/accounts/#move-an-account
  5. User Story Reseller wants to store recordings onto Amazon Web Service while insuring as few permissions are given to the service account as is possible. Reseller is looking for a solution that helps ensure strong encryption is implemented for call recording features and connect this account to a specific KAZOO account. Reseller plans to assign each account a unique “bucket” with its unique credentials. Before you Start Sign up and Log in to your Amazon Web Services account. If you don’t have one already you can go to their website here to get started: https://aws.amazon.com/ Quick Overview of Steps Set up an account with Amazon Web Services Decide what clients and client names to use for each bucket Create bucket names for each client and define settings Create user names for each client Add JSON IAM policy and permissions Add JSON Bucket policy and permissions Capture your Access Key ID and Secret Access Key , Bucket Name Open the AWS app Create a new AWS account in KAZOO and enter that information. Set up an S3 Bucket An Amazon S3 (Simple Storage Service) bucket is Amazon’s term for a place you define to store your data and its metadata. It is the equivalent to a file folder with your company identifier on it. From your AWS portal, access the S3 application Select Create Bucket Enter a new Bucket name. You will do this for every client? The Region field can be left blank, AWS will read the account default. Click NEXT and page through the remaining settings options. We recommend enabling the “Block ALL public access” option to on. Set up an IAM User An IAM (Identity and Access Management) User is an entity name and credential that you create in AWS to represent the person or application that uses it to interact with AWS. An IAM user with administrator permissions is not the same thing as the AWS account root user. From your AWS portal, access the IAM application Select Add User Enter a new username. This will likely be your client name or client reference Check the Programmatic Access box under Access Type Select NEXT Under Set Permissions, select “Attach existing policies directly” Select Create Policy This will open a new tab for you to enter your policy details into. A policy defines the AWS permissions that you can assign to a user, group, or role. Yo can create and edit a policy in the visual editor and using JSON. For this example we will use the JSON. Copy the text below. Replace the “BUCKET_NAME_HERE” text string with the bucket name you entered earlier. It will display something like below: Review Policy Select Review Policy using the button at the bottom right. Return to the IAM tab and refresh your screen using the refresh button to the right (circled in red). Enter the name of the policy in the search field and select the checkbox to the left of the Policy name it to be active. Select NEXT Go to Set Permissions Boundary, Select NEXT: Tags The next two pages are for tagging and review, you can just leave them blank and click create user. Your access key and secret access key will be displayed. SAVE these! You will need to add these to your connector app. Return to the main page for IAM Click Users, and click on your user account. Save the Amazon Resource Name (ARN) shown. This is your identifier Amazon recognizes. (for more info on these, see HERE.) Enter your bucket policy Return to the S3 app and select the bucket you want to add a policy to. Click on Permissions Click on Bucket Policy Copy / Paste the code below Update your bucket name and ARN (see highlighted area). SAVE !!! You should see confirmation of your updates here. Update your bucket name and ARN (See. highlighted areas). SAVE ! You should see confirmation of your updates here. Enter saved data into your AWS Connector App in KAZOO Click on AWS Connector from your Apps listing NOTE: If you can’t find it right away, use the Search Apps field at the left of the screen. Click Add AWS Account Enter your saved account details NOTE The Host field below should be left blank. This will be auto-detected. Frequently Asked Questions When is it important to assign an AWS account to a client? AWS offers storage with enhanced privacy encryption, which is often required for HIPAA compliance and other clients who are concerned about privacy. It also provides automatic backup services to give your client files additional redundancy. If your client is concerned about tight encryption and security, this is an option to consider. What are Bucket and IAM policies? Below is an overview provided by Amazon, here: IAM policies specify what actions are allowed or denied on what AWS resources (e.g. allow ec2:TerminateInstance on the EC2 instance with instance_id=i-8b3620ec). You attach IAM policies to IAM users, groups, or roles, which are then subject to the permissions you’ve defined. In other words, IAM policies define what a principal can do in your AWS environment. S3 bucket policies, on the other hand, are attached only to S3 buckets. S3 bucket policies specify what actions are allowed or denied for which principals on the bucket that the bucket policy is attached to (e.g. allow user Alice to PUT but not DELETE objects in the bucket). Note: You attach S3 bucket policies at the bucket level (i.e. you can’t attach a bucket policy to an S3 object), but the permissions specified in the bucket policy apply to all the objects in the bucket. IAM policies and S3 bucket policies are both used for access control and they’re both written in JSON using the AWS access policy language, so they can be confused. Related Articles Accounts Manager Wizard Notes on HIPAA Compliance Responsibilities API Reference docs.2600hz.com Storage - Kazoo API Reference REST API Reference for Kazoo Crossbar API
  6. Configuring Video for use on the KAZOO Platform User Stories A user wants to enable a device so it supports video calling between two office desk phones A user wants to call into a KAZOO video conference using a video-enabled desk phone instead of a laptop. A user wants to allow video replay and/or online streaming on an office phone (to replay a saved video call for example) using the KAZOO platform. Overview Video Calling Video is an image capture process that takes a rapid amount of still pictures at a source, compresses the data, and transmits the packet across phone lines. The recipient unpacks them and replays the sequence to show movement, or “video.” Some notes about the transmission: “Frames” are single images, transmission is described in “frames per second”, or FPS. Typical compression is 20-30 frames per second. Lower rates and lower resolution means you will see a stuttered, jagged result. The resulting “video” is a stream of these captures. As with any images, video takes up significant data bandwidth to transmit. To help mitigate this video uses one of several compression algorithms which collectively are referred to as “CODECS” (short for “COder-DECoder”). CODECS Compression CODECS refers to the format for compressed data transmitted across devices (including WebRTC, Softphones, mobile devices, comm.io). Some formats compress audio only, others compress audio and video. There are several different compression types available today. To successfully transmit these files, both the originating device and the receiving device must be equipped with the same codec compression interpreter. If a device transmits H264 video, then the receiver must be able to “read” that. Your office desk phone and your laptop application for example, must be able to talk in the same language. Common audio formats used by telco devices include .mp3 and Opus. Popular compression formats for video are H263, H264, and the newer Google-developed VP8. Audio and the KAZOO Platform All KAZOO Platform calls assume (and require) audio CODECS. Audio is typically set by default, and users can fine tune those settings in either our Provisioner setup or the SmartPBX app. KAZOO includes support for the most common audio formats. This audio information will be sent to the corresponding phone hardware so the two are synchronized. Video and the KAZOO Platform Video is optional as its transmission takes considerably more bandwidth and can lead to an additional charge to your account. To support independent control over video, the KAZOO platform transmits audio and video on separate ports for each call. In order for the sending and receiving devices to share video, they must both recognize the same CODECS data. This requires an intentional setup in both SmartPBX and the Provisioner app. Enabling Video Calls To use video, you will need to enable it for your devices in your user account. This is a two step process. Since the call origination device (whoever starts the call) is what picks the algorithm, or the “rules.” As your system will do both, you will need to provide available compression settings for both sending and receiving instances: Server to Phone (using SmartPBX) and Phone to Server (using Provisioner) Below is an illustration summarizing the process. Before you start Confirm the video format(s) that are supported by your devices. The most common include H261, H263, H264 and VP8. CONFIGURE VIDEO SETTINGS FOR SERVER → PHONE TRANSMISSION This setting is defined in SmartPBX. Here you will define Server to Phone connections. NOTE: If the two settings do not match you will get “incompatible destination” errors. To set these preferences, go into SmartPBX Select the Device tab to the left. Search for your device, and select the Edit icon to its right From that dialog, select the Advanced Tab, and then Video from the drop-down menu. You will see a screen that shows a list of video compression options. Drag the compression types you want to recognize to the Selected column. NOTES: By default, there will be no options in the Selected column. This effectively means video is not enabled. To enable a video type, drag the compression style your devices support to the Selected column. VP8 is currently the most popular, as its compression has the best results and there is no license fee related to it. Most newer devices prefer it for these reasons, so if your devices support it, it’s recommended you use it as your primary selection. You can move more than one codec to the Selected column, and drag them into a preferred priority. SUCCESS !!! You are now ready to move to the Provisioner app and configure the settings there. CONFIGURE VIDEO SETTINGS FOR PHONE → SERVER TRANSMISSION Define the settings for a Phone to Server video transmission in the Provisioner app. This setting defines the transmission codec from the phone to the server. Under the Devices tab, find your phone and select the Settings gear; Choose Configure. Select the Codecs tab from the Blue Menu and review the video preferences. If Video selection isn’t visible, you’ll need to go back to SmartPBX and verify you saved your settings to turn it on. Even if the video is turned on, by default the selection here will be None. If you see a value for “Inherits”, this means the setting will carry down from your parent account. Your selection here MUST MATCH your selection in SmartPBX as you configured above. You can only select Primary, Secondary, and Tertiary types if you have moved each into the Selected column in SmartPBX. SAVE your settings! SELECTING A TYPE OF CALL WHEN YOU DIAL Some phones and web phones allow you to choose whether to make your call an audio-only or a video call. If you do not intend to share video this is a great way to save bandwidth and unnecessary usage fees. On the Bria softphone To the right of the phone # field, you will see a drop-down menu arrow. Select that to choose your phone call mode. If you choose video, a video “screen” will appear. Yealink phones Yealink will ask for audio/video on your screen once you dial the number. NOTE: It’s best to define your type of call at the beginning of your call. While some phones may provide a way to switch mid-call, this may interrupt the call integrity and cause reduced quality and/or a disconnect. HOW KAZOO MANAGES VIDEO CALLS Because video takes significant bandwidth and processing power to compress and decompress, KAZOO has set up dedicated servers to process video calls. ADDITIONAL NOTES Once video is enabled, it typically is used as the default for every call. Newer devices may give you the option as the call is made (see above), so you can choose audio if you do not want to incur extra costs. Older models have a configuration setting that can be set to “optional.” You will need to make sure this is set correctly in the back end configuration. Usually this can be found in the Provisioner app. If you turn on video on as a default in your device, all calls will include the video codec even if the receiver has no video capabilities. This is clearly a waste of bandwidth so it is recommended you find and enable an “optional” setting to trigger the setting for each call. FREQUENTLY ASKED QUESTIONS : VIDEO SETUP What devices does KAZOO support for video? KAZOO supports any device that supports the CODEC options listed in the SmartPBX and Provisioner settings. Currently this includes H261, H263, H264, and VP8. This is typically provided as part of the device specifications. Do I have to configure my comm.io video to use the conferencing there? No. comm.io has automatically configured the video codec in its software. It should work without any added configuration. When I try to use my video I get an error message that says “incompatible destination”. This error is indicating that the CODEC algorithms on the sending and receiving devices do not match. You will need to review the settings for each device and add a matching CODEC in the configuration. If I have vp8 set as primary and H263 set as tertiary on my sending device, and my receiving device only has H263 set, will the call connect? Yes. As long as the codec has been moved to Selected in SmartPBX under your device, it won’t matter which is primary, secondary or tertiary. Those priorities will kick in only if multiple options exist. Typically it makes sense to select VP8 as the primary as it has the most efficient compression and therefore will likely incur less charges. My device settings in Provisioner say “inherited”. Where from? This references a parent account setting. If you have a hierarchy of accounts, it comes from the account, or reseller, or system defaults – whichever one is found first (in that order). Does the order (primary, secondary, etc) of the video selection(s) I add in Smart PBX have to match the order I enter in Provisioner or do they just need to be enabled in both places? As long as the codec has been moved to Selected in SmartPBX under your device, it won’t matter which is primary, secondary or tertiary. Those priorities will kick in only if multiple options exist. Do I need to configure these settings for mobile phones? Mobile phones are pre-configured for both audio and video. Phone browsers often choose a codec and then optimize it for best use of battery life and resolution for their device. If you cannot see a video transmitted from a mobile phone on your desktop phone (or vice-versa, and you get a “Can’t play video - video codec not supported) it may be you need to configure the desktop so it supports the mobile phone video codec. Below is what is currently supported: Apple iPhones: H. 264 and their new format for Apple only, HEVC Apple Safari: H. 264 and now also vp8 starting with Safari 12.1 Android Phones: H. 263 / H.264 There are apps available for each operating system that will convert and/or display files using other formats such as VLC Media Player; you can search for these in their app stores. Why do some of my calls cause video errors and others don’t? There are several reasons this could happen. Consider the following as a way to troubleshoot this: Are the calls that are working internal calls within your office? This may be related to your carrier configuration if you have a BYOC account. Refer to the Carrier section above. Is the difference related to incoming v. outgoing calls? Check your configuration and codec assignments in SmartPBX (server to device or incoming) and in Provisioner (device to server, or outgoing). Is it specific to a device type? In some cases a device does not support the video codecs you have configured and/or it may not support video at all, and your calls are sending video requests. Often these issues will provide an error saying “video not supported” or “incompatible destination.” Does the KAZOO CallThru.us mobile app support this video process? Not at this time. Configuring Video for use on the KAZOO Platform Reseller Notes Billing Structure for Video Calls Currently video is currently enabled for all accounts at no additional charge for our introductory beta rollout; once the product is officially released you will be charged $20/video channel. Once we have video call features (such as inviting external participants to video conferences) that significantly increase the video load we will add a setting to the Control Center to manage maximum channels -- similar to the trunking setting. This will mean account managers will be able to distribute charges in a similar manner. How KAZOO detects video calls (back end SIP code) Audio call request is shown in the gray section Additional Video call request is shown below the added gray line BYOC Carrier Configuration If you are using your own carrier it is critical you also assign audio settings. If you do not, the system will assume your devices support both audio and video and will by default try to make video calls. As no 3rd party carriers are supporting video at this time this will cause Outbound calls made from a video phone to a carrier to fail. Calls within an office will work correctly. To configure the carrier settings, go to the Carrier app. And select an account you have created or create a new account. Then select Audio and add specific codecs. Continue with video, even though they are likely not supported. #####
  7. In today’s technology-run world, digitization has made a significant impact on the telecommunication industry. All thanks to it, communication is quicker and more comfortable. One cannot forget the considerable role telecom and internet service providers have played in this transformation, including the creation of new field engineering job opportunities, for IT & Telecom professionals such as the Telecom Field Engineer.

    Field Engineer responsibilities typically include handling maintaining, monitoring, installing and providing support for network hardware, software and communication links. They must ensure the stability of in-house voice, data, video, and networks. Field Engineering includes proposing offer technical and engineering solutions for communication-based subjects such as wireless telephony services, radio and satellite communications, internet and broadband technologies.

  8. Free

    Version 1.0.0

    0 downloads

    This is an overview of the process you will take to contribute documents to our download library.
  9. Below is an overview of what the SmartPBX dashboard is showing about your account configuration. NOTE: For details on each setting and strategies for how to define them, refer to our companion User Guide that walks through the setup process, HERE. Dashboard Header Information This information provides quick access to some of the main features of your account. The top left displays the account name you are viewing and is read-only. The tabs to the right are clickable and provide access to the following settings: Account Default Caller ID Number Here you can set what number is used as the default Caller ID for outbound calls from the account. You can also set the CNAM and E911 info associated with the number. For more info on CNAM and E911 see the Main Number section below. 911 VERY IMPORTANT: Calls to 911 will not be allowed if one of the DIDs belonging to the account is not configured with proper E911 address information. If the account has multiple physical locations, each location must have its own DID with E911 address information specific to that location. Devices that are not at the location matching the E911 address of the account’s default E911 configured number must specify the correct DID to be used for emergency calls placed from that device so that the 911 call can be handled by the correct 911 call center and so they can if needed send emergency responders to the correct address. If a call to 911 is placed and it is determined that the address is not configured or incorrect there are significant penalty fees charged. If you bring your own carrier (BYOC) then E911 is not managed through Kazoo’s Monster UI and no check can be made to ensure you have E911 address information properly configured for the emergency Caller ID that you have configured. Account Default Hold music (MOH) Set what the account’s default hold music is. It will play when someone is on hold, in a conference room when there is only one person there, if you get Call Center the hold music there. NOTE: This can be over-ruled by add-on applications. For example, the Call Center Pro application provides added choices for uploading music and a sequence of "on hold" interactions, including "approximate waiting time" and "number in queue ahead of you." Hours This allows you to revise the office hours you previously set up. Total Users The total users graph shows the total number of users assigned to this account, and how many, if any have been given access to SMS/MMS messaging. There is an added charge for this so it is helpful to see what the summary here. Total Devices This summarizes the number of devices (not users, remember many users will have more than 1 device) configured for the account. A desk phone is one type of device that is called a “SIP Phone” device type. Not all devices are necessarily themselves a “Phone”. Some can be a static forward to a phone number off net like a Cell Phone or might be an ATA that an old analog phone is connected to. A circle graph representing the percentages of types of devices with a legend showing the actual count of each device type. Unregistered Devices The total number of device that are not currently registered. It will include SIP phones/devices that are not registered and will include device types that by nature do not register like Landline, cell phones, and RTC webphones used in the comm.io app. Conference Bridge count Summarizes the total number of conference bridges set up for this account. Main Number This displays the main numbers and the features active for each number. If you bring your own carrier E911 and Caller ID Name will not be available for you to manage with Kazoo. When you first set up the account there will be a special message here to assign a Main Number. Once you have one assigned, there will be a message to configure E911 for a Main Number. See the Numbers section below for the meaning of the icons like that may appear with a number. Conference Number The account’s conference number if assigned. One of the available user features is to have their own conference room, and/or a video conference room as part of the comm.io app. The user would give out the main conference number and the user’s conference room number along with an optional PIN access code. Main Faxbox Number The account’s Main Faxbox number if assigned. This faxbox only handles inbound faxes and will send inbound faxes to the email address configured when a number is assigned to the Main Faxbox. Total Numbers Summarizes the total Numbers owned by the account and indicates any and spare numbers you may have purchased in a group but not yet assigned. It also identifies 800 numbers you manage. A Graph showing the classification of the Numbers owned by the account. The available classification names can be seen in the Restrictions portion of a device. US DID includes United States and Canadian numbers. Company Directory Shows how many users there are in the company directory. You can configure a user not to be listed in the company directory. But by default, users will be added to the company directory. You can download this information as a .csv file also, and import it into a document for distribution. Account ID This number will be used if you need a support person to help track down call routing issues or any other support questions. Account Realm The realm of the account. This is used as part of SIP authentication and for faxboxes so the account users can send an email to the system that will then be sent as a fax to the destination number. See the Creating Accounts and Branding articles in the Getting Started resources for more info on the significance of the realm and the implications of changing it later. Numbers & Users Below is a quick overview of the pages displayed when you click on the icons in the dashboard. NOTE: A more detailed discussion of these settings can be found in the SmartPBX User guide, HERE. Numbers in use shows the phone numbers, the users assigned to the numbers, and some of the attributes assigned to that number. When a number is selected there are actions displayed above the list of numbers that can be performed on that number. Here the actions for selected numbers are and . In Number Manager App there is also the action which allows you to move a spare number to another account. Be aware, if you move a number to another account and later Delete it from that account the number will go back as a spare number to the account it was previously moved from. If you believe a number is in the wrong place (Spare/In Use) you can use the to try to correct it. Charges for DIDs apply to spare numbers as well as Numbers in use. Meaning of Number Icons like indicates the number was added manually or imported to the system and features like inbound and outbound Caller ID and E911 are not available for it. Generally, this is the case because it is from a BYOC carrier and those features need to be managed through the carrier that the number was bought from. icon when clicked displays a menu that allows you to manage features of the number like Caller ID, CNAM, and E911. E911 is configured on the number. Caller ID name will be looked up for the number the call came from, AKA Inbound CNAM lookup. number has set a name in the national CNAM database that can be looked up by OTHER systems that do Caller ID lookup. This is not to be confused with the External Caller ID Name. The External Caller ID Name is only effective for calls between accounts. The PSTN network does not support transmitting Caller ID information so when a call goes out a carrier across PSTN the Caller ID name is lost. But the destination number’s service provider, like we offer with the “Inbound CNAM lookup” described above, can do a lookup in the national CNAM database and provide that to their users. . indicates the number is in the process of porting. Indicates that the number has been enabled for SMS text messaging Indicates the number has Prepended value to it that will display on caller ID. Spare Numbers Users Here is where you can view and manage the account’s users and the features they have set up. Each Column for the user reflects primary info of that column’s category for that user and you can click it to access the settings for that category for that user. For a detailed description of what the icons represent and how to assign them, refer to the SmartPBX User guide.
  10. Overview Pivot enables you to generate real-time KAZOO callflows via a REST API. This means your web application can tell phone calls what to do, during the call! Some examples use cases: Checking an external account balance before allowing a call Routing an incoming call based on custom logic Present menu items and respond to selections based on information in your database Here’s how it works:When you add the Pivot module to your call flow, you provide Pivot with a callback URL to your webserver. From then on, when KAZOO receives a phone call for a Pivot-enabled phone number, KAZOO sends an HTTP request to your webserver asking it for a new callflow. Along with the request, KAZOO passes information about the call, such as the originating number. Your web application will then generate a new callflow, which KAZOO will run. Since your new callflow can itself contain another Pivot, you have the ability to make completely dynamic callflows. Features Routing a call based on accounts in a remote system Here’s an example where PIVOT is used to check if a customer record exists in Zendesk based on the incoming phone number. If so, the caller is connected to support. If not, the caller is played an audio message. Create a Call Flow based on a menu selection. Here’s an example Call Flow where a menu is presented to the caller. Once a selection is made, PIVOT makes a request to your webserver, passing along the menu item selected by the caller. Your webserver then returns a new Call Flow based on the menu selections.
  11. Overview Today’s users demand more control of their phone system than ever before. Administrators are tasked with providing these features while avoiding complicated user interfaces and instructions for end-users. The User Portal app gives you all of your personalized communications information in one place. View corporate contacts, manage voicemails and faxes, see devices registered, and more. All without exposing end-users to complexities of the entire platform. The User Portal’s UI is easy to navigate. You can ensure devices are online and registered. You can view and listen to voicemails, see who has sent you a fax and download the fax online, or delete it from your fax mailbox. In addition, if you have changing needs, you can modify incoming call handling settings such as call forwarding or simultaneous ringing across devices. User Portal also exposes an advanced personal conference bridge system, allowing you to manage your own dedicated conference bridge. See who has called in, manage user access to the conference and see who is talking, real-time. Features Device Status and Configuration You can view a visual representation of the devices configured and assigned to you. Additionally, you get a thumbs up if the phone is operating normally, and a thumbs down if the device is offline. Settings You can set your own call forwarding number or configure their voicemail to email settings. You can manipulate Caller ID handling on forwarded calls to help identify work calls on your personal number. Conference bridges You can set your own pins and manage moderators for every conference. Every call is tracked, and every device that connects is shown. You have real-time control on conference using lock, mute, unmute and hangup options. Contact list You have your own list of contact numbers, in addition to direct dialing out of the UI. Voicemails You can search or select voicemails from the list in order to view and manage them. You can download any visible voicemail message by clicking on the Download icon, which will download a .WAV file to your desktop. Technical Specifications Voicemails Supports multiple voicemail boxes View and sort the user’s voicemails by date, numbers or duration Search for voicemails within that list Listen to the user’s voicemails directly in the app Download any voicemail as an mp3 file Mark any voicemail as new, listened, or deleted Real-time MWI sync with the user’s devices Call History View and sort the user’s past calls by date, number/caller ID, or duration Search for calls within that list Filter the user’s call history to view calls within a specific date and time range Faxes View and sort the user’s faxes by direction, date, faxboxes or numbers Search for faxes within that list Filter the list to view faxes within a specific date and time range Download any fax as pdf Contact List View and sort the user’s contacts by name, extension or number Search for contacts within that list Call anyone from any of the user’s registered devices by using by clicking on their number in the user’s contact list or simply typing the number thanks to the QuickCall feature Conference View whether the conference is currently active as well as its duration View the current Moderators and Participants in the user’s conference live thanks to websockets Perform actions on the whole conference room such as Lock, Mute/Unmute or Hangup View the Call-in number for conferences in the account, as well as the user’s conference number Set up different PINs for moderators and participants Choose whether the participants will join the conference muted/deaf. Choose whether to play an entry and/or exit tone Devices View and sort the user’s devices by registration status, name, type or mac address Settings Enable/Disable call forwarding: Choose the forwarding target Choose whether to also ring the user’s VoIP phone Choose whether to keep the Caller ID Enable/Disable voicemail-to-email Choose the email address to send the user’s voicemails to
  12. 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
  13. 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
  14. 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
  15. Awesome - i will check this out - thanks for the quick reply
  16. Hi! 1) I used quickcall for this. https://docs.2600hz.com/supported/applications/crossbar/doc/quickcall/
  17. 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
  18. Thanks, Might not be that many commits but just need to know if we need to resubmit them or not.
  19. 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 ####
  20. Ahh interesting, that was not intentional. Let me see what we can do about that.
  21. 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?
  22. 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.
  23. 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
  1. Load more activity
×
×
  • Create New...