search for: amanu

-uzzi PS: If you're not seeing any connection information, be sure to double-check the IP address is correct. Learned that lesson the hard way =\ On Sun, Jan 31, 2010 at 5:51 PM, Jim Rosenberg <jr at amanue.com> wrote: > Let's say I have two Asterisk boxes, A and B. I am trying to get A to do > SIP registration on B, so an extension for A can dial SIP phones covered by > B. If I examine the logs on B, if the registration succeeds, I am seeing a > notice to that effect on B. But if...

I am trying to get Asterisk 1.6.2.5 working with a Grandstream HT-503 ATA. The FXO part is giving me fits. Every call I try to make to the FXO port outbound I get 403 Forbidden coming back. I've been through every configuration setting I can see, and Uncle Google is not helping me much. I updated the firmware to the current version, and that didn't help. If anyone has this working, I

Let's suppose you have a PSTN line with multiple extensions. One of these extensions is connected to an Asterisk FXO port. For reasons that I won't go into, the "normal" configuration of the system is that when a call comes in on the PSTN line, Asterisk *does not answer* -- the other extensions do whatever they would do if there were no Asterisk system there. When I hear one

What should my allow= line look like in h323.conf for G.729? I've tried allow=G729A but this doesn't seem to be right. These "codec indentifiers" sure are mysterious. Take g711alaw. To allow it you seem to have to use allow=ALAW. Even though "ALAW" does not show anywhere as an identifier when you say show codecs.

It appears Asterisk can handle DTMF inband on only a limited selection of formats, of which G.729 is not one. The issue appears to be something involving "short data" -- whatever that is. (I'm inferring all this from looking at dsp.c in the vicinity of the error message I was getting, which pointed to line 1424.) What *is* "short data"? Is this really a show-stopper for

Let's say I have two Asterisk boxes, A and B. I am trying to get A to do SIP registration on B, so an extension for A can dial SIP phones covered by B. If I examine the logs on B, if the registration succeeds, I am seeing a notice to that effect on B. But if the registration *fails*, i'm not seeing any message logged on B. Maybe I'm just not looking in the right place. Is there a

Has Asterisk ever been audited for common security holes, such as buffer overruns? A quick grep through the source for routines that should never be used, like strcpy, strcat, etc., reveals a lot of it. I fear I fear. Has anyone flung pathology at IAX2 to see if it stands up to malformed packets? (This is always an issue when you have a protocol that only a small number of programs use ...) I

I am using procmail with deliver as recommended on the wiki to send mail snagged by SpamAssassin straight to a spam folder. It seemed to be working fine, but now I'm finding messages like this: Sep 17 12:13:47 hosty deliver(whoey): write() failed with mbox file /var/mail/whoey: File too large I don't think this is a setrlimit problem -- the host operating system is OpenBSD 4.0. My

The following is pasted from SecurityFocus Newsletter #254: ------------------------- Asterisk PBX Multiple Logging Format String Vulnerabilities BugTraq ID: 10569 Remote: Yes Date Published: Jun 18 2004 Relevant URL: http://www.securityfocus.com/bid/10569 Summary: It is reported that Asterisk is susceptible to format string vulnerabilities in its logging functions. An attacker may use these

I am having a recurring problem with Dovecot 1.0.8 failing to MIME-decode certain messages. The client is Mulberry 4.0.8. The messages causing the problem seem to be MIME messages with "no parts". I.e. the message has some MIME encoding, but is just included as the message body. The kind of effect I will see is a proliferation of untranslated =xx codes, or in some cases an untranslated