SIP trunk configuration on both CUBE and CUCM not working

[niceinfotech]

I’m relatively new to Cisco technologies and have been working on configuring SIP trunking between a CUBE (Cisco Unified Border Element) and CUCM (Cisco Unified Communications Manager) and also between a CUBE (Cisco Unified Border Element) and the Service Provider . I followed the Cisco white papers and documentation to set up the configuration, but I’m facing an issue where:

1. Outbound calls from internal extensions are not going out.

2. Inbound calls from outside cannot reach our internal extensions.

 I have already gathered and uploaded the following:

• Topology diagram

• Configuration files (CUBE and CUCM)

• Logs (CUCM and CUBE)

• Screenshots of the CUCM configuration

Here’s a brief overview of my setup:

• CUBE Version: Cisco IOS XE Software, Version 17.03.04a
  Cisco IOS Software [Amsterdam], ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 17.3.4a, RELEASE SOFTWARE (fc3)

• CUCM Version: System version: 14.0.1.10000-20

• SIP Provider: BSNL

I’ve double-checked the configuration against the Cisco documentation, but I’m clearly missing something. Could someone please review my configuration and logs to help identify the issue?

[Marco Rojas Abarca]

Dear niceinfotech,

According to the debugs uploaded on the file, seems to me like the router is unable to match a dial-peer as outgoing for this call:

*Feb 3 12:00:40.884: //-1/52C7F6E580BA/CCAPI/cc_api_display_ie_subfields:
cc_api_call_setup_ind_common:
cisco-username=918837099070
----- ccCallInfo IE subfields -----
cisco-ani=918837099070
cisco-anitype=0
cisco-aniplan=0
cisco-anipi=0
cisco-anisi=0
dest=+913642310489

*Feb 3 12:00:40.890: //179/52C7F6E580BA/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 10.181.34.1:5060;branch=z9hG4bKcczpl12uk912km1411ccur5upT09274
From: <sip:918837099070@siptrunk.ims.bsnl.in;user=phone>;tag=sbc08038nh1nhyy
To: <sip:+913642310489@siptrunk.ims.bsnl.in;user=phone>;tag=AA3364-C0C
Date: Mon, 03 Feb 2025 12:00:40 GMT
Call-ID: asbcyuy89ubhb9z8y1gy8unzf9dzu2a82u2f@10.191.102.18
CSeq: 1 INVITE
Allow-Events: telephone-event
Warning: 399 172.21.6.185 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-17.3.4a
Reason: Q.850;cause=1
Session-ID: 3c8e7ba153ab57d7893cbfa7d121572f;remote=2aca406198cc5d12b039ee35263ae028
Content-Length: 0

Kindly find below a couple of very useful references which you can use to diagnose your issue further:

Understand Matching Inbound/Outbound Dial Peers on IOS Platforms
https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/14074-in-dial-peer-match.html

Determine Voice Translation Rules
https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/61083-voice-transla-rules.html

Hope this information helps,
Sincerely,
Marco R.

[Maren Mahoney]

As @Marco Rojas Abarca pointed out, the call is failing with No matching outgoing dial peer. The reason is that the SIP INVITE is coming in with a dialed number of +913642310489 where your router's dialplan does not have the + configured. This is also why the incoming dialpeer for the call is dial-peer 10 in lieu of a specific match. 

I would suggest reconfiguring your dial-peers to be specific about capturing calls inbound to the CUBE with 'incoming called-number' patterns. 

As for dealing with the +, you would either need to add (or reconfigure) dial-peers or add voice translations to remove the +.

Maren