MGCP gateway on 3640 -> Unknown MGCP Gateway ... NoEntryInDatabase

lterebizh · ‎08-19-2001

Hi.

Does anybody have this problem...?

I have

CM 3.1.1

3640 with NM-2V + Vic-2FXO + VIC-2fxs + IOS - c3640-jk8o3s-mz.122-2.XA.bin

Here config:

mgcp

mgcp call-agent 192.168.111.10 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp sdp simple

call rsvp-sync

ccm-manager mgcp

voice-port 1/0/0

!

voice-port 1/0/1

!

voice-port 1/1/0

!

voice-port 1/1/1

!

dial-peer cor custom

!

dial-peer voice 1 pots

application mgcpapp

port 1/0/0

!

dial-peer voice 2 pots

application mgcpapp

port 1/0/1

!

dial-peer voice 3 pots

application mgcpapp

port 1/1/0

!

dial-peer voice 4 pots

application mgcpapp

port 1/1/1

I checked this configuration and found that:

I have tcp connection between CM and 3640.

I can see endpoints named from CM (aal...)

I found that CM should know about GW even if we do not configure GW in CM (but 3640 should be configured). You can see it in Serviceability in CallMgr Info....

"show ccm" says that CM is registered....

But:

Serviceability says that status of this gw is "rejected" by the reason that

Unknown MGCP Gateway ... NoEntryInDatabase

I have no idea what is it...I think it is some problem with software on 3640.....

Is it true that 12.2.2-XA ans 3640 should work as MGCP gw...?

Thanks in advance.

Lev

lter@rmconsulting.com

dgoodwin · ‎08-20-2001

The gateway can still register to the call agent even if the gateway is not registered in the CCM database. But placing or receiving calls or doing pretty much anything will not function until the gateway is configured in CallManager.

lterebizh · ‎08-20-2001

Ok.

I have configured gw on CM and it is not still registered in CM.

I wrote it before... that :

Serviceability says that status of this gw is "rejected" by the reason that

Unknown MGCP Gateway ... NoEntryInDatabase

This is thing I cannot understand....

I tried this with 2621 with 2V+fxs+fxo

And get the same result....

So.... I configured gw and put it to the route group ..Then route group put to route list and create route pattern.

I gave some DN to fxs ports. Then I tried to call and it is not work.... So ..problem is still the same....

Why CM reject gw registration?

I checked SQL tables and see that there is gw-s records there and ports and so on....

I can see TCP keepalive connection (port 2428) between gw and cm. So it work partially...

dgoodwin · ‎08-20-2001

On the gateway, type show ccm

Whatever it says for MGCP Domain Name at the top, copy that to the clipboard. Then go to the gateway configuration in CCMAdmin for the gateway. There is a field there called MGCP Domain Name. Paste into the field, click Update, then reset the gateway.

It should probably work now.

lterebizh · ‎08-20-2001

Is sound weird..... but it works....

Thanks a lot...

But I am sure that CM can resolve names... so I believe it is not right behavior...

Again thanks

dgoodwin · ‎08-21-2001

Actually, it may look misleading, but the MGCP Domain Name configured in CallManager has nothing at all to do with DNS resolution.

The MGCP Domain Name on the gateway is actually used during the MGCP registration process. So that is the name that CallManager must have in the database in order to match up the registration attempt with a device in the system. That is the reason they must be the same.