[cisco-voip] VG248 constantly rebooting

[Lelio Fulgenzi]

I'm just cleaning up my inbox (down to 994 messages from 1500 yippee!) and wanted to post back to the list the resolution to this problem. We had the port misconfigured to accept more than one call at a time. After we configured it to receive just one at a time, we were fine. 
  ----- Original Message ----- 
  From: Wes Sisk 
  To: Lelio Fulgenzi 
  Cc: Cisco Voip 
  Sent: Wednesday, July 12, 2006 10:20 AM
  Subject: Re: [cisco-voip] VG248 constantly rebooting


  That is the first thing to try.  If restarts persist after that, then we'll need to get you onto an engineering special image of 1.2.


  /Wes


  On Jul 12, 2006, at 11:10 AM, Lelio Fulgenzi wrote:


  Thanks - I'll bet that's what's happening. The bug mentions the workaround is specifically for voicemail integrations, do you think we could apply the workaround?

  --------------------------------------------------------------------------------
  Lelio Fulgenzi, B.A.
  Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
  (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
  "I can eat fifty eggs." "Nobody can eat fifty eggs."
    ----- Original Message -----
    From: Wes Sisk
    To: Lelio Fulgenzi
    Cc: Cisco Voip
    Sent: Wednesday, July 12, 2006 9:48 AM
    Subject: Re: [cisco-voip] VG248 constantly rebooting


    Voicemail really has nothing to do with it.


    It's more the race condition that occurs between the digital and analog signaling legs.


    consider this case:


    call is connected between ipphone user and vg248 analog phone user
    ipphone user hangs up.  CM tells vg248 to go onhook.  CM immediately expects that port to be idle.  However, on the analog side the vg248 has to drop loop current or do polarity reversal for up to 200msec to indicate disconnect supervision.  In this 200msec window CM sees the vg248 port as idle and can attempt to send another call.  When this happens several times the vg248 seems to roll over.


    It's been mostly noted in voicemail deployments as those tend to use linear hunting (first available starting from first port).  If you have any such hunt groups that receive high call volume you could be encountering this issue.


    /Wes




    On Jul 11, 2006, at 7:43 PM, Lelio Fulgenzi wrote:


    Thanks Wes. Our VG248 is not connected to a voicemail system, do you think that we might still be affected?

    --------------------------------------------------------------------------------
    Lelio Fulgenzi, B.A.
    Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
    (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
    "I can eat fifty eggs." "Nobody can eat fifty eggs."
      ----- Original Message -----
      From: Wes Sisk
      To: Lelio Fulgenzi
      Cc: cisco-voip at puck.nether.net
      Sent: Tuesday, July 11, 2006 7:31 PM
      Subject: Re: [cisco-voip] VG248 constantly rebooting


      what sort of call volume are you running through that one?  there is an issue with resource utilization in all 1.3(1) code where a busy system will reboot CSCsa68044.  mostly observed when calls are delivered in rapid succession to the same port on the vg248.


      otherwise, vg248 only generates a 'cold boot' snmp trap.  syslog contains all the same things as the event viewer.


      /Wes


      On Jul 11, 2006, at 10:19 AM, Lelio Fulgenzi wrote:


      We are having a problem where one of our VG248s is sometimes constantly, sometimes occassionaly rebooting. We have replaced it twice and have swapped the UPS but troubles still persist.

      The logs don't show much and we're not sure what the problem might be. We're guessing it's one of the devices attached to the switch and we have a few leads, but I'm wondering if anyone out there has run into a problem where a device was causing the unit to reload. We have another VG248 with the same code and types of devices plugged into the same UPS so we're pretty sure it's an end device.

      Also, is there any extra information contained in the SNMP traps and SYSLOG?

      What was curious, and what we are investigating are three ports that register off-hook but the status says call ended on the next screen.

      --------------------------------------------------------------------------------
      Lelio Fulgenzi, B.A.
      Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
      (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
      "I can eat fifty eggs." "Nobody can eat fifty eggs."
      _______________________________________________
      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/20070101/9633c0b3/attachment-0001.html