Trying to make a basic (attended) transfer for 2 SM users (71193 and 71191) with Breeze profile assigned, to a CM H.323 station (11072). These users do not have CM profiles.

First call, 71193 calls 71191 through CM:
SIP Station 71193 – [Call ID 1] – Breeze – [Call ID 2] – Communication Manager VDN – [Call ID 3] – Breeze – [Call ID 4] – SIP Station 71191

Second call, 71191 calls 11072:
SIP Station 71191 – [Call ID 5] – Breeze – [Call ID 6] – Communication Manager (H.323 station 11072)

After 11072 answers, 71191 initiate REFER with replaces towards 71193, and Refer-To contains “Replaces = Call ID 5”.
SIP Station 71191 – [Call ID 4, REFER 71193, “Replaces = Call ID 5”] – Breeze – [Call ID 3, REFER 71193, “Replaces = Call ID 5”] – Communication Manager

Refer is received by Communication Manager for Call ID 5, which it’s not aware of, and refer fails.

My understanding is Breeze intentionally keeps Refer-To header unmodified during REFER handling.
What is an idea behind that, and how should such transfer work? Is it supported?

Legend for the attached trace:
10.22.127.201 – 71193
10.22.127.202 – 71191
172.22.240.12 – SM
172.22.240.19 – Breeze
172.22.240.13 – CM

Breeze SDK 3.2.0.1.320111. Snap-in does not use a media server, and in general just allows the call (Call.Allow using Java SDK).

Thank you!

Best regards,
Dmitry Romanov.

Dmitry, this is not a supported call topology. We assume that there's really no such thing as a "SM SIP station". All SIP stations should be CM/SM SIP stations.

If your intent is to simulate external callers and entities such as Experience Portal by using SM SIP stations, that's OK. However, in that case, SIP station 71191 should be a CM station and it would NOT be possible to sequence Breeze on this leg of the call. Breeze would be sequenced but would not invoke any snap-ins, as we can only be sequenced on the trunk side of calls.