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’. 🙂


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.

Single Number Reach on CME

I can remember it was not so single procedure to configure SNR on CUCM, but on CME? It’s more easy! Just few commands and that’s it! So let’s do it…

This is my phone I configured SNR:


ephone-dn 3 octo-line
 number 645
 label 645
 description Mijanur Rahman
 name Mijanur Rahman
 snr 998180433 delay 5 timeout 15

ephone-template  1
 softkeys idle  Redial Newcall Mobility Cfwdall Pickup Dnd
 softkeys connected  Endcall Hold Mobility
ephone  3
 device-security-mode none
 mac-address 0023.5EB7.2949
 ephone-template 1
 type 7961
 button  1:3
dial-peer voice 6 pots
 destination-pattern 99.......
 port 0/0/0
 forward-digits 8


Maximum Number of Conference Participants on Hardware CFB: a small note

IOS earlier than 12.4(15)T supports 8 participants per conference session.

IOS equal or later than 12.4(15)T supports 32 participants per conference session.

Found on CUCM SRND:

“A conference based on these DSPs allows a maximum of 8 participants. When a conference begins, all 8 positions are reserved at that time. Starting with Cisco IOS Release 12.4(15)T, this limit on the maximum number of participants has been increased to 32.”

CUCME: If you get the error “ERROR: could not add peer”

I got this strange (not literary!!) error today while adding one dial-peer and I was just wondered seeing the error (‘ERROR: could not add peer’) and I was thinking ‘what happened to my router!!’, but it’s not a strange message! Sometime your CME router won’t allow you to create any additional dial-peer or any additional DN on your router. So what’s the fix? Before that let’s discuss why router was not allowing you to create additional dial-peer or DN. It’s because of the insufficient memory the router was running with. I issued the command ‘max ephone-dn 20’ while I was needed only 5! It reserved my router memory from the pool and made my router hungry! So let’s discuss what’s the fix?

1. Check how many DN you have created additionally more than you need. If you need 5, create ‘max ephone-dn 5’. 🙂 Don’t reserve your router memory with additional DNs.

2. Check your IO-Memory what’s the percentage is there? By default the routers reserves 25% memory from the pool for IO, I have set it down to 10% and my router is booting fine. Minimize your iomem setting with the command ‘memory-size iomem xx’ where xx is the least percentage of memory your router need to be boot up.

3.  If none of the methods trick, then remove the additional features and commands from the router. If you don’t need the QoS, don’t apply and enable it. If you have any additional modules/slots connected to your router remove it! Configure your router just as per your need, it might save lots of your router memory.

4. If none of the above tricks, then I’m sorry. 🙂 Order a new memory and increase your router memory.

Anyway, This document helped me understanding the DN things:;jsessionid=59932EFC68B7475599481780EE688611.node0

Thanks to the author ‘TCC’ (that’s the name I have found on the post.)

Extension Mobility on CME: virtualize your phone :)

I don’t want to discuss the Extension Mobility concepts, google for that, my objective is to note down some straightforward commands for EM on CME. The concept is pretty interesting, you don’t need the ‘button’ command to assign DN on you ephone, rather than DN would be assigned on the ‘logout-profile’. I would change the word ‘logout-profile’ to ‘default-profile’ if I were the Cisco designer, hehe. Because it’s the profile set on the device (phone) by default (when user is not logged in to say more clearly). Oh, another point I need specify here clearly, you will MUST needthe ephone-dn for the number you are going to set on profiles. Some people do not create the ephone-dn for the numbers they have assigned on the profiles and shout ‘my EM is not working! help!!’. Okey, let’s configure EM:

1. Create the ‘logout-profile’ first and assign it on ephones:

Remember to create/check if the DN exists first before going to create the logout-profile, it’s very important if you don’t want to cry later 🙂

ephone-dn  1  octo-line
number 1001 no-reg primary

voice logout-profile 1
user 1001 password 1001
number 1001 type normal
ephone  1
mac-address 001A.6D70.D39C
type 7941
logout-profile 1

Have you noticed no ‘button’ command under ephone 1!!

2. Let’s create the user-profile which would be user specific and users will use it while login:

ephone-dn  6  octo-line
number 1010 no-reg primary

voice user-profile 1
user cisco password cisco
number 1010 type normal

So have you done it? No man, it’s not the time for clapping, what do you think what you are missing? Setting the URL for login through ‘Services’ button right? let’s do it now.

3. Setting up URL Authentication:

url authentication username password

You don’t need to worry about the username/password here, set it as you wish. It’s not the user facing credentials, system will use it. So you are set! Have a test and give a big smile!!

Happy Labbing!!! 😀