Rick Guyton

Man, you are awesome. I owe you a beer.

@Karl: Don't know. I've been unable to replicate it to get the level of detail Darren's giving. That's been my biggest frustration in all of this. It's been going on for months now. I've been getting these reports since late November. But they are SO hard to nail down because they are so intermittent. EDIT: the best I've been able to get is some CDR info. But a lot of my clients have stopped getting back to me on it. I think they believe I'm just using it to stall them out until they stop bugging me. But I REALLY want that info.

Thanks Darren! Got the update on the ticket, thanks!

Yea, that's the tough part, it's very hard to recreate. We will see the issue for a day or two then it'll go away. Only my most loyal and helpful clients persist in giving me example calls, so it's really tough to nail down..

I submitted a ticket with an example call yesterday... no response yet. Got another report today too...

How are you replicating it?

Yes, we've been hearing this as well for quite some time. But I have had a very hard time getting example CDRs from people. And I know 2600 won't take it seriously without those... So what do you do?

Sounds like you should write a visual voicemail app and open source it for all us. ;)

Both of those features are normally visual voicemail app functionality and Kazoo doesn't have anything like that AFAIK. At least not in the base product. Maybe someone's made something like that on their own. If it were my client, I'd get them using the voicemail to email. The caller ID shows up there. They'd have to dial the number. But, if it's a big enough account, you could probably mess with the voicemail template and include a link that'd trigger the quick call API. might take a little code on your side though...

Did Vern decide to go for it? My impression was that he dipped his toe in, but found it to hard to translate it to other clients. Could be total wrong here though.

Ok, well no one else is jumping on the bandwagon. From what I understand, there's a braintree integration if you are self hosted or on their IAAS solutions. Otherwise, I think they mostly expect that you'll write your own billing glue that hits the API.

FWIW, as an ex-sonicwall fan boy, run and hide from sonic wall on VOIP. The only way I've seen it work well, consistently is with an NSA series. Also, you want to enable consistent NAT, it does help. More info on how it works: https://support.sonicwall.com/kb/sw4320

Wow, cool, thanks, I'll check into them.

Thanks! I'll check them out!

Anyone know of a super cheap carrier for outbound SIP trunking minutes? I know flowroute's $0.0098/min. But I'm curious if anyone is aware of anything cheaper. Don't care about call quality for this particular project...

Thanks Darren, this client is on Comcast and in an area I'm not familiar with. I wouldn't doubt it actually.

No cutting out, you could understand perfectly, just wasn't crisp and clear. Like maybe the HD audio codecs weren't working. I know your a Polycom guy Karl, this was on a yealink. Man, if this kind of crazyness keeps going I might try switching to polycoms...

Has anyone else noticed that call quality over TCP is noticeably degraded? In diagnosing an un-related issue I swapped a phone over to TCP and though it fixed the issue I was having, I noticed calls on those phones seemed noticeably degraded. I understand that there's more overhead with TCP. But these guys were on a 100/100 meg connection and using less than 10%... Just curious if anyone else has seen this.

Has anyone developed an employee training for the 2600hz system that they'd mind sharing? We are hoping to grow quite a bit this year and it'd be helpful if we at least had a starting point for new employee training. Thanks!

Yea, there's one option, but you have to specify port 0 as well or it'll just use regular A record lookup and UDP. the provisioner doesn't give me an option to set the port number for the realm. So I don't know what it sticks in there honestly. Either 5060 or 7000. I know it doesn't use 0 for sure though.

We use NAPTR on the proxy and not on the realm. Fun fact, on yealinks, if you don't specify port 0, it basically ignores NAPTR even if the transport type is DNS-NATPR.

Thanks! I think the real question here is what is the lunch to beer conversion rate? :)

Sure, I understand. I think a one time fee would be plausible eventually. But, in the short term, this would all run off our servers. Even so, curious what your thoughts would be on a fair flat price. Assuming it met all of your requirements of course.

Also, just realized I had a typo. There would only be one CSV with multiple device lines. Obviously, not a CSV per device. :)

Thanks Joseph, we'd be using the python SDK. So, it'd work on both. Can you please let me know what you'd think a fair per device fee would be? This will be critical in determining if we can fund this or not. Thanks!!