Solved: Re: IPHONE with UC540 SIP "internal server error"

Michael Hamann · ‎09-13-2012

Hello,

I am trying to setup an iphone as mobile phone device together with a SMB UC540 system. the System has the newest IOS installed (Cisco IOS Software, UC500 Software (UC500-ADVIPSERVICESK9-M), Version 15.1(4)M4b). Normal telephony with several 7965 und 7945 works without problems.

Now our customers wants to use his IPhone as a phone device. So we configured the UC540 according to http://www.ccierants.com/2011/05/finally-cisco-mobile-81-supports-cme-86.html the customer installed Cisco Jabber (since Cisco Mobile 8.1 is not available anymore) and entered Device ID, TFP Server and username/pw....

The configuration (parts of it) on the UC450 looks like this:

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

supplementary-service h450.12

sip

bind control source-interface BVI100

bind media source-interface BVI100

registrar server expires max 1200 min 300

no update-callerid

!

voice class codec 1

codec preference 1 g711ulaw

codec preference 2 g729r8

!

voice register global

mode cme

source-address 172.19.15.1 port 5060

max-dn 10

max-pool 10

authenticate register

hold-alert

tftp-path flash:

create profile sync 0204580672223416

!

voice register dn 1

number 25

call-forward b2bua busy 88

call-forward b2bua noan 88 timeout 20

call-forward b2bua unregistered 88

name Michael Hamann

no-reg

label 25

!

voice register pool 1

registration-timer max 720 min 660

id mac 1234.5678.9100

session-transport tcp

type CiscoMobile-iOS

number 1 dn 1

dtmf-relay rtp-nte

username hamann password 12345

codec g711ulaw

!

------------

The IP interfaces look like this:

UC540#show ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 unassigned YES NVRAM administratively down down

In0/0 172.19.16.2 YES unset up up

Vlan1 unassigned YES unset up up

Vlan100 unassigned YES unset up up

NVI0 unassigned NO unset up up

BVI1 192.168.200.91 YES NVRAM up up

BVI100 172.19.15.1 YES NVRAM up up

Loopback0 172.19.16.2 YES NVRAM up up

the tftp Server is bound to BVI100. A debug shows that the IPhone reaches the tftp server and gets his configuration file. But when the phone tries to register via SIP I get the following debug messages (debug ccsip messages):

----------------

001981: Sep 13 06:27:53.434: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 192.168.220.5:59997;branch=z9hG4bK57e47025

From: <sip:25@172.19.15.1>;tag=000000000000001728568569-4850c52f

To: <sip:25@172.19.15.1>

Date: Thu, 13 Sep 2012 06:27:53 GMT

Call-ID: 00000000-0000000b-3838095b-66ee5232@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 129 REGISTER

Content-Length: 0

001982: Sep 13 06:27:53.482: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 500 Internal Server Error

Via: SIP/2.0/TCP 192.168.220.5:59997;branch=z9hG4bK57e47025

From: <sip:25@172.19.15.1>;tag=000000000000001728568569-4850c52f

To: <sip:25@172.19.15.1>;tag=1D19CF30-CD5

Date: Thu, 13 Sep 2012 06:27:53 GMT

Call-ID: 00000000-0000000b-3838095b-66ee5232@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 129 REGISTER

Content-Length: 0

001983: Sep 13 06:27:53.482: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/TCP 192.168.220.5:59997;branch=z9hG4bK2ec1b5c0

From: <sip:25@172.19.15.1>;tag=000000000000001728568569-4850c52f

To: <sip:25@172.19.15.1>;tag=1D19CF2C-738

Date: Thu, 13 Sep 2012 06:27:53 GMT

Call-ID: 00000000-0000000b-3838095b-66ee5232@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 128 REGISTER

WWW-Authenticate: Digest realm="bitconsulting",nonce="ACBAE8F002E8FB1E",algorithm=MD5,qop="auth"

Content-Length: 0

001984: Sep 13 06:27:58.110: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

REFER sip:172.19.15.1 SIP/2.0

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK4da4a08d

From: <sip:000000000000@192.168.220.5>;tag=000000000000001815e09326-4adcaf02

To: <sip:172.19.15.1>

Call-ID: 00000000-0000000d-5e65d2b3-6eec162f@192.168.220.5

Date: Thu, 13 Sep 2012 06:27:57 GMT

CSeq: 1000 REFER

User-Agent: Cisco-SIPIPCommunicator/9.2.1

Expires: 10

Max-Forwards: 0

Contact: <sip:000000000000@192.168.220.5:60000>

Require: norefersub

Referred-By: <sip:000000000000@192.168.220.5>

Refer-To: cid:7328b0cd@192.168.220.5

Content-Id: <7328b0cd@192.168.220.5>

Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE

Content-Length: 1297

Content-Type: application/x-cisco-alarm+xml

Content-Disposition: session;handling=required

<?xml version="1.0" encoding="UTF-8" ?>

<x-cisco-alarm>

<String name="ModelNumber">SIPIPCommunicator</String>

<String name="LastProtocolEventSent">Sent:REGISTER sip:172.19.15.1 SIP/2.0 Cseq:130 REGISTER CallId:00000000-0000000b-3838095b-66ee5232@192.168.220.5</String>

</ParameterList>

</Alarm>

</x-cisco-alarm>

001985: Sep 13 06:27:58.114: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 400 Bad Request

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK4da4a08d

From: <sip:000000000000@192.168.220.5>;tag=000000000000001815e09326-4adcaf02

To: <sip:172.19.15.1>;tag=1D19E17C-2014

Date: Thu, 13 Sep 2012 06:27:58 GMT

Call-ID: 00000000-0000000d-5e65d2b3-6eec162f@192.168.220.5

CSeq: 1000 REFER

Content-Length: 0

Contact: <sip:172.19.15.1:5060;transport=tcp>

001986: Sep 13 06:28:02.974: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

REGISTER sip:172.19.15.1 SIP/2.0

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK19a3abb4

From: <sip:25@172.19.15.1>;tag=00000000000000190dd65e0e-74b8f03a

To: <sip:25@172.19.15.1>

Call-ID: 00000000-0000000c-746f9dcb-4be0b625@192.168.220.5

Max-Forwards: 70

Date: Thu, 13 Sep 2012 06:27:57 GMT

CSeq: 131 REGISTER

User-Agent: Cisco-SIPIPCommunicator/9.2.1

Contact: <sip:25@192.168.220.5:60000;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-000000000000>";+sip.instance="<urn:uuid:00000000-0000-0000-0000-000000000000>";+u.sip!devicename.ccm.cisco.com="SEP123456789100";+u.sip!model.ccm.cisco.com="30016"

Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.2.0

Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEP123456789100 ActiveLoad= InactiveLoad= Last=initialized"

Expires: 3600

Content-Type: multipart/mixed; boundary=uniqueBoundary

Mime-Version: 1.0

Content-Length: 1099

--uniqueBoundary

Content-Type: application/x-cisco-remotecc-request+xml

Content-Disposition: session;handling=optional

<?xml version="1.0" encoding="UTF-8"?>

<x-cisco-remotecc-request>

</contact>

</bulkregisterreq>

</x-cisco-remotecc-request>

--uniqueBoundary

Content-Type: application/x-cisco-remotecc-request+xml

Content-Disposition: session;handling=optional

<?xml version="1.0" encoding="UTF-8"?>

<x-cisco-remotecc-request>

</remotecc>

<service-control></service-control>

</combine>

</dialog>

</dialog>

</presence>

<cfwdall-anyline></cfwdall-anyline>

</optionsind>

</x-cisco-remotecc-request>

--uniqueBoundary--

001987: Sep 13 06:28:02.978: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

REGISTER sip:172.19.15.1 SIP/2.0

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK03d2cb5c

From: <sip:25@172.19.15.1>;tag=00000000000000190dd65e0e-74b8f03a

To: <sip:25@172.19.15.1>

Call-ID: 00000000-0000000c-746f9dcb-4be0b625@192.168.220.5

Max-Forwards: 70

Date: Thu, 13 Sep 2012 06:28:01 GMT

CSeq: 132 REGISTER

User-Agent: Cisco-SIPIPCommunicator/9.2.1

Contact: <sip:25@192.168.220.5:60000;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-000000000000>";+sip.instance="<urn:uuid:00000000-0000-0000-0000-000000000000>";+u.sip!devicename.ccm.cisco.com="SEP123456789100";+u.sip!model.ccm.cisco.com="30016"

Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.2.0

Content-Length: 0

Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEP123456789100 ActiveLoad= InactiveLoad= Last=initialized"

Expires: 0

001988: Sep 13 06:28:02.986: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK19a3abb4

From: <sip:25@172.19.15.1>;tag=00000000000000190dd65e0e-74b8f03a

To: <sip:25@172.19.15.1>

Date: Thu, 13 Sep 2012 06:28:02 GMT

Call-ID: 00000000-0000000c-746f9dcb-4be0b625@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 131 REGISTER

Content-Length: 0

001989: Sep 13 06:28:02.986: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK03d2cb5c

From: <sip:25@172.19.15.1>;tag=00000000000000190dd65e0e-74b8f03a

To: <sip:25@172.19.15.1>

Date: Thu, 13 Sep 2012 06:28:02 GMT

Call-ID: 00000000-0000000c-746f9dcb-4be0b625@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 132 REGISTER

Content-Length: 0

001990: Sep 13 06:28:03.034: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 500 Internal Server Error

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK03d2cb5c

From: <sip:25@172.19.15.1>;tag=00000000000000190dd65e0e-74b8f03a

To: <sip:25@172.19.15.1>;tag=1D19F480-6AD

Date: Thu, 13 Sep 2012 06:28:02 GMT

Call-ID: 00000000-0000000c-746f9dcb-4be0b625@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 132 REGISTER

Content-Length: 0

001991: Sep 13 06:28:03.034: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/TCP 192.168.220.5:60000;branch=z9hG4bK19a3abb4

From: <sip:25@172.19.15.1>;tag=00000000000000190dd65e0e-74b8f03a

To: <sip:25@172.19.15.1>;tag=1D19F47C-26F

Date: Thu, 13 Sep 2012 06:28:02 GMT

Call-ID: 00000000-0000000c-746f9dcb-4be0b625@192.168.220.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 131 REGISTER

WWW-Authenticate: Digest realm="bitconsulting",nonce="F915D05E02E8FED9",algorithm=MD5,qop="auth"

Content-Length: 0

--------------

So the phone tries to register via SIP and stops with an internal server error.

There are no ACLs in the system, no firewall between the IPhone and the UC system... I tried diferent settings also used the Cisco Mobile 8.0 client without succes... On the phone username is set to "hamann" password is "12345"...

On a lab system with same IOS the same IPhone it works like a charm....

Any hints ?

Thank you

Michael

keglass · ‎09-13-2012

Michael,

This community does not provide technical support and is not staffed with technical support experts. I recommend you post this and future technical support questions to the Cisco Support Community (https://supportforums.cisco.com/index.jspa) where our Cisco technical support experts provide debugging assistance. Another option is to open a ticket with the Cisco Technical Assistance Center (www.cisco.com/go/support) to get expert assistance.

We do encourage you to participate in the Cisco Collaboration Community and to also join our Cisco Collaboration User Group program! In the community, we encourage your discussion/sharing around collaboration topics and Cisco Collaboration Solutions, including business and IT requirements, industry trends, process, culture/organization issues, how collaboration can be used to transform businesses, vendor selection, adoption, training, architecture, licensing, and product features/functionality. If you are a customer or partner, you can also join the user group program to be eligible for member-only events and influence product direction.

We hope to hear from you again.

Kelli Glass

Moderator for the Cisco Collaboration Community

View solution in original post

keglass · ‎09-13-2012

Michael,

This community does not provide technical support and is not staffed with technical support experts. I recommend you post this and future technical support questions to the Cisco Support Community (https://supportforums.cisco.com/index.jspa) where our Cisco technical support experts provide debugging assistance. Another option is to open a ticket with the Cisco Technical Assistance Center (www.cisco.com/go/support) to get expert assistance.

We do encourage you to participate in the Cisco Collaboration Community and to also join our Cisco Collaboration User Group program! In the community, we encourage your discussion/sharing around collaboration topics and Cisco Collaboration Solutions, including business and IT requirements, industry trends, process, culture/organization issues, how collaboration can be used to transform businesses, vendor selection, adoption, training, architecture, licensing, and product features/functionality. If you are a customer or partner, you can also join the user group program to be eligible for member-only events and influence product direction.

We hope to hear from you again.

Kelli Glass

Moderator for the Cisco Collaboration Community