# COMET USB Caller ID Setup Issue **URL:** \ **Category:** V5 Question\ **Created:** [June 21, 2016, 4:01am UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361 "2016-06-21T04:01:18Z")\ **Posts on this page:** 18\ **Page:** 4
**Author:** ![digithai](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@digithai](https://forum.sambapos.com/u/digithai)\ **Post date:** [October 31, 2016, 1:04pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/61 "2016-10-31T13:04:37Z")
I totally understand you emre, it’s NOT EASY to develop a patch while not able to test or reproduce the defect. You don’t have to trust me or either putty log, you should trust the Telco STANDARDS for CALLER ID. I rewrite below for your convenience the 2 TYPES of packed DATA available WORLDWIDE and **their structure**. If you implement the SMDF you CANNOT mistake, is standard **From Wikipedia** > There are two types of caller ID, number only and name+number. Number-only caller ID is called Single Data Message Format (SDMF), which provides the caller’s telephone number, the date and time of the call. Name+number caller ID is called Multiple Data Message Format (MDMF), which in addition to the information provided by SDMF format, can also provide the directory listed name for the particular number. Caller ID readers which are compatible with MDMF can also read the simpler SDMF format, but an SDMF caller ID reader will not recognize an MDMF data stream, and will act as if there is no caller ID information present, e.g. as if the line is not equipped for caller ID. STANDARDS **Multiple data message format (MDMF)** **The one you Handle PERFECTLY:** > the multiple data message format (MDMF), is more complex and versatile than the SDMF. > It is capable of delivering more data concerning an incoming call, such > as the name of a calling party. Although both formats share some > features in common such as the message type and the message length > parameters, the structure of the MDMF is more flexible and more readily > accommodates the development of new provider services. > As with SDMF, the message type parameter is the first byte of an MDMF > formatted packet. Since MDMF is designed to provide a wider variety of > information than SDMF, six message type values are specified for it > instead of the three defined for SDMF. The message type value > identifying a Caller ID data block is 0x80, 128 decimal. The message > length parameter, the next byte in the frame, specifies the number of > bytes that follow in the data block. It is after the message length > parameter, that the structure of an MDMF packet differs from that of a > SDMF. > At this point, the message block is broken up into smaller messages > called parameter messages. Each parameter message is composed of > a parameter type value, a parameter length value, and an accompanying > data block that contains a specific type of information, such as the > number of an incoming call. Each piece of information that is transmitted > in an MDMF formatted packet, such as the time and date, calling > number, and the calling name, is packaged within its own parameter > message. This encapsulation of data enables a service provider to > selectively add to or omit information from Caller ID transmissions. > As its name suggests, the parameter type value is used to identify the > type of data contained in a parameter message. Currently, 17 parameter > type values are defined for MDMF. The values of most interest to Caller > ID capable equipment are 0x01, 0x02, and 0x07 which identify a time > and date, number, and name parameter message respectively. This > parameter is followed by the parameter length value which contains the > remaining number of bytes in a parameter message’s data block. Single data message format (SDMF) **The one your DLL NOT HANDLE** > The message assembly layer forms an SDMF formatted packet by > prepending a 2-byte header to a Caller ID data packet. The first byte of > the header is the packet’s message type parameter value. This value > alerts a Caller ID device as to the type of information that is contained in > the accompanying data block. There are currently three values defined > for the message type parameter of SDMF formatted packets. A packet > with a message type value of 0x04 contains the number of a calling > party, a value of 0x06 indicates a message waiting indicator packet, and > a value of 0x0B has been reserved for future applications. The next byte > in the header is the message length parameter. This parameter, as its > name suggests, contains the number of bytes of Caller ID data that > remain in a block.The message assembly layer also specifies the arrangement of > information within the data portion of a frame. The data portion of an > SDMF frame consists of ASCII codes arranged in three fields > representing the date, time, and number of an incoming call. > The date field which is the first piece of information in the data > block, consists of 4 bytes. The first two bytes are ASCII codes for > the digits representing the month and the other two represent the > day. Any months or days that can be represented by a single digit, > are preceded by a zero. > • The next 4 bytes are ASCII codes for digits representing the time. > The first two bytes are the ASCII codes for the digits representing > the hour and the remaining two represent the minutes. The values > in the hour field are allowed to range from 0 to 23, while the > minutes can range from 0 to 59. > • The remaining 10 ASCII codes represent the digits of the > telephone phone number of the incoming call. If the incoming call > is a local call and lacks an area code, the area code portion of the > number field is filled by default with the ASCII codes for three > zeroes. Thanks for your time. Regards. ---
**Author:** ![emre](https://forum.sambapos.com/user_avatar/forum.sambapos.com/emre/32/39073_2.png) [@emre](https://forum.sambapos.com/u/emre)\ **Post date:** [October 31, 2016, 1:07pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/62 "2016-10-31T13:07:10Z")
OK. I already wasted hours while trying to validate it. I’m rolling back and compile your code. Please stay tuned until I finish my work. ---
**Author:** ![digithai](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@digithai](https://forum.sambapos.com/u/digithai)\ **Post date:** [October 31, 2016, 1:08pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/63 "2016-10-31T13:08:27Z")
THANKS… you rock! Just try to handle “our patch” in the ELSE statement (that today you ignore) Many thanks. ---
**Author:** ![JTRTech](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jtrtech/32/21270_2.png) [@JTRTech](https://forum.sambapos.com/u/JTRTech)\ **Post date:** [October 31, 2016, 1:17pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/64 "2016-10-31T13:17:34Z")
> [@digithai](#): > > You don’t have to trust me or either putty log, you should trust the Telco STANDARDS for CALLER ID. > I rewrite below for your convenience the 2 TYPES of packed DATA available WORLDWIDE and their structure . If you implement the SMDF you CANNOT mistake, is standard > From Wikipedia While this is all above my experiance level, this doesnt make sence to me,if Samba was not configured acording to the standards of caller ID how would the hundreds of other people using caller id device be doing so? ---
**Author:** ![QMcKay](https://forum.sambapos.com/user_avatar/forum.sambapos.com/qmckay/32/27925_2.png) [@QMcKay](https://forum.sambapos.com/u/QMcKay)\ **Post date:** [October 31, 2016, 1:25pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/65 "2016-10-31T13:25:08Z")
> [@digithai](#): > > Maybe we can (not aware of btw) , but why to create a component that duplicate a functionality that is already there but has a defect? Because it might be faster for you than waiting ;), since it seems this is very urgent, and like you say … > [@digithai](#): > > Would be a temporarily code (workaround) until the bug is not fixed. ---
**Author:** ![digithai](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@digithai](https://forum.sambapos.com/u/digithai)\ **Post date:** [October 31, 2016, 1:36pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/66 "2016-10-31T13:36:00Z")
> [@JTRTech](#): > > While this is all above my experiance level, this doesnt make sence to me,if Samba was not configured acording to the standards of caller ID how would the hundreds of other people using caller id device be doing so? Ok, I don’t pretend you to read all above again, but probably the 99% of SambaPos Users are located in USA or EU Where TELCO STANDARD Bell UK included USE MDMF Standard. And SambaPOS handle PERFECTLY! Here in ASIA (Thailand specifically) The TELCO provider send CALLER ID as SMDF STANDARD and Samba DOES NOT HANDLE. Probably we are the first customers handling Caller ID in ASIA with SambaPos? That’s why most of your user has CallerId module work perfectly. Does make sense now? 🙂 Cheers ---
**Author:** ![emre](https://forum.sambapos.com/user_avatar/forum.sambapos.com/emre/32/39073_2.png) [@emre](https://forum.sambapos.com/u/emre)\ **Post date:** [October 31, 2016, 2:01pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/67 "2016-10-31T14:01:38Z")
Here is the compiled dll. [Samba.Addon.CalleridDevices.dll.zip](https://forum.sambapos.com/uploads/default/original/3X/1/e/1efb47c26a6009d6bdb3c7c1545c0d4557b57ffe.zip) (12.9 KB) ---
**Author:** ![digithai](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@digithai](https://forum.sambapos.com/u/digithai)\ **Post date:** [November 1, 2016, 2:48am UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/68 "2016-11-01T02:48:45Z")
WHAT A GOOD NEWS ! We tried your DLL and now the Caller ID ShowUp perfectly!! After more than 4 months we figured out! Maybe you can introduce these change in the next release of SambaPos. THANKS for your support, and finally we can have SambaPos works as expected! Glad to try to help you find and optimize Samba Module! Cheers! ![](https://forum.sambapos.com/uploads/default/original/3X/e/a/ea47eba0afd690ddb5e8f145e6d67b136c821c7c.jpg) ---
**Author:** ![morshed1](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/8c91f0/32.png) [@morshed1](https://forum.sambapos.com/u/morshed1)\ **Post date:** [February 22, 2017, 10:35pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/69 "2017-02-22T22:35:32Z")
Hi emre, I’m seeing similar issue with CTI COMET Caller ID device. I’m not sure what is going on, I initially thought the issue was with faulty CTI COMET device so i ordered a another unit for testing but I’m seeing same issue/behaviour with new unit. I believe the issue started after updating to one of the BETA version 5.1.6x at that time I thought the issue was due to faulty unit so I do not raise the issue. Nothing new changed with my telephone line/ provider, I have always tested the Caller ID device on the same phone line and did not come across this issue before for the last 2/3 years. My testing environment has not changed. I have double checked the caller ID feature and its active on the Telephone line (BT). This issue has been going since January. Below is screen captures of what is displayed by SAMBAPOS when call is received , corrupted phone number displayed, COMET CID error or no pop up message at all. Corrupted number/text: ![](https://forum.sambapos.com/uploads/default/original/3X/e/d/edb0bc0a2ab5aa7177c4b0062d1adf0ed1bbb2c8.png) COMET CID error ![](https://forum.sambapos.com/uploads/default/original/3X/1/1/110ea362ab2af05e80ac642135004a921d1217de.png) Actual RealTerm: Serial Capture when phone is dialed [2017-02-22\_20-55-24-RealTerm Serial Capture.zip](https://forum.sambapos.com/uploads/default/original/3X/f/a/fa2bee42480d15c97e01cf1bf9346cf8f9fb91f1.zip) (65.7 KB) Output from Putty when call received ![](https://forum.sambapos.com/uploads/default/original/3X/2/c/2cc9260efd9fb64eff5db6b318148f42c5336d37.png) ![](https://forum.sambapos.com/uploads/default/original/3X/0/9/093b779b555f85b680882b389c2e63311d0ad295.png) Tested with different Baud rate settings. ![](https://forum.sambapos.com/uploads/default/original/3X/a/8/a83adf39b24f21e0996107d5bf86d2cb5cd63a85.png) I have also tried updated BETA version. ![](https://forum.sambapos.com/uploads/default/original/3X/e/9/e9da04a01034cecb74d2d675ee91050d5da5c39f.png) Original Diagnostics check: 21 January 2017 ![](https://forum.sambapos.com/uploads/default/original/3X/3/8/38315784a62bb21eb92edb25eda9a58093553525.png) Note: I have also tested with the compiled dll,. no luck. ![](https://forum.sambapos.com/uploads/default/original/3X/d/d/dd9651173d0929693fdb0459903776f90b69fad2.jpg) would be interesting to see any other members in UK have come across this issue. ---
**Author:** ![JTRTech](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jtrtech/32/21270_2.png) [@JTRTech](https://forum.sambapos.com/u/JTRTech)\ **Post date:** [February 22, 2017, 11:14pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/70 "2017-02-22T23:14:30Z")
I am reading that and seeing that putty is not showing number as expected either? is that correct? If putty isnt getting number as expected samba wont either… ---
**Author:** ![morshed1](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/8c91f0/32.png) [@morshed1](https://forum.sambapos.com/u/morshed1)\ **Post date:** [February 22, 2017, 11:45pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/71 "2017-02-22T23:45:02Z")
correction, putty display the number when speed set to 1200 Below is the output from putty with below settings - Speed 9600 ![](https://forum.sambapos.com/uploads/default/original/3X/8/a/8a1d6e292ab65e8c7838ea0bc285af4188ba389c.JPG) CTI comet correct speed settings: 1200 - number is displayed. ![](https://forum.sambapos.com/uploads/default/original/3X/3/2/32507c966f058081ab2cbd336b4114cefae8dc73.JPG) ![](https://forum.sambapos.com/uploads/default/original/3X/2/3/239f6e0020e0da52a8ad5199ffa9de7858c93af3.JPG) ---
**Author:** ![JTRTech](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jtrtech/32/21270_2.png) [@JTRTech](https://forum.sambapos.com/u/JTRTech)\ **Post date:** [February 22, 2017, 11:53pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/72 "2017-02-22T23:53:47Z")
If putty isn’t getting good output samba has no chance. If putty has issue its not samba related… ---
**Author:** ![morshed1](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/8c91f0/32.png) [@morshed1](https://forum.sambapos.com/u/morshed1)\ **Post date:** [February 23, 2017, 12:08am UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/73 "2017-02-23T00:08:40Z")
not sure what is going on its working on Sambapos now… I will need to do more testing with both units I have tried with below settings before and it was playing up. ![](https://forum.sambapos.com/uploads/default/original/3X/a/0/a05015368f088fb2e5a31d178579ec8fd6ee33c4.png)… ![](https://forum.sambapos.com/uploads/default/original/3X/4/f/4fbe46893b3b481b284ccb71fc104e8ff8faf96a.jpg) ---
**Author:** ![emre](https://forum.sambapos.com/user_avatar/forum.sambapos.com/emre/32/39073_2.png) [@emre](https://forum.sambapos.com/u/emre)\ **Post date:** [February 23, 2017, 8:56am UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/74 "2017-02-23T08:56:21Z")
Did you checked how it works with 5.1.60? ---
**Author:** ![morshed1](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/8c91f0/32.png) [@morshed1](https://forum.sambapos.com/u/morshed1)\ **Post date:** [February 23, 2017, 11:46pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/75 "2017-02-23T23:46:11Z")
I have uninstalled version 5.1.61 and then reinstalled 5.1.60 to test…getting following error message when trying to load. * * * [General Info] Application: SambaPOS Version: 5.1.60 Region: en DB: SQ Machine: NUC1 User: main Date: 23/02/2017 Time: 23:42 User Explanation: ## main said “” [Exception Info 1] Top-level Exception Type: System.Reflection.ReflectionTypeLoadException Message: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. Source: mscorlib Stack Trace: at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at System.Reflection.RuntimeModule.GetTypes() at System.Reflection.Assembly.GetTypes() at System.ComponentModel.Composition.Hosting.AssemblyCatalog.get\_InnerCatalog() at System.ComponentModel.Composition.Hosting.AssemblyCatalog.GetEnumerator() at System.Linq.Enumerable.d\_\_16`2.MoveNext() at Microsoft.Practices.Prism.MefExtensions.DefaultPrismServiceRegistrar.GetRequiredPrismPartsToRegister(AggregateCatalog aggregateCatalog) at Microsoft.Practices.Prism.MefExtensions.DefaultPrismServiceRegistrar.RegisterRequiredPrismServicesIfMissing(AggregateCatalog aggregateCatalog) at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.RegisterDefaultTypesIfMissing() at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration) at Samba.Presentation.App.RunInReleaseMode() * * * [Assembly Info] mscorlib, Version=4.0.0.0 Samba.Services, Version=1.0.0.0 Samba.Domain, Version=1.0.0.0 Samba.Infrastructure.Data, Version=1.0.0.0 System.ComponentModel.Composition, Version=4.0.0.0 System.Core, Version=4.0.0.0 PresentationCore, Version=4.0.0.0 DevExpress.Xpf.LayoutControl.v14.1, Version=14.1.13.0 System.Xml, Version=4.0.0.0 DevExpress.Xpf.Grid.v14.1, Version=14.1.13.0 System, Version=4.0.0.0 DevExpress.Xpf.Grid.v14.1.Core, Version=14.1.13.0 WindowsBase, Version=4.0.0.0 System.Xaml, Version=4.0.0.0 PresentationFramework, Version=4.0.0.0 Samba.Infrastructure, Version=1.0.0.0 Microsoft.Practices.Prism, Version=4.0.0.0 System.Runtime.Serialization, Version=4.0.0.0 Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0 DevExpress.Xpf.Core.v14.1, Version=14.1.13.0 Samba.Presentation.Services, Version=1.0.0.0 System.Windows.Forms, Version=4.0.0.0 System.Drawing, Version=4.0.0.0 Stateless, Version=1.0.0.0 Samba.Persistance, Version=1.0.0.0 PropertyTools, Version=2012.4.14.1 Samba.Localization, Version=1.0.0.0 ReachFramework, Version=4.0.0.0 EntityFramework, Version=6.0.0.0 FluentValidation, Version=3.4.0.0 Omu.ValueInjecter, Version=2.3.0.0 Microsoft.Practices.ServiceLocation, Version=1.0.0.0 Microsoft.CSharp, Version=4.0.0.0 * * * [System Info] Operating System -Microsoft Windows 10 Pro –CodeSet = 1252 –CSDVersion = –CurrentTimeZone = 0 –FreePhysicalMemory = 6696828 –OSArchitecture = 64-bit –OSLanguage = 2057 –ServicePackMajorVersion = 0 –ServicePackMinorVersion = 0 –Version = 10.0.14393 Machine -NUC1 * * * ---
**Author:** ![emre](https://forum.sambapos.com/user_avatar/forum.sambapos.com/emre/32/39073_2.png) [@emre](https://forum.sambapos.com/u/emre)\ **Post date:** [February 23, 2017, 11:47pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/76 "2017-02-23T23:47:35Z")
After uninstall delete all remaining files under installation folder and re-install. ---
**Author:** ![Hasa](https://forum.sambapos.com/user_avatar/forum.sambapos.com/hasa/32/50950_2.png) [@Hasa](https://forum.sambapos.com/u/Hasa)\ **Post date:** [February 24, 2017, 2:22am UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/77 "2017-02-24T02:22:44Z")
Just wanna mention here that Whozz Calling Caller ID Devices work REALLY Well. [http://callerid.com/](http://callerid.com/) ---
**Author:** ![morshed1](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/8c91f0/32.png) [@morshed1](https://forum.sambapos.com/u/morshed1)\ **Post date:** [March 1, 2017, 9:17pm UTC](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361/78 "2017-03-01T21:17:32Z")
> After uninstall delete all remaining files under installation folder and re-install. I have tried that and it did work… so as a test I carried out fresh installation of o/s and Sambapos on a different unit to isolate every thing and I was still seeing the same issue with caller ID. Now getting the phone line checked with Phone Line provider (BT), they have acknowledged there was an issue on the line and currently investigating [Previous page](https://forum.sambapos.com/t/comet-usb-caller-id-setup-issue/11361.md?page=3)