The `` verb connects an existing call to another phone number. `` will end this new call if: the called number does not answer, the number does not exist, or SignalWire receives a busy signal. You can use the `` verb with the following nouns: | Noun | | | --- | --- | | [``](/content/docs/compatibility-api/cxml/reference/voice/conference/index.html) | A conference call between two or more callers. | | [``](/content/docs/compatibility-api/cxml/reference/voice/number/index.html) | A phone number with additional attributes. | | [``](/content/docs/compatibility-api/cxml/reference/voice/sip/index.html) | A SIP endpoint. | | [``](/content/docs/compatibility-api/cxml/reference/voice/verto/index.html) | A Verto client. | | [``](/content/docs/compatibility-api/cxml/reference/voice/queue/index.html) | A line for callers to wait in. The current call will be connected to the call at the front of the queue. | ## Verb attributes ###### action string The `action` attribute takes in an absolute URL. SignalWire will make a `GET` or `POST` request to this URL after the dialed call ends. If no `action` is provided, SignalWire will continue to the next verb in the document. SignalWire will end the call if there are no more verbs following the `` verb in the document. See [below](/content/docs/compatibility-api/cxml/reference/voice/dial#dial_action/index.html) for request parameters. ###### answerOnBridge booleanDefaults to false If set to true, the inbound call will ring until the number that was dialed answers the call. If the inbound call is a SIP call, SignalWire will send a 180 or 183 to your SIP server as soon as it connects to SignalWire. When the `` call is connected, a 200 will be sent. ###### callerId string The inbound caller’s phone number, which is displayed to the number that was dialed. The caller ID must be a valid E.164 number. Note that the number specified here must either be verified or purchased in the SignalWire Dashboard. ###### callerName string The caller name displayed for Sip calls. This should be an alphanumeric string. Limit is 70 characters. ###### hangupOnStar booleanDefaults to false The initiator of the call can hangup on the dialed number by using the `*` key. ###### method stringDefaults to POST The `method` attribute specifies whether the request to action is a `GET` or a `POST`. Valid values are `GET` or `POST`. ###### record stringDefaults to do-not-record The `record` attribute allows the ability to record both legs of a call. Recordings are available as **mono-channel** or **dual-channel**. See [below](/content/docs/compatibility-api/cxml/reference/voice/dial#record_channels/index.html) for a detailed explanation of these channels. ###### recordingStatusCallback string The `recordingStatusCallback` attribute takes in an absolute or relative URL. SignalWire will make a `GET` or `POST` request to this URL when recording is available. See [below](/content/docs/compatibility-api/cxml/reference/voice/dial#dial_recordingStatusCallback/index.html) for request parameters. ###### recordingStatusCallbackEvent stringDefaults to completed The different recording statuses. Possible values are `completed`, `in-progress`, and `absent`. To specify multiple events, separate with a space. ###### recordingStatusCallbackMethod stringDefaults to POST Whether the request to `recordingStatusCallback` URL is a `GET` or a `POST`. ###### recordingStorageUrl string The `recordingStorageUrl` attribute accepts an absolute URL as the destination to send a recording to, if you prefer to host your own recordings and bypass SignalWire storage. The recording files are in `.wav` format. ###### recordingStorageUrlMethod stringDefaults to POST Specifies which HTTP verb to use when sending the recording to the `recordingStorageUrl`. Available values are: **POST** and **PUT**. ###### recordingTrack stringDefaults to both Specifies whether to record the `inbound` audio to SignalWire from the called party or the `outbound` audio from SignalWire to the called party or `both` the inbound and outbound audio. ###### ringTone string The ability to change the ringback tone played to the caller when dialing a number. Default value is the ringback tone from the carrier. Available values are the following ISO 3166-1 alpha-2 country codes: **at**, **au**, **bg**, **br**, **be**, **ch**, **cl**, **cn**, **cz**, **de**, **dk**, **ee**, **es**, **fi**, **fr**, **gr**, **hu**, **il**, **in**, **it**, **lt**, **jp**, **mx**, **my**, **nl**, **no**, **nz**, **ph**, **pl**, **pt**, **ru**, **se**, **sg**, **th**, **uk**, **us**, **us-old**, **tw**, **ve**, **za**. ###### timeLimit integerDefaults to 14400 Maximum duration, in seconds, for a ``. Default value is 4 hours (14400 seconds). ###### timeout integerDefaults to 30 The time, in seconds, that SignalWire will wait for a call to be answered before setting the status of the call to `no-answer`. Minimum value is 5 seconds and maximum value is 600 seconds. For some call flows, there may be a 5-second buffer added to the timeout value you provide. ###### trim stringDefaults to do-not-trim Whether silence in the beginning and end of recordings is removed. Use `trim-silence` to achieve this behavior. #### Request parameters for the `action` URL You can expect several parameters to be present in the request associated to the `action` URL. First, you have the [Standard Request Parameters](/content/docs/compatibility-api/cxml/reference/voice#request-parameters/index.html). Then, you also have the following specific parameters: ###### DialCallDuration integer The duration, in seconds, of the dialed call. ###### DialCallSid string The unique identifier of the new call leg. ###### DialCallStatus string The status of the dialed call attempt. See [below](/content/docs/compatibility-api/cxml/reference/voice/dial#action_dialCallStatus/index.html) for status values. ###### RecordingUrl string The URL of the recorded audio file. This parameter is only present if `record` is set on a ``. #### Values for `DialCallStatus` parameter The `DialCallStatus` parameter of the `action` attribute can be one of the following values: | Value | Description | | --- | --- | | `completed` | The number that was dialed answered the call and was successfully connected to the caller. | | `answered` | When calling to a conference, the number that was dialed answered the call and was successfully connected to the caller. | | `busy` | SignalWire received a busy signal when connecting to the dialed number. | | `no-answer` | The number that was dialed did not answer the call in time. | | `failed` | SignalWire was unable to connect to the dialed number. This usually occurs when the dialed number does not exist. | | `canceled` | The call was canceled through a REST API before it was answered. | #### Values for `record` parameter The `record` attribute allows for recordings in **mono-channel** or **dual-channel**: - **mono-channel**: both legs of a call are combined into one channel in one recording file - _record-from-answer_: starts the recording when the call is answered - _record-from-ringing_: starts the recording when ringing begins - **dual-channel**: both legs of a call use separate channels in one recording file - _record-from-answer-dual_: starts the recording when the call is answered - _record-from-ringing-dual_: starts the recording when ringing begins #### Request parameters for `recordingStatusCallback` ## Examples ### A simple dial ```xml 123-456-7890 ``` If the dialed number answers the call, the two parties can talk to each other until one of them hangs up the phone. ### Dial a number from a SignalWire client ```xml +18004445566 ``` In order to dial from a SignalWire client, you need to make sure you are inputting a valid phone number. If the number in the `callerID` is not valid, the call will fail. ### Mono-channel recording ```xml +10123456789 ``` With mono-channel recording, each participant in the call will be recorded on the same channel. The recording will then be stored in a single recording file. Since we have set `record` to **record-from-ringing**, the recording will begin when the phone starts to ring. ### Dual-channel recording for a conference call ```xml teamcall ``` This example connects the caller to the conference call, **teamcall**. With dual-channel recording, each participant in the call will be recorded in a separate channel. The recording will then be stored in a single recording file. Since we have set `record` to **record-from-ringing-dual**, the recording will begin when the phone starts to ring.