Cisco Telepresence Basic Product Knowledge – Part 2

Here is the second part goes!πŸ™‚

Cisco Telepresence Basic Product Knowledge – Part 1

This presentation is ripped from Cisco Partner Education Connection(PEC) and this is targeted for some certifications, but I thought I should share this for a good reason. Very few materials are available on websites to study on Cisco and Tandberg Telepresence system solutions specially the end to end product knowledge in one or few. At least I tried to find some good documentations like this for days but couldn’t find – maybe it will help some of you who are trying to get some product knowledge.πŸ™‚

Total three parts are there, only first part is shared now – will share the rest once ripped. Please warn me if I’m violating any partner rules and confidentiality, I can remove the contents happily.πŸ™‚

CME BACD Really Doesn’t Need *.au Format Audio Files

I know whoever starts working with CME BACD, specially those voice engineers, starts feeling stress to find the right media encoder to convert media files to *.au format – even I used to feel the same.πŸ™‚ But really *.au is nothing special! Maybe the *.au extension is just another extension of CCITT u-Law, 8Khz Mono Attribute and 8-Bit encoded files, we are well known of this format used for all Cisco voice applications – in UCCX, UCCE, CVP, CUE etc. etc. Thanks to Mark Snow!

If you have your UCxn ready, or CUE ready, or UCCX ready or even your Windows XP is ready (πŸ™‚ ) then you have all to move forward. You can change the string ‘param welcome-prompt’ to ‘param welcome-prompt anything.wav’ and it will work fine. Just make sure the format is as mentioned and the ‘anything.wav’ is in the right folder into the flash.

If you are still using Windows XP then use the default Sound Recorder to convert the prompt from any type. If you are using Windows 7, copy the original Sound Recorder application from Windows XP System32 and paste it anywhere on Windows 7, it will work great even though it might show some warning prior start – just ignore it.πŸ˜‰

All other prompts except the welcome-prompt, file names must need to be the same. So you still need the *.au converter? Answer is ‘no’ – just rename the prompt from, for example, ‘en_bacd_options_menu.wav’ to ‘’ – it’s a trick!

I hope you won’t google again the ‘*.au media converter’.πŸ™‚

Find me on INE forums – IEOC!

Hey fellows! Nah, I’m not inactive! Just I have changed my job and relocated to UAE – the Arab land, relocation isn’t a easy task, I swear! So I wasn’t very active on my blogs. But you can find me at INE forum – IEOC, specially on Voice forums anytime. I am still trying to be very active there and I will be answering your questions, doubts or any technical helps related to Cisco UC.

Happy labbing!

Image Image

MWI on SIP Phone during SRST: an open bug yet to solve!

Well, I discovered it when was trying to solve a issue on IEOC forum. MWI on SCCP phones works without any issue, but for SIP? It’s still a bug (bug idΒ CSCta76151) on 12.4T trends IOS series.

Cisco Bug Toolkit can really save some of your precious time if you search for the bug rather than getting panic and googling and googling when anything not working.

Decryption of IOS Passwords/Secrets: an IOS method!

It’s very regular issue who works for support team, who have the router/IOS configuration files but can’t retrieve the password. Even I don’t know how you faced the issue guys but it was very regular headache for me until i didn’t know this simple method to decrypt the IOS secrets! No, its by any tool or by any code on C/C++! It’s from the IOS itself!! Now let’s see how it works….

Let’s the username/password string we got from IOS is:

‘username cisco password 7 0822455D0A16554745’

Now we need to find out what’s the actual password encrypted to ‘7 0822455D0A16554745’. Now we will need to take help from another router and follow the command chains like below:

R3#conf t
R3(config)#key chain ?
WORD Key-chain name

R3(config)#key chain decryption
R3(config-keychain)#key ?
<0-2147483647> Key identifier

R3(config-keychain)#key 1
R3(config-keychain-key)#key-string 7 0822455D0A16554745
R3(config-keychain-key)#do sh key chain decryption
Key-chain decrypt:
key 1 — text “cisco007”
accept lifetime (always valid) – (always valid) [valid now]
send lifetime (always valid) – (always valid) [valid now]

So the actual secret was ‘cisco007’!πŸ™‚

Special thanks toΒ Ivan Pepelnjak, CCIE#1354 an his blogsΒ where I found this tip.

Cisco Unified CallConnector for Microsoft Dynamic CRM 4.0, CTI integration made easy!

You must have known with the term ‘CTI Integration or CTI Development’ if you are working with Contact Center! It’s completely a coding job to develop the front-end GUI and integration with the CTI, have to have knowledge on contact center CTI area as well as connection procedures with CRM via SOAP or Web Service or ODBC/JDBC whatever they allow. But Cisco is ready to help you for Microsoft Dynamic CRM even for others like, Cisco brings a software named ‘Cisco Unified CallConnector for Microsoft Dynamic CRM’ which will save your integration time as well as will saving overall contact center budgeting! Ok, let’s see how it works…

Microsoft Dynamic CRM is a browser based server where you can administer, edit of view the customer contact/record. Cisco Unified CallConnector is basically a server-client process where the server need to be installed on the CRM server itself, and the client needs to be installed on agent desktops. Let me write few simple quotes to think it more easily!

1. Install the ‘Cisco Unified CallConnector (CUCC) for Microsoft Dynamic CRM’ server on the CRM server itself. It will need proper authentication to access (read/write) the CRM.

2. Install the client tool on each agent desktop, it will need the server hostname as well as authentication to access the CUCC server. The client machine must need to be on the same Active Directory domain to authenticate the user on the CRM otherwise you might get ‘access denied’ message!

3. Create some rules Contact Center server (it was UCCX for me) to call some automatic events while ringing, answered or even call is dropped. It will push your CAD to deliver the ANI or any required information to CUCC so that the CUCC client can communication with the CUCC server accordingly. You can configure your CUCC client to pop-up the contact information automatically!

Press here to get the detail about the Cisco Unified CallConnector for Microsoft Dynamic CRM, and here to get the integration document from Cisco, and it’s your goal to get the software from CCO.