FASTDEVICE

@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?

Our SMS to Email gateway is code complete and in beta testing with a couple providers. We should be ready by next week for additional beta testers.

I have a question regarding the message length of SMS. I see the length following the 160 character limit before being split. However, when messages are larger than 160, they are following the 153 segment split but are not being rebuilt by the recipients device as a single message. They come in as multipart messages. Any thoughts as to why or what should be done to enforce the device to rebuild as a single message?

@Logicwrath - according to the directions, it only works when an enabled DID is associated to a user, not a ring group.

What I have learned so far following directions here on the forum is... If I associate an enabled DID to a callflow as described in the forum directions, messages do show in the text message inbox of my Yealink. Pretty cool. However, if I reply to a message, although the phone states the message was sent, the text is not received on my mobile phone. Any additional configuration required, or sending is not supported?

I heard we can configure a Yealink phone to use the new SMS service. Is that correct and if so, how do we configure the phone? I don't see a way to link the SMS enabled number to the phone.

It's probably an acceptable solution but consider the Grandstream HT801 is an analog adapter that requires the ATA and an analog phone.

I don't believe there are timers in Kazoo that can be used for this purpose. However, you can create your own and use https://docs.2600hz.com/supported/applications/crossbar/doc/channels/ to invoke a hangup after the expired time.

We are currently working on an SMS to Email application. People will be able to SMS your 2600hz landline number and you will receive an email with the content. Additional, you will be able to reply via the received email and the sender will receive an SMS with the content of the email. Looking to have this in beta in the next few weeks. Message me, if you are interested.

@esoare What you are asking for can be done with CAV described in the CDR detail. The issue is the CAV is only inserted in the CDR details and not in the CDR summary. There is a huge difference in the amount of processing it takes to search and process the detail CDRs vs the summary. The idea is we can detect that a customer reached a menu from the Summary and then dig deeper into the CDR detail to determine which menu option they selected. Otherwise, we need to check every leg of every call just to determine they reached a menu. It's time consuming. Looking for a better way.

Any movement on this? Has there been a change that allows the CAV or any custom data for that matter to be inserted into the summary CDR and not just in the details? We need custom data in the summary CDR for quickly identifying the callflow path.

Has this been discussed and if so, which firmware allows customers to factory refresh their existing phones without being blocked.

Does anyone know the address and port for the 2600hz hosted Sandbox websocket server?

@mc_ custom_application_vars DO NOT appear on callflow webhooks, hook_event : channel_bridge, hook_event : channel_create.

@safarov that is what we are doing now but the convenience of creating and managing API key is better. Also, admins are more likely to accidently reset/ delete a service user. Have had it happen several times. Admins forget about the service user months down the line and since they are not associated with a device look at it as a security risk and delete the user.

Is it possible to create multiple API Keys? I'd like to authorize several applications using an API Key but want the flexibility to delete and/ or change them without affecting other authorized applications.

Are you building a WS client in python? If so, is it standalone? We use Laravel/ PHP for our app development and Lumen for microservices.

I'm trying to confirm that physical phone holds are creating hold events in websockets. There is no equivalent in Webhooks so I need to move to Websockets. I was planning to test it out over the weekend and your question seemed very timely. Thanks for confirming!

@Rick Guyton was that event initiated by pressing the hold button on a device i.e. Yealink/ Polycom IP phone, or programmatically from the Operator Console Pro UI? I'm trying to detect when a user places a caller on hold from the IP phone directly.

@Rick Guyton tangential question. Does websockets report the hold status from Konami, the device (SIP re-invite), or both?

@Mark Diaz will that work on the shared environment where we don't have the ability to assign fake DIDs to callflows?

Wouldn't it be easier to give each branch their own account and tie them together using DIDs and landline devices? I.e. ext 9000 is a callflow with a landline device that reaches the main DID of another branch where the caller can be greeted by the auto-attendant of that branch and then enter an extension. You will need to pay the 2600hz DID and device fee but it's a solid solution and provides separation of operating hours. I do wish 2600hz would give us the ability to call between accounts without that tax. If 2600hz is reading this, we don't need BLF across accounts just an inexpensive way to tie accounts together. Alternatively, create callflows using vars and branching which is not available through the UI and would need to be implemented programmatically using the API. I don't recommend as changing callflows modified this way would be difficult.