[cisco-voip] busting SBC
Erick Bergquist
erickbe at yahoo.com
Fri Jun 3 17:26:34 EDT 2005
What version of CCM and what IOS on router/gw?
Can you post snippet of config with mgcp and
ccm-manager commands from router/gw config, and
dial-peers?
The admin down in logs sent previously indicated it
was MGCP if no human was doing shutdown commands. MGCP
shutsdown interfaces while it is applying
configuration it downloaded from CCM. That may happen
when router loses connectivity to CCM for some reason
or another, also there have been some MGCP bugs/issues
that could be effecting you perhaps.
--- IT <it at cimgroup.com> wrote:
> Thanks for all the advice everyone.
>
> It appears that the issue was the gateway was no
> longer being registered
> with the CM. Doing the following fixed it:
> Conf t
> No mgcp
> Mgcp
>
> Does anyone have any ideas how the gateway could
> have unregistered
> itself? This thing is on a point-to-point T1 to the
> CM.
> Any ideas?
>
> Thanks,
> Avidan
>
> -----Original Message-----
> From: Erick Bergquist [mailto:erickbe at yahoo.com]
> Sent: Thursday, June 02, 2005 10:46 PM
> To: IT; Wes Sisk
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] busting SBC
>
> You can do a 'show controller t1 0/2/0' and see what
> types of errors are on it, alarms, etc.
>
>
> Is the router configured for MGCP or H323?
>
> --- IT <it at cimgroup.com> wrote:
>
> > The problem is that I am not at the site. No
> option
> > of making a T1
> > loopback plug. I cant plug anything into the
> router.
> > Any other ways to check if I have a bad module?
> >
> > -----Original Message-----
> > From: Wes Sisk [mailto:wsisk at cisco.com]
> > Sent: Thursday, June 02, 2005 7:55 PM
> > To: IT
> > Cc: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] busting SBC
> >
> > make yourself a t1 loopback plug and plug in, make
> > sure your interface
> > comes up/up.
> >
> > Then re-connect the t1 from SBC. give it a min
> and
> > do 'show cont t1'
> > it will likely be in red alarm. Search that
> > Cisco.com.
> >
> > Tell them you looped it up and your interface came
> > up.
> >
> > If your interface does not come up with the
> loopback
> > plug you may have a
> >
> > bad module, time for RMA.
> >
> > /Wes
> >
> > IT wrote:
> >
> > >Hey All,
> > >
> > >So I have a 2801 gateway device that has been
> > driving me nuts. Ive got
> > a
> > >point-to-point T1 to HQ for data and CM traffic,
> > and a T1 PRI from SBC
> > >for outbound calling. Earlier today, calls got
> cut
> > off, and I saw this
> > >in my log:
> > >Log Buffer (4096 bytes):
> > >ial0/2/0:22, changed state to down
> > >Jun 2 18:24:11: %LINK-5-CHANGED: Interface
> > Serial0/2/0:23, changed
> > >state to adm
> > >inistratively down
> > >Jun 2 18:24:16: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:23, changed
> > state
> > >to up
> > >Jun 2 18:24:16: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:0, changed state
> > >to down
> > >Jun 2 18:24:16: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:1, changed state
> > >to down
> > >.................yada yada yada
> > >Jun 2 18:24:16: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:22, changed
> > state
> > >to down
> > >Jun 2 18:56:20: %LINK-5-CHANGED: Interface
> > Serial0/2/0:23, changed
> > >state to adm
> > >inistratively down
> > >Jun 2 18:56:23: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:23, changed
> > state
> > >to up
> > >Jun 2 18:56:23: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:0, changed state
> > >to down
> > >Jun 2 18:56:23: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:1, changed state
> > >to down
> > >...............yada yada yada................
> > >Jun 2 18:56:23: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:21, changed
> > state
> > >to down
> > >Jun 2 18:56:23: %LINK-3-UPDOWN: Interface
> > Serial0/2/0:22, changed
> > state
> > >to down
> > >
> > >
> > >Now, an hour later, every time I call any of the
> > inbound lines, I get a
> > >busy signal, and when I try to dial out, I get
> > busy. What IOS commands
> > >can I issue on the 2801 to show that this is an
> SBC
> > problem, not an
> > >issue with my config. I am sick of getting
> blamed
> > for these issues.
> > >HELP!
> > >
> > >-Avidan
> > >
> >
>
>******************************************************
> > >This email may contain trade secrets and/or other
> > information that is
> > >proprietary and/or confidential. Use of this by
> > anyone other than the
> > >intended recipient(s) is prohibited and may be
> > unlawful. If you are not
> >
> > >the intended recipient, delete the e-mail and
> > notify us immediately.
> >
>
>******************************************************
> >
> > >
> > >
> > >_______________________________________________
> > >cisco-voip mailing list
> > >cisco-voip at puck.nether.net
> >
> >https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> > >
> >
> >
>
******************************************************
> > This email may contain trade secrets and/or other
> > information that is
> > proprietary and/or confidential. Use of this by
> > anyone other than the
> > intended recipient(s) is prohibited and may be
> > unlawful. If you are not
> > the intended recipient, delete the e-mail and
> notify
> > us immediately.
> >
>
******************************************************
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
>
>
> __________________________________
> Discover Yahoo!
> Get on-the-go sports scores, stock quotes, news and
> more. Check it out!
> http://discover.yahoo.com/mobile.html
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
__________________________________
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html
More information about the cisco-voip
mailing list