Karl Stallknecht
-
Posts
1,154 -
Joined
-
Days Won
21
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Karl Stallknecht
-
-
We get one of these emails every time we setup a new account, but then we don't get any more after that....odd.
-
Depending on the model of Polycom it sometimes likes the SSL and other times doesn't. I think it's an issue of older Polycoms versus newer ones. We were trying to get an older Polycom to provision and couldn't, and after contacting 2600hz support they told us not to use SSL - we weren't even aware of this problem since we had been using SSL on VVX 400s (newer Polycoms) with zero issues.
-
Sooooo when are websockets coming? I was told exactly a year ago that they were about to be released within the next few weeks :-(
-
Not sure, sorry...to be safe I just leave them as BCC but I would check with them for an official answer.
-
Oh, that's weird...I'll just copy and paste it.
I asked the following:
--------------------------------------------------------------
Some of the email templates (i.e. for device registration) are set to go to platform_alerts@2600hz.com. Should we leave this as is since it is how 2600hz monitors all of their clients, or can we change it to our own monitoring system and still have 2600hz get the notifications they need?
--------------------------------------------------------------
Karl Anderson (2600hz Karl) Responded:
--------------------------------------------------------------
If you remove the email then you are correct we would not receive the notifications for those clients. We monitor the system in other ways but these can be useful to determine if there is a localized issue. Using the UI Branding application you could add our email as the BCC but it is not required.
-------------------------------------------------------------- -
-
I agree that this could be very useful for larger companies, but I must imagine that it's fairly difficult for 2600hz to implement :-/
-
Yes, or regular in Kazoo. Just go and add a caller ID prepend with the voicemail box name before any place there is a voicemail item in a call flow.
-
DITTO!!! I've wanted this since day one.
FYI a hack we have found is just adding a name caller ID prepend before the call flow reaches voicemail. -
Wow that is awesome!
I still hate Yealinks though after we could not get them to work at that one customer... :-( -
How did you pull the original screenshot off the phone itself?
-
Agreed!
-
Correct me if I am wrong, but I thought CyberData only made amplifiers themselves, which are obviously a lot more expensive to replace than just adding in an adapter like the SNOM device. Still a good option, it just requires replacing more equipment of course.
-
Darren: Ditto on Panasonic. They don't seem to want to stay registered with any VoIP provider we have tried using them on. The providers that do support them though have provisioning profiles and they seem to work on those. I never took the time to compare the config beyond a basic run through and couldn't find any differences, so who knows.
-
I tried this 10 minutes ago :-/ I'll send in a ticket.
-
That's great, but I believe the bigger issue and the point of this thread is bulk adding the same BLF keys on many phones.
-
Hi Darren,
To chime in on two points:
We have never been able to get DISA to work in the manner we want it with caller ID, which is a customer, from a cell phone, needs to be able to dial out as their office caller ID and not their cell phone. Regardless of whether or not we check the "use account caller ID box" the caller ID that shows up is always that of the first phone that dialed into DISA. No idea why since I feel like we are doing everything correctly...?
The use case our customers have is "Customer has multiple offices and they want the local number to appear for the office they're calling from" - in our situation, the Washington, D.C. area basically has 3 states all within a few miles of each other. Most service companies for example will service all 3 states; however, many customers feel better knowing that the company is located in their own state. We have many customers who want to be able to have their Maryland area code show up when they call Maryland customers, versus the Virginia area code showing up when they call Virginia customers. Automating this would be SO cool, but not 100% necessary. -
That's literally exactly what I am doing Travis, but it doesn't work :-(
-
I can't get this to work :-( Are you able to help Travis?
I dial 32 from my phone and enter the caller ID (one of our clients instead of our office number), I then dial the DISA code and dial my cell phone. My cell phone shows our office calling me, not the client's DID.
Any ideas what we are doing wrong? -
I'd love to know the answer to this as well!
-
Okay, but when I spent probably 3 hours on the phone with Darren one day he basically told me it wasn't a great solution to use an ATA for faxing and that I could expect further problems down the road even if I got configuration that seemed to work for a few test faxes (with any VoIP provider, not just 2600hz)
-
Yes, that is the correct device. I was aware that Vitelity was reselling another solution it's just easier to resell Vitelity than to try and built out integration with that device.
-
Hmm, interesting. I tried using prepend a few months ago and it didn't seem to work on outbound calls. We were trying to have a customer see based on the caller ID on their cell phone that a call was being forwarded from their office, so we tried using a prepend to add like a * or 0 or something prior to the number before forwarding the call to the external number, and the prepend didn't do anything.
So I am guessing what is happening in your example is that the prepend is basically pushing out the default caller ID data? -
Darren himself basically told me don't expect ATAs to work with faxing on 2600hz. So I'm surprised to hear another 2600hz employee saying otherwise.
Account is running out of credit
in Product Discussion
Posted