asterisk users - Jul 2007 - Need help with inbound IAX

I have just started working with Asterisk and have run into a road block 
concerning IAX and an inbound DID from callwithus.com. I am getting 
nowhere and I don't really know how to isolate the problem. The asterisk 
version is 1.2.7 on ubuntu, sits behind a firewall with iptables. I can 
connect and make a call to other internal extensions using zoiper and 
iax. When I try and use the number, I do not see any traffic on the 
firewall from the provider, so I think it is config string I have put in 
at callwithus, but I have tried so many things anymore, I am not sure 
anymore. Any help is much appreciated.

Thanks,
Patrick

I have the following rules on the firewall:
-A FORWARD -p udp -m udp --dport 4569 -j ACCEPT
-A PREROUTING -i eth2 -p udp -m udp --dport 4569 -j DNAT 
--to-destination 192.168.1.2

I have similar rules for port 25 and 80 that work.

On the asterisk machine, iax.conf looks like:
[general]
bandwidth=low
disallow=lpc10                
jitterbuffer=no
forcejitterbuffer=no
tos=lowdelay
autokill=yes

register => 45*****:12**@callwithus.com

[iaxin]
type=friend
context=iax-inbound
username=iaxin
secret=easypass
qualify=no
host=callwithus.com


in extensions.conf:
[iax-inbound]
exten => s,1,Answer()
exten => s,2,Playback(hello-world)
exten => s,3,Hangup()

This is what callwithus is supposed to forward the call to:
IAX/iaxin:easypass at myserver.com/s at iax-inbound

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What do you get with:

iax2 show registry

- --
Cheers,

Matt Riddell
Director
_______________________________________________

http://www.venturevoip.com (Great new VoIP end to end solution)
http://feeds.feedburner.com/AsteriskNews (Daily Asterisk News - rss)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqVvRDQNt8rg0Kp4RAj89AJ9XzL/EUCBMG3/qfDkhHMSJggoIWQCggAMu
e4tnaTrjg6wRI8kIyOS0Qgo=AbcT
-----END PGP SIGNATURE-----

> What do you get with:
>
> iax2 show registry
>   
homer*CLI> iax2 show registry
Host                  Username    Perceived             Refresh  State
64.85.162.136:4569    06*******   68.XX.XX.XX:4569          300  Registered

is that bad?

Patrick

On 7/26/07, Patrick Buller <pbuller at deerplain.com>
wrote:
>
> This is what callwithus is supposed to forward the call to:
> IAX/iaxin:easypass at myserver.com/s at iax-inbound
Does that need to be IAX2/iaxin:easypass at myserver.com/s at iax-inbound ?
Notice the "2"? It used to be that IAX referred to v1 of the IAX
protocol, which has since been obsoleted. I vaguely recall discussions
that IAX2 and IAX were to be made synonymous now that v1 is obsolete
for quite a while. Didn't follow those discussions to know whether
that happened or not. Might be worth a try changing your config with
callwithus to IAX2/...