Greetings,
IP Office 406
Phone Manager 3.x OR 4.x
Term Server WIndwos 2003 R2 Std
Term Server Windows 2008 R2 Ent
We are upgrading to Windows2008R2 Term Services:
1) Has anyone gotten any version of Phone Manager to work in a Terminal Server environment under WIndows 2008 R2? Windows 2003 Terminal Server and Phone Manager(3.2.30) worked fine, but Phone Manager 4.x or even 3.x don't see the control unit. Is there a setting I am missing? I am able to ping the head unit from win2008r2.
Also...this might matter ;-)
2) The working phonemanager on windows 2003 Term Serv is in a co-lo datacenter across an MPLS IP VPN from the IP Office unit so crossing the router seems like it works ok as all traffic is passed and nothing "seems to be" blocked. The new 2008 Term Serv is also in the same co-lo...but phonemanager can't see the head unit from that box?
TIA for ANY guidance for this Avaya newbie
Thanks
Paul
IP Office 406
Phone Manager 3.x OR 4.x
Term Server WIndwos 2003 R2 Std
Term Server Windows 2008 R2 Ent
We are upgrading to Windows2008R2 Term Services:
1) Has anyone gotten any version of Phone Manager to work in a Terminal Server environment under WIndows 2008 R2? Windows 2003 Terminal Server and Phone Manager(3.2.30) worked fine, but Phone Manager 4.x or even 3.x don't see the control unit. Is there a setting I am missing? I am able to ping the head unit from win2008r2.
Also...this might matter ;-)
2) The working phonemanager on windows 2003 Term Serv is in a co-lo datacenter across an MPLS IP VPN from the IP Office unit so crossing the router seems like it works ok as all traffic is passed and nothing "seems to be" blocked. The new 2008 Term Serv is also in the same co-lo...but phonemanager can't see the head unit from that box?
TIA for ANY guidance for this Avaya newbie
Thanks
Paul