12-14-2010 02:52 PM - edited 03-16-2019 02:25 AM
I have a 2821 router connected trough VPN with a CallManager 4.2.
It has a T1 CAS configured that now, works ok in SRST mode but I have problems with it and MGCP:
In MGCP mode, when we place inbound calls it always matches the srst dial-peers and phones doesn't ring.
For Outbound calls we can only place one call if we try with a second one we heard the busy signal. After that if we dial a number, the ip phones return to main screen and nothing happens. We have to shut and no shut the controller t1 to be able to place another call, only one.
I'm not also sure if I have to specify a isdn switch type with a T1 CAS, and If I have to, I don't know exacly wich one.
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname GW-S
!
boot-start-marker
boot system flash:c2800nm-adventerprisek9-mz.124-4.XC5.bin
boot-end-marker
!
card type t1 0 1
enable secret 5 $1$G4vy$iZ3bbI7Ru.c571aFhts641
!
no aaa new-model
!
resource policy
!
clock timezone gmt -6
network-clock-participate wic 1
network-clock-select 1 T1 0/1/0
no ip source-route
!
!
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.7.1 192.168.1.2
!
ip dhcp pool Pool
network 192.168.0.0 255.255.255.0
option 150 ip 192.168.0.1 192.168.0.2
default-router 192.168.1.1
dns-server 192.168.0.1 192.168.0.2
domain-name ccmdom.local
!
!
ip tftp source-interface GigabitEthernet0/0
no ip domain lookup
ip domain name ccmdom.local
ip host CM1 192.168.0.1
ip host CM2 192.168.0.2
ip ssh version 1
!
!
voice-card 0
no dspfarm
!
!
!
voice service voip
allow-connections h323 to h323
h323
!
!
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
codec preference 4 g729br8
!
!
!
voice class h323 1
h225 timeout tcp establish 3
h225 timeout setup 3
call preserve
!
!
!
!
!
voice translation-rule 1
rule 1 /.*/ /2100/
!
voice translation-rule 2
rule 1 /^0/ //
!
voice translation-rule 20
rule 1 reject /981999999/
!
!
!
voice translation-profile Bloqueo_in
translate calling 20
!
voice translation-profile translate-in
translate called 1
!
voice translation-profile translate-out
translate called 2
!
!
!
application
global
service alternate default
!
!
!
controller T1 0/1/0
framing sf
linecode ami
ds0-group 1 timeslots 1-24 type e&m-wink-start
description PRIMARIO
!
!
!
interface GigabitEthernet0/0
description INTERFAZ GATEWAY_1
ip address 192.168.1.1 255.255.255.0
duplex auto
speed auto
ccm-manager switchback immediate
ccm-manager fallback-mgcp
ccm-manager redundant-host CM2
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 192.168.0.1
ccm-manager config
!
mgcp
mgcp call-agent CM1 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 profile default
!
!
!
dial-peer voice 999010991 pots
service mgcpapp
port 0/1/0:1
!
dial-peer voice 999001 pots
service mgcpapp
port 0/0/1
!
!
!
call-manager-fallback
max-conferences 8 gain -6
transfer-system full-blind
ip source-address 192.168.1.1 port 2000
max-ephones 30
max-dn 20 dual-line
keepalive 120
time-format 24
date-format dd-mm-yy
12-14-2010 05:34 PM
Hello Sergio,
I hope you are doing great,
Would you try this:
From this dial peer remove this line ( incoming called-number . ):
!
dial-peer voice 8000 pots
description INCOMING T1 CAS Mode SRST
incoming called-number .
port 0/1/0:1
This will be because the logic of the dial peers will match first the incomming called number when it is hunting between them.
Regards,
Luis Sandi
12-14-2010 06:52 PM
You're using a relatively old IOS version on this gateway. I'd start by suggesting you get something more current.
Second, based on the config, it doesn't look like it is registering up with CCM and configuring correctly. I'd suggest you reboot the gateway, and once it is back up, do a SHOW CCM to make sure it's really registered up.
You should have the gateway configured for MGCP on CCM, and you should have your T1 configured there also. You do not need to define an ISDN switch type on a CAS circuit. Once you have configured the T1 on CallManager, and hit reset, it should push the config onto the gateway. If it doesn't, you can do a NO MGCP followed by an MGCP on the gateway to force a reset.
Please try this and then repost the gateway config.
12-15-2010 03:19 PM
Luis, I've removed that line and now, over MGCP mode an incoming call matches the correct dial-peer with service Mgcpapp.
For Outgoing calls i have the same problem over MGCP, I can place only one call and it matches the SRST dial-peer 8000 (see below) . After that if I try to place an outgoing call I dial the number on the ip phone but nothing happens, it returns to its main screen directly. That's my greatest problem, outgoing calls over MGCP.
GW-S(config-controller)#do sh voice call stat
CallID CID ccVdb Port DSP/Ch Called # Codec Dial-peers
0xB 11E5 0x4871A3D0 0/1/0:1.1 0/1:1 8xxxxxx7 g711ulaw 8000/0
Over SRST it works ok if I modify the dial-peers 8000 and 8001 to look like this:
dial-peer voice 8001 pots
description INBOUND SRST
translation-profile incoming translate-in
service default
port 0/1/0:1
dial-peer voice 8000 pots
description OUTBOUND SRST
translation-profile outgoing translate-out
service default
destination-pattern 0T
port 0/1/0:1
But when the connection is restablished and MGCP is back all in and out calls still match those SRST dial-peers, even if i reset the t1 controller, the MGCP service, etc. so I have to modify the SRST to make it work.
After a lot of test my situation is this:
I don't have problems over SRST with the apropiate dial-peers.
Over MGCP, once I place an incoming call to the T1 CAS I can't place any outgoing call but can receive incoming perfecly over the dial-peer Inbound SRST. In order to be able to place outgoing calls again over MGCP, I have to shu/no shut the controller t1 on the router (tried also resetting the t1 port gateway on CCM, shutting the voice port...), it's the only way, reset controller t1 or the entire router... But, the first incoming call the T1 receives, inhabilitates the outgoings...
Clifford: T1, gateway, phones, etc is registered OK when MGCP is up. I've already tried to reboot the gateway, reset the mgcp service, but nothing changes. I think that the problem might be on the CCM route patterns or some T1 CAS configuration in the CCM. Thank you for your instructions!
I surely have a bad configuration on the CCM (T1 CAS, router patters...), gateway (Controller) or both, but I don't know ...
Don't know what else can I try... any sugestions?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide