We are upgrading to Exchange 2013 and running Exchange 2010 side by side until all users are migrated. 2013 is in front and directs traffic to 2010 if needed. Below is how we programmed it and what is and what is and isn’t working.
-We copied our existing SIP Profile but changed the port 5062. We disabled our old SIP Profile.
-When you dial our pilot number (6100) from a desk that has voicemail, everything worked fine, regardless of where your mailbox was located (2013 or 2010)
-When you dial from the outside (xxx-6100) and you are prompted for your extension and if your mailbox is on 2013 everything worked fine. If the mailbox was on 2010, the voicemail asks for your extension number, you briefly hear the on hold greeting and then it prompts again for the extension number. This is a non-ending loop.
-If internally you dial the pilot 6100 from a phone that does not have a voicemail box, it would put you in the same loop asking for your extension number over and over.
When you call in (xxx-6100), it comes in on our PRI’s that are on a different Controller, then I assume it hops over to our vMCD and then sends it to Exchange. Is there something with the integration of these calls that is not working.
Any suggestions would be appreciated.
-We copied our existing SIP Profile but changed the port 5062. We disabled our old SIP Profile.
-When you dial our pilot number (6100) from a desk that has voicemail, everything worked fine, regardless of where your mailbox was located (2013 or 2010)
-When you dial from the outside (xxx-6100) and you are prompted for your extension and if your mailbox is on 2013 everything worked fine. If the mailbox was on 2010, the voicemail asks for your extension number, you briefly hear the on hold greeting and then it prompts again for the extension number. This is a non-ending loop.
-If internally you dial the pilot 6100 from a phone that does not have a voicemail box, it would put you in the same loop asking for your extension number over and over.
When you call in (xxx-6100), it comes in on our PRI’s that are on a different Controller, then I assume it hops over to our vMCD and then sends it to Exchange. Is there something with the integration of these calls that is not working.
Any suggestions would be appreciated.
