[cisco-voip] Where do I start trouble shooting the Bug?

[Wes Sisk]

A quick chat between the CM and Unity teams -
We can't figure out how you get 5Mbps in this scenario unless a network 
loop and possibly ICMP unreachables with full payload instead of headers.

That said the root of the problem sounds like Unity Connection not 
hanging up.  Unity Connection does not understand call preservation as 
best we can tell - i.e. UC does not take any action when CM sends "temp 
fail", "cm down features disabled", softkey updates, callstate update, 
or any other indication of call preservation.

It is a pretty common issue for systems to be configured with a greeting 
loop. A greeting loop will loop through greetings if user ever stops 
providing input.  This is essentially what happens with call preservation. 

The Unity team is on board to look for a greeting loop to help 
automatically terminate the call.

This would not explain how the ASA reached 5Mbps on the inside 
interface.  That investigation would start with packet captures at the 
ASA and work backward from there.  Multiple people posited, and I tend 
to agree, that a network loop must be involved somehow.  Some napkin math:
5Mbps = 39 G.711 calls @ 128kbps
if route to remote PC goes down there will be ICMP unreachables 
generated. there are usually header only but if they contained full 
payload somehow then ICMP would account for 50% of traffic
5Mbps = (19 G711 calls @ 128kbps)*2 if ICMP *every* RTP packet

Even this doesn't add up for 1 single user. Possibly if that user were 
in a conference with 18 other WAN users?  It just gets more hypothetical 
from there. Packet captures on ASA would show traffic, source, and 
headers to look for loops.

/Wes

Scott Voll wrote:
>
> Puckers--
>
>  
>
> I’m not sure how to open a ticket with Cisco on this as so much is at 
> play.
>
>  
>
> ASA running 8.2.4.  anyconnect client running 2.5.1024.  IPC 7.0.5.1 
> Unity connection 7.1.5.32018-24.  CM 7.1.5.31900-3.
>
>  
>
> Telecommuter is VPN’d in and using their softphone.  Not sure what 
> happens… Disconnect possibly.  But Locks a UC port and streams large 
> amounts of traffic to the ASA on the inside.  Only way to clear it is 
> to find the port that is locked in RTMT then go to UC and restart 
> port.  Then it stops streaming traffic.  Where do I start with opening 
> a ticket? ASA group, CM group, or the UC group?
>
>  
>
> See Graph of the issue on the ASA attached.
>
>  
>
> Thanks
>
>  
>
> Scott
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20101228/9c723abb/attachment.html>