I never said you did. Chargeback wasn't a threat. If your product is not listed as beta, and your sales info says it will work with the phone we have we expect it to work. If not we expect a refund, or we'll protest the charges. FreePBX is a top notch product, we're happy to pay for commercial modules if we know they are supported and they work. If not...well, that is all I was trying to say.
Good to know. Since most of our customers actually use their phones for business purposes, and they might require support outside of the M-F 9-5 at some point, that statement will make a big difference in the solutions for phone systems we promote to our customers.
I agreed with you on that point already. This still does not change the fact that it does not work with brand new fresh out of the box Grandstream GXP model phones. If you have been using them for 7 years, and the EMP is working for with brand new phones I would love to hear how you got them working - kind of the point of this post. And, not exactly sure why you are calling the Grandstream XML configs new since when I first configured some of their phones back in 2009 it was with XML.
Of course.
Thanks for your help. But all you are doing is arguing with me as if you are trying to convince me I don't have a problem. The config files produced don't work. There appears to be no option on the phones to force them to use the type of configuration files the module produces. This is a problem. I was hoping to find someone who had encountered the same problem and found a solution, not someone trying to tell me...whatever it is you are trying to tell me.
Again, thanks. If anyone actually has a solution it would be awesome if you shared it. Otherwise, I guess we'll have to manually create the configs ourselves. Probably will take less time using sed and bash script than I have already spent trying to get this module to work.