cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2878
Views
5
Helpful
5
Replies

9971 inbound call fails - CUCM: Unable to find a device handler

aku
Level 1
Level 1

Hello everyone,

We have a standalone CUCM 7.1.5 with 2911 CUBE (Version 15.0(1)M2) installed together with 15 SIP phone model 9971.

Outbound calls from 9971 SIP phone works fine.

Inbound calls from PSTN to SIP phone fails at CUCM side.

In this case we get a rejection message from CUCM:

Sep 17 07:12:55.908: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 503 Service Unavailable

Warning: 399 CUCM-7-1-5 "Unable to find a device handler for the request received on port 5060 from 192.168.253.251"

Date: Tue, 17 Sep 2013 07:12:57 GMT

From: "MY-GSM-NUMBER" <sip:MY-GSM-NUMBER@voip.provider-name.com>;tag=3DD480-1B7E

Allow-Events: presence

Content-Length: 0

To: <sip:100@192.168.253.253>;tag=403939668

Call-ID: 68D983F9-1E9F11E3-8049D627-7FFDB3D4@192.168.253.251

Via: SIP/2.0/UDP 192.168.253.251:5060;branch=z9hG4bK42238

CSeq: 101 INVITE

Outside called number (pstn-number) is translated on cube to DN 100, which is applied and used on 9971 phone and is registered to CUCM.

SIP trunks on CUBE and CUCM should be properly setup (no issues with outbound calls?).

I'm attaching the full debugs from CUBE and a CUCM trace for inbound call for more detailed information.

Did anyone had any similar issues?

i'll be very gratefull for any usefull advise for resolving this problem

Regards!

5 Replies 5

Chris Deren
Hall of Fame
Hall of Fame

Ensure the CSS applied to the sip trunk has access to the partition of the phone DN.

Chris

Sent from Cisco Technical Support iPhone App

Chris,

Thank you for your reply.

Inbound CSS on trunk configuration was checked many times, was even changed to new CSS with phone partition only, wrong CSS isn't the issue here.

Does CUCM trace give any suspicion on something else (besides CSS issue) ?

Thank you for any feedback!

Ales

Hi Ales.

The CUCM is rejecting your sip requests becoming, probably, from a wrong ip address

Check your trunk configuration on CUCM and verify that you configured the right ip address of your cube.

In your CUBE configuration also add under voice service voip:

sip

bind control source-interface gx/x (the ip address of this interface, should be the one you configured on sip trunk on CUCM)

bind media source-interface gx/x

HTH

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"

vemanyam
Level 1
Level 1

First make sure about binding the traffic properly on cube.
Out going calls to outbound interface and incoming to inbound interface.

In dial-peer for incoming, set preference to zero.

Make sure you select the right settings on sip trunk.

If all settings are perfect, Reset sip trunk and try, if not working, try rebooting cucm.

Thank you all.

We need to upgrade CUBE to 15.1(4M6) first, then we test with proper bind commands on dial-peer.

I will report back to let you know, and rate all your useful answers.

Thanks again, regards!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: