[asterisk-gui] Teliax

[Trevor Benson]

Login to your Teliax customer portal.  Most of your settings are from here.  next verify which proxy server you have setup..  I ported all my numbers away from Teliax a few months back, but had used the service for years.  As long as you have the Inbound Route defined, and go through their portal to select your proxy, make sure that proxy's IP is in your configuration for your trunk then it should work.  If you are using SIP, then turn on DNIS in the portal to make the DID sent over via sip.

Also if you have IAX an and AUTH configured then its expecting the inbound number to be in a Teliax context, which in the asterisk gui isnt going to happen without you customizing the context.  Otherwise make sure you have the 10 digit DID setup in your inbound routes, (pretty sure it was just 10 digit, not 11 prepended with a 1).


Trevor Benson
A1 Networks
(707)570-2021 x201
tbenson at a-1networks.com



On Dec 2, 2009, at 4:26 PM, Kevin Pate wrote:

> Lief,
> 
> Thanks!!  That clears things up a bit.  The next problem I'm having is 
> when a call comes in, it shows up on my phone as coming from 
> asterisk at 192.168.1.75.  How do I get the CallerID to show up instead?  
> Is that handled on the Asterisk box or at the provider?
> 
> Phone - Cisco 7940G
> 
> Thanks!!
> 
> Kevin Pate
> RHCE - MCSE - CCNA
> Pate Consulting, Inc.
> www.pateconsulting.com
> kevin at pateconsulting.com
> V 713.333.LINUX (5468)
> F 713.333.5494
> M 713.823.8845
> 
> 
> 
> Leif Madsen wrote:
>> Kevin Pate wrote:
>> 
>>> Hello again everyone.  I'm looking for someone that has configured 
>>> Asterisk-GUI with the Teliax service before.  I'm having problems 
>>> accepting inbound calls on my Teliax IAX trunk that I created using the 
>>> GUI.  I have set an incoming calling rule with the 's' (catchall) for 
>>> this trunk.  Outbound calls work find.
>>> 
>>> Any help is greatly appreciated.
>>> 
>> 
>> 's' is not a catch-all extension. It is a built in extension for use by incoming 
>> analog lines that do not request an extension by default (and thus, DAHDI enters 
>> the dialplan via the 's' extension in the context you've configured).
>> 
>> Perform a SIP debug at the Asterisk CLI to determine what extension is being 
>> requested, and in which context, then you can determine what pattern match you 
>> need to create to accept the call. Likely you can use something like:
>> 
>> _X.
>> 
>> ...as the pattern match the incoming call request.
>> 
>> Leif Madsen.
>> 
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> 
>> asterisk-gui mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-gui
>> 
>> !DSPAM:4b1703cc220011504189220!
>> 
>> 
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-gui mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-gui