Thursday, January 02, 2014

Understanding the Oracle Communications product portfolio

A little less then a year ago Oracle completed the purchase of Acme Packet. "Acme Packet enables trusted, first-class delivery of next-generation voice, data and unified communications services and applications across IP networks for service providers and enterprises. The company's solutions are deployed by more than 1,900 service providers and enterprises globally, including 89 of world's top 100 communications companies".

By purchasing ACME Packet Oracle has extended its product portfolio extensively and create the Oracle Communications product group. The current Oracle Communications product group is shown below in overview diagram;

The current naming of the products within the Oracle Communications product group can be a bit strange for people who are used to the original naming used by ACME Packet. For them, and for people working with Oracle Communications products it can be good to have some understanding of how Oracle has grouped products in the product group and sub product groups.

In general Oracle Communications is buildup out of 4 main product groups, Hardware, Network Session Delivery and Control Infrastructure, Enterprise Communications and Network Visibility and Resource Management. The last product group, the Network Visibility and Resource Management group is divided in two separate sub groups; Oracle Communications Session Delivery Manager and Oracle Communications Session Monitor.

When looking at the Oracle Communications website the total reach of the product portfolio is a lot bigger then what you can see above and the full integration possibilities become clear. By combining the products from "pure" Oracle Communication and combining them with other products from Oracle you can build a near red-stack solution for your entire communication delivery within your enterprise or have it as your core business to end-users outside of your company.

It is a shame that this part of Oracle is overlooked and it is especially a shame that it is overlooked by a lot of the integration and solution architects who design software solutions and commonly stop where direct communication is needed between humans and we leave the computer-to-computer communication.

No comments: