Dialogic Support Helpweb
Dialogic® DM3 & JCT Media Boards
Incorrect LCD/LED display data on D42NE2PCI
Display Information from previous call being displayed for current caller on D42NEPCI
Symptom:
Display information of the previous caller on a channel/port, is being displayed for the current caller. This problem is seen with PBX integration cards such as the D42NEPCI.
Reason for the problem:
The root of the problem is due to a delayed on the switch side in sending "call information". Here's an illustration of what occurs:
|PBX| |Dialogic-D4NE2PCI|
((( Previous caller on port completed. That call information was x8000 ))))
((( New call arrives from new caller.. with call information x1234 ))))
1:00:00:000 RING >>>>>>
1:00:00:050 ( Detected call )
1:00:01:000 <<<< get display information of call (d42_display) returns x8000
1:00:03:000 RING >>>>>>>
1:00:03:500 Send call information x1234 >>>>
1:00:06:000 RING >>>>>>>>
1:00:07:000 <<< << Answers call and routes caller based on DNIS. In this case it will be routed to x8000 (an incorrect DNIS)
Here are some independent tests one can do to indicate a delay in the Call Information is ocurring:
FIRST, Enable logging. To capture logging information for the D42 card you will need to add this mdoule to your RTFconfig.xml file.
<!-- D42 LIBRARY -->
<Module name="libd42mt.dll" state = "1">
<MLabel name="Internal_Entry" state = "1"/>
<MLabel name="Internal_Exit" state = "1"/>
<MLabel name="Internal_Entry_Args" state = "1"/>
<MLabel name="Internal_Exit_Args" state = "1"/>
<MLabel name="Warning" state = "1"/>
<MLabel name="External_Entry" state = "1"/>
<MLabel name="External_Exit" state = "1"/>
<MLabel name="External_Entry_Args" state = "1"/>
<MLabel name="External_Exit_Args" state = "1"/>
</Module>
TEST#1 : If your application is able to delay getting display/call information in ms time (i.e. ANI Check Time Period). They can try a huge delay time of 2 to 3 seconds. If the issue does not occur with a high delay time
TEST#2 : Attached is an application that gets the call INfo for any given channel. It can run independently of other applications, in an MSDOS window. Basically, run your application as normal (no delay in check for display information). When you have reached the condition of a particular call that recieved incorrect display/call information, query that channel display information.
USAGE: d42display -n<the number of d42 channels in the system>
1-Start system and launch applications (customers application & d42display).
2-Reproduce the issue as you normally would.
3-When you have reproduced the issue, enter the channel number that you are not getting the display information.
The d42display will print out what is in the buffer.
Fix / Solution:
Here are some ideas to solve this problem:
A) Have the application call 'd42_display after the call has been answered OR wait 'x' number of milleseconds before issuing the d42_display function call (basically, delay calling this function call). << This is to give the switch time to send the new call information.
B) See if the switch Engineer can speed up the messaging of when the Call Information is sent.
Workaround:
No specific work arounds besides delaying the retrieval of display/call information.
Product List
- D42NEPCI
Glossary of Acronyms / Terms
Related Documentation
