Hello,

I am using clearwater Elite release.
With two different clients I am having a problem . . .
It looks like ACKs from clients get to bono and bono sends on to sprout . .
.
BUT sprout never receives the ACK.
(ACKs in response to various things seem to have same problem)

With one client this results in chat being a bit flaky but mostly working.
With another client chat is very flaky and not working.

I can see in bono log:
 a SIP 200 OK is received and sent to handset (in response to chat or file
xfer INVITE)
 an ACK is received from handset
 ACK is re-written and sent to sprout
   *** BUT using tcpdump I don't see the ACK sent to sprout (port 5054) ?
***

In sprout log:
 we see the SIP 200 OK going out
 when we expect the ack I am seeing a pjsip assert. ?
I'm not sure if the pjsip asserts are related to the ACK.

I don't understand (yet) what is happening . . . I wonder could someone
take a look at the logs in this mail?
1. is the pjsip Assert related and what does it mean?
2. what is the problem with the ACK? Is it due to the ACK content?
  is communication from bono to sprout failing for these ACKs?

Thanks in advance if you can take a look and give me any pointers!

James.


I have just included a part of bono and sprout log here:


13-05-2014 09:04:24.620 Verbose stack.cpp:242: TX 1219 bytes Response msg
200/INVITE/cseq=1 (tdta0x7f0ea00603a0) to UDP 89.101.214.194:20770:
--start msg--

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.128.211:5060
;rport=20770;received=89.101.214.194;branch=z9hG4bKcffd5ef3d054a198e4185f7d15594add373434
From: <sip:[email protected]>;tag=jY000XUHWA
To: <sip:[email protected];user=phone>;tag=hpclwkxqqtdo
Call-ID: [email protected]
Contact: <sip:[email protected]:5060
>;+sip.instance="<urn:uuid:f65f00be-b9b7-392f-873c-42130f8f084e>";+g.oma.sip-im
Record-Route: <sip:[email protected]:5060>
Record-Route: <sip:ec2-54-198-205-191.compute-1.amazonaws.com:5054
;transport=TCP;lr>
Record-Route: <sip:10.124.51.133:5058;transport=TCP;lr>
Record-Route:
<sip:/gW/[email protected]:5060
;transport=UDP;lr>
Allow: INVITE, UPDATE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, MESSAGE, REFER
CSeq: 1 INVITE
Content-Type: application/sdp
Content-Length:   354

v=0
o=OpenmindAccess 1399971864 1399971864 IN IP4 176.34.92.238
s=-
c=IN IP4 176.34.92.238
t=0 0
m=message 2855 TCP/MSRP *
a=path:msrp://176.34.92.238:2855/097680c0;tcp
a=setup:passive
a=accept-types:image/jpeg
a=file-transfer-id:1399971860838
a=max-size:10240000
a=file-selector:name:"IMAG0001(8).jpg" type:image/jpeg size:77324
a=recvonly

--end msg--



13-05-2014 09:04:24.903 Verbose stack.cpp:226: RX 862 bytes Request msg
ACK/cseq=1 (rdata0x7f0e8c065e78) from UDP89.101.214.194:20770:
--start msg--

ACK sip:[email protected]:5060 SIP/2.0
Call-ID: [email protected]
CSeq: 1 ACK
From: <sip:[email protected]>;tag=jY000XUHWA
To: <sip:[email protected];user=phone>;tag=hpclwkxqqtdo
Via: SIP/2.0/UDP 192.168.128.211:5060;branch=z9hG4bKc8a2755b15c8d2316a3383b
ef11f3cc2373434;rport
Max-Forwards: 70
Route: <sip:/gW/[email protected].
com:5060;transport=UDP;lr>,<sip:10.124.51.133:5058;
transport=TCP;lr>,<sip:ec2-54-198-205-191.compute-1.amazonaws.com:5054
;transport=TCP;lr>,<sip:[email protected]:5060>
Contact: <sip:[email protected]:5060;transport=udp>;+
sip.instance="<urn:uuid:9d6d8b7a-4589-3dab-ab1f-7877c67243a9>"
User-Agent: IM-client/OMA1.0 Neusoft-Silta-RCSe-client/2.0.1344.33_TR
Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER
Content-Length: 0


--end msg--
13-05-2014 09:04:24.903 Info pjutils.cpp:760: Resolved destination URI
sip:ec2-54-198-205-191.compute-1.amazonaws.com:5054;transport=TCP;lr to 1
servers
13-05-2014 09:04:24.903 Verbose pjsip:  tcpc0x2671268 TCP client transport
created
13-05-2014 09:04:24.903 Verbose pjsip:  tcpc0x2671268 TCP transport
10.124.51.133:58185 is connecting to 54.198.205.191:5054...
13-05-2014 09:04:24.903 Verbose stack.cpp:242: TX 1087 bytes Request msg
ACK/cseq=1 (tdta0x268daf0) to TCP54.198.205.191:5054:
--start msg--

ACK sip:[email protected]:5060 SIP/2.0
Record-Route: <sip:10.124.51.133:5058;transport=TCP;lr>
Record-Route: <sip:*/gW/w8E5kA*@ec2-54-198-205-191.compute-1.amazonaws.
com:5060;transport=UDP;lr>
Call-ID: [email protected]
CSeq: 1 ACK
From: <sip:[email protected]>;tag=jY000XUHWA
To: <sip:[email protected];user=phone>;tag=hpclwkxqqtdo
Via: SIP/2.0/TCP 10.124.51.133:58185;rport;branch=
z9hG4bKPj99be5097077d8dad70d5a4cb35f5645d
Via: SIP/2.0/UDP 192.168.128.211:5060;rport=20770;received=89.101.214.194;
branch=z9hG4bKc8a2755b15c8d2316a3383bef11f3cc2373434
Max-Forwards: 69
Route: <sip:ec2-54-198-205-191.compute-1.amazonaws.com:5054;
transport=TCP;lr>
Route: <sip:[email protected]:5060>
Contact: <sip:[email protected]:5060;transport=udp>;+
sip.instance="<urn:uuid:9d6d8b7a-4589-3dab-ab1f-7877c67243a9>"
User-Agent: IM-client/OMA1.0 Neusoft-Silta-RCSe-client/2.0.1344.33_TR
Allow: INVITE, UPDATE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, MESSAGE, REFER
P-Asserted-Identity: <sip:[email protected]>
Content-Length:  0


--end msg--





*sprout log . . . earlier:*

13-05-2014 09:04:24.571 Error pjsip: Assert failed:
../src/pjsip/sip_transaction.c:3159 event->type == PJSIP_EVENT_TX_MSG &&
event->body.tx_msg.tdata == tsx->last_tx
13-05-2014 09:04:24.611 Verbose stack.cpp:226: RX 1431 bytes Response msg
200/INVITE/cseq=1 (rdata0x7fd0ec11a048) from UDP 176.34.92.238:1024:
--start msg--

SIP/2.0 200 OK

. . .

13-05-2014 09:04:24.843 Error pjsip: Assert failed:
../src/pjsip/sip_transaction.c:3159 event->type == PJSIP_EVENT_TX_MSG &&
event->body.tx_msg.tdata == tsx->last_tx
13-05-2014 09:04:25.035 Verbose stack.cpp:226: RX 1476 bytes Response msg
200/INVITE/cseq=685 (rdata0x7fd0e044f138) from TCP 10.124.51.133:5058:
--start msg--

SIP/2.0 200 OK

. . .



*in sprout log at time of ACK message:13-05-2014 09:04:24.843 Error pjsip:
Assert failed: ../src/pjsip/sip_transaction.c:3159 event->type ==
PJSIP_EVENT_TX_MSG && event->body.tx_msg.tdata == tsx->last_tx*



*comparing with log with an ACK received into sprout from earlier this year
. . . *

04-03-2014 12:10:44.136 Verbose pjsip:    tcplis:5054 TCP listener
10.124.51.133:5054: got incoming TCP connection from10.124.51.133:53550,
sock=183
04-03-2014 12:10:44.136 Verbose pjsip: tcps0x7f0a3409 TCP server transport
created
04-03-2014 12:10:44.136 Verbose stack.cpp:221: RX 1057 bytes Request msg
ACK/cseq=1 (rdata0x7f0a3409b448) from TCP10.124.51.133:53550:
--start msg--

ACK sip:[email protected]:5060 SIP/2.0
Record-Route: <sip:10.124.51.133:5058;transport=TCP;lr>
Record-Route:
<sip:[email protected]:5060
;transport=UDP;lr>
Call-ID: [email protected]
CSeq: 1 ACK
From: <sip:[email protected]>;tag=ynLANSUjFA
To: <sip:[email protected];user=phone>;tag=kcetdyfirixc
Via: SIP/2.0/TCP 10.124.51.133:53550
;rport;branch=z9hG4bKPj0a3afc089bb020f92952ecd8af98e7ee
Via: SIP/2.0/UDP 192.168.127.233:5060
;rport=5060;received=89.101.214.194;branch=z9hG4bK7791ca5a24e33316178bd349b71bac4a313030
Max-Forwards: 69
Route: <sip:10.124.51.133:5054;transport=TCP;lr>
Route: <sip:[email protected]:5060>
Contact: <sip:[email protected]:5060
;transport=udp>;+sip.instance="<urn:uuid:75e5a19f-9549-35a1-a6cf-5c971e6dae86>"
User-Agent: IM-client/OMA1.0 Neusoft-Silta-RCSe-client/2.0.1344.33_TR
Allow: INVITE, UPDATE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, MESSAGE, REFER
P-Asserted-Identity: <sip:[email protected]>
Content-Length:  0


--end msg--

-- 


<http://www.linkedin.com/company/76647?trk=fc_badge>

openmindnetworks.com
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to