Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avyaya IP Office and Exchange UM integration

Status
Not open for further replies.

qlafferty

Technical User
Dec 17, 2009
5
US
thread940-1469382
I just read through a few threads in here and I see that a while back there were several posts about integrating Avaya IP Office with Exchange UM using hardware and software gateways. I am currently playing around with a pbxnsip PBX that allows me to forward and store all of my voicemails in Exchange 2010 Unified Messaging. It actual works pretty well. The reason for this post is that I am moving to an IP Office PBX and it looks like this is much more difficult to accomplish with Avaya equipment. There was a post from RavenAndy referring to a software gateway called Sipmerge, but I'm guessing that product is no longer available since it doesn't show up when I do a simple Google search on it. Has anyone out there made any headway on this issue and does anyone have any advice for someone that is about to dig into this topic?

Thanks in advance for any responses,

Quin
 
Exchange 2010 is just in trial so you can not expect it to work with anything !
Exchange 2007 and UM needs a 3th party to get full functionality
So i guess that will also be the case for 2010 in the feature




ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Exchange 2010 RTM was released last month. It is no longer a Release Candidate or Beta. I am running the final version in production on my server and on the servers of two of my clients. It works quite well.
 
I believe it runs well but RTM is still not official
Avaya has a policy to support within 6 months after the release
I hear stories about upgrading from 2003 straight to 2010 and skip 2007 because it is so much better





ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
tlpeter - RTM is release to market. its the final / official release.

exch 2010 is available on technet as a final release.

exch 2007 is great when its working but when it breaks, be prepaired to spend hours on the phone to MS technical support, typing loads of commandlets.

lets hope 2010 is a step beyond 2003 and not a step back.
 
I haven't been able to find a lot of answers on this issue and I was hoping that things might be different now with Exchange 2010. With that attitude I decided to burn a few hours reinventing the wheel on this problem. I have attached a link to a SIP trace from the Avaya Monitor program that shows the result of my efforts. I think that I have a codec issue that I can't get around.

Here is a list of settings that I am using in my environment:

IP Office R5 [5.0(15)] - IP Address: 192.168.81.200
Exchange 2010 UM/Windows 2008 R2 - IP Address: 192.168.81.8
SIP Line (Line Group 5) to 192.168.81.8 - TCP 5065
Testing Short Code 7N; --> Dial --> N"@192.168.81.8" --> Line Group 5

It turns out that Exchange redirects all incoming traffic on TCP port 5060 to port 5065 using a '302 Moved Temporarily'. I got around this by configuring my SIP Line to use a 'SEND Port' of 5065. Apparently Exchange is OK with this and the SIP trace shows what looks like a healthy call.

Unfortunately I never hear anything when Exchange answers the call. I tried forcing Exchange and IP Office to use G.711u then G.711a and then G.723.1. I used the WiredCodecList registry entry on the Exchange box to force the issue (along with the 'VoIP' properties on the SIP Line). I also turned off 'Allow Direct Media Path' on my testing extension because I thought that might be introducing a problem.

No matter what I do I can never get any audio from the Exchange box even though it looks like the call is connecting and the codecs are negotiating properly. Does anyone out there have any insight into what else might be causing a problem here? I feel like I am really close to getting some basic functionality here but I think I am missing something.

Quin

 
 http://www.bntwk.com/avaya/SIPTrunk-to-Exchange2010.txt
You might have a look at this:


Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top