When reading through the lab initially, be very careful to not read too much into the lab during the first few minutes. Don’t spend great detail reading about a section that you will touch six or seven hours later. Points to touch and understand initially: infrastructure, CUCM/CUCME phones, call routing, QoS, type of voicemail integration (avoid specific messaging questions), and presence integration.
1.0 Infrastructure
2.0 Call Routing
- For CUPC devices, you must enter the name as UPC<USERNAME> where the username is entered in upper-case (case-sensitive).
- For CUCM dial plans with sites in multiple countries (numbering plans), create route partition like PT-PSTN-NANP and PT-PSTN-ENP.
3.0 Single Number Reach
- To affect the amount of time a terminated mobility call remains at the desk phone, configure the Maximum Wait Time for Desk Pickup setting under End Users.
- Application dial rules are necessary when configuring remote destinations. Otherwise, outbound calls to the remote destination will fail because the system is trying to dial 2123942123 instead of 9-1-212-394-2123.
- Display of caller ID for the remote destination profile will be missing by default. When a shared line is created, only the Alerting Name is copied from the line. Go to the DN configuration of 5002 and select RDP > Associated Devices list < Edit Line Appearance > Change caller ID name.
- Make sure to configure the Owner User ID on the Cisco IP phone used for single number reach. After adding this ID, you will need to reset the phone. Otherwise, you may get an error about not being a valid mobile phone user.
4.0 Messaging
- CUE Reload Process
- Reset factory default (reload)
- Install license (reload)
- CLI setup (reload)
- Finish GUI (optional, but requires reload
- The CUE pilot is created in CUCM as a CTI Route Point.
- The CUE ports are created in CUCM under DEVICES > PHONES > CTI Port
- If the CUE CTI ports in CUCM will not register, try restarting CTI Manager in CUCM.
- I had a horrible issue with my voicemail hunt list not working. At first, I thought it was an issue with the Unity Connection to CUCM integration. I finally realized that it was a problem separate from the integration. How? I called the voicemail port numbers directly. When I dialed them, the calls went through just fine. In the end, after resetting the hunt list, all my calls to voicemail worked correctly.
- If a CUC integration is preconfigured but the voicemail ports are not registering, it is easier to simply rip out the integration on the CUCM side, validate the CUC side, and then add the CUCM side back in.
- To allow users to call voicemail during times of network congestion, make sure to setup AAR and external number masks correctly. You will also need to configure an alternate extension under the user configuration in Unity Connection. Refer to the “debug isdn q931″ for the exact number that should be entered.
- To setup voicemail access through the CUPC client, there are two changes that must be made to the Class of Service in Unity Connection:
- Allow Users to Access Voice Mail Using an IMAP Client > Allow Users to Access Message Bodies (selected)
- Allow Users to Use Unified Client to Access Voice Mail (checked)
5.0 Quality of Service
- Before you can apply a class to a Serial sub-interface, you must go to “interface Serial 0/0/1:0″ and issue a “no fair queue” to remove the fair queue argument.
- “auto qos voip” | “auto qos voip trust” – These commands will configure QoS with FRF.12
- “auto qos voip fr-atm” | “auto qos voip trust fr-atm” – These commands will configure QoS with MLP LFI, PPP Multilink
- If you are asked to do class-based shaping, it’s best to not trust the packets in your auto qos command. Instead, issue an “auto qos voip” and let the router add its own classification and marking. Otherwise, you will need to touch CUCM, CUC, SCCP in IOS, MGCP in IOS, VoIP dial peers (use “ip qos dscp af31 signaling” by default).
- CoS is the default trust entered by “auto qos voip trust”. We would need to change this on interfaces from routers or servers. It is a layer 2 v. layer 3 issue.
- Queue-set 1 is used by all switch port by default.
- Pay attention to the different between interface- and class-based cRTP.
- Remember to mark on the ingress and queue on the egress. In other words, you will have two separate policy-maps.
- Layer two overhead: MLP (9 bytes), FR or FRF.12 (6 bytes).
- G.729 10 ms = 10 bytes, 20 ms = 20 bytes, 30 ms = 30 bytes
- G.711 10 ms =80 bytes, 20 ms = 160 bytes, 30 ms = 240 bytes
- 20 ms sampling rate: (L2 + L3 + Payload) * 8 * 50
- 30 ms sampling rate (L2 + L3 + Payload) * 8 * 33
- Verify 3750 interface configuration using “clear counters” | “show mls qos interface FastEthernet 1/0/2 statistics”.
- Ingress 3750 queues: 2 queues, SRR shared only
- mls qos srr-queue input priority-queue 1 bandwidth 10
- mls qos srr-queue input bandwidth 4 4
- mls qos srr-queue input cos-map queue 1 threshold 2 1
- mls qos srr-queue input priority-queue 1 0 - Disables priority queue for Q1
- mls qos srr-queue input priority-queue 2 0 - Disables priority queue for Q2
- Egress 3750 queues: 4 queues, SRR shared + shaped
- mls qos srr-queue output cos-map queue 1 threshold 3 5
- mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
- mls qos srr-queue output cos-map queue 3 threshold 3 2 4
- mls qos srr-queue output cos-map queue 4 threshold 2 1
- mls qos srr-queue output cos-map queue 4 threshold 3 0
- interface FastEthernet 1/0/7
- srr-queue bandwidth share 10 10 60 20 – Priority 3
- srr-queue bandwidth shape 0 4 0 0 – Priority 2
- priority-queue out – Priority 1
6.0 Applications
7.0 Presence
- If I am asked to configure CUCM Presence with call lists, I will need to configure the following CallManager service parameters:
- Default Inter-Presence Group Subscription
- BLF for Call Lists
- Do a search in the CUCM SRND for “IPPM” in order to find the URL for the phone service configuration.
- By default, leave your Presence SIP trunk in the standard presence group so that it can see everyone’s presence information.
- Next time I do this lab, I am going to try configuring one presence group per site. Assign this group to the phones and the lines. You will then need to go to SYSTEM > PRESENCE and disallow presence subscription from one group to another.
- Presence information for Extension Mobility is assigned under the End User Configuration in CUCM. You can modify the presence group and SUBSCRIBE calling search space.
