Macro-user-callerid can't find AMPUSER (FIXED)

Dear,

I’m having a problem with DAHDI extensions and macro-user-callerid. The macro-caller-userid can’t locate the AMPUSER from my DAHDI extensions.
I saw the forum post http://www.freepbx.org/forum/freepbx/users/not-bug-in-2-7-for-zap-handling-but-in-the-chan-dahdi-conf and I did some checks in my configs.

My chan_dahdi_additional.conf ->
;;;;;;[7000]
signalling=fxo_ks
pickupgroup=1
[email protected]
immediate=no
echotraining=yes
echocancelwhenbridged=no
echocancel=yes
context=from-internal
callprogress=yes
callgroup=1
callerid=device <7000>
busydetect=yes
busycount=2
accountcode=7000
channel=>3

[[email protected] asterisk]# asterisk -rx ‘database show device/7000’ ->
Parsing /etc/asterisk/extconfig.conf
/DEVICE/7000/default_user : 7000
/DEVICE/7000/dial : ZAP/3
/DEVICE/7000/type : fixed
/DEVICE/7000/user : 7000
4 results found.
Asterisk ending (0).

And when I place a call from my dahdi extension 7000 to, for exemple, voicemail *97, the 7000 caller id isn’t identified and the feature *97 asks me for my mailbox and password.

Bellow an output log ->

-- Starting simple switch on 'DAHDI/3-1'
-- Executing [*[email protected]:1] Answer("DAHDI/3-1", "") in new stack
-- Executing [*[email protected]:2] Wait("DAHDI/3-1", "1") in new stack
-- Executing [*[email protected]:3] Macro("DAHDI/3-1", "user-callerid,") in new stack
-- Executing [[email protected]:1] Set("DAHDI/3-1", "AMPUSER=") in new stack
-- Executing [[email protected]:2] GotoIf("DAHDI/3-1", "0?report") in new stack
-- Executing [[email protected]:3] ExecIf("DAHDI/3-1", "1?Set(REALCALLERIDNUM=)") in new stack
-- Executing [[email protected]:4] Set("DAHDI/3-1", "AMPUSER=") in new stack
-- Executing [[email protected]:5] Set("DAHDI/3-1", "AMPUSERCIDNAME=") in new stack
-- Executing [[email protected]:6] GotoIf("DAHDI/3-1", "1?report") in new stack
-- Goto (macro-user-callerid,s,10)
-- Executing [[email protected]:10] GotoIf("DAHDI/3-1", "0?continue") in new stack
-- Executing [[email protected]:11] Set("DAHDI/3-1", "__TTL=64") in new stack
-- Executing [[email protected]:12] GotoIf("DAHDI/3-1", "1?continue") in new stack
-- Goto (macro-user-callerid,s,19)
-- Executing [[email protected]:19] NoOp("DAHDI/3-1", "Using CallerID "" <>") in new stack
-- Executing [*[email protected]:4] Macro("DAHDI/3-1", "get-vmcontext,") in new stack
-- Executing [[email protected]:1] Set("DAHDI/3-1", "VMCONTEXT=") in new stack
-- Executing [[email protected]:2] GotoIf("DAHDI/3-1", "1?200:300") in new stack
-- Goto (macro-get-vmcontext,s,200)
-- Executing [[email protected]:200] Set("DAHDI/3-1", "VMCONTEXT=default") in new stack
-- Executing [*[email protected]:5] MailboxExists("DAHDI/3-1", "@default") in new stack
-- Executing [*[email protected]:6] GotoIf("DAHDI/3-1", "0?mbexist") in new stack
-- Executing [*[email protected]:7] VoiceMailMain("DAHDI/3-1", "") in new stack
-- <DAHDI/3-1> Playing 'vm-login.gsm' (language 'en')

I opened a bug ticket but Mister p_lindheimer said this is not a FreePBX bug, is and error in my dahdi configuration, but my chan_dahdi.conf and chan_dahdi_additional.conf are correct because the command asterisk -rx ‘database show device/7000’ reports the correct information.

So, what’s wrong?

what do you get when you type:

dahdi show channel 3

at the CLI?

[[email protected] asterisk]# asterisk -rx 'dahdi show channel 3’
Parsing /etc/asterisk/extconfig.conf
Channel: 3
File Descriptor: 28
Span: 1
Extension:
Dialing: no
Context: from-internal
Caller ID:
Calling TON: 0
Caller ID name:
Mailbox: 7000
Destroy: 0
InAlarm: 0
Signalling Type: FXO Kewlstart
Radio: 0
Owner:
Real:
Callwait:
Threeway:
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no
Busy Detection: yes
Busy Count: 2
Busy Pattern: 0,0
TDD: no
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
DND: no
Echo Cancellation:
128 taps
(unless TDM bridged) currently OFF
Wait for dialtone: 0ms
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Onhook
Asterisk ending (0).

Notice anything wrong with that:

Caller ID:
Caller ID name:

you have a problem with your dahdi configuration.

chan_dahdi.conf:
[channels]
language=en
usecallerid=yes
hidecallerid=no
callwaiting=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
rxgain=5.0
txgain=5.0
progzone=br
tonezone=20
cidsignalling=dtmf
cidstart=polarity
canpark=yes
callreturn=yes
useincomingcalleridondahditransfer=yes

;;;;;;[2130157398]
group=0
callgroup=0
pickupgroup=0
signalling=fxs_ks
callerid=asreceived
context=from-zaptel
echotraining=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=yes
busydetect=yes
busycount=2
callprogress=yes
channel=>1

;;;;;;[2130055849]
group=0
callgroup=0
pickupgroup=0
signalling=fxs_ks
callerid=asreceived
faxdetect=incoming
context=from-zaptel
echotraining=yes
echocancel=yes
echocancelwhenbridged=no
busydetect=yes
busycount=2
callprogress=yes
channel=>2

#include chan_dahdi_additional.conf

chan_dahdi_additional.conf:
;;;;;;[7000]
signalling=fxo_ks
pickupgroup=1
[email protected]
immediate=no
echotraining=yes
echocancelwhenbridged=no
echocancel=yes
context=from-internal
callprogress=yes
callgroup=1
callerid=device <7000>
busydetect=yes
busycount=2
accountcode=7000
channel=>3

;;;;;;[7100]
signalling=fxo_ks
pickupgroup=1
[email protected]
immediate=no
echotraining=yes
echocancelwhenbridged=no
echocancel=yes
context=from-internal
callprogress=yes
callgroup=1
callerid=device <7100>
busydetect=yes
busycount=2
accountcode=7100
channel=>4

Well, I felt compelled to come here to inform you that, in fact, the problem is not with FreePBX, but with Asterisk. I’ve found the solution with the developers and not an error in my settings.

I’m sorry. I forgot to inform the path to the solution. :slight_smile:

https://issues.asterisk.org/view.php?id=16968

glad to see you got the issue resolved.

I must assume that you upgraded something else in Asterisk as well to introduce the new asterisk (well dahdi) bug, and thus it wasn’t “exactly after updating core.”

It’s a good idea in the future to not update multiple system components at once. It’s also a good idea to disclose that information when seeking help, you are much more likely to get better suggestions and guidance.

I am having this same issue. I am running FPBX 2.8 on Asterisk 1.6.16.1 on one box and 1.8.2.2 on another and both are still having this issue. I have tried running the patch, which says it’s already been applied, and either way it still happens. I’ll report it in Asterisk forums as well. The output of dahdi show chanel # shows nothing for Caller ID nor Caller ID Name. Just wondering if anyone else is still dealing with this.