Jabber Called party sends REFER instead of 200 OK

[bdry]

Hi,

I have a basic point to point call flow between two Jabber web SDK clients or between a Jabber WebSDK client and a Jabber for Windows client.  In both cases, the Called party responds to incoming calls with a series of SIP REFER messages instead of 200 OK's example call flow is below.

Any ideas why?

[shinajcm]

Even i have the same issue.

Attached the screen shot.

Customer says while on one call another call came in and Finesse frozen.

[tabennett1978]

Hi,

Was there ever a reason discovered for this? Is this normal behaviour on a simple point to point call? Not what I expected.

Thanks,

Tom.

[R0g22]

What does the REFER look like as in the actual message ?

[tabennett1978]

Hi Nipun,
Thanks for the feedback\question, I’ve been chatting to a colleague and looking through some RFCs and it appears that after the 200 OK message the call is setup successfully but the REFER are used for other in call features\functions\data exchanges and are normal.
Thanks,
Tom.

[R0g22]

Yeah I mean REFER is not illegal in a SIP call. You would see them all the time with the more common usage being during a transfer.