Logicwrath
-
Posts
578 -
Joined
-
Days Won
21
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Logicwrath
-
-
Check this out:
-
Have you tried or seen this yet?
-
This would be great!
-
I have not re-visited this since I made the original posting. I was hoping to get some kind of official response. We use Yealink phones. You can logon to the phones web interface, and then go to the Status -> RTP Status page. From here you will see what the "Remote IP" is for the current or previous call. I found that when using US-CENTRAL it is using RTP media from SJC which is on the west coast. I have not tested this again since I posted it. I suspect it is still doing it. I moved all of my phones over to US-EAST for now until this gets some review.
Are there media servers in Chicago or only in US-EAST and US-WEST?
We see packet loss and poor audio from using SJC media servers as we are in Michigan near Chicago.
-
Did you check the phone settings or open the config in a browser to see what you actually get? We have seen it where the "Inherit" tool tip style text in gold shows what we expect but the actual values in the configuration are different. We only noticed this because we are now checking to make sure all of our us-central and us-east clients are not connecting to the us-west proxy.
For example, all of our Yealink phones configured for US-CENTRAL right now end up getting media servers in US-WEST. This causes packet loss and audio issues.
-
Did you try factory resetting the phone to see if it removed G722 correctly after that? The Use User Settings options can cause issues if you want a setting overridden that you manually changed in the past.
-
The Primary Address on Account 1 is correctly inheriting the Primary Address from the account level. The Primary Address on Account 2 is not inheriting the correct address from the account level.
We have US-EAST at the provider level settings.
We have to manually specify US-EAST at the account level because the inherit is broken there.
The Primary Address on account 2 is showing up as US-CENTRAL. Manually specifying US-EAST on the Primary Address field for Account 2 fixes the issue and overrides the broken inherit.
-
Yes, I have reported it before too. However, I recently committed to reporting "Inherit" bugs so I am going to start doing it again.
-
Hello,
First, Choosing "Inherit" for the "Type" and "Account" fields on Combo Key 1 is working. It successfully inherited "Line" and "Account 1".
On combo key 2 the "Inherit" for "Type" succesfully chose "Line". However, when choosing "Inherit" for "Account" on this key it incorrectly chose "Account 2" even though the tooltip says "Inherits Account 1 from the Defaults".
I did not test this on Combo Key 3 but I assume it would probably increment to "Account 3"
-
Everyone, this type of collaboration is going to drastically improve the product. I strongly believe that getting the community involved in the planning and development of new features is critical. I suspect it would be hugely positive if there were more enhancement style threads requesting feedback and/or feature requests for projects in development. Give the end users and re-sellers the ability to point out what is most important.
Josh, thank you for taking time to post.
Rick, thank you for asking questions.
-
Yes, we have seen inherit fail to work as intended occasionally for certain fields. I will try to start reporting them here for review. I just wish I knew when stuff was fixed so I stop working around them.
-
e,
One thing I like to do when troubleshooting provisioning stuff is to pull up the config in a web browser before and after making changes and see if the config is the same or different. You can copy the URL from the phone and then add the MAC address .cfg to the end of the URL. The MAC will need to be lower case. This might help you identify if something is getting set right.
This way you can see the changes without having to worry about "Use User Settings" as well.
-
I agree. Every time I look at this I have to stop and think and try to remember what it means. It is too vague.
-
I just spoke with someone at one of our distributors who suggested that Yealink will be unlocking better versions of their OPUS codec sometime this fall in a firmware update. This is great news and I hope it ends up sounding much better.
-
We have used video successfully with Bria to Bria in the past. It should work if it is supported. Make sure you have video codecs setup correctly. Also, make sure you don't have to take an action to turn on video when you start your test calls.
-
e,
Your video is private. However, we have noticed that Inherit does not see to work on the Account field as well.
-
It seems the provisioner is constantly having issues with inheriting settings. The good news here is that it would probably be easy to create some kind of automated check and balance system where anytime you add or remove features to the provisioner you could have a file generated and check it against what you expect to be there and find any bugs. It seems that every time we roll out new features these new settings often have problems where the "Inherit" feature is not actually working. I suspect you could have a script check database fields against a generated CFG file and look for errors. This would help root out inherit issues.
In this case we are trying to make a quick change to the proxy address being used.
At the "Provider Settings" level we have a proxy address set. At the "Account Settings" level we have the proxy set to "Inherit" and tool tip is correct. At the phone level we have it set to inherit as well and the tool tip is correct.
It seems this is not working as the only way I could get the config file to update to the correct proxy was to set it at the account level. I would prefer to set it and the provider level and be able to change it globally as needed in an emergency. I set it as US-EAST at provider, left it black at account, and blank at the phone levels. A factory reset was setting it as US-CENTRAL. I opened the CFG file in a browser and confirmed it was incorrect there. After setting it at the account level it is now correct at the phone level.
Please consider fixing this bug as being able to manipulate the proxy easily at the root level is a big deal and very helpful. I also think there are other "Inherit" bugs that have not bee reported or fixed. I will try to commit to reporting them as I find them. It would be great if we could be notified when this is fixed so we could test and change our setup to start using the inherit.
-
I believe the issue here with the bad audio is because of some bugs in how SRV/NAPTR is currently working. I identified the issue in my case as getting RTP media from SJC when we are in Detroit. It took me some time to figure this out because my original phone had US-EAST manually specified as the proxy so the only difference I could think of was the new phone model. After some troubleshooting I figured out that the audio issues were from packet loss and jitter. I ended up creating a new post in PSTN Connectivity about the SRV/NAPTR RTP issues so it will get some exposure.
-
Just to clarify further in case this is hard to follow. When using SRV/NAPTR and selecting us-central.p.zswitch.net as the outbound proxy the phones are using SJC for their media servers in the 8.30.x.x range. We are now having to update all of our configs to use US-EAST until this gets reviewed and resolved.
-
Hello,
On the hosted platform are there RTP media servers in all three locations East, Central, and West?
I am troubleshooting audio issues and it seems like we only ever get 8.30.x.x or 8.36.x.x when specifying the outbound proxy as either us-central.p.zswitch.net or us-east.p.zswitch.net.
When the outbound proxy is configured as us-central.p.zswitch.net the RTP media is typically 8.30.x.x which is high latency with packet loss.
When the outbound proxy is configured as us-east.p.zswitch.net the RTP media is typically 8.36.x.x which is performs better.
I was hoping and wondering if there are any RTP media servers in ORD. If there are I am trying to figure out why they never get chosen.
Additionally, if there are only 2 sets of RTP media servers I am going to have to start specifying US-EAST because using the media from 8.30.x.x is not working out at all.
When I look at the 2600hz SRV records I see references to ORD and EWR for US-CENTRAL. SJC only gets referenced in US-WEST. Please advise.
*edit*
Just to clarify, this is when using Yealink DNS-NAPTR with port 0 for server host and outbound proxy.
-
Hello,
I am not satisfied with G722 and Yealink's 16Khz opus implementation. Is anyone aware of any handsets that offer ultra wideband support? The Bria softphone for example implements 48 Khz opus. This sounds much better. Are there any handsets out there with better audio codecs.
I believe Polycom might be the phone too look at. I am trying to figure out which phones support the best wideband codecs. It looks like the VVX 500 supports 722.1 and 722.1C which might be significantly better. Does it get better than this? Which phones support the best codecs? Which models should I be investigating?
Is there another play besides Polycom building phones with ultra wideband audio?
Any help or advice is appreciated. Thanks!
-
I am getting another T46S to test with. I want to see if a new T46S will still do the audio clipping. I used the default 81.0.90 and 81.0.110 firmwares with G722 and opus and I am getting audio cutout/skipping. Perhaps the unit I was sold is defective. I will follow-up.
-
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.
-
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.
Call Park RingBack time change
in Tips and Feedback
Posted
Yes, I agree that this would be a nice enhancement.