network-clock-participate wic 0
network-clock-participate wic 1
isdn switch-type primary-net5
controller E1 0/0/0
pri-group timeslots 1-8,16 service mgcp
controller E1 0/1/0
pri-group timeslots 1-13,16 service mgcp
ccm-manager redundant-host x.x.x.x
ccm-manager config server x.x.x.x
ccm-manager config (wait for router to register, then remove this command)
mgcp call-agent x.x.x.x 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
mgcp bind media source-interface GigabitEthernet0/0
The above is your standard MGCP config. If you noticed that on your debug isdn q931 that your calls aren't hitting the right channels you can change the behaviour they select by selecting either top down or bottom up on the voice gateway configuration page on callmanager.
i have a question about this workaround.
I have a scenario with a Cat 6000 E1 Blade and need a separate QSIG Gateway with a fractional E1 with 10 B-Channels. I remember that i can disable some B-Channels in the CCM Service Parameters, but i think this will also affect the E1 Blades, right ?
If i do not disable this channels and work with the config you provided, how does the ccm know, that he cant use the 11th channel ?
Take a read of these threads:
If you have ccm-manager configured, I would remove that line as CCM has no way of knowing how many channels are active on the PRI. CCM will therefore assume there is a full PRI and change the config as a result.
The limitation within CCM is that you can only configure the channel maintenance status for 5 gateways. This cerntainly is the case in CCM5.x
Therefore I would not specifically reconfigure the pri-group unless it was absolutely necessary. If you are able to change the maintenance status, then I would recommend this.
However, as I have mentioned on previous posts, I would only configure the pri-group with the respective number of time-slots only in order to preserve DSPs for transcoding/conference resources on the same gateway.
Have a look at this url if you haven't already seen it. It describes how to busy out the channels on the call manager, sorry Unified Communication Manager