*8 not picking up ringing phone

General Help
1

I installed the FreePBX 2.7 and everything else seems working fine. But pickup ringing extensions using *8 not working. I checked *8 is enabled, ** also enabled in the feature code. (however, from top meny bar, between panel and help, click on the recording and login, I don’t see *8 listed in that feature code listing).

In the chan_dahdi.conf, each channel also have callgroup=1 and pickupgroup=1 before the channel number. But I could not get any extension pickup. Looked the full log, it seems the extension trying to pick up always hangup by pbx.c.

[Mar 24 15:23:34] VERBOSE[22262] app_dial.c: – DAHDI/1-1 is ringing
[Mar 24 15:23:35] VERBOSE[22264] chan_dahdi.c: – Starting simple switch on ‘DAHDI/2-1’
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [*8@from-internal:1] Macro(“DAHDI/2-1”, “user-callerid,SKIPTTL,”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:1] Set(“DAHDI/2-1”, “AMPUSER=7010”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:2] GotoIf(“DAHDI/2-1”, “0?report”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:3] ExecIf(“DAHDI/2-1”, “1?Set(REALCALLERIDNUM=7010)”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:4] Set(“DAHDI/2-1”, “AMPUSER=7010”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:5] Set(“DAHDI/2-1”, “AMPUSERCIDNAME=my name”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:6] GotoIf(“DAHDI/2-1”, “0?report”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:7] Set(“DAHDI/2-1”, “AMPUSERCID=7010”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:8] Set(“DAHDI/2-1”, “CALLERID(all)=“my name” <7010>”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:9] GotoIf(“DAHDI/2-1”, “1?continue”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Goto (macro-user-callerid,s,18)
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-user-callerid:18] NoOp(“DAHDI/2-1”, “Using CallerID “my name” <7010>”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Auto fallthrough, channel ‘DAHDI/2-1’ status is ‘UNKNOWN’
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [h@from-internal:1] Macro(“DAHDI/2-1”, “hangupcall”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Executing [s@macro-hangupcall:1] GotoIf(“DAHDI/2-1”, “1?skiprg”) in new stack
[Mar 24 15:23:37] VERBOSE[22264] pbx.c: – Goto (macro-hangupcall,s,4)
What could be wrong with this one?
Thanks so much for your help!

2

When you want to pickup dial ** followed by the extention that is ringing.

3

**EXT can pick up the call, but *8 just gave busy signals. With many phones ring in similar tone, it is hard to tell which extension is ringing. It would be nice to have *8 to pickup any ringing phone.

4

Look at each of your extensions and insure the “Pickup Group” is set on them. They must be in the same pickup group for the *8 pickup to work.

5

Yes, I have them in the chan_dahdi.conf file already:
group=1
signalling=fxo_ks
context=from-internal
callerid=“name1”<7009>
mailbox=7009
callgroup=1
pickupgroup=1
channel => 1
callerid=“my name”<7010>
mailbox=7010
callgroup=1
pickupgroup=1
channel => 2
callerid=“name3”<7011>
mailbox=7011
callgroup=1
pickupgroup=1
channel => 3
callerid=“name4”<7012>
mailbox=7012
callgroup=1
pickupgroup=1
channel => 4

You can see them all in the same callgroup and also in the same pickupgroup. I add them all in the same queue, from large to small ring in the liner order. I can hear them ring when call coming. From tar - f /ver/log/asterisk/full, I can see each extension in turn being rang. But *8 immediately got a busy tone. From the log I provided, it showed when DAHDI/2-1 trying to pick up the call ringing at DAHDI/1-1, pbx.c actually called macro “hangupcall”.

Since this is a feature has been there for serveral version, I am sure there is something wrong with my configuration somewhere.