Recent content by Mike Loiterman

Also, what do you have in default settings for: http_auth_disable http_auth_password http_auth_type http_auth_username

You have a W52p? And when you go to http://yourdomain/app/provision/{ThePhonesMacAddress}.cfg, it shows both the contents of y000000000025.cfg and {$mac}.cfg?

That looks like the default y000000000025.cfg file...which is what I have. But my phone W52p, won't pick it up, or it's not getting pushed.

I think that's part of the problem. When I go to http://yourdomain/app/provision/{ThePhonesMacAddress}.cfg, it appears that only the contents of {$mac}.cfg are pushed. The contents of the y000000000025.cfg file don't appear to be part of what is pushed.

That's exactly what I have and it doesn't work.

This didn't work for me on my W52P. None of these variables were pushed to the configuration file. These yealink phones are incredibly frustrating to get provisioned correctly.

That’s what I have and it doesn’t work.

Yeah, I can confirm that it fixes my Polycoms, but my yealink is still wrong. Additionally, it shows time in 24 hour format. Any ideas how I can get the DST issue (and hopefully the time format) issue fixed on Yealink?

So is does this fix it or not?

I am. I also have polycom_gmt_offset set which may be part of the issue. Although my yealink phones are also not respecting daylight savings time either. Any ideas would be great.

Here in the US we've just ended DST. But, none of my phones have had the correct time pushed to them. I run NTP on the Debian server on which FreeSWITCH and Fusion are running and that has updated its time correctly, but my phones (polycom and yealink) have not pushed the clock ahead by an...

But how do you set: <variable name="register-gateway" value="user1out"/> from within the GUI? Fusion doesn't have any way to add this, as far as I can tell.

Sounds right to me, but how do you get it to route in the dialplan?

Interesting point. So then how does it get used? What’s the point if it?

This looks great. How can it be implemented without compromising integrity of FusionPBX sand future upgradability?