Nothing Outbound Works

Greetings,

We have a trixbox setup running and working.

I see almost no support left for the trixbox so I built up a FreePBX using a FreePBX Distro 1.812.210.57 32Bit.

The card currently in the trixbox is the DIGIUM TDM2400P. This is the exact card I need to use in my FreePBX box.

I basically went into the trixbox and menu by menu, copied the extensions, trunks, ring groups, and basic settings. I also followed the Installing the FreePBX Distro documentation, followed by the First Steps After Installation to the best I could.

I am only using 3 analog lines coming in and all phones are analog.

I was given the opportunity to shut down the trixbox and put the card into the new machine to try it out. Everything internal works from what I could tell (calling other extensions, ect). HOWEVER, I cannot dial out.

I checked the settings in the trunk menu compared to the trunks on the trixbox and they are nearly identical.

I made sure the outbound routes are the same. The dial routes look different from the trixbox but they are set up by selecting a drop-down menu item.

Perhaps I am missing a step. Any ideas?

Thanks in advance!

The DAHDI drivers are part of Asterisk, not FreePBX, just like trixbox and all the other distro’s.

You need to configure the card. The dahdi_genconf -F -vvvvv should get you very close but sometimes a little tweaking is needed.

I am sure that if you run a ‘dahdi show channels’ from Astrisk when the card is installed you don’t have a group of FXO’s to use for outbound defined.

Ok, I did the dahdi_genconf -F -vvvvv.

Then I ran the dahdi show channels and saw

1 from-internal en default In Service
2 from-internal en default In Service
3 from-internal en default In Service
4 from-internal en default In Service
5 from-internal en default In Service
6 from-internal en default In Service
7 from-internal en default In Service
8 from-internal en default In Service
9 from-internal en default In Service
10 from-internal en default In Service
11 from-internal en default In Service
12 from-internal en default In Service

… and I still did not get any outside lines. It told me that all circuits are busy.

I’m new (but hoping to involve myself enough to ask not-so n00b questions) so I appreciate any help here.

EDIT:

I ran the dahdi show channels from the working trixbox and found the above PLUS:

21 from-pstn en default In Service
22 from-pstn en default In Service
23 from-pstn en default In Service
24 from-pstn en default In Service

Hmmm. I have no idea how to configure this. Please help. :slight_smile:

As I said you are going to have to tweak the output of dahdi_genconf.

I guess my first question is have you read the Dahdi configuration guide? My guess is you don’t know how to use doxygen so I found this link for you:

http://docs.tzafrir.org.il/dahdi-tools/README.html

Forget the build/installation that has been done for you with the distro. Just read the configuration.

When following the files in /etc/asterisk realize the last include takes precedence.

If you are using group 0 as the object of your trunk you need to make sure that your FXO ports are in group 0.

This was an excellent post. Thanks.

I am able to dial out now; however, I cannot dial in. I get the standard woman’s voice saying “The number you are calling… is not in service”

Now, I think because I have the ability to call out, the system.conf is configured correctly.

Here it is, just in case but it matches my old trixbox.

Autogenerated by /usr/sbin/dahdi_genconf on Fri Jun 8 12:13:52 2012

If you edit this file and execute /usr/sbin/dahdi_genconf again,

your manual changes will be LOST.

Dahdi Configuration File

This file is parsed by the Dahdi Configurator, dahdi_cfg

Span 1: WCTDM/0 “Wildcard TDM2400P” (MASTER)

fxoks=1
echocanceller=mg2,1
fxoks=2
echocanceller=mg2,2
fxoks=3
echocanceller=mg2,3
fxoks=4
echocanceller=mg2,4
fxoks=5
echocanceller=mg2,5
fxoks=6
echocanceller=mg2,6
fxoks=7
echocanceller=mg2,7
fxoks=8
echocanceller=mg2,8
fxoks=9
echocanceller=mg2,9
fxoks=10
echocanceller=mg2,10
fxoks=11
echocanceller=mg2,11
fxoks=12
echocanceller=mg2,12

channel 13, WCTDM/0/12, no module.

channel 14, WCTDM/0/13, no module.

channel 15, WCTDM/0/14, no module.

channel 16, WCTDM/0/15, no module.

channel 17, WCTDM/0/16, no module.

channel 18, WCTDM/0/17, no module.

channel 19, WCTDM/0/18, no module.

channel 20, WCTDM/0/19, no module.

fxsks=21
echocanceller=mg2,21
fxsks=22
echocanceller=mg2,22
fxsks=23
echocanceller=mg2,23
fxsks=24
echocanceller=mg2,24

Global data

loadzone = us
defaultzone = us

You must have the channels in the wrong context. Must be in from-trunk

Thanks for the heads up but if we’re looking at the dahdi-channels.conf, the current usable box is working just fine with the context=from-pstn. The new box has the same:

; Span 1: WCTDM/0 “Wildcard TDM2400P” (MASTER)
; Skip channel=1(FXS) – freepbx option.
; Skip channel=2(FXS) – freepbx option.
; Skip channel=3(FXS) – freepbx option.
; Skip channel=4(FXS) – freepbx option.
; Skip channel=5(FXS) – freepbx option.
; Skip channel=6(FXS) – freepbx option.
; Skip channel=7(FXS) – freepbx option.
; Skip channel=8(FXS) – freepbx option.
; Skip channel=9(FXS) – freepbx option.
; Skip channel=10(FXS) – freepbx option.
; Skip channel=11(FXS) – freepbx option.
; Skip channel=12(FXS) – freepbx option.
;;; line="21 WCTDM/0/20 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 21
callerid=
group=
context=default

;;; line="22 WCTDM/0/21 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 22
callerid=
group=
context=default

;;; line="23 WCTDM/0/22 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 23
callerid=
group=
context=default

;;; line="24 WCTDM/0/23 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 24
callerid=
group=
context=default

from-pstn will work also, but if you are are getting that message they are in the wrong context.

From the Asterisk CLI do a ‘dahdi show channels’

Also post the log output of the failed call.

Ok,

‘dahdi show channels’

Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 from-internal en default In Service
2 from-internal en default In Service
3 from-internal en default In Service
4 from-internal en default In Service
5 from-internal en default In Service
8 from-internal en default In Service
9 from-internal en default In Service
10 from-internal en default In Service
11 from-internal en default In Service
12 from-internal en default In Service
21 from-pstn en default In Service
22 from-pstn en default In Service
23 from-pstn en default In Service
24 from-pstn en default In Service

LOG

sig_analog.c: – Starting simple switch on 'DAHDI/21-1’
pbx.c: – Executing [s@from-pstn:1] NoOp(“DAHDI/21-1”, “No DID or CID Match”) in new stack
pbx.c: – Executing [s@from-pstn:2] Answer(“DAHDI/21-1”, “”) in new stack
pbx.c: – Executing [s@from-pstn:3] Wait(“DAHDI/21-1”, “2”) in new stack
[2012-06-11 12:07:17pbx.c: – Executing [s@from-pstn:4] Playback(“DAHDI/21-1”, “ss-noservice”) in new stack
[2012-06-11 12:07:17file.c: – <DAHDI/21-1> Playing ‘ss-noservice.ulaw’ (language ‘en’)
pbx.c: – Executing [s@from-pstn:5] SayAlpha(“DAHDI/21-1”, “”) in new stack
pbx.c: – Executing [s@from-pstn:6] Hangup(“DAHDI/21-1”, “”) in new stack
pbx.c: == Spawn extension (from-pstn, s, 6) exited non-zero on 'DAHDI/21-1’
pbx.c: – Executing [h@from-pstn:1] Macro(“DAHDI/21-1”, “hangupcall,”) in new stack
pbx.c: – Executing [s@macro-hangupcall:1] GotoIf(“DAHDI/21-1”, “1?theend”) in new stack
pbx.c: – Goto (macro-hangupcall,s,3)
pbx.c: – Executing [s@macro-hangupcall:3] ExecIf(“DAHDI/21-1”, “0?Set(CDR(recordingfile)=)”) in new stack
pbx.c: – Executing [s@macro-hangupcall:4] Hangup(“DAHDI/21-1”, “”) in new stack
app_macro.c: == Spawn extension (macro-hangupcall, s, 4) exited non-zero on ‘DAHDI/21-1’ in macro 'hangupcall’
pbx.c: == Spawn extension (from-pstn, h, 1) exited non-zero on 'DAHDI/21-1’
sig_analog.c: – Hanging up on 'DAHDI/21-1’
chan_dahdi.c: – Hungup ‘DAHDI/21-1’

It says no DID, so I went in and saw my inbound route settings were missing. Hmmm. To be simple (or perhaps I am making things more complicated), I added an Incoming Route with everything going to my main ring group with no id. Perhaps that is it but I wont be able to test it until tomorrow or much later today. What do you think??

I think you are missing a route. In needs to have the DID and the CID blank.

Inbound Route settings were gone. Perhaps I forgot to save them. I added the incoming route with no DID or CID.

I came in early this morning just to try it out and it works!!!

Thank you very much! I look forward to my next problem. :slight_smile: