Author |
|
AllanMar Groupie
Joined: April 02 2007
Online Status: Offline Posts: 45
|
Posted: May 22 2009 at 20:45 | IP Logged
|
|
|
The caller ID plugin will not work for me. I believe the issue is because of my Canadian PH company. The Caller ID is received on the serial port as:
RING
DATE=0522
TIME=2056
NAME=<caller NAME>
DDN=<7 or 9 Digit number>
I suspect the DDN= rather than NMBR= is causing the problem. Is the source for the plugin available? Otherwise would it be possible for you to add support for this format? (should be trivial). Or perhaps this is supported and i've got some other issue....
Thanks,
-Allan
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: May 22 2009 at 21:32 | IP Logged
|
|
|
I think the only solution would be to use the CID macro and change the strings it looks for.
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: May 25 2009 at 17:15 | IP Logged
|
|
|
Allan,
I have updated the PH_CID plugin based upon your settings above. Use Format=4 in the INI file. If that doesnt work, I have also included the source code for the CID plugin so you can modify as needed.
You can get the ph_cid plugin version 2.0 off of the download page.
Let me know how it goes.
Dave.
|
Back to Top |
|
|
krommetje Super User
Joined: December 29 2004 Location: Netherlands
Online Status: Offline Posts: 695
|
Posted: December 18 2010 at 10:46 | IP Logged
|
|
|
Hey Guys,
I solved my callerID problem by using callclerk.
A package which does the decoding by itself and runs the socket commandline util and sends the number to PH.
I tested it by sending a testnumber to PH as a usermessage and that worked...
Now I send it to PH as a global which fires a trigger and runs a macro and stores all sent numbers in a History (11 numbers).
Peter
Edited by krommetje - December 18 2010 at 11:23
|
Back to Top |
|
|