Asterisk settings for Tello Zero Cost Routing Service

Tello Corporation offers a service that enables free internet calls from Asterisk PBXs to other registered PBXs. This service is offered at no charge to the Asterisk community.

To register for the service and activate Zero Cost Routing (TM), just follow these instructions:

; Tello Asterisk Example Configurations - SIP Lookup Code
;
; v1.10 2006-06-28 
; John Todd <jtodd@tello.com>
;
; (c) 2005-2006 Tello Corporation
; San Mateo, CA
; http://www.tello.com/
;
;
; This file is part of a large descriptive document which provides
;  additional information on configuration and concepts.  Note that
;  the lines included below cannot simply be cut-and-pasted into
;  your configuration file; you will need to (at least) take the
;  values in the [globals] section out and place them in your
;  existing [globals] context, and you will need to know where in
;  your dialplan you should insert the Tello SIP test dialing 
;  lines.
;
;
; - start -
;
; First, you will need to sign up for a Tello account, which 
;  gives you a username and password.  This username and password
;  then will allow you to do two things: 1) it will allow you to
;  register your numbers in the Tello database so that others
;  may use the Tello system to route calls to you, and 2) it will
;  allow you to look up answers in the Tello database so that
;  you may route calls to others based on their preferences
;  and statuses.
; To sign up, visit [https://connect.tello.com/pbxreg]
;
; To begin, we need to add the definition of the Tello SIP 
;  server and your specific information.  For the purposes of
;  this example, the username (also known as "enterprise ID") is
;  set to 9988, and the password for this enterprise is "bhe9zoqd"
; We create two entries: a "peer" which is where this system will
;  send it's outbound calls, and a "user" which will accept inbound
;  calls from Tello (which in turn are from other enterprises.) We
;  separate the two so we can have some redundancy and load-sharing
;  abilities.
;
;  So, we'd put the following information into sip.conf as a new
;   SIP peer entry (minimalist config example):
;
; (If you have selected "IP Authentication" in the Tello
;   registration interface, you can remove the "username=",
;   "fromuser=", and "secret=" lines as they are not needed.)
;
;  [tello-peer]
;  type=peer
;  secret=bhe9zoqd
;  fromuser=9988
;  username=9988
;  insecure=invite
;  insecure=port
;  host=zcr.tello.com
;  context=from-tello
;  canreinvite=yes
;  disallow=none
;  allow=all
;
; That's all that needs to be added.  This will take inbound calls
;  from the Tello system and send them to context "from-tello" as 
;  well as serve as a named SIP peer for outbound calls.
;
; Depending on your local site requirements, you may wish to 
;   remove the "canreinvite=no" parameter, but we suggest it
;   remains at least during testing.
;
; Remember that your Asterisk server _must_ have a public, non-NAT
;   IP address for Tello service to function correctly!
; 
;
; The modifications to "extensions.conf" follow below.
;
;
;
[globals]
;
; The [globals] area is where global variables are kept.  This
;  is simply an easy place at the top of your configuration file
;  where you can set values for the lookup methods that the
;  system will use, so that you can easily activate/deactivate
;  each lookup loop without changing any configuration file
;  lines further down below.
;
; In order to make these changes effective, you should edit
;  this file, and then type the following in a root shell window:
;
;    asterisk -rx "extensions reload"
;
; OR you can just restart asterisk in the normal way that you
;  would stop/start that process from your system.
;
; If you already have a [globals] context defined, just add these
;  variables to the list. 
;
; Do we perform Tello SIP lookups on numbers?
;
USE-TELLO=YES
;
;
; What context do we hand off calls to for "normal" dialing?  This
;  context should be where we hand off calls that fail the Tello
;  SIP lookups, or where we redirect calls if we have neither
;  the USE-TELLO value is set to something other than "YES". The number
;  passed to this context will be "as-dialed", meaning that any
;  prefix or local dialing stuff will be handed to that context.
;
TELLO-DEFAULTCONTEXT=normal-dial
;
;
; This is the area code in which this PBX "lives".  This is used
;  by the dialing tests in the cases where this routine might be
;  presented with a seven-digit North American number; this
;  Area Code is added on to the front of the number.  It is only
;  a precautionary configuration value.
;
TELLO-AREACODE=650
;
;
; end of Tello variables
;
;
;
; The rest of your dialplan can go in here.  The location of these
;  contexts in your extensions.conf file is kind of irrelevant; they
;  can appear at the start or end, though it makes sense to keep them
;  close to the main dialing routines for your platform.
;
[tello-test]
; 
;
; It is assumed that calls are passed to the tello-test context 
;  after the call has passed through your 'local' contexts, meaning
;  that you probably should be checking to see if the call is one
;  of your local extensions, a voicemail access number, or is
;  prefaced by "9" for a "forced" outside line, if you have that type
;  of dialplan.
;
; First, let's make sure we should do anything at all:
;
exten => _X.,2,GotoIf($[${USE-TELLO} = YES]?3:10)
;
; Well, USE-TELLO was set to "YES", so we'll jump to the next 
;  step of the Tello process.  But first, we set a string to 
;  the "original" dialed number because we'll be modifying 
;  $EXTEN through this process, and we may need to jump out 
;  of these routines and hand the originally dialed number 
;  back to some context outside these lines, and we will need
;  to reference that originally dialed number.
;
exten => _X.,3,SetVar(TELLO-ORIGEXTEN=${EXTEN})
exten => _X.,4,Goto(tello-test2,${EXTEN},1)
;
; Priority 10 means that USE-TELLO was not set to "YES" so we
;  will jump back out to the normal dialing context and
;  extension.  This is the end of any Tello dialing methods.
; 
exten => _X.,10,Goto(${TELLO-DEFAULTCONTEXT},${EXTEN},1)
;
;
; Include the "standard" exit handlers here.  You may wish to
;  replace these here and in the rest of this example with your
;  own values if you have them set differently.
;
exten => h,1,Hangup
exten => i,1,Hangup
exten => t,1,Hangup
exten => T,1,Hangup
;
;
;
;
[tello-test2]
;
; So, we now start to normalize the number.  This is somewhat
;  confusing, since we use the "include" statements to force
;  an ordered examination of the number strings.  To create
;  some sanity, the context numbering will have a majorname.minornum
;  format to make it so that wildcards don't step on each other.
;
; This set of the dialplan is "just-in-case" a non-E.164 format
;  number gets passed in here.  Things like leading "011" and
;  the like should be deleted, and any numbers less than seven 
;  digits should be bounced out to the normal dialing plan, and
;  any numbers that are exactly seven digits probably need an
;  area code (North American) and a leading "1" added to them.
;
; Note that we have no way of protecting against a leading "9"
;  digit, as some PBXes use to indicate an outbound trunk dial.
;  This is because "9" is a valid leading digit as an area code
;  or country code digit, so we have no way of testing if it is
;  "valid" or "invalid" in a number.  Please consult Tello engineers
;  if this presents a problem; there are easy (but custom) solutions
;  that can quickly be implemented as a part of this dialplan but
;  do not warrant inclusion as they are somewhat confusing.
;
; This context essentially loops until all instances of the prefix
;  searched for are removed from the dialstring.  The default
;  case is to strip off "011" and then jump to tello-test3.
;
include => tello-test2.1
include => tello-test2.2
include => tello-test2.3
include => tello-test2.4
;
; Include the "standard" exit handlers here.
;
exten => h,1,Hangup
exten => i,1,Hangup
exten => t,1,Hangup
exten => T,1,Hangup
;
[tello-test2.1]
; 
; In North America, the sequence "011" prefixes any international
;  call.  So, to dial a number in the UK (44) we would dial
;  0114480033330000 as an example.  We need to strip the first
;  three digits off the number to get the E.164 number, which
;  just starts with the country code and everything after it.
;  Just run this context over again, with the new extension after
;  stripping off the first three digits.
;
; Hopefully, anyone in other nations will never have a number 
;  starting with "011" that is dialed.  If you do, just comment
;  out this line and it should do no harm.
;
; !!NON-NORTH AMERICAN USERS READ THIS!!
;
; If you are in a nation that uses some other three-digit prefix
;  to dial internationally, please replace "011" below with that
;  three digit prefix and it will be stripped off and correctly
;  handled.  If you only use two digits (i.e.: 00) then change
;  the ${EXTEN:0:3} to be ${EXTEN:0:2}
;
exten => _011XXXXXX.,1,Goto(${EXTEN:0:3},1)
;
[tello-test2.2]
;
; Test for seven-digit only and add area code and leading "1"
;
exten => _XXXXXXX,1,Goto(1${TELLO-AREACODE}${EXTEN},1)
;
[tello-test2.3]
;
; Test for less than seven digits, and if so, dump
;  out to normal parsing.  This would be the end of any Tello
;  dialplan use.  This allows mistaken 411, 911, etc. and 0 and
;  other types of calls to avoid being tested against the Tello database.
;
exten => _XXXXXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XXXXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XXXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _X,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
;
[tello-test2.4]
; 
; All numbers that don't match any of the other included contexts,
;  or which have been re-written and looped back into the included
;  context list will match against this extension, and so will just
;  jump to the next context in our examination chain. 
;
exten => _X.,1,Goto(tello-test3,${EXTEN},1)
;
;
;
[tello-test3]
;
; So here is the actual test against the Tello database, via a SIP INVITE.
;  The number has been "normalized" into what hopefully is an E.164 compatible
;  number, and now we place the call to the SIP peer of Tello's proxy.
; If the call is successful, then the dial will create a call to the remote 
;  SIP peer via Tello's SIP proxy.  The two parties will talk, and the 
; See below for failure cases and results.  If you are a particularly
;  sophisticated Asterisk user, you will recognize this as the heart of
;  the dialplan.  Based on this Dial statement, we either complete the 
;  call to a remote Tello system user, or we fail and fall back to another
;  method to try to complete the call.
;
exten => _X.,1,Dial(SIP/${EXTEN}@tello-peer) 
;
; So, our dial has either failed miserably, has rung "busy" (+101), or
;  has timed out (+51).  No matter - all failures go to the backup method.  This
;  is not optimal, since "busy" should lead to a call fail, but there are
;  too many 'dumb' softswitches out there which reply with 'busy' when they
;  should reply with some other failure method, so it is unsafe to assume
;  that a busy means that the call cannnot be completed via PSTN.  Therefore,
;  we send all paths to the secondary dialing method, which is specified
;  elsewhere in the dialplan by the administrator (not included in this 
;  file, as this is outside the scope of the intended example.)
;
; This code will work with =>1.2 (with no +101 or +53 jumping) or with older
;  versions of Asterisk as well which do priority jumping as a result of
;  Dial failures.
; 
; This is the end of the Tello-specific call routing and directory lookup.
;
exten => dial,3,Goto(103)
exten => dial,53,Goto(103)
exten => dial,103,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
;
;
; Include the normal inclusions for invalid, hangup, and timeouts.
;
exten => h,1,Hangup
exten => i,1,Hangup
exten => t,1,Hangup
exten => T,1,Hangup
;
;
;
[from-tello]
; 
; The "from-tello" context is where inbound calls come from Tello.  We pass
;  calls to this context from the "tello-peer" SIP stanza in sip.conf
;  These calls will be the number of digits you specify (which can be managed 
;  on the Tello webpage) and need to go elsewhere into your dialplan so that
;  the appropriate phone might ring.  This is very dependent on your dialplan
;  so this is just a "Goto" to the hypothetical context called "internal"
;  which is where you have your primary extensions listed, using a five digit
;  dialing sequence.  We'll assume this is an 11-digit number (North American
;  E.164) from Tello, and that you only need the last five digits, so cut
;  off the first six digits and re-direct.  All other numbers get sent to 
;  a congestion tone, since we don't know what to do with them.  If you
;  change the number of digits you receive by telling Tello to send you
;  fewer digits, make sure to modify this context appropriately.
;
;  ** YOU NEED TO MODIFY THE LINES BELOW TO SEND INBOUND CALLS FROM ***
;       ** TELLO USERS TO THE RIGHT PLACE IN YOUR DIALPLAN. ***
;
exten => _1XXXXXXXXXX,1,Goto(internal,${EXTEN:6}
exten => i,1,Congestion
exten => h,1,Hangup
;
;end






Tello Corporation offers a service that enables free internet calls from Asterisk PBXs to other registered PBXs. This service is offered at no charge to the Asterisk community.

To register for the service and activate Zero Cost Routing (TM), just follow these instructions:

; Tello Asterisk Example Configurations - SIP Lookup Code
;
; v1.10 2006-06-28 
; John Todd <jtodd@tello.com>
;
; (c) 2005-2006 Tello Corporation
; San Mateo, CA
; http://www.tello.com/
;
;
; This file is part of a large descriptive document which provides
;  additional information on configuration and concepts.  Note that
;  the lines included below cannot simply be cut-and-pasted into
;  your configuration file; you will need to (at least) take the
;  values in the [globals] section out and place them in your
;  existing [globals] context, and you will need to know where in
;  your dialplan you should insert the Tello SIP test dialing 
;  lines.
;
;
; - start -
;
; First, you will need to sign up for a Tello account, which 
;  gives you a username and password.  This username and password
;  then will allow you to do two things: 1) it will allow you to
;  register your numbers in the Tello database so that others
;  may use the Tello system to route calls to you, and 2) it will
;  allow you to look up answers in the Tello database so that
;  you may route calls to others based on their preferences
;  and statuses.
; To sign up, visit [https://connect.tello.com/pbxreg]
;
; To begin, we need to add the definition of the Tello SIP 
;  server and your specific information.  For the purposes of
;  this example, the username (also known as "enterprise ID") is
;  set to 9988, and the password for this enterprise is "bhe9zoqd"
; We create two entries: a "peer" which is where this system will
;  send it's outbound calls, and a "user" which will accept inbound
;  calls from Tello (which in turn are from other enterprises.) We
;  separate the two so we can have some redundancy and load-sharing
;  abilities.
;
;  So, we'd put the following information into sip.conf as a new
;   SIP peer entry (minimalist config example):
;
; (If you have selected "IP Authentication" in the Tello
;   registration interface, you can remove the "username=",
;   "fromuser=", and "secret=" lines as they are not needed.)
;
;  [tello-peer]
;  type=peer
;  secret=bhe9zoqd
;  fromuser=9988
;  username=9988
;  insecure=invite
;  insecure=port
;  host=zcr.tello.com
;  context=from-tello
;  canreinvite=yes
;  disallow=none
;  allow=all
;
; That's all that needs to be added.  This will take inbound calls
;  from the Tello system and send them to context "from-tello" as 
;  well as serve as a named SIP peer for outbound calls.
;
; Depending on your local site requirements, you may wish to 
;   remove the "canreinvite=no" parameter, but we suggest it
;   remains at least during testing.
;
; Remember that your Asterisk server _must_ have a public, non-NAT
;   IP address for Tello service to function correctly!
; 
;
; The modifications to "extensions.conf" follow below.
;
;
;
[globals]
;
; The [globals] area is where global variables are kept.  This
;  is simply an easy place at the top of your configuration file
;  where you can set values for the lookup methods that the
;  system will use, so that you can easily activate/deactivate
;  each lookup loop without changing any configuration file
;  lines further down below.
;
; In order to make these changes effective, you should edit
;  this file, and then type the following in a root shell window:
;
;    asterisk -rx "extensions reload"
;
; OR you can just restart asterisk in the normal way that you
;  would stop/start that process from your system.
;
; If you already have a [globals] context defined, just add these
;  variables to the list. 
;
; Do we perform Tello SIP lookups on numbers?
;
USE-TELLO=YES
;
;
; What context do we hand off calls to for "normal" dialing?  This
;  context should be where we hand off calls that fail the Tello
;  SIP lookups, or where we redirect calls if we have neither
;  the USE-TELLO value is set to something other than "YES". The number
;  passed to this context will be "as-dialed", meaning that any
;  prefix or local dialing stuff will be handed to that context.
;
TELLO-DEFAULTCONTEXT=normal-dial
;
;
; This is the area code in which this PBX "lives".  This is used
;  by the dialing tests in the cases where this routine might be
;  presented with a seven-digit North American number; this
;  Area Code is added on to the front of the number.  It is only
;  a precautionary configuration value.
;
TELLO-AREACODE=650
;
;
; end of Tello variables
;
;
;
; The rest of your dialplan can go in here.  The location of these
;  contexts in your extensions.conf file is kind of irrelevant; they
;  can appear at the start or end, though it makes sense to keep them
;  close to the main dialing routines for your platform.
;
[tello-test]
; 
;
; It is assumed that calls are passed to the tello-test context 
;  after the call has passed through your 'local' contexts, meaning
;  that you probably should be checking to see if the call is one
;  of your local extensions, a voicemail access number, or is
;  prefaced by "9" for a "forced" outside line, if you have that type
;  of dialplan.
;
; First, let's make sure we should do anything at all:
;
exten => _X.,2,GotoIf($[${USE-TELLO} = YES]?3:10)
;
; Well, USE-TELLO was set to "YES", so we'll jump to the next 
;  step of the Tello process.  But first, we set a string to 
;  the "original" dialed number because we'll be modifying 
;  $EXTEN through this process, and we may need to jump out 
;  of these routines and hand the originally dialed number 
;  back to some context outside these lines, and we will need
;  to reference that originally dialed number.
;
exten => _X.,3,SetVar(TELLO-ORIGEXTEN=${EXTEN})
exten => _X.,4,Goto(tello-test2,${EXTEN},1)
;
; Priority 10 means that USE-TELLO was not set to "YES" so we
;  will jump back out to the normal dialing context and
;  extension.  This is the end of any Tello dialing methods.
; 
exten => _X.,10,Goto(${TELLO-DEFAULTCONTEXT},${EXTEN},1)
;
;
; Include the "standard" exit handlers here.  You may wish to
;  replace these here and in the rest of this example with your
;  own values if you have them set differently.
;
exten => h,1,Hangup
exten => i,1,Hangup
exten => t,1,Hangup
exten => T,1,Hangup
;
;
;
;
[tello-test2]
;
; So, we now start to normalize the number.  This is somewhat
;  confusing, since we use the "include" statements to force
;  an ordered examination of the number strings.  To create
;  some sanity, the context numbering will have a majorname.minornum
;  format to make it so that wildcards don't step on each other.
;
; This set of the dialplan is "just-in-case" a non-E.164 format
;  number gets passed in here.  Things like leading "011" and
;  the like should be deleted, and any numbers less than seven 
;  digits should be bounced out to the normal dialing plan, and
;  any numbers that are exactly seven digits probably need an
;  area code (North American) and a leading "1" added to them.
;
; Note that we have no way of protecting against a leading "9"
;  digit, as some PBXes use to indicate an outbound trunk dial.
;  This is because "9" is a valid leading digit as an area code
;  or country code digit, so we have no way of testing if it is
;  "valid" or "invalid" in a number.  Please consult Tello engineers
;  if this presents a problem; there are easy (but custom) solutions
;  that can quickly be implemented as a part of this dialplan but
;  do not warrant inclusion as they are somewhat confusing.
;
; This context essentially loops until all instances of the prefix
;  searched for are removed from the dialstring.  The default
;  case is to strip off "011" and then jump to tello-test3.
;
include => tello-test2.1
include => tello-test2.2
include => tello-test2.3
include => tello-test2.4
;
; Include the "standard" exit handlers here.
;
exten => h,1,Hangup
exten => i,1,Hangup
exten => t,1,Hangup
exten => T,1,Hangup
;
[tello-test2.1]
; 
; In North America, the sequence "011" prefixes any international
;  call.  So, to dial a number in the UK (44) we would dial
;  0114480033330000 as an example.  We need to strip the first
;  three digits off the number to get the E.164 number, which
;  just starts with the country code and everything after it.
;  Just run this context over again, with the new extension after
;  stripping off the first three digits.
;
; Hopefully, anyone in other nations will never have a number 
;  starting with "011" that is dialed.  If you do, just comment
;  out this line and it should do no harm.
;
; !!NON-NORTH AMERICAN USERS READ THIS!!
;
; If you are in a nation that uses some other three-digit prefix
;  to dial internationally, please replace "011" below with that
;  three digit prefix and it will be stripped off and correctly
;  handled.  If you only use two digits (i.e.: 00) then change
;  the ${EXTEN:0:3} to be ${EXTEN:0:2}
;
exten => _011XXXXXX.,1,Goto(${EXTEN:0:3},1)
;
[tello-test2.2]
;
; Test for seven-digit only and add area code and leading "1"
;
exten => _XXXXXXX,1,Goto(1${TELLO-AREACODE}${EXTEN},1)
;
[tello-test2.3]
;
; Test for less than seven digits, and if so, dump
;  out to normal parsing.  This would be the end of any Tello
;  dialplan use.  This allows mistaken 411, 911, etc. and 0 and
;  other types of calls to avoid being tested against the Tello database.
;
exten => _XXXXXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XXXXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XXXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XXX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _XX,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
exten => _X,1,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
;
[tello-test2.4]
; 
; All numbers that don't match any of the other included contexts,
;  or which have been re-written and looped back into the included
;  context list will match against this extension, and so will just
;  jump to the next context in our examination chain. 
;
exten => _X.,1,Goto(tello-test3,${EXTEN},1)
;
;
;
[tello-test3]
;
; So here is the actual test against the Tello database, via a SIP INVITE.
;  The number has been "normalized" into what hopefully is an E.164 compatible
;  number, and now we place the call to the SIP peer of Tello's proxy.
; If the call is successful, then the dial will create a call to the remote 
;  SIP peer via Tello's SIP proxy.  The two parties will talk, and the 
; See below for failure cases and results.  If you are a particularly
;  sophisticated Asterisk user, you will recognize this as the heart of
;  the dialplan.  Based on this Dial statement, we either complete the 
;  call to a remote Tello system user, or we fail and fall back to another
;  method to try to complete the call.
;
exten => _X.,1,Dial(SIP/${EXTEN}@tello-peer) 
;
; So, our dial has either failed miserably, has rung "busy" (+101), or
;  has timed out (+51).  No matter - all failures go to the backup method.  This
;  is not optimal, since "busy" should lead to a call fail, but there are
;  too many 'dumb' softswitches out there which reply with 'busy' when they
;  should reply with some other failure method, so it is unsafe to assume
;  that a busy means that the call cannnot be completed via PSTN.  Therefore,
;  we send all paths to the secondary dialing method, which is specified
;  elsewhere in the dialplan by the administrator (not included in this 
;  file, as this is outside the scope of the intended example.)
;
; This code will work with =>1.2 (with no +101 or +53 jumping) or with older
;  versions of Asterisk as well which do priority jumping as a result of
;  Dial failures.
; 
; This is the end of the Tello-specific call routing and directory lookup.
;
exten => dial,3,Goto(103)
exten => dial,53,Goto(103)
exten => dial,103,Goto(${TELLO-DEFAULTCONTEXT},${TELLO-ORIGEXTEN},1)
;
;
; Include the normal inclusions for invalid, hangup, and timeouts.
;
exten => h,1,Hangup
exten => i,1,Hangup
exten => t,1,Hangup
exten => T,1,Hangup
;
;
;
[from-tello]
; 
; The "from-tello" context is where inbound calls come from Tello.  We pass
;  calls to this context from the "tello-peer" SIP stanza in sip.conf
;  These calls will be the number of digits you specify (which can be managed 
;  on the Tello webpage) and need to go elsewhere into your dialplan so that
;  the appropriate phone might ring.  This is very dependent on your dialplan
;  so this is just a "Goto" to the hypothetical context called "internal"
;  which is where you have your primary extensions listed, using a five digit
;  dialing sequence.  We'll assume this is an 11-digit number (North American
;  E.164) from Tello, and that you only need the last five digits, so cut
;  off the first six digits and re-direct.  All other numbers get sent to 
;  a congestion tone, since we don't know what to do with them.  If you
;  change the number of digits you receive by telling Tello to send you
;  fewer digits, make sure to modify this context appropriately.
;
;  ** YOU NEED TO MODIFY THE LINES BELOW TO SEND INBOUND CALLS FROM ***
;       ** TELLO USERS TO THE RIGHT PLACE IN YOUR DIALPLAN. ***
;
exten => _1XXXXXXXXXX,1,Goto(internal,${EXTEN:6}
exten => i,1,Congestion
exten => h,1,Hangup
;
;end






Created by: tello, Last modification: Fri 05 of Nov, 2010 (22:00 UTC) by admin
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+