Nested Class Summary
public class	TwoStageRingbackSource

Field Summary
private String	dceDn
private long	dnReleaseTimeout
private boolean	dtmfSubscriptionEnabled
private String	twoStageBusyAnnouncementUri
private long	twoStageCdmaConfirmTimeout
private String	twoStageDn
private TwoStageRingbackSource	twoStageRingbackSource
TwoStageRingbackSource	MEDIA_SERVER
TwoStageRingbackSource	NONE
TwoStageRingbackSource	PSTN
private String	twoStageRingbackUri
private String	twoStageRingbackUriPrefix

dceDn represents the RoutableNumber at which the client may request directed call establishment. Constraints:
- see DirectoryNumber constraints
- must be unique within the service invocation numbers of this subscription
- must be unique within all PersonalHandbackPref.handbackDn1/2 and PersonalPickupPref.pickupDn
- may be the same as global service invocation numbers from other subscriptions
- must be unique within the Identity.sdnAddress values
- must be unique within the Endpoint.address values
Default:
- none
Clone:
- yes, verbatim

dnReleaseTimeout represents the time (in seconds) for which the DCE capability should wait for acknowledgment (SIP ACK) from the handset client for the DCE call before releasing the call.
Constraints:
- 0 < dnReleaseTimeout < 20
Default:
- 5
Clone:
- yes, verbatim

dtmfSubscriptionEnabled flag indicates (TRUE) that the DCE capability should subscribe (via SIP SUBSCRIBE/NOTIFY) for DTMF notifications from the gateway in order to receive the out-pulsed digits from the client for the second phase of dialing. Alternatively the flag indicates (FALSE) that the DTMF digits will be delivered from the gateway via INFO messages (no-registration/solicitation required). NOTE: Currently only AudioCodes media gateway supports the INFO message delivery mechanism. Both CCM and AudioCodes support SUBSRIBE/NOTIFY however, the CISCO call manager currently has a bug through which they omit a mandatory header in the notify which causes the Radivision SIP stack to reject the message.
Constraints:
- true | false
Default:
- false
Clone:
- yes, verbatim

twoStageBusyAnnouncementUri represents the Uri of the announcement to be played when the destination number is busy.
Constraints:
- must be a valid URI or null
Defaults:
- none
Clone:
- yes, verbatim

twoStageCdmaConfirmTimeout represents the time (in milliseconds) to wait before creating confirmation call back to client to indicate that it may proceed with the second stage of two stage dialing (out pulse digits). NOTE: the DCE/Two Stage capability marks the call parameters such that the client can identify that the call is a confirmation call.
Constraints:
- 100 <= twoStageCdmaConfirmTimeout <= 20000
Default:
- 100
Clone:
- yes, verbatim

the twoStageDn is the DN for which the two stage dialing capability is associated. Calls to the twoStageDn are treated with the two stage origination logic
Constraints:
- see DirectoryNumber constraints
- must be unique within the service invocation numbers of this subscription
- must be unique within all personal service invocation numbers (PersonalHandbackPref.handbackDn1/2 and PersonalPickupPref.pickupDn)
- may be the same as global service invocation numbers from other subscriptions
- must be unique within the Identity.sdnAddress values
- must be unique within the Endpoint.address values
Default:
- none
Clone:
- yes, verbatim

twoStageRingbackSource is an enum indicating how ringback should be
provided during two stage dialing.
Constraints:
- NONE: no ringback is provided (currently not deployable)
- MEDIA_SERVER: ringback is provided by a media server. NOTE: this option
requires a media server ringback URI to be provided
- PSTN: ringback is provided by the PSTN by looping a call through the
PBX and back to a CSN invocation number. CSN will provide 180 on the
call which in turn will cause the PSTN to generate ringback to the
caller. NOTE: this option requires a ringback DN which is a DID number
on the PBX that is routed to the CSN as a service invocation number for
180. The ringbackDN is provisioned as the user part of the twoStageRingbackUri.
This option may also require a prefix in order to force the PBX to
route the call out to the PSTN rather than terminating it directly back
to the CSN invocation number.
Default:
- NONE
Clone:
- yes, verbatim

twoStageRingbackUri is the URI two which the CSN propagates the call in
order to have ringback generated to the caller. If the
twoStageRingbackSource is PSTN the user part of the URI (which is a DN,
a DID number that will route back to the CSN) is treated as an
invocation number by the CSN in order to provide the 180 RINGING on the
looped call.
Constraints:
- must be a valid URI if twoStageRingbackSource != NONE
Default:
- none
Clone:
- yes, verbatim

twoStageRingbackUriPrefix is an optional four digit prefix which may be
added to the twoStageRingbackUri user part by the CSN when looping the call in
the PSTN via a PBX. The prefix is required in some deployments in order
to force the PBX to route the call out the PSTN rather than terminate it
directly to the associated extension (CSN in this case). The prefix is
stripped by the PBX and the looped leg appears to the CSN without the
prefix as a call to an invocation number. The CSN requires the call to be
propagated through the PSTN because it needs to leverage the PSTN's
ringback facilities.
Constraints:
- may be null
- digits representing an integer 0 <= twoStageRingbackUriPrefix <= 9999
Default:
- none
Clone:
- yes, verbatim