Communications Manager Release - Networking, Cloud, And .

2y ago
15 Views
2 Downloads
4.53 MB
107 Pages
Last View : 21d ago
Last Download : 4m ago
Upload by : Mariam Herr
Transcription

Application NoteAlcatel-Lucent OmniPCX R11.1 using SIP trunk toCisco Unified Communications Manager Release10.5.2 SU3Application NoPage 1 of 107

Table of ContentsIntroduction . 4The following items were tested: . 4Listed below are the highlights of the integration issues: . 4Below are the key results:. 5Network Topology . 5Basic Call Setup. 5Limitations . 5System Components. 7Hardware Requirements . 7Software Requirements . 7Features . 8Features Supported . 8Features Not Supported or Not Tested . 8Configuration . 9Configuring Sequence and Tasks: . 9Configuring the Alcatel OmniPCX . 10Alcatel Software Version, capacity and Licensing . 10Access the Alcatel-Lucent OXE Manager . 10Configure IP Domain . 12Configure SIP Trunk Group. 12Trusted IP Addresses List . 14Configure SIP Gateway. 14Configure SIP External Gateway for CUCM Subscriber . 15Configure SIP External Gateway for CUCM Publisher . 17Configure Network Routing Table . 20Configure Prefix Plan – Pointing to Cisco Phones. . 20Configure Prefix Plan – Pointing to Cisco Voice Mail Pilot Number. . 21Configure Privacy . 22Configure Call Park . 24Page 2 of 107

Configure G729 Codec . 26Configure NOE user. 26Configure SIP user . 27Configuring the Cisco Unified Communications Manager . 30Cisco Unified Communications Manager SIP Trunk Security Profile . 31Cisco Unified Communications Manager SIP Trunk Security Profile for Unity Connection. 32Cisco Unified Communications Manager SIP Profile . 32Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration . 38Cisco Unified Communications Manager SIP Trunk to Cisco Unity Connection Configuration . 44Cisco Unified Communications Manager Service Parameter . 50Cisco Unified Communications Manager Device Pool Configuration . 51Cisco Unified Communications Manager Region Configuration. 56Cisco Unified Communications Manager Media Resource Group. 59Cisco Unified Communications Manager Media Resource Group List . 61Cisco Unified Communications Manager Route Pattern to Alcatel . 63Cisco Unified Communications Manager SIP Phone Device Level Configuration. 65Cisco Unified Communications Manager SCCP Phone Device Level Configuration . 78Cisco Unified Communications Manager Audio Codec Preference List Configuration . 85Cisco UCM Extent and Connect. 88Cisco UCM end user configuration . 88Add Phone: CTI Remote Device . 91Remote Destination Configuration . 93Cisco UCM UC service Configuration . 94Cisco UCM service Profile Configuration . 94Cisco Unified CM IM Presence – CCMCIP Profile Configuration . 96Cisco UCM – SIP trunk to Cisco IM&Presence Trunk Configuration . 97Cisco Unity Connection . 101Cisco Unity Connection Telephony Integration . 101Cisco Unity Connection User Configuration. 104Acronyms . 107Page 3 of 107

IntroductionThis document describes the steps and configurations necessary for Cisco Unified CommunicationsManager (Cisco UCM) release 10.5.2 to interoperate with the Alcatel-Lucent OmniPCX Release 11.1 usingSIP Early-Offer.The following items were tested: Basic call between the two systems and verification of voice path, using both SIP and NOE on theAlcatel side, and SIP and SCCP IP phones on the Cisco side (Refer to limitation section for more info) CLIP/CLIR/CNIP/CNIR features: calling party Name and number delivery (allowed and restricted)(Refer to limitation section for more info) COLP/CONP/COLR/CONR features: connected Name and number delivery (allowed and restricted)(Refer to limitation section for more info) Call transfer: attended and early attended (Refer to limitation section for more info) Alerting Name Identification (Refer to limitation section for more info) Call forwarding: call forward unconditional(CFU), call forward busy (CFB), and call forward noanswer (CFNA) Hold and resume with music on hold Three-way conferencing (Refer to limitation section for more info) Voice messaging and MWI activation-deactivation (Refer to limitation section for more info) Audio Codec Preference List Extend and Connect (Refer to limitation section for more info) Call Park (Refer to limitation section for more info)Listed below are the highlights of the integration issues: Basic calls work from Cisco UCM to Alcatel OmniPCX and vice versa. Audio and ring back tone issuesare observed with Alcatel SIP phones. Caller name and number is not updated correctly for basic calls and in the attended and unattendedtransfer scenarios. The Alcatel OmniPCX mid call INVITE and 200 OK messages do not contain “PAI”and “user part” in the “Contact” header or “From” header, causing the issue. CLIR/CNIR—the Alcatel OmniPCX SIP trunk does not support connected Name and numberrestriction. Restriction of calling number on Alcatel NOE and SIP phones is achieved by configuringthe “Phone Features Classes of Service” with “External Services Secret/Identity” set to “YES” andassigning this class of service to the User under test. COLR/CONR—as with calling Name and number presentation restrictions, the Alcatel OmniPCX doesnot support connected Name and number restriction on SIP trunks.Page 4 of 107

For call forwarding scenarios where the Alcatel station is the forwarding station, it is required thatthe Cisco UCM have the “Redirect by Application” checkbox enabled in the SIP Profile used by theSIP Trunk to the Alcatel PBX. Retrieval of a parked call on the Alcatel PBX from the Cisco UCM is not supported. Video calls between the Alcatel OmniPCX users and the Cisco UCM users is not supported.Below are the key results: Basic call, call transfer, call forwarding, conference call, and hold and resume tested successfullywith a few caveats and limitations. Centralized voicemail, using Unity Connection server integrated with Cisco UCM via SIP was usedfor testing. This voicemail solution can provide centralized voicemail services, supporting bothAlcatel and Cisco end-users.Network TopologyBasic Call SetupLimitationsThese are the known limitations, caveats, or integration issues: Although the Codec Preference List is used and the INVITE message displays the right codec, AlcatelOmniPCX responds to the INVITE with its preferred Codec Preference for the call.Page 5 of 107

Alcatel OmniPCX SIP does not update the caller ID (connected Name) for a basic or privacy enabledcall from the Cisco UCM. Therefore, only the connected party number is displayed on the Cisco UCMPhone. Alcatel does not send a privacy header in “200 OK” to Cisco UCM for connected name on restrictedcalls. The caller ID on the Cisco Phones therefore displays “SIP” or “MASK IDENTITY” instead of“Anonymous/Private”. Even though the Alcatel OmniPCX sends Privacy header as Privacy: user; id and from header asanonymous@anonymous.invalid, the Alcatel PBX fails to update its privacy header after the CiscoUCM initiates a transfer. This is due to the difference in the way the two systems handle passing ofthe restricted information across SIP Trunk. The caller name is not updated in transfer/conference scenarios. This is an Alcatel OmniPCX issuebecause even though the mid call INVITE and UPDATE messages sent by Cisco UCM after thetransfer/conference contain PAI and RPI, the Alcatel PBX fails to update this information on itsendpoints. There is no ring back tone heard on Alcatel SIP phones for a basic outbound call from AlcatelOmniPCX to the Cisco UCM phones. In a transfer scenario where the Alcatel SIP phone completes an attended transfer, there is no audiobetween the connected parties. Also, the call gets disconnected about 20 seconds after the transferis complete. In a transfer scenario, where the attended transfer is made to an Alcatel SIP phone, if the transferis initiated by a Cisco UCM SIP phone, there is one-way audio if the connected party also is a CiscoUCM phone (legacy or SIP). The Alcatel SIP Phone cannot hear the connected party. In a transferscenario where the Cisco UCM phone transfers a call from an Alcatel user to another Alcatel user,there is no audio once the transfer is complete. Configuring “Set Ignore inactive/black hole” to Truein SIP External Configuration page resolves this issue. There is currently no support for Video Capability on the OXE. In a Conference call scenario where the conference is initiated by an Alcatel SIP phone, theremaining parties are disconnected from the conference once the Alcatel SIP phone disconnects orleaves the conference. In all call forwarding scenarios where the Alcatel station is the forwarding station, it is required thatthe Cisco UCM have the “Redirect by Application” checkbox enabled in the SIP Profile used by theSIP Trunk to the Alcatel PBX. All external call forward attempts would otherwise fail. Call forward from the Alcatel OmniPCX to Cisco UCM fails with an “extend and connect” (CTIRD)configured user. Even though the “302 Moved temporarily” is triggered from Alcatel with thecorrect contact information (Contact: sip:5000@10.80.10.3;user phone ) the call is notterminated on the desired Cisco UCM phone/destination. This issue has been identified as a defectand will be addressed in future releases, tracked against defect ID CSCva13893. MWI : The MWI lights up on the Alcatel NOE phone when a user leaves a voicemail for the user.However, on the device, this indication is stored not against a new voicemail, but against acallback to the voicemail pilot number. The user can successfully retrieve and delete the newPage 6 of 107

voicemail. However, the MWI turns off only after deleting the “callback” entry or calling thevoicemail pilot number from that menu. MWI does not light up on the Alcatel SIP phones. The Alcatel OmniPCX does not support Call Retrieval of a parked call on the local PBX by users onan external node. Therefore; any phone / user on the Cisco UCM cannot retrieve a call that is parkedon the Alcatel OmniPCX. In a call forward scenario involving multiple hops, if a Cisco user calls an Alcatel phone that isconfigured in call forward loop, the call fails and never reaches any target destination.Scenario : PBX A CCM; PBX B Vendor PBX; PBX C CCMAction: Station B.1 activates Call Forwarding All to Station C.1.Action: Station C.1 activates Call Forwarding All to Station B.2.Action: Station B.2 activates Call Forwarding All to Station A.2.Action: Station A.2 activates Call Forwarding All to Station B.1.Action: Station A.1 calls station B.1.System ComponentsHardware RequirementsThe following hardware was used Cisco UCS-C240-M3S VMWare Host Cisco 7965,7975 ,7960, 8945, 9951, and 9971 IP phones Alcatel-Lucent NOE phones 4038, 8068 and SIP phones 4008 and 4018Software RequirementsThe following software is required: Cisco UCSC-C240-M3S VMware vSphere Image Profile: ESXi-5.5.0-1331820-standard Cisco Unified Communications Manager release 10.5.2.13900-12 Cisco Unified Communications Manager IM & P release 10.5.2.13900-12 Cisco Unity Connection release 10.5.2.13900-12 Cisco Jabber 11.6.0 Build 35037 Alcatel-Lucent OmniPCX Enterprise R11.1Page 7 of 107

FeaturesThis section lists supported and unsupported features. No deviation from the configuration presented inthis document will be supported by Cisco. Please see the Limitations section for more information.Features Supported CLIP—calling line (number) identification presentation CLIR—calling line (number) identification restriction CNIP—calling Name identification presentation CNIR—calling Name identification restriction Alerting Name Attended call transfer Early attended call transfer CFU—call forwarding unconditional CFB—call forwarding busy CFNA—call forwarding no answer COLP—connected line (number) identification presentation COLR—connected line (number) identification restriction CONP—connected Name identification presentation CONR—connected Name identification restriction Hold and resume Conference call MWI—Message Waiting Indicator (lamp ON, lamp OFF) Audio Codec Preference List Call Park/Pickup(see limitation section) Extend and ConnectFeatures Not Supported or Not Tested Call completion (callback, automatic callback) Shared Line - Hold & Resume with MOH Blind transfer Video callsPage 8 of 107

ConfigurationThe goal of this guide is to provide an overview of the integration between Cisco Unified CommunicationManager and Alcatel OmniPCX PBX’s. The deployment will interconnect the UC systems using SIP. NoPSTN connectivity has been tested with this integration. The following sections provide the requiredconfigurations for a successful integration.Configuring Sequence and Tasks:Alcatel OmniPCX:Verify Alcatel-Lucent OXE LicensesAccess the Alcatel-Lucent OXE managerConfigure IP DomainConfigure SIP Trunk GroupConfigure GatewayConfigure SIP External Gateway – Cisco UCM Subscriber/PublisherConfigure Network Routing TableConfigure Prefix Plan – Cisco Extension/Voice mailConfigure G729 CodecConfigure PrivacyConfigure Call ParkConfigure NOE userConfigure SIP UserCisco Unified Communications Manager:SIP trunk security profileDevice setting SIP profileMedia resource group and media resource group listAssign media resource group list (MRGL) in the default device poolSIP trunk to Alcatel PBXSIP Trunk to Cisco Unity ConnectionAssign User in Cisco Unity ConnectionSIP and SCCP phones device configurationRoute pattern to the Alcatel PBXCall Manager Service Parameter “Duplex Streaming Enabled” set to “True”Audio Codec Preference, Region and device pool ConfigurationExtend and Connect Feature and User configurationCisco Unity Connection:Cisco Unity Connection Telephony IntegrationCisco Unity Connection User ConfigurationPage 9 of 107

Configuring the Alcatel OmniPCXAlcatel Software Version, capacity and LicensingFrom the CLI prompt, use the spadmin command and from the menu shown, select option 2,Ensure that the system has enough licenses available against the SIP Gateway, Advanced IP users, SIPusers, Standard IP users with respect to the configuration requirement.Access the Alcatel-Lucent OXE ManagerEstablish a Telnet connection to the CS board of the OXE. At the CLI prompt type mgr. A menu is thenpresented.Page 10 of 107

Page 11 of 107

Configure IP DomainNavigation: IP IP domainIP Domain Name: lab.tekvizion.com, this is used in this exampleClick ctrl v to complete.Configure SIP Trunk GroupNavigation: Trunk Groups CreateNode Number: 101, this is used in this exampleTrunk Group ID: 1, this is used in this exampleTrunk Group Type: T2Trunk Group Name: SIPRemote Network: 15, this is used in this exampleQ931 Signal variant: ABC-FT2 Specification: SIPAssociated Ext SIP gateway: 2Page 12 of 107

Page 13 of 107

Trusted IP Addresses ListNavigation: SIP Trusted IP Addresses Review Modify All InstancesThe IP address of the Cisco UCM publisher and subscriber is added to the Trusted IP Addresses List.Configure SIP GatewayNavigation: SIP SIP GatewayNode Number: 101, this is used in this exampleSIP Trunk Group: 1, this is used in this exampleIP Address: 10.70.50.6, this is used in this exampleDNS local domain name: lab.tekvizion.com, this is used in this exampleSIP DNS1 IP Address: 10.64.1.3, this is used in this examplePage 14 of 107

Configure SIP External Gateway for CUCM SubscriberNavigation: SIP SIP External Gateway CreateNode Number: 101, this is used in this exampleSIP External Gateway ID: 1, this is used in this exampleSIP Remote domain: 10.80.10.3(CUCM subscriber IP), this is used in this exampleTrunk group number: 1, this is used in this exampleMinimal authentication method SIP none, this is used in this exampleDynamic Payload type for DTMF: 101Outbound Calls 100 REL SupportedIncoming Calls 100 REL Not RequestedP-Asserted-ID in Calling Number TrueTrusted P-Asserted-ID header TrueDiversion Info to provide via DiversionType of codec negotiation Default, this is used in this exampleIgnore inactive/Black hole True, this is used in this examplePage 15 of 107

Page 16 of 107

Configure SIP External Gateway for CUCM PublisherSIP Remote domain: 10.80.10.2 (CUCM PUBLISHER)Navigation: SIP SIP External Gateway CreateNode Number: 101, this is used in this exampleSIP External Gateway ID: 1, this is used in this exampleSIP Remote domain: 10.80.10.2, this is used in this exampleTrunk group number: 1, this is used in this exampleMinimal authentication method SIP none, this is used in this exampleDynamic Payload type for DTMF: 101Outbound Calls 100 REL SupportedIncoming Calls 100 REL Not RequestedP-Asserted-ID in Calling Number TrueTrusted P-Asserted-ID header TrueDiversion Info to provide via DiversionType of codec negotiation Default, this is used in this exampleIgnore inactive/Black hole True, this is used in this examplePage 17 of 107

Page 18 of 107

Page 19 of 107

Configure Network Routing TableNavigation: Translator Network Routing TableNode Number: 101, this is used in this exampleProtocol Type: ABC-FARS Route List: 5, this is used in this exampleAssociated Ext SIP Gateway: 2, this is used in this exampleConfigure Prefix Plan – Pointing to Cisco Phones.Navigation: Translator Prefix plan CreateNode Number: 101, this is used in this examplePrefix Meaning Routing No.Network Number: 10, this is used in this exampleNode Number/ABC-F Trunk Group: 1, this is used in this exampleNumber of Digits: 4Note: Cisco extension are started with 5 as prefix digit.Page 20 of 107

Configure Prefix Plan – Pointing to Cisco Voice Mail Pilot Number.Navigation: Translator Prefix plan CreateNode Number: 101, this is used in this examplePrefix Meaning Routing No.Network Number: 10, this is used in this exampleNode Number/ABC-F Trunk Group: 1, this is used in this exampleNumber of Digits: 4Note: Cisco Voice mail pilot number started with 7 as prefix digit.Page 21 of 107

Configure PrivacyPrivacy for particular userNavigation: mgr user Descend hierarchy Dynamic State User Review/ModifySet Consistent with Identity: False i.e., Secret Identity EnabledEnable Privacy in Entity Privacy for particular userNavigation: mgr Entities Review/Modify Entity Number:Set Caller ID Secret: Yes (i.e., Secret Identity enabled in whole entity that includes sip trunk & users)Page 22 of 107

Enable Privacy in COSNavigation: mgr Classes of service Phone Features COS Review/modifyNode Number: 101, this is used in this example.Instance (reserved):1, Phone Features COS: 1Rights Mask Id. name only for ext. Calls: set to 0 . This is used in this example.Page 23 of 107

Configure Call Parka. Authorization : To enable the rights on the user to be able to use the call park/retreive featureNavigation: Classes of Service Phone Features COS Review/Modify External Services ParkCall/Retrieve: 1Page 24 of 107

b. Prefix Definition: Configure a prefix or verify if the system has a default prefix configuration thatis used for activating the parking function and retrieving the parked call.Navigation: Translator Prefix Plan Review/Modify *75c. Operationi.ParkingWith a call in progress:1. Dial the parking prefix and wait for the voice guide.2. Dial the number of the set on which you wish to park the call.3. The PBX confirms your action by voice guide.4. Hang up.ii.Retrieving the parked callTo retrieve a parked call from any set:1. Hang up.2. Dial the parking prefix and wait for the voice guide.Page 25 of 107

3. Dial the number of the set on which the call was parked.Note: To retrieve the parked call from the same set the call was parked on, dial the parking prefix.Configure G729 CodecNavigation: IP IP Domain Review/Modify 0Node Number: 101, this is used in this exampleIP Domain Name: lab.tekvizion.comIntra-domain Coding Algorithm Without CompressionExtra-domain Coding Algorithm With CompressionConfigure NOE userNavigation: Users CreateNode Number (reserved): 101Directory Number: 4004Directory name: NOE USER1Set Type IPTouch 4038/8038, this is used in this examplesPage 26 of 107

Configure SIP userNavigation: Users CreateNode Number (reserved): 101Directory Number: 4004, this is used in this examplesDirectory name: ALU SIP1, this is used in this examplesSet Type SIP extension, this is used in this examplesPage 27 of 107

URL Username: 4003URL Domain: tekvizionoxeSIP Authentication: 4003SIP Password: ******Confirm: ******Page 28 of 107

Page 29 of 107

Configuring the Cisco Unified Communications ManagerCisco Unified Communications Manager Software VersionPage 30 of 107

Cisco Unified Communications Manager SIP Trunk Security ProfileNavigation: System Security SIP trunk security profileSet Name* Non Secure SIP Trunk Profile. This is used for this example.Set Description Non Secure SIP Trunk Profile authenticated by null StringCheck Accept out of dialog referCheck Accept unsolicited notificationAll other values are default.Note: Alcatel sends refer-to with replaces header for transfer scenarios, Cisco sends 403 forbidden butthere were no issues in the call flow.Page 31 of 107

Cisco Unified Communications Manager SIP Trunk Security Profile for Unity ConnectionSet Name* Non Secure SIP Trunk to VM Profile. This is used for this example.Set Description this text is used to identify this SIP Trunk Security Profile.Check Accept presence subscriptionCheck Accept out of dialog refer**Check Accept unsolicited notificationAll other values are default.Cisco Unified Communications Manager SIP ProfileNavigation: Device Device Settings SIP ProfileSet Name* ALU - Standard SIP Profile. This is used for this example.Set Description this text is used to identify this SIP Profile.Check Disable Early Media on 180Check Redirect by ApplicationPage 32 of 107

All other values are default.Page 33 of 107

Cisco Unified Communications Manager SIP Profile (Continued)These values are default.Set SIP Rel1XX Options* Send PRACK if 1xx Contains SDPAll other values are default.Page 34 of 107

Cisco Unified Communications Manager SIP Profile (Continued)Page 35 of 107

Cisco Unified Communications Manager SIP Profile (Continued)Page 36 of 107

Cisco Unified Communications Manager SIP Profile (Continued)Early Offer support for voice and video calls: Mandatory (insert MTP if needed)Check Enable OPTIONS Ping to monitor Destination status for Trunks with Service Type "None (Default)"Check Send send-receive SDP in mid-call INVITEAll other values are default.Page 37 of 107

Cisco Unified Communications Manager SIP Trunk to Alcatel ConfigurationNavigation: Device TrunkSet Device Name* ALU. This is used for this example.Set Description this text is used to identify this Trunk Group.Set Device Pool* G711 Preferred. This is used for this exampleSet Call Classification* Use System Default. This is used for this exampleSet Media Resource Group List MRGL NoMTP. This is used for this exampleAll other values are default.Page 38 of 107

Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration (Continued)All other values are default.Page 39 of 107

Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration (Continued)Page 40 of 107

Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration (Continued)Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration (Continued)Check Redirecting Diversion Header Delivery - OutboundAll other values are default.Page 41 of 107

Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration (Continued)Set Destination Address 10.70.50.6. This is used in this example.Set SIP Trunk Security Profile* Non Secure SIP Trunk ProfileSet SIP Profile* ALU – Standard SIP ProfileSet DTMF Signaling Method* No PreferenceAll other values are default.Page 42 of 107

Cisco Unified Communications Manager SIP Trunk to Alcatel Configuration (Continued)Page 43 of 107

Cisco Unified Communications Manager SIP Trunk to Cisco Unity ConnectionConfigurationNavigation: Device TrunkSet Device Name* CUC. This is used for this example.Set Description this text is used to identify this Trunk Group.Set Device Pool* DefaultAll other values are default.Page 44 of 107

Cisco Unified Communications Manager SIP Trunk to Cisco Unity Connection Configuration(Continued)Check Run On All Active Unified CM NodesAll other values are default.Page 45 of 107

Cisco Unified Communications Manager SIP Trunk to Cisco Unity Connection Configuration(Continued)Check Redirecting Diversion Header Delivery - InboundAll other values a

Hardware Requirements The following hardware was used Cisco UCS-C240-M3S VMWare Host Cisco 7965,7975 ,7960, 8945, 9951, and 9971 IP phones Alcatel-Lucent NOE phones 4038, 8068 and SIP phones 4008 and 4018

Related Documents:

4 Release Notes for Cisco Unified Communications Manager Release 8.5(1) OL-23282-01 System Requirements Note Make sure that the matrix shows that your server model supports Cisco Unified CM Release 8.5(1). Note Be aware that some servers that are listed in the Cisco Unified Communications Manager Software Compatibility Matrix may require additional hardware support for Cisco Unified CM Release .

sites cloud mobile cloud social network iot cloud developer cloud java cloud node.js cloud app builder cloud cloud ng cloud cs oud database cloudinfrastructureexadata cloud database backup cloud block storage object storage compute nosql

For Cisco Unified Communications Manager Release 5.0 or earlier, see Bulk Administration Tool User Guide for Cisco Unified Communications Manager for detailed instructions about BAT and TAPS. For Cisco Unified Communications Manager Release 6.0 or later, see Cisco Unified Communications Manager Bulk Administration Guide. Related Topics

The Cisco Unified Communications Manager Adapter pr ovides connectivity between the IBM Security Identity server and the Cisco Unified Communications Manager server . The adapter r uns as a service, independent of whether you ar e logged on to IBM Security Identity Manager . The Cisco Unified Communications Manager Adapter automates the following

Data Communications and Networking Overview, Overview, Data Communication vs Networking, Distributed Systems vs Networks, Simplified Communications Model, Data Communications: Example, Communications Tasks, Types of Networks, An Example Configuration, Protocol Layers, A Sample Protocol Architecture,

If your EM is based on 12c Release 2 Plugin Update 1 (12.1.0.2), then you will see the following release description. If you do not see it, then you have 12c Release 2 (12.1.0.2) released in Sep 2012 Release:Oracle Enterprise Manager Cloud Control 12c Release 2 Plugin Update 1 (12.1.0.2)

Private Cloud Solution Package for Cisco Networking organizations to rapidly deploy the F5 private cloud solution for Cisco Networking, accelerating the migration of existing workloads to a private cloud utilizing BIG-IP i5800 ADC devices and deployment of a BIG-IP VE instance within an L2-7 fabric . Implementing BIG-IP Local Traffic Manager

The Sun News View Release San Jose Mercury News View Release The Miami Herald View Release. Star Tribune View Release CEO World News View Release AZ Central . Poteau Daily News View Release The Evening Leader View Release Wapakoneta Daily News View Release Observer News Enterprise. View Release Valley City Times-Record