Forked Dialog TO tag issue

[GuyPothiboon4406]

Hi,

InterOp testcase 19 and 20 requires "The TO tag in the 200 OK is different than the TO tag in 18x"

See attached captures that the TO tag are the same.

Is this "AS_CLI/Interfaces/Sip> set accessForkingSupport
multipleDialogsWithErrorCorrection" enabled on server?

[skumar1]

Can you make sure that the call is forwared to Broadworks User A's Voice message No Answer Greeting ?

[GuyPothiboon4406]

Yes I have setup voicemail greeting and the call is CFNA to voicemail

In capture "FAIL T019 Early to Confirmed Dialog Forking.pcapng" 

 - DUT 2294 calls UserA 2292

 - DUT receives remote ringback 183

 - then the call is CFNA to Voice Portal as shown in P-Asserted-Identity in 200OK

The TO tag  in 200 OK and 183 are the same

In capture "FAIL T020 Early to Early to Confirmed Dialog Forking.pcapng"

 - DUT 2294 calls UserA 2292

 - DUT receives remote ringback 183

 - call is CFNA to UserB 2291 and DUT receives ringing 180

 - UserB answers and DUT receives 200OK

The TO tag in 183, 180 and 200OK are all the same 

[GuyPothiboon4406]

Hi skumar1,

Any update on this issue?  Functional wise DUT is working as expected.  The issue is only the test plan mentions the TO tag must be different

[skumar1]

We have found an issue in SBC handling the tag value in the "TO header" and working on it to fix the issue.
We do not have an estimate at this time. We will respond as soon as we hear from the team looking into the issue.