Re: [Project Clearwater] Is it a bug that Clearwater invalidate the ODI once it receives 200OK response?

2018-03-05 Thread Anthony Lee
f Of *Anthony Lee > *Sent:* 24 February 2018 01:53 > *To:* clearwater@lists.projectclearwater.org > *Subject:* Re: [Project Clearwater] Is it a bug that Clearwater > invalidate the ODI once it receives 200OK response? > > > > From TS 124.229 V12.6.0, the spec doesn't say

Re: [Project Clearwater] Is it a bug that Clearwater invalidate the ODI once it receives 200OK response?

2018-02-28 Thread Richard Whitehouse (projectclearwater.org)
Of Anthony Lee Sent: 24 February 2018 01:53 To: clearwater@lists.projectclearwater.org Subject: Re: [Project Clearwater] Is it a bug that Clearwater invalidate the ODI once it receives 200OK response? From TS 124.229 V12.6.0, the spec doesn't say anything about the 200OK response from the re

Re: [Project Clearwater] Is it a bug that Clearwater invalidate the ODI once it receives 200OK response?

2018-02-23 Thread Anthony Lee
>From TS 124.229 V12.6.0, the spec doesn't say anything about the 200OK response from the request. It only talks about the subsequent request should be co-related with the previous request by using ODI in route header. To me it looks like a bug. On Fri, Feb 23, 2018 at 2:21 PM, Anthony Lee wrote:

[Project Clearwater] Is it a bug that Clearwater invalidate the ODI once it receives 200OK response?

2018-02-23 Thread Anthony Lee
In my case, there is a application service in terminating side doing message Store-And-Forward. So when the service receives an Invite it replies 200OK response immiediately and then it create a new Invite to the user. Since scscf invalidated the AS chain when it receives 200OK response the Invit