Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CU Personal Communicator doesn't connect to Presence Server

Hello.

Could anybody help me.

I have CUCM business edition 6.1.2 and CUPS 6.0.4. all software was installed on VMWARE. In addition I have MS Win2003 when I was installing the AD (LDAP) and the DNS services.

When i login to CUPC 7.1 i see at tab Show Server Health that Presence is not connected. It is triying to connect alltime.

DNS service is work. I can ping all srv and the host via short name and full name.

  • Unified Communications Applications
8 REPLIES

Re: CU Personal Communicator doesn't connect to Presence Server

Can you make sure your CUPS server health is good? You will need to log into CUPS and run the "Troubleshooter" This will tell you if all services, CTIs, AXL, etc are configured and running

New Member

Re: CU Personal Communicator doesn't connect to Presence Server

Sorry, i forgot. yes, i can.

troubleshooter showed what all okay and all services were running whitout errors.

Re: CU Personal Communicator doesn't connect to Presence Server

Tough to say in VMware. You might be having some sort of SIP problem because of VMware. The CUPC client, you can turn on logging, then go through the logs on the PC to see what it's doing.

Also, on RTMT on the CUPS server you can turn on live trace logs for SIP proxy and see if you are even getting any invites from the client to connect.

New Member

Re: CU Personal Communicator doesn't connect to Presence Server

I attached UnifiedClientLog4CXX and Resiplog log files.

I haven't the sip skill

Tommer, Could you help me?

Thanks a lot.

New Member

Re: CU Personal Communicator doesn't connect to Presence Server

SDI log for SIP Proxy

<:STANDALONECLUSTER><:VM-CUPS><:ALL><:FFFF>

09/01/2008 14:00:49.900 ESP|Mon Sep 01 14:00:49 2008] PID(32356) mod_sip.c(375) ipc handler 1 msgs

[Mon Sep 01 14:00:49 2008] PID(10447) sip_tcp.c(2983) sip_tcp received auth state as: 0 for connid: 1022 from sip_sm

[Mon Sep 01 14:00:49 2008] PID(10447) sip_tcp.c(495) sip_tcp is now sending ok pdu 192.168.2.176 connid 1022, sock_fd 29 1 msgs

[Mon Sep 01 14:00:49 2008] PID(1564) sip_sm.c(382) sip_process_sendok_msg ed7c9d07756e9838MTIzNDAyYzA0ZGNmYjY2MjVmNjg4Zjc3MWE1ZmMwNWQ.:1 connid 1022 sock_fd 29 (ffffffff:48bbbd51:48bbbd51:48bbbd51)

[Mon Sep 01 14:00:49 2008] PID(1564) mod_sip.c(375) ipc handler 1 msgs

PID(10447) prefork.c(1511) Perf Idle server maint 6:0:6:6

|<:STANDALONECLUSTER><:VM-CUPS><:ALL><:FFFF>

09/01/2008 14:00:49.900 ESP|ID(10447) prefork.c(1515) server stats: 3 http: 0 udp: 0 time: 19 ptime: 0 tevents: 0 ipc: 2 ievents: 2

|<:STANDALONECLUSTER><:VM-CUPS><:ALL><:FFFF>

09/01/2008 14:00:50.014 ESP|[Mon Sep 01 14:00:50 2008] PID(10447) sip_tcp.c(455) sip_tcp is now reporting pdu to state machine 192.168.2.176 connid 1022, sock_fd 29 0 msgs

PID(32358) sip_protocol.c(5663) Received 895 bytes TCP packet from 192.168.2.176:1417

REGISTER sip:demobox.voice.lan;transport=tcp SIP/2.0

Via: SIP/2.0/TCP 192.168.2.176:50054;branch=z9hG4bK-d87543-552dea7cc32e6f07-1--d87543-

Max-Forwards: 70

Contact: ;q=0.6

To: "Alexey Timoshenko"<>a_timoshenko@demobox.voice.lan>

From: "Alexey Timoshenko"<>a_timoshenko@demobox.voice.lan>;tag=124e3959

Call-ID: ed7c9d07756e9838MTIzNDAyYzA0ZGNmYjY2MjVmNjg4Zjc3MWE1ZmMwNWQ.

CSeq: 2 REGISTER

Expires: 3600

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO

Supported: eventlist

User-Agent: Cisco-UCModel01/7.0.1

Authorization: Digest username="a_timoshenko",realm="demobox.voice.lan",nonce="48bbbd51",uri="sip:demobox.voice.lan;transport=tcp",response="d097c0f8e46f2dbe7645da425b609e6f",cnonce="e32da8e1048cd49a",nc=00000001,qop=auth,algorithm=MD5

Content-Length: 0

|<:STANDALONECLUSTER><:VM-CUPS><:ALL><:FFFF>

09/01/2008 14:00:50.252 ESP|PID(32358) sip_sm.c(1100) Sent 481 bytes TCP packet to 192.168.2.176:1417

SIP/2.0 401 Unauthorized

Via: SIP/2.0/TCP 192.168.2.176:50054;received=192.168.2.176;branch=z9hG4bK-d87543-552dea7cc32e6f07-1--d87543-

Call-ID: ed7c9d07756e9838MTIzNDAyYzA0ZGNmYjY2MjVmNjg4Zjc3MWE1ZmMwNWQ.

From: "Alexey Timoshenko"<>a_timoshenko@demobox.voice.lan>;tag=124e3959

To: "Alexey Timoshenko"<>a_timoshenko@demobox.voice.lan>

CSeq: 2 REGISTER

WWW-Authenticate: DIGEST realm="demobox.voice.lan", nonce="48bbbd52", qop="auth", algorithm=MD5

Content-Length: 0

New Member

Re: CU Personal Communicator doesn't connect to Presence Server

I set "Authentication Module Status" to off.

And after that i can login to CUPS.

but i don't know is it correct?

New Member

Re: CU Personal Communicator doesn't connect to Presence Server

Try using a_timoshenko@demobox.voice.lan as your userid in the CUCM, modifying the LDAP System configuration (setting "LDAP Attribute for User ID" to "mail").

And ensure that under System->Licensing->Capabilities Assignments

your user has both "CUP Enabled" and "CUPC Enabled" checked

HTH,

Alberto

New Member

Re: CU Personal Communicator doesn't connect to Presence Server

I just had the same issue. i fixed it with help of tech support and the digest credential.

hope this helps

Jeff

Due to the SIP protocol design (IETF standard), you need to configure "Digest Credential" on CUCM Admin > User Management > End User page. The Digest Credential could be any non-blank value.

If you don't want to configure "Digest Credential" for each end users, there are two ways to bypass the SIP authentication:

Option 1: Like you did, set "authentication module" to off.

Option 2: On CUP server, create an incoming ACL. Any address pattern match the ACL will bypass the SIP authentication. The "ALL" pattern would match any address.

269
Views
0
Helpful
8
Replies
This widget could not be displayed.