I am still working out the tool part of everything.
Once we get it autodetecting the cards (if its 100% possible) then
it will automatically add trunks sequentially from lines available
on each span.
If you know C or javascript then send me a message. If not, then
just keep bugging me about it.
PM me if you want specific details.
Glad to see people are still interested :]
Good point, however, we may add a place for manual setup, the problem
is, when you get people using the GUI that may not know asterisk, and
you let them free on a Digital card, when it does not work, they are
going to blame the GUI.
It could escalate pretty quick :[
-bkruse
Tell me what you guys think.
Brian Alexander wrote:
What is the status of support for T1 spans in the GUI? Is there even a
way to manually configure a digital card as a service provider?
I agree with Phillip - it is not important that the GUI be able to
configure the zaptel/zapata configurations... However, it would be
very helpful to be able to use a manually configured span as a service
provider (or any other way it could be used for incoming and outgoing
call routes)
On 5/17/07, *Phillip Neumann* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Maybe it could be a good idea to work on the Calling Routes and
Incomming Calls, for digital cards support, so users that already have
zaptel.conf and zapata.conf can make use of theirs T1/E1.
------------------------------------------------------------------------
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-gui mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-gui
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-gui mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-gui
