automated reboot

You are right, unfortunately Grandstream is unresponsive and can't help us. In addition, its hard to debug the phones which regularly go "bad" on a live system since the users have been told to just unplug/replug the power of the phone right away.

So far Grandstream support asked me to capture audio packets but they don't want to tell us how to do that... which of course hasn't got anything to do with the phones locking up at random.

For now, i'll just reboot the phones (since this isn't a trixbox/asterisk issue) once a week so it should be ok as a temporary solution.

PS:
Grandstream support hasn't been very forthcoming with information, so far we've had to beg for the default configurations of the various GXP phones (1200, 2010, etc) and received just a single default setup for an older version of the firmware.

oh well...

First of all, we don't have a sample configuration for the new firmware, simply because grandstream support hasn't given it to us, nor is it available in their website.

The "gxp_config_1.1.5.15.txt" which is a sample configuration for the previous firmware doesn't mention WDT anywhere (btw we got that file from google, i'm not sure whats the issue here, but i don't see why the sample config should be such a well kept secret).

At least, the latest 1.1.6.16 firmware corrected a lot of problems and the current bug list is rather short:

1) GXP-2010: the "menu" button and arrows stop working. Pressing them does absolutely nothing, otherwise the phone works fine. This usually results in calls from the secretary saying that she can't access the menu to see the phonebook or missed calls, etc.

2) GXP-1200: the phone suddenly looks as if it has no power (LCD is blank and not lit, etc) but when someone forwards a call the message indicator light is blinking. Also, we can access the phone via HTTP. Unfortunately no calls can be made or answered at this state.

3) GXP-1200: the person on the phone can be heard but he can't hear the other side. This happens often and you can spot it when one of our people shouts "hello? hello?" on the phone and hangs up. We witnessed this while we called the office from a mobile phone and we could hear the shouts on the mobile but the office phone couldn't hear us.

4) GXP-1200: garbage on screen. This is seen when the phone changes "state", like when we hang up, then the screen looks half-drawn (some part is from the previous "state" and some part is from the new "state"). Also, when rebooting the phone the "Rebooting" message is sometimes broken up.

5) GXP-1200 & 2010: Sometimes the handset is too loud and the microphone picks up the voice and generates unnecessary echo. It doesn't happen all the time, so far we haven't managed to figure out when it happens but when it does we can see the secretary holding the phone with her hand outstretched. The echo is only from the person holding the GXP phone, not the incoming voice of the other person.

6) GXP: We have the latest firmware but we don't have the latest gxp_config_xxx.txt file for it.

7) GXP: The documentation for the XML idle screen doesn't include the default XML, so we can have something to start with. Instead we have to spend hours and hours recreating it from trial and error.

8) GXP: The user documentation doesn't explain some things, like for example the "MUTE" button acts as DELETE when editing something in the on-screen menu.

9) GXP (feature request): The "TRANSFER" button should do an attended transfer by default, the same way it works on all major PBX systems (siemens, samsung etc). The current method is too complicated (put caller on hold, hit a LINEx button, dial an extension, talk, hit transfer LINEx to LINEy).

Sorry for the long post, i hope the above issues are of some help to others. If you know the solution or workaround for one of them, please post it.