Actually, one point of clarification here. The service parameter Sergey is referring to ( "Inbound Calling Search Space for Remote Destination") does not play a role in digit analysis for MVA calls. That service parameter is a little misleading and confusing.
There are two call flows you have to keep in mind when dealing with ingress calls from Remote Destinations. 1. Direct inward dial from the RD to your internal dial plan (e.g. directory numbers, MML, hunt pilots, etc.) Basically, anything that is not the MVA steering digit pattern. The service parameter Sergey mentioned can affect the digit analysis applied to these calls. 2. Calls handed off by the MVA VXML application to CUCM. As Sergey noted, the IOS is terminating the call. Most of the heavy lifting is done at the gateway. The prompts, etc. are all coming by way of VXML but the call is terminated on the gateway. At least up to the point where you choose the option to place a call. At this point in time, the IOS device is going to send the call to the MVA number and the CUCM digit analysis process is going to make a routing decision based on the CSS assigned to the Remote Destination Profile (RDP), regardless of what you have set for that service parameter. So, the service parameter affects ingress calls to DIDs that are not pre-processed by the MVA VXML first. Any call that comes by way of MVA, will use the RDP CSS for digit analysis. You can test this by doing the following. Using the IPExpert topology samples. 1. Create a new partition: block-hqph1_pt 2. Put a translation in this partition 2001/block-hqph1_pt and set that translation to block the number 3. Put this partition in your RDP CSS. Ensure it is at a higher priority partition than the PT that currently holds the 2001 extension programmed on HQ Phone 1. If you use the <none> partition then it doesn't matter where you add the block PT. 4. Ensure that the service parameter "Inbound Calling Search Space for Remote Destination" is set to the default value (which is to use the GW CSS). Now, use the PSTN phone line that is associated with your RD and call 2025552001 directly. It should ring (unless you have something else messed up). Using the same PSTN phone line, call into MVA. Log into the service, press 1 to place a call and dial 2001. You should get ANN telling you that the number is unassigned. Another test that may be of interest. 1. Create a new partition: block-hqph1_pt 2. Put a translation in this partition 2001/block-hqph1_pt and set that translation to block the number 3. Put this partition in the CSS you assign to your HQ gateway. Make sure it is sitting at a higher priority than your internal phone PT (if you use one). At this point in time, any calls from the PSTN to 2025552001 will fail. 4. Set the service parameter "Inbound Calling Search Space for Remote Destination" to use RDP Device/Line CSS 5. Ensure that the RDP CSS does NOT have the block PT 6. Call 2025552001 from the PSTN line associated with your RD. It should work. So, now you can't call 2025552001 from any PSTN line EXCEPT for the line associated with the RD. That would be an interesting IE lab question. -Bill -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 7, 2013, at 10:59 AM, Sergey Heyphets wrote: > Hi Donny, > > When you dial 4 digit extension from the MVA, the IOS sends call to the MVA > number defined under Media Resources, so you must have a dial-peer that > matches that number and sends the call to the CUCM. The extension you've > dialed is transfered in the "Redirected number IE" inside the SETUP message > sent to the MVA number defined under media resources. Once the call gets to > CUCM, it extracts the extension you've dialed from the "Redirected Number IE" > and uses either Gateway CSS or RDP+Line CSS (depending on Service Parameters) > to place the call to extension. So, if your call to extension doesn't work, > you need to check that you have dial-peer that matches MVA number defined in > Media Resources, the Service Params to see which CSS you use for MVA calls > and then make sure that whatever CSS you use can reach that extension. > > I know there are some bugs with partial match in early versions of CUCM 7.X, > the workaround is to use complete match. > > Sergey > _______________________________________________ > 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
