FASTDEVICE

My thought is provide direct SIP dialing across accounts. This way we can create a callflow with a devices that points to a SIP address in another account. While not a perfect solution given the caveats, it's one that should exist.

That's a rather open ended question. Are you looking for browser extensions, CRM integration, and/ or outlook integration etc.? There are many options to consider and each can vary on how they are implemented.  

@Karl, do you request existing clients be transferred to Peerless? And, if so, does the transfer go smoothly?

When do you think this missing functionality will be restored?

@Darren, I'm running into an interesting issue with SMS providers and the choice of underlying carrier that 2600hz assigns. The most predominant landline DID enabling SMS service is Zipwhip and they are rejecting anyone using Bandwidth.com. It's not Zipwhip per say, but Bandwidth that is causing the problem. Whenever Zipwhip converts a landline DID to their service, within weeks Bandwidth reverts the SMS service back to them. Therefore, Zipwhip has given up and refuses to enable anyone on Bandwidth for obvious reasons.  In fact, if Bandwidth doesn't change their policy, I'm inclined to ask not to use them going forward.  I believe it's small things like this where the option to select the carrier makes sense.

I have some test code written about a week ago whereby I hard coded an auth token. The token currently fails the user_auth validation (as expected with a week old hash), but still allows me to use quickcall. I wonder if that's a bug?

I'm looking to understand how this trigger works.

old school developer background. I like to validate a value is not null before using it. That way I don't have to fail, set value, and retry.

ahh, but if you have many channels open, even that returns a large amount of JSON.

I'm trying to avoid a query that returns a large amount of JSON. I'm thinking to do an incomplete .../channels, which returns a null data value and status of "success." 

I want to test to see if the token is still valid and if not, request a new one. At the moment my routine requests a new token every 30 minutes. It appears that depending on the operation, the lifetime of a token varies.

Is there an API the validates if an auth token is expired and if not, what is the recommended way to validate a token before requesting a new one?

I spent an hour writing PHP code and completed a decent integration to Slack. I type /yealink <number> and it routes the call to my extension. Thanks for putting me on to this...very cool feature! 

Integrating to Slack doesn't seem all that difficult. I installed "Slash Commands," defined a slash command and in the url provided it my quick-call details. Worked perfectly. However, I'm thinking wrap that call around a way to get an auth token and pass the phone number etc.. and you should be good.  

I'm trying to edit a group created in the prior UI. It's no longer accessible in Advanced Callflows or under SmartPBX. 

When I research low-bitrate codecs, two are predominately recommended; Opus and iLBC. The issue is a number of softphones don't support Opus, but do support iLBC. I.e Zoiper.

I'm not sure it's the same. The one in SmartPBX is requiring an extension which I would interpret as a "RingGroup," not "Groups" as defined in the prior UI. 

I believe we are waiting on Lazedo, as per "i'll post an update when it becomes available."

You are awesome! Buy this man a beer at Kazoocon.

Not sure I understand fully, but on a Yealink you can add an Extension value that only gets applied when the BLF is in "ringing" status. Otherwise it dials the initial value.  I'm thinking the feature code should work similarly to park.

yes, "answered" would be indicated by "RED." However, would it be possible to have a feature code like "*98" be a prefix to the mailbox number? (I.e. *98101) This way the BLF could dial out the sequence and reach the voicemail box. Otherwise, the BLF will be interpreted as a callflow.  

In other products, it's called "voicemail hint," where a presence ID (BLF) can be associated with a voicemail box. 

What would be nice is if Yealink provided a way to separate the action of the message button from the MWI subscribe value. This way when the message button is pressed it can dial *98. Let me know if anyone finds a solution.

I got it to work using MWI. On a Yealink here is what to do: 1. Account | Advanced | Subscribe for MWI = Enabled 2. Account | Advanced | Subscribe MWI To Voice Mail = Enabled  3. Account | Advanced | Voice Mail = <your VM number> The caveat is that the message button, when pressed, tries to dial the VM number set in Account | Advanced | Voice Mail and this will be interpreted as a callflow.

@lazedo, are you saying that we can subscribe a BLF to the Voicemail number?