Actually, iaxclient does support the netstat events, and shouldn't =20
print anything saying it doesn't -- maybe the OP is using an old =20
As far as supressing these messages generally, there isn't presently =20
a mechanism for doing that as far as I remember (I could be wrong, I =20
haven't looked), but a patch that does that would be nice, as long as =20=
the default behavior was the same (or, at least, it was reasonable, =20
which the present behavior may or may not be; I'd say warnings, etc, =20
should go to stderr by default).
On Jan 10, 2006, at 1:35 AM, Cristian Draghici wrote:
> The message comes from the IAX parser when it does recognize an
> Information Element (actually 3 of them in your case).
> cristi:~/Programming/projects/iaxclient_CURRENT diciu$ grep -r
> "Ignoring unknown " .
> ./lib/libiax2/src/iax2-parser.c: snprintf(tmp,
> (int)sizeof(tmp), "Ignoring unknown information element '%s' (%d) of
> length %d\n", iax_ie2str(ie), ie, len);
> You could print out the line following the snprintf to get rid of =20
> the message.
> Alternatively, you could handle these information elements in the =20
> iax2 parser.
> =46rom asterisk cvs (the channels directory):
> cristi:~/Programming/external/asterisk-1.2.0/channels diciu$ grep
> "4" iax2.h
> #define IAX_IE_CODEC_PREFS 45 /* Codec Negotiation */
> #define IAX_IE_RR_JITTER 46 /*
> Received jitter (as in RFC1889) u32 */
> #define IAX_IE_RR_LOSS 47 /*
> Received loss (high byte loss pct, low 24 bits loss count, as in
> rfc1889 */
> Anyone can step in to correct me but I think this is an explanation as
> to why the network stats event (IAXC_EVENT_NETSTAT) only carries data
> for peers running iaxclient and shows zeros everywhere for the remote
> asterisk end.
> Anyway, hope this helps,
> On 1/10/06, Da Beave <beave@...> wrote:
>> I'm pretty new with IAXClient, but so far it's been fun =20
>> to work
>> with. Here's my question; How can I suppress the console =20
>> message. For
>> example, the software I'm writing has a ncurses front-end. I've =20=
>> IAXClient to work (dialing, etc), but the "status" messages from =20
>> really messes up my ncurses display! For example:
>> IAXCLIENT: Call 0 ringing
>> Ignoring unknown information element 'Unknown IE' (46) of length 4
>> Ignoring unknown information element 'Unknown IE' (47) of length 4
>> Ignoring unknown information element 'Unknown IE' (48) of length 4
>> Is there any way to turn this off? The software that I'm
>> writing is in good ole C (gcc - Linux in particular, but also =20
>> with FreeBSD).
>> Thanks in advance, and I hope this question makes sense.
>> Da Beave (beave@...)
>> Telephreak Voicemail Box 7337 | FWD: 61106
>> http://deathrow.vistech.net | The Deathrow OpenVMS Cluster
>> http://www.telephreak.org | Telephreak Asterisk/VoIP =20
>> Key Id: 357B86AD
>> Key fingerprint =3D 1470 658D 16BB A129 462E 84BF 6C53 8FDD 357B =
>> If it wasn't for C, we'd be using BASI, PASAL and OBOL.
> This SF.net email is sponsored by: Splunk Inc. Do you grep through =20
> log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD =20
> Iaxclient-devel mailing list