Jump to content
Vodia PBX forum

Harvey

Members
  • Content Count

    47
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Harvey

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. After the PBX was upgraded he does not have the provisioning instructions or config files and xml files any longer. Do you have a synopsis of what needs to be in these files and I can see if I can make it work, please.
  2. I believe you spoke to one of my end users. I will check in with him to see if he has made the suggested settings changes.
  3. Trying to auto provision some SNOM D120s. We are having some issues provisioning the phones where they will not register. Is there any more documentation than what is found here: https://doc.vodia.com/pnp_snom
  4. I can understand how you misunderstood my comment, however as we are deploying a Vodia phone system, not sure why we would be looking to deploy the Yealink phones to a system we are moving from. I suppose there was a leap to expect that when I mentioned we are deploying the Vodia phone system that when we were deploying Yealinks that it would be on the phone system we are deploying (Vodia) and not on a phone system that we are moving the customer from ..... Anyway, the answer to your question is no, we have not deployed Yealink phones on their old phone system.
  5. I did not test the Yealinks on that system. And I'm not going to. You asked what we were trying to do, I've explained it in the forum, talked about it on the phone and showed the video. Can't be done by Vodia? Fine. Can be done by Vodia, great.
  6. We're using the Yealinks with the Vodia solution, not on the old system.
  7. I can ask for that, yes, though I can tell you I have seen this on Yealink phones using 3CX. And I have of course seen it on Cisco phone systems. So this is not a foreign concept.
  8. They were using Mitel 5320, 5330e and 5360 . We are deploying Yealink T27G and T46S. Customer also thinks that every phone is registered as a hot desk, unassigned phone and each one has to be signed in to. Perhaps this is a way to get around the issue? However, can we force an extension to only be logged in to one phone?
  9. Based on our phone call earlier today I chatted with the customer and their current system. This is what they sent back to me
  10. Sorry, no. I don't dictate that. That is by the client CIO and nope, sorry, it is not a win win. They see this as a problem that we are not giving them as feature rich a solution as what they are coming from. Sorry, that is how the CUSTOMER sees it.
  11. OK, so two things. 1. That is great, we have been looking for when the new app base was going to be released. Is this on the Windows platform as well? (the interface before was antiquate and crazy) 2. These are state contracts where they are mandated to have certain things onsite. And when audits happen, those things need to be there. Like a desk phone with the preprogrammed numbers to various services. So while I love that a new client exists, it doesn't solve this problem for my client. Any other options?
  12. Well, it is a social welfare agency with social workers who travel to sites to visit clients, And it is a low paid position and their turn over is 15-20 people a month. oh, and their client's destroy things, like phones, so we built in a replacement of 5 phones a month. So to answer your question, often. This is my first installation of Vodia and I believe I am going to have to eat the 128 seat Enterprise license and move them over to 3CX, where I know all of the things that I need to do are possible. It is a shame because I thought Vodia might be a good fit for my client base. The fact is, a mobile work force is how almost all of my clients are set up and aside from some receptionists, almost every employee moves from desks to desk or from office to office. I just can't fathom how the ability to log a phone out and in to a user is seen as a luxury with the way the work force is going. Thank you for your help and suggestions, but I don't believe the solution is practical.
  13. Right, but it has to be managed (phones die, people leave, etc) and it sounds like a management nightmare.
  14. So if I understand you if I have 150+ users that may move around. So I would have to put 150 MAC addresses on 150 users to make this work? Clearly all 150 won't go to every 150 seats, but from a management perspective that seems like a real bear.
×
×
  • Create New...