Need some guidance on setting up Caller ID Feature

I decided to give the caller ID feature a go and need some guidance:

So I bought this modem:

I then enabled the Caller ID Module from Samba Market.

Is there any other configuration that needs to be done within Samba to get the modem communicating to the software?

Go to Local Settings > Devices set CallerID Device asGeneric Modem, click Settings and choose Serial Port that your modem connected to.

1 Like


  1. Make sure the phone line is active with caller ID (if not you need to contact land line company to activate it i.e. BT)

  2. The USB Modem must support Voice for caller ID to work. Looking at the picture of the modem it looks similar to the low cost version I had purchased initially via e-bay which did not work, although they advertised it with support for caller id. I had to return it for refund.

Version purchased from eBay NOT supporting caller ID-

I then purchased alternative version from Amazon. which worked straight out of the box.

You can test the modem using Putty first:

Its straight forward to configure caller id. install the USB modem driver then configure/ select the modem in sambapos

Configure the modem in Sambapos.
Select the Generic modem for the USB modem and PORT configured on (i.e COM 1 or COM 2 etc)


Thanks guys for pointing me in the right direction @Morshed1 @emre

I have phoned BT and activated the Caller ID feature and ordered the recommended kit from Amazon. Thanks again @morshed1.

So it’s a waiting game for now.

@Emre As this is local based, client PC’s would not benefit from this feature?

@Isaac I couldn’t understand how you are planning to use it on client PC’s. Can you give an example?


The usb modem will be installed on the main SERVER which is my Till in the shop, this is where we take phone orders and will benefit from this feature greatly.

I also have a OFFICE PC (Which is my where I spend most my time on Samba Forums :slight_smile: ) which is connected to the SERVER and I also take phone orders from this terminal.

I was just curious to know if I can use the caller ID feature on both terminals without having to install separate Modems but I’m guessing this is not possible?

Unless we have something like the messaging server which relays any incoming caller ids to all terminals… So whichever terminal clicks on the pop up 1st can take the order.

In V2 we could send messages between terminals using rules & actions. I haven’t tried with V4.
@emre is this still possible ?

Yes it is still possible but since Caller-ID module takes care of the workflow I’m not sure how we’ll be able to handle this without it. Displaying popups on multiple terminals is simple but closing correct popup remotely is something I never thought before.

Assign the popups with a UID. When a user taps the popup it broadcasts a close popup command with that UID and the other terminals then close the popup.
Having a “caller id server” would make some setups easier due to phone line locations.

OK I’ll think about it.

I have received my new modem as recommended by @Morshed1

And BT have activated Caller ID feature.

I have installed the Windows 7 64 Bit Driver for the modem and managed to succesfully query the device which is set at COM3.

I then added Generic Modem and set it to COM3 in Local Settings

Restarted the application and get a error The port COM3 does not exist message on the popup.

Any Ideas?

Ensure you don’t have any other programs querying the modem otherwise Invalid Port error message will appear on the popup. (265.6 KB)

Before testing on Sambapos. carry out test using putty…
Select COM3, serial and then open. as per below.

Make a phone call to the line and putty should display the phone number

1 Like


I done as suggested and typed;


The Result was: OK

But when I ring nothing happens in Putty Command Prompt.

Also when I add COM3 in Caller ID Devices, I no longer get a error as long as im not using the port. However when I ring nothing happens in Samba?

I’m missing something here.

@Emre does caller Id feature support 64bit?

@Isaac Is the modem connected to master phone socket? if not can you try connecting to the master phone socket. if you have ADSL then can you use filter?

You can also run another diagnostic tool which I found useful

Run RealTerm so that the raw hex data can be captured from serial modem when call is made. Make sure that RealTerm is properly configured and that the “Change” button has been clicked both after selecting Hex+ASCII in the Display As parameter under the Display tab and after setting up the correct Serial line connection parameters under the Port tab.

  1. Install Realtime (935.3 KB)

selecting Hex+ASCII in the Display

Select the Modem port for your configured modem.

Make a phone call.

if there is communication then realtern will capture the data as per below example

I’m not getting any results when ringing, blank screen.

Yes its on a Master Socket with ADSL filter.

can dial below number from your phone to check if it is active. Below only applies to BT line.

Is the Caller ID facility switched on?
Check the facility is switched on by entering the code * # 234 # If the facility is active you will get the massage Caller identity will be displayed. If the facility is not active then activate it using the code * 234 #.

Yes it is active, I have just checked now.

For some reason I’m not convinced this modem has caller id support?

When you query the modem in Properties I see this:


Do you get this also?

Here is the windows log:

AT+GMM - +GMM: V90
AT+FCLASS=? - 0,1,1.0,8
AT+GCI? - +GCI: B4
AT+GCI=? - +GCI: (00,01,02,03,04,05,06,07,08,09,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,17,18,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27,28,29,2A,2B,2C,2D,2E,2F,31,32,33,34,35,36,37,38,39,3A,3B,3C,3D,3E,40,41,42,43,44,45,46,47,48,49,4A,4B,4C,4D,4E,4F,50,51,52,53,54,55,56,57,58,59,5A,5B,5C,5D,5E,5F,60,61,62,63,64,65,66,67,68,69,6A,6B,6C,6D,6E,6F,70,71,72,73,74,75,76,77,78,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8B,8C,8D,8E,8F,90,91,92,93,94,95,96,97,98,99,9A,9B,9C,9D,9E,9F,A0,A1,A3,A4,A5,A6,A8,A9,AA,AB,AC,AD,AE,AF,B0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF,C0,C1,C2,C3,C4,C5,C7,C8,C9,CA,D1,D2,D3,D4,D5,D6,D7,D8,D9,DD,DE,DF,E0,E1,E3,E4,E5,E6,E7,E8,EB,EC,ED,EE,EF,F0,F1,F2,F3,F4,F5,F7,F8,F9,FA,FB,FC,FE)
ATI3 - CX93001-EIS_V0.2002-V92
ATI5 - B4