UC Data vs UC Data (Matching Data from Different Sources)

Posted in CUCM on September 18, 2013 by miskaone

Some excel basics for comparing data out of CUCM and CUE. Using directory number extensions from CUCM to match CUE phonenumber extensions to get CUE username.

Stupid-pet tricks1

Used index() and match() excel formula to correlate the available user names.

CUCM 9.1.2 Changing Just The Host Name

Posted in CUCM on September 6, 2013 by miskaone

I used the following steps to change all the host names in a cluster that was upgraded to CUCM 9.1.2.

This closely follows the CCO guide for changing host names but a little more concise.

 

hello-my-name-is

– Step 1 –

On each server  check the replication status. I prefer the CLI and the following command.

  • show perf query class “Number of Replicates Created and State of Replication”

– Step 2 –

Validate or Reset DRF services. If any of the DRF services are not active and responsive the name change will fail.

  • utils service stop Cisco DRF Local – all nodes

  • utils service start Cisco DRF Local – all nodes

  • utils service stop Cisco DRF Master -Pub Only

  • utils service start Cisco DRF Master -Pub Only

– Step 3 –

Change DNS if the dns client is enable on the servers

 

– Step 4 –

Publisher Host name change requires changing the Cluster Publisher Host Name setting on each node. This can completed via the GUI or CLI

  • set network cluster publisher hostname {host name}

 

– Step 5 –

Now you can change the host name on the server requiring the change.

  • CLI: set network hostname

Note the following scripts will run  as component notification

  • adns_verify.sh
  • clm_notify_hostname.sh
  • drf_notify_hostname_change.py
  • regenerate_all_certs.sh
  • update_idsenv.sh

Note the server will automatically reboot.

– Step 6 –

After the reboot on the node that the host name was changed run  the dropadmin table to clear the syscdr configurations.

  • utils dbreplication dropadmindb

 

– Step 7 –

Reboot all other servers in the cluster, including the Publisher.

 

– Step 8 –

Verify that the name-IP association change

  • utils network host {name}

Note Do not proceed until the change propagates to all nodes.

– Step 9 –

From Publisher force the replication to restart and rebuild the replication connections.

  • utils dbreplication reset all

 

– Step 10 –

Check replication status periodically to ensure all replication get to state 2.

  • show perf query class “Number of Replicates Created and State of Replication”

 

– Step 11 –

Repeat for each node that needs to be renamed.

 

Cisco Phone Menu XML Build From Scratch Example

Posted in Uncategorized with tags , , on September 2, 2013 by miskaone

One of the the things I am practicing for the lab. Most folks will go to the programing guide and copy the template provided. I have memorized it to save some steps.

Now,  as you can see I am not the best typist but it removes the reliance on going to the the product documentation.

Cisco 7900 programing guide examples:

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/all_models/xsi/7_0/english/programming/guide/xsi70obj.html#wp1033319

The Chromecast experience

Posted in Uncategorized on September 2, 2013 by miskaone

{Null}

So I in my infinite abundance of free time decided to unbox and use my new Chromecast in the hotel. Well first defect discovered in Chromecast setup. Most Hotels are Hotspot enabled now. Chromecast has an interesting setup process to say the least. The setup app creates an ad-hoc connection from you laptop or tablet to the Chromecast device for setup. This seemed work well enough. But the ad-hoc connect is used to specify the Wifi connect that Chromecast will be using. Here in-lies the issue while traveling. The App Developers did not think to include an interface option for passing Hotspot Credentials to the Wifi connection.

Google-foo has turned up various recommendations, only reasonable one is to connect a travel wifi router to the hotel wired connection. This does not seem practical for all hotel stays as you often do not get a wired connection and you are relying on the Hotspot not having appropriate MAC security (One MAC for each authenticated connection). Needless to say I will sip the kool aid a step out and get a travel wifi router and see if I can get this connected.

marquee-productBroken-WiFi

Other options:

Get the Hotel Tech to whitelist your Chromecast MAC (Ugh what a conversation that would be)

Share your Internet connection (OK I already feel dirty when I let my laptop connect to public wifi, now I am going to share that connection, talk about hacker brothel…)

Use your Phone Hotspot (Hmm, costly)

Will post the travel Wifi router experience later.

 

Update

Asked the Hotel to whitelist my Chromecast MAC. I should have had a farsi translator helping me explain this for all the effort I went through.

The local Best Buy had its myriad of consumer grade access points but no travel wifi AP. So I went with the Linksys N300 for cost and simplicity.

15 minutes setup and I am streaming Google Music to the TV.

 

Start VM from VBS script – Securecrt

Posted in Uncategorized on September 1, 2013 by miskaone

This is a work in progress but I have been using SecureCRT to automate many things that I do in the LAB. The following details starting VM servers from SecureCRT vbs scripts.

  • Create a VBS like below. SecureCRT will do this if you turn on the Record Macro.
  • Adjust the server ID and replicate script for all the servers.
  • Add a button for each and link to the VBS script to SecureCRT button Bar.

SecureCRT-AddButton

Securecrt-ESXi-start

To find the VM server ssh to ESXi. You will have to enable SSH in the Security configuration of ESXi.

Command to run from ESXi shell to get the VM server id:

  • vim-cmd vmsvc/getallvms
  • find vmid located in the left column {nn}

Following is the start script.

#$language = “VBScript”

#$interface = “1.0”

crt.Screen.Synchronous = True

Sub Main

crt.Screen.Send “vim-cmd vmsvc/power.on {nn}” & chr(13)

End Sub

Consider this before CUCM Cluster Restore

Posted in Uncategorized on September 1, 2013 by miskaone

Checking and Restarting DRS in CUCM

 

Something to be checked before restoring a CUCM cluster,  are the Disaster Recovery Service (DRS) related services running.

If one of the subscriber nodes or any node for that matter is not in a good state this can lead to a failed restore.

I prefer use of the CUCM CLI for this activity so here are the steps:

Check all nodes to be sure the DRF Local and DRF Master service are started.

  • utils service list

Steps to ensure the DRF services are started.

  • To be done on all nodes – utils service stop Cisco DRF Local
  • To be done on all nodes – utils service start Cisco DRF Local
  • To be done on Publisher – utils service stop Cisco DRF Master
  • To be done on Publisher – utils service start Cisco DRF Master

 

B-ACD and the Drop-through

Posted in CCIE Studies on July 28, 2013 by miskaone

Ran this exercise in the Lab today. Focus was to us CUCME Embedded B-ACD (Call-queue) TCL script for a call application that will play a welcome greeting, route calls to agents (phones registered to CME), queue up to 2 calls and if no agent answer notify the user all agents are busy. The embedded B-ACD has positives and negatives based on how simple the call flows is.

Overall the main benefit of using the embedded si that is come with the Router IOS and offers the  convenience of not having to load additional TCL scripts. In a controlled environment this maybe the only practical method for standing up B-ACD.

Draw-back are that not all options (param) will function with the embedded Call-queue such as exit call queue options. Additionally, you are limited with number of option you can develop with the Embedded Call-queue

Most configuration is completed in the call application configuration:

application
service app-b-acd-aa
 param voice-mail 566
paramspace english index 0
param max-time-call-retry 700
param service-name app-b-acd
param number-of-hunt-grps 1
param drop-through-option 1
paramspace english language en
param handoff-string app-b-acd-aa
param max-time-vm-retry 2
param aa-pilot 555
paramspace english location flash:
param drop-through-prompt _greeting.au
param second-greeting-time 60
param welcome-prompt _bacd_allagentsbusy.au
param call-retry-timer 60
!
service app-b-acd
 param queue-len 2
param number-of-hunt-grps 1
param queue-manager-debugs 1
param aa-hunt1 410

The next critical component is the the hunt pilot or ephone-hunt to distribute the calls to the agent phones.

ephone-hunt 10 longest-idle
pilot 410
list 411, 412
final *411
timeout 10, 10

Final configuration component is the dial-peer routing that will engage the B-ACD.

dial-peer voice 555 pots
service app-b-acd-aa
incoming called-number 555
port 0/0/0:23
dial-peer voice 556 voip
service app-b-acd-aa
destination-pattern 555
session target ipv4:142.102.66.254
incoming called-number 555
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

 

Resources used:

http://blog.ipexpert.com/2009/01/24/b-acd-in-a-nutshell/
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/bacd/configuration/guide/40bacd.html#wp1083384

Troubleshooting:

show run | sec application

show call application session

call application session stop id NN

debug voice application session

debug voip dialpeer all