Jump to content

Skunkbeard

Customers
  • Posts

    75
  • Joined

Posts posted by Skunkbeard

  1. You could setup a TR-069 Protocol to remote provision Cisco ATA's. We have deployed Cisco SPA8800 & SPA8000. Don't really need remote provision on those in most cases. Once you get it setup you typically dont have to touch it. But if you do set it up to be internet facing which is what we have had the best luck with you can just login to it to make changes.  I attached some PDF's of how we configure ours. We set this one up 7 years ago and haven't had to touch it. Just replicate line 1 for additional lines. Creating an ATA device for each line. Hope this helps. 

    Cisco SPA Configuration - Line 1.pdf Cisco SPA Configuration - SIP.pdf

  2. I'm guessing from post history you are running the open source platform. Depending on the carrier you are using and how much you have integrated the carrier to the platform. You are probably better off using the carrier API to do SMS. 

    Are you on open source? 

    Who is your carrier? 

    Do you have SMS enabled with your carrier? 

    Are you using a third party app for SMS or something you build? 

  3. (This is for Polycom phones)

    This allows you to override or add features that the provisioner doesn't have built in. 

    1. So you create a web URL with a directory you can save config as the MAC-web.cfg | For example www.YourURL.com/p/overrides/
    2. Go to Advanced Provisioner > Find the device > Settings > Configure > Settings > Go down to Configuration Settings > Custom Overrides Directory URL> Paste your override url in the field  www.YourURL.com/p/overrides/ > Save
    3. Then create an override file with the MAC of the phone example:       64167f000000-web.cfg

    I currently don't know of a way to add this URL to all devices on an account so you'll have to paste them in individually. (I think it can probably be done via the API. If there is another way please let me know. We plan to add this but its on a list of 100 other things to make since we moved to hosted)

    We chose to use the web config. But in your config file you use the code below . Then put the config settings into it between <OVERRIDES and />. Whatever you want to change based off the manufactures docs. Below is for Polycom Intercom. This changes the ring type when using *0XXXX. So their is an audible alert before connecting intercom. 

    We had to do this since the current provisioner is lacking the ability. The default Intercom and Answer settings don't provide an audible (Well one loud enough to hear) short alert letting you know someone is connecting to you using the  intercom. 

     

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <WEB_CONFIG>
    	<OVERRIDES
         voIpProt.SIP.alertInfo.1.class="ringAutoAnswer" voIpProt.SIP.alertInfo.1.value="intercom" se.rt.ringAutoAnswer.ringer="ringer11" se.rt.ringAutoAnswer.timeout="500" se.rt.ringAutoAnswer.type="ring-answer"               
     	/>
    </WEB_CONFIG>

     

  4. 1 hour ago, Chuck said:

    I want to thank everyone for the info on this thread.  I did not know about the ability to press 9 to call back the person who left the VM.  Very important feature for a new customer and I would not have been able to provide it without this thread!

    Awesome! Happy it helped!

  5. TWIL: So we have a client who's outgoing number is being flagged as SPAM by their patients carriers. 

    Need to use the following websites:

    Verzion: https://www.voicespamfeedback.com/vsf/

    ATT and others: https://freecallerregistry.com/

    Free Caller Registry also has these emails listed for contact:

    First Orion : FCRsupport@firstorion.com

    Hiya : freecallerregistry@hiya.com

    TNS : communications@tnsi.com

  6. 2 hours ago, Rick said:

    @Skunkbeard the sysconfig wouldn't set the default for you. It only enables it across a whole cluster. You already have it enabled. :) There's no real way to set it up as a default. BUT... if you use the CSV onbaord app, you can define extra JSON you'd like to apply to your NEW users/devices/voicemail boxes. So, you could just define it there. If you want to apply a setting across all your existing voicemails, ect, put in a ticket. I've got a little script I can run against your account to do that for you as a one-off

     

    EDIT:

    Just in case any PC/GI/Open Source folks need it, the sys_config is under the callflows doc, voicemail.is_voicemail_ff_rw_enabled that needs to be true

    Awesome thank you for the clarification! I just starting learning programming and the ins and outs kazoo so I apologize for my ignorance. I really appreciate the offer of the one off script. i will look into the JSON as that seems it will fit my needs.  Is the below the JSON format its looking for on import? 

    image.png

     

  7. On 7/22/2022 at 2:35 PM, Rick said:

    Heh, love hidden options! FYI there’s a sysconfig needed to enable this. Don’t have it off hand but LMK if you need it and I’ll get OPs to dig it out. I believe it’s on on ZSwitch though. Also 9 will call back the person who left the voicemail!

    Yah hidden options are always a fun find! Part of the enjoyment of exploring menus. Oh awesome I didn’t know about the opt 9! 
    Ya! I’d love to hear more about the sysconfig. No rush I know you guys are busy making magic happen with all the new features. Been working on using the api to set defaults like VM FF and play oldest first. We are new hosted customers migrating all our customers. Being able to set defaults for options every user/device/menu have will save tons of time in setup over the course of migration and new customers. 

     

  8. Hey I was poking around a bit and completed the bootcamp course. I think its a great start! I don't have any criticisms for it.  One thing that would be nice would be able to designate someone as a manager and be able to send an enrollment email out to new hires and be able to track their progress, see where they had issues and then the manager can do additional training with them. but that's purely just a fluff add on. 

  9. 11 hours ago, DanH said:

    Ah that's awesome! So to clarify one of the main ideas behind this subforum, we are actively encouraging users like yourself to also make your own TWIL posts based on information that you've discovered and verified on your own as well, we're crowd sourcing this concept! This is exactly in the spirit the forum, all you need to do is give it its own post and voila, first community contributor to TWIL archives. 😃 Please let me know if I can clarify anything about this further, it's a work in progress as usual and we can always work on explaining things or defining the idea and boundaries better. Thanks @Skunkbeard!

    @DanH Ah I see ok I thought you guys were making a weekly post and we add to it. I was thinking that because I didn't see the orange button to create a new post. 

  10. @DanH No it was more a my own TWIL for hang up explanations. I am still looking into what a dropped call might report if it does at all. I was more thinking out loud incase someone saw it and might have an answer to it.  The links I got from a support ticket and a comment from MC in another thread on hang up reasons. Was just sharing them as I found them in my journey to figure out if dropped calls from packet loss report a different type of hang up cause. 

  11. I think the new system is great. It would be nice if you had a section in the PAID Client section where it posts the Question and Answer from support tickets of issues that are applicable to Hosted/GC/PC clients. (Just block out the names and person info) I'm sure there a tons of questions that are asked of support that many paid users are wondering and it would save us the client from having to submit a ticket if its answered there and save the time of the support agent from having to answer repetitive questions. As well as having some of the more specific questions that could be useful to all hosted/pc/gc clients. 

  12. Just FYI for doing sidecars with the provisioner. Here is supports response. 

    After asking around it seems you will need to make a custom config file to configure the side car. The syntax to configure the side car should be:




    attendant.resourceList.X.address = ""
    attendant.resourceList.X.label = ""
    attendant.resourceList.X.type = ""
    />


    notes on that template:
     

    X should be a number greater than the number of keys for the target phone
    otherwise you risk overwriting keys set through provisioner
    although that number changes if you increase the number of line keys on polycom
×
×
  • Create New...