[asterisk-bugs] [Asterisk 0012743]: [patch] OOH323 channel names shouldn't use CIDname

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12743 
====================================================================== 
Reported By:                softins
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   12743
Category:                   Addons/chan_ooh323
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 604 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             05-28-2008 12:26 CDT
Last Modified:              05-28-2008 17:23 CDT
====================================================================== 
Summary:                    [patch] OOH323 channel names shouldn't use CIDname
Description: 
For incoming calls, OOH323 channels are currently named using the CIDName
of the incoming call (if set), which could be anything completely unrelated
to the host from which the call came, and even contain strange chars, e.g.

-- Executing Answer("OOH323/Tony Mountifield-3f83", "1") in new stack

For outgoing calls, the channel uses the name of the peer or friend to
which the call is routed. I would have thought for incoming calls, it
should use the name of the user or friend section that was matched.

For more details, see my post on -dev at
http://lists.digium.com/pipermail/asterisk-dev/2008-May/033101.html

The attached patches cause the name to be generated using the name of the
matched section:

-- Executing Answer("OOH323/h323si-420a", "1") in new stack

The patches also correct five places where the output controlled by
"ooh323 set debug" was sent to ast_log/ast_debug instead of to
ast_verbose.

The patch for 1.4 won't merge to trunk or 1.6.0, so a separate patch has
been included for 1.6.0 and trunk.

====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-28-08 17:23  svnbot         Status                   assigned => resolved
05-28-08 17:23  svnbot         Resolution               open => fixed       
======================================================================