From: David LaRue
I have some working code that may not be reliable (as per a design/code review) and I could use a second opinion. Right now, I depend on the CallID information to be present (via d42_gtcallid()) after I receive ring notification (via TDX_CST with DE_RINGS).
It has been suggested that TD42_ASYNCCALLID is a better message to wait for. I kind of agree except that the documentation and code in SR 5.1.1 don't agree. I've not been able to activate this message by setting D4CH_ASYNCCALLID with d42_setparm since D4CH_ASYNCCALLID is not defined.
Our concern is that a PBX configured to send CallID Information later than after the first ring will cause us a problem. Presumably d42_gtcallid() would fail and I would have no idea when to check again. I could check every so often until a TDX_CST/DE_RNGOFF occurs, but that doesn't seem appropriate.
For each device detected, we are setting
sr_enbhdr (...EV_ANYEVT...
d42_setparm (...D4CH_CHANNELSTATUS...
d42_setparm (...D4CH_ASYNCCHSTATUS...
What is the proper way to watch for CallID information present?
-
To reply: mailto:General.28032@pysdiscussext.py.intel.com
To start a new topic: mailto:General@pysdiscussext.py.intel.com
To login: http://members.support.dialogic.com/wbproxy/wbpx.dll/~general
Received on Thu Apr 15 13:59:12 2004
This archive was generated by hypermail 2.1.8 : Sat Jul 16 2005 - 03:48:32 EDT