Enabling the R2 Protocol

Outbound Call Setup

An outbound call request sequence that results in call acceptance by the remote side is illustrated in Figure 53. The Host application issues the module an L4L3mCALL_REQUEST message with the following R2 payload entries:

l43msg.msgtype = L4L3mCALL_REQUEST; l43msg.lapdid = 0x1; l43msg.data.call_req_data.bchannel = 1;

l43msg.data.call_req_data.called_party.num_digits

l43msg.data.call_req_data.called_party.dnis_category (set to an IISDN_R2MF_SIGNAL_CODES value)

l43msg.data.call_req_data.called_party.digits (ASCII string)

l43msg.data.call_req_data.calling_party.num_digits

l43msg.data.call_req_data.calling_party.ani_category (set to an IISDN_R2MF_SIGNAL_CODES value)

l43msg.data.call_req_data.calling_party.presentation_ind (set to an IISDN_R2_ANI_XXXX value)

l43msg.data.call_req_data.calling_party.digits (ASCII string)

l43msg.data.call_req_data.call_type (set to IISDNcalltypR2_GND for a terrestrial circuit or IISDNcalltypR2_SAT for a satellite circuit)

November 2009

356

Page 356
Image 356
Dialogic 6.2 manual Outbound Call Setup, November 356