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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya is Avaya - Unfortunately IP Office is something else... 1

Status
Not open for further replies.
Totally different business sector ddrib, an SBS server will not do half the stuff a fully redundant distributed server envoirmoent will but it's not meant to. Also half of that is just marketing talk, let's see the actual costs both monitary and enginnering/support time to deliver that kind of service, it's not what the IP office is aimed at at all :)

ACS - IP Office Implement

"What the Crocodile Hat....was that?
 
Since you mention the SBS Server, MS still years ahead of Avaya, even though a different business sector SBS, Windows Server Std or Ent. are all the same platform, also fully support the same MS descktop/client for all “business sector”, all teams are working together to deliver a unique experience. Avaya “IP Office” team could deliver much more in their software release if they were communicating with their colleagues from others business sectors, less effort/developing for the team to deliver .
A good example is the 96XX series, a modern state of art handset not compatible with IP Office even in release 5.0. It’s a shame.
If this is a marketing strategy. results is to sell less IP Office, even worst to let all competitor a step ahead.
 
If you can't sell Avaya IP Office then don't.
The majority of the SMB market still use win2k3 server and windows XP because that works well and there is no need to invest in new hardware/software.
We sell a lot ipo and only rarely we encounter this as a problem.
Costs is a big issue in SMB market, more important as fancy phones ( the 96xx series are very expensive ) or state of the art computer hardware/software.
My "unique experience" with MS seems to be another as yours...
It would be nice if everything is perfect but not at all costs.
 
FYI...

96XX series phones will be supported on R6
 
Ssssch... isn't that a secret still? =)

Although 96xx phones are nice SMB cust probably rather buy 16xx cause they are cheaper and then complain about the lack of functions =)

"Trying is the first step to failure..." - Homer
 
I have been hearing that the 96xx phones will be supported in the next release for 2 years. It would be a nice option alot pricier. the 16xx are horrible but cheap.
 
I'm not comparing MS and Avaya, just mentioned that from a product perspective MS manage to deliver a platform for many segments and Avaya/IP Office team should try more of that.

When I mentioned the 96xx it was only one example, but I also think the Phone Manager is pretty crap comparing with what the competitors is offering by now, IP Office One-X is times behind enterprise segment, APIs to software develop for IP Office aren't good enough and so on.

I love IP Office and I'm not here to criticise only, I just want more and more... faster...
 
One major new release of IP Office per year isn't fast enough? :)

I agree though there are some major features that Avaya needs to push out more quickly. Exchange 2007 UM integration, direct OCS support (although you get it from 3rd party today I'd like to see it with an Avaya name). 1XP will see a pretty big face lift in R6 (keep in mind it is at version 1 today). If nothing else I'd like to see better support for SIP stations and none of this 3rd party crap we got today.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M,
ACE Implement: IP Office
TIA-CTP, MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
direct OCS support (although you get it from 3rd party today I'd like to see it with an Avaya name)
Kyle, any chance you could point me towards this third party product?

I've been asked to look into this for a client?

is it version specific? they are running a pb of 4.0 and are very reluctant to move from that version...

See what my brain does when it's not thinking about phones.
 
Tom, you need to be at 5.0 to get it working a bit easier
That is because of the wildcard you can use in the sip uri



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 is talking about supporting OCS via SIP internal to the IP Office. This is limited and doesn't provide full integration. Alternatively, Zeacom has a full integration solution for IP Office and OCS.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M,
ACE Implement: IP Office
TIA-CTP, MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Thanks Kyle. I'll take a look. Do you know if they operate outside the US?

See what my brain does when it's not thinking about phones.
 
Their contact page lists non-US locations so I would assume yes.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M,
ACE Implement: IP Office
TIA-CTP, MCP/MCTS Exchange 2007
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top