Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To: <1264195414.3493.364.ca...@scott>
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <40715>
Message-ID: <[email protected]>



Excellent thread Scott, I hope your ready for the feedback!

On a general note, I think the solution is fairly simple and
straightforward to setup, certainly as an IP Telephony
platform its much simpler than a lot of the other solutions
out there...

I don't have a production solution yet, so may not have a
true reflection of the complete solution.  However, testing
so far has brought up the following things that I think
could be simplified, or have the documentation improved with
sample configurations etc...

Diagnosis - Im not a Linux admin, and try and keep all
changes in the Web UI as much as possible.  It would be good
to get SIP Viewer (or a basic version) accessible via the
Web UI. Secondly, some tool or utility to allow you to enter
a dial string and see how the dial plan would handle it. 
You can do this on Cisco gateways, and always proves to be a
useful tool, especially if you have a large diaplan with
prefixing, digit stripping or transform masks etc...

Upgrades - I know upgrades are much easier now, but they can
still be made simpler I believe, especially for systems that
do not have Internet connectivity.  If you could download a
single file called something like 404to42upgrade, it would
make it easier, rather than having to copy a whole bunch of
files.

Voicemail - I think this functionality needs further
development to make user administration simpler e.g. message
size quotas, an interface view of used/free storage space.

Soft-phone - I know we have the SIPXtapi development kit,
but I think it would be really good for the project to have
a simple soft-phone for all the popular OS platforms that
allows users to test/deploy all SipX features. I have tested
lots of softphones over the past few months, and cannot find
a good open-source product that is good enough to deploy to
users. The FreeSwitch project are working on FSComm, it will
be interesting to see how that develops.

Finally, I think people could get further sooner if there
were sample configurations that could be used as a starting
point. Recently, Steffan provided an excellent sample config
for a Cisco ISDN gateway IOS config.  I know it really
helped me and a few others to get something setup much
quicker than having to start from scratch.  The suggestion
of a tested phone/gateway section sounds brilliant!

Hope these points help!
Abdul

_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to