<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1498" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>what sort of agent is this? do you use this as a transactional log of sorts
to see who made what changes?</DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=gary.ciscomail@gmail.com href="mailto:gary.ciscomail@gmail.com">Gary
Roberton</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, June 13, 2005 6:29 AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] 1760 MGCP Gateway
on CCM 4.1(2)</DIV>
<DIV><BR></DIV>Hello all<BR><BR>We have been having trouble for several weeks
now and would like to<BR>hear from anyone having similar trouble as I want to
know how<BR>widespread our type of problem is.<BR><BR>We have a Call Manager
which was running on 3.3(3) which we upgraded<BR>to 4.1(2). The
upgrade was smooth although we hit the problem where<BR>the agent that
monitors changes in the call manager database was not<BR>working correctly so
changes to route filters were being ignored. <BR>This was fixed with an
ES.<BR><BR>At the same time we also had a remote site to install which was
using<BR>a 1760 and Euro ISDN2e. We decided to use MGCP for this gateway
but<BR>the call manager always tries to configure the ISDN BRI card in
slot<BR>0, no matter which slot it is in! If we do put it in slot 0
the<BR>config is downloaded to the router but the ISDN will not come up
at<BR>layer 2. I will not bore you all with the details here but we
have<BR>tried various levels of IOS and have had a TAC case open for
several<BR>weeks. Cisco have built this and confirmed it to be a problem
- but I<BR>want to try to gauge if other people are seeing similar problems
and<BR>if so how they are getting around
them.<BR><BR>TIA<BR><BR>Gary<BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>