djanjic
-
Posts
164 -
Joined
-
Last visited
1 Follower
Recent Profile Visitors
7,863 profile views
djanjic's Achievements
-
Hello, we have a customer which needs to receive calls without inbound caller ID being displayed. This is the requirement, anything can be displayed but the name or the caller ID of the caller. I tried creating a separate trunk for this customer where i basically stripped everything and still no go. We use ThinQ/Commio as our trunk provider if that has any relevance. Has someone done this before? Dusan
-
Is there a way to setup an external source, IE, server, HD, NAS, for call recording? We have a customer that may need a very long retention time for their recorded calls. I am looking through documentation and I don't see the way to do it. Does anyone have the solution Dusan
-
Hello, has this issue been resolved and if it has what is the current release which corrects it? Dusan
-
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?
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
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?
-
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
-
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?
-
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?
-
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.
