[cisco-voip] h323 to call manager inbound calls randomly complete

Scott Irey irey at oakland.edu
Tue Mar 16 13:55:59 EDT 2010


Thanks! Funny you mentioned that as I did turn on debug ip tcp
transactions and am able to see some tcp timeouts. Haven't had much time
to go any further (not a production box) but seems to be something there.
Some negotiation of congestion window happens and then 3 tcp timeouts.
Like I said, it's not every time.

Strange.

Scott Irey
Network & Telecom Systems Engineer
Oakland University
Office: 248.370.2808
Mobile: 248.505.9827

-----Original Message-----
From: matthn at gmail.com [mailto:matthn at gmail.com] On Behalf Of Nick
Matthews
Sent: Tuesday, March 16, 2010 1:47 PM
To: Scott Irey
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] h323 to call manager inbound calls randomly
complete

Looking at this from a packet capture in a TCP level instead of odd
H323 debugs will be much more helpful.

-nick

On Mon, Mar 15, 2010 at 10:12 AM, Scott Irey <irey at oakland.edu> wrote:
> Hello,
>
>
>
> Having a problem with inbound calls from TDM completing h323 to cucm
7.1.
> Seems to be fairly random, works once or twice, next call fails, cycle
> repeats. Doing a debug CCH323 all, here is where a call fails and never
> connects.
>
>
>
> ar 15 10:51:35.455: //-1/xxxxxxxxxxxx/H323/cch323_timer_dispatch:
> Timer[CCH323_SOCK_WRITE_BLOCKED_TIMER] expired
>
> Mar 15 10:51:35.455:
> //-1/xxxxxxxxxxxx/H323/h323_gw_sock_block_timer_expired: fd 2
>
> Mar 15 10:51:35.455:
> //-1/xxxxxxxxxxxx/H323/h323_gw_start_sock_blocked_timer: fd 2
>
> Mar 15 10:51:35.455:
> //-1/xxxxxxxxxxxx/H323/h323_gw_sock_block_timer_expired: Retry, fd=2
>
> Mar 15 10:51:35.555: //-1/xxxxxxxxxxxx/H323/cch323_timer_dispatch:
> Timer[CCH323_SOCK_WRITE_BLOCKED_TIMER] expired
>
> Mar 15 10:51:35.555:
> //-1/xxxxxxxxxxxx/H323/h323_gw_sock_block_timer_expired: fd 2
>
> Mar 15 10:51:35.555:
> //-1/xxxxxxxxxxxx/H323/h323_gw_start_sock_blocked_timer: fd 2
>
> Mar 15 10:51:35.555:
> //-1/xxxxxxxxxxxx/H323/h323_gw_sock_block_timer_expired: Retry, fd=2
>
> Mar 15 10:51:35.655: //-1/xxxxxxxxxxxx/H323/cch323_timer_dispatch:
> Timer[CCH323_SOCK_WRITE_BLOCKED_TIMER] expired
>
> Mar 15 10:51:35.655:
> //-1/xxxxxxxxxxxx/H323/h323_gw_sock_block_timer_expired: fd 2
>
> Mar 15 10:51:35.655:
> //-1/xxxxxxxxxxxx/H323/h323_gw_start_sock_blocked_timer: fd 2
>
> Mar 15 10:51:35.655:
> //-1/xxxxxxxxxxxx/H323/h323_gw_sock_block_timer_expired: Retry, fd=2
>
> Mar 15 10:51:35.755: //-1/xxxxxxxxxxxx/H323/cch323_timer_dispatch:
> Timer[CCH323_SOCK_WRITE_BLOCKED_TIMER] expired
>
>
>
> Repeats this for a bit and then sends a disconnect. And I get operator
from
> the telco.
>
>
>
> Any one seen something like this before where some calls complete and
some
> don't?
>
> Scott Irey
>
> Network & Telecom Systems Engineer
>
> Oakland University
>
> Office: 248.370.2808
>
> Mobile: 248.505.9827
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


More information about the cisco-voip mailing list