Jump to content

djanjic

Members
  • Posts

    161
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

7,847 profile views

djanjic's Achievements

Apprentice

Apprentice (3/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare

Recent Badges

0

Reputation

  1. Has this question been answered? That is a pretty major bug if it hasn't. Some of us are hesitant to upgrade our production systems. Scrolling to release notes it seems that there were a lot of changes from version 68. As much as we would like to implement some of the features it is hard to decide is it worth and what will break with an upgrade! Can someone share their experience upgrading from 68 to 69.2 on a hosted server with about 100 tenents please?
  2. Add to this MOH per tenant. Under General Settings 3 MOH sources are available. But under the tenant, they are not. I can include screenshots if needed.
  3. We upgraded our test system with the latest version 69.1.2. Testing some general features one of the important features doesn't seem to work. Creating few location and trying to assign them to specific user doesn't display anything. Each of the locations contained additional field with floor and room number. Each location is available from the pool down menu for the user but when selected nothing is displayed.
  4. Actually, I do have a syslog file from the phone, would be glad to submit it. But .tar file exceeds the file size allowed here.
  5. UDP works only with username and password, not with the MAC address. Firewall, I can register any other phone behind this firewall, just not the new batch of phones we recently ordered. The phone, base, simply doesn't react to the address of the domain weather is https://mydomain.com or http://mydomain.com. The certificate on the server is current. Unfortunately Yealink doesn't have any logs we can look at to determine what is wrong.
  6. Well, we tried all these options and none of them work. I am wondering if it has to do with new MAC addresses with Yealink? The only registration that works is via UDP with account username and the SIP password.
  7. Ok folks, here is the official response by Vodia support: "We only support one SMS provider at a time, this feature is not available . " So chuse wisely., Dusan
  8. We ordered a new batch of Yealink W73P DECT phones,. Tried to register few of those on hosted version 68.0.14. via MAC address. None of them, three, could register. I read in their release notes that they now support TLS 1.3. I am wondering if that is the case and if there is any way to forced to use TLS 1.2. They have a field for it but I don't know where will I change that on the PBX?
  9. To add my two cents on this topic, our customers are furious about this. As the previous poster said it, it is unusable. This change was not good. Any plans to change back the way it was, this was not an improvement? Dusan
  10. I thought is possible but am not sure how to configure. The most confusing is the setting under "system level", "messaging" Notifications, that page allows only one provider, one API token, one identification. Where would I set up second provider?
  11. Hell All, on the hosted PBX with multiple tenants can you use more than one trunk provider for sending and receiving SMS messages, let's say Questblue and ThiQ-Commio? If so how?
  12. When we were testing 68.0.13 beta we had agent group created. Only the extension who had an ANI originally assigned to it would receive the incoming text, the other extension in the agent group would not. I even sent a log of that change to the support. So either I am not understanding the Agent group or it is not working the way it was meant to work.
  13. The link used was the only one one on the portal, I wasn't provided with a specific link. I would love to have it so I can hopefully put SMS behind me.
  14. Hello again, back on this topic. This is still not working correctly, at least what was described in one of the previous answers. Multiple extensions cannot receive inbound messaging if they are in the agent queue. Also, In my attempt to finally resolve these issues I tried updating to 68.0.14 last night. Unfortunately the link on the site downgrades you to .0.04. even though that the release notes talk about .0.14. This getting very frustrating since we wasted a lot of time on this issue. Would you please be so kind to keep announcements current with correct links to the latest version. I think all of your users would appreciate this, thank you.
  15. Hello Richard, I had the same question myself and from the conversation with Hamlet yesterday it appears that the answer is NO unless something has changed in the latest 68.0.14 version. My understanding was that each extension has to have its own ANI.
×
×
  • Create New...