[cisco-voip] MGCP FAllback to H323

Erick Bergquist erickbe at yahoo.com
Wed Nov 1 01:04:29 EST 2006


How are your voice-ports configured, and dial-peers? 

I've seen unsupported config w/MGCP on voice-ports and dial-peers cause commands to go away, and I have heard the opposite from TAC about ccm config. But if you have a config not supported by MGCP then you may need to remove the ccm config command to avoid the problems of CCM-MANAGER/MGCP trying to put a good MGCP (supported?) config on. 


----- Original Message ----
From: Joe Pollere (US) <Joe.Pollere at us.didata.com>
To: Ruben Montes (EU) <Ruben.Montes at eu.didata.com>; cisco-voip at puck.nether.net
Sent: Tuesday, October 31, 2006 6:09:06 PM
Subject: Re: [cisco-voip] MGCP FAllback to H323







 

 




<!--
 _filtered {font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */

 p.MsoNormal, li.MsoNormal, div.MsoNormal

	{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink

	{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed

	{color:purple;
text-decoration:underline;}
span.EmailStyle17

	{
font-family:Arial;
color:windowtext;}
span.EmailStyle18

	{
font-family:Arial;
color:navy;}
 _filtered {
margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.Section1

	{}
-->












Ruben,
 



  
 



Had

similar issues in the past; If you are using the ccm config server and ccm

config commands Tac says that there is a long history of problems with them. Once

the ports are initially configured via CM (and ccm config server); the ccm

config server and ccm config command should be removed.
 



  
 



Joe
 



  
 




















From:

cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ruben Montes (EU)


Sent: Tuesday, October 31, 2006

2:46 PM


To: cisco-voip at puck.nether.net


Subject: [cisco-voip] MGCP

FAllback to H323
 








  
 



Hi,
 



  
 



I’m having several problems using this functionality

in routers running MGCP with BRI ports. When the callmanager goes offline, all

works fine, but when the callmanager is up again, the router cannot register

with the Callmanager. I’ve also noticed that there are a lot of commands

that have ‘disappeared’ form the config, causing the router to

behave in this way.
 



  
 



Does anybody have this config working properly? I

have the same situation in two customers, I don’t know if it is an IOS

problem or what: there is no bug related with that for the release I’m

using (Version 12.4(4)T4)
 



  
 



Thanks in advance, 
 



  
 







Ruben
 








  
 














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






-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061031/2e972a00/attachment.html 


More information about the cisco-voip mailing list