<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thomas Kenyon wrote:
<blockquote cite="mid:47AD91E2.3050100@sanguinarius.co.uk" type="cite">
<pre wrap="">Rob Peck wrote:
</pre>
<pre wrap=""><!---->Grandstream sadly have the habit of releasing broken firmwares, and
there are notoroiusly some phones with faulty hardware (which get replaced).
</pre>
</blockquote>
<br>
We've given up on Grandstream due to multiple f/w issues and patchy
response from their tech support.<br>
<br>
<blockquote cite="mid:47AD91E2.3050100@sanguinarius.co.uk" type="cite">
<pre wrap="">And admittedly provisioning can be a pain needing to encode the
configuration plan, and being capable of handling multiple config files.
(even with the old atcoms you could have a global config file with
default settings and a separate per-unit one).
I've not tried it, but the unencrypted GXP2000 config files look like a
small header and some URL-style form data at the end. You may be able to
make global changes as simply as:
sed -e -i 's/P625=0/P625=1' cfg*
Would presumably reconfigure all the phones to auto-answer on line 4.
(finding the keys is as simple as looking at the souce on one of the web
pages).
</pre>
</blockquote>
<br>
We provision our GXP-2000's with some bash scripts. The originals were
simple and took a "global" template and concatenated it with a
device-specific config before feeding the result to the GS encoder. We
just maintain templates for the configs in text format, a "map" file
with the extension number, user name and MAC address and the scripts do
the rest. All of the Grandstream configuration pain is gone! (except
for the f/w bugs! :-)<br>
<br>
regards,<br>
<br>
Drew<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Drew Gibson
Systems Administrator
OANDA Corporation
<a class="moz-txt-link-abbreviated" href="http://www.oanda.com">www.oanda.com</a>
</pre>
</body>
</html>