I'm attempting to get two Asterisk 0.4.0 PBXes to communicate with one
another using IAX/IAX2 trunks.
I've managed to get a semi-functional NAT Firewall working as a PBX
(with Asterisk running directly on the firewall itself), but there are
issues with bind()ing to various interfaces which is
I would use the latest CVS for one. And try again.
bkw
On Wed, 20 Aug 2003, Ian Blenke wrote:
I'm attempting to get two Asterisk 0.4.0 PBXes to communicate with one
another using IAX/IAX2 trunks.
I've managed to get a semi-functional NAT Firewall working as a PBX
(with Asterisk running
Brian West wrote:
I would use the latest CVS for one. And try again.
Unfortunately, I've tried numerous times to get a current CVS trunk
snapshot to talk to *anything*, to no avail. Even getting my Grandstream
phones to register with it was an apparent excersize in futility.
Dropping back to
On Wed, 2003-08-20 at 11:09, Ian Blenke wrote:
Brian West wrote:
I would use the latest CVS for one. And try again.
Unfortunately, I've tried numerous times to get a current CVS trunk
snapshot to talk to *anything*, to no avail. Even getting my Grandstream
phones to register with it was
I would also like to see a more structured release
program. It's kind
of scary to tell people that they should just use
the latest CVS code.
That's where consultants earn their money. They
should be preforming some kind of quality control.
You build the code, get it to work, test it and
Chris Albertson wrote:
I would also like to see a more structured release
program. It's kind
of scary to tell people that they should just use
the latest CVS code.
For testing and development, this isn't a bad thing - as long as the
trunk codebase generally *compiles* and *runs* more often than
Ian Blenke wrote:
Brian West wrote:
I would use the latest CVS for one. And try again.
Unfortunately, I've tried numerous times to get a current CVS trunk
snapshot to talk to *anything*, to no avail. Even getting my Grandstream
phones to register with it was an apparent excersize in
