Configure MGCP on Gateway Cisco VOIP Phone Command

Configure VG200 gateway to be controlled by CallManager via MGCP. Start by removing all dial
peers. You cannot have other manually configured dial peers with MGCP.
hostname VG200-A This case-sensitive name must agree with the Domain Name used
for the CallManager setup in the next section “Adding a Gateway in CallManager”.
ip host MCS7835 192.168.20.6 If DNS isn’t running, the CallManager name must be
manually resolved. In this case, the CallManager name is MCS7835.

mgcp Enable MGCP protocol
mgcp call-agent 192.168.20.6 Identify the CallManager
ccm-manager config server 192.168.20.6 TFTP server address
ccm-manager config Enable download of config files
mgcp dtmf-relay voip codec all mode out-of-band Codec type and DTMF function
ccm-manager mgcp Enable support for CCM within MGCP

ip routing Enable IP routing. Cisco documentation says this step is needed for
VG200’s but they seem to work fine from an initialized state without it.
ip route 0.0.0.0 0.0.0.0 192.168.20.1 Without a default route, the CallManager
may get phones to ring but the gateways won’t be able to talk to each other if
they are on different subnets.
Beware that these commands may vary depending on the IOS version and feature set being used.
NOTE: Skip ccm-manager config above if it is unavailable in the IOS.

FXS ports
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 4 pots
application MGCPAPP
port 1/1/1

Both ports 1/0/0 and 1/0/1 are affected by no shut
voice-port 1/0/0
no shut

Both ports 1/1/0 and 1/1/1 are affected by no shut
voice-port 1/1/0
no shut

copy run start
Read More:http://iiusatech.com/VOIPCommandRef.pdf

Related post



Newer Post Older Post

0 comments:

Post a Comment

 

Wiki Voip And Fax Tutorials Copyright © 2010 Labloub