Inbound routes:
------1939 Any Shop Ring Groups: 300 Shop
------5355 Any House Ring Groups: 100 House
------3334 Any FAX Extensions: 201 FAX
Outbound routes:
House ------5355
Shop ------1939
FAX ------3334
Logs in a separate post.
Inbound calls do nothing. No reaction or log by the PBX.
Here’s one log of an outbound call. It failed because I dialed an 11 digit number and the phone company was not happy. This was NOT an issue of dal pattern matching. The next number I dialed was a local 7 digit number, that went through as expected.
[2018-02-15 23:56:54] VERBOSE[15050][C-00000001] sig_analog.c: Starting simple switch on ‘DAHDI/12-1’
[2018-02-15 23:57:06] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:1] ResetCDR(“DAHDI/12-1”, “”) in new stack
[2018-02-15 23:57:06] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:2] NoCDR(“DAHDI/12-1”, “”) in new stack
[2018-02-15 23:57:06] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:3] Progress(“DAHDI/12-1”, “”) in new stack
[2018-02-15 23:57:06] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:4] Wait(“DAHDI/12-1”, “1”) in new stack
[2018-02-15 23:57:07] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:5] Playback(“DAHDI/12-1”, “silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer”) in new stack
[2018-02-15 23:57:07] VERBOSE[15050][C-00000001] file.c: <DAHDI/12-1> Playing ‘silence/1.ulaw’ (language ‘en’)
[2018-02-15 23:57:08] VERBOSE[15050][C-00000001] file.c: <DAHDI/12-1> Playing ‘cannot-complete-as-dialed.ulaw’ (language ‘en’)
[2018-02-15 23:57:11] VERBOSE[15050][C-00000001] file.c: <DAHDI/12-1> Playing ‘check-number-dial-again.ulaw’ (language ‘en’)
[2018-02-15 23:57:13] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:6] Wait(“DAHDI/12-1”, “1”) in new stack
[2018-02-15 23:57:14] VERBOSE[15050][C-00000001] pbx.c: Executing [12542101939@from-internal:7] Congestion(“DAHDI/12-1”, “20”) in new stack
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx.c: Spawn extension (from-internal, 12542101939, 7) exited non-zero on ‘DAHDI/12-1’
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx.c: Executing [h@from-internal:1] Macro(“DAHDI/12-1”, “hangupcall”) in new stack
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx.c: Executing [s@macro-hangupcall:1] GotoIf(“DAHDI/12-1”, “1?theend”) in new stack
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx.c: Executing [s@macro-hangupcall:3] ExecIf(“DAHDI/12-1”, “0?Set(CDR(recordingfile)=)”) in new stack
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx.c: Executing [s@macro-hangupcall:4] Hangup(“DAHDI/12-1”, “”) in new stack
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] app_macro.c: Spawn extension (macro-hangupcall, s, 4) exited non-zero on ‘DAHDI/12-1’ in macro ‘hangupcall’
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] pbx.c: Spawn extension (from-internal, h, 1) exited non-zero on ‘DAHDI/12-1’
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] sig_analog.c: Hanging up on ‘DAHDI/12-1’
[2018-02-15 23:57:17] VERBOSE[15050][C-00000001] chan_dahdi.c: Hungup ‘DAHDI/12-1’
But your log shows that FreePBX was unhappy (12542101939 did not match a pattern in any Outbound Route) – no trunk was ever selected. Each outbound route would usually require separate dial patterns for 7-, 10- and 11- digit dialing. If you are reasonably sure that the Route is correct, confirm that the Trunk doesn’t have any dial patterns set up (that could cause it to reject the call).
On incoming, does it fail with calls to both MJ and POTS? What does the caller hear? You might try connecting one line via a splitter to both the FXO board and a corded phone. Verify that the phone rings and can be answered when you call in (to confirm that the FXO board is not falsely tripping the ring or otherwise interfering with the signaling).
It is extremely strange that you don’t get anything at all on your asterisk log when receiving a call from a DAHDI card. Assuming the card and the DAHDI trunk are correctly configured, you should at least get a message like this when the PSTN line is ringing:
Starting simple switch on ‘DAHDI/x-x’
where x references the DAHDI channel.
If you are not even getting that, maybe your log level is not high enough, because if outgoing calls are working, I assume the card is correctly configured. Maybe the issue is on the inbound routes.
I believe your wikipedia article is referring to digital ,i,e, T1 PRI/e&m circuits or possibly analog DID e&m lines (now exceedingly rare) , DNIS is not pertinent to analog lines, but as each analog line carries one number, then the DID is intrinsic and you need to map that to the FXO it is carried to, if there is cfb or hunting then as I said, you can use the ‘pilot’ numbet for all.
I guess you missed the part where I said:
And the subsequent post:
Where I used “-” to mask the full number because I’d rather NOT publish my phone number here.
Both reflect changes I made in DAHDI Configure DID and Inbound Routes.
Is there something wrong that I did with this?
Set up a ‘catchall’ Inbound Route:
DID Number (leave blank, which means ANY)
CallerID Number (leave blank, which means ANY)
Set Destination: Extensions (choose a working extension)
Then, call into the system from your mobile and see whether the extension rings. Try both your magicJack line and one of your POTS numbers.
If this works, the CDR should show you why your normal routes aren’t working.
If the catchall route also fails, go into Settings -> Asterisk Logfile Settings and make sure that for ‘full’, Debug, Error, Verbose, Notice and Warning are all set to On. Then, try to call in again, go to Reports -> Asterisk Log Files and see whether anything gets logged for the attempt. If nothing, post your DAHDI configuration (masking any personal info).
I brought one of the telco lines over to the PBX today.
I called that number from my cell phone.
When it’s plugged into the FXO port for the FAX the FAX machine rang (none of the other extensions rang.) Although for some odd reason it hung up before the FAX machine had time to answer.
When it’s plugged into the FXO port for the house, All the phones on Ring Group 100 rang like they should.
For some odd reason, when I plugged it into the FXO port for the Shop, it returned a busy signal.
Previously, I’d been trying to get things working using a Magic Jack for the telco line.
I can dial out but goes immediate to MJ voice mail when plugged into an FXO port.
Obviously this is a problem. If your answer is to tell me what a Turd Magic Jack is, don’t bother.
Part of the problem here is it’s what I have to make work.
Fax machines generally only answer fax calls, if your fax machine has a “pass through port” to an FXS extension, then plug a phone into it. If you are connecting to a dahdi fxo, then it will answer if properly configured. and you will see logs in /var/log/asterisk/full
From bash
dahdi_cfg -vv
dahdi_tool
dahdi_hardware
. . . .
But you miss the point
------1939 should be physically attached to the FXO with the pseudoDID of ------1939
similarly
------5355 should be physically attached to the FXO with the pseudoDID of ------5355
and
------3334 should be physically attached to the FXO with the pseudoDID of ------3334
1939
if you don’t do that exactly, you will confuse yourself as is currently apparent, but from that point, then inbound routes will work as expected.
As to your MJ, then depending on your DAHDI hardware, then it might not provide an acceptable ring voltage (90v AC 30HZ expected) less than 30 and it likely wont be recognized as a legitimate FXO 
Calling the FAX machine from extension 112 to 201, it rings 6 times, then picks up and sends the FAX tones.
Calling the FAX machine from “outside” via the FXO port designated as the FAX line, it rang three times and the PBX hung up the call.
Which point did I miss?
And what exactly do you assume I’m confused about?
While setting up the PBX, I have ONE telco line to play with.
So I can plug it into one of three FXO ports.
I have the DAHDI Configure DID set for each of the three FXO ports to the full 10 digit phone number associated with the line that connects to each of the three FXO ports.
Channel 1 goes to Ring Group 100 like it should and the calls goes through.
Channel 2 goes to Extension 201 but hangs up after three rings of the FAX machine.
Channel 3, for some reason presents a busy signal to the telco line.
And thank you, that is at least a helpful bit of information.
The Magic Jack does work with a X100M module on a TDM400 card.
Apparently it is NOT working for incoming calls with the X400M module with the TDM2400 card.
If need be, then I’ll add a TDM400 and a X100M as a work around.
" . . . .While setting up the PBX, I have ONE telco line to play with. . ."
So why are you trying to set up three?
It may have something to do with I’d like to get the PBX working before I pay for a second phone line. That and I’d prefer to use the Magic Jack for the third line. It DOES work with the TDM400 card and an X100M FXO module.
So please start over, get the one line working, stop being too clever and worry about MJ later, the Wiki had it all for you, just reread and absorb it. If you have one line, you have one DID, that’s all .
NO.
Forget that I said anything about Magic Jack.
I have a requirement for THREE lines, so I will continue to move the one telco line I have from one FXO port to the other to test each inbound and outbound route situation I need.
Each FXO port has an individual line DID assigned to it.
Currently:
Port 1 Incoming calls go the the assigned Ring Group. Outbound calls from that Ring Group go to that port and work properly.
Port 2 incoming calls go to the Extension with the FAX machine, but the PBX hangs up before the FAX machine can answer. Outgoing calls from that extension go the the correct port and work properly
Port 3 incoming calls get a busy a busy signal. Outgoing calls get a busy signal.
Given that some log info is apparently missing, I suggest that you debug this in a systematic fashion.
First, check your DAHDI config and confirm that all four FXO ports are configured equivalently (with different DID numbers but the same options for all). Then, temporarily remove your ‘normal’ inbound routes and put in a catchall that routes to a single working extension. Connect your POTS line to each port in turn and test from your mobile. If the call rings the test extension properly and you have audio both ways upon answer, test that port with the magicJack as well.
At this point, if one or more ports are failing, you probably have a hardware issue. Possibly, it’s something you can fix, e.g. a bent pin or the X400M not making good contact with the TDM2400P. Otherwise, if just one port is bad, your requirements should be satisfied by the other three.
Once that’s complete, reinstall your normal routes (using ports that passed the test above). If incoming calls on your fax line are dedicated to fax, set the fax machine to auto-answer ‘immediately’ (this probably means at the beginning of the second ring, so it can read the caller ID). If calls to the fax line are also used for other purposes, please describe the desired behavior. From a working extension, dial the fax machine’s extension number (not using a trunk) and confirm that it answers and you hear the high pitched ANS tone within 10 seconds. Then, plug your POTS line into the FXO port that routes to fax and test. If for some reason the fax machine’s answer must be delayed, set Ring Time (in the Advanced settings) for the fax extension to 30 or more (the system default is only 15 seconds, probably not enough).
If you still have trouble, report results of the above tests in detail.
I got it working, thank you everyone.
Jeff