06-09-2017 05:24 AM - edited 03-19-2019 12:31 PM
We have created the SIP Trunk in CUCM and configure below dial-peer in CME but unable to dial CME extension From CUCM while the vice versa is working can any one help??
dial-peer voice 500 voip
Outgoing CME to CUCM
destination-pattern ....
session protocol sipv2
session target ipv4:172.31.8.13
voice-class codec 1
dtmf-relay h245-signal h245-alphanumeric
dial-peer voice 5001 voip
Incoming From CUCM to CME
session protocol sipv2
session target sip-server
incoming called-number .
dtmf-relay sip-notify
Solved! Go to Solution.
06-09-2017 08:15 AM
As you can see the call is not routable
BlockThisPattern
Make sure your routing is configured properly in CUCM:
06-09-2017 06:29 AM
You don't need the session target in DP 5001 as its an inbound dial peer being matched on the incoming called number.
Are the calls hitting the CUBE?
Try the following debugs when you make a call.
debug ccsip packets
debug ccsip events
debug ccslip calls
06-09-2017 06:51 AM
Hi,
When we call from CUCM ext to CME ext its give error call cannot be considered as dial and no logs shown at CME side
06-09-2017 06:58 AM
Do you have proper route pattern in allowed partition pointing to proper RL/RG/Trunk?
What does Dialed Number analyzer show?
06-09-2017 08:11 AM
06-09-2017 08:15 AM
As you can see the call is not routable
BlockThisPattern
Make sure your routing is configured properly in CUCM:
06-11-2017 09:06 AM
Hi,
Thanks all for there valuable inputs its working now.
06-09-2017 06:38 AM
Please post "debug ccsip messages" for the failed call. Assign voice codec-class to dial peer 5001 and correct dumf-relay on dial peer 500 (this is not causing the issue). Posting full configuration would be helpful too, to ensure you allow sip-sip calls, and toll-fraud prevention is properly configured.
06-09-2017 06:55 AM
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