Cisco Developer Community

Post your integrated Solutions to the CDN Marketplace

2013-06-19T15:29:03Z

Greetings CDN Members,
as we ramp up to Cisco Live Orlando 2012, there is still time to post or edit your integration solutions and or products.
Be a part of the CDN Marketplace Solutions Catalog!

We noticed that some of you are still not part of our Catalog - lots of promotion activities at the upcoming CL and the CDN Developer Forum so it is available for all to see...and you want to be seen! The CDN Marketplace showcases you by promoting your integrated Cisco-compatible solution.

Call to Action & Five Steps to Success for CDN Members

1. Log into My Developer Dashboard
2. Select ‘Complex Product’
3. Add text to new fields, upload images, upload collateral and take advantage of link to YouTube video
4. Review ‘Preview’ product page
5. Select ‘Post Product’

Detailed screen shots can also be found here: CDN Partner Guide

For additional best practices and how to take advantage of our Marketplace logo, look here

Extending Application Collaboration in the cloud through HCS – Hosted Collaboration Solution

2013-06-19T15:11:29Z

New Developer Center Alert! CDN has launched the new Hosted Collaboration Solution for all of our technology partners and developers interested in application Integration to Cisco UC Cloud Applications, Service Fulfillment, Service Assurance and Billing.
HCS Developer Center

New and Enhanced Go-To-Market Resource Center

2013-06-19T15:06:45Z

Greetings, check the New and enhanced Go-To-Market Resource Center
Go-To-Market Resource Center

GTM RC v2 available now! This is a comprehensive go-to-market planning guide designed to help partners develop a complete GTM plan. You will find useful resource links and valuable tools and tips for engaging Cisco and its reseller partners. Let us know what you think.

CG-NMS Access using Clientless SSL VPN

2013-06-18T01:31:35Z

CG-NMS Access using Clientless SSL VPN

The steps below describe the procedure to access Connected Grid - Network Management Station (CG-NMS) software. Please note that a unique instance of CG-NMS is software is hosted in CG-REDI per partner.

Step 1

Remote Access Client opens web browser to https://173.36.209.69
Select "CG-CDN-Clientless-Users" in Group
Provide credentials and Login

Step 2

Access CG-NMS using the provided Bookmark/URL

SSL VPN connection to CG-REDI for Application Servers

2013-06-18T01:34:19Z

SSL VPN connection to CG-REDI for Application Servers

This blog describes the procedure to setup Cisco AnyConnect Secure Mobility Client based SSL VPN access to the CG-REDI infrastructure. This connection is setup from the Application Server hosted in the partner premises to the CG-REDI infrastructure. The supported Application Server operating systems are:

Microsoft Windows
Apple Mac OSX
Various Linux distributions

If your Application server operating system is not supported, you will still need a VPN connection back to the CG-REDI infrastructure. In this case, refer to the Application Server section here for alternative Application Server setups in the Starter Kit.

The following screenshots run through the setup of Cisco AnyConnect based SSL VPN access to CG-REDI on the Windows platform. Similar steps should be performed for other operating systems.

Step 1:

Open web browser connection to https://173.36.209.69
Select "CG-CDN-AnyConnect-Users" in Group
Provide credentials and Login

Step 2:

Wait for the system to detect the platform (Windows, Mac or Linux) and Java installation
If Java is not found, please install JRE
Download and Install AnyConnect Client Software, by following the prompt on the screen

Step 3

Launch Cisco Anyconnect Secure Mobility Client
Connect to 173.36.209.29 using the AnyConnect software
Provide login credentials
VPN should connect with the following message

Android Studio & The DX650 Add-on

2013-06-12T15:23:24Z

On May 16th, 2013, Google launched an early access preview of Android Studio, a new Android development environment based on IntelliJ IDEA. Android Studio, which can be downloaded here, is available for free on Windows, OS X, and Linux.

Android Studio is currently only available as an early access preview, meaning that several features are either not yet implemented or incomplete. There are currently known issues with installing add-ons on Android Studio. The Cisco DX650 add-on is not currently supported with the early access preview of Android Studio, but we will post a "How To" article when this changes!

Introducing CG-REDI and the new partner development architecture

2013-06-17T22:33:45Z

Connected Grid - Rapid Endpoint Development Infrastructure-as-a-service (CG-REDI)

The Connected Grid Rapid Endpoint Development Infrastructure-as-a-service or CG-REDI, is a collection of cloud-based network infrastructure services, that are hosted at Cisco's DMZ facility and are available to partners signed up in the Cisco-Enabled Grid Devices development center.

A partner will create a Starter Kit at their premises and connect to the CG-REDI infrastructure to obtain hosted services to enable development of their Cisco Connected Grid Endpoints (CGE) and perform Compatibility Verification Testing (CVT).

As part of this new architecture, we have significantly reduced the complexity of the SDK (System Development Kit) Starter Kit. The starter kit has now been reduced to the following elements:

Field Area Router
Windows, Mac or Linux based PC or Laptop
Application Server for hosting client server applications
Endpoint Devices

The following diagram illustrates the topology of the new (Thin) Starter Kit:

The following diagram illustrates the connection of the Starter Kit at the vendor premises to the CG-REDI infrastructure:

The following are the VPN connection types from partner premises back to CG-REDI infrastructure:

IPv6 GRE over IPSec VPN: This connection is created between the FAR (CGR 1000) on partner premises and the ASR1K hosted at the CG-REDI. This connection is REQUIRED for the partner developed CGE to pass the IVT/CVT and be "Cisco Certified". Establishing this connection will require a static globally-routable IP address for the FAR.
SSL VPN: This connection is created between an Application Server hosted at the partner premises (or alternately at a third party SaaS/PaaS infrastructure) and terminates at an ASA at the CG-REDI. This requires the client server to install AnyConnect VPN software client. This connection is OPTIONAL for IVT/CVT and Cisco certification, but required if the partner wishes to communicate from their Application Server(s) to their CGE.
IPv6 GRE over IPSec VPN for Application Server (Optional): This is an alternate VPN service available when AnyConnect based SSL VPN is not an option. This is typically the case, where a non-supported OS is being used or the Application Server is hosted as a platform running customized embedded software. This connection is OPTIONAL for IVT/CVT and Cisco certification, but required if the partner wishes to communicate from their Application Server(s) to their CGE.
Clientless SSL VPN Connection: This connection can be established using a secure browser connection to the ASA appliance. This connects the user to the CG-REDI hosted CG-NMS (Connected Grid Network Management Service) instance. This connection is OPTIONAL for IVT/CVT and Cisco certification, but required if the partner wishes to use the hosted CGNMS to manage their endpoints.

Once the appropriate VPN connections are established, the following can take place:

The Connected Grid Endpoints can access the network infrastructure services like NTP, PKI, DHCPv6 Server, AAA/NPS via the IPSec GRE VPN Tunnel.
The partner's Application Server(s) can connect to the CGE via a tunnel to CG-REDI and then back again through the IPSec GRE VPN connection to their premise-based FAR.
A user at the partner premises (or anywhere) can open a session with their hosted CGNMS instance.

The following services are hosted on CG-REDI:

NTP, DHCPv6, DNS, AAA/NPS, Certificate Authority (CA), Active Directory Services, Active Directory Certificate Services are shared between all partners
A unique instance of CG-NMS is available for each partner for management and IVT/CVT testing

This makes development and integration of partner endpoints into Cisco's Field Area Network architecture even simpler and streamlined! So are you Connected Grid ready yet?

New AXL Notifications Feature in 10.0

2013-05-21T15:31:35Z

AXL Developers:

A new comprehensive AXL Change Notification Feature has been added to our Administrative XML interface in Unified CM 10.0.

Due to scalability issues, the old Notification mechanism introduced in UCM 9.0 has been removed. The old notification feature only supported Users, Phones, and Lines, was never documented, and was not able to scale to meet our needs. Notification requests based on the 9.x mechanism will no longer work when using UCM release 10.0. No alternatives were available. We apologize for any inconvenience this change in direction may cause.

We are 100% confident the new 10.0 Notification feature is the right approach and aligns with our go-forward direction.

Please read the AXL Change Notification page which illustrates how your application can take advantage of this new, powerful feature

Cisco Live Update

2013-05-17T17:12:12Z

Finesse Developers,

Are you excited about Cisco Live in Orlando? We are because we're anxious to share all of the progress that the Finesse team has made over the past year. We also want to provide details on our Finesse 10.0 release.

There are two Finesse sessions this year:

BRKCCT1031 -- Cisco Finesse: Revolutionizing the Agent Experience
BRKCDN1001- Programming with the Finesse API

I will be co-presenting the programming session with Finesse Lead Architect, Gary Olmsted.

Have you built an integration to Cisco Finesse? If so, are you are interested in me showing a slide or two about your product in BRKCCT-1031? I don't provide endorsements or anything like that, but I am happy to make the attendees aware of how our development partners are using the Finesse API. Please send me an email if you are interested.

Ted Phipps
tephipps@cisco.com

Interested in becoming a Cisco Solution Technology Integrator?

2013-05-02T20:58:56Z

A Cisco Solution Technology Integrator (STI) integrates and embeds Cisco products into a solution that it develops, manufactures, sells and supports. STIs can and do operate on a worldwide basis.

STIs are technology and infrastructure solution providers and sell either through their own direct sales force and/or through their reseller channel partners. Contractually, STIs are Cisco Channel Partners because they sign Cisco’s Indirect Channel Partner Agreement (ICPA) and an amendment to it which is the STI contract. However, because of the very nature of STIs and the business relationship Cisco has with them, Cisco’s channel incentive programs, partner certification and specialization requirements do not apply.

STIs, like OEMs, serve as a strategic go-to-market channel for Cisco. STIs give Cisco access to certain market segments and channels of distribution that we may not be privy to or inclined to pursuing ourselves. Additionally, the Cisco ingredient brand "Cisco Technology" is used by STIs along with their own brand to promote their solutions.

The basis for the financial relationship between Cisco and an STI is its annual forecast and past performance. Based on these metrics, discounts are provided to the STI which then purchases Cisco products either through Cisco authorized distributors or upon qualification, directly from Cisco.

The Worldwide Channels team appreciates your interest in the STI go-to-market model. If your company’s strategy has changed and is interested in integrated solution selling please click here and describe the solution, product requirements from Cisco, and provide a business forecast.

Scaling applications when using Notifications

2013-04-30T15:58:01Z

I am glad to see queries coming from developers as they start to develop complex applications using the Unity Connection API.
There are questions when using the notifications about the scale of the new applications being developed.

The developer should plan on doing a scale test to determine the final numbers. The various components that build the solution can provide their numbers, but combining them together can lead to situations which were not clear earlier.

On this page here we have posted what the performance tests on Unity Connection has determined -
docwiki page about scale

Cisco Live US 2013: Register Now for the Developer Forums!

2013-04-26T15:45:28Z

It's hard to believe it's been more than a month since Cisco Live Melbourne. Despite a long flight from the U.S., the experience was wonderful. There is no greater reward than hearing feedback from our partners and learning how the Cisco Developer Network has helped their businesses grow.

Partners I spoke with at the World of Solution during Cisco Live commented on the very high quality of leads generated from the show. My thanks to CDN partners including SolarWinds, Cyara, Nimble Storage, ScienceLogic, OpenText, Jabra, TelStrat, and Netformix who all shared their positive experiences, regarding both the CDN program and Cisco Live experience.

Have you registered for Cisco Live U.S.? This year the event takes place in Orlando, Florida from June 23-June 27. We hope you’ll join us.

As part of Cisco Live, our Developer Forum is a key opportunity for you to meet Cisco leaders and learn about technology advancements and membership benefits. The 1.5 day agenda will focus on your business imperatives and provide information through two focused tracks – technical and business – to ensure you have access to essential product lifecycle information from build to Go-to-Market.

The CDN Developer Forum is complimentary for all CDN members, but a reservation is required. You can register here. The Cisco Live U.S. Explorer Pass is included in your registration and entitles you to World of Solutions access along with keynotes and Super Sessions.

The Developer Forum offers your business development and marketing teams the opportunity to:
• Discuss best practices in identifying routes to market and building the right relationships that will drive Return on Investment (ROI).
• Develop a Channels strategy by identifying and gaining the attention of the right resellers to support your business model
• Learn how to use the Go-To-Market Resource Center to build and execute your Go-To-Market strategy and discover the key tools and assets available through the Resource Center to help your business thrive
• Stay current with CDN program enhancements and information about the 2013 CDN program strategic roadmap

The Developer Forum offers your technical team the opportunity to:
• Gain insight into the technology groups strategic roadmaps
• Increase your expertise in building solutions that leverage Cisco products
• Connect with key technical leads from the various Cisco technology groups

You can register for the Developer Forums here. As always, if you have any questions, please contact the CDN Program Office at cisco-developer-network@cisco.com.

I look forward to seeing you in Orlando.

Beth Bohdanowicz-Jensen
Director, Cisco Developer Network

UCCX Config API Developer Training video

2013-04-18T15:22:00Z

Here is the video of the UCCX Config API Developer Training

https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=65968487&rKey=8194f60c7ffd4b23

"Installing" the Finesse CUIC sample gadget

2013-04-16T21:00:45Z

Finesse gadgets can be hosted on your own web server or on the Finesse server itself.

To host gadgets on your own web server, you host the gadget just as you would any web site. You could use IIS, Apache, etc. That is up to you.

You specify in the Finesse gadget layout (see the Finesse Administration guide) the location for files on the web server where you place the gadget files. For example for the CUIC sample gadget, on Apache web server I place the files in C:\Program Files (x86)\Apache Software Foundation\Apache2.2\htdocs\ so that when I access the web site at http://<host>/CUIC.xml I can retrieve the xml file. The web server knows to retrieve any include files (CUIC.js and CUIC.css and finesse.js and jquery-1.5.min.js) since they are listed in CUIC.xml.

When you upload the CUIC gadget files (either to your own web server or to Finesse) be sure to also upload the required include files as listed in the Readme.txt:

Finesse.js and jquery-1.5.min.js

These files are in the finesse javascript library. Download the file finesse_javascript_library_and_samples_9.1.1.zip on the Tools section of Finesse Documentation page. Unzip the file and use the files that are in \Finesse_9.1.1\samples\GadgetSamples

Then in the gadget layout on the desktop layout tab of the Finesse Administrative desktop, you put the address of the xml file

<gadget>http:<host>/<directory>/CUIC.xml</gadget>

Where <host> is the ip address of the server you have installed to host the gadget files, and <directory> is the location that you would browse to in order to retrieve the files from the web server.

For example my web server is at 10.201.64.72 and the gadget files are in the CUICGadget subdirectory of my htdocs directory,
So my gadget layout has <gadget>http://10.201.64.72/CUICGadget/CUIC.xml</gadget>

You modify the gadget layout using the Administrative login and going to the Desktop Layout tab. See the Finesse Administration GuideFinesse Administration guide for more details.

When Finesse retrieves the gadget xml file, the web server automatically returns any imbedded javascript and css files assuming they are in the same location with the .xml file. These files are spelled out in the CUIC.xml file as files to include.

Alternately you can host the gadget on the Finesse server if you have Finesse 9.1(x) or later . To do this, see the section "Third Party Gadgets" in the Finesse Developer Guide. You would then upload the gadget files to the Finesse server and specify in the Administrative Desktop Layout the following:

<gadget>http://localhost/3rdpartygadget/files/CUIC.xml</gadget>

Where localhost is the Finesse server. The 3rdpartygadget/files directory is where you upload the gadgets using the 3rdpartygadget account and password.

Getting Started with Finesse Gadgets

2013-04-16T20:47:28Z

bMost of the information you need is in this Finesse Developer Center and there is a detailed presentation for Finesse Developers here https://communities.cisco.com/docs/DOC-28452

You can explore the Finesse Developer Center http://developer.cisco.com/web/finesseand if you can’t find what you need, let us know.

For an overview of Finesse and creating Finesse gadgets http://developer.cisco.com/web/finesse/technical-overview

You will need a Finesse and UCCE lab. Getting started with that is defined here http://developer.cisco.com/web/finesse/getting-started-guide

Once you are able to work with the Finesse Agent desktop and the Cisco supplied gadgets, and are ready to develop your own gadgets, start with the Finesse Javascript Library by downloading it from the tools folder on the documentation page http://developer.cisco.com/web/finesse/documentation

The Finesse 9.1(1) version of the finesse javascript library is in finesse_javascript_library_and_samples_9.1.1.zip
Unzip the file and you will see a Gadget and Non-Gadget sample directories.
Copy the files from Finesse_9.1.1\samples\GadgetSamples to your 3rd party web server where you will be hosting your custom gadgets. (You can have the Finesse server host your gadgets by following the directions in Chapter 10 of the Finesse Developer Guide)

Then you will need to add the sample gadget to your Finesse Layout XML. For information on modifying the default layout see the Finesse Developer ppt here https://communities.cisco.com/docs/DOC-28452 and the Finesse Administration Guide
For the finesse gadget sample you will be adding something like
<gadget>http://<IPaddress>/3rdpartygadget/files/SampleGadget.xml</gadget>

There is a presentation on creating a Finesse gadget here https://communities.cisco.com/docs/DOC-28452

Next try downloading and installing the other sample gadgets in the Sample Gadgets directory. You might start with Screenpop.zip
You can see a video on how to modify the screenpop gadget to screenpop your own url here: http://developer.cisco.com/web/finesse/videos

That should get you started. If you have any questions you can post them here or in a new forum thread.

Pushing Applications to your DX650

2013-04-12T20:22:55Z

Last time I talked about some of the additional features that the Cisco Unified Communications Manager brought to table in regards to the DX650. I did however leave out a crucial ability of the CUCM, which is pushing applications to the DX650. This is a feature that the system administrator of the CUCM would be able to perform. So, let's take a look at creating this IP Phone Service by going to your CUCM Administration page under Device Settings > Phone Services.

Above is what you will see when you try and create your IP Phone Services. There is a few required fields that you need. Let's go through each of these fields.

Service Name/ASCII Service Name: This value must be the package name of the Android Application that you are trying to install. This is required in order for the service to work.
Service URL: The location of the Android APK you are installing.
Service Category: Set this to Android APK.
Service Type: Set this to Standard IP Phone Service.
Service Version: This is the version code that is specified in the Android Manifest. If leave this blank it will automatically re-download the application every time the configuration is updated. Assuming you don't want this to happen just fill this in with the version code. If the version code you specify is different from the Android Manifest it will not update the application. If you update the version with a different value and update the subscription it will update the application. Please note this is the version code, not the version name.

At the bottom you see that there is a Parameters section, this is used to send additional information to the application. For instance, you want to name the phone. Let's take a look at how we would pass this name to our device.

Above you can see the parameter that we created with the name of Name. The default value or the value that will be stored with the key of Name is DX650. This parameter will be installed on your device as a shared preference. With this in mind the application can just grab the value out of the shared preference. Below is a small code snippet that would do just that. If you need more information on Shared Preferences head on over to the Android Developer Site. Knowing about this Parameter section when writing your Android Application could come in handy.

1SharedPreferences app_preferences = PreferenceManager.getDefaultSharedPreferences(this);
2String text = app_preferences.getString("Name", "null");

Once the service is setup, all you have to do is go to the Device page and subscribe the device to the service you created. This will then in turn push the application to your device.

Designing Applications For the DX650

2013-04-08T14:19:24Z

Designing Applications For the DX650

Writing applications for the DX650 is no different than writing applications for any other Android device. With that being said, a very common questions about our device and I’m sure other devices as well, is “Why doesn’t my app work on your device?.” My standard answer is “Because you did something wrong!”

Obviously, that’s not a fair thing to say without more information. To understand the problem with modern devices, you have to take a brief look at the history of Android.

To gain access to Google applications like the Play store a device must meet rigorous standards as defined at http://source.android.com/compatibility/. The Android Compatibility Definition Document (CDD) and Compatibility Test Suite are used to define the standards and test that a device meets the standard.

To fully understand why some applications don’t work on some devices, you have to look at the history of the CDD. For example, in version 1.6 (Éclair) the rule regarding the Camera is:

Device implementations MUST include a camera
Not much wiggle room there because in a formal specification, MUST means just that, it’s required and non negotiable.

If you fast forward to the version 4.0 (Ice Cream Sandwich) CDD, it says:

Device implementations SHOULD include a rear-facing camera and May include a front-facing camera.
This is obviously a big change in the definition (a good one in my opinion), and it adds some complexity that developers need to deal with. Why would the definition change? In the beginning all Android devices were pretty much the same. As time passed there was a desire to have devices in different sizes and shapes, and it really didn’t make sense to force them all to the same characteristics.

Another quick example. In Android 1.6 compatible devices were required to have an Accelerometer, Compass and GPS. In 4.0, the requirements are that a device must correctly report the sensors that it has and that the sensors must report accurate and genuine data (no fake sensors allowed), but there is no requirement that a device has any sensors at all.

As Android changed, one thing they tried to do was preserve backward compatibility, so in many cases, an old app will work on a new device. There are exceptions of course, for example, if an application was written when cameras were required, that application will likely have problems on a modern device with no camera at all.

So what’s the best approach to dealing with the fact that many different devices exists. I’ll suggest three methods

Google Play Filtering
Runtime Detection
Just Deal With It (my favorite)

Google Play Filtering

All devices that access Google Play must passed the compatibility tests which means they must accurately report their features. For example: these are the features reported by a DX650

In the Manifest for your application, you can if you want ,define various device requirements such as screen size, the presence of a rear camera or other device specific features.

Google play looks at both the device requirement in the application Manifest and the features reported by the device and filters (removes) any applications that require a feature that doesn’t exist on a specific device. If you’ve ever wondered why applications are available for some devices and not others, now you know.

You can get a full explanation of how this works here: http://developer.android.com/google/play/filters.html

This filtering feature is great for applications that are deployed from Google Play, but as an application developer you may want to have the ability to deploy your application via other means, or you may simply want more devices to have access to your application.

Runtime Detection

Many problems can be solved before they exist by simply writing good code. As devices have change Android has done a great job of adding the ability to determine device characteristics at runtime rather than just assuming that the device had a specific feature. Take the Camera for example. Prior to Android version 2.3 the Camera had a simple “open()” method that returned the “default” camera which must be a back-facing camera. In Android 2.3, the front cameras were first allowed and all cameras became optional, new APIs were added to allow your application to get the number of cameras, the type of camera (front, back) and a new “open(int cameraId)” method that allows you to specify which camera you want to use.

In my opinion, no modern application should ever use the old Camera.open() method, but instead should use the modern APIs to detect the cameras and open the specific camera that it needs.

For a good example of detecting capabilities at runtime, check out James Catalano’s blog on using the from camera. These same techniques can be used for other device dependent features.

Dealing with different screen sizes and resolutions is another complex subject. The Android Developer site has several great guides include “Supporting Multiple Screens” and “Designing for Multiple Screens.

Just Deal With It

Detecting capabilities at runtime and writing your code to adjust accordingly is a good first step, but you can do more. Rather than just failing gracefully if a feature doesn’t exist, I think you can go one step further by writing your application to adapt, or “deal with” whatever capabilities are present on a specific device.

For example, the DX650 doesn’t have a GPS. Is this a problem? Not really. GPS is a very low power signal and most GPS radios don’t work well or even at all indoors. Also, a DX650 isn’t a mobile device, so exact location isn’t necessarily as important as it would be for other devices.

But what if your application needs to know your location when recording some event, or because you want to show businesses nearby.

Not a problem. One of the Google services is a Wi-Fi based location technology, known as “Course Location” on Android. Remember above when I said a device “must correctly report the sensors that it has”. The DX650 reports Course location, but not Fine (GPS) location. Applications can be written to use Fine Location, Course Location, or even both depending on what is available at runtime.

Cisco DX650 Device specifics

Now that you understand the potential problems and several solutions, it’s worth mentioning a few of specific characteristics of the DX650.

Conclusion

Taking full advantage of the tools and APIs available in Android is key to writing stable, well-behaved applications that work on a variety of devices, now and in the future. Even if you are only targeting a single device, like the DX650, I encourage you employ the best practices described above.

Registration for Developer Forums Cisco Live Orlando - Coming Soon!

2013-04-22T05:51:09Z

Dear CDN Partner,
Please accept my personal invitation to join us for the CDN Developer Forum Orlando taking place in conjunction with Cisco Live U.S. on Sunday, June 23 and Monday June 24, 2013.
The CDN Developer Forum will provide your technical, business development, and marketing executives with relevant information to advance your partnership with Cisco and accelerate your business growth.

The 1.5 day agenda will focus on your business imperatives and provide information through two focused tracks – technical and business – to ensure you have access to essential product lifecycle information from build to Go-to-Market.
The CDN Developer Forum is complimentary for all CDN members, but a reservation is required. Register today at (URL). The Cisco Live U.S. Explorer Pass is included in your registration and entitles you to World of Solutions access along with keynotes and Super Sessions June 24-27, 2013.

Send your business development and marketing teams to:
• Discuss best practices in identifying routes to market and building the right relationships that will drive Return on Investment (ROI).
• Develop a Channels strategy by identifying and gaining the attention of the right resellers to support your business model
• Learn how to use the Go-To-Market Resource Center to build and execute your Go-To-Market strategy and discover the key tools and assets available through the Resource Center to help your business thrive
• Stay current with CDN program enhancements and information about the 2013 CDN program strategic roadmap

Send your technical teams to:
• Gain insight into the technology groups strategic roadmaps
• Increase your expertise in building solutions that leverage Cisco products
• Connect with key technical leads from the various Cisco technology groups

The Internet of Everything is creating unprecedented business opportunities for you to partner with Cisco. An informed ecosystem of partners is increasingly important to drive relevant business solutions to our customers. Key business opportunities span Cisco technologies, solutions and new business models.

Please mark your calendars and plan to join us at the CDN Developer Forum in Orlando, Florida June 23-24, 2013.

I look forward to seeing you there.

Beth Bohdanowicz-Jensen
Director, Cisco Developer Network

DX650 and the Cisco Unified Communications Manager

2013-04-01T19:39:04Z

With the recent release of the Cisco Desktop Collaboration Experience DX650, it is important for us to clarify some of the differences that this product has over other generic Android Devices. One of these differences would be that it is connected to a Cisco Unified Communications Manager. With this connection, there are certain controls that the CUCM has over the device. These administrator controls give additional security to the DX600 Series products.

Features

Android Debug Bridge - ADB
Allow Applications from Unknown Sources
Allow Applications from Android Market
Require Screen Lock
Maximum Screen Lock Timeout
Lock Device
Wipe Device

All of these controls can be changed by the system administrator of the CUCM the device is connected to. They can be accessed on the DX650 Device page. If you are the developer of an application that will be deployed on a DX650, make sure to notify users that they might need the system administrator to update these settings. For instance, if they are installing using the ADB, make sure it is enabled. Or perhaps your application is available on the Android Market, you would then need to make sure that the Android Market is enabled. Hopefully, having knowledge of these settings will save you from troubles you might encounter in the future.

CDN Program Insights: March Update

2013-04-22T05:58:15Z

Join Us For The CDN Developer Forum at Cisco Live U.S.
Registration for the CDN Developer Forum at Cisco Live U.S. opens the first week of April. Watch your email Inboxes for more information. Join us to learn about latest developments in your technology area. Send your business development and marketing representatives to learn about the latest additions that support your marketing needs. We’ll also share our CDN program strategic roadmap. Meet the CDN leadership team and join us for our CDN partner appreciation event. Cisco Live US U.S. 2013 takes place June 23 to June 27 in Orlando, Florida.

Power Hour Webinar Schedule & Replays
Are you taking part in our Power Hour series? Power Hour webinars are designed to maximize your partnership with the Cisco Developer Network. Coming events include Working With CDN's Not-For-Resale (NFR) Program on April 2, Technical Webinar: Smart+Connected Residential system on April 16, and How to Make Cisco Care About You on April 23. To register or learn more, visit our Events Calendar. If you are unable to attend an event, the recordings and presentations are all available within the CDN portal. You will need your Cisco.com login to participate.

Gain A Competitive Edge With SIP To Attract Resellers
The Solution Incentive Program (SIP) rewards resellers who team with CDN partners to sell replicable business solutions that include your hardware and software products. If your products have passed Cisco Compatible testing and are listed in the CDN Marketplace Solutions Catalog, you’re eligible to apply for SIP approval. Learn more today to boost your profitability.

Win 5 Case Studies with Deal Registration
Register your Cisco deals now using the Deal Registration tool on the CDN Developer Dashboard to earn program points and a chance to win one of five written case studies valued at $2500 each. The top five CDN Partner organizations who register the most deals between January 1, 2013 and May 31, 2013 will each be awarded a case study sponsored by Cisco and co-branded for use in marketing your solutions to customers and prospects. Deals must be completed between Jan 1 2013 – May 31 2013 and registered by May 31, 2013.
The written case study requires a customer who is willing to share their story publicly. The winning CDN partner organizations will be announced the first week of June 2013. Learn more on the portal, or please refer to Section II, ‘Participation Level, Requirements and Advancement’ of the CDN Program Guide.

Cisco Marketing & Communications Style Guide Available
The 2013 “Cisco Marketing and Communications Style Guide” update is here! You can download the latest version from the Cisco Brand Exchange. Our style guide provides recommendations and policy guidelines addressing global, brand, legal, and program-specific topics. It includes general and web-specific guidelines, conventions for acronyms and units of measure, an extensive word list, and closes with a list of resources.

____________________________________________________________

Tech News and Resources

New Developer Center for UCCXAPI
There is a new Contact Center Developer Center for UCCX Config API.
The Cisco Unified Contact Center Express Application programming Interface (UCCXAPI) provides for Cisco partners to integrate provisioning applications.

Attention Finesse Developers
Our Finesse Developer Center has a new blog entry about the SampleGadget_Logging sample gadget Are you subscribed to this Community? Simplify your participation by clicking on any of our Developer Communities, and locating the subscribe button in the right side of the page. One click will keep you connected.

. ____________________________________________________________

Contact Us
As always, please email our Program Office if you have any concerns. Follow us on Twitter @Cisco_Developer for regular updates.