Re: [OSL | CCIE_Voice] mva
Great Observation. I will try some diff solutions and let you know the results Mostly it think now that Calling Name is not supported On Sun, Aug 11, 2013 at 7:38 AM, Somphol Boonjing somp...@gmail.com wrote: On Sun, Aug 11, 2013 at 11:17 AM, Somphol Boonjing somp...@gmail.comwrote: Reading through two thread originated by a candidate by the name datucha/datoc, read through it both discussion threads, you will see how confusing this can be. http://ieoc.com/forums/p/18782/162049.aspx http://onlinestudylist.com/archives/ccie_voice/2012-February/079707.html Having read through it one more time, I think there is no contradiction there. I would bet that Calling Name (CNAM) not showing up for call originating through MVA IVR is expected. Datoc said If anyone is interested: *Calling Number *is not supported for MVA calls into extenstions (or even any other destination). Got this answer from one of the CCIE Voice Instructors. Note that Datoc misspell that while he actually meant to say Calling Name. A typo which Mark's later on point out and hence his following comment. Well, calling number shows up, only it will be what Cisco calls rooted in CDR as the shared desk line. Just as any call in to UCM where calling number matches the RD will show up as the shared desk line. AND I think maybe you meant to say calling name (CNAM), not calling number (CLID) - that's what both Juan and Vik mentioned to you on OSL. To which Datoc later on agree. Yes i mean Calling Name :) Sorry for that, I just make a error in typing. So, while there is no Bug ID whatsoever, credible sources suggestion seems to be in line with real world experiment. I would be highly interested to see anyone who can produce different result for this paritcular case. (Note: Strictly for call made through MVA IVR.) Just an observation, there are a few points that worth discussing about, but this is getting long, so perhaps we can discuss it at a later point. Those topics are - MVA DID (appeared in CUCM's Call Manager service parameters) vs MVA DN (appeared on one of the Media Resource sub-menu) - The actual role of a Media Resource called MVA DN. Regards, --Somphol. ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] Per VC Frame Relay Fragmentation
I have rephrased my question slightly to highlight my dilemma which involves whether or not to configure fragmentation on all PVCs or only one out of three. *Given below detail:* HQ - SA - 64Kbps (DLCI 100) - Data Voice HQ - SB - 128Kbps (DLCI 200) - Data Only HQ - SC - 64Kbps (DLCI 300) - Data Only HQ - 256Kbps --- Aggregate WAN SA - 64Kbps SB - 128Kbps SC - 64Kbps 3xG729 between HQ-SA *Question: Configure FRF.12 with 10-ms delay for voice traffic.* [1] According to Table 3-1 Recommended Fragment Sizes, CIR, and Bc Values for Slow-Speed Frame Relay Links, it should be safe to use PVC speed as a reference point to calcualte Maximum Fragment Size (for 10-ms Delay). (As opposed to a physical interface's speed.) - http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND/WANQoS.html#wp106984 [2] Should I perform the fragmentation on DLCI 200 DLCI 300 or not? I think it is reasonable to assume that since all of these PVCs will share the same physical interface, fragmenting only for large frame in DLCI 100 is not enough, therefore I think it is necessary to also fragment DLCI 200 DLCI 300. [For reference, under section FRF.12 on this link, it is stated - http://www.cisco.com/en/US/tech/tk652/tk698/technologies_configuration_example09186a0080094af9.shtml ...Any other PVCs that share the same physical interface need to configure the fragmentation to the size used by the voice PVC...] *If I have to bet, should I bet on performing fragmentation on all PVCs or only perform fragmentation on HQ-SA's PVC?* *Sample configuration below:* Class-map match-any signal match ip dscp cs3 Class-map match-any voice match ip dscp ef policy-map LLQ class voice priority 48 class signal bandwidth 8 class-default fair-queue policy-map SHAPE-SA class class-default shape average 64000 service-policy LLQ-SA policy-map SHAPE-SB class class-default shape average 128000 fair-queue policy-map SHAPE-SC class class-default shape average 64000 fair-queue map-class frame-relay HQ-SA frame-relay fragment 80 service-policy output SHAPE-SA map-class frame-relay HQ-SB frame-relay fragment 160 service-policy output SHAPE-SB map-class frame-relay HQ-SC frame-relay fragment 80 service-policy output SHAPE-SC interface serial 0/0 encapsulation frame-relay interface serial 0/0.1 point-to-point ip address 192.168.1.1 255.255.255.0 frame-relay interface-dlci 100 class HQ-SA interface serial 0/0.2 point-to-point ip address 192.168.2.1 255.255.255.0 frame-relay interface-dlci 200 class HQ-SB interface serial 0/0.3 point-to-point ip address 192.168.3.1 255.255.255.0 frame-relay interface-dlci 300 class HQ-SC Regards, --Somphol. On Tue, Aug 6, 2013 at 6:16 PM, Somphol Boonjing somp...@gmail.com wrote: Hi, Can anyone help confirm my understanding on this topic? My observation is that Per VC fragmentation, while it can be configured as when in the example below, is not very useful if not configured for all of the existing PVC that shared the same physical interface, isn't it? With the example below, only one of the VC (DLCI 100) is configured for fragmentation while the rest of the VCs (DLCI 200 DCLI 300) that shared the same physical interface are not, then potentially outgoing fragmented frames from DLCI 100 could be waiting in queue while a fragmented large data frames from DLCI 200/DLCI 300 is being sent out. Am I correct? (REF: http://www.cisco.com/en/US/docs/ios-xml/ios/wan_frly/configuration/12-4t/wan-mqc-fr-tfshp.html#GUID-BAC1F514-EBD4-48FF-87AB-41F2BF86463E ) Class-map voice match ip dscp ef policy-map llq class voice priority 32 policy-map shape-policy-map class class-default shape average 64000 shape adaptive 32000 service-policy llq map-class frame-relay shape-map-class frame-relay fragment 80 service-policy output shape-policy-map interface serial 0/0 encapsulation frame-relay interface serial 0/0.1 point-to-point ip address 192.168.1.1 255.255.255.0 frame-relay interface-dlci 100 class shape-map-class interface serial 0/0.2 point-to-point ip address 192.168.2.1 255.255.255.0 frame-relay interface-dlci 200 interface serial 0/0.3 point-to-point ip address 192.168.3.1 255.255.255.0 frame-relay interface-dlci 300 Regards, --Somphol ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
[OSL | CCIE_Voice] MOH multicast
folks, I try to configure MOH using multicast for SB site. here is what i did : = SB router: -- call-manager-fallback moh music-on-hold.au multicast moh 239.1.1.1 po 16384 route 142.1.65.254 142.102.65.254 max-dn 20 max-ephone 10 ip source 142.102.65.254 po 2000 ip multicast-routing UCM : --- Region : MOH G711 to all sites MOH DP : MOH region MOH server SUB : check Enable Multicast 239.1.1.1 , port 16384 , Max Hop : 2 assign the MOH DP MRG-MOH : contain above MOH SUB, check multicast assign to MOH MRGL SB DP and SB GW : assigned the MOH MRGL Add G729 to IP Voice media streaming and restart UCM and IPVM services Test: --- - call from SB phone to PSTN, and press ON Hold, but even Hold key is not in effect here ? - sh ccm-manager musin-on-hold = 0 - debug ccm-manager moh events : did not give clear indication what missing. Any idea , what I missed here? tks K___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
[OSL | CCIE_Voice] CUCCX
CUCCX is not supposed to be this hard. I know I a missing something. My CTI ports are regisested, they are both in the correct DP, and CSS. The phones are in the same CSS and they can call each ohter. The trigger is correct and it is also in the correct CSS and DP. The ccx user is the correct CSS and DP. Goes immediatly to the promp thank you for calling. all our reps are assiting other callers at this time Not showing up in the queue. Yipes!___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] CUCCX
Never mind. I just figured it out. DUH! CSQ skill level was too high. From: Michael Davis michaeldavis1...@yahoo.com To: ccie_voice@onlinestudylist.com ccie_voice@onlinestudylist.com Sent: Sunday, August 11, 2013 5:22 PM Subject: CUCCX CUCCX is not supposed to be this hard. I know I a missing something. My CTI ports are regisested, they are both in the correct DP, and CSS. The phones are in the same CSS and they can call each ohter. The trigger is correct and it is also in the correct CSS and DP. The ccx user is the correct CSS and DP. Goes immediatly to the promp thank you for calling. all our reps are assiting other callers at this time Not showing up in the queue. Yipes!___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] MOH multicast
Karen Do you have ccm-manager music-on-hold configured on the global config? On Aug 11, 2013 1:35 PM, Karen Johnson karen.johnson...@yahoo.ca wrote: folks, I try to configure MOH using multicast for SB site. here is what i did : = SB router: -- call-manager-fallback moh music-on-hold.au multicast moh 239.1.1.1 po 16384 route 142.1.65.254 142.102.65.254 max-dn 20 max-ephone 10 ip source 142.102.65.254 po 2000 ip multicast-routing UCM : --- Region : MOH G711 to all sites MOH DP : MOH region MOH server SUB : check Enable Multicast 239.1.1.1 , port 16384 , Max Hop : 2assign the MOH DP MRG-MOH : contain above MOH SUB, check multicast assign to MOH MRGL SB DP and SB GW : assigned the MOH MRGL Add G729 to IP Voice media streaming and restart UCM and IPVM services Test: --- - call from SB phone to PSTN, and press ON Hold, but even Hold key is not in effect here ? - sh ccm-manager musin-on-hold = 0 - debug ccm-manager moh events : did not give clear indication what missing. Any idea , what I missed here? tks K ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
Re: [OSL | CCIE_Voice] Access list for cue traffic marking
This might be worth revisiting.Forgive me if this is not entirely a new insight. In short, be aware that as soon as the command service-policy input XXX in entered into the configuration, the mls qos trust cos/dscp will be removed. Likewise, if the command mls qos trust cos/dscp is re-entered, the command service-policy input XXX will be automatically removed. http://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a0080883f9e.shtml - If any other QoS Classification methods, such as port based or VLAN based, are configured on the port gi 1/0/3, those configurations are removed when you apply the policy-map. For example, the port Gi 1/0/13 is configured to trust CoS as shown here: interface GigabitEthernet1/0/13 description Access Port switchport access vlan 10 switchport mode access switchport voice vlan 100 mls qos cos 3 mls qos trust cos spanning-tree portfast - When you apply the policy-map to the interface, it removes the *trust* command. Distribution1(config)#*int gi 1/0/13* Distribution1(config-if)#*service-policy input sample-policy1* Distribution1(config-if)#*do show run int gi 1/0/13* Building configuration... Current configuration : 228 bytes ! interface GigabitEthernet1/0/13 description Access Port switchport access vlan 10 switchport mode access switchport voice vlan 100 service-policy input sample-policy1 *!--- It replaces the mls qos trust or mls qos !--- vlan-based command.* mls qos cos 3 *!--- This command is not removed.* spanning-tree portfast end Regards, --Somphol. On Mon, Jul 8, 2013 at 12:42 PM, jainpiyush2...@ymail.com wrote: Steve, you absolutely make sense that traffic for cue can be marked on router (site c) on which cue module is connected when it goes out on wan link.. and then on the trunk port on hq switch we would have trust statement. However the question in lab expect us to mark the cue traffic on hq switch on the port connected to sub cucm.. so the above solution won't work.. right? Thanks and regards, Piyush Jain Sent from my android device. -Original Message- From: sbar...@mystictraveler.net To: LorenzLGRC lorenzl...@gmail.com, Piyush Jain jainpiyush2...@ymail.com Cc: ccie_voice@onlinestudylist.com ccie_voice@onlinestudylist.com Sent: Mon, 08 Jul 2013 6:23 AM Subject: RE: [OSL | CCIE_Voice] Access list for cue traffic marking Maybe I am missing something so please forgive me, and to recap, the question was LAN QoS and CUE (not WAN). The example below (which is pretty much out of the SRND) will correctly mark the traffic, but only going out the serial port. It seems to me that you would want to mark the traffic inbound from the CUE module to the router in which it resides so that no matter how the traffic exits the router it will be handled correctly. Can you mark the traffic as it leaves the AIM module and is passed to the router? As far as the policy map on the serial port, wouldn't we want to see all traffic correctly prioritized not just the CTI-QBE to answer the question correctly if we were to look at the WAN QoS? I assume for traffic leaving on an LAN port to a switch, the switch would have the appropriate trust statements and since we marked on the packets as they transition from the AIM to the router prioritization and re-marking would not be an issue? Steve Original Message Subject: Re: [OSL | CCIE_Voice] Access list for cue traffic marking From: LorenzLGRC lorenzl...@gmail.com Date: Sun, July 07, 2013 5:25 am To: Piyush Jain jainpiyush2...@ymail.com Cc: ccie_voice@onlinestudylist.com ccie_voice@onlinestudylist.com Hello, you can use something like this: access-list 101 permit tcp host a.b.c.d any eq 2748 ! class-map match-all cti-qbe match access-group 101 ! policy-map cti-qbe class cti-qbe set dscp af31 bandwidth 20 ! interface Serial0/1 service-policy output cti-qbe On Sun, Jul 7, 2013 at 6:06 AM, Piyush Jain jainpiyush2...@ymail.comwrote: Hi Guys, I am trying to understand how we can mark CUE traffic on HQ Switch to implement LAN QOS. I have come up with the below solution. ip access-list extended name CUE permit tcp host 142.100.64.12 host 142.1.66.253 eq 2748 class-map match-any CUE-CLASS match access group name CUE policy-map CUE-POLICY class CUE-CLASS set ip dhcp CS3 int fa 1/0/4 description * CONNECTED TO SUB CUCM *** service policy input CUE-POLICY In above config, 142.100.64.12 is SUB CUCM, 142.1.66.253 is CUE on SC router. Explanation: Since we are applying service policy in incoming direction on switch port connected to CUCM, so the source port number (of CUCM) can be anything but destination port number (i.e for CUE) should be 2748 (JTAPI port). Any advice or inputs are most welcome. Cheers !! Piyush Jain
