Logicwrath
-
Posts
580 -
Joined
-
Days Won
21
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Logicwrath
-
-
Hello,
I have some questions about related to how the mobile product gets billed.
I have a mobile device configured on a sub account. It has credits loaded and I see the credits getting used up. I assume this is from the mobile device. When I click on the account and view "Per Minute" or "Transactions" I do not see any listings about where the credit is going. Is mobile billing getting filtered out of those views? I do not see any calls listed and their costs.
Another thing is I noticed that "Activated Devices" and SMS/MMS get billed as combined single entry per device. Are we not able to pool SMS/MMS usage across all of our accounts?
What about data. The description on the 2600hz website shows "Per Device". I was actually hoping this would get pooled across all accounts. Does data get pooled for all mobiles across sub accounts or is sold and metered per device like the description says?
I noticed in the managed portal that we do not have the ability to turn off data completely. I think the lowest amount you can specify is 50 MB. I would prefer to have an option that says 0 data. Is this something we can expect to see at some point?
Finally, can we get a description or some documentation that defines what types of calls are billed and how they are billed? For example an outbound call, I believe this gets the per minute mobile billing and it also uses a trunk or gets billed per minute. I would like to better understand the billing so I can speak to it or plan accordingly as we start considering mobile for more use cases.
-
-
I did not even know this was available on sandbox. Looking forward to seeing how it works.
-
It is also worth mentioning that the Obihai devices have a great management system from the vendor. I would look into the ITSP management interface they offer. You might prefer using their interface over the 2600 interface for managing these devices. You should be able to add all your devices with it.
-
If it is not working try removing the http:// and trailing slash. Make sure you have working DNS as well.
-
In Advanced Provision for T46S for example current is: v81.0.90. However, the only other selectable option is: v81.0.110. If you notify us of a Current change, we don't have the ability to select the existing current firmware manually to avoid the change if we actually wanted to avoid the change.
I think one thing we could do is start testing the v81.0.110 to try and find problems ahead of the change. However, announcing the change does not improve the safety if we can't avoid it.
I had to check my phone status to find out what firmware was Current for that model. I would still like Current to be specified.
1. Show it like Current (v81.0.90)
2. Allow v81.0.90 to be selectable outside of current.
3. Make sure we have enough time to provision and test out phones on the newer firmware. I suspect it will be available to be selected ahead of the change.
-
Yes, they may be able to improve the OPUS quality. However, I am still seeing that audio clipping in the G722. I only tested over an hour period today. I will test more and see how consistent it is. I am worried that this new T46S model might have some kind of issue itself. In which case I may need to have Yealink review it. I noticed that I occasionally drop packets to Level 3's Colorado DC where the RTP audio is coming from but I don't have issues with other phones so I don't think the very mild packet loss is the problem here.
-
15 minutes ago, Rick Guyton said:
Yea, I agree. Though I think they'll probably announce it when they do it. I'm a little concerned for the first big update. Hopefully they will do something like a staged roll out. All MACs ending with a 1 on day one, all MACs starting with a 2 on day 2, etc
I agree that doing the changes in stages would be best case. I worry that something will get over looked and a setting might get missed or the inherit might be broken etc for a critical item.
Part of the problem is even if they announce the change, the Current is different between models in some cases and I may forget which model is current on which version. The BLF issues were so bad with that one v73 that I would never want to use that. I need to know if I should still be manually setting it on new deployments.
-
I also noticed that the voice quality using OPUS is worse than using G722. I found that using OPUS-WB (16K) is producing a tinny sounding audio that almost buzzes at times. It reminds of when I tested using SIP over TCP. Switching back to G722 is better. This is disappointing. I was very much looking forward to better audio quality with OPUS. Could this be caused from some kind of transcoding problem? I noticed when I open my Bria troubleshooting window it says that the remote server is using opus (64 kbps) and the local audio codec is (32 kbps) so it makes me wonder if some kind of processing is happening to match things up.
I am going to continue testing this out. In it's current state I am worried that I will not be able to use this phone. The tinny audio in OPUS is bad, G722 is better, but I still notice that audio is getting clipped out. I will be talking to someone in a test and then every so often I will hear part of the audio get dropped for a fraction of a second. I confirmed this is only happening on the T46S. I switch to Bria and no issue.
TLDR
1. OPUS-WB (16K) is worse than G722. /me is sad.
2. Using the T46S I am able to pickup and notice a consistent loss of audio where a portion of a word gets clipped out very briefly. This is only happening on the T46S I started testing. I compared the Jitter buffer and voice settings to my T46G and they seem to match up.
-
Manually specifying HTTPS to enabled updates the config correctly so it must be an inherit issue.
-
Hello,
The web server is coming in disabled for the T46S. I checked the Advanced Provisioner and it was set to inherit HTTPS enable. I then pulled the config from p3 and I get this:
####################################################################################### ## WEB Port ## ####################################################################################### ##It configures the HTTP port for web server access. ##The default value is 80.It takes effect after a reboot. network.port.http = ##It configures the HTTPS port for web server access. ##The default value is 443.It takes effect after a reboot. network.port.https = wui.https_enable = 0 wui.http_enable = 0 wui.quick_login =
-
It would be nice if the Advanced Provisioner said something like "Current (v80.0.1337)" instead of "Current". Current will change and I might not know what it is currently.
It would also be nice if you could give us an option to download the device CFG file in case we want to review it for troubleshooting or hosting elsewhere. You could add a download option to the settings cog.
-
In the past we talked about "Locations" in Smart PBX. There was a lot of interest for this. Having locations would make managing 911 easier if we could assign a 911 number to a "location". At this time it is becoming very cumbersome to manage 911 for accounts with multiple locations. We have to edit the user or the device and manually add an emergency phone number caller ID. It would be nice if we could see a list of all users and all devices and how their 911 information is configured. It would be better if we could do mass maintenance against that list.
-
I am seeing listings for Parked Calls in Operator Console. I am unable to pick these calls up. They appear to be phantom calls. I have seen these on 2 accounts. In one case the Call ID is showing a name for someone who has not been there for a very long time. Are these parking spots actually in use or is this a bug with Operator Console?
I have no idea how to flush these out.
-
Hello,
The firmware setting on the W56P does not seem to have any affect. I left it as inherit and my W56P base station was downgraded to v73. I changed it to 80.0.15 and the base station would not upgrade. I also was unable to access the Phone tab of the base station's web interface. I also believe that v73 is not a supported firmware for the W56P. I do not even see it listed on the support website for download. I had to reset the base back to defaults and then for some reason I was able to get into the Phone tab on the web interface and manually upgrade to 80.0.15.
It appears to keep the 80.0.15 firmware when manually installed.
There also appears to be some settings that do not get set. These do not get set as Inherit or when manually specifying a value:
1. Date Format
2. Time Format
-
We have auto dealerships running W52P's with 5 handsets attached. If you opened this up I would prefer to support the max allowed handsets. We are aware of the 4 call limit.
On a side note, those base stations say they support up to 6 repeaters! I am not sure how they do this. 5 handsets, 6 repeaters, and 4 simultaneous calls? I wonder what the simultaneous call limit is when you have 6 repeaters setup!
-
It looks like the oldest firmware for the T46S is T46S-66.81.0.25.zip. I assume you are referring to v81.
-
Hello,
It appears that both of my suppliers are no longer offering the T46G. They had gotten some extra shipments in the past due but this grace period appears to be over. How close are we to Advanced Provisioner support with the T46S?
I read that some people are resorting to provisioning these devices as T46G with some success. However, this sounds like a recipe for disaster.
-
Karl,
I am pretty sure this only affects me because we do not have a "support contract". They basically suspended my login and I think their system might be filtering my emails and/or responses. -
I am no longer able to access Zendesk or submit support tickets. How do I request CNAM Name updates?
SmartPBX will automatically open a ticket every time the name changes. So I can change the name to something fake and then change it back to open 2 tickets. Then I can respond to the correct ticket and say something like please do this update. However, I am not getting any responses to those tickets.
2600hz is still our "carrier" and we have no way to effect the CNAM name without opening a ticket. What is the correct process to request that now?
Is SmartPBX now configured to automatically affect the CNAM name without fees and tickets? -
Hello,
First, thanks for adding W56P to provisioner.
So far I have seen 2-3 examples where a Yealink wireless device (W52P/W56P) is not getting the firmware updates automatically via Advanced Provisioner.
In one case I manually updated to the same version I selected in AP and the update stuck. However, I suspect the firmware update feature may not be working correctly for those devices.
I also noticed that Date & Time -> Daylight Savings -> Inherit (Automatic) setting is not getting applied. I had to manually configure it to get the time correct on a W56P. It kept the setting on reboot. I believe it was configured to do DST by Date even though Inherit was selected. -
It's the new p3.zswitch.net and it appears to be working now. Thanks!
-
I still can't reach the provisioner. It is not responding to ping or allowing me to open configs via URLs that work outside that office. I will be reviewing the firewall again for anything strange but if it's not on your end I am going to have to call Comcast.
-
Hello,
I typically add all devices to Yealinks RPS service. I have a few devices that got added to RPS but were never added to Advanced Provisioner due to lack of support. ie: T46S or W56P
These devices have gotten my sites banned from the provisioner. I assume this is some kind of fail2ban setup.
Can you please remove IP 68.37.xx.xx from the provisioner ban.
Additionally, please advise how long the ban period is for devices that request configs but are not in the system. I may need to deal with this again.
KazooCon 2017
in Product Discussion
Posted
It would be nice to see a presentation about setting up new accounts as quickly as possible. For example, if I need to deploy a new 30 phone account this currently takes a long time to setup. The most time consuming part is setting up the phones in Advanced Provisioner. Setting up 5-25 combo keys per phone manually in Advanced Provisioner makes me squirm just thinking about it.
Perhaps you could provide some scripts, and/or tools to automate this and do some kind of presentation. Most of the time the the configuration is very similar across all phones. In a perfect world the Advanced Provisioner would support some kind of top down inherited configuration for things like BLF or model specific phone settings. However, I would certainly move to scripting if it means i could avoid spending 2 hours mindlessly clicking drop downs and copy and pasting data into fields.