I’m attempting to place an outgoing call over POTS/DAHDI, it dials without problem but the remote answer isn’t tried.

So far I’ve attempted:

– Searching on google
– Enabling full and verbose logging (including the debug option of the
DAHDI module) – showing NO event at the time I answer on the remote phone
a.k.a “my mobile”
– Using another phone on the same line – it works
– Receiving a call on that line – no problem
– Logging DTMF – it shows digits dialled on my mobile, after I’ve
answered, even whilst it seems to still be ringing locally
– Looking on the wiki
– Asking on IRC

So far, I’ve found nothing that helps.

A sample log output is here: http://pastebin.com/cprZSy9i And my chan_dahdi.conf: http://pastebin.com/L7mBJ66Y
And dahdi system.conf: http://pastebin.com/6UQPVC9x also in modprobe.d/dahdi.conf: http://pastebin.com/5ZqtcZdj

*any* advice/suggestions at this point would be very much appreciated!

I have a recurrent problem on my asterisk box. I have “VIA Samuel 2″ as a CPU. With asterisk v11.1.0 and dahdi-linux-complete-2.6.1+2.6.1 compiled from source.

I get a RED alrm drom the port 1( FXO) two or three times per day:

[Feb 4 15:54:57] WARNING[9991]: chan_dahdi.c:8018 handle_alarms: Detected alarm on channel 1: RED Alarm




I plug the RJ11 in a normal phone and I can hear the line is up and I can call extern number (via PSTN)

I must stop asterisk + restart dahdi and start asterisk to get asterisk work normaly. I have no idea where is the problem or even what to do to debug the issue



I get these outputs when the channel is in “RED Alarm”

root@pbx01:~# /etc/init.d/dahdi status
### Span 1: WCTDM/0 “Wildcard TDM410P” (MASTER)
1 FXO FXSKS (In use) (EC: MG2 – INACTIVE) RED <=======This is my problem !
2 FXO FXSKS (EC: MG2 - INACTIVE) RED
3 FXS FXOKS (In use) (EC: MG2 - INACTIVE)
4 FXS FXOKS (In use) (EC: MG2 - INACTIVE)



pbx01*CLI> dahdi show status Description Alarms IRQ bpviol CRC Fra Codi Options LBO
Wildcard TDM410P OK 0 0 0 CAS
Unk 0 db (CSU)/0-133 feet (DSX-1)
pbx01*CLI>


pbx01*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked
State Description pseudo default default
In Service
1 from-pstn default
In Service
3 local default
In Service
4 local default
In Service pbx01*CLI> dahdi show cadences channel channels status version pbx01*CLI> dahdi show cadences r1: 125,125,2000,4000
r2: 250,250,500,1000,250,250,500,4000
r3: 125,125,125,125,125,4000
r4: 1000,500,2500,5000



pbx01*CLI> dahdi show version DAHDI Version: 2.6.1 Echo Canceller: HWEC, MG2


pbx01*CLI> dahdi show channel 1
Channel: 1
Description:
File Descriptor: 12
Span: 1
Extension:
Dialing: no Context: from-pstn Caller ID:
Calling TON: 0
Caller ID subaddress:
Caller ID name: port-bell01
Mailbox: 1
Destroy: 0
InAlarm: 1
Signalling Type: FXS Kewlstart Radio: 0
Owner:
Real:
Callwait:
Threeway:
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no Busy Detection: no TDD: no Relax DTMF: no Dialing/CallwaitCAS: 0/0
Default law: ulaw Fax Handled: no Pulse phone: no Gains (RX/TX): 0.00/0.00
Dynamic Range Compression (RX/TX): 0.00/0.00
DND: no Echo Cancellation:
128 taps currently OFF
Wait for dialtone: 0ms Actual Confinfo: Num/0, Mode/0×0000
Actual Confmute: No Hookstate (FXS only): Onhook




Is it a known bug ? Why I have to restart dhadi to resolve this ?

Thanks a lot !

Hello out there,

I’m running an Asterisk 1.8.15-cert1 with DAHDI. Today I noticed that Asterisk is signalling to the calling party the current internal CallerID whenever I put a call to another internal phone.

Example:

Customer calls 020212345-555
-> IVR answers and puts caller to the chosen queue
-> Someone picks up the phone (Internal ext. 321)
-> CallerID shown on customers device changes to
020212345-321

Same when I park the call and pick it up on another phone.


I don’t want this to happen and can’t figure out how to disable this on DAHDI or at least the current channel. I tried “facilityenable=no” in chan_dahdi.conf, but this only supresses signalling the on hold status.

We are using a german ISDN “Anlagenanschluss” (bri_cpe) whith DDI served by the Deutsche Telekom, connected to a ISDN card which is used with DAHDI.


Is there a hidden config flag or something to disable this for DAHDI?
Or maybe a channel variable to temporarily disabling this on some channels?


THANK YOU!

Greetings from Wuppertal Max

Hi, all. I’m upgrading my company’s old 1.2 box with a new-and-improved one. But a fair bit’s changed in the interim. To start, at least, I just want the new box to act as a pass-through for all calls — PSTN calls go, unmodified, to the internal T1, and vice-versa. (That way, I can begin to build a skeleton dialplan and work my way forward from there.) But I’m bumping into problems:
— Executing [6000@pstn:1] Dial(“DAHDI/i1/6034941234-1″,
“DAHDI/G2/6000″) in new stack
[Jan 21 12:19:35] WARNING[15163][C-00000000]: app_dial.c:2433
dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 0 –
Unknown)

So, a few questions:
1) What’s the difference between chan_dahdi.conf and dahdi-channels.conf?
2) Could someone show me a SuperDumb(tm) minimal config for the necessary /etc/*dahdi*.conf and /etc/extensions.conf files?

Thanks!

-Ken

Hello,

We want the ability to choose from an AGI script whether or not to enable faxdetect for calls over SIP or DAHDI. Is this possible, or can anyone suggest a workaround?

Thanks for any advice.