Topic: How to configure Dahdi on SME8 Sark

[jufra]

HI all,

I'm using SME8 bundled with Sark from the http://sailpbx.com/iso/SME8b6 site. Installed a Digium TDM400P card which is recognised ok (after fixing the broken Dahdi kernel, which is described in another thread in this forum).
Went through all of that and now in the GUI I see a Dahdi trunkline appearing, called DAHDIGroup0. I suppose this is a good sign, as there's only one external line plugged into the card (which has 4 FXO ports)
As the server was a new install, I put in a route which pointed to the Dahdi group and then defined an extension and was able to make and receive calls through the card.
Now that I have defined all the other trunks (SIP), I am wondering how to integrate the Dahdi card into the picture.
What I noticed is that the Dahdi trunkline doesn't allow for the "Open" and "Closed" Inbound routes to be allocated as for instance a SIP trunk does.
So the question is how do I route a Dahdi incoming call to a certain destination, let's say a call group? For SIP trunks this seems easy enough by just setting the "Open/Closed" inbound routes, but what to do here with Dahdi?

Do I need to do this manually in the configuration files or does the GUI allow for this? Sorry if there is an obvious answer to this, but so far I never mucked around with the conf files, rather did all through the GUI (I've never used Asterisk in another context as Sail/Sark)

Thanks a lot
Cheers
Frank

[SARK devs]

Hi Frank

Routing fxo channels is covered in the pdf manual on page 20.  The manual can be downloaded here

http://www.sailpbx.com/pdfmanuals/sark_manual_3.1.0-125.pdf


It's a little out of date being -125 but it covers the fxo stuff with a few screen shots. 

Come back if it doesn't work for you.

Best

S

[jufra]

Thanks heaps for this link, I didn't know this document existed.
Anyhow, it doesn't really cover our case (or maybe I'm missing something, which is not unlikely  )
I have run all dahdi configuration, and at the end of the day, in the trunklines panels there is the following trunk which appears automatically:
DAHDIGroup0       group       LOCAL    N/A          N/A    [Device definition is active]    [Click to Edit]    [Click  to Delete]
Both fields "OPEN" and "CLOSED" are NOT set, when the line rings, all extensions ring as is explained in the manual you sent!

When I edit this trunk,  I get 2 tabs, "routing" and "line"
Under routing I find:
Active?
Tenant
Fax detect
Line Pre-select
Switch on CLIP
Transformation mask
Trunkname

Under "Line":
Alpha TagA
Add CLI Prefix
MOH instead of Ringtone
DISA Password
Caller ID
Dial String Lead-in (SET to "DAHDI/g0)
Dial String Lead-out
Call Progress?

So there is no option to set the trunk to "routable" or instruct it where to route the incoming calls....
This is where I'm getting stuck...

Is there anything I need to do with this DAHDI/go under Dial String Lead-In?? Do I need to create another trunk that makes use of this? It read in the manual about this PIKA thing for fxo

Any pointers?

Thanks again
Frank

[SARK devs]

Hi Frank

It does cover your case, look at the last paragraph on the page "Adding Trunks"....

To route individual FXO channels you can set up custom trunks and name them as
follows:-
• for FXO, use fxo{n}; where {n} is the port number on the tdm card

It then goes on to show 2 screen shots of one of these trunks being added.   

Maybe, a word of further explanation will help;  the DAHDIGroup0 object you refer to is not strictly a trunk in SARK, it is actually an outbound hunt group for the DAHDI channels i.e. it is an outbound only object, - and that is why you are unable to choose OPEN/CLOSED routing for it.

In its default state, SARK (3.1.0-125 or higher) will automatically route inbound analogue calls to the end-point you have declared as the Operator in globals. This can be a single extension or a callgroup. By default it is set to the callgroup RINGALL, which contains every extension on the system. For most users this is enough and it is easy to set up.  However, if you wish to do inbound OPEN/CLOSED type routing on analogue (FXO) lines then you must set up a trunk for each line you wish to route.  The manual shows you how to do this in the section I referenced above.

Hope this helps.   

S

[jufra]

Hi mate,

thanks for this, yes, great!! It worked. Hadn't thought of setting the operator extension to another extension than RINGALL... all good now.
However, I could not get the individual FXO routing to work, however, it is not really needed, it works as it is now.

The final aim with this DAHDI line is to receive faxes. I noticed there is a "fax detect" setting in the DAHDI hunt group (thanks BTW for clarifying that!), how is that used?
I guess I need some other plugin to receive faxes on Asterisk? We used to have Hylafax working, but I understand it doesn't work on SME8.
Can you give me a general direction here?

Thanks again for all your valuable help
Cheers
Frank