>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 <anthonyn...@gmail.com> wrote:
> 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
> Invite request is matched with iFC again from the beginning instead just
> match with the rest iFCs. So it fail to send to the user.
> Is it a bug?
Clearwater mailing list