PRI issue using MGCP

[DallasBPF]

I am running CCM 4.1(3) at our main location, and a 3825 (running 12.4) at a branch location running MGCP protocol between them. The issue is with getting it where we are only using 12 channels on the PRI.

In the CCM I went to the B-Channel Maintance and added the card/router info followed by = 0000 0000 0000 1111 1111 1111.

Then I went into the router and changed the controller for that port to "timeslots 1-12, 24 service mgcp".

The MGCP took over after getting it registered with the CCM and changed it BACK to "1-24 service mgcp".... plus I noticed the IP address for the gateway is using the serial interface to AT&T (12.*.*.*) and not the IP address for the LAN side (192.168.*.100).

This site was recently upgraded to the 3825 router, and the VoIP is going in next friday. Basically trying to get things ironed out before making the 2hr flight and spending a day there.

Dallas, Texas
Telecommunications
CCNA, Net+
Working on MCSA, Convergence+, CCVP

 

[globalchicken]

Basically you need to delete the command ccm-manager config from your configuration. This command will automatically configure the PRI for a full 24 channels. After your configuration is complete take away the command and write it. Next time mgcp bounces the fractional PRI will still be on your config.

As for for your registration IP, your config needs the command mgcp bind control source-interface FastEthernet0/0
mgcp bind media source-interface FastEthernet0/0

only put the required interfaces in substitution.

Hope this helps.

 

[globalchicken]

mgcp bind control source-interface FastEthernet0/0
mgcp bind media source-interface FastEthernet0/0


These are the commands.

 

[DallasBPF]

mgcp bind control source-interface GigabitEthernet0/0.1
mgcp bind media source-interface GigabitEthernet0/0.1

The above is where I had it configured for, which is the currect subinterface.


as for the other part "ccm-manager config", I was under the impression that with that line in there and also the B-Channel Maintance set up properly it would auto config the controller to those specific channels. Or am I missunderstanding the purpose of the B-Channel Maintance?

Dallas, Texas
Telecommunications
CCNA, Net+
Working on MCSA, Convergence+, CCVP

 

[DallasBPF]

Below are pieces of the config;


controller T1 0/2/0
framing esf
linecode b8zs
pri-group timeslots 1-24 service mgcp

interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
media-type rj45
negotiation auto
!
interface GigabitEthernet0/0.1
description Data VLAN
encapsulation dot1Q 1 native
ip address 192.168.**.100 255.255.255.0
ip helper-address *********
ip helper-address *********
ip nbar protocol-discovery
no snmp trap link-status
!
interface GigabitEthernet0/0.2
description Voice VLAN
encapsulation dot1Q 400
ip address 172.16.**.254 255.255.255.0
ip helper-address *********
ip helper-address *********
ip nbar protocol-discovery
no snmp trap link-status

interface Serial0/2/0:23
no ip address
isdn switch-type primary-4ess
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable


ccm-manager fallback-mgcp
ccm-manager redundant-host 172.16.100.201
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 172.16.100.201
ccm-manager config
!
mgcp
mgcp call-agent "Sub IP Address" 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface GigabitEthernet0/0.1
mgcp bind media source-interface GigabitEthernet0/0.1
!
mgcp profile default

Dallas, Texas
Telecommunications
CCNA, Net+
Working on MCSA, Convergence+, CCVP