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

[Gary Roberton]

The 'agent' that I referred to is in fact a service that monitors the
call manager database.  When changes are made to the database, this
service notifies the call managers to check SQL for the changes that
have been made.  The problems we had meant that although we were
making changes to route filters and call forwards, these changes were
effectively being ignored as the call managers were not being notified
of the changes we had made.  You can find out more info under bug ID
CSCeg15756 and CSCsa64684

Hope this is useful

Gary
On 6/13/05, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>  
> what sort of agent is this? do you use this as a transactional log of sorts
> to see who made what changes? 
>   
>  
> ----- 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
>