Hi Gavin, We expire the ODI token when the original transaction completes (as they’re used to keep track of which application servers we’ve already invoked for this request, so they’re not useful after the end of the transaction).
Do you see a log saying “Destroying AsChain 0x7fa5d8308700” amongst the logs you’ve omitted? If so, that will be the point at which the ODI token is expired. If the original transaction hasn’t completed, then I don’t think we should be expiring the ODI token – if you can send across the full logs, I can investigate further. If the original transaction has completed, then it might be useful to get a better idea of what you’re trying to achieve by reusing the ODI token – there might be alternative solutions. Best, Rob -- Rob Day Software Engineer, Project Clearwater From: Clearwater [mailto:[email protected]] On Behalf Of Gavin Murphy Sent: 27 November 2015 21:34 To: [email protected] Subject: [Clearwater] Expired ODI Token Hi, we've come across a situation where sprout appears to be saying that an ODI token that was issued a tenth of a second before has "expired". Here are the logs (some logs omitted): 27-11-2015 18:42:25.563 UTC Info scscfsproutlet.cpp:1084: Routing to Application Server sip:10.42.38.155:10672 with ODI token odi_7VhkxDKy0r for AsChain-term[0x7fa5d8308700]:6/7 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:148: Found next routable URI: sip:[email protected]:5054;lr 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:266: Found user - odi_7VhkxDKy0r 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:266: Found user - odi_7VhkxDKy0r 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:266: Found user - odi_7VhkxDKy0r 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:180: No Sproutlet found using service name or host 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:1074: Remove top Route header Route: <sip:[email protected]:5054;lr><sip:[email protected]:5054;lr> 27-11-2015 18:42:25.688 UTC Debug sproutletproxy.cpp:1521: Adding message 0x7fa5a8615d20 => txdata 0x7fa5a86157b8 mapping 27-11-2015 18:42:25.688 UTC Verbose sproutletproxy.cpp:1388: scscf-0x7fa5a83ce810 pass initial request Request msg INVITE/cseq=1 (tdta0x7fa5a8615710) to Sproutlet 27-11-2015 18:42:25.688 UTC Info scscfsproutlet.cpp:408: S-CSCF received initial request 27-11-2015 18:42:25.688 UTC Debug pjutils.cpp:2254: Setting session expires value from Min-SE header: 90 27-11-2015 18:42:25.688 UTC Debug scscfsproutlet.cpp:672: Route header references this system 27-11-2015 18:42:25.688 UTC Debug scscfsproutlet.cpp:685: Found ODI token 7VhkxDKy0r 27-11-2015 18:42:25.688 UTC Info scscfsproutlet.cpp:698: Expired ODI token 7VhkxDKy0r so handle as OOTB request 27-11-2015 18:42:25.688 UTC Debug scscfsproutlet.cpp:725: No ODI token, or invalid ODI token, on request, and no P-Charging-Vector header (so can't log ICID for correlation) Under what circumstances will sprout consider the ODI to no longer be valid? I don't think it's actually expired given the time between when it was issued and when it was reported as expired. Thanks, Gavin -- Gavin Murphy VP Engineering, RCS Products +1 (902) 406–8375 x1002 [email protected]<mailto:[email protected]> www.newnet.com<http://www.newnet.com> [cid:[email protected]] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This e-mail is intended only for the named recipient(s) and may contain information that is otherwise privileged, confidential and/or exempt from disclosure under applicable law. No waiver of privilege, confidence, or otherwise is intended by virtue of communication via the internet. Any unauthorized use, dissemination or copying is strictly prohibited. If you have received this e-mail in error, or are not the named as a recipient, please immediately notify the sender and destroy all copies of this e-mail. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
