FreePBX, Digium B410p using DAHDI

Hi all,

FreePBX:
Feature Code Admin 2.7.0.0 FreePBX
FreePBX ARI Framework 2.7.0.1 FreePBX
FreePBX FOP Framework 2.7.0.0 FreePBX
FreePBX Framework 2.7.0.2 FreePBX
All modules are up to date.

Can anyone advise me on installing a B410p using DAHDI/DAHDI-Tools and configuring it in FreePBX. I’ve installed DAHDI/DAHDI-Tools and it picks up the B410p. I have two ISDN lines plugged into Port 1 and 2. These two ISDN lines are configured into a hunting group on the providers side.

I’m stumped by the Trunks, Outbound and Inbound routes. I have no idea what to put in these sections.

I’m in the server room now so if anyone can help soon it will be great :slight_smile:

I’m not sure if this analogous experience is directly related but…

When I plugged in some A400P FXO cards I needed to

  1. run the dahdi genconf (this created the trunks)
  2. review the generated file and edit as needed
  3. edit the dadhi channels conf file (to see all ports, by default only 2 of the 4 FXO are active)
  4. reboot

While I have no ISDN experience I would think the outbound and inbound configuration is exactly the same regardless of FXO/ISDN/T1/etc.

Thanks vegastech,

I’m giving it another go on the weekend. If i’m not mistaken this would be the procedure to install the B410p card on a fresh install:

dahdi_scan

dahdi_genconfig

dahdi_tool
See if the status is OK (and the lights are green at the back)

Edit amportal.conf and set ZAP2DAHDI mode = TRUE

Edit chan_dahdi.conf: #include chan_dahdi_additional.conf and #include dahdi-channels.conf

BELOW is where I get stuck:

In FreePX under trunks: “Add ZAP Device (DAHDI compatibility mode)”

Under Outgoing Routes: Add a new route, configure a dial plan and add the ZAP/g0

What to do under Inbound?

It’s the GUI config that’s confusing me :slight_smile:

Please help :slight_smile:

Is this forum still active?

I’m desperate to get this working. I have updated to 2.8 and still do not have a chan_dahdi.conf that everyone says I need to configure.

Has anyone setup a B410p card in freePBX? Can anyone post a tutorial on how they got it to work. I have done absolutely everything.

I cannot understand why no one has any input?

I’ll run through what I have done with 2.8.

It’s a FRESH install of FreePBX updated to 2.8.

All Bars are green in FreePBX admin page

No errors are being reported by FreePBX

dahdi_genconfig run

dahdi_tool Reports no alarms on 1 and 2. (3 and 4 are red [nothing plugged in])

I can post a dahdi_scan if anyone wants

Add a DAHDI Trunk (Now that dahdi comptatible has been removed as of update to 2.8)

Try to the best of my ability to configure outgoing.

All i’m getting is the voice message telling me to try again.

Why is documentation so outdated? If anyone can point me to a tutorial that doesn’t want me to edit chan_dahdi.conf or zapata.conf I’d be very grateful!

Hi,

I am having a similar problem using a TDM410 card, I have no idea how to configure the FreePBX GUI for incoming calls using FXO…

I get the following error in asterisk:

-- Starting simple switch on 'DAHDI/1-1'

== Starting DAHDI/1-1 at ,s,1 failed so falling back to exten ‘s’
== Starting DAHDI/1-1 at ,s,1 still failed so falling back to context ‘default’
– Executing [[email protected]:1] Playback(“DAHDI/1-1”, “vm-goodbye”) in new stack
– <DAHDI/1-1> Playing ‘vm-goodbye.ulaw’ (language ‘en’)
– Executing [[email protected]:2] Macro(“DAHDI/1-1”, “hangupcall”) in new stack
– Executing [[email protected]:1] GotoIf(“DAHDI/1-1”, “1?skiprg”) in new stack
– Goto (macro-hangupcall,s,4)
– Executing [[email protected]:4] GotoIf(“DAHDI/1-1”, “1?skipblkvm”) in new stack
– Goto (macro-hangupcall,s,7)
– Executing [[email protected]:7] GotoIf(“DAHDI/1-1”, “1?theend”) in new stack
– Goto (macro-hangupcall,s,9)
– Executing [[email protected]:9] Hangup(“DAHDI/1-1”, “”) in new stack
== Spawn extension (macro-hangupcall, s, 9) exited non-zero on ‘DAHDI/1-1’ in macro ‘hangupcall’
== Spawn extension (default, s, 2) exited non-zero on ‘DAHDI/1-1’
– Executing [[email protected]:1] Macro(“DAHDI/1-1”, “hangupcall,”) in new stack
– Executing [[email protected]:1] GotoIf(“DAHDI/1-1”, “1?skiprg”) in new stack
– Goto (macro-hangupcall,s,4)
– Executing [[email protected]:4] GotoIf(“DAHDI/1-1”, “1?skipblkvm”) in new stack
– Goto (macro-hangupcall,s,7)
– Executing [[email protected]:7] GotoIf(“DAHDI/1-1”, “1?theend”) in new stack
– Goto (macro-hangupcall,s,9)
– Executing [[email protected]:9] Hangup(“DAHDI/1-1”, “”) in new stack
== Spawn extension (macro-hangupcall, s, 9) exited non-zero on ‘DAHDI/1-1’ in macro ‘hangupcall’
== Spawn extension (default, h, 1) exited non-zero on ‘DAHDI/1-1’
– Hungup ‘DAHDI/1-1’

for me, it was saying the same thing. It happened after an automatic upgrade. In the Dahdi section, there’s a link Edit, and after you have your FXO ports. At the right, context, for me it was empty and the log was showing:

[2012-01-17 09:36:40] VERBOSE[10345] sig_analog.c: – Starting simple switch on ‘DAHDI/1-1’
[2012-01-17 09:36:41] DEBUG[10345] chan_dahdi.c: CallerID number: 5147023139, name: (null), flags=4
[2012-01-17 09:36:41] VERBOSE[10345] pbx.c: == Starting DAHDI/1-1 at ,s,1 failed so falling back to exten ‘s’
[2012-01-17 09:36:41] VERBOSE[10345] pbx.c: == Starting DAHDI/1-1 at ,s,1 still failed so falling back to context ‘default’
[2012-01-17 09:36:41] VERBOSE[10345] pbx.c: – Executing [[email protected]:1] Playback(“DAHDI/1-1”, “vm-goodbye”) in new stack
[2012-01-17 09:36:41] VERBOSE[10345] file.c: – <DAHDI/1-1> Playing ‘vm-goodbye.gsm’ (language ‘en’)
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:2] NoOp(“DAHDI/1-1”, “ERROR: FreePBX Does not use the [default] context, confguration error”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:3] Macro(“DAHDI/1-1”, “hangupcall”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:1] GotoIf(“DAHDI/1-1”, “1?theend”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Goto (macro-hangupcall,s,3)
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:3] Hangup(“DAHDI/1-1”, “”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] app_macro.c: == Spawn extension (macro-hangupcall, s, 3) exited non-zero on ‘DAHDI/1-1’ in macro ‘hangupcall’
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: == Spawn extension (default, s, 3) exited non-zero on ‘DAHDI/1-1’
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:1] Macro(“DAHDI/1-1”, “hangupcall,”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:1] GotoIf(“DAHDI/1-1”, “1?theend”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Goto (macro-hangupcall,s,3)
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: – Executing [[email protected]:3] Hangup(“DAHDI/1-1”, “”) in new stack
[2012-01-17 09:36:42] VERBOSE[10345] app_macro.c: == Spawn extension (macro-hangupcall, s, 3) exited non-zero on ‘DAHDI/1-1’ in macro ‘hangupcall’
[2012-01-17 09:36:42] VERBOSE[10345] pbx.c: == Spawn extension (default, h, 1) exited non-zero on ‘DAHDI/1-1’
[2012-01-17 09:36:42] VERBOSE[10345] sig_analog.c: – Hanging up on ‘DAHDI/1-1’
[2012-01-17 09:36:42] VERBOSE[10345] chan_dahdi.c: – Hungup ‘DAHDI/1-1’

I put from-zaptel into the context box and calls began to come in. I use Dahdi zaptel compatible…