Strange behaviour on connecting networked IPO with different Manager/OS

[digiteltlc]

We experience different behaviours while trying to connect three remote IPO :

IPO "A" 406 V3.2(0)
IPO "B" 401NG SmallOffice V4.2(23)
IPO "C" 401NG SmallOffice V4.2(20)

They all are behind Mikrotik routers, each with its own public IP address and with TCP ports 50802, 50804, 50808, 50812 forwarded.

4 Managers are all on same LAN behind the same router so sharing the same "outgoing" public IP adress, they are :

Manager "1" Windows XP sp3 running 9.1.3.0 build 120 (lite)
Manager "2" Windows XP sp3 running 10.0.(43)
Manager "3" Windows 7 running 9.1.3.0 build 120 (lite)
Manager "4" Windows 10 running 9.1.3.0 build 120 (lite)

All managers try to connect IPOs typing the remote ip address on lower "Unit/Broadcast Address" field of "Select IP Office" windows and clicking "Refresh" button.

These are behaviours :

Manager "1" displays only IPO "B" or "C" while pushing refresh , no way to see IPO "A"
Manager "2" displays correctly all IPOs
Manager "3" displays NONE of IPOs
Manager "4" displays only IPO "B" or "C" while pushing refresh , no way to see IPO "A"

All IPOs are seen by any Manager if , after selecting IP address, the "OK" button instead "Refresh" button is pressed, but sometimes wrong model/version is displayed.

I have tried Manager 10.0.(43) on Windows 7 still NONE of IPOs are seen (not yet tried 10.0(43) on Win10)

Do you have experienced some behaviours like these ?? Any idea about ??

Thank you

 

[IPGuru]

They all are behind Mikrotik routers, each with its own public IP address and with TCP ports 50802, 50804, 50808, 50812 forwarded.
{/quote]
unless you have taken further action you are asking to be hacked!

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[holdmusic34]

Try with Manager 6.2? You can use call status too!

How many onomasticonists do you know? Make a list.

 

[IPGuru]

Manager V9.1 will not speak to anything prior to V4.0
(Avaya should be updating their documentation shortly)

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[digiteltlc]

Yes, Manager 6.2 seems to work with all older systems
So....Is it a wanted behaviour when latest manager versions ignore identification of older pbx release ???

This case, I'll go for some unused XP machines with old manager for old IPOs.....

 

[holdmusic34]

It wasn't a wanted behaviour for you.
It doesn't affect most because those releases are obsolete and eol.

Yes it is wanted. I want 9.1.3 to work and work well with 9.1.3< release 9.0.
8.1, 9.0 and 9.1 were major releases with many changes.
I don't want Avaya to be tied to something just because that's the way it worked in 2003. Somewhere they have to draw the line in the sand.

Glad you can see your systems now. Have you had a play with call status? (cheap phone manager pro!)

Poopy bubbles!

 

[digiteltlc]

Thanks for infos
Not yet played with call status.....

 

[IPGuru]

Im not sure it was wanted behaviour
when I reported it they initially cam back with "Design Intent" but then admitted they did not realise it was intended behaviour until I reported it.

(Actually they had decided to kill of an earlier method of discovery for security reasons & had not fully thought about the side affects. As it only affects IP4XX systems & IP4XX is no longer supported hardware they can justify removing support)

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[derfloh]

Telling us it is a design intend is much easier to say it is an error and start to resolve it.