[cisco-voip] Re: MGCP Registration

kevin knowlen kevin.knowlen at gmail.com
Wed Oct 20 20:44:30 EDT 2004


All,

I created a new CM group and device pool and only put the publisher in
them to test the registration problem with only one CM.  Now when I do
a sho CCM-Manager, it continues to say Registering with CM and never
actually registers.  Current active call managers = none


On Thu, 21 Oct 2004 02:49:07 +0300, kevin knowlen
<kevin.knowlen at gmail.com> wrote:
> All,
> 
> I'm trying to set up a new T1 CAS MGCP gateway.  I'm running CCM3.3(3)
> and 3640 IOS 12.3(10) with NM-HDV VWIC-2MFT-T1.
> 
> Im having problems setting up the T1 endpoint identifyiers in gateway
> configuration screen.  When I click on the T1 to configure it it come
> up with a screen that makes me select T1 CAS or T1 PRI.  I select T1
> CAS, which the type I want to set up.  The next screen does not show
> up with the T1 being registered.  It has an insert button only.  I
> make the necessary selections and press insert and it returns a
> scripting error.  It says that a Null value is not acceptable.  I
> assume that it is refering to the fact that the ports aren't
> configured yet.  The add port hyperlink didn't show up, so ports can't
> be added.
> 
> When I do a sho ccm-manager it returns
> 
> Priority                   Status                      Host
> -------------------------------------------------------------------
> Primary                 Backup Ready           192.168.1.2
> First Backup          Registering With CM  192.168.1.3
> 
> Current active Call Manager:            None
> 
> the downloads are successful and configuration is successful.  It
> keeps flip flopping between the the primary and backup for which one
> is "Backup Ready" or "Registering With CM."
> 
> I can ping the the publisher CM(tftp server) fine, its on the same
> subnet.  From the publisher I can ping the hostname of the gateway
> just fine (I added a lmhost file to do this).  debug mgcp packets show
> the info being sent to the CCM and back to the routers hostname with a
> @ in front of the name.
> 
> I have configured the gateway with the following.
> 
> hostname D3GW3640
> !
> voice-card 1
>  dsp services dspfarm
> !
> !
> ccm-manager fallback-mgcp
> ccm-manager redundant-host 192.168.1.3
> ccm-manager mgcp
> ccm-manager config server 192.168.1.2
> ccm-manager config
> !
> controller T1 2/0
> framing esf
> linecode b8zs
> cable length short 133
> ds0-group 0 timeslots 1-24 type none service mgcp
> !
> controller T1 2/1
> framing esf
> linecode b8zs
> cable length short 133
> ds0-group 0 timeslots 1-24 type none service mgcp
> !
> voice-port 2/0:0
> !
> voice-port 2/1:0
> !
> !
> mgcp
> mgcp call-agent 192.168.1.2 2427 service-type mgcp version 0.1
> mgcp dtmf-relay voip codec all mode cisco
> mgcp unreachable timeout 1000 action notify
> mgcp package-capability rtp-package
> mgcp package-capability sst-package
> no mgcp package-capability fxr-package
> mgcp sdp simple
> mgcp fax t38 inhibit
> mgcp rtp payload-type g726r16 static
> mgcp bind control source-interface fa0/0
> mgcp bind media source-interface fa0/0
> !
> mgcp profile default
> !
> dial-peer voice 1 pots
>  application mgcpapp
>  port 2/0:0
> !
> dial-peer voice 2 pots
>  application mgcpapp
>  port 2/0:0
> !
> --
> 1LT Knowlen, Kevin
> Proud Soldier
> 


-- 
1LT Knowlen, Kevin


More information about the cisco-voip mailing list