Need help on Asterisk Now 2.0.2 (with FreePBX.) + Digium TE122P

I’m relatively new to the Asterisk environment.
So bear with me.
I try to implement an Asterisk based PBX Now 2.0x for this
I purchased a Digium TE122P twenty days ago.
I followed all instructions in the manuals available for configuration and still not get to run the system.
Communication between internal extensions work, I configured the inbound and outbound routes, dialing rules, etc.
After many hours of research and assistance of a friend who knows a bit more about it I noticed that in the detection of hardware, it reports the following:

Span: Wildcard TE122, Card 1 - Port (span_1)
Alarms: OK
Framing / Coding: D4/AMI
Channels Used / Total: 24/24
Signalling: me_w

It Shows the 24 channels in use.
It shouldn’t be, right?

Unless all channels are in use for outgoing and incoming calls from registered SIP extensions.

Currently I only have three SIP registered extensions.
And my PBX does not have internet access right now.

This is the content of the configuration files of my system.
I hope you can help me.

chan_dadhi.conf:

; Copied from DAHDI Module of FreePBX

[general]

#include chan_dahdi_general.conf

[channels]

; include dahdi groups defined by DAHDI module of FreePBX
#include chan_dahdi_groups.conf

; include dahdi extensions defined in FreePBX
#include chan_dahdi_additional.conf

dahdi_channels.conf:

; Span 1: WCT1/0 “Wildcard TE122 Card 0” (MASTER)
group=0,11
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 1-23
context = default
group = 63

chan_dahdi_groups.conf:

; [span_1]
signalling=em_w
switchtype=national
pridialplan=unknown
prilocaldialplan=unknown
group=0
context=from-pstn
channel=1-24

/etc/dahdi/system.conf:

span=1,0,0,D4,AMI
e&m=1-24
loadzone=us
defaultzone=us

In the asterisk CLI try typing “dahdi show channels”. Does it output all 24 channels and say “In Service”?

What is the output of your asterisk console when you try to send a call to and outside number?

Hi Wrender

Thanks

when executing “dahdi show channels”

it returns:

elastix*CLI> core show channels
Channel Location State Application(Data)
0 active channels
0 active calls

When i try to call an outside number, the Asterisk logs shows this:

Executed application: Set
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:15] ExecIf(“SIP/122-09289058”, “0|Set|DIAL_TRUNK_OPTIONS=M(setmusic^)”) in new stack
Oct 14 21:03:38 DEBUG [3292] app_macro.c:
Executed application: ExecIf
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:16] Macro(“SIP/122-09289058”, “dialout-trunk-predial-hook|”) in new stack
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:1] MacroExit(“SIP/122-09289058”, “”) in new stack
Oct 14 21:03:38 DEBUG [3292] app_macro.c:
Executed application: Macro
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:17] GotoIf(“SIP/122-09289058”, “0?bypass|1”) in new stack
Oct 14 21:03:38 DEBUG [3292] app_macro.c:
Executed application: GotoIf
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:18] GotoIf(“SIP/122-09289058”, “0?customtrunk”) in new stack
Oct 14 21:03:38 DEBUG [3292] app_macro.c:
Executed application: GotoIf
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:19] Dial(“SIP/122-09289058”, “DAHDI/g0/8096817357|300|”) in new stack
Oct 14 21:03:38 NOTICE [3292] app_dial.c:
Hey! chan SIP/122-09289058’s context=‘macro-dialout-trunk’, and exten='s’
Oct 14 21:03:38 WARNING [3292] channel.c:
No channel type registered for 'DAHDI’
Oct 14 21:03:38 WARNING [3292] app_dial.c:
Unable to create channel of type ‘DAHDI’ (cause 66 - Channel not implemented)
Oct 14 21:03:38 VERBOSE [3292] logger.c:
== Everyone is busy/congested at this time (1:0/0/1)
Oct 14 21:03:38 DEBUG [3292] app_macro.c:
Executed application: Dial
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Executing [[email protected]:20] Goto(“SIP/122-09289058”, “s-CHANUNAVAIL|1”) in new stack
Oct 14 21:03:38 VERBOSE [3292] logger.c:
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)

Ariel Almonte

Have you run the dahdi configuration utilities?

For example,

  • “dahdi-cfg -vv” to configure the dahdi kernel modules.
  • “dahdi-genconf” to generate the dahdi config files.

Then after that you will want to restart the dahdi services, and then asterisk. On a centos/redhat based server normally you would do “service dahdi restart” and then “service asterisk restart”.

Beyond that maybe it could be an advanced T1 setting that is not working. Like your signalling is incorrect for the type of interface or something like that?