<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: outbound call over SIP Trunk not working but inbound calls working in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366161#M51376</link>
    <description>&lt;P&gt;The SIP transport being UDP or TCP shouldn't matter as long as the far end will accept it. Is there a firewall between the CUCM clusters? I have seen a SIP ALG on a firewall cause problems with TCP packets being delayed by the firewall to the point that call setup fails or is incomplete.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on your latest response it sounds like the call actually does ring through and connect but you just aren't getting any audio or video? Do you have all nodes from both clusters defined in the SIP trunk? In other words, if CUCM A has three nodes running the Call Manager service you need to have all three of those nodes defined as destinations in the SIP trunk to CUCM A.&lt;/P&gt;&lt;P&gt;Do you have a valid network path between the two endpoints? Media is endpoint to endpoint, not CUCM to CUCM (unless you have the device configured to require an MTP, but that's another discussion) so you could have a call set up correctly but if phone A can't reach phone B you aren't going to get any media.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To pull SDL traces you can follow this&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200787-How-to-Collect-Traces-for-CUCM-9-x-10-x.html" target="_self"&gt;guide&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jan 2026 20:24:01 GMT</pubDate>
    <dc:creator>sjdamme</dc:creator>
    <dc:date>2026-01-29T20:24:01Z</dc:date>
    <item>
      <title>outbound call over SIP Trunk not working but inbound calls working</title>
      <link>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5365899#M51367</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I have two sites: Site A and Site B. This is in a lab environment. both are connected via a fiber link.&lt;/P&gt;&lt;P&gt;Both site use cucm version 12.5&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a sip trunk between the two CUCMS. Trunk status on CUCM B shows Full service while the trunk status on CUCM A shows no service. Both were using sip ports 5060. I changed the ports to 5065 on both cucm and the trunk status on both now show Full service.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem:&lt;/P&gt;&lt;P&gt;The endpoint on CUCM B (6571) can dial the endpoint 3005 on CUCM A.&lt;/P&gt;&lt;P&gt;The endpoint on CUCM A (3005) can't dial the endpoint 6571 on CUCM B.]&lt;/P&gt;&lt;P&gt;The sip trace using Wireshark shows call rejected. see screenshot. I don't know what is wrong&amp;nbsp;&lt;/P&gt;&lt;P&gt;any help will be greatly appreciated&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 21:03:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5365899#M51367</guid>
      <dc:creator>collinks2</dc:creator>
      <dc:date>2026-01-28T21:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: outbound call over SIP Trunk not working but inbound calls working</title>
      <link>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366151#M51374</link>
      <description>&lt;P&gt;It's difficult to diagnose this with just the information provided. We see the 65XX route pattern assigned to the trunk from CUCM A to CUCM B, but we don't know what the internal_css calling search space assigned to the SIP trunk on the CUCM B side provides access to. Is the partition that contains extension 6571 included in the internal_css calling search space on CUCM B? There should also be some information in the SIP packet where the call is rejected, but it's probably just Q.850 cause=21 (call rejected). You could pull SDL traces on CUCM B from the time of a failed call attempt and that should show you why CUCM is rejecting the call.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 19:39:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366151#M51374</guid>
      <dc:creator>sjdamme</dc:creator>
      <dc:date>2026-01-29T19:39:59Z</dc:date>
    </item>
    <item>
      <title>Re: outbound call over SIP Trunk not working but inbound calls working</title>
      <link>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366155#M51375</link>
      <description>&lt;P&gt;Thank you so much for your contribution.On CUCM B, the internal css contains all the partitions. 6571 belongs to the internal_css and Internal_PT. On the CUCM B , the trunk that points to CUCM A&amp;nbsp; has internal_css for Incoming calls..With sound 'pio pio', I was tempted to believe it's a css and partition problem. I removed&amp;nbsp; all the css and partition but still no success.&lt;/P&gt;&lt;P&gt;Sons hours ago, I changed the outgoing transport to UDP&amp;nbsp; on the Non Secure profile . After I restarted&amp;nbsp; the server, 3005 was able to dial 6571. No audio and video. (Just the self video ). I dialed 3005 from 6571 :no audi and video.&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is definitely something wrong somewhere. CUCM B belongs to domain xyz while CUCMA belongs to abc. Could this&amp;nbsp; contribute to the issue?.I am thinking CUCM A is the one rejecting the call because it thinks the endpoint 65xx is local .why did the call go through after changing to UDP? I changed back to TCP and the call failed&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do I pull out SDL traces on CUCM B&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 20:04:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366155#M51375</guid>
      <dc:creator>collinks2</dc:creator>
      <dc:date>2026-01-29T20:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: outbound call over SIP Trunk not working but inbound calls working</title>
      <link>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366161#M51376</link>
      <description>&lt;P&gt;The SIP transport being UDP or TCP shouldn't matter as long as the far end will accept it. Is there a firewall between the CUCM clusters? I have seen a SIP ALG on a firewall cause problems with TCP packets being delayed by the firewall to the point that call setup fails or is incomplete.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on your latest response it sounds like the call actually does ring through and connect but you just aren't getting any audio or video? Do you have all nodes from both clusters defined in the SIP trunk? In other words, if CUCM A has three nodes running the Call Manager service you need to have all three of those nodes defined as destinations in the SIP trunk to CUCM A.&lt;/P&gt;&lt;P&gt;Do you have a valid network path between the two endpoints? Media is endpoint to endpoint, not CUCM to CUCM (unless you have the device configured to require an MTP, but that's another discussion) so you could have a call set up correctly but if phone A can't reach phone B you aren't going to get any media.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To pull SDL traces you can follow this&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200787-How-to-Collect-Traces-for-CUCM-9-x-10-x.html" target="_self"&gt;guide&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 20:24:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366161#M51376</guid>
      <dc:creator>sjdamme</dc:creator>
      <dc:date>2026-01-29T20:24:01Z</dc:date>
    </item>
    <item>
      <title>Re: outbound call over SIP Trunk not working but inbound calls working</title>
      <link>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366674#M51381</link>
      <description>&lt;P&gt;Thank you so much for your contributions. Apologies for my late response. I was trying to install the RTMT so I can get the trace. I am still finding it difficult to install RTMT on my windows 11. i have installed on more than 3 PCs&amp;nbsp; but no success. I have installed java but no success.&amp;nbsp; What baffles me is that I have&amp;nbsp; two CUCM users . The end points in the two clusters can communicate very well&amp;nbsp; over a sip trunk. Both belong to the same domain. . I don't know if it's because this cluster is in a different domain . Both&amp;nbsp; clusters can resolve all their domains . There is no subscriber. Just one CUCM Publisher&amp;nbsp; per cluster&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Feb 2026 16:08:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/outbound-call-over-sip-trunk-not-working-but-inbound-calls/m-p/5366674#M51381</guid>
      <dc:creator>collinks2</dc:creator>
      <dc:date>2026-02-01T16:08:22Z</dc:date>
    </item>
  </channel>
</rss>

