mskenderian

how can I troubleshoot this?

i follow the normal process, factory default, reboots, go into web gui, setting -> provisioning server http: tenant domain name, restart the phone, and it says provisional failed. This all started when i upgraded my dev PBX to 69.0.4, i could not make button changes, so i tried to factory reset it and here i am.

No putting names in the first line doesn’t work. No one hates v69 because of its features. They hate it because of its half baked features. But this is why people are frustrated. I mentioned a bug. And you said oh but look at v69. I am not on v69. I just care about this version for the time being. By the time I get to v69. Vodia will say oh look at v70. The only feature that actually interests me in v69 is the call recording to a S3 bucket. I am hoping that “EC2 recordings This version beginds to support storing recordings in the cloud instead of storing them locally.” means S3 bucket. So I can store them much longer then I do currently. Only reason my development PBX is on v69, so I can test the new fanvil w6116w.

v68.0.30 Last Name doesnt show. and the web password and SIP password are not in the correct order, i dont know which is first. The template says to put in SIP;WEB but it parses it incorrectly.

Is it possible to add a passkey to a script living on a server? I don’t know how that works? if you concerned about basic auth, we should just do what everyone else does. Use API keys.

Oh I see it. We should of added this change to the release documentation. Since it’s a breaking change. It created hours of frustration.

while passkey become widespread, can we display the passkey prompt in v69. i am not against passkeys, but users will get confused onto why they are getting prompted. a simple system level and tenant level setting can ease the pain while users get used to passkey and how they work.

Since we dont have a API section in the forum, I thought this would be the best place to post it. PBX v69.0.4 Debian Test Computer: Windows Command: curl -v -u admin:password https://pbxHostname/rest/system/status we get permissions denied. v68 we get the correct response.

I totally agree. The lack of communication is a big problem. Specially when you are trying to build a business around their software. I don’t use Vodia for queues at all. I just use them for small simple PBX setups. My criteria for a Vodia system is either ATA devices, client doesn’t want SMS, client doesn’t want call recording. Client doesn’t want international calling. I do see a lot of potential. That’s why I have stuck around. I look forward to v69 when it’s production ready. I wish the front end was a separate install from the backend. That way we can add core features to the backend, until front end is ready. API first!

As far as tenant two goes. They shouldn’t have more then 100% since they do not even know about web app or mobile app. I can see mobile app on tenant one.

I dont see it as a big deal, it would of been nice if we had a promo period as far as pricing goes. I rather give more money and see things fixed, but I think thats the real issue. things dont get fixed and Vodia races to the next feature. Documentation is not good. support tickets takes months to get anywhere. Its the attention to detail that matters. Also know what the roadmap is or what issues are set to be fixed would be ideal.

There seems to be a miscalculation for the number of registrations. going into the first tenants registrations page. and the second tenant... i dont understand how both these tenats show up as 150% registration.

can we also add buttons for this phone?

What cost changes? Has pricing changed?

can we add it to the next version of v68. it might be a while until 69 is stable enough for production.

Can we add Fanvil W611W? Fanvil calls it: "LINKVIL by Fanvil Portable WiFi Phone W611W"

what i have done, is restore the whole system to another server then backup the tenant i need. its a pain, but thats the only way.

I would like to setup a catch all user, to accept any phone number from the trunk and play a message. I have clients that have cancelled and i still have the phone numbers. I would like to point all the phone numbers to a Auto Attendant and play a message like "This number is no longer in service.", but i dont want to put each phone number in one by one. When the PBX gets the call it should check who the phone number belongs to and if none, then go to this catch all tenant.

I have 2x shared cores, I am about to go to 2x dedicated and I was debating on the ram. But it seems I will go to 8gb ram. Running Debian. after this upgrade. Would it be wise to go to 4x dedicated cpu and stay at 8gb ram, or is it wiser to do 2x dedicated cpu and 16gb ram.

It monitors everything you want. I even made a custom template in Zabbix to use Vodia API to get system stats and graph it. I just started using Zabbix to monitor Vodia ssl script, I have had many issue where it did not renew the cert. Zabbix.com

I will check that out. thanks.

When does Vodia request Let’s Encrypt SSL certificate renewal? 30 days? trying to setup a monitoring script to check if ssl expired, I have had problems where it didn’t get renewed for some reason.

What should be the blend between CPU / RAM ? currently using 2x cpu and 4gb ram. Should I upgrade the ram to higher amount or upgrade the CPU to a dedicated one?

We would like to have a green/red circle so indicate that there is a connection to the PBX. sometimes they lose connection or password is incorrect and they try to dial out and it doesn do anything. no message. it would be nice to see a green circle at the top to indicate that we have a connection. and a red circle that would indicate there is a problem.

sipcli sipvicious sip-scan sipsak sundayddr friendly-scanner iWar CSipSimple SIVuS Gulp sipv smap friendly-request VaxIPUserAgent VaxSIPUserAgent siparmyknife PortSIP pplsip