[cisco-voip] Inbound H.323 calls stopped working with CCM 5.1.1-3126-1

[Erick Bergquist]

Naw... was late and such.  Just was wondering if anyone knew about a
problem like this or not, going to plan an update to 5.1.3 anyway.


On Mon, Mar 17, 2008 at 9:41 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
> I'd imagine just the system and application event logs would be where
>  CSA would log alerts for blocking activity.
>
>  It's also possible the thread that listens for data on port 1720 died
>  within the callmanager process.  Did you try restarting CallManager
>  before the reboot?
>
>  -Ryan
>
>
>
>  On Mar 17, 2008, at 10:41 AM, Erick Bergquist wrote:
>
>  We did not get a sniffer trace (was remote sites) and outbound calls
>  worked but we did not try to register a phone to the publisher/primary
>  server which we had to reboot and make a call due to it being late on
>  a Friday, etc.  The primary and secondary server are on the subnet,
>  and the router could reach both servers with ping. I should have tried
>  to telnet to port 1720. There were about 3-4 remote sites who had
>  their main dial peer set to use the primary server also (one we had to
>  reboot) that also had calls failing until we adjusted the preferences
>  on the dial peers.  Is there a CSA log to see if CSA was blocking
>  something maybe?
>
>  Thanks
>
>  On Mon, Mar 17, 2008 at 9:25 AM, Ryan Ratliff <rratliff at cisco.com>
>  wrote:
>  > Did you happen to get a packet capture of the failing calls?  If you
>  >  weren't seeing anything in the CCM traces it sounds like the gateway
>  >  wasn't even able to establish a TCP session with the server.
>  >
>  >  Did you test any outbound calls from a phone registered to that
>  >  subscriber out via the H.323 gateway?
>  >
>  >  -Ryan
>  >
>  >
>  >
>  >  On Mar 17, 2008, at 8:47 AM, Erick Bergquist wrote:
>  >
>  >  Hi,
>  >
>  >  Had an issue where inbound calls on a PRI stopped working to one
>  >  server, and routing calls to the other server worked.  Rebooting of
>  >  the one server solved the problem.
>  >
>  >  The CCM Detailed traces showed no sign of a inbound call occurring
>  >  (just normal keepalive messages in the traces, no H225, and they were
>  >  on detailed - I saw the gateway reset in the traces). All the
>  > services
>  >  were started and there were no errors in the application log that
>  > were
>  >  related besides a port on a VG224 trying to register which I
>  >  corrected.
>  >
>  >  The Call Manager version is 5.1.1-3126-1 (ES 26 I believe) and I
>  >  looked at the release notes for 5.1.1-4000 but it doesn't have a list
>  >  of what is resolved bug wise, and saids to use bug toolkit to see
>  > what
>  >  was fixed.  Does anyone know of a issue in this version that could
>  >  stop inbound H.323 calls to stop working and not show up in the
>  >  traces?
>  >
>  >  On the H.323 gateway, the q931 debugs showed the call come in, then a
>  >  delay with a recovery timer expired error. I reset the gateway on
>  > Call
>  >  Manager which had no effect.
>  >
>  >  Thanks, Erick
>  >  _______________________________________________
>  >  cisco-voip mailing list
>  >  cisco-voip at puck.nether.net
>  >  https://puck.nether.net/mailman/listinfo/cisco-voip
>  >
>  >
>
>