[cisco-voip] RTMT logs for disconnect signal of RCC

Jefflin Choi jefflin.choi at gmail.com
Thu Feb 5 03:22:53 EST 2015


cheers mate.

On Thu, Feb 5, 2015 at 12:02 AM, Brian Meade <bmeade90 at vt.edu> wrote:

> Jefflin,
>
> Usually you just want to hit Default then set trace level to Detailed.  If
> SIP is involved, also want to enable SIP Stack trace.
>
> Having all the default traces enabled just makes sure nothing gets missed.
>
> Brian
>
> On Tue, Feb 3, 2015 at 11:29 PM, Jefflin Choi <jefflin.choi at gmail.com>
> wrote:
>
>> Thanks all. we are still running ver 8.5. I don't see any On Hook with it
>> unfortunately.
>>
>> logged ticket with vendor then TAC and turns out they wanted me to get
>> detailed traces instead of Arbitrary. weird part is they want me to mostly
>> all traces including PRI trace, Enable DT-24+/DE-30+ Trace, Enable
>> Annunciator Trace , Enable Music On Hold Trace , etc. Even MGCP trace.Can't
>> understand why since we do not use MGCP.
>>
>>
>>
>> On Mon, Jan 26, 2015 at 7:31 PM, Rajamani N <rajamani85 at gmail.com> wrote:
>>
>>> Please do look into the SIP Proxy logs from the CUPS, you can see the
>>> CSTA events for RCC in them
>>>
>>> -Rajamani
>>>
>>> On Sat, Jan 24, 2015 at 2:45 AM, Brian Meade <bmeade90 at vt.edu> wrote:
>>>
>>>> 9.x has the interleaved traces as well.
>>>>
>>>> On Fri, Jan 23, 2015 at 4:10 PM, Ryan Ratliff (rratliff) <
>>>> rratliff at cisco.com> wrote:
>>>>
>>>>> For an SCCP phone you'll see a StationInit from CCM to the phone
>>>>> instructing the phone to go OnHook.  Using SDL traces you can follow that
>>>>> back to where it originated from, which will likely be CTI if I recall how
>>>>> RCC works correctly.
>>>>> This tracking is much easier in 10.x with interleaved traces.
>>>>>
>>>>> -Ryan
>>>>>
>>>>> On Jan 23, 2015, at 6:55 AM, Jefflin Choi <jefflin.choi at gmail.com>
>>>>> wrote:
>>>>>
>>>>> All,
>>>>>
>>>>> We have lync remote call control integrated on our CCM/CUPS system.
>>>>> I'm troubleshooting some call disconnect issues basically.
>>>>>
>>>>> Does anyone know which criteria to look for if it's caused by the lync
>>>>> RCC on CCM and CUPS traces?
>>>>>
>>>>> If it's SIP phone, 9951 did saw one time with SIP REFER Message to the
>>>>> phone  to disconnect on CCM traces though not sure if this is also the case
>>>>> with SCCP phones.
>>>>> Softkey event does show me if it was an end call press but i don't
>>>>> think this applies if it was triggered by closing the call dialog box on
>>>>> lync.
>>>>>
>>>>> What's the normal logging trace configuration that needs to be enabled
>>>>> also?
>>>>>
>>>>> TIA,
>>>>> Jeff
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150205/0fd2989d/attachment.html>


More information about the cisco-voip mailing list