Rick Guyton
-
Posts
628 -
Joined
-
Days Won
41
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Rick Guyton
-
-
Sorry , should have been more clear. I'm having an issue with my clients coming up with the wrong name on t mobile cell phones. One of my clients has an employee named jennifer LASTNAME and when anyone from the company calls a T mobile customer the caller are shows Jennifer LASTNAME instead of the company name that's programmed in Caller ID.
-
Is anyone else having a sudden surge of issues with incorrect caller names coming up? Apparently Tmobile uses an app called T-Mobile Name ID. I'm just finding out about this, but it seems like they use whitepages.com to supply names associated with phone numbers. This information has been wildly inaccurate for a few of my customers now. The only way to remove the info is to report it as incorrect from a t-mobile android phone. WOW... just wow...
Anyone else seen this? Have better fixes? -
Well, in a best case senario, it'd be nice to be able to have conflicting EXTs call eachother somehow. For example if ext 100 in accountA called 100@accountb.domain.com or *FETCODEFORACCOUNTB100.
But, all the other "caveats" you've listed would actually be very beneficial to us. I mean it'd be nice if they could see BLF. But, I can code around that workign directly with the phones. -
Yes, for us it's for extension to extension dialing between accounts. For us there's a two fold need. First, one of our clients keeps buying out other smaller businesses. If we could set them up on their own account we could retain their existing extension numbers, mailbox numbers, ect. All while allowing them to dial out to other accounts. This also prevents them from for example intercomming the CEO. (Yea, that happened) Second, it allows location managers to manage their own systems via SmartPBX without messing with other locations. This is a really big need for us.
-
:( Ok, need to find a way to transfer calls between accounts. I was hoping SIP URIs would do it. I know I can do it with DIDs. But that's going to chew up a heck of a lot of DIDs.
-
Ok, what about between accounts?
-
Ok, so to be clear, Kazoo can't receive SIP URI calls, only place SIP URI calls to outside systems?
-
Is there a way to connect from an external system using a SIP URI instead of a DID? For example if I have a device setup as user_2484 on a realm RingMe.mydomain.com, can I route calls to user_2484@RingMe.mydomain.com? Is there another way to do something similar? I know there's a SIP URI "device" but it seems silly to have to setup a whole new device for this.
-
Hey Darren, on the CNAM dip bit, I'm assuming you cache responses so that you don't have to dip every single time. Is that correct? If so, will the billing system be able to differentiate between cached dips and non-cached dips as to not charge for the former? Also, will a reseller be able to define the max life time of a cached CNAM on their respective systems so that we can balance responsiveness to changes VS cost?
-
I'm almost never accused of doing something the "new fangled" way. I need to take this in for a minute...
....
......
Wait For It
..........
.............
Awww yea, that's nice. ;)
Gun to my head, I'd use v1/accounts/{account_id}/webhooks. First, if you are relying upon webhooks for other parts of your app, you can double check it and make sure they are still there whit this data. So, at least it wouldn't be a totally wasteful request. Second, I don't think very many people even use this feature. So, most accounts will probably be empty. Those that do use the webhooks should only have a couple. So, in any scenario it should be a pretty small request.
I'd still assume the token's good for some length of time. At least a minute or two. Can't imagine checking it before every single API call.
The best docs I've found are here: https://github.com/2600hz/kazoo/tree/master/applications/crossbar/doc
Maybe you can find something that works better for you. I don't see any functions that simply validate a token or return static data though. -
Maybe do a GET on v1/accounts/{account_id}/webhooks if absolutely needed? If it returns anything, it should be pretty small.
-
Hrm, I donno about channels. They seem to be a bit touchy about the use of that API. May I ask why you are trying to catch that on the front end? Why not just grab a new token when you see it fail?
-
Couldn't you just make any old API req with the token and see if you get
"status":"success"? Just as an example, do a GET request on /v1/accounts/{account_id} -
You are wanting to validate that a past token was at one time valid? I'm assuming so that you can request a new one using your API key, but only if the token was once valid?
-
Hrm, never used it in that kind of environment. If you try it out, please let me know how it goes. Oh, BTW, they used standard Ni-MH AAA batteries. I've seen clients pop re-chargeable battery stations right next to the phones and I've not seen one spontaneously combust yet. But the manufacture doesn't seem to recommend it.
-
We use the W52P all the time. I didn't know that they were finally included in the provisioner. Thank goodness/Why isn't 2600 telling me this? Ugh.
Anyhow, other than not having Combo/BLF buttons they can do everything a T46G can. I've written my user training specifically so that all operations I train on can be done via both types of phones.
Call quality is impeccable.
Battery life is ok, but not incredible. SET THE EXPECTATION ON THIS! These are great for carrying on a belt clip and answering the occasional call that the front desk can't pick up in time or to respond to pages. (BTW, intercom doesn't work last I checked) But you aren't going to get 10 hours of talk time as advertised. I'd say on a good day, you'll get 48 hours standby/5 hours talk time before needing a 5 hour charge.
Range is always one of those fickle things. Depends on building construction materials, noise, ect. But I've generally never have a problem with single story, single building environments even large ones. I've got one at my home. My house is old and has some weird construction elements. Long story short, I'll just barely get though 3 block walls and that's pretty impressive to me. -
LOL, I feel like an old fuddy duddy every time I talking to you Raj. I'm replying to see see what everyone else says.
-
Wowah, Karl's official now. :)
-
Happy to help!
-
Wow, amazing. Thanks!
-
Hi Eugen, I called about this about a year ago and the answer was no and that they weren't interested in developing it. Don't think that's changed, but I could be wrong...
-
Hey Logicwrath, try it again. A couple months ago they changed the way the provisioner works on a base level. I've been successfully using RPS ever since. If it still doesn't work go into ADV Provisioner, hit the gear and then hit "unlock".
-
DHCP option 43 works for yealinks to specify a http or https provisioning server.
-
Hole...Lee...Hell. That's awesome. You have no idea how happy my clients are going to be! Thanks!!!
Caller Name on T-Mobile?
in Product Discussion
Posted