06-06-2015 10:56 AM - edited 03-17-2019 03:15 AM
Hello,
I am able to successfully dial out to the PSTN in SRST mode but unable to receive calls. The phones are registered using SIP. The following is the output after I entered the show run command.
Building configuration...
Current configuration : 4447 bytes
!
! Last configuration change at 22:32:27 UTC Sat Mar 21 2015 by admin
! NVRAM config last updated at 22:32:28 UTC Sat Mar 21 2015 by admin
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname LabRouter
!
boot-start-marker
boot-end-marker
!
! card type command needed for slot/vwic-slot 0/3
logging message-counter syslog
!
no aaa new-model
clock timezone UTC -4
!
dot11 syslog
--More-- ip source-route
!
!
ip cef
!
!
no ip domain lookup
ip name-server 172.16.2.140
ip name-server 172.16.0.1
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
voice service voip
allow-connections sip to h323
allow-connections sip to sip
fax protocol cisco
sip
registrar server expires max 600 min 60
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
voice register global
max-dn 5
max-pool 5
!
voice register pool 5
id network 172.16.2.0 mask 255.255.255.128
dtmf-relay rtp-nte cisco-rtp sip-notify
codec g711ulaw
no vad
!
!
!
voice-card 0
!
--More-- !
application
global
service alternate Default
!
!
!
!
!
!
username admin password 0 cisco
archive
log config
hidekeys
!
!
!
!
!
!
!
!
!
interface GigabitEthernet0/0
ip address 172.16.0.2 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/1.10
encapsulation dot1Q 10
ip address 172.16.1.1 255.255.255.0
ip helper-address 172.16.2.140
!
interface GigabitEthernet0/1.20
encapsulation dot1Q 20
ip address 172.16.2.1 255.255.255.128
ip helper-address 172.16.2.140
!
interface GigabitEthernet0/1.30
encapsulation dot1Q 30
ip address 172.16.2.129 255.255.255.128
!
interface GigabitEthernet0/1.40
encapsulation dot1Q 40
ip address 172.16.3.1 255.255.255.248
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 172.16.0.1
no ip http server
--More-- no ip http secure-server
!
!
!
!
!
!
!
!
!
control-plane
!
!
!
voice-port 0/0/0
timing hookflash-out 50
timing guard-out 1000
connection plar 1001
!
voice-port 0/0/1
timing hookflash-out 50
timing guard-out 1000
connection plar 1001
!
voice-port 0/1/0
!
voice-port 0/1/1
!
voice-port 0/1/2
!
voice-port 0/1/3
!
voice-port 0/2/0
!
voice-port 0/2/1
!
voice-port 0/2/2
!
voice-port 0/2/3
!
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 172.16.2.10
ccm-manager config
!
mgcp
mgcp call-agent 172.16.2.10 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
--More-- no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
!
mgcp profile default
!
!
!
dial-peer voice 999000 pots
service mgcpapp
port 0/0/0
!
dial-peer voice 999001 pots
service mgcpapp
port 0/0/1
!
dial-peer voice 1 pots
description PSTN-emergency dial 9 first fxo 0
destination-pattern 999.
port 0/0/0
forward-digits 3
!
dial-peer voice 2 pots
description PSTN-emergency dial 9 first fxo 1
destination-pattern 999.
port 0/0/1
!
dial-peer voice 3 pots
description PSTN-emergency fxo 0
destination-pattern 99.
port 0/0/0
forward-digits all
!
dial-peer voice 4 pots
description PSTN-emergency fxo 1
destination-pattern 99.
port 0/0/1
forward-digits all
!
dial-peer voice 5 pots
description Local PSTN
destination-pattern 9[2-9]......
port 0/0/0
forward-digits 7
!
dial-peer voice 6 pots
description Local PSTN FXO 1
destination-pattern 9[2-9]......
port 0/0/1
forward-digits 7
!
dial-peer voice 7 pots
description NANP FXO 0
destination-pattern 91[2-9].........
--More-- port 0/0/0
forward-digits 11
!
dial-peer voice 8 pots
description NANP FXO 1
destination-pattern 91[2-9].........
port 0/0/1
forward-digits 11
!
dial-peer voice 868 pots
service mgcpapp
incoming called-number .
direct-inward-dial
port 0/0/0
!
dial-peer voice 869 pots
service mgcpapp
incoming called-number .
direct-inward-dial
port 0/0/1
!
!
sip-ua
registrar ipv4:172.16.2.1 expires 600
!
!
!
call-manager-fallback
max-conferences 8 gain -6
transfer-system full-consult
ip source-address 172.16.2.1 port 2000
max-ephones 6
max-dn 12
keepalive 20
!
!
line con 0
exec-timeout 0 0
password cisco
logging synchronous
login
line aux 0
line vty 0 4
password cisco
login local
transport input telnet ssh
!
scheduler allocate 20000 1000
ntp master
end
Thanks in advance,
Martin.
06-06-2015 06:31 PM
Debug your GW, do you see the calls hitting your GW???
06-07-2015 09:08 AM
Hi Jaime,
Thanks for the reply. I don't know if I ran the correct debug command (debug voice dialpeer detail). The following is the logs on the router during an incoming call.
Mar 22 07:42:07.891: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=, Voice-Interface=0x492D4A04,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Mar 22 07:42:07.891: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Match Rule=DP_MATCH_PORT;
Mar 22 07:42:07.891: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_PORT; Incoming Dial-peer=999000
Mar 22 07:42:07.891: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerSPI:exit@6170
Thanks again for your assistance.
06-07-2015 11:17 AM
Run ccapi inout, but that debug does not show calling or called numbers, that would be a telco issue
06-08-2015 12:27 PM
I ran the ccapi inout debug command and noticed that the dial-peer mgcp created (999000 and 999001) are being match as the incoming dial-peer.
Result=Success(0) after DP_MATCH_PORT; Incoming Dial-peer=999000
June 7 15:14:12.037: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
Try with the demoted called number 0
June 7 15:14:12.037: //2254/EDF9F1C19458/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 2254 with tag 999000 to app "MGCPAPP"
When I shutdown this dial-peer I am able to receive calls with the following output from the debug command.
Result=Success(0); Incoming Dial-peer=40006 Is Matched
Result=Success(0); Outgoing Dial-peer=40006 Is Matched
40005 voip up up 1001 0 syst ipv4:172.16.2.46:506
40006 voip up up 0 0 syst ipv4:172.16.2.46:506
40003 voip up up 1000 0 syst ipv4:172.16.2.48:506
40004 voip up up 1002 0 syst ipv4:172.16.2.45:506
40001 voip up up 0 0 syst ipv4:172.16.2.48:506
40002 voip up up 0 0 syst ipv4:172.16.2.45:506
However, if I leave this port shutdown and callmanager comes online this port is now seen as unregistered.
Is there a way for another dial-peer to be match as the incoming dial-peer so that the incoming calls will be successful?
06-10-2015 09:24 PM
Hi Martin,
Should the incoming dial peers be voip and not pots??
dial-peer voice 868 pots
service mgcpapp
incoming called-number .
direct-inward-dial
port 0/0/0
!
dial-peer voice 869 pots
service mgcpapp
incoming called-number .
direct-inward-dial
port 0/0/1
Thanks.
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