Hello, Attached chat_and_airport_sprout_core_20140528_1600.tbz With extra debug logging in sprout and pcap from clearwater and mas. There seems to have been 2 sprout cores . . . ?
Look at this time period: 16:34 2 handsets registered. chat. 16:36:26 one handset into airport mode 16:38:00 in pcap see OPTIONS 408 408 480 . . . 480 408 (last 2 packets 1922, 1923) 16:38:13 sprout logs Basic stack dump 16:39:24 First BYE seen 16:39:55 sprout logs Basic and Advanced stack dump 16:39:56 last BYE and 408 seen in pcap Thanks! James. On 28 May 2014 16:59, James Coleman <[email protected]>wrote: > Hello, > > My reply with attached logs and pcap is awaiting moderator . . . > in the meantime . . . here is the text . . . > > Thanks Matt, > > James. > > On 28 May 2014 16:44, James Coleman <[email protected]>wrote: > >> Great, Thanks very much Matt, . . . >> >> The full logs for those times are gone. :-7 >> However just now I did chat and airport mode and got a sprout core. >> I have collected .pcap and logs* (see attached)* . . . however I realise >> now sprout debug logging is not on. >> Anyway I will send these to you and turn up sprout logging and do it >> again. >> I presume the full sprout debug logs would be useful. >> >> I find Wireshark - Telephony - VoIP flow is quite useful to get an >> overview of what is happening. >> Can see that the BYE messages go a bit funny. >> I'm not sure why but the handset that doesn't go into airport mode >> initiates BYE. >> I'm guessing something happening on the MSRP session triggered that. >> I should capture debug or .pcap on the MAS to see that. >> BYE from that handset transitions through sprout to MAS okay >> BYE from MAS to other handset is retried . . . every 4 secs . . . 8 times >> 408 request timeout response to BYE >> 408 request timeout response to an OPTIONS >> OPTIONS >> 100 trying >> 480 temporarily unavailable response to OPTIONS >> **sprout core dump** >> >> >> answering questions inline below . . . in colour . . . >> >> >> Thanks for digging into this! >> >> James. >> >> >> >> On 28 May 2014 15:11, Matt Williams <[email protected]> wrote: >> >>> James, >>> >>> Thanks for raising this issue - I've been digging into it. >>> >>> I was hoping I could get a bit more detail on the SIP flow here. I've >>> stated what I understand (with some gaps) below - please could you correct >>> any errors, and provide any missing details? >>> - You're sending a SIP MESSAGE from one UE. >>> - You're trying to send the SIP MESSAGE to another UE that is registered >>> but uncontactable (because it's in airplane mode). >>> >> >> *Yes. A normal chat session happens first. * >> *INVITE from one handset -> bono -> sprout -> mas -> sprout -> bono -> >> other handset* >> * then 200 ok* >> * then ACK* >> * then chat messages exchange on MSRP session* >> *I have just one ims and one mas so anything going to mas (OPTIONS or >> INVITES or other messages) comes straight back out on the other leg.* >> >> >>> - You're going via an AS. (Is that right?) >> >> - What (if anything) does the AS do to the SIP flow? >>> >> >> *Yes. . . sprout -> mas -> sprout generally for SIP messages . . . * >> *The flow is split into 2 legs (handset1 to mas and mas to handset2).* >> *MSRP session for chat or file transfer or other happens on MAS.* >> >> >>> - Do you have I-CSCF enabled? >>> >> >> *I think so, in /etc/clearwater/config:* >> * # I-CSCF/S-CSCF configuration * >> >> *scscf=5054icscf=5052My clearwater node is an all-in-one single-node >> instance in Amazon.* >> >> >>> - Do you have Rf billing enabled? >>> >> >> *No, ralf is not running (or installed I think).* >> >> >>> >>> Also, is it possible to share the full logs, right from the initial >>> receipt of the SIP MESSAGE (maybe as an attachment rather than inline)? >>> >> >> *Yes, well, . . :) see attached and I'm turning up debug now to get some >> more . . .* >> >> >>> Please let me know. >>> >>> Thanks for your help, >>> >>> Matt >>> >>> -- <http://www.golgi.io/> <https://www.linkedin.com/company/openmind-networks?trk=fc_badge> <https://twitter.com/Openmind_Ntwks> openmindnetworks.com
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
