[Asterisk-Users] IAXy setup

Sat Oct 16 21:20:50 MST 2004

> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com 
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
> Andres Tello Abrego
> Sent: October 16, 2004 11:15 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] IAXy setup
> 
> 
> Jim Van Meggelen wrote:
> > Actually, the IAXy is really very immature, and is desperate for 
> > several
> > enhancements:
> 
> Yeap, rigth.
> > 
> > 1. The MAC address needs to be visible on the unit. As it 
> stands the 
> > only way to determine the identity of the thing is packet 
> sniffing or 
> > looking through logs. This is tolerable in a lab, but ridiculous in 
> > production. What if I want to program 100 of them, and assign IP 
> > addresses based on MAC addresses?
> Be methodic.
> Place a label of the ip used.
> Is on production, at fixed position: use fixed ip.
> Is on production, not fixed position: shellscript + xforms 
> and you have a popup to tell where your iaxy is. Not the best 
> solution, but, not a critical issue. At least not for me.

Sure, There's always a way around these types of things. Nevertheless,
it's kinda not proper to deliver an ethernet device that is not labeled
with it's MAC address. Why should we have to go through any kind of
trouble to determine this? I say it should be on the unit.

> > 2. DNS support. The IAXy needs to be able to handle names.
> Static * box ip using vpn. You need extra hardware, but due 
> the dhcp and nat-piercing capabilities, you can live without this...

I CAN live without it, but do I want to? Any device that's intended to
traverse an internet connection would be well served by some ability to
request name resolution, no? Also, what happens if your IP address
changes at the Asterisk end? You'll have to connect to all your IAXys to
reprogram them. You're proposing some extra piece of hardware at the far
end to handle the IP translation. But what if I just want to deploy an
IAXy at the home of several employees? I have to give them an IANA IP
address to connect to, and if I ever need to change that address, I
can't see how to do it without having the IAXy sent back to me to get
reprogrammed. It's a safe bet that other companies are gonna support IAX
on other FX devices very soon. What sort of features do you think they
will include? 

> > 3. Restore to factory. There is currently no documented method to 
> > resore an IAXy to factory defaults. This means that if you have a 
> > stock of them that may or may not have been pre-configured, you'll 
> > need to do more packet sniffing to figure out what the IP 
> address is.
> Yes, this is an issue, iaxy unit do have something like a 
> reset switch, I used, no luck. That where I relized to be 
> methodic. Iaxy at production, label, not at production, 
> provided with a generic 192.168.0.2/255.255.255.0 192.168.0.1 
> gw 192.168.0.1 * bpx configuration. Not to die for.

I asked Digium support. They said that 1) there is no process to restore
to factory default and 2) that button has no purpose at this time. It
looks so tempting, though. Who couldn't resist pushing it.

> > 4. Some kind of TFTP, SSH or whatever is needed to allow connection 
> > and configuration of the device.
> ssh needs a lot of hardware, tftp, maybe... providing works 
> good for me. You may have a point.
> > 
> > I also love the IAXy (I use them happily in my lab), but it is much 
> > more of a beta device at this point. I really couldn't feel 
> > comfortable deploying them at customer locations until the 
> management 
> > functions are improved.
> I think, iaxy is a very well tougth product, and I´m using it 
> at production. Mainly becose, it doesn´t have too much 
> technical issues, it works perfectly with * and there is 
> nothig a vpn + routing cannot solve.
> 
> Lukly there is a lot of people.

I haven't even gotten into the physical limitations of the unit: no wall
mount lugs, no eyes for ty-raps, no rubber feet. It's very difficult to
secure one, never mind several.

Look, I probably sound like a troll, daring to critisise the mighty
IAXy. But the fact is that things get better when people point out ways
in which improvements can be made. I love what the IAXy has done, and I
think it's quite appropriate to develop a wish list of features that
should be implemented as the product evolves. Products do not improve by
people talking about how much they love them; they improve when users
direct criticism at shortfalls, and manufacterers listen and implement
the changes.

IAX has a bright and glorious future, and the IAXy is blazing a trail by
being a really top-notch first effort as an IAX-based FXS endpoint. But
there are some practical, useful enhancements that would improve it
tenfold. Those should be pointed out and discussed. 

> > It'll get there I'm sure.
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: asterisk-users-bounces at lists.digium.com
> >>[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
> >>Andres Tello Abrego
> >>Sent: October 16, 2004 7:43 PM
> >>To: Asterisk Users Mailing List - Non-Commercial Discussion
> >>Subject: Re: [Asterisk-Users] IAXy setup
> >>
> >>
> >>:) I supposed that
> >>
> >>iaxy are soooo beatiful!
> >>
> >>rich allen wrote:
> >>
> >>>well it looks like i had a typo in the iax.conf. instead of
> >>>disallow=all
> >>>i had dsallow=all which i didnt notice til i about to paste 
> >>
> >>the file.
> >>
> >>>thanks for responding
> >>>
> >>>- hcir
> >>>
> >>>
> >>>>could  you paste the file u are trying to provide?
> >>>>
> >>>>
> >>>>rich allen wrote:
> >>>>
> >>>>
> >>>>>iH
> >>>>>getting the following in the console when i go off hook from IAXy
> >>>>>chan_iax2.c:5713 socket_read:Rejected connect attemp from 
> >>>>>192.168.0.5 requested/compability 0x4/0x24 incompatible with our 
> >>>>>capability 0xff3 any idea what this is telling me? thanks
> >>>>>- hcir
> >>>
> >>>
> >>>_______________________________________________
> >>>Asterisk-Users mailing list
> >>>Asterisk-Users at lists.digium.com
> >>>http://lists.digium.com/mailman/listinfo/asterisk-users
> >>>To UNSUBSCRIBE or update options visit:
> >>>  http://lists.digium.com/mailman/listinfo/asterisk-users
> >>>
> >>
> >>_______________________________________________
> >>Asterisk-Users mailing list
> >>Asterisk-Users at lists.digium.com
> >>http://lists.digium.com/mailman/listinfo/> asterisk-users
> >>To 
> >>UNSUBSCRIBE or update options visit:
> >>   
> > 
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > 
> > 
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004
> >  
> > 
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004
> >  
> > 
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users at lists.digium.com 
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> > 
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com 
> http://lists.digium.com/mailman/listinfo/> asterisk-users
> To 
> UNSUBSCRIBE or update options visit:
>    
http://lists.digium.com/mailman/listinfo/asterisk-users

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.775 / Virus Database: 522 - Release Date: 08/10/2004