carrier using trunkinbound, should be ...?

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

carrier using trunkinbound, should be ...?

Postby THUFIR » Wed Apr 08, 2015 5:31 pm

I'm not quite understanding what this line:

Code: Select all
TESTSIPTRUNK = SIP/babytel_out


p 149 of the definitive asterisk guide refers to that as a variable, TESTSIPTRUNK, and that this variable makes it easier to change carriers by making just one change in the dialplan. This is a channel variable?

This global string doesn't show anywhere else in any config file I can find, which seems odd.

in extensions.conf, the trunkinbound context, which the outbound channel is unfortunately using, is defined as so:

Code: Select all
[trunkinbound]
; DID call routing process
; exten => _XXXXXXXXXX,1,AGI(agi-DID_route.agi)  ; use this one instead of the one below if you are having delay issues, and match to$
exten => _X.,1,AGI(agi-DID_route.agi)
exten => _X.,n,Hangup()
; If you have DIDs that arrive with a plus sign at the beginning then uncomment
;exten => _+X.,1,AGI(agi-DID_route.agi)
;exten => _+X.,n,Hangup()

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



exten => _9x.,1,Dial(SIP/${EXTEN:1}@babytel_out)



as shipped with vicidial by default.


babytel_out is using the wrong context:

Code: Select all
vici*CLI>
vici*CLI> sip show peer babytel_out


  * Name       : babytel_out
  Secret       : <Set>
  MD5Secret    : <Not set>
  Remote Secret: <Not set>
  Context      : trunkinbound



but, what should the context for babytel_out be set to? Clearly not trunkinbound. I tried adding a line in babytel_out through the web interface to explicitly set the context as vicidial-auto-external, but I still cannot dial out.


Dialing leads entered as 1xxxxxxxxxx results in invalid.gsm playing. Inputting the leads as 91xxxxxxxxxx results in demo-instruct.gsm playing.



What I don't understand is where the context should be defined?


(For whatever reason, the carrier suggests breaking the channel definition up into inbound and outbound, so I'm going with that for now.)
ViciBox Redux v.6.0.3-141118 from .iso | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | AMD Phenom(tm) II X6 1090T Processor | 8GiB RAM
THUFIR
 
Posts: 109
Joined: Fri May 02, 2014 10:46 pm

Re: carrier using trunkinbound, should be ...?

Postby bobchaos » Fri May 01, 2015 4:15 pm

the carriers you setup in the admin interface end up in /etc/asterisk/extensions-vicidial.conf, which is where you'll find the variable. That file is a #include in the default vicidial extensions.conf.

If I recall correctly, the default outbound dialing context is called "trunkoutbound" and is commented out in /etc/asterisk/extensions.conf. You need to copy that into your carrier's dialplan, edit accordingly (if needed, default should be fine for US i think, if you're in Canada like me there's a few adjustments to get optimal performance), activate the carrier and deactivate any conflicting carrier if any.

If you filled in all the parameters right for your account and copied the dialplan from extensions.conf to the Vicidial carrier admin interface you should be able to dial out.
bobchaos
 
Posts: 171
Joined: Fri Jan 06, 2012 12:46 pm


Return to Support

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 92 guests