[cisco-voip] traces for remote destinations?

[Daniel Pagan]

Cool - I'd say if the line association box was the issue, then your traces should show the RDP missing from the listed called devices for "dispatchToAllDevices". For the successful call, you should see an additional device listed by Line Control - that being the RDP. If it's the rerouting CSS, the trace should show a missing digit analysis results for the DA matching attempt.

From: Erick Wellnitz [mailto:ewellnitzvoip at gmail.com]
Sent: Thursday, August 22, 2013 1:36 PM
To: Daniel Pagan
Cc: cisco-voip
Subject: Re: [cisco-voip] traces for remote destinations?

I did get it working.  Set dedicated rerouting CSS with only the outbound PT defined and unchecked then checked the line association box.

I'm still going to sift through the traces with this info and see what I can dig up.

On Thu, Aug 22, 2013 at 11:06 AM, Daniel Pagan <dpagan at fidelus.com<mailto:dpagan at fidelus.com>> wrote:
If you're referring to outbound routing (not matching RemDest w/ calling number), then my first step would be to check if digit analysis is being attempted to the remote destination -- search for dd="<DialedNumber>" including quotes. Perhaps the call is failing at DA (wrong rerouting css).

If you don't see DA for the destination number, then I'd take a step back and see if LineControl is sending the call to the RDP (in addition to the user's phone devices). Marking the 2nd CI in Notepad++ should lead you to the LineControl instance located slightly below DA results. The dispatch to all devices lines should list all the IP phone devices receiving the call, including the RDP.

I've also found that searching for "initRemDest" helps for finding a remote destination being dialed.

So.. I guess the order should be...


1.       Traces set to detailed (sorry.. had to say it...)

2.       Use 2nd CI to determine if LineControl is dispatching the call to the RDP... if yes then..

3.       Search for "initRemDest" - should show what destination is being dialed. Also useful if you're not sure how to find the CI.

4.       Few lines below initRemDest should be the DA results - if successful then next is determining the status of the outbound call attempt. If no successful DA results are found, then likely a Rerouting CSS issue on the profile.

Hope this helps

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Erick Wellnitz
Sent: Thursday, August 22, 2013 11:07 AM
To: cisco-voip
Subject: [cisco-voip] traces for remote destinations?

CUCM version 9.1

What should I be looking for in the SDL traces to troubleshoot Remote Destination issues?  Im not finding anything concrete.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130822/8e46b060/attachment.html>