| Summary: | ASTERISK-11149: On high call volumne chan_zap is not working properly | ||
| Reporter: | ss7pro (ss7pro) | Labels: | |
| Date Opened: | 2008-01-04 06:22:32.000-0600 | Date Closed: | 2011-06-07 14:07:54 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_zap |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | issue related to: 0008507 with the asterisk 1.4.15, libpri 1.4.3 problem still exists. | ||
| Comments: | By: Jason Parker (jparker) 2008-01-04 10:20:17.000-0600 How is it "not working properly"? We need some detail here. By: ss7pro (ss7pro) 2008-01-08 10:23:27.000-0600 Asterisk cannot create new calls: app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) Configuration is very easy: 30 channels for incoming calls and 30 channels for outgoing calls. When this situation occurs there're free channels on outoging trunk. By: acid (acid) 2008-01-12 13:12:12.000-0600 I've some basic idea about this problem. I think that there's no enough space on D channel to setup new call. Does anybod know how many new calls per second can fit on single D channel ? By: dustyc21 (dustyc21) 2008-01-16 16:25:43.000-0600 Same issue here, running 1.4.11 and zaptel 1.4.6 Seeing anywhere from 12 to 50 percent of calls go into Cause 34 status when auto-dialing beyond 12 lines at a time. I tried putting waits in the dialplan to space out the requests for a channel, thinking that might have some effect, but I never got consistent results from my testing. By: jmls (jmls) 2008-02-17 12:51:37.000-0600 is this still an issue with the latest 1.4 ? By: Tilghman Lesher (tilghman) 2008-05-19 15:37:09 Suspending for no response. Please reopen if you are able to reproduce this in 1.4.19 or later. | ||