We are building a dialer interface to our client app that calls our customers and then allows those customers to connect and autodial to their clients. We are using these api commands to do this: originate [origination_caller_id_name ='[caller_id_name]',origination_caller_id_number=[caller_id_number],user_name=[a gent_id],park_after_bridge=true]sofia/gateway/vitelity-outbound/1[number_to_call ] &park uuid_audio [uuid1] start write level 0 originate [origination_caller_id_nam e='[caller_id_name]',origination_caller_id_number=[caller_id_number],user_name=[ agent_id]]sofia/gateway/vitelity-outbound/1[number_to_call] &park uuid_bridge [uuid1] [uuid2] When the second call (leg-b) hangs up, we do not get a disconnect event (we believe this is due to the uuid_audio start). We need that disconnect in order to launch the next call. We are sending the uuid_audio [uuid1] start command because we do not have any media audio when we do the bridge. We tried also sending a uuid_media off command but that has the consequence of dropping the first leg/call when the second call disconnects (does not honor the park_after_bridge). This only happens when bridging two external calls. If one of the legs is an internal extension, then we don't need the uuid_audio start or the uuid_media off and everything works fine. Is there another way of doing this or a way for uuid_media off to honor the park_after_bridge condition? Could we use fifo's instead of the park_after_bridge? btw: we have also tried this using Flowroute as the gateway instead of Vitelity. Thanks, Lynn -- -- Lynn Nielson Green Seed Technologies / The RedX