Solved: Thanks for the updade and

Ruzanna Zohrabyan · ‎11-09-2015

Hi there all.

I have a problem related to my CallManager Express (version 10.0) SIP trunk. On my site already configured SIP trunk between CME and CUE. I have configured DN for SIP phone, and SIP phones have registered on CME successfully, but ... As soon as SIP phone registered on CME, DIAL-PEER for CME and CUE connection changes. Especially "session target ipv4" automaticaly changes to my SIP phone IP address, and all calls go to my SIP phone and doesn't reach to AutoAttendant.

How can I solve this problem???

Vivek Batra · ‎11-19-2015

Hi,

Follwoing is the error from CUCM;

Warning: 399 UnicompCM "Unable to find a device handler for the request received on port 55549 from 192.168.10.2"

This probably means that CME uses 192.168.10.2 to source the SIP packets to CUCM however SIP trunk in CUCM is not pointed to this IP, it may be pointed to some other interface IP address of CME and hence rejecting this call.

Can you please check what is the IP address of CME you've configured on SIP trunk in CUCM?

- Vivek

View solution in original post

Vivek Batra · ‎11-09-2015

Was it working before or it's a new installation?

Please share running-config and output of debug ccsip messages and debug voice ccapi inout.

- Vivek

Ruzanna Zohrabyan · ‎11-10-2015

Sorry, but now is business time, and I can't make changes and redirect all icoming calls to sip phone :)

Attached file is config file.

Vivek Batra · ‎11-10-2015

Seems 192.168.100.1 belongs to int gigabitethernet 0/0.100 but I can't see this interface set/status in the running config, can you please check.

Also you don't have ip route set for CUE module in the attached configuration.

- Vivek

Please rate useful posts.

Ruzanna Zohrabyan · ‎11-10-2015

OK. Here is full config file

Vivek Batra · ‎11-10-2015

Other point, which SIP phones you're using? There is no type command under voice register pool.

- Vivek

Please rate useful posts.

Ruzanna Zohrabyan · ‎11-10-2015

I use Xlite softphone

Vivek Batra · ‎11-10-2015

<<DIAL-PEER for CME and CUE connection changes. Especially "session target ipv4" automaticaly changes to my SIP phone IP address>>

How did you verify this? Can you please share?

- Vivek

Please rate useful posts.

Ruzanna Zohrabyan · ‎11-10-2015

After SIP phone registration, I notcied that all incoming calls comes to this phone. Then I check running-config, and at this section

dial-peer voice 1 voip
paramspace callsetup after-hours-exempt FALSE
destination-pattern 10.
session protocol sipv2
session target ipv4:192.168.100.2
session transport udp
no voice-class sip bandwidth video
no voice-class sip anat
dtmf-relay sip-notify
codec g711ulaw
ip qos dscp cs3 signaling
no vad

becomes to this

dial-peer voice 1 voip
paramspace callsetup after-hours-exempt FALSE
destination-pattern 10.
session protocol sipv2
session target ipv4:192.168.30.30
session transport udp
no voice-class sip bandwidth video
no voice-class sip anat
dtmf-relay sip-notify
codec g711ulaw
ip qos dscp cs3 signaling
no vad

Vivek Batra · ‎11-12-2015

It's really strange. You might be hitting known/unknow bug and worth to open a case with TAC.

- Vivek

Ruzanna Zohrabyan · ‎11-18-2015

Hello Vivek.

Now I have another SIP trunk problem related with CME 10.0 and CUCM 11.

All my problems are associated with SIP :))).

So, aforenamed CME connected with CUCM via SIP trunk, they are in different VLANs.

On the CME I have registered Cisco phones (SCCP). On CUCM I have ragistered one SIP phone (Yealink phone). From CUCM I can call to CME, but can't in the opposite direction.

Here is output of debug ccsip messages command:

.Nov 19 06:22:01.382: //128055/ABEA5C5CA79C/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:5000@192.168.0.145:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.2:5060;branch=z9hG4bK1DFA42365
From: "Ruzanna Zohrabyan" <sip:129@192.168.100.2>;tag=1818F60C-764
To: <sip:5000@192.168.0.145>
Date: Thu, 19 Nov 2015 06:22:01 GMT
Call-ID: ADCAC252-8DBC11E5-A7A1FF2D-93D729F8@192.168.10.2
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2884263004-2377912805-2812084013-2480351736
User-Agent: Cisco-SIPGateway/IOS-15.3.3.M
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1447914121
Contact: <sip:129@192.168.10.2:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 8796 7988 IN IP4 192.168.10.2
s=SIP Call
c=IN IP4 192.168.10.2
t=0 0
m=audio 16806 RTP/AVP 0 101
c=IN IP4 192.168.10.2
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

.Nov 19 06:22:01.386: //128055/ABEA5C5CA79C/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.10.2:5060;branch=z9hG4bK1DFA42365
From: "Ruzanna Zohrabyan" <sip:129@192.168.100.2>;tag=1818F60C-764
To: <sip:5000@192.168.0.145>
Date: Thu, 19 Nov 2015 06:22:01 GMT
Call-ID: ADCAC252-8DBC11E5-A7A1FF2D-93D729F8@192.168.10.2
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0

.Nov 19 06:22:01.386: //128055/ABEA5C5CA79C/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 192.168.10.2:5060;branch=z9hG4bK1DFA42365
From: "Ruzanna Zohrabyan" <sip:129@192.168.100.2>;tag=1818F60C-764
To: <sip:5000@192.168.0.145>;tag=924514903
Date: Thu, 19 Nov 2015 06:22:01 GMT
Call-ID: ADCAC252-8DBC11E5-A7A1FF2D-93D729F8@192.168.10.2
CSeq: 101 INVITE
Allow-Events: presence
Warning: 399 UnicompCM "Unable to find a device handler for the request received on port 55549 from 192.168.10.2"
Content-Length: 0

.Nov 19 06:22:01.394: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:5000@192.168.0.145:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.2:5060;branch=z9hG4bK1DFA42365
From: "Ruzanna Zohrabyan" <sip:129@192.168.100.2>;tag=1818F60C-764
To: <sip:5000@192.168.0.145>;tag=924514903
Date: Thu, 19 Nov 2015 06:22:01 GMT
Call-ID: ADCAC252-8DBC11E5-A7A1FF2D-93D729F8@192.168.10.2
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

Vivek Batra · ‎11-19-2015

Hi,

Follwoing is the error from CUCM;

Warning: 399 UnicompCM "Unable to find a device handler for the request received on port 55549 from 192.168.10.2"

This probably means that CME uses 192.168.10.2 to source the SIP packets to CUCM however SIP trunk in CUCM is not pointed to this IP, it may be pointed to some other interface IP address of CME and hence rejecting this call.

Can you please check what is the IP address of CME you've configured on SIP trunk in CUCM?

- Vivek

Ruzanna Zohrabyan · ‎11-19-2015

Yeees, you are right. On CUCM SIP trunk was configured with IP address 192.168.100.1, when I changed it to 192.168.10.2 (that is voice router IP address) it worked.

Thank you Vivek. :) You are the best. :)

Vivek Batra · ‎11-19-2015

Thanks for the updade and comments :)

- Vivek

Ruzanna Zohrabyan · ‎11-10-2015

192.168.30.30 is my computer IP address on which running SIP softphone

after correcting

session target ipv4:192.168.30.30 to session target ipv4:192.168.100.2

it works fine!

CallManager Express SIP trunk problem