• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1080
  • Last Modified:

Add CAS Role on Exchange 2010 Mailbox Server

Hello,

Brief overview of our Exchange config.
1 X Exchange 2010 Mailbox server(physical)
2 x Exchange CAS (on different Virtual machines) for OWA and Outlook clients

Now onto the question at hand.

We recently upgraded our Phone System NEC Sphericall v7.0.2, which has support for Exchange 2010. However, when we commissioned Sphericall to use Exchange 2010 and Voice mail server, it had some errors. We contacted Sphericall TAC and they mentioned that a CAS role needs to be on the Exchange server in order for the Phone system to send voice mail to the exchange server. Both the exchange server and phone system are in same physical location and subnet.

Question is, Will adding the CAS role on the Exchange Mailbox Server cause and issue with the 2 existing CAS servers communicating with the Mailbox server?
0
PT Guy
Asked:
PT Guy
  • 4
  • 3
1 Solution
 
ronnypotCommented:
Hi,
Don't think it will make any difference if you install the CAS role on the Mailbox server role.
Have you installed the HUB transport role also on the same servers as the CAS role?

 I think the problem is you need to create a receive connector on (all) your HUB transport servers, because the phone system will deliver to your Exchange server but isn't athenticating so it isn't allowed to deliver any messages.

Read more about receive connectors over here: http://technet.microsoft.com/en-us/library/aa996395.aspx
And for anonymous acceptance here http://technet.microsoft.com/en-us/library/bb232021.aspx

Ronny
0
 
e_aravindCommented:
> Do you have any other older versions of Exchange servers available along with this E2010?
If yes, there would be the problem.

>> test the OWA, Outlook Anywhere from both the CAS servers using the IP-Address
0
 
PT GuyAuthor Commented:
Hello,

Yes, we do have and Exchange 2003 box that we have communicating with E2010. We have been migrating all the Mailboxes from E2003 -> E2010 and when we upgraded the phone system, we wanted to commission only the E2010 server as the new Voice mail server. The E2010 CAS servers do have SAN certs on them and OWA can be accessed via IP/OWA.

Currently we still have Vmail being sent to the E2003 server.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
e_aravindCommented:
so you can have the stand-alone CAS with the External-URLs
This should have the NATTing to the internet

The second cas+mbx could be used only for the voice mail.

> To reach the E2k3 MBX...the URL\path should always use the stand-alone CAS server
0
 
PT GuyAuthor Commented:
e aravind,

We have 2 CAS servers(VMs) comm. with the E2010 MB server. What I think will work(correct me if I'm wrong) is set up a CAS Role on the MB server, where it does not need to access the web. It will not need to comm. with the existing 2 CAS servers.

We plan on decom the E2003 server soon.
0
 
e_aravindCommented:
IMO, yes it should work
(Having CAS on the MBX + Stand-alone CAS server)
0
 
PT GuyAuthor Commented:
Hello all,

The problem was due to the VoIP system not capable of communicating with a CAS array. The Company provided a work around(reg hacks) to get to work.
0
 
PT GuyAuthor Commented:
Problem, due to VoIP provider not designing software to communicate with an Exchange 2010 CAS array.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now