Exactly what I was looking for. Thanks for the info. Going to go study
now ...
-- Mitch
Tzafrir Cohen wrote:
On Thu, Oct 19, 2006 at 11:08:09PM -0500, Mitch Miller wrote:
* is having permission problems accessing /dev/zap/channel. When I
look, these devices (everything in /dev/zap
* is having permission problems accessing /dev/zap/channel. When I
look, these devices (everything in /dev/zap) shows root.root for uid and
gid. If I start Asterisk from the command line, it runs fine (running
as Root). When I start it as a service, I get
Oct 19 23:02:55 WARNING[10587] chan
Okay, I have Asterisk up and running on Fedora Core 5 with a TDM400
board with one FXO and FXS module. Zap is up and running and * is
functioning with the modules. Oh yeah, and I have some soft phones
configured and have them working as well.
Now I'm ready to begin playing with dial plans an
The "moving to another port" discussion is actually what happens with
sockets. A socket listens on a designated port (ex: port 80) and when a
connection is made to that socket, another socket begins to listen to
port 80 for NEW connections.
Sockets and Ports often gets confused with each othe