Logicwrath

Are there any limitations in our business using the app names in branding or marketing material? Can we use terms like Smart PBX, Pivot, PBX Connector etc.. on any public facing website or sales material we create?  Since we can't rename or control what they show up as in the web interface I would prefer to use them as-is.  I just want to make sure that 2600hz will not be upset or consider these terms trademarked etc. Please advise.

Yes, I will review.  I am working on something right now, that I planned on posting in the forum, maybe it will be a good fit for this new section on Github.  Thanks!

I think Github would work fine for me.  I don't typically use Github and I tend to be more of a hobby programmer and copy/paste/hack kind of guy so it would be best if there were at least a couple sample submissions so I could get an idea on how things should be included and formatted etc.. I think another important piece is having a big obvious link somewhere in the community to this location so other people get involved.  For me Github is fine, however, it might intimidate other folks and it would likely not get used if it was not searchable in the community or at the very least prominently showcased. When I read my response, I think the important detail is having it searchable in the community so more people get involved, but I am just guessing.

Thanks.  I will consider submitting inclusions if necessary.  I have mostly been able to find API documentation between the Google Dev group and the different project related websites. I was thinking more about community related configurations documentations. For example: How to properly configure a Yealink or Bria phone with DNS-NAPTR or How to create a simple pivot script that enables specific functionality that gets requested. Addtionally, I will be posting things from time to time in the forums on how to do something specific and it would be nice if it was open for users to improve and versioned.  Reading a thread on how to setup something and then having to read 20 more threads with improvements or bug fixes is more work than a versioned user submitted how to article.

Is there currently any kind of wiki or user contributed documentation system setup?  This forum is helpful and great, however, it would also be great if we centralize our independent documentation of configurations, best practices, scripts, innovations etc.. in some kind of wiki. I have seen members post good ideas, work arounds, and best practices in the forum.  However, threaded conversations are not ideal.  Is there any plan to create a community driven documentation system like a wiki? If I spend a long time testing and creating something I am typically going to be documenting it on my end.  It seems like this documentation would be better served if it were shared with the entire community.

It's worth mentioning that during our demo period faxing is the first thing we tested.  Getting faxing right is the bane of selling VoIP.

I was able to solve this by emailing my account executive.

I have confirmed this only happens when I limit access by specific users and choose myself and one other user.  After setting the permission, logging off, and then logging back in, I can know longer access the app, turning the app on and off will get me back in.

I am also missing the Advanced Call Flows app.  Should I be opening a case instead?

I am also unable to register devices using the branded DNS hostnames.

The Advanced Provisioner app is missing.  Please update my account to include this app.

I switched from my demo account to the production account and some of the apps I have enabled are not working.  I click on branding and the accounts manager app and the they do not function at all.  Smart PBX will always work.  I am not sure if this has to do with the fact that I have limited access to these apps to specific users or not. If I disable and re-enable the app, I can access it again.  Soon after it will stop working. I have also uploaded logo images and set preferences in the branding application and it is not working, do you need to turn this feature on?  It appears to not be working at all. I was also not able to get the *.s. outbound faxing DNS check to show a green check mark.  I have manually queried this record using nslookup and randomly generated 23243.s.vcspbx.net hostnames and the MX record gets returned correctly.  I am wondering if the logic on the check is bugged. I have tested these issues using Chrome, Edge, and IE 11.  I will also clear all browser data in all 3 browsers and try to access the Apps and they will not open.  They will only function after I enable/re-enable the app.

I think the reason we did not move forward with Vitelity is because of some of the requirements necessary to choose a specific DID or something about how the emails needed to be sent or formatted.  I would need to ask.

Honestly, we are already setup with Vitelity and for some reason we moved away from it, I can't remember why at this point, but we do have an account with them and did test it out. For what it's worth, I recently did quite a bit of testing using 2600's fax2email and email2fax and so far we have had 100% success rate.  I was quite impressed.  We sent faxes to US and Canada with 0 failures.  I don't plan on using ATA's if I can avoid it, but I do want to be ready to try it in those special cases. The testing I did previously with this ATA and an Obihai was with my previous carrier VoIP Innovations.

It's an HT702.  I bought it for testing. http://www.grandstream.com/products/gateways-and-atas/analog-telephone-adaptors/product/handytone-70... I suspect some of the configurations will be similar.  I have had trouble getting ATA's to work properly with T38 before.  It would be helpful to see if there are settings that I may have missed. Is there a community wiki somewhere?  It would be great for documenting best practices.

Karl, would you be willing to share your grandstream tweaks?  I have one on my desk right now that I am getting ready to start testing for faxing.

I think it might be a T46G only feature.  It's on the upper right side of the DSSKey page.

It is also worth noting that this phone provisioned from the Advanced Provisioner and does not have label length set to extended as that is not available yet. As you can see the line keys will be cut off and he will need to manually logon and set that option if more than 4 characters are used.

I would like to use the Yealink RPS server to drop ship handsets to my customers.  I enter in the MAC address into their website and it will correctly redirect to the Advanced Provisioner URL and configure the phone. The problem is that the Advanced Provisioner does not set the server URL in the Auto Provision settings of the Yealink configuration.  Any changes I make to the devices configuration in the Advanced Priovisioner will not get applied at reboot because it is not configured and not checking-in after the first redirection from Yealink's RPS service. It appears that I cannot use this RPS service correctly until the Advanced Provisioner sets that field. Thanks! Additionally, please also consider adding the Label Length field to the options.  I typically set this to Extended on the T46G otherwise it will cutoff anything longer than about 4 characters.

I have a specific need to automatically change the caller id based on the destination number.  A specific customer has 7 or 8 numbers in multiple area codes and likes to change the caller id based on which area code they are calling. I have been creating call flows using postman to try and solve this because patterns and the set_cid module are not available in Monster. The problem is that my pattern is not matching/working.  If I create the exact same call flow using numbers, the set_cid module works.  If I switch to patterns, it always chooses the default caller id. Here is the JSON I am using to create the call flow:  http://pastebin.com/91QSUnDf I have tried 3-4 different patterns.  As soon as I use numbers instead, the call flow functions correctly.  It appears that something else is matching first like no_match.  I assume this because I can see different recording URLs in the call logs. If I post the pattern with a * in front like ^\\*(1586\d{7})$ the correct call flow will get matched but the call is sent with the * and fails. Can anyone help me understand what I am doing wrong?

You can record outbound calls by editing the no_match call flow.  Just add a "start call recording" object in front of the Global Carrier.