how did you configure Entity Types for ‘Customer’? can you provide a screen capture of all your settings?
if Putty works perfectly then something is not correct in your Sambapos configuration.
Below is my settings/configuration and it works.
Local Settings:
Department - Take Away
Entity Screens - TAKE AWAY
Additional Information:
Ok my Configuration is pretty much the same:
Device Manager:
SambaPOS Config:
Entity Screen:
Department:
So we are pretty much the exact same configuration… unless you notice something i missed.
Braud rate is different for one.
Also you have no match pattern or entity type?
Yeah added Entity Type, and match pattern to no luck.
Also tried setting it up as Advanced Generic Modem, but that didnt work.
Baud rate 9600 @ putty also does not work… I notice others used baud rate 9600 in device manager and 1200 in putty and SambaPOS which is very odd, but the only combination that seems to work.
PS: Would the SambaPOS team be willing to connect via team-viewer and check the configuration on my SambaPOS server? I understand you cant really test the caller ID remotely, but if you can have a look at my config and tell me if you notice something it would be much appreciated.
Ok. to figure out if the issue is the environment, i installed SambaPOS on a new system now.
Installed Comet Caller ID at COM5, baud 9600.
Putty again at 9600 baud did not give me anything, 1200 got me the correct phone number with 8 extra digits in the beginning. hence the match pattern .{8}(.{10})
I’ve setup everything all over, and im stuck at the same point again.
Fair to say the issue must be in my config…
Here is what i have:
Caller ID Settings:
Entity Type:
any ideas ?
So far i have tried both baud 9600 and 1200 in device manager and SambaPOS & Vice versa.
Installed the Comet caller ID inside Sambapos as:
Comet Caller ID,
Generic modem,
Advanced Generic Modem, tried emre’s tip on setting read timeout as 100, also tried 300, 500 and 1000 as i noticed the caller ID blinks about half a second after the phone starts ringing.
The only possible issue i can imagine now is something to do with my detailed settings in SambaPOS.
Are we talking about this model? This is what SambaPOS supports and should just work with Comet Device.
yes this is it emre. Really sorry to be a pain… im really stuck with it.
does it have an external test application?
i tested with putty and that works.
they dont provide anything more than the driver.
If it is exactly that model there is no need to deal with modem devices. Better setup a default SambaPOS to ensure there is no configuration issue and configure comet device as morshed showed.
You can also try to handle “Device Event Generated” rule and put a show message in it. In all configurations it will trigger when it receives a phone number.
1 Like
Guys, we are really out of time here, customer is starting complaining about we are not able to make it run Samba Pos Caller ID Module.
I tried to investigate a bit also “outside” sambapos. So following my thoughts.
- The modem we use (COMET as suggested in tutorial) seems working fine
- Customer and Line provider are located in Thailand (maybe some different telco standards?)
- Using Putty seems the ID is read from the PORT and sent to the PC
- Putty DO NOT seems to listen and display any RING RING before showing the number.
- The number format seems to be in Single Data Message Format, SDMF. and NOT Multiple
Data Message Format, MDMF, as UK standard. So only date time and calling number is sent over the line.
My wondering is: Do SambaPos module work ok either with SDMF and MDMF formats?
To me, it looks like the DATA is sent ok to the PC, but for some reason (misconfiguration or bug?) SambaPOS does not recognize the input STRING and DO NOT show up the popup.
We posted here many and all possible screenshot for configure the system. All seems fine.
We tried all possible configuration, now please, help us to troubleshoot the issue and maybe we will find another “use case” or tip to add the the public forum to help developers to make sambapos even a better product.
Thanks in advance for any help!
FYI duplicating your posts will just p*ss people off not get more help…
Do you get anything?
I hadn’t used caller ID for a long time but do you get anything?
Try taking out the search side of things and just try and get a notification full stop.
If your not getting a notification I would say it’s config error as com port is fairly basic interface, while the auto searching entity is more involved just a device triggered event should be basic and easy. If you can’t do that your just making finding the problem harder by complicating with all the other parts.
Thanks,
Also duplicating responses p@$ss people off.
As I said, its been months we try to fix the issue and tried all possible configurations. So just saying its a config problem does not give any help.
If someone has some good point to try id welcome.
Did you see my question in the other post you made? Let’s keep the discussion here
Did you try what Emre suggested? Specifically this [quote=“emre, post:32, topic:11361”]
You can also try to handle “Device Event Generated” rule and put a show message in it. In all configurations it will trigger when it receives a phone number.
[/quote]
1 Like
Can you shoot the photo of the caller id box and the model identification label? I’ll contact the manufacturer.
1 Like
Thanks emre, I will tomorrow.
In the meantime I will try again to use an external app in c# to see what I get from com port. And try to check modem drivers.
What I noticed also is that the modem does not respond ( with ok) to the atz commands using putty. But I get the string of the callerid while listening with putty and receiving calls.
Yes we tried to handle “Device Event Generated” with no success, so it seems SambaPos do not receive the Number at all I guess. BUT if we detach the modem and restart SambaPos it says COMXX failed to connect. so means that the connection with the virtual COM is established in somehow I guess.
Alright, we did some proper digging in and found out the exact issue. Still not sure if its a hardware defect or local telephone line rules.
We used the code provided at http://www.crucible-technologies.co.uk/help/comet/cometexample.aspx
and found that every time the output was “ERROR - Not a CID packet!!!”.
So basically if (data[0] == CALLER_ID) is always false. [CALLER_ID = 0x80].
referring to the source code on V3: https://github.com/emreeren/SambaPOS-3/blob/master/Samba.Modules.CidMonitor/CometDevice.cs
Since your if(data[0] == CALLER_ID) has no else, nothing shows up in SambaPOS.
Which makes total sense now.
I understand the current version is not Open Source and i cant modify the code…So i need to figure out a solution.
Ive sent an email to Crucible Technologies regarding this issue, but i do feel that its not a hardware issue but a simple matter of understanding the incoming string from the device.
To get really specific, It seems the SambaPOS code is expecting MDMF format -> Multiple Data Message Format.
However, in Thailand it we only have SDMF -> Simple Data Message Format.
So how do we proceed? Would SambaPOS team be fixing the Source code to fix this or be comfortable sharing the CometDevice.cs and we fix it on our end and send it over to you to compile?
Caller ID Box front:
My Caller ID Box serial Number:
Device Manager settings and Putty output:
