Hi James, I'm glad to hear your ACKs are being routed correctly now!
It looks like Bono was resolving the ec2-54.x.x.x:5054 to the public IP rather than the private IP (from the logs - "Request msg ACK/cseq=1 (tdta0x268daf0) to TCP54.x.x.x:5054")). Sprout typically rejects messages to its *external* IP address (depending on your particular port rules of course!), so the ACK wasn't getting through. Ellie -----Original Message----- From: clearwater-boun...@lists.projectclearwater.org [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of James Coleman Sent: 15 May 2014 15:26 To: clearwater@lists.projectclearwater.org Subject: Re: [Clearwater] clearwater, chat/file transfer fails, ACK reveived by bono, pjsip assert error in sprout my ACK problem is solved . . . The ec2-54.x.x.x:5054 address in Route in the ACK (from Record-Route in 200 OK) was the problem. >From old bono log I can see for the internal ports in the past the 10.x.x.x ip >address was used. Changing sprout_hostname in /etc/clearwater/config to the 10.x.x.x ip address solved it. ims chat is working again. James. from Record-Route in 200 OK with problem: Record-Route: <sip:masorig@176.34.92.238: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/w8e...@ec2-54-198-205-191.compute-1.amazonaws.com:5060 ;transport=UDP;lr> Route in ACK in older bono log: 04-03-2014 12:10:02.454 Verbose stack.cpp:221: RX 827 bytes Request msg ACK/cseq=1 (rdata0x7fa3f80953a8) from UDP 89.101.214.194:17377: . . . *Route: <sip:t73x7i7...@ec2-54-198-205-191.compute-1.amazonaws.com:5060;transport=UDP;lr>,<sip:10.124.51.133:5058;transport=TCP;lr>,<sip:10.124.51.133:5054;transport=TCP;lr>,<sip:masorig@176.34.92.238:5060 <http://sip:masorig@176.34.92.238:5060>>* sprout process: 4 S sprout 1113 1 0 80 0 - 244136 futex_ 09:10 ? 00:00:33 /usr/share/clearwater/bin/sprout --domain openims.test --localhost 10.124.51.133 --realm openims.test --memstore /etc/clearwater/cluster_settings --hss 10.124.51.133:8888 --chronos localhost:7253 --xdms 10.124.51.133:7888 --enum 10.124.51.133 --enum-suffix .e164.arpa --sas 0.0.0.0,spr...@ec2-54-198-205-191.compute-1.amazonaws.com--pjsip-threads 1 --worker-threads 10 --record-routing-model pcscf --default-session-expires 600 --authentication -T 10.124.51.133 -o 9888 -a /var/log/sprout -F /var/log/sprout -L 4 --scscf 5054 *--scscf_uri sip:ec2-54-198-205-191.compute-1.amazonaws.com:5054;transport=TCP* --icscf 5052 On 14 May 2014 15:46, James Coleman <james.cole...@openmindnetworks.com>wrote: > 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=z9hG4bKcffd5ef3d054a198e41 > 85f7d15594add373434 > From: <sip:+353894468...@openims.test>;tag=jY000XUHWA > To: <sip:+353861953...@openims.test;user=phone>;tag=hpclwkxqqtdo > Call-ID: aY000XUGWA@192.168.128.211 > Contact: <sip:+353894468340@192.168.128.211:5060 > >;+sip.instance="<urn:uuid:f65f00be-b9b7-392f-873c-42130f8f084e>";+g.o > >ma.sip-im > Record-Route: <sip:masorig@176.34.92.238: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/w8e...@ec2-54-198-205-191.compute-1.amazonaws.com: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:+353894468340@192.168.128.211:5060 SIP/2.0 > Call-ID: aY000XUGWA@192.168.128.211 > CSeq: 1 ACK > From: <sip:+353894468...@openims.test>;tag=jY000XUHWA > To: <sip:+353861953...@openims.test;user=phone>;tag=hpclwkxqqtdo > Via: SIP/2.0/UDP 192.168.128.211:5060;branch= > z9hG4bKc8a2755b15c8d2316a3383bef11f3cc2373434;rport > Max-Forwards: 70 > Route: <sip:/gW/w8E5kA@ec2-54-198-205-191.compute-1.amazonaws. > 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:masorig@176.34.92.238:5060> > Contact: <sip:+353894468340@192.168.128.211: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:+353894468340@192.168.128.211: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: aY000XUGWA@192.168.128.211 > CSeq: 1 ACK > From: <sip:+353894468...@openims.test>;tag=jY000XUHWA > To: <sip:+353861953...@openims.test;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:masorig@176.34.92.238:5060> > Contact: <sip:+353894468340@192.168.128.211: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:+353894468...@openims.test> > 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:+353894017259@192.168.127.233:5060 SIP/2.0 > Record-Route: <sip:10.124.51.133:5058;transport=TCP;lr> > Record-Route: > <sip:17rycmv...@ec2-54-198-205-191.compute-1.amazonaws.com:5060 > ;transport=UDP;lr> > Call-ID: lnLANSUiFA@192.168.127.233 > CSeq: 1 ACK > From: <sip:+353894017...@openims.test>;tag=ynLANSUjFA > To: <sip:+353894017...@openims.test;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=z9hG4bK7791ca5a24e33316178b > d349b71bac4a313030 > Max-Forwards: 69 > Route: <sip:10.124.51.133:5054;transport=TCP;lr> > Route: <sip:masorig@176.34.92.238:5060> > Contact: <sip:+353894017259@192.168.127.233: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:+353894017...@openims.test> > Content-Length: 0 > > > --end msg-- > -- <http://www.linkedin.com/company/76647?trk=fc_badge> openmindnetworks.com _______________________________________________ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/listinfo/clearwater
