I *think* you need to downgrade the Audiocodes Mediant 1000 firmware to 5.4 to get it to play nicely with SipX.
We have a similar set-up in our college - SipX server on CentOS with three Mediant 1000 units (with FXS modules) distributed on three sites. Works brilliantly so far :) HTH Huw -- Huw Wyn Jones Systems Administrator Coleg Meirion Dwyfor [email protected] ----- Original Message ----- From: "Johan Reinalda" <[email protected]> To: [email protected] Sent: Tuesday, 6 April, 2010 00:16:21 GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [sipx-users] Newbie: AudioCodes configuration help Dave, thanks for the suggestion. We've looked at that, and see no difference. A wireshark packet capture reveals that the Mediant 1000 requests bootp info, gets the proper fields and options (ip, next server, subnetmask, router, dns, hostname, tftp, filename, etc.) On the console, it shows the proper ip address, gw, mask, but the tftp server is set to 10.1.10.6 This is not what is sent via bootp, and is incorrect for our network. Boot filename is also wrong (preset value seems to show; v5.00 firmware), and ini name is blank. Any ideas ? I am going to try hardcoding these in the web config and see what happens... Johan On 4/3/2010 5:12 AM, Black, Dave wrote: > Try taking a look at the switch port that the audio codes is plugged > into. If STP is enabled, likely the audio codes is timing out on bootp > request prior to switch starting to forward packets, hence ini files are > not downloaded. If this is the case, you can temporarily disable STP on > the switch port that the audio codes is connected to for testing. There > is also a parameter in the audio codes setup that controls how long it > waits for bootp response. Refer to audio codes manual for specific > settings, I believe it's in the quick start guide that comes with audio > codes gateways. > > DaveB. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Johan > Reinalda > Sent: April 2, 2010 2:03 PM > To: [email protected] > Subject: [sipx-users] Newbie: AudioCodes configuration help > > All, > > we are testing/researching sipX 4.1.7 for potential campus use. > Got the centos5 installer setup& working with two instances, and a > handfull of Polycom 330/430 phones no problems. Voicemail, calls, etc > all work fine. > > Just purchased some AudioCodes devices (an MP 1000 for gateway testing, > and several MP112-SIP to simulate FAX lines.) > All are running firmware v5.80A... > > Configured the devices in sipX as a gateway, and several phones (with > lines). > Followed > http://sipx-wiki.calivia.com/index.php/HowTo_configure_AudioCodes_SIP_Ga > teway_with_sipX > and configured dhcpd accordingly (see below) > > We can login to the devices' web interfaces, but cannot get them to > register. Manual configuration of the devices is the next step, > but we were under the impression that this would be automatically done > by sipX > (we see the ini files in the tftp directory) > > Any suggestions as to what we may be missing ? > > Thanks, > Johan > > > -------------------------------------------------- > part of dhcpd.conf: > Note that the firmware files are not actually in the tftp dir, but these > > are the image names > that are already in the devices. > > #AudioCodes FXS and SIP-PSTN Gateways > group { > next-server 10.64.8.101; > > host audiocodes-mp112-1 { > option host-name "mp112-1"; > hardware ethernet 00:90:8f:26:1e:15; > fixed-address 10.64.8.51; > filename "MP112_SIP_F5.80A.023.006.cmp;00908F261E15.ini"; > } > > host audiocodes-mediant-1000-1 { > option host-name "mediant-1000-1"; > hardware ethernet 00:90:8f:27:67:fc; > fixed-address 10.64.8.61; > filename "MP1000_SIP_F5.80A.023.006.cmp;00908F2767FC.ini"; > } > > #end of group > } > > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
