Channels Busy

Asterisk Asterisk Support
1

I have an Asterisk application, and Digium 8 port analog card, I have the following configuration:

context=from-internal
group=1
echocancel=yes
signalling = fxs_ks
channel = 1-8

Connect a telephone line that has the number 12345 on channel 1 … Everything works fine there …
When I connect the phone line 2 having the number 67890 on channel 2 and make a call marks all busy …

In the extensions.conf file and performed the call request

exten => ${NUMTEL},n,Dial(DAHDI/1&DAHDI/2&DAHDI/3&DAHDI/4&DAHDI/5&DAHDI/6&DAHDI/7&DAHDI/8,20,rt)

The log has this

– Starting simple switch on ‘DAHDI/2-1’
– Executing [s@from-internal:1] Answer(“DAHDI/2-1”, “”) in new stack
– Executing [s@from-internal:2] Dial(“DAHDI/2-1”, “DAHDI/1&DAHDI/2&DAHDI/3&DAHDI/4&DAHDI/5&DAHDI/6&DAHDI/7&DAHDI/8,20,rt”) in new stack
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:13] WARNING[17173][C-00000001]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
– Called DAHDI/1
– DAHDI/1-1 answered DAHDI/2-1
– Hanging up on ‘DAHDI/1-1’
– Hungup ‘DAHDI/1-1’
== Spawn extension (from-internal, s, 2) exited non-zero on ‘DAHDI/2-1’
– Hanging up on ‘DAHDI/2-1’
– Hungup ‘DAHDI/2-1’
– Starting simple switch on ‘DAHDI/1-1’
– Executing [s@from-internal:1] Answer(“DAHDI/1-1”, “”) in new stack
– Executing [s@from-internal:2] Dial(“DAHDI/1-1”, “DAHDI/1&DAHDI/2&DAHDI/3&DAHDI/4&DAHDI/5&DAHDI/6&DAHDI/7&DAHDI/8,20,rt”) in new stack
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
[Oct 10 12:59:54] WARNING[17176][C-00000002]: app_dial.c:2437 dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 - User busy)
– Called DAHDI/2
– DAHDI/2-1 answered DAHDI/1-1
– Hanging up on ‘DAHDI/2-1’
– Hungup ‘DAHDI/2-1’
== Spawn extension (from-internal, s, 2) exited non-zero on ‘DAHDI/1-1’
– Hanging up on ‘DAHDI/1-1’
– Hungup ‘DAHDI/1-1’

I feel that I must group the number 12345 and 67890 somewhere … any ideas?

Thank you very much

2

Extension number patterns are parsed at file parse time. Variables are not substituted until call time. You cannot have a variable in the extension or priority fields.

3

Thanks … if I make the change that you mention it … I mark

Channel ‘DAHDI / 1-1’ sent to invalid extension handler but not invalid: context, exten, priority = from-internal, s, 1

To the extent I put the phone number 12345

What is it?

4

Firstly, your subject is confusing as none of this relates to busy channels. In fact the logs you provided showed two successful calls.

You have signalling =fxs_ks. That is for use on exchange lines and does not support incoming dialed digits. If these lines really are FXO lines, you will need ISDN to have any hope of receiving the dialed number.

If you want to run an automated attendant, you will have to explicitly read the digits or use WaitExten, after answering the call.

If these re really on FXS interfaces, you will need fxo… type signalling.