Jump to content

proskater1223

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by proskater1223

  1. Is there a way to use the old app interface? Prior to version 69, the app interface was ok and workable. Now version 69 feels like someone made it 1/8th of the way through development, and just considered it "good enough". We have had just about every customer that tried it complain. It was to the point that we had a customer tell us to change it back, or they are going to switch to another platform. One made the comment "It's no longer usable." and "Where did everything go?" We were able to get them back on 68.0.30 but now we are having SMS issues, and we are told the fix it to switch to version 69.0.4. So now we are in a situation where we either piss our customers off with the horrible interface or tell them they can no longer send sms messages. What are others doing?
  2. After digging, I did find that we had a customized template on the root level. I cleared that, and moved out modifications to the "Yealink General" parameter of the root user. After clearing that up, I found that our filters were wrong. Wrong: ldap.name_filter = (|(sn=*%)(gn=*%)(company=*%)(category=*%)) ldap.number_filter = (|(telephoneNumber=*%)(mobile=*%)) Correct: ldap.name_filter = (|(sn=%)(gn=%)(company=%)(category=%)) ldap.number_filter = (|(telephoneNumber=%)(mobile=%))
  3. Version 68.0.28 My Yealink LDAP looks like the following: ####################################################################################### ## LDAP Settings ## ####################################################################################### #Configure the search criteria for name and number lookups. ldap.name_filter = (|(sn=*%)(gn=*%)(company=*%)(category=*%)) ldap.number_filter = (|(telephoneNumber=*%)(mobile=*%)) ldap.photo.enable = 1 ldap.enable = 1 ldap.host = xxx.xxxx.com ldap.port = 2345 ldap.tls_mode = 0 ldap.base = ou=people ldap.user = xxx.xxxx.com\211 ldap.password = xxxxxxxx #Specify the maximum of the displayed search results. It ranges from 1 to 32000, the default value is 50. ldap.max_hits = 50 ldap.name_attr = cn sn givenName ldap.numb_attr = telephoneNumber mobileTelephoneNumber ldap.display_name = %cn #Configure the LDAP version. The valid value is 2 or 3 (default). ldap.version = 2 #Conifugre the search delay time. It ranges from 0 (default) to 2000. ldap.search_delay = 1000 #Enable or disable the phone to query the contact name from the LDAP server when receiving an incoming call; 0-Disabled (default), 1-Enabled; ldap.call_in_lookup = 0 #Enable or disable the phone to sort the search results in alphabetical order; 0-Disabled (default), 1-Enabled; ldap.ldap_sort = 1 #Enable or disable the phone to query the LDAP server when in the pre-dialing or the dialing state; 0-Disabled (default), 1-Enabled; ldap.dial_lookup = 1 We can search after pressing a few letters, but at the start when you hit directory, it states "LDAP Server unavailable."
  4. Has there been any update to the ldap and yealink? I am still seeing Server unavailable when we go into the directory.
  5. When we try to add a phone to yealink DMP, nothing happens. We have had it working before, and it just randomly stopped working today while trying to add a phone. Digging through the logs, I keep seeing lines such as "RPS add 249ADxxxxxx domain xxx.xxx.com (4 pending)ⓘ" The pending seems to count up the more I add and remove a device. Is there a limit to the number of API calls Vodia does in a given moment, or does it run on a cron job? Could you shed some light on the "pending"?
  6. We are running on V68 until the UI gets fixed on 69. We are also seeing this with our windows app. Every time you close it, and reopen it, it will say it is taking longer than usual. I have made sure I have the latest windows store version. Update: Windows store lied to me. I went back into it, and saw I had an update to Vodia. The update seems to have fixed the connection and relog issue on my side.
  7. There is one thing that is holding us back from moving 3cx customers to our Vodia platform, is group inbound SMS. We have customers that require the ability to have multiple people see inbound SMS messages and then reply. Maybe dump the sms messages into a chat, then assign what users have access to the chat. I know Vodia is working on revamping the user dashboard, hoping you could add this aspect.
  8. Thanks for the screenshots. Yeah, that does look a bit "alpha". We personally will need to wait till that is corrected, as we have a good amount of users that are used to Version 68's look. Taking away a good amount isn't a good look.
  9. Is there any screenshots of the new frontend? I don't feel like spinning up another machine to check.
  10. AA only allows you a max DTMF of 0-9. It won't allow you to use option 11.
  11. I have been having issues logging into the windows app when two factor authentication is enabled. It would always tell me my username and password were incorrect, until I disable two factor authentication. Once two factor authentication is disabled, i am able to login with no issues.
×
×
  • Create New...