Dialogic Support Helpweb
Dialogic® DM3 & JCT Media Boards
How Do I Define The Wink Length In Robbed-Bit PDK Global Call Protocols?
Problem Description:It is unclear how to define the wink length of a CAS protocol. The .cdp file (e.g. pdk_us_mf_io.cdp) does not define the parameter list for the structure CAS_SIGNAL_PULSE_t, which is used to define both transmit and receive winks.
/* Wink receives signaling pulse (outbound) */
All CAS_SIGNAL_PULSE_t CAS_WINKRCV = 00xx,11xx,50,50,0,80,200,250,300
/* Wink generates signaling pulse (inbound) */
All CAS_SIGNAL_PULSE_t CAS_WINKXMT = 00xx,11xx,50,50,0,80,200,250,300
This information is not available in the Global Call CDP reference. It is mentioned in the Global Call Protocol Writer's Guide (p/n 05-1235-001-03).
Solution Summary/Technical Discussion:
From the Global Call Protocol Writer's Guide, the components of CAS_SIGNAL_PULSE_t are defined as:
OffPulseCode, OnPulseCode, PrePulseInterval, PostPulseInterval, PrePulseIntervalNominal, PostPulseIntervalNominal, PulseIntervalMin, PulseIntervalNominal, PulseIntervalMax
When specifying the wink length, consider the last three elements of the structure:
PulseIntervalMin (ms)
PulseIntervalNominal (ms)
PulseIntervalMax (ms)
The wink length is defined as PulseIntervalNominal with an acceptable range between PulseIntervalMin and PulseIntervalMax. To define a 150 ms wink ± 25 ms, the last three elements would be 125, 150, 175.
e.g.
All CAS_SIGNAL_PULSE_t CAS_WINKRCV = 00xx,11xx,50,50,0,80,125,150,175
All CAS_SIGNAL_PULSE_t CAS_WINKXMT = 00xx,11xx,50,50,0,80,125,150,175
Attachments:
N/A
