[cisco-voip] SDI message

[Wes Sisk]

Sometimes that would invoke code yellow.  Do you see any of those? 
perfomon counter under "callmanger systems performance" or in the 
application event log/syslog search for 'yellow'.

However, in my lab recreates I can consistently trigger delay dialtone 
without code yellow.  If you want to zip up a large batch of CM SDI 
traces and upload to ftp://ftp-sj.cisco.com/incoming I think I have some 
scripts to parse looking for delayed dialtone.  Upload and then send me 
the filename if you're interested.

/Wes

On Friday, April 10, 2009 11:22:51 AM, Ed Leatherman 
<ealeatherman at gmail.com> wrote:
> Thanks Wes, trying to troubleshoot some false positive's i'm getting
> from NetQoS voice monitor... wanted to get all my ducks in a row
> before I call tech support. It's picking up 20-30 seconds of delay to
> dialtone specifically on consultative transfers (yikes). No one I've
> followed up with on specific calls has ever noticed a problem and the
> SDI traces corroborate with that. So I'm thinking either a bug or the
> product isn't setup properly.
>
> On Thu, Apr 9, 2009 at 11:56 PM, Wes Sisk <wsisk at cisco.com> wrote:
>   
>> you got it. pressing line button 4.
>>
>> On Thursday, April 09, 2009 7:34:47 PM, Ed Leatherman
>> <ealeatherman at gmail.com> wrote:
>>     
>>> Anyone know what this SDI trace message means?
>>>
>>> CCM|StationInit: (0005055) Stimulus stimulus=9(Line) stimulusInstance=4.
>>>
>>> I realize it's a message coming in from that phone (0005055), just not
>>> sure what it means the caller is doing. Pushing the line button 4?
>>>
>>> Thanks!
>>>
>>>
>>>       
>>     
>
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090410/a30b7699/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ftp-sj.doc
Type: application/msword
Size: 24576 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090410/a30b7699/attachment.doc>