Asked by:
Avaya Phone Systems

Question
-
Hi,
I am working on integrating OCS with Avaya IP Office and Avaya CM. I have the IP Office working but can't get presence to work correctly we can now make calls from MOC and call users on MOC. I am working on getting the integration done with CM either through a SES or a AES, I am trying to do this without using a IP Gateway. I am looking for any assistance or would love to discuess this with anyone who is trying to do the samething. Please email any questions to me at tony@tlarsen.net
Thanks
TonyWednesday, February 20, 2008 4:59 AM
All replies
-
We are currently workin at the same subj.
for today we have linked AES/SES and OCS, but the problem is how to make work all employers andpoint at the one system.
We still looking the way how to map OCS MOC to CM ext, like a CellPhone with EC500 any attempts to do this, was unhappy - the CM cannot fork call to OCS, and replay with denial event "NO USER RESPONDING"
other feauteres working pretty well.
Friday, March 28, 2008 2:20 PM -
If the CM is able to register standard (3rd party) SIP devices, have you looked at a gateway partner that can register to the CM as a SIP device; and have the CM associate the CM extension with the SIP Device extension?
If this is possible, the call to the SIP device will arrive on the gateway, and it can transport the call to OCS (and perform any number normalizations, if required).
Monday, March 31, 2008 5:13 AM -
Hi,
I got my system to work with the CM/IP Office by using a IP Gateway. I am now trying to get this integration working with SES 4.0 directly without using the GW but am having trouble. Could you provide some assistance?
As for dual forking we created two ext. for a user then we pointed the DID directly to OCS and then using Sim. ring to get the desk phone working.
Thursday, April 3, 2008 10:15 PM -
Moto822, I have a simlar configuration to yours could you point me in the correct direction to have our IP office and OCS 2007 talk to each other?
thanks,Saturday, January 3, 2009 3:14 AM -
Moto822
I am also interested in how you configured your Avaya integration. We are working on Avaya CM integration. We have configured two extentions, but the DID is still on the traditional phone and we're attempting to forward calls to the OCS extention.
Calls to existing DID work xxx-4535
Calls to OCS extention work 6535
Setup Avaya to forward extention to 6535 via access code
Call "blips" the hard phone and then we get a fast busy... The following error is registered with a trace of the mediation server
The forward is failing with a "SIP/2.0 400 Malformed route header" ms-diagnostics: 1018;reason='Parsing failure"
Perhaps there is a more elegant integration with the Avaya? We're hoping to keep the Avaya extention available as a falback during our pilot period...Wednesday, March 25, 2009 1:48 PM