FASTDEVICE

@Olaolu Abiodun The first step is to research were to purchase web hosting space as there are many hosting companies. Hosting companies offer low-cost shared hosting and many have virtual machines where you can standup your own web server. It's hard to say which company to recommend as most are pretty good with serving simple XML files. Secondly, you will need to read the Yealink guide on XML configuration to better understand how these files are constructed and what to change. Yealink provides sample XML files and you can even download a rather comprehensive one directly from Advanced Provisioner with all the settings you entered in the interface. If you are not familiar with all this and still need assistance, my company offers consulting.

First, I'd start with making the ID a number, but that's just me thinking of good practice. The idea is to use a single presence id to represent the status of some function. I.e. As a user, I want to know if the office is open or closed. Therefore, using presence ID 9999: when someone opens the office the status of presence ID 9999 is now set to "idle." When someone closes the office, the presence ID 9999 is set to "busy." Let me know if that makes sense.

The BLF should be configured using the value of the manual presence id. Whatever status the value is set to should be indicated on the phone's BLF.

This has been discussed at length. Here is a link to the thread. In many of the cases a menu was used, but you can substitute for a button reaching a callflow.

The configuration option is: voice.tone.callwaiting How to create custom tones https://support.yealink.com/en/portal/knowledge/show?id=d78743e1aeb7fc964a6f93bd

Provided you have the ability to serve web pages over the Internet, you can create an XML file to support the functions you want to change and serve it on your web server. The option to retrieve the file is in Advanced Provisioner under Settings | Custom Config File URL. Please consider to never store credentials or personal information in that file.

Thanks everyone that participated in our Email to SMS middleware testing. It was super helpful and flushed out many issues between carriers etc. We have a decent load on the system and everything is working reliably, therefore, we would like to open the opportunity for testing to those that bring their own carriers. Again, similar rules apply to qualify for the free test period. You must be a 2600hz reseller and please let us know which carrier(s) you are using.

We are in production with our Email to SMS/ SMS to Email and SMS Forwarding application and looking for a few more strategic partners for our phase two "load testing" rollout while our Monster Application is under development. We are providing functionality for free during the test period and you must be on the 2600hz shared hosting environment to qualify. Please PM me for more details. Email-to-SMS/SMS-to-Email and SMS forwarding features will allow resellers to sell message (SMS/MMS) enabled telephone numbers and use email as the main way to send and receive those messages (Conversational Text Messaging). It’s intuitive for business users and gives sales teams unlimited possibilities to communicate with clients. You can select a single user or have many users share a single telephone number. Additional features include auto-respond and forward SMS to email using your own distribution list of recipients.

I was thinking, something along the lines of how preflow works, but have a postflow as a callflow element.

Have you ever taken a survey after speaking to customer service rep? If you opt-in, the call automatically transfers to a survey after the call ends with the CSR. Is there a way to force a call transfer or next callflow element after the call completes/ terminates? Any ideas would be appreciated apart from having the CSR do the transfer, as you know how that may end up.

@mc_ I'm late to the party here, but just getting around to working with hotdesking. If I disable hotdesking for a user, should it also clear that user from all the devices where that user has been hot-desked? My testing is showing that the user remains hot-desked, but unable to logout.

2600hz resolved the segmentation issue by enabling concatenated SMS on their provider's gateway. Thank you 2600hz support!

Any further thoughts on why we are receiving SMS messages greater than 160 characters segmented into several messages? Again, this is not happening with other SMS providers that we tested and I suspect there may be a setting on the 2600hz side that needs to be addressed. Otherwise, we are going to release our SMS to Email application for 2600hz with this segmentation issue as there is nothing we can do but send the SMS body using your API with a limit of 700 characters.

@lazedo We are using your carriers, SMS provider and API https://docs.2600hz.com/supported/applications/crossbar/doc/sms/#about-sms Whenever we receive an SMS that is 160 chars or less, we receive one SMS message. When we receive a message that is longer than 160 characters, it comes in as more than one SMS messages. Using a different SMS provider, ie. Telynx when we receive an SMS message greater than 160 chars, it comes in as one SMS message.

@lazedo We are seeing messages coming in assembled from other SMS providers but not the one from 2600hz. Do we have to perform the re-assembly?