[asterisk-bugs] [JIRA] (ASTERISK-21800) ooh323 channels stuck if no gatekeer or ooh323 reload
Alexander Anikin (JIRA)
noreply at issues.asterisk.org
Thu May 30 07:17:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206899#comment-206899 ]
Alexander Anikin commented on ASTERISK-21800:
---------------------------------------------
Formally it must be 21 (Call rejected) or 38 (network out of order), i think 38 is more correct but will take example from another channel drivers.
> ooh323 channels stuck if no gatekeer or ooh323 reload
> -----------------------------------------------------
>
> Key: ASTERISK-21800
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21800
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Addons/chan_ooh323
> Affects Versions: 11.3.0
> Environment: Centos 6 x86
> Reporter: Dmitry Melekhov
> Assignee: Alexander Anikin
> Attachments: ASTERISK-21800.patch, h323_log
>
>
> Hello!
> This happens second time after upgrade to 11.x several weeks ago- if I reboot server with gnugk I get stuck channels:
> {noformat}
> ast-nsk*CLI> pri show channels
> PRI B Chan Call PRI Channel
> Span Chan Chan Idle Level Call Name
> 1 1 Yes No Overlap No DAHDI/i1/7171-ad
> 1 2 Yes No Overlap No DAHDI/i1/7175-ae
> 1 3 Yes No Overlap No DAHDI/i1/7171-af
> 1 4 Yes No Overlap No DAHDI/i1/7175-b0
> 1 5 Yes No Connect Yes DAHDI/i1/7116-b1
> 1 6 Yes No Connect Yes DAHDI/i1/7024-b6
> 1 7 Yes No Connect Yes DAHDI/i1/7000-b8
> 1 8 Yes No Connect Yes DAHDI/i1/7109-b7
> 1 9 Yes Yes Idle No
> 1 10 Yes No Connect Yes DAHDI/i1/7094-bb
> 1 11 Yes No Overlap Yes DAHDI/i1/7171-bc
> 1 12 Yes Yes Idle No
> 1 13 Yes Yes Idle No
> 1 14 Yes Yes Idle No
> 1 15 Yes Yes Idle No
> 1 17 Yes Yes Idle No
> 1 18 Yes Yes Idle No
> 1 19 Yes Yes Idle No
> 1 20 Yes Yes Idle No
> 1 21 Yes Yes Idle No
> 1 22 Yes Yes Idle No
> 1 23 Yes Yes Idle No
> 1 24 Yes Yes Idle No
> 1 25 Yes Yes Idle No
> 1 26 Yes Yes Idle No
> 1 27 Yes Yes Idle No
> 1 28 Yes Yes Idle No
> 1 29 Yes No Overlap No DAHDI/i1/7175-aa
> 1 30 Yes No Overlap No DAHDI/i1/7175-ab
> 1 31 Yes No Overlap No DAHDI/i1/7171-ac
> ast-nsk*CLI> core show cha
> channel channels channeltypes channeltype
> ast-nsk*CLI> core show channels
> Channel Location State Application(Data)
> DAHDI/i1/7175-b0 6879 at dahdi:5 Ring Dial(OOH323/6879)
> OOH323/4271-184 (None) Down (None)
> DAHDI/i1/7171-ac 4271 at dahdi:5 Ring Dial(OOH323/4271)
> DAHDI/i1/7171-ad 4271 at dahdi:5 Ring Dial(OOH323/4271)
> DAHDI/i1/7171-af 4271 at dahdi:5 Ring Dial(OOH323/4271)
> OOH323/192.168.46.40 7094 at h323:2 Up Dial(DAHDI/g1/7094)
> OOH323/4271-172 (None) Down (None)
> OOH323/4271-170 (None) Down (None)
> OOH323/4271-169 (None) Down (None)
> DAHDI/i1/7171-bc 4271 at dahdi:5 Ring Dial(OOH323/4271)
> OOH323/6879-167 (None) Down (None)
> OOH323/6879-168 (None) Down (None)
> OOH323/6879-171 (None) Down (None)
> OOH323/6879-173 (None) Down (None)
> DAHDI/i1/7000-b8 (None) Up AppDial((Outgoing Line))
> DAHDI/i1/7116-b1 (None) Up AppDial((Outgoing Line))
> DAHDI/i1/7094-bb (None) Up AppDial((Outgoing Line))
> DAHDI/i1/7024-b6 (None) Up AppDial((Outgoing Line))
> OOH323/192.168.22.25 7024 at h323:2 Up Dial(DAHDI/g1/7024)
> OOH323/192.168.22.25 7116 at h323:2 Up Dial(DAHDI/g1/7116)
> OOH323/10.2.2.10-181 7000 at h323:2 Up Dial(DAHDI/g1/7000)
> OOH323/10.2.2.10-180 7109 at h323:2 Up Dial(DAHDI/g1/7109)
> DAHDI/i1/7175-ae 6879 at dahdi:5 Ring Dial(OOH323/6879)
> DAHDI/i1/7175-aa 6879 at dahdi:5 Ring Dial(OOH323/6879)
> DAHDI/i1/7175-ab 6879 at dahdi:5 Ring Dial(OOH323/6879)
> DAHDI/i1/7109-b7 (None) Up AppDial((Outgoing Line))
> 26 active channels
> 13 active calls
> 187 calls processed
> {noformat}
> there is script which do ooh323 reload if there is no registration in gatekeeper, not sure what causes this- no connection to gatekeeper or ooh323 reload.
> There is no such problem in 10.x ..
> Thank you!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list