10-24-2007 03:18 PM - edited 03-15-2019 07:00 AM
I am having a problem with incoming calls on one of my remote gateways. Calls from area code that begin with 9 are not being completed - outside users are getting fast busy when they dial from these area code (ex 908, 970, 973)
I ran a debug voice dialpeer on the gateway and noticed that when users from these area code dial in, the call is matching dial-peer 1, however, when users call from other area code the call matches dial-peer 999011 which is correct. For the time being I have shut down dial-peer 1,2,3,4 to force calls to use the MGCP dial-peers. However, for SRST purpose i would need to use these dial-peers for outbound calls. Any suggestions?
Working Call
VG1#
Oct 24 18:55:12 EDT: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=7326611000, Called Number=, Voice-Interface=0x452F6E1C,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Oct 24 18:55:12 EDT: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_PORT; Incoming Dial-peer=999011
VG1#
Not Working Call
VG1#
Oct 24 18:55:47 EDT: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=9706860700, Called Number=, Voice-Interface=0x452F6E1C,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Oct 24 18:55:47 EDT: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=1
Oct 24 18:55:47 EDT: //-1/1827DFC9895D/DPM/dpMatchPeersCore:
Calling Number=, Called Number=0106, Peer Info Type=DIALPEER_INFO_SPEECH
Oct 24 18:55:47 EDT: //-1/1827DFC9895D/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=0106
Oct 24 18:55:47 EDT: //-1/1827DFC9895D/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
Oct 24 18:55:47 EDT: //-1/1827DFC9895D/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)
!
voice-port 0/1/0
echo-cancel coverage 48
timing hookflash-out 500
connection plar 0105
caller-id enable
!
voice-port 0/1/1
echo-cancel coverage 48
timing hookflash-out 500
connection plar 0106
caller-id enable
!
voice-port 0/1/2
echo-cancel coverage 48
timing hookflash-out 500
connection plar 0107
caller-id enable
!
voice-port 0/1/3
echo-cancel coverage 48
timing hookflash-out 500
connection plar 0108
caller-id enable
!
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
port 0/1/2
!
dial-peer voice 1 pots
description SRST Backup Outbound Dial-peer
preference 5
shutdown
destination-pattern 9T
port 0/1/0
forward-digits all
!
dial-peer voice 2 pots
description SRST Backup Outbound Dial-peer
preference 5
shutdown
destination-pattern 9T
port 0/1/1
forward-digits all
!
dial-peer voice 3 pots
description SRST Backup Outbound Dial-peer
preference 5
shutdown
destination-pattern 9T
port 0/1/2
forward-digits all
!
dial-peer voice 4 pots
description SRST Backup Outbound Dial-peer
preference 5
shutdown
destination-pattern 9T
port 0/1/3
forward-digits all
!
10-24-2007 03:37 PM
Just put service mgcpapp under the rest of the dial-peers, and make sure you have MGCP fallback setup properly and then when the MGCPAPP service isn't available all those dialpeers will fall back to H323 mode including the dial peers starting with 999. You could put destination-pattern commands on those peers also.
The reason why the 1 is being used, the calls wil hit the first dial peer with the port on it which is configured for H323 mode and not MGCP.
10-24-2007 05:00 PM
Excellent, thank you that worked. I will have to test to ensure that SRST dialing is not affected with these changes at a later date.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: