Alcatel Unleashed

Hello guys,

i have also the problemon the common hardware rel. 9.0 , that the attendant ist not to start. i have only one network interface, and no MAC in the OXE. the firewall isn`t aktive.

The PC ist a Windows VIsta clinet and the release of the 4059 ist 5.1.6.
what make i wrong?

greetings

Klaus

I take it for granted that you run Vista x86 and not x64?
1- Check the IP-address, it must be That of the Main CPU.
2- Check the defined mcdu, this must be the same as the one used when creating the A4059 IP.
The mcdu is used to make an association between the defined 4059 in OXE and the mac-address of the PC.
When the mac-address is assigned in oxe ( done automatically ) the mcdu is sent over the wire when the application starts but never taken into account by the pbx...

3- Use built-in tool tcpdump to see if the mac-address is sent by the 4059.
( note that the 4059 appends '02' to the macaddress but this is just used to identify the request as a 4059-request...)

We had this issue at another location where the Attendant was loaded on a different PC and then later moved. To resolve the issue we had to delete the attendant set and recreate it and the attendant came into service. Also make sure the you are using the attendant console physical number in the association field in the 4059 software

Thank you guys, the attendent it´s starting now. i removed it an take the pysical number not a A1, i take a number wie cann dial, and so is it good.

@rogermorse: It's normally enough to remove the MAC address under Attendant set (GoDown) after moving the Application to a new PC.
The number to be entered in the Application Setup tool is the physically attendant set number shown also with opstat command.

That is true but for some reason, I have had to do this in the past to get it to work -

Thank you everyone for all the suggestions. After trying a few of these I finally got my 4059IP working.