Karl Stallknecht

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.

Hmm, interesting. Vitelity faxing is the best thing since sliced bread imho. Never been more impressed with a fax solution in my life!

To confirm are you referring to the fax API? (fax2email and email2fax) It usually works well for us too, I just meant it's too much of a pain to have some customers on one faxing platform and other customers on another faxing platform, so we migrated almost everyone who needs outbound faxing to Vitelity. Inbound faxing has always worked fine other than for a period of maybe a month or two when they had some glitches, so if a customer only needs inbound faxing then we just set them up on 2600hz.

You have an Obihai working on 2600hz with faxing!? I'm shocked...we tried Obihai, Cisco SPA, and Grandstream all with probably a 30% success rate. It was horrible. We did everything in the book and went back and forth with 2600hz support for weeks. This was about a year ago. Maybe they have improved?

Your inability to get the ATA to work probably had nothing to do with configuration...it's just FoIP being a crappy technology and 2600hz's platform not playing nicely :-/

FYI I highly recommend against faxing on the 2600hz platform. It was horrible many times when we tried, regardless of whether or not we used T38. Most faxes failed. Not to plug another company, but Vitelity's Fax ATAs (called FaxEnable) are amazing and have almost a 100% success rate. We've deployed about 20 of them so far and our customers love them. It's the best of both worlds because you have a device that you can use for your customer to plug their fax machine into, but they still can use fax to email and also they have a web interface where they can log in and see previously sent and received faxes. So it's like an ATA plus eFaxing combined into one product. The way it works is the device, rather than act as an actual ATA, receives the fax onto it locally. It then sends the fax over https to Vitelity and they send the actual fax from their servers. Incoming faxes work in the same manner, just vice versa (Vitelity receives the fax on their servers, then sends it to the device at the customer's site as some form of https transmission, and then the local device sends the fax to the fax machine). This prevents the entire issue of trying to send a live fax over an Internet line with jitter/packet loss/etc. It's a TDM-based technology which is much more reliable.

I'd love that! I've never used specifically that one before so I'm curious how it holds up compared to the other ones we have used.

What Grandstream model(s)? I only have screenshots for the config for the GXW-4004

If you get this working, please let me know. We have a few customers who would love to be able to do this but we haven't been able to get it to work in the past unfortunately.

Yep, this works.

Hi Anthony, This article explains it perfectly on Polycoms: https://kb.intermedia.net/article/2599 This avoids Kazoo/2600hz altogether. It goes straight phone to phone so it's super fast.