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!

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

IMS and R3.0.44

Status
Not open for further replies.
Morrack

Morrack

Vendor
May 13, 2004
1,264
CA
Has anyone, anywhere on the planet, gotten IMS to work properly with R3.0.44 firmware???

Even better, has anyone gotten it to work when using outlook 2003? According to Avaya Tek-tip#80 Outlook 2003 is supported as long as you don't use cached mode, which I am not. But the planets must not be lined up properly because I either get an 80050007 error and it won't connect, or after much fiddling with dcom (and having outlook open on the VMPro server and opening Outlook BEFORE launching phone manager) I manage to get it to connect but then it won't actually play the message over the phone - phone rings and says invite, goes offhook, and nothing.

I'm getting ready to do some serious Avaya bashing over this, and that's something I'm usually pretty good about restraining myself from.

Anybody - HELP!! At this point I'd even like to hear from anyone that also tried and failed with IMS and 3.0.44.

Worst part is this client LOVES IMS and can't figure out why it used to work so well and we can't get it to work ever since we "upgraded" them. And now that they've been sold 54xx phones downgrading isn't even an option.




Peter Sherwood

Morrack Consulting
 
Sort by date Sort by votes
I've got it working in my demo area - that is after an inital install of 2.1(27). Since then I upgraded to V3 beta, 3.0(40), 3.0(44) just upgrading all the way and it seems to be fine.

Only using Outlook XP at the moment though

That probably hasn't helped you at all - sorry, but it is working
 
Upvote 0 Downvote
Actually it has helped me in that at least I know I should keep plugging away at it. You didn't have to adjust anything after upgrading at all?

The weird thing is this client has been working fine with IMS since 1.4, and it simply stopped working after upgrading from 2.1.35 (which it worked on) to 3.0.40; upgrading to 3.0.44 was no help at all.

I even tried downgrading a single client PC to Outlook 2000 to no avail - although the VMPro server has Outlook 2003 running on it. I've tried outlook 2000 on the server with outlook 2003 on the clients to no avail but haven't tried 2000 on both server and clients - but 2003 is supposed to bloody work as long as you don't use cached mode.

Getting frustrated if you can't tell :)

Thank you for responding.





Peter Sherwood

Morrack Consulting
 
Upvote 0 Downvote
Just to check...are all your services running? VM Pro, IMS gateway etc?

I've found a few times they just stop....usually after the VMProsvc.exe crashes (happens quite a bit in my demo system and so VM Pro is neither in IP Office or Intuity mode - can't even select it in prferences - anyone else had this problem?)
 
Upvote 0 Downvote
How about rebuilding the VM Pro server from scratch...I bet that would sort it out.
 
Upvote 0 Downvote
Yes and tried it to all the above. All the services are running, and I rebuilt the VMPro box with 2003 server OS (was XP Pro SP2) just in case but still no joy.

What kills me is when I finally can get a client to authenticate, and then the phone disconnects after going off-hook to play the message.

If you have any more ideas keep 'em coming! :)



Peter Sherwood

Morrack Consulting
 
Upvote 0 Downvote
hey you know, I found that I had to do registry hacks and give the IMS registry keys credentials it hadn't already asked for and BANG, it started working
 
Upvote 0 Downvote
hohumIPO what registry keys did you change? What credentials did you add? Are you referring to the client PC's or the server PC?



Peter Sherwood

Morrack Consulting
 
Upvote 0 Downvote
I got it to work with 3.0.44 firmware. You need your vmpro to be on 3.0.15 and don't just uninstall the previous version you must completly remove the vmpro folder from c:\program files\avaya\ip office\vmpro. Then install 3.0.15 it should work after that.
 
Upvote 0 Downvote
Hey Morrak,
We found the easiest way to fool it into working was to use the IMS client that ships with the 2.1(35) firmware. I don't understand why but..... it just does. the settings I was referring to in the registry are on the client PC's, IMS client key, in there there is an additional User name key that I frigged around with in conjunction with the password field it helped in one circumstance
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

BernPed
  • Locked
  • Question
Ring Central and Avaya 9
Replies
8
Views
908
telecomtekperson
T
ipohead
  • Locked
  • Question
ICR and multiple accounts
Replies
6
Views
633
ipohead
ipohead
X
  • Question
Paging with dial and dial paging together
Replies
3
Views
325
TouchToneTommy
TouchToneTommy
hibroth
  • Locked
  • Question
Avaya SPACES EoS and Pepix ?
Replies
3
Views
385
sizbut
sizbut
Scuzzie2k
  • Locked
  • Question
IP Office 500 and Avaya Workplace 1
Replies
6
Views
614
derfloh
derfloh

Part and Inventory Search

Sponsor

Back
Top