<snip>

However, when one of the called parties answers then the whole "enterprise" has completed its mission (sorry). If you need the called party to do some sort of acknowledgement (i.e. press a key) then you'll need to employ group_confirm_key/group_confirm_file.

</snip>

E.g. if you are calling a mobile, you should always do group confirm: otherwise if the phone is off / no reception, voicemail on the mobile picks up - doh!

An enterprise that bridges to a cellphone and to a SIP phone could look something like this:

<originate_timeout=25>{ignore_early_media=true,group_confirm_file=ivr/ivr-accept_reject_voicemail.wav,group_confirm_key=1}sofia/gateway/flowroute/12223334444:_:user/1000

The < is for everything, the { is only for that "thread" of the enterprise originate - the group confirm isn't used for the user/ bridge.

You can also do a leg_delay_start=5 on the mobile section so that only if the sip phone isn't picked up within the first e.g. 5 seconds then it rings the mobile (beware of PDD though).

If the other legs error out, then the leg_delay_start will be skipped.

-Avi