Logicwrath

Any updates on this?

How do we transfer a call to park in Teams? When you click on transfer and then type something like *31 it will not allow you to transfer the call because it can't find a match. I assume this is some kind of setting or permission. How do we allow transfers to parking slots like *31?

I literally just rekt myself on this right now on 2 Yealink T57W phones. For some reason, they had ignore completed elsewhere checked (no idea why btw, did CSV import do this?) and I edited the device to uncheck it in Smart PBX and lost all 29 buttons on both devices. I now have to reconfigure 58 buttons in advanced provisioner. /facepalm I now see that every device has "Ignore Completed Elsewhere" checked. I believe CSV import caused this. Unchecking the box in advanced call flows does not erase provisioning profile. Editing device in SmartPBX to uncheck box does.

Are you referring to Advanced Callflows?

Hello, I am not sure if you consider this a bug or not. I know it has been brought up in the past. It would be great if you could fix this. We have customers and technicians that will edit their device and then they lose their provisioning profile. It's pretty frustrating when a customer calls you up and none of their phones work because they decided to rename every device in the list. I imagine this could be fixed because, when you PATCH a device via the API the provisioning profile is not lost. It's only lost when you edit the device and save it from the SmartPBX. Please consider fixing this behaviour.

We set a caller-id manually on a user in advanced call flows or through the API. We need to do this when we are onboarding users and we don't have the phone numbers ported into the system yet. Next, I go to assign some temporary DID's to users in Smart PBX. Smart PBX shows the message I pasted above and then removes our manually setup caller-id. I then have to go back in and set the caller-id again after I assign the DID.

When assigning a DID to a user, SmartPBX is deciding to disable a previously set caller-id number. This is frustrating and creates extra work. Please don't remove my previously set caller-id without asking. I would prefer this did not happen.

Any updates to the dynamic location 911 routing? I seem to recall it mentioned that something like this was being worked on where we would be able to merge in address 2 data dynamically. We need this.

I was trying to think if there was a clever way to use CAMP for this. However, I don't think you can camp an active call. https://docs.2600hz.com/dev/applications/callflow/doc/camping_feature/

The setting to allow the same account to register multiple times has been turned off since Kazoo essentially generates revenue based on the number of accounts that get setup. As I understand it, you can register multiple devices using the same account. However, whichever device was the last one to check in to the cluster is likely the device that will receive any inbound calls. You can for example, create a generic account configured to dial out as a secondary phone number and register this one account onto multiple devices at the same time. Any outbound calls placed to this account should work normally. It would be the incoming calls that would generate a problem. However, in this use case, you may not require inbound calling since the main priority is the ability to switch phone numbers for an outbound call easily.

It looks like you can provision some changes around this. See here: http://forum.yealink.com/forum/showthread.php?mode=linear&tid=1474&pid=#pid

For the T33G there is an issue around white noise generation where you can hear a sort of sine loop audio in the back ground. The newest firmware fixes most of this. It is actually a sort of sine loop audio that phases high and low. You can hear it when you pick up the handset and remove the dial tone in while the handset is still off the cradle.

We also need v85 support for for using the T5XW series Bluetooth with Yealink's new line of DECT headsets like the WH66. I have to manually upgrade phones to v85 to pair. Also, the latest T33G v85 firmware fixes some handset audio issues.

Hello, I like the new interface/app you created for this. It will make it easier to train and does not require advanced call flow access. Some feedback: It would be nice if we could specify or enable a feature code for people to automatically add the last received call to a default blacklist.

I think what is happening for me is that I have a sprint mobile device also assigned to my user but turned off. The device is likely consuming the SMS first (even if its off) and it never makes it to my Yealink phone.