[asterisk-bugs] [JIRA] (ASTERISK-17172) [patch] OOH323 Incoming and Outgoing Calls Fail Avaya with Asterisk 1.8.1.1

AvayaXAsterisk (JIRA) noreply at issues.asterisk.org
Sat Sep 20 17:20:28 CDT 2014


    [ https://issues.asterisk.org/jira/browse/ASTERISK-17172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222722#comment-222722 ] 

AvayaXAsterisk commented on ASTERISK-17172:
-------------------------------------------

Running into exactly the same console and log messages with outgoing calls. Using Asterisk 11.6. Incoming calls are fine. Help appreciated

> [patch] OOH323 Incoming and Outgoing Calls Fail Avaya with Asterisk 1.8.1.1
> ---------------------------------------------------------------------------
>
>                 Key: ASTERISK-17172
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17172
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Addons/chan_ooh323
>            Reporter: Vladimir Mikhelson
>         Attachments: 16min disconnect.pcap, 16 minutes drop, packet 20 discarded.pcap, 2011-01-25-h245tunneling--packet-c.cap, 30 seconds drop.pcap, 5 minute drop.pcap, avaya.txt, GDB.TXT, H323_LOG-16 minutes failure and undalanced structures, H323_LOG_18542_PATCH1, H323_LOG-32sec_disconnect, h323_log-5_minute_drop, H323_LOG-both incoming and outgoing, H323_LOG-h245 disabled.txt, H323_LOG-h245tunneling=on_no sound_30 seconds disconnect.txt, H323_LOG-incoming_16_min_disconnect.txt, H323_LOG-incoming_inconsistency, H323_LOG-no _r_ in dial command options.txt, h323_log-patch1+no_h245_tunneling.txt, H323_LOG-patch2-dropped_incoming_call.txt, H323_LOG-see Avaya Log.txt, issue18542-2.patch, issue18542-3.patch, issue18542-4.patch, issue18542-5.patch, issue18542-6.patch, issue18542-final-3-1.8.2.3.patch, issue18542-final-3.patch, issue18542.patch, OOH323.CONF
>
>
> 1. Upgraded to Asterisk 1.8.1.1 from Asterisk 1.6.2.15.
> 2. All outgoing calls started to fail.
> 3. "ooh323 show" was not recognized as a valid command. Auto-complete worked though.
> 4 Rebooted the system.
> CLI:
> pbx*CLI> ooh323 show peers
> Name             Accountcode      ip:port                  Formats
> avaya            h3230101         172.17.135.2:1720        0x4 (ulaw)
> FreePBX 2.8.0.4
> AsteriskNOW 1.7
> ****** ADDITIONAL INFORMATION ******
> Sections form the logs with the failure reason.
> Console log:
>     -- Executing [s at macro-dialout-trunk:27] Dial("DAHDI/7-1", "OOH323/352/avaya,300,tr") in new stack
>   == Everyone is busy/congested at this time (1:0/0/1)
>     -- Executing [s at macro-dialout-trunk:28] NoOp("DAHDI/7-1", "Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 0") in new stack
> Asterisk log:
> [Dec 28 11:09:27] VERBOSE[3230] pbx.c: -- Executing [s at macro-dialout-trunk:27] Dial("DAHDI/7-1", "OOH323/352/avaya,300,tr") in new stack
> [Dec 28 11:09:27] ERROR[3230] chan_ooh323.c: Call to undefined peer 352[Dec 28 11:09:27] WARNING[3230] app_dial.c: Unable to create channel of type 'OOH323' (cause 0 - Unknown)
> [Dec 28 11:09:27] VERBOSE[3230] app_dial.c: == Everyone is busy/congested at this time (1:0/0/1)
> Asterisk log:
> [Dec 28 10:54:09] VERBOSE[2700] config.c: == Parsing '/etc/asterisk/ooh323.conf': [Dec 28 10:54:09] VERBOSE[2700] config.c: == Found
> [Dec 28 10:54:09] VERBOSE[2700] chan_ooh323.c: -- == Setting default context to default
> [Dec 28 10:54:09] VERBOSE[2700] channel.c: == Registered channel type 'OOH323' (Objective Systems H323 Channel Driver)
> [Dec 28 10:54:09] VERBOSE[2700] rtp_engine.c: == Registered RTP glue 'OOH323'
> [Dec 28 10:54:09] VERBOSE[2700] loader.c: chan_ooh323.so => (Objective Systems H323 Channel)
> h323_log:
> Shows the time stamp of the system restart.  Zero bytes.



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



More information about the asterisk-bugs mailing list