I have a case open with cisco for this problem for 5 months. It took forever
to convince him that this is not the right implementation. It should send an
INVITE from the REFER message. But he still didn't care to open a bug case
with design engineer...
how about cisco gw? it looks to me that it can't handle refer correctly
either. when it receives a refer where refer-to has some foreign
domain, it still starts to go though its destination pattern list where
only the user part is compared.
-- juha