Karl Stallknecht

Comcast in Virginia is *mostly* a nightmare...surprisingly it's much better in D.C. and Maryland.

Nothing surprises me about Comcast ;-) It's definitely better in some places than others though. I was about to say Verizon FiOS is like heaven when we have a customer with it, but their new "Quantum" routers have serious issues with SIP signaling where random phones don't ring, or phones keep ringing after calls are answered. We immediately replace the Quantum routers with something else and all of the problems go away. We've literally never gotten any other complaint from a FiOS customer (and now we get none because we know to switch the router out before setting them up). My fear is that Comcast will start doing the same thing. So far so good with their issued modem/router units (knock on wood), but the huge problem with Comcast is that if you have a static IP, you HAVE to use their modem/router and there is no way around it. What happens when their routers start causing VoIP issues but the customer has to have a static IP? Then what? And if you're wondering why Comcast requires you to use their modem/router when you have static IPs, it has to do with a combination of how they handle subnetting and their specific implementation of RIP. Basically comes down to how they have decided to ensure you aren't announcing the wrong IPs. And no, bridge mode might not be the solution either because their bridge mode is still doing Layer 3 functionality.

Specifically what do you mean by call quality? As in the call itself was cutting in and out and made it difficult to understand, or it just didn't sound as crisp and clear?

I actually filed this a long time ago and it got morphed into call center, which isn't what I was looking for. We just wanted basic eavesdropping for non-queues.

We've had quite a few clients ask about this, as well as eavesdropping. It seems like there is definitely a lot of interest.

Woohoo! 7200 works now! Thanks!

Hmm odd, I'll have to try that. Thanks!

I did, but there's an issue with the template engine and it incorrectly interpreted it. I filed a bug somewhere but of course I can't for the life of me find it...

Nope, literally nothing else in it:

@Logicwrath: I almost always use Monster in Incognito mode 

I tried creating a new call recording element on a call flow and got this error.

Ugh, it's back to 600 now...

Glad I'm not the only one who can't stand 24 hour time lol.

Great :-)

Edit the macro in the email template as follows: {{date_called.local|date:"l, F j, Y @ g:i A"}} This will produce something like this: Tuesday, February 28, 2017 @ 12:52 PM The reason I have an @ symbol is because I found a bug where if you use the word "at" it thinks it's part of the macro...I cannot for the life of me find where I submitted this bug, but last I checked it was still an issue. See the following page if you want to customize further: http://php.net/manual/en/function.date.php

KAZOO-5364

Looks like 3600 is the limit. Any chance we can get it bumped up to 7200?

Ah okay, very interesting, thanks! :-)

Yikes, what a complete mess...

Oh, wait...having more phones in a ring group can cause problems? What exactly is the reason? I'm curious now!

I couldn't agree more! :-) Our clients seem to all want something wildly different, so just being able to set it custom on each account without going through a ton of API calls would be huge. One of the things we love about the 2600hz platform is that we can customize all sorts of things on a per-account basis (i.e. extension length, feature codes, hold music, etc). Having the flexibility to be able to customize this too (easily through the GUI) would be awesome.

Ditto to pretty much 100% of what Rick has been saying in this thread :-)

The first example I understood, which is why we always wait to set e911 addresses until after the port completes. The second example I didn't realize was the case. I assumed that the PSAP would get the caller ID number from you, and then run a search to see which address was associated with that and then the address info from Verizon would pop up.

But I thought it wouldn't have anything to do with you? The call gets routed to the PSAP and they see the existing number, which already has an address configured from another provider...

Right, but the caller ID for 911 will be set to their existing number which should already have an address configured with it from the existing provider. So it doesn't matter, correct?