[cisco-voip] traces for remote destinations?

[Erick Wellnitz]

No upgrade between the time they were working and stopped working.


On Thu, Aug 22, 2013 at 1:11 PM, Eric Pedersen
<PedersenE at bennettjones.com>wrote:

>  Was it an upgrade to 9.1? We ran into CSCue58307 and had to uncheck and
> recheck the RD line associates after we upgraded.****
>
> ** **
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Erick Wellnitz
> *Sent:* 22 August 2013 11:36 AM
> *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> 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] *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.****
>
> ** **
>
> The contents of this message may contain confidential and/or privileged
> subject matter. If this message has been received in error, please contact
> the sender and delete all copies. Like other forms of communication,
> e-mail communications may be vulnerable to interception by unauthorized
> parties. If you do not wish us to communicate with you by e-mail, please
> notify us at your earliest convenience. In the absence of such
> notification, your consent is assumed. Should you choose to allow us to
> communicate by e-mail, we will not take any additional security measures
> (such as encryption) unless specifically requested.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130822/7997eed5/attachment.html>