CER - Configuration

        After installation of the Cisco Emergency Responder (E911), the configuration is a little confusing if you haven't done it in a while or if it is your first time. Not many states require E911 capabilities and it is an extra cost that you must enable with your provider.

1. Enable SNMP - E911 uses SNMP to utilize CDR to discover IP phones that are connected
1. Enable SNMP on the switch
1. "snmp-server community <SNMP-String> RO"
2. Make the SNMP String something more cryptic than just "public"
3. RO stands for Read Only
2. Enable SNMP on CUCM 
1. In the top-right corner, under Navigation, select "Cisco Unified Serviceability" and click Go
2. Select SNMP V1/V2c > Community String and click "Add New"
3. Enter the community string that you created on the switch and select "Accept SNMP Packets from any host"
4. For Access Privileges select "ReadOnly", checkmark "Apply To All Nodes" and click Save.
3. Enable SNMP on E911
1. In CER Administration select Phone Tracking > SNMP Settings
2. Add New SNMP entries for CUCM and the switches
1. *.*.*.* is a valid catchall statement

1. Configure Phone Tracking
1. In E911 select Phone Tracking > LAN Switch Details
1. Enter the Switch IP or Host Name, Description and click Insert
2. Do this for each switch in your network containing IP Phones

1.  Add CUCM nodes to E911
1. Add an Application User in CUCM
1. In CUCM Administration, select User Management > Application User and click on "Add New"
2. Create a new user called "CER_User"
3. Assign the Permissions: Standard CCM End Users, Standard CTI Allow Calling Number Modification, and Standard CTI Enabled
2. Add the same Application User in E911
1. In E911 Administration, select Phone Tracking > Cisco Unified Communications Manager Clusters
2. Add New cluster and enter the CUCM IP address, CER_User with password, and the BackUp CTI Manager(s) which are your CUCM Subscribers

1. Create a CTI Route Point - Used to communicate between CUCM and E911
1. In CUCM Administration go to Device > CTI Route Point and click Add New
2. Create a RP911 Route Point with no Calling Search Space (we will add this later)
3. Add a DN for RP911. This DN will be "911" for users to dial. Place this 911 DN in the E911 Partition.
1. The E911-PT should be at the TOP of all CSS lists so that phones will match this first.
2. Leave the CSS blank for now and we'll add it later

1. Import IP Phone Information into E911
1. In E911 Administration go to Phone Tracking > Run Switch-Port & Phone Update
2. IP Phones will show up under ERL Membership > Switch Ports
3. 
   
4. In E911 select System > Cisco ER Group Settings

.

VGW - TSHOOT (T1 or E1)

For a T1 or E1 PRI troubleshooting, follow the following steps.

1. show controllers [t1 | e1] 
1. Check most of the PRI fields by this show controllers command.
2. Ensure that line coding, framing, and clock source are configured and match the settings set by your Service Provider
1. Line Coding
1. T1 - Bipolar-8 Zero Substitution (B8ZS) and Alternate Mark Inversion (AMI) 
1. B8ZS - (also called Clear Channel and Binary 8 Zero Substitution) replaces each string of 8 consecutive zeros with the special pattern "000VB0VB" 
2. AMI -  Each successive mark is inverted and the average or DC level of the line is therefor zero
2. E1 - High Density Bipolar of Order 3 (HDB3)
2. Framing
1. T1 - Super Frame (sf) and Extended Super Frame (esf) - not compatible with each other
1. Super Frame - consists of 12 consecutive 193-bit frames
2. Extended Super Frame - consists of 24 consecutive 193-bit frames
1. E1 - framing crc4 (cyclic redundancy check) and no-crc4
3. Check if the line is down
1. Make sure the controller is NOT administratively down. Perform a "no shut" command on the Controller interface.
4. Check for reported alarms
1.  Use the show controllers command to see if there are any alarms on the controller.
2. Receive Alarm Indication Signal (BLUE)
1. 
   
5. Check for error events
6. Check if the interface is T1 or E1 CAS, E1 R2, or PRI

show controllers t1

T1 0/3/0 is up.

  Applique type is Channelized T1

  Cablelength is long 0db

  Description: Qwest LongDist #4 CID DS1-1234567

  No alarms detected.

  alarm-trigger is not set

  Soaking time: 3, Clearance time: 10

  AIS State:Clear  LOS State:Clear  LOF State:Clear

  Version info Firmware: 20100222, FPGA: 13, spm_count = 0

  Framing is ESF, Line Code is B8ZS, Clock Source is Line.

  CRC Threshold is 320. Reported from firmware  is 320.

  Data in current interval (155 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

  Total Data (last 24 hours)

     0 Line Code Violations, 0 Path Code Violations,

     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

VGW - Troubleshooting

Docwiki Troubleshooting T1

• show controller T1
• show isdn status
• show voice port summary
• show dial-peer voice [summary]
• show call history voice
• show call active voice
•  
• show rawmsg
• show cdapi
• debug isdn event
• debug tsp
• debug cdapi
• debug voice ccapi inout
• Traces the execution path through the call control API, which serves as the interface between the call session application and the underlying network specific software
• debug isdn q931
• debug isdn q921
• debug vpm
• debug vpm all
• debug vpm spi
• debug vpm signal
• debug vpm dsp
• debug vtsp
• debug vtsp session
• debug vtsp error
• debug vtsp dsp

.

UCCX - High Availability

Cisco Contact Center Express offers high availability (HA) over the LAN and now over the WAN (HAoWAN for version 8.x and higher). At least UCCX Enhanced is needed for High Availability and 80ms round-trip is required for HAoWAN deployments. Cisco took away the support for a "Cold Standby" server option in UCCX 8.X.








.