[cisco-voip] strange uccx 7.0 issue

[Erick Wellnitz]

Oops.  Here are the files direct from the MIVR directory.

On Sat, Aug 11, 2012 at 7:15 AM, Ryan LaFountain (rlafount) <
rlafount at cisco.com> wrote:

>   Hi Eric,
>
>  Did you copy the log file content to a text file through RDP or VNC?
> They are all on a single line and impossible to read.
>
>  Please copy the actual .log file from the server and send them along.
> I'll be able to parse them pretty easily and will let you know what I see.
>
>  Thank you,
>
>  Ryan LaFountain
> Unified Contact Center
> Cisco Services
> Direct: +1 919 392 9898
> Email: rlafount at cisco.com
> Hours: M – F 9:00am – 5:00pm
>
>   From: Erick Wellnitz <ewellnitzvoip at gmail.com>
> Date: Friday, August 10, 2012 5:04 PM
> To: Ryan LaFountain <rlafount at cisco.com>
> Cc: cisco-voip <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] strange uccx 7.0 issue
>
>   Ryan,
>
>  Attached are three MIVR logs from the timeframe surrounding one of the
> calls yesterday.
>
>  Any external call to 1234 exhibits the same behavior.  Time of call was
> 15:44
>
>  I see a lot of exceptions but I'm really rusty on reading these logs.
>
> On Fri, Aug 10, 2012 at 3:32 PM, Ryan LaFountain (rlafount) <
> rlafount at cisco.com> wrote:
>
>>   Hi Erick,
>>
>>  With the symptoms you've described I would look for some type of call
>> loop. If that isn't it, send along the MIVR traces and the call
>> information, time, etc. and I'll check 'em out.
>>
>>  Thank you,
>>
>>  Ryan LaFountain
>> Unified Contact Center
>> Cisco Services
>> Direct: +1 919 392 9898
>> Email: rlafount at cisco.com
>> Hours: M – F 9:00am – 5:00pm
>>
>>   From: Erick Wellnitz <ewellnitzvoip at gmail.com>
>> Date: Friday, August 10, 2012 3:59 PM
>> To: cisco-voip <cisco-voip at puck.nether.net>
>> Subject: [cisco-voip] strange uccx 7.0 issue
>>
>>   I have a really strange issue.  I have 1 trigger misbehaving across
>> the WAN.
>>
>>  The number comes in at the remote site as 1234, should play prompts if
>> the agents are busy or do it's normal agent selection routine. This works
>> fine dialing 1234 from a cisco phone.  When an outside caller calls
>> 555-555-1234 the call maxes out our configured maximum sessions in short
>> order and reserves all of the available agents.
>>
>>  Anyone seen this kind of behavior before?  Any ideas as to what to look
>> for in the logs/traces?
>>
>>  It shouldn't be a codec mismatch or  I would expect a fast busy.
>>
>>  Thanks!
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120813/1db25946/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Cisco001MIVR125.log
Type: application/octet-stream
Size: 3159631 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120813/1db25946/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Cisco001MIVR126.log
Type: application/octet-stream
Size: 3157895 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120813/1db25946/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Cisco001MIVR127.log
Type: application/octet-stream
Size: 3159267 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120813/1db25946/attachment-0005.obj>