SOLVED Moving from IncridiblePBX to XIVO - touble with analog (DAHDI) incoming calls

[alange]

Dear XIVO users,

I've been using FreePBX/IncrediblePBX with an analog card to connect to 2 pstn lines. I'm moving over to XIVO. This has been no trouble with SIP trunks but handles analog In FreePBX there is a web page to assign DIDs to the trunks and then routes are assigned in the same way as SIP trunks. I've followed the XIVO manual for setup but I'm at a point where I have good outgoing calls but incoming calls fail with "this s extension can only be used from a SIP channel".

Is there a step missing that I've not followed?

chan_dahdi.conf contains:

; Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-extern
channel => 1
;;; line="2 WCTDM/4/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-extern
channel => 2

In the web GUI I have a custom trunk:

Name: tg0
Interface: dahdi/g0
Interface Suffix:
Context: Incalls (from-extern)

In incoming calls (web GUI) I have: (this is where I'm beginning to doubt I've got it right)

DID: 301
Context: Incalls (from-extern)
Destination: User
Redirect to: Reception
Ring time: 20
Caller ID mode:
Preprocess subroutine:

In outgoing calls I have: (this works fine)

Name: totrunkfxo
Context: Outcalls (to-extern)
Use ENUM:
Internal:
Preprocess subroutine:
Ring time before hangup: Unlimited
Trunks: tg0 (dahdi/g0)

In my contexts I have:

Name: from-extern
Displayed name: Incalls
Entity: myentity
Context type: Incall
Include sub-contexts:
Users:
Groups:
Queues:
Conference Rooms:
Incoming calls: 300-399; 01000000000-09999999999

Can you tell me what step I missed? I've been using XIVO happily with sip trunks, it's just the DAHDI bit that I'm stuck on.
Thanks!

Note: a version of this question also posted in XIVO forum

 

[alange]

OK so I figured it out. I'd not got the custom bit of config required to get the call inwards. For reference here is what I added.

In the folder etc/asterisk/extensions_extra.d/ i created a file called dahdi_incoming_alan.conf with the following contents:

[from-dahdi-alan]
exten = _.,1,NoOp(This is going to send DAHDI g0 ch1 and 2 to 301 in from-extern)
same  = n,Set(DID=301)
same  = n,Goto(from-extern,${DID},1)

I then changed by chan_dahdi.conf to the following:

; Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) 
;;; line="1 WCTDM/4/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-dahdi-alan
channel => 1
callerid=

;;; line="2 WCTDM/4/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-dahdi-alan
channel => 2
callerid=

So calls are sent to my from-dahdi-alan context, issued a number, sent back to from-extern and now xivo is happy. IncrediblePBX/FreePBX handle this configuration from the GUI, XiVO leaves you to do it in config files for each custom trunk you wish to add. I can see the logic. XIVO don't want to write tons of code for bits of hardware you may/may not have. FreePBX must just have decided that enough people were using digium/openvox/zaptel cards that it was worth including at the time.