standard dialable number format (c++ tapi) - c++

I want to programatically make calls on a windows mobile device using standard c++ TAPI lineMakeCall function. The phone number (null-terminated) must be in the "standard dialable number format".
There is a function lineTranslateAddress which should make the conversion to the dialable format.
I am testing my application and if I use a nonformated string (ex: 0728000000, valid for my country), this number is dialed but not recognized (The dialing screen shows: Dialing: Unknown).
I cannot find much information about this standard format. Does anyone know something about this format, how it should look, or is it secret?
Help please,
Thanks,

Here is the MSDN documentation page describing this format: Dialable Addresses

Related

Represent international phone numbers in Cloud Spanner

What would be the best way to represent international phone numbers in Google Cloud Spanner? I would like it to be consistent with the protos defined here.
I am going on the fact that the phone numbers that I need to capture are of the e164_number format and I have represented the extension (as in the proto) as a STRING column. This is a potential fix, but I feel like there could be a more correct solution. Any help would be appreciated.
It sounds like your use case is a good fit for JSON type which Cloud Spanner now supports. You should be able to create a corresponding JSON representation for the phone_number.proto that you have linked. Please see https://cloud.google.com/spanner/docs/working-with-json for how-to as well as examples of how to query individual fields during reads.

How does GDB pretty printer know the output format the user is requesting?

I have a few complex classes generated by a third party domain-specific tool. The classes are complex because the tool tries to be generic as much as possible, so that I was asked to design a GDB pretty printer python script to improve the debugging experience.
I designed it by "to_string" APIs which can print the information with organized rich text (e.g. colors), so far everything works fine.
However, I don't know how to get the output format user requests, no matter that user uses "p" or "p/x" will all output the same string because my script does not know user wants hex rather than decimal.
I tried googling but didn't figure out an elegant approach. I indeed have a few workarounds but they all change the usages (for example, implement two printers to be switched), please give me some suggestions, thank you.
Just realized there had been a feature request to GDB already.
Bug 17291 - IWBN if the print format was available to pretty-printers.

How to detect the carrier for a phone number in India?

This could be a locale specific question. I am trying to find out the network operator for a given phone number. I have seen a similar service on www.bmobile.in but unable to find any documentation w.r.t APIs etc. It seems to work even with numbers who have switched operators while retaining the number. It shows the original operator the number was registered with.
Hy! You can try using this web-app:
http://www.fonefinder.net/

Automatically selecting incomming telephone call with Java

I want to select incoming calls based on user input. E.g. by matching the telephone number to the user input number. To get user input number I used Java.
What are the best hardwares supporting to this requirement. I guess this hardware should allow us to call API and get current caller number. Then we can do the selection part using Java. After that we can another API method ans allow that call to proceed.
Let me know about the suitable hardware for this.
You have a number of options depending on how your incoming calls are presented - if you are lucky enough that they are coming in to a PABX which has some form of computer telephony interface (CTI) then you just need to interface your Java app to the PABX (many Cisco, Avaya etc pABX's will support some form of CTI).
If your calls come in on a standard line to a standard phone today, then you can either replace the phone with a simple commercial PABX (if you have the budget) or you can create your own PABX using one of the open source options and some line cards - see the answer to this question for a link to an example line card for the open source Asterix PABX:
https://stackoverflow.com/a/18220055/334402
If you have the option of a hosted VoIP 'telephone line' then it would be worth contacting your provider as they may provide hosted CTI options, saving you the need to get dedicated hardware.

KORMARC to MARC21 converter

Does anyone know if there is a free open-source solution to convert KORMARC (Korean MARC) into MARC21 (aka USMARC)?
While I'm not certain it has KORMARC support, you may want to try USEMARCON if you can find a mapping. From the USEMARCON page:
USEMARCON facilitates the conversion of catalogue records from one MARC format to another e.g. from UKMARC to UNIMARC. The software was designed as a toolbox-style application, allowing users with detailed knowledge of the source and target MARC formats to develop rules governing the behaviour of the conversion. Rules files may be supplemented by additional tables for more accurate conversion of MARC-specific character sets or coded information. The tables and rules files are simple ASCII text files and can be created using any standard text editor such as MS Windows Notepad.
Also, this thread from the Ask a Korean Studies Librarian Google Group might be useful, particularly the following message:
Library of Congress once tried to download records from the National
Library of Korea (NLK) to use as order records. LC wrote a
specification and developed a in-house program to convert KORMARC to
USMARC. Since NLK records only provide script, LC used a
transliterator to provide romanization for Voyager system developed by
non-LC programmer. The feedback of this method is not very positive
by LC staff. ... In stead of converting KORMARC to USMARC, a few research libraries
including LC is currently using MarcEdit with Excel spreadsheets which
are provided by Korean vendors based on contract. Vendors provide
both Korean script and romanization for several elements of MARC
fields (ISBN, title, author, publisher, place, series, etc.) in
different columns of spreadsheet for your order items. It sounds a
lot simpler to set up initially. And once MarcEdit is set up
properly, it creates MARC records.