carrier using trunkinbound, should be ...?
Posted: Wed Apr 08, 2015 5:31 pm
I'm not quite understanding what this line:
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:
as shipped with vicidial by default.
babytel_out is using the wrong context:
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.)
- 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.)