Inbound DID PRI configuration

[mjmillr2]

Configuring Inbound DID on a PRI with GoAutoDial, and I just want to verify that what I did is correct.

I went to the "Add a New DID" screen and sent DID extension 6136 to my vicidial phone. When I called the number from my wireless, I got a number not in service error (from the phone company I think) and saw the following in my Asterisk CLI log.

Code: Select all

Extension '6136' in context 'from-internal' from 'XXXXXXXXX' does not exist.  Rejecting call on channel 0/1, span 1

In my chan_dahdi.config is the following:

Code: Select all

;Sangoma A101 port 1 [slot:1 bus:7 span:1] <wanpipe1>
switchtype=national
context=from-internal
group=1
echocancel=yes
faxdetect=incoming
signalling=pri_cpe
channel =>1-23

In my Extensions.conf is the following:

Code: Select all

[trunkinbound]
; DID call routing process
exten => _X.,1,AGI(agi-DID_route.agi)

; FastAGI for VICIDIAL/astGUIclient call logging
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})

In extensions.conf I replaced [trunkinbound] with [from-internal] and now the calls work. I just want to verify that this is correct. I'm still new to Asterisk/Vicidial and I'm worried that that the [trunkinbound] context is needed elsewhere. I could change the extension in the dahdi config, but that file is auto-generated so I'm afraid if I make a change it will just get overwritten later.

If anyone knows the correct way to configure this, or if you can verify that what I did is OK, that would be great.

Thanks,
-Mike


GoAutodial CE 2.0 ISO | Asterisk 1.4.27.1-1 | Vicidial 2.2.1-260 BUILD: 100527-2211 | Sangoma A101D Card | Single Server | No extra Software

[williamconley]

you kinda did it a little backwards, but not wrong.

ordinarily we would recommend changing the context to trunkinbound so it would just "land" in the default setup. then when you "upgrade" or "update" the extensions.conf file can be overwritten by a new one (which may have necessary modifications in it for other functions) instead of having to "hope" your old extensions.conf works OR having to re-change this if you allow extensions.conf to be overwritten during update.

But: You did troubleshoot it well and fixed it correctly. Just not the way *I* would recommend (I won't presume to speak for The Vicidial Group ... but I'd guess they agree with me since I try to use everything they make STOCK when possible)

PS: Kudos also for posting your entire setup specs!

[mjmillr2]

Thanks for the quick response.

My first instinct was to do as you suggested, but I wasn't sure if/when we add another PRI card and redo the dahdi configuration if it would overwrite my changes there. The dahdi config file has an "autogenerated/do not manually edit" note.

[williamconley]

you could create a script to run the config ... and have your script activate the config generator and then have that same script reach in and change the from-trunk to trunkinbound after it runs

then you run your script instead of the config generator and it'll always be right!