[asterisk-bugs] [JIRA] (ASTERISK-25330) Failed to originate a call using AMI on OOH323 channel (Avaya)

[Vincent BEZARD (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent BEZARD updated ASTERISK-25330:
--------------------------------------

    Attachment: mylogger.txt

Here is the logger content.

> Failed to originate a call using AMI on OOH323 channel (Avaya)
> --------------------------------------------------------------
>
>                 Key: ASTERISK-25330
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25330
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_ooh323
>    Affects Versions: 1.8.13.1
>         Environment: Debian Wheezy
> H323 trunk with an ACM r6.2
>            Reporter: Vincent BEZARD
>         Attachments: mylogger.txt
>
>
> I want to originate a call using AMI to a device localized on the Avaya side.
> My issue: no call is distributedto the ACM.
> Here is the AMI message:
> Action: Originate
> ActionID: 12036987_35#
> Channel: OOH323/avaya-acm/4102
> Context: observeRecord
> Exten: Local/observe
> Priority: 1
> Async: false
> Timeout: 0
> Variable: var1=TOTO|var2=TITI|var3=TUTU
> On the CLI, here is the H323 traces:
> ---   ooh323_request - data avaya-acm/4102 format 0x40 (slin)
> ---   ooh323_alloc
> +++   ooh323_alloc
> ---   find_peer "avaya-acm"
>                 comparing with "192.168.10.102"
>                 found matching peer
> +++   find_peer "avaya-acm"
> ---   ooh323_new - avaya-acm, 64
> +++   h323_new
> +++   ooh323_request
> ---   ooh323_call- avaya-acm/4102
> ---   onNewCallCreated 2d1f8b8: ooh323c_o_13
> ---   find_call
> +++   find_call
> +++   ooh323_call
>        > Channel OOH323/avaya-acm-13 was never answered.
> ---   ooh323_hangup
>     hanging avaya-acm with cause: 16
> +++   ooh323_hangup
>  Outgoing call avaya-acm(ooh323c_o_13) - Codec prefs - (alaw)
>         Adding capabilities to call(outgoing, ooh323c_o_13)
>         Adding g711 alaw capability to call(outgoing, ooh323c_o_13)
> ---   configure_local_rtp
> +++   configure_local_rtp
> +++   onNewCallCreated ooh323c_o_13
> ---   onOutgoingCall 2d1f8b8: ooh323c_o_13
> ---   find_call
> +++   find_call
> +++   onOutgoingCall ooh323c_o_13
> ---   onCallCleared ooh323c_o_13
> ---   find_call
> +++   find_call
> +++   onCallCleared
> ---   ooh323_destroy
>  Destroying avaya-acm
>  Destroying ooh323c_o_13
> +++   ooh323_destroy
> I do not see the call incoming on the ACM side. So, I have made some network traces, and I can see that the only H323 message is related to a RELEASE_COMPLETE => There is no setup message.
> Here is the ooh323.conf:
> [general]
> port=1720
> bindaddr=192.168.40.13
> progress_setup=8
> progress_alert=8
> faststart=yes
> h245tunneling=yes
> gatekeeper=DISABLE
> disallow=all
> allow=alaw
> dtmfmode=inband
> context=internal
> [avaya-acm]
> type=friend
> context=internal
> host=192.168.10.102
> port=1720
> disallow=all
> allow=alaw
> canreinvite=no
> dfmfmode=inband
> e164=#41
> h323id=Asterisk
> Please, advise,
> Vincent



--
This message was sent by Atlassian JIRA
(v6.2#6252)