Skip to main content

Outbound calls cannot be transferred; need help with the config changes

Posted by ottcomputing on Mon, 12/12/2016

Hi,

As titled, I need some help locating the config changes that I need to make to enable transferring on outbound calls. Some research on the Asterisk reveals that I need to append ",,T" to some dialstrings, presumably in the extensions.conf but I'm not 100% sure, can anyone illuminate me?


Submitted by ottcomputing on Thu, 12/15/2016 Permalink

Bump, if anyone can point me towards the functions in the .conf that pertain to this, I am not sure if I should be looking in the extensions.conf or features.conf file

I have looked through the function list (http://www.voip-info.org/wiki/view/Asterisk+functions 'here'), but nothing jumps out to me

I've also read through the asterisk kb article on the extensions.conf file (http://www.voip-info.org/wiki/view/Asterisk+config+extensions.conf 'here')

I realize this may be an elementary question, I am not asking for step-by-step instructions on the procedure just some info as to whether I'm on the right track or not and if not, for someone to point me in the right direction

Submitted by ottcomputing on Thu, 12/22/2016 Permalink

Right now they are unable to transfer Outbound calls to another extension in their trunk. Incoming calls can be transferred fine, but trying to transfer an outbound call results in the caller being put in some limbo wherein they can hear my client but my client can't hear the caller. From what I've read, it's a common issue in asterisk-based phone systems, and the solution is to append the Ttr switch to the end of outbound dialstring functions, but I'm not sure how that is done in thirdlane.

Basically, I need to know: what is the ThirdLane equivalent of editing dial string functions in Asterisk. In FreePBX that meant diving into the extensions.conf file and making a few changes in the [macro-dialout-trunk] portion, but the thirdlane system has the extensions.conf file configured a little differently, I looked through the extensions.include file that is linked in the .conf file but wasn't able to find it.

Hope that clears it up

Submitted by eugene.voityuk on Thu, 12/22/2016 Permalink

You don't need to edit files for that purpose. You can specify "Dial command options" in Outbound Route configuration in case you are using default Thirdlane scripts to dial out.

Submitted by ottcomputing on Fri, 12/23/2016 Permalink

Thanks for your help guys, I figured there was something in the Thirdlane UI I was missing, but couldn't find it in the admin guide

What's the syntax for dial command options? Everything I've found says that the switch to append is tT, but adding that to the dial command options on it's own doesn't seem to change anything. Should I be adding a semicolon or something at the end? I found one article saying to use the format ",,tT", I did try that and had no success. Am I missing something?

Submitted by ottcomputing on Fri, 12/23/2016 Permalink

I've also tried creating a clone of the script with the only change being addinf ,Tt to the end of the following call of the exten function:
exten => s,n(dial),Macro(tl-dialout-base,${ARG1},${ARG2},${ARG3},${ARG4},${ARG5})

so now it reads exten => s,n(dial),Macro(tl-dialout-base,${ARG1},${ARG2},${ARG3},${ARG4},${ARG5}, Tt) and they are still unable to transfer outbound calls.

Am I woefully misunderstanding everything I've read so far? Seems to me this should be working.

Submitted by eeman on Mon, 01/23/2017 Permalink

do you mean pick up phone, dial a number... talk to them, and then transfer them to another extension?

Tt has nothing to do with that. Tt means to allow DTMF based transfers (as defined in features.conf) to transfer a call. Thats generally a terrible idea on a trunk line because a caller could call in and use the DTMF code to re-route a call back out on your dime.