[asterisk-bugs] [JIRA] Issue Comment Edited: (ASTERISK-19308) problem with transit calls ooh323-dahdi(pri)-panasonic 500

[Alexander Anikin (JIRA)]

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

Alexander Anikin edited comment on ASTERISK-19308 at 8/10/12 11:34 AM:
-----------------------------------------------------------------------

The problem is in indicate routine that mark call as already gone and hangup isn't send that is wrong.

      was (Author: may213):
    The problem is in indicate routine that mark call as already gone. This cause hangup isn't send that wrong.
  
> problem with transit calls ooh323-dahdi(pri)-panasonic 500
> ----------------------------------------------------------
>
>                 Key: ASTERISK-19308
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19308
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_ooh323
>    Affects Versions: 10.2.0
>         Environment: Centos 6 x86
>            Reporter: Dmitry Melekhov
>            Assignee: Alexander Anikin
>            Severity: Critical
>         Attachments: ASTERISK-19308.patch, h323_log.7169
>
>
> Here is call from ooh323 to dahdi how I see it in console (there are several other calls, I removed info about them):
>     -- Executing [7015 at h323:1] Set("OOH323/10.3.1.3-83", "FAXOPT(t38gateway)=yes") in new stack
>     -- Executing [7015 at h323:2] Dial("OOH323/10.3.1.3-83", "DAHDI/g1/7015") in new stack
>     -- Requested transfer capability: 0x00 - SPEECH
>     -- Called DAHDI/g1/7015
>     -- DAHDI/i1/7015-54 is making progress passing it to OOH323/10.3.1.3-83
>     -- DAHDI/i1/7015-54 is busy
>     -- Hungup 'DAHDI/i1/7015-54'
>   == Everyone is busy/congested at this time (1:1/0/0)
>     -- Auto fallthrough, channel 'OOH323/10.3.1.3-83' status is 'BUSY'
> now I have this channel busy on ooh323 side:
> ast-nsk*CLI> core show channels
> Channel              Location             State   Application(Data)             
> OOH323/10.3.1.3-83   7015 at h323:3          Busy    (None)                        
> 1 active channel
> 1 active call
> and there is problem with new calls:
>     -- DAHDI/i1/7024-5a is making progress passing it to OOH323/192.168.22.253-89
>     -- DAHDI/i1/7024-5a is proceeding passing it to OOH323/192.168.22.253-89
>     -- DAHDI/i1/7024-5a is ringing
> [Feb  8 11:42:43] WARNING[23285]: app_dial.c:1379 wait_for_answer: Unable to write frametype: 2
> [Feb  8 11:42:43] WARNING[23285]: app_dial.c:1379 wait_for_answer: Unable to write frametype: 2
> [Feb  8 11:42:43] WARNING[23285]: app_dial.c:1379 wait_for_answer: Unable to write frametype: 2
> [Feb  8 11:42:43] WARNING[23285]: app_dial.c:1379 wait_for_answer: Unable to write frametype: 2
>     -- Hungup 'DAHDI/i1/7024-5a'
>   == Spawn extension (h323, 7024, 2) exited non-zero on 'OOH323/192.168.22.253-89'
> and system load is very high:
> load average: 5.63, 5.32, 3.33
> asterisk eats cpu:
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
> 23055 asterisk -11   0  156m 126m   9m S 94.7  8.4  14:07.49 asterisk 
> Looks like there is no such problem when there are not more then 2 concurrent calls,but when load increases up to 5-6... and we have no such problem with different, but similar configuration, where transit is SIP- dahdi- TS-004 (PRI switch).
> What can be wrong? What can I do to solve this problem?
> Thank you!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira