Using Third Party IP Stacks

Outbound Call

The following section uses SIP to demonstrate the interaction between the third party stack in the application and Bfv for negotiating RTP and T.38 for an outbound call.

Systems that will perform RTP can generate the CNG tone and avoid setting the RTP on the Bfv. If this is the case applications can skip calling BfvCallSwitchConnectIP(Listen RTP local IP/Port), BfvCallSWConnectIP(FullDuplex RTP), BfvLineCallProgressEnable() Generates CNG, and BfvLineCallProgressDisable.

If RTP is also going to be done with the Bfv, make sure the port used in BfvCallSWConnectIP is unused.

If both RTP and T.38 are done with Bfv, some ICMP errors may appear as the port is switched from RTP to T.38. To avoid the ICMP errors use unique ports for RTP and T.38.

Figure 24. Outbound SIP Sequence

November 2009

263

Page 263
Image 263
Dialogic 6.2 manual Outbound Call, November 263