Hi Dave, thanks for your advice. I tried to play with 1.0.10.1 and 1.2.1.1, actually got the same warning messages as in 1.2.7.1. Finally I found the problem myself, it is the dial-plan error that caused not sending calls out, however the warning seems not affect the incoming and outgoing calls.
The one in error: exten => 1xx,1,Dial(iax2/iaxtrunktox330/[EMAIL PROTECTED],120) The one working: exten => _1xx,1,Dial(iax2/iaxtrunktox330/[EMAIL PROTECTED],120) Thanks, Chris Chen On 8/1/06, David Cook <[EMAIL PROTECTED]> wrote:
Is there a ztdummy with 1.2.7.1? If so, lets make sure you load it. This would be a kernel module as opposed to an asterisk modules so you may want to look into /etc/modules.d or explicitly load it with insmod from the asterisk start script. Else, try going back to 1.0.10. It works fine for me on that platform. Based on that error, you are not even getting into any authentication or dial plan issues yet. dbc. Chris Chen wrote: > Hi Dave, I am running Asterisk 1.2.7.1 <http://1.2.7.1> with OpenWRT > whiterussion RC5 on WRTSL54GS with one USB 2.0 port. > Here is the config in iax.conf > > [99999] > type=user > host= 192.168.0.253 <http://192.168.0.253> > secret=xxxxxxx > context=default > trunk=yes > allow=gsm > qualify=yes > > [iaxtrunktox330] > username=99998 > type=peer > secret=xxxxxxx > qualify=yes > host= 192.168.0.253 <http://192.168.0.253> > disallow=all > context=default > allow=gsm > > Dial plan in extensions.conf > > exten => 1xx,1,Dial(iax2/iaxtrunktox330/[EMAIL PROTECTED],120) > > Here is the log from /var/log/asterisk/messages > Jul 30 17:24:10 WARNING[2573] chan_iax2.c: Unable to support trunking > on user '99999' without zaptel timing > Jul 30 17:24:10 WARNING[2573] chan_iax2.c: Unable to support trunking > on peer 'iaxtrunktox330' without zaptel timing > > I could get incoming call from my extensions on 192.168.0.253 > <http://192.168.0.253>, but when I tried to call extensions 1xx on > 192.168.0.253 <http://192.168.0.253>, I got the messages that the > destination is not available. > > Please shed some light on this. > > Thanks, > Chris Chen > >
