I agree, I got my first IAXy yesterday. I couldn't for the life of me get DHCP to work, then I remember it was plugged into a VLAN on a Cisco Switch (3550). Spanning tree always "waits" to bring up the vlan on ports, unless specified otherwise. It would appear the IAXy only sends an initial DHCP request and then it's hit or miss. DNS support would be great, that's why there is an altserver, I would guess. Speaking of which, I'm going to put up a new post on echo avoidance with the IAXy.
-----Original Message----- From: Jim Van Meggelen [mailto:[EMAIL PROTECTED] >Actually, the IAXy is really very immature, and is desperate for several >enhancements: 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? 2. DNS support. The IAXy needs to be able to handle names. 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. 4. Some kind of TFTP, SSH or whatever is needed to allow connection and configuration of the device. 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. It'll get there I'm sure. _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
