CUCM SIP Trunk Unable to find a device handler for the request received

[Mike Assel]

I have a lab running CUCM 10.0 that has a SIP trunk to a VCS.  Previously I was able to place and receive calls across the trunk, but now I can only place calls, not receive.  I did recently upgrade to 10.5, but I really can't recall if it ever worked after the upgrade.   The error I'm getting in CUCM is

Unable to route message, Cannot find the SIP Device with Name=192.1.1.61, Source Port=5060, IpAddress Type=0

This confuses me, because the destination IP/port of the VCS SIP trunk is 192.1.1.61:5060.  The trunk on CUCM show as up and the Zone in VCS shows as up.  What is going on?

Thanks,  Mike

[Mike Assel]

Sorry, meant to include the CUCM trace file.  Attached.

[George Thomas]

Weird stuff, looks like your options ping from VCS to CUCM is failing and hence the reason why you cant route calls to CUCM. Did you reset the SIP trunk, maybe restart CM?

[Mike Assel]

George, I will give the reboot a try after customer demos are done today :)  And I've reset the trunk several times.  Regarding the options ping failing, where are you seeing that?  Are you sure it's for the same SIP trunk I'm referring to (192.1.1.61)?  I have 2 other SIP trunks (one to CUCM 8.6 and the other to IM&P 10.5) that both have that issue, but the status of the trunk in question is Full Service.

[George Thomas]

Right here:

OPTIONS sip:10.1.200.31:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.1.1.61:5060;branch=z9hG4bK88e7b16bb065f01389a0a4a2943beeb1473237;rport
Call-ID: d27a442574642eb4@192.1.1.61
CSeq: 38266 OPTIONS
From: <sip:192.1.1.61>;tag=5a094120ac85a0dc
To: <sip:10.1.200.31:5060>
Max-Forwards: 0
User-Agent: TANDBERG/4129 (X8.1.1)
Supported: com.tandberg.vcs.resourceusage
Content-Length: 0

SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 192.1.1.61:5060;branch=z9hG4bK88e7b16bb065f01389a0a4a2943beeb1473237;rport
From: <sip:192.1.1.61>;tag=5a094120ac85a0dc
To: <sip:10.1.200.31:5060>;tag=758047327
Date: Wed, 24 Sep 2014 11:18:54 GMT
Call-ID: d27a442574642eb4@192.1.1.61
CSeq: 38266 OPTIONS
Warning: 399 pub "Unable to find a device handler for the request received on port 25166 from 192.1.1.61"
Content-Length: 0

[Mike Assel]

Like you said, weird stuff.  I wonder why the trunk shows as Full Service in CUCM?
 

[George Thomas]

It shows as full service in CUCM since the options ping go from CUCM to VCS, which is different from the options ping from VCS to CUCM. Looks like CUCM needs a kick. :)

[Mike Assel]

Reboot didn't help.  Same issue.

[George Thomas]

How many CUCMs do you have? Do you have Run on all active nodes checked on the route list/trunk? Does the SIP profile have the incoming transport set as TCP and not UDP?

[Mike Assel]

It's a lab, so only a single server.  Regardless, I do have run on all active nodes checked and the SIP security profile does have incoming transport as TCP and UDP.  Thanks, Mike

[George Thomas]

Ok, I am out of ideas other than deleting and recreating the SIP trunk in CUCM. Will see if someone else will help. :)

[Mike Assel]

Appreciate the help.  I will see about getting a TAC case opened.  I'll let you know what I find.

[Mike Assel]

I figured it out.  Long story short, it was a port mismatch.  When you configure Mobile Remote Access on the Expressway Core it creates a SIP trunk from Expressway to CUCM using port 5060.  If you then create another SIP trunk from the same Expressway to CUCM for firewall traversal or external calling, you must use a different port.  The port used for the zone in Expressway must match the SIP security profile used on the CUCM side SIP trunk.  So I had created another SIP Security profile in CUCM with port 5062 for this purpose.  However, the VCS in question that I was working with was only being used for FW traversal, so I used 5060 as the port on the VCS side, but I applied the SIP security profile that used 5062 on the CUCM side.  That's why CUCM was throwing that "device not found" error.  Once I changed the Security Profile to match the same port used on VCS (5060) all was well.  Sorry for the long winded answer.  Hope it helps someone else down the road.

[Safuvan]

Thanks for the clarification,

I have this problem too, When I changed the port number from "sip security profile"the issue were solved. 

Thanks, Safuvan