User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 387
Dialogic Corporation
Section 1.46, “Dialogic
®
DI0408LSAR2 Board Support for Host Systems with Multiple
NICs”, on page 159 of this Release Update.
Update for early media
Because of a new feature in the Service Update, information about early media
should be added to Chapter 3, IP Call Scenarios. For information about this feature,
see Section 1.52, “Early Media”, on page 213 of this Release Update.
Update for SIP call transfer
Because of a new feature in the Service Update, information about SIP call transfer
should be added to Chapter 4, IP-Specific Operations. For information about this
feature, see Section 1.51, “SIP Call Transfer”, on page 182 of this Release Update.
Update for SIP message header fields (PTR# 35268)
The ability to set and retrieve SIP message header fields is not supported in Dialogic
®
System Release 6.0 PCI for Windows
®
. The information in Section 4.5, Setting and
Retrieving SIP Message Information Fields, and all of its subsections (pages 59-
62) should be ignored.
The version of the IP_VIRTBOARD data structure that is implemented in Dialogic
®
System Release 6.0 PCI for Windows
®
(structure version 0x100) does not include the
sip_msginfo_mask field. The line of the typedef on page 184 that defines this field and
the description of the field on page 185 should both be ignored, and applications
should not attempt to set the value of this undefined field.
Update for adjusting the Windows
®
TimedWait state
The following information on adjusting the Windows
®
TimedWait state should be
added to the guide:
Running ONLY call control on 10 or more timeslots may cause the error:
IPEC_Q931Cause34NoCircuitChannelAvailable
Each IP call uses a Windows
®
socket that binds the call to a unique TCP address/port. The
Dialogic
®
Global Call stack uses these ports starting at port address 20000. When an IP call is
completed, the socket associated with that call closes and then enters into a TimedWait state,
during which the socket.s associated address/port is not available for use until the time expires. The
default time for this TimedWait state is 240 seconds.
If an application is stopped and then immediately restarted before the TimedWait state expires, as
may be the case during application development and debugging, calls may fail. Reducing the
duration of the TimedWait state can alleviate this problem.
Another problem that may result from the TimedWait state duration is when a server experiences a
high call rate. Even though the maximum number of TCP connections that can be opened
simultaneously is large, in a high call rate scenario the potential exists for hundreds of TCP sockets
to be in the TimedWait state causing the system to reach the maximum number of TCP
connections. Again, reducing the duration of the TimedWait state can alleviate this problem.
Changing the TimedWait state to a value less than the 240 second default requires a change to the
Windows
®
registry:
System Key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
(PTR# 32165)