[cisco-voip] Bandwidth Sync Issues

Andrew F. Wolfe deadpool.slayer.telecomm at gmail.com
Tue Mar 13 14:56:31 EST 2007


Well I was hoping to avoid calling TAC (deep sigh) Oh well gotta do what ya
gotta do.  I just find it so odd that the other sites are not having this
issue.  That includes a large site in that has more users than this one I
have issues with.  Thanks all, if you have other suggestions let me know
otherwise I will post when I find an answer.

On 3/13/07, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
>  We've got about 300 phones there and will only be using the WAN for long
> distance and intra-site calling and conference resources.
>
> So even with all 300 phones talking, it would be 300 x 64kbps = ~ 20 Mbps
> . Still plenty left over.
>
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ...there's no such thing as a bad timbit...
>
> ----- Original Message -----
> *From:* Jason Aarons (US) <jason.aarons at us.didata.com>
> *To:* cisco-voip at puck.nether.net
> *Sent:* Tuesday, March 13, 2007 3:47 PM
> *Subject:* Re: [cisco-voip] Bandwidth Sync Issues
>
>  Would the number of phones at site using G.711/729 possibly exceed the
> LLQ reserved bandwidth (show policy-map interface) on the 100MBps interface?
>
>
>
> If not, I would consider using Unlimted for bandwidth location.
>
> If yes, I would consider setting the bandwidth and opening TAC cases as
> needed and re-sync as needed!
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Lelio Fulgenzi
> *Sent:* Tuesday, March 13, 2007 3:43 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Bandwidth Sync Issues
>
>
>
> So should I stay away from locations where possible? We have a remote site
> coming online with a large pipe (100Mbps) and I wanted to use locations. It
> sounds like there are definately some bugs.
>
>
>
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ....there's no such thing as a bad timbit...
>
>  ----- Original Message -----
>
> *From:* Patrick Diener <patrick.diener at gmail.com>
>
> *To:* cisco-voip at puck.nether.net
>
> *Sent:* Tuesday, March 13, 2007 3:39 PM
>
> *Subject:* Re: [cisco-voip] Bandwidth Sync Issues
>
>
>
> unfortunatly that sounds like a ccm bug to me...
>
> On 3/13/07, Andrew F. Wolfe <deadpool.slayer.telecomm at gmail.com> wrote:
> > Calls are properly released.  Essentially when the calls come in and are
> > released it looks like the bandwidth that was originally allocated is
> not
> > released.  Eventually the bandwidth usage climbs to a point that there
> are
> > no more resources
> >
> >
> > On 3/13/07, Patrick Diener <patrick.diener at gmail.com> wrote:
> > > you said "calls will drop and that bandwidth does not release", what
> > > does drop mean exactly? Are calls properly released or do they
> > > actually drop in the middle of conversations?
> > >
> > >
> > > On 3/13/07, Andrew F. Wolfe <
> > deadpool.slayer.telecomm at gmail.com> wrote:
> > > > That is pretty much the same issue, unfortunately resynch of the
> > bandwidth
> > > > is only temporary.  It lasts about 45 minutes then starts to climb
> up
> > again.
> > > >
> > > >
> > > >
> > > > On 3/13/07, Jason Aarons (US) <jason.aarons at us.didata.com> wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > I've given up on Locations in CCM 4.1 being error free. Seems to
> have
> > some
> > > > caveats requiring re-syncs here and there.
> > > > >
> > > > >
> > > > >
> > > > > I had a hub/spoke site with T1 1.54MBps and 3 7940s. Locations was
> set
> > to
> > > > 384k.  Codec was G729a.  After a couple months no issues, the third
> > phone
> > > > would call across the WAN and get "Not Enough Bandwidth", then I saw
> > this at
> > > > other customers randomly. Once we re-synch the issue went away.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: cisco-voip-bounces at puck.nether.net
> > > > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf
> > Of
> > > > Matt Slaga (US)
> > > > > Sent: Tuesday, March 13, 2007 2:57 PM
> > > > > To: Andrew F. Wolfe; cisco-voip at puck.nether.net
> > > > > Subject: Re: [cisco-voip] Bandwidth Sync Issues
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > What version of CCM are you running?  I've seen this before..
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > From: cisco-voip-bounces at puck.nether.net [mailto:
> > > > cisco-voip-bounces at puck.nether.net] On Behalf Of Andrew
> > F.
> > > > Wolfe
> > > > > Sent: Tuesday, March 13, 2007 1:49 PM
> > > > > To: cisco-voip at puck.nether.net
> > > > > Subject: [cisco-voip] Bandwidth Sync Issues
> > > > >
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > I have an H.323 gateway at an SRST site that is having bandwidth
> > > > synchronization issues.  When you watch a perfmon of the calls using
> the
> > > > Cisco Locations Performance Object, you see that the bandwidth seems
> > fine
> > > > but then calls will drop and that bandwidth does not release.  When
> you
> > > > manually resync the bandwidth everything is corrected but within
> about
> > 30
> > > > minutes the bandwidth climbs higher and higher until out of
> resources.
> > At
> > > > the other 53 locations we don't have this issue.  Any thoughts?
> What do
> > you
> > > > need to know from me?  Thanks in advance.
> > > > > ________________________________
> > > >
> > > > >
> > > > > Disclaimer: This e-mail communication and any attachments may
> contain
> > > > confidential and privileged information and is for use by the
> designated
> > > > addressee(s) named above only. If you are not the intended
> addressee,
> > you
> > > > are hereby notified that you have received this communication in
> error
> > and
> > > > that any use or reproduction of this email or its contents is
> strictly
> > > > prohibited and may be unlawful. If you have received this
> communication
> > in
> > > > error, please notify us immediately by replying to this message and
> > deleting
> > > > it from your computer. Thank you.
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Disclaimer: This e-mail communication and any attachments may
> contain
> > > > confidential and privileged information and is for use by the
> designated
> > > > addressee(s) named above only. If you are not the intended
> addressee,
> > you
> > > > are hereby notified that you have received this communication in
> error
> > and
> > > > that any use or reproduction of this email or its contents is
> strictly
> > > > prohibited and may be unlawful. If you have received this
> communication
> > in
> > > > error, please notify us immediately by replying to this message and
> > deleting
> > > > it from your computer. Thank you.
> > > > > _______________________________________________
> > > > > cisco-voip mailing list
> > > > > cisco-voip at puck.nether.net
> > > > > https://puck..nether.net/mailman/listinfo/cisco-voip<https://puck.nether.net/mailman/listinfo/cisco-voip>
> > > > >
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > cisco-voip mailing list
> > > > cisco-voip at puck.nether.net
> > > > https://puck..nether.net/mailman/listinfo/cisco-voip<https://puck.nether.net/mailman/listinfo/cisco-voip>
> > > >
> > > >
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck..nether.net/mailman/listinfo/cisco-voip<https://puck.nether.net/mailman/listinfo/cisco-voip>
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck..nether.net/mailman/listinfo/cisco-voip<https://puck.nether.net/mailman/listinfo/cisco-voip>
>
>  ------------------------------
>
> *Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleting
> it from your computer. Thank you. *
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> 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/20070313/31024c5c/attachment.html 


More information about the cisco-voip mailing list