[cisco-voip] 1760 MGCP Gateway on CCM 4.1(2)

[IT]

I have had a very different issue with my gateway, but I saw some of the
same hot-words, and couldn't help but sharing....

I have an 1820 and I had and ISDN PRI, PTP T1, and a 9port switch all in
the chasis.  I constantly tried to put them in that order, with the ISDN
PRI in Slot 0.  The slot said VIC only, but since I assumed the PRI was
voice, not data, it would be fine.  I was wrong. According to Cisco, the
ISDN PRI card will not work in a VIC slot, but you will not realize it
until you try to setup the time-channels.  I'm not %100 sure on the
details, but I had Analog FXO's in there previous, and they worked fine.
My solution was to shuffle the cards so the 9port switch sat in Slot 0
and 1 (really only plugged into 1). And moving the T1 cards over to 2
and 3.
Obviously, my experience is different (1700vs1800, BRIvsPRI) but I'm
hoping the experience can help someone...
Thanks,
Avidan


> ----- Original Message ----- 
> From: Gary Roberton 
> To: cisco-voip at puck.nether.net 
> Sent: Monday, June 13, 2005 6:29 AM 
> Subject: [cisco-voip] 1760 MGCP Gateway on CCM 4.1(2) 
> 
> Hello all
> 
> We have been having trouble for several weeks now and would like to
> hear from anyone having similar trouble as I want to know how
> widespread our type of problem is.
> 
> We have a Call Manager which was running on 3.3(3) which we upgraded
> to 4.1(2).   The upgrade was smooth although we hit the problem where
> the agent that monitors changes in the call manager database was not
> working correctly so changes to route filters were being ignored. 
> This was fixed with an ES.
> 
> At the same time we also had a remote site to install which was using
> a 1760 and Euro ISDN2e.  We decided to use MGCP for this gateway but
> the call manager always tries to configure the ISDN BRI card in slot
> 0, no matter which slot it is in!  If we do put it in slot 0 the
> config is downloaded to the router but the ISDN will not come up at
> layer 2.  I will not bore you all with the details here but we have
> tried various levels of IOS and have had a TAC case open for several
> weeks.  Cisco have built this and confirmed it to be a problem - but I
> want to try to gauge if other people are seeing similar problems and
> if so how they are getting around them.
> 
> TIA
> 
> Gary
> 
> _______________________________________________
> 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

******************************************************
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.
******************************************************