Hi Tony, 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.
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. Attached I am sending my extensions.conf and ooh323.conf files. Sema is the end user and I believe mypeer is the GK definition, right? [mypeer1] type=peer ;context=context2 ip=10.192.192.6 ; UPDATE with appropriate ip address port=1720 ; UPDATE with appropriate port allow=all ;e164=101 [Sema] type=friend context=default ip=10.192.192.36 ; UPDATE with appropriate ip address port=1820 ; UPDATE with appropriate port ;disallow=all allow=all e164=05336887755 rtptimeout=60 dtmfmode=rfc2833 I would really appreciate if you can take a look. Kr, Sema On Wed, Jun 11, 2008 at 1:25 PM, Tony Mountifield <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, > Tzafrir Cohen <[EMAIL PROTECTED]> wrote: > > On Wed, Jun 11, 2008 at 10:40:41AM +0300, Sema Arca wrote: > > > 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". > > > 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. > > > 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: [EMAIL PROTECTED] - http://www.softins.co.uk > Play: [EMAIL PROTECTED] - 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 >
ooh323.conf
Description: Binary data
extensions.conf
Description: Binary data
_______________________________________________ -- 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
