cant dial out using dial-peers when in SRST

[satish rawat]

I am experiencing a unique issue, i am running 2921 with c2900-universalk9-mz.SPA.151-4.M4.bin on CM 8.6, i have GW setup as MGCP controlling PRI and FXO trunkis on GW, when in MGCP everything works ie inbound outbound. I have dial-peers on GW for SRST when i failover phones to SRST i cant dial out of PRI. While troubleshooting i forced a particular phone in CM to fallback to SRST and then trying dialout PRI ( which at that time is still controlled by CM using bind-l3 CCM ). my understanding is SIP,H323,MGCP are separate codes on router and they can work independently so if i do a CSIM start string or force a CM phone to go to SRST i should still be able to use local dial-peers on GW...i am missing something on GW config. Debug ISDN q931 doesnt show any activity when i run CSIM or call out using SRST phone.

[chrysostomos1980]

Hi

Can we have your config for srst?

You have already creaded SRST Reference in the device pool right?

The phones are registered normally in srst mode but the calls are not working?Incoming outgoing?

[satish rawat]

Hi, Its pretty standard config

dial-peers pointing to D channel

dial-peer voice 11 pots

description ### 11 digit LD calls ###

destination-pattern 71[2-9]..[2-9]......

port 0/0/0:23

forward-digits 11

dial-peer voice 7 pots

description ### 7 DIGIT LOCAL CALLS ###

destination-pattern 7[2-9]......

port 0/0/0:23

forward-digits 7

dial-peer voice 7011 pots

description ### INTL calls ###

destination-pattern 7011T

port 0/0/0:23

forward-digits 18

dial-peer voice 911 pots

description ### 911 ###

destination-pattern 911

port 0/0/0:23

forward-digits 3

when phones are on CM ( GW is MGCP) inbound outbound works with no issues, in SRST mode is when i have problem, seems like none of the dial-peers works....all dial-peers shows up...sh dialplan string shows matching dial-peers. I made a test dial-peer with exact match of my cellphone but its still not working

[satish rawat]

additional info

when doing a csim start 937.....

debug voice dial-peer gives me below out put which means there is a dial-peer match

BC-PEN-VGW-01#csim start 19375465342
csim: called number = 19375465342, loop count = 1 ping count = 0

csim: loop = 1, failed = 1
csim: call attempted = 1, setup failed = 1, tone failed = 0

BC-PEN-VGW-01#
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=19375465342, Peer Info Type=DIALPEER_INFO_SPE
CH
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=19375465342
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
   Dial String=19375465342, Expanded String=19375465342, Calling Number=
   Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
   Result=Success(0); Outgoing Dial-peer=937 Is Matched
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
Oct 26 12:30:57.004: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=937

here is status of PRI when i make this call

lobal ISDN Switchtype = primary-ni

Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not ap

SDN Serial0/0/0:23 interface
       dsl 0, interface ISDN Switchtype = primary-ni
       L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER 0x0003
   Layer 1 Status:
       ACTIVE
   Layer 2 Status:
       TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
   Layer 3 Status:
       0 Active Layer 3 Call(s)
   Active dsl 0 CCBs = 0
   The Free Channel Mask:  0x807FFFFF
   Number of L2 Discards = 0, L2 Session ID = 8
   Total Allocated ISDN CCBs = 0

[chrysostomos1980]

Hi

Show ccm-manager pls

Also can we have the configuration for mgcp in gw?

[satish rawat]

Primary         Registered              10.10.1.2
First Backup    Backup Ready            10.10.1.3
Second Backup   None

Current active Call Manager:   10.10.1.2
Backhaul/Redundant link port:   2428
Failover Interval:              30 seconds
Keepalive Interval:             15 seconds
Last keepalive sent:            09:12:25 EDT Oct 26 2012 (elapsed time: 00:00:04
)
Last MGCP traffic time:         09:12:25 EDT Oct 26 2012 (elapsed time: 00:00:04
)
Last failover time:             18:50:58 EDT Oct 25 2012 from (172.16.118.21)
Last switchback time:           18:51:28 EDT Oct 25 2012 from (172.16.118.20)
Switchback mode:                Immediate
MGCP Fallback mode:             Enabled/OFF
Last MGCP Fallback start time:  None
Last MGCP Fallback end time:    None
MGCP Download Tones:            Disabled
TFTP retry count to shut Ports: 2

Backhaul Link info:
    Link Protocol:      TCP
    Remote Port Number: 2428
    Remote IP Address: 10.10.1.2
    Current Link State: OPEN
    Statistics:
        Packets recvd:   214
        Recv failures:   0
        Packets xmitted: 287
        Xmit failures:   0
    PRI Ports being backhauled:
        Slot 0, VIC 0, port 0
Configuration Auto-Download Information
=======================================
Current version-id: 1351193913-92e4944e-8208-45c1-9773-5b6086940d34
Last config-downloaded:00:00:00
Current state: Waiting for commands
Configuration Download statistics:
        Download Attempted             : 10
          Download Successful          : 10
          Download Failed              : 0
          TFTP Download Failed         : 0
        Configuration Attempted        : 6
          Configuration Successful     : 6
          Configuration Failed(Parsing): 0
          Configuration Failed(config) : 0
Last config download command: New Registration
FAX mode: disable
Configuration Error History:
no network-clock-participate wic 0

isdn bind-l3 ccm-manager
ccm-manager switchback immediate
ccm-manager fallback-mgcp
ccm-manager redundant-host10.10.1.3
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server10.10.1.3
ccm-manager config

pri-group timeslots 1-24 service mgcp
ccm-manager fallback-mgcp
ccm-manager mgcp
mgcp
mgcp call-agent10.10.1.2 2427 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
mgcp bind control source-interface GigabitEthernet0/0
mgcp bind media source-interface GigabitEthernet0/0
mgcp profile default
service mgcpapp
service mgcpapp
service mgcpapp
service mgcpapp
service mgcpapp
service mgcpapp
service mgcpapp
BC-PEN-VGW-01#

end

[Aaron Harrison]

Hi

javascript:;

If your gateway is registered to CUCM via MGCP then the PRI signalling is backhauled to CUCM - this means that the PRI is basically not under the control of the gateway, and therefore can't be used by dial-peers.

If you want to test SRST, you must cut off comms to CUCM for the gateway and phone so that they both go into SRST mode.

You can verify this by doing a 'show dial-peer voice summary' - you should see that the dial-peers show as 'down' while MGCP is connected to CUCM.

Aaron Harrison

Principal Engineer at Logicalis UK

Please rate helpful posts...

[satish rawat]

Aaron, thanks for response, i thought about it however i my dial-peers status shows up even though GW is backhauled and controlled by MGCP function in CM. I have in the past used GW for both MGCP and H323 at same time and it has worked like charm...one common example of this is mobile voice access

1      voip  up   up                                0  syst

11     pots  up   up             71[2-9]..[2-9]..-  0                      up

0/0/0:23

                                 ....

7      pots  up   up             7[2-9]......       0                      up

0/0/0:23

7011   pots  up   up             7011T              0                      up

0/0/0:23

911    pots  up   up             911                0                      up

0/0/0:23

7911   pots  up   up             7911               0                      up

0/0/0:23

16     pots  up   up             7911               0                      up

trunkgroup PRI-FAILOVER

15     pots  up   up             911                0                      up

trunkgroup PRI-FAILOVER 1      voip  up   up                                0  syst
11     pots  up   up             71[2-9]..[2-9]..-  0                      up
0/0/0:23
                                 ....
7      pots  up   up             7[2-9]......       0                      up
0/0/0:23
7011   pots  up   up             7011T              0                      up
0/0/0:23
911    pots  up   up             911                0                      up
0/0/0:23
7911   pots  up   up             7911               0                      up
0/0/0:23
16     pots  up   up             7911               0                      up
trunkgroup PRI-FAILOVER
15     pots  up   up             911                0                      up
trunkgroup PRI-FAILOVER

[Aaron Harrison]

Hmmm

Do you have 'no dial-peer outbound status-check pots' enabled?

Maybe post up your whole config...

Aaron

[satish rawat]

i dont see this command in my config,...what is this command do ?

[satish rawat]

attached is entire config

card type t1 0 0
logging buffered 51200 warnings
!
no aaa new-model
clock timezone EDT -5 0
clock summer-time EDT recurring
network-clock-participate wic 0
--More--                           network-clock-select 1 T1 0/0/0
!
no ipv6 cef
ip source-route
ip cef
!
!
!
!
!
ip domain name kjc,org
ip name-server 172.16.2.10
ip name-server 172.16.2.11
multilink bundle-name authenticated
!
!
!
!
isdn switch-type primary-ni
!
!

voice service voip
no ip address trusted authenticate
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
  call preserve
!
voice class h323 1
  h225 timeout tcp establish 30
!
--More--                           !
!
!
!
voice translation-profile INBOUND-DID
translate called 1
!
!
license udi pid CISCO2921/K9 sn FTX1634AH9D
hw-module pvdm 0/0
!
hw-module sm 1
!
!
!
username admin privilege 15 secret 4 nPYkYmzSqi6pny9E7H4akYODmmzT6IgDmesYgV.62uc
!
redundancy
!
--More--                           !
controller T1 0/0/0
cablelength long 0db
pri-group timeslots 1-24 service mgcp
!
!
!
!
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
ip address 172.16.118.15 255.255.254.0
ip pim dense-mode
duplex auto
speed auto
h323-gateway voip interface
h323-gateway voip bind srcaddr 172.16.118.15
!
interface GigabitEthernet0/1
no ip address
--More--                            shutdown
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
interface SM1/0
ip unnumbered GigabitEthernet0/0
ip pim dense-mode
service-module ip address 172.16.118.24 255.255.254.0
!Application: Cisco UMG running on SM
service-module ip default-gateway 172.16.118.1
--More--                           !
interface SM1/1
description Internal switch interface connected to Service Module
no ip address
!
interface Vlan1
no ip address
!
ip default-gateway 172.16.118.1
ip forward-protocol nd
!
ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
ip route 0.0.0.0 0.0.0.0 172.16.118.1
ip route 172.16.118.24 255.255.255.255 SM1/0
!
!
!
!
control-plane
!
--More--                           !
voice-port 0/0/0:23
translation-profile incoming INIBOUND-DID
local-alerting
!
voice-port 0/1/0
trunk-group PRI-FAILOVER
timing hookflash-out 50
connection plar 9900
description ### 856-792-2200 ###
!
voice-port 0/1/1
trunk-group PRI-FAILOVER
timing hookflash-out 50
connection plar 9900
description ### 856-792-2202 ###
!
voice-port 0/1/2
trunk-group PRI-FAILOVER
timing hookflash-out 50
connection plar 9900
description ### 856-792-4102 ###
!
voice-port 0/1/3
--More--                            trunk-group PRI-FAILOVER
timing hookflash-out 50
connection plar 9900
description ### 856-792-4103 ###
!
voice-port 0/2/0

!
voice-port 0/2/1

!
voice-port 0/2/2

!
voice-port 0/2/3
!
voice-port 0/3/0
!
voice-port 0/3/1
!
ccm-manager switchback immediate
ccm-manager fallback-mgcp
ccm-manager redundant-host 172.16.118.20
ccm-manager mgcp
--More--                           no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 172.16.118.20 
ccm-manager config
!
mgcp
mgcp call-agent 172.16.118.21 2427 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
mgcp bind control source-interface GigabitEthernet0/0
mgcp bind media source-interface GigabitEthernet0/0
!
mgcp profile default
!
!
dial-peer voice 999020 pots
service mgcpapp
--More--                            port 0/2/0
!
dial-peer voice 999021 pots
service mgcpapp
port 0/2/1
!
dial-peer voice 999022 pots
service mgcpapp
port 0/2/2
!
dial-peer voice 999010 pots
service mgcpapp
port 0/1/0
!
dial-peer voice 999011 pots
service mgcpapp
port 0/1/1
!
dial-peer voice 999013 pots
service mgcpapp
port 0/1/3
!
dial-peer voice 999012 pots
service mgcpapp
--More--                            port 0/1/2
!
dial-peer voice 1 voip
incoming called-number .
codec g711ulaw
no vad
!
dial-peer voice 11 pots
description ### 11 digit LD calls ###
destination-pattern 71[2-9]..[2-9]......
port 0/0/0:23
forward-digits 11
!
dial-peer voice 7 pots
description ### 7 DIGIT LOCAL CALLS ###
destination-pattern 7[2-9]......
port 0/0/0:23
forward-digits 7
!
dial-peer voice 7011 pots
description ### INTL calls ###
destination-pattern 7011T
port 0/0/0:23
forward-digits 18
--More--                           !
dial-peer voice 911 pots
description ### 911 ###
destination-pattern 911
port 0/0/0:23
forward-digits 3
!
dial-peer voice 7911 pots
description ### 911 failover ###
destination-pattern 7911
port 0/0/0:23
forward-digits 3
!
dial-peer voice 16 pots
trunkgroup PRI-FAILOVER
description ### 911 OUT OF FXOs ###
destination-pattern 7911
forward-digits 3
!
dial-peer voice 15 pots
trunkgroup PRI-FAILOVER
description ### 911 OUT OF FXOs ###
destination-pattern 911
forward-digits 3
--More--                           !
dial-peer voice 937 pots
destination-pattern 4869955
progress_ind setup enable 3
progress_ind progress enable 8
progress_ind connect enable 8
port 0/1/0
forward-digits all
!
!
!
!

[acampbell]

Hi,

From your config I can not see the key element to turn on

the default H323 protocol when mgcp fails

Try adding

!

application

global

service alternate Default

!

A good link for serst implementation

https://supportforums.cisco.com/docs/DOC-24097#3_MGCP_GatewayFallback_Configuration_on_the_Cisco_IOS_Gateway

Regards,
Alex.
Please rate useful posts.

[Roger Kallberg]

That wouldn't be needed for the PRI to fall back to H.323. Only thing needed for that is "ccm-manager fallback-mgcp".

The below application part is needed for the FXO ports to fall over to H.323 control.

application
global
service alternate Default

But as been said before, the L3 is back hauled to CUCM, so the GW would not be in control of the PRI. As long as you have this "isdn bind-l3 ccm-manager" line under the D channel config you won't be able to test SRST. You need to force the GW and the phone(s) to loose connectivity to CUCM. That will remove the line from the D channel and turn over control to the default protocol, namely H.323.

My preferred method for this is to temporarily add host routes that point to null for the addresses to the CUCMs on the egress GW. In that way you "only" affect the communication for the phone system from that remote site.

Please remember to rate all useful posts.

Sent from Cisco Technical Support iPhone App

[cyberbillp]

I added routes for my primary and secondary subscribers to null to trigger srst.

It then replicated via eigrp and bgp though out the corporation and wiped out about 30 sites for thousands of phones/users, throwing them all into srst mode.

I'm lucky I didn't get fired.

So this is a bad idea.

[Ayodeji Okanlawon]

This is definitely not a bad idea. I do this all the time at the remote gateway for the branch I am testing. You create an Ip route that points to null interface for the CUCM servers in the cucm group for that site and only that site will fall into SRST. I must have done over 100s of this and works well all the time..

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"