Xlite (sip) and UC500

Unanswered Question
Aug 24th, 2009

I am a happy user of the UC500 :)

But, now I have a problem with the Xlite client outbound call. I can register on the Xlite client to the UC500 server. I can recieve call on this Xlite client user on my computer. But when I take an outbound call, I see the message on the top of the Xlite client "Call failed: Internal Server error".

I have deleted all the access-lists. Can somebody say how to troubeshoot now....?

The following configure I have add:

voice register global
mode cme
source-address WAN IP port 5060
max-dn 20
max-pool 10
authenticate register
!
voice register dn  1
number 501
allow watch
!
voice register dn  2
number 502
!
voice register pool  1
id mac FFFF.FFFF.FFFF
number 1 dn 1
dtmf-relay sip-notify
username 501 password 501501
codec g711alaw
!
voice register pool  2
id mac FFFF.FFFF.FFFF
number 1 dn 2
dtmf-relay sip-notify
username 502 password 502502
codec g711alaw

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Steven Smith Mon, 08/24/2009 - 14:01

You probably know this already, but this is not a supported configuration, although this could work with no problems.

Could you do a debug ccsip messages?  Also, could you post your whole config removing passwords?

w.boerendans Mon, 08/24/2009 - 14:21

Is there a support configuration for SIP softphones for the UC500?

See the attachment for the running-config

The command "debug ccsip events" and than "terminal monitor" gives the following output:

Aug 24 21:21:40.987: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event f
rom SIP SPI : SIPSPI_EV_OUTBOUND_REGISTER
Aug 24 21:21:40.991: //95/F322FCE68070/SIP/Event/sact_idle_new_message_register:

ccsip_api_register_ind return value : SIP_SUCCESS

Aug 24 21:21:40.991: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event f
rom SIP SPI : SIPSPI_EV_REGISTER_RESP
Aug 24 21:21:47.211: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_call_subscribe_response:
Queued event from SIP SPI : SIPSPI_EV_CC_SUBSCRIBE_RESP
Aug 24 21:21:47.211: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_api_initiate_subscription
_termination: Queued event from SIP SPI : SIPSPI_EV_SUBSCRIPTION_TERMINATED

Steven Smith Mon, 08/24/2009 - 14:29

The messages seem to be about registration messages.  Can you do a debug ccsip messages when you are trying to make the call?

w.boerendans Mon, 08/24/2009 - 14:41

Aug 24 21:41:06.895: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 84.87.43.170:65076;branch=z9hG4bK-d8754z-fb774921cc27277b-1---d
8754z-;rport
Max-Forwards: 70
Contact:
To: "202"[email protected]>
From: "501"[email protected]>;tag=4c723802
Call-ID: NTU4ZGRiMjk4NzhhMjQxYWViM2UxOGUzNjllZmFiYmI.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF
O
Content-Type: application/sdp
User-Agent: X-Lite release 1103k stamp 53621
Content-Length: 264

v=0
o=- 1 2 IN IP4 84.87.43.170
s=CounterPath X-Lite 3.0
c=IN IP4 84.87.43.170
t=0 0
m=audio 40896 RTP/AVP 107 0 8 101
a=alt:1 1 : lLwAR3l/ MqbYvi3Z 84.87.43.170 40880
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:101 telephone-event/8000
a=sendrecv

Aug 24 21:41:06.899: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 84.87.43.170:65076;branch=z9hG4bK-d8754z-fb774921cc27277b-1---d
8754z-;rport
From: "501"[email protected]>;tag=4c723802
To: "202"[email protected]>;tag=5A547C-1BB3
Date: Mon, 24 Aug 2009 21:41:06 GMT
Call-ID: NTU4ZGRiMjk4NzhhMjQxYWViM2UxOGUzNjllZmFiYmI.
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=63
Content-Length: 0

Aug 24 21:41:06.959: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 84.87.43.170:65076;branch=z9hG4bK-d8754z-fb774921cc27277b-1---d
8754z-;rport
To: "202"[email protected]>;tag=5A547C-1BB3
From: "501"[email protected]>;tag=4c723802
Call-ID: NTU4ZGRiMjk4NzhhMjQxYWViM2UxOGUzNjllZmFiYmI.
CSeq: 1 ACK
Content-Length: 0

w.boerendans Mon, 08/24/2009 - 14:52

Yes, here the log:

Aug 24 21:52:43.599: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpSocketReads: Msg enqueu
ed for SPI with IP addr: 84.87.43.170:65076
Aug 24 21:52:43.599: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event
: ccsip_spi_get_msg_type returned: 2 for event 1
Aug 24 21:52:43.599: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewCon
nMsg: context=0x00000000
Aug 24 21:52:43.599: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 84.87.43.170:65076;branch=z9hG4bK-d8754z-2238ec7c9324416f-1---d
8754z-;rport
Max-Forwards: 70
Contact:
To: "202"[email protected]>
From: "501"[email protected]>;tag=1d2b754f
Call-ID: YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF
O
Content-Type: application/sdp
User-Agent: X-Lite release 1103k stamp 53621
Content-Length: 264

v=0
o=- 0 2 IN IP4 84.87.43.170
s=CounterPath X-Lite 3.0
c=IN IP4 84.87.43.170
t=0 0
m=audio 24332 RTP/AVP 107 0 8 101
a=alt:1 1 : /Zx9KqFE oJ5unffo 84.87.43.170 24316
a=fmtp:101 0-15
a=rtpmap:107 BV32/16000
a=rtpmap:101 telephone-event/8000
a=sendrecv

Aug 24 21:52:43.599: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Chec
king Invite Dialog
Aug 24 21:52:43.603: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIAddContextToTable: Added c
ontext(0x84F77F14) with key=[200] to table
Aug 24 21:52:43.603: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: D
ialog Transaction Address 84.87.43.170,Port 65076, Transport 1, SentBy Port 6507
6
Aug 24 21:52:43.603: //-1/49579DB48087/SIP/State/sipSPIChangeState: 0x84F77F14 :
State change from (STATE_NONE, SUBSTATE_NONE)  to (STATE_IDLE, SUBSTATE_NONE)
Aug 24 21:52:43.603: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: D
ialog Transaction Address 84.87.43.170,Port 65076, Transport 1, SentBy Port 5060
Aug 24 21:52:43.603: //-1/xxxxxxxxxxxx/SIP/Info/sipSPISetDateHeader: Converting
TimeZone CET to SIP default timezone = GMT
Aug 24 21:52:43.603: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: D
ialog Transaction Address 84.87.43.170,Port 65076, Transport 1, SentBy Port 6507
6
Aug 24 21:52:43.603: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIGetContentGTD: No GTD foun
d in inbound container
Aug 24 21:52:43.603: //-1/49579DB48087/SIP/Info/sipSPIUaddCcbToUASReqTable: ****
Adding to UAS Request table.
Aug 24 21:52:43.603: //-1/49579DB48087/SIP/Info/sipSPIUaddCcbToTable: Added to t
able. ccb=0x84F77F14 key=YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.202
Aug 24 21:52:43.603: //-1/49579DB48087/SIP/Info/sipSPIMatchSrcIpGroup: Match not
found on carrier id
Aug 24 21:52:43.603: //-1/49579DB48087/SIP/Info/sipSPIUaddCcbToUASRespTable: ***
*Adding to UAS Response table.
Aug 24 21:52:43.603: //-1/49579DB48087/SIP/Info/sipSPIUaddCcbToTable: Added to t
able. ccb=0x84F77F14 key=YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.64F5FC-745
Aug 24 21:52:43.607: //-1/49579DB48087/SIP/Transport/sipSPITransportSendMessage:
msg=0x86CB4768, addr=84.87.43.170, port=65076, sentBy_port=65076, is_req=0, tra
nsport=1, switch=0, callBack=0x80D14728
Aug 24 21:52:43.607: //-1/49579DB48087/SIP/Transport/sipSPITransportSendMessage:
Proceedable for sending msg immediately
Aug 24 21:52:43.607: //-1/49579DB48087/SIP/Transport/sipTransportLogicSendMsg: s
witch transport is 0
Aug 24 21:52:43.607: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage
: Posting send for msg=0x86CB4768, addr=84.87.43.170, port=65076, connId=0 for U
DP
Aug 24 21:52:43.607: //-1/49579DB48087/SIP/Info/sentErrResDisconnecting: Sent an
3456XX Error Response
Aug 24 21:52:43.607: //-1/49579DB48087/SIP/State/sipSPIChangeState: 0x84F77F14 :
State change from (STATE_IDLE, SUBSTATE_NONE)  to (STATE_DISCONNECTING, SUBSTAT
E_NONE)
Aug 24 21:52:43.607: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 84.87.43.170:65076;branch=z9hG4bK-d8754z-2238ec7c9324416f-1---d
8754z-;rport
From: "501"[email protected]>;tag=1d2b754f
To: "202"[email protected]>;tag=64F5FC-745
Date: Mon, 24 Aug 2009 21:52:43 GMT
Call-ID: YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=63
Content-Length: 0

Aug 24 21:52:43.663: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpSocketReads: Msg enqueu
ed for SPI with IP addr: 84.87.43.170:65076
Aug 24 21:52:43.663: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event
: ccsip_spi_get_msg_type returned: 2 for event 1
Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewCon
nMsg: context=0x00000000
Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 84.87.43.170:65076;branch=z9hG4bK-d8754z-2238ec7c9324416f-1---d
8754z-;rport
To: "202"[email protected]>;tag=64F5FC-745
From: "501"[email protected]>;tag=1d2b754f
Call-ID: YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.
CSeq: 1 ACK
Content-Length: 0

Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Chec
king Invite Dialog
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIFindCcbUASRespTable: *****
CCB found in UAS Response table. ccb=0x84F77F14
Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: S
ubsq Transaction Address 84.87.43.170,Port 65076, Transport 1, SentBy Port 5060
Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Info/sipSPISetDateHeader: Converting
TimeZone CET to SIP default timezone = GMT
Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Transport/sipSPIUpdateResponseInfo: S
ubsq Transaction Address 84.87.43.170,Port 65076, Transport 1, SentBy Port 65076
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/State/sipSPIChangeState: 0x84F77F14 :
State change from (STATE_DISCONNECTING, SUBSTATE_NONE)  to (STATE_DEAD, SUBSTAT
E_NONE)
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x84F77F14
State of The Call        : STATE_DEAD
TCP Sockets Used         : NO
Calling Number           : 501
Called Number            : 202
Source IP Address (Sig  ): 83.161.212.166
Destn SIP Req Addr:Port  : 84.87.43.170:0
Destn SIP Resp Addr:Port : 84.87.43.170:65076
Destination Name         : 84.87.43.170

Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC)    : 63
Disconnect Cause (SIP)   : 500

Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIDeleteContextFromTable: Co
ntext for key=[200] removed.
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIUdeleteCcbFromUASReqTable:
****Deleting from UAS Request table.
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIUdeleteCcbFromTable: Delet
ing from table. ccb=0x84F77F14 key=YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.2
02
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIUdeleteCcbFromUASRespTable
: ****Deleting from UAS Response table.
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIUdeleteCcbFromTable: Delet
ing from table. ccb=0x84F77F14 key=YjEwMjk3ZDM0NmVkM2U4MjE5MTAyNzc2MTcwMjE4Yzk.6
4F5FC-745
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIFlushEventBufferQueue: The
re are 0 events on the internal queue that are going to be free'd
Aug 24 21:52:43.667: //-1/49579DB48087/SIP/Info/sipSPIUfreeOneCCB: Freeing ccb 8
4F77F14
Aug 24 21:52:43.667: //-1/xxxxxxxxxxxx/SIP/Info/sipSPIGetContextFromTable: NO co
ntext for key[200]
Aug 24 21:52:47.075: //-1/xxxxxxxxxxxx/SIP/Info/httpish_msg_process_network_msg:
MSG LINE READ FAILURE DUE TO RS->EOF
Aug 24 21:52:47.075: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_network_message: p
rocess_network_msg: not complete
Aug 24 21:52:47.075: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:


Aug 24 21:52:47.075: //-1/xxxxxxxxxxxx/SIP/Error/HandleUdpSocketReads: SIP Messa
ge incomplete, trashed

wboerendans Tue, 08/25/2009 - 08:55

"You probably know this already, but this is not a supported configuration, although this could work with no problems."

1: Okay, but what is a supported configuration for SIP?

2: Can I downlaod aan Cisco SIP softphone? Is there a download link available?

Thanks in advance!

Steven Smith Tue, 08/25/2009 - 09:07

3rd Party SIP phones are not supported.  They might work with no issues, it is just that support will be tough to find.  We do support SIP trunks and work with several providers to make sure the config will work.  If you use CCA, you can see several drop down's for different SIP providers.

The softphone that is supported on UC500 is IP Communicator.  Currently, that is the only softphone that is support on the UC500.

wboerendans Tue, 08/25/2009 - 12:45

Okay, thanks.

But can I use the IP communicator over the Internet for a remote teleworker (without VPN connection)?

Steven Smith Tue, 08/25/2009 - 12:47

Without the VPN is going to be a problem.  Is there a reason you can't get the VPN client to work on their machine?

wboerendans Tue, 08/25/2009 - 03:30

I have the solution....

I have change the following

voice source-group CCA_SIP_SOURCE_GROUP
access-list 2
translation-profile incoming SIP_Incoming

to

voice source-group CCA_SIP_SOURCE_GROUP
translation-profile incoming SIP_Incoming

;)

Eivind Jonassen Tue, 08/25/2009 - 14:26

Do you use a domain name or an IP for the sip-server under "sip-ua" in your config. I've experienced a similar issue with my SP. The thing you could try is to add a whole subnet to access-list 2, instead of just the 1 IP. This is if you use a domain name for the sip server that is.

Regards

Eivind

wboerendans Wed, 08/26/2009 - 02:52

My config is:

sip-ua
no remote-party-id
retry invite 2
retry register 10
timers connect 100
registrar ipv4:192.168.10.1:5060 expires 3600
sip-server ipv4:192.168.10.1:5060
  host-registrar

For the test, I have deleted all the access-list.

Question: I use the internal IP adres.... Is this the problem? Maybe I have to use the WAN IP?

Steven Smith Thu, 09/10/2009 - 13:19

The access list that is there is to prevent toll fraud.  You would need to add in valid IP addresses for this to work.  If you added in the IP address of the remote system with XLITE it would work.  The rest of the sip-ua config doesn't really apply to your problem.

Actions

This Discussion