similar to: zaptel make problem

I am attempting to use an IAX2 channel between two Asterisk systems. This would seem to be a normal thing to do. I actually want to trunk traffic between the two that are in remote locations. However, I have started with what I think is a simple configuration, which should allow for one way calling. Attached are the pertinent parts of my configuration files. I am attempting to place a call on

Thanks to all that have helped me so far. I have made a lot of progress. I am able to make prilib and zaptel. Now to Asterisk... After installing the kernel source, I have: # cd /usr/src/linux # make cloneconfig # make prepare-all Then I have run ./configure in the asterisk-1.4.4 directory. I have: # make clean # make Which goes through a number of compiles and then ends

In looking at the safe_asterisk script, it would appear that it is encouraging the running of the Asterisk application as root user. My natural inclination is to run it as a non-privileged user. What is recommendation? +++++++++++++ This e-mail was checked by the TecInfo Content Scanning Service for potentially harmful content, such as viruses or Spam For more information, call 800.863.5415

I am new at this. I have read "Asterisk: The Future of Telephony" and have installed AsteriskNOW (beta 4, due to the dual processor problem in beta 5). The GUI interface does not seem to provide the capability that I need, although I have modified the *.conf files to successfully create what I need. Given this, I would like to install Asterisk on a distro. I am most familiar with

From: Malcom Kemp Sent: Wednesday, April 25, 2007 11:19 AM To: 'asterisk-users@lists.digium.com' Subject: AsteriskNOW generation of zapata.conf file I am a new user of Asterisk, and an trying to use AsteriskNOW. The test system is dual processor, so I am using the beta 4 version. I am currently trying to manually configure, as the GUI does not seem to let me accomplish what I need.

Hi, Just tested the latest snapshot on RHL72 via building RPM's of it. Nroff detection was wrong, and if no --with-mantype was specified, the type would always revert to cat. This one-byter fixes it. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert

Hi, On systems that have mandoc installed but are missing an nroff binary, the configure script will fall back to pre-formatted manual pages despite the fact that mandoc could be used. The proposed patch adds mandoc as a valid formatter to configure.ac. As mandoc supports the -mdoc flag, it can simply be added to the list of nroff-like binaries. Wolfgang -------------- next part --------------

Hi, I am sorry about this stupid question but after compilation of openssh-2.3.0p1 the manpages were installed but a man ssh gives only unstructured response without underlined lines etc. A nroff -man sshd.8 gives the same output but the contents of the file shows a nroff-format. Any ideas? My system is a HP-UX 11.000 with the pam-patch. regards Stephan -- LDS Brandenburg Dr. Stephan Hendl

What is the difference between the 1.2.x and the 1.4.x branches? I am starting to deploy asterisk from scratch. I expect that I should use the 1.4.x branch, but don't know the rationale for the two. +++++++++++++ This e-mail was checked by the TecInfo Content Scanning Service for potentially harmful content, such as viruses or Spam For more information, call 800.863.5415 or visit

Hello, the man pages for openssh-2.3.0p1 look bad on our Tru64 Unix V4.0E systems. (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine. It is intended to replace rlogin and rsh, and provide secure encrypted communica- tions between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be

I am using R 1.2.3 on Linux Mandrake 7.2. I have a ton of S Nroff help files that end with source code typified by the following: Last S statement in an example, e.g. X <- y ..KW models ..KW regression ..WR When using R RMD Sd2Rd to create the .Rd file I get X <- y \keyword{models} \keyword{regression} } The } matches a { in \examples{ at the beginning of the example code (started in

Thanks to Brian Ripley I have been using R utilities for some time for converting S-Plus UNIX nroff help files to .Rd to .html files. .Rd files seem to be the most natural format for help files and this format is probably easier to maintain than nroff, so I would like to start using .Rd files as my master documentation format if anyone has a utility for going from .Rd to nroff. I guess I could

These are all in the port of 1.2.3pre2: - configure accepts --includedir, but doesn't seem to pass it on to the Makefile. You have to edit the Makefile manually if you have include files anywhere but /usr/include. Which is a problem because... - The Makefile doesn't include /usr/local/include by default, which is where zlib installs itself by default. Probably oughta be in there.

I have help files in several formats. Up until now I have converted nroff files to S-Plus 6 sgml and html files using Splus doc_to_S ... (creates .sgml file) Splus HINSTALL ... (creates .sgm and .html files) I maintain master help files in R .Rd files, and for some of my functions converting from .Rd to .sgm using R CMD Rdconv --type=Ssgm ... produces better .sgm files than beginning with

Right out of the box (after I made Damien's LDFLAGS fix in configure) using gcc-2.95.2. The only problem I have now is the man pages. I still can't read them using Solaris nroff, and when I tried to build with --with-catman=cat, I got the following during a make install: /rtr/bin/install -c -m 644 ssh.[01].out /usr/local/man/cat1/ssh.1 Try `/rtr/bin/install --help' for more

Pascal Volk writes: >> Cut&pasted off the terminal man page output. Looking into >> man1/doveadm-move.1, I see >> >> .B doveadm move \-u jane Archive/2011/09 mailbox INBOX BEFORE \(rs >> .B 2011-10-01 SINCE 01-Sep-2011 >> >> so it's a problem with my nroff, not dovecot's man pages. (Hmm, it >> happens with groff too -- it appears

Robert Gentleman <rgentlem at stat.auckland.ac.nz> writes: > Help Files > ========== > Has anyone had any experience with latex2rtf and then on to windows help? > We can hope that people have netscape and then simply use the html version > but it would be nice if there were some easy way to produce real windows > help. Please keep the nroff versions and the old help()

Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using

I've noticed that the man pages provided in the tarball do not work on Solaris - the output is not formatted as expected. On a linux box it is possible to view the man pages using nroff -mdoc ./sshd.8, where prepended file is /usr/lib/groff/tmac/tmac.doc. There does not appear to be an equivelent macro file on Solaris 2.6. Does anybody know how I can get the man pages to display properly on

Hi Team, I'm looking to "upgrade" my sites ssh installation from the original. I have built openssh-2.3.0p1 and it looks good. I am puzzled as to why there are so many source distributions? However, that is not why am writing - the man pages provided do not format with either Solaris 'nroff -man' or 'groff -man'. What am I missing here? Thanks for your help. Scott