Tuesday, January 18, 2011

Presence Configuration: Configuring CUPC Client in Softphone Mode

Integrating CUPS with CUCM for CUPC Client in Softphone Mode:
Part 1 - CUCM Steps:
1. Add End User.
 
 
 



























2. Add CUPC Device:  The name of Device should be less than 15 chars. It must start with UPC followed by Username (till 15 chars, discard chars after 15th).













3. Add CUPS Server as an Application Server.








4. Assign Capabilities to the End User.











5. Create a new SIP Trunk Profile with the following parameters.


















6. Add a SIP Trunk to the CUPS Server.














7. Update Service & Enterprise Parameters to Enable BLF Status, Allow Subscription & CUP SIP Trunk. Mention the SIP Trunk in Service Parameters. If you have more than 2 SIP Trunks in your UCM cluster. Always a good idea to have this mentioned.









8. Add an Application User with AXL API access for the CUPS Server to talk to UCM.













Part 2 : Configuring the CUPS Server

1. Goto System >> Topology and edit the CUPS Publisher name to IP Address.

This image shows the updated version.







2. Goto System >> CUCM Publisher and add CUCM Pub with admin user account.















3.Goto Security & create Inbound & Outbound ACL. 
 





4. Goto Service Params and add a domain name for the SIP Proxy  Service.
5.Now got to Serviceability and start all the Service. Come back to Topology after it to see the status of all the services. It should all show green with right checkboxes.


6.  Goto Presence >> Update CUPS Sip Trunk here.
 










7.Goto Gateways  and add CUCM as a Presence Gateway.  







8.Now goto Application >> CUPC >> Settings and add UCM as TFTP Server .
Now you can launch your CUPC Client and it will work in the shared line mode.
Hope this helps.
 

Monday, January 17, 2011

Configuring CBarge & Privacy Feature in CME

=====================
CBarge & Privacy in CME
=====================

If you want to test the cBarge functionality, you must disable privacy either from telephony-service or from phones. Oh, one more thing I just forgot to specify, you will must need the hardware conference bridge and the ad-hoc conference DN to be active during cBarge.
First, configure a Hardware Conference bridge & register it to CME. 
---------------------------------------------------------------------------------------
!
voice-card 0
  no dspfarm
  dsp services dspfarm
!
sccp local GigabitEthernet0/0
 sccp ccm 10.200.197.24 identifier 1 version 6.0
 sccp
!
sccp ccm group 1
  associate ccm 1 priority 1
  associate profile 1 register cme-cfb
!
dspfarm profile 1 conference
  codec g711ulaw
  codec g711alaw
  codec g729ar8
  codec g729abr8
  codec g729r8
  codec g729br8
  maximum sessions 4
  associate application SCCP
!
telephony-service
  sdspfarm units 2
  sdspfarm tag 1 cme-cfb
  no privacy         ! IMP. Else you won't see Remote in Use option.
  conference hardware
  max-ephones 10
  max-dn 40
  ip source-address 10.200.197.24 port 2000
  system message CME
  max-conferences 4 gain -6
  transfer-system full-blind
  create cnf-files version-stamp 7960 Dec 11 2010 10:26:55
!
------------------------------------------------------------------------------
! Create the new Ephone Template
!
ephone-template  1
  softkeys remote-in-use  CBarge Newcall
  softkeys hold  Newcall Resume Select Join
  softkeys idle  Cfwdall ConfList Dnd Gpickup HLog Join Login Newcall Pickup Redial RmLstC
  softkeys seized  Redial Pickup Gpickup HLog Meetme Endcall
  softkeys connected  Acct ConfList Confrn Endcall Flash HLog Hold Join Park RmLstC Select
!
!
ephone-dn  4  octo-line
  number 4000
  label Octo-Line 4000
  description 4000
!
!
ephone-dn  11  octo-line
  number 8889
  name My-Conference
  conference ad-hoc
!
!
ephone  1
  mac-address DC7B.9477.AEC1
  button  1:2 2:3
!
ephone  2
  privacy-button
  mac-address 001D.705E.D407
  ephone-template 1
  type 7962
  button  1:4
!
ephone  3
mac-address DC7B.94F8.BF47
ephone-template 1
type 7961
button  1:4
!

Configuring Extension Mobility On CME

================
  Configuring EM
================
Step 1: Create the DN, seems basic, but I created numbers inside the user & logout profiles without defining these DNs.
!
ephone-dn  4  octo-line
  number 4000
  label Octo-Line 4000
  description 4000
!
ephone-dn  5  octo-line
  number 4001 no-reg primary
  label Line-4001

Step 2: Create the logout Profile & assign it to the Ephone which needs EM Enabled. Without this, EM is not enabled o the phone. Similar to EM Enable Param on UCM.
!
voice logout-profile 1
  pin 9999
  user 1111 password 1111
  number 4001 type normal
!
!
ephone  3
  mac-address DC7B.94F8.BF47
  ephone-template 1
  type 7961
  logout-profile 1

Step 3: Create the User Profile, Unlike UCM, the password here is used for login instead of the PIN.
!
voice user-profile 1
  pin 1111
  user abc password 111
  number 4001,4000 type normal
!
Contrary to documentation in CME Admin Guide, I didn't need to create the URL Authentication with the tel-ser to make EM Work.

Thursday, January 13, 2011

Dynamic Zone Prefix Registration

Hey,
This allows gateways to dynamically add their prefixes into GK "Dynamic Zone Prefix Registration".

Voice service voip
H323
Ras rrq dynamic prefixes
Terminal-alias-pattern 22… priority 7
Gatekeeper
rrq dynamic-prefixes-accept

H323 Caller ID name display in Cisco IP Phones

Hey guys,
check this out:

https://supportforums.cisco.com/docs/DOC-8873

Sunday, January 9, 2011

CUE and B-ACD integration

Hi guys,
Interesting doc: "Cisco CME Basic Automatic Call Distribution and Cisco Unity Express Auto Attendant Interoperation Configuration Example"

http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_configuration_example09186a0080566c4a.shtml


Enjoy.

Saturday, January 8, 2011

UCCX not properly integrated with CUCM

Hey guys,
I'm back on track now (don't know if I can make it time).
Anyways I was messing around with UCCX integration with CUCM and was able to break it.
Here are the symptoms:
1) UCCX integrated with CUCM
2) CUCM does not show that it has any integrated UCCX. This can be seen from two places:
a) End user does NOT show any IPCC extension option
b) Under Enterprise Params, it shows that Auto Attendant and IPCC are not installed

The only way to rebuild it is by going to CUCM and typing the following:
run sql update processconfig set paramvalue="T" where paramname like'%nstalled%'

This will change the Auto Attendant and IPCC so that CUCM thinks it is integrated with UCCX.
Next to reset any settings done on UCCX, go to Run and type "cet.bat".
A pop up will appear press No
Once a window opens select ""com.cisco.crs.cluster.config.AppAdminSetupConfig""
Double click on the row on the right
Click on the second tab
in "Setup State" change it to "FRESH_INSTALL" from the drop down menu.
Press Ok and close that window.
Now you can can open the web page again and use the default credentials as if ure integrating UCCX for the first time (usr: Administrator pwd: ciscocisco)

HTH,
Nick