This morning I updated to latest weak password detection module (v2.5.0.2) and (quite appropriately) my server has begun complaining about my extensions having weak secret passwords. I am behind a hardware firewall, but I am aware that I need to improve my passwords. Problem becomes that when I change my secret extension password to something unique, then I am not allowed to get my voicemail messages. What am I doing wrong?
Once you change your password, your phones need to update their config files with that new password. Reboot your phone (if its configured in the endpoint manager), and it should pull configs from the server and everything will be fine :)
Randall Degges
Lead Developer, RCI Telecommunications
projectb14ck - http://projectb14ck.org/ - Weblog
Due to the economy, I am only working three days a week, so I am just getting back to this.
Apparently my extensions (phones) are not storing their configuration onto the server. I tried what you suggested and now my extension (only one right now) cannot get it's voicemails. Server response is "password", I enter my password and server response is "login incorrect."
Not sure where to start, here, any suggestions??
Flash the phones, let them pull configs from the server fresh.
Randall Degges
Lead Developer, RCI Telecommunications
projectb14ck - http://projectb14ck.org/ - Weblog
Yes, that is what I did.
My trixbox experience began with version 2.2. That initial configuration has remained with each upgrade. (Currently running 2.6.2.2) Could it be that I did something wrong back then and it has "stuck" and now I am seeing this problem?
I need to find documentation that will instruct me as to current method of configuring Grandstream extensions under trixbox 2.6.2.2, any ideas where I might find that?
The sureteq guide to setting up trixbox is a great tool: http://sureteq.com/asterisk/trixboxv2.6.2.htm
In a nutshell:
setup-grandstream
then from the web interface, create an extension for your phone, then create an endpoint manager entry for your phone. Then reboot the phone and let it update. Usually straight-forward :)
Randall Degges
Lead Developer, RCI Telecommunications
projectb14ck - http://projectb14ck.org/ - Weblog
First, b14ck, I want to thank you for your help with this.
It has been a while and as I read I am remembering most of this.
I ssh into my server and ran "setup-grandstream". All seemed to go as it should have.
When I go into PBX-->setup-->extensions and my ip address range is correctly filled and I click "GO". My server finds two extensions of my eight extensions. (BTW, three GXP-2000 and five BT-200) When I click "Grandstream-Devices" I see all my extensions including the two the "GO" button found.
So, because it is an operational system, I am attempting to adjust the setup of one of the lesser used extensions (a BT-200) and if that works okay, then the rest of the extensions on the system. Well, "GO" does not find my extension (I am experimenting with.)
I tried deleting this "experiment" extension. I have set the extension to acquire it's IP address via DHCP and made sure my DCHP server saw and issued the correct address for the telephone. Still, server will not find the extension via "GO" button.
Any ideas what to try, now?
Maybe this thread needs to be moved to the endpoint manager forum? Administrator?
I have been reading over in the endpoint manager (EM) forum that this may be an EM issue.
It discussed nmap being run by the EM and when I run nmap manually, nmap only sees those two "found" extensions.
So, I might be wrong but it sounds like an EM issue against GXP-2000 and BT200 extensions not being "seen".
Yes, this started as a "secret password" on the extension issue and I am still looking into that. I think that will solve itself in the manner b14ck suggested.
PLEASE CLOSE THIS ISSUE.
Copyright © 2011 Fonality
Fonality and trixbox are trademarks of Fonality. Trademark Policy. Privacy Policy.
Asterisk is a trademark of Digium, Inc. Fonality and trixbox are not affiliated with, nor endorsed by Digium, Inc.
Member Since:
2007-08-20