Unable to call the device registered to cucm

[sallysa124]

1.My roomkit device has been registered with cucm, and the device can be called out through cucm->Esspressway

2.The external network fails to call the device, cucm replies 404 not found

analyze: 1.Both vcs-e and vcs-c have forwarded the call. vcs-c sends the call to cucm, and cucm replies 404.

cucm configuration：

The device has been successfully registered, and the 300 number is also there, why can't I find it? Is there any other configuration required?

[Nithin Eluvathingal]

Your post is a bit unclear. What do you mean by “can be called out”? And what do you mean by “external network fail to call this device”?

Are you trying to say that the device registered over MRA can make outgoing calls, but no one can call this device, specifically users outside the network over MRA? Can this extension be called from an extension that is local to the office, not one over MRA?

[sallysa124]

my means: The device is registered to cucm on the intranet. It can call a public network conference through expressway-E. However, the public network conference fails to invite the device to join the conference directly through expressway-E. When the invitation is sent to cucm, it will show that the device cannot be found.

[Roger Kallberg]

Does the CSS on the trunk for your Expressway include the partition(s) needed to route the call to the directory number of the device?

[Nithin Eluvathingal]

Check if the trunk between CUCM and Expressway has the CSS to reach this extensions highlighted by @Roger Kallberg .

[sallysa124]

What does CSS mean? How should it be configured?

This is the message cucm replied to vCS-C:

tvcs: UTCTime="2024-10-17 05:18:44,832" Module="network.sip" Level="DEBUG": Action="Received" Local-ip="192.168.128.125" Local-port="27891" Src-ip="192.168.128.21" Src-port="5060" Msg-Hash="3904099666084189779"
SIPMSG:
|SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 192.168.128.125:5060;egress-zone=ToCUCM01;branch=z9hG4bKad6491972090366a2fcbb03275294c0b31935.f236cfc4081821568cffa53851620a8b;proxy-call-id=7f251a2c-7a03-4fa1-ad70-6819a20c6630;rport,SIP/2.0/TLS 192.168.128.127:7001;egress-zone=traversalzone;branch=z9hG4bK7c7b5ca300e87e9a8bf0fe7e997a682c5858;proxy-call-id=a85de401-032d-473a-a284-ac240fd6041c;received=192.168.128.127;rport=7001;ingress-zone=traversalzone,SIP/2.0/TLS 192.168.128.127:5073;branch=z9hG4bK96ce93e49fbcabc4070e93294380834b54;x-cisco-local-service=nettle;received=192.168.128.127;rport=31959;ingress-zone=DefaultZone,SIP/2.0/TLS 10.100.138.242:5061;egress-zone=DefaultZone;branch=z9hG4bK5fc96df09f54ebbca32cc2ca7cd2748f5857.4dfff14f41e6ae786c1916ddfbc03ef4;proxy-call-id=11eeda83-9817-425c-acea-9e06f35f851a;received=10.100.138.242;rport=25028,SIP/2.0/TLS 10.100.120.20:3901;branch=z9hG4bK-d8754z-b824cd7495c7d1280-1---d8754z-;received=10.100.120.20;rport=40706;ingress-zone=DefaultZone
Call-ID: NTEzODM2ODNhNThlYjdlMGYxYWIyYjI0OTliMTI3YzE.f579bdd0@10.100.120.20
CSeq: 1 INVITE
From: "91559656862" <sip:XX@10.100.120.20>;tag=19bdfd03f579bdd0
To: <sip:300@10.100.138.242>;tag=22029~f7cedb61-dc3c-4cf8-aa79-7487363d6020-20507702
Server: Cisco-CUCM11.5
Date: Thu, 17 Oct 2024 05:18:44 GMT
Allow-Events: presence
Reason: Q.850 ;cause=1
Session-ID: 00000000000000000000000000000000;remote=6681c2f700255000a0000bf4f6fa0000
Content-Length: 0

[Nithin Eluvathingal]

Since CUCM is sending a 404 not found error, please check if the trunk on the CUCM has an inbound CSS assigned that can reach the partition these extensions belong to.

Can you send the full messages? Also, if possible, collect the trace from CUCM.

[sallysa124 · Accepted solution]

Thank you very much, my problem has been solved. The reason is that the Calling Search Space in the Inbound Calls section of my sip trunk is not selected.

[Roger Kallberg]

Glad you managed to resolve this. But why did you select your own response as the solution to your question?