02-20-2015 04:26 PM - edited 03-17-2019 02:04 AM
This is my lab environment:
VOIP.MS --> 2811 CUBE--> CUCM 10.5.2
Attached is my configuration on both my cube and publisher
What is going on is if I make a call from my IP Communicator phone it does not call out. Also if I do a debug ccsip all, I get no output from the calls I make going out. I have not even attempted the incoming since I believe that my cucm server and gateway are not even communicating with each other. Please let me know if I am doing something wrong.
Thanks
02-20-2015 08:27 PM
Hi,
Have you added a Route pattern on CUCM with the SIP Trunk pointing to the CUBE in its Route List? Please make sure that the partition assigned on the Route pattern is added to the CSS of the calling phone.
HTH
Manish
02-21-2015 12:58 PM
Yes I have I have Route Group with the SIP Trunk as a member
A RouteList containing the Route GROUP registered with the Subscriber
I have a Route Pattern 9.1[2-9]XXXXXXXXX with the current Route List
02-22-2015 12:38 AM
If the above config is in place and the call is not hitting the CUBE then you should upload the callmanager sdl trace file for a test call to check what is going wrong.
HTH
Manish
02-22-2015 11:18 AM
02-22-2015 03:10 PM
Calling Number=18042221111, Called Number=18042221111, Peer Info Type=DIALPEER_INFO_SPEECH *Feb 22 19:11:08.287: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=18042221111 *Feb 22 19:11:08.287: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
dial-peer voice 1002 voip description 303893xxxx Calls to HNBUCM preference 2 shutdown destination-pattern ^303893....$ session target ipv4:172.16.89.16 incoming called-number . voice-class codec 1 voice-class h323 1 dtmf-relay h245-alphanumeric no vad
dial-peer voice 1001 voip description 720/484-37xx Calls to HNBUCM preference 2 shutdown destination-pattern ^72048437..$ session target ipv4:172.16.89.16 incoming called-number . voice-class codec 1 voice-class h323 1 dtmf-relay rtp-nte digit-drop no dtmf-interworking no vad
Looks like the dial-peer is not matching (first output), at the same time, seems like your dial-peer voip are shutdown.
Not sure if this is the reason indeed, the calls are not going out.
Could you please let us know, the Calling and Called Numbers as well, will make it much easier.
Secondly, could you please post the DNA output as well
Regards
02-22-2015 04:36 PM
I am calling (804) 222-1111 from 9142281462, how do I get the dna output?
02-22-2015 05:32 PM
It is http://x.x.x.x/dna
Where x.x.x.x = Pub IP Address, and then select Phone based analysis, after that it is very intuitive.
Secondly, on the second glimpse, I notice that you are using hostname instead of the IP Address for the SIP ITSP in PSTN bound Dial Peers,
dial-peer voice 9001 voip description 1+10 Digit Calls to ITSP preference 1 destination-pattern ^1[2-9]..[2-9]......$ session protocol sipv2 session target sip-server session transport udp voice-class codec 1 voice-class sip early-offer forced dtmf-relay rtp-nte sip-kpml sip-notify no va
Are you sure the CUBE is able to resolve this to the correct IP Address?
HTH
02-24-2015 06:02 AM
Results Summary
I also adjusted my dial-peer to be:
dial-peer voice 10 voip
destination-pattern 1[2-9].........
session protocol sipv2
session target dns:newyork4.voip.ms
voice-class codec 1
dtmf-relay sip-notify rtp-nte
I also verified I can ping newyork4.voip.ms
02-24-2015 06:08 AM
Did I miss it or is the incoming dial-peer coming in from CUCM to CUBE missing? I see a bunch of hybrid incoming/outgoing. (not recommended in my opinion).
What do the latest ccsip mess or voip dialpeer debugs say after you changed the DP?
02-25-2015 11:47 AM
Brandon
I split my peers and now I am able to make outgoing calls. I am having an issue with incoming calls. Below is my debug for the incoming call, as you can see it matches the dialpeer but I get the feeling there is something I am missing:
VOICEROUTER#
*Feb 25 04:38:29.135: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=9142281462, Called Number=9142281462, Peer Info Type=DIALPEER_INFO_SPEECH
*Feb 25 04:38:29.135: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=9142281462
*Feb 25 04:38:29.135: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Feb 25 04:38:29.135: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=9142281462, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Feb 25 04:38:29.135: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=1
2: Dial-peer Tag=2
02-21-2015 10:53 AM
What version of IOS are you running on the CUBE?
If 15.2(1)T or later the toll fraud feature could be blocking your calls.
http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/112083-tollfraud-ios.html
02-21-2015 12:53 PM
This is my version
flash:c2800nm-adventerprisek9-mz.151-4.M8.bin
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