Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community
 SearchSearch 

[asterisk-users] How to turn on the H323 logging on Asterisk


 
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> Asterisk Users
View previous topic :: View next topic  
Author Message
tzafrir.cohen at xorco...
Guest





PostPosted: Wed Jun 11, 2008 3:20 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

On Wed, Jun 11, 2008 at 10:40:41AM +0300, Sema Arca wrote:
Quote:
Hi,

Does anybody know how I can turn on the logging for H323 in Asterisk? I have
set the logging path and the file name in the ooh323.conf file however it
did not help. The file is created but is empty. I want to, if possible, turn
on the logging in DEBUG level.

The file name is ooh323c.conf (note the extra 'c').

It is used by chan_ooh323c, rather than chan_h323. chan_ooh323c is
unmaintained and not recommended for new installations.

--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Back to top
tony at softins.clara....
Guest





PostPosted: Wed Jun 11, 2008 5:25 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

In article <20080611082011.GB23243 at xorcom.com>,
Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:
Quote:
On Wed, Jun 11, 2008 at 10:40:41AM +0300, Sema Arca wrote:
Quote:
Hi,

Does anybody know how I can turn on the logging for H323 in Asterisk? I have
set the logging path and the file name in the ooh323.conf file however it
did not help. The file is created but is empty. I want to, if possible, turn
on the logging in DEBUG level.

ooh323 does not have debug-to-file. You enable debugging with "ooh323 debug",
and then the debug information is sent to the "verbose" channel, which
normally goes to the console and may go to one of the general log files,
according to the settings in logger.conf. ooh323 debugging is stopped by
giving "ooh323 no debug".

Quote:
The file name is ooh323c.conf (note the extra 'c').

No, ooh323.conf is correct. The 'c' is used in the name of the stack,
but not in the name of the Asterisk channel or the conf file.

Quote:
It is used by chan_ooh323c, rather than chan_h323. chan_ooh323c is
unmaintained and not recommended for new installations.

This was because until recently, the most up-to-date chan_ooh323 driver
and stack were the ones in the 1.2 branch of asterisk-addons.

However, I recently ported the 1.2 version forward to 1.4, trunk and
1.6.0, and added a couple of bug fixes. Those changes were accepted into
SVN, so that all those variants are now up to date. It should therefore
now be easy to keep them maintained as far as Asterisk API changes are
concerned.

Having tried chan_h323, chan_oh323 and chan_ooh323, I *would* strongly
recommend chan_ooh323 over the first two. It is clean and lightweight,
uses the Asterisk RTP stack (and can therefore bridge properly), and
doesn't creak under the bloat of OpenH323 like the first two do.

I don't know whether Objective Systems have abandoned chan_ooh323 and
the ooh323c stack, but it would be great to see them moved from -addons
into the main Asterisk tree.

Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org
Back to top
bilmar_gh at yahoo.com
Guest





PostPosted: Thu Jun 12, 2008 3:44 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

I am still looking to know if all of these h323's are
able to work as gatekeeper, so endpoint can register?

About "chan_ooh323 and using It is clean the Asterisk
RTP stack (and can therefore bridge properly), and
doesn't creak under the bloat of OpenH323 like the
first two do":

The other two: how they use the RTP stack if they do
not use Asterisk RTP?

And what do u mean by bridge properly? (How?)

Your kindly help is high appreciated.
Regards
Bilal
-------------------
In article <20080611082011.GB23243 at xorcom.com>,
Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:
Quote:
On Wed, Jun 11, 2008 at 10:40:41AM +0300, Sema Arca
wrote:
Quote:
Quote:
Hi,

Does anybody know how I can turn on the logging
for H323 in
Asterisk? I have
Quote:
Quote:
set the logging path and the file name in the
ooh323.conf
file
however it
Quote:
Quote:
did not help. The file is created but is empty. I
want to, if
possible, turn
Quote:
Quote:
on the logging in DEBUG level.

ooh323 does not have debug-to-file. You enable
debugging with "ooh323
debug",
and then the debug information is sent to the
"verbose" channel, which
normally goes to the console and may go to one of the
general log
files,
according to the settings in logger.conf. ooh323
debugging is stopped
by
giving "ooh323 no debug".

Quote:
The file name is ooh323c.conf (note the extra 'c').

No, ooh323.conf is correct. The 'c' is used in the
name of the stack,
but not in the name of the Asterisk channel or the
conf file.

Quote:
It is used by chan_ooh323c, rather than chan_h323.
chan_ooh323c is
Quote:
unmaintained and not recommended for new
installations.

This was because until recently, the most up-to-date
chan_ooh323 driver
and stack were the ones in the 1.2 branch of
asterisk-addons.

However, I recently ported the 1.2 version forward to
1.4, trunk and
1.6.0, and added a couple of bug fixes. Those changes
were accepted
into
SVN, so that all those variants are now up to date. It
should therefore
now be easy to keep them maintained as far as Asterisk
API changes are
concerned.

Having tried chan_h323, chan_oh323 and chan_ooh323, I
*would* strongly
recommend chan_ooh323 over the first two. It is clean
and lightweight,
uses the Asterisk RTP stack (and can therefore bridge
properly), and
doesn't creak under the bloat of OpenH323 like the
first two do.

I don't know whether Objective Systems have abandoned
chan_ooh323 and
the ooh323c stack, but it would be great to see them
moved from -addons
into the main Asterisk tree.

Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org -
http://tony.mountifield.org
Back to top
tony at softins.clara....
Guest





PostPosted: Thu Jun 12, 2008 4:18 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

In article <531036.69111.qm at web53902.mail.re2.yahoo.com>,
bilal ghayyad <bilmar_gh at yahoo.com> wrote:
Quote:
I am still looking to know if all of these h323's are
able to work as gatekeeper, so endpoint can register?

I think they all run only as a gateway, not a gatekeeper, but I'm not
100% certain.

Quote:
About "chan_ooh323 and using It is clean the Asterisk
RTP stack (and can therefore bridge properly), and
doesn't creak under the bloat of OpenH323 like the
first two do":

The other two: how they use the RTP stack if they do
not use Asterisk RTP?

Looking at http://www.voip-info.org/wiki/index.php?page=Asterisk+H323+channels
it appears I was only partially correct. I never got chan_h323 working,
so have less experience of that. According to the above wiki page,
chan_h323 does use the Asterisk RTP stack, although it still uses the
OpenH323 library for the protocol part.

I used chan_oh323 for a long time 2 or 3 years ago, and it definitely
didn't use Asterisk's RTP stack, nor its codecs. It used the ones that
are part of OpenH323, and communicated with the chan_oh323 driver using
pipes (I guess in slin format). It was very profligate in its use of
system resources (file descriptors, CPU, etc), such that even on a dual
Xeon system we got degradation above about 15 simultaneous calls.

With both those versions, you easily run into version number hell with
OpenH323 and PWlib, which is another reason, IMHO, to avoid them.

I tried chan_ooh323 much more recently, and it just felt cleaner, more
streamlined and better integrated with Asterisk. However, I have not yet
used it in production. When I need to, this is the H.323 driver that I
will use, and if necessary bug fix and/or enhance.

Quote:
And what do u mean by bridge properly? (How?)

I guess since chan_h323 does indeed use Asterisk RTP, that it can bridge
channels at the RTP packet level just like chan_ooh323 and chan_sip can.
But chan_oh323 always had to pass audio through the Asterisk core because
it didn't use Asterisk RTP.

Quote:
Your kindly help is high appreciated.
Regards
Bilal

Cheers
Tony

Quote:
-------------------
In article <20080611082011.GB23243 at xorcom.com>,
Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:
Quote:
On Wed, Jun 11, 2008 at 10:40:41AM +0300, Sema Arca
wrote:
Quote:
Quote:
Hi,

Does anybody know how I can turn on the logging
for H323 in
Asterisk? I have
Quote:
Quote:
set the logging path and the file name in the
ooh323.conf
file
however it
Quote:
Quote:
did not help. The file is created but is empty. I
want to, if
possible, turn
Quote:
Quote:
on the logging in DEBUG level.

ooh323 does not have debug-to-file. You enable
debugging with "ooh323
debug",
and then the debug information is sent to the
"verbose" channel, which
normally goes to the console and may go to one of the
general log
files,
according to the settings in logger.conf. ooh323
debugging is stopped
by
giving "ooh323 no debug".

Quote:
The file name is ooh323c.conf (note the extra 'c').

No, ooh323.conf is correct. The 'c' is used in the
name of the stack,
but not in the name of the Asterisk channel or the
conf file.

Quote:
It is used by chan_ooh323c, rather than chan_h323.
chan_ooh323c is
Quote:
unmaintained and not recommended for new
installations.

This was because until recently, the most up-to-date
chan_ooh323 driver
and stack were the ones in the 1.2 branch of
asterisk-addons.

However, I recently ported the 1.2 version forward to
1.4, trunk and
1.6.0, and added a couple of bug fixes. Those changes
were accepted
into
SVN, so that all those variants are now up to date. It
should therefore
now be easy to keep them maintained as far as Asterisk
API changes are
concerned.

Having tried chan_h323, chan_oh323 and chan_ooh323, I
*would* strongly
recommend chan_ooh323 over the first two. It is clean
and lightweight,
uses the Asterisk RTP stack (and can therefore bridge
properly), and
doesn't creak under the bloat of OpenH323 like the
first two do.

I don't know whether Objective Systems have abandoned
chan_ooh323 and
the ooh323c stack, but it would be great to see them
moved from -addons
into the main Asterisk tree.

Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org -
http://tony.mountifield.org







_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org
Back to top
tony at softins.clara....
Guest





PostPosted: Thu Jun 12, 2008 10:52 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

Hi Sema,

In article <20bf8c660806120116j75d94498m952925c5759fb3a3 at mail.gmail.com>,
Sema Arca <semaarca at gmail.com> wrote:
Quote:
Thanks a lot for the tips. I have turned on the logging and saw them in the
console. However, this applies only for startup, when I try to register a
user, which I cannot succeed, there is no logging done.

Check your logger.conf file and make sure that verbose is going either to
messages, or full or both. Then you will be able to extract relevant debug
output for any future posting.

Quote:
Do you think you can give me an idea why my user cannot register? All I want
to do is, send the register to a GK which has the IWF functionality.

I haven't enough information to answer that, and I am not very familiar
with gatekeepers anyway.

Quote:
Attached I am sending my extensions.conf and ooh323.conf files.

A few things I noticed:

In your extensions.conf, you have this:

[h323]
exten => _1NXXNXXXXXX,1,Dial,H323/${EXTEN}

When using chan_ooh323, you need to use OOH323 instead of H323, and you
also need to name the peer you want to dial out through:

exten => _1NXXNXXXXXX,1,Dial(OOH323/${EXTEN}@mypeer1)

Or possibly "Sema" instead of "mypeer1", depending on what you need.

In your ooh323.conf, you should disallow all codecs first, and then just
allow the ones you want. For initial testing, just stick with ulaw or alaw:

disallow=all
allow=ulaw
allow=alaw

Then remove the "allow=all" from your peer, user and friend sections.

There may well be other issues, but fix these first. Then if you still
get problems, include the verbose output from the log file.

Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org
Back to top
r.scobie at clear.net.nz
Guest





PostPosted: Sat Jun 14, 2008 3:49 pm    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

Tony Mountifield wrote:

Quote:
I don't know whether Objective Systems have abandoned chan_ooh323 and
the ooh323c stack, but it would be great to see them moved from -addons
into the main Asterisk tree.

This was always the plan from the beginning.

I have a post from one of the Objective Systems developers:

"We are working closely with digium towards making it an official
channel driver once the testing phase is complete."

I'm not sure what happened subsequently - perhaps licencing issues, but
I agree, it is an easy to build implementation that I have had in light
production use for 3 years.

Regards,

Richard
Back to top
r.scobie at clear.net.nz
Guest





PostPosted: Mon Jun 16, 2008 2:32 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

Sema Arca wrote:
Quote:
Hi Richard,

I could not succeed to make my ooh323 work somehow. I can see the peers
and the users but although my exten definition states that the call
should be forwarded to a GK, Asterisk does not send it out. I also have
the same problem with registration.

Do you think you can give me some ideas? Maybe send your conf as a
reference?

I am sorry I have no experience using ooh323 with a gatekeeper.

My setup is as an endpoint between asterisk and a Panasonic TDM100 PBX.

Regards,

Richard
Back to top
r.scobie at clear.net.nz
Guest





PostPosted: Mon Jun 16, 2008 3:53 am    Post subject: [asterisk-users] How to turn on the H323 logging on Asterisk Reply with quote

Sema Arca wrote:
Quote:
Can you still send the config files? Maybe I can come up with an idea? Sad

extensions.conf entry

exten => _1XX,1,Dial(OOH323/${EXTEN}@192.168.0.2)
exten => _1XX,2,Congestion

ooh323.conf

[general]
h323id=ObjSysAsterisk
e164=100
callerid=asterisk

context=default
tos=lowdelay

disallow=all
allow=alaw

dtmfmode=inband

[Panasonic]
type=friend
context=default
ip=192.168.0.2
port=1720
disallow=all
allow=alaw
Regards,

Richard
Back to top
Display posts from previous:   
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> Asterisk Users All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

VoiceMeUp - Corporate & Wholesale VoIP Services