Jump to content

FASTDEVICE

Members
  • Posts

    437
  • Joined

  • Days Won

    26

Posts posted by FASTDEVICE

  1. @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.  

  2. 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. 

  3. @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. 

  4. 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? 

  5. 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?

  6. 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.   

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

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

    Quote

    For existing phones which have been provisioned via RPS once, an additional two-factor device authentication is now required and implemented when these phones request for RPS service again. If the authentication fails, the phones will be blocked from accessing RPS service. 

    Quote

    When you are doing a factory reset to reconfigure an existing phone via RPS service again, you may get a prompt on phone screen asking you to enter the last 5 digits of the Serial Number of this device. Please follow the instructions to enter the digits to finish the authentication. Otherwise, the device will not be able to connect to RPS.

     

     

     

  9. @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.  

×
×
  • Create New...