[asterisk-bugs] [Asterisk 0017186]: OOH323 Outgoing Call Fails if Originated from a DAHDI Extension

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17186 
====================================================================== 
Reported By:                vmikhelson
Assigned To:                may213
====================================================================== 
Project:                    Asterisk
Issue ID:                   17186
Category:                   Addons/chan_ooh323
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.2.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-15 01:10 CDT
Last Modified:              2010-04-17 16:32 CDT
====================================================================== 
Summary:                    OOH323 Outgoing Call Fails if Originated from a
DAHDI Extension
Description: 
A call originated from a DAHDI extension on Asterisk 1.6.2.6 rings
indefinitely. The destination end point, Avaya IPOffice 403, does not show
a call in its monitor. After the call is hung, the following shows up in
Avaya monitor:
5272909mS H323Rx: src=172.17.137.11:12032
            H323 Pcol=08(Q931) Reflen=2 ref=004B(Remote)
            Message Type = ReleaseComplete

 5272910mS PRN: Could not decode field index 51 + 0
 5272910mS PRN: H225.0 Decode Failure!
 5272911mS PRN: BUF ff029570 : data=ff08a056 , length = 34
 5272911mS PRN: 0000 25 c0 05 00 08 91 4a 00 04 58 88 00 11 00 6f 6f
%....J..X....oo
 5272912mS PRN: 0010 68 33 32 33 63 2d 02 9b 74 00 00 00 00 00 10 80
h323c-..t.......
 5272912mS PRN: 0020 01 80                                           ..
 5272912mS PRN: Buf2Sys failed 'Decode failed!'

h323_log shows ASN1 Errors and "Unbalanced Structure" errors.

Logs attached.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016968 [patch] Callerid  Channel dahdi port FX...
====================================================================== 

---------------------------------------------------------------------- 
 (0120564) may213 (manager) - 2010-04-17 16:32
 https://issues.asterisk.org/view.php?id=17186#c120564 
---------------------------------------------------------------------- 
Seen in log:

00:27:06:756  Added local alias  to call. (outgoing, ooh323c_o_3)

and after

00:27:06:874  Built SETUP message (outgoing, ooh323c_o_3)
00:27:06:874  Asn1Error: -23 at ooh323c/src/encode.c:516
00:27:06:874  Asn1Error: -23 at ooh323c/src/encode.c:969
00:27:06:874  Asn1Error: -23 at ooh323c/src/encode.c:237
00:27:06:874  ERROR: UserInfo encoding failed
00:27:06:874  Error:Failed to encode uuie. (outgoing, ooh323c_o_3)
00:27:06:874  Error:Failed to encode H225 message. (outgoing,
ooh323c_o_3)
00:27:06:874  Error:Failed to enqueue SETUP message to outbound queue.
(outgoing, ooh323c_o_3)

seems like to incorrect alias added to h323 call alias fields.
Also need to think about hangup sending in this case, we can't send setup
due to incorrect encoding but we try send hangup to close non-opened call. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-17 16:32 may213         Note Added: 0120564                          
======================================================================