There are tons of posts on this if you use search. Your best bet while you wait for an answer here is to use search. To get a better response here you need to provide more detailed screenshots of the setup.
I personally have not used caller ID so other than using search I won’t be able to help much.
I’ve tried using CTI Comet USB Caller ID with the same settings but again it results in no popup.
@Jesse I’ve filled all this in, but it makes no difference. If I use the test function, it prepopulates the data in the right area anyway without any input.
I don’t know about caller ids but generally serial to usb adapters can be a right pain in my experience in print shop using older serial fed vinyl cutters…
TBH could you not look at a different device? The USB caller device I bought a while back was only like £15 and wored straight away.
I did have an ARTECH USB Caller ID unit, but SambaPOS doesn’t work well with that unit, even following the workaround technique I found on this forum. (I.e. running the CHC program and emulating a port).
I then bought the recommended TRIXES unit from the original tutorial, and that didn’t even have Caller ID built in much to my frustration! It also had some terrible reviews with unreliability.
The CTI unit (supposed to be one of the best units out there, albeit in serial form) is actually working perfectly, as I’ve mentioned Putty is picking up the number no problem. However I can’t see why SambaPOS isn’t picking up the data?
Yes the baud rate is definitely correct as that’s what Crucible (the manufacturer) says the device operates on. If you use any other baud rate, you get a garbled output.
Also, I always restart SambaPOS after using Putty, as you can’t obviously simultaneously connect both applications. You just get the Access denied to COM5 in Samba if Putty is open.
Ok I’ve finally managed to find a post similar to the problem, and it seems all it boils down to is the match pattern. So I’ve tried putting in the suggested match pattern of [^0-9]*?([0-9]+)
This finally ellicits a response from an incoming call! But not the one I want as you can see in the following screenshot:
And just to remind you of the Putty output:
So as you can see, Samba is pulling the matching numbers… but in separate popups, including the initial date stamp.
So, my question is, any ideas on the match pattern I should use to pluck out the number?
I hate to be a pest, but as everything else is working perfectly, it just seems a shame I can’t seem to solve this problem? Perhaps I can fumble my way through solving it, but can anyone point me towards the syntax that can be used in Match Pattern field? My business is completely dependent on Caller ID working, and it seems that everything is in place for it to work.
Ok, I think we’re making progress, but not there yet! The problem with the first pattern is that the character before OFF-LINE (In this case a U as per the Putty screenshot) is always random.
The second pattern with new line as the termination string brings up the following:
This is better than before as it’s now grouping the numbers as opposed to separate pop-ups. However because the termination string is new line, I’m guessing it doesn’t pick up the second line where the telephone number is?
Could anyone give me an insight into the syntax used for the Match Pattern field? I would like to try and solve this somehow, it’s the only thing holding back the system from being fully efficient for us.