Logicwrath

The pictures are not loading anymore but review this: https://forums.2600hz.com/forums/themes/cms/pages/academy/cheat-sheets/devices/setting-up-bria-mobile-softphone

Looking forward to a follow-up if you have time and get this sorted out. https://docs.2600hz.com/dev/applications/callflow/doc/camping_feature/

It works for me when I have tried it. I believe the default behavior will pickup a call from a ringing BLF. Additionally, you can transfer a call, and the grab it back while its ringing. At least this has worked for me with Yealink phones.

I am not sure. I was actually excited about the possibility of using URL to get around the file size limit. I am wondering how the "streamable" property affects media at this point.

I believe the size limit is right around 5 MB.

I do not see any recording timeout settings in the menu schema. You may need to record this on a PC, convert to mp3 < 5 MB and upload manually to a menu. If this is something he needs to do constantly you may need to train him on updating the call flow in advanced callflows or create a script that patches the call flow with the new recordings using something like curl.

I like this answer better than using PIVOT.

We have asked in the past for an option to download a config for a phone. I was not specifically thinking about "last downloaded config" in that request. In the past when we were troubleshooting we would try to pull up the config in a browser to look for errors. This is not a good idea anymore due to the increase in security that 2600hz has rolled out. It would be great to get a config download button. This would let you confirm the settings are there correctly, troubleshoot any errors in the config, and also use the configuration as a base for hosting the configuration somewhere if you need to implement a work around for a specific phone.

I wonder if it is possible to turn on inbound CNAM with the API for the mobile number.

Are you not able to pre-pend anything to the caller ID name on mobile? I suspect you tried that first thing but I am curious.

Any chance this app becomes available once you push the billing stuff into hosted production? I suspect that is coming soon. I need to onboard ~65-70 users and phones soon and this would be great.

I just realized this is a monster app not a stand alone CSV importing solution. The app is available on the sandbox.

It would be great if this was ready. I would like to try it in a month or two when I start configuring a larger client. I don't see any instructions.

Are you on the hosted platform? I was not able to get this working. Have you ever tested this out and got it working? I would love to see someone post a step by step on getting it working. I have another post regarding it.

Hello, I started thinking about this today as well as I was reviewing an RFP. The RFP references Michigan's guide lines for multi-line telephone systems: https://www.michigan.gov/documents/msp/FINAL_MLTS_Guidelines_503991_7.pdf At first glance this it appears that to meet the requirements you need to enter the location of the phone in the "Address Line 2" box of the E911 emergency address: According to that PDF it looks like this will be required for MLTS by December 31st 2019. "Under Michigan law, the provision of an Emergency Response Location (ERL) for every telephone capable of dialing 911 on a multi-line telephone system is required by December 31, 2019." I know in the past we talked about introducing locations into Monster UI to help with managing e911 for larger accounts with multiple locations. As I was thinking about this specific use case (for RFP's requiring the location information) I was wondering if it was possible to allow the location information (Address Line 2) to be merged from the User and Device level when the call is processed. Perhaps this is what you were mentioning earlier in the thread Darren. The wording above makes it sound like all MLTS systems will require this by 2020.

Anything new on this? It would be great if there was a guide for setting this up properly on the hosted platform.

I have no experience with this. However, you may look into the different DTMF types being used by the phones calling the doorbell. RFC2833 vs INBAND etc.. One of the types I think INBAND will blast the DMTF audio on the same audio channel as the caller. You may try different settings on the phone calling the intercom to see if it helps.

I believe by default pressing 0 will exit to your main call flow from a voicemail greeting. The only issue is I do not think you can change where it goes.

Yes.

In my past experience if you do not have something in the main "Fax Sent Receipts" field then none of the users will receive a fax sent receipt. It effectively disabled the sent receipts entirely. As a work around you can submit a fake email or unmonitored email or public folder/shared mailbox in the "Fax Sent Receipts" field and then all users should get their own fax sent receipts as well as the person listed in the field.

Perhaps it would be better to transfer people into a private conference room instead.

You could also consider using a dial by name directory.

What about a menu that says press 1 to call home, press 2 to call your friend.

I started testing a Polycom VVX 411 as well and I am seeing the same errors and unable to receive calls but I can send them.

Hello, I have a specific client interested in using SRTP to encrypt voice calls. I am trying to test these features out but I am running into some issues. Here is what I have done so far on my Yealink T46S. 1. Edited device in advanced call flows. Under the Audio tab I set Secure RTP to SRTP. This erases your advanced provisioner profile for the device. 2. In the Advanced Provisioner under Lines I made sure that RTP Encryption (SRTP) was set to Enabled. 3. In the Advanced Provisioner under Lines I made sure that the Primary Address was set to secure-us-east.p.zswitch.net. 4. In the phones web interface under Account -> Advanced I manually set RTP Encryption (SRTP) to "Compulsory". I was not able to place outbound calls without setting this manually. I am able to place outbound calls and lock shows up on my Yealink phone indicating that the call is encrypted. However, I am seeing some major issues and I was hoping to get some assistance. 1. BLF is not working. The BLF keys are showing a RED X. 2. I am not able to receive inbound calls. The Hangup Cause is "RECOVERY_ON_TIMER_EXPIRE" with a hangup code of "sip:408" Any suggestions on how I could get this working?